All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	 "open list:X86 PLATFORM DRIVERS"
	<platform-driver-x86@vger.kernel.org>,
	 Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Subject: Re: [PATCH] platform/x86/amd: Extend Framework 13 quirk to more BIOSes
Date: Tue, 16 Apr 2024 15:24:06 +0300 (EEST)	[thread overview]
Message-ID: <ace9e5fe-0565-b24d-5394-ba4bd9f4305c@linux.intel.com> (raw)
In-Reply-To: <20240410141046.433-1-mario.limonciello@amd.com>

On Wed, 10 Apr 2024, Mario Limonciello wrote:

> BIOS 03.05 still hasn't fixed the spurious IRQ1 issue.  As it's still
> being worked on there is still a possiblitiy that it won't need to
> apply to future BIOS releases.

Hi Mario,

Could you explain/confirm what the second sentence is supposed to mean? 
Mainly I mean "it won't need to apply to future", did you perhaps mean it 
might need to be applied still to some future versions too besides this 
one because the fix is still being worked on, or what?

There's also "possiblitiy" typo, in case you end up rewriting the message 
and send v2.

-- 
 i.


> Add a quirk for BIOS 03.05 as well.
> 
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
>  drivers/platform/x86/amd/pmc/pmc-quirks.c | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/drivers/platform/x86/amd/pmc/pmc-quirks.c b/drivers/platform/x86/amd/pmc/pmc-quirks.c
> index b456370166b6..b4f49720c87f 100644
> --- a/drivers/platform/x86/amd/pmc/pmc-quirks.c
> +++ b/drivers/platform/x86/amd/pmc/pmc-quirks.c
> @@ -208,6 +208,15 @@ static const struct dmi_system_id fwbug_list[] = {
>  			DMI_MATCH(DMI_BIOS_VERSION, "03.03"),
>  		}
>  	},
> +	{
> +		.ident = "Framework Laptop 13 (Phoenix)",
> +		.driver_data = &quirk_spurious_8042,
> +		.matches = {
> +			DMI_MATCH(DMI_SYS_VENDOR, "Framework"),
> +			DMI_MATCH(DMI_PRODUCT_NAME, "Laptop 13 (AMD Ryzen 7040Series)"),
> +			DMI_MATCH(DMI_BIOS_VERSION, "03.05"),
> +		}
> +	},
>  	{}
>  };
>  
> 

  parent reply	other threads:[~2024-04-16 12:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 14:10 [PATCH] platform/x86/amd: Extend Framework 13 quirk to more BIOSes Mario Limonciello
2024-04-10 16:34 ` Mario Limonciello
2024-04-15 13:54 ` Hans de Goede
2024-04-16 12:24 ` Ilpo Järvinen [this message]
2024-04-16 12:37   ` Mario Limonciello
2024-04-16 12:42     ` Ilpo Järvinen
2024-04-16 12:44 ` Ilpo Järvinen

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=ace9e5fe-0565-b24d-5394-ba4bd9f4305c@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=mario.limonciello@amd.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.