[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241217-impossible-chameleon-of-flowers-8ce18a@houat>
Date: Tue, 17 Dec 2024 14:58:52 +0100
From: Maxime Ripard <mripard@...nel.org>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Paul Kocialkowski <paulk@...-base.io>,
linux-arm-kernel@...ts.infradead.org, linux-sunxi@...ts.linux.dev, linux-kernel@...r.kernel.org,
Uwe Kleine-König <ukleinek@...nel.org>, Chen-Yu Tsai <wens@...e.org>,
Jernej Skrabec <jernej.skrabec@...il.com>, Samuel Holland <samuel@...lland.org>,
Paul Kocialkowski <contact@...lk.fr>
Subject: Re: [PATCH] pinctrl: sunxi: Use minimal debouncing period as default
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@...nel.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
Download attachment "signature.asc" of type "application/pgp-signature" (274 bytes)
Powered by blists - more mailing lists