| /linux-6.3-rc2/drivers/pinctrl/intel/ |
| A D | Kconfig | 24 allows configuring of SoC pins and using them as GPIOs.
37 using them as GPIOs.
75 of Intel Alder Lake PCH pins and using them as GPIOs.
83 configuring of SoC pins and using them as GPIOs.
99 of Intel Cedar Fork PCH pins and using them as GPIOs.
107 of Intel Denverton SoC pins and using them as GPIOs.
123 of Intel Emmitsburg pins and using them as GPIOs.
139 of Intel Ice Lake PCH pins and using them as GPIOs.
163 of Intel Lewisburg pins and using them as GPIOs.
171 of Intel Meteor Lake pins and using them as GPIOs.
[all …]
|
| /linux-6.3-rc2/Documentation/admin-guide/mm/ |
| A D | swap_numa.rst | 17 to be swapped on. Simply swapping them on by doing::
24 that the order of them being swapped on doesn't matter.
29 The way to swap them on is the same as above::
38 Then node 0 will use them in the order of::
44 node 1 will use them in the order of::
48 node 2 will use them in the order of::
55 node 3 will use them in the order of::
|
| /linux-6.3-rc2/drivers/staging/media/ |
| A D | Kconfig | 8 Most of them don't follow properly the V4L, DVB and/or RC API's,
13 If you wish to work on these drivers, to help improve them, or
14 to report problems you have with them, please use the
22 # Please keep them in alphabetic order
|
| /linux-6.3-rc2/Documentation/hwmon/ |
| A D | vexpress.rst | 28 from a wide range of boards, each of them containing (apart of the main
33 temperature and power usage. Some of them also calculate consumed energy
40 Tree passed to the kernel. Details of the DT binding for them can be found
|
| /linux-6.3-rc2/Documentation/i2c/ |
| A D | ten-bit-addresses.rst | 8 address 0x10 (though a single device could respond to both of them).
21 hardware doesn't support them (SMBus doesn't require 10-bit address
33 needs them to be fixed.
|
| /linux-6.3-rc2/drivers/staging/ |
| A D | Kconfig | 8 them. Please note that these drivers are under heavy
17 If you wish to work on these drivers, to help improve them, or
18 to report problems you have with them, please see the
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/pwm/ |
| A D | clk-pwm.yaml | 14 (e.g. by muxing them to GPIO pins)
15 It's often possible to control duty-cycle of such clocks which makes them
|
| /linux-6.3-rc2/Documentation/admin-guide/ |
| A D | abi-testing.rst | 9 errors or security problems are found in them.
17 developers can easily notify them if any changes occur.
|
| /linux-6.3-rc2/Documentation/driver-api/ |
| A D | isa.rst | 22 to the driver creating them because it might want to drive them, meaning
54 them in at all. The id is the only thing we ever want other then the
60 of the old .probe in .match, which would only keep them registered after
78 loops over the passed in ndev creating devices and registering them.
79 This causes the bus match method to be called for them, which is::
|
| /linux-6.3-rc2/Documentation/ |
| A D | Kconfig | 21 have errors that would break them for being parsed by
22 scripts/get_abi.pl. Add a check to verify them.
|
| /linux-6.3-rc2/drivers/media/usb/ttusb-dec/ |
| A D | Kconfig | 19 download/extract them, and then copy them to /usr/lib/hotplug/firmware
|
| /linux-6.3-rc2/tools/testing/selftests/tc-testing/plugin-lib/ |
| A D | README-PLUGINS | 14 tdc.py will find them and use them.
|
| /linux-6.3-rc2/Documentation/ABI/stable/ |
| A D | sysfs-firmware-opal-elog | 18 but not explicitly acknowledged them to firmware and
24 entries, read them out and acknowledge them.
|
| /linux-6.3-rc2/Documentation/admin-guide/pm/ |
| A D | suspend-flows.rst | 32 cannot be implemented without platform support and the difference between them
34 resume hooks that need to be provided by the platform driver to make them
53 That allows them to prepare for the change of the system state and to clean
84 accessed in more than two of them.
97 transition of the system is started when one of them signals an event.
102 into the deepest available idle state. While doing that, each of them
114 interrupt that woke up one of them comes from an IRQ that has been armed for
144 accessed in more than two of them.
161 "notification type" parameter value is passed to them.
187 when all CPUs in them are in sufficiently deep idle states and all I/O
|
| /linux-6.3-rc2/Documentation/bpf/libbpf/ |
| A D | libbpf_build.rst | 21 To build only static libbpf.a library in directory build/ and install them
31 dependency installed in /build/root/ and install them together with libbpf
|
| /linux-6.3-rc2/Documentation/ABI/testing/ |
| A D | sysfs-firmware-efi-runtime-map | 12 can reassemble them and pass them into the kexec kernel.
|
| /linux-6.3-rc2/Documentation/input/ |
| A D | gamepad.rst | 45 differently labeled on most devices so we define them as NORTH,
57 Analog-sticks may also provide a digital button if you press them.
60 Not all devices provide them, but the upper buttons are normally named
74 Legacy drivers often don't comply to these rules. As we cannot change them
76 user-space yourself. Some of them might also provide module-options that
85 and one analog stick. It reports them as if it were a gamepad with only one
|
| /linux-6.3-rc2/drivers/memstick/core/ |
| A D | Kconfig | 13 normal behaviour is to remove them at suspend and
14 redetecting them at resume. Breaking this assumption will
|
| /linux-6.3-rc2/Documentation/core-api/ |
| A D | boot-time-mm.rst | 34 macros. Some of them are actually internal, but since they are
35 documented it would be silly to omit them. Besides, reading the
|
| A D | netlink.rst | 24 to match them up, and we have plenty of ID space.
27 sort the notifications from replies (and present them to the user
54 them - make sure to report dump inconsistency with ``NLM_F_DUMP_INTR``.
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/leds/ |
| A D | ti,tca6507.yaml | 14 7 separate lines either by holding them low, or by pulsing them with modulated
|
| /linux-6.3-rc2/drivers/leds/ |
| A D | TODO | 13 not sleep.) Review the requirements for any bugs and document them
62 them up.
65 clean them up.
|
| /linux-6.3-rc2/Documentation/driver-api/acpi/ |
| A D | scan_handlers.rst | 28 information from the device objects represented by them and populating them with
29 appropriate data, but some of them require additional handling after they have
56 to match a scan handler against each of them using the ids arrays of the
|
| /linux-6.3-rc2/Documentation/parisc/ |
| A D | registers.rst | 113 r1,r2,r19-r26,r28,r29 & r31 can be used without saving them first. And of
114 course, you need to save them if you care about them, before calling
136 these are arg3-arg0, i.e. you can use them if you
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/bus/ |
| A D | baikal,bt1-apb.yaml | 15 which routes them to the AXI-APB bridge. This interface is a single master
16 multiple slaves bus in turn serializing IO accesses and routing them to the
|