From: Mario Limonciello <superm1@kernel.org>
To: Lukas Wunner <lukas@wunner.de>,
Bjorn Helgaas <helgaas@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
linux-pci@vger.kernel.org, linux-pm@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org,
Oleksij Rempel <o.rempel@pengutronix.de>,
Timo Jyrinki <timo.jyrinki@iki.fi>,
Ernst Persson <ernstp@gmail.com>,
Steven Harms <sjharms@gmail.com>,
James Ettle <james@ettle.org.uk>,
Nick Coghlan <ncoghlan@gmail.com>,
Weng Xuetian <wengxt@gmail.com>,
Andrey Rahmatullin <wrar@wrar.name>,
Boris Barbour <boris.barbour@ens.fr>,
Vlastimil Zima <vlastimil.zima@gmail.com>,
David Banks <amoebae@gmail.com>,
Michal Jaegermann <michal@harddata.com>,
Chris Moeller <kode54@gmail.com>,
Daniel Fraga <fragabr@gmail.com>,
Javier Marcet <jmarcet@gmail.com>,
Pavel Pisa <pisa@cmp.felk.cvut.cz>
Subject: Re: [PATCH] PCI/PM: Move ASUS EHCI workaround out of generic code
Date: Thu, 11 Sep 2025 08:34:56 -0500 [thread overview]
Message-ID: <80980751-64db-4dc2-9516-03046e8b4b31@kernel.org> (raw)
In-Reply-To: <75e4ae507fa4faddd063a3a9e17d319ed84529b6.1757562971.git.lukas@wunner.de>
On 9/11/25 8:11 AM, Lukas Wunner wrote:
> In 2012, commit dbf0e4c7257f ("PCI: EHCI: fix crash during suspend on ASUS
> computers") amended pci_pm_suspend_noirq() to work around a BIOS issue by
> clearing the Command register if the suspended device is a USB EHCI host
> controller.
>
> Commit 0b68c8e2c3af ("PCI: EHCI: Fix crash during hibernation on ASUS
> computers") subsequently amended pci_pm_poweroff_noirq() to do the same.
>
> Two years later, commit 7d2a01b87f16 ("PCI: Add pci_fixup_suspend_late
> quirk pass") introduced the ability to execute arbitrary quirks
> specifically in pci_pm_suspend_noirq() and pci_pm_poweroff_noirq().
>
> This allows moving the ASUS workaround out of generic code and into a
> proper quirk to improve maintainability and readability. Constrain to x86
> since the ASUS BIOS doesn't seem to have been used on other arches.
>
> lspci output of affected EHCI host controllers reveals that the only bits
> set in the Command register are Memory Space Enable and Bus Master Enable:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658778
>
> The latter is cleared by:
> hcd_pci_suspend()
> suspend_common()
> pci_disable_device()
>
> pci_disable_device() does not clear I/O and Memory Space Enable, although
> its name suggests otherwise.
That was my gut reaction as well.
> The kernel has never disabled these bits
> once they're enabled. Doing so would avoid the need for the quirk, but it
> is unclear what will break if this fundamental behavior is changed.
>
It's too late for this cycle to do so, but how would you feel about
making this change at the start of the next cycle so it had a whole
cycle to bake in linux-next and see if there is a problem in doing so?
If there is it could certainly be moved back to a quirk.
> Signed-off-by: Lukas Wunner <lukas@wunner.de>
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>> ---
> arch/x86/pci/fixup.c | 19 +++++++++++++++++++
> drivers/pci/pci-driver.c | 19 -------------------
> 2 files changed, 19 insertions(+), 19 deletions(-)
>
> diff --git a/arch/x86/pci/fixup.c b/arch/x86/pci/fixup.c
> index e7e71490bd25..c34ff72434f2 100644
> --- a/arch/x86/pci/fixup.c
> +++ b/arch/x86/pci/fixup.c
> @@ -1041,3 +1041,22 @@ static void quirk_tuxeo_rp_d3(struct pci_dev *pdev)
> }
> DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_AMD, 0x1502, quirk_tuxeo_rp_d3);
> #endif /* CONFIG_SUSPEND */
> +
> +#ifdef CONFIG_PM_SLEEP
> +/*
> + * Some BIOSes from ASUS have a bug: If a USB EHCI host controller's Command
> + * register is not 0 on suspend, the BIOS assumes that the controller has not
> + * been quiesced and tries to turn it off. If the controller is already in D3,
> + * this can hang or cause memory corruption.
> + *
> + * Since the value of the Command register does not matter once the device has
> + * been suspended, it can safely be set to 0.
> + */
> +static void quirk_clear_command_reg(struct pci_dev *pdev)
> +{
> + pci_write_config_word(pdev, PCI_COMMAND, 0);
> +}
> +DECLARE_PCI_FIXUP_CLASS_SUSPEND_LATE(PCI_ANY_ID, PCI_ANY_ID,
> + PCI_CLASS_SERIAL_USB_EHCI, 0,
> + quirk_clear_command_reg);
> +#endif /* CONFIG_PM_SLEEP */
> diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
> index 63665240ae87..e1089dfeb419 100644
> --- a/drivers/pci/pci-driver.c
> +++ b/drivers/pci/pci-driver.c
> @@ -914,18 +914,6 @@ static int pci_pm_suspend_noirq(struct device *dev)
>
> pci_pm_set_unknown_state(pci_dev);
>
> - /*
> - * Some BIOSes from ASUS have a bug: If a USB EHCI host controller's
> - * PCI COMMAND register isn't 0, the BIOS assumes that the controller
> - * hasn't been quiesced and tries to turn it off. If the controller
> - * is already in D3, this can hang or cause memory corruption.
> - *
> - * Since the value of the COMMAND register doesn't matter once the
> - * device has been suspended, we can safely set it to 0 here.
> - */
> - if (pci_dev->class == PCI_CLASS_SERIAL_USB_EHCI)
> - pci_write_config_word(pci_dev, PCI_COMMAND, 0);
> -
> Fixup:
> pci_fixup_device(pci_fixup_suspend_late, pci_dev);
>
> @@ -1205,13 +1193,6 @@ static int pci_pm_poweroff_noirq(struct device *dev)
> if (!pci_dev->state_saved && !pci_has_subordinate(pci_dev))
> pci_prepare_to_sleep(pci_dev);
>
> - /*
> - * The reason for doing this here is the same as for the analogous code
> - * in pci_pm_suspend_noirq().
> - */
> - if (pci_dev->class == PCI_CLASS_SERIAL_USB_EHCI)
> - pci_write_config_word(pci_dev, PCI_COMMAND, 0);
> -
> pci_fixup_device(pci_fixup_suspend_late, pci_dev);
>
> return 0;
next prev parent reply other threads:[~2025-09-11 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 13:11 [PATCH] PCI/PM: Move ASUS EHCI workaround out of generic code Lukas Wunner
2025-09-11 13:28 ` Rafael J. Wysocki
2025-09-11 13:34 ` Mario Limonciello [this message]
2025-09-11 13:43 ` Rafael J. Wysocki
2025-09-11 13:46 ` Mario Limonciello
2025-09-11 13:56 ` Rafael J. Wysocki
2025-09-11 18:20 ` Mario Limonciello
2025-09-12 7:26 ` Lukas Wunner
2025-09-12 9:34 ` Rafael J. Wysocki
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=80980751-64db-4dc2-9516-03046e8b4b31@kernel.org \
--to=superm1@kernel.org \
--cc=amoebae@gmail.com \
--cc=boris.barbour@ens.fr \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=ernstp@gmail.com \
--cc=fragabr@gmail.com \
--cc=helgaas@kernel.org \
--cc=hpa@zytor.com \
--cc=james@ettle.org.uk \
--cc=jmarcet@gmail.com \
--cc=kode54@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michal@harddata.com \
--cc=mingo@redhat.com \
--cc=ncoghlan@gmail.com \
--cc=o.rempel@pengutronix.de \
--cc=pisa@cmp.felk.cvut.cz \
--cc=rafael@kernel.org \
--cc=sjharms@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
--cc=timo.jyrinki@iki.fi \
--cc=vlastimil.zima@gmail.com \
--cc=wengxt@gmail.com \
--cc=wrar@wrar.name \
--cc=x86@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