Home
last modified time | relevance | path

Searched refs:subsystem (Results 1 – 200 of 385) sorted by relevance

12

/linux-4.1.27/sound/pci/emu10k1/
Demu10k1_main.c1350 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10241102,
1396 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10211102,
1414 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10011102,
1453 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x20011102,
1463 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x42011102,
1473 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40041102,
1482 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40071102,
1491 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40011102,
1499 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40021102,
1507 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40021102,
[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.");
130 enable_ir[dev], subsystem[dev], in snd_card_emu10k1_probe()
/linux-4.1.27/Documentation/devicetree/bindings/video/
Drockchip-drm.txt6 graphics subsystem.
9 - compatible: Should be "rockchip,display-subsystem"
16 display-subsystem {
17 compatible = "rockchip,display-subsystem";
/linux-4.1.27/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-4.1.27/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 …]
Drfkill.txt12 The rfkill subsystem provides a generic interface to disabling any radio
16 The subsystem also provides the ability to react on button presses and
21 The rfkill subsystem has a concept of "hard" and "soft" block, which
28 The rfkill subsystem has two parameters, rfkill.default_state and
34 The rfkill subsystem is composed of three main components:
Dpinctrl.txt1 PINCTRL (PIN CONTROL) subsystem
2 This document outlines the pin control subsystem in Linux
4 This subsystem deals with:
87 To enable the pinctrl subsystem and the subgroups for PINMUX and PINCONF and
119 subsystem has a mechanism for enumerating groups of pins and retrieving the
126 These two groups are presented to the pin control subsystem by implementing
186 The pin control subsystem will call the .get_groups_count() function to
278 Interaction with the GPIO subsystem
287 situations a cross-subsystem mapping between pins and GPIOs is needed.
289 Since the pin controller subsystem have its pinspace local to the pin
[all …]
D00-INDEX135 - info on CPU_IDLE, CPU idle state management subsystem.
169 - info on Linux Digital Video Broadcast (DVB) subsystem.
209 - HSI subsystem overview.
221 - directory with info about the Linux I2O subsystem.
319 - directory with info about devices using the misc dev subsystem
321 - directory with info about the MMC subsystem
333 - directory with information on the NetLabel subsystem.
361 - info on pinctrl subsystem and the PINMUX/PINCONF and drivers
369 - directory with info on the priveledge control subsystem
379 - info on the pulse width modulation driver subsystem
[all …]
Dhsi.txt40 In the Linux kernel the hsi subsystem is supposed to be used for HSI devices.
41 The hsi subsystem contains drivers for hsi controllers including support for
Dphy.txt122 This subsystem is pm runtime enabled. So while creating the PHY,
123 pm_runtime_enable of the phy device created by this subsystem is called and
125 device created by this subsystem will be a child of the device that calls
128 So pm_runtime_get_sync of the phy_device created by this subsystem will invoke
DSM501.txt39 maximum possible resource allocation can be made to the video subsystem
44 occurs the memory footprint of the video subsystem changes.
DSubmittingPatches42 directly. Most subsystem maintainers run their own trees and want to see
43 patches prepared against those trees. See the "T:" entry for the subsystem
149 subsystem maintainer to refer back to earlier patch versions or referenced
266 You should always copy the appropriate subsystem maintainer(s) on any patch
270 cannot find a maintainer for the subsystem your are working on, Andrew
276 to tune it out. Look in the MAINTAINERS file for a subsystem-specific
304 Note, however, that some subsystem maintainers want to come to their own
456 If you are a subsystem or branch maintainer, sometimes you need to slightly
524 one subsystem maintainer then this usually indicates acknowledgement of just
608 Subject: [PATCH 001/123] subsystem: summary phrase
[all …]
Dkselftest.txt35 To run only tests targeted for a single subsystem:
DHOWTO219 main kernel "branches" and lots of different subsystem-specific kernel
224 - subsystem specific kernel trees and patches
299 kernel subsystem developers --- expose their current state of
303 onto such a subsystem kernel tree so that conflicts between the
308 these subsystem repositories are listed in the MAINTAINERS file. Many
311 Before a proposed patch is committed to such a subsystem tree, it is
322 Before updates from subsystem trees are merged into the mainline 4.x
324 testing repository exists into which virtually all subsystem trees are
Ddigsig.txt13 Currently digital signatures are used by the IMA/EVM integrity protection subsystem.
Dstable_kernel_rules.txt46 or subsystem maintainer.
100 other developers and by the relevant subsystem maintainer.
/linux-4.1.27/drivers/target/
DKconfig11 subsystem logic for virtual LUN 0 access
19 Say Y here to enable the TCM/IBLOCK subsystem plugin for non-buffered
25 Say Y here to enable the TCM/FILEIO subsystem plugin for buffered
31 Say Y here to enable the TCM/pSCSI subsystem plugin for non-buffered
38 Say Y here to enable the TCM/USER subsystem plugin for a userspace
/linux-4.1.27/net/bluetooth/
DKconfig2 # Bluetooth subsystem configuration
6 tristate "Bluetooth subsystem support"
23 Linux Bluetooth subsystem consist of several layers:
38 To use Linux Bluetooth subsystem, you will need several user-space
71 Run self tests when initializing the Bluetooth subsystem. This
75 When the Bluetooth subsystem is built as module, then the test
77 subsystem is compiled into the kernel image, then the test cases
/linux-4.1.27/scripts/
Dget_maintainer.pl47 my $subsystem = 0;
214 'subsystem!' => \$subsystem,
253 $subsystem = 0;
258 my $selections = $email + $scm + $status + $subsystem + $web;
482 my @subsystem = ();
504 if ($subsystem) {
505 @subsystem = uniq(@subsystem);
506 output(@subsystem);
560 @subsystem = ();
949 my $subsystem = $typevalue[$start];
[all …]
/linux-4.1.27/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
58 Currently Linux RapidIO subsystem does not create any endpoint specific sysfs
66 RapidIO switches have additional attributes in sysfs. RapidIO subsystem supports
68 integrated into the RapidIO subsystem, it offers a method to create
119 named as "rapidioN" where N = mport ID registered with RapidIO subsystem.
156 lrwxrwxrwx 1 root root 0 Feb 11 15:04 subsystem -> ../../../../../../class/rapidio_port
Dtsi721.txt1 RapidIO subsystem mport driver for IDT Tsi721 PCI Express-to-SRIO bridge.
/linux-4.1.27/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 …]
D00-INDEX13 freezer-subsystem.txt
Dnet_prio.txt25 Each net_prio cgroup contains two files that are subsystem specific
/linux-4.1.27/lib/
Dkobject_uevent.c129 static int init_uevent_argv(struct kobj_uevent_env *env, const char *subsystem) in init_uevent_argv() argument
133 len = strlcpy(&env->buf[env->buflen], subsystem, in init_uevent_argv()
170 const char *subsystem; in kobject_uevent_env() local
216 subsystem = uevent_ops->name(kset, kobj); in kobject_uevent_env()
218 subsystem = kobject_name(&kset->kobj); in kobject_uevent_env()
219 if (!subsystem) { in kobject_uevent_env()
245 retval = add_uevent_var(env, "SUBSYSTEM=%s", subsystem); in kobject_uevent_env()
341 retval = init_uevent_argv(env, subsystem); in kobject_uevent_env()
/linux-4.1.27/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-4.1.27/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-4.1.27/Documentation/devicetree/bindings/drm/imx/
Dfsl-imx-drm.txt5 IPU or other display interface nodes that comprise the graphics subsystem.
8 - compatible: Should be "fsl,imx-display-subsystem"
14 display-subsystem {
15 compatible = "fsl,display-subsystem";
/linux-4.1.27/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-4.1.27/Documentation/devicetree/bindings/arm/msm/
Dtimer.txt6 properties specify which subsystem the timers are paired with.
8 "qcom,kpss-timer" - krait subsystem
9 "qcom,scss-timer" - scorpion subsystem
Dqcom,saw2.txt6 subsystem) into and out of low power modes via a direct connection to
/linux-4.1.27/drivers/cpuidle/
DKconfig.powerpc11 through cpuidle subsystem.
20 through cpuidle subsystem.
/linux-4.1.27/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).
Dsysfs-platform-msi-laptop22 WLAN subsystem enabled: contains either 0 or 1.
29 Bluetooth subsystem enabled: contains either 0 or 1. Please
Dsysfs-ptp15 subsystem.
120 PPS events to the Linux PPS subsystem. To enable PPS
/linux-4.1.27/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 …]
D00-INDEX10 - subsystem for high-resolution kernel timers
/linux-4.1.27/Documentation/locking/
D00-INDEX8 - info on the generic mutex subsystem.
12 - desc. of RT-mutex subsystem with PI (Priority Inheritance) support.
Drt-mutex.txt1 RT-mutex subsystem with PI support
/linux-4.1.27/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.
Dscsi_mid_low_api.txt18 its own subsystem in Linux (e.g. USB and ieee1394). In such cases the
19 SCSI subsystem LLD is a software bridge to the other driver subsystem.
49 describing the SCSI subsystem in the lk 2.4 series. Two upper level
60 Traditionally an LLD for the SCSI subsystem has been at least two files in
86 An LLD interfaces to the SCSI subsystem several ways:
125 from the SCSI subsystem. Hosts can be introduced as early as driver
342 struct tags. Both can be still found in the SCSI subsystem, but
960 * Notes: The SCSI subsystem uses a "trickle down" ioctl model.
996 * support can now be configured out of the scsi subsystem.
1374 In the 2.4 series the SCSI subsystem configuration descriptions were
[all …]
Ddpti.txt33 * V2.0 Rewrite of driver. Re-architectured based on i2o subsystem.
/linux-4.1.27/Documentation/power/powercap/
Dpowercap.txt58 ?   ?   ??? subsystem -> ../../../../../../class/power_cap
75 ?   ?   ??? subsystem -> ../../../../../../class/power_cap
84 ?   ??? subsystem -> ../../../../../class/power_cap
111 ?   ?   ??? subsystem -> ../../../../../../class/power_cap
128 ?   ?   ??? subsystem -> ../../../../../../class/power_cap
137 ?   ??? subsystem -> ../../../../../class/power_cap
142 ??? subsystem -> ../../../../class/power_cap
/linux-4.1.27/Documentation/devicetree/bindings/arm/omap/
Dmpu.txt1 * TI - MPU (Main Processor Unit) subsystem
3 The MPU subsystem contain one or several ARM cores
Diva.txt1 * TI - IVA (Imaging and Video Accelerator) subsystem
/linux-4.1.27/Documentation/devicetree/bindings/clock/
Dmarvell,mmp2.txt3 The MMP2 clock subsystem generates and supplies clock to various
11 - reg: physical base address of the clock subsystem and length of memory mapped
Dmarvell,pxa168.txt3 The PXA168 clock subsystem generates and supplies clock to various
11 - reg: physical base address of the clock subsystem and length of memory mapped
Dmarvell,pxa910.txt3 The PXA910 clock subsystem generates and supplies clock to various
11 - reg: physical base address of the clock subsystem and length of memory mapped
/linux-4.1.27/Documentation/leds/
Dleds-blinkm.txt22 brightness device max_brightness power subsystem trigger uevent
25 brightness device max_brightness power subsystem trigger uevent
28 brightness device max_brightness power subsystem trigger uevent
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.
Dleds-class.txt6 handled by the input subsystem and the led class is *not* needed.
74 delay_off parameters to the leds subsystem.
87 rest of the LED subsystem can be modular.
/linux-4.1.27/arch/arm/mach-sa1100/
Dbadge4.c264 void badge4_set_5V(unsigned subsystem, int on) in badge4_set_5V() argument
274 badge4_5V_bitmap |= subsystem; in badge4_set_5V()
276 badge4_5V_bitmap &= ~subsystem; in badge4_set_5V()
/linux-4.1.27/Documentation/networking/
Dnfc.txt1 Linux NFC subsystem
4 The Near Field Communication (NFC) subsystem is required to standardize the
13 The NFC subsystem is responsible for:
18 The subsystem is divided in some parts. The 'core' is responsible for
56 When registering on the NFC subsystem, the device driver must inform the core
/linux-4.1.27/drivers/media/dvb-core/
DKconfig12 increases the memory consumption of the DVB subsystem even
23 If you say Y here, the DVB subsystem will use dynamic minor
/linux-4.1.27/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:
241 To clear the filters for all events in a subsystem, write a '0' to the
242 subsystem's filter file.
247 For convenience, filters for every event in a subsystem can be set or
249 at the root of the subsystem. Note however, that if a filter for any
250 event within the subsystem lacks a field specified in the subsystem
[all …]
/linux-4.1.27/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,
Dbt8xx.txt81 2c) Probing the cards with broken PCI subsystem ID
84 reason. The cards do not have correct PCI subsystem ID. But we can force
85 probing the cards with broken PCI subsystem ID
Dreadme.txt1 Linux Digital Video Broadcast (DVB) subsystem
/linux-4.1.27/drivers/isdn/gigaset/
DKconfig14 Note: If you build your ISDN subsystem (ISDN_CAPI or ISDN_I4L)
26 the Kernel CAPI subsystem. To use it with the old ISDN4Linux
27 subsystem you'll have to enable the capidrv glue driver.
/linux-4.1.27/
DREPORTING-BUGS23 Identify the problematic subsystem
31 Instead, try to figure out which kernel subsystem is causing the issue,
32 and email that subsystem's maintainer and mailing list. If the subsystem
40 Once you know the subsystem that is causing the issue, you should send a
43 via the subsystem mailing list.
45 To find out where to send an emailed bug report, find your subsystem or
60 If you can't figure out which subsystem caused the issue, you should file
/linux-4.1.27/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.
/linux-4.1.27/Documentation/devicetree/bindings/gpu/
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
103 must be a child of sti-display-subsystem
176 sti-display-subsystem {
177 compatible = "st,sti-display-subsystem";
/linux-4.1.27/Documentation/power/
Druntime_pm.txt48 are executed by the PM core for the device's subsystem that may be either of
61 If the subsystem chosen by applying the above rules doesn't provide the relevant
69 are referred to as subsystem-level callbacks in what follows.
80 The subsystem-level suspend callback, if present, is _entirely_ _responsible_
84 callback in a device driver as long as the subsystem-level suspend callback
87 * Once the subsystem-level suspend callback (or the driver suspend callback,
115 The subsystem-level resume callback, if present, is _entirely_ _responsible_ for
119 callback in a device driver as long as the subsystem-level resume callback knows
122 * Once the subsystem-level resume callback (or the driver resume callback, if
134 The idle callback (a subsystem-level one, if present, or the driver one) is
[all …]
Dpci.txt271 Specifically, the pm field of the PCI subsystem's struct bus_type object,
325 The PCI subsystem's first task related to device power management is to
351 The PCI subsystem plays a vital role in the runtime power management of PCI
354 Namely, it provides subsystem-level callbacks:
377 system-dependent and is determined by the PCI subsystem on the basis of the
380 PCI subsystem can use the platform firmware as well as the device's native PCI
385 low-power state. The driver ought to leave these tasks to the PCI subsystem
403 a notification for the PCI subsystem after the source device has been
413 however, the PCI subsystem doesn't really know if the device really can be
421 in a specific way and the PM core executes subsystem-level power management
[all …]
Dsuspend-and-interrupts.txt41 The IRQF_NO_SUSPEND flag is used to indicate that to the IRQ subsystem when
73 The IRQ subsystem provides two helper functions to be used by device drivers for
103 IRQ subsystem to trigger a system wakeup.
Ddevices.txt54 appropriate subsystem (bus type, device type or device class) driver and
87 Device power management operations, at the subsystem level as well as at the
142 write subsystem-level drivers; most driver code is a "device driver" that builds
208 bus type (or generally subsystem) code using pm_runtime_allow() or
307 If the subsystem callback chosen for execution is not present, the PM core will
608 analogous to the subsystem-level and device driver callbacks that are executed
610 subsystem-level callbacks. Specifically, if a device's pm_domain pointer is
612 executed instead of its subsystem's (e.g. bus type's) ->suspend() callback and
615 precedence over the callbacks provided by the device's subsystem (e.g. bus
621 support for power domains into subsystem-level callbacks, for example by
[all …]
/linux-4.1.27/net/rfkill/
DKconfig2 # RF switch subsystem configuration
5 tristate "RF switch subsystem support"
/linux-4.1.27/Documentation/devicetree/bindings/net/
Dkeystone-netcp.txt25 NetCP subsystem(10G or 1G)
47 NetCP subsystem properties:
50 - clocks: phandle to the reference clocks for the subsystem.
77 - switch subsystem registers
83 index #0 - switch subsystem registers
88 index #0 - switch subsystem registers
/linux-4.1.27/drivers/isdn/
DKconfig40 supported by the new CAPI subsystem yet.
45 tristate "CAPI 2.0 subsystem"
57 you have an ISDN adapter supported by the CAPI subsystem.
/linux-4.1.27/drivers/staging/iio/
DTODO18 - touchscreen controller (input subsystem related device)
20 - battery voltage monitor (power subsystem related device)
63 subsystem. Current approach is abusing purpose of RTC.
DKconfig2 # Industrial I/O subsystem configuration
/linux-4.1.27/Documentation/filesystems/
Dquota.txt2 Quota subsystem
5 Quota subsystem allows system administrator to set limits on used space and
24 quota subsystem traditionally printed a message to the controlling terminal of
Dsysfs-pci.txt45 subsystem_device PCI subsystem device (ascii, ro)
46 subsystem_vendor PCI subsystem vendor (ascii, ro)
/linux-4.1.27/Documentation/devicetree/bindings/phy/
Dphy-bindings.txt2 information about PHY subsystem refer to Documentation/phy.txt
37 phys : the phandle for the PHY device (used by the PHY subsystem)
/linux-4.1.27/arch/arm/boot/dts/
Dimx6dl.dtsi103 display-subsystem {
104 compatible = "fsl,imx-display-subsystem";
Dstih407.dtsi26 sti-display-subsystem {
27 compatible = "st,sti-display-subsystem";
Dimx6q.dtsi224 display-subsystem {
225 compatible = "fsl,imx-display-subsystem";
Dstih410.dtsi97 sti-display-subsystem {
98 compatible = "st,sti-display-subsystem";
/linux-4.1.27/security/integrity/
DKconfig3 bool "Integrity subsystem"
7 This option enables the integrity subsystem, which is comprised
/linux-4.1.27/arch/cris/arch-v32/mm/
Dmmu.S37 ; Bus fault handler. Extracts relevant information and calls mm subsystem
60 ; 1. PMD and PTE exists in mm subsystem but not in TLB
177 8: ; PMD missing, let the mm subsystem fix it up.
179 9: ; PTE missing, let the mm subsystem fix it up.
/linux-4.1.27/tools/thermal/tmon/
DREADME1 TMON - A Monitoring and Testing Tool for Linux kernel thermal subsystem
22 complex thermal subsystem.
/linux-4.1.27/Documentation/vm/
Dfrontswap.txt165 Whenever the swap subsystem is readying a page to write to a swap
179 When the swap subsystem needs to swap-in a page (swap_readpage()),
195 No. First, the existing swap subsystem doesn't allow for any kind of
198 rewritten, the existing swap subsystem uses the block I/O layer which
200 addressable. Frontswap barely touches the existing swap subsystem,
201 and works around the constraints of the block I/O subsystem to provide
218 and/or the block I/O subsystem. That said, only the initial "store"
254 swap subsystem then writes the new data to the read swap device,
259 When the (non-frontswap) swap subsystem swaps out a page to a real
263 routine allows code outside of the swap subsystem to force pages out
[all …]
Dnuma69 subsystem, complete with its own free page lists, in-use page lists, usage
131 a subsystem allocates per CPU memory resources, for example.
136 the node id returned. When such an allocation fails, the requesting subsystem
138 example of this. Or, the subsystem may choose to disable or not to enable
139 itself on allocation failure. The kernel profiling subsystem is an example of
Dremap_file_pages.txt9 code in kernel virtual memory subsystem including hot paths. Also to get
Dzswap.txt21 impact to the guest workload and guests sharing the I/O subsystem
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-class-rfkill3 For details to this subsystem look at Documentation/rfkill.txt.
13 Description: The rfkill class subsystem folder.
/linux-4.1.27/net/decnet/
DREADME4 The documentation for this kernel subsystem is available in the
/linux-4.1.27/sound/soc/xtensa/
DKconfig7 the drivers for the rest of XTFPGA audio subsystem.
/linux-4.1.27/drivers/staging/gs_fpgaboot/
DTODO7 And please CC to "Staging subsystem" mail list <devel@driverdev.osuosl.org> too.
/linux-4.1.27/net/netlabel/
DKconfig6 bool "NetLabel subsystem support"
/linux-4.1.27/Documentation/power/regulator/
Dmachine.txt5 initialisation code to configure the regulator subsystem.
59 name is provided then the subsystem will choose one.
/linux-4.1.27/Documentation/sound/alsa/soc/
Dpops_clicks.txt5 of components within the audio subsystem. This is noticeable on PCs when an
10 because the components within the subsystem are being dynamically powered
Dmachine.txt10 the audio subsystem with the kernel as a platform device and is represented by
85 audio power map of the audio subsystem. This allows for automatic power up/down
Ddapm.txt9 subsystem at all times. It is independent of other kernel PM and as
19 audio subsystem, this includes internal codec power blocks and machine
33 3. Path domain - audio subsystem signal paths
117 audio paths within the audio subsystem. They have the following form:-
186 subsystem individually with a call to snd_soc_dapm_new_control().
Dclocking.txt11 Every audio subsystem is driven by a master clock (sometimes referred to as MCLK
/linux-4.1.27/drivers/iio/
DKconfig2 # Industrial I/O subsystem configuration
9 The industrial I/O subsystem provides a unified framework for
/linux-4.1.27/drivers/staging/lustre/include/linux/libcfs/
Dlibcfs_debug.h204 static inline int cfs_cdebug_show(unsigned int mask, unsigned int subsystem) in cfs_cdebug_show() argument
207 ((libcfs_debug & mask) && (libcfs_subsystem_debug & subsystem)); in cfs_cdebug_show()
/linux-4.1.27/Documentation/devicetree/bindings/gpio/
Dpl061-gpio.txt10 - gpio-ranges : Interaction with the PINCTRL subsystem.
/linux-4.1.27/Documentation/PCI/
D00-INDEX12 - info on the PCI subsystem for device driver authors
/linux-4.1.27/Documentation/tpm/
Dxen-tpmfront.txt5 This document describes the virtual Trusted Platform Module (vTPM) subsystem for
17 these domains (manager, vTPM, and guest) is trusted, the vTPM subsystem extends
23 This mini-os vTPM subsystem was built on top of the previous vTPM work done by
/linux-4.1.27/arch/arc/
DKconfig.debug12 on the VM subsystem for higher order allocations.
/linux-4.1.27/arch/arm/mach-sa1100/include/mach/
Dbadge4.h74 extern void badge4_set_5V(unsigned subsystem, int on);
/linux-4.1.27/Documentation/netlabel/
Dlsm_interface.txt21 NetLabel subsystem converts the security attributes to and from the correct
33 the administrator has configured the NetLabel subsystem.
/linux-4.1.27/drivers/usb/
DREADME42 ../input/ - This is for any driver that uses the input subsystem,
46 subsystem.
/linux-4.1.27/Documentation/devicetree/
D00-INDEX3 probing. This subsystem is maintained by Grant Likely
/linux-4.1.27/drivers/memstick/
DKconfig2 # MemoryStick subsystem configuration
/linux-4.1.27/Documentation/devicetree/bindings/iio/adc/
Dtwl4030-madc.txt3 The MADC subsystem in the TWL4030 consists of a 10-bit ADC
/linux-4.1.27/net/irda/irnet/
DKconfig8 working PPP subsystem (driver, daemon and config)...
/linux-4.1.27/arch/powerpc/boot/dts/
Damigaone.dts68 subsystem-id = <0>;
69 subsystem-vendor-id = <0>;
/linux-4.1.27/Documentation/development-process/
D2.Process160 inclusion, it should be accepted by a relevant subsystem maintainer -
163 subsystem tree and into the -next trees (described below). When the
173 appropriate subsystem or driver maintainer, you should be persistent
212 who has overall responsibility for the code within that subsystem. These
213 subsystem maintainers are the gatekeepers (in a loose way) for the portion
230 trusts the subsystem maintainers to not send bad patches upstream.
247 The chain of subsystem trees guides the flow of patches into the kernel,
256 the interesting subsystem trees, but that would be a big and error-prone
259 The answer comes in the form of -next trees, where subsystem trees are
262 started). The -mm tree integrates patches from a long list of subsystem
[all …]
D6.Followthrough104 entry into a subsystem maintainer's tree. How that works varies from one
105 subsystem to the next; each maintainer has his or her own way of doing
110 For patches applying to areas for which there is no obvious subsystem tree
115 Inclusion into a subsystem tree can bring a higher level of visibility to a
185 either forward it on to the subsystem maintainer (be sure to include a
D5.Posting68 subsystem tree, though, to facilitate wider testing and review. Depending
140 subsystem name first, followed by the purpose of the patch. For
156 These include subsystem maintainers and reviewers who need to decide
260 - The maintainer(s) of the affected subsystem(s). As described earlier,
283 subsystem maintainers who watch over specific parts of the kernel. Usually
293 patches in the series, and "subsys" is the name of the affected subsystem.
D3.Early-stage126 subsystem list, posting there is often preferable to posting on
128 relevant subsystem and the environment may be more supportive.
136 currently active within the subsystem of interest. Look at who is writing
/linux-4.1.27/Documentation/blockdev/
D00-INDEX16 - information about the parallel port IDE subsystem.
Dmflash.txt16 driver and currently works well under standard IDE subsystem. Actually it's
Dparide.txt36 parallel port IDE subsystem, including:
53 subsystem, is actually structured in three parts. There is a base
88 2. Using the PARIDE subsystem
103 subsystem to try them all for you.
248 # mkd -- a script to create the device special files for the PARIDE subsystem
/linux-4.1.27/drivers/mmc/
DKconfig2 # MMC subsystem configuration
/linux-4.1.27/net/9p/
DKconfig34 Say Y if you want the 9P subsystem to log debug information.
/linux-4.1.27/net/nfc/
DKconfig8 tristate "NFC subsystem support"
/linux-4.1.27/Documentation/sysctl/
Dsunrpc.txt12 flags of the SUN Remote Procedure Call (RPC) subsystem in
/linux-4.1.27/drivers/net/wireless/iwlegacy/
DKconfig20 This driver uses the kernel's mac80211 subsystem.
46 This driver uses the kernel's mac80211 subsystem.
/linux-4.1.27/drivers/devfreq/event/
DKconfig12 may be used by devfreq governor and other subsystem.
/linux-4.1.27/Documentation/devicetree/bindings/input/
Dgpio-keys-polled.txt9 subsystem.
Dgpio-keys.txt8 subsystem.
Drotary-encoder.txt7 - linux,axis: the input subsystem axis to map to this rotary encoder.
Dbrcm,bcm-keypad.txt59 subsystem (optional).
/linux-4.1.27/tools/perf/Documentation/
Dperf.txt32 Performance counters for Linux are a new kernel-based subsystem
Dperf-mem.txt24 queueing delays in addition to the memory subsystem latency.
/linux-4.1.27/Documentation/ABI/obsolete/
Dsysfs-class-rfkill3 For details to this subsystem look at Documentation/rfkill.txt.
/linux-4.1.27/kernel/trace/
Dtrace_events.c456 __get_system(dir->subsystem); in __get_system_dir()
463 WARN_ON_ONCE(system_refcount(dir->subsystem) == 1 && dir->ref_count != 1); in __put_system_dir()
465 __put_system(dir->subsystem); in __put_system_dir()
833 struct event_subsystem *system = dir->subsystem; in system_enable_read()
878 struct event_subsystem *system = dir->subsystem; in system_enable_write()
1152 system = dir->subsystem; in subsystem_open()
1227 if (dir->subsystem) in subsystem_release()
1240 struct event_subsystem *system = dir->subsystem; in subsystem_filter_read()
1509 system = dir->subsystem; in event_subsystem_dir()
1547 dir->subsystem = system; in event_subsystem_dir()
[all …]
/linux-4.1.27/fs/sysfs/
DKconfig19 sysfs is currently used by the block subsystem to mount the root
/linux-4.1.27/Documentation/devicetree/bindings/usb/
Dkeystone-usb.txt9 - reg : Address and length of the register set for the USB subsystem on
/linux-4.1.27/drivers/staging/lustre/lnet/
DKconfig2 tristate "Lustre networking subsystem"
/linux-4.1.27/Documentation/misc-devices/mei/
Dmei-client-bus.txt15 for the various MEI features as a stand alone entities found in their respective subsystem.
138 /* Hook to the NFC subsystem */
/linux-4.1.27/net/irda/
DKconfig7 tristate "IrDA (infrared) subsystem support"
86 Say Y here if you want the IrDA subsystem to write debug information
/linux-4.1.27/kernel/time/
DKconfig2 # Timer subsystem related configuration options
55 menu "Timers subsystem"
163 large a concern as is energy efficiency. The sysidle subsystem
/linux-4.1.27/arch/metag/
DKconfig.debug16 on the VM subsystem for higher order allocations. This option
/linux-4.1.27/Documentation/isdn/
DREADME.fax6 of the ISDN subsystem is capable of the Fax Class 2 commands.
DREADME.audio3 ISDN subsystem for Linux.
7 subsystem is capable of a reduced set of commands to support audio.
DREADME.gigaset50 The driver works with the Kernel CAPI subsystem as well as the old
51 ISDN4Linux subsystem, so it can be used with any software which is able
125 character device node; access from the ISDN subsystem is blocked.
126 If cmd==0, the device is set to be used from the ISDN subsystem and does
178 variant), it registers the device with the legacy ISDN4Linux subsystem
181 for setting up that subsystem. Otherwise you can use some HOWTOs like
D00-INDEX40 - info on the Modular ISDN subsystem (mISDN)
DREADME.x2533 in the Linux source tree since version 2.1.16. The isdn subsystem might be
42 from the ISDN subsystem options when you configure your kernel for
49 from the isdn subsystem's configuration menu.
/linux-4.1.27/Documentation/devicetree/bindings/media/
Dsamsung-fimc.txt4 The S5P/Exynos SoC Camera subsystem comprises of multiple sub-devices
9 also includes common properties of the whole subsystem not really specific to
31 clocks registered by the camera subsystem corresponding to CAM_A_CLKOUT,
Dexynos4-fimc-is.txt3 The FIMC-IS is a subsystem for processing image signal from an image sensor.
/linux-4.1.27/Documentation/sound/oss/
Doss-parameters.txt22 dmasound= [HW,OSS] Sound subsystem buffers
/linux-4.1.27/Documentation/devicetree/bindings/leds/
Dleds-pwm.txt12 - pwm-names : (optional) Name to be used by the PWM subsystem for the PWM device
/linux-4.1.27/Documentation/arm/
D00-INDEX8 - ARM Interrupt subsystem documentation
/linux-4.1.27/Documentation/spi/
Dspi-sc18is60216 kernel's SPI core subsystem.
Dspi-summary530 that a message is coming in soon, so the subsystem requests the
541 The subsystem calls the driver to transfer a single message while
544 spi_finalize_current_message() so the subsystem can issue the next
549 The subsystem calls the driver to transfer a single transfer while
552 spi_finalize_current_transfer() so the subsystem can issue the next
554 are mutually exclusive; when both are set, the generic subsystem does
577 SPI subsystem, just implement the queued methods specified above. Using
582 Unless the queueing mechanism in the SPI subsystem is selected, the bulk
Dspi-lm70llp14 temperature sensor evaluation board to the kernel's SPI core subsystem.
/linux-4.1.27/drivers/net/ethernet/emulex/benet/
Dbe_cmds.c71 static bool be_cmd_allowed(struct be_adapter *adapter, u8 opcode, u8 subsystem) in be_cmd_allowed() argument
79 subsystem == cmd_priv_map[i].subsystem) in be_cmd_allowed()
159 u8 opcode = 0, subsystem = 0; in be_async_cmd_process() local
163 subsystem = resp_hdr->subsystem; in be_async_cmd_process()
167 subsystem == CMD_SUBSYSTEM_LOWLEVEL) { in be_async_cmd_process()
174 subsystem == CMD_SUBSYSTEM_COMMON) { in be_async_cmd_process()
182 subsystem == CMD_SUBSYSTEM_ETH && in be_async_cmd_process()
190 subsystem == CMD_SUBSYSTEM_COMMON) { in be_async_cmd_process()
209 u8 opcode = 0, subsystem = 0; in be_mcc_compl_process() local
221 subsystem = resp_hdr->subsystem; in be_mcc_compl_process()
[all …]
Dbe_cmds.h268 u8 subsystem; /* dword 0 */ member
281 u8 subsystem; /* dword 0 */ member
1397 u8 subsystem; member
1430 u8 subsystem; member
1682 u8 subsystem; member
/linux-4.1.27/sound/pci/ca0106/
Dca0106_main.c160 static uint subsystem[SNDRV_CARDS]; /* Force card subsystem model */ variable
168 module_param_array(subsystem, uint, NULL, 0444);
169 MODULE_PARM_DESC(subsystem, "Force card subsystem model.");
1731 if (subsystem[dev]) { in snd_ca0106_create()
1732 if (c->serial == subsystem[dev]) in snd_ca0106_create()
1738 if (subsystem[dev]) { in snd_ca0106_create()
1741 c->name, chip->serial, subsystem[dev]); in snd_ca0106_create()
/linux-4.1.27/Documentation/hid/
Duhid.txt1 UHID - User-space I/O driver support for HID subsystem
22 device with the HID subsystem, then you need to open /dev/uhid once for each
56 UHID_OPEN events without an UHID_CLOSE event. The HID subsystem performs
61 If you want to send data on the interrupt channel to the HID subsystem, you send
/linux-4.1.27/drivers/staging/android/
DKconfig10 The ashmem subsystem is a new shared memory allocator, similar to
/linux-4.1.27/Documentation/video4linux/
Dsoc-camera.txt18 Purpose of the soc-camera subsystem
21 The soc-camera subsystem initially provided a unified API between camera host
31 The subsystem has been designed to support multiple camera host interfaces and
DREADME.cx8841 cx8800[0]: subsystem: 0070:3400, board: Hauppauge WinTV \
/linux-4.1.27/arch/alpha/lib/
Dev6-memset.S160 wh64 ($4) # L1 : memory subsystem write hint
337 wh64 ($4) # L1 : memory subsystem write hint
524 wh64 ($4) # L1 : memory subsystem write hint
Dev6-clear_user.S151 wh64 ($3) # .. .. .. L1 : memory subsystem hint
Dev6-memcpy.S84 wh64 ($7) # L1 : memory subsystem hint: 64 bytes at
/linux-4.1.27/Documentation/mtd/
Dspi-nor.txt13 find the right LUT sequence. Unfortunately, the SPI subsystem has no notion of
/linux-4.1.27/Documentation/i2c/
Dold-module-parameters11 With the conversion of the i2c subsystem to the standard device driver
/linux-4.1.27/drivers/fmc/
DKconfig11 This kernel subsystem supports the matching between carrier
/linux-4.1.27/Documentation/hwmon/
Dsubmitting-patches5 drivers for the hwmon subsystem. Following these suggestions will greatly
93 with the hwmon subsystem.
/linux-4.1.27/drivers/i2c/muxes/
DKconfig56 multiplexer that uses the pinctrl subsystem, i.e. pin multiplexing.
/linux-4.1.27/drivers/net/wireless/ath/ath5k/
DKconfig20 This driver uses the kernel's mac80211 subsystem.
/linux-4.1.27/kernel/irq/
DKconfig1 menu "IRQ subsystem"
/linux-4.1.27/Documentation/gpio/
Dgpio-legacy.txt274 For GPIOs that use pins known to the pinctrl subsystem, that subsystem should
277 pinctrl_free_gpio(). The pinctrl subsystem allows a pinctrl_request_gpio()
292 the pinctrl subsystem's mapping table, so that GPIO users need not be aware
442 GPIO controllers and the pinctrl subsystem
446 subsystem, in the sense that the pins can be used by other functions
456 But how does the pin control subsystem cross-correlate the GPIO
464 While the pin allocation is totally managed by the pinctrl subsystem,
469 the pin ctrl subsystem before it will call 'pinctrl_request_gpio' in order
470 to request the corresponding pin to be prepared by the pinctrl subsystem
474 subsystem. There are two ways of doing it currently: with or without DT.
/linux-4.1.27/Documentation/ja_JP/
DSubmittingPatches471 Subject: [PATCH 001/123] subsystem: summary phrase
698 Greg Kroah-Hartman, "How to piss off a kernel subsystem maintainer".
/linux-4.1.27/drivers/scsi/be2iscsi/
Dbe_cmds.c231 mbx_hdr->subsystem, in beiscsi_mccq_compl()
339 hdr->subsystem, hdr->opcode, in be_mcc_compl_process()
759 u8 subsystem, u8 opcode, int cmd_len) in be_cmd_hdr_prepare() argument
762 req_hdr->subsystem = subsystem; in be_cmd_hdr_prepare()
/linux-4.1.27/drivers/staging/unisys/common-spar/include/channels/
Ddiagchannel.h170 u8 subsystem; member
/linux-4.1.27/net/can/
DKconfig7 tristate "CAN bus subsystem support"
/linux-4.1.27/drivers/staging/iio/Documentation/
Dinkernel.txt3 The IIO subsystem can act as a layer under other elements of the kernel
Doverview.txt3 The Industrial I/O subsystem is intended to provide support for devices
Ddevice.txt5 subsystem.
/linux-4.1.27/drivers/infiniband/
DKconfig47 On demand paging support for the InfiniBand subsystem.
/linux-4.1.27/Documentation/laptops/
Dsony-laptop.txt14 reported both through the ACPI subsystem as acpi events and through the INPUT
15 subsystem. See the logs of /proc/bus/input/devices to find out what those
/linux-4.1.27/fs/quota/
DKconfig44 If you say Y here, quota subsystem will perform some additional
/linux-4.1.27/Documentation/input/
Dcma3000_d0x.txt34 Driver reports acceleration data through input subsystem. It generates ABS_MISC
/linux-4.1.27/Documentation/devicetree/bindings/mfd/
Domap-usb-host.txt66 The OMAP HS USB Host subsystem contains EHCI and OHCI controllers.
/linux-4.1.27/Documentation/devicetree/bindings/
Dsubmitting-patches.txt50 2) For driver (not subsystem) bindings: If you are comfortable with the
/linux-4.1.27/drivers/s390/block/
DKconfig29 S/390s channel subsystem commands. This is necessary for running
/linux-4.1.27/Documentation/sound/alsa/
Dhda_codec.txt38 needs to check the PCI subsystem IDs, so on. For non-PCI system, it
240 When the codec id and codec subsystem id match with the given id and
311 as a module parameter, and PCI subsystem IDs. If the matching entry
/linux-4.1.27/Documentation/misc-devices/
Dc2port.txt54 dev_id flash_blocks_num flash_size subsystem/
/linux-4.1.27/Documentation/fb/
Dsstfb.txt63 as the console subsystem automagicaly binds ttys to the fb.
155 console subsystem can cause some troubles, specifically, you should
/linux-4.1.27/Documentation/driver-model/
Ddesign-patterns.txt6 It is likely that subsystem maintainers will ask driver developers to
/linux-4.1.27/Documentation/devicetree/bindings/mmc/
Dsdhci-st.txt10 subsystem (mmcss) inside the FlashSS (available in STiH407 SoC
/linux-4.1.27/drivers/usb/core/
DKconfig37 If you say Y here, the USB subsystem will use dynamic minor
/linux-4.1.27/arch/sh/
DKconfig.debug38 on the VM subsystem for higher order allocations. This option
/linux-4.1.27/arch/cris/arch-v10/kernel/
Dentry.S338 ;; a real fault we let the mm subsystem handle it.
387 2: ; PMD or PTE missing, let the mm subsystem fix it up.
391 ; Ok, not that easy, pass it on to the mm subsystem
/linux-4.1.27/drivers/pcmcia/
DKconfig2 # PCCARD (PCMCIA/CardBus) bus subsystem configuration
47 subsystem, instead of relying on cardmgr from pcmcia-cs to do so.
/linux-4.1.27/Documentation/ptp/
Dptp.txt24 - Synchronization of the Linux system time via the PPS subsystem
/linux-4.1.27/Documentation/x86/x86_64/
Dmachinecheck9 a hardware subsystem) and subevents in a bank. The exact meaning
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dsamsung-i2s.txt28 i2s0 uses some base clks from CMU and some are from audio subsystem internal
/linux-4.1.27/drivers/net/ethernet/ti/
DKconfig102 tristate "TI Keystone NETCP Ethernet subsystem Support"
/linux-4.1.27/sound/
DKconfig134 sound subsystem and other function drivers completely unrelated to
/linux-4.1.27/drivers/clk/
DKconfig31 Supports the clocking subsystem of the WM831x/2x series of
/linux-4.1.27/Documentation/video4linux/bttv/
DREADME49 only bt878-based cards can have a subsystem ID (which does not mean

12