From: Mario Limonciello <mario.limonciello@amd.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:USB XHCI DRIVER" <linux-usb@vger.kernel.org>,
Daniel Drake <drake@endlessos.org>, Gary Li <Gary.Li@amd.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"Mario Limonciello" <mario.limonciello@amd.com>
Subject: [PATCH 2/4] PCI: Verify functions currently in D3cold have entered D0
Date: Thu, 13 Jun 2024 00:42:02 -0500 [thread overview]
Message-ID: <20240613054204.5850-3-mario.limonciello@amd.com> (raw)
In-Reply-To: <20240613054204.5850-1-mario.limonciello@amd.com>
It is reported that USB4 routers and downstream devices may behave
incorrectly if a dock cable is plugged in at approximately the time that
the autosuspend_delay is configured. In this situation the device has
attempted to enter D3cold, but didn't finish D3cold entry when the PCI
core tried to transition it back to D0.
Empirically measuring this situation an "aborted" D3cold exit takes
~60ms and a "normal" D3cold exit takes ~10ms.
The PCI-PM 1.2 spec specifies that the restore time for functions
in D3cold is either 'Full context restore or boot latency'.
As PCIe r6.0 sec 5.8 specifies that the device will have gone
through a conventional reset it may take some time for the
device to be ready.
Wait up to 1 sec as specified in PCIe r6.0 sec 6.6.1 for a device
in D3cold to return to D0.
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
---
drivers/pci/pci.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index 41961e28a86c..a6ed85dd8d92 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -1387,6 +1387,17 @@ int pci_power_up(struct pci_dev *dev)
else if (state == PCI_D2)
udelay(PCI_PM_D2_DELAY);
+ /*
+ * D3cold -> D0 will have gone through a conventional reset and may need
+ * time to be ready.
+ */
+ if (dev->current_state == PCI_D3cold) {
+ int ret;
+
+ ret = pci_dev_wait(dev, "D3cold->D0", PCI_RESET_WAIT);
+ if (ret)
+ return ret;
+ }
end:
dev->current_state = PCI_D0;
if (need_restore)
--
2.43.0
next prev parent reply other threads:[~2024-06-13 5:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 5:42 [PATCH 0/4] Verify devices transition from D3cold to D0 Mario Limonciello
2024-06-13 5:42 ` [PATCH 1/4] PCI: Check PCI_PM_CTRL in pci_dev_wait() Mario Limonciello
2024-06-19 18:33 ` Markus Elfring
2024-06-19 18:44 ` Mario Limonciello
2024-06-13 5:42 ` Mario Limonciello [this message]
2024-06-19 18:45 ` [PATCH 2/4] PCI: Verify functions currently in D3cold have entered D0 Markus Elfring
2024-06-19 18:46 ` Mario Limonciello
2024-06-13 5:42 ` [PATCH 3/4] PCI: Allow Ryzen XHCI controllers into D3cold and drop delays Mario Limonciello
2024-06-13 5:42 ` [PATCH 4/4] PCI: Drop Radeon quirk for Macbook Pro 8.2 Mario Limonciello
2024-06-18 13:14 ` [PATCH 0/4] Verify devices transition from D3cold to D0 Mika Westerberg
2024-06-18 16:56 ` Mario Limonciello
2024-06-19 5:29 ` Mika Westerberg
2024-06-19 18:50 ` Mario Limonciello
2024-06-25 15:43 ` Mario Limonciello
2024-06-26 7:53 ` Mika Westerberg
2024-07-09 3:07 ` Mario Limonciello
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=20240613054204.5850-3-mario.limonciello@amd.com \
--to=mario.limonciello@amd.com \
--cc=Gary.Li@amd.com \
--cc=bhelgaas@google.com \
--cc=drake@endlessos.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--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