[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230711005325.1499-1-mario.limonciello@amd.com>
Date: Mon, 10 Jul 2023 19:53:23 -0500
From: Mario Limonciello <mario.limonciello@....com>
To: "Rafael J . Wysocki" <rafael@...nel.org>,
Bjorn Helgaas <helgaas@...nel.org>
CC: <linux-pci@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Len Brown <lenb@...nel.org>, <linux-acpi@...r.kernel.org>,
Mario Limonciello <mario.limonciello@....com>
Subject: [PATCH v7 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 series adjusts it so only root ports that are power manageable by
the platform will be considered for being put into D3.
Mario Limonciello (2):
PCI: Refactor pci_bridge_d3_possible()
PCI: Don't put PCIe root ports into D3 unless they are power
manageable
drivers/pci/pci.c | 76 ++++++++++++++++++++++++++---------------------
1 file changed, 42 insertions(+), 34 deletions(-)
base-commit: 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5
--
2.34.1
Powered by blists - more mailing lists