| /kernel/linux/linux-4.19/Documentation/filesystems/configfs/ |
| D | configfs.txt | 47 subsystems. Once a client subsystem is loaded, it will appear as a
117 object in the subsystem. It has attributes that match values on that
119 and its attributes, allowing the subsystem to ignore all but the
127 A subsystem is the top level of a client module. During initialization,
128 the client module registers the subsystem with configfs, the subsystem
130 subsystem is also a config_group, and can do everything a config_group
154 structure that actually represents what the subsystem is doing. The
168 Usually a subsystem wants the item to display and/or store attributes,
282 …vided, this method is called from mkdir(2) in the group's directory. The subsystem allocates a new
287 If the subsystem wants the child to be a group itself, the subsystem
[all …]
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/kunit/ |
| D | style.rst | 25 the kernel, and a subsystem is a set of test suites which test different parts
26 of the same kernel subsystem or driver.
31 Every test suite must belong to a subsystem. A subsystem is a collection of one
33 rule of thumb is that a test subsystem should match a single kernel module. If
34 the code being tested can't be compiled as a module, in many cases the subsystem
43 If a test subsystem name has multiple components, they should be separated by
44 underscores. *Do not* include "test" or "kunit" directly in the subsystem name
66 suffix, and ``qos`` is ambiguous as a subsystem name. ``power_qos`` would be a
69 The corresponding module name is ``parport_pc``, so this subsystem should also
86 Test suites are named after the subsystem they are part of. If a subsystem
[all …]
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | configfs.rst | 50 subsystems. Once a client subsystem is loaded, it will appear as a
122 object in the subsystem. It has attributes that match values on that
124 and its attributes, allowing the subsystem to ignore all but the
132 A subsystem is the top level of a client module. During initialization,
133 the client module registers the subsystem with configfs, the subsystem
135 subsystem is also a config_group, and can do everything a config_group
162 structure that actually represents what the subsystem is doing. The
176 Usually a subsystem wants the item to display and/or store attributes,
301 mkdir(2) in the group's directory. The subsystem allocates a new
306 If the subsystem wants the child to be a group itself, the subsystem
[all …]
|
| /kernel/linux/linux-4.19/drivers/target/ |
| D | Kconfig | 13 subsystem logic for virtual LUN 0 access
18 tristate "TCM/IBLOCK Subsystem Plugin for Linux/BLOCK"
21 Say Y here to enable the TCM/IBLOCK subsystem plugin for non-buffered
25 tristate "TCM/FILEIO Subsystem Plugin for Linux/VFS"
27 Say Y here to enable the TCM/FILEIO subsystem plugin for buffered
31 tristate "TCM/pSCSI Subsystem Plugin for Linux/SCSI"
34 Say Y here to enable the TCM/pSCSI subsystem plugin for non-buffered
38 tristate "TCM/USER Subsystem Plugin for Linux"
41 Say Y here to enable the TCM/USER subsystem plugin for a userspace
|
| /kernel/linux/linux-5.10/drivers/target/ |
| D | Kconfig | 14 subsystem logic for virtual LUN 0 access
19 tristate "TCM/IBLOCK Subsystem Plugin for Linux/BLOCK"
22 Say Y here to enable the TCM/IBLOCK subsystem plugin for non-buffered
26 tristate "TCM/FILEIO Subsystem Plugin for Linux/VFS"
28 Say Y here to enable the TCM/FILEIO subsystem plugin for buffered
32 tristate "TCM/pSCSI Subsystem Plugin for Linux/SCSI"
35 Say Y here to enable the TCM/pSCSI subsystem plugin for non-buffered
39 tristate "TCM/USER Subsystem Plugin for Linux"
42 Say Y here to enable the TCM/USER subsystem plugin for a userspace
|
| /kernel/linux/linux-4.19/Documentation/rapidio/ |
| D | rapidio.txt | 1 The Linux RapidIO Subsystem
10 This document describes the basics of the Linux RapidIO subsystem and provides
16 Because the RapidIO subsystem follows the Linux device model it is integrated
20 The Linux RapidIO subsystem is architecture independent and therefore defines
22 subsystem operations.
28 Each of these components is represented in the subsystem by an associated data
29 structure. The core logical components of the RapidIO subsystem are defined
36 packets (transactions). In the RapidIO subsystem each master port is represented
42 RapidIO master ports are serviced by subsystem specific mport device drivers
43 that provide functionality defined for this subsystem. To provide a hardware
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/cgroup-v1/ |
| D | cgroups.rst | 34 3.3 Subsystem API
53 A *subsystem* is a module that makes use of the task grouping
55 particular ways. A subsystem is typically a "resource controller" that
58 virtualization subsystem.
62 hierarchy, and a set of subsystems; each subsystem has system-specific
107 At one extreme, each resource controller or subsystem could be in a
179 cgroup_subsys_state objects, one for each cgroup subsystem
184 subsystem state is something that's expected to happen frequently
217 It's not currently possible to bind a new subsystem to an active
218 cgroup hierarchy, or to unbind a subsystem from an active cgroup
[all …]
|
| /kernel/linux/linux-4.19/Documentation/cgroup-v1/ |
| D | cgroups.txt | 30 3.3 Subsystem API
49 A *subsystem* is a module that makes use of the task grouping
51 particular ways. A subsystem is typically a "resource controller" that
54 virtualization subsystem.
58 hierarchy, and a set of subsystems; each subsystem has system-specific
103 At one extreme, each resource controller or subsystem could be in a
175 cgroup_subsys_state objects, one for each cgroup subsystem
180 subsystem state is something that's expected to happen frequently
213 It's not currently possible to bind a new subsystem to an active
214 cgroup hierarchy, or to unbind a subsystem from an active cgroup
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 10 This document describes the basics of the Linux RapidIO subsystem and provides
16 Because the RapidIO subsystem follows the Linux device model it is integrated
20 The Linux RapidIO subsystem is architecture independent and therefore defines
22 subsystem operations.
28 Each of these components is represented in the subsystem by an associated data
29 structure. The core logical components of the RapidIO subsystem are defined
37 packets (transactions). In the RapidIO subsystem each master port is represented
43 RapidIO master ports are serviced by subsystem specific mport device drivers
44 that provide functionality defined for this subsystem. To provide a hardware
45 independent interface for RapidIO subsystem operations, rio_mport structure
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-pxa/include/mach/ |
| D | pxa3xx-regs.h | 40 #define ASCR __REG(0x40f40000) /* Application Subsystem Power Status/Configuration */
41 #define ARSR __REG(0x40f40004) /* Application Subsystem Reset Status */
42 #define AD3ER __REG(0x40f40008) /* Application Subsystem Wake-Up from D3 Enable */
43 #define AD3SR __REG(0x40f4000c) /* Application Subsystem Wake-Up from D3 Status */
44 #define AD2D0ER __REG(0x40f40010) /* Application Subsystem Wake-Up from D2 to D0 Enable */
45 #define AD2D0SR __REG(0x40f40014) /* Application Subsystem Wake-Up from D2 to D0 Status */
46 #define AD2D1ER __REG(0x40f40018) /* Application Subsystem Wake-Up from D2 to D1 Enable */
47 #define AD2D1SR __REG(0x40f4001c) /* Application Subsystem Wake-Up from D2 to D1 Status */
48 #define AD1D0ER __REG(0x40f40020) /* Application Subsystem Wake-Up from D1 to D0 Enable */
49 #define AD1D0SR __REG(0x40f40024) /* Application Subsystem Wake-Up from D1 to D0 Status */
[all …]
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/ |
| D | sysfs-rules.rst | 68 - subsystem (``block``, ``tty``, ``pci``, ...)
71 - retrieved by reading the "subsystem"-link and using only the
108 - Classification by subsystem
115 classification directories into one place at ``/sys/subsystem``,
117 classes, including the converted block subsystem, will show up
119 The devices belonging to a subsystem will create a symlink in the
120 "devices" directory at ``/sys/subsystem/<name>/devices``,
122 If ``/sys/subsystem`` exists, ``/sys/bus``, ``/sys/class`` and ``/sys/block``
124 places, as the kernel is free to move a subsystem from one place to
126 subsystem name.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | sysfs-rules.rst | 68 - subsystem (``block``, ``tty``, ``pci``, ...)
71 - retrieved by reading the "subsystem"-link and using only the
108 - Classification by subsystem
115 classification directories into one place at ``/sys/subsystem``,
117 classes, including the converted block subsystem, will show up
119 The devices belonging to a subsystem will create a symlink in the
120 "devices" directory at ``/sys/subsystem/<name>/devices``,
122 If ``/sys/subsystem`` exists, ``/sys/bus``, ``/sys/class`` and ``/sys/block``
124 places, as the kernel is free to move a subsystem from one place to
126 subsystem name.
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/mach-pxa/include/mach/ |
| D | pxa3xx-regs.h | 43 #define ASCR __REG(0x40f40000) /* Application Subsystem Power Status/Configuration */
44 #define ARSR __REG(0x40f40004) /* Application Subsystem Reset Status */
45 #define AD3ER __REG(0x40f40008) /* Application Subsystem Wake-Up from D3 Enable */
46 #define AD3SR __REG(0x40f4000c) /* Application Subsystem Wake-Up from D3 Status */
47 #define AD2D0ER __REG(0x40f40010) /* Application Subsystem Wake-Up from D2 to D0 Enable */
48 #define AD2D0SR __REG(0x40f40014) /* Application Subsystem Wake-Up from D2 to D0 Status */
49 #define AD2D1ER __REG(0x40f40018) /* Application Subsystem Wake-Up from D2 to D1 Enable */
50 #define AD2D1SR __REG(0x40f4001c) /* Application Subsystem Wake-Up from D2 to D1 Status */
51 #define AD1D0ER __REG(0x40f40020) /* Application Subsystem Wake-Up from D1 to D0 Enable */
52 #define AD1D0SR __REG(0x40f40024) /* Application Subsystem Wake-Up from D1 to D0 Status */
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/aoe/ |
| D | udev.txt | 3 # 8 udev manpage to see whether your udev supports SUBSYSTEM, and
4 # whether it uses one or two equal signs for SUBSYSTEM and KERNEL.
19 SUBSYSTEM=="aoe", KERNEL=="discover", NAME="etherd/%k", GROUP="disk", MODE="0220"
20 SUBSYSTEM=="aoe", KERNEL=="err", NAME="etherd/%k", GROUP="disk", MODE="0440"
21 SUBSYSTEM=="aoe", KERNEL=="interfaces", NAME="etherd/%k", GROUP="disk", MODE="0220"
22 SUBSYSTEM=="aoe", KERNEL=="revalidate", NAME="etherd/%k", GROUP="disk", MODE="0220"
23 SUBSYSTEM=="aoe", KERNEL=="flush", NAME="etherd/%k", GROUP="disk", MODE="0220"
|
| /kernel/linux/linux-4.19/Documentation/aoe/ |
| D | udev.txt | 3 # 8 udev manpage to see whether your udev supports SUBSYSTEM, and
4 # whether it uses one or two equal signs for SUBSYSTEM and KERNEL.
19 SUBSYSTEM=="aoe", KERNEL=="discover", NAME="etherd/%k", GROUP="disk", MODE="0220"
20 SUBSYSTEM=="aoe", KERNEL=="err", NAME="etherd/%k", GROUP="disk", MODE="0440"
21 SUBSYSTEM=="aoe", KERNEL=="interfaces", NAME="etherd/%k", GROUP="disk", MODE="0220"
22 SUBSYSTEM=="aoe", KERNEL=="revalidate", NAME="etherd/%k", GROUP="disk", MODE="0220"
23 SUBSYSTEM=="aoe", KERNEL=="flush", NAME="etherd/%k", GROUP="disk", MODE="0220"
|
| /kernel/linux/linux-5.10/samples/configfs/ |
| D | configfs_sample.c | 24 * This first example is a childless subsystem. It cannot create
28 * This is not necessary if a subsystem has no attributes directly
29 * on the subsystem. See the next example, 02-simple-children, for
30 * such a subsystem.
79 "The childless subsystem is the simplest possible subsystem in\n" in childless_description_show()
120 * subsystem, as it has no attributes of its own.
204 "This subsystem allows the creation of child config_items. These\n" in simple_children_description_show()
254 * the simple_children group is not the subsystem itself, it is a
255 * child of the subsystem. Creation of a group in the subsystem creates
282 "This subsystem allows the creation of child config_groups. These\n" in group_children_description_show()
[all …]
|
| /kernel/linux/linux-4.19/samples/configfs/ |
| D | configfs_sample.c | 40 * This first example is a childless subsystem. It cannot create
44 * This is not necessary if a subsystem has no attributes directly
45 * on the subsystem. See the next example, 02-simple-children, for
46 * such a subsystem.
101 "The childless subsystem is the simplest possible subsystem in\n" in childless_description_show()
143 * subsystem, as it has no attributes of its own.
236 "This subsystem allows the creation of child config_items. These\n" in simple_children_description_show()
287 * the simple_children group is not the subsystem itself, it is a
288 * child of the subsystem. Creation of a group in the subsystem creates
315 "This subsystem allows the creation of child config_groups. These\n" in group_children_description_show()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| D | writing_usb_driver.rst | 12 The Linux USB subsystem has grown from supporting only two different
44 excellent introduction to the Linux USB subsystem can be found at the
46 subsystem is structured and introduces the reader to the concept of USB
50 the Linux USB subsystem, giving it some information about which devices
53 information is passed to the USB subsystem in the :c:type:`usb_driver`
73 another kernel subsystem, such as the SCSI, network or TTY subsystem.
75 subsystem, and any user-space interactions are provided through that
76 interface. But for drivers that do not have a matching kernel subsystem,
78 is needed. The USB subsystem provides a way to register a minor device
91 /* register this driver with the USB subsystem */
[all …]
|
| /kernel/linux/linux-4.19/Documentation/driver-api/usb/ |
| D | writing_usb_driver.rst | 12 The Linux USB subsystem has grown from supporting only two different
44 excellent introduction to the Linux USB subsystem can be found at the
46 subsystem is structured and introduces the reader to the concept of USB
50 the Linux USB subsystem, giving it some information about which devices
53 information is passed to the USB subsystem in the :c:type:`usb_driver`
73 another kernel subsystem, such as the SCSI, network or TTY subsystem.
75 subsystem, and any user-space interactions are provided through that
76 interface. But for drivers that do not have a matching kernel subsystem,
78 is needed. The USB subsystem provides a way to register a minor device
91 /* register this driver with the USB subsystem */
[all …]
|
| /kernel/linux/linux-4.19/net/bluetooth/ |
| D | Kconfig | 2 # Bluetooth subsystem configuration
6 tristate "Bluetooth subsystem support"
24 Linux Bluetooth subsystem consist of several layers:
39 To use Linux Bluetooth subsystem, you will need several user-space
97 Run self tests when initializing the Bluetooth subsystem. This
101 When the Bluetooth subsystem is built as module, then the test
103 subsystem is compiled into the kernel image, then the test cases
|
| /kernel/linux/linux-4.19/Documentation/driver-api/fpga/ |
| D | intro.rst | 4 The FPGA subsystem supports reprogramming FPGAs dynamically under
7 * The FPGA subsystem is vendor agnostic.
9 * The FPGA subsystem separates upper layers (userspace interfaces and
27 this is the subsystem for you. Low level FPGA manager drivers contain
28 the knowledge of how to program a specific device. This subsystem
40 of an FPGA. This subsystem includes fpga-bridge.c and the low level
|
| /kernel/linux/linux-5.10/Documentation/driver-api/fpga/ |
| D | intro.rst | 4 The FPGA subsystem supports reprogramming FPGAs dynamically under
7 * The FPGA subsystem is vendor agnostic.
9 * The FPGA subsystem separates upper layers (userspace interfaces and
27 this is the subsystem for you. Low level FPGA manager drivers contain
28 the knowledge of how to program a specific device. This subsystem
40 of an FPGA. This subsystem includes fpga-bridge.c and the low level
|
| /kernel/linux/linux-5.10/Documentation/doc-guide/ |
| D | maintainer-profile.rst | 3 Documentation subsystem maintainer entry profile
6 The documentation "subsystem" is the central coordinating point for the
12 It's worth noting, though, that the boundaries of this subsystem are rather
13 fuzzier than normal. Many other subsystem maintainers like to keep control
17 always) maintained by the relevant subsystem maintainer.
41 I am the sole maintainer for the documentation subsystem, and I am doing
|
| /kernel/linux/linux-5.10/net/bluetooth/ |
| D | Kconfig | 3 # Bluetooth subsystem configuration
7 tristate "Bluetooth subsystem support"
26 Linux Bluetooth subsystem consist of several layers:
41 To use Linux Bluetooth subsystem, you will need several user-space
114 Run self tests when initializing the Bluetooth subsystem. This
118 When the Bluetooth subsystem is built as module, then the test
120 subsystem is compiled into the kernel image, then the test cases
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-counter-104-quad-8 | 9 This interface is deprecated; please use the Counter subsystem.
18 This interface is deprecated; please use the Counter subsystem.
54 This interface is deprecated; please use the Counter subsystem.
64 This interface is deprecated; please use the Counter subsystem.
73 This interface is deprecated; please use the Counter subsystem.
96 This interface is deprecated; please use the Counter subsystem.
106 This interface is deprecated; please use the Counter subsystem.
115 This interface is deprecated; please use the Counter subsystem.
|