Re: [PATCH v3 3/3] input: gpio-keys: Use hrtimer for software debounce, if possible

2021-04-06 Thread Dmitry Torokhov
On Tue, Apr 06, 2021 at 11:37:07AM +0300, Tony Lindgren wrote: > Hi, > > * Dmitry Torokhov [700101 02:00]: > > On Sun, Mar 07, 2021 at 10:22:40PM +, Paul Cercueil wrote: > > > We want to be able to report the input event as soon as the debounce > > > delay elapsed. However, the current code

Re: [PATCH v3 3/3] input: gpio-keys: Use hrtimer for software debounce, if possible

2021-04-06 Thread Tony Lindgren
Hi, * Dmitry Torokhov [700101 02:00]: > On Sun, Mar 07, 2021 at 10:22:40PM +, Paul Cercueil wrote: > > We want to be able to report the input event as soon as the debounce > > delay elapsed. However, the current code does not really ensure that, > > as it uses the jiffies-based

Re: [PATCH v3 3/3] input: gpio-keys: Use hrtimer for software debounce, if possible

2021-03-23 Thread Dmitry Torokhov
On Sun, Mar 07, 2021 at 10:22:40PM +, Paul Cercueil wrote: > We want to be able to report the input event as soon as the debounce > delay elapsed. However, the current code does not really ensure that, > as it uses the jiffies-based schedule_delayed_work() API. With a small > enough HZ value

[PATCH v3 3/3] input: gpio-keys: Use hrtimer for software debounce, if possible

2021-03-07 Thread Paul Cercueil
We want to be able to report the input event as soon as the debounce delay elapsed. However, the current code does not really ensure that, as it uses the jiffies-based schedule_delayed_work() API. With a small enough HZ value (HZ <= 100), this results in some input events being lost, when a key is