From: iivanov@mm-sol.com (Ivan T. Ivanov)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v7 3/3] usb: dwc3: qcom: Add device tree binding
Date: Wed, 02 Jul 2014 11:43:25 +0300 [thread overview]
Message-ID: <1404290605.3622.6.camel@iivanov-dev> (raw)
In-Reply-To: <CAL_JsqLjjDV50x5LCDeySvV0u4U1om-3KDkFHMd5WouC=eV8kw@mail.gmail.com>
Hi,
On Tue, 2014-07-01 at 14:47 -0500, Rob Herring wrote:
> On Tue, Jul 1, 2014 at 1:01 PM, Andy Gross <agross@codeaurora.org> wrote:
> > On Tue, Jul 01, 2014 at 12:04:35AM -0500, Rob Herring wrote:
<snip>
> > <snip>
> >
> >> > +
> >> > + ranges;
> >> > +
> >> > + status = "disabled";
> >> > +
> >> > + dwc3 at 11000000 {
> >> > + compatible = "snps,dwc3";
> >>
> >> This sub-node is just wrong. Why can't you have a single node with '
> >> "qcom,dwc3", "snps,dwc3" ' for the compatible property? All you are
> >> adding here is clocks. Does the Synopsys block have no clocks?
> >>
> >> I guess this is copied from other broken dwc3 bindings... That doesn't
> >> mean you have to copy it.
> >
> > The dwc3 core does not deal with clocks. That is why everyone has a wrapper.
> > That, in addition to pm, has to be handled from the wrapper. That's my take
> > anyway. I am sure Felipe can speak more to this.
>
> That is a Linux driver issue which is irrelevant to the binding.
DWC3 IP core from Synopsys is the same across SoC's (OMAP, Exynos..),
vendors are adding glue IP to provide necessary clocks and voltages.
I think that the DT bindings properly reflect this fact.
Regards,
Ivan
>
> Rob
next prev parent reply other threads:[~2014-07-02 8:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 16:03 [Patch v7 0/3] DWC3 USB support for Qualcomm platform Andy Gross
2014-06-30 16:03 ` [Patch v7 1/3] usb: dwc3: Add Qualcomm DWC3 glue layer driver Andy Gross
2014-06-30 16:52 ` Felipe Balbi
2014-07-18 2:10 ` Jingoo Han
2014-06-30 16:03 ` [Patch v7 2/3] usb: phy: Add Qualcomm DWC3 HS/SS PHY drivers Andy Gross
2014-06-30 17:00 ` Felipe Balbi
[not found] ` <CA+neC=McWS8=iSi2XShJyvc85Aw4PSmF-osNpVgJv42d9or1WQ@mail.gmail.com>
2014-07-17 10:30 ` kiran.padwal at smartplayin.com
2014-07-17 18:28 ` Andy Gross
2014-06-30 16:03 ` [Patch v7 3/3] usb: dwc3: qcom: Add device tree binding Andy Gross
2014-06-30 17:37 ` Kumar Gala
2014-07-01 5:04 ` Rob Herring
2014-07-01 18:01 ` Andy Gross
2014-07-01 19:47 ` Rob Herring
2014-07-02 8:43 ` Ivan T. Ivanov [this message]
2014-07-02 12:48 ` Arnd Bergmann
2014-07-02 15:54 ` Felipe Balbi
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=1404290605.3622.6.camel@iivanov-dev \
--to=iivanov@mm-sol.com \
--cc=linux-arm-kernel@lists.infradead.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).