From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>,
Rob Herring <robh+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Magnus Damm <magnus.damm@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v2 4/5] arm64: dts: renesas: r8a77970: add LVDS support
Date: Tue, 27 Feb 2018 23:11:28 +0300 [thread overview]
Message-ID: <04a6d33c-b1fc-c20a-2979-1174e9c3f4b0@cogentembedded.com> (raw)
In-Reply-To: <23a6ac28-134b-b5dd-69a7-910774c4b8c1@cogentembedded.com>
Define the generic R8A77970 part of the LVDS device node.
Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
---
Changes in version 2:
- resolved rejects and updated atop of the DU support patch;
- changed the LVDS node's label/name;
- renamed the input/output endpoints' labels;
- added the "power-domains" and "resets" properties.
arch/arm64/boot/dts/renesas/r8a77970.dtsi | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
Index: renesas/arch/arm64/boot/dts/renesas/r8a77970.dtsi
===================================================================
--- renesas.orig/arch/arm64/boot/dts/renesas/r8a77970.dtsi
+++ renesas/arch/arm64/boot/dts/renesas/r8a77970.dtsi
@@ -655,6 +655,34 @@
port@1 {
reg = <1>;
du_out_lvds0: endpoint {
+ remote-endpoint = <&lvds0_in>;
+ };
+ };
+ };
+ };
+
+ lvds0: lvds-encoder@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 {
};
};
};
next prev parent reply other threads:[~2018-02-27 20:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 20:06 [PATCH v2 0/5] Add R8A77970/V3MSK LVDS/HDMI support Sergei Shtylyov
2018-02-27 20:08 ` [PATCH v2 1/5] arm64: dts: renesas: r8a77970: add FCPVD support Sergei Shtylyov
2018-02-27 20:09 ` [PATCH v2 2/5] arm64: dts: renesas: r8a77970: add VSPD support Sergei Shtylyov
2018-02-27 20:10 ` [PATCH v2 3/5] arm64: dts: renesas: r8a77970: add DU support Sergei Shtylyov
2018-02-27 20:11 ` Sergei Shtylyov [this message]
2018-02-27 20:12 ` [PATCH v2 5/5] arm64: dts: renesas: v3msk: add DU/LVDS/HDMI support Sergei Shtylyov
2018-02-27 20:23 ` [PATCH v2 0/5] Add R8A77970/V3MSK LVDS/HDMI support Sergei Shtylyov
2018-02-28 13:27 ` Simon Horman
2018-02-28 17:57 ` Sergei Shtylyov
2018-03-01 9:54 ` Simon Horman
2018-03-01 10:20 ` Sergei Shtylyov
2018-03-01 15:28 ` Sergei Shtylyov
2018-03-02 10:21 ` Simon Horman
2018-03-02 10:29 ` Sergei Shtylyov
2018-04-23 20:45 ` [PATCH v3] arm64: dts: renesas: v3msk: add DU/LVDS/HDMI support Sergei Shtylyov
2018-05-01 6:00 ` Simon Horman
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=04a6d33c-b1fc-c20a-2979-1174e9c3f4b0@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
/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).