Searched full:via (Results 1 – 25 of 1279) sorted by relevance
12345678910>>...52
| /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-class-tee | 6 RPMB frames can be routed to the RPMB device via the
9 will route the RPMB frames via user space. Conversely,
10 "kernel" means that the frames are routed via the RPMB
12 should be assumed that RPMB frames are routed via user
|
| 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 | via,vt8500-uart.yaml | 5 $id: http://devicetree.org/schemas/serial/via,vt8500-uart.yaml#
8 title: VIA VT8500 and WonderMedia WM8xxx UART Controller
19 - via,vt8500-uart # up to WM8850/WM8950
42 compatible = "via,vt8500-uart";
|
| /Documentation/driver-api/surface_aggregator/ |
| D | client.rst | 43 differentiate between devices that are presented to the system via one of
44 the conventional ways, e.g. as platform devices via ACPI, and devices that
52 All communication with the SAM EC is handled via the |ssam_controller|
55 connection/relation to that controller. This can be done via the
58 client device and controller (this can also be done separate via
82 The controller may be separately obtained via |ssam_get_controller| and its
83 lifetime be guaranteed via |ssam_controller_get| and |ssam_controller_put|.
93 If a device does not already exist/is not already provided via conventional
94 means, it should be provided as |ssam_device| via the SSAM client device
96 corresponding registry. SSAM devices can also be manually allocated via
[all …]
|
| D | internal.rst | 87 implemented as platform devices, via |ssam_device| and |ssam_device_driver|
100 The packet transport layer is represented via |ssh_ptl| and is structured
109 Packets to be transmitted by the SSAM core are represented via |ssh_packet|
111 structure and are managed entirely via the raw |ssh_frame|).
117 lifetime (accessible via |ssh_packet_get| and |ssh_packet_put|). When this
118 counter reaches zero, the ``release()`` callback provided to the packet via
131 The state of a packet is managed via its ``state`` flags
161 this queue via |ssh_ptl_submit|. Note that this includes control packets
208 to the corresponding pending packet (via sequence ID) and completing it, as
216 Any payload data is forwarded via a callback to the next upper layer, i.e.
[all …]
|
| /Documentation/driver-api/surface_aggregator/clients/ |
| D | san.rst | 13 battery and thermal events via this interface. In addition to this, events
16 only currently known event sent via this interface is a dGPU power-on
18 relays the dGPU events to any other driver interested via its public API and
25 via |san_client_link|. This can be used to ensure that the a client
33 should be unregistered via |san_dgpu_notifier_unregister|.
|
| /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/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/timer/ |
| D | via,vt8500-timer.txt | 1 VIA/Wondermedia VT8500 Timer
5 - compatible : "via,vt8500-timer"
12 compatible = "via,vt8500-timer";
|
| /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/networking/ |
| D | statistics.rst | 17 - driver-defined statistics available via ethtool.
42 `ip` supports JSON formatting via the `-j` option.
47 Queue statistics are accessible via the netdev netlink family.
56 Protocol-specific statistics are exposed via relevant interfaces,
75 Standard ethtool statistics can be accessed via the interfaces used
89 functionality are exposed via ``ethtool -S $ifc`` by specifying
174 Identifiers via `ETHTOOL_GSTRINGS` with `string_set` set to `ETH_SS_STATS`,
175 and values via `ETHTOOL_GSTATS`. User space should use `ETHTOOL_GDRVINFO`
194 Some drivers expose extra statistics via `debugfs`.
207 via `.ndo_get_stats64`. Reporting such standard stats via ethtool
[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/driver-api/ |
| D | vfio-pci-device-specific-driver-acceptance.rst | 21 accessible via the vfio-pci base driver. Authors of such drivers
22 should be diligent not to create exploitable interfaces via these
26 New driver submissions are therefore requested to have approval via
32 available to the user via vfio-pci, what safeguards exist to validate
|
| /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/devicetree/bindings/display/ |
| D | via,vt8500-fb.txt | 1 VIA VT8500 Framebuffer
5 - compatible : "via,vt8500-fb"
16 compatible = "via,vt8500-fb";
|
| /Documentation/virt/hyperv/ |
| D | clocks.rst | 10 clocksource and clockevents via the standard arm_arch_timer.c
26 also provides access to the virtualized TSC via the RDTSC and
30 to the guest VM via a synthetic MSR. Hyper-V initialization code
37 The Hyper-V synthetic system clock can be read via a synthetic MSR,
55 clock implemented via the shared page (identified as
58 The Hyper-V synthetic system clock is available to user space via
|
| /Documentation/devicetree/bindings/net/wireless/ |
| D | ti,wlcore.yaml | 13 The wl12xx/wl18xx chips can be connected via SPI or via SDIO.
36 This is required when connected via SPI, and optional when connected via
51 chip. This is required when connected via SPI.
|
12345678910>>...52