| /linux/sound/pci/emu10k1/ |
| A 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,
1772 uint subsystem) in snd_emu10k1_create() argument
1814 if (subsystem) { in snd_emu10k1_create()
1815 if (c->subsystem && (c->subsystem == subsystem)) in snd_emu10k1_create()
1820 if (c->subsystem && (c->subsystem != emu->serial)) in snd_emu10k1_create()
1833 if (c->subsystem && !subsystem) in snd_emu10k1_create()
1835 else if (subsystem) in snd_emu10k1_create()
[all …]
|
| /linux/Documentation/dev-tools/kunit/ |
| A 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
86 Test suites are named after the subsystem they are part of. If a subsystem
88 subsystem name, separated by an underscore.
103 Part of the ``ext4`` subsystem, testing the ``inode`` area.
107 Part of the ``apparmor`` subsystem, testing the ``property_entry`` area.
110 the subsystem name.
115 There's 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
306 If the subsystem wants the child to be a group itself, the subsystem
316 config_item_put() on the item on behalf of the subsystem.
330 teardown happens, the subsystem can implement the
356 A subsystem consists of a toplevel config_group and a mutex.
363 When the register call returns, the subsystem is live, and it
365 the subsystem must be ready for it.
371 subsystem/group and the simple_child item in
420 in its own subsystem).
[all …]
|
| /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/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.
41 I am the sole maintainer for the documentation subsystem, and I am doing
|
| /linux/drivers/remoteproc/ |
| A 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/Documentation/admin-guide/ |
| 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 | 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 | 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/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/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/admin-guide/cgroup-v1/ |
| A D | cgroups.rst | 53 A *subsystem* is a module that makes use of the task grouping
58 virtualization subsystem.
179 cgroup_subsys_state objects, one for each cgroup subsystem
313 the "cpuset" cgroup subsystem, the steps are something like::
485 you give a subsystem a name.
539 Each subsystem should:
551 Called to allocate a subsystem state object for a cgroup. The
552 subsystem should allocate its subsystem state object for the passed
558 create the root subsystem state for this subsystem; this case can be
581 callback, @cgrp should be considered dead to the subsystem.
[all …]
|
| /linux/Documentation/devicetree/bindings/display/rockchip/ |
| A D | rockchip-drm.yaml | 16 graphics subsystem.
20 const: rockchip,display-subsystem
37 display-subsystem {
38 compatible = "rockchip,display-subsystem";
|
| /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/scripts/ |
| A D | get_maintainer.pl | 56 my $subsystem = 0;
318 $subsystem = 0;
632 my @subsystem = ();
653 if ($subsystem) {
654 @subsystem = uniq(@subsystem);
848 @subsystem = ();
1255 $subsystem = substr($subsystem, 0, $output_section_maxlen - 3);
1257 $subsystem = $subsystem . "...";
1259 return $subsystem;
1307 $subsystem = "";
[all …]
|
| /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/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/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
|
| /linux/net/bluetooth/ |
| A 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
121 Run self tests when initializing the Bluetooth subsystem. This
125 When the Bluetooth subsystem is built as module, then the test
127 subsystem is compiled into the kernel image, then the test cases
|
| /linux/Documentation/driver-api/usb/ |
| A 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
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
94 /* register this driver with the USB subsystem */
108 itself with the USB subsystem. This is done with usb_deregister()
113 /* deregister this driver with the USB subsystem */
188 subsystem. This can be seen in the following code::
215 called when the urb is finished by the USB subsystem. The callback
[all …]
|
| 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";
|
| /linux/Documentation/timers/ |
| A 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 …]
|
| /linux/drivers/rapidio/ |
| A 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
|