| /openbmc/linux/drivers/pinctrl/intel/ |
| H A D | Kconfig | 22 allows configuring of SoC pins and using them as GPIOs.
30 using them as GPIOs.
45 of Intel Alder Lake PCH pins and using them as GPIOs.
52 configuring of SoC pins and using them as GPIOs.
59 of Intel Cannon Lake PCH pins and using them as GPIOs.
66 of Intel Cedar Fork PCH pins and using them as GPIOs.
73 of Intel Denverton SoC pins and using them as GPIOs.
80 of Intel Elkhart Lake SoC pins and using them as GPIOs.
87 of Intel Emmitsburg pins and using them as GPIOs.
94 of Intel Gemini Lake SoC pins and using them as GPIOs.
[all …]
|
| /openbmc/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::
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-awesomeversion_24.6.0.bb | 1 …ion package to rule them all, One version package to find them, One version package to bring them …
|
| /openbmc/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.
|
| /openbmc/linux/drivers/staging/media/ |
| H A 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
|
| /openbmc/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
|
| /openbmc/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::
|
| /openbmc/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()
|
| /openbmc/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
|
| /openbmc/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
|
| /openbmc/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.
|
| /openbmc/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
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 290.out | 7 # Fill all clusters with data and then discard them
19 # Fill all clusters with data and then discard them
38 # Fill all clusters with data and then discard them
51 # Fill all clusters with data and then discard them
|
| /openbmc/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
|
| /openbmc/openbmc-build-scripts/config/ |
| H A D | .gitlint | 99 # Ignore certain rules, you can reference them by their id or by their full name
108 # Ignore certain rules, you can reference them by their id or by their full name
121 # Ignore certain rules, you can reference them by their id or by their full name
126 # You need to explicitly enable them one-by-one by adding them to the "contrib" option
|
| /openbmc/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.
|
| /openbmc/openbmc/poky/meta/recipes-kernel/lttng/lttng-tools/ |
| H A D | disable-tests.patch | 4 a variety of distros. Exclude them for now to work out if this is the
5 only place we see them and give SWAT/triage a break from the stream
6 of them.
|
| /openbmc/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.
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 …]
|
| /openbmc/qemu/contrib/plugins/ |
| H A D | lockstep.c | 129 static void report_divergance(ExecState *us, ExecState *them) in report_divergance() argument
168 them->pc, them->insn_count, in report_divergance()
199 ExecState us, them; in vcpu_tb_exec() local
223 bytes = read(socket_fd, &them, sizeof(ExecState)); in vcpu_tb_exec()
235 if (us.pc != them.pc) { in vcpu_tb_exec()
236 report_divergance(&us, &them); in vcpu_tb_exec()
|
| /openbmc/linux/drivers/staging/ |
| H A 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
|
| /openbmc/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.
|
| /openbmc/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 …]
|
| /openbmc/u-boot/arch/arm/mach-tegra/tegra124/ |
| H A D | psci.c | 37 * However, this doesn't work in practice. We rather need to power them in psci_board_init()
38 * up first and park them in wfi. While they are waiting there, we can in psci_board_init()
39 * indeed program the Flow Controller to powergate them on wfi, which in psci_board_init()
|