From: Lee Jones <lee@kernel.org>
To: "Ondřej Jirman" <megi@xff.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] mfd: rk8xx-core: Fix interrupt processing order for power key button
Date: Fri, 23 Feb 2024 16:15:59 +0000 [thread overview]
Message-ID: <20240223161559.GI1666215@google.com> (raw)
In-Reply-To: <20240217195615.1767907-1-megi@xff.cz>
On Sat, 17 Feb 2024, Ondřej Jirman wrote:
> From: Ondrej Jirman <megi@xff.cz>
>
> Process rise event last, to avoid stuck keys when multiple interrupts
> are coalesced. This can happen typically when resuming from suspend
> via power key press and holding the power button for a bit too short,
> so that RISE an FALL IRQ flags are set before any interrupt routine
> has a chance to run.
>
> Input subsystem will interpret it as holding down a power key for
> a long time, which leads to unintended initiation of shutdown UI
> on some OSes.
>
> Signed-off-by: Ondrej Jirman <megi@xff.cz>
> ---
> Sorry, resent without the bogous patch series numbering.
>
> drivers/mfd/rk8xx-core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mfd/rk8xx-core.c b/drivers/mfd/rk8xx-core.c
> index b1ffc3b9e2be..e2261b68b844 100644
> --- a/drivers/mfd/rk8xx-core.c
> +++ b/drivers/mfd/rk8xx-core.c
> @@ -43,8 +43,8 @@ static struct resource rk806_pwrkey_resources[] = {
> };
>
> static const struct resource rk817_pwrkey_resources[] = {
> - DEFINE_RES_IRQ(RK817_IRQ_PWRON_RISE),
> DEFINE_RES_IRQ(RK817_IRQ_PWRON_FALL),
> + DEFINE_RES_IRQ(RK817_IRQ_PWRON_RISE),
FWIW, basing solutions on ordering like this is often fragile!
> };
>
> static const struct resource rk817_charger_resources[] = {
> --
> 2.43.0
>
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2024-02-23 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 19:56 [RESEND PATCH] mfd: rk8xx-core: Fix interrupt processing order for power key button Ondřej Jirman
2024-02-23 16:14 ` (subset) " Lee Jones
2024-02-23 16:15 ` Lee Jones [this message]
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=20240223161559.GI1666215@google.com \
--to=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=megi@xff.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.