[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161207175208.GB87970@google.com>
Date: Wed, 7 Dec 2016 09:52:08 -0800
From: Brian Norris <briannorris@...omium.org>
To: Heiko Stuebner <heiko@...ech.de>
Cc: linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
Caesar Wang <wxt@...k-chips.com>,
Doug Anderson <dianders@...omium.org>,
devicetree@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Stephen Barber <smbarber@...omium.org>,
linux-arm-kernel@...ts.infradead.org,
Chris Zhong <zyw@...k-chips.com>
Subject: Re: [PATCH 4/9] arm64: dts: rockchip: support dwc3 USB for rk3399
Hi,
On Wed, Dec 07, 2016 at 06:09:16PM +0100, Heiko Stuebner wrote:
> Am Donnerstag, 1. Dezember 2016, 18:27:28 CET schrieb Brian Norris:
> > Add the dwc3 usb needed node information for rk3399.
> >
> > Signed-off-by: Brian Norris <briannorris@...omium.org>
> > ---
> > Somewhat rewritten from Caesar's reposting (v2) of my patch.
> >
> > Changes:
> > * Include USB2 PHY (which is now in -next)
> > * Don't include USB3 PHY, as extcon support is not ready yet
> > * Drop non-upstream properties
> > * Fixup whitespace a bit
> > ---
> > arch/arm64/boot/dts/rockchip/rk3399.dtsi | 60
> > ++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> > b/arch/arm64/boot/dts/rockchip/rk3399.dtsi index 4ca8f9a7601c..1e97fb8c6415
> > 100644
> > --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> > +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> > @@ -316,6 +316,66 @@
> > };
> > };
> >
> > + usbdrd3_0: usb@...00000 {
>
> insert location above usb@...80000 is sorted wrong
So, *how* do you think things are sorted here? Alphabetical by label? Or
by node name? Or by unit address? I guess I'm seeing you meant unit
address. But pcie@...00000 is also out of order then. I guess maybe
that's the only one then.
> > + compatible = "rockchip,rk3399-dwc3";
> > + #address-cells = <2>;
> > + #size-cells = <2>;
> > + ranges;
> > + clocks = <&cru SCLK_USB3OTG0_REF>, <&cru SCLK_USB3OTG0_SUSPEND>,
> > + <&cru ACLK_USB3OTG0>, <&cru ACLK_USB3_RKSOC_AXI_PERF>,
> > + <&cru ACLK_USB3>, <&cru ACLK_USB3_GRF>;
> > + clock-names = "clk_usb3otg0_ref", "clk_usb3otg0_suspend",
> > + "aclk_usb3otg0", "aclk_usb3_rksoc_axi_perf",
> > + "aclk_usb3", "aclk_usb3_grf";
>
> clock-names do not match binding. The dwc3-of-simple does not care, as it just
> enables all of them it seems, but binding doc states the clock names as
>
> - clock-names: Should contain the following:
> "ref_clk" Controller reference clk, have to be 24 MHz
> "suspend_clk" Controller suspend clk, have to be 24 MHz or 32 KHz
> "bus_clk" Master/Core clock, have to be >= 62.5 MHz for SS
> operation and >= 30MHz for HS operation
> "grf_clk" Controller grf clk
Ah, sorry. I'll try to go with the rockchip,dwc3.txt names better.
There are a few extra clocks here now, but I think those might only be
for USB3 support, which isn't really working yet. I'll either document
them or drop them.
> > + resets = <&cru SRST_A_USB3_OTG0>;
> > + reset-names = "usb3-otg";
>
> you could update the binding documentation to list this one.
Similar story; this is only used for some of the hacky stuff Rockchip is
doing for USB3/TypeC stuff out of tree. I'll either document it or drop
it (as I'm not actually using it yet).
Thanks,
Brian
> Heiko
>
> > + status = "disabled";
> > +
> > + usbdrd_dwc3_0: dwc3 {
> > + compatible = "snps,dwc3";
> > + reg = <0x0 0xfe800000 0x0 0x100000>;
> > + interrupts = <GIC_SPI 105 IRQ_TYPE_LEVEL_HIGH 0>;
> > + dr_mode = "otg";
> > + phys = <&u2phy0_otg>;
> > + phy-names = "usb2-phy";
> > + snps,dis_enblslpm_quirk;
> > + snps,dis-u2-freeclk-exists-quirk;
> > + snps,dis_u2_susphy_quirk;
> > + snps,dis-del-phy-power-chg-quirk;
> > + status = "disabled";
> > + };
> > + };
[...]
Powered by blists - more mailing lists