From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
linux-kernel@vger.kernel.org
Cc: "Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: [PATCH 1/2] PCI: Clear LBMS on resume to avoid Target Speed quirk
Date: Mon, 29 Jan 2024 13:27:09 +0200 [thread overview]
Message-ID: <20240129112710.2852-2-ilpo.jarvinen@linux.intel.com> (raw)
In-Reply-To: <20240129112710.2852-1-ilpo.jarvinen@linux.intel.com>
While a device is runtime suspended along with its PCIe hierarchy, the
device could get disconnected. Because of the suspend, the device
disconnection cannot be detected until portdrv/hotplug have resumed. On
runtime resume, pcie_wait_for_link_delay() is called:
pci_pm_runtime_resume()
pci_pm_bridge_power_up_actions()
pci_bridge_wait_for_secondary_bus()
pcie_wait_for_link_delay()
Because the device is already disconnected, this results in cascading
failures:
1. pcie_wait_for_link_status() returns -ETIMEDOUT.
2. After the commit a89c82249c37 ("PCI: Work around PCIe link
training failures"), pcie_failed_link_retrain() spuriously detects
this failure as a Link Retraining failure and attempts the Target
Speed trick, which also fails.
3. pci_bridge_wait_for_secondary_bus() then calls pci_dev_wait() which
cannot succeed (but waits ~1 minute, delaying the resume).
The Target Speed trick (in step 2) is only used if LBMS bit (PCIe r6.1
sec 7.5.3.8) is set. For links that have been operational before
suspend, it is well possible that LBMS has been set at the bridge and
remains on. Thus, after resume, LBMS does not indicate the link needs
the Target Speed quirk. Clear LBMS on resume for bridges to avoid the
issue.
Fixes: a89c82249c37 ("PCI: Work around PCIe link training failures")
Reported-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
---
drivers/pci/pci-driver.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
index 51ec9e7e784f..05a114962df3 100644
--- a/drivers/pci/pci-driver.c
+++ b/drivers/pci/pci-driver.c
@@ -574,6 +574,12 @@ static void pci_pm_bridge_power_up_actions(struct pci_dev *pci_dev)
{
int ret;
+ /*
+ * Clear LBMS on resume to avoid spuriously triggering Target Speed
+ * quirk in pcie_failed_link_retrain().
+ */
+ pcie_capability_write_word(pci_dev, PCI_EXP_LNKSTA, PCI_EXP_LNKSTA_LBMS);
+
ret = pci_bridge_wait_for_secondary_bus(pci_dev, "resume");
if (ret) {
/*
--
2.39.2
next prev parent reply other threads:[~2024-01-29 11:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 11:27 [PATCH 0/2] PCI: Fix disconnect related issues Ilpo Järvinen
2024-01-29 11:27 ` Ilpo Järvinen [this message]
2024-01-29 18:43 ` [PATCH 1/2] PCI: Clear LBMS on resume to avoid Target Speed quirk Bjorn Helgaas
2024-01-30 11:53 ` Ilpo Järvinen
2024-01-30 16:41 ` Maciej W. Rozycki
2024-01-30 17:33 ` Ilpo Järvinen
2024-02-01 9:47 ` Ilpo Järvinen
2024-02-01 18:49 ` Maciej W. Rozycki
2024-02-02 15:27 ` Ilpo Järvinen
2024-02-07 12:33 ` Ilpo Järvinen
2024-08-09 13:25 ` Maciej W. Rozycki
2024-08-09 15:55 ` Ilpo Järvinen
2024-08-12 11:59 ` Maciej W. Rozycki
2024-02-12 17:56 ` Maciej W. Rozycki
2024-01-29 11:27 ` [PATCH 2/2] PCI: Do not wait for disconnected devices when resuming Ilpo Järvinen
2024-01-29 18:55 ` Bjorn Helgaas
2024-01-30 13:15 ` Ilpo Järvinen
2024-02-02 17:03 ` Ilpo Järvinen
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=20240129112710.2852-2-ilpo.jarvinen@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=mika.westerberg@linux.intel.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