| /linux/drivers/pinctrl/intel/ |
| A D | Kconfig | 24 allows configuring of SoC pins and using them as GPIOs.
37 using them as GPIOs.
64 of Intel Alder Lake PCH pins and using them as GPIOs.
72 configuring of SoC pins and using them as GPIOs.
88 of Intel Cedar Fork PCH pins and using them as GPIOs.
96 of Intel Denverton SoC pins and using them as GPIOs.
112 of Intel Emmitsburg pins and using them as GPIOs.
128 of Intel Ice Lake PCH pins and using them as GPIOs.
144 of Intel Lakefield SoC pins and using them as GPIOs.
152 of Intel Lewisburg pins and using them as GPIOs.
[all …]
|
| /linux/Documentation/admin-guide/mm/ |
| A D | swap_numa.rst | 19 to be swapped on. Simply swapping them on by doing::
26 that the order of them being swapped on doesn't matter.
31 The way to swap them on is the same as above::
40 Then node 0 will use them in the order of::
46 node 1 will use them in the order of::
50 node 2 will use them in the order of::
57 node 3 will use them in the order of::
|
| /linux/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/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/Documentation/x86/ |
| A D | microcode.rst | 89 somewhere else and/or you've downloaded them directly from the processor
111 packages already put them there.
137 so that the build system can find those files and integrate them into
138 the final kernel image. The early loader finds them and applies them.
|
| /linux/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/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/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
|
| A D | cpuidle.rst | 23 Since part of the processor hardware is not used in idle states, entering them
39 (program) from memory and executing them, but it need not work this way
49 work physically in parallel with each other, so if each of them executes only
70 by one of them, the hardware thread (or CPU) that asked for it is stopped, but
99 to allow them to make some progress over time.]
194 allow them to make reasonable progress in a given time frame is to make them
295 and variance of them. If the variance is small (smaller than 400 square
463 between them is that the name is expected to be more concise, while the
540 global CPU latency limit and for each individual CPU, aggregates them and
616 them affect Intel processors only.
[all …]
|
| /linux/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/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/Documentation/ |
| A D | Kconfig | 20 have errors that would break them for being parsed by
21 scripts/get_abi.pl. Add a check to verify them.
|
| /linux/drivers/media/usb/ttusb-dec/ |
| A D | Kconfig | 19 download/extract them, and then copy them to /usr/lib/hotplug/firmware
|
| /linux/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/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/tools/testing/selftests/tc-testing/plugin-lib/ |
| A D | README-PLUGINS | 14 tdc.py will find them and use them.
|
| /linux/Documentation/devicetree/bindings/mmc/ |
| A D | brcm,sdhci-brcmstb.txt | 7 on Device Tree properties to enable them for SoC/Board combinations
8 that support them.
|
| /linux/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/Documentation/ABI/testing/ |
| A D | sysfs-firmware-efi-runtime-map | 12 can reassemble them and pass them into the kexec kernel.
|
| /linux/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/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/Documentation/x86/x86_64/ |
| A D | fsgs.rst | 95 The availability of the instructions does not enable them
96 automatically. The kernel has to enable them explicitly in CR4. The
98 the GS register and enforce them when GS base is set via
107 kernel has FSGSBASE instructions enabled and applications can use them.
129 instructions. Clang 5 supports them as well.
|
| /linux/tools/power/pm-graph/ |
| A D | README | 437 It is possible to add new function calls to the timeline by adding them to
439 the config so that you can override and edit them. Place them in the
444 custom calls, or leave it false to append them to the internal ones.
454 them.
511 It is possible to add new function calls to the dev timeline by adding them
513 functions into the config so that you can override and edit them. Place them
518 custom calls, or leave it false to append them to the internal ones.
529 them.
544 actually supports them. To do this, run the tool with your config file
546 custom and internal if you haven't overridden them) and actually attempts
[all …]
|
| /linux/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/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
|