mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Riesch <michael.riesch@collabora.com>
To: Jason Yang <jason98166@gmail.com>, Vinod Koul <vkoul@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Guochun Huang <hero.huang@rock-chips.com>,
	Philipp Zabel <p.zabel@pengutronix.de>
Cc: Sebastian Reichel <sebastian.reichel@collabora.com>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 9/9] arm64: dts: rockchip: add the dcphy mipi csi-2 receiver nodes to rk3588
Date: Wed, 11 Nov 2026 13:32:40 +0100	[thread overview]
Message-ID: <cb2a2451-149f-44d5-aea3-e050673422e4@collabora.com> (raw)
In-Reply-To: <20261110-dcphy-rx-v1-v6-9-d681ba20b36a@gmail.com>

Hi Jason,

On 11/10/26 09:18, Jason Yang wrote:
> The MIPI0 and MIPI1 receiver units are connected to MIPI DCPHY0 and
> MIPI DCPHY1, whose receiver side is now supported. Add the two nodes and
> wire them to the VICAP ports.
> 
> The dsi nodes keep <&mipidcphy0 PHY_TYPE_DPHY>, the only value the
> binding had before the PHY receiver was added. PHY_TYPE_DPHY still
> selects the PHY transmitter in D-PHY mode. The csi nodes use the new
> PHY_DIRECTION_RX from the dt-bindings header. Neither phy node needs
> phy-type: the DSI host and the CSI-2 host both run the block in D-PHY
> mode, the default.
> 
> There is an ABI break if the dsi and csi nodes use the new cell values:
> an older kernel ignores phy-type and takes any cell value as the mode of
> the block. A DSI node with PHY_DIRECTION_TX then gets no display, and a
> CSI-2 node with PHY_DIRECTION_RX gets no camera.
> 
> To keep the ABI break small, the dsi nodes keep PHY_TYPE_DPHY, which
> older and newer kernels both accept. With the csi nodes disabled, the
> display therefore keeps working on either kernel.
> 
> The csi nodes have no older value to keep and have to use
> PHY_DIRECTION_RX. Enabling csi0 or csi1 therefore needs a PHY driver
> with receiver support. Since v7.0, a CSI-2 host driver probes the csi
> nodes. An older PHY driver then gives the CSI-2 host the PHY transmitter
> that drives the display. The camera gets no frames, and the display can
> stop working as well.

I think you can restrict the patch description to what the patch
actually does.

This patch modifies the device tree in a perfectly valid way as set out
in the DT bindings. Any breakage or disadvantage of the approach therein
should be discussed there.

> Signed-off-by: Jason Yang <jason98166@gmail.com>

But apart from that this LGTM!

Reviewed-by: Michael Riesch <michael.riesch@collabora.com>

Best regards,
Michael

