On Mon, Jul 23, 2012 at 2:03 PM, Roger Quadros <rogerq@xxxxxx> wrote: > Hi, > > On 06/22/2012 05:43 PM, Munegowda, Keshava wrote: >> On Fri, Jun 22, 2012 at 7:41 PM, Kevin Hilman <khilman@xxxxxx> wrote: >>> "Munegowda, Keshava" <keshava_mgowda@xxxxxx> writes: >>> >>> [...] >>> > >>> >>> You are not reading what I write. >>> >>> To repeat: your patch fixes the oops during boot, and the suspend hang >>> and now I see CORE hit retention in *suspend*. >> >> thanks ! >> >>> >>> However, CORE does still not hit retention during *idle*. >> >> here is the problem. >> >> usb host retention in idle is not supported till now. >> in current code, usb host cuts clock only in driver suspend not in bus >> suspend ( auto suspend). >> usb host driver need to use the io daisy chain framework through io wakeup. >> I will post the patches once ehci remote wakeup features stabilized in >> omap3, omap4 and omap5 too. >> > > We are talking about CORE retention support during idle. How is IO daisy > chaining related to that? Doesn't IO daisy chain only apply when device > hits OFF? when we see the usb bus suspend, then we disable the clocks of usb host to enable to enable the retention in cpu idle; since we have disabled the clock of usb host , we will not see the device connection at the controller level, instead the irq chain handler can detect it and corresponding irq can set the clocks. this same use case holds good for device OFF too. regards keshava -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
