| /openbmc/linux/drivers/base/power/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/admin-guide/cgroup-v1/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/dev-tools/kunit/ |
| H A 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
|
| /openbmc/linux/Documentation/power/ |
| H A 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
|
| /openbmc/linux/Documentation/driver-api/pm/ |
| H A 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
|
| /openbmc/qemu/docs/devel/ |
| H A D | kconfig.rst | 25 architecture of the hardware emulation subsystems. Boards only have
141 **subsystems**, of which **buses** are a special case
148 Subsystems always default to false (they have no ``default`` directive)
150 up to other symbols to ``select`` whatever subsystems they require.
153 subsystems or buses. For example, ``AUX`` (the DisplayPort auxiliary
263 starting point to turn on devices and subsystems.
|
| /openbmc/linux/drivers/remoteproc/ |
| H A 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
|
| /openbmc/linux/Documentation/sphinx/ |
| H A D | maintainers_include.py | 53 subsystems = False
72 if maintainers and not subsystems:
74 subsystems = True
100 elif subsystems:
|
| /openbmc/linux/include/linux/ |
| H A D | cgroup_subsys.h | 3 * List of cgroup subsystems.
69 * The following subsystems are not supported on the default hierarchy.
|
| H A 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.
|
| /openbmc/linux/drivers/base/regmap/ |
| H A D | Kconfig | 3 # this is an API intended to be used by other kernel subsystems. These
4 # subsystems should select the appropriate symbols.
|
| /openbmc/linux/drivers/clk/baikal-t1/ |
| H A D | Kconfig | 8 responsible for the chip subsystems clocking and resetting. It
48 AXI-bus and some subsystems reset. These are mainly the
|
| /openbmc/linux/drivers/soc/qcom/ |
| H A 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()
|
| /openbmc/linux/Documentation/ |
| H A D | subsystem-apis.rst | 7 These books get into the details of how specific kernel subsystems work
13 Core subsystems
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/omap/ |
| H A 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
|
| /openbmc/linux/drivers/pmdomain/st/ |
| H A D | ste-ux500-pm-domain.c | 25 * Drivers/subsystems handling devices in the PM domain needs to perform in pd_power_off()
37 * Drivers/subsystems handling devices in the PM domain needs to perform in pd_power_on()
|
| /openbmc/linux/Documentation/driver-api/ |
| H A 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
|
| /openbmc/docs/architecture/ |
| H A D | optionality.md | 16 These are subsystems that, while widely applicable, a user might choose to
21 functional impacts to other subsystems. Examples of these include the webui,
|
| /openbmc/linux/Documentation/devicetree/bindings/spi/ |
| H A D | sprd,spi-adi.yaml | 33 Since we have multi-subsystems will use unique ADI to access analog chip, when
38 Then we need one hardware spinlock to synchronize between the multiple subsystems.
|
| /openbmc/linux/kernel/cgroup/ |
| H A D | cgroup-v1.c | 674 * Grab the subsystems state racily. No need to add avenue to in proc_cgroupstats_show()
950 /* Explicitly have no subsystems */ in cgroup1_parse_param()
1043 /* 'all' => select all the subsystems */ in check_cgroupfs_options()
1048 * We either have to specify by name or by subsystems. (So all in check_cgroupfs_options()
1062 /* Can't specify "none" and some subsystems */ in check_cgroupfs_options()
1079 /* See what subsystems are wanted */ in cgroup1_reconfigure()
1148 /* First find the desired set of subsystems */ in cgroup1_root_to_use()
1154 * Destruction of cgroup root is asynchronous, so subsystems may in cgroup1_root_to_use()
1156 * dying subsystems. We just need to ensure that the ones in cgroup1_root_to_use()
1188 * If we asked for subsystems (or explicitly for no in cgroup1_root_to_use()
[all …]
|
| H A D | cgroup-internal.h | 55 u16 subsys_mask; /* Selected subsystems */
146 /* subsystems affected by migration */
177 * for_each_subsys - iterate all enabled cgroup subsystems
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | xfs-maintainer-entry-profile.rst | 43 some part of the XFS codebase and/or other subsystems in the kernel.
112 - Authors of patches touching other subsystems need to coordinate with
113 the maintainers of XFS and the relevant subsystems to decide how to
|
| /openbmc/qemu/include/hw/arm/ |
| H A D | armsse.h | 2 * ARM SSE (Subsystems for Embedded): IoTKit, SSE-200
13 * This is a model of the Arm "Subsystems for Embedded" family of
123 * These type names are for specific IoTKit subsystems; other than
|
| /openbmc/linux/Documentation/timers/ |
| H A 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.
|
| /openbmc/linux/drivers/gpio/ |
| H A D | TODO | 68 gpiolib-of.c: in some cases subsystems are doing custom flags and
151 it may make sense to bring these subsystems closer. One reason for
154 make sense to simply join the subsystems into one and make pin
|