From: Luke Jones <luke@ljones.dev>
To: Mario Limonciello <mario.limonciello@amd.com>,
linux-kernel@vger.kernel.org
Cc: Shyam-sundar.S-k@amd.com, "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 2/2] ACPI: x86: s2idle: Add another ID to s2idle_dmi_table
Date: Thu, 29 Sep 2022 14:00:53 +1300 [thread overview]
Message-ID: <f49217c531a61d42d2cf370d2140cf57fe79ec34.camel@ljones.dev> (raw)
In-Reply-To: <20220928161935.31913-2-mario.limonciello@amd.com>
On Wed, 2022-09-28 at 11:19 -0500, Mario Limonciello wrote:
> It's reported that "ASUSTeK COMPUTER INC. ROG Flow X16 GV601RW" has
> non-functional fans after resume when using the AMD codepath. This
> issue is fixed using the Microsoft codepath.
>
> Add the 3 variants of this system to the Microsoft codepath DMI
> table.
> * GV601RW
> * GV601RM
> * GV601RE
>
> Link:
> https://www.reddit.com/r/linuxhardware/comments/wh50nd/compatibility_report_asus_rog_flow_x16_gv601rm/
> Link:
> https://gitlab.freedesktop.org/drm/amd/-/issues/2148#note_1571241
> Reported-by: Luke Jones <luke@ljones.dev>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> drivers/acpi/x86/s2idle.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/acpi/x86/s2idle.c b/drivers/acpi/x86/s2idle.c
> index 3ae2ba74de92..0155c1d2d608 100644
> --- a/drivers/acpi/x86/s2idle.c
> +++ b/drivers/acpi/x86/s2idle.c
> @@ -451,6 +451,17 @@ static const struct dmi_system_id
> s2idle_dmi_table[] __initconst = {
> DMI_MATCH(DMI_PRODUCT_NAME, "ROG Flow X13
> GV301"),
> },
> },
> + {
> + /*
> + * ASUSTeK COMPUTER INC. ROG Flow X16 GV601RW_GV601RW
> + *
> https://gitlab.freedesktop.org/drm/amd/-/issues/2148
> + */
> + .callback = lps0_prefer_microsoft,
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER
> INC."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "ROG Flow X16
> GV601"),
> + },
> + },
> {}
> };
>
Hi Mario,
related dts here
https://gitlab.com/asus-linux/reverse-engineering/-/tree/master/GV601R
next prev parent reply other threads:[~2022-09-29 1:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 16:19 [PATCH 1/2] ACPI: x86: s2idle: Fix a NULL pointer dereference Mario Limonciello
2022-09-28 16:19 ` [PATCH 2/2] ACPI: x86: s2idle: Add another ID to s2idle_dmi_table Mario Limonciello
2022-09-29 1:00 ` Luke Jones [this message]
2022-09-28 19:36 ` [PATCH 1/2] ACPI: x86: s2idle: Fix a NULL pointer dereference Rafael J. Wysocki
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=f49217c531a61d42d2cf370d2140cf57fe79ec34.camel@ljones.dev \
--to=luke@ljones.dev \
--cc=Shyam-sundar.S-k@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rafael@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
all inboxes | Powered by JetHome®