On 10/10/2013 07:23 PM, Tony Lindgren wrote: > * Tony Lindgren <tony@xxxxxxxxxxx> [131010 09:09]: >> * Roger Quadros <rogerq@xxxxxx> [131010 06:32]: >>> >>> I tried testing this with the USB EHCI driver, but I'm not getting wake up interrupts >>> while the system is still running and only the EHCI controller is runtime suspended. >>> >>> It seems we need to somehow call _reconfigure_io_chain() to update the daisy chain >>> whenever the pad wakeup_enable bit is changed. >> >> Sounds like this is on omap3? Have you tried calling pcs_soc->rearm() in the >> pcs_irq_handle() like the comments there suggest? At least for me that keeps >> the wake-up interrupts continuously running on omap3 instead of just idle modes. >> >> Now on omap4, I've noticed the wake up interrupts are on all the time based on tests >> with the serial driver. > > Oh, and if you're runtime suspending EHCI only, and if the EHCI module has > wake-up registers, it should be able to wake EHCI from retention on it's own > without a need for the io chain at all. > The problem is that the asynchronous wake up mechanism for USB Host module is broken in the design so we have to rely on IO daisy chain every time. :( cheers, -roger -- 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
