linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Anderson <ruinairas1992@gmail.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
	rafael@kernel.org, linux-kernel@vger.kernel.org
Cc: catalin@antebit.com, philipp.zabel@gmail.com,
	travisghansen@yahoo.com, Shyam-sundar.S-k@amd.com,
	Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 5/6] acpi/x86: s2idle: Add a quirk for ASUS ROG Zephyrus G14
Date: Wed, 14 Sep 2022 22:48:37 -0500	[thread overview]
Message-ID: <4536a322-df6f-4994-287b-a8e85083d318@gmail.com> (raw)
In-Reply-To: <20220912172401.22301-6-mario.limonciello@amd.com>


On 9/12/22 12:23 PM, Mario Limonciello wrote:
> ASUS ROG Zephyrus G14 is affected by the same BIOS bug as ASUS TUF
> Gaming A17 where important ASL is not called in the AMD code path.
> Use the Microsoft codepath instead.
>
> Reported-and-suggested-by: Philipp Zabel <philipp.zabel@gmail.com>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> v1->v2:
>   * New patch
> ---
>   drivers/acpi/x86/s2idle.c | 8 ++++++++
>   1 file changed, 8 insertions(+)
>
> diff --git a/drivers/acpi/x86/s2idle.c b/drivers/acpi/x86/s2idle.c
> index 9ee734e0c3c5..4bdc7133d2ea 100644
> --- a/drivers/acpi/x86/s2idle.c
> +++ b/drivers/acpi/x86/s2idle.c
> @@ -420,6 +420,14 @@ static const struct dmi_system_id s2idle_dmi_table[] __initconst = {
>   			DMI_MATCH(DMI_PRODUCT_NAME, "ASUS TUF Gaming A17"),
>   		},
>   	},
> +	{
> +		/* ASUS ROG Zephyrus G14 (2022) */
> +		.callback = lps0_prefer_microsoft,
> +		.matches = {
> +			DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
> +			DMI_MATCH(DMI_PRODUCT_NAME, "ROG Zephyrus G14 GA402"),
> +		},
> +	},
>   	{}
>   };
>   

Tested-by: Matthew Anderson <ruinairas1992@gmail.com>

Apologies for my troubles, I'm new to submitting to public emails.


  parent reply	other threads:[~2022-09-15  3:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 17:23 [PATCH v2 0/6] Fixups for s2idle on various Rembrandt laptops Mario Limonciello
2022-09-12 17:23 ` [PATCH v2 1/6] acpi/x86: s2idle: Move _HID handling for AMD systems into structures Mario Limonciello
2022-09-13 16:44   ` Philipp Zabel
2022-09-12 17:23 ` [PATCH v2 2/6] acpi/x86: s2idle: If a new AMD _HID is missing assume Rembrandt Mario Limonciello
2022-09-13 16:46   ` Philipp Zabel
2022-09-12 17:23 ` [PATCH v2 3/6] acpi/x86: s2idle: Add module parameter to prefer Microsoft GUID Mario Limonciello
2022-09-13 16:47   ` Philipp Zabel
2022-09-12 17:23 ` [PATCH v2 4/6] acpi/x86: s2idle: Add a quirk for ASUS TUF Gaming A17 FA707RE Mario Limonciello
2022-09-13 16:48   ` Philipp Zabel
2022-09-12 17:23 ` [PATCH v2 5/6] acpi/x86: s2idle: Add a quirk for ASUS ROG Zephyrus G14 Mario Limonciello
2022-09-13 16:50   ` Philipp Zabel
2022-09-15  3:22     ` Matthew Anderson
2022-09-15  3:48   ` Matthew Anderson [this message]
2022-09-12 17:24 ` [PATCH v2 6/6] acpi/x86: s2idle: Add a quirk for Lenovo Slim 7 Pro 14ARH7 Mario Limonciello

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=4536a322-df6f-4994-287b-a8e85083d318@gmail.com \
    --to=ruinairas1992@gmail.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=catalin@antebit.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=philipp.zabel@gmail.com \
    --cc=rafael@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).