Searched +full:usb +full:- +full:c (Results 1 – 25 of 236) sorted by relevance
12345678910
| /Documentation/ABI/testing/ |
| D | sysfs-driver-typec-displayport | 6 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 …]
|
| D | sysfs-class-usb_role | 5 Place in sysfs for USB Role Switches. USB Role Switch is a
6 device that can select the data role (host or device) for USB
14 requesting role swapping with non-USB Type-C ports. With USB
15 Type-C ports, the ABI defined for USB Type-C connector class
19 - none
20 - host
21 - device
27 Optional symlink to the USB Type-C connector.
|
| D | sysfs-class-typec | 1 USB Type-C port devices (eg. /sys/class/typec/port0/)
7 The supported USB data roles. This attribute can be used for
47 dual (The port will behave as dual-role-data and
48 dual-role-power port)
57 when both the port and the partner support USB Power Delivery.
66 - "no" when the port is not the VCONN Source
67 - "yes" when the port is the VCONN Source
74 power operation mode means current level for VBUS. In case USB
80 - default
81 - 1.5A
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | realtek,rtd-type-c.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/usb/realtek,rtd-type-c.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Realtek DHC RTD SoCs USB Type-C Connector detection
11 - Stanley Chang <stanley_chang@realtek.com>
14 Realtek digital home center (DHC) RTD series SoCs include a type c module.
15 This module is able to detect the state of type c connector.
20 - realtek,rtd1295-type-c
21 - realtek,rtd1312c-type-c
[all …]
|
| D | richtek,rt1719.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/usb/richtek,rt1719.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Richtek RT1719 sink-only Type-C PD controller
10 - ChiYuan Huang <cy_huang@richtek.com>
13 The RT1719 is a sink-only USB Type-C controller that complies with the latest
14 USB Type-C and PD standards. It does the USB Type-C detection including attach
15 and orientation. It integrates the physical layer of the USB BMC power
17 support for alternative interfaces of the Type-C specification.
[all …]
|
| D | willsemi,wusb3801.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/willsemi,wusb3801.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: WUSB3801 Type-C port controller
10 The Will Semiconductor WUSB3801 is a USB Type-C port controller which
12 compatible with the USB Type-C Cable and Connector Specification v1.2.
15 - Samuel Holland <samuel@sholland.org>
20 - willsemi,wusb3801
30 $ref: ../connector/usb-connector.yaml#
[all …]
|
| D | richtek,rt1711h.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/richtek,rt1711h.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Richtek RT1711H Type-C Port Switch and Power Delivery controller
10 - Gene Chen <gene_chen@richtek.com>
13 The RT1711H is a USB Type-C controller that complies with the latest
14 USB Type-C and PD standards. It does the USB Type-C detection including attach
15 and orientation. It integrates the physical layer of the USB BMC power
17 support for alternative interfaces of the Type-C specification.
[all …]
|
| D | st,typec-stm32g0.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/st,typec-stm32g0.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: STMicroelectronics STM32G0 USB Type-C PD controller
10 The STM32G0 MCU can be programmed to control Type-C connector(s) through I2C
15 - Fabrice Gasnier <fabrice.gasnier@foss.st.com>
19 const: st,stm32g0-typec
29 $ref: /schemas/connector/usb-connector.yaml#
32 firmware-name:
[all …]
|
| D | maxim,max33359.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/maxim,max33359.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Maxim TCPCI Type-C PD controller
10 - Badhri Jagan Sridharan <badhri@google.com>
12 description: Maxim TCPCI Type-C PD controller
17 - maxim,max33359
27 $ref: ../connector/usb-connector.yaml#
29 Properties for usb c connector.
[all …]
|
| D | mediatek,mt6360-tcpc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/mediatek,mt6360-tcpc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Mediatek MT6360 Type-C Port Switch and Power Delivery controller
10 - ChiYuan Huang <cy_huang@richtek.com>
13 Mediatek MT6360 is a multi-functional device. It integrates charger, ADC, flash, RGB indicators,
15 This document only describes MT6360 Type-C Port Switch and Power Delivery controller.
20 - mediatek,mt6360-tcpc
25 interrupt-names:
[all …]
|
| D | qcom,pmic-typec.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/qcom,pmic-typec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm PMIC based USB Type-C block
10 - Bryan O'Donoghue <bryan.odonoghue@linaro.org>
13 Qualcomm PMIC Type-C block
18 - enum:
19 - qcom,pmi632-typec
20 - qcom,pm8150b-typec
[all …]
|
| D | analogix,anx7411.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/usb/analogix,anx7411.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Analogix ANX7411 Type-C controller
10 - Xin Ji <xji@analogixsemi.com>
15 - analogix,anx7411
25 $ref: ../connector/usb-connector.yaml
29 const: usb-c-connector
32 - compatible
[all …]
|
| D | qcom,wcd939x-usbss.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/usb/qcom,wcd939x-usbss.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm WCD9380/WCD9385 USB SubSystem Altmode/Analog Audio Switch
10 - Neil Armstrong <neil.armstrong@linaro.org>
13 Qualcomm WCD9390/WCD9395 is a standalone Hi-Fi audio codec IC with a
14 functionally separate USB SubSystem for Altmode/Analog Audio Switch
17 USB-C Mux subsystems are external to the IC, thus requiring DT port-endpoint
18 graph description to handle USB-C altmode & orientation switching for Audio
[all …]
|
| D | fcs,fusb302.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/usb/fcs,fusb302.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Fairchild FUSB302 Type-C Port controller
10 - Rob Herring <robh@kernel.org>
22 vbus-supply:
27 $ref: /schemas/connector/usb-connector.yaml#
31 - compatible
32 - reg
[all …]
|
| D | st,stusb160x.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/usb/st,stusb160x.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: STMicroelectronics STUSB160x Type-C controller
10 - Amelie Delaunay <amelie.delaunay@foss.st.com>
15 - st,stusb1600
23 vdd-supply:
24 description: main power supply (4.1V-22V)
26 vsys-supply:
[all …]
|
| /Documentation/driver-api/usb/ |
| 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_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_bus.rst | 2 API for USB Type-C Alternate Mode drivers
6 ------------
9 Messages (VDM) as defined in USB Type-C and USB Power Delivery Specifications.
13 USB Type-C bus allows binding a driver to the discovered partner alternate
16 :ref:`USB Type-C Connector Class <typec>` provides a device for every alternate
36 ------
43 space (See Documentation/ABI/testing/sysfs-class-typec). Port drivers should not
46 ``->vdm`` is the most important callback in the operation callbacks vector. It
49 the SVID specific commands to each other using :c:func:`typec_altmode_vdm()`.
53 needs to notify the bus using :c:func:`typec_altmode_notify()`. The driver
[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 | URB.rst | 1 .. _usb-urb:
3 USB Request Block (URB)
6 :Revised: 2000-Dec-05
7 :Again: 2002-Jul-06
8 :Again: 2005-Sep-19
9 :Again: 2017-Mar-29
14 The USB subsystem now has a substantial section at :ref:`usb-hostside-api`
24 called USB Request Block, or URB for short.
26 - An URB consists of all relevant information to execute any USB transaction
29 - Execution of an URB is inherently an asynchronous operation, i.e. the
[all …]
|
| /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 …]
|
| /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 …]
|
| /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 …]
|
| /Documentation/admin-guide/media/ |
| D | dvb-usb-dvbsky-cardlist.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 dvb-usb-dvbsky cards list
8 .. flat-table::
9 :header-rows: 1
11 :stub-columns: 0
13 * - Card name
14 - USB IDs
15 * - DVBSky S960/S860
16 - 0572:6831
17 * - DVBSky S960CI
[all …]
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,pmic-glink.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/qcom/qcom,pmic-glink.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm PMIC GLINK firmware interface for battery management, USB
8 Type-C and other things.
11 - Bjorn Andersson <andersson@kernel.org>
15 platforms and implement USB Type-C handling and battery management. This
18 particularly the USB Type-C controllers relationship with USB and DisplayPort
24 - items:
[all …]
|
12345678910