From: Andreas Kemnade <andreas@kemnade.info>
To: dmitry.torokhov@gmail.com, andreas@kemnade.info,
bartosz.golaszewski@oss.qualcomm.com, arnd@arndb.de,
marco.crivellari@suse.com, tony@atomide.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
brgl@kernel.org
Subject: [PATCH v2] Input: gpio-keys - do not BUG() on requested wakeirqs
Date: Sat, 7 Nov 2026 11:48:07 +0100 [thread overview]
Message-ID: <20261107104807.54410-1-andreas@kemnade.info> (raw)
Having the IRQ handler called when enabled IRQs arrive should be considered
as a feature not as a bug. So do not BUG() there when this happens.
Also BUG() is too harsh here.
Fixes: 3717194f24922 ("Input: gpio-keys - add system suspend support for dedicated wakeirqs")
Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
---
Changes in v2:
do not BUG() at all here and remove the other similar instance of this
BUG().
drivers/input/keyboard/gpio_keys.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/drivers/input/keyboard/gpio_keys.c b/drivers/input/keyboard/gpio_keys.c
index fbc31c5db3db4..41a9210b40176 100644
--- a/drivers/input/keyboard/gpio_keys.c
+++ b/drivers/input/keyboard/gpio_keys.c
@@ -412,8 +412,6 @@ static irqreturn_t gpio_keys_gpio_isr(int irq, void *dev_id)
{
struct gpio_button_data *bdata = dev_id;
- BUG_ON(irq != bdata->irq);
-
if (bdata->button->wakeup) {
const struct gpio_keys_button *button = bdata->button;
@@ -465,8 +463,6 @@ static irqreturn_t gpio_keys_irq_isr(int irq, void *dev_id)
struct gpio_button_data *bdata = dev_id;
struct input_dev *input = bdata->input;
- BUG_ON(irq != bdata->irq);
-
guard(spinlock_irqsave)(&bdata->lock);
if (!bdata->key_pressed) {
--
2.47.3
reply other threads:[~2026-11-07 10:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261107104807.54410-1-andreas@kemnade.info \
--to=andreas@kemnade.info \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=tony@atomide.com \
/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
all inboxes | Powered by JetHome®