Thread (23 messages) 23 messages, 4 authors, 2012-05-04

Re: GPIO debounce problems on 3.2

From: Grazvydas Ignotas <hidden>
Date: 2012-01-31 01:00:48

On Tue, Jan 31, 2012 at 2:22 AM, Kevin Hilman [off-list ref] wrote:
Paul Walmsley [off-list ref] writes:
quoted
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 majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help