[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aFw5_rnz2dPdQcNG@smile.fi.intel.com>
Date: Wed, 25 Jun 2025 21:03:42 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: "Limonciello, Mario" <Mario.Limonciello@....com>
Cc: Mario Limonciello <superm1@...nel.org>,
Hans de Goede <hansg@...nel.org>,
Mika Westerberg <westeri@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
"open list:GPIO ACPI SUPPORT" <linux-gpio@...r.kernel.org>,
"open list:GPIO ACPI SUPPORT" <linux-acpi@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
"open list:INPUT (KEYBOARD, MOUSE, JOYSTICK, TOUCHSCREEN)..." <linux-input@...r.kernel.org>
Subject: Re: [PATCH 2/2] Revert "Input: soc_button_array - debounce the
buttons"
On Wed, Jun 25, 2025 at 05:59:50PM +0000, Limonciello, Mario wrote:
> On 6/25/25 12:54 PM, Andy Shevchenko wrote:
> > On Wed, Jun 25, 2025 at 03:34:55PM +0000, Limonciello, Mario wrote:
> >> On 6/25/25 10:17 AM, Andy Shevchenko wrote:
...
> > Probably gpiod_set_debounce() should become a no-op in this case?
>
> But my point is this 50 needs to be a quirk /somewhere/. It shouldn't
> be a default behavior.
>
> It can be in the GPIO driver(s), it can be in soc-button-array, or it
> can be in gpio_keys.
>
> I've got an idea mocked up for a v2, I'll send that out and I think we
> can discuss the merits of it on that series.
Sure, thanks!
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists