From: Michael Riesch <michael.riesch@collabora.com>
To: Gerald Loacker <gerald.loacker@wolfvision.net>,
Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-phy@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/3] phy: rockchip: phy-rockchip-inno-csidphy: add clock lane phase tuning
Date: Fri, 10 Jul 2026 11:31:20 +0200 [thread overview]
Message-ID: <21e79fd6-6c72-481c-a7a1-18af94b9cb9a@collabora.com> (raw)
In-Reply-To: <20260630-feature-mipi-csi-dphy-4k60-v3-3-176792ab71fa@wolfvision.net>
Hi Gerald,
Thanks for your patch.
On 6/30/26 09:48, Gerald Loacker wrote:
> At high data rates like 4K60 (2500 Mbps), such as when using an
> LT6911GXD bridge chip on an RK3588 board, fixed default timing parameters
> can cause signal integrity issues and clock-data recovery failures.
> The driver currently lacks a mechanism to adjust the clock lane sampling
> phase to compensate for board-specific trace variations.
>
> Resolve this by parsing and applying the optional 'rockchip,clk-lane-phase'
> device tree property. This enables board-specific tuning of the clock
> lane sampling phase in ~40 ps steps (range 0-7) to optimize link
> stability. If the property is absent, the driver falls back to the
> hardware default.
>
> Signed-off-by: Gerald Loacker <gerald.loacker@wolfvision.net>
> ---
> drivers/phy/rockchip/phy-rockchip-inno-csidphy.c | 25 ++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/drivers/phy/rockchip/phy-rockchip-inno-csidphy.c b/drivers/phy/rockchip/phy-rockchip-inno-csidphy.c
> index 5281f8dea0ad3..3a15840e86cad 100644
> --- a/drivers/phy/rockchip/phy-rockchip-inno-csidphy.c
> +++ b/drivers/phy/rockchip/phy-rockchip-inno-csidphy.c
> @@ -69,6 +69,10 @@
> #define RK1808_CSIDPHY_CLK_CALIB_EN 0x168
> #define RK3568_CSIDPHY_CLK_CALIB_EN 0x168
>
> +#define CSIDPHY_LANE_CLK_3_PHASE 0x38
> +#define CSIDPHY_CLK_PHASE_MASK GENMASK(6, 4)
> +#define CSIDPHY_CLK_PHASE_DEFAULT 3
This default value definition is unused right now, but...
> +
> #define RESETS_MAX 2
>
> /*
> @@ -151,6 +155,7 @@ struct rockchip_inno_csidphy {
> const struct dphy_drv_data *drv_data;
> struct phy_configure_opts_mipi_dphy config;
> u8 hsfreq;
> + int clk_phase;
> };
>
> static inline void write_grf_reg(struct rockchip_inno_csidphy *priv,
> @@ -304,6 +309,13 @@ static int rockchip_inno_csidphy_power_on(struct phy *phy)
> rockchip_inno_csidphy_ths_settle(priv, priv->hsfreq,
> CSIDPHY_LANE_THS_SETTLE(i));
>
> + if (priv->clk_phase >= 0) {
...you can make sure that clk_phase has a valid value in any case (apply
default value defined above if DT does not define it or defines
something invalid) and write the register unconditionally.
> + val = readl(priv->phy_base + CSIDPHY_LANE_CLK_3_PHASE);
> + val &= ~CSIDPHY_CLK_PHASE_MASK;
> + val |= FIELD_PREP(CSIDPHY_CLK_PHASE_MASK, priv->clk_phase);
> + writel(val, priv->phy_base + CSIDPHY_LANE_CLK_3_PHASE);
> + }
> +
> write_grf_reg(priv, GRF_DPHY_CSIPHY_CLKLANE_EN, 0x1);
> write_grf_reg(priv, GRF_DPHY_CSIPHY_DATALANE_EN,
> GENMASK(priv->config.lanes - 1, 0));
> @@ -449,6 +461,7 @@ static int rockchip_inno_csidphy_probe(struct platform_device *pdev)
> struct device *dev = &pdev->dev;
> struct phy_provider *phy_provider;
> struct phy *phy;
> + u32 phase;
> int ret;
>
> priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL);
> @@ -464,6 +477,18 @@ static int rockchip_inno_csidphy_probe(struct platform_device *pdev)
> return -ENODEV;
> }
>
> + priv->clk_phase = -1;
> + if (device_property_read_u32(dev, "rockchip,clk-lane-phase",
> + &phase) == 0) {
> + if (phase >= BIT(3)) {
if (phase > 7)
> + dev_err(dev,
> + "rockchip,clk-lane-phase %u out of range [0,7]\n",
> + phase);
> + return -EINVAL;
Seems a bit harsh. What would you think about printing a warning and
applying the default value?
> + }
> + priv->clk_phase = phase;
> + }
Maybe
ret = device_property_read_u32(dev, "rockchip,clk-lane-phase",
&priv->clk_phase);
if (ret < 0 || priv->clk_phase > 7) {
dev_info(dev,
"found %s value for rockchip,clk-lane-phase,"
"assuming default value",
ret < 0 ? "no" : "invalid");
priv->clk_phase = CSIDPHY_CLK_PHASE_DEFAULT;
}
would do the trick too?
Best regards,
Michael
> +
> priv->grf = syscon_regmap_lookup_by_phandle(dev->of_node,
> "rockchip,grf");
> if (IS_ERR(priv->grf)) {
>
prev parent reply other threads:[~2026-07-10 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 7:48 [PATCH v3 0/3] phy: rockchip: inno-csidphy: fix 2500 Mbps support and add clock lane phase tuning Gerald Loacker
2026-06-30 7:48 ` [PATCH v3 1/3] phy: rockchip: phy-rockchip-inno-csidphy: fix rk1808 hsfreq table Gerald Loacker
2026-07-10 9:28 ` Michael Riesch
2026-06-30 7:48 ` [PATCH v3 2/3] dt-bindings: phy: rockchip-inno-csi-dphy: add rockchip,clk-lane-phase property Gerald Loacker
2026-06-30 19:25 ` Rob Herring (Arm)
2026-07-10 9:30 ` Michael Riesch
2026-06-30 7:48 ` [PATCH v3 3/3] phy: rockchip: phy-rockchip-inno-csidphy: add clock lane phase tuning Gerald Loacker
2026-07-10 9:31 ` Michael Riesch [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=21e79fd6-6c72-481c-a7a1-18af94b9cb9a@collabora.com \
--to=michael.riesch@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gerald.loacker@wolfvision.net \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--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