Searched refs:subsystems (Results 1 – 25 of 161) sorted by relevance
1234567
| /linux-6.1.9/drivers/soc/qcom/ |
| D | qcom_stats.c | 33 static const struct subsystem_data subsystems[] = { variable
179 for (i = 0; i < ARRAY_SIZE(subsystems); i++) { in qcom_create_subsystem_stat_files()
180 stat = qcom_smem_get(subsystems[i].pid, subsystems[i].smem_item, NULL); in qcom_create_subsystem_stat_files()
184 debugfs_create_file(subsystems[i].name, 0400, root, (void *)&subsystems[i], in qcom_create_subsystem_stat_files()
|
| /linux-6.1.9/Documentation/sphinx/ |
| D | maintainers_include.py | 53 subsystems = False
72 if maintainers and not subsystems:
74 subsystems = True
100 elif subsystems:
|
| /linux-6.1.9/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 …]
|
| /linux-6.1.9/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.
|
| /linux-6.1.9/Documentation/power/ |
| 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
|
| /linux-6.1.9/Documentation/dev-tools/kunit/ |
| 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-6.1.9/drivers/clk/baikal-t1/ |
| D | Kconfig | 8 responsible for the chip subsystems clocking and resetting. It
48 AXI-bus and some subsystems reset. These are mainly the
|
| /linux-6.1.9/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
|
| /linux-6.1.9/drivers/dma/ |
| D | TODO | 11 4. Check other subsystems for dma drivers and merge/move to dmaengine
|
| /linux-6.1.9/Documentation/userspace-api/ebpf/ |
| D | index.rst | 9 kernel subsystems, including networking, tracing and Linux security modules
|
| /linux-6.1.9/drivers/nvme/target/ |
| 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-6.1.9/Documentation/driver-api/80211/ |
| D | introduction.rst | 9 These books attempt to give a description of the various subsystems
|
| /linux-6.1.9/drivers/remoteproc/ |
| 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
|
| /linux-6.1.9/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
|
| /linux-6.1.9/Documentation/devicetree/bindings/spi/ |
| D | sprd,spi-adi.yaml | 34 Since we have multi-subsystems will use unique ADI to access analog chip, when
39 Then we need one hardware spinlock to synchronize between the multiple subsystems.
|
| /linux-6.1.9/Documentation/devicetree/bindings/powerpc/ |
| D | ibm,vas.txt | 3 VAS is a hardware mechanism that allows kernel subsystems and user processes
|
| /linux-6.1.9/Documentation/devicetree/bindings/arm/ |
| D | vexpress-scc.txt | 10 (like silicon temperature sensors) and as interface to other subsystems
|
| /linux-6.1.9/Documentation/ |
| D | subsystem-apis.rst | 7 These books get into the details of how specific kernel subsystems work
|
| /linux-6.1.9/fs/sysfs/ |
| D | Kconfig | 14 and other kernel subsystems.
|
| /linux-6.1.9/Documentation/driver-api/iio/ |
| D | intro.rst | 11 :doc:`input <../input>` subsystems. Hwmon is directed at low sample rate
|
| /linux-6.1.9/Documentation/devicetree/bindings/clock/ |
| D | qcom,rpmhcc.yaml | 15 other hardware subsystems via RSC to control clocks.
|
| /linux-6.1.9/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smd.yaml | 16 sending data between the various subsystems in Qualcomm platforms.
|
| D | qcom,smem.yaml | 15 reserved-memory used to share data between various subsystems and OSes in
|
| /linux-6.1.9/Documentation/admin-guide/ |
| D | lockup-watchdogs.rst | 37 perf subsystems, respectively. A direct consequence of this is that,
39 subsystems are present.
|
| /linux-6.1.9/Documentation/userspace-api/media/dvb/ |
| D | fe-set-tone.rst | 37 Usually, satellite antenna subsystems require that the digital TV device
|
1234567