Some platforms have only super speed data bus connected to HD3SS3220 device and high speed data bus directly connected to the SoC. In such platforms modelling connector as a child of this device is making it non compliant with usb connector bindings. By modelling connector node as standalone device node along with HD3SS3220 device and the SoC data bus will make it compliant with usb connector bindings. It is based on the below discussion threads 1) https://patchwork.kernel.org/patch/11669423/ 2) https://patchwork.kernel.org/patch/11129567/ Biju Das (4): dt-bindings: usb: renesas,usb3-peri: Document HS and SS data bus usb: typec: hd3ss3220: Use OF graph API to get the connector fwnode arm64: dts: renesas: cat874: Move connector node out of hd3ss3220 device arm64: dts: renesas: beacon-renesom-baseboard: Move connector node out of hd3ss3220 device Lad Prabhakar (1): dt-bindings: usb: convert ti,hd3ss3220 bindings to json-schema .../bindings/usb/renesas,usb3-peri.yaml | 36 +++++++-- .../devicetree/bindings/usb/ti,hd3ss3220.txt | 38 --------- .../devicetree/bindings/usb/ti,hd3ss3220.yaml | 81 +++++++++++++++++++ .../dts/renesas/beacon-renesom-baseboard.dtsi | 67 +++++++++++---- .../boot/dts/renesas/r8a774c0-cat874.dts | 67 +++++++++++---- drivers/usb/typec/hd3ss3220.c | 18 ++++- 6 files changed, 225 insertions(+), 82 deletions(-) delete mode 100644 Documentation/devicetree/bindings/usb/ti,hd3ss3220.txt create mode 100644 Documentation/devicetree/bindings/usb/ti,hd3ss3220.yaml -- 2.17.1
