Searched full:generally (Results 1 – 25 of 745) sorted by relevance
12345678910>>...30
| /Linux-v5.15/Documentation/driver-api/media/ |
| D | camera-sensor.rst | 15 divisors. The clock tree is generally configured by the driver based on a few
17 and the link frequency. The two parameters generally are obtained from system
64 Register list based drivers generally, instead of able to configure the device
115 level interface natively, generally use the concept of frame interval (or frame
|
| /Linux-v5.15/Documentation/power/ |
| D | suspend-and-interrupts.rst | 12 Device interrupt request lines (IRQs) are generally disabled during system
61 System wakeup interrupts generally need to be configured to wake up the system
72 After wakeup, it generally is better to disable that input to prevent the
128 interrupt source and an IRQF_NO_SUSPEND interrupt source does not generally
|
| D | freezing-of-tasks.rst | 36 kernel/freezer.c & include/linux/freezer.h). User space processes are generally
104 Generally speaking, there is a couple of reasons to use the freezing of tasks:
123 devices are deactivated, because we generally need them for swapping out.
206 tasks, since it generally exists anyway.
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | uncore-other.json | 661 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an…
673 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an…
685 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an…
697 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an…
709 …ade to the MMIO space of a card on IIO Part0 by a unit on the main die (generally a core) or by an…
721 …ade to the MMIO space of a card on IIO Part1 by a unit on the main die (generally a core) or by an…
733 …de to the MMIO space of a card on IIO Part2 by a unit on the main die (generally a core) or by an…
745 …de to the MMIO space of a card on IIO Part3 by a unit on the main die (generally a core) or by an…
949 …for up to a 64 byte transaction of data made by a unit on the main die (generally a core) or by an…
961 …for up to a 64 byte transaction of data made by a unit on the main die (generally a core) or by an…
[all …]
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | uncore-other.json | 640 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an…
652 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an…
664 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an…
676 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an…
688 …ade to the MMIO space of a card on IIO Part0 by a unit on the main die (generally a core) or by an…
700 …ade to the MMIO space of a card on IIO Part1 by a unit on the main die (generally a core) or by an…
712 …de to the MMIO space of a card on IIO Part2 by a unit on the main die (generally a core) or by an…
724 …de to the MMIO space of a card on IIO Part3 by a unit on the main die (generally a core) or by an…
928 …for up to a 64 byte transaction of data made by a unit on the main die (generally a core) or by an…
940 …for up to a 64 byte transaction of data made by a unit on the main die (generally a core) or by an…
[all …]
|
| /Linux-v5.15/Documentation/core-api/ |
| D | bus-virt-phys-mapping.rst | 48 not generally necessarily true on other PCI/ISA setups.
125 And you generally **never** want to use the physical address, because you can't
143 memory" on the PCI or ISA bus. That's generally not RAM (although in the case
213 It's generally not hard to fix drivers, and in many cases the code
|
| /Linux-v5.15/Documentation/vm/ |
| D | active_mm.rst | 76 should generally just do
81 we have a user context", and is generally done by the page fault handler
|
| /Linux-v5.15/Documentation/i2c/busses/ |
| D | i2c-ali15x3.rst | 61 - Gigabyte GA-5AX (Generally doesn't work because the BIOS doesn't
121 SMBus. Therefore the SMBus hangs can generally be avoided
|
| /Linux-v5.15/Documentation/admin-guide/pm/ |
| D | cpufreq.rst | 42 the utilization of the system generally changes over time, that has to be done
160 scheduler tick or generally whenever the CPU utilization may change (from the
215 and their behavior generally does not depend on what scaling driver is in use
388 generally is regarded as a part of the CPU scheduler, so it can access the
430 This governor generally is regarded as a replacement for the older `ondemand`_
460 It generally selects CPU frequencies proportional to the estimated load, so that
644 The frequency boost mechanism is generally intended to help to achieve optimum
655 conditions. Generally, the processor's energy consumption increases
|
| D | intel_pstate.rst | 81 names of some of those governors. Moreover, confusingly enough, they generally
182 registers of the CPU. It generally selects P-states proportional to the
266 In turn, the P-states below the turbo threshold generally are sustainable. In
273 but the maximum P-state that can be set for them generally depends on the number
291 generally causes turbo P-states to be set more often when ``intel_pstate`` is
320 Generally, ways to obtain that information are specific to the processor model
455 as the current scaling driver and it generally depends on the driver's
707 diagnostics. One of them is the ``cpu_frequency`` trace event generally used
713 their output (if the kernel is generally configured to support event tracing)::
|
| D | cpuidle.rst | 19 Modern processors are generally able to enter states in which the execution of
24 generally allows power drawn by the processor to be reduced and, in consequence,
40 physically. Generally, three different cases can be consider here.
153 (in particular, before the closest timer triggers) and it generally is not known
255 generally regarded as more energy-efficient than the systems running kernels in
487 hierarchy of units in the processor, and it generally is hard to obtain idle
492 The number in the :file:`time` file generally may be greater than the total time
506 Generally, an interrupt received when trying to enter an idle state causes the
|
| /Linux-v5.15/kernel/power/ |
| D | Kconfig | 172 Hardware support is generally required for this functionality to work
277 Generally, if you don't have a battery in your machine, there isn't
295 Per-cpu workqueues are generally preferred because they show
|
| /Linux-v5.15/drivers/thermal/ti-soc-thermal/ |
| D | TODO | 9 generally:
|
| /Linux-v5.15/Documentation/process/ |
| D | volatile-considered-harmful.rst | 71 waiting is generally an anti-social act to begin with.
104 Patches to remove volatile variables are generally welcome - as long as
|
| /Linux-v5.15/arch/x86/include/uapi/asm/ |
| D | posix_types_64.h | 6 * This file is generally used by user-level software, so you need to
|
| D | posix_types_x32.h | 10 * These types should generally match the ones used by the 64-bit kernel,
|
| D | posix_types_32.h | 6 * This file is generally used by user-level software, so you need to
|
| /Linux-v5.15/arch/powerpc/include/uapi/asm/ |
| D | posix_types.h | 6 * This file is generally used by user-level software, so you need to
|
| /Linux-v5.15/arch/alpha/include/uapi/asm/ |
| D | posix_types.h | 6 * This file is generally used by user-level software, so you need to
|
| /Linux-v5.15/arch/parisc/include/uapi/asm/ |
| D | posix_types.h | 6 * This file is generally used by user-level software, so you need to
|
| /Linux-v5.15/Documentation/driver-api/pm/ |
| D | devices.rst | 57 However, devices are not generally independent of each other (for
200 by the bus type (or generally subsystem) code using :c:func:`pm_runtime_allow()`
401 vectors, like PCI, generally need it; otherwise a driver might encounter
432 generally means undoing the actions of the ``suspend_noirq`` phase. If
445 of the resume methods. This generally involves undoing the actions of
449 state, so that it can perform normal I/O. This generally involves
654 been thawed. Generally speaking, the PM notifiers are suitable for performing
698 cases it generally is not possible to put devices into low-power states
820 the case generally depends on the state of the device before the given system
842 ``DPM_FLAG_MAY_SKIP_RESUME`` flag is necessary, but generally not sufficient,
|
| /Linux-v5.15/arch/m68k/include/uapi/asm/ |
| D | posix_types.h | 6 * This file is generally used by user-level software, so you need to
|
| /Linux-v5.15/Documentation/kbuild/ |
| D | llvm.rst | 95 even the development tree will generally yield the best results.
96 An architecture's ``defconfig`` is generally expected to work well,
|
| /Linux-v5.15/kernel/rcu/ |
| D | Makefile | 3 # and is generally not a function of system call inputs.
|
| /Linux-v5.15/arch/mips/include/uapi/asm/ |
| D | posix_types.h | 16 * This file is generally used by user-level software, so you need to
|
12345678910>>...30
