| /linux/drivers/pinctrl/intel/ |
| H A D | Kconfig | 22 allows configuring of SoC pins and using them as GPIOs.
30 using them as GPIOs.
46 of Intel PCH pins and using them as GPIOs. Currently the following
56 of Intel Alder Lake PCH pins and using them as GPIOs.
63 configuring of SoC pins and using them as GPIOs.
70 of Intel Cannon Lake PCH pins and using them as GPIOs.
77 of Intel Cedar Fork PCH pins and using them as GPIOs.
84 of Intel Denverton SoC pins and using them as GPIOs.
91 of Intel Elkhart Lake SoC pins and using them as GPIOs.
98 of Intel Emmitsburg pins and using them as GPIOs.
[all …]
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | swap_numa.rst | 17 to be swapped on. Simply swapping them on by doing::
24 that the order of them being swapped on doesn't matter.
29 The way to swap them on is the same as above::
38 Then node 0 will use them in the order of::
44 node 1 will use them in the order of::
48 node 2 will use them in the order of::
55 node 3 will use them in the order of::
|
| /linux/Documentation/filesystems/bcachefs/ |
| H A D | CodingStyle.rst | 6 Good development is like gardening, and codebases are our gardens. Tend to them
32 are logically impossible. (Or, make them debug mode assertions if they're
47 means that you can run them in only a few places in the checked in version, but
49 quickly shotgun them everywhere to find the codepath that broke the invariant.
71 percpu data structures among them. Don't let things stay hidden.
76 Pretty printers are wonderful, because they compose and you can use them
88 the issue. It's worth putting effort into them.
118 Users notice all sorts of interesting things, and by just talking to them and
119 interacting with them you can benefit from their experience.
134 Expect to throw a lot of things away, or leave them half finished for later.
|
| /linux/mm/kasan/ |
| H A D | Makefile | 40 # If compiler instruments memintrinsics by prefixing them with __asan/__hwasan,
41 # we need to treat them normally (as builtins), otherwise the compiler won't
42 # recognize them as instrumentable. If it doesn't instrument them, we need to
43 # pass -fno-builtin, so the compiler doesn't inline them.
|
| /linux/Documentation/admin-guide/pm/ |
| H A 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 …]
|
| 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
|
| H A D | intel_idle.rst | 52 processor) corresponding to them depends on the processor model and it may also
79 enter one of them. The return package of that ``_CST`` is then assumed to be
96 default (so all of them will be taken into consideration by ``CPUIdle``
100 space still can enable them later (on a per-CPU basis) with the help of
145 platform firmware is extracted from them.
169 and ``idle=nomwait``. If any of them is present in the kernel command line, the
185 some reason to the ``CPUIdle`` core, but it does so by making them effectively
197 driver ignore the system's ACPI tables entirely or use them for all of the
249 to the ``C1`` idle state), but the majority of them give it a license to put
|
| /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/Documentation/process/ |
| H A 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/kernel/kcsan/ |
| H A D | permissive.h | 7 * them separate from core code to make it easier to audit.
62 * that marking them all is often unrealistic and left to maintainer in kcsan_ignore_data_race()
83 * ordinary booleans (one of them was 0 and the 0th bit was in kcsan_ignore_data_race()
85 * memory ordering requirements, so let's report them. in kcsan_ignore_data_race()
|
| /linux/Documentation/input/ |
| H A 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/Documentation/timers/ |
| H A 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
162 all of them over time. Adaptive-tick mode may prevent this
195 scheduler will decide where to run them, which might or might not be
196 where you want them to run.
229 dyntick-idle mode, an option that most of them take. However,
282 simply offloading RCU callbacks from all CPUs and pinning them
283 where you want them whenever you want them pinned.
|
| H A 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/drivers/md/bcache/ |
| H A 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.
347 * possibly issue discards to them, then we add the bucket to in bch_allocator_thread()
371 * we can invalidate. First, invalidate them in memory and add in bch_allocator_thread()
372 * them to the free_inc list: in bch_allocator_thread()
[all …]
|
| /linux/arch/mips/include/uapi/asm/ |
| H A 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/tools/power/pm-graph/ |
| H A 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/Documentation/filesystems/ |
| H A D | directory-locking.rst | 77 Trees grow as we do operations; memory pressure prunes them. Normally
81 from the same NFS4 server and doing lookups in one of them has reached
138 them in order of non-decreasing rank. Namely,
171 are done directly to that filesystem and none of them has actually
200 more than one cross-directory rename among them. Without loss of
211 all of them had been stable.
220 children must be involved and thus neither of them could be a descendent
285 either to make sure that link(2) doesn't work for them or to make changes
|
| H A D | hpfs.rst | 51 What to do with extended attributes. 'no' - ignore them and use always
53 attributes but do not create them. 'rw' - create extended attributes
148 list, I don't know how to delete them when file is deleted and how to not
149 overwrite them with extended attributes. Send me some info on these structures
151 structures, remount read-only and not destroy them (I hope).
180 reasons. If you extremely wish to update them, let me know, I'll write it (but
197 correctly and writes warning if it finds them. If you see this message, this is
215 marks them as short (and writes "minor fs error corrected"). This bug is not in
279 not 100% ok, I have no info on it and OS/2 doesn't want to create them)
|
| /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
|
| /linux/arch/m68k/include/asm/ |
| H A 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/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/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/include/uapi/linux/ |
| H A 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/arch/arm/include/asm/hardware/ |
| H A D | sa1111.h | 47 * Don't believe the specs! Take them, throw them outside. Leave them
48 * there for a week. Spit on them. Walk on them. Stamp on them.
49 * Pour gasoline over them and finally burn them. Now think about coding.
|
| /linux/arch/arm/common/ |
| H A 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.
|