Searched full:them (Results 1 – 25 of 4418) sorted by relevance
12345678910>>...177
| /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 …]
|
| /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::
|
| /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
|
| D | intel_idle.rst | 52 processor) corresponding to them depends on the processor model and it may also
78 enter one of them. The return package of that ``_CST`` is then assumed to be
95 default (so all of them will be taken into consideration by ``CPUIdle``
99 space still can enable them later (on a per-CPU basis) with the help of
143 platform firmware is extracted from them.
167 and ``idle=nomwait``. If any of them is present in the kernel command line, the
183 some reason to the ``CPUIdle`` core, but it does so by making them effectively
194 driver ignore the system's ACPI tables entirely or use them for all of the
230 to the ``C1`` idle state), but the majority of them give it a license to put
|
| /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
|
| /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::
|
| /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.
|
| /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
|
| /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
|
| /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.
|
| /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
|
| /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.
|
| /linux-5.10/Documentation/i2c/ |
| 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-5.10/drivers/md/bcache/ |
| D | alloc.c | 17 * of buckets on disk, with a pointer to them in the journal header.
27 * free_inc list and optionally discard them.
37 * have nothing pointing into them - these we can reuse without waiting for
40 * them (because they were overwritten). That's the unused list - buckets on the
60 * invalidated, and then invalidate them and stick them on the free_inc list -
120 * invalidates them, rewrites prios/gens (marking them as invalidated on disk),
122 * them on the various freelists.
326 * possibly issue discards to them, then we add the bucket to in bch_allocator_thread()
350 * we can invalidate. First, invalidate them in memory and add in bch_allocator_thread()
351 * them to the free_inc list: in bch_allocator_thread()
[all …]
|
| /linux-5.10/arch/arm/common/ |
| D | sharpsl_param.c | 19 * address PARAM_BASE. As the kernel will overwrite them, we need to store
20 * them early in the boot process, then pass them to the appropriate drivers.
|
| /linux-5.10/arch/h8300/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.
|
| /linux-5.10/include/uapi/linux/ |
| D | uhid.h | 115 * All these commands and requests are obsolete. You should avoid using them in
116 * new code. We support them for backwards-compatibility, but you might not get
117 * access to new feature in case you use them.
177 * the kernel writes short events, user-space shall extend them with 0s.
|
| /linux-5.10/Documentation/driver-api/acpi/ |
| 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-5.10/fs/dlm/ |
| D | midcomms.c | 18 * split them up into packets and pass them to the interested
21 * It also takes messages from the locking layer, formats them
22 * into packets and sends them to the comms layer.
|
| /linux-5.10/tools/power/pm-graph/ |
| D | README | 207 delay in seconds between them. For instance, -multi 20 5: execute 20 tests with
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.
543 perform a quick check to see if you formatted them correctly and if the system
[all …]
|
| /linux-5.10/fs/notify/ |
| D | fsnotify.h | 42 /* run the list of all marks associated with inode and destroy them */
47 /* run the list of all marks associated with vfsmount and destroy them */
52 /* run the list of all marks associated with sb and destroy them */
|
| /linux-5.10/Documentation/timers/ |
| D | no_hz.rst | 110 task implies also omitting them for idle CPUs.
116 it allows them to improve their worst-case response times by the maximum
165 all of them over time. Adaptive-tick mode may prevent this
202 scheduler will decide where to run them, which might or might not be
203 where you want them to run.
236 dyntick-idle mode, an option that most of them take. However,
289 simply offloading RCU callbacks from all CPUs and pinning them
290 where you want them whenever you want them pinned.
|
| D | hrtimers.rst | 49 them becomes necessary. Thus the users of these timeouts can accept
52 Accurate timing for them is not a core purpose - in fact most of the
53 timeout values used are ad-hoc. For them it is at most a necessary
109 time-changing code had to fix them up one by one, and all of them had to
122 1:1 mapping between them on the algorithmic level, and thus no real
|
| /linux-5.10/arch/sparc/include/asm/ |
| D | mman.h | 76 * if ADI is enabled on them even if they in sparc_validate_prot()
77 * have identical data on them. This can be in sparc_validate_prot()
80 * tags on them. Disallow ADI on mergeable in sparc_validate_prot()
|
12345678910>>...177