From: sashiko-bot@kernel.org
To: "Francisco Beltrán Millalén" <fbeltranmillalen@gmail.com>,
linux-pci@vger.kernel.org
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 2/2] PCI: Do not mistake an absent device for an active link
Date: Mon, 19 Oct 2026 20:35:08 +0000 [thread overview]
Message-ID: <sashiko-outbox-178180@kernel.org> (raw)
In-Reply-To: <20261019202445.38259-3-fbeltranmillalen@gmail.com>
> When an inaccessible bridge's Link Status register reads as 0xffff,
> both PCI_EXP_LNKSTA_DLLLA and PCI_EXP_LNKSTA_LT appear set. The link
> wait code then takes the inaccessible bridge for an active link:
>
> - pci_bridge_wait_for_secondary_bus(), for ports up to 5 GT/s, decides
> that the link is up and waits PCIE_RESET_READY_POLL_MS for the device
> below it;
>
> - pcie_wait_for_link_status(), used for faster ports and by
> pcie_retrain_link(), reports success at once when waiting for an
> active link, and times out after PCIE_LINK_RETRAIN_TIMEOUT_MS when
> waiting for LT to clear.
>
> Treat an all-ones read as the device being gone. All callers of
> pcie_wait_for_link_status() and pcie_retrain_link() treat any non-zero
> return as failure.
>
> On a MacBookPro14,3 whose Thunderbolt controller does not come back from
> S3, the downstream ports of the controller are 2.5 GT/s ports that no
> longer answer. Resume spent about 65 seconds waiting for the xHCI
> controller behind one of them ("not ready 65535ms after resume"); with
> the pci_bridge_wait_for_secondary_bus() change it gives up on that
> controller after about one second. That machine never reaches
> pcie_wait_for_link_status() in this situation, so that part has not been
> tested.
>
> Assisted-by: LLM
> Signed-off-by: Francisco Beltrán Millalén <fbeltranmillalen@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261019202445.38259-1-fbeltranmillalen@gmail.com?part=2
next prev parent reply other threads:[~2026-10-19 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 20:24 [PATCH v3 0/2] PCI/PM: Keep the saved config space of an inaccessible device Francisco Beltrán Millalén
2026-10-19 20:24 ` [PATCH v3 1/2] " Francisco Beltrán Millalén
2026-10-19 20:34 ` sashiko-bot
2026-10-19 20:24 ` [PATCH v3 2/2] PCI: Do not mistake an absent device for an active link Francisco Beltrán Millalén
2026-10-19 20:35 ` sashiko-bot [this message]
2026-10-20 10:20 ` [PATCH v3 0/2] PCI/PM: Keep the saved config space of an inaccessible device Mika Westerberg
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=sashiko-outbox-178180@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=fbeltranmillalen@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox