Linux ACPI
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Yao Qi <xnorigc@gmail.com>,
	westeri@kernel.org, linusw@kernel.org, brgl@kernel.org,
	linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpiolib: acpi: Add ignore_wake quirk for ASUS TX Air FA401GM
Date: Thu, 3 Sep 2026 14:55:49 +0300	[thread overview]
Message-ID: <aplgRRCxGEC-ahyw@ashevche-desk.local> (raw)
In-Reply-To: <a89e95e2-abaa-4ea4-9be2-2a179f6f5257@amd.com>

On Mon, Aug 24, 2026 at 10:12:18AM -0500, Mario Limonciello wrote:
> On 8/23/26 03:25, Andy Shevchenko wrote:
> > On Sat, Aug 08, 2026 at 03:55:13PM +0000, Yao Qi wrote:
> > > The ASUS TX Air FA401GM experiences immediate wakeups from s2idle
> > > (Modern Standby) when suspended with an external HDMI display connected.
> > > 
> > > This issue is caused by spurious ACPI event signaling routed through
> > > GPIO 24 on the AMD GPIO controller (AMDI0030:00), which triggers a
> > > system-wide IRQ 7 (pinctrl_amd) wake-up interrupt during sleep.
> > > 
> > > Add an ignore_wake quirk for GPIO 24 on this machine to prevent these
> > > unwanted wakeups. This has been runtime-tested and verified using the
> > > `gpiolib_acpi.ignore_wake=AMDI0030:00@24` kernel parameter.
> > 
> > Mario, can you ack this one?
> 
> It's likely very similar to
> 
> https://lore.kernel.org/linux-gpio/20260821070651.39763-1-vaknins33@gmail.com/
> 
> As you can see that's also GPIO pin 24.

Right, but this will need still its own DMI entry, will it?

> Can we please see an acpidump to confirm though?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-09-03 11:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-08 15:55 [PATCH] gpiolib: acpi: Add ignore_wake quirk for ASUS TX Air FA401GM Yao Qi
2026-08-08 19:42 ` Andy Shevchenko
2026-08-09 22:17   ` Linus Walleij
2026-08-10  8:36     ` Andy Shevchenko
2026-08-11 14:54       ` Andy Shevchenko
2026-08-12  8:23         ` Bartosz Golaszewski
2026-08-12  8:39           ` Andy Shevchenko
2026-08-12 11:54             ` Bartosz Golaszewski
2026-08-12 13:16               ` Andy Shevchenko
2026-08-12 13:39                 ` Bartosz Golaszewski
2026-08-23  8:23                   ` Andy Shevchenko
2026-08-23  8:25 ` Andy Shevchenko
2026-08-24 15:12   ` Mario Limonciello
2026-09-03 11:55     ` Andy Shevchenko [this message]
2026-09-03 13:44       ` Mario Limonciello

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=aplgRRCxGEC-ahyw@ashevche-desk.local \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=brgl@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=westeri@kernel.org \
    --cc=xnorigc@gmail.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