From: Mario Limonciello <mario.limonciello@amd.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Mark Gross <mgross@linux.intel.com>,
"open list:X86 PLATFORM DRIVERS"
<platform-driver-x86@vger.kernel.org>,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
open list <linux-kernel@vger.kernel.org>,
"Mario Limonciello" <mario.limonciello@amd.com>
Subject: [PATCH 0/2] Fix s2idle resume on HP 15s-eq2xxx
Date: Mon, 10 Jul 2023 13:39:32 -0500 [thread overview]
Message-ID: <20230710183934.17315-1-mario.limonciello@amd.com> (raw)
HP 15s-eq2xxx has problems resuming from s2idle when IOMMU is enabled.
This is the same root cause as some Lenovo laptops had where IOMMU enabled
caused issues with NVME during s2idle resume from a problematic SMI.
To series fixes the issue by re-using the same quirk developed from the
older Lenovo laptops.
Mario Limonciello (2):
platform/x86: Move s2idle quirk from thinkpad-acpi to amd-pmc
platform/x86/amd: pmc: Apply nvme quirk to HP 15s-eq2xxx
drivers/platform/x86/amd/Makefile | 2 +-
drivers/platform/x86/amd/pmc-quirks.c | 172 ++++++++++++++++++++++++++
drivers/platform/x86/amd/pmc.c | 30 +----
drivers/platform/x86/amd/pmc.h | 43 +++++++
drivers/platform/x86/thinkpad_acpi.c | 143 ---------------------
5 files changed, 222 insertions(+), 168 deletions(-)
create mode 100644 drivers/platform/x86/amd/pmc-quirks.c
create mode 100644 drivers/platform/x86/amd/pmc.h
--
2.34.1
next reply other threads:[~2023-07-10 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 18:39 Mario Limonciello [this message]
2023-07-10 18:39 ` [PATCH 1/2] platform/x86: Move s2idle quirk from thinkpad-acpi to amd-pmc Mario Limonciello
2023-07-10 18:39 ` [PATCH 2/2] platform/x86/amd: pmc: Apply nvme quirk to HP 15s-eq2xxx Mario Limonciello
2023-07-11 9:47 ` [PATCH 0/2] Fix s2idle resume on " Hans de Goede
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=20230710183934.17315-1-mario.limonciello@amd.com \
--to=mario.limonciello@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.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 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®