| /kernel/linux/linux-5.10/drivers/base/power/ |
| D | generic_ops.c | 3 * drivers/base/power/generic_ops.c - Generic PM callbacks for subsystems
13 * pm_generic_runtime_suspend - Generic runtime suspend callback for subsystems.
32 * pm_generic_runtime_resume - Generic runtime resume callback for subsystems.
70 * pm_generic_suspend_noirq - Generic suspend_noirq callback for subsystems.
82 * pm_generic_suspend_late - Generic suspend_late callback for subsystems.
94 * pm_generic_suspend - Generic suspend callback for subsystems.
106 * pm_generic_freeze_noirq - Generic freeze_noirq callback for subsystems.
118 * pm_generic_freeze_late - Generic freeze_late callback for subsystems.
130 * pm_generic_freeze - Generic freeze callback for subsystems.
142 * pm_generic_poweroff_noirq - Generic poweroff_noirq callback for subsystems.
[all …]
|
| /kernel/linux/linux-6.6/drivers/base/power/ |
| D | generic_ops.c | 3 * drivers/base/power/generic_ops.c - Generic PM callbacks for subsystems
13 * pm_generic_runtime_suspend - Generic runtime suspend callback for subsystems.
32 * pm_generic_runtime_resume - Generic runtime resume callback for subsystems.
70 * pm_generic_suspend_noirq - Generic suspend_noirq callback for subsystems.
82 * pm_generic_suspend_late - Generic suspend_late callback for subsystems.
94 * pm_generic_suspend - Generic suspend callback for subsystems.
106 * pm_generic_freeze_noirq - Generic freeze_noirq callback for subsystems.
118 * pm_generic_freeze_late - Generic freeze_late callback for subsystems.
130 * pm_generic_freeze - Generic freeze callback for subsystems.
142 * pm_generic_poweroff_noirq - Generic poweroff_noirq callback for subsystems.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/cgroup-v1/ |
| D | cgroups.rst | 51 or more subsystems.
62 hierarchy, and a set of subsystems; each subsystem has system-specific
76 tracking. The intention is that other subsystems hook into the generic
96 specific subsystems such as cpusets to provide additional behaviour as
101 different subsystems - having parallel hierarchies allows each
104 unrelated subsystems needed to be forced into the same tree of
108 separate hierarchy; at the other extreme, all subsystems
141 (by putting those resource subsystems in different hierarchies),
207 comma-separated list of subsystems to mount as the filesystem mount
209 mount a hierarchy containing all registered subsystems.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/cgroup-v1/ |
| D | cgroups.rst | 51 or more subsystems.
62 hierarchy, and a set of subsystems; each subsystem has system-specific
76 tracking. The intention is that other subsystems hook into the generic
98 specific subsystems such as cpusets to provide additional behaviour as
103 different subsystems - having parallel hierarchies allows each
106 unrelated subsystems needed to be forced into the same tree of
110 separate hierarchy; at the other extreme, all subsystems
143 (by putting those resource subsystems in different hierarchies),
209 comma-separated list of subsystems to mount as the filesystem mount
211 mount a hierarchy containing all registered subsystems.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/kunit/ |
| D | style.rst | 20 Subsystems, Suites, and Tests
24 and subsystems. A test suite is a group of tests which test a related area of
28 Subsystems section in Subsystems, Suites, and Tests
39 Test subsystems should be named after the code being tested, either after the
41 subsystems should be named to avoid ambiguity where necessary.
47 Example subsystems could be:
73 The KUnit API and tools do not explicitly know about subsystems. They're
84 Not all subsystems will need to be split into multiple test suites (e.g. simple drivers).
|
| /kernel/linux/linux-6.6/Documentation/dev-tools/kunit/ |
| D | style.rst | 20 Subsystems, Suites, and Tests
23 To make tests easy to find, they are grouped into suites and subsystems. A test
28 Subsystems section in Subsystems, Suites, and Tests
38 Test subsystems should be named after the code being tested, either after the
40 subsystems should be named to avoid ambiguity where necessary.
45 example, subsystems could be called:
71 The KUnit API and tools do not explicitly know about subsystems. They are
81 shutdown code which is run for all tests in the suite. Not all subsystems need
|
| /kernel/linux/linux-6.6/Documentation/power/ |
| D | energy-model.rst | 12 subsystems willing to use that information to make energy-aware decisions.
24 Multiple subsystems might use the EM and it is up to the system integrator to
27 Documentation/scheduler/sched-energy.rst. For some subsystems like thermal or
29 These subsystems are more interested in estimation of power used in the past,
33 Kernel subsystems might implement automatic detection to check whether EM
110 subsystems which use EM might rely on this flag to check if all EM devices use
111 the same scale. If there are different scales, these subsystems might decide
168 Subsystems interested in the energy model of a CPU can retrieve it using the
|
| /kernel/linux/linux-5.10/drivers/remoteproc/ |
| D | Kconfig | 188 used to control subsystems such as ADSP, Compute and Sensor.
217 about other subsystems being shut down.
219 Say y here if your system runs firmware on any other subsystems, e.g.
272 subsystems on various TI K3 family of SoCs through the remote
284 Say m here to support TI's R5F remote processor subsystems
|
| /kernel/linux/linux-5.10/Documentation/driver-api/pm/ |
| D | notifiers.rst | 13 There are some operations that subsystems or drivers may want to carry out
15 to be fully functional, so the drivers' and subsystems' ``->suspend()`` and
26 Subsystems or drivers having such needs can register suspend notifiers that
|
| /kernel/linux/linux-6.6/Documentation/driver-api/pm/ |
| D | notifiers.rst | 13 There are some operations that subsystems or drivers may want to carry out
15 to be fully functional, so the drivers' and subsystems' ``->suspend()`` and
26 Subsystems or drivers having such needs can register suspend notifiers that
|
| /kernel/linux/linux-5.10/drivers/base/regmap/ |
| D | Kconfig | 3 # this is an API intended to be used by other kernel subsystems. These
4 # subsystems should select the appropriate symbols.
|
| /kernel/linux/linux-6.6/drivers/remoteproc/ |
| D | Kconfig | 233 used to control subsystems such as ADSP (Audio DSP),
267 about other subsystems being shut down.
269 Say y here if your system runs firmware on any other subsystems, e.g.
336 subsystems on various TI K3 family of SoCs through the remote
348 Say m here to support TI's R5F remote processor subsystems
|
| /kernel/linux/linux-6.6/Documentation/sphinx/ |
| D | maintainers_include.py | 53 subsystems = False
72 if maintainers and not subsystems:
74 subsystems = True
100 elif subsystems:
|
| /kernel/linux/linux-5.10/Documentation/sphinx/ |
| D | maintainers_include.py | 53 subsystems = False
74 if maintainers and not subsystems:
76 subsystems = True
102 elif subsystems:
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | cgroup-defs.h | 41 /* define the enumeration of all cgroup subsystems */
78 CGRP_ROOT_NOPREFIX = (1 << 1), /* mounted subsystems have no named prefix */
411 * The bitmask of subsystems enabled on the child cgroups.
414 * one which may have more subsystems enabled. Controller knobs
498 /* The bitmask of subsystems attached to this hierarchy */
679 * is broken in some ways - some subsystems ignore hierarchy
684 * cases. Eventually, all subsystems will be made properly
717 * A subsystem may depend on other subsystems. When such subsystem
718 * is enabled on a cgroup, the depended-upon subsystems are enabled
719 * together if available. Subsystems enabled due to dependency are
[all …]
|
| D | cgroup_subsys.h | 3 * List of cgroup subsystems.
65 * The following subsystems are not supported on the default hierarchy.
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | cgroup_subsys.h | 3 * List of cgroup subsystems.
69 * The following subsystems are not supported on the default hierarchy.
|
| D | cgroup-defs.h | 41 /* define the enumeration of all cgroup subsystems */
78 CGRP_ROOT_NOPREFIX = (1 << 1), /* mounted subsystems have no named prefix */
449 * The bitmask of subsystems enabled on the child cgroups.
452 * one which may have more subsystems enabled. Controller knobs
540 /* The bitmask of subsystems attached to this hierarchy */
748 * A subsystem may depend on other subsystems. When such subsystem
749 * is enabled on a cgroup, the depended-upon subsystems are enabled
750 * together if available. Subsystems enabled due to dependency are
752 * specifies the mask of subsystems that this one depends on.
|
| /kernel/linux/linux-6.6/drivers/base/regmap/ |
| D | Kconfig | 3 # this is an API intended to be used by other kernel subsystems. These
4 # subsystems should select the appropriate symbols.
|
| /kernel/linux/linux-6.6/drivers/clk/baikal-t1/ |
| D | Kconfig | 8 responsible for the chip subsystems clocking and resetting. It
48 AXI-bus and some subsystems reset. These are mainly the
|
| /kernel/linux/linux-6.6/drivers/soc/qcom/ |
| D | qcom_stats.c | 33 static const struct subsystem_data subsystems[] = { variable
178 for (i = 0; i < ARRAY_SIZE(subsystems); i++) in qcom_create_subsystem_stat_files()
179 debugfs_create_file(subsystems[i].name, 0400, root, (void *)&subsystems[i], in qcom_create_subsystem_stat_files()
|
| /kernel/linux/linux-6.6/Documentation/ |
| D | subsystem-apis.rst | 7 These books get into the details of how specific kernel subsystems work
13 Core subsystems
|
| /kernel/linux/linux-5.10/arch/arm/mach-ux500/ |
| D | pm_domains.c | 23 * Drivers/subsystems handling devices in the PM domain needs to perform in pd_power_off()
35 * Drivers/subsystems handling devices in the PM domain needs to perform in pd_power_on()
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/omap/ |
| D | crossbar.txt | 2 the needs of its many peripherals and subsystems. All of the
3 interrupt lines from the subsystems are not needed at the same
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/omap/ |
| D | crossbar.txt | 2 the needs of its many peripherals and subsystems. All of the
3 interrupt lines from the subsystems are not needed at the same
|