[PATCH] pinctrl: sunxi: Use minimal debouncing period as default
Maxime Ripard
mripard at kernel.org
Tue Dec 17 05:58:52 PST 2024
On Tue, Dec 17, 2024 at 02:41:36PM +0100, Linus Walleij wrote:
> On Tue, Nov 19, 2024 at 3:43 PM Maxime Ripard <mripard at kernel.org> wrote:
>
> > [Paul]
> > > 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 273 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20241217/f4b40c3e/attachment.sig>
More information about the linux-arm-kernel
mailing list