| /linux/drivers/pinctrl/intel/ |
| H A D | Kconfig | 22 allows configuring of SoC pins and using them as GPIOs.
30 using them as GPIOs.
46 of Intel PCH pins and using them as GPIOs. Currently the following
56 of Intel Alder Lake PCH pins and using them as GPIOs.
63 configuring of SoC pins and using them as GPIOs.
70 of Intel Cannon Lake PCH pins and using them as GPIOs.
77 of Intel Cedar Fork PCH pins and using them as GPIOs.
84 of Intel Denverton SoC pins and using them as GPIOs.
91 of Intel Elkhart Lake SoC pins and using them as GPIOs.
98 of Intel Emmitsburg pins and using them as GPIOs.
[all …]
|
| H A D | Kconfig.tng | 22 an interface that allows configuring of SoC pins and using them as
30 an interface that allows configuring of SoC pins and using them as
|
| /linux/Documentation/admin-guide/mm/ |
| H 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/Documentation/hwmon/ |
| H 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/Documentation/i2c/ |
| H 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/Documentation/driver-api/ |
| H 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/Documentation/filesystems/bcachefs/ |
| H A D | CodingStyle.rst | 6 Good development is like gardening, and codebases are our gardens. Tend to them
32 are logically impossible. (Or, make them debug mode assertions if they're
47 means that you can run them in only a few places in the checked in version, but
49 quickly shotgun them everywhere to find the codepath that broke the invariant.
71 percpu data structures among them. Don't let things stay hidden.
76 Pretty printers are wonderful, because they compose and you can use them
88 the issue. It's worth putting effort into them.
118 Users notice all sorts of interesting things, and by just talking to them and
119 interacting with them you can benefit from their experience.
134 Expect to throw a lot of things away, or leave them half finished for later.
|
| /linux/Documentation/admin-guide/ |
| H 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/Documentation/ |
| H 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/Documentation/admin-guide/pm/ |
| H 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/drivers/media/usb/ttusb-dec/ |
| H A D | Kconfig | 19 download/extract them, and then copy them to /usr/lib/hotplug/firmware
|
| /linux/tools/testing/selftests/tc-testing/plugin-lib/ |
| H A D | README-PLUGINS | 14 tdc.py will find them and use them.
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-firmware-opal-elog | 18 but not explicitly acknowledged them to firmware and
24 entries, read them out and acknowledge them.
|
| /linux/Documentation/trace/coresight/ |
| H A D | coresight-dummy.rst | 15 platforms. For these devices, a dummy driver is needed to register them as
19 disabling them. It also provides the Coresight dummy sink/source paths for
|
| /linux/drivers/peci/controller/ |
| H A D | Kconfig | 12 connected to it, and communicate with them using PECI protocol.
28 to it and communicate with them using PECI protocol.
|
| /linux/Documentation/bpf/libbpf/ |
| H 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/Documentation/input/ |
| H 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/tools/include/uapi/ |
| H A D | README | 10 including them to compile something.
48 headers and broke them accidentally for kernel builds.
67 and integate them into the tooling build. The warnings above serve as a
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-efi-runtime-map | 12 can reassemble them and pass them into the kexec kernel.
|
| /linux/Documentation/driver-api/acpi/ |
| H 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/Documentation/arch/parisc/ |
| H 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/drivers/memstick/core/ |
| H A D | Kconfig | 13 normal behaviour is to remove them at suspend and
14 redetecting them at resume. Breaking this assumption will
|
| /linux/Documentation/core-api/ |
| H 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
|
| /linux/drivers/leds/ |
| H A D | TODO | 13 not sleep.) Review the requirements for any bugs and document them
62 them up.
65 clean them up.
|
| /linux/drivers/hid/bpf/progs/ |
| H A D | README | 4 fix some behaviors without being entirely mandatory. It is better to load them
14 "upstream" them, but also this way we can test them thanks to the HID
|