| Message ID | 20250407-rk3576-sige5-usb-v1-1-67eec166f82f@collabora.com (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | RK3576 USB Enablement | expand |
diff --git a/Documentation/devicetree/bindings/phy/rockchip,inno-usb2phy.yaml b/Documentation/devicetree/bindings/phy/rockchip,inno-usb2phy.yaml index 6a7ef556414cebad63c10de754778f84fd4486ee..3a662bfc353250a8ad9386ebb5575d1e84c1b5ba 100644 --- a/Documentation/devicetree/bindings/phy/rockchip,inno-usb2phy.yaml +++ b/Documentation/devicetree/bindings/phy/rockchip,inno-usb2phy.yaml @@ -78,6 +78,11 @@ properties: When set the driver will request its phandle as one companion-grf for some special SoCs (e.g rv1108). + port: + $ref: /schemas/graph.yaml#/properties/port + description: + A port node to link the PHY to a USB connector's "high-speed" port. + host-port: type: object additionalProperties: false
USB connectors like to have OF graph connections to high-speed related nodes to do various things. In the case of the RK3576, we can make use of a port in the usb2 PHY to detect whether the OTG controller is connected to a type C port and apply some special behaviour accordingly. The usefulness of having different bits of a fully functioning USB stack point to each other is more general though, and not constrained to RK3576 at all, even for this use-case. Add a port property to the binding. Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com> --- Documentation/devicetree/bindings/phy/rockchip,inno-usb2phy.yaml | 5 +++++ 1 file changed, 5 insertions(+)