Zephyr debounce support

RE: Zephyr debounce support

Hieu — Fri, 05 Sep 2025 21:26:05 GMT

Hi Yaxit,

You are right. My apology. I misunderstood the source files back then. Indeed, the default GPIO driver, enabled with just CONFIG_GPIO, doesn't provide the gpio-keys input driver functionality. We would need to enable CONFIG_INPUT_GPIO_KEYS and use the driver like in the link you gave. Thank you for the correction.

RE: Zephyr debounce support

Yaxit — Tue, 02 Sep 2025 15:06:32 GMT

This answer seems misleading, and I think it's creating confusion. As far as I know, the GPIO driver does not provide debouncing. Debouncing is provided by the gpio-keys input driver, which has a completely different API.
An example here: github.com/.../main.c

RE: Zephyr debounce support

Hieu — Tue, 18 Jun 2024 11:55:38 GMT

Hi Hiroshi,

It seems that the default Zephyr GPIO driver has some software debouncing integrated.
Update 08 Sep 2025: The information above is incorrect. The default Zephyr GPIO driver, which is enabled with CONFIG_GPIO, doesn't use the gpio-keys debounce property. Refer to the later replies to this.

The feature is requested here: https://github.com/zephyrproject-rtos/zephyr/issues/52344
and added here: https://github.com/zephyrproject-rtos/zephyr/pull/52698.

It is also documented here: gpio-keys (nordicsemi.com).

Please give it a try and see if it works for you.

If that doesn't match your requirement, then there is an article from Golioth on how to setup your own debouncing on the Zephyr project site: How to Debounce Button Inputs in Real Time Operating Systems – Zephyr Project.

Hieu