From: "Jian Yang (杨戬)" <Jian.Yang@mediatek.com>
To: "mani@kernel.org" <mani@kernel.org>
Cc: "linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"Chuanjia Liu (柳传嘉)" <Chuanjia.Liu@mediatek.com>,
"Yonglong Wu (吴永龙)" <Yonglong.Wu@mediatek.com>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"robh@kernel.org" <robh@kernel.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"kwilczynski@kernel.org" <kwilczynski@kernel.org>,
"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"Ryder Lee" <Ryder.Lee@mediatek.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH v1] PCI: mediatek-gen3: Align PERST# sequence with PCIe CEM specification
Date: Thu, 2 Apr 2026 08:44:16 +0000 [thread overview]
Message-ID: <9013d68ffdfff49c852f609e2e8b6f5e13741d22.camel@mediatek.com> (raw)
In-Reply-To: <x6nabkumov75khx4icgibrmd4o3oz5drm3cfthh6j2himsihla@echprgpjanoq>
Hi Mani,
On Wed, 2026-04-01 at 17:49 +0530, Manivannan Sadhasivam wrote:
> On Wed, Apr 01, 2026 at 11:16:42AM +0800, Jian Yang wrote:
> > 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:
> >
>
> You are fixing multiple issues in one patch, which is not acceptable.
>
> > 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#
> >
>
> This issue is separate and not related to the below two issues.
>
> > 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.
> >
>
> Adding 'shutdown()' callback should belong to a separate patch with
> its own
> motivation.
Thanks for your comments. I will send a new patch series.
>
> > 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);
>
> PERST# is asserted by setting the 'PCIE_PE_RSTB' bit. So if that
> controls the
> actual voltage transition of PERST# signal, will reading it back
> ensure that the
> transition has been completed without waiting for an arbitrary delay?
You're right. I believe this delay is unnecessary. I will remove it in
the next version.
>
> Nevertheless, this also belongs to a separate patch.
>
> - Mani
>
Best regards,
Jian Yang
prev parent reply other threads:[~2026-04-02 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 3:16 [PATCH v1] PCI: mediatek-gen3: Align PERST# sequence with PCIe CEM specification Jian Yang
2026-04-01 5:00 ` Chen-Yu Tsai
2026-04-01 12:19 ` Manivannan Sadhasivam
2026-04-02 8:44 ` Jian Yang (杨戬) [this message]
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=9013d68ffdfff49c852f609e2e8b6f5e13741d22.camel@mediatek.com \
--to=jian.yang@mediatek.com \
--cc=Chuanjia.Liu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Ryder.Lee@mediatek.com \
--cc=Yonglong.Wu@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bhelgaas@google.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 \
/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