linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: Hans de Goede <hansg@kernel.org>,
	Mika Westerberg <westeri@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-gpio@vger.kernel.org (open list:GPIO ACPI SUPPORT),
	linux-acpi@vger.kernel.org (open list:GPIO ACPI SUPPORT),
	linux-kernel@vger.kernel.org (open list),
	linux-input@vger.kernel.org (open list:INPUT (KEYBOARD, MOUSE,
	JOYSTICK, TOUCHSCREEN)...),
	Mario Limonciello <mario.limonciello@amd.com>
Subject: [PATCH v2 0/3] Fix soc-button-array debounce
Date: Wed, 25 Jun 2025 13:13:39 -0500	[thread overview]
Message-ID: <20250625181342.3175969-1-superm1@kernel.org> (raw)

From: Mario Limonciello <mario.limonciello@amd.com>

I have some hardware in front of me that uses the soc-button-array
driver but the power button doesn't work.

Digging into it, it's because the ASL prescribes a debounce of 0 for
the power button, but the soc-button-array driver hardcodes 50ms.

Hardcoding it to what the ASL expects the power button works.

I looked at the callpath into the GPIO core and I believe it's
because the debounce value from _CRS is never programmed to the
hardware the way that the GPIO gets setup.

This series add that programming path and then sets the hardcoded
value on on some quirked systems.  Hopefully Hans can confirm this
continues to work on the hardware that he originally developed the
hardcoding for.

---
v2:
 * Add a helper for making ACPI debounce program nonfatal
 * Use a quirk instead of a revert

Mario Limonciello (3):
  gpiolib: acpi: Add a helper for programming debounce
  gpiolib: acpi: Program debounce when finding GPIO
  Input: soc_button_array: Only debounce cherryview and baytrail systems

 drivers/gpio/gpiolib-acpi-core.c      | 25 ++++++++++++++-----------
 drivers/input/misc/soc_button_array.c | 21 ++++++++++++++++++++-
 2 files changed, 34 insertions(+), 12 deletions(-)

-- 
2.43.0


             reply	other threads:[~2025-06-25 18:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25 18:13 Mario Limonciello [this message]
2025-06-25 18:13 ` [PATCH v2 1/3] gpiolib: acpi: Add a helper for programming debounce Mario Limonciello
2025-06-25 18:58   ` Hans de Goede
2025-06-25 18:13 ` [PATCH v2 2/3] gpiolib: acpi: Program debounce when finding GPIO Mario Limonciello
2025-06-25 18:58   ` Hans de Goede
2025-06-25 18:13 ` [PATCH v2 3/3] Input: soc_button_array: Only debounce cherryview and baytrail systems Mario Limonciello
2025-06-25 19:03   ` Hans de Goede
2025-06-25 19:23     ` Mario Limonciello
2025-06-25 19:42       ` Hans de Goede
2025-06-25 20:34         ` Mario Limonciello
2025-06-26 18:27           ` Dmitry Torokhov
2025-06-26 18:30             ` Mario Limonciello
2025-06-26 18:53               ` Dmitry Torokhov
2025-06-26 18:58                 ` Mario Limonciello
2025-06-26 19:04                 ` Hans de Goede
2025-06-26 19:32                   ` Dmitry Torokhov
2025-06-26 19:37                     ` Mario Limonciello
2025-06-26 19:54                       ` Dmitry Torokhov
2025-06-26 21:39                         ` Mario Limonciello
2025-06-27  5:08                           ` Dmitry Torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250625181342.3175969-1-superm1@kernel.org \
    --to=superm1@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=brgl@bgdev.pl \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hansg@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=westeri@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).