Re: GPIO debounce problems on 3.2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Grazvydas Ignotas <notasas@xxxxxxxxx> writes:

> Hi,
>
> On 3.2 (I think some earlier versions too), with CONFIG_CPU_IDLE
> enabled GPIO based buttons are not working properly on OMAP3 pandora,
> button presses are almost never registered. The buttons are connected
> GPIO bank4 and have hardware debounce feature enabled.
>
> Doing either of the following solves (or hides) the problem:
> - disabling CPU_IDLE in kernel config
> - disabling debounce for the buttons
> - running a program spinning a loop on the CPU
>
> From what I can see in the code debounce clock is disabled when
> entering idle, can those GPIOs work without debounce clock?

Yes, the clock is only for the debounce feature, but the GPIOs are
capable of wakeups and interrupts with the debounce clock disabled.

Kevin
--
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


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux