lkml.org 
[lkml]   [2011]   [Oct]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 5/5 v14] omap: usb: host: Replace usbhs core driver APIs by Runtime pm APIs
On Thu, 13 Oct 2011, Felipe Balbi wrote:

> Hi,
>
> On Tue, Oct 11, 2011 at 01:22:11PM +0530, Keshava Munegowda wrote:
> > From: Keshava Munegowda <Keshava_mgowda@ti.com>
> >
> > The ehci and ohci drivers does not use the APIs of the usbhs
> > core driver; the runtime pm APIs are used for clock
> > enable/disable. Since usbhs is parent platform device of the
> > ehci and ohci devices, the runtime apis indirectly uses the
> > usb hs core device as input parameter to for clock functions.
> >
> > Signed-off-by: Keshava Munegowda <keshava_mgowda@ti.com>
> > Reviewed-by: Kevin Hilman <khilman@ti.com>
> > Reviewed-by: Partha Basak <parthab@india.ti.com>
>
> I'm not sure who should queue this one. Alan, maybe ?

All my stuff goes by way of Greg in any case.

> FWIW:
>
> Acked-by: Felipe Balbi <balbi@ti.com>
>
> as an extra comment, this patch has a very deep dependency on the hwmod
> conversion patches which come before this. If those aren't applied on
> the same merge window, we will have a non-working *HCI driver on OMAP.

To keep things simple, this patch should go through the same submission
path as the others in the series. I view it more as an OMAP thing than
an EHCI thing anyway. For the record:

Acked-by: Alan Stern <stern@rowland.harvard.edu>

Alan Stern



\
 
 \ /
  Last update: 2011-10-13 20:15    [W:0.480 / U:0.260 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site