devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrzej Hajda <andrzej.hajda@intel.com>
To: Jagan Teki <jagan@amarulasolutions.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Cc: <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-samsung-soc@vger.kernel.org>,
	<linux-amarula@amarulasolutions.com>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] arm64: dts: exynos: Link DSI panel at port@1 for TM2 board
Date: Tue, 11 Jan 2022 09:35:11 +0100	[thread overview]
Message-ID: <9912c743-8acb-c59a-760a-a9b79ed48784@intel.com> (raw)
In-Reply-To: <20220110152714.58220-1-jagan@amarulasolutions.com>

+CC: dri-devel

On 10.01.2022 16:27, Jagan Teki wrote:
> TM2 board DSI pipeline has input from MIC and output to
> s6e3ha2 panel.
>
> The existing pipeline has child nodes of ports, panel and
> MIC is remote-endpoint reference of port@0 of ports.
>
> Adding panel as another child node to DSI is unconventional
> as pipeline has ports child. However it can be true if MIC
> is added inside port node like this.
>
> dsi {
> 	compatible = "samsung,exynos5433-mipi-dsi";
> 	#address-cells = <1>;
> 	#size-cells = <0>;
>
> 	port {
> 		dsi_to_mic: endpoint {
> 			remote-endpoint = <&mic_to_dsi>;
> 		};
> 	};
>
> 	panel@0 {
> 		compatible = "samsung,s6e3hf2";
>                  reg = <0>;
>                  vdd3-supply = <&ldo27_reg>;
>                  vci-supply = <&ldo28_reg>;
>                  reset-gpios = <&gpg0 0 GPIO_ACTIVE_LOW>;
>                  enable-gpios = <&gpf1 5 GPIO_ACTIVE_HIGH>;
> 	};
> };
>
> The above pipeline is proper but it requires the DSI input MIC
> pipeline to update.
>
> This patch is trying to add panel at port@1 so-that the entire
> pipeline before to panel output is untouched.
>
> Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
>   arch/arm64/boot/dts/exynos/exynos5433-tm2.dts | 16 ++++++++++++++++
>   1 file changed, 16 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/exynos/exynos5433-tm2.dts b/arch/arm64/boot/dts/exynos/exynos5433-tm2.dts
> index aca01709fd29..e13210c8d7e0 100644
> --- a/arch/arm64/boot/dts/exynos/exynos5433-tm2.dts
> +++ b/arch/arm64/boot/dts/exynos/exynos5433-tm2.dts
> @@ -53,6 +53,16 @@ &cmu_disp {
>   };
>   
>   &dsi {
> +	ports {
> +		port@1 {
> +			reg = <1>;
> +
> +			dsi_out_panel: endpoint {
> +				remote-endpoint = <&dsi_in_panel>;
> +			};
> +		};
> +	};
> +
>   	panel@0 {
>   		compatible = "samsung,s6e3ha2";
>   		reg = <0>;
> @@ -60,6 +70,12 @@ panel@0 {
>   		vci-supply = <&ldo28_reg>;
>   		reset-gpios = <&gpg0 0 GPIO_ACTIVE_LOW>;
>   		enable-gpios = <&gpf1 5 GPIO_ACTIVE_HIGH>;
> +
> +		port {
> +			dsi_in_panel: endpoint {
> +				remote-endpoint = <&dsi_out_panel>;
> +			};
> +		};


As I already wrote in Exynos thread, DSI host has already parent-child 
relation with the panel - DSI host knows well who is connected to it. 
Adding another links between them is redundant and has no value added.

I have already answered in Exynos thread[1] how could you deal with the 
issue, you have.

[1]: 
https://lore.kernel.org/dri-devel/e541c52b-9751-933b-5eac-783dd0ed9056@intel.com/


Regards

Andrzej


>   	};
>   };
>   

  parent reply	other threads:[~2022-01-11  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 15:27 [PATCH 1/2] arm64: dts: exynos: Link DSI panel at port@1 for TM2 board Jagan Teki
2022-01-10 15:27 ` [PATCH 2/2] arm64: dts: exynos: Link DSI panel at port@1 for TM2E board Jagan Teki
2022-01-11  8:35 ` Andrzej Hajda [this message]
2022-01-11  9:33   ` [PATCH 1/2] arm64: dts: exynos: Link DSI panel at port@1 for TM2 board Jagan Teki

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=9912c743-8acb-c59a-760a-a9b79ed48784@intel.com \
    --to=andrzej.hajda@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jagan@amarulasolutions.com \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).