[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230802201013.910-1-mario.limonciello@amd.com>
Date: Wed, 2 Aug 2023 15:10:11 -0500
From: Mario Limonciello <mario.limonciello@....com>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Bjorn Helgaas <helgaas@...nel.org>
CC: <linux-pci@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-acpi@...r.kernel.org>, Iain Lane <iain@...ngesquash.org.uk>,
"Andy Shevchenko" <andriy.shevchenko@...ux.intel.com>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@...ux.intel.com>,
Mario Limonciello <mario.limonciello@....com>
Subject: [PATCH v8 0/2] Fix wakeup problems on some AMD platforms
Problems have been reported on AMD laptops with suspend/resume
where particular root ports are put into D3 and then the system is unable
to resume properly.
The issue boils down to the currently selected kernel policy for root port
behavior at suspend time:
0) If the machine is from 2015 or later
1) If a PCIe root port is power manageable by the platform then platform
will be used to determine the power state of the root port at suspend.
2) If the PCIe root is not power manageable by the platform then the kernel
will check if it was configured to wakeup.
3) If it was, then it will be put into the deepest state that supports
wakeup from PME.
4) If it wasn't, then it will be put into D3hot.
This patch adjusts it so that device constraints for low power idle are
considered instead of a time based policy.
Mario Limonciello (2):
ACPI: Add comments to clarify some #ifdef statements
PCI/ACPI: Use device constraints instead of dates to opt devices into
D3
drivers/acpi/x86/s2idle.c | 28 ++++++++++++++++++++++++++--
drivers/pci/pci-acpi.c | 19 +++++++++++++++++++
drivers/pci/pci.c | 15 ++++++++++-----
drivers/pci/pci.h | 5 +++++
include/linux/acpi.h | 10 ++++++++--
5 files changed, 68 insertions(+), 9 deletions(-)
--
2.34.1
Powered by blists - more mailing lists