| /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-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-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-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 …]
|
| D | mport_cdev.rst | 2 RapidIO subsystem mport character device driver (rio_mport_cdev.c)
16 This driver (MPORT_CDEV) provides access to basic RapidIO subsystem operations
25 following RapidIO bus and subsystem operations:
56 - Manage device objects supported by RapidIO subsystem (RIO_DEV_ADD/RIO_DEV_DEL).
59 kernel RapidIO subsystem.
64 This device driver uses standard interfaces defined by kernel RapidIO subsystem
66 subsystem with limitations set by available mport implementation.
|
| /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-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-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-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-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 …]
|
| D | hotplug.rst | 45 The /sbin/hotplug program can be invoked by any subsystem as part of its
46 reaction to a configuration change, from a thread in that subsystem.
47 Only one parameter is required: the name of a subsystem being notified of
50 the subsystem making that invocation.
62 The USB subsystem currently invokes ``/sbin/hotplug`` when USB devices
122 Most USB device drivers should pass these tables to the USB subsystem as
123 well as to the module management subsystem. Not all, though: some driver
127 Drivers that connect directly to the USB subsystem should be declared
145 When the USB subsystem knows about a driver's device ID table, it's used when
|
| /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.
|
| /kernel/linux/linux-5.10/drivers/staging/gasket/ |
| D | gasket_interrupt.h | 21 /* Opaque type used to hold interrupt subsystem data. */
39 * Clean up and re-initialize the MSI-x subsystem.
42 * Performs a teardown of the MSI-x subsystem and re-initializes it. Does not
49 * Reset the counts stored in the interrupt subsystem.
52 * Sets the counts of all interrupts in the subsystem to 0.
86 * Get the health of the interrupt subsystem.
|
| /kernel/linux/linux-5.10/Documentation/leds/ |
| D | leds-class-flash.rst | 5 Some LED devices provide two modes - torch and flash. In the LED subsystem
13 registered in the LED subsystem with led_classdev_flash_register function.
29 A LED subsystem driver can be controlled also from the level of VideoForLinux2
30 subsystem. In order to enable this CONFIG_V4L2_FLASH_LED_CLASS symbol has to
34 V4L2 subsystem. The function takes six arguments:
88 Opening the V4L2 flash sub-device makes the LED subsystem sysfs interface
|
| /kernel/linux/linux-5.10/Documentation/timers/ |
| D | hrtimers.rst | 2 hrtimers - subsystem for high-resolution kernel timers
5 This patch introduces a new subsystem for high-resolution kernel timers.
7 One might ask the question: we already have a timer subsystem
36 - the implementation of the current posix-timer subsystem on top of
51 largely expect the timer subsystem to have near-zero overhead.
62 high-resolution timer subsystem as well.
64 While this subsystem does not offer high-resolution clock sources just
65 yet, the hrtimer subsystem can be easily extended with high-resolution
75 hrtimers. E.g. we could decrease the frequency of the timeout subsystem
78 hrtimer subsystem implementation details
[all …]
|
| /kernel/linux/linux-5.10/Documentation/maintainer/ |
| D | maintainer-entry-profile.rst | 8 subsystem/device-driver-local customs as well as details about the patch
17 Provide an introduction to how the subsystem operates. While MAINTAINERS
19 convey other subsystem-local infrastructure and mechanisms that aid
26 - Does the subsystem have a patchwork instance? Are patchwork state
29 testing feedback that the subsystem uses to gate acceptance?
33 device-driver may point to an entry for its parent subsystem. This makes
46 of related hardware specifications. For example, does the subsystem
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | runtime_pm.rst | 54 are executed by the PM core for the device's subsystem that may be either of
67 If the subsystem chosen by applying the above rules doesn't provide the relevant
75 are referred to as subsystem-level callbacks in what follows.
86 The subsystem-level suspend callback, if present, is _entirely_ _responsible_
90 callback in a device driver as long as the subsystem-level suspend callback
93 * Once the subsystem-level suspend callback (or the driver suspend callback,
121 The subsystem-level resume callback, if present, is **entirely responsible** for
125 callback in a device driver as long as the subsystem-level resume callback knows
128 * Once the subsystem-level resume callback (or the driver resume callback, if
140 The idle callback (a subsystem-level one, if present, or the driver one) is
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/rockchip/ |
| D | rockchip-drm.yaml | 16 graphics subsystem.
20 const: rockchip,display-subsystem
37 display-subsystem {
38 compatible = "rockchip,display-subsystem";
|
| /kernel/linux/linux-5.10/Documentation/sphinx/ |
| D | maintainers_include.py | 72 # Start subsystem processing? This is to skip processing the text
73 # between the Maintainers heading and the first subsystem name.
103 # Skip empty lines: subsystem parser adds them as needed.
106 # Subsystem fields are batched into "field_content"
108 # Render a subsystem entry as:
109 # SUBSYSTEM NAME
116 # Collapse whitespace in subsystem name.
121 # Render a subsystem field as:
|
| /kernel/linux/linux-5.10/drivers/rapidio/ |
| D | Kconfig | 33 this switch is set the RapidIO subsystem will enable all
52 bool "RapidIO subsystem debug messages"
55 Say Y here if you want the RapidIO subsystem to produce a bunch of
57 problem with the RapidIO subsystem and want to see more of what is
68 for RapidIO subsystem. You may select single built-in method or
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | pm.h | 59 * subsystem and generally the rest of the kernel is supposed to prevent
77 * The PM core executes subsystem-level @prepare() for all devices before
95 * The PM core executes subsystem-level @complete() after it has executed
109 * depends on the device's subsystem (PM domain, device type, class or bus
110 * type), but generally the device must be quiescent after subsystem-level
112 * Subsystem-level @suspend() is executed for all devices after invoking
113 * subsystem-level @prepare() for all of them.
121 * depends on the device's subsystem, but generally the driver is expected
125 * driver's @resume() callback is run depends on the platform and subsystem
128 * Subsystem-level @resume() is executed for all devices after invoking
[all …]
|