mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
To: aln8 <aln8un@gmail.com>
Cc: hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com,
	luke@ljones.dev, platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86/amd: pmf: Add quirk for TUF Gaming A14
Date: Thu, 12 Sep 2024 21:00:49 +0530	[thread overview]
Message-ID: <b3ecf961-c399-43b2-a8b3-6b5ed664db27@amd.com> (raw)
In-Reply-To: <20240912073601.65656-1-aln8un@gmail.com>



On 9/12/2024 13:06, aln8 wrote:
> The ASUS TUF Gaming A14 has the same issue as the ROG Zephyrus G14
> where it advertises SPS support but doesn't use it.
> 
> Signed-off-by: aln8 <aln8un@gmail.com>

Thank you for the patch. Looks good to me.

Acked-by: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>

> ---
> v1 -> v2: Change to FA401W so full series models will get the fix.
> ---
>  drivers/platform/x86/amd/pmf/pmf-quirks.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/drivers/platform/x86/amd/pmf/pmf-quirks.c b/drivers/platform/x86/amd/pmf/pmf-quirks.c
> index 48870ca52..7cde5733b 100644
> --- a/drivers/platform/x86/amd/pmf/pmf-quirks.c
> +++ b/drivers/platform/x86/amd/pmf/pmf-quirks.c
> @@ -37,6 +37,14 @@ static const struct dmi_system_id fwbug_list[] = {
>  		},
>  		.driver_data = &quirk_no_sps_bug,
>  	},
> +	{
> +		.ident = "ASUS TUF Gaming A14",
> +		.matches = {
> +			DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
> +			DMI_MATCH(DMI_PRODUCT_NAME, "FA401W"),
> +		},
> +		.driver_data = &quirk_no_sps_bug,
> +	},
>  	{}
>  };
>  

  reply	other threads:[~2024-09-12 15:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12  7:36 aln8
2024-09-12 15:30 ` Shyam Sundar S K [this message]
2024-09-14 16:10 ` Hans de Goede

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=b3ecf961-c399-43b2-a8b3-6b5ed664db27@amd.com \
    --to=shyam-sundar.s-k@amd.com \
    --cc=aln8un@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=platform-driver-x86@vger.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®