> ---
>  arch/arm64/boot/dts/rockchip/rk3588-base.dtsi | 68 +++++++++++++++++++++++++++
>  1 file changed, 68 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-base.dtsi b/arch/arm64/boot/dts/rockchip/rk3588-base.dtsi
> index aa69fd3793fd..c7174c2f15c3 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3588-base.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3588-base.dtsi
> @@ -1516,10 +1516,18 @@ vicap_dvp: port@0 {
>  
>  			vicap_mipi0: port@1 {
>  				reg = <0x1>;
> +
> +				vicap_mipi0_input: endpoint {
> +					remote-endpoint = <&csi0_output>;
> +				};
>  			};
>  
>  			vicap_mipi1: port@2 {
>  				reg = <0x2>;
> +
> +				vicap_mipi1_input: endpoint {
> +					remote-endpoint = <&csi1_output>;
> +				};
>  			};
>  
>  			vicap_mipi2: port@3 {
> @@ -1568,6 +1576,66 @@ vicap_mmu: iommu@fdce0800 {
>  		status = "disabled";
>  	};
>  
> +	csi0: csi@fdd10000 {
> +		compatible = "rockchip,rk3588-mipi-csi2", "rockchip,rk3568-mipi-csi2";
> +		reg = <0x0 0xfdd10000 0x0 0x10000>;
> +		interrupts = <GIC_SPI 143 IRQ_TYPE_LEVEL_HIGH 0>,
> +			     <GIC_SPI 144 IRQ_TYPE_LEVEL_HIGH 0>;
> +		interrupt-names = "err1", "err2";
> +		clocks = <&cru PCLK_CSI_HOST_0>;
> +		phys = <&mipidcphy0 PHY_DIRECTION_RX>;
> +		power-domains = <&power RK3588_PD_VI>;
> +		resets = <&cru SRST_P_CSI_HOST_0>;
> +		status = "disabled";
> +
> +		ports {
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +
> +			csi0_in: port@0 {
> +				reg = <0>;
> +			};
> +
> +			csi0_out: port@1 {
> +				reg = <1>;
> +
> +				csi0_output: endpoint {
> +					remote-endpoint = <&vicap_mipi0_input>;
> +				};
> +			};
> +		};
> +	};
> +
> +	csi1: csi@fdd20000 {
> +		compatible = "rockchip,rk3588-mipi-csi2", "rockchip,rk3568-mipi-csi2";
> +		reg = <0x0 0xfdd20000 0x0 0x10000>;
> +		interrupts = <GIC_SPI 145 IRQ_TYPE_LEVEL_HIGH 0>,
> +			     <GIC_SPI 146 IRQ_TYPE_LEVEL_HIGH 0>;
> +		interrupt-names = "err1", "err2";
> +		clocks = <&cru PCLK_CSI_HOST_1>;
> +		phys = <&mipidcphy1 PHY_DIRECTION_RX>;
> +		power-domains = <&power RK3588_PD_VI>;
> +		resets = <&cru SRST_P_CSI_HOST_1>;
> +		status = "disabled";
> +
> +		ports {
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +
> +			csi1_in: port@0 {
> +				reg = <0>;
> +			};
> +
> +			csi1_out: port@1 {
> +				reg = <1>;
> +
> +				csi1_output: endpoint {
> +					remote-endpoint = <&vicap_mipi1_input>;
> +				};
> +			};
> +		};
> +	};
> +
>  	csi2: csi@fdd30000 {
>  		compatible = "rockchip,rk3588-mipi-csi2", "rockchip,rk3568-mipi-csi2";
>  		reg = <0x0 0xfdd30000 0x0 0x10000>;
> 


      reply	other threads:[~2026-11-11 12:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10  8:18 [PATCH v6 0/9] phy: rockchip-samsung-dcphy: Add the MIPI D-PHY receiver Jason Yang
2026-11-10  8:18 ` [PATCH v6 1/9] dt-bindings: phy: Add PHY_DIRECTION_TX/RX definitions Jason Yang
2026-11-11 10:29   ` Michael Riesch
2026-11-10  8:18 ` [PATCH v6 2/9] dt-bindings: phy: rockchip,rk3588-mipi-dcphy: Select TX or RX, add phy-type Jason Yang
2026-11-10 18:02   ` Rob Herring (Arm)
2026-11-11 10:33   ` Michael Riesch
2026-11-10  8:18 ` [PATCH v6 3/9] phy: rockchip-samsung-dcphy: Unwind power-on on PLL lock failure Jason Yang
2026-11-11 13:02   ` Michael Riesch
2026-11-10  8:18 ` [PATCH v6 4/9] phy: rockchip-samsung-dcphy: Always write the rate-dependent registers Jason Yang
2026-11-11 13:05   ` Michael Riesch
2026-11-10  8:18 ` [PATCH v6 5/9] phy: rockchip-samsung-dcphy: Move block-level setup to runtime resume Jason Yang
2026-11-11 13:14   ` Michael Riesch
2026-11-10  8:18 ` [PATCH v6 6/9] phy: rockchip-samsung-dcphy: Name the transmitter helpers and ops Jason Yang
2026-11-10  8:18 ` [PATCH v6 7/9] phy: rockchip-samsung-dcphy: Support the new phy-type and direction binding Jason Yang
2026-11-10  8:18 ` [PATCH v6 8/9] phy: rockchip-samsung-dcphy: Add MIPI D-PHY receiver support Jason Yang
2026-11-10  8:18 ` [PATCH v6 9/9] arm64: dts: rockchip: add the dcphy mipi csi-2 receiver nodes to rk3588 Jason Yang
2026-11-11 12:32   ` 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=cb2a2451-149f-44d5-aea3-e050673422e4@collabora.com \
    --to=michael.riesch@collabora.com \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=hero.huang@rock-chips.com \
    --cc=jason98166@gmail.com \
    --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=mani@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=sebastian.reichel@collabora.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

all inboxes | Powered by JetHome®