From: Mario Limonciello <superm1@kernel.org>
To: Mark Pearson <mpearson-lenovo@squebb.ca>,
Bruno BOI <bruno.boi@bobtopus.eu>,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Cc: "platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86/amd/pmc: Add Thinkpad L14 Gen3 (21C5) to quirk_s2idle_bug
Date: Mon, 28 Sep 2026 11:54:41 -0500 [thread overview]
Message-ID: <0c8bb28c-0814-4446-b8fb-2f07e9174cc2@kernel.org> (raw)
In-Reply-To: <c22fe14e-41c3-425e-9f8e-39b900ab6e3b@app.fastmail.com>
On 9/28/26 11:53, Mark Pearson wrote:
> On Mon, Sep 28, 2026, at 12:09 PM, Mario Limonciello wrote:
>> On 9/28/26 11:06, Bruno BOI wrote:
>>> The Thinkpad L14 Gen3 with DMI product name 21C5 is affected by the same
>>> s2idle resume stall as the already listed 21C6 variant: resuming from
>>> s2idle blocks for several seconds before the kernel resumes.
>>>
>>> DMI_MATCH() performs substring matching, so a "21C5" entry also covers
>>> SKUs such as 21C5S05800. Add the 21C5 model to the existing
>>> quirk_s2idle_bug table.
>>>
>>> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=222070
>>> Link: https://bugzilla.kernel.org/show_bug.cgi?id=221273
>>> Signed-off-by: Bruno BOI <bruno.boi@bobtopus.eu>
>>> ---
>>> Changes in v2: resent with the correct sender address; the patch
>>> content is unchanged from v1.
>>> drivers/platform/x86/amd/pmc/pmc-quirks.c | 9 +++++++++
>>> 1 file changed, 9 insertions(+)
>>
>> Mark,
>>
>> Since it uses prefixes rather than a new entry how would you feel about:
>>
>> DMI_MATCH(DMI_PRODUCT_NAME, "21C"),
>>
>> On the 21C6 existing entry.
>
> The last char covers a lot of platforms unfortunately
>
> Ignoring the Intel platforms (I assume this driver wouldn't try and load on those - there are a bunch including a Chromebook if that makes any difference)
>
> T14s Gen 3 AMD, X13 Gen 3 AMD, L14 Gen 3 AMD, L15 Gen 3 AMD, T14 Gen 3 AMD, T16 G1 AMD, P16s Gen 1 AMD, K14 AMD would all be impacted.
>
> I probably have a bunch of these to be able to test - but not all (and definitely not the K14).
>
> Adding 21C5 and 21C6 should cover all L14 G3 AMD models.
>
> Mark
Got it; thanks for confirming. No concerns by me with the new quirk
then either.
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
next prev parent reply other threads:[~2026-09-28 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 16:06 Bruno BOI
2026-09-28 16:09 ` Mario Limonciello
2026-09-28 16:22 ` Bruno BOI
2026-09-28 16:53 ` Mark Pearson
2026-09-28 16:54 ` Mario Limonciello [this message]
2026-09-28 16:59 ` Mark Pearson
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=0c8bb28c-0814-4446-b8fb-2f07e9174cc2@kernel.org \
--to=superm1@kernel.org \
--cc=Shyam-sundar.S-k@amd.com \
--cc=bruno.boi@bobtopus.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--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®