From: Bjorn Helgaas <helgaas@kernel.org>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
lpieralisi@kernel.org, kwilczynski@kernel.org,
bhelgaas@google.com, will@kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
linux-arm-msm@vger.kernel.org, zhangsenchuan@eswincomputing.com,
vincent.guittot@linaro.org
Subject: Re: [PATCH v2 2/3] PCI: qcom: Check for the presence of a device instead of Link up during suspend
Date: Thu, 13 Nov 2025 11:22:50 -0600 [thread overview]
Message-ID: <20251113172250.GA2291436@bhelgaas> (raw)
In-Reply-To: <zgj3ubyb234ig6ndz6ov5q3szvuxnd3jkz2rjglbad4ksri6nl@ov7boxuar4va>
On Thu, Nov 13, 2025 at 10:24:17PM +0530, Manivannan Sadhasivam wrote:
> On Thu, Nov 13, 2025 at 10:41:47AM -0600, Bjorn Helgaas wrote:
> > On Fri, Nov 07, 2025 at 10:13:18AM +0530, Manivannan Sadhasivam wrote:
> > > The suspend handler checks for the PCIe Link up to decide when to turn off
> > > the controller resources. But this check is racy as the PCIe Link can go
> > > down just after this check.
> > >
> > > So use the newly introduced API, pci_root_ports_have_device() that checks
> > > for the presence of a device under any of the Root Ports to replace the
> > > Link up check.
> >
> > Why is pci_root_ports_have_device() itself not racy?
>
> Because it is very uncommon for the 'pci_dev' to go away during the
> host controller suspend. It might still be possible in edge cases,
> but very common as the link down. I can reword it.
I guess it's better to acknowledge replacing one race with another
than it would be to suggest that this *removes* a race.
But I don't understand the point of this. Is
pci_root_ports_have_device() *less* racy than the
qcom_pcie_suspend_noirq() check? Why would that be?
I'm kind of skeptical about adding pci_root_ports_have_device() at
all. It seems like it just encourages racy behavior in drivers.
> > > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
> > > ---
> > > drivers/pci/controller/dwc/pcie-qcom.c | 6 ++++--
> > > 1 file changed, 4 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/pci/controller/dwc/pcie-qcom.c b/drivers/pci/controller/dwc/pcie-qcom.c
> > > index 805edbbfe7eb..b2b89e2e4916 100644
> > > --- a/drivers/pci/controller/dwc/pcie-qcom.c
> > > +++ b/drivers/pci/controller/dwc/pcie-qcom.c
> > > @@ -2018,6 +2018,7 @@ static int qcom_pcie_probe(struct platform_device *pdev)
> > > static int qcom_pcie_suspend_noirq(struct device *dev)
> > > {
> > > struct qcom_pcie *pcie;
> > > + struct dw_pcie_rp *pp;
> > > int ret = 0;
> > >
> > > pcie = dev_get_drvdata(dev);
> > > @@ -2053,8 +2054,9 @@ static int qcom_pcie_suspend_noirq(struct device *dev)
> > > * powerdown state. This will affect the lifetime of the storage devices
> > > * like NVMe.
> > > */
> > > - if (!dw_pcie_link_up(pcie->pci)) {
> > > - qcom_pcie_host_deinit(&pcie->pci->pp);
> > > + pp = &pcie->pci->pp;
> > > + if (!pci_root_ports_have_device(pp->bridge->bus)) {
> > > + qcom_pcie_host_deinit(pp);
> > > pcie->suspended = true;
> > > }
> > >
> > > --
> > > 2.48.1
> > >
>
> --
> மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2025-11-13 17:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 4:43 [PATCH v2 0/3] PCI: dwc: Check for device presence in suspend and resume Manivannan Sadhasivam
2025-11-07 4:43 ` [PATCH v2 1/3] PCI: host-common: Add an API to check for any device under the Root Ports Manivannan Sadhasivam
2025-11-10 16:36 ` Frank Li
2025-11-07 4:43 ` [PATCH v2 2/3] PCI: qcom: Check for the presence of a device instead of Link up during suspend Manivannan Sadhasivam
2025-11-13 16:41 ` Bjorn Helgaas
2025-11-13 16:54 ` Manivannan Sadhasivam
2025-11-13 17:22 ` Bjorn Helgaas [this message]
2025-11-17 17:37 ` Manivannan Sadhasivam
2025-11-19 8:03 ` zhangsenchuan
2025-11-19 16:15 ` Manivannan Sadhasivam
2025-11-07 4:43 ` [PATCH v2 3/3] PCI: dwc: Check for the device presence during suspend and resume Manivannan Sadhasivam
2025-11-10 16:26 ` Frank Li
2025-11-13 16:56 ` Manivannan Sadhasivam
2025-11-13 16:40 ` Bjorn Helgaas
2025-11-13 17:01 ` Manivannan Sadhasivam
2025-11-14 2:03 ` zhangsenchuan
2025-11-08 10:24 ` [PATCH v2 0/3] PCI: dwc: Check for device presence in " Manivannan Sadhasivam
2025-11-10 10:48 ` Vincent Guittot
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=20251113172250.GA2291436@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=will@kernel.org \
--cc=zhangsenchuan@eswincomputing.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