From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Armando De Leon <auribe84@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Armando De Leon <learmand@amazon.com>
Subject: Re: [PATCH] Input: gpio-keys - add hibernation support
Date: Mon, 6 Apr 2026 09:24:15 -0700 [thread overview]
Message-ID: <adPdc2Z1SYxvqDmP@google.com> (raw)
In-Reply-To: <20260406160437.3084755-1-learmand@amazon.com>
Hi Armando,
On Mon, Apr 06, 2026 at 09:04:37AM -0700, Armando De Leon wrote:
> The gpio-keys driver uses DEFINE_SIMPLE_DEV_PM_OPS which maps .freeze
> and .restore to the same callbacks as .suspend and .resume. This is
> insufficient for hibernation (suspend-to-disk) because the SoC is fully
> powered off, unlike suspend-to-RAM where hardware state is preserved.
>
> After hibernation resume, GPIO keys fail to function correctly because
> the interrupt controller (e.g. GIC) is fully re-initialized during
> restore, resetting all IRQ trigger type configurations to defaults.
> GPIO keys require IRQ_TYPE_EDGE_BOTH for proper press/release detection,
> but after the interrupt controller re-initialization only a single edge
> remains active. This causes buttons to report only release events but
> not press events, or vice versa.
I believe you just described a bug in the interrupt controller handling
of hibernation. It needs to be fixed there, not in consumer driver.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2026-04-06 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 16:04 [PATCH] Input: gpio-keys - add hibernation support Armando De Leon
2026-04-06 16:24 ` Dmitry Torokhov [this message]
2026-04-06 16:58 ` Armando De Leon
2026-04-06 18:18 ` Dmitry Torokhov
2026-04-06 20:39 ` Armando De Leon
2026-04-07 4:31 ` 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=adPdc2Z1SYxvqDmP@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=auribe84@gmail.com \
--cc=learmand@amazon.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.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