From: Konstantin Pospelov <kupospelov@gmail.com>
To: "Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Konstantin Pospelov <kupospelov@gmail.com>
Subject: [PATCH] platform/x86/amd/pmc: Delay suspend for HP EliteBook 845 G10
Date: Sun, 8 Nov 2026 21:48:52 +0100 [thread overview]
Message-ID: <20261108204852.11194-1-kupospelov@gmail.com> (raw)
On the HP EliteBook 845 G10 (Ryzen 7 7840U), the CPU stays stuck at 544
MHz after resume from s2idle. Delaying suspend avoids this.
Tested with and without the patch over 6 cycles:
1. Suspend.
2. Connect the charger.
3. Resume.
The issue was reproduced 3 times, and was not reproducible 3 times with
the patch.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=218557
Signed-off-by: Konstantin Pospelov <kupospelov@gmail.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 fed6c51879fc..037bb575870f 100644
--- a/drivers/platform/x86/amd/pmc/pmc-quirks.c
+++ b/drivers/platform/x86/amd/pmc/pmc-quirks.c
@@ -297,6 +297,15 @@ static const struct dmi_system_id fwbug_list[] = {
DMI_MATCH(DMI_PRODUCT_NAME, "83N1"),
}
},
+ /* https://bugzilla.kernel.org/show_bug.cgi?id=218557 */
+ {
+ .ident = "HP EliteBook 845 G10",
+ .driver_data = &quirk_s2idle_need_suspend_delay,
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "HP"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "HP EliteBook 845 14 inch G10 Notebook PC"),
+ }
+ },
{
.ident = "HP Laptop 14-fq1xxx",
.driver_data = &quirk_s2idle_spurious_8042,
--
2.56.0
reply other threads:[~2026-11-08 20:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261108204852.11194-1-kupospelov@gmail.com \
--to=kupospelov@gmail.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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®