On Tue, Jan 31, 2012 at 2:22 AM, Kevin Hilman <khil...@ti.com> wrote: > Paul Walmsley <p...@pwsan.com> writes: > >> That's probably I/O ring/pad wakeups happening there, not GPIO wakeups. >> Gražvydas, you are referring to the case where the CORE powerdomain is on, >> but the GPIO IP block is idle? > > Right good point. > > If CORE is powerdomain is staying on, you might also have a look at the > "GPIO module-level wakeups not always working" item in the "Known > problems" section of the OMAP PM wiki: > > http://elinux.org/OMAP_Power_Management#Known_Problems > > It might be the case that haven't done a request_irq() + > enable_irq_wake() for those GPIOs.
Well I'm just using standard gpio_keys driver, which does request_threaded_irq(), I guess that's good enough? I've also tried sticking enable_irq_wake() just after it but that didn't help. -- Gražvydas -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
