Searched +full:usb +full:- +full:c +full:- +full:connector (Results 1 – 25 of 575) sorted by relevance
12345678910>>...23
| /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-6.6/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-6.6/Documentation/devicetree/bindings/usb/ |
| 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
28 connector:
[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 | 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
27 connector:
29 $ref: /schemas/connector/usb-connector.yaml#
[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
23 connector:
25 $ref: ../connector/usb-connector.yaml
29 Properties for usb c connector.
[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
25 connector:
27 $ref: ../connector/usb-connector.yaml#
[all …]
|
| D | mediatek,musb.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
2 # Copyright (c) 2020 MediaTek
4 ---
5 $id: http://devicetree.org/schemas/usb/mediatek,musb.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Min Guo <min.guo@mediatek.com>
15 pattern: '^usb@[0-9a-f]+$'
19 - enum:
20 - mediatek,mt8516-musb
21 - mediatek,mt2701-musb
[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 …]
|
| D | richtek,rt1711h.txt | 4 - compatible : Must be "richtek,rt1711h".
5 - reg : Must be 0x4e, it's slave address of RT1711H.
6 - interrupts : <a b> where a is the interrupt number and b represents an
9 Required sub-node:
10 - connector: The "usb-c-connector" attached to the tcpci chip, the bindings
11 of connector node are specified in
12 Documentation/devicetree/bindings/connector/usb-connector.yaml
18 interrupt-parent = <&gpio26>;
21 usb_con: connector {
22 compatible = "usb-c-connector";
[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:
25 connector:
27 $ref: /schemas/connector/usb-connector.yaml#
31 - compatible
[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 | nxp,ptn5110.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/nxp,ptn5110.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Li Jun <jun.li@nxp.com>
22 connector:
24 $ref: /schemas/connector/usb-connector.yaml#
28 - compatible
29 - reg
30 - interrupts
[all …]
|
| D | mediatek,mtu3.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
2 # Copyright (c) 2020 MediaTek
4 ---
5 $id: http://devicetree.org/schemas/usb/mediatek,mtu3.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Chunfeng Yun <chunfeng.yun@mediatek.com>
14 - $ref: usb-drd.yaml
23 - enum:
24 - mediatek,mt2712-mtu3
25 - mediatek,mt8173-mtu3
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-driver-typec-displayport | 5 Shows the current DisplayPort configuration for the connector.
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]
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/usb/ |
| D | fcs,fusb302.txt | 1 Fairchild FUSB302 Type-C Port controllers
4 - compatible : "fcs,fusb302"
5 - reg : I2C slave address
6 - interrupts : Interrupt specifier
8 Required sub-node:
9 - connector : The "usb-c-connector" attached to the FUSB302 IC. The bindings
10 of the connector node are specified in:
12 Documentation/devicetree/bindings/connector/usb-connector.yaml
17 fusb302: typec-portc@54 {
20 interrupt-parent = <&nmi_intc>;
[all …]
|
| D | typec-tcpci.txt | 2 ---------------------------------------------
5 - compatible: should be set one of following:
6 - "nxp,ptn5110" for NXP USB PD TCPC PHY IC ptn5110.
8 - reg: the i2c slave address of typec port controller device.
9 - interrupt-parent: the phandle to the interrupt controller which provides
11 - interrupts: interrupt specification for tcpci alert.
13 Required sub-node:
14 - connector: The "usb-c-connector" attached to the tcpci chip, the bindings
15 of connector node are specified in
16 Documentation/devicetree/bindings/connector/usb-connector.yaml
[all …]
|
| D | richtek,rt1711h.txt | 4 - compatible : Must be "richtek,rt1711h".
5 - reg : Must be 0x4e, it's slave address of RT1711H.
6 - interrupts : <a b> where a is the interrupt number and b represents an
9 Required sub-node:
10 - connector: The "usb-c-connector" attached to the tcpci chip, the bindings
11 of connector node are specified in
12 Documentation/devicetree/bindings/connector/usb-connector.yaml
18 interrupt-parent = <&gpio26>;
21 usb_con: connector {
22 compatible = "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 DT bindings
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 …]
|
| /kernel/linux/linux-5.10/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 | 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()`.
52 in need to reconfigure the pins on the connector, the alternate mode driver
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /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
13 is supported, the Alternate Modes, where the connector is used for
14 something else then USB communication.
16 USB Power Delivery Specification defines a protocol that can be used
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-driver-typec-displayport | 5 Shows the current DisplayPort configuration for the connector.
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]
[all …]
|
12345678910>>...23