Home
last modified time | relevance | path

Searched full:usb (Results 1 – 25 of 758) sorted by relevance

12345678910>>...31

/Documentation/admin-guide/media/
Dusb-cardlist.rst3 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
21 Older cameras and TV USB devices uses USB Vendor Classes: each vendor
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
37 for cameras not supported by the USB Video Class (UVC) driver,
45 b2c2-flexcop-usb Technisat/B2C2 Air/Sky/Cable2PC USB
46 cx231xx Conexant cx231xx USB video capture
[all …]
/Documentation/devicetree/bindings/usb/
Dchipidea,usb2-imx.yaml4 $id: http://devicetree.org/schemas/usb/chipidea,usb2-imx.yaml#
7 title: NXP USB2 ChipIdea USB controller
16 - fsl,imx27-usb
19 - fsl,imx23-usb
20 - fsl,imx25-usb
21 - fsl,imx28-usb
22 - fsl,imx35-usb
23 - fsl,imx50-usb
24 - fsl,imx51-usb
25 - fsl,imx53-usb
[all …]
Ddwc2.yaml4 $id: http://devicetree.org/schemas/usb/dwc2.yaml#
7 title: DesignWare HS OTG USB 2.0 controller
13 - $ref: usb-drd.yaml#
14 - $ref: usb-hcd.yaml#
19 - const: brcm,bcm2835-usb
20 - const: hisilicon,hi6220-usb
29 - const: rockchip,rk3066-usb
33 - rockchip,px30-usb
34 - rockchip,rk3036-usb
35 - rockchip,rk3128-usb
[all …]
Dtwlxxxx-usb.txt1 USB COMPARATOR OF TWL CHIPS
3 TWL6030 USB COMPARATOR
4 - compatible : Should be "ti,twl6030-usb"
8 usb interrupt number that raises VBUS interrupts when the controller has to
10 - usb-supply : phandle to the regulator device tree node. It should be vusb
13 twl6030-usb {
14 compatible = "ti,twl6030-usb";
19 &twl6030-usb {
20 usb-supply = <&vusb>;
23 TWL4030 USB PHY AND COMPARATOR
[all …]
Dusb-drd.yaml4 $id: http://devicetree.org/schemas/usb/usb-drd.yaml#
7 title: Generic USB OTG Controller
15 Tells usb driver the release number of the OTG and EH supplement with
25 Tells Dual-Role USB controllers that we want to work on a particular
26 mode. In case this attribute isn't passed via DT, USB DRD controllers
51 usb-role-switch:
53 Indicates that the device is capable of assigning the USB data role
54 (USB host or USB device) for a given USB connector, such as Type-C,
55 Type-B(micro). See connector/usb-connector.yaml.
59 Indicates if usb-role-switch is enabled, the device default operation
[all …]
Dam33xx-usb.txt3 - compatible: ti,am33xx-usb
8 at least a control module node, USB node and a PHY node. The second USB
13 - compatible: ti,am335x-usb-ctrl-module
14 - reg: offset and length of the "USB control registers" in the "Control
15 Module" block. A second offset and length for the USB wake up control
17 - reg-names: "phy_ctrl" for the "USB control registers" and "wakeup" for
18 the USB wake up control register.
20 USB PHY
22 compatible: ti,am335x-usb-phy
23 reg: offset and length of the "USB PHY" register space
[all …]
Ds3c2410-usb.txt1 Samsung S3C2410 and compatible SoC USB controller
6 - compatible: should be "samsung,s3c2410-ohci" for USB host controller
8 - interrupts: interrupt number for the USB OHCI controller
11 "usb-bus-host" for the USB bus clock
12 "usb-host" for the USB host clock
21 clock-names = "usb-bus-host", "usb-host";
Dusb.yaml4 $id: http://devicetree.org/schemas/usb/usb.yaml#
7 title: Generic USB Controller
16 pattern: "^usb(@.*)?"
20 List of all the USB PHYs on this HCD
24 Name specifier for the USB PHY
26 usb-phy:
31 List of all the USB PHYs on this HCD to be accepted by the legacy USB
37 Tells USB controllers that we want to configure the core to support a
41 selected. In case this isn't passed via DT, USB controllers should
48 Tells USB controllers we want to work up to a certain speed. In case this
[all …]
/Documentation/ABI/testing/
Dsysfs-bus-usb1 What: /sys/bus/usb/devices/<INTERFACE>/authorized
9 by writing INTERFACE to /sys/bus/usb/drivers_probe
15 What: /sys/bus/usb/devices/usbX/interface_authorized_default
22 What: /sys/bus/usb/device/.../authorized
29 USB devices are authorized.
31 What: /sys/bus/usb/drivers/.../new_id
33 Contact: linux-usb@vger.kernel.org
36 dynamically add a new device ID to a USB device driver.
48 # echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id
53 # echo "0458 7045 0 0458 704c" > /sys/bus/usb/drivers/foo/new_id
[all …]
/Documentation/usb/
Dusb-help.rst2 USB references
7 For USB help other than the readme files that are located in
8 `Documentation/usb/*`, see the following:
10 - Linux-USB project: http://www.linux-usb.org
11 mirrors at http://usb.in.tum.de/linux-usb/
12 and http://it.linux-usb.org
13 - Linux USB Guide: http://linux-usb.sourceforge.net
14 - Linux-USB device overview (working devices and drivers):
15 http://www.qbik.ch/usb/devices/
17 The Linux-USB mailing list is at linux-usb@vger.kernel.org
Dauthorization.rst2 Authorizing (or not) your USB devices to connect to the system
7 This feature allows you to control if a USB device can be used (or
9 of USB devices, fully controlled by user space.
11 As of now, when a USB device is connected it is configured and
21 $ echo 1 > /sys/bus/usb/devices/DEVICE/authorized
25 $ echo 0 > /sys/bus/usb/devices/DEVICE/authorized
30 $ echo 0 > /sys/bus/usb/devices/usbX/authorized_default
34 $ echo 1 > /sys/bus/usb/devices/usbX/authorized_default
36 By default, all USB devices are authorized. Writing "2" to the
38 only devices connected to internal USB ports.
[all …]
DCREDITS1 Credits for the Simple Linux USB Driver:
31 Linux USB driver effort and writing much of the larger uusbd driver.
34 The NetBSD & FreeBSD USB developers. For being on the Linux USB list
42 of Linux USB / UUSBD:
48 - USAR Systems provided us with one of their excellent USB
49 Evaluation Kits. It allows us to test the Linux-USB driver
50 for compliance with the latest USB specification. USAR
58 built-in USB support. Cherry is one of the biggest keyboard
62 PCI-to-USB Controller Board to test the OHCI implementation.
69 It was almost impossible to get a PC backplate USB connector
[all …]
/Documentation/devicetree/bindings/net/
Dmicrochip,lan95xx.yaml7 title: Microchip SMSC9500/LAN9530/LAN9730 USB Ethernet Controllers
13 Device tree properties for hard wired SMSC95xx compatible USB Ethernet
23 - usb424,9500 # SMSC9500 USB Ethernet Device
24 - usb424,9505 # SMSC9505 USB Ethernet Device
25 - usb424,9530 # SMSC LAN9530 USB Ethernet Device
26 - usb424,9730 # SMSC LAN9730 USB Ethernet Device
27 - usb424,9900 # SMSC9500 USB Ethernet Device (SAL10)
28 - usb424,9901 # SMSC9505 USB Ethernet Device (SAL10)
29 - usb424,9902 # SMSC9500A USB Ethernet Device (SAL10)
30 - usb424,9903 # SMSC9505A USB Ethernet Device (SAL10)
[all …]
/Documentation/devicetree/bindings/phy/
Drenesas,rcar-gen2-usb-phy.yaml4 $id: http://devicetree.org/schemas/phy/renesas,rcar-gen2-usb-phy.yaml#
7 title: Renesas R-Car Gen2 USB PHY
16 - renesas,usb-phy-r8a7742 # RZ/G1H
17 - renesas,usb-phy-r8a7743 # RZ/G1M
18 - renesas,usb-phy-r8a7744 # RZ/G1N
19 - renesas,usb-phy-r8a7745 # RZ/G1E
20 - renesas,usb-phy-r8a77470 # RZ/G1C
21 - renesas,usb-phy-r8a7790 # R-Car H2
22 - renesas,usb-phy-r8a7791 # R-Car M2-W
23 - renesas,usb-phy-r8a7794 # R-Car E2
[all …]
Drealtek,usb2phy.yaml8 title: Realtek DHC SoCs USB 2.0 PHY
14 Realtek USB 2.0 PHY support the digital home center (DHC) RTD series SoCs.
15 The USB 2.0 PHY driver is designed to support the XHCI controller. The SoCs
19 RTD1295/RTD1619 SoCs USB
20 The USB architecture includes three XHCI controllers.
21 Each XHCI maps to one USB 2.0 PHY and map one USB 3.0 PHY on some
29 RTD1395 SoCs USB
30 The USB architecture includes two XHCI controllers.
31 The controller#0 has one USB 2.0 PHY. The controller#1 includes two USB 2.0
37 RTD1319/RTD1619b SoCs USB
[all …]
Dphy-da8xx-usb.txt1 TI DA8xx/OMAP-L1xx/AM18xx USB PHY
4 - compatible: must be "ti,da830-usb-phy".
7 This device controls the PHY for both the USB 1.1 OHCI and USB 2.0 OTG
9 the USB 2.0 phy device and index 1 for the USB 1.1 phy device.
21 usb_phy: usb-phy {
22 compatible = "ti,da830-usb-phy";
26 usb20: usb@200000 {
31 phy-names = "usb-phy";
34 usb11: usb@225000 {
39 phy-names = "usb-phy";
Dbrcm,stingray-usb-phy.txt1 Broadcom Stingray USB PHY
5 - "brcm,sr-usb-combo-phy" is combo PHY has two PHYs, one SS and one HS.
6 - "brcm,sr-usb-hs-phy" is a single HS PHY.
9 - Must be 1 for brcm,sr-usb-combo-phy as it expects one argument to indicate
11 - Must be 0 for brcm,sr-usb-hs-phy.
16 usbphy0: usb-phy@0 {
17 compatible = "brcm,sr-usb-combo-phy";
22 usbphy1: usb-phy@10000 {
23 compatible = "brcm,sr-usb-combo-phy";
28 usbphy2: usb-phy@20000 {
[all …]
Dqcom,usb-hs-phy.yaml4 $id: http://devicetree.org/schemas/phy/qcom,usb-hs-phy.yaml#
7 title: Qualcomm's USB HS PHY
17 - qcom,usb-hs-phy-apq8064
18 - qcom,usb-hs-phy-msm8660
19 - qcom,usb-hs-phy-msm8960
43 - qcom,usb-hs-phy-apq8064
44 - qcom,usb-hs-phy-msm8226
45 - qcom,usb-hs-phy-msm8660
46 - qcom,usb-hs-phy-msm8916
47 - qcom,usb-hs-phy-msm8960
[all …]
/Documentation/devicetree/bindings/dma/
Drenesas,usb-dmac.yaml4 $id: http://devicetree.org/schemas/dma/renesas,usb-dmac.yaml#
7 title: Renesas USB DMA Controller
19 - renesas,r8a7742-usb-dmac # RZ/G1H
20 - renesas,r8a7743-usb-dmac # RZ/G1M
21 - renesas,r8a7744-usb-dmac # RZ/G1N
22 - renesas,r8a7745-usb-dmac # RZ/G1E
23 - renesas,r8a77470-usb-dmac # RZ/G1C
24 - renesas,r8a774a1-usb-dmac # RZ/G2M
25 - renesas,r8a774b1-usb-dmac # RZ/G2N
26 - renesas,r8a774c0-usb-dmac # RZ/G2E
[all …]
/Documentation/driver-api/usb/
Dwriting_usb_driver.rst1 .. _writing-usb-driver:
4 Writing USB Device Drivers
12 The Linux USB subsystem has grown from supporting only two different
15 almost all USB class devices (standard types of devices like keyboards,
17 vendor-specific devices (such as USB to serial converters, digital
19 different USB devices currently supported, see Resources.
21 The remaining kinds of USB devices that do not have support on Linux are
24 needs to be created. Some vendors are open with their USB protocols and
30 have written a generic USB driver skeleton, modelled after the
32 network drivers have been based. This USB skeleton can be found at
[all …]
Dusb3-debug-port.rst19 3) have a USB 3.0 super-speed A-to-A debugging cable.
31 the USB framework and provides the equivalent of a very high
56 USB subsystem by adding below kernel boot parameter::
61 port to a USB port (root port or port of any external hub) on
63 should be a USB 3.0 super-speed A-to-A debugging cable.
75 [ 1815.983374] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
76 [ 1815.999595] usb 4-3: LPM exit latency is zeroed, disabling LPM.
77 [ 1815.999899] usb 4-3: New USB device found, idVendor=1d6b, idProduct=0004
78 [ 1815.999902] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
79 [ 1815.999903] usb 4-3: Product: Remote GDB
[all …]
/Documentation/devicetree/bindings/extcon/
Dextcon-palmas.txt3 PALMAS USB COMPARATOR
6 * "ti,palmas-usb-vid".
7 * "ti,twl6035-usb-vid".
8 * "ti,palmas-usb" (DEPRECATED - use "ti,palmas-usb-vid").
9 * "ti,twl6035-usb" (DEPRECATED - use "ti,twl6035-usb-vid").
19 palmas-usb {
20 compatible = "ti,twl6035-usb", "ti,palmas-usb";
/Documentation/devicetree/bindings/connector/
Dusb-connector.yaml4 $id: http://devicetree.org/schemas/connector/usb-connector.yaml#
7 title: USB Connector
13 A USB connector node represents a physical USB connector. It should be a child
14 of a USB interface controller or a separate node when it is attached to both
15 MUX and USB interface controller.
21 - usb-a-connector
22 - usb-b-connector
23 - usb-c-connector
26 - const: gpio-usb-b-connector
27 - const: usb-b-connector
[all …]
/Documentation/devicetree/bindings/power/supply/
Dx-powers,axp20x-usb-power-supply.yaml4 $id: http://devicetree.org/schemas/power/supply/x-powers,axp20x-usb-power-supply.yaml#
7 title: AXP20x USB power-supply
22 - x-powers,axp192-usb-power-supply
23 - x-powers,axp202-usb-power-supply
24 - x-powers,axp221-usb-power-supply
25 - x-powers,axp223-usb-power-supply
26 - x-powers,axp717-usb-power-supply
27 - x-powers,axp813-usb-power-supply
29 - const: x-powers,axp803-usb-power-supply
30 - const: x-powers,axp813-usb-power-supply
[all …]
/Documentation/ABI/stable/
Dsysfs-driver-usb-usbtmc1 What: /sys/bus/usb/drivers/usbtmc/*/interface_capabilities
2 What: /sys/bus/usb/drivers/usbtmc/*/device_capabilities
6 These files show the various USB TMC capabilities as described
8 can be found in the USB TMC documents from the USB-IF entitled
15 What: /sys/bus/usb/drivers/usbtmc/*/usb488_interface_capabilities
16 What: /sys/bus/usb/drivers/usbtmc/*/usb488_device_capabilities
20 These files show the various USB TMC capabilities as described
22 can be found in the USB TMC documents from the USB-IF entitled

12345678910>>...31