Searched full:them (Results 1 – 25 of 6853) sorted by relevance
12345678910>>...275
| /kernel/linux/linux-5.10/drivers/pinctrl/intel/ |
| D | Kconfig | 24 allows configuring of SoC pins and using them as GPIOs.
37 using them as GPIOs.
47 interface that allows configuring of SoC pins and using them as
64 configuring of SoC pins and using them as GPIOs.
72 of Intel Cannon Lake PCH pins and using them as GPIOs.
80 of Intel Cedar Fork PCH pins and using them as GPIOs.
88 of Intel Denverton SoC pins and using them as GPIOs.
96 of Intel Emmitsburg pins and using them as GPIOs.
104 of Intel Gemini Lake SoC pins and using them as GPIOs.
112 of Intel Ice Lake PCH pins and using them as GPIOs.
[all …]
|
| /kernel/linux/linux-4.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.
|
| /kernel/linux/linux-4.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::
|
| /kernel/linux/linux-5.10/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::
|
| /kernel/linux/linux-4.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
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/pm/ |
| 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
63 instructions from multiple locations in memory and execute them in the same time
70 by one of them, the hardware thread (or CPU) that asked for it is stopped, but
81 *idle* by the Linux kernel when there are no tasks to run on them except for the
99 to allow them to make some progress over time.]
163 ``ladder`` and ``haltpoll``. Which of them is used by default depends on the
179 decision on which one of them to use has to be made early (on Intel platforms
194 allow them to make reasonable progress in a given time frame is to make them
[all …]
|
| 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
|
| /kernel/linux/linux-5.10/drivers/staging/media/ |
| 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
|
| /kernel/linux/linux-4.19/arch/sh/mm/ |
| D | Makefile | 58 # use of them, so it's probably beneficial to performance to save them
59 # and have them available for it.
62 # use any of them and will spill them to the stack itself.
|
| /kernel/linux/linux-4.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::
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| 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::
|
| /kernel/linux/linux-4.19/Documentation/x86/ |
| 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.
|
| 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.
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| 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.
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | management-style.rst | 47 competent to make that decision for them.
114 sure as hell shouldn't encourage them by promising them that what they
115 work on will be included. Make them at least think twice before they
150 is fairly easy, and un-alienating them is hard. Thus "alienating"
193 Some people react badly to smart people. Others take advantage of them.
196 Suck up to them, because they are the people who will make your job
212 are doing something irreversible when you **do** prod them in some
229 Then make the developer who really screwed up (if you can find them) know
287 by trying to keep up with everybody else and running after them as fast
|
| /kernel/linux/linux-4.19/Documentation/process/ |
| D | management-style.rst | 46 competent to make that decision for them.
113 sure as hell shouldn't encourage them by promising them that what they
114 work on will be included. Make them at least think twice before they
149 is fairly easy, and un-alienating them is hard. Thus "alienating"
192 Some people react badly to smart people. Others take advantage of them.
195 Suck up to them, because they are the people who will make your job
211 are doing something irreversible when you **do** prod them in some
228 Then make the developer who really screwed up (if you can find them) know
286 by trying to keep up with everybody else and running after them as fast
|
| /kernel/linux/linux-5.10/arch/mips/include/uapi/asm/ |
| D | break.h | 15 * other MIPS operating systems. Linux/MIPS doesn't use all of them. The
16 * unused ones are here as placeholders; we might encounter them in
17 * non-Linux/MIPS object files or make use of them in the future.
|
| /kernel/linux/linux-4.19/arch/mips/include/uapi/asm/ |
| D | break.h | 15 * other MIPS operating systems. Linux/MIPS doesn't use all of them. The
16 * unused ones are here as placeholders; we might encounter them in
17 * non-Linux/MIPS object files or make use of them in the future.
|
| /kernel/linux/linux-4.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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/arch/arc/plat-eznps/ |
| D | Kconfig | 34 any of them seem like CPU from Linux point of view.
36 core and HW scheduler round robin between them.
58 of the core, so there will be a need to initialize them per cpu.
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| 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
|
| /kernel/linux/linux-4.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
|
| /kernel/linux/linux-4.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.
|
| /kernel/linux/linux-5.10/arch/m68k/include/asm/ |
| D | switch_to.h | 18 * syscall stores these registers itself and none of them are used
23 * to push them onto the stack and read them back right after.
|
12345678910>>...275