mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Aksh Garg <a-garg7@ti.com>
Cc: <vigneshr@ti.com>, <lpieralisi@kernel.org>,
	<kwilczynski@kernel.org>, <mani@kernel.org>, <robh@kernel.org>,
	<bhelgaas@google.com>, <mpillai@cadence.com>,
	<unicorn_wang@outlook.com>, <me@ziyao.cc>, <18255117159@163.com>,
	<linux-pci@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <danishanwar@ti.com>,
	<s-vadapalli@ti.com>
Subject: Re: [PATCH] PCI: cadence: skip the link polling when endpoint not connected
Date: Tue, 9 Jun 2026 09:12:46 +0530	[thread overview]
Message-ID: <19ded2fa-4560-4b38-975c-6b490328e992@ti.com> (raw)
In-Reply-To: <20260605071922.1724499-1-a-garg7@ti.com>

On 05/06/26 12:49, Aksh Garg wrote:
> cdns_pcie_host_wait_for_link() polls on link-up for 10 retries with a
> delay of 90-100ms each (~1 second). A call to cdns_pcie_host_link_setup()
> during the resume operation blocks the resume operation unnecessarily for
> ~1s even when no endpoint device is connected.
> 
> Add skip_link_polling flag to track link state across suspend/resume
> cycles. If link was down before suspend, skip the expensive polling
> in resume since no endpoint was present.
> 
> Signed-off-by: Aksh Garg <a-garg7@ti.com>
> ---
>   drivers/pci/controller/cadence/pci-j721e.c             | 5 +++++
>   drivers/pci/controller/cadence/pcie-cadence-host-hpa.c | 3 +++
>   drivers/pci/controller/cadence/pcie-cadence-host.c     | 3 +++
>   drivers/pci/controller/cadence/pcie-cadence.h          | 3 +++
>   4 files changed, 14 insertions(+)
> 
> diff --git a/drivers/pci/controller/cadence/pci-j721e.c b/drivers/pci/controller/cadence/pci-j721e.c
> index bfdfe98d5aba..849eb8bb9e45 100644
> --- a/drivers/pci/controller/cadence/pci-j721e.c
> +++ b/drivers/pci/controller/cadence/pci-j721e.c
> @@ -686,6 +686,11 @@ static int j721e_pcie_suspend_noirq(struct device *dev)
>   	struct j721e_pcie *pcie = dev_get_drvdata(dev);
>   
>   	if (pcie->mode == PCI_MODE_RC) {
> +		struct cdns_pcie_rc *rc = cdns_pcie_to_rc(pcie->cdns_pcie);
> +
> +		/* If link is down before suspend, skip polling in resume */
> +		rc->skip_link_polling = !j721e_pcie_link_up(pcie->cdns_pcie);
> +

Please consider the following scenario:
1. Endpoint device is not connected initially and we suspend with 
'skip_link_polling' set to true.
2. We resume and skip link polling.
3. An Endpoint device is connected to the PCIe Connector a while later.
4. We perform a bus rescan, but with skip_link_polling still set (in 
resume), wouldn't we skip polling for the link to be up?

Shouldn't 'skip_link_polling' be set to false on resume, after we skip the 
polling initially, in order to allow waiting for a link up for a newly 
connected device? Although this may not be done in practice and the 
Endpoint device may always be left connected from the start, I am wondering 
if we should clear 'skip_link_polling' on resume to account for the 
aforementioned scenario. Let me know if I am overlooking something here.

>   		gpiod_set_value_cansleep(pcie->reset_gpio, 0);
>   		clk_disable_unprepare(pcie->refclk);
>   	}

[TRIMMED]

Regards,
Siddharth.

  parent reply	other threads:[~2026-06-09  3:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05  7:19 Aksh Garg
2026-06-08  6:26 ` Chen Wang
2026-06-09  3:42 ` Siddharth Vadapalli [this message]
2026-06-09  4:28   ` Aksh Garg
2026-06-09  5:11     ` Siddharth Vadapalli
2026-06-09  5:36       ` Manikandan Karunakaran Pillai
2026-06-22 14:52 ` Manivannan Sadhasivam
2026-06-23  5:23   ` Aksh Garg
2026-06-23  5:45     ` Manivannan Sadhasivam
2026-06-23  6:37       ` Aksh Garg

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=19ded2fa-4560-4b38-975c-6b490328e992@ti.com \
    --to=s-vadapalli@ti.com \
    --cc=18255117159@163.com \
    --cc=a-garg7@ti.com \
    --cc=bhelgaas@google.com \
    --cc=danishanwar@ti.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=me@ziyao.cc \
    --cc=mpillai@cadence.com \
    --cc=robh@kernel.org \
    --cc=unicorn_wang@outlook.com \
    --cc=vigneshr@ti.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

Powered by JetHome