From: Geert Uytterhoeven <geert+renesas@glider.be>
To: "Magnus Damm" <magnus.damm@gmail.com>,
"Simon Horman" <horms@verge.net.au>,
"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: linux-renesas-soc@vger.kernel.org,
Takeshi Kihara <takeshi.kihara.df@renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH/RFC 1/5] arm64: dts: r8a7796: salvator-x: Update memory node to 4 GiB map
Date: Mon, 31 Oct 2016 18:08:18 +0100 [thread overview]
Message-ID: <1477933702-13423-2-git-send-email-geert+renesas@glider.be> (raw)
In-Reply-To: <1477933702-13423-1-git-send-email-geert+renesas@glider.be>
From: Takeshi Kihara <takeshi.kihara.df@renesas.com>
This patch updates memory region:
- After changes, the new map of the Salvator-X board on R8A7796 SoC
Bank0: 2GiB RAM : 0x000048000000 -> 0x000bfffffff
Bank1: 2GiB RAM : 0x000600000000 -> 0x0067fffffff
- Before changes, the old map looked like this:
Bank0: 2GiB RAM : 0x000048000000 -> 0x000bfffffff
Signed-off-by: Takeshi Kihara <takeshi.kihara.df@renesas.com>
[geert: Correct size of old map]
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
Note: Depending on firmware version, this patch may not make a
difference at all!
Indeed, U-Boot may already add the second memory region to the "reg"
property of the first memory node in DT, regardless of the presence of a
second memory node. Fortunately Linux handles duplicate memory regions
just fine...
---
arch/arm64/boot/dts/renesas/r8a7796-salvator-x.dts | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a7796-salvator-x.dts b/arch/arm64/boot/dts/renesas/r8a7796-salvator-x.dts
index f7c0ec47af7660b1..2fe75b06288c608e 100644
--- a/arch/arm64/boot/dts/renesas/r8a7796-salvator-x.dts
+++ b/arch/arm64/boot/dts/renesas/r8a7796-salvator-x.dts
@@ -32,6 +32,11 @@
reg = <0x0 0x48000000 0x0 0x78000000>;
};
+ memory@600000000 {
+ device_type = "memory";
+ reg = <0x6 0x00000000 0x0 0x80000000>;
+ };
+
reg_1p8v: regulator0 {
compatible = "regulator-fixed";
regulator-name = "fixed-1.8V";
--
1.9.1
next prev parent reply other threads:[~2016-10-31 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 17:08 [PATCH/RFC 0/5] arm64: r8a7796: 64-bit Memory and Ethernet Prototype Geert Uytterhoeven
2016-10-31 17:08 ` Geert Uytterhoeven [this message]
2016-10-31 17:08 ` [PATCH/RFC 2/5] arm64: dts: r8a7796: Add IPMMU device nodes Geert Uytterhoeven
2016-10-31 17:08 ` [PATCH/RFC 3/5] arm64: dts: r8a7796: Connect Ethernet AVB to IPMMU Geert Uytterhoeven
2016-10-31 17:08 ` [PATCH/RFC 4/5] arm64: dts: r8a7796: Enable ipmmu_ds0 and ipmmu_mm Geert Uytterhoeven
2016-11-01 11:27 ` Sergei Shtylyov
2016-10-31 17:08 ` [PATCH/RFC 5/5] dmaengine: rcar-dmac: Widen DMA mask to 40 bits Geert Uytterhoeven
2016-11-25 9:00 ` Geert Uytterhoeven
2016-11-25 9:01 ` Magnus Damm
2016-12-21 7:17 ` Kuninori Morimoto
2016-12-21 9:28 ` Geert Uytterhoeven
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=1477933702-13423-2-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=takeshi.kihara.df@renesas.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).