From: Marco Scardovi <scardracs@disroot.org>
To: w_armin@gmx.de
Cc: andriy.shevchenko@linux.intel.com, bnatikar@amd.com,
brgl@kernel.org, linusw@kernel.org, linux-acpi@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
mario.limonciello@amd.com, scardracs@disroot.org,
westeri@kernel.org
Subject: Re: [PATCH v2 0/1] gpiolib: acpi: Add quirk for ASUS ROG Strix G16 G614 series
Date: Thu, 18 Jun 2026 01:14:24 +0200 [thread overview]
Message-ID: <20260617231428.96076-1-scardracs@disroot.org> (raw)
In-Reply-To: <0e6ea9d5-68ac-4d18-b40a-25e70216b288@gmx.de>
Hi Armin,
On Wed, Jun 17, 2026 at 10:33 PM, Armin Wolf wrote:
>
> could you share the output of "acpidump" on your device? I suspect that Asus
> uses a _DSM control method to tell Windows to invert the polarity inside the
> ActiveBoth check.
>
I have extracted and decompiled the ACPI tables (DSDT and SSDTs) from acpidump.
You can find the raw acpidump.out and the decompiled ASL tables in the
following Google Drive folder:
https://drive.google.com/drive/folders/1aTqLAnUhrTsPdpA8tfOFyRopG3P3DGnc?usp=drive_link
As far as I can see/understand there is no _DSM method defined under the
GPIO controller device (AMDI0030) or the \_SB.GPIO scope.
Under the _AEI method (defined in SSDT9 line 188-193), pin 21 (0x15) and
pin 24 (0x18) are defined as:
GpioInt (Edge, ActiveBoth, ExclusiveAndWake, PullNone, 0x0000,
"\\_SB.GPIO", 0x00, ResourceConsumer, ,
)
{
0x0015 // Pin 21 (Touchpad attention line)
}
When triggered, they evaluate the _EVT method which calls:
Case (0x15)
{
\_SB.PCI0.SBRG.HNC0 (0x15, Zero)
}
Since Arg1 is Zero, HNC0 executes the Else branch, invoking M009 and ATKM/ADTM,
which stalls synchronously for ~36 seconds when executed during the probe path at
boot time.
Thanks,
Marco
next prev parent reply other threads:[~2026-06-17 23:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 9:08 [PATCH] gpiolib: acpi: Add quirk for ASUS ROG Strix G614 series Marco Scardovi
2026-06-16 9:31 ` Andy Shevchenko
2026-06-16 9:43 ` Marco Scardovi
2026-06-16 9:58 ` Andy Shevchenko
2026-06-16 10:24 ` Mika Westerberg
2026-06-16 10:58 ` Marco Scardovi
2026-06-16 11:04 ` Andy Shevchenko
2026-06-17 8:51 ` Marco Scardovi
2026-06-17 8:52 ` Marco Scardovi
2026-06-17 18:34 ` Basavaraj Natikar
2026-06-17 18:50 ` [PATCH v2 0/1] gpiolib: acpi: Add quirk for ASUS ROG Strix G16 " Marco Scardovi
2026-06-17 18:50 ` [PATCH v2 1/1] " Marco Scardovi
2026-06-17 21:23 ` [PATCH v2 0/1] " Armin Wolf
2026-06-17 23:14 ` Marco Scardovi [this message]
2026-06-18 13:16 ` Basavaraj Natikar
2026-06-18 14:35 ` Andy Shevchenko
2026-06-18 16:59 ` Marco Scardovi
2026-06-18 18:01 ` Andy Shevchenko
2026-06-18 18:07 ` Marco Scardovi
2026-06-19 10:17 ` Basavaraj Natikar
2026-06-19 10:28 ` Marco Scardovi
2026-06-20 6:52 ` Andy Shevchenko
2026-06-20 7:20 ` Marco Scardovi
2026-06-21 7:58 ` Mario Limonciello
2026-06-21 11:00 ` Hans de Goede
2026-06-21 12:38 ` Marco Scardovi
2026-06-24 14:42 ` Armin Wolf
2026-06-24 17:49 ` Marco Scardovi
2026-06-25 6:08 ` Andy Shevchenko
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=20260617231428.96076-1-scardracs@disroot.org \
--to=scardracs@disroot.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bnatikar@amd.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=w_armin@gmx.de \
--cc=westeri@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