From: Andy Gross <agross@codeaurora.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Felipe Balbi <balbi@ti.com>,
jackp@codeaurora.org,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Linux USB List <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Ivan T. Ivanov" <iivanov@mm-sol.com>,
Kumar Gala <galak@codeaurora.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Patch v7 3/3] usb: dwc3: qcom: Add device tree binding
Date: Tue, 1 Jul 2014 13:01:14 -0500 [thread overview]
Message-ID: <20140701180114.GA2082@qualcomm.com> (raw)
In-Reply-To: <CAL_JsqJTO4htxHMVtMG6mGLmgRtQ7igE1OCX_jXM4xabN76ntg@mail.gmail.com>
On Tue, Jul 01, 2014 at 12:04:35AM -0500, Rob Herring wrote:
<snip>
> > +- clock-names: Should contain the following:
> > + "core" Master/Core clock, have to be >= 125 MHz for SS
> > + operation and >= 60MHz for HS operation
> > +
> > +Optional clocks:
> > + "iface" System bus AXI clock. Not present on all platforms
>
> Really?, some platforms have a clockless bus?
Some platforms require core and interface. The specific platform I tested on
does not have an iface clk. I'll take a look at the ipq block diagram to see if
they did something cute, but i don't believe there is one.
>
> > + "sleep" Sleep clock, used when USB3 core goes into low
> > + power mode (U3).
> > +
> > +Optional regulator:
> > +- gdsc-supply: phandle to the regulator from globally distributed
> > + switch controller
>
> The name should reflect the name of the input, not the source.
Ok, I'll revisit this. I took this from the original patch set.
<snip>
> > +
> > + ranges;
> > +
> > + status = "disabled";
> > +
> > + dwc3@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.
--
sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: agross@codeaurora.org (Andy Gross)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v7 3/3] usb: dwc3: qcom: Add device tree binding
Date: Tue, 1 Jul 2014 13:01:14 -0500 [thread overview]
Message-ID: <20140701180114.GA2082@qualcomm.com> (raw)
In-Reply-To: <CAL_JsqJTO4htxHMVtMG6mGLmgRtQ7igE1OCX_jXM4xabN76ntg@mail.gmail.com>
On Tue, Jul 01, 2014 at 12:04:35AM -0500, Rob Herring wrote:
<snip>
> > +- clock-names: Should contain the following:
> > + "core" Master/Core clock, have to be >= 125 MHz for SS
> > + operation and >= 60MHz for HS operation
> > +
> > +Optional clocks:
> > + "iface" System bus AXI clock. Not present on all platforms
>
> Really?, some platforms have a clockless bus?
Some platforms require core and interface. The specific platform I tested on
does not have an iface clk. I'll take a look at the ipq block diagram to see if
they did something cute, but i don't believe there is one.
>
> > + "sleep" Sleep clock, used when USB3 core goes into low
> > + power mode (U3).
> > +
> > +Optional regulator:
> > +- gdsc-supply: phandle to the regulator from globally distributed
> > + switch controller
>
> The name should reflect the name of the input, not the source.
Ok, I'll revisit this. I took this from the original patch set.
<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.
--
sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-07-01 18:01 UTC|newest]
Thread overview: 37+ 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 ` 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:03 ` Andy Gross
2014-06-30 16:52 ` Felipe Balbi
2014-06-30 16:52 ` Felipe Balbi
2014-06-30 16:52 ` Felipe Balbi
2014-07-18 2:10 ` Jingoo Han
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 16:03 ` Andy Gross
2014-06-30 17:00 ` Felipe Balbi
2014-06-30 17:00 ` Felipe Balbi
2014-06-30 17:00 ` Felipe Balbi
[not found] ` <CA+neC=McWS8=iSi2XShJyvc85Aw4PSmF-osNpVgJv42d9or1WQ@mail.gmail.com>
2014-07-17 10:30 ` kiran.padwal
2014-07-17 10:30 ` kiran.padwal
2014-07-17 10:30 ` kiran.padwal at smartplayin.com
[not found] ` <1405593024.423213197-0ZYIasU8DW2IAIbY1eLdq9BPR1lH4CV8@public.gmane.org>
2014-07-17 18:28 ` Andy Gross
2014-07-17 18:28 ` Andy Gross
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 16:03 ` Andy Gross
2014-06-30 17:37 ` Kumar Gala
2014-06-30 17:37 ` Kumar Gala
2014-07-01 5:04 ` Rob Herring
2014-07-01 5:04 ` Rob Herring
2014-07-01 18:01 ` Andy Gross [this message]
2014-07-01 18:01 ` Andy Gross
2014-07-01 19:47 ` Rob Herring
2014-07-01 19:47 ` Rob Herring
2014-07-02 8:43 ` Ivan T. Ivanov
2014-07-02 8:43 ` Ivan T. Ivanov
2014-07-02 12:48 ` Arnd Bergmann
2014-07-02 12:48 ` Arnd Bergmann
2014-07-02 15:54 ` Felipe Balbi
2014-07-02 15:54 ` Felipe Balbi
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=20140701180114.GA2082@qualcomm.com \
--to=agross@codeaurora.org \
--cc=balbi@ti.com \
--cc=galak@codeaurora.org \
--cc=iivanov@mm-sol.com \
--cc=jackp@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robherring2@gmail.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 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.