devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Olof Johansson <olof@lixom.net>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	NAOYA SHIIBA <naoya.shiiba.nx@renesas.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] ARM: shmobile: lager: correct memory map
Date: Tue, 26 Aug 2014 17:52:37 +0900	[thread overview]
Message-ID: <20140826085234.GA29667@verge.net.au> (raw)
In-Reply-To: <CAMuHMdVqZ29-jaS+kLwdVycLOMSbz9H7oJGuq3dLH2y-81mVcQ@mail.gmail.com>

On Tue, Aug 26, 2014 at 09:52:10AM +0200, Geert Uytterhoeven wrote:
> On Tue, Aug 26, 2014 at 6:20 AM, Simon Horman <horms@verge.net.au> wrote:
> >> > diff --git a/arch/arm/boot/dts/r8a7790-lager.dts b/arch/arm/boot/dts/r8a7790-lager.dts
> >> > index 0118cbf..84dcafa 100644
> >> > --- a/arch/arm/boot/dts/r8a7790-lager.dts
> >> > +++ b/arch/arm/boot/dts/r8a7790-lager.dts
> >> > @@ -32,7 +32,7 @@
> >> >                 reg = <0 0x40000000 0 0x40000000>;
> >> >         };
> >> >
> >> > -       memory@180000000 {
> >> > +       memory@140000000 {
> >>
> >> That should even be "memory@1,40000000".
> >
> > Two comma-separated 32bit values in the case
> > where a memory range starts above 4Gb?
> 
> Yes. As #address-cells is 2, there should be two values after the "@"
> (the first one may be optional if it's zero, I don't know for sure?)
> 
> > If so it looks like this will be the first user of that syntax
> > (I don't see any in linux-next today).
> 
> No, "git grep '@.*,' -- arch/arm/boot/dts" shows several users.
> Not all of them are 64-bit memory addresses, but some are.

Thanks, I like your grep better than mine.

> > I do however see several users of memrory@64bit_value.
> > Mostly other renesas fds files; ecx-2000.dts being the exception.
> > Should they be fixed too?
> >
> > $ find -name "*.dts" | xargs grep memory@[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]
> > ./arch/arm/boot/dts/r8a7791-henninger.dts:      memory@200000000 {
> > ./arch/arm/boot/dts/r8a7791-koelsch.dts:        memory@200000000 {
> > ./arch/arm/boot/dts/ecx-2000.dts:       memory@200000000 {
> > ./arch/arm/boot/dts/r8a73a4-ape6evm-reference.dts:      memory@200000000 {
> > ./arch/arm/boot/dts/r8a7790-lager.dts:  memory@180000000 {
> > ./arch/arm/boot/dts/r8a73a4-ape6evm.dts:        memory@200000000 {
> 
> Yes, these should be fixed, too.
> 
> It's a pity dtc doesn't complain about this.

Indeed.

      reply	other threads:[~2014-08-26  8:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1409021623-10633-1-git-send-email-horms+renesas@verge.net.au>
     [not found] ` <CAOesGMieRk4Dvg=gxTgcVssARkK6DeoaVyK8619B2N5=wwo=Uw@mail.gmail.com>
     [not found]   ` <20140826042055.GA12108@verge.net.au>
2014-08-26  7:52     ` [PATCH] ARM: shmobile: lager: correct memory map Geert Uytterhoeven
2014-08-26  8:52       ` 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=20140826085234.GA29667@verge.net.au \
    --to=horms@verge.net.au \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=naoya.shiiba.nx@renesas.com \
    --cc=olof@lixom.net \
    /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).