From: "Heiko Stübner" <heiko@sntech.de>
To: u-boot@lists.denx.de
Cc: Tom Rini <trini@konsulko.com>, Lukasz Majewski <lukma@denx.de>,
David Lechner <dlechner@baylibre.com>,
Julien Stephan <jstephan@baylibre.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Peng Fan <peng.fan@nxp.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
Philip Molloy <philip.molloy@analog.com>,
Sean Anderson <sean.anderson@linux.dev>,
Richard Genoud <richard.genoud@bootlin.com>,
Simon Glass <sjg@chromium.org>,
Peter Korsgaard <peter@korsgaard.com>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kever Yang <kever.yang@rock-chips.com>,
Daniele Briguglio <hello@superkali.me>,
Jonas Karlman <jonas@kwiboo.se>,
Daniele Briguglio <hello@superkali.me>
Subject: Re: [PATCH v3 2/4] pci: pcie_dw_rockchip: enable clocks before PHY init
Date: Tue, 09 Jun 2026 20:50:26 +0200 [thread overview]
Message-ID: <3345243.5fSG56mABF@diego> (raw)
In-Reply-To: <20260520-rock-5-itx-pcie-refclk-dtsi-v3-2-58f2cea72030@superkali.me>
Am Mittwoch, 20. Mai 2026, 08:05:28 Mitteleuropäische Sommerzeit schrieb Daniele Briguglio:
> rockchip_pcie_init_port() calls generic_phy_init() and
> generic_phy_power_on() before clk_enable_bulk(), so the PCIe PHY
> tries to lock its PLL while the external reference clock can still
> be off. Where the refclk is generated by an external oscillator
> gated by a regulator that is not marked regulator-always-on (e.g.
> the PI6C clock generator on radxa rock-3b modelled with the
> gated-fixed-clock binding), this results in a PHY lock timeout:
>
> rockchip_pcie3phy phy@fe8c0000: lock failed 0x6890000
> rockchip_pcie3phy phy@fe8c0000: PHY: Failed to init phy@fe8c0000: -110.
> pcie_dw_rockchip pcie@fe280000: failed to init phy (ret=-110)
>
> Move clk_enable_bulk() ahead of generic_phy_init() so that any
> clock-frequency consumer (including external gated refclks) is
> powered up before the PHY PLL attempts to lock.
>
> Reported-by: Jonas Karlman <jonas@kwiboo.se>
> Signed-off-by: Daniele Briguglio <hello@superkali.me>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Tested-by: Heiko Stuebner <heiko@sntech.de> # rock-5-itx
next prev parent reply other threads:[~2026-06-09 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 6:05 [PATCH v3 0/4] rockchip: PCIe gated reference clock support Daniele Briguglio
2026-05-20 6:05 ` [PATCH v3 1/4] clk: add gated-fixed-clock driver Daniele Briguglio
2026-06-09 18:49 ` Heiko Stübner
2026-05-20 6:05 ` [PATCH v3 2/4] pci: pcie_dw_rockchip: enable clocks before PHY init Daniele Briguglio
2026-06-09 18:50 ` Heiko Stübner [this message]
2026-05-20 6:05 ` [PATCH v3 3/4] pci: pcie_dw_rockchip: drop clk_release_bulk calls Daniele Briguglio
2026-06-09 19:04 ` Heiko Stübner
2026-06-09 20:06 ` Daniele Briguglio
2026-05-20 6:05 ` [PATCH v3 4/4] pci: pcie_dw_rockchip: imply CLK_GATED_FIXED and switch PHY to imply Daniele Briguglio
2026-06-09 19:04 ` Heiko Stübner
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=3345243.5fSG56mABF@diego \
--to=heiko@sntech.de \
--cc=dlechner@baylibre.com \
--cc=hello@superkali.me \
--cc=jonas@kwiboo.se \
--cc=jstephan@baylibre.com \
--cc=kever.yang@rock-chips.com \
--cc=lukma@denx.de \
--cc=peng.fan@nxp.com \
--cc=peter@korsgaard.com \
--cc=philip.molloy@analog.com \
--cc=philipp.tomsich@vrull.eu \
--cc=quentin.schulz@cherry.de \
--cc=richard.genoud@bootlin.com \
--cc=sean.anderson@linux.dev \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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