From: Kevin Xie <kevin.xie@starfivetech.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<mason.huo@starfivetech.com>, <leyfoon.tan@starfivetech.com>,
<minda.chen@starfivetech.com>
Subject: [PATCH v1] PCI: Add PCIE_CONFIG_REQUEST_WAIT_MS waiting time value
Date: Fri, 24 Nov 2023 09:45:08 +0800 [thread overview]
Message-ID: <20231124014508.43358-1-kevin.xie@starfivetech.com> (raw)
Add the PCIE_CONFIG_REQUEST_WAIT_MS marco to define the minimum waiting
time between sending the first configuration request to the device and
exit from a conventional reset (or after link training completes).
As described in the conventional reset rules of PCI specifications,
there are two different use cases of the value:
- With a downstream port that supports link speeds <= 5.0 GT/s,
the waiting is following exit from a conventional reset.
- With a downstream port that supports link speeds > 5.0 GT/s,
the waiting is after link training completes.
Signed-off-by: Kevin Xie <kevin.xie@starfivetech.com>
Reviewed-by: Mason Huo <mason.huo@starfivetech.com>
---
drivers/pci/pci.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
index 5ecbcf041179..4ca8766e546e 100644
--- a/drivers/pci/pci.h
+++ b/drivers/pci/pci.h
@@ -22,6 +22,13 @@
*/
#define PCIE_PME_TO_L2_TIMEOUT_US 10000
+/*
+ * PCIe r6.0, sec 6.6.1, <Conventional Reset>
+ * Requires a minimum waiting of 100ms before sending a configuration
+ * request to the device.
+ */
+#define PCIE_CONFIG_REQUEST_WAIT_MS 100
+
extern const unsigned char pcie_link_speed[];
extern bool pci_early_dump;
--
2.25.1
next reply other threads:[~2023-11-24 1:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 1:45 Kevin Xie [this message]
2023-11-29 23:21 ` [PATCH v1] PCI: Add PCIE_CONFIG_REQUEST_WAIT_MS waiting time value Bjorn Helgaas
2023-11-30 10:03 ` Kevin Xie
2023-11-30 18:35 ` Bjorn Helgaas
2023-12-01 1:41 ` Kevin Xie
2023-11-29 23:22 ` Bjorn Helgaas
2023-11-30 11:13 ` Kevin Xie
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=20231124014508.43358-1-kevin.xie@starfivetech.com \
--to=kevin.xie@starfivetech.com \
--cc=bhelgaas@google.com \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mason.huo@starfivetech.com \
--cc=minda.chen@starfivetech.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