From: Peter Geis <pgwipeout@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-rockchip@lists.infradead.org, heiko@sntech.de,
michael.riesch@wolfvision.net, jbx6244@gmail.com,
Peter Geis <pgwipeout@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Felipe Balbi <balbi@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: [PATCH v4 0/8] enable usb support on rk356x
Date: Mon, 28 Feb 2022 08:56:51 -0500 [thread overview]
Message-ID: <20220228135700.1089526-1-pgwipeout@gmail.com> (raw)
Good Morning,
This is my patch series that I have maintained out of tree until the
combophy driver landed.
Patch 1 fixes the grf dt binding from the combophy merge.
Patch 2 adds the dt bindings for the grf changes necessary.
Patch 3 adds the SoC specific binding.
Patch 4 adds support to the grf driver to set the rk3566 otg clock
source.
Patch 5 is a downstream patch ported forward to shut down the usb3 clock
when the controller is operating in usb2 mode.
Patch 6 adds the dwc3 nodes to the rk356x device tree includes.
Patch 7 enables the dwc3 nodes on the Quartz64 Model A.
Patch 8 enables the dwc3 nodes on the rk3568-evb.
Note, there are functional changes from previous versions.
Please review and apply.
Very Respectfully,
Peter Geis
Changelog:
v4:
- Add SoC specific binding, fall back to core.
v3:
- Drop the dwc-of-simple method in favor of using dwc core.
- Drop all quirks except snps,dis_u2_susphy_quirk, which is necessary to
prevent device detection failures in some states.
- Drop the reset-names.
v2:
- Add a dt-bindings fix for grf.yaml
- Unify the reset names.
- Constrain the force usb2 clock dwc3 patch to only supported variants of
the ip.
- Change dwc3-of-simple to support of-match-data.
- Drop the PCLK-PIPE clk.
- Rename the usb nodes to be more friendly.
- Add the rk3568-evb enable patch.
Bin Yang (1):
usb: dwc3: core: do not use 3.0 clock when operating in 2.0 mode
Michael Riesch (2):
dt-bindings: usb: add rk3568 compatible to rockchip, dwc3
arm64: dts: rockchip: add usb3 support to rk3568-evb1-v10
Peter Geis (5):
dt-bindings: soc: grf: fix rk3568 usb definitions
dt-bindings: soc: grf: add rk3566-pipe-grf compatible
soc: rockchip: set dwc3 clock for rk3566
arm64: dts: rockchip: add rk356x dwc3 usb3 nodes
arm64: dts: rockchip: enable dwc3 on quartz64-a
.../devicetree/bindings/soc/rockchip/grf.yaml | 5 +-
.../bindings/usb/rockchip,dwc3.yaml | 2 +
.../boot/dts/rockchip/rk3566-quartz64-a.dts | 37 +++++++++++++++
arch/arm64/boot/dts/rockchip/rk3566.dtsi | 11 +++++
.../boot/dts/rockchip/rk3568-evb1-v10.dts | 46 +++++++++++++++++++
arch/arm64/boot/dts/rockchip/rk3568.dtsi | 9 ++++
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 35 +++++++++++++-
drivers/soc/rockchip/grf.c | 17 +++++++
drivers/usb/dwc3/core.c | 5 ++
drivers/usb/dwc3/core.h | 1 +
10 files changed, 165 insertions(+), 3 deletions(-)
--
2.25.1
next reply other threads:[~2022-02-28 13:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 13:56 Peter Geis [this message]
2022-02-28 13:56 ` [PATCH v4 1/8] dt-bindings: soc: grf: fix rk3568 usb definitions Peter Geis
2022-03-01 14:52 ` Peter Geis
2022-03-02 8:16 ` Vinod Koul
2022-03-02 12:18 ` Peter Geis
2022-03-02 14:22 ` Vinod Koul
2022-02-28 13:56 ` [PATCH v4 2/8] dt-bindings: soc: grf: add rk3566-pipe-grf compatible Peter Geis
2022-03-07 23:10 ` Rob Herring
2022-02-28 13:56 ` [PATCH v4 3/8] dt-bindings: usb: add rk3568 compatible to rockchip, dwc3 Peter Geis
2022-03-07 23:10 ` Rob Herring
2022-02-28 13:56 ` [PATCH v4 6/8] arm64: dts: rockchip: add rk356x dwc3 usb3 nodes Peter Geis
2022-03-03 16:05 ` Aw: " Frank Wunderlich
2022-02-28 13:56 ` [PATCH v4 7/8] arm64: dts: rockchip: enable dwc3 on quartz64-a Peter Geis
2022-02-28 13:56 ` [PATCH v4 8/8] arm64: dts: rockchip: add usb3 support to rk3568-evb1-v10 Peter Geis
2022-03-01 14:30 ` [PATCH v4 0/8] enable usb support on rk356x 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=20220228135700.1089526-1-pgwipeout@gmail.com \
--to=pgwipeout@gmail.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--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=michael.riesch@wolfvision.net \
--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).