From: Marco Scardovi <scardracs@disroot.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Mika Westerberg <westeri@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Mario Limonciello <mario.limonciello@amd.com>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpiolib: acpi: Add quirk for ASUS ROG Strix G614 series
Date: Wed, 17 Jun 2026 10:52:35 +0200 [thread overview]
Message-ID: <h3V3bT1sQUiheRF3xSbypg@disroot.org> (raw)
In-Reply-To: <ajEtpY101OpZdtaF@ashevche-desk.local>
>
> Okay, perhaps this all needs to be elaborated and summarized in the commit
> message.
> > Sidenote
> > Personally I'd wait for Mario for further info: after all it's him the
> > maintainer for AMD side and surely knows more than me.
>
> Sure, I am with you on this.
>
What I'm saying below is purely based on my own speculations but it's the
most plausible thing I can think as for now.
When I tested Mario's patch back in April it totally used to work on my
device: I have an idea that the value probably happened to be equal 1, like
requested on the patch and making it working as intended.
In the meantime I updated the BIOS (from 310 to 315, released in May),
changing the value from 1 to 0 and breaking the boot time again (as said it's
my own speculation, I'm not sure if it is actually possible).
I didn't test the patch after the BIOS update 'cause I had the
gpiolib_acpi.run_edge_events_on_boot=0 option enabled and didn't think it
would stop working again.
next prev parent reply other threads:[~2026-06-17 8:52 UTC|newest]
Thread overview: 13+ 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 [this message]
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
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=h3V3bT1sQUiheRF3xSbypg@disroot.org \
--to=scardracs@disroot.org \
--cc=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=mika.westerberg@linux.intel.com \
--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