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
108 - $ref: /schemas/types.yaml#/definitions/string
115 description: Set this property if the Type-C connector has no power delivery support.
118 # The following are optional properties for "usb-c-connector" with power
121 description: An array of u32 with each entry providing supported power
122 source data object(PDO), the detailed bit definitions of PDO can be found
123 in "Universal Serial Bus Power Delivery Specification" chapter 6.4.1.2
124 Source_Capabilities Message, the order of each entry(PDO) should follow
125 the PD spec chapter 6.4.1. Required for power source and power dual role.
126 User can specify the source PDO array via PDO_FIXED/BATT/VAR/PPS_APDO()
127 defined in dt-bindings/usb/pd.h.
130 $ref: /schemas/types.yaml#/definitions/uint32-array
133 description: An array of u32 with each entry providing supported power sink
134 data object(PDO), the detailed bit definitions of PDO can be found in
135 "Universal Serial Bus Power Delivery Specification" chapter 6.4.1.3
136 Sink Capabilities Message, the order of each entry(PDO) should follow the
137 PD spec chapter 6.4.1. Required for power sink and power dual role. User
138 can specify the sink PDO array via PDO_FIXED/BATT/VAR/PPS_APDO() defined
139 in dt-bindings/usb/pd.h.
142 $ref: /schemas/types.yaml#/definitions/uint32-array
145 description: An array of u32 with each entry, a Vendor Defined Message Object (VDO),
146 providing additional information corresponding to the product, the detailed bit
147 definitions and the order of each VDO can be found in
148 "USB Power Delivery Specification Revision 3.0, Version 2.0 + ECNs 2020-12-10"
149 chapter 6.4.4.3.1 Discover Identity. User can specify the VDO array via
150 VDO_IDH/_CERT/_PRODUCT/_UFP/_DFP/_PCABLE/_ACABLE(1/2)/_VPD() defined in
151 dt-bindings/usb/pd.h.
154 $ref: /schemas/types.yaml#/definitions/uint32-array
157 description: An array of u32 with each entry, a Vendor Defined Message Object (VDO),
158 providing additional information corresponding to the product, the detailed bit
159 definitions and the order of each VDO can be found in
160 "USB Power Delivery Specification Revision 2.0, Version 1.3" chapter 6.4.4.3.1 Discover
161 Identity. User can specify the VDO array via VDO_IDH/_CERT/_PRODUCT/_CABLE/_AMA defined in
162 dt-bindings/usb/pd.h.
165 $ref: /schemas/types.yaml#/definitions/uint32-array
168 description: Sink required operating power in microwatt, if source can't
169 offer the power, Capability Mismatch is set. Required for power sink and
173 $ref: /schemas/graph.yaml#/properties/ports
174 description: OF graph bindings modeling any data bus to the connector
175 unless the bus is between parent node and the connector. Since a single
176 connector can have multiple data buses every bus has an assigned OF graph
177 port number as described below.
181 $ref: /schemas/graph.yaml#/properties/port
182 description: High Speed (HS), present in all connectors.
185 $ref: /schemas/graph.yaml#/properties/port
186 description: Super Speed (SS), present in SS capable connectors.
189 $ref: /schemas/graph.yaml#/properties/port
190 description: Sideband Use (SBU), present in USB-C. This describes the
191 alternate mode connection of which SBU is a part.
196 new-source-frs-typec-current:
197 description: Initial current capability of the new source when vSafe5V
198 is applied during PD3.0 Fast Role Swap. "Table 6-14 Fixed Supply PDO - Sink"
199 of "USB Power Delivery Specification Revision 3.0, Version 1.2" provides the
200 different power levels and "6.4.1.3.1.6 Fast Role Swap USB Type-C Current"
201 provides a detailed description of the field. The sink PDO from current source
202 reflects the current source's(i.e. transmitter of the FRS signal) power
203 requirement during fr swap. The current sink (i.e. receiver of the FRS signal),
204 a.k.a new source, should check if it will be able to satisfy the current source's,
205 new sink's, requirement during frswap before enabling the frs signal reception.
206 This property refers to maximum current capability that the current sink can
207 satisfy. During FRS, VBUS voltage is at 5V, as the partners are in implicit
208 contract, hence, the power level is only a function of the current capability.
209 "1" refers to default USB power level as described by "Table 6-14 Fixed Supply PDO - Sink".
210 "2" refers to 1.5A@5V.
211 "3" refers to 3.0A@5V.
212 $ref: /schemas/types.yaml#/definitions/uint32
216 description: Allows PMIC charger loops which are slow(i.e. cannot meet the 15ms deadline) to
217 still comply to pSnkStby i.e Maximum power that can be consumed by sink while in Sink Standby
218 state as defined in 7.4.2 Sink Electrical Parameters of USB Power Delivery Specification
219 Revision 3.0, Version 1.2. When the property is set, the port requests pSnkStby(2.5W -
220 5V@500mA) upon entering SNK_DISCOVERY(instead of 3A or the 1.5A, Rp current advertised, during
221 SNK_DISCOVERY) and the actual currrent limit after reception of PS_Ready for PD link or during
222 SNK_READY for non-pd link.
226 sink-vdos-v1: [ 'sink-vdos' ]
227 sink-vdos: [ 'sink-vdos-v1' ]
237 const: gpio-usb-b-connector
249 const: samsung,usb-connector-11pin
259 - new-source-frs-typec-current
261 additionalProperties: true
264 # Micro-USB connector with HS lines routed via controller (MUIC).
267 usb_con1: connector {
268 compatible = "usb-b-connector";
274 # USB-C connector attached to CC controller (s2mm005), HS lines routed
275 # to companion PMIC (max77865), SS lines to USB3 PHY and SBU to DisplayPort.
276 # DisplayPort video lines are routed to the connector via SS mux in USB3 PHY.
279 usb_con2: connector {
280 compatible = "usb-c-connector";
284 #address-cells = <1>;
289 usb_con_hs: endpoint {
290 remote-endpoint = <&max77865_usbc_hs>;
295 usb_con_ss: endpoint {
296 remote-endpoint = <&usbdrd_phy_ss>;
301 usb_con_sbu: endpoint {
302 remote-endpoint = <&dp_aux>;
309 # USB-C connector attached to a typec port controller(ptn5110), which has
310 # power delivery support and enables drp.
312 #include <dt-bindings/usb/pd.h>
314 usb_con3: connector {
315 compatible = "usb-c-connector";
318 try-power-role = "sink";
319 source-pdos = <PDO_FIXED(5000, 2000, PDO_FIXED_USB_COMM)>;
320 sink-pdos = <PDO_FIXED(5000, 2000, PDO_FIXED_USB_COMM)
321 PDO_VAR(5000, 12000, 2000)>;
322 op-sink-microwatt = <10000000>;
326 # USB-C connector attached to SoC and USB3 typec port controller(hd3ss3220)
327 # with SS 2:1 MUX. HS lines routed to SoC, SS lines routed to the MUX and
328 # the output of MUX is connected to the SoC.
331 compatible = "usb-c-connector";
336 #address-cells = <1>;
341 remote-endpoint = <&usb3_hs_ep>;
347 remote-endpoint = <&hd3ss3220_in_ep>;
353 # USB connector with GPIO control lines
355 #include <dt-bindings/gpio/gpio.h>
359 compatible = "gpio-usb-b-connector", "usb-b-connector";
361 id-gpios = <&pio 12 GPIO_ACTIVE_HIGH>;
362 vbus-supply = <&usb_p0_vbus>;
366 # Micro-USB connector with HS lines routed via controller (MUIC) and MHL
367 # lines connected to HDMI-MHL bridge (sii8620) on Samsung Exynos5433-based
371 usb_con4: connector {
372 compatible = "samsung,usb-connector-11pin", "usb-b-connector";
377 #address-cells = <1>;
382 muic_to_usb: endpoint {
383 remote-endpoint = <&usb_to_muic>;
388 usb_con_mhl: endpoint {
389 remote-endpoint = <&sii8620_mhl>;