Home
last modified time | relevance | path

Searched refs:via (Results 1 – 200 of 921) sorted by relevance

12345

/linux-4.4.14/drivers/macintosh/
Dvia-cuda.c31 static volatile unsigned char __iomem *via; variable
126 via = via1; in find_via_cuda()
132 via = NULL; in find_via_cuda()
167 via = ioremap(taddr, 0x2000); in find_via_cuda()
168 if (via == NULL) { in find_via_cuda()
179 via = NULL; in find_via_cuda()
186 out_8(&via[IFR], 0x7f); /* clear interrupts by writing 1s */ in find_via_cuda()
187 out_8(&via[IER], IER_SET|SR_INT); /* enable interrupt from SR */ in find_via_cuda()
205 if (via == NULL) in via_cuda_start()
243 if (via == NULL) in cuda_probe()
[all …]
Dvia-maciisi.c29 static volatile unsigned char *via; variable
107 via = via1; in maciisi_probe()
116 if (via == NULL) in maciisi_init()
121 via = NULL; in maciisi_init()
139 int status = via[B] & (TIP|TREQ); in maciisi_stfu()
149 via[ACR] &= ~SR_OUT; in maciisi_stfu()
150 via[IER] = IER_CLR | SR_INT; in maciisi_stfu()
154 status = via[B] & (TIP|TREQ); in maciisi_stfu()
158 via[B] |= TIP; in maciisi_stfu()
164 while (!(via[IFR] & SR_INT) && poll_timeout-- > 0) in maciisi_stfu()
[all …]
Dvia-macii.c38 static volatile unsigned char *via; variable
144 via = via1; in macii_probe()
177 via[DIRB] = (via[DIRB] | ST_EVEN | ST_ODD) & ~CTLR_IRQ; in macii_init_via()
180 via[B] |= ST_IDLE; in macii_init_via()
181 last_status = via[B] & (ST_MASK|CTLR_IRQ); in macii_init_via()
184 via[ACR] = (via[ACR] & ~SR_CTRL) | SR_EXT; in macii_init_via()
187 x = via[SR]; in macii_init_via()
360 via[ACR] |= SR_OUT; in macii_start()
362 via[SR] = req->data[1]; in macii_start()
364 via[B] = (via[B] & ~ST_MASK) | ST_CMD; in macii_start()
[all …]
Dvia-pmu.c78 static volatile unsigned char __iomem *via; variable
276 if (via != 0) in find_via_pmu()
341 via = ioremap(taddr, 0x2000); in find_via_pmu()
342 if (via == NULL) { in find_via_pmu()
347 out_8(&via[IER], IER_CLR | 0x7f); /* disable all intrs */ in find_via_pmu()
348 out_8(&via[IFR], 0x7f); /* clear IFR */ in find_via_pmu()
363 iounmap(via); in find_via_pmu()
364 via = NULL; in find_via_pmu()
438 out_8(&via[IER], IER_SET | SR_INT | CB1_INT); in via_pmu_start()
533 out_8(&via[B], via[B] | TREQ); /* negate TREQ */ in init_pmu()
[all …]
DMakefile14 obj-$(CONFIG_ADB_PMU) += via-pmu.o via-pmu-event.o
15 obj-$(CONFIG_ADB_PMU_LED) += via-pmu-led.o
16 obj-$(CONFIG_PMAC_BACKLIGHT) += via-pmu-backlight.o
17 obj-$(CONFIG_ADB_CUDA) += via-cuda.o
22 obj-$(CONFIG_ADB_MACII) += via-macii.o
23 obj-$(CONFIG_ADB_MACIISI) += via-maciisi.o
25 obj-$(CONFIG_ADB_PMU68K) += via-pmu68k.o
/linux-4.4.14/arch/arm/boot/dts/
Dwm8505.dtsi41 compatible = "via,vt8500-intc";
49 compatible = "via,vt8500-intc";
66 compatible = "via,vt8500-pmc";
86 compatible = "via,vt8500-pll-clock";
93 compatible = "via,vt8500-pll-clock";
100 compatible = "via,vt8500-pll-clock";
107 compatible = "via,vt8500-pll-clock";
114 compatible = "via,vt8500-device-clock";
121 compatible = "via,vt8500-device-clock";
128 compatible = "via,vt8500-device-clock";
[all …]
Dvt8500.dtsi12 compatible = "via,vt8500";
39 compatible = "via,vt8500-intc";
46 compatible = "via,vt8500-pinctrl";
55 compatible = "via,vt8500-pmc";
70 compatible = "via,vt8500-device-clock";
78 compatible = "via,vt8500-device-clock";
86 compatible = "via,vt8500-device-clock";
94 compatible = "via,vt8500-device-clock";
103 compatible = "via,vt8500-timer";
109 compatible = "via,vt8500-ehci";
[all …]
Dwm8750.dtsi43 compatible = "via,vt8500-intc";
51 compatible = "via,vt8500-intc";
68 compatible = "via,vt8500-pmc";
124 compatible = "via,vt8500-device-clock";
131 compatible = "via,vt8500-device-clock";
138 compatible = "via,vt8500-device-clock";
145 compatible = "via,vt8500-device-clock";
152 compatible = "via,vt8500-device-clock";
160 compatible = "via,vt8500-device-clock";
168 compatible = "via,vt8500-device-clock";
[all …]
Dwm8850.dtsi40 compatible = "via,vt8500-intc";
48 compatible = "via,vt8500-intc";
65 compatible = "via,vt8500-pmc";
135 compatible = "via,vt8500-device-clock";
142 compatible = "via,vt8500-device-clock";
149 compatible = "via,vt8500-device-clock";
156 compatible = "via,vt8500-device-clock";
163 compatible = "via,vt8500-device-clock";
171 compatible = "via,vt8500-device-clock";
179 compatible = "via,vt8500-device-clock";
[all …]
Dwm8650.dtsi37 compatible = "via,vt8500-intc";
45 compatible = "via,vt8500-intc";
62 compatible = "via,vt8500-pmc";
118 compatible = "via,vt8500-device-clock";
125 compatible = "via,vt8500-device-clock";
132 compatible = "via,vt8500-device-clock";
139 compatible = "via,vt8500-device-clock";
146 compatible = "via,vt8500-device-clock";
154 compatible = "via,vt8500-device-clock";
162 compatible = "via,vt8500-device-clock";
[all …]
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-tty29 These sysfs values expose the TIOCGSERIAL interface via
30 sysfs rather than via ioctls.
38 These sysfs values expose the TIOCGSERIAL interface via
39 sysfs rather than via ioctls.
47 These sysfs values expose the TIOCGSERIAL interface via
48 sysfs rather than via ioctls.
56 These sysfs values expose the TIOCGSERIAL interface via
57 sysfs rather than via ioctls.
65 These sysfs values expose the TIOCGSERIAL interface via
66 sysfs rather than via ioctls.
[all …]
Dsysfs-driver-hid-prodikeys6 Allows control (via software) the midi channel to which
15 Allows control (via software) the sustain duration of a
26 The octave can be shifted via software up/down 2 octaves.
Dsysfs-platform-twl4030-usb8 Changes are notified via select/poll.
Dsysfs-platform-kim21 locally and also sent across to the WL128x via a HCI-VS
43 configuring baud and install line discipline via this sysfs
Dsysfs-firmware-memmap7 in the kernel resource tree and exposed to userspace via
13 just because the user overwrites that memory map via command
Dsysfs-class-mic.txt133 access the card OS log buffer via debugfs. When read, this entry
147 access the card OS log buffer via debugfs. When read, this entry
160 via a heartbeat mechanism (see the description of
164 the responsibility of user space to detect card crashes via
/linux-4.4.14/sound/pci/au88x0/
Dau88x0.c58 static void vortex_fix_agp_bridge(struct pci_dev *via) in vortex_fix_agp_bridge() argument
69 if (!(rc = pci_read_config_byte(via, 0x42, &value)) in vortex_fix_agp_bridge()
71 || !(rc = pci_write_config_byte(via, 0x42, value | 0x10)))) { in vortex_fix_agp_bridge()
72 dev_info(&via->dev, "bridge config is 0x%x\n", value | 0x10); in vortex_fix_agp_bridge()
74 dev_warn(&via->dev, in vortex_fix_agp_bridge()
81 struct pci_dev *via = NULL; in snd_vortex_workaround() local
86 via = pci_get_device(PCI_VENDOR_ID_VIA, in snd_vortex_workaround()
89 if (via == NULL) { in snd_vortex_workaround()
90 via = pci_get_device(PCI_VENDOR_ID_VIA, in snd_vortex_workaround()
93 if (via == NULL) in snd_vortex_workaround()
[all …]
/linux-4.4.14/arch/powerpc/platforms/powermac/
Dtime.c261 volatile unsigned char __iomem *via; in via_calibrate_decr() local
276 via = ioremap(rsrc.start, resource_size(&rsrc)); in via_calibrate_decr()
277 if (via == NULL) { in via_calibrate_decr()
283 out_8(&via[ACR], (via[ACR] & ~T1MODE) | T1MODE_CONT); in via_calibrate_decr()
285 out_8(&via[T1CH], 2); in via_calibrate_decr()
287 out_8(&via[T1LL], count); in via_calibrate_decr()
288 out_8(&via[T1LH], count >> 8); in via_calibrate_decr()
290 while ((in_8(&via[IFR]) & T1_INT) == 0) in via_calibrate_decr()
294 in_8(&via[T1CL]); in via_calibrate_decr()
295 while ((in_8(&via[IFR]) & T1_INT) == 0) in via_calibrate_decr()
[all …]
/linux-4.4.14/arch/arm/mach-spear/
DKconfig33 Supports ST SPEAr1310 machine configured via the device-tree
40 Supports ST SPEAr1340 machine configured via the device-tree
59 Supports ST SPEAr300 machine configured via the device-tree
65 Supports ST SPEAr310 machine configured via the device-tree
71 Supports ST SPEAr320 machine configured via the device-tree
87 Supports ST SPEAr600 boards configured via the device-tree
/linux-4.4.14/arch/arm/
DKconfig.debug6 bool "Export kernel pagetable layout to userspace via debugfs"
98 bool "Kernel low-level debugging messages via Alpine UART0"
106 bool "Kernel low-level debugging via asm9260 UART"
155 bool "Kernel low-level debugging messages via BCM KONA UART"
189 bool "Kernel low-level debugging messages via UART1"
196 bool "Kernel low-level debugging messages via UART2"
252 bool "Kernel low-level debugging messages via footbridge serial port"
259 bool "Kernel low-level debugging messages via Digicolor UA0"
266 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
289 bool "Kernel low-level debugging messages via Highbank UART"
[all …]
/linux-4.4.14/Documentation/ABI/obsolete/
Dsysfs-block-zram7 Now accessible via zram<id>/stat node.
15 Now accessible via zram<id>/stat node.
23 Now accessible via zram<id>/io_stat node.
31 Now accessible via zram<id>/io_stat node.
39 Now accessible via zram<id>/io_stat node.
53 Now accessible via zram<id>/io_stat node.
62 Now accessible via zram<id>/mm_stat node.
72 Now accessible via zram<id>/mm_stat node.
82 Now accessible via zram<id>/mm_stat node.
94 Now accessible via zram<id>/mm_stat node.
/linux-4.4.14/drivers/misc/lis3lv02d/
DKconfig12 via SPI. The accelerometer data is readable via
29 via I2C. The accelerometer data is readable via
/linux-4.4.14/drivers/staging/iio/light/
DKconfig16 Data from sensor is accessible via sysfs.
25 Proximity value via iio. The ISL29028 provides the concurrent sensing
33 Access ALS data via iio, sysfs.
41 Provides iio_events and direct access via sysfs.
/linux-4.4.14/Documentation/hwmon/
Dg76215 done via a userland daemon like fancontrol.
19 fan revolution, ...); Those can be modified via devicetree bindings
43 speed control (open-loop) via pwm1 described below, 2 for
44 automatic fan speed control (closed-loop) via fan1_target
55 the fan speed is programmed by setting a value between 0 and 255 via 'pwm1'
58 the chip via 'fan1_target'. In closed-loop mode, the target speed is compared
59 with current speed (available via 'fan1_input') by the device and a feedback
Dlm7328 conversion time via the 'update_interval' sysfs attribute for the
69 'update_interval' via a step function. Reading back the
74 via the following function:
85 feature is exposed via the sysfs attributes.
Dina20928 The INA209 chip is highly configurable both via hardwiring and via
31 This tries to expose most monitoring features of the hardware via
82 via platform data, the driver checks if the calibration register has been
Dds62022 returned via sysfs displays post decimal positions.
24 The thermostat function works as follows: When configured via platform_data
Dg760a18 The fan speed is programmed by setting the period via 'pwm1' of two
25 The measured fan rotation speed returned via 'fan1_input' is derived
Dlm7024 It communicates with a host processor (or microcontroller) via an
30 complement digital temperature (sent via the SIO line), is available in the
Dtmp40149 Exported via sysfs attributes tempX_lowest and tempX_highest.
53 Exported via sysfs attribute temp_reset_history. Writing 1 to this
Dds1621116 support, which is achieved via the R0 and R1 config register bits, where:
129 userspace, via the device 'update_interval' sysfs attribute. This attribute
176 user input, via a step function. Reading back the 'update_interval' value
180 via the following function:
Dina2xx54 The shunt value in micro-ohms can be set via platform data or device tree at
55 compile-time or via the shunt_resistor attribute in sysfs at run-time. Please
Ddme173759 accessible via SMBus, while the SCH311x and SCH5127 only provide access via
158 support the setting of the output frequency via the freq attribute.
162 temperature input. Associating PWM outputs to temperature inputs is done via
165 be retrieved via the zone[1-3]_auto_channels_temp attributes. Each PWM output
169 and low and min can be programmed via pwm[1-3]_auto_point1_pwm and
171 programmed via zone[1-3]_auto_point[1-3]_temp and
Dnct780220 Smart Fan™ speed control is available via pwmX_auto_point attributes.
/linux-4.4.14/Documentation/filesystems/
Ddlmfs.txt3 A minimal DLM userspace interface implemented via a virtual file
47 your lockspace can access. The easiest way to do this is via
62 Users may access dlmfs via standard file system calls, or they can use
77 Lock value blocks can be read and written to a resource via read(2)
78 and write(2) against the fd obtained via your open(2) call. The
89 domain directory. Locking against them is done via the open(2) system
117 access to the resources via dlmfs on your local node only.
120 Exclusive modes via the read(2) system call. It can be written via
Dfiemap.txt67 number of elements in the fiemap_extents[] array should be passed via
69 returned via fm_mapped_extents. If the number of fiemap_extents
134 extent via I/O to the block device will have undefined results.
141 extent data via I/O to the block device while the filesystem is
144 filesystem via the block device under any other circumstances.
203 Flag checking should be done at the beginning of the ->fiemap callback via the
209 set of fiemap flags which the fs understands should be passed via fs_flags. If
Dgfs2-uevents.txt45 recovery via the /sys/fs/gfs2/<fsname>/lock_module/recovery file.
76 line (locktable=) or via fstab. It is used as a filesystem label
83 on the mount command line, or via fstab. It will be either
/linux-4.4.14/drivers/net/ethernet/via/
DMakefile5 obj-$(CONFIG_VIA_RHINE) += via-rhine.o
6 obj-$(CONFIG_VIA_VELOCITY) += via-velocity.o
DKconfig31 will be called via-rhine.
54 will be called via-velocity.
/linux-4.4.14/drivers/gpu/drm/via/
DMakefile6 via-y := via_irq.o via_drv.o via_map.o via_mm.o via_dma.o via_verifier.o via_video.o via_dmablit…
8 obj-$(CONFIG_DRM_VIA) +=via.o
/linux-4.4.14/Documentation/devicetree/bindings/arm/vt8500/
Dvia,vt8500-pmc.txt5 - compatible : "via,vt8500-pmc"
11 compatible = "via,vt8500-pmc";
Dvia,vt8500-timer.txt5 - compatible : "via,vt8500-timer"
12 compatible = "via,vt8500-timer";
/linux-4.4.14/Documentation/devicetree/bindings/rtc/
Dvia,vt8500-rtc.txt5 - compatible : "via,vt8500-rtc"
12 compatible = "via,vt8500-rtc";
/linux-4.4.14/drivers/staging/iio/cdc/
DKconfig11 (ad7150, ad7151, ad7156) Provides direct access via sysfs.
21 (ad7152, ad7153) Provides direct access via sysfs.
31 (AD7745, AD7746, AD7747) Provides direct access via sysfs.
/linux-4.4.14/drivers/staging/iio/resolver/
DKconfig11 to digital converters, ad2s90, provides direct access via sysfs.
23 via sysfs.
34 to digital converters, ad2s1210, provides direct access via sysfs.
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Dvia,vt8500-intc.txt5 - compatible : "via,vt8500-intc"
12 compatible = "via,vt8500-intc";
Dsnps,arc700-intc.txt15 intc accessed via the special ARC AUX register interface, hence "reg" property
Dsnps,archs-intc.txt12 intc accessed via the special ARC AUX register interface, hence "reg" property
/linux-4.4.14/Documentation/sound/alsa/
Dpowersave.txt5 This feature is enabled via Kconfig CONFIG_SND_AC97_POWER_SAVE
14 The time-out for automatic power-off can be specified via power_save
17 power-saving. The default value of timeout is given via
25 adjust the value via sysfs on the fly. For example, to turn on the
DHD-Audio.txt53 read in two ways, either via a LPIB register or via a position-buffer
57 a case, you can change the default method via `position_fix` option.
77 via `bdl_pos_adj` option.
102 It means that the codec response isn't notified via an IRQ. The
111 codec slots via `probe_mask` option. It's a bitmask, and each bit
240 external amplifier. This can be set usually via EAPD verb or a
242 chance via SET_EAPD_BTL verb (0x70c). On others, GPIO pin (mostly
263 When the PCM device is opened via "default" PCM (without pulse-audio
289 to fight against evil, try debugging via hitting the raw HD-audio
318 (one per each codec), and you have a raw access to the device via
[all …]
DCMIPCI.txt50 via alsamixer or somewhat else. When this switch is on, line-in jack
110 The SPDIF playback and capture are done via the third PCM device
128 control via mixer or alsactl ("IEC958" is the official name of
135 You can play via SPDIF even with the first device (hw:0,0),
177 can be toggled via IEC958 playback control, but usually you need to
178 access it via alsa-lib. See alsa-lib documents for more details.
246 The modem is enabled dynamically via a card control switch "Modem".
DVIA82xx-mixer.txt7 with EIO (input/output error) via OSS emulation. This control should be left
/linux-4.4.14/arch/x86/boot/
Dcode16gcc.h4 # This file is added to the assembler via -Wa when compiling 16-bit C code.
5 # This is done this way instead via asm() to make sure gcc does not reorder
/linux-4.4.14/Documentation/trace/
Dintel_th.txt17 via sysfs attributes.
25 debug host via a PTI port,
35 via its "masters" attribute group. More detailed GTH interface
43 buffer, which can later on be read from its device nodes via read() or
48 and collected via sysfs attributes, and device nodes.
63 allocated, are accessible via /dev/intel_th0/msc{0,1}.
Dkprobetrace.txt17 Similar to the events tracer, this doesn't need to be activated via
18 current_tracer. Instead of that, add probe points via
19 /sys/kernel/debug/tracing/kprobe_events, and enable it via
89 You can check the total number of probe hits and probe miss-hits via
113 You can see the format of these events via
154 And you can see the traced information via /sys/kernel/debug/tracing/trace.
Duprobetracer.txt12 Similar to the kprobe-event tracer, this doesn't need to be activated via
13 current_tracer. Instead of that, add probe points via
14 /sys/kernel/debug/tracing/uprobe_events, and enable it via
63 You can check the total number of probe hits and probe miss-hits via
145 And you can see the traced information via /sys/kernel/debug/tracing/trace.
Dstm.txt24 mechanism via configfs, that allows defining rules that map string
65 need to allocate that many channels to themselves (via the
74 stm devices at runtime via a sysfs attribute.
/linux-4.4.14/drivers/video/fbdev/via/
DMakefile9 via-core.o via-gpio.o via_modesetting.o via_clock.o \
/linux-4.4.14/Documentation/w1/slaves/
Dw1_ds28e0416 during memory accesses can optionally be enabled/disabled via the device
18 via the module parameter "w1_strong_pullup".
32 The 2 PIOs of the DS28E04-100 are accessible via the "pio" sysfs file.
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dvia-rhine.txt4 - compatible : Should be "via,vt8500-rhine" for integrated
14 compatible = "via,vt8500-rhine";
Dvia-velocity.txt4 - compatible : Should be "via,velocity-vt6110"
16 compatible = "via,velocity-vt6110";
/linux-4.4.14/drivers/staging/most/Documentation/
Ddriver_usage.txt19 consumer devices via optical or electrical physical layers directly to one
38 to MOST via one the following ways: character devices, ALSA, Networking or
58 Host wants to communicate with hardware via MediaLB.
61 Host wants to communicate with the hardware via I2C.
64 Host wants to communicate with the hardware via USB.
70 configuration via sysfs, buffer management and data forwarding.
89 the driver via the networking subsystem.
93 driver via the V4L subsystem.
97 used to access the driver via the ALSA subsystem.
/linux-4.4.14/Documentation/scsi/
Dhptiop.txt6 For RR44xx Intel IOP based adapters, the controller IOP is accessed via PCI BAR0 and BAR2:
25 For Intel IOP based adapters, the controller IOP is accessed via PCI BAR0:
40 For Marvell not Frey IOP based adapters, the IOP is accessed via PCI BAR0 and BAR1:
58 For Marvell Frey IOP based adapters, the IOP is accessed via PCI BAR0 and BAR1:
84 All queued requests are handled via inbound/outbound queue port.
121 Non-queued requests (reset/flush etc) can be sent via inbound message
129 All queued requests are handled via inbound/outbound list.
160 Non-queued requests (reset communication/reset/flush etc) can be sent via PCIe
/linux-4.4.14/Documentation/filesystems/configfs/
Dconfigfs.txt21 appear in sysfs, allowing userspace to read the attributes via
22 readdir(3)/read(2). It may allow some attributes to be modified via
27 A configfs config_item is created via an explicit userspace operation:
28 mkdir(2). It is destroyed via rmdir(2). The attributes appear at
29 mkdir(2) time, and can be read or modified via read(2) and write(2).
51 An item is created via mkdir(2). The item's attributes will also
65 item cannot be destroyed if any other item has a link to it (via
66 symlink(2)). Links can be removed via unlink(2).
99 That's it. That's all there is. Now the device is configured, via the
151 All users of a config_item should have a reference on it via
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/display/
Dvia,vt8500-fb.txt5 - compatible : "via,vt8500-fb"
16 compatible = "via,vt8500-fb";
/linux-4.4.14/Documentation/devicetree/bindings/pwm/
Dvt8500-pwm.txt4 - compatible: should be "via,vt8500-pwm"
15 compatible = "via,vt8500-pwm";
/linux-4.4.14/drivers/isdn/capi/
DKconfig6 of CAPI messages. This feature can be enabled/disabled via IOCTL for
15 applications via /dev/capi20. Applications should use the
25 established via the usual /dev/capi20 interface to a special tty
/linux-4.4.14/drivers/staging/iio/Documentation/
Doverview.txt15 A typical device falling into this category would be connected via SPI
21 hwmon with simple polled access to device channels via sysfs.
28 event must be accessed via polling.
31 turned on or off (if possible) via sysfs interfaces.
Dring.txt7 implementation to be selected at compile time via Kconfig options.
11 IIO core. Access to the embedding structure is typically done via
/linux-4.4.14/arch/arc/kernel/
Dentry-arcv2.S184 ; Handle special case #1: (Entry via Exception, Return via IRQ)
209 ; Handle special case #2: (Entry via Exception in Delay Slot, Return via IRQ)
213 ; entry was via Exception in DS which got preempted in kernel).
Dentry.S55 ; 1. Any forked task (Reach here via BRne above)
56 ; 2. First ever init task (Reach here via return from JL above)
59 ; a kernel thread which is executed via JL above but always returns
/linux-4.4.14/drivers/staging/iio/frequency/
DKconfig11 AD9832 and AD9835, provides direct access via sysfs.
21 AD9833, AD9834, AD9837 and AD9838, provides direct access via sysfs.
/linux-4.4.14/Documentation/devicetree/bindings/serial/
Dvt8500-uart.txt4 - compatible: should be "via,vt8500-uart" (for VIA/WonderMedia chips up to and
23 compatible = "via,vt8500-uart";
/linux-4.4.14/drivers/misc/cxl/
DKconfig29 coherently attached to a CPU via an MMU. This driver enables
30 userspace programs to access these accelerators via /dev/cxl/afuM.N
/linux-4.4.14/Documentation/input/
Dgpio-tilt.txt1 Driver for tilt-switches connected via GPIOs
4 Generic driver to read data from tilt switches connected via gpios.
31 one axis in 4 steps and emits the current tilt via two GPIOs.
Dbcm5974.txt31 mouse via the mousedev driver (/dev/input/mice).
36 The Apple multi-touch trackpads report both mouse and keyboard events via
/linux-4.4.14/security/selinux/
DKconfig66 permissive mode (if permitted by the policy) via /selinux/enforce.
74 /selinux/avc/cache_stats, which may be monitored via
91 The checkreqprot flag may be changed from the default via the
93 via /selinux/checkreqprot if authorized by policy.
104 to userspace via /selinux/policyvers and used at policy load time.
110 and set the value via the next option. For Fedora Core 5 and later,
/linux-4.4.14/arch/tile/gxio/
DKconfig1 # Support direct access to TILE-Gx hardware from user space, via the
2 # gxio library, or from kernel space, via kernel IORPC support.
/linux-4.4.14/Documentation/i2c/busses/
Di2c-viapro20 Datasheet: available on http://linux.via.com.tw
23 Datasheet: available on http://linux.via.com.tw
26 Datasheet: available on http://linux.via.com.tw
Di2c-via1 Kernel driver i2c-via
12 i2c-via is an i2c bus driver for motherboards with VIA chipset.
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dvt8500.txt9 "via,vt8500-pll-clock" - for a VT8500/WM8505 PLL clock
13 "via,vt8500-device-clock" - for a VT/WM device clock
68 compatible = "via,vt8500-device-clock";
Dpwm-clock.txt12 via the period given in the PWM specifier.
/linux-4.4.14/Documentation/infiniband/
Duser_verbs.txt4 enables direct userspace access to IB hardware via "verbs," as
18 management operations via the /dev/infiniband/uverbsN character
23 Commands are sent to the kernel via write()s on these device files.
47 ib_uverbs module manages pinning and unpinning memory regions via
/linux-4.4.14/Documentation/s390/
Ddriver-model.txt10 All ccw devices are accessed via a subchannel, this is reflected in the
23 In this example, device 0815 is accessed via subchannel 0 in subchannel set 0,
24 device 4711 via subchannel 1 in subchannel set 0, and subchannel 2 is a non-I/O
25 subchannel. Device 1234 is accessed via subchannel 0 in subchannel set 1.
33 You should address a ccw device via its bus id (e.g. 0.0.4711); the device can
36 All ccw devices export some data via sysfs.
70 via the 'online' interface.
142 activated via the 'online' attribute. The driver should finally
152 de-activated via the 'online' attribute. The driver should shut
279 number is assigned sequentially to the connections defined via the 'connection'
/linux-4.4.14/arch/powerpc/platforms/pasemi/
DKconfig35 tristate "MDIO support via GPIO"
38 Driver for MDIO via GPIO on PWRficient platforms
/linux-4.4.14/drivers/net/wireless/cw1200/
DKconfig15 Enable support for the CW1200 connected via an SDIO bus.
26 Enables support for the CW1200 connected via a SPI bus. You will
/linux-4.4.14/Documentation/mic/
Dscif_overview.txt18 6. Remote memory mapping for low latency CPU accesses via mmap
25 different node via a SCIF "endpoint". SCIF endpoints support messaging APIs
28 DMA, CPU copies or remote memory mapping via mmap. SCIF supports both user and
60 SCIF allows memory sharing via mmap(..) between processes on different PCIe
/linux-4.4.14/drivers/iio/frequency/
DKconfig18 Clock Generator. The driver provides direct access via sysfs.
36 Wideband Synthesizers. The driver provides direct access via sysfs.
/linux-4.4.14/drivers/regulator/
DKconfig63 the voltage is programmed via I2C interface.
79 regulator via I2C bus.
249 controlled via gpios.
319 8-output regulators controlled via I2C.
325 This driver controls a Maxim MAX14577/77836 regulator via I2C bus.
334 regulator via I2C bus. The provided regulator is suitable
342 This driver controls a Maxim 8649 voltage output regulator via
350 regulator via I2C bus.
357 via I2C bus. The provided regulator is suitable for Tegra
371 via I2C bus. Maxim 8952 has one voltage output and supports 4 DVS
[all …]
/linux-4.4.14/Documentation/hid/
Dhid-transport.txt63 device. Once a device is registered with HID core, the callbacks provided via
84 required on asynchronous channels, a transport-driver must implement that via
100 not send via intr, except if high throughput is required.
107 Outgoing reports are usually sent on the ctrl channel via synchronous
110 Communication between devices and HID core is mostly done via HID reports. A
241 destroyed them via hid_destroy_device().
261 about it via hid_parse_report().
273 report following the HID specs and send it via the ->raw_request() callback.
290 Send raw output report via intr channel. Used by some HID device drivers
306 Every raw data packet read from a device must be fed into HID core via
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/net/wireless/
Dti,wl1251.txt3 The wl1251 chip can be connected via SPI or via SDIO. This
/linux-4.4.14/Documentation/ptp/
Dptp.txt24 - Synchronization of the Linux system time via the PPS subsystem
32 driver of asynchronous events (alarms and external time stamps) via
51 events via blocking read() and poll(). One shot and periodic
52 signals may be configured via the POSIX timer_settime() system
/linux-4.4.14/Documentation/networking/
Doperstates.txt24 Both admin and operational state can be queried via the netlink
66 This TLV can also be queried via sysfs.
73 This TLV can also be queried via sysfs.
130 via RTM_SETLINK instructs the kernel that an interface should go to
141 -set IFLA_LINKMODE to 1 via RTM_SETLINK
148 -see how operstate and IFF_RUNNING is echoed via netlink multicast
Dteam.txt1 Team devices are driven from userspace via libteam library which is here:
Datm.txt3 programs and related material can be found via the ATM on Linux Web
Dswitchdev.txt347 default via 192.168.0.2 dev eth0
349 11.0.0.4/30 via 11.0.0.1 dev sw1p1 proto zebra metric 20 offload
351 11.0.0.12/30 via 11.0.0.9 dev sw1p2 proto zebra metric 20 offload
353 nexthop via 11.0.0.1 dev sw1p1 weight 1
354 nexthop via 11.0.0.9 dev sw1p2 weight 1
355 12.0.0.3 via 11.0.0.1 dev sw1p1 proto zebra metric 20 offload
356 12.0.0.4 via 11.0.0.9 dev sw1p2 proto zebra metric 20 offload
367 address discovery comes via the ARP (or ND) process and is available via the
/linux-4.4.14/drivers/mtd/onenand/
DKconfig22 tristate "OneNAND Flash device via platform device driver"
24 Support for OneNAND flash via platform device driver.
31 via the GPMC memory controller.
/linux-4.4.14/drivers/remoteproc/
DKconfig23 and DSP on OMAP4) via the remote processor framework.
64 Say y here to support DA8xx/OMAP-L13x remote processors via the
73 directory. It can be specified via the module parameter
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DCPUfreq.txt9 frequencies. The core control is exported via the CPUFreq driver
15 PLL to feed the ARM, memory and peripherals via a series of dividers
53 The core code exports extra information via sysfs in the directory
/linux-4.4.14/drivers/isdn/mISDN/
DKconfig37 - layer 1 control via network keepalive frames
38 - direct tunneling of physical interface via IP
/linux-4.4.14/drivers/firmware/
DKconfig36 BIOS tries boot from. This information is then exported via sysfs.
62 bool "Console device selection via EFI PCDP or HCDP table"
86 tristate "BIOS update support for DELL systems via sysfs"
114 bool "Export DMI identification via sysfs to userspace"
128 data via sysfs. This is useful for consuming the data without
153 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
/linux-4.4.14/drivers/staging/gdm72xx/
DKconfig41 processor via USB.
48 processor via SDIO.
/linux-4.4.14/security/tomoyo/
DKconfig38 You can read the log via /sys/kernel/security/tomoyo/audit.
64 activation. You can override this setting via TOMOYO_loader= kernel
74 You can override this setting via TOMOYO_trigger= kernel command line
/linux-4.4.14/drivers/uwb/
DKconfig36 Radio Controller connected to your system via USB. Most of
51 radio/host controllers connected via memory mapping (eg:
63 This driver enables support for the i1480 when connected via
/linux-4.4.14/Documentation/
Dsmsc_ece1099.txt7 via the SMSC BC-Link interface or via the SMBus.
34 through a series of read/write registers via the SMBus
Dsgi-ioc4.txt38 up to the ioc4 driver via the appropriate registration, probe, and
44 other than it hooks up to the ioc4 driver via the appropriate registration,
Dstatic-keys.txt24 performance-sensitive fast-path kernel code, via a GCC feature and a code
117 Keys defined via DEFINE_STATIC_KEY_TRUE(), or DEFINE_STATIC_KEY_FALSE, may
121 Branch(es) can be set true via:
125 or false via:
129 The branch(es) can then be switched via reference counts:
/linux-4.4.14/Documentation/locking/
Dlocktorture.txt9 messages via printk(), which can be examined via the dmesg (perhaps
12 is tortured, via rcutorture.
62 torture_runnable to be set via sysfs before starting.
104 verbose Enable verbose debugging printing, via printk(). Enabled
/linux-4.4.14/arch/sh/include/mach-ecovec24/mach/
Dpartner-jet-setup.txt6 LIST "This script can be used to boot the kernel from RAM via JTAG:"
12 LIST "Use the following command to burn the zImage to flash via JTAG:"
/linux-4.4.14/drivers/ata/
DKconfig556 PATA controllers via the new ATA layer.
565 PATA controllers via the new ATA layer.
574 controllers via the new ATA layer.
583 PATA controllers via the new ATA layer
617 controllers via the new ATA layer.
626 PATA controllers via the new ATA layer, including RAID
635 Enable support for the JMicron IDE controller, via the new
650 tristate "Marvell PATA support via legacy mode"
737 PATA controllers via the new ATA layer
746 controllers via the new ATA layer. For the RDC 1010, you need to
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dvexpress-sysreg.txt60 bus via "system control" interface, addressing devices with site number,
63 controller accessible via this interface must reference the sysreg
64 node via "arm,vexpress,config-bridge" phandle and define appropriate
Darch_timer.txt8 per-processor interrupts via PPIs. The memory mapped timer is attached to a GIC
9 to deliver its interrupts via SPIs.
Dvt8500.txt6 compatible = "via,vt8500";
/linux-4.4.14/Documentation/arm/
Dmemory.txt68 Kernel modules inserted via insmod are
72 Per-thread mappings are placed here via
79 space are also caught via this mapping.
/linux-4.4.14/sound/pci/hda/
DMakefile25 snd-hda-codec-via-objs := patch_via.o
42 obj-$(CONFIG_SND_HDA_CODEC_VIA) += snd-hda-codec-via.o
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Dgeneric.txt7 via DT, USB controllers should default to their maximum
12 passed via DT, USB DRD controllers should default to
/linux-4.4.14/tools/perf/Documentation/
Dperf-sched.txt27 via perf sched record. (this is done by starting up mockup threads
34 workload captured via perf sched record. Columns stand for
Dexamples.txt9 First, discovery/enumeration of available counters can be done via
173 Or observe how fluctuating the page allocations are, via statistical
214 possible via /proc/vmstat.
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-st.txt16 First type is via irqmux, single interrupt is used by multiple gpio banks. This
45 with other gpio banks via irqmux.
62 bank can be an interrupt controller iff one of the interrupt type either via
167 interrupts = <3 IRQ_TYPE_LEVEL_HIGH>; /* Interrupt line via PIO3-3 */
/linux-4.4.14/drivers/power/reset/
DKconfig15 This driver supports turning off board via a ams AS3722 power-off.
56 This driver supports turning off your board via a GPIO line.
64 This driver supports restarting your board via a GPIO line.
94 down via the LTC2952. Bindings are made in the device tree.
/linux-4.4.14/arch/m68k/mac/
DMakefile5 obj-y := config.o macints.o iop.o via.o oss.o psc.o \
/linux-4.4.14/drivers/infiniband/ulp/ipoib/
DKconfig32 IPoIB driver. The output can be turned on via the
46 of the IPoIB driver. The output can be turned on via the
/linux-4.4.14/drivers/leds/trigger/
DKconfig7 be configured via sysfs. If unsure, say Y.
16 via sysfs. Some LED hardware can be programmed to start
27 controlled via sysfs. It's useful to notify the user on
/linux-4.4.14/Documentation/devicetree/bindings/soc/fsl/
Dbman.txt56 Devices connected to a BMan instance via Direct Connect Portals (DCP) must link
63 to which this device is connected via the DCP
86 via the Reset Configuration Word (RCW) and that are relevant to a specific board
Dqman.txt64 Devices connected to a QMan instance via Direct Connect Portals (DCP) must link
71 to which this device is connected via the DCP
103 configured via the Reset Configuration Word (RCW) and that are relevant to a
/linux-4.4.14/drivers/parport/
Dparport_pc.c2306 const struct parport_pc_via_data *via) in sio_ite_8872_probe() argument
2435 const struct parport_pc_via_data *via) in sio_via_probe() argument
2481 pci_read_config_byte(pdev, via->via_pci_superio_config_reg, &tmp); in sio_via_probe()
2482 tmp |= via->via_pci_superio_config_data; in sio_via_probe()
2483 pci_write_config_byte(pdev, via->via_pci_superio_config_reg, tmp); in sio_via_probe()
2486 outb(via->viacfg_function, VIA_CONFIG_INDEX); in sio_via_probe()
2489 outb(via->viacfg_parport_control, VIA_CONFIG_INDEX); in sio_via_probe()
2497 outb(via->viacfg_function, VIA_CONFIG_INDEX); in sio_via_probe()
2501 outb(via->viacfg_parport_control, VIA_CONFIG_INDEX); in sio_via_probe()
2506 outb(via->viacfg_parport_base, VIA_CONFIG_INDEX); in sio_via_probe()
[all …]
/linux-4.4.14/Documentation/security/
DLSM.txt7 loadable kernel modules. Instead, they are selectable at build-time via
8 CONFIG_DEFAULT_SECURITY and can be overridden at boot-time via the
/linux-4.4.14/drivers/staging/iio/adc/
DKconfig91 activate only one via device tree selection. Provides direct access
92 via sysfs.
114 ST SPEAr SoC. Provides direct access via sysfs.
/linux-4.4.14/drivers/staging/most/aim-cdev/
DKconfig9 Say Y here if you want to commumicate via character devices.
/linux-4.4.14/drivers/staging/most/aim-v4l2/
DKconfig9 Say Y here if you want to commumicate via Video 4 Linux.
/linux-4.4.14/drivers/staging/most/aim-network/
DKconfig10 Say Y here if you want to commumicate via a networking device.
/linux-4.4.14/drivers/staging/most/hdm-i2c/
DKconfig9 Say Y here if you want to connect via I2C to network tranceiver.
/linux-4.4.14/Documentation/devicetree/bindings/mips/img/
Dxilfpga.txt70 This is for easy reprogrammibility via JTAG.
83 vmlinux file via JTAG.
/linux-4.4.14/drivers/acpi/apei/
DKconfig39 PCIe AER errors may be reported via APEI firmware first mode.
46 Memory errors may be reported via APEI firmware first mode.
/linux-4.4.14/drivers/staging/media/lirc/
DTODO.lirc_zilog24 to lirc_zilog via struct IR_i2c_init_data. cx18 and ivtv already have routines
25 to perform Z8 chip resets via GPIO manipulations. This would allow lirc_zilog
/linux-4.4.14/drivers/staging/most/aim-sound/
DKconfig10 Say Y here if you want to commumicate via ALSA/sound devices.
/linux-4.4.14/drivers/reset/
DKconfig11 via GPIOs or SoC-internal reset controller modules.
/linux-4.4.14/drivers/media/mmc/siano/
DKconfig6 tristate "Siano SMS1xxx based MDTV via SDIO interface"
/linux-4.4.14/Documentation/devicetree/bindings/input/
Dtps65218-pwrbutton.txt3 This driver provides a simple power button event via an Interrupt.
Dtwl4030-pwrbutton.txt6 This module provides a simple power button event via an Interrupt.
/linux-4.4.14/Documentation/sound/oss/
Dmwave131 causes the kernel to crash when loaded via loadlin (but NOT when loaded via
132 LILO). The APM stuff COULD be forced out of the kernel via the kernel compile
134 to be dynamically deactivated via kernel arguments. Whatever you chose to
/linux-4.4.14/Documentation/acpi/
Dmethod-tracing.txt19 enabled. The debugging messages which are deployed via
21 level (known as debug layer, configured via
23 debug level, configured via /sys/module/acpi/parameters/debug_level).
84 that, as the "AML tracer" logs are implemented via ACPI_DEBUG_PRINT()
132 All method tracing functions can be configured via ACPI module
/linux-4.4.14/Documentation/fb/
Dudlfb.txt15 pixels line-by-line via USB bulk transfers.
78 rectangles from the X DAMAGE protocol extension down to udlfb via udlfb's
92 Or modify options on the fly at /sys/module/udlfb/parameters directory via
108 changed regions via ioctl, as this method is simpler,
134 communicate their capabilities via EDID. Reading
Dmetronomefb.txt20 Metronomefb requires waveform information which is delivered via the AMLCD
22 be delivered from userspace via the firmware class interface. The waveform file
/linux-4.4.14/Documentation/early-userspace/
DREADME137 filesystem via linuxrc and use the pivot_root syscall. The initrd is
138 mounted and executed via prepare_namespace().
142 into initramfs either via modifying usr/gen_init_cpio.c or via the new
147 comes via an initramfs cpio archive. If this is not the case,
/linux-4.4.14/drivers/staging/most/hdm-usb/
DKconfig10 Say Y here if you want to connect via USB to network tranceiver.
/linux-4.4.14/drivers/gpu/drm/udl/
DKconfig15 Say M/Y to add support for these devices via drm/kms interfaces.
/linux-4.4.14/arch/powerpc/
DKconfig.debug182 Select this to enable early debugging via the RTAS panel.
189 Select this to enable early debugging via the RTAS console.
208 Select this to enable early debugging for IBM 44x chips via the
216 Select this to enable early debugging for IBM 40x chips via the
235 consoles via an external USB Gecko adapter.
242 Select this to enable early debugging for the PlayStation3 via
355 be selectively enabled via the fail_iommu property.
/linux-4.4.14/drivers/staging/unisys/Documentation/
Doverview.txt39 * s-Par also supports sharing physical PCI adapters via SR-IOV, but
47 provide a guest graphics console are for keyboard and mouse (via visorinput).
63 visorbus about the device classes (via specifying a list of device type
69 as a module it will typically be loaded automatically via standard udev or
202 <devname> if applicable, each file here identifies (via
314 As the s-Par back-end reports keyboard and mouse activity via events on the
320 usyscon Partition Desktop into a Linux environment via the
321 usyscon_partitiondesktop-*.rpm, or into a Windows environment via
346 configurations where the Linux guest boots via an SR-IOV-provided HBA or
/linux-4.4.14/fs/efivarfs/
DKconfig7 variable support via sysfs, as it doesn't suffer from the
/linux-4.4.14/drivers/isdn/gigaset/
DKconfig53 Say M here if you want to connect to the Gigaset base via DECT
60 Say M here if you want to connect to the Gigaset base via DECT
/linux-4.4.14/kernel/irq/
DKconfig81 bool "Expose hardware/virtual IRQ mapping via debugfs"
85 numbers and Linux irq numbers. The mapping is exposed via debugfs
/linux-4.4.14/net/can/
DKconfig25 The raw CAN protocol option offers access to the CAN bus via
37 interaction. The BCM can be 'programmed' via the BSD socket API and
/linux-4.4.14/drivers/staging/iio/impedance-analyzer/
DKconfig13 Network Analyzer, AD5933/4, provides direct access via sysfs.
/linux-4.4.14/drivers/misc/vmw_vmci/
DKconfig11 environment via the VMCI virtual device.
/linux-4.4.14/Documentation/block/
Dcapability.txt14 space via kernel uevent.
/linux-4.4.14/drivers/staging/most/hdm-dim2/
DKconfig11 Say Y here if you want to connect via MediaLB to network transceiver.
/linux-4.4.14/Documentation/leds/
Dleds-lp55xx.txt10 Register access via the I2C
73 run_engine : Start program which is loaded via the firmware interface
157 via the sysfs if needed.
188 Then, mode_1 and mode_2 can be run via through the sysfs.
Dleds-lm3556.txt18 from 93.75 mA to 1500 mA.The Flash currents are adjusted via the CURRENT
32 In Torch Mode, the current source(LED) is programmed via the CURRENT CONTROL
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Dinfo.txt4 All but index, number of crypto threads and maximum IO size can changed via remount.
7 Each mountpoint is associated with a special index via this option.
62 Client will connect to all servers specified in the working set via previous command:
Ddesign_notes.txt21 (like removing the whole kernel tree via a single network command).
60 Administrators can add or remove servers from the set at run-time via special commands (described
72 can be controlled via a mount option.
/linux-4.4.14/Documentation/x86/x86_64/
D00-INDEX16 - Booting Linux via Unified Extensible Firmware Interface.
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dstorm.txt4 connected to a MAX98357A DAC via I2S.
/linux-4.4.14/Documentation/devicetree/bindings/hwmon/
Dvexpress.txt11 - "arm,vexpress-sysreg,func" when controlled via vexpress-sysreg
/linux-4.4.14/drivers/media/firewire/
DKconfig6 which are connected via IEEE 1394 (FireWire).
/linux-4.4.14/Documentation/i2c/
Dslave-eeprom-backend7 I2C bus. The memory contents can be modified from userspace via this file
/linux-4.4.14/drivers/hid/i2c-hid/
DKconfig11 other HID based devices which is connected to your computer via I2C.
/linux-4.4.14/Documentation/video4linux/
DREADME.ir34 applications to access the remote via /dev/input/event<n> devices.
49 linux input layer (via event device). The input layer tools tarball
/linux-4.4.14/drivers/hwtracing/intel_th/
DKconfig42 trace sources to be sent out via Intel(R) Trace Hub. It
61 of Intel TH architecture that facilitates STP trace output via
/linux-4.4.14/net/mpls/
Daf_mpls.c596 struct nlattr *via, struct nlattr *newdst) in mpls_nh_build() argument
610 if (via) { in mpls_nh_build()
611 err = nla_get_via(via, &nh->nh_via_alen, &nh->nh_via_table, in mpls_nh_build()
970 struct rtvia *via; in nla_put_via() local
980 via = nla_data(nla); in nla_put_via()
981 via->rtvia_family = family; in nla_put_via()
982 memcpy(via->rtvia_addr, addr, alen); in nla_put_via()
1057 struct rtvia *via = nla_data(nla); in nla_get_via() local
1069 switch (via->rtvia_family) { in nla_get_via()
1088 memcpy(via_addr, via->rtvia_addr, alen); in nla_get_via()
/linux-4.4.14/drivers/leds/
DKconfig58 LED HW controller accessed via MMIO registers.
66 LED HW controller accessed via MMIO registers.
245 Driver provides direct control via LED class and interface for
256 Driver provides direct control via LED class and interface for
266 Driver provides direct control via LED class and interface for
276 Driver provides direct control via LED class and interface for
336 LED driver chips accessed via the I2C bus. Supported
345 LED driver chip accessed via the I2C bus. Supported
408 accessed via the I2C bus.
496 LED driver chips accessed via the I2C bus.
/linux-4.4.14/drivers/media/common/b2c2/
DKconfig22 # Selected via the PCI or USB flexcop drivers
/linux-4.4.14/drivers/infiniband/hw/mthca/
DKconfig15 mthca driver. The output can be turned on via the
/linux-4.4.14/drivers/sfi/
DKconfig10 via static tables in memory. Kernel SFI support is required to
/linux-4.4.14/arch/openrisc/boot/dts/
Dor1ksim.dts28 * OR1K PIC is built into CPU and accessed via special purpose
/linux-4.4.14/fs/notify/inotify/
DKconfig9 directories via a single open fd. Events are read from the file
/linux-4.4.14/arch/x86/lib/
Dcmpxchg16b_emu.S26 # via the ZF. Caller will access %al to get result.
/linux-4.4.14/sound/hda/
DKconfig29 via a proc file (/proc/asound/card*/pcm*/sub*/prealloc), too.
/linux-4.4.14/drivers/staging/fwserial/
DTODO8 3. Expose means of controlling attach/detach of peers via sysfs. Include
/linux-4.4.14/Documentation/spi/
D00-INDEX16 - Connecting an LM70-LLP sensor to the kernel via the SPI subsys.
/linux-4.4.14/Documentation/vm/
Dovercommit-accounting27 The overcommit policy is set via the sysctl `vm.overcommit_memory'.
29 The overcommit amount can be set via `vm.overcommit_ratio' (percentage)
/linux-4.4.14/drivers/firmware/efi/
DKconfig5 tristate "EFI Variable Support via sysfs"
10 Interface) variable information via sysfs. You may read,
/linux-4.4.14/tools/virtio/virtio-trace/
DREADME104 option, trace data are output via stdout in the guest.
113 A host injects read start order to the guest via virtio-serial.
117 A host injects read stop order to the guest via virtio-serial.
/linux-4.4.14/Documentation/scheduler/
Dsched-bwc.txt24 Quota and period are managed within the cpu subsystem via cgroupfs.
58 This is tunable via procfs:
66 A group's bandwidth statistics are exported via 3 fields in cpu.stat.
/linux-4.4.14/arch/powerpc/sysdev/
DKconfig36 bool "Expose SCOM controllers via debugfs"
/linux-4.4.14/sound/pcmcia/
DKconfig8 Support for sound devices connected via the PCMCIA bus.
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dqcom,tcsr.txt5 registers via syscon.
/linux-4.4.14/Documentation/devicetree/bindings/power/
Drx51-battery.txt3 The Nokia N900 battery status can be read via the TWL4030's A/D converter.
/linux-4.4.14/drivers/char/agp/
DMakefile22 obj-$(CONFIG_AGP_VIA) += via-agp.o
/linux-4.4.14/drivers/media/common/siano/
DKconfig29 statistics response packets via debugfs. Currently, works
/linux-4.4.14/net/9p/
DKconfig10 Plan 9 resource sharing via the 9P2000 protocol.
/linux-4.4.14/Documentation/devicetree/bindings/regulator/
Dvexpress.txt6 - "arm,vexpress-sysreg,func" when controlled via vexpress-sysreg
/linux-4.4.14/Documentation/video4linux/cx2341x/
Dfw-calling.txt65 firmware which events it is interested in via an API call. That call tells the
66 firmware which notification mailbox to use. The firmware signals the host via
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dmtd-physmap.txt23 unaligned accesses as implemented in the JFFS2 code via memcpy().
27 physmap-flash drivers as boot loader pass the mtd partition via the old
Dst-fsm.txt13 - st,boot-device-spi : Expected boot-device value if booted via this device
/linux-4.4.14/drivers/staging/iio/accel/
DKconfig85 accelerometer. The driver supplies direct access via sysfs files
86 and an event interface via a character device.
/linux-4.4.14/Documentation/misc-devices/
Dc2port.txt26 where the micro controller is connected via special GPIOs pins.
34 - AN127: FLASH Programming via the C2 Interface at
/linux-4.4.14/arch/sh/include/mach-kfr2r09/mach/
Dpartner-jet-setup.txt5 LIST "This script can be used to boot the kernel from RAM via JTAG:"
11 LIST "Use the following command to burn the zImage to flash via JTAG:"
/linux-4.4.14/arch/tile/
DKconfig.debug9 Write kernel log output directly via the hypervisor console.
/linux-4.4.14/Documentation/blockdev/
Dcciss.txt103 also be directed to dynamically engage the SCSI core via the /proc filesystem
105 /proc/driver/cciss/cciss* at runtime. This is best done via a script.
126 have been made. This may be done via the /proc filesystem.
194 Or, as a kernel boot parameter passed in via grub: cciss.cciss_tape_cmds=8

12345