From: sashiko-bot@kernel.org
To: "Krishna Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v5 1/3] PCI: host-common: Fix early bus-walk exit in d3cold_possible()
Date: Sat, 05 Sep 2026 00:56:49 +0000 [thread overview]
Message-ID: <20260905005649.6D8311F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260905-shutdown-v5-1-f0c6bafa1d4f@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] PME capability detection is still skipped for devices not in D3hot, leaving the fix incomplete for endpoints in D0.
--
commit 6e30f6ce4308da682727250705301b528bde2289
Author: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
PCI: host-common: Fix early bus-walk exit in d3cold_possible()
This commit addresses an issue in __pci_host_common_d3cold_possible() where
the bus walk was aborted when a downstream device was found outside of
PCI_D3hot. By changing the return value to 0 instead of -EOPNOTSUPP, it allows
the bus walk to continue and check subsequent devices for PME-from-D3cold
capabilities, which is especially important during shutdown when devices might
still be in D0.
> diff --git a/drivers/pci/controller/pci-host-common.c b/drivers/pci/controller/pci-host-common.c
> index a23907a875e57..78bc4c8c96564 100644
> --- a/drivers/pci/controller/pci-host-common.c
> +++ b/drivers/pci/controller/pci-host-common.c
> @@ -274,22 +274,19 @@ static int __pci_host_common_d3cold_possible(struct pci_dev *pdev,
> if (!pdev->dev.driver && !pci_is_enabled(pdev))
> return 0;
>
> - if (pdev->current_state != PCI_D3hot)
> - goto exit;
> + if (pdev->current_state != PCI_D3hot) {
> + *flags &= ~PCI_HOST_D3COLD_ALLOWED;
> + return 0;
> + }
[Severity: High]
This is a pre-existing issue, but doesn't this early return still skip PME
capability detection for endpoints in D0?
The commit message notes it is common during shutdown for an endpoint to still
be in D0, and this patch aims to ensure later devices on the bus are visited.
However, for the very device in D0, __pci_host_common_d3cold_possible() will
clear PCI_HOST_D3COLD_ALLOWED and return 0 before it checks device_may_wakeup().
Does this mean a PCIe endpoint in D0 that supports Wakeup/PME from D3cold will
fail to have its PME capabilities recorded, causing its auxiliary power (Vaux)
to be incorrectly turned off during shutdown?
>
> if (device_may_wakeup(&pdev->dev)) {
> - if (!pci_pme_capable(pdev, PCI_D3cold))
> - goto exit;
> - else
> + if (pci_pme_capable(pdev, PCI_D3cold))
> *flags |= PCI_HOST_PME_D3COLD_CAPABLE;
> + else
> + *flags &= ~PCI_HOST_D3COLD_ALLOWED;
> }
>
> return 0;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260905-shutdown-v5-0-f0c6bafa1d4f@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-09-05 0:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 0:48 [PATCH v5 0/3] PCI: qcom: Implement shutdown() to avoid SMMU/NoC errors on reboot Krishna Chaitanya Chundru
2026-09-05 0:48 ` [PATCH v5 1/3] PCI: host-common: Fix early bus-walk exit in d3cold_possible() Krishna Chaitanya Chundru
2026-09-05 0:56 ` sashiko-bot [this message]
2026-09-09 10:50 ` Konrad Dybcio
2026-09-05 0:48 ` [PATCH v5 2/3] PCI: dwc: Force L2 link entry on shutdown/reboot without D3cold check Krishna Chaitanya Chundru
2026-09-05 1:01 ` sashiko-bot
2026-09-09 10:53 ` Konrad Dybcio
2026-09-09 11:00 ` Manivannan Sadhasivam
2026-09-09 11:47 ` Krishna Chaitanya Chundru
2026-09-05 0:48 ` [PATCH v5 3/3] PCI: qcom: Implement shutdown() callback Krishna Chaitanya Chundru
2026-09-05 1:03 ` sashiko-bot
2026-09-09 10:56 ` Konrad Dybcio
2026-09-09 11:49 ` Krishna Chaitanya Chundru
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=20260905005649.6D8311F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.