mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chen Wang <unicorn_wang@outlook.com>
To: Aksh Garg <a-garg7@ti.com>,
	linux-pci@vger.kernel.org, vigneshr@ti.com, s-vadapalli@ti.com,
	lpieralisi@kernel.org, kwilczynski@kernel.org, mani@kernel.org,
	robh@kernel.org, bhelgaas@google.com, mpillai@cadence.com,
	me@ziyao.cc, 18255117159@163.com
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, danishanwar@ti.com
Subject: Re: [PATCH] PCI: cadence: skip the link polling when endpoint not connected
Date: Mon, 8 Jun 2026 14:26:04 +0800	[thread overview]
Message-ID: <MA5P287MB6080BBC405ACFED6C3D307AAFE1C2@MA5P287MB6080.INDP287.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20260605071922.1724499-1-a-garg7@ti.com>


On 6/5/2026 3:19 PM, 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>

Reviewed-by: Chen Wang <unicorn_wang@outlook.com>

[......]



  reply	other threads:[~2026-06-08  6:26 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 [this message]
2026-06-09  3:42 ` Siddharth Vadapalli
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=MA5P287MB6080BBC405ACFED6C3D307AAFE1C2@MA5P287MB6080.INDP287.PROD.OUTLOOK.COM \
    --to=unicorn_wang@outlook.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=s-vadapalli@ti.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

all inboxes | Powered by JetHome®