Searched full:via (Results 1 – 25 of 969) sorted by relevance
12345678910>>...39
| /Documentation/ABI/testing/ |
| D | sysfs-tty | 29 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 …]
|
| D | sysfs-bus-counter-104-quad-8 | 8 are boolean. Detection must first be enabled via the
52 input. The index function (as enabled via preset_enable)
59 via index_polarity. The index function (as enabled via
|
| D | sysfs-driver-hid-prodikeys | 6 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.
|
| /Documentation/i2c/busses/ |
| D | i2c-viapro.rst | 6 * VIA Technologies, Inc. VT82C596A/B
7 Datasheet: Sometimes available at the VIA website
9 * VIA Technologies, Inc. VT82C686A/B
10 Datasheet: Sometimes available at the VIA website
12 * VIA Technologies, Inc. VT8231, VT8233, VT8233A
13 Datasheet: available on request from VIA
15 * VIA Technologies, Inc. VT8235, VT8237R, VT8237A, VT8237S, VT8251
16 Datasheet: available on request and under NDA from VIA
18 * VIA Technologies, Inc. CX700
19 Datasheet: available on request and under NDA from VIA
[all …]
|
| D | i2c-via.rst | 2 Kernel driver i2c-via
6 * VIA Technologies, InC. VT82C586B
7 Datasheet: Publicly available at the VIA website
14 i2c-via is an i2c bus driver for motherboards with VIA chipset.
16 The following VIA pci chipsets are supported:
22 Bridge: VIA Technologies, Inc. VT82C586B ACPI (rev 10)
38 This can happen. This driver uses the pins VIA recommends in their
|
| /Documentation/devicetree/bindings/net/ |
| D | via-rhine.txt | 1 * VIA Rhine 10/100 Network Controller
4 - compatible : Should be "via,vt8500-rhine" for integrated
5 Rhine controllers found in VIA VT8500, WonderMedia WM8950
14 compatible = "via,vt8500-rhine";
|
| D | via-velocity.txt | 1 * VIA Velocity 10/100/1000 Network Controller
4 - compatible : Should be "via,velocity-vt6110"
16 compatible = "via,velocity-vt6110";
|
| /Documentation/hwmon/ |
| D | raspberrypi-hwmon.rst | 6 * Raspberry Pi A+ (via GPIO on SoC)
7 * Raspberry Pi B+ (via GPIO on SoC)
8 * Raspberry Pi 2 B (via GPIO on SoC)
9 * Raspberry Pi 3 B (via GPIO on port expander)
10 * Raspberry Pi 3 B+ (via PMIC)
|
| D | g762.rst | 15 done via a userland daemon like fancontrol.
19 fan revolution, ...); Those can be modified via devicetree bindings
50 speed control (open-loop) via pwm1 described below, 2 for
51 automatic fan speed control (closed-loop) via fan1_target
64 the fan speed is programmed by setting a value between 0 and 255 via 'pwm1'
67 the chip via 'fan1_target'. In closed-loop mode, the target speed is compared
68 with current speed (available via 'fan1_input') by the device and a feedback
|
| /Documentation/devicetree/bindings/serial/ |
| D | vt8500-uart.txt | 1 * VIA VT8500 and WonderMedia WM8xxx UART Controller
4 - compatible: should be "via,vt8500-uart" (for VIA/WonderMedia chips up to and
23 compatible = "via,vt8500-uart";
|
| /Documentation/devicetree/bindings/arm/vt8500/ |
| D | via,vt8500-pmc.txt | 1 VIA/Wondermedia VT8500 Power Management Controller
5 - compatible : "via,vt8500-pmc"
11 compatible = "via,vt8500-pmc";
|
| /Documentation/devicetree/bindings/timer/ |
| D | via,vt8500-timer.txt | 1 VIA/Wondermedia VT8500 Timer
5 - compatible : "via,vt8500-timer"
12 compatible = "via,vt8500-timer";
|
| /Documentation/devicetree/bindings/rtc/ |
| D | via,vt8500-rtc.txt | 1 VIA/Wondermedia VT8500 Realtime Clock Controller
5 - compatible : "via,vt8500-rtc"
12 compatible = "via,vt8500-rtc";
|
| /Documentation/devicetree/bindings/pwm/ |
| D | vt8500-pwm.txt | 1 VIA/Wondermedia VT8500/WM8xxx series SoC PWM controller
4 - compatible: should be "via,vt8500-pwm"
15 compatible = "via,vt8500-pwm";
|
| /Documentation/filesystems/ |
| D | dlmfs.rst | 8 A minimal DLM userspace interface implemented via a virtual file
52 your lockspace can access. The easiest way to do this is via
67 Users may access dlmfs via standard file system calls, or they can use
82 Lock value blocks can be read and written to a resource via read(2)
83 and write(2) against the fd obtained via your open(2) call. The
94 domain directory. Locking against them is done via the open(2) system
127 access to the resources via dlmfs on your local node only.
130 Exclusive modes via the read(2) system call. It can be written via
|
| D | configfs.rst | 23 appear in sysfs, allowing userspace to read the attributes via
24 readdir(3)/read(2). It may allow some attributes to be modified via
29 A configfs config_item is created via an explicit userspace operation:
30 mkdir(2). It is destroyed via rmdir(2). The attributes appear at
31 mkdir(2) time, and can be read or modified via read(2) and write(2).
54 An item is created via mkdir(2). The item's attributes will also
80 item cannot be destroyed if any other item has a link to it (via
81 symlink(2)). Links can be removed via unlink(2).
115 That's it. That's all there is. Now the device is configured, via the
171 All users of a config_item should have a reference on it via
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | via,vt8500-intc.txt | 1 VIA/Wondermedia VT8500 Interrupt Controller
5 - compatible : "via,vt8500-intc"
12 compatible = "via,vt8500-intc";
|
| /Documentation/sound/designs/ |
| D | powersave.rst | 6 This feature is enabled via Kconfig ``CONFIG_SND_AC97_POWER_SAVE``
15 The time-out for automatic power-off can be specified via ``power_save``
18 power-saving. The default value of timeout is given via
26 adjust the value via sysfs on the fly. For example, to turn on the
|
| /Documentation/networking/ |
| D | statistics.rst | 17 - driver-defined statistics available via ethtool.
42 `ip` supports JSON formatting via the `-j` option.
119 Identifiers via `ETHTOOL_GSTRINGS` with `string_set` set to `ETH_SS_STATS`,
120 and values via `ETHTOOL_GSTATS`. User space should use `ETHTOOL_GDRVINFO`
137 Some drivers expose extra statistics via `debugfs`.
150 via `.ndo_get_stats64`. Reporting such standard stats via ethtool
159 via `/proc/net/dev`. If driver may sleep when retrieving the statistics
|
| /Documentation/devicetree/bindings/display/ |
| D | via,vt8500-fb.txt | 1 VIA VT8500 Framebuffer
5 - compatible : "via,vt8500-fb"
16 compatible = "via,vt8500-fb";
|
| /Documentation/firmware-guide/acpi/ |
| D | lpit.rst | 12 Residencies for each low power state can be read via FFH
18 - CPU PKG C10 (Read via FFH interface)
19 - Platform Controller Hub (PCH) SLP_S0 (Read via memory mapped interface)
|
| /Documentation/filesystems/cifs/ |
| D | cifsroot.rst | 4 Mounting root file system via SMB (cifs.ko)
12 support over the SMB protocol via cifs.ko.
31 to use can nonetheless be changed via the 'vers=' mount option. This
53 the root file system via SMB protocol.
59 Enables the kernel to mount the root file system via SMB that are
|
| /Documentation/userspace-api/media/dvb/ |
| D | net.rst | 22 ``/dev/dvb/adapter?/net?`` device node. The data will be available via
23 virtual ``dvb?_?`` network interfaces, and will be controlled/routed via
26 Data types and and ioctl definitions are defined via ``linux/dvb/net.h``
|
| /Documentation/s390/ |
| D | driver-model.rst | 11 All ccw devices are accessed via a subchannel, this is reflected in the
24 In this example, device 0815 is accessed via subchannel 0 in subchannel set 0,
25 device 4711 via subchannel 1 in subchannel set 0, and subchannel 2 is a non-I/O
26 subchannel. Device 1234 is accessed via subchannel 0 in subchannel set 1.
34 You should address a ccw device via its bus id (e.g. 0.0.4711); the device can
37 All ccw devices export some data via sysfs.
61 Via which chpids the device is connected.
77 via the 'online' interface.
161 activated via the 'online' attribute. The driver should finally
175 de-activated via the 'online' attribute. The driver should shut
[all …]
|
| /Documentation/trace/ |
| D | intel_th.rst | 20 via sysfs attributes.
28 debug host via a PTI port,
38 via its "masters" attribute group. More detailed GTH interface
46 buffer, which can later on be read from its device nodes via read() or
52 and collected via sysfs attributes, and device nodes.
67 allocated, are accessible via /dev/intel_th0/msc{0,1}.
109 capture from a remote debug host, which should be connected via one of
132 Such drivers can further export the data via other devices, such as
|
12345678910>>...39