From: Tobias Schramm <t.schramm@manjaro.org>
To: linux-usb@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org
Cc: Johan Jonker <jbx6244@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Tobias Schramm <t.schramm@manjaro.org>
Subject: [PATCH v2 0/5] Add USB support for RK3308 SoC
Date: Fri, 14 May 2021 17:00:39 +0200 [thread overview]
Message-ID: <20210514150044.2099298-1-t.schramm@manjaro.org> (raw)
The RK3308 SoC features integrated USB controllers and PHYs. The USB
controller is compatible with the usual RK3066 USB controller, the phy is
in general compatible with the inno-usb2 phy structure but is not quite
the same as any of the phys supported yet.
This patchset adds USB support for the RK3308 SoC to both the RK3308 dtsi
and Rockchip inno-usb2 phy driver.
I've tested this patchset on a Rock Pi S, works flawlessly with HS, FS and
LS devices.
This patchset depends on grf.txt to YAML conversion [1] by Johan.
This is v2 of the patchset.
Cheers,
Tobias
Changelog:
v2:
- switch changes over to Johan's converted yaml documentation
- document "rockchip,rk3308-usb2phy-grf", "syscon", "simple-mfd"
compatible
- fix rockchip,rk3308-usb2phy documentation
[1] https://lkml.org/lkml/2021/5/12/464
Tobias Schramm (5):
dt-bindings: phy: rockchip-inno-usb2: add compatible for rk3308 USB
phy
phy: phy-rockchip-inno-usb2: add support for RK3308 USB phy
dt-bindings: usb: dwc2: add compatible for RK3308 USB controller
dt-bindings: soc: rockchip: grf: add compatible for RK3308 USB grf
arm64: dts: rockchip: add USB support to RK3308 dts
.../bindings/phy/phy-rockchip-inno-usb2.yaml | 1 +
.../devicetree/bindings/soc/rockchip/grf.yaml | 1 +
.../devicetree/bindings/usb/dwc2.yaml | 1 +
arch/arm64/boot/dts/rockchip/rk3308.dtsi | 73 +++++++++++++++++++
drivers/phy/rockchip/phy-rockchip-inno-usb2.c | 44 +++++++++++
5 files changed, 120 insertions(+)
--
2.31.1
next reply other threads:[~2021-05-14 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 15:00 Tobias Schramm [this message]
2021-05-14 15:00 ` [PATCH v2 1/5] dt-bindings: phy: rockchip-inno-usb2: add compatible for rk3308 USB phy Tobias Schramm
2021-05-18 1:30 ` Rob Herring
2021-05-31 8:23 ` Vinod Koul
2021-05-14 15:00 ` [PATCH v2 2/5] phy: phy-rockchip-inno-usb2: add support for RK3308 " Tobias Schramm
2021-05-31 8:24 ` Vinod Koul
2021-05-14 15:00 ` [PATCH v2 3/5] dt-bindings: usb: dwc2: add compatible for RK3308 USB controller Tobias Schramm
2021-05-18 1:30 ` Rob Herring
2021-05-14 15:00 ` [PATCH v2 4/5] dt-bindings: soc: rockchip: grf: add compatible for RK3308 USB grf Tobias Schramm
2021-05-14 15:53 ` Johan Jonker
2021-05-14 15:00 ` [PATCH v2 5/5] arm64: dts: rockchip: add USB support to RK3308 dts Tobias Schramm
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=20210514150044.2099298-1-t.schramm@manjaro.org \
--to=t.schramm@manjaro.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@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).