From: Magnus Damm <magnus.damm@gmail.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH/RFC 03/06] arm64: dts: renesas: r8a7796: One IMP-X5 device for R-Car M3-W
Date: Mon, 21 Jan 2019 21:17:11 +0900 [thread overview]
Message-ID: <154807303153.2406.5961455669905578679.sendpatchset@octo> (raw)
In-Reply-To: <154807300302.2406.14245640502137089757.sendpatchset@octo>
From: Magnus Damm <damm+renesas@opensource.se>
Add an IMP-X5 device node to the r8a7796 device tree source.
Not for upstream merge.
Not-Yet-Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---
arch/arm64/boot/dts/renesas/r8a7796.dtsi | 9 +++++++++
1 file changed, 9 insertions(+)
--- 0003/arch/arm64/boot/dts/renesas/r8a7796.dtsi
+++ work/arch/arm64/boot/dts/renesas/r8a7796.dtsi 2019-01-21 19:38:59.092820475 +0900
@@ -2791,6 +2791,15 @@
};
};
+ imp-x5@ff900000 {
+ compatible = "renesas,imp-x5";
+ reg = <0 0xff900000 0 0x300000>;
+ interrupts = <GIC_SPI 439 IRQ_TYPE_LEVEL_HIGH>;
+ clocks = <&cpg CPG_MOD 824>;
+ power-domains = <&sysc R8A7796_PD_A3IR>;
+ resets = <&cpg 824>;
+ };
+
prr: chipid@fff00044 {
compatible = "renesas,prr";
reg = <0 0xfff00044 0 4>;
next prev parent reply other threads:[~2019-01-21 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 12:16 [PATCH/RFC 00/06] R-Car Gen3 IMP-X5 prototype code Magnus Damm
2019-01-21 12:16 ` [PATCH/RFC 01/06] Prototype code for IMP-X5 Magnus Damm
2019-01-21 12:17 ` [PATCH/RFC 02/06] arm64: dts: renesas: r8a7795: One IMP-X5 device for R-Car H3 Magnus Damm
2019-01-21 12:17 ` Magnus Damm [this message]
2019-01-21 12:17 ` [PATCH/RFC 04/06] arm64: dts: renesas: r8a77965: One IMP-X5 device for R-Car M3-N Magnus Damm
2019-01-21 12:17 ` [PATCH/RFC 05/06] arm64: dts: renesas: r8a77970: One IMP-X5 device for R-Car V3M Magnus Damm
2019-01-21 12:17 ` [PATCH/RFC 06/06] arm64: dts: renesas: r8a77980: One IMP-X5 device for R-Car V3H Magnus Damm
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=154807303153.2406.5961455669905578679.sendpatchset@octo \
--to=magnus.damm@gmail.com \
--cc=linux-renesas-soc@vger.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).