From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: Luke Jones <luke@ljones.dev>,
rafael@kernel.org, linux-kernel@vger.kernel.org
Cc: travisghansen@yahoo.com, catalin@antebit.com,
Shyam-sundar.S-k@amd.com, ruinairas1992@gmail.com,
philipp.zabel@gmail.com, iam@decentr.al, hdegoede@redhat.com,
davidedp91@gmail.com, marko.cekrlic.26@gmail.com,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v4 7/7] acpi/x86: s2idle: Add a quirk for ASUSTeK COMPUTER INC. ROG Flow X13
Date: Tue, 27 Sep 2022 11:07:44 -0500 [thread overview]
Message-ID: <df22755c-bf4c-9d85-2c7c-a149f8580d05@amd.com> (raw)
In-Reply-To: <26bbda5d03f0eadc54dfa0036e24e16ae9134f5e.camel@ljones.dev>
On 9/27/2022 04:06, Luke Jones wrote:
> Hello Mario,
>
> I have confirmed that another suspect ASUS laptop requires the quirk,
> patch is as follows:
>
>
> ---
> drivers/acpi/x86/s2idle.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/acpi/x86/s2idle.c b/drivers/acpi/x86/s2idle.c
> index 2cd381f6c002..c811eeed42cd 100644
> --- a/drivers/acpi/x86/s2idle.c
> +++ b/drivers/acpi/x86/s2idle.c
> @@ -428,6 +428,16 @@ static const struct dmi_system_id
> s2idle_dmi_table[] __initconst = {
> DMI_MATCH(DMI_PRODUCT_NAME, "ROG Zephyrus G14
> GA402"),
> },
> },
> + {
> + /*
> + * ASUS ROG Flow X16 - GV601
> + */
> + .callback = lps0_prefer_microsoft,
> + .matches = {
> + DMI_MATCH(DMI_BOARD_VENDOR, "ASUSTeK COMPUTER
> INC."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "GV601"),
> + },
> + },
> {}
> };
>
Hey Luke,
The series that was under development has been merged for 6.1. At this
point, can you just make a proper patch with a S-o-b on top of
linux-pm/bleeding-edge for the new model to add to the list and send it out?
In addition to that, if you can please add a Link: to the acpidump and
dmesg if available?
Thanks
next prev parent reply other threads:[~2022-09-27 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 20:40 [PATCH v4 0/7] Fixups for s2idle on various Rembrandt laptops Mario Limonciello
2022-09-21 20:40 ` [PATCH v4 1/7] acpi/x86: s2idle: Move _HID handling for AMD systems into structures Mario Limonciello
2022-09-21 20:40 ` [PATCH v4 2/7] acpi/x86: s2idle: If a new AMD _HID is missing assume Rembrandt Mario Limonciello
2022-09-21 20:40 ` [PATCH v4 3/7] acpi/x86: s2idle: Add module parameter to prefer Microsoft GUID Mario Limonciello
2022-09-21 20:40 ` [PATCH v4 4/7] acpi/x86: s2idle: Add a quirk for ASUS TUF Gaming A17 FA707RE Mario Limonciello
2022-09-21 20:40 ` [PATCH v4 5/7] acpi/x86: s2idle: Add a quirk for ASUS ROG Zephyrus G14 Mario Limonciello
2022-09-21 20:40 ` [PATCH v4 6/7] acpi/x86: s2idle: Add a quirk for Lenovo Slim 7 Pro 14ARH7 Mario Limonciello
2022-09-21 20:40 ` [PATCH v4 7/7] acpi/x86: s2idle: Add a quirk for ASUSTeK COMPUTER INC. ROG Flow X13 Mario Limonciello
2022-09-27 9:06 ` Luke Jones
2022-09-27 16:07 ` Limonciello, Mario [this message]
2022-09-27 20:00 ` Luke Jones
2022-09-24 17:07 ` [PATCH v4 0/7] Fixups for s2idle on various Rembrandt laptops 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=df22755c-bf4c-9d85-2c7c-a149f8580d05@amd.com \
--to=mario.limonciello@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=catalin@antebit.com \
--cc=davidedp91@gmail.com \
--cc=hdegoede@redhat.com \
--cc=iam@decentr.al \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=marko.cekrlic.26@gmail.com \
--cc=philipp.zabel@gmail.com \
--cc=rafael@kernel.org \
--cc=ruinairas1992@gmail.com \
--cc=travisghansen@yahoo.com \
/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