From: Mario Limonciello <superm1@kernel.org>
To: Lukas Wunner <lukas@wunner.de>,
Bjorn Helgaas <helgaas@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Alex Williamson <alex@shazbot.org>, linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Stop setting cached power state to "unknown" on unbind
Date: Fri, 17 Apr 2026 13:26:09 -0500 [thread overview]
Message-ID: <7ebd7665-4ae8-4937-8d48-04fe9c04fbe1@kernel.org> (raw)
In-Reply-To: <af7d11d3ceb231acc90829f7a5c8400c2446744f.1776415510.git.lukas@wunner.de>
On 4/17/26 03:51, Lukas Wunner wrote:
> When a PCI device is unbound from its driver, pci_device_remove() sets the
> cached power state in pci_dev->current_state to PCI_UNKNOWN. This was
> introduced by commit 2449e06a5696 ("PCI: reset pci device state to unknown
> state for resume") to invalidate the cached power state in case the system
> is subsequently put to sleep.
>
> For bound devices, the cached power state is set to PCI_UNKNOWN in
> pci_pm_suspend_noirq(), immediately before entering system sleep.
>
> Extend to unbound devices for consistency.
>
> This obviates the need to change the cached power state on unbind, so stop
> doing so.
>
> Signed-off-by: Lukas Wunner <lukas@wunner.de>
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
FWIW I also had review-prompts /kreview check for corner cases and it
didn't find any.
> ---
> drivers/pci/pci-driver.c | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
> index 7c2d9d5..774892d 100644
> --- a/drivers/pci/pci-driver.c
> +++ b/drivers/pci/pci-driver.c
> @@ -482,13 +482,6 @@ static void pci_device_remove(struct device *dev)
> pm_runtime_put_sync(dev);
>
> /*
> - * If the device is still on, set the power state as "unknown",
> - * since it might change by the next time we load the driver.
> - */
> - if (pci_dev->current_state == PCI_D0)
> - pci_dev->current_state = PCI_UNKNOWN;
> -
> - /*
> * We would love to complain here if pci_dev->is_enabled is set, that
> * the driver should have called pci_disable_device(), but the
> * unfortunate fact is there are too many odd BIOS and bridge setups
> @@ -862,7 +855,7 @@ static int pci_pm_suspend_noirq(struct device *dev)
>
> if (!pm) {
> pci_save_state(pci_dev);
> - goto Fixup;
> + goto set_unknown;
> }
>
> if (pm->suspend_noirq) {
> @@ -914,6 +907,7 @@ static int pci_pm_suspend_noirq(struct device *dev)
> goto Fixup;
> }
>
> +set_unknown:
> pci_pm_set_unknown_state(pci_dev);
>
> /*
prev parent reply other threads:[~2026-04-17 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 8:51 [PATCH] PCI: Stop setting cached power state to "unknown" on unbind Lukas Wunner
2026-04-17 18:26 ` Mario Limonciello [this message]
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=7ebd7665-4ae8-4937-8d48-04fe9c04fbe1@kernel.org \
--to=superm1@kernel.org \
--cc=alex@shazbot.org \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=rafael@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