From: Johan Jonker <jbx6244@gmail.com>
To: Peter Geis <pgwipeout@gmail.com>, Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org, frank.wang@rock-chips.com,
linux-usb@vger.kernel.org, kever.yang@rock-chips.com,
william.wu@rock-chips.com, zyw@rock-chips.com,
wulf@rock-chips.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/4] arm64: dts: rockchip: add rk3328 usb3 and usb3phy nodes
Date: Mon, 16 Nov 2020 17:07:37 +0100 [thread overview]
Message-ID: <ce2217b9-3627-df09-04d9-e47bef6c3572@gmail.com> (raw)
In-Reply-To: <20201116151735.178737-4-pgwipeout@gmail.com>
Hi Peter,
Just some comments...
The compatible "rockchip,rk3328-dwc3" is currently under test in:
https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git/
I think we should let it go in mainline first
(if the maintainers agree?) and then you can base your serie on that.
The compatible "rockchip,rk3328-usb3phy" needs to be added to a document
as well.
Add increase version number after previous series.
Is there any change in code or on how you detect?
On 11/16/20 4:17 PM, Peter Geis wrote:
> Add the usb3 controller and usb3 phy nodes to the rk3328.
>
> Signed-off-by: Peter Geis <pgwipeout@gmail.com>
> ---
> arch/arm64/boot/dts/rockchip/rk3328.dtsi | 65 ++++++++++++++++++++++++
> 1 file changed, 65 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> index bbdb19a3e85d..9fea9203d114 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> @@ -853,6 +853,40 @@ u2phy_host: host-port {
> };
> };
>
> + usb3phy: usb3-phy@ff470000 {
> + compatible = "rockchip,rk3328-usb3phy";
> + reg = <0x0 0xff460000 0x0 0x10000>;
> + clocks = <&cru PCLK_USB3PHY_OTG>, <&cru PCLK_USB3PHY_PIPE>;
> + clock-names = "usb3phy-otg", "usb3phy-pipe";
> + resets = <&cru SRST_USB3PHY_U2>,
> + <&cru SRST_USB3PHY_U3>,
> + <&cru SRST_USB3PHY_PIPE>,
> + <&cru SRST_USB3OTG_UTMI>,
> + <&cru SRST_USB3PHY_OTG_P>,
> + <&cru SRST_USB3PHY_PIPE_P>;
> + reset-names = "usb3phy-u2-por", "usb3phy-u3-por",
> + "usb3phy-pipe-mac", "usb3phy-utmi-mac",
> + "usb3phy-utmi-apb", "usb3phy-pipe-apb";
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> + status = "disabled";
> +
> + usb3phy_utmi: utmi@ff470000 {
> + compatible = "rockchip,rk3328-usb3phy-utmi";
> + reg = <0x0 0xff470000 0x0 0x8000>;
> + #phy-cells = <0>;
> + status = "disabled";
> + };
> +
> + usb3phy_pipe: pipe@ff478000 {
> + compatible = "rockchip,rk3328-usb3phy-pipe";
> + reg = <0x0 0xff478000 0x0 0x8000>;
> + #phy-cells = <0>;
> + status = "disabled";
> + };
> + };
> +
> sdmmc: mmc@ff500000 {
> compatible = "rockchip,rk3328-dw-mshc", "rockchip,rk3288-dw-mshc";
> reg = <0x0 0xff500000 0x0 0x4000>;
> @@ -983,6 +1017,37 @@ usb_host0_ohci: usb@ff5d0000 {
> status = "disabled";
> };
>
> + usbdrd3: usb@ff600000 {
> + compatible = "rockchip,rk3328-dwc3";
> + clocks = <&cru SCLK_USB3OTG_REF>, <&cru ACLK_USB3OTG>,
> + <&cru SCLK_USB3OTG_SUSPEND>;
> + clock-names = "ref", "bus_early", "suspend";
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> + status = "disabled";
> +
> + usbdrd_dwc3: dwc3@ff600000 {
> + compatible = "snps,dwc3";
> + reg = <0x0 0xff600000 0x0 0x100000>;
> + interrupts = <GIC_SPI 67 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&cru SCLK_USB3OTG_REF>, <&cru ACLK_USB3OTG>,
> + <&cru SCLK_USB3OTG_SUSPEND>;
> + clock-names = "ref", "bus_early", "suspend";
> + dr_mode = "host";
> + usb-phy = <&usb3phy_utmi>, <&usb3phy_pipe>;
> + phy_type = "utmi_wide";
> + snps,dis_enblslpm_quirk;
> + snps,dis-u2-freeclk-exists-quirk;
> + snps,dis_u2_susphy_quirk;
> + snps,dis_u3_susphy_quirk;
> + snps,dis-del-phy-power-chg-quirk;
> + snps,dis-tx-ipgap-linecheck-quirk;
> + snps,xhci-trb-ent-quirk;
> + status = "disabled";
> + };
> + };
> +
> gic: interrupt-controller@ff811000 {
> compatible = "arm,gic-400";
> #interrupt-cells = <3>;
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-16 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 15:17 [PATCH 0/4] [RFC] rk3328 usb3 phy driver Peter Geis
2020-11-16 15:17 ` [PATCH 1/4] phy: rockchip: add rockchip usb3 innosilicon " Peter Geis
2021-07-19 14:29 ` Alex Bee
2021-07-19 23:19 ` Peter Geis
2020-11-16 15:17 ` [PATCH 2/4] usb: dwc3: add rockchip innosilicon usb3 glue layer Peter Geis
2020-11-16 15:17 ` [PATCH 3/4] arm64: dts: rockchip: add rk3328 usb3 and usb3phy nodes Peter Geis
2020-11-16 16:07 ` Johan Jonker [this message]
2020-11-16 16:25 ` Peter Geis
2020-11-16 15:17 ` [PATCH 4/4] arm64: dts: rockchip: enable usb3 on rk3328-roc-cc board 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=ce2217b9-3627-df09-04d9-e47bef6c3572@gmail.com \
--to=jbx6244@gmail.com \
--cc=balbi@kernel.org \
--cc=frank.wang@rock-chips.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=pgwipeout@gmail.com \
--cc=william.wu@rock-chips.com \
--cc=wulf@rock-chips.com \
--cc=zyw@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