From: Michael Riesch <michael.riesch@wolfvision.net>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Frank Wunderlich <frank-w@public-files.de>,
Michael Riesch <michael.riesch@wolfvision.net>,
Sascha Hauer <s.hauer@pengutronix.de>,
Liang Chen <cl@rock-chips.com>, Peter Geis <pgwipeout@gmail.com>,
Johan Jonker <jbx6244@gmail.com>, Simon Xue <xxm@rock-chips.com>,
Yifeng Zhao <yifeng.zhao@rock-chips.com>,
Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
Subject: [PATCH v2 0/4] arm64: dts: rockchip: add usb3 support to rk356x
Date: Fri, 25 Feb 2022 14:15:58 +0100 [thread overview]
Message-ID: <20220225131602.2283499-1-michael.riesch@wolfvision.net> (raw)
Hi all,
This series introduces the USB 3.0 xHCI controller nodes and enables
them on the RK3568 EVB1. USB 3.0 host and gadget operation have been
tested successfully.
The second version of the series considers Johan's comments which
helped a lot to clean things up and get rid of the dtbs_check issues.
Looking forward to your comments!
Best regards,
Michael
Changes since v1:
- move power domain PD_PIPE to rk356x
- add rockchip,rk3568-dwc3 compatible to documentation
- merge subnodes with corresponding nodes
- remove all quirks (add at a later stage if required)
Michael Riesch (4):
arm64: dts: rockchip: move power domain PD_PIPE to rk356x
dt-bindings: usb: add rk3568 compatible to rockchip,dwc3
arm64: dts: rockchip: add the usb3 nodes to rk356x
arm64: dts: rockchip: add usb3 support to rk3568-evb1-v10
.../bindings/usb/rockchip,dwc3.yaml | 2 +
.../boot/dts/rockchip/rk3568-evb1-v10.dts | 46 +++++++++++++++++++
arch/arm64/boot/dts/rockchip/rk3568.dtsi | 17 ++-----
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 44 ++++++++++++++++++
4 files changed, 95 insertions(+), 14 deletions(-)
--
2.30.2
next reply other threads:[~2022-02-25 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 13:15 Michael Riesch [this message]
2022-02-25 13:15 ` [PATCH v2 1/4] arm64: dts: rockchip: move power domain PD_PIPE to rk356x Michael Riesch
2022-02-25 14:14 ` Robin Murphy
2022-02-25 15:43 ` Michael Riesch
2022-02-25 16:42 ` Johan Jonker
2022-02-25 13:16 ` [PATCH v2 2/4] dt-bindings: usb: add rk3568 compatible to rockchip,dwc3 Michael Riesch
2022-03-03 13:43 ` Rob Herring
2022-02-25 13:16 ` [PATCH v2 3/4] arm64: dts: rockchip: add the usb3 nodes to rk356x Michael Riesch
2022-02-25 13:16 ` [PATCH v2 4/4] arm64: dts: rockchip: add usb3 support to rk3568-evb1-v10 Michael Riesch
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=20220225131602.2283499-1-michael.riesch@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=frattaroli.nicolas@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=xxm@rock-chips.com \
--cc=yifeng.zhao@rock-chips.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).