linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms+renesas@verge.net.au>
To: linux-renesas-soc@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	Magnus Damm <magnus.damm@gmail.com>,
	Biju Das <biju.das@bp.renesas.com>,
	Simon Horman <horms+renesas@verge.net.au>
Subject: [PATCH 11/12] ARM: dts: r8a7744: Add DU support
Date: Fri,  8 Feb 2019 12:14:12 +0100	[thread overview]
Message-ID: <5f152018d340d90c185ced8ef6230b7044ea5540.1549623128.git.horms+renesas@verge.net.au> (raw)
In-Reply-To: <cover.1549623128.git.horms+renesas@verge.net.au>

From: Biju Das <biju.das@bp.renesas.com>

Add du node to r8a7744 SoC DT. Boards that want to enable the DU
need to specify the output topology.

Signed-off-by: Biju Das <biju.das@bp.renesas.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
 arch/arm/boot/dts/r8a7744.dtsi | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/arch/arm/boot/dts/r8a7744.dtsi b/arch/arm/boot/dts/r8a7744.dtsi
index 8d25a0a0594a..83804aa042c6 100644
--- a/arch/arm/boot/dts/r8a7744.dtsi
+++ b/arch/arm/boot/dts/r8a7744.dtsi
@@ -1645,8 +1645,14 @@
 		};
 
 		du: display@feb00000 {
-			reg = <0 0xfeb00000 0 0x40000>,
-			      <0 0xfeb90000 0 0x1c>;
+			compatible = "renesas,du-r8a7744";
+			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>;
+			clock-names = "du.0", "du.1";
+			status = "disabled";
 
 			ports {
 				#address-cells = <1>;
@@ -1663,7 +1669,6 @@
 					};
 				};
 			};
-			/* placeholder */
 		};
 
 		prr: chipid@ff000044 {
-- 
2.11.0


  parent reply	other threads:[~2019-02-08 11:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 11:14 [GIT PULL] Renesas ARM Based SoC DT Updates for v5.1 Simon Horman
2019-02-08 11:14 ` [PATCH 01/12] ARM: dts: stout: Convert to new LVDS DT bindings Simon Horman
2019-02-08 11:14 ` [PATCH 02/12] ARM: dts: iwg23s-sbc: Enable RTC Simon Horman
2019-02-08 11:14 ` [PATCH 03/12] ARM: dts: r8a7744: Fix sorting of vsp and msiof nodes Simon Horman
2019-02-08 11:14 ` [PATCH 04/12] ARM: dts: r8a7743: Remove generic compatible string from iic3 Simon Horman
2019-02-08 11:14 ` [PATCH 05/12] ARM: dts: r8a7743: Remove aliases from SoC dtsi Simon Horman
2019-02-08 11:14 ` [PATCH 06/12] ARM: dts: r8a7743: Fix sorting of rwdt node Simon Horman
2019-02-08 11:14 ` [PATCH 07/12] ARM: dts: r8a7778: Add HSCIF0/1 support Simon Horman
2019-02-08 11:14 ` [PATCH 08/12] ARM: dts: r8a7779: Add HSCIF0/1 device nodes Simon Horman
2019-02-08 11:14 ` [PATCH 09/12] ARM: dts: r7s9210: Initial SoC device tree Simon Horman
2019-02-08 11:14 ` [PATCH 10/12] ARM: dts: r7s9210-rza2mevb: Add support for RZ/A2M EVB Simon Horman
2019-02-08 11:14 ` Simon Horman [this message]
2019-02-08 11:14 ` [PATCH 12/12] ARM: dts: r8a7744: Add LVDS support Simon Horman
2019-02-15 14:49 ` [GIT PULL] Renesas ARM Based SoC DT Updates for v5.1 Arnd Bergmann

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=5f152018d340d90c185ced8ef6230b7044ea5540.1549623128.git.horms+renesas@verge.net.au \
    --to=horms+renesas@verge.net.au \
    --cc=biju.das@bp.renesas.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.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).