Home
last modified time | relevance | path

Searched refs:subsystem (Results 1 – 25 of 551) sorted by relevance

12345678910>>...23

/Linux-v4.19/sound/pci/emu10k1/
Demu10k1_main.c1310 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10241102,
1356 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10211102,
1374 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10011102,
1413 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x20011102,
1423 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x42011102,
1433 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40041102,
1442 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40071102,
1451 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40011102,
1459 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40021102,
1467 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40021102,
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/display/rockchip/
Drockchip-drm.txt6 graphics subsystem.
9 - compatible: Should be "rockchip,display-subsystem"
16 display-subsystem {
17 compatible = "rockchip,display-subsystem";
/Linux-v4.19/Documentation/filesystems/configfs/
Dconfigfs.txt47 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 …]
/Linux-v4.19/Documentation/
Dvideo-output.txt17 | |-- subsystem -> ../../../class/video_output
22 | |-- subsystem -> ../../../class/video_output
27 | |-- subsystem -> ../../../class/video_output
32 |-- subsystem -> ../../../class/video_output
/Linux-v4.19/drivers/target/
DKconfig13 subsystem logic for virtual LUN 0 access
21 Say Y here to enable the TCM/IBLOCK subsystem plugin for non-buffered
27 Say Y here to enable the TCM/FILEIO subsystem plugin for buffered
34 Say Y here to enable the TCM/pSCSI subsystem plugin for non-buffered
41 Say Y here to enable the TCM/USER subsystem plugin for a userspace
/Linux-v4.19/Documentation/driver-api/fpga/
Dintro.rst4 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-v4.19/Documentation/rapidio/
Drapidio.txt10 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
44 independent interface for RapidIO subsystem operations, rio_mport structure
[all …]
Dmport_cdev.txt1 RapidIO subsystem mport character device driver (rio_mport_cdev.c)
20 This driver (MPORT_CDEV) provides access to basic RapidIO subsystem operations
29 following RapidIO bus and subsystem operations:
60 - Manage device objects supported by RapidIO subsystem (RIO_DEV_ADD/RIO_DEV_DEL).
63 kernel RapidIO subsystem.
67 This device driver uses standard interfaces defined by kernel RapidIO subsystem
69 subsystem with limitations set by available mport implementation.
/Linux-v4.19/Documentation/admin-guide/
Dsysfs-rules.rst68 - 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 …]
/Linux-v4.19/Documentation/cgroup-v1/
Dcgroups.txt49 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
227 for each active hierarchy, the subsystem names and the cgroup name
[all …]
/Linux-v4.19/net/bluetooth/
DKconfig2 # 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
98 Run self tests when initializing the Bluetooth subsystem. This
102 When the Bluetooth subsystem is built as module, then the test
104 subsystem is compiled into the kernel image, then the test cases
/Linux-v4.19/scripts/
Dget_maintainer.pl53 my $subsystem = 0;
256 'subsystem!' => \$subsystem,
307 $subsystem = 0;
312 my $selections = $email + $scm + $status + $subsystem + $web;
607 my @subsystem = ();
629 if ($subsystem) {
630 @subsystem = uniq(@subsystem);
631 output(@subsystem);
824 @subsystem = ();
1219 my $subsystem = $typevalue[$start];
[all …]
/Linux-v4.19/sound/pci/ctxfi/
Dxfi.c36 static unsigned int subsystem[SNDRV_CARDS]; variable
44 module_param_array(subsystem, int, NULL, 0444);
45 MODULE_PARM_DESC(subsystem, "Override subsystem ID for Creative X-Fi driver");
94 pci_id->driver_data, subsystem[dev], &atc); in ct_card_probe()
/Linux-v4.19/Documentation/leds/
Dleds-class-flash.txt5 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.
28 A LED subsystem driver can be controlled also from the level of VideoForLinux2
29 subsystem. In order to enable this CONFIG_V4L2_FLASH_LED_CLASS symbol has to
33 V4L2 subsystem. The function takes six arguments:
71 Opening the V4L2 flash sub-device makes the LED subsystem sysfs interface
/Linux-v4.19/Documentation/devicetree/bindings/clock/
Dsun9i-de.txt9 - clocks: phandle to the clocks feeding the display engine subsystem.
13 - "bus": the bus clock for the whole display engine subsystem
15 - resets: phandle to the reset control for the display engine subsystem.
Dsun8i-de2.txt13 - clocks: phandle to the clocks feeding the display engine subsystem.
16 - "bus": the bus clock for the whole display engine subsystem
18 - resets: phandle to the reset control for the display engine subsystem.
/Linux-v4.19/Documentation/driver-api/
Drapidio.rst18 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-v4.19/drivers/rapidio/
DKconfig21 this switch is set the RapidIO subsystem will enable all
40 bool "RapidIO subsystem debug messages"
43 Say Y here if you want the RapidIO subsystem to produce a bunch of
45 problem with the RapidIO subsystem and want to see more of what is
56 for RapidIO subsystem. You may select single built-in method or
/Linux-v4.19/Documentation/driver-api/usb/
Dhotplug.rst45 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
Dwriting_usb_driver.rst12 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 …]
/Linux-v4.19/Documentation/devicetree/bindings/display/
Dst,stih4xx.txt21 - 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-v4.19/Documentation/devicetree/bindings/timer/
Dqcom,msm-timer.txt6 properties specify which subsystem the timers are paired with.
8 "qcom,kpss-timer" - krait subsystem
9 "qcom,scss-timer" - scorpion subsystem
/Linux-v4.19/drivers/cpuidle/
DKconfig.powerpc11 through cpuidle subsystem.
20 through cpuidle subsystem.
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-bus-css21 subchannel, as reported by the channel subsystem
31 channel subsystem when last queried by the common I/O
33 in sync with the values current in the channel subsystem).
/Linux-v4.19/Documentation/timers/
Dhrtimers.txt2 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 …]

12345678910>>...23