| /linux/Documentation/sphinx/ |
| H A D | maintainers_include.py | 55 subsystems = False
74 if maintainers and not subsystems:
76 subsystems = True
102 elif subsystems:
|
| /linux/Documentation/ |
| H A D | subsystem-apis.rst | 7 These books get into the details of how specific kernel subsystems work
13 Core subsystems
65 Other subsystems
|
| /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/userspace-api/fwctl/ |
| H A D | fwctl.rst | 34 no longer fit neatly into the kernel's division of subsystems. Modern
36 subsystems while sharing the underlying hardware using the auxiliary device
56 In the past when devices were more single function, individual subsystems would
104 subsystems.
138 fwctl is not a replacement for device direct access subsystems like uacce or
145 important than proper kernel subsystems that eventually emerge. Mistakes in this
162 fwctl devices can be related to driver components in other subsystems through
194 that stretch across all subsystems in the kernel. fwupd is a great example of
209 subsystems are going to be sharing the same device and FW interface layer so the
211 subsystems. fwctl should fit into that same model.
[all …]
|
| /linux/drivers/soc/qcom/ |
| H A D | qcom_stats.c | 49 static const struct subsystem_data subsystems[] = { variable
298 for (i = 0; i < ARRAY_SIZE(subsystems); i++) in qcom_create_subsystem_stat_files()
299 debugfs_create_file(subsystems[i].name, 0400, root, (void *)&subsystems[i], in qcom_create_subsystem_stat_files()
|
| /linux/drivers/reset/spacemit/ |
| H A D | Kconfig | 23 for various peripherals and subsystems in the SoC.
34 for various peripherals and subsystems in the SoC.
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | style.rst | 23 To make tests easy to find, they are grouped into suites and subsystems. A test
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/Documentation/admin-guide/ |
| H A D | workload-tracing.rst | 4 Discovering Linux kernel subsystems used by a workload
102 subsystems used by these workloads. Let's start with an overview of these
110 benchmarks for executing different subsystems in the Linux kernel and
114 integrate transparently, and use performance-rich tooling subsystems.
120 you to exercise various physical subsystems of the computer, as well as
189 This way we can find the kernel subsystems used by a process when it is
240 benchmarks for executing different subsystems in the Linux kernel and
258 the kernel. It allows you to exercise various physical subsystems of the
600 … by OpenAPS <https://elisa.tech/blog/2022/02/02/discovery-linux-kernel-subsystems-used-by-openaps>…
601 …* `ELISA-White-Papers-Discovering Linux kernel subsystems used by a workload <https://github.com/e…
|
| H A D | index.rst | 86 Core-kernel subsystems
175 subsystems expectations will be found here.
|
| H A D | lockup-watchdogs.rst | 37 perf subsystems, respectively. A direct consequence of this is that,
39 subsystems are present.
|
| /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/remoteproc/ |
| H A D | Kconfig | 236 subsystems such as ADSP (Audio DSP), CDSP (Compute DSP), MPSS (Modem
269 about other subsystems being shut down.
271 Say y here if your system runs firmware on any other subsystems, e.g.
338 subsystems on various TI K3 family of SoCs through the remote
350 Say m here to support TI's M4 remote processor subsystems
363 Say m here to support TI's R5F remote processor subsystems
|
| /linux/drivers/nvme/target/ |
| H A D | discovery.c | 76 list_for_each_entry(s, &port->subsystems, entry) { in nvmet_subsys_disc_changed()
151 list_for_each_entry(p, &req->port->subsystems, entry) { in discovery_log_entries()
216 list_for_each_entry(p, &req->port->subsystems, entry) { in nvmet_execute_disc_get_log_page()
|
| /linux/drivers/dma/ |
| H A D | TODO | 11 4. Check other subsystems for dma drivers and merge/move to dmaengine
|
| /linux/Documentation/userspace-api/ebpf/ |
| H A D | index.rst | 9 kernel subsystems, including networking, tracing and Linux security modules
|
| /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
|
| /linux/Documentation/driver-api/80211/ |
| H A D | introduction.rst | 9 These books attempt to give a description of the various subsystems
|
| /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
|
| /linux/Documentation/devicetree/bindings/powerpc/ |
| H A D | ibm,vas.txt | 3 VAS is a hardware mechanism that allows kernel subsystems and user processes
|
| /linux/Documentation/core-api/kho/ |
| H A D | index.rst | 28 in-memory data that shall not be touched across kexec. After KHO, subsystems
34 KHO FDT and structures defined by the subsystems form an ABI between pre-kexec
|
| /linux/Documentation/devicetree/bindings/arm/ |
| H A D | vexpress-scc.txt | 10 (like silicon temperature sensors) and as interface to other subsystems
|
| /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/fs/sysfs/ |
| H A D | Kconfig | 14 and other kernel subsystems.
|
| /linux/Documentation/driver-api/iio/ |
| H A D | intro.rst | 11 :doc:`input <../input>` subsystems. Hwmon is directed at low sample rate
|