From: Jian Yang <jian.yang@mediatek.com>
To: "Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Ryder Lee" <ryder.lee@mediatek.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>
Cc: <linux-pci@vger.kernel.org>, <linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
<jian.yang@mediatek.com>, <chuanjia.liu@mediatek.com>,
<yonglong.wu@mediatek.com>
Subject: [PATCH v1] PCI: mediatek-gen3: Align PERST# sequence with PCIe CEM specification
Date: Wed, 1 Apr 2026 11:16:42 +0800 [thread overview]
Message-ID: <20260401031917.9108-1-jian.yang@mediatek.com> (raw)
Fix the control sequence of PERST# during system bootup/shutdown to
meet the requirement from PCIe CEM specification. There are two major
changes in this patch:
1. Some of MediaTek's chip will stop generating REFCLK if the
PCIE_PHY_RSTB signal of PCIe controller is asserted. We have to
adjust the startup sequence as follows to ensure that PERST# will be
de-asserted after the REFCLK is stable:
Assert PHY reset and PERST# -> delay 10ms -> De-assert PHY reset ->
delay 100ms -> De-assert PERST#
2. Add 'shutdown' callback to control the timing of PERST# and power
during the system shutdown phase, ensuring that PERST# is active
before the power on connector is removed.
Signed-off-by: Jian Yang <jian.yang@mediatek.com>
---
drivers/pci/controller/pcie-mediatek-gen3.c | 39 +++++++++++++++++++--
1 file changed, 36 insertions(+), 3 deletions(-)
diff --git a/drivers/pci/controller/pcie-mediatek-gen3.c b/drivers/pci/controller/pcie-mediatek-gen3.c
index a94fdbaf47fe..66d177918565 100644
--- a/drivers/pci/controller/pcie-mediatek-gen3.c
+++ b/drivers/pci/controller/pcie-mediatek-gen3.c
@@ -62,6 +62,7 @@
#define PCIE_PHY_RSTB BIT(1)
#define PCIE_BRG_RSTB BIT(2)
#define PCIE_PE_RSTB BIT(3)
+#define PCIE_BRG_RST_RDY_MS 10
#define PCIE_LTSSM_STATUS_REG 0x150
#define PCIE_LTSSM_STATE_MASK GENMASK(28, 24)
@@ -133,6 +134,7 @@
#define MAX_NUM_PHY_RESETS 3
#define PCIE_MTK_RESET_TIME_US 10
+#define PCIE_MTK_PDN_PERST_TIME_MS 5
/* Time in ms needed to complete PCIe reset on EN7581 SoC */
#define PCIE_EN7581_RESET_TIME_MS 100
@@ -430,6 +432,21 @@ static int mtk_pcie_devices_power_up(struct mtk_gen3_pcie *pcie)
return err;
}
+ /*
+ * Some of MediaTek's chips won't output REFCLK when PCIE_PHY_RSTB is
+ * asserted, we have to de-assert MAC & PHY & BRG reset signals first
+ * to allow the REFCLK to be stable. While PCIE_BRG_RSTB is asserted,
+ * there is a short period during which the PCIe internal register
+ * cannot be accessed, so we need to wait 10ms here.
+ */
+ msleep(PCIE_BRG_RST_RDY_MS);
+
+ if (!(pcie->soc->flags & SKIP_PCIE_RSTB)) {
+ /* De-assert MAC, PHY and BRG reset signals */
+ val &= ~(PCIE_MAC_RSTB | PCIE_PHY_RSTB | PCIE_BRG_RSTB);
+ writel_relaxed(val, pcie->base + PCIE_RST_CTRL_REG);
+ }
+
/*
* Described in PCIe CEM specification revision 6.0.
*
@@ -439,9 +456,8 @@ static int mtk_pcie_devices_power_up(struct mtk_gen3_pcie *pcie)
msleep(PCIE_T_PVPERL_MS);
if (!(pcie->soc->flags & SKIP_PCIE_RSTB)) {
- /* De-assert reset signals */
- val &= ~(PCIE_MAC_RSTB | PCIE_PHY_RSTB | PCIE_BRG_RSTB |
- PCIE_PE_RSTB);
+ /* De-assert PERST# signal */
+ val &= ~PCIE_PE_RSTB;
writel_relaxed(val, pcie->base + PCIE_RST_CTRL_REG);
}
@@ -459,6 +475,14 @@ static void mtk_pcie_devices_power_down(struct mtk_gen3_pcie *pcie)
writel_relaxed(val, pcie->base + PCIE_RST_CTRL_REG);
}
+ /*
+ * Described in PCIe CEM specification revision 6.0.
+ *
+ * The PERST# gose active before the power on the connector is removed.
+ * Wait a while to ensure the voltage transition of PERST# is completed.
+ */
+ msleep(PCIE_MTK_PDN_PERST_TIME_MS);
+
pci_pwrctrl_power_off_devices(pcie->dev);
}
@@ -1266,6 +1290,14 @@ static void mtk_pcie_remove(struct platform_device *pdev)
mtk_pcie_irq_teardown(pcie);
}
+static void mtk_pcie_shutdown(struct platform_device *pdev)
+{
+ struct mtk_gen3_pcie *pcie = platform_get_drvdata(pdev);
+
+ mtk_pcie_devices_power_down(pcie);
+ mtk_pcie_power_down(pcie);
+}
+
static void mtk_pcie_irq_save(struct mtk_gen3_pcie *pcie)
{
int i;
@@ -1404,6 +1436,7 @@ MODULE_DEVICE_TABLE(of, mtk_pcie_of_match);
static struct platform_driver mtk_pcie_driver = {
.probe = mtk_pcie_probe,
.remove = mtk_pcie_remove,
+ .shutdown = mtk_pcie_shutdown,
.driver = {
.name = "mtk-pcie-gen3",
.of_match_table = mtk_pcie_of_match,
--
2.45.2
next reply other threads:[~2026-04-01 3:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 3:16 Jian Yang [this message]
2026-04-01 5:00 ` [PATCH v1] PCI: mediatek-gen3: Align PERST# sequence with PCIe CEM specification Chen-Yu Tsai
2026-04-01 12:19 ` Manivannan Sadhasivam
2026-04-02 8:44 ` Jian Yang (杨戬)
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=20260401031917.9108-1-jian.yang@mediatek.com \
--to=jian.yang@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bhelgaas@google.com \
--cc=chuanjia.liu@mediatek.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=yonglong.wu@mediatek.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