From: Marco Scardovi <scardracs@disroot.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Basavaraj Natikar <bnatikar@amd.com>
Cc: w_armin@gmx.de, 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,
westeri@kernel.org
Subject: Re: [PATCH v2 0/1] gpiolib: acpi: Add quirk for ASUS ROG Strix G16 G614 series
Date: Fri, 19 Jun 2026 12:28:49 +0200 [thread overview]
Message-ID: <P9sY7IKaQumFwq7UGDqIPA@disroot.org> (raw)
In-Reply-To: <9643455e-f4ce-4496-bcdf-1122420c18eb@amd.com>
In data venerdì 19 giugno 2026 12:17:17 Ora legale dell’Europa centrale, Basavaraj Natikar ha scritto:
> On 6/18/2026 11:37 PM, Marco Scardovi wrote:
> > In data giovedì 18 giugno 2026 20:01:40 Ora legale dell’Europa centrale, Andy Shevchenko ha scritto:
> >> On Thu, Jun 18, 2026 at 06:59:15PM +0200, Marco Scardovi wrote:
> >>> On Thu, Jun 18, 2026 at 16:35:37 CEST, Andy Shevchenko wrote:
> >>>> On Thu, Jun 18, 2026 at 06:46:28PM +0530, Basavaraj Natikar wrote:
> >>>>> On 6/18/2026 4:44 AM, Marco Scardovi wrote:
> >>>>>> On Wed, Jun 17, 2026 at 10:33 PM, Armin Wolf wrote:
...
>
> I also checked the BIOS 316 ACPI dump — the stalling path is byte‑for‑byte identical
> to 315, so the AML is unchanged and it'll still stall if pin 21 boots low.
>
> On the OEM side, I'm connecting internally with our AMD contact for ASUS to report
> this behavior and follow up on a firmware fix.
>
> Thanks,
> --
> Basavaraj
>
Hi Basavaraj,
Thank you. Does that mean that my patch will not be required anymore?
If that's the case you can consider it as null. I don't mind having the boot
flag added until it's completely fixed on ASUS' side. BTW I have the suspect
that my model is not the only one with the long boot bug on ASUS [1] [2]
but actually the only one who came up with an actual patch on the kernel.
[1] https://bbs.archlinux.org/viewtopic.php?id=307251
[2] https://rog-forum.asus.com/t5/rog-strix-series/linux-boot-is-very-slow-at-this-moment/td-p/1138746
next prev parent reply other threads:[~2026-06-19 10:29 UTC|newest]
Thread overview: 23+ 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
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 [this message]
2026-06-20 6:52 ` Andy Shevchenko
2026-06-20 7:20 ` Marco Scardovi
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=P9sY7IKaQumFwq7UGDqIPA@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