From: Peter Geis <pgwipeout@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Peter Geis <pgwipeout@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Heiko Stuebner <heiko@sntech.de>, Felipe Balbi <balbi@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: [PATCH v1 0/8] enable usb support on rk356x
Date: Fri, 25 Feb 2022 09:54:23 -0500 [thread overview]
Message-ID: <20220225145432.422130-1-pgwipeout@gmail.com> (raw)
Good Morning,
This is my patch series that I have maintained out of tree until the
combophy driver landed. Note, it is dependent on this series to function
(aside from the rk3566 dwc3-otg port, which will work currently).
This series is still dependent on Patch 4 of the combophy series, which
has yet to be accepted.
Patches 1 and 2 add the dt bindings for the grf changes necessary for
this series.
Patch 3 adds support to the grf driver to set the rk3566 otg clock
source.
Patch 4 is a downstream patch ported forward to shut down the usb3 clock
when the controller is operating in usb2 mode.
Patches 5 and 6 clean up the dwc3-of-simple driver and add the
compatible for the rk3568.
Patch 7 adds the dwc3 nodes to the rk356x device tree includes.
Patch 8 enables the dwc3 nodes on the Quartz64 Model A.
Please review and apply.
Very Respectfully,
Peter Geis
Bin Yang (1):
usb: dwc3: core: do not use 3.0 clock when operating in 2.0 mode
Peter Geis (7):
dt-bindings: soc: grf: add rk3566-pipe-grf compatible
dt-bindings: usb: dwc3: add description for rk3568
soc: rockchip: set dwc3 clock for rk3566
usb: dwc3: reorder dwc-of-simple compatibles
usb: dwc3: add rk3568 dwc3 support
arm64: dts: rockchip: add the dwc3 usb3 nodes to rk356x
arm64: dts: rockchip: enable the dwc3 nodes on quartz64-a
.../devicetree/bindings/soc/rockchip/grf.yaml | 1 +
.../bindings/usb/rockchip,dwc3.yaml | 7 ++-
.../boot/dts/rockchip/rk3566-quartz64-a.dts | 37 +++++++++++++++
arch/arm64/boot/dts/rockchip/rk3566.dtsi | 12 +++++
arch/arm64/boot/dts/rockchip/rk3568.dtsi | 9 ++++
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 45 ++++++++++++++++++-
drivers/soc/rockchip/grf.c | 17 +++++++
drivers/usb/dwc3/core.c | 4 ++
drivers/usb/dwc3/core.h | 1 +
drivers/usb/dwc3/dwc3-of-simple.c | 10 +++--
10 files changed, 137 insertions(+), 6 deletions(-)
--
2.25.1
next reply other threads:[~2022-02-25 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 14:54 Peter Geis [this message]
2022-02-25 14:54 ` [PATCH v1 1/8] dt-bindings: soc: grf: add rk3566-pipe-grf compatible Peter Geis
2022-02-25 14:54 ` [PATCH v1 2/8] dt-bindings: usb: dwc3: add description for rk3568 Peter Geis
2022-02-25 16:07 ` Johan Jonker
2022-02-25 18:04 ` Peter Geis
2022-02-25 14:54 ` [PATCH v1 7/8] arm64: dts: rockchip: add rk356x dwc3 usb3 nodes Peter Geis
2022-02-25 17:01 ` Michael Riesch
2022-02-25 17:59 ` Peter Geis
2022-02-25 18:25 ` Michael Riesch
2022-02-25 14:54 ` [PATCH v1 8/8] arm64: dts: rockchip: enable dwc3 on quartz64-a Peter Geis
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=20220225145432.422130-1-pgwipeout@gmail.com \
--to=pgwipeout@gmail.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).