From: Biju Das <biju.das.jz@bp.renesas.com>
To: Rob Herring <robh+dt@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: [PATCH v2 0/5] Remodel HD3SS3220 device nodes
Date: Tue, 11 Aug 2020 09:02:22 +0100 [thread overview]
Message-ID: <20200811080227.3170-1-biju.das.jz@bp.renesas.com> (raw)
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
next reply other threads:[~2020-08-11 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 8:02 Biju Das [this message]
2020-08-11 8:02 ` [PATCH v2 1/5] dt-bindings: usb: convert ti,hd3ss3220 bindings to json-schema Biju Das
2020-08-11 8:02 ` [PATCH v2 2/5] dt-bindings: usb: renesas,usb3-peri: Document HS and SS data bus Biju Das
2020-08-24 11:29 ` Yoshihiro Shimoda
2020-08-24 11:54 ` Biju Das
2020-08-24 12:08 ` Yoshihiro Shimoda
2020-08-24 12:14 ` Biju Das
2020-08-25 7:13 ` Geert Uytterhoeven
2020-08-11 8:02 ` [PATCH v2 4/5] arm64: dts: renesas: cat874: Move connector node out of hd3ss3220 device Biju Das
2020-08-11 8:02 ` [PATCH v2 5/5] arm64: dts: renesas: beacon-renesom-baseboard: " Biju Das
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200811080227.3170-1-biju.das.jz@bp.renesas.com \
--to=biju.das.jz@bp.renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).