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 <[email protected]>
> > 
> > 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 <[email protected]>
> > Reviewed-by: Kevin Hilman <[email protected]>
> > Reviewed-by: Partha Basak <[email protected]>
> 
> 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 <[email protected]>
> 
> 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 <[email protected]>

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to