| /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-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-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-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
|
| 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 …]
|
| /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-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-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-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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/spi/ |
| D | spi-sprd-adi.txt | 21 Since we have multi-subsystems will use unique ADI to access analog chip, when
26 Then we need one hardware spinlock to synchronize between the multiple subsystems.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/kernel/cgroup/ |
| D | cgroup-v1.c | 682 * ideally we don't want subsystems moving around while we do this. in proc_cgroupstats_show()
959 /* Explicitly have no subsystems */ in cgroup1_parse_param()
1046 /* 'all' => select all the subsystems */ in check_cgroupfs_options()
1051 * We either have to specify by name or by subsystems. (So all in check_cgroupfs_options()
1065 /* Can't specify "none" and some subsystems */ in check_cgroupfs_options()
1082 /* See what subsystems are wanted */ in cgroup1_reconfigure()
1151 /* First find the desired set of subsystems */ in cgroup1_root_to_use()
1157 * Destruction of cgroup root is asynchronous, so subsystems may in cgroup1_root_to_use()
1159 * dying subsystems. We just need to ensure that the ones in cgroup1_root_to_use()
1191 * If we asked for subsystems (or explicitly for no in cgroup1_root_to_use()
[all …]
|
| D | cgroup-internal.h | 56 u16 subsys_mask; /* Selected subsystems */
147 /* subsystems affected by migration */
178 * for_each_subsys - iterate all enabled cgroup subsystems
|
| /kernel/linux/linux-5.10/drivers/gpio/ |
| D | TODO | 73 gpiolib-of.c: in some cases subsystems are doing custom flags and
188 it may make sense to bring these subsystems closer. One reason for
191 make sense to simply join the subsystems into one and make pin
|
| /kernel/linux/linux-5.10/drivers/nvme/target/ |
| D | configfs.c | 775 pr_err("can only link subsystems into the subsystems dir.!\n"); in nvmet_port_subsys_allow_link()
786 list_for_each_entry(p, &port->subsystems, entry) { in nvmet_port_subsys_allow_link()
791 if (list_empty(&port->subsystems)) { in nvmet_port_subsys_allow_link()
797 list_add_tail(&link->entry, &port->subsystems); in nvmet_port_subsys_allow_link()
817 list_for_each_entry(p, &port->subsystems, entry) { in nvmet_port_subsys_drop_link()
829 if (list_empty(&port->subsystems)) in nvmet_port_subsys_drop_link()
979 /* passthru subsystems use the underlying controller's version */ in nvmet_subsys_attr_version_store()
1527 INIT_LIST_HEAD(&port->subsystems); in nvmet_ports_make()
1537 "subsystems", &nvmet_port_subsys_type); in nvmet_ports_make()
1633 "subsystems", &nvmet_subsystems_type); in nvmet_init_configfs()
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | lockup-watchdogs.rst | 37 perf subsystems, respectively. A direct consequence of this is that,
39 subsystems are present.
|
| /kernel/linux/linux-5.10/drivers/s390/char/ |
| D | Kconfig | 126 tape subsystems and 100% compatibles.
135 tape subsystems and 100% compatibles.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/qcom/ |
| D | rpmh-rsc.txt | 28 or idle. When all subsystems like Modem, GPU, CPU are idle, the resource state
29 will be an aggregate of the sleep votes from each of those subsystems. Clients
|
| /kernel/linux/linux-5.10/sound/usb/line6/ |
| D | pcm.h | 50 subsystems. It is therefore necessary to maintain the state of the
51 subsystems with respect to PCM usage.
|
| /kernel/linux/linux-5.10/drivers/dma/ |
| D | TODO | 11 4. Check other subsystems for dma drivers and merge/move to dmaengine
|
| /kernel/linux/linux-5.10/drivers/staging/unisys/ |
| D | TODO | 11 - move individual drivers into proper driver subsystems
|