| /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
|
| H A D | userspace-tools.rst | 19 setup monitoring limits etc. You can get them on their homepage
32 3) load them and run "sensors" command, you should see some results.
|
| /linux/drivers/staging/ |
| H 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/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/drivers/pinctrl/intel/ |
| 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/ |
| H A D | Kconfig | 21 have errors that would break them for being parsed by
22 tools/docs/get_abi.py. Add a check to verify them.
|
| /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/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/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/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/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/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/ABI/testing/ |
| H A D | sysfs-firmware-efi-runtime-map | 12 can reassemble them and pass them into the kexec kernel.
|
| /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
|
| H 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/fs/crypto/ |
| H A D | Kconfig | 18 # whereas selecting them from FS_ENCRYPTION would force them to be built-in.
|
| /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/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
|
| /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/Documentation/arch/x86/x86_64/ |
| H 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.
|