| /kernel/linux/linux-4.19/drivers/usb/typec/ |
| D | Kconfig | 3 tristate "USB Type-C Support"
5 USB Type-C Specification defines a cable and connector for USB where
7 be Type-A plug on one end of the cable and Type-B plug on the other.
8 Determination of the host-to-device relationship happens through a
9 specific Configuration Channel (CC) which goes through the USB Type-C
11 Accessory Modes - Analog Audio and Debug - and if USB Power Delivery
13 something else then USB communication.
15 USB Power Delivery Specification defines a protocol that can be used
17 partners. USB Power Delivery allows higher voltages then the normal
18 5V, up to 20V, and current up to 5A over the cable. The USB Power
[all …]
|
| D | mux.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * USB Type-C Multiplexer/DeMultiplexer Switch support
5 * Copyright (C) 2018 Intel Corporation
14 #include <linux/usb/typec_mux.h>
27 if (!strcmp(con->endpoint[ep], dev_name(sw->dev))) in typec_switch_match()
34 return ERR_PTR(-EPROBE_DEFER); in typec_switch_match()
38 * typec_switch_get - Find USB Type-C orientation switch
43 * ERR_PTR(-EPROBE_DEFER) when a connection was found but the switch
51 sw = device_connection_find_match(dev, "typec-switch", NULL, in typec_switch_get()
54 WARN_ON(!try_module_get(sw->dev->driver->owner)); in typec_switch_get()
[all …]
|
| /kernel/linux/linux-5.10/drivers/usb/typec/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Support"
6 USB Type-C Specification defines a cable and connector for USB where
8 be Type-A plug on one end of the cable and Type-B plug on the other.
9 Determination of the host-to-device relationship happens through a
10 specific Configuration Channel (CC) which goes through the USB Type-C
12 Accessory Modes - Analog Audio and Debug - and if USB Power Delivery
14 something else then USB communication.
16 USB Power Delivery Specification defines a protocol that can be used
18 partners. USB Power Delivery allows higher voltages then the normal
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/connector/ |
| D | usb-connector.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/connector/usb-connector.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: USB Connector
10 - Rob Herring <robh@kernel.org>
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.
20 - enum:
[all …]
|
| /kernel/linux/linux-5.10/drivers/usb/typec/tcpm/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Port Controller Manager"
5 depends on USB
9 The Type-C Port Controller Manager provides a USB PD and USB Type-C
10 state machine for use with Type-C Port Controllers.
15 tristate "Type-C Port Controller Interface driver"
19 Type-C Port Controller driver for TCPCI-compliant controller.
24 tristate "Richtek RT1711H Type-C chip driver"
26 Richtek RT1711H Type-C chip driver that works with
27 Type-C Port Controller Manager to provide USB PD and USB
[all …]
|
| /kernel/linux/linux-4.19/Documentation/driver-api/usb/ |
| D | writing_usb_driver.rst | 1 .. _writing-usb-driver:
4 Writing USB Device Drivers
7 :Author: Greg Kroah-Hartman
12 The Linux USB subsystem has grown from supporting only two different
15 almost all USB class devices (standard types of devices like keyboards,
16 mice, modems, printers and speakers) and an ever-growing number of
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
22 almost all vendor-specific devices. Each vendor decides to implement a
[all …]
|
| D | typec.rst | 2 USB Type-C connector class
6 ------------
8 The typec class is meant for describing the USB Type-C ports in a system to the
13 The platforms are expected to register every USB Type-C port they have with the
14 class. In a normal case the registration will be done by a USB Type-C or PD PHY
16 USB PD controller or even driver for Thunderbolt3 controller. This document
17 considers the component registering the USB Type-C ports with the class as "port
25 attributes are described in Documentation/ABI/testing/sysfs-class-typec.
28 --------------------
35 "port0-partner". Full path to the device would be
[all …]
|
| D | gadget.rst | 2 USB Gadget API for Linux
11 This document presents a Linux-USB "Gadget" kernel mode API, for use
12 within peripherals and other USB devices that embed Linux. It provides
17 - Supports USB 2.0, for high speed devices which can stream data at
20 - Handles devices with dozens of endpoints just as well as ones with
21 just two fixed-function ones. Gadget drivers can be written so
24 - Flexible enough to expose more complex USB device capabilities such
28 - USB "On-The-Go" (OTG) support, in conjunction with updates to the
29 Linux-USB host side.
31 - Sharing data structures and API models with the Linux-USB host side
[all …]
|
| D | writing_musb_glue_layer.rst | 10 The Linux MUSB subsystem is part of the larger Linux USB subsystem. It
11 provides support for embedded USB Device Controllers (UDC) that do not
15 Instead, these embedded UDC rely on the USB On-the-Go (OTG)
17 reference design used in most cases is the Multipoint USB Highspeed
18 Dual-Role Controller (MUSB HDRC) found in the Mentor Graphics Inventra™
21 As a self-taught exercise I have written an MUSB glue layer for the
24 ``drivers/usb/musb/jz4740.c``. In this documentation I will walk through the
25 basics of the ``jz4740.c`` glue layer, explaining the different pieces and
28 .. _musb-basics:
33 To get started on the topic, please read USB On-the-Go Basics (see
[all …]
|
| D | usb.rst | 1 .. _usb-hostside-api:
4 The Linux-USB Host Side API
7 Introduction to USB on Linux
10 A Universal Serial Bus (USB) is used to connect a host, such as a PC or
11 workstation, to a number of peripheral devices. USB uses a tree
14 support several such trees of USB devices, usually
15 a few USB 3.0 (5 GBit/s) or USB 3.1 (10 GBit/s) and some legacy
16 USB 2.0 (480 MBit/s) busses just in case.
18 That master/slave asymmetry was designed-in for a number of reasons, one
20 downstream or it does not matter with a type C plug (or they are built into the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| D | writing_usb_driver.rst | 1 .. _writing-usb-driver:
4 Writing USB Device Drivers
7 :Author: Greg Kroah-Hartman
12 The Linux USB subsystem has grown from supporting only two different
15 almost all USB class devices (standard types of devices like keyboards,
16 mice, modems, printers and speakers) and an ever-growing number of
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
22 almost all vendor-specific devices. Each vendor decides to implement a
[all …]
|
| D | typec.rst | 3 USB Type-C connector class
7 ------------
9 The typec class is meant for describing the USB Type-C ports in a system to the
14 The platforms are expected to register every USB Type-C port they have with the
15 class. In a normal case the registration will be done by a USB Type-C or PD PHY
17 USB PD controller or even driver for Thunderbolt3 controller. This document
18 considers the component registering the USB Type-C ports with the class as "port
26 attributes are described in Documentation/ABI/testing/sysfs-class-typec.
29 --------------------
36 "port0-partner". Full path to the device would be
[all …]
|
| D | writing_musb_glue_layer.rst | 10 The Linux MUSB subsystem is part of the larger Linux USB subsystem. It
11 provides support for embedded USB Device Controllers (UDC) that do not
15 Instead, these embedded UDC rely on the USB On-the-Go (OTG)
17 reference design used in most cases is the Multipoint USB Highspeed
18 Dual-Role Controller (MUSB HDRC) found in the Mentor Graphics Inventra™
21 As a self-taught exercise I have written an MUSB glue layer for the
24 ``drivers/usb/musb/jz4740.c``. In this documentation I will walk through the
25 basics of the ``jz4740.c`` glue layer, explaining the different pieces and
28 .. _musb-basics:
33 To get started on the topic, please read USB On-the-Go Basics (see
[all …]
|
| D | usb.rst | 1 .. _usb-hostside-api:
4 The Linux-USB Host Side API
7 Introduction to USB on Linux
10 A Universal Serial Bus (USB) is used to connect a host, such as a PC or
11 workstation, to a number of peripheral devices. USB uses a tree
14 support several such trees of USB devices, usually
15 a few USB 3.0 (5 GBit/s) or USB 3.1 (10 GBit/s) and some legacy
16 USB 2.0 (480 MBit/s) busses just in case.
18 That master/slave asymmetry was designed-in for a number of reasons, one
20 downstream or it does not matter with a type C plug (or they are built into the
[all …]
|
| D | gadget.rst | 2 USB Gadget API for Linux
11 This document presents a Linux-USB "Gadget" kernel mode API, for use
12 within peripherals and other USB devices that embed Linux. It provides
17 - Supports USB 2.0, for high speed devices which can stream data at
20 - Handles devices with dozens of endpoints just as well as ones with
21 just two fixed-function ones. Gadget drivers can be written so
24 - Flexible enough to expose more complex USB device capabilities such
28 - USB "On-The-Go" (OTG) support, in conjunction with updates to the
29 Linux-USB host side.
31 - Sharing data structures and API models with the Linux-USB host side
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/connector/ |
| D | usb-connector.txt | 1 USB Connector
4 USB connector node represents physical USB connector. It should be
5 a child of USB interface controller.
8 - compatible: describes type of the connector, must be one of:
9 "usb-a-connector",
10 "usb-b-connector",
11 "usb-c-connector".
14 - label: symbolic name for the connector,
15 - type: size of the connector, should be specified in case of USB-A, USB-B
16 non-fullsize connectors: "mini", "micro".
[all …]
|
| /kernel/linux/linux-4.19/Documentation/hid/ |
| D | hiddev.txt | 5 In addition to the normal input type HID devices, USB also uses the
11 To support these disparate requirements, the Linux USB system provides
15 normalised event interface - see Documentation/input/input.rst
21 usb.c ---> hid-core.c ----> hid-input.c ----> [keyboard/mouse/joystick/event]
24 --> hiddev.c ----> POWER / MONITOR CONTROL
26 In addition, other subsystems (apart from USB) can potentially feed
32 The hiddev interface is a char interface using the normal USB major,
35 mknod /dev/usb/hiddev0 c 180 96
36 mknod /dev/usb/hiddev1 c 180 97
37 mknod /dev/usb/hiddev2 c 180 98
[all …]
|
| /kernel/linux/linux-4.19/include/linux/usb/ |
| D | typec.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
8 /* USB Type-C Specification releases */
73 * struct usb_pd_identity - USB Power Delivery identity data
78 * USB power delivery Discover Identity command response data.
80 * REVISIT: This is USB Power Delivery specific information, so this structure
81 * probable belongs to USB Power Delivery header file once we have them.
93 * struct typec_altmode_desc - USB Type-C Alternate Mode Descriptor
96 * @vdo: VDO returned by Discover Modes USB PD command
131 * struct typec_plug_desc - USB Type-C Cable Plug Descriptor
135 * Represents USB Type-C Cable Plug.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | usb-cardlist.rst | 1 .. 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 …]
|
| /kernel/linux/linux-5.10/Documentation/hid/ |
| D | hiddev.rst | 8 In addition to the normal input type HID devices, USB also uses the
14 To support these disparate requirements, the Linux USB system provides
18 normalised event interface - see Documentation/input/input.rst
24 usb.c ---> hid-core.c ----> hid-input.c ----> [keyboard/mouse/joystick/event]
27 --> hiddev.c ----> POWER / MONITOR CONTROL
29 In addition, other subsystems (apart from USB) can potentially feed
36 The hiddev interface is a char interface using the normal USB major,
40 mknod /dev/usb/hiddev0 c 180 96
41 mknod /dev/usb/hiddev1 c 180 97
42 mknod /dev/usb/hiddev2 c 180 98
[all …]
|
| /kernel/linux/linux-5.10/include/linux/usb/ |
| D | typec.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
8 /* USB Type-C Specification releases */
76 * struct enter_usb_data - Enter_USB Message details
80 * @active_link_training is a flag that should be set with uni-directional SBRX
81 * communication, and left 0 with passive cables and with bi-directional SBRX
90 * struct usb_pd_identity - USB Power Delivery identity data
96 * USB power delivery Discover Identity command response data.
98 * REVISIT: This is USB Power Delivery specific information, so this structure
99 * probable belongs to USB Power Delivery header file once we have them.
112 * struct typec_altmode_desc - USB Type-C Alternate Mode Descriptor
[all …]
|
| /kernel/linux/linux-4.19/Documentation/usb/ |
| D | acm.txt | 2 (c) 1999 Vojtech Pavlik <vojtech@suse.cz>
4 ----------------------------------------------------------------------------
20 Temple Place, Suite 330, Boston, MA 02111-1307 USA
22 Should you need to contact me, the author, you can do so either by e-mail
23 - mail your message to <vojtech@suse.cz>, or by paper mail: Vojtech Pavlik,
31 The drivers/usb/class/cdc-acm.c drivers works with USB modems and USB ISDN terminal
33 Abstract Control Model (USB CDC ACM) specification.
49 Some cell phones also connect via USB. I know the following phones work:
59 uhci-hcd.ko ohci-hcd.ko or ehci-hcd.ko
60 cdc-acm.ko
[all …]
|
| /kernel/linux/linux-5.10/Documentation/usb/ |
| D | acm.rst | 5 Copyright (c) 1999 Vojtech Pavlik <vojtech@suse.cz>
23 Temple Place, Suite 330, Boston, MA 02111-1307 USA
25 Should you need to contact me, the author, you can do so either by e-mail -
34 The drivers/usb/class/cdc-acm.c drivers works with USB modems and USB ISDN terminal
36 Abstract Control Model (USB CDC ACM) specification.
40 - 3Com OfficeConnect 56k
41 - 3Com Voice FaxModem Pro
42 - 3Com Sportster
43 - MultiTech MultiModem 56k
44 - Zoom 2986L FaxModem
[all …]
|
| /kernel/linux/linux-5.10/drivers/staging/wlan-ng/ |
| D | prism2usb.c | 1 // SPDX-License-Identifier: GPL-2.0
2 #include "hfa384x_usb.c"
3 #include "prism2mgmt.c"
4 #include "prism2mib.c"
5 #include "prism2sta.c"
6 #include "prism2fw.c"
13 PRISM_DEV(0x04bb, 0x0922, "IOData AirPort WN-B11/USBS"),
14 PRISM_DEV(0x07aa, 0x0012, "Corega Wireless LAN USB Stick-11"),
15 PRISM_DEV(0x09aa, 0x3642, "Prism2.x 11Mbps WLAN USB Adapter"),
16 PRISM_DEV(0x1668, 0x0408, "Actiontec Prism2.5 11Mbps WLAN USB Adapter"),
[all …]
|
| /kernel/linux/linux-4.19/drivers/staging/wlan-ng/ |
| D | prism2usb.c | 1 // SPDX-License-Identifier: GPL-2.0
2 #include "hfa384x_usb.c"
3 #include "prism2mgmt.c"
4 #include "prism2mib.c"
5 #include "prism2sta.c"
6 #include "prism2fw.c"
13 PRISM_DEV(0x04bb, 0x0922, "IOData AirPort WN-B11/USBS"),
14 PRISM_DEV(0x07aa, 0x0012, "Corega Wireless LAN USB Stick-11"),
15 PRISM_DEV(0x09aa, 0x3642, "Prism2.x 11Mbps WLAN USB Adapter"),
16 PRISM_DEV(0x1668, 0x0408, "Actiontec Prism2.5 11Mbps WLAN USB Adapter"),
[all …]
|