From: Neil Armstrong <neil.armstrong@linaro.org>
To: Shawn Lin <shawn.lin@rock-chips.com>, Vinod Koul <vkoul@kernel.org>
Cc: Kishon Vijay Abraham I <kishon@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-phy@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v2 1/2] phy: rockchip: naneng-combphy: Fix PCIe L1ss support RK3528
Date: Tue, 18 Nov 2025 14:47:40 +0100 [thread overview]
Message-ID: <710f2b4a-b443-44cd-aec8-ce9a8630dfbc@linaro.org> (raw)
In-Reply-To: <1763459526-35004-1-git-send-email-shawn.lin@rock-chips.com>
On 11/18/25 10:52, Shawn Lin wrote:
> When PCIe link enters L1 PM substates, the PHY will turn off its
> PLL for power-saving. However, it turns off the PLL too fast which
> leads the PHY to be broken. According to the PHY document, we need
> to delay PLL turnoff time.
>
> Fixes: bbcca4fac873 ("phy: rockchip: naneng-combphy: Add RK3528 support")
> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
> ---
>
> Changes in v2:
> - add more commit message
>
> drivers/phy/rockchip/phy-rockchip-naneng-combphy.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c b/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
> index a3ef198..e303bec 100644
> --- a/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
> +++ b/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
> @@ -21,6 +21,9 @@
> #define REF_CLOCK_100MHz (100 * HZ_PER_MHZ)
>
> /* RK3528 COMBO PHY REG */
> +#define RK3528_PHYREG5 0x14
> +#define RK3528_PHYREG5_GATE_TX_PCK_SEL BIT(3)
> +#define RK3528_PHYREG5_GATE_TX_PCK_DLY_PLL_OFF BIT(3)
> #define RK3528_PHYREG6 0x18
> #define RK3528_PHYREG6_PLL_KVCO GENMASK(12, 10)
> #define RK3528_PHYREG6_PLL_KVCO_VALUE 0x2
> @@ -504,6 +507,10 @@ static int rk3528_combphy_cfg(struct rockchip_combphy_priv *priv)
> case REF_CLOCK_100MHz:
> rockchip_combphy_param_write(priv->phy_grf, &cfg->pipe_clk_100m, true);
> if (priv->type == PHY_TYPE_PCIE) {
> + /* Gate_tx_pck_sel length select for L1ss support */
> + rockchip_combphy_updatel(priv, RK3528_PHYREG5_GATE_TX_PCK_SEL,
> + RK3528_PHYREG5_GATE_TX_PCK_DLY_PLL_OFF, RK3528_PHYREG5);
> +
> /* PLL KVCO tuning fine */
> val = FIELD_PREP(RK3528_PHYREG6_PLL_KVCO, RK3528_PHYREG6_PLL_KVCO_VALUE);
> rockchip_combphy_updatel(priv, RK3528_PHYREG6_PLL_KVCO, val,
Thanks for updating, it's clearer now !
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-11-18 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 9:52 [PATCH v2 1/2] phy: rockchip: naneng-combphy: Fix PCIe L1ss support RK3528 Shawn Lin
2025-11-18 9:52 ` [PATCH v2 2/2] phy: rockchip: naneng-combphy: Fix PCIe L1ss support RK3562 Shawn Lin
2025-11-18 13:47 ` Neil Armstrong
2025-11-18 13:47 ` Neil Armstrong [this message]
2025-11-20 17:12 ` [PATCH v2 1/2] phy: rockchip: naneng-combphy: Fix PCIe L1ss support RK3528 Vinod Koul
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=710f2b4a-b443-44cd-aec8-ce9a8630dfbc@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=heiko@sntech.de \
--cc=kishon@kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=shawn.lin@rock-chips.com \
--cc=vkoul@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