Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
	"Simon Horman" <horms@verge.net.au>,
	linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 4/5] arm64: dts: renesas: r8a77970: add the LVDS instance
Date: Thu, 8 Feb 2018 19:05:53 +0300	[thread overview]
Message-ID: <af85dc17-e97d-bd40-6b46-376ae90123d7@cogentembedded.com> (raw)
In-Reply-To: <20180208154720.5766-5-niklas.soderlund+renesas@ragnatech.se>

Hello!

On 02/08/2018 06:47 PM, Niklas Söderlund wrote:

> Add the LVDS device to r8a77970.dtsi in a disabled state. Also connect
> the it to the LVDS output of the DU. While at it align the endpoint name
> of the du to du_out_lvds0 which is used in other Renesas DTS files to
> describe this link.
> 
> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> ---
>  arch/arm64/boot/dts/renesas/r8a77970.dtsi | 29 ++++++++++++++++++++++++++++-
>  1 file changed, 28 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm64/boot/dts/renesas/r8a77970.dtsi b/arch/arm64/boot/dts/renesas/r8a77970.dtsi
> index c6056635bd372ce3..9c65884cc384952d 100644
> --- a/arch/arm64/boot/dts/renesas/r8a77970.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a77970.dtsi
> @@ -653,7 +653,34 @@
>  
>  				port@1 {
>  					reg = <1>;
> -					du_out_lvds: endpoint {
> +					du_out_lvds0: endpoint {
> +						remote-endpoint = <&lvds0_in>;
> +					};
> +				};
> +			};
> +		};
> +
> +		lvds0: lvds@feb90000 {
> +			compatible = "renesas,r8a77970-lvds";
> +			reg = <0 0xfeb90000 0 0x14>;
> +			clocks = <&cpg CPG_MOD 727>;
> +			power-domains = <&sysc R8A77970_PD_ALWAYS_ON>;
> +			resets = <&cpg 727>;
> +			status = "disabled";
> +
> +			ports {
> +				#address-cells = <1>;
> +				#size-cells = <0>;
> +
> +				port@0 {
> +					reg = <0>;
> +					lvds0_in: endpoint {
> +						remote-endpoint = <&du_out_lvds0>;
> +					};
> +				};
> +				port@1 {
> +					reg = <1>;
> +					lvds0_out: endpoint {
>  					};
>  				};
>  			};


   That's basically my patch modulo the added "power-domains" and "resets" props, and the node/endpoint rename (of a dubious value, if you ask me ;-)).

MBSR, Sergei

  reply	other threads:[~2018-02-08 16:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 15:47 [PATCH v2 0/5] arm64: dts: renesas: r8a77970: enable HDMI output Niklas Söderlund
2018-02-08 15:47 ` [PATCH v2 1/5] arm64: dts: renesass: r8a77970: add FCPVD support Niklas Söderlund
2018-02-12 12:56   ` Kieran Bingham
2018-02-15 19:17   ` Simon Horman
2018-02-08 15:47 ` [PATCH v2 2/5] arm64: dts: renesass: r8a77970: add VSPD support Niklas Söderlund
2018-02-12 12:58   ` Kieran Bingham
2018-02-08 15:47 ` [PATCH v2 3/5] arm64: dts: renesas: r8a77970: add DU support Niklas Söderlund
2018-02-12 14:55   ` Kieran Bingham
2018-02-08 15:47 ` [PATCH v2 4/5] arm64: dts: renesas: r8a77970: add the LVDS instance Niklas Söderlund
2018-02-08 16:05   ` Sergei Shtylyov [this message]
2018-02-19 12:51     ` Simon Horman
2018-02-08 15:47 ` [PATCH v2 5/5] arm64: dts: renesas: eagle: add HDMI output using the ADV7511W Niklas Söderlund

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=af85dc17-e97d-bd40-6b46-376ae90123d7@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=devicetree@vger.kernel.org \
    --cc=horms@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    /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