Home
last modified time | relevance | path

Searched full:subsystems (Results 1 – 25 of 527) sorted by relevance

12345678910>>...22

/kernel/linux/linux-4.19/drivers/base/power/
Dgeneric_ops.c2 * drivers/base/power/generic_ops.c - Generic PM callbacks for subsystems
15 * pm_generic_runtime_suspend - Generic runtime suspend callback for subsystems.
34 * pm_generic_runtime_resume - Generic runtime resume callback for subsystems.
72 * pm_generic_suspend_noirq - Generic suspend_noirq callback for subsystems.
84 * pm_generic_suspend_late - Generic suspend_late callback for subsystems.
96 * pm_generic_suspend - Generic suspend callback for subsystems.
108 * pm_generic_freeze_noirq - Generic freeze_noirq callback for subsystems.
120 * pm_generic_freeze_late - Generic freeze_late callback for subsystems.
132 * pm_generic_freeze - Generic freeze callback for subsystems.
144 * pm_generic_poweroff_noirq - Generic poweroff_noirq callback for subsystems.
[all …]
/kernel/linux/linux-5.10/drivers/base/power/
Dgeneric_ops.c3 * 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/
Dcgroups.rst51 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-4.19/Documentation/cgroup-v1/
Dcgroups.txt47 or more subsystems.
58 hierarchy, and a set of subsystems; each subsystem has system-specific
72 tracking. The intention is that other subsystems hook into the generic
92 specific subsystems such as cpusets to provide additional behaviour as
97 different subsystems - having parallel hierarchies allows each
100 unrelated subsystems needed to be forced into the same tree of
104 separate hierarchy; at the other extreme, all subsystems
137 (by putting those resource subsystems in different hierarchies),
203 comma-separated list of subsystems to mount as the filesystem mount
205 mount a hierarchy containing all registered subsystems.
[all …]
/kernel/linux/linux-5.10/Documentation/dev-tools/kunit/
Dstyle.rst20 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/
DKconfig188 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/
Dnotifiers.rst13 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-4.19/Documentation/driver-api/pm/
Dnotifiers.rst9 There are some operations that subsystems or drivers may want to carry out
11 to be fully functional, so the drivers' and subsystems' ``->suspend()`` and
22 Subsystems or drivers having such needs can register suspend notifiers that
/kernel/linux/linux-4.19/drivers/base/regmap/
DKconfig3 # 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/drivers/base/regmap/
DKconfig3 # 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/
Dmaintainers_include.py53 subsystems = False
74 if maintainers and not subsystems:
76 subsystems = True
102 elif subsystems:
/kernel/linux/linux-5.10/include/linux/
Dcgroup-defs.h41 /* define the enumeration of all cgroup subsystems */
78 CGRP_ROOT_NOPREFIX = (1 << 1), /* mounted subsystems have no named prefix */
410 * The bitmask of subsystems enabled on the child cgroups.
413 * one which may have more subsystems enabled. Controller knobs
497 /* The bitmask of subsystems attached to this hierarchy */
678 * is broken in some ways - some subsystems ignore hierarchy
683 * cases. Eventually, all subsystems will be made properly
716 * A subsystem may depend on other subsystems. When such subsystem
717 * is enabled on a cgroup, the depended-upon subsystems are enabled
718 * together if available. Subsystems enabled due to dependency are
[all …]
Dcgroup_subsys.h3 * List of cgroup subsystems.
65 * The following subsystems are not supported on the default hierarchy.
/kernel/linux/linux-4.19/include/linux/
Dcgroup-defs.h39 /* define the enumeration of all cgroup subsystems */
70 CGRP_ROOT_NOPREFIX = (1 << 1), /* mounted subsystems have no named prefix */
382 * The bitmask of subsystems enabled on the child cgroups.
385 * one which may have more subsystems enabled. Controller knobs
463 /* The bitmask of subsystems attached to this hierarchy */
640 * is broken in some ways - some subsystems ignore hierarchy
645 * cases. Eventually, all subsystems will be made properly
678 * A subsystem may depend on other subsystems. When such subsystem
679 * is enabled on a cgroup, the depended-upon subsystems are enabled
680 * together if available. Subsystems enabled due to dependency are
[all …]
Dcgroup_subsys.h3 * List of cgroup subsystems.
65 * The following subsystems are not supported on the default hierarchy.
/kernel/linux/linux-5.10/arch/arm/mach-ux500/
Dpm_domains.c23 * 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-4.19/arch/arm/mach-ux500/
Dpm_domains.c23 * 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-4.19/Documentation/devicetree/bindings/arm/omap/
Dcrossbar.txt2 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/
Dcrossbar.txt2 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-4.19/Documentation/devicetree/bindings/spi/
Dspi-sprd-adi.txt21 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-4.19/drivers/nvme/target/
Dconfigfs.c579 pr_err("can only link subsystems into the subsystems dir.!\n"); in nvmet_port_subsys_allow_link()
590 list_for_each_entry(p, &port->subsystems, entry) { in nvmet_port_subsys_allow_link()
595 if (list_empty(&port->subsystems)) { in nvmet_port_subsys_allow_link()
601 list_add_tail(&link->entry, &port->subsystems); in nvmet_port_subsys_allow_link()
620 list_for_each_entry(p, &port->subsystems, entry) { in nvmet_port_subsys_drop_link()
630 if (list_empty(&port->subsystems)) in nvmet_port_subsys_drop_link()
1146 INIT_LIST_HEAD(&port->subsystems); in nvmet_ports_make()
1154 "subsystems", &nvmet_port_subsys_type); in nvmet_ports_make()
1250 "subsystems", &nvmet_subsystems_type); in nvmet_init_configfs()
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/spi/
Dspi-sprd-adi.txt21 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/
Dioctl.rst55 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-4.19/drivers/clk/qcom/
DKconfig43 profile. It communicates with other hardware subsystems via shared
56 profile. It communicates with other hardware subsystems via shared
67 SoCs. It accepts requests from other hardware subsystems via RSC.
/kernel/linux/linux-4.19/kernel/cgroup/
Dcgroup-v1.c693 * ideally we don't want subsystems moving around while we do this. in proc_cgroupstats_show()
928 /* Explicitly have no subsystems */ in parse_cgroupfs_options()
1012 * If the 'all' option was specified select all the subsystems, in parse_cgroupfs_options()
1022 * We either have to specify by name or by subsystems. (So all in parse_cgroupfs_options()
1036 /* Can't specify "none" and some subsystems */ in parse_cgroupfs_options()
1052 /* See what subsystems are wanted */ in cgroup1_remount()
1123 /* First find the desired set of subsystems */ in cgroup1_mount()
1129 * Destruction of cgroup root is asynchronous, so subsystems may in cgroup1_mount()
1131 * dying subsystems. We just need to ensure that the ones in cgroup1_mount()
1167 * If we asked for subsystems (or explicitly for no in cgroup1_mount()
[all …]

12345678910>>...22