From: Frank Li <Frank.li@nxp.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Cc: lpieralisi@kernel.org, kwilczynski@kernel.org, mani@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 3/3] PCI: dwc: Check for the device presence during suspend and resume
Date: Mon, 10 Nov 2025 11:26:38 -0500 [thread overview]
Message-ID: <aRISPgCZyEZxStIN@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20251107044319.8356-4-manivannan.sadhasivam@oss.qualcomm.com>
On Fri, Nov 07, 2025 at 10:13:19AM +0530, Manivannan Sadhasivam wrote:
> If there is no device available under the Root Ports, there is no point in
> sending PME_Turn_Off and waiting for L2/L3 transition during suspend, it
> will result in a timeout. Hence, skip those steps if no device is available
> during suspend.
>
> During resume, do not wait for the link up if there was no device connected
> before suspend. It is very unlikely that a device will get connected while
> the host system was suspended.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
> ---
> drivers/pci/controller/dwc/pcie-designware-host.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/drivers/pci/controller/dwc/pcie-designware-host.c b/drivers/pci/controller/dwc/pcie-designware-host.c
> index 20c9333bcb1c..5a39e7139ec9 100644
> --- a/drivers/pci/controller/dwc/pcie-designware-host.c
> +++ b/drivers/pci/controller/dwc/pcie-designware-host.c
> @@ -20,6 +20,7 @@
> #include <linux/platform_device.h>
>
> #include "../../pci.h"
> +#include "../pci-host-common.h"
> #include "pcie-designware.h"
>
> static struct pci_ops dw_pcie_ops;
> @@ -1129,6 +1130,9 @@ int dw_pcie_suspend_noirq(struct dw_pcie *pci)
> u32 val;
> int ret;
>
> + if (!pci_root_ports_have_device(pci->pp.bridge->bus))
> + goto stop_link;
> +
> /*
> * If L1SS is supported, then do not put the link into L2 as some
> * devices such as NVMe expect low resume latency.
> @@ -1162,6 +1166,7 @@ int dw_pcie_suspend_noirq(struct dw_pcie *pci)
> */
> udelay(1);
I think move pme_turn_off() to helper funciton will make code look better
if (pci_root_ports_have_device()) {
ret = dwc_pme_turn_off();
if (ret)
return ret;
};
>
> +stop_link:
> dw_pcie_stop_link(pci);
> if (pci->pp.ops->deinit)
> pci->pp.ops->deinit(&pci->pp);
> @@ -1195,6 +1200,14 @@ int dw_pcie_resume_noirq(struct dw_pcie *pci)
> if (ret)
> return ret;
>
> + /*
> + * If there was no device before suspend, skip waiting for link up as
> + * it is bound to fail. It is very unlikely that a device will get
> + * connected *during* suspend.
I think it should use certern term. the a device will not get linkup during
suspend, if this happen, it is a new hotjoin device after system resume.
Frank
> + */
> + if (!pci_root_ports_have_device(pci->pp.bridge->bus))
> + return 0;
> +
> ret = dw_pcie_wait_for_link(pci);
> if (ret)
> return ret;
> --
> 2.48.1
>
next prev parent reply other threads:[~2025-11-10 16:27 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
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 [this message]
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=aRISPgCZyEZxStIN@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--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