From: Matthias Kaehlcke <mka@chromium.org>
To: "Sandeep Maheswaram (Temp)" <sanm@codeaurora.org>
Cc: Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Boyd <swboyd@chromium.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Manu Gautam <mgautam@codeaurora.org>
Subject: Re: [PATCH v3 1/1] arm64: dts: qcom: sc7180: Add USB related nodes
Date: Wed, 27 Nov 2019 08:49:56 -0800 [thread overview]
Message-ID: <20191127164956.GF228856@google.com> (raw)
In-Reply-To: <0101016eac17bc4a-9bcb2dd5-bcb0-4532-84ff-c423179bfec4-000000@us-west-2.amazonses.com>
On Wed, Nov 27, 2019 at 09:01:07AM +0000, Sandeep Maheswaram (Temp) wrote:
> Hi Matthias,
>
> Thanks for the review.
>
> On 11/22/2019 6:21 AM, Matthias Kaehlcke wrote:
> > Hi Sandeep,
> >
> > On Fri, Nov 15, 2019 at 10:53:41AM +0530, Sandeep Maheswaram wrote:
> > > Add nodes for DWC3 USB controller, QMP and QUSB PHYs.
> > >
> > > Signed-off-by: Sandeep Maheswaram <sanm@codeaurora.org>
> > > Reviewed-by: Stephen Boyd <swboyd@chromium.org>
> > > ---
> > > arch/arm64/boot/dts/qcom/sc7180-idp.dts | 25 ++++++++
> > > arch/arm64/boot/dts/qcom/sc7180.dtsi | 105 ++++++++++++++++++++++++++++++++
> > > 2 files changed, 130 insertions(+)
> > >
> > > diff --git a/arch/arm64/boot/dts/qcom/sc7180.dtsi b/arch/arm64/boot/dts/qcom/sc7180.dtsi
> > > index 666e9b9..2c7dbdc 100644
> > > --- a/arch/arm64/boot/dts/qcom/sc7180.dtsi
> > > +++ b/arch/arm64/boot/dts/qcom/sc7180.dtsi
> > >
> > > ...
> > >
> > > + usb_1: usb@a6f8800 {
> > > + compatible = "qcom,sc7180-dwc3", "qcom,dwc3";
> > > + reg = <0 0x0a6f8800 0 0x400>;
> > > + status = "disabled";
> > > + #address-cells = <2>;
> > > + #size-cells = <2>;
> > > + ranges;
> > > + dma-ranges;
> > > +
> > > + clocks = <&gcc GCC_CFG_NOC_USB3_PRIM_AXI_CLK>,
> > > + <&gcc GCC_USB30_PRIM_MASTER_CLK>,
> > > + <&gcc GCC_AGGRE_USB3_PRIM_AXI_CLK>,
> > > + <&gcc GCC_USB30_PRIM_MOCK_UTMI_CLK>,
> > > + <&gcc GCC_USB30_PRIM_SLEEP_CLK>;
> > > + clock-names = "cfg_noc", "core", "iface", "mock_utmi",
> > > + "sleep";
> > > +
> > > + assigned-clocks = <&gcc GCC_USB30_PRIM_MOCK_UTMI_CLK>,
> > > + <&gcc GCC_USB30_PRIM_MASTER_CLK>;
> > > + assigned-clock-rates = <19200000>, <150000000>;
> > > +
> > > + interrupts = <GIC_SPI 131 IRQ_TYPE_LEVEL_HIGH>,
> > > + <GIC_SPI 486 IRQ_TYPE_LEVEL_HIGH>,
> > > + <GIC_SPI 488 IRQ_TYPE_LEVEL_HIGH>,
> > > + <GIC_SPI 489 IRQ_TYPE_LEVEL_HIGH>;
> > > + interrupt-names = "hs_phy_irq", "ss_phy_irq",
> > > + "dm_hs_phy_irq", "dp_hs_phy_irq";
> > > +
> > > + power-domains = <&gcc USB30_PRIM_GDSC>;
> > > +
> > > + resets = <&gcc GCC_USB30_PRIM_BCR>;
> > > +
> > > + usb_1_dwc3: dwc3@a600000 {
> > > + compatible = "snps,dwc3";
> > > + reg = <0 0x0a600000 0 0xe000>;
> > > + interrupts = <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
> > > + iommus = <&apps_smmu 0x540 0>;
> > > + snps,dis_u2_susphy_quirk;
> > > + snps,dis_enblslpm_quirk;
> > > + phys = <&usb_1_hsphy>, <&usb_1_ssphy>;
> > > + phy-names = "usb2-phy", "usb3-phy";
> > > + };
> > I see the following message at boot:
> >
> > [ 4.248436] dwc3 a600000.dwc3: Failed to get clk 'ref': -2
> >
> > Apparently the driver is operational regardless, however the binding lists
> > the clocks as required:
> >
> > Required properties:
> > ...
> > - clock-names: should contain "ref", "bus_early", "suspend"
> > - clocks: list of phandle and clock specifier pairs corresponding to
> > entries in the clock-names property.
> >
> > [Documentation/devicetree/bindings/usb/dwc3.txt]
> >
> > The driver code also has a comment stating that the clocks should be
> > specified:
> >
> > /*
> > * Clocks are optional, but new DT platforms should support all
> > * clocks as required by the DT-binding.
> > */
> >
> > [drivers/usb/dwc3/core.txt]
> We are implenting all the required clocks in glue driver
> drivers/usb/dwc3/dwc3-qcom.c.
>
> Also there is exception for qcom,dwc3 in documentation
>
> Documentation/devicetree/bindings/usb/dwc3.txt
>
>
> Exception for clocks:
>
> clocks are optional if the parent node (i.e. glue-layer) is compatible to
> one of the following:
> "amlogic,meson-axg-dwc3"
> "amlogic,meson-gxl-dwc3"
> "cavium,octeon-7130-usb-uctl"
> "qcom,dwc3"
> "samsung,exynos5250-dwusb3"
> "samsung,exynos5433-dwusb3"
> "samsung,exynos7-dwusb3"
> "sprd,sc9860-dwc3"
> "st,stih407-dwc3"
> "ti,am437x-dwc3"
> "ti,dwc3"
> "ti,keystone-dwc3"
> "rockchip,rk3399-dwc3"
> "xlnx,zynqmp-dwc3"
ah, I missed this, thanks for the pointer!
next prev parent reply other threads:[~2019-11-27 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 5:23 [PATCH v3 0/1] Add USB related nodes for SC7180 Sandeep Maheswaram
2019-11-15 5:23 ` [PATCH v3 1/1] arm64: dts: qcom: sc7180: Add USB related nodes Sandeep Maheswaram
2019-11-22 0:51 ` Matthias Kaehlcke
2019-11-27 9:01 ` Sandeep Maheswaram (Temp)
[not found] ` <0101016eac17bc4a-9bcb2dd5-bcb0-4532-84ff-c423179bfec4-000000@us-west-2.amazonses.com>
2019-11-27 16:49 ` Matthias Kaehlcke [this message]
2019-11-28 22:11 ` Bjorn Andersson
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=20191127164956.GF228856@google.com \
--to=mka@chromium.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mgautam@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sanm@codeaurora.org \
--cc=swboyd@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.