| /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 …]
|
| /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 …]
|
| /linux/Documentation/ |
| H A D | subsystem-apis.rst | 7 These books get into the details of how specific kernel subsystems work
13 Core subsystems
64 Other subsystems
|
| /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
|
| H A 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/Documentation/sphinx/ |
| H A D | maintainers_include.py | 53 subsystems = False
72 if maintainers and not subsystems:
74 subsystems = True
100 elif subsystems:
|
| /linux/include/linux/ |
| H A D | execmem.h | 19 * There are several subsystems that allocate executable memory.
22 * by these subsystems.
23 * Types in this enum identify subsystems that allocate executable memory
|
| H A D | cgroup_subsys.h | 3 * List of cgroup subsystems.
69 * The following subsystems are not supported on the default hierarchy.
|
| /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
135 subsystems which use EM might rely on this flag to check if all EM devices use
136 the same scale. If there are different scales, these subsystems might decide
193 Subsystems interested in the energy model of a CPU can retrieve it using the
|
| /linux/Documentation/userspace-api/ |
| H A D | dma-buf-alloc-exchange.rst | 10 subsystems. Modern systems require extensive integration between all three
11 classes; this document details how applications and kernel subsystems should
16 support, however any other subsystems should also follow this design and advice.
277 are not portable between contexts, processes, devices, or subsystems.
283 contexts, processes, devices, and subsystems.
304 The concept of modifiers post-dates all of the subsystems mentioned above. As
381 Any new users - userspace programs and protocols, kernel subsystems, etc -
|
| /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.
|
| /linux/drivers/soc/qcom/ |
| H A D | qcom_stats.c | 33 static const struct subsystem_data subsystems[] = { variable
182 for (i = 0; i < ARRAY_SIZE(subsystems); i++) in qcom_create_subsystem_stat_files()
183 debugfs_create_file(subsystems[i].name, 0400, root, (void *)&subsystems[i], in qcom_create_subsystem_stat_files()
|
| /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
|
| /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
|
| /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()
|
| /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
|
| /linux/Documentation/devicetree/bindings/sound/ |
| H A D | qcom,wcd939x.yaml | 18 subsystems are external to the IC, thus requiring DT port-endpoint graph description
44 A port node to link the WCD939x Codec node to USB MUX subsystems for the
|
| /linux/kernel/cgroup/ |
| H A D | cgroup-v1.c | 680 * Grab the subsystems state racily. No need to add avenue to in proc_cgroupstats_show()
960 /* Explicitly have no subsystems */ in cgroup1_parse_param()
1054 /* 'all' => select all the subsystems */ in check_cgroupfs_options()
1059 * We either have to specify by name or by subsystems. (So all in check_cgroupfs_options()
1073 /* Can't specify "none" and some subsystems */ in cgroup1_reconfigure()
1090 /* See what subsystems are wanted */ in cgroup1_reconfigure()
1159 /* First find the desired set of subsystems */ in cgroup1_root_to_use()
1165 * Destruction of cgroup root is asynchronous, so subsystems may in cgroup1_root_to_use()
1167 * dying subsystems. We just need to ensure that the ones in cgroup1_root_to_use()
1199 * If we asked for subsystems (o in cgroup1_root_to_use()
[all...] |
| H A D | cgroup-internal.h | 55 u16 subsys_mask; /* Selected subsystems */
148 /* subsystems affected by migration */
178 * for_each_subsys - iterate all enabled cgroup subsystems
|
| /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.
|
| /linux/Documentation/filesystems/xfs/ |
| 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
|
| /linux/Documentation/userspace-api/netlink/ |
| H A 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
556 Netlink refers to subsystems as families. This is a remnant of using
|
| /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.
|
| /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
|
| /linux/Documentation/admin-guide/ |
| H A D | lockup-watchdogs.rst | 37 perf subsystems, respectively. A direct consequence of this is that,
39 subsystems are present.
|