Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: krzk@kernel.org (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: exynos: Add the OF graph between fimd and dsi
Date: Fri, 9 Jun 2017 09:27:54 +0200	[thread overview]
Message-ID: <20170609072754.GB4018@kozik-book> (raw)
In-Reply-To: <1496977173-20550-1-git-send-email-hoegeun.kwon@samsung.com>

On Fri, Jun 09, 2017 at 11:59:33AM +0900, Hoegeun Kwon wrote:
> It should be connected to OF graph between fimd and dsi.
> Add the OF graph between fimd and dsi.

I need more explanation why this is needed. What happens without this?
What issue is fixed here?

What about Exynos5250 and Exynos5420? I think we do not have a board in
mainline using FIMD but maybe this should be added just for correct
hardware description?


Best regards,
Krzysztof

> 
> Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>
> ---
>  arch/arm/boot/dts/exynos3250.dtsi | 26 ++++++++++++++++++++++++++
>  arch/arm/boot/dts/exynos4.dtsi    | 26 ++++++++++++++++++++++++++
>  2 files changed, 52 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/exynos3250.dtsi b/arch/arm/boot/dts/exynos3250.dtsi
> index 590ee44..22d523f 100644
> --- a/arch/arm/boot/dts/exynos3250.dtsi
> +++ b/arch/arm/boot/dts/exynos3250.dtsi
> @@ -311,6 +311,19 @@
>  			iommus = <&sysmmu_fimd0>;
>  			samsung,sysreg = <&sys_reg>;
>  			status = "disabled";
> +
> +			ports {
> +				#address-cells = <1>;
> +				#size-cells = <0>;
> +
> +				port at 0 {
> +					reg = <0>;
> +					fimd_to_dsi: endpoint {
> +						remote-endpoint =
> +							<&dsi_to_fimd>;
> +					};
> +				};
> +			};
>  		};
>  
>  		dsi_0: dsi at 11C80000 {
> @@ -326,6 +339,19 @@
>  			#address-cells = <1>;
>  			#size-cells = <0>;
>  			status = "disabled";
> +
> +			ports {
> +				#address-cells = <1>;
> +				#size-cells = <0>;
> +
> +				port at 0 {
> +					reg = <0>;
> +					dsi_to_fimd: endpoint {
> +						remote-endpoint =
> +							<&fimd_to_dsi>;
> +					};
> +				};
> +			};
>  		};
>  
>  		sysmmu_fimd0: sysmmu at 11E20000 {
> diff --git a/arch/arm/boot/dts/exynos4.dtsi b/arch/arm/boot/dts/exynos4.dtsi
> index 497a947..773d392 100644
> --- a/arch/arm/boot/dts/exynos4.dtsi
> +++ b/arch/arm/boot/dts/exynos4.dtsi
> @@ -193,6 +193,19 @@
>  		status = "disabled";
>  		#address-cells = <1>;
>  		#size-cells = <0>;
> +
> +		ports {
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +
> +			port at 0 {
> +				reg = <0>;
> +				dsi_to_fimd: endpoint {
> +					remote-endpoint =
> +						<&fimd_to_dsi>;
> +				};
> +			};
> +		};
>  	};
>  
>  	camera {
> @@ -715,6 +728,19 @@
>  		iommus = <&sysmmu_fimd0>;
>  		samsung,sysreg = <&sys_reg>;
>  		status = "disabled";
> +
> +		ports {
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +
> +			port at 0 {
> +				reg = <0>;
> +				fimd_to_dsi: endpoint {
> +					remote-endpoint =
> +						<&dsi_to_fimd>;
> +				};
> +			};
> +		};
>  	};
>  
>  	tmu: tmu at 100C0000 {
> -- 
> 1.9.1
> 

  reply	other threads:[~2017-06-09  7:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170609025951epcas1p19f5ca8c241b8b79068a84eb239ed46ed@epcas1p1.samsung.com>
2017-06-09  2:59 ` [PATCH] ARM: dts: exynos: Add the OF graph between fimd and dsi Hoegeun Kwon
2017-06-09  7:27   ` Krzysztof Kozlowski [this message]
2017-06-09  8:26     ` Hoegeun Kwon

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=20170609072754.GB4018@kozik-book \
    --to=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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