| /Linux-v6.1/Documentation/dev-tools/kunit/ |
| D | style.rst | 24 suite is a group of tests which test a related area of the kernel. A subsystem
25 is a set of test suites which test different parts of a kernel subsystem
31 Every test suite must belong to a subsystem. A subsystem is a collection of one
33 test subsystem should match a single kernel module. If the code being tested
34 cannot be compiled as a module, in many cases the subsystem should correspond to
42 If a test subsystem name has multiple components, they should be separated by
43 underscores. *Do not* include "test" or "kunit" directly in the subsystem name
64 suffix. ``qos`` is also ambiguous as a subsystem name, because several parts
65 of the kernel have a ``qos`` subsystem. ``power_qos`` would be a better name.
67 The corresponding module name is ``parport_pc``, so this subsystem should also
[all …]
|
| /Linux-v6.1/sound/pci/emu10k1/ |
| D | emu10k1_main.c | 1282 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10241102,
1328 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10211102,
1346 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10011102,
1385 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x20011102,
1395 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x42011102,
1405 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40041102,
1414 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40071102,
1423 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40011102,
1431 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40021102,
1439 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40021102,
[all …]
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | video-output.rst | 17 | |-- subsystem -> ../../../class/video_output
22 | |-- subsystem -> ../../../class/video_output
27 | |-- subsystem -> ../../../class/video_output
32 |-- subsystem -> ../../../class/video_output
|
| 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 …]
|
| D | rapidio.rst | 18 subsystem internals.
39 subsystem to gather info on devices, request/map memory region
58 subsystem.
96 The following people have contributed to the RapidIO subsystem directly
|
| /Linux-v6.1/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
|
| /Linux-v6.1/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.
|
| /Linux-v6.1/drivers/target/ |
| D | Kconfig | 14 subsystem logic for virtual LUN 0 access
22 Say Y here to enable the TCM/IBLOCK subsystem plugin for non-buffered
28 Say Y here to enable the TCM/FILEIO subsystem plugin for buffered
35 Say Y here to enable the TCM/pSCSI subsystem plugin for non-buffered
42 Say Y here to enable the TCM/USER subsystem plugin for a userspace
|
| /Linux-v6.1/drivers/remoteproc/ |
| D | qcom_common.c | 104 static int qcom_add_minidump_segments(struct rproc *rproc, struct minidump_subsystem *subsystem) in qcom_add_minidump_segments() argument
118 seg_cnt = le32_to_cpu(subsystem->region_count); in qcom_add_minidump_segments()
119 ptr = ioremap((unsigned long)le64_to_cpu(subsystem->regions_baseptr), in qcom_add_minidump_segments()
145 struct minidump_subsystem *subsystem; in qcom_minidump() local
158 subsystem = &toc->subsystems[minidump_id]; in qcom_minidump()
164 if (subsystem->regions_baseptr == 0 || in qcom_minidump()
165 le32_to_cpu(subsystem->status) != 1 || in qcom_minidump()
166 le32_to_cpu(subsystem->enabled) != MD_SS_ENABLED || in qcom_minidump()
167 le32_to_cpu(subsystem->encryption_status) != MD_SS_ENCR_DONE) { in qcom_minidump()
172 ret = qcom_add_minidump_segments(rproc, subsystem); in qcom_minidump()
|
| /Linux-v6.1/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
|
| /Linux-v6.1/Documentation/driver-api/media/ |
| D | maintainer-entry-profile.rst | 7 The media subsystem covers support for a variety of devices: stream
24 by them before being merged via the media subsystem's development
29 add new features to the subsystem must also bring changes to the
32 Due to the size and wide scope of the media subsystem, media's
34 knowledge of a specific aspect of the subsystem. It is the sub-maintainers'
36 following the subsystem rules and are properly using the media kernel and
39 Patches for the media subsystem must be sent to the media mailing list
66 At the media subsystem, we have a group of senior developers that
69 subsystem as a whole. For core changes, whenever possible, multiple
72 The media maintainers that work on specific areas of the subsystem are:
[all …]
|
| D | index.rst | 6 Media subsystem kernel internal API
9 This section contains usage information about media subsystem and
16 - for usage information about media subsystem and supported drivers;
|
| /Linux-v6.1/Documentation/admin-guide/cgroup-v1/ |
| D | cgroups.rst | 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
231 for each active hierarchy, the subsystem names and the cgroup name
[all …]
|
| /Linux-v6.1/scripts/ |
| D | get_maintainer.pl | 56 my $subsystem = 0;
267 'subsystem!' => \$subsystem,
318 $subsystem = 0;
323 my $selections = $email + $scm + $status + $subsystem + $web;
632 my @subsystem = ();
653 if ($subsystem) {
654 @subsystem = uniq(@subsystem);
655 output(@subsystem);
848 @subsystem = ();
1254 my $subsystem = $typevalue[$start];
[all …]
|
| /Linux-v6.1/sound/pci/ctxfi/ |
| D | xfi.c | 32 static unsigned int subsystem[SNDRV_CARDS]; variable
40 module_param_array(subsystem, int, NULL, 0444);
41 MODULE_PARM_DESC(subsystem, "Override subsystem ID for Creative X-Fi driver");
90 pci_id->driver_data, subsystem[dev], &atc); in ct_card_probe()
|
| /Linux-v6.1/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
|
| /Linux-v6.1/net/bluetooth/ |
| D | Kconfig | 3 # Bluetooth subsystem configuration
7 tristate "Bluetooth subsystem support"
26 Linux Bluetooth subsystem consist of several layers:
42 To use Linux Bluetooth subsystem, you will need several user-space
122 Run self tests when initializing the Bluetooth subsystem. This
126 When the Bluetooth subsystem is built as module, then the test
128 subsystem is compiled into the kernel image, then the test cases
|
| /Linux-v6.1/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
|
| /Linux-v6.1/Documentation/driver-api/usb/ |
| 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
|
| 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`
76 another kernel subsystem, such as the SCSI, network or TTY subsystem.
78 subsystem, and any user-space interactions are provided through that
79 interface. But for drivers that do not have a matching kernel subsystem,
81 is needed. The USB subsystem provides a way to register a minor device
94 /* register this driver with the USB subsystem */
[all …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/display/ |
| D | st,stih4xx.txt | 21 - sti-display-subsystem: Master device for DRM sub-components
25 - compatible: "st,sti-display-subsystem"
29 must be a child of sti-display-subsystem
45 must be a child of sti-display-subsystem
57 must be a child of sti-display-subsystem
74 must be a child of sti-display-subsystem
87 must be a child of sti-display-subsystem
102 must be a child of sti-display-subsystem
175 sti-display-subsystem {
176 compatible = "st,sti-display-subsystem";
|
| /Linux-v6.1/Documentation/admin-guide/media/ |
| D | index.rst | 6 Media subsystem admin and user guide
9 This section contains usage information about media subsystem and
23 The media subsystem
|
| /Linux-v6.1/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
|
