Searched refs:subsystems (Results 1 – 25 of 146) sorted by relevance
123456
/kernel/linux/linux-5.10/Documentation/sphinx/ |
D | maintainers_include.py | 53 subsystems = False 74 if maintainers and not subsystems: 76 subsystems = True 102 elif subsystems:
|
/kernel/linux/linux-5.10/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 …]
|
/kernel/linux/linux-5.10/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.
|
/kernel/linux/linux-5.10/Documentation/dev-tools/kunit/ |
D | style.rst | 24 and subsystems. A test suite is a group of tests which test a related area of 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/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
|
/kernel/linux/linux-5.10/drivers/dma/ |
D | TODO | 11 4. Check other subsystems for dma drivers and merge/move to dmaengine
|
/kernel/linux/linux-5.10/drivers/remoteproc/ |
D | Kconfig | 188 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/drivers/nvme/target/ |
D | discovery.c | 75 list_for_each_entry(s, &port->subsystems, entry) { in nvmet_subsys_disc_changed() 150 list_for_each_entry(p, &req->port->subsystems, entry) { in discovery_log_entries() 207 list_for_each_entry(p, &req->port->subsystems, entry) { in nvmet_execute_disc_get_log_page()
|
/kernel/linux/linux-5.10/Documentation/driver-api/80211/ |
D | introduction.rst | 9 These books attempt to give a description of the various subsystems
|
/kernel/linux/linux-5.10/drivers/staging/unisys/ |
D | TODO | 11 - move individual drivers into proper driver subsystems
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/powerpc/ |
D | ibm,vas.txt | 3 VAS is a hardware mechanism that allows kernel subsystems and user processes
|
/kernel/linux/linux-5.10/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
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/spi/ |
D | spi-sprd-adi.txt | 21 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/devicetree/bindings/arm/ |
D | vexpress-scc.txt | 10 (like silicon temperature sensors) and as interface to other subsystems
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/qcom/ |
D | qcom,smem.txt | 4 between various subsystems and OSes in Qualcomm platforms.
|
D | rpmh-rsc.txt | 28 or idle. When all subsystems like Modem, GPU, CPU are idle, the resource state 29 will be an aggregate of the sleep votes from each of those subsystems. Clients
|
/kernel/linux/linux-5.10/Documentation/driver-api/iio/ |
D | intro.rst | 11 :doc:`input <../input>` subsystems. Hwmon is directed at low sample rate
|
/kernel/linux/linux-5.10/fs/sysfs/ |
D | Kconfig | 14 and other kernel subsystems.
|
/kernel/linux/linux-5.10/arch/powerpc/platforms/powernv/ |
D | Kconfig | 44 to be accessible to kernel subsystems and user processes.
|
/kernel/linux/linux-5.10/Documentation/admin-guide/ |
D | lockup-watchdogs.rst | 37 perf subsystems, respectively. A direct consequence of this is that, 39 subsystems are present.
|
/kernel/linux/linux-5.10/Documentation/userspace-api/media/dvb/ |
D | fe-set-tone.rst | 37 Usually, satellite antenna subsystems require that the digital TV device
|
D | fe-set-voltage.rst | 37 Usually, a satellite antenna subsystems require that the digital TV
|
/kernel/linux/linux-5.10/drivers/powercap/ |
D | Kconfig | 9 The power capping sysfs interface allows kernel subsystems to expose power
|
/kernel/linux/linux-5.10/Documentation/driver-api/ |
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
|
/kernel/linux/linux-5.10/drivers/clk/baikal-t1/ |
D | Kconfig | 8 responsible for the chip subsystems clocking and resetting. It
|
123456