Thread (16 messages) 16 messages, 3 authors, 2025-01-07

Re: [PATCH] pinctrl: sunxi: Use minimal debouncing period as default

From: Maxime Ripard <mripard@kernel.org>
Date: 2024-12-17 13:58:55
Also in: linux-sunxi, lkml

On Tue, Dec 17, 2024 at 02:41:36PM +0100, Linus Walleij wrote:
On Tue, Nov 19, 2024 at 3:43 PM Maxime Ripard [off-list ref] wrote:
quoted
[Paul]
quoted
The pinctrl code supports an input-debounce device-tree property to set
a specific debouncing period and choose which clock source is most
relevant. However the property is specified in microseconds, which is
longer than the minimal period achievable from the high-frequency
oscillator without a pre-scaler.
That can be fixed by introducing a new property with a ns resolution.
Perhaps, but I think a setting of 0 should just yield the minimum
resolution in this case, as apparently the debounce cannot be
turned off? This would also make sense to expose for
gpiod_set_debounce() as explained in my other mail.
Yeah, if we want to have 0 == lowest resolution, I'm all for it.

Maxime

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help