Re: [PATCH] gpiolib: acpi: Add ignore_wake quirk for ASUS TX Air FA401GM

Bartosz Golaszewski <[email protected]>
Newsgroups org.kernel.vger.linux-gpio,org.kernel.vger.linux-acpi,org.kernel.vger.linux-kernel
Message-ID <CAMRc=MeDLc-LPwoCEA8yMw3+L9UcN-NgXpYpFPxtUNffAAffyw@mail.gmail.com>
On Tue, 11 Aug 2026 16:54:29 +0200, Andy Shevchenko
<[email protected]> said:
> On Mon, Aug 10, 2026 at 11:36:19AM +0300, Andy Shevchenko wrote:
>> On Mon, Aug 10, 2026 at 12:17:06AM +0200, Linus Walleij wrote:
>> > On Sat, Aug 8, 2026 at 9:42 PM Andy Shevchenko
>> > <[email protected]> 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.
>> > >
>> > > If AMD people will be quick enough to tag this, I will include in my PR to
>> > > Linus W. on next week.
>> >
>> > To Bartosz?
>> > It's gpiolib...
>>
>> Oh, true, I have also pin control stuff to send!
>
> Okay, I have checked if I have anything to Bart and it seems I mixed that with
> pin control stuff. So, Bart, if you feel confident about this patch, you can
> take it directly. Here is my formal tag for that
>
> Reviewed-by: Andy Shevchenko <[email protected]>
>

Is this a bugfix? I'll be OoO until the end of August starting on Friday with
the exception of a single day to catch up on email. I'll be sending my PRs for
v7.3 tomorrow. Not sure if I should take it for v7.3 or v7.2?

Bart
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.