1 # SPDX-License-Identifier: GPL-2.0-only
4 $id: http://devicetree.org/schemas/connector/usb-connector.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
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.
26 - const: gpio-usb-b-connector
27 - const: usb-b-connector
30 - const: samsung,usb-connector-11pin
31 - const: usb-b-connector
34 description: Symbolic name for the connector.
37 description: Size of the connector, should be specified in case of
38 non-fullsize 'usb-a-connector' or 'usb-b-connector' compatible
40 $ref: /schemas/types.yaml#/definitions/string
47 description: Set this property if the USB device has its own power source.
50 # The following are optional properties for "usb-b-connector".
52 description: An input gpio for USB ID pin.
56 description: An input gpio for USB VBus pin, used to detect presence of
61 description: A phandle to the regulator for USB VBUS if needed when host
62 mode or dual role mode is supported.
63 Particularly, if use an output GPIO to control a VBUS regulator, should
64 model it as a regulator. See bindings/regulator/fixed-regulator.yaml
66 # The following are optional properties for "usb-c-connector".
68 description: Determines the power role that the Type C connector will
69 support. "dual" refers to Dual Role Port (DRP).
70 $ref: /schemas/types.yaml#/definitions/string
78 description: Preferred power role.
79 $ref: /schemas/types.yaml#/definitions/string
87 description: Data role if Type C connector supports USB data. "dual" refers
88 Dual Role Device (DRD).
89 $ref: /schemas/types.yaml#/definitions/string
97 description: Determines the power operation mode that the Type C connector
98 will support and will advertise through CC pins when it has no power
100 - "default" corresponds to default USB voltage and current defined by the
101 USB 2.0 and USB 3.2 specifications, 5V 500mA for USB 2.0 ports and
102 5V 900mA or 1500mA for USB 3.2 ports in single-lane or dual-lane
103 operation respectively.
104 - "1.5A" and "3.0A", 5V 1.5A and 5V 3.0A respectively, as defined in USB
105 Type-C Cable and Connector specification, when Power Delivery is not
107 $ref: /schemas/types.yaml#/definitions/string
114 description: Set this property if the Type-C connector has no power delivery support.
117 # The following are optional properties for "usb-c-connector" with power
120 description: An array of u32 with each entry providing supported power
121 source data object(PDO), the detailed bit definitions of PDO can be found
122 in "Universal Serial Bus Power Delivery Specification" chapter 6.4.1.2
123 Source_Capabilities Message, the order of each entry(PDO) should follow
124 the PD spec chapter 6.4.1. Required for power source and power dual role.
125 User can specify the source PDO array via PDO_FIXED/BATT/VAR/PPS_APDO()
126 defined in dt-bindings/usb/pd.h.
129 $ref: /schemas/types.yaml#/definitions/uint32-array
132 description: An array of u32 with each entry providing supported power sink
133 data object(PDO), the detailed bit definitions of PDO can be found in
134 "Universal Serial Bus Power Delivery Specification" chapter 6.4.1.3
135 Sink Capabilities Message, the order of each entry(PDO) should follow the
136 PD spec chapter 6.4.1. Required for power sink and power dual role. User
137 can specify the sink PDO array via PDO_FIXED/BATT/VAR/PPS_APDO() defined
138 in dt-bindings/usb/pd.h.
141 $ref: /schemas/types.yaml#/definitions/uint32-array
144 description: An array of u32 with each entry, a Vendor Defined Message Object (VDO),
145 providing additional information corresponding to the product, the detailed bit
146 definitions and the order of each VDO can be found in
147 "USB Power Delivery Specification Revision 3.0, Version 2.0 + ECNs 2020-12-10"
148 chapter 6.4.4.3.1 Discover Identity. User can specify the VDO array via
149 VDO_IDH/_CERT/_PRODUCT/_UFP/_DFP/_PCABLE/_ACABLE(1/2)/_VPD() defined in
150 dt-bindings/usb/pd.h.
153 $ref: /schemas/types.yaml#/definitions/uint32-array
156 description: An array of u32 with each entry, a Vendor Defined Message Object (VDO),
157 providing additional information corresponding to the product, the detailed bit
158 definitions and the order of each VDO can be found in
159 "USB Power Delivery Specification Revision 2.0, Version 1.3" chapter 6.4.4.3.1 Discover
160 Identity. User can specify the VDO array via VDO_IDH/_CERT/_PRODUCT/_CABLE/_AMA defined in
161 dt-bindings/usb/pd.h.
164 $ref: /schemas/types.yaml#/definitions/uint32-array
167 description: Sink required operating power in microwatt, if source can't
168 offer the power, Capability Mismatch is set. Required for power sink and
172 $ref: /schemas/graph.yaml#/properties/ports
173 description: OF graph bindings modeling any data bus to the connector
174 unless the bus is between parent node and the connector. Since a single
175 connector can have multiple data buses every bus has an assigned OF graph
176 port number as described below.
180 $ref: /schemas/graph.yaml#/properties/port
181 description: High Speed (HS), present in all connectors.
184 $ref: /schemas/graph.yaml#/properties/port
185 description: Super Speed (SS), present in SS capable connectors.
188 $ref: /schemas/graph.yaml#/properties/port
189 description: Sideband Use (SBU), present in USB-C. This describes the
190 alternate mode connection of which SBU is a part.
195 new-source-frs-typec-current:
196 description: Initial current capability of the new source when vSafe5V
197 is applied during PD3.0 Fast Role Swap. "Table 6-14 Fixed Supply PDO - Sink"
198 of "USB Power Delivery Specification Revision 3.0, Version 1.2" provides the
199 different power levels and "6.4.1.3.1.6 Fast Role Swap USB Type-C Current"
200 provides a detailed description of the field. The sink PDO from current source
201 reflects the current source's(i.e. transmitter of the FRS signal) power
202 requirement during fr swap. The current sink (i.e. receiver of the FRS signal),
203 a.k.a new source, should check if it will be able to satisfy the current source's,
204 new sink's, requirement during frswap before enabling the frs signal reception.
205 This property refers to maximum current capability that the current sink can
206 satisfy. During FRS, VBUS voltage is at 5V, as the partners are in implicit
207 contract, hence, the power level is only a function of the current capability.
208 "1" refers to default USB power level as described by "Table 6-14 Fixed Supply PDO - Sink".
209 "2" refers to 1.5A@5V.
210 "3" refers to 3.0A@5V.
211 $ref: /schemas/types.yaml#/definitions/uint32
215 description: Allows PMIC charger loops which are slow(i.e. cannot meet the 15ms deadline) to
216 still comply to pSnkStby i.e Maximum power that can be consumed by sink while in Sink Standby
217 state as defined in 7.4.2 Sink Electrical Parameters of USB Power Delivery Specification
218 Revision 3.0, Version 1.2. When the property is set, the port requests pSnkStby(2.5W -
219 5V@500mA) upon entering SNK_DISCOVERY(instead of 3A or the 1.5A, Rp current advertised, during
220 SNK_DISCOVERY) and the actual currrent limit after reception of PS_Ready for PD link or during
221 SNK_READY for non-pd link.
225 sink-vdos-v1: [ 'sink-vdos' ]
226 sink-vdos: [ 'sink-vdos-v1' ]
236 const: gpio-usb-b-connector
248 const: samsung,usb-connector-11pin
258 - new-source-frs-typec-current
260 additionalProperties: true
263 # Micro-USB connector with HS lines routed via controller (MUIC).
266 usb_con1: connector {
267 compatible = "usb-b-connector";
273 # USB-C connector attached to CC controller (s2mm005), HS lines routed
274 # to companion PMIC (max77865), SS lines to USB3 PHY and SBU to DisplayPort.
275 # DisplayPort video lines are routed to the connector via SS mux in USB3 PHY.
278 usb_con2: connector {
279 compatible = "usb-c-connector";
283 #address-cells = <1>;
288 usb_con_hs: endpoint {
289 remote-endpoint = <&max77865_usbc_hs>;
294 usb_con_ss: endpoint {
295 remote-endpoint = <&usbdrd_phy_ss>;
300 usb_con_sbu: endpoint {
301 remote-endpoint = <&dp_aux>;
308 # USB-C connector attached to a typec port controller(ptn5110), which has
309 # power delivery support and enables drp.
311 #include <dt-bindings/usb/pd.h>
313 usb_con3: connector {
314 compatible = "usb-c-connector";
317 try-power-role = "sink";
318 source-pdos = <PDO_FIXED(5000, 2000, PDO_FIXED_USB_COMM)>;
319 sink-pdos = <PDO_FIXED(5000, 2000, PDO_FIXED_USB_COMM)
320 PDO_VAR(5000, 12000, 2000)>;
321 op-sink-microwatt = <10000000>;
325 # USB-C connector attached to SoC and USB3 typec port controller(hd3ss3220)
326 # with SS 2:1 MUX. HS lines routed to SoC, SS lines routed to the MUX and
327 # the output of MUX is connected to the SoC.
330 compatible = "usb-c-connector";
335 #address-cells = <1>;
340 remote-endpoint = <&usb3_hs_ep>;
346 remote-endpoint = <&hd3ss3220_in_ep>;
352 # USB connector with GPIO control lines
354 #include <dt-bindings/gpio/gpio.h>
358 compatible = "gpio-usb-b-connector", "usb-b-connector";
360 id-gpios = <&pio 12 GPIO_ACTIVE_HIGH>;
361 vbus-supply = <&usb_p0_vbus>;
365 # Micro-USB connector with HS lines routed via controller (MUIC) and MHL
366 # lines connected to HDMI-MHL bridge (sii8620) on Samsung Exynos5433-based
370 usb_con4: connector {
371 compatible = "samsung,usb-connector-11pin", "usb-b-connector";
376 #address-cells = <1>;
381 muic_to_usb: endpoint {
382 remote-endpoint = <&usb_to_muic>;
387 usb_con_mhl: endpoint {
388 remote-endpoint = <&sii8620_mhl>;