Searched refs:subsystem (Results 1 – 25 of 581) sorted by relevance
12345678910>>...24
1295 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10241102,1341 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10211102,1359 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10011102,1398 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x20011102,1408 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x42011102,1418 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40041102,1427 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40071102,1436 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40011102,1444 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40021102,1452 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40021102,[all …]
6 graphics subsystem.9 - compatible: Should be "rockchip,display-subsystem"16 display-subsystem {17 compatible = "rockchip,display-subsystem";
47 subsystems. Once a client subsystem is loaded, it will appear as a117 object in the subsystem. It has attributes that match values on that119 and its attributes, allowing the subsystem to ignore all but the127 A subsystem is the top level of a client module. During initialization,128 the client module registers the subsystem with configfs, the subsystem130 subsystem is also a config_group, and can do everything a config_group154 structure that actually represents what the subsystem is doing. The168 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 new287 If the subsystem wants the child to be a group itself, the subsystem[all …]
17 | |-- subsystem -> ../../../class/video_output22 | |-- subsystem -> ../../../class/video_output27 | |-- subsystem -> ../../../class/video_output32 |-- subsystem -> ../../../class/video_output
68 - subsystem (``block``, ``tty``, ``pci``, ...)71 - retrieved by reading the "subsystem"-link and using only the108 - Classification by subsystem115 classification directories into one place at ``/sys/subsystem``,117 classes, including the converted block subsystem, will show up119 The devices belonging to a subsystem will create a symlink in the120 "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 to126 subsystem name.[all …]
18 subsystem internals.39 subsystem to gather info on devices, request/map memory region58 subsystem.96 The following people have contributed to the RapidIO subsystem directly
14 subsystem logic for virtual LUN 0 access22 Say Y here to enable the TCM/IBLOCK subsystem plugin for non-buffered28 Say Y here to enable the TCM/FILEIO subsystem plugin for buffered35 Say Y here to enable the TCM/pSCSI subsystem plugin for non-buffered42 Say Y here to enable the TCM/USER subsystem plugin for a userspace
4 The FPGA subsystem supports reprogramming FPGAs dynamically under7 * The FPGA subsystem is vendor agnostic.9 * The FPGA subsystem separates upper layers (userspace interfaces and27 this is the subsystem for you. Low level FPGA manager drivers contain28 the knowledge of how to program a specific device. This subsystem40 of an FPGA. This subsystem includes fpga-bridge.c and the low level
10 This document describes the basics of the Linux RapidIO subsystem and provides16 Because the RapidIO subsystem follows the Linux device model it is integrated20 The Linux RapidIO subsystem is architecture independent and therefore defines22 subsystem operations.28 Each of these components is represented in the subsystem by an associated data29 structure. The core logical components of the RapidIO subsystem are defined37 packets (transactions). In the RapidIO subsystem each master port is represented43 RapidIO master ports are serviced by subsystem specific mport device drivers44 that provide functionality defined for this subsystem. To provide a hardware45 independent interface for RapidIO subsystem operations, rio_mport structure[all …]
2 RapidIO subsystem mport character device driver (rio_mport_cdev.c)16 This driver (MPORT_CDEV) provides access to basic RapidIO subsystem operations25 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 subsystem66 subsystem with limitations set by available mport implementation.
53 A *subsystem* is a module that makes use of the task grouping55 particular ways. A subsystem is typically a "resource controller" that58 virtualization subsystem.62 hierarchy, and a set of subsystems; each subsystem has system-specific107 At one extreme, each resource controller or subsystem could be in a179 cgroup_subsys_state objects, one for each cgroup subsystem184 subsystem state is something that's expected to happen frequently217 It's not currently possible to bind a new subsystem to an active218 cgroup hierarchy, or to unbind a subsystem from an active cgroup231 for each active hierarchy, the subsystem names and the cgroup name[all …]
54 my $subsystem = 0;258 'subsystem!' => \$subsystem,309 $subsystem = 0;314 my $selections = $email + $scm + $status + $subsystem + $web;609 my @subsystem = ();631 if ($subsystem) {632 @subsystem = uniq(@subsystem);633 output(@subsystem);826 @subsystem = ();1222 my $subsystem = $typevalue[$start];[all …]
3 # Bluetooth subsystem configuration7 tristate "Bluetooth subsystem support"26 Linux Bluetooth subsystem consist of several layers:41 To use Linux Bluetooth subsystem, you will need several user-space100 Run self tests when initializing the Bluetooth subsystem. This104 When the Bluetooth subsystem is built as module, then the test106 subsystem is compiled into the kernel image, then the test cases
33 static unsigned int subsystem[SNDRV_CARDS]; variable41 module_param_array(subsystem, int, NULL, 0444);42 MODULE_PARM_DESC(subsystem, "Override subsystem ID for Creative X-Fi driver");91 pci_id->driver_data, subsystem[dev], &atc); in ct_card_probe()
5 Some LED devices provide two modes - torch and flash. In the LED subsystem13 registered in the LED subsystem with led_classdev_flash_register function.29 A LED subsystem driver can be controlled also from the level of VideoForLinux230 subsystem. In order to enable this CONFIG_V4L2_FLASH_LED_CLASS symbol has to34 V4L2 subsystem. The function takes six arguments:88 Opening the V4L2 flash sub-device makes the LED subsystem sysfs interface
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.
9 - clocks: phandle to the clocks feeding the display engine subsystem.13 - "bus": the bus clock for the whole display engine subsystem15 - resets: phandle to the reset control for the display engine subsystem.
14 - clocks: phandle to the clocks feeding the display engine subsystem.17 - "bus": the bus clock for the whole display engine subsystem19 - resets: phandle to the reset control for the display engine subsystem.
45 The /sbin/hotplug program can be invoked by any subsystem as part of its46 reaction to a configuration change, from a thread in that subsystem.47 Only one parameter is required: the name of a subsystem being notified of50 the subsystem making that invocation.62 The USB subsystem currently invokes ``/sbin/hotplug`` when USB devices122 Most USB device drivers should pass these tables to the USB subsystem as123 well as to the module management subsystem. Not all, though: some driver127 Drivers that connect directly to the USB subsystem should be declared145 When the USB subsystem knows about a driver's device ID table, it's used when
12 The Linux USB subsystem has grown from supporting only two different44 excellent introduction to the Linux USB subsystem can be found at the46 subsystem is structured and introduces the reader to the concept of USB50 the Linux USB subsystem, giving it some information about which devices53 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 that76 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 device91 /* register this driver with the USB subsystem */[all …]
21 - sti-display-subsystem: Master device for DRM sub-components25 - compatible: "st,sti-display-subsystem"29 must be a child of sti-display-subsystem45 must be a child of sti-display-subsystem57 must be a child of sti-display-subsystem74 must be a child of sti-display-subsystem87 must be a child of sti-display-subsystem102 must be a child of sti-display-subsystem175 sti-display-subsystem {176 compatible = "st,sti-display-subsystem";
33 this switch is set the RapidIO subsystem will enable all52 bool "RapidIO subsystem debug messages"55 Say Y here if you want the RapidIO subsystem to produce a bunch of57 problem with the RapidIO subsystem and want to see more of what is68 for RapidIO subsystem. You may select single built-in method or
6 properties specify which subsystem the timers are paired with.8 "qcom,kpss-timer" - krait subsystem9 "qcom,scss-timer" - scorpion subsystem
2 hrtimers - subsystem for high-resolution kernel timers5 This patch introduces a new subsystem for high-resolution kernel timers.7 One might ask the question: we already have a timer subsystem36 - the implementation of the current posix-timer subsystem on top of51 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 just65 yet, the hrtimer subsystem can be easily extended with high-resolution75 hrtimers. E.g. we could decrease the frequency of the timeout subsystem78 hrtimer subsystem implementation details[all …]
12 through cpuidle subsystem.21 through cpuidle subsystem.
