| /linux/sound/pci/emu10k1/ |
| A D | emu10k1_main.c | 945 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10241102,
991 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10211102,
1018 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10011102,
1057 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x20011102,
1469 uint subsystem) in snd_emu10k1_create() argument
1512 if (subsystem) { in snd_emu10k1_create()
1513 if (c->subsystem && (c->subsystem == subsystem)) in snd_emu10k1_create()
1518 if (c->subsystem && (c->subsystem != emu->serial)) in snd_emu10k1_create()
1531 if (c->subsystem && !subsystem) in snd_emu10k1_create()
1533 else if (subsystem) in snd_emu10k1_create()
[all …]
|
| /linux/Documentation/dev-tools/kunit/ |
| A 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
84 Test suites are named after the subsystem they are part of. If a subsystem
86 subsystem name, separated by an underscore.
99 Part of the ``ext4`` subsystem, testing the ``inode`` area.
103 Part of the ``apparmor`` subsystem, testing the ``property_entry`` area.
106 the subsystem name.
111 There is no reason to state the subsystem twice.
[all …]
|
| /linux/Documentation/filesystems/ |
| A D | configfs.rst | 124 and its attributes, allowing the subsystem to ignore all but the
133 the client module registers the subsystem with configfs, the subsystem
305 If the subsystem wants the child to be a group itself, the subsystem
315 config_item_put() on the item on behalf of the subsystem.
329 teardown happens, the subsystem can implement the
345 tells configfs to make the subsystem appear in the file tree::
355 A subsystem consists of a toplevel config_group and a mutex.
362 When the register call returns, the subsystem is live, and it
364 the subsystem must be ready for it.
370 subsystem/group and the simple_child item in
[all …]
|
| /linux/Documentation/devicetree/bindings/display/sprd/ |
| A D | sprd,display-subsystem.yaml | 4 $id: http://devicetree.org/schemas/display/sprd/sprd,display-subsystem.yaml#
15 graphics subsystem.
44 const: sprd,display-subsystem
62 display-subsystem {
63 compatible = "sprd,display-subsystem";
|
| /linux/Documentation/admin-guide/ |
| A D | video-output.rst | 17 | |-- subsystem -> ../../../class/video_output
22 | |-- subsystem -> ../../../class/video_output
27 | |-- subsystem -> ../../../class/video_output
32 |-- subsystem -> ../../../class/video_output
|
| A 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``,
126 subsystem name.
128 Assuming ``/sys/class/<subsystem>`` and ``/sys/bus/<subsystem>``, or
133 The converted block subsystem at ``/sys/class/block`` or
[all …]
|
| A 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/Documentation/devicetree/bindings/display/rockchip/ |
| A D | rockchip-drm.yaml | 16 graphics subsystem.
20 const: rockchip,display-subsystem
39 display-subsystem {
40 compatible = "rockchip,display-subsystem";
|
| /linux/Documentation/driver-api/rapidio/ |
| A 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.
29 structure. The core logical components of the RapidIO subsystem are defined
45 independent interface for RapidIO subsystem operations, rio_mport structure
67 The RapidIO subsystem defines the format and initialization method for subsystem
106 After all active master ports are registered with a RapidIO subsystem,
165 on RapidIO subsystem build configuration:
243 first release of RapidIO subsystem code. The enumeration process is
[all …]
|
| A 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/drivers/target/ |
| A 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/Documentation/driver-api/fpga/ |
| A 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/Documentation/doc-guide/ |
| A 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.
48 I am the sole maintainer for the documentation subsystem, and I am doing
|
| /linux/Documentation/driver-api/media/ |
| A 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
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
89 The subsystem maintainer is:
120 subsystem.
144 be one patch for the whole subsystem (if the cleanup is low volume),
[all …]
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| A D | cgroups.rst | 53 A *subsystem* is a module that makes use of the task grouping
58 virtualization subsystem.
181 cgroup_subsys_state objects, one for each cgroup subsystem
315 the "cpuset" cgroup subsystem, the steps are something like::
487 you give a subsystem a name.
541 Each subsystem should:
553 Called to allocate a subsystem state object for a cgroup. The
554 subsystem should allocate its subsystem state object for the passed
560 create the root subsystem state for this subsystem; this case can be
583 callback, @cgrp should be considered dead to the subsystem.
[all …]
|
| /linux/drivers/remoteproc/ |
| A D | qcom_common.c | 106 static int qcom_add_minidump_segments(struct rproc *rproc, struct minidump_subsystem *subsystem, in qcom_add_minidump_segments() argument
122 seg_cnt = le32_to_cpu(subsystem->region_count); in qcom_add_minidump_segments()
123 ptr = ioremap((unsigned long)le64_to_cpu(subsystem->regions_baseptr), in qcom_add_minidump_segments()
152 struct minidump_subsystem *subsystem; in qcom_minidump() local
165 subsystem = &toc->subsystems[minidump_id]; in qcom_minidump()
171 if (subsystem->regions_baseptr == 0 || in qcom_minidump()
172 le32_to_cpu(subsystem->status) != 1 || in qcom_minidump()
173 le32_to_cpu(subsystem->enabled) != MINIDUMP_SS_ENABLED) { in qcom_minidump()
177 if (le32_to_cpu(subsystem->encryption_status) != MINIDUMP_SS_ENCR_DONE) { in qcom_minidump()
188 ret = qcom_add_minidump_segments(rproc, subsystem, rproc_dumpfn_t); in qcom_minidump()
|
| /linux/sound/pci/ctxfi/ |
| A 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/Documentation/leds/ |
| A 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/scripts/ |
| A D | get_maintainer.pl | 58 my $subsystem = 0;
323 $subsystem = 0;
638 my @subsystem = ();
659 if ($subsystem) {
660 @subsystem = uniq(@subsystem);
860 @subsystem = ();
1273 $subsystem = substr($subsystem, 0, $output_section_maxlen - 3);
1275 $subsystem = $subsystem . "...";
1277 return $subsystem;
1325 $subsystem = "";
[all …]
|
| /linux/Documentation/devicetree/bindings/soc/qcom/ |
| A D | qcom,smd.yaml | 19 directly below the device node representing the respective remote subsystem
33 Each subnode of the SMD node represents a remote subsystem or a remote
44 # "rpm" subsystem. For the "rpm" subsystem we have a device tied to the
|
| /linux/net/bluetooth/ |
| A 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
125 Run self tests when initializing the Bluetooth subsystem. This
129 When the Bluetooth subsystem is built as module, then the test
131 subsystem is compiled into the kernel image, then the test cases
|
| /linux/Documentation/maintainer/ |
| A 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
|
| A D | feature-and-driver-maintainers.rst | 17 subsystem.
28 a subsystem could well have a hundred such drivers. Subsystem
31 The exact expectations on the response time will vary by subsystem.
32 The patch review SLA the subsystem had set for itself can sometimes
33 be found in the subsystem documentation. Failing that as a rule of thumb
35 review delay of the subsystem maintainer. The resulting expectations
43 Maintainers must be subscribed and follow the appropriate subsystem-wide
63 than the expected review timeline for the subsystem, maintainer should
90 should be conducted in a manner typical for the larger subsystem.
160 to remember to include the maintainers in discussions and subsystem
|
| /linux/Documentation/driver-api/usb/ |
| A 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
|
| /linux/Documentation/devicetree/bindings/display/ |
| A 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";
|