Searched refs:them (Results 1 – 25 of 1005) sorted by relevance
12345678910>>...41
| /Linux-v4.19/drivers/pinctrl/intel/ |
| D | Kconfig | 32 allows configuring of SoC pins and using them as GPIOs.
42 interface that allows configuring of SoC pins and using them as
59 configuring of SoC pins and using them as GPIOs.
67 of Intel Cannon Lake PCH pins and using them as GPIOs.
75 of Intel Cedar Fork PCH pins and using them as GPIOs.
83 of Intel Denverton SoC pins and using them as GPIOs.
91 of Intel Gemini Lake SoC pins and using them as GPIOs.
99 of Intel Ice Lake PCH pins and using them as GPIOs.
107 of Intel Lewisburg pins and using them as GPIOs.
116 using them as GPIOs.
|
| /Linux-v4.19/drivers/staging/media/ |
| D | Kconfig | 7 Most of them don't follow properly the V4L, DVB and/or RC API's,
12 If you wish to work on these drivers, to help improve them, or
13 to report problems you have with them, please use the
21 # Please keep them in alphabetic order
|
| /Linux-v4.19/Documentation/vm/ |
| 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-v4.19/Documentation/hwmon/ |
| D | vexpress | 21 from a wide range of boards, each of them containing (apart of the main
26 temperature and power usage. Some of them also calculate consumed energy
33 Tree passed to the kernel. Details of the DT binding for them can be found
|
| D | userspace-tools | 16 setup monitoring limits etc. You can get them on their homepage
29 3) load them and run "sensors" command, you should see some results.
|
| /Linux-v4.19/Documentation/x86/ |
| D | microcode.txt | 83 somewhere else and/or you've downloaded them directly from the processor
105 packages already put them there.
131 so that the build system can find those files and integrate them into
132 the final kernel image. The early loader finds them and applies them.
|
| D | intel_mpx.txt | 105 them somewhere. It has two special instructions for this which allow
117 the instructions for moving bounds in and out of them are extremely
124 are a few ways this could be done. We don't think any of them are practical
128 never have to allocate them?
132 even if we clean them up aggressively. In the worst-case scenario, the
136 If we were to preallocate them for the 128TB of user virtual address
160 bounds tables that we could think of, we create them on demand in
200 knowledge, it is also responsible for freeing them when the associated
233 directory at them through XSAVE instruction, and then set valid bit
238 them at the same bounds table.
|
| /Linux-v4.19/Documentation/i2c/ |
| D | ten-bit-addresses | 4 address 0x10 (though a single device could respond to both of them).
16 hardware doesn't support them (SMBus doesn't require 10-bit address
28 needs them to be fixed.
|
| /Linux-v4.19/arch/arc/plat-eznps/ |
| D | Kconfig | 33 any of them seem like CPU from Linux point of view.
35 core and HW scheduler round robin between them.
57 of the core, so there will be a need to initialize them per cpu.
|
| /Linux-v4.19/drivers/media/usb/ttusb-dec/ |
| D | Kconfig | 18 download/extract them, and then copy them to /usr/lib/hotplug/firmware
|
| /Linux-v4.19/Documentation/ |
| D | isa.txt | 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-v4.19/Documentation/devicetree/bindings/mmc/ |
| D | brcm,sdhci-brcmstb.txt | 7 on Device Tree properties to enable them for SoC/Board combinations
8 that support them.
|
| /Linux-v4.19/tools/testing/selftests/tc-testing/plugin-lib/ |
| D | README-PLUGINS | 14 tdc.py will find them and use them.
|
| /Linux-v4.19/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 18 but not explicitly acknowledged them to firmware and
24 entries, read them out and acknowledge them.
|
| /Linux-v4.19/arch/ia64/hp/sim/boot/ |
| D | bootloader.lds | 21 can access them all, and initialized data all before uninitialized, so
43 of the section so we begin them at 0. */
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-firmware-efi-runtime-map | 12 can reassemble them and pass them into the kexec kernel.
|
| /Linux-v4.19/Documentation/input/ |
| 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-v4.19/drivers/memstick/core/ |
| D | Kconfig | 12 normal behaviour is to remove them at suspend and
13 redetecting them at resume. Breaking this assumption will
|
| /Linux-v4.19/drivers/staging/ |
| 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-v4.19/Documentation/parisc/ |
| D | registers | 94 r1,r2,r19-r26,r28,r29 & r31 can be used without saving them first. And of
95 course, you need to save them if you care about them, before calling
113 r23-r26: these are arg3-arg0, i.e. you can use them if you
|
| /Linux-v4.19/Documentation/acpi/ |
| D | scan_handlers.txt | 22 information from the device objects represented by them and populating them with
23 appropriate data, but some of them require additional handling after they have
50 to match a scan handler against each of them using the ids arrays of the
|
| /Linux-v4.19/Documentation/admin-guide/pm/ |
| D | strategies.rst | 11 One of them is based on using global low-power states of the whole system in
29 allowing them to process data and to be accessed by software. In turn, if they
35 draw (or maximum energy usage) of it. If all of them are inactive, the system
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | vga-softcursor.rst | 16 where 1, 2 and 3 are parameters described below. If you omit any of them,
36 (by simply XORing them with the value of this parameter). On standard
|
| /Linux-v4.19/Documentation/usb/ |
| D | wusb-cbaf | 45 (connection key). Device saves them for the next time it wants to
46 connect wireless. We save them for that next time also so we can
|
| /Linux-v4.19/fs/ufs/ |
| D | Kconfig | 9 these partitions; if you also want to write to them, say Y to the
21 When accessing NeXTstep files, you may need to convert them from the
|
12345678910>>...41
