linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Biju Das <biju.das@bp.renesas.com>
To: Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>
Cc: Biju Das <biju.das@bp.renesas.com>,
	Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Subject: [PATCH v2 4/5] ARM: dts: r8a7743: Remove LVDS encoder from du node
Date: Wed,  5 Dec 2018 09:06:54 +0000	[thread overview]
Message-ID: <1544000815-28069-5-git-send-email-biju.das@bp.renesas.com> (raw)
In-Reply-To: <1544000815-28069-1-git-send-email-biju.das@bp.renesas.com>

The internal LVDS encoder now has DT bindings separate from the DU.
So remove it from du node.

Fixes: c6a27fa41fab ("drm: rcar-du: Convert LVDS encoder code to bridge driver")

Signed-off-by: Biju Das <biju.das@bp.renesas.com>
---
V1-->V2
	* Removed LVDS encoder definition from DU node.
---
 arch/arm/boot/dts/r8a7743.dtsi | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/arch/arm/boot/dts/r8a7743.dtsi b/arch/arm/boot/dts/r8a7743.dtsi
index 3cc33f7..3ad1efc 100644
--- a/arch/arm/boot/dts/r8a7743.dtsi
+++ b/arch/arm/boot/dts/r8a7743.dtsi
@@ -1681,15 +1681,12 @@
 
 		du: display@feb00000 {
 			compatible = "renesas,du-r8a7743";
-			reg = <0 0xfeb00000 0 0x40000>,
-			      <0 0xfeb90000 0 0x1c>;
-			reg-names = "du", "lvds.0";
+			reg = <0 0xfeb00000 0 0x40000>;
 			interrupts = <GIC_SPI 256 IRQ_TYPE_LEVEL_HIGH>,
 				     <GIC_SPI 268 IRQ_TYPE_LEVEL_HIGH>;
 			clocks = <&cpg CPG_MOD 724>,
-				 <&cpg CPG_MOD 723>,
-				 <&cpg CPG_MOD 726>;
-			clock-names = "du.0", "du.1", "lvds.0";
+				 <&cpg CPG_MOD 723>;
+			clock-names = "du.0", "du.1";
 			status = "disabled";
 
 			ports {
-- 
2.7.4

  parent reply	other threads:[~2018-12-05  9:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05  9:06 [PATCH v2 0/5] Add more support to RZ/G1N Biju Das
2018-12-05  9:06 ` [PATCH v2 1/5] ARM: dts: iwg20d-q7-common: Move cmt/rwdt node out of RZ/G1M SOM Biju Das
2018-12-05 19:53   ` Simon Horman
2018-12-05  9:06 ` [PATCH v2 2/5] ARM: dts: r8a7744-iwg20m: Add SPI NOR support Biju Das
2018-12-05 19:53   ` Simon Horman
2018-12-05  9:06 ` [PATCH v2 3/5] ARM: dts: r8a7744: Add DU support Biju Das
2018-12-05 19:56   ` Simon Horman
2019-01-03 13:47   ` Geert Uytterhoeven
2019-01-03 14:35     ` Biju Das
2018-12-05  9:06 ` Biju Das [this message]
2019-01-03 13:47   ` [PATCH v2 4/5] ARM: dts: r8a7743: Remove LVDS encoder from du node Geert Uytterhoeven
2019-01-03 14:34     ` Biju Das
2019-01-04  9:05       ` Simon Horman
2019-01-04 10:02         ` Biju Das
2019-01-04 13:14           ` Simon Horman
2018-12-05  9:06 ` [PATCH v2 5/5] ARM: dts: r8a7744: Fix sorting of vsp and msiof nodes Biju Das
2018-12-10 12:31   ` Geert Uytterhoeven
2018-12-10 12:58     ` 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=1544000815-28069-5-git-send-email-biju.das@bp.renesas.com \
    --to=biju.das@bp.renesas.com \
    --cc=Chris.Paterson2@renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabrizio.castro@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=horms@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.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).