Home
last modified time | relevance | path

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

12345678910>>...45

/kernel/linux/linux-5.10/drivers/usb/typec/
DKconfig1 # 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-6.6/drivers/usb/typec/
DKconfig1 # 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-6.6/drivers/usb/typec/tcpm/
DKconfig1 # 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-6.6/Documentation/devicetree/bindings/connector/
Dusb-connector.yaml1 # 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/Documentation/devicetree/bindings/connector/
Dusb-connector.yaml1 # 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/
DKconfig1 # 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-5.10/Documentation/driver-api/usb/
Dwriting_usb_driver.rst1 .. _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 …]
Dtypec.rst3 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 …]
Dwriting_musb_glue_layer.rst10 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 …]
Dusb.rst1 .. _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-6.6/Documentation/driver-api/usb/
Dwriting_usb_driver.rst1 .. _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 …]
Dtypec.rst3 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 …]
Dusb.rst1 .. _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 …]
Dwriting_musb_glue_layer.rst10 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 …]
/kernel/linux/linux-6.6/Documentation/admin-guide/media/
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 …]
/kernel/linux/linux-6.6/drivers/extcon/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
11 host USB ports. Many of 30-pin connectors including PDMI are
25 tristate "X-Power AXP288 EXTCON support"
29 Say Y here to enable support for USB peripheral detection
30 and USB MUX switching by X-Power AXP288 PMIC.
39 FSA9480 microUSB switch and accessory detector chip. The FSA9480 is a USB
41 I2C and enables USB data, stereo and mono audio, video, microphone
55 Say Y here to enable extcon support for USB OTG ports controlled by
85 Maxim MAX14577/77836. The MAX14577/77836 MUIC is a USB port accessory
89 tristate "Maxim MAX3355 USB OTG EXTCON Support"
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/media/
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 …]
/kernel/linux/linux-6.6/include/linux/usb/
Dtypec.h1 /* SPDX-License-Identifier: GPL-2.0 */
8 /* USB Type-C Specification releases */
90 * struct enter_usb_data - Enter_USB Message details
94 * @active_link_training is a flag that should be set with uni-directional SBRX
95 * communication, and left 0 with passive cables and with bi-directional SBRX
104 * struct usb_pd_identity - USB Power Delivery identity data
110 * USB power delivery Discover Identity command response data.
112 * REVISIT: This is USB Power Delivery specific information, so this structure
113 * probable belongs to USB Power Delivery header file once we have them.
126 * struct typec_altmode_desc - USB Type-C Alternate Mode Descriptor
[all …]
/kernel/linux/linux-6.6/Documentation/ABI/testing/
Dsysfs-driver-typec-displayport6 Valid values are USB, source and sink. Source means DisplayPort
14 USB [source] sink
18 Note. USB configuration does not equal to Exit Mode. It is
20 USB Type-C Standard. Functionally it equals to the situation
22 Documentation/ABI/testing/sysfs-bus-typec, and use file
29 VESA DisplayPort Alt Mode on USB Type-C Standard defines six
30 different pin assignments for USB Type-C connector that are
31 labeled A, B, C, D, E, and F. The supported pin assignments are
37 C [D]
44 Note. As of VESA DisplayPort Alt Mode on USB Type-C Standard
[all …]
/kernel/linux/linux-5.10/Documentation/hid/
Dhiddev.rst8 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-6.6/Documentation/hid/
Dhiddev.rst8 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/
Dtypec.h1 /* 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-5.10/Documentation/usb/
Dacm.rst5 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-6.6/Documentation/usb/
Dacm.rst5 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-6.6/drivers/usb/core/
Dfile.c1 // SPDX-License-Identifier: GPL-2.0
3 * drivers/usb/core/file.c
5 * (C) Copyright Linus Torvalds 1999
6 * (C) Copyright Johannes Erdfelt 1999-2001
7 * (C) Copyright Andreas Gal 1999
8 * (C) Copyright Gregory P. Smith 1999
9 * (C) Copyright Deti Fliegl 1999 (new USB architecture)
10 * (C) Copyright Randy Dunlap 2000
11 * (C) Copyright David Brownell 2000-2001 (kernel hotplug, usb_device_id,
13 * (C) Copyright Yggdrasil Computing, Inc. 2000
[all …]

12345678910>>...45