From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH resend] arm64: dts: r8a7796: salvator-x: Update memory node to 4 GiB map
Date: Tue, 20 Dec 2016 11:54:25 +0100 [thread overview]
Message-ID: <20161220105424.GK19532@verge.net.au> (raw)
In-Reply-To: <1481815889-15583-1-git-send-email-geert+renesas@glider.be>
On Thu, Dec 15, 2016 at 04:31:29PM +0100, Geert Uytterhoeven wrote:
> 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>
> ---
> Simon, please apply!
>
> U-Boot already adds the second memory region to the "reg" property of
> the first memory node in DT, so this patch is actually a no-op.
> IMHO it doesn't make much sense to keep on pretending we don't have
> enabled memory outside the 32-bit address space.
Hi Geert,
I agree with the reasoning above and have queued up this patch for v4.11.
It is a shame that u-boot has enabled this for us as it would have
been nice to retain control of that occuring. But alas it was not to be so.
prev parent reply other threads:[~2016-12-20 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 15:31 [PATCH resend] arm64: dts: r8a7796: salvator-x: Update memory node to 4 GiB map Geert Uytterhoeven
2016-12-20 10:54 ` Simon Horman [this message]
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=20161220105424.GK19532@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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).