Searched full:them (Results 1 – 25 of 5212) sorted by relevance
12345678910>>...209
| /Linux-v5.4/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-v5.4/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-v5.4/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 and ``ladder``. Which of them is used by default depends on the configuration
181 decision on which one of them to use has to be made early (on Intel platforms
196 allow them to make reasonable progress in a given time frame is to make them
[all …]
|
| /Linux-v5.4/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-v5.4/Documentation/x86/ |
| D | intel_mpx.rst | 112 them somewhere. It has two special instructions for this which allow
124 the instructions for moving bounds in and out of them are extremely
131 are a few ways this could be done. We don't think any of them are practical
135 never have to allocate them?
139 even if we clean them up aggressively. In the worst-case scenario, the
143 If we were to preallocate them for the 128TB of user virtual address
167 bounds tables that we could think of, we create them on demand in
207 knowledge, it is also responsible for freeing them when the associated
241 directory at them through XSAVE instruction, and then set valid bit
246 them at the same bounds table.
|
| 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-v5.4/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-v5.4/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.
|
| /Linux-v5.4/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-v5.4/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-v5.4/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-v5.4/tools/power/pm-graph/ |
| D | README | 333 It is possible to add new function calls to the timeline by adding them to
335 the config so that you can override and edit them. Place them in the
340 custom calls, or leave it false to append them to the internal ones.
350 them.
407 It is possible to add new function calls to the dev timeline by adding them
409 functions into the config so that you can override and edit them. Place them
414 custom calls, or leave it false to append them to the internal ones.
425 them.
439 perform a quick check to see if you formatted them correctly and if the system
440 actually supports them. To do this, run the tool with your config file
[all …]
|
| /Linux-v5.4/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-v5.4/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-v5.4/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-v5.4/Documentation/filesystems/ |
| D | hpfs.txt | 43 What to do with extended attributes. 'no' - ignore them and use always
45 attributes but do not create them. 'rw' - create extended attributes
135 list, I don't know how to delete them when file is deleted and how to not
136 overwrite them with extended attributes. Send me some info on these structures
138 structures, remount read-only and not destroy them (I hope).
166 reasons. If you extremely wish to update them, let me know, I'll write it (but
182 correctly and writes warning if it finds them. If you see this message, this is
199 marks them as short (and writes "minor fs error corrected"). This bug is not in
245 not 100% ok, I have no info on it and OS/2 doesn't want to create them)
|
| /Linux-v5.4/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-v5.4/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 -
121 * invalidates them, rewrites prios/gens (marking them as invalidated on disk),
123 * them on the various freelists.
327 * possibly issue discards to them, then we add the bucket to in bch_allocator_thread()
351 * we can invalidate. First, invalidate them in memory and add in bch_allocator_thread()
352 * them to the free_inc list: in bch_allocator_thread()
[all …]
|
| /Linux-v5.4/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-v5.4/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-v5.4/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-v5.4/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-v5.4/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-v5.4/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-v5.4/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
204 scheduler will decide where to run them, which might or might not be
205 where you want them to run.
238 dyntick-idle mode, an option that most of them take. However,
291 simply offloading RCU callbacks from all CPUs and pinning them
292 where you want them whenever you want them pinned.
|
12345678910>>...209
