Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-04-04 Thread David Lechner
On 04/04/2016 03:45 AM, Petr Kulhavy wrote: I'm trying to move on with my USB2.0 patch set because my projects is blocked waiting for it. I've seen your PHY patch but it contains only on/off functions and does not handle the clocks, which IMHO should be moved to the PHY driver as well if we decid

Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-04-04 Thread Petr Kulhavy
On 15.03.2016 03:07, David Lechner wrote: On 03/14/2016 02:00 AM, Felipe Balbi wrote: Hi, why isn't this an actual clock phandle ? Driver could, then, use clk_get_rate() to figure this one out. You could just use a fixed clock here to satisfy the clock API. I've actually been working on g

Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-03-19 Thread Petr Kulhavy
On 11.03.2016 19:24, Sergei Shtylyov wrote: On 03/11/2016 07:21 PM, Petr Kulhavy wrote: I am having 2nd thought on parsing the clock prop, Sergei's comment might be better. I will look more on this over this weekend. (DT is not in my expertise...) Regards, -Bin. I like Sergei's comment as

Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-03-18 Thread Rob Herring
On Fri, Mar 11, 2016 at 09:29:45AM +0100, Petr Kulhavy wrote: > DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver. > > Signed-off-by: Petr Kulhavy > --- > v1: > > v2: > - using standard properties "dr_mode", "mentor,power", "mentor,num-eps", > "mentor,multipoint", "mentor,ram-bit

Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-03-15 Thread Felipe Balbi
Hi, David Lechner writes: > [ text/plain ] > On 03/14/2016 02:00 AM, Felipe Balbi wrote: >> >> Hi, >> >> Petr Kulhavy writes: >>> + - ti,usb2-phy-refclock-hz : Integer. Frequency in Hz of the USB 2.0 PHY >>> reference clock, >>> + either provided by the internal PLL or an external source.

Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-03-14 Thread David Lechner
On 03/14/2016 02:00 AM, Felipe Balbi wrote: Hi, Petr Kulhavy writes: + - ti,usb2-phy-refclock-hz : Integer. Frequency in Hz of the USB 2.0 PHY reference clock, + either provided by the internal PLL or an external source. + The supported values are: 12MHz, 13MHz, 19.2MHz, 20MHz, 24MHz

Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-03-14 Thread Felipe Balbi
Hi, Petr Kulhavy writes: > + - ti,usb2-phy-refclock-hz : Integer. Frequency in Hz of the USB 2.0 PHY > reference clock, > + either provided by the internal PLL or an external source. > + The supported values are: 12MHz, 13MHz, 19.2MHz, 20MHz, 24MHz, 26MHz, > 38.4MHz, 40MHz, 48MHz. why

Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-03-11 Thread Bin Liu
Hi, On Fri, Mar 11, 2016 at 09:27:23PM +0300, Sergei Shtylyov wrote: > On 03/11/2016 06:51 PM, Bin Liu wrote: > > >>DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver. > > > >It seems the dts(i) file is not touched in this patch set, so DA8xx MUSB > >still does not use DT with these p

Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-03-11 Thread Sergei Shtylyov
On 03/11/2016 06:51 PM, Bin Liu wrote: DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver. It seems the dts(i) file is not touched in this patch set, so DA8xx MUSB still does not use DT with these patches? Or did I miss anything? The .dts[i] patches go thru the arm-soc tree.

Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-03-11 Thread Sergei Shtylyov
On 03/11/2016 07:21 PM, Petr Kulhavy wrote: I am having 2nd thought on parsing the clock prop, Sergei's comment might be better. I will look more on this over this weekend. (DT is not in my expertise...) Regards, -Bin. I like Sergei's comment as well, but cannot see (yet) how the clock input

Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-03-11 Thread Petr Kulhavy
On 11.03.2016 17:06, Bin Liu wrote: Hi, On Fri, Mar 11, 2016 at 04:58:52PM +0100, Petr Kulhavy wrote: On 11.03.2016 16:51, Bin Liu wrote: Hi, On Fri, Mar 11, 2016 at 09:29:45AM +0100, Petr Kulhavy wrote: DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver. It seems the dts(i)

Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-03-11 Thread Bin Liu
Hi, On Fri, Mar 11, 2016 at 04:58:52PM +0100, Petr Kulhavy wrote: > > > On 11.03.2016 16:51, Bin Liu wrote: > >Hi, > > > >On Fri, Mar 11, 2016 at 09:29:45AM +0100, Petr Kulhavy wrote: > >>DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver. > >It seems the dts(i) file is not touched i

Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-03-11 Thread Petr Kulhavy
On 11.03.2016 16:51, Bin Liu wrote: Hi, On Fri, Mar 11, 2016 at 09:29:45AM +0100, Petr Kulhavy wrote: DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver. It seems the dts(i) file is not touched in this patch set, so DA8xx MUSB still does not use DT with these patches? Or did I m

Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-03-11 Thread Bin Liu
Hi, On Fri, Mar 11, 2016 at 09:29:45AM +0100, Petr Kulhavy wrote: > DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver. It seems the dts(i) file is not touched in this patch set, so DA8xx MUSB still does not use DT with these patches? Or did I miss anything? Thanks, -Bin. > > Sign

Re: [PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-03-11 Thread Sergei Shtylyov
On 3/11/2016 11:29 AM, Petr Kulhavy wrote: DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver. Signed-off-by: Petr Kulhavy Acked-by: Sergei Shtylyov MBR, Sergei -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.k

[PATCH 1/5 v10] dt/bindings: Add binding for the DA8xx MUSB driver

2016-03-11 Thread Petr Kulhavy
DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver. Signed-off-by: Petr Kulhavy --- v1: v2: - using standard properties "dr_mode", "mentor,power", "mentor,num-eps", "mentor,multipoint", "mentor,ram-bits" - using "ti," prefix instead of "da8xx," for specific property names - no w