Home
last modified time | relevance | path

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

1234567891011

/linux-2.6.39/sound/pci/emu10k1/
Demu10k1_main.c1334 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10211102,
1352 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10011102,
1391 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x20011102,
1401 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x42011102,
1411 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40041102,
1420 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40011102,
1428 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40021102,
1436 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40021102,
1451 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x20071102,
1464 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x20061102,
[all …]
Demu10k1.c54 static uint subsystem[SNDRV_CARDS]; /* Force card subsystem model */ variable
75 module_param_array(subsystem, uint, NULL, 0444);
76 MODULE_PARM_DESC(subsystem, "Force card subsystem model.");
129 enable_ir[dev], subsystem[dev], in snd_card_emu10k1_probe()
/linux-2.6.39/Documentation/filesystems/configfs/
Dconfigfs.txt47 subsystems. Once a client subsystem is loaded, it will appear as a
105 object in the subsystem. It has attributes that match values on that
107 and its attributes, allowing the subsystem to ignore all but the
115 A subsystem is the top level of a client module. During initialization,
116 the client module registers the subsystem with configfs, the subsystem
118 subsystem is also a config_group, and can do everything a config_group
142 structure that actually represents what the subsystem is doing. The
156 Usually a subsystem wants the item to display and/or store attributes,
248 …vided, this method is called from mkdir(2) in the group's directory. The subsystem allocates a new
253 If the subsystem wants the child to be a group itself, the subsystem
[all …]
/linux-2.6.39/Documentation/
Dvideo-output.txt17 | |-- subsystem -> ../../../class/video_output
22 | |-- subsystem -> ../../../class/video_output
27 | |-- subsystem -> ../../../class/video_output
32 |-- subsystem -> ../../../class/video_output
Dsysfs-rules.txt64 o subsystem (block, tty, pci, ...)
66 - retrieved by reading the "subsystem"-link and using only the
101 - Classification by subsystem
108 classification directories into one place at /sys/subsystem,
110 classes, including the converted block subsystem, will show up
112 The devices belonging to a subsystem will create a symlink in the
113 "devices" directory at /sys/subsystem/<name>/devices.
115 If /sys/subsystem exists, /sys/bus, /sys/class and /sys/block can be
117 places, as the kernel is free to move a subsystem from one place to
119 subsystem name.
[all …]
/linux-2.6.39/scripts/
Dget_maintainer.pl46 my $subsystem = 0;
205 'subsystem!' => \$subsystem,
244 $subsystem = 0;
249 my $selections = $email + $scm + $status + $subsystem + $web;
471 my @subsystem = ();
494 if ($subsystem) {
495 @subsystem = uniq(@subsystem);
496 output(@subsystem);
550 @subsystem = ();
934 my $subsystem = $typevalue[$start];
[all …]
/linux-2.6.39/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 …]
Dsysfs.txt8 For each RapidIO device, the RapidIO subsystem creates files in an individual
57 Currently Linux RapidIO subsystem does not create any endpoint specific sysfs
65 RapidIO switches have additional attributes in sysfs. RapidIO subsystem supports
67 integrated into the RapidIO subsystem, it offers a method to create
/linux-2.6.39/Documentation/cgroups/
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-2.6.39/drivers/target/
DKconfig10 subsystem logic for virtual LUN 0 access
17 Say Y here to enable the TCM/IBLOCK subsystem plugin for non-buffered
23 Say Y here to enable the TCM/FILEIO subsystem plugin for buffered
29 Say Y here to enable the TCM/pSCSI subsystem plugin for non-buffered
/linux-2.6.39/drivers/rapidio/
DKconfig19 this switch is set the RapidIO subsystem will enable all
26 bool "RapidIO subsystem debug messages"
29 Say Y here if you want the RapidIO subsystem to produce a bunch of
31 problem with the RapidIO subsystem and want to see more of what is
/linux-2.6.39/Documentation/trace/
Devents.txt49 etc., and a full event name looks like this: <subsystem>:<event>. The
50 subsystem name is optional, but it is displayed in the available_events
51 file. All of the events in a subsystem can be specified via the syntax
52 "<subsystem>:*"; for example, to enable all irq events, you can use the
71 To enable all events in sched subsystem:
234 To clear the filters for all events in a subsystem, write a '0' to the
235 subsystem's filter file.
240 For convenience, filters for every event in a subsystem can be set or
242 at the root of the subsystem. Note however, that if a filter for any
243 event within the subsystem lacks a field specified in the subsystem
[all …]
/linux-2.6.39/sound/pci/ctxfi/
Dxfi.c35 static unsigned int subsystem[SNDRV_CARDS]; variable
43 module_param_array(subsystem, int, NULL, 0444);
44 MODULE_PARM_DESC(subsystem, "Override subsystem ID for Creative X-Fi driver");
91 pci_id->driver_data, subsystem[dev], &atc); in ct_card_probe()
/linux-2.6.39/net/bluetooth/
DKconfig2 # Bluetooth subsystem configuration
6 tristate "Bluetooth subsystem support"
16 Linux Bluetooth subsystem consist of several layers:
29 To use Linux Bluetooth subsystem, you will need several user-space
/linux-2.6.39/lib/
Dkobject_uevent.c135 const char *subsystem; in kobject_uevent_env() local
182 subsystem = uevent_ops->name(kset, kobj); in kobject_uevent_env()
184 subsystem = kobject_name(&kset->kobj); in kobject_uevent_env()
185 if (!subsystem) { in kobject_uevent_env()
211 retval = add_uevent_var(env, "SUBSYSTEM=%s", subsystem); in kobject_uevent_env()
298 argv [1] = (char *)subsystem; in kobject_uevent_env()
/linux-2.6.39/Documentation/usb/
Dhotplug.txt40 The /sbin/hotplug program can be invoked by any subsystem as part of its
41 reaction to a configuration change, from a thread in that subsystem.
42 Only one parameter is required: the name of a subsystem being notified of
45 the subsystem making that invocation.
59 The USB subsystem currently invokes /sbin/hotplug when USB devices
116 Most USB device drivers should pass these tables to the USB subsystem as
117 well as to the module management subsystem. Not all, though: some driver
121 Drivers that connect directly to the USB subsystem should be declared
139 When the USB subsystem knows about a driver's device ID table, it's used when
/linux-2.6.39/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-2.6.39/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 …]
/linux-2.6.39/net/rfkill/
DKconfig2 # RF switch subsystem configuration
5 tristate "RF switch subsystem support"
/linux-2.6.39/Documentation/scsi/
Dscsi.txt1 SCSI subsystem documentation
4 the SCSI subsystem in the Linux kernel (lk) 2.4 series. See:
10 Notes on using modules in the SCSI subsystem
23 the SCSI subsystem.
/linux-2.6.39/arch/arm/mach-sa1100/
Dbadge4.c230 void badge4_set_5V(unsigned subsystem, int on) in badge4_set_5V() argument
240 badge4_5V_bitmap |= subsystem; in badge4_set_5V()
242 badge4_5V_bitmap &= ~subsystem; in badge4_set_5V()
/linux-2.6.39/Documentation/power/
Druntime_pm.txt52 referred to as subsystem-level callbacks in what follows.
63 The subsystem-level suspend callback is _entirely_ _responsible_ for handling
67 callback in a device driver as long as the subsystem-level suspend callback
70 * Once the subsystem-level suspend callback has completed successfully
74 not communicate with the CPU(s) and RAM until the subsystem-level resume
76 successful execution of the subsystem-level suspend callback is 'suspended'.
78 * If the subsystem-level suspend callback returns -EBUSY or -EAGAIN,
82 * If the subsystem-level suspend callback returns an error code different
93 power state during the execution of the subsystem-level suspend callback, it is
98 The subsystem-level resume callback is _entirely_ _responsible_ for handling the
[all …]
/linux-2.6.39/drivers/isdn/gigaset/
DKconfig13 Note: If you build your ISDN subsystem (ISDN_CAPI or ISDN_I4L)
25 the Kernel CAPI subsystem. To use it with the old ISDN4Linux
26 subsystem you'll have to enable the capidrv glue driver.
/linux-2.6.39/Documentation/dvb/
Dudev.txt1 The DVB subsystem currently registers to the sysfs subsystem using the
44 For every device that registers to the sysfs subsystem with a "dvb" prefix,
/linux-2.6.39/Documentation/w1/
Dw1.generic1 The 1-wire (w1) subsystem
9 The w1 subsystem provides the framework for managing w1 masters and
21 What does the w1 subsystem do?
23 When a w1 master driver registers with the w1 subsystem, the following occurs:
50 registers with the w1 subsystem.

1234567891011