| /Linux-v6.1/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 …]
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/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
|
| /Linux-v6.1/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
|
| /Linux-v6.1/drivers/soc/qcom/ |
| D | qcom_stats.c | 33 static const struct subsystem_data subsystems[] = { variable
179 for (i = 0; i < ARRAY_SIZE(subsystems); i++) { in qcom_create_subsystem_stat_files()
180 stat = qcom_smem_get(subsystems[i].pid, subsystems[i].smem_item, NULL); in qcom_create_subsystem_stat_files()
184 debugfs_create_file(subsystems[i].name, 0400, root, (void *)&subsystems[i], in qcom_create_subsystem_stat_files()
|
| /Linux-v6.1/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
|
| D | devices.rst | 43 cleanly power down hardware and software subsystems, then reactivate
91 There are programming interfaces provided for subsystems (bus type, device type,
109 operations available at least for some subsystems. This approach does not use
125 device drivers whose subsystems (PM domains, device types, device classes and
177 file contains the "enabled" string. This information is used by subsystems,
375 ``->suspend`` methods provided by subsystems (bus types and PM domains
383 subsystems or drivers from putting devices into runtime suspend at
399 The majority of subsystems and device drivers need not implement this
601 subsystems.
652 To handle these cases, subsystems and device drivers may register power
[all …]
|
| /Linux-v6.1/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
|
| /Linux-v6.1/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.
|
| /Linux-v6.1/Documentation/sphinx/ |
| D | maintainers_include.py | 53 subsystems = False
72 if maintainers and not subsystems:
74 subsystems = True
100 elif subsystems:
|
| /Linux-v6.1/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 */
81 CGRP_ROOT_NOPREFIX = (1 << 1), /* mounted subsystems have no named prefix */
435 * The bitmask of subsystems enabled on the child cgroups.
438 * one which may have more subsystems enabled. Controller knobs
522 /* The bitmask of subsystems attached to this hierarchy */
727 * A subsystem may depend on other subsystems. When such subsystem
728 * is enabled on a cgroup, the depended-upon subsystems are enabled
729 * together if available. Subsystems enabled due to dependency are
731 * specifies the mask of subsystems that this one depends on.
|
| /Linux-v6.1/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
|
| /Linux-v6.1/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()
|
| /Linux-v6.1/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
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | ioctl.rst | 55 Some subsystems use version numbers in data structures to overload
75 -ENOTTY being returned from the system call. Some subsystems return
80 commands. As all subsystems are now responsible for handling compat
213 subsystems implement the same command for multiple drivers. Ideally the
|
| /Linux-v6.1/kernel/cgroup/ |
| D | cgroup-v1.c | 675 * Grab the subsystems state racily. No need to add avenue to in proc_cgroupstats_show()
951 /* Explicitly have no subsystems */ in cgroup1_parse_param()
1044 /* 'all' => select all the subsystems */ in check_cgroupfs_options()
1049 * We either have to specify by name or by subsystems. (So all in check_cgroupfs_options()
1063 /* Can't specify "none" and some subsystems */ in check_cgroupfs_options()
1080 /* See what subsystems are wanted */ in cgroup1_reconfigure()
1149 /* First find the desired set of subsystems */ in cgroup1_root_to_use()
1155 * Destruction of cgroup root is asynchronous, so subsystems may in cgroup1_root_to_use()
1157 * dying subsystems. We just need to ensure that the ones in cgroup1_root_to_use()
1189 * If we asked for subsystems (or explicitly for no in cgroup1_root_to_use()
[all …]
|
| D | cgroup-internal.h | 55 u16 subsys_mask; /* Selected subsystems */
146 /* subsystems affected by migration */
176 * for_each_subsys - iterate all enabled cgroup subsystems
|
| /Linux-v6.1/Documentation/devicetree/bindings/spi/ |
| D | sprd,spi-adi.yaml | 34 Since we have multi-subsystems will use unique ADI to access analog chip, when
39 Then we need one hardware spinlock to synchronize between the multiple subsystems.
|
| /Linux-v6.1/drivers/gpio/ |
| D | TODO | 73 gpiolib-of.c: in some cases subsystems are doing custom flags and
139 it may make sense to bring these subsystems closer. One reason for
142 make sense to simply join the subsystems into one and make pin
|
| /Linux-v6.1/Documentation/userspace-api/netlink/ |
| D | intro.rst | 79 of IDs to subsystems and provided little supporting infrastructure.
86 subsystems (and subsystem ID allocation), introspection and simplifies
90 number of subsystems using Generic Netlink outnumbers the older
94 the Linux kernel (or another of the 20 subsystems using Classic
129 multiple subsystems in a single protocol so it uses this field to
167 versioning of the APIs provided by the subsystems. No subsystem to
550 Netlink refers to subsystems as families. This is a remnant of using
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | lockup-watchdogs.rst | 37 perf subsystems, respectively. A direct consequence of this is that,
39 subsystems are present.
|
| /Linux-v6.1/Documentation/timers/ |
| D | hrtimers.rst | 8 (kernel/timers.c), why do we need two timer subsystems? After a lot of
60 users like drivers and subsystems which require precise timed events
69 separate the "timeout" and "precise timer" subsystems.
|
| /Linux-v6.1/drivers/nvme/target/ |
| D | configfs.c | 839 pr_err("can only link subsystems into the subsystems dir.!\n"); in nvmet_port_subsys_allow_link()
850 list_for_each_entry(p, &port->subsystems, entry) { in nvmet_port_subsys_allow_link()
855 if (list_empty(&port->subsystems)) { in nvmet_port_subsys_allow_link()
861 list_add_tail(&link->entry, &port->subsystems); in nvmet_port_subsys_allow_link()
881 list_for_each_entry(p, &port->subsystems, entry) { in nvmet_port_subsys_drop_link()
893 if (list_empty(&port->subsystems)) in nvmet_port_subsys_drop_link()
1056 /* passthru subsystems use the underlying controller's version */ in nvmet_subsys_attr_version_store_locked()
1672 INIT_LIST_HEAD(&port->subsystems); in nvmet_ports_make()
1682 "subsystems", &nvmet_port_subsys_type); in nvmet_ports_make()
1910 "subsystems", &nvmet_subsystems_type); in nvmet_init_configfs()
|
| /Linux-v6.1/drivers/s390/char/ |
| D | Kconfig | 137 tape subsystems and 100% compatibles.
146 tape subsystems and 100% compatibles.
|
