From: Mario Limonciello <mario.limonciello@amd.com>
To: Werner Sembach <wse@tuxedocomputers.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: ggo@tuxedocomputers.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PCI: Avoid putting some root ports into D3 on some Ryzen chips
Date: Mon, 9 Dec 2024 13:45:21 -0600 [thread overview]
Message-ID: <215cd12e-6327-4aa6-ac93-eac2388e7dab@amd.com> (raw)
In-Reply-To: <20241209193614.535940-1-wse@tuxedocomputers.com>
On 12/9/2024 13:36, Werner Sembach wrote:
> From: Mario Limonciello <mario.limonciello@amd.com>
>
> commit 9d26d3a8f1b0 ("PCI: Put PCIe ports into D3 during suspend")
> sets the policy that all PCIe ports are allowed to use D3. When
> the system is suspended if the port is not power manageable by the
> platform and won't be used for wakeup via a PME this sets up the
> policy for these ports to go into D3hot.
>
> This policy generally makes sense from an OSPM perspective but it leads
> to problems with wakeup from suspend on the TUXEDO Sirius 16 Gen 1 with
> an unupdated BIOS.
>
> - On family 19h model 44h (PCI 0x14b9) this manifests as a missing wakeup
> interrupt.
> - On family 19h model 74h (PCI 0x14eb) this manifests as a system hang.
>
> On the affected Device + BIOS combination, add a quirk for the PCI device
> ID used by the problematic root port on both chips to ensure that these
> root ports are not put into D3hot at suspend.
>
> This patch is based on
> https://lore.kernel.org/linux-pci/20230708214457.1229-2-mario.limonciello@amd.com/
> but with the added condition both in the documentation and in the code to
> apply only to the TUXEDO Sirius 16 Gen 1 with the original unpatched BIOS.
>
> Co-developed-by: Georg Gottleuber <ggo@tuxedocomputers.com>
> Signed-off-by: Georg Gottleuber <ggo@tuxedocomputers.com>
> Co-developed-by: Werner Sembach <wse@tuxedocomputers.com>
> Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
> Cc: stable@vger.kernel.org # 6.1+
> Reported-by: Iain Lane <iain@orangesquash.org.uk>
> Closes: https://forums.lenovo.com/t5/Ubuntu/Z13-can-t-resume-from-suspend-with-external-USB-keyboard/m-p/5217121
> Fixes: 9d26d3a8f1b0 ("PCI: Put PCIe ports into D3 during suspend")
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> drivers/pci/quirks.c | 31 +++++++++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index 76f4df75b08a1..2226dca56197d 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -3908,6 +3908,37 @@ static void quirk_apple_poweroff_thunderbolt(struct pci_dev *dev)
> DECLARE_PCI_FIXUP_SUSPEND_LATE(PCI_VENDOR_ID_INTEL,
> PCI_DEVICE_ID_INTEL_CACTUS_RIDGE_4C,
> quirk_apple_poweroff_thunderbolt);
> +
> +/*
> + * Putting PCIe root ports on Ryzen SoCs with USB4 controllers into D3hot
> + * may cause problems when the system attempts wake up from s2idle.
> + *
> + * On family 19h model 44h (PCI 0x14b9) this manifests as a missing wakeup
> + * interrupt.
> + * On family 19h model 74h (PCI 0x14eb) this manifests as a system hang.
> + *
> + * This fix is still required on the TUXEDO Sirius 16 Gen1 with the original
> + * unupdated BIOS.
> + */
> +static const struct dmi_system_id quirk_ryzen_rp_d3_dmi_table[] = {
> + {
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "TUXEDO"),
> + DMI_MATCH(DMI_BOARD_NAME, "APX958"),
> + DMI_MATCH(DMI_BIOS_VERSION, "V1.00A00"),
> + },
> + },
> + {}
> +};
> +
> +static void quirk_ryzen_rp_d3(struct pci_dev *pdev)
> +{
> + if (dmi_check_system(quirk_ryzen_rp_d3_dmi_table) &&
> + !acpi_pci_power_manageable(pdev))
> + pdev->dev_flags |= PCI_DEV_FLAGS_NO_D3;
> +}
> +DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_AMD, 0x14b9, quirk_ryzen_rp_d3);
> +DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_AMD, 0x14eb, quirk_ryzen_rp_d3);
> #endif
>
> /*
Wait, what is wrong with:
commit 7d08f21f8c630 ("x86/PCI: Avoid PME from D3hot/D3cold for AMD
Rembrandt and Phoenix USB4")
Is that not activating on your system for some reason?
next prev parent reply other threads:[~2024-12-09 19:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 19:36 [PATCH v2] PCI: Avoid putting some root ports into D3 on some Ryzen chips Werner Sembach
2024-12-09 19:45 ` Mario Limonciello [this message]
2024-12-10 15:24 ` Werner Sembach
2024-12-10 16:00 ` Mario Limonciello
2024-12-11 12:47 ` Werner Sembach
2024-12-11 21:24 ` Mario Limonciello
2024-12-12 18:47 ` Werner Sembach
2024-12-12 19:01 ` Mario Limonciello
2024-12-13 10:05 ` Richard Hughes
2024-12-16 23:37 ` Werner Sembach
2024-12-17 10:10 ` Richard Hughes
2024-12-17 11:58 ` Werner Sembach
2024-12-17 14:12 ` Mario Limonciello
2024-12-17 14:07 ` Werner Sembach
2024-12-17 14:11 ` Mario Limonciello
2024-12-17 15:58 ` Werner Sembach
2024-12-17 16:08 ` Werner Sembach
2024-12-17 16:18 ` Mario Limonciello
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=215cd12e-6327-4aa6-ac93-eac2388e7dab@amd.com \
--to=mario.limonciello@amd.com \
--cc=bhelgaas@google.com \
--cc=ggo@tuxedocomputers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=wse@tuxedocomputers.com \
/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