| Message ID | 5121F945.1020907@ti.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
Roger Quadros <rogerq@ti.com> writes: > On 02/15/2013 05:54 PM, Kevin Hilman wrote: >> Roger Quadros <rogerq@ti.com> writes: >> >>> Hi Kevin, >>> >>> On 02/15/2013 12:50 AM, Kevin Hilman wrote: >>>> Felipe, Roger, >>>> >>>> Using Tony's current master branch, and enabling EHCI support, I see >>>> the clock framework spitting loudly about the EHCI driver (full boot log >>>> below.) The same thing happens on v3.8-rc7. >>>> >>>> Any idea what's going on? Am I missing a set of fixes that's already >>>> been posted? >>> >>> Thanks for pointing out. This series should fix the issues >>> https://lkml.org/lkml/2013/1/23/155 >>> >>> They should be on their way to linux-next. >> >> Great. But what about v3.8? I see the same problems in v3.8-rc7. >> > > Kevin, the fix is below for older kernels. Tested-by: Kevin Hilman <khilman@linaro.org> Thanks, tested on v3.8-rc and works great. Are you planning on submitting this for v3.8 via stable? Thanks, Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 02/18/2013 04:47 PM, Kevin Hilman wrote: > Roger Quadros <rogerq@ti.com> writes: > >> On 02/15/2013 05:54 PM, Kevin Hilman wrote: >>> Roger Quadros <rogerq@ti.com> writes: >>> >>>> Hi Kevin, >>>> >>>> On 02/15/2013 12:50 AM, Kevin Hilman wrote: >>>>> Felipe, Roger, >>>>> >>>>> Using Tony's current master branch, and enabling EHCI support, I see >>>>> the clock framework spitting loudly about the EHCI driver (full boot log >>>>> below.) The same thing happens on v3.8-rc7. >>>>> >>>>> Any idea what's going on? Am I missing a set of fixes that's already >>>>> been posted? >>>> >>>> Thanks for pointing out. This series should fix the issues >>>> https://lkml.org/lkml/2013/1/23/155 >>>> >>>> They should be on their way to linux-next. >>> >>> Great. But what about v3.8? I see the same problems in v3.8-rc7. >>> >> >> Kevin, the fix is below for older kernels. > > Tested-by: Kevin Hilman <khilman@linaro.org> > > Thanks, tested on v3.8-rc and works great. Are you planning on > submitting this for v3.8 via stable? > OK I'll do that. cheers, -roger -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/drivers/mfd/omap-usb-host.c b/drivers/mfd/omap-usb-host.c index 05164d7..f6f5b18 100644 --- a/drivers/mfd/omap-usb-host.c +++ b/drivers/mfd/omap-usb-host.c @@ -299,9 +299,6 @@ static int usbhs_runtime_resume(struct device *dev) if (is_ehci_tll_mode(pdata->port_mode[1])) clk_enable(omap->usbhost_p2_fck); - clk_enable(omap->utmi_p1_fck); - clk_enable(omap->utmi_p2_fck); - spin_unlock_irqrestore(&omap->lock, flags); return 0; @@ -327,9 +324,6 @@ static int usbhs_runtime_suspend(struct device *dev) if (is_ehci_tll_mode(pdata->port_mode[1])) clk_disable(omap->usbhost_p2_fck); - clk_disable(omap->utmi_p2_fck); - clk_disable(omap->utmi_p1_fck); - if (omap->ehci_logic_fck && !IS_ERR(omap->ehci_logic_fck)) clk_disable(omap->ehci_logic_fck);