platform-driver-x86.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Werner Sembach <wse@tuxedocomputers.com>
To: "Mario Limonciello" <superm1@kernel.org>,
	"Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
	"Hans de Goede" <hansg@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Christoffer Sandberg" <cs@tuxedo.de>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86/amd/pmc: Add Stellaris Slim Gen6 AMD to spurious 8042 quirks list
Date: Tue, 2 Sep 2025 16:37:51 +0200	[thread overview]
Message-ID: <c154022c-c00d-46ba-86fb-2030ccab0272@tuxedocomputers.com> (raw)
In-Reply-To: <3830aeee-91d7-48ee-b67e-8aefbbd2124e@kernel.org>


Am 02.09.25 um 16:15 schrieb Mario Limonciello:
> On 9/1/2025 11:42 AM, Werner Sembach wrote:
>> From: Christoffer Sandberg <cs@tuxedo.de>
>>
>> Prevents instant wakeup ~1s after suspend
>>
>> Signed-off-by: Christoffer Sandberg <cs@tuxedo.de>
>> Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
>> ---
>>   drivers/platform/x86/amd/pmc/pmc-quirks.c | 7 +++++++
>>   1 file changed, 7 insertions(+)
>>
>> diff --git a/drivers/platform/x86/amd/pmc/pmc-quirks.c 
>> b/drivers/platform/x86/amd/pmc/pmc-quirks.c
>> index 7ffc659b27944..8b8944483b859 100644
>> --- a/drivers/platform/x86/amd/pmc/pmc-quirks.c
>> +++ b/drivers/platform/x86/amd/pmc/pmc-quirks.c
>> @@ -248,6 +248,13 @@ static const struct dmi_system_id fwbug_list[] = {
>>               DMI_MATCH(DMI_PRODUCT_NAME, "Lafite Pro V 14M"),
>>           }
>>       },
>> +    {
>> +        .ident = "TUXEDO Stellaris Slim 15 AMD Gen6",
>> +        .driver_data = &quirk_spurious_8042,
>> +        .matches = {
>> +            DMI_MATCH(DMI_BOARD_NAME, "GMxHGxx"),
>> +        }
>> +    },
>>       {}
>>   };
>
> FYI - this seems to conflict with other changes on review-ilpo-fixes and fixes 
> branches.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/drivers/platform/x86/amd/pmc/pmc-quirks.c?h=review-ilpo-fixes&id=c96f86217bb28e019403bb8f59eacd8ad5a7ad1a 
>
Sorry, i will rebase and send a v2.
>
> Also - a few other comments.
>
> 1) Do you have line of sight to a firmware (BIOS or EC) fix?  If so; it would 
> be better to specify a specific firmware release that is affected.

No

@Christoffer you have more knowledge of how realistic it is to get this fixed by 
the odm?

But even then, we still don't have fwupd support to get the fw update out easily

>
> 2) Shouldn't you also have DMI_SYS_VENDOR or some other matching keys else 
> set?  Or is it really all these boards with this specific name?

I was following the style of the i8042 quirk list where we also always only did 
boardnames

Ofc we only tested the boards the odm has sent to us

best regards,

Werner Sembach


  reply	other threads:[~2025-09-02 14:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01 16:42 [PATCH] platform/x86/amd/pmc: Add Stellaris Slim Gen6 AMD to spurious 8042 quirks list Werner Sembach
2025-09-02 14:15 ` Mario Limonciello
2025-09-02 14:37   ` Werner Sembach [this message]
2025-09-02 15:25     ` 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=c154022c-c00d-46ba-86fb-2030ccab0272@tuxedocomputers.com \
    --to=wse@tuxedocomputers.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=cs@tuxedo.de \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=superm1@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;
as well as URLs for NNTP newsgroup(s).