From: Daniel Gibson <daniel@gibson.sh>
To: stable@vger.kernel.org
Cc: Daniel Gibson <daniel@gibson.sh>
Subject: [PATCH 0/2] amd_pmc: Backport additional delay_suspend patches for linux-6.6.y
Date: Wed, 22 Jul 2026 18:54:00 +0200 [thread overview]
Message-ID: <20260722165402.3199573-1-daniel@gibson.sh> (raw)
These commits belong to:
bc08f495c7b8 platform/x86/amd/pmc: Check for intermediate wakeup in function
caa25575c3c2 platform/x86/amd/pmc: Delay suspend for some Lenovo Laptops
0c9901b84b59 platform/x86/amd/pmc: Add delay_suspend module parameter
The "Don't log during intermediate wakeups" commit prevents the
aforementioned commits from spamming dmesg during intermediate wakeups.
The affected IdeaPad devices have *lots* of intermediate wakeups when
charging while in s2idle.
The other commit is more cosmetical, but is also trivial and ensures that
the log messages log the same on all kernel versions with these patches.
These commits are already merged in mainline and in the stable-rc
branches for 6.12, 6.18 and 7.1.
In 6.6 they were missing because of merge conflicts. I resolved those.
See also https://lore.kernel.org/stable/2026072230-volatile-citric-73fa@gregkh/
Daniel Gibson (2):
platform/x86/amd/pmc: Don't log during intermediate wakeups
platform/x86/amd/pmc: Avoid logging "(null)" for DMI values
drivers/platform/x86/amd/pmc/pmc.c | 39 ++++++++++++++++++++++++------
drivers/platform/x86/amd/pmc/pmc.h | 1 +
2 files changed, 32 insertions(+), 8 deletions(-)
--
2.48.1
next reply other threads:[~2026-07-22 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 16:54 Daniel Gibson [this message]
2026-07-22 16:54 ` [PATCH 1/2] platform/x86/amd/pmc: Don't log during intermediate wakeups Daniel Gibson
2026-07-22 16:54 ` [PATCH 2/2] platform/x86/amd/pmc: Avoid logging "(null)" for DMI values Daniel Gibson
2026-07-24 11:22 ` [PATCH 0/2] amd_pmc: Backport additional delay_suspend patches for linux-6.6.y Sasha Levin
2026-07-25 14:54 ` Daniel Gibson
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=20260722165402.3199573-1-daniel@gibson.sh \
--to=daniel@gibson.sh \
--cc=stable@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