Home
last modified time | relevance | path

Searched +full:usb +full:- +full:based (Results 1 – 25 of 136) sorted by relevance

123456

/Documentation/usb/
Draw-gadget.rst2 USB Raw Gadget
5 USB Raw Gadget is a gadget driver that gives userspace low-level control over
8 Like any other gadget driver, Raw Gadget implements USB devices via the
9 USB gadget API. Unlike most gadget drivers, Raw Gadget does not implement
10 any concrete USB functions itself but requires userspace to do that.
21 USB gadget layer for userspace. The key differences are:
23 1. Raw Gadget passes every USB request to userspace to get a response, while
24 GadgetFS responds to some USB requests internally based on the provided
28 2. Raw Gadget allows providing arbitrary data as responses to USB requests,
29 while GadgetFS performs sanity checks on the provided USB descriptors.
[all …]
Dlinux.inf1 ; Based on template INF file found at
2 ; <https://msdn.microsoft.com/en-us/library/ff570620.aspx>
6 ; <http://msdn.microsoft.com/en-us/cc300389.aspx#MLPL>.
12 ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
21 %LinuxDevice% = RNDIS.NT.5.1, USB\VID_0525&PID_a4a2, USB\VID_1d6b&PID_0104&MI_00
25 %LinuxDevice% = RNDIS.NT.5.1, USB\VID_0525&PID_a4a2, USB\VID_1d6b&PID_0104&MI_00
29 %LinuxDevice% = RNDIS.NT.5.1, USB\VID_0525&PID_a4a2, USB\VID_1d6b&PID_0104&MI_00
36 ; References the in-build Netrndis.inf
59 ; No sys copyfiles - the sys files are already in-build
61 ; We do not support XP SP1-, 2003 SP1-, ME, 9x.
[all …]
Dmtouchusb.rst8 - 0.3 - Created based off of scanner & INSTALL from the original touchscreen
10 - Amended for linux-2.4.18, then 2.4.19
12 - 0.5 - Complete rewrite using Linux Input in 2.6.3
15 - 1.4 - Multiple changes to support the EXII 5000UC and house cleaning
16 Changed reset from standard USB dev reset to vendor reset
19 Performed multiple successful tests with an EXII-5010UC
30 ------------------------------------------------------
32 USB Capacitive - Pearl Case 14-205 (Discontinued)
33 USB Capacitive - Black Case 14-124 (Discontinued)
34 USB Capacitive - No Case 14-206 (Discontinued)
[all …]
/Documentation/admin-guide/media/
Dtechnisat.rst1 .. SPDX-License-Identifier: GPL-2.0
13 -----------------------------
15 Important Notice: The driver does NOT support Technisat USB 2 devices!
19 .. code-block:: none
21 lspci -vvv for a PCI device (lsusb -vvv for an USB device) will show you for example:
29 -------------------
37 (except ``Simple tuner support`` for ATSC 3rd generation only -> see case 9 please).
41 - Main module part:
46 #) => ``Technisat/B2C2 Air/Sky/Cable2PC USB`` (USB 1.1 adapter)
50 - Frontend / Tuner / Demodulator module part:
[all …]
Ddvb-usb-dib0700-cardlist.rst1 .. SPDX-License-Identifier: GPL-2.0
3 dvb-usb-dib0700 cards list
8 .. flat-table::
9 :header-rows: 1
11 :stub-columns: 0
13 * - Card name
14 - USB IDs
15 * - ASUS My Cinema U3000 Mini DVBT Tuner
16 - 0b05:171f
17 * - ASUS My Cinema U3100 Mini DVBT Tuner
[all …]
Ddvb-usb-dtt200u-cardlist.rst1 .. SPDX-License-Identifier: GPL-2.0
3 dvb-usb-dtt200u cards list
8 .. flat-table::
9 :header-rows: 1
11 :stub-columns: 0
13 * - Card name
14 - USB IDs
15 * - WideView WT-220U PenType Receiver (Miglia)
16 - 18f3:0220
17 * - WideView WT-220U PenType Receiver (Typhoon/Freecom)
[all …]
Dusb-cardlist.rst1 .. SPDX-License-Identifier: GPL-2.0
3 USB drivers
6 The USB boards are identified by an identification called USB ID.
8 The ``lsusb`` command allows identifying the USB IDs::
18 via USB Video Class. Those cameras are automatically supported by the
19 ``uvc-driver``.
21 Older cameras and TV USB devices uses USB Vendor Classes: each vendor
23 card lists for such vendor-class devices.
25 While this is not as common as on PCI, sometimes the same USB ID is used
30 The current supported USB cards (not including staging drivers) are
[all …]
/Documentation/devicetree/bindings/net/
Dmarvell-bt-8xxx.txt1 Marvell 8897/8997 (sd8897/sd8997) bluetooth devices (SDIO or USB based)
2 ------
4 the btmrvl driver is used and when used on USB interface, the btusb driver is
9 - compatible : should be one of the following:
10 * "marvell,sd8897-bt" (for SDIO)
11 * "marvell,sd8997-bt" (for SDIO)
12 * "usb1286,204e" (for USB)
16 - marvell,cal-data: Calibration data downloaded to the device during
20 - marvell,wakeup-pin: It represents wakeup pin number of the bluetooth chip.
22 - marvell,wakeup-gap-ms: wakeup gap represents wakeup latency of the host
[all …]
Dmicrochip,lan78xx.txt8 - compatible: Should be one of "usb424,7800", "usb424,7801" or "usb424,7850".
14 - microchip,led-modes: a 0..4 element vector, with each element configuring
16 are defined in "include/dt-bindings/net/microchip-lan78xx.h".
20 /* Based on the configuration for a Raspberry Pi 3 B+ */
21 &usb {
22 usb-port@1 {
25 #address-cells = <1>;
26 #size-cells = <0>;
28 usb-port@1 {
31 #address-cells = <1>;
[all …]
/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,nsp.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
14 DDR3 memory, PCIE Gen-2, USB 2.0 and USB 3.0, serial and NAND flash,
18 - Ray Jui <rjui@broadcom.com>
19 - Scott Branden <sbranden@broadcom.com>
26 - description: BCM58522 based boards
28 - enum:
29 - brcm,bcm958522er
30 - const: brcm,bcm58522
[all …]
Dbrcm,hr2.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 are based on Broadcom's iProc SoC architecture and feature a single core Cortex
12 A9 ARM CPUs, DDR2/DDR3 memory, PCIe GEN-2, USB 2.0 and USB 3.0, serial and NAND
16 - Florian Fainelli <f.fainelli@gmail.com>
23 - enum:
24 - ubnt,unifi-switch8
25 - const: brcm,bcm53342
26 - const: brcm,hr2
/Documentation/ABI/testing/
Dsysfs-driver-eud6 USB Debugger(EUD). This enables and disables the
7 EUD based on a 1 or a 0 value. By enabling EUD,
8 the user is able to activate the mini-usb hub of
Dsysfs-bus-pci-drivers-ehci_hcd2 /sys/bus/usb/devices/usbN/../companion
7 PCI-based EHCI USB controllers (i.e., high-speed USB-2.0
9 "companion" full/low-speed USB-1.1 controllers. When a
10 high-speed device is plugged in, the connection is routed
11 to the EHCI controller; when a full- or low-speed device
15 Sometimes you want to force a high-speed device to connect
23 For example: To force the high-speed device attached to
26 echo 4 >/sys/bus/usb/devices/usb2/../companion
28 To return the port to high-speed operation::
30 echo -4 >/sys/bus/usb/devices/usb2/../companion
[all …]
Dsysfs-class-net-qmi9 framing from '802.3' to 'raw-ip'.
14 frames with an ethernet header over the USB link. The
15 netdev is a headerless p-t-p device in 'raw-ip' mode,
17 without any L2 header over the USB link.
23 firmware is configured for 'raw-ip' mode.
33 based network device, supported by recent Qualcomm based
50 created qmap mux based network device.
69 Set this to 'Y' to enable 'pass-through' mode, allowing packets
75 'Pass-through' mode can be enabled when the device is in
76 'raw-ip' mode only.
/Documentation/firmware-guide/acpi/
Dintel-pmc-mux.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Intel North Mux-Agent
10 North Mux-Agent is a function of the Intel PMC firmware that is supported on
11 most Intel based platforms that have the PMC microcontroller. It's used for
12 configuring the various USB Multiplexer/DeMultiplexers on the system. The
13 platforms that allow the mux-agent to be configured from the operating system
16 The North Mux-Agent (aka. Intel PMC Mux Control, or just mux-agent) driver
18 (drivers/platform/x86/intel_scu_ipc.c). The driver registers with the USB Type-C
19 Mux Class which allows the USB Type-C Controller and Interface drivers to
21 also registers with the USB Role Class in order to support both USB Host and
[all …]
/Documentation/devicetree/bindings/soc/qcom/
Dqcom,eud.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm Embedded USB Debugger
10 - Souradeep Chowdhury <quic_schowdhu@quicinc.com>
13 This binding is used to describe the Qualcomm Embedded USB Debugger, which is
14 mini USB-hub implemented on chip to support USB-based debug capabilities.
19 - enum:
20 - qcom,sc7280-eud
21 - const: qcom,eud
[all …]
/Documentation/sound/designs/
Dmidi-2.0.rst12 - Support of Universal MIDI Packet (UMP)
13 - Support of MIDI 2.0 protocol messages
14 - Transparent conversions between UMP and legacy MIDI 1.0 byte stream
15 - MIDI-CI for property and profile configurations
26 MIDI-CI is a high-level protocol that can talk with the MIDI device
31 the encoding/decoding of MIDI protocols on UMP, while MIDI-CI is
32 supported in user-space over the standard SysEx.
34 As of this writing, only USB MIDI device supports the UMP and Linux
62 Rawmidi Device with USB MIDI 2.0
65 When a device supports MIDI 2.0, the USB-audio driver probes and uses
[all …]
/Documentation/devicetree/bindings/usb/
Diproc-udc.txt1 Broadcom IPROC USB Device controller.
4 iProc family (Northstar2, Cygnus) of SoCs'. The UDC is based
9 - compatible: Add the compatibility strings for supported platforms.
10 For Broadcom NS2 platform, add "brcm,ns2-udc","brcm,iproc-udc".
11 For Broadcom Cygnus platform, add "brcm,cygnus-udc", "brcm,iproc-udc".
12 - reg: Offset and length of UDC register set
13 - interrupts: description of interrupt line
14 - phys: phandle to phy node.
17 udc_dwc: usb@664e0000 {
18 compatible = "brcm,ns2-udc", "brcm,iproc-udc";
Dmaxim,max3421.txt1 Maxim Integrated SPI-based USB 2.0 host controller MAX3421E
4 - compatible: Should be "maxim,max3421"
5 - spi-max-frequency: maximum frequency for this device must not exceed 26 MHz.
6 - reg: chip select number to which this device is connected.
7 - maxim,vbus-en-pin: <GPOUTx ACTIVE_LEVEL>
8 GPOUTx is the number (1-8) of the GPOUT pin of MAX3421E to drive Vbus.
10 - interrupts: the interrupt line description for the interrupt controller.
16 usb@0 {
19 maxim,vbus-en-pin = <3 1>;
20 spi-max-frequency = <26000000>;
[all …]
Dgpio-sbu-mux.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/usb/gpio-sbu-mux.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: GPIO-based SBU mux
10 - Bjorn Andersson <andersson@kernel.org>
13 In USB Type-C applications the SBU lines needs to be connected, disconnected
21 - enum:
22 - nxp,cbdtu02043
23 - onnn,fsusb43l10x
[all …]
/Documentation/devicetree/bindings/arm/
Dapple.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Hector Martin <marcan@marcan.st>
15 This currently includes devices based on the "M1" SoC:
17 - Mac mini (M1, 2020)
18 - MacBook Pro (13-inch, M1, 2020)
19 - MacBook Air (M1, 2020)
20 - iMac (24-inch, M1, 2021)
22 Devices based on the "M2" SoC:
[all …]
/Documentation/userspace-api/media/mediactl/
Dmedia-controller-intro.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _media-controller-intro:
8 Media devices increasingly handle multiple related functions. Many USB
10 video, or SoC camera interfaces also perform memory-to-memory operations
14 be modelled as separate devices. A USB camera with a microphone will be
16 The devices' relationships (when using a webcam, end-users shouldn't
17 have to manually select the associated USB microphone), while not made
30 applications really require based on limited information, thereby
/Documentation/devicetree/bindings/platform/
Dlenovo,yoga-c630-ec.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/platform/lenovo,yoga-c630-ec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bjorn Andersson <andersson@kernel.org>
13 The Qualcomm Snapdragon-based Lenovo Yoga C630 has an Embedded Controller
14 (EC) which handles things such as battery and USB Type-C. This binding
19 const: lenovo,yoga-c630-ec
24 '#address-cells':
27 '#size-cells':
[all …]
/Documentation/devicetree/bindings/misc/
Dge-achc.yaml1 # SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
5 ---
6 $id: http://devicetree.org/schemas/misc/ge-achc.yaml#
7 $schema: http://devicetree.org/meta-schemas/core.yaml#
9 title: GE Healthcare USB Management Controller
12 A device which handles data acquisition from compatible USB based peripherals.
15 Note: This device does not expose the peripherals as USB devices.
18 - Sebastian Reichel <sre@kernel.org>
23 - const: ge,achc
24 - const: nxp,kinetis-k20
[all …]
/Documentation/fb/
Dudlfb.rst5 This is a driver for DisplayLink USB 2.0 era graphics chips.
9 USB wire. That hardware framebuffer is able to drive the VGA, DVI, or HDMI
15 pixels line-by-line via USB bulk transfers.
18 does not require any acks - the effect is very low latency that
20 non-gaming and non-video applications.
23 setting is very flexible - able to set nearly arbitrary modes from any timing.
25 Advantages of USB graphics in general:
27 * Ability to add a nearly arbitrary number of displays to any USB 2.0
29 (FB_MAX is currently 32). Of course, all USB devices on the same
30 host controller share the same 480Mbs USB 2.0 interface.
[all …]

123456