From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Simon Horman <horms@verge.net.au>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Subject: Re: [PATCH 4/4] arm64: dts: renesas: Add HiHope RZ/G2N main board support
Date: Fri, 27 Sep 2019 15:41:35 +0200 [thread overview]
Message-ID: <CAMuHMdWLpNn+8rh8Fb2-tQC_g9ThdAGxv4Js6muhPMr1BXR8Zg@mail.gmail.com> (raw)
In-Reply-To: <OSBPR01MB2103CA9A60AE9366BC593944B8810@OSBPR01MB2103.jpnprd01.prod.outlook.com>
Hi Biju,
On Fri, Sep 27, 2019 at 2:56 PM Biju Das <biju.das@bp.renesas.com> wrote:
> > Subject: Re: [PATCH 4/4] arm64: dts: renesas: Add HiHope RZ/G2N main
> > board support
> > On Tue, Sep 17, 2019 at 3:12 PM Biju Das <biju.das@bp.renesas.com> wrote:
> > > Basic support for the HiHope RZ/G2N main board:
> > > - Memory,
> > > - Main crystal,
> > > - Serial console
> > >
> > > Signed-off-by: Biju Das <biju.das@bp.renesas.com>
> >
> > Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
> > One question below...
> >
> > > --- /dev/null
> > > +++ b/arch/arm64/boot/dts/renesas/r8a774b1-hihope-rzg2n.dts
> > > @@ -0,0 +1,26 @@
> > > +// SPDX-License-Identifier: GPL-2.0
> > > +/*
> > > + * Device Tree Source for the HiHope RZ/G2N main board
> > > + *
> > > + * Copyright (C) 2019 Renesas Electronics Corp.
> > > + */
> > > +
> > > +/dts-v1/;
> > > +#include "r8a774b1.dtsi"
> > > +#include "hihope-common.dtsi"
> > > +
> > > +/ {
> > > + model = "HopeRun HiHope RZ/G2N main board based on r8a774b1";
> > > + compatible = "hoperun,hihope-rzg2n", "renesas,r8a774b1";
> > > +
> > > + memory@48000000 {
> > > + device_type = "memory";
> > > + /* first 128MB is reserved for secure area. */
> > > + reg = <0x0 0x48000000 0x0 0x78000000>;
> > > + };
> > > +
> > > + memory@480000000 {
> > > + device_type = "memory";
> > > + reg = <0x4 0x80000000 0x0 0x80000000>;
> > > + };
> > > +};
> >
> > So both the HiHope RZ/G2M and RZ/G2N boards have 4 GiB of RAM, while
> > the latter has a narrower memory bus, so it must be wired differently?
>
> RZ/G2M is LPDDR4-3200 with 32 bits × 2 channels, where as RZ/G2N is LPDDR4-3200 with 32 bits × 1 channel.
> RZ/G2M can have split mapping where as RZ/G2N can have only linear mapping.
Thanks for the confirmation, will queue in renesas-devel for v5.5.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2019-09-27 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 13:05 [PATCH 0/4] Add HiHope RZ/G2N main board support Biju Das
2019-09-17 13:05 ` [PATCH 1/4] arm64: dts: renesas: Initial r8a774b1 SoC device tree Biju Das
2019-09-27 12:06 ` Geert Uytterhoeven
2019-09-17 13:05 ` [PATCH 2/4] arm64: defconfig: enable R8A774B1 SoC Biju Das
2019-09-27 11:32 ` Geert Uytterhoeven
2019-09-17 13:05 ` [PATCH 3/4] arm64: renesas_defconfig: " Biju Das
2019-09-27 11:38 ` Geert Uytterhoeven
2019-09-17 13:05 ` [PATCH 4/4] arm64: dts: renesas: Add HiHope RZ/G2N main board support Biju Das
2019-09-27 12:38 ` Geert Uytterhoeven
2019-09-27 12:56 ` Biju Das
2019-09-27 13:41 ` Geert Uytterhoeven [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=CAMuHMdWLpNn+8rh8Fb2-tQC_g9ThdAGxv4Js6muhPMr1BXR8Zg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).