From: Chester Lin <clin@suse.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Rob Herring <robh+dt@kernel.org>,
s32@nxp.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shawn Guo <shawnguo@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Oleksij Rempel <linux@rempel-privat.de>,
Stefan Riedmueller <s.riedmueller@phytec.de>,
Matthias Schiffer <matthias.schiffer@ew.tq-group.com>,
Li Yang <leoyang.li@nxp.com>, Fabio Estevam <festevam@gmail.com>,
Matteo Lisi <matteo.lisi@engicam.com>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Tim Harvey <tharvey@gateworks.com>,
Jagan Teki <jagan@amarulasolutions.com>,
catalin-dan.udma@nxp.com, bogdan.hamciuc@nxp.com,
bogdan.folea@nxp.com, ciprianmarian.costea@nxp.com,
radu-nicolae.pirea@nxp.com, ghennadi.procopciuc@nxp.com,
Matthias Brugger <matthias.bgg@gmail.com>,
"Ivan T . Ivanov" <iivanov@suse.de>,
"Lee, Chun-Yi" <jlee@suse.com>
Subject: Re: [PATCH 7/8] arm64: dts: s32g2: add memory nodes for evb and rdb2
Date: Fri, 13 Aug 2021 22:58:29 +0800 [thread overview]
Message-ID: <YRaIlYiYH6P7UolW@linux-8mug> (raw)
In-Reply-To: <17ab7b71-2dbe-0c66-e180-4cc2e8310441@suse.de>
On Thu, Aug 12, 2021 at 08:25:00PM +0200, Andreas Färber wrote:
> Hi Chester et al.,
>
> On 05.08.21 08:54, Chester Lin wrote:
> > Add memory nodes for S32G-VNP-EVB and S32G-VNP-RDB2 since they have fixed
> > RAM size.
>
> You can drop "since they have fixed RAM size" - if they didn't, you
> would simply choose the lowest size and rely on the bootloader (U-Boot)
> to overwrite it with the actually detected size.
>
> Please expand why this patch is separate - BSP based, I assume?
>
Yes, the information of memory banks is from s32 downstream kernel, which is
listed in the board DTs of older releases [bsp27] although newer releases
[bsp28 & bsp29] have moved it into s32 downstream u-boot as runtime fdt-fixup.
I think we should still reveal this information in kernel DTs in order to have
better understanding of system memory ranges that each board can have.
@NXP: Please don't hesitate to let me know if any better idea, thanks!
> >
> > Signed-off-by: Chester Lin <clin@suse.com>
> > ---
> > arch/arm64/boot/dts/freescale/s32g274a-evb.dts | 8 ++++++++
> > arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts | 8 ++++++++
> > 2 files changed, 16 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/freescale/s32g274a-evb.dts b/arch/arm64/boot/dts/freescale/s32g274a-evb.dts
> > index a1ae5031730a..cd41f0af5dd8 100644
> > --- a/arch/arm64/boot/dts/freescale/s32g274a-evb.dts
> > +++ b/arch/arm64/boot/dts/freescale/s32g274a-evb.dts
> > @@ -1,6 +1,7 @@
> > // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
> > /*
> > * Copyright (c) 2021 SUSE LLC
> > + * Copyright 2019-2020 NXP
>
> @NXP: Please review year, alignment. Do any Signed-off-bys apply?
>
> > */
> >
> > /dts-v1/;
> > @@ -14,6 +15,13 @@ / {
> > chosen {
> > stdout-path = "serial0:115200n8";
> > };
> > +
> > + memory@80000000 {
> > + device_type = "memory";
> > + /* 4GB RAM */
>
> This looks strange to me - either put /* 4 GiB RAM */ before the node,
> three lines above, and/or append comment /* 2 GiB */ on each line below.
> Note the space, and suggest to be precise about factor 1024 vs. 1000.
>
Thank you for the suggestion.
> > + reg = <0 0x80000000 0 0x80000000>,
>
> Note that this gives you the range to use for the .dtsi /soc node:
> Address 0x0 with size 0x80000000 gets mapped to 0x0 0x0, excluding the
> upper 0x80000000 for the RAM here. Or address 0x0 0x0 for two /soc cells
> if there are high-memory peripherals.
>
I don't know if memory ranges might be changed for new boards or CPU revisions
in the future, which means the first memory range might be expanded as well
[e.g. 0~4GB]. Based this assumption, I think the size should also be changed
accordingly. Not sure if overlays can still work with this case but overwriting
all reg properties under /soc could be awful.
However if we only have to think of current hardware spec, it's good to declare
"range = <0 0 0 0x80000000>".
Please feel free to let me know if any suggestions, thanks.
> > + <8 0x80000000 0 0x80000000>;
>
> Maybe use 0x8 here and 0x0 above? (second 0 stays same, so don't mind)
>
Will fix it.
> > + };
> > };
> >
> > &uart0 {
> > diff --git a/arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts b/arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts
> > index b2faae306b70..8fbbf3b45eb8 100644
> > --- a/arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts
> > +++ b/arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts
> > @@ -1,6 +1,7 @@
> > // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
> > /*
> > * Copyright (c) 2021 SUSE LLC
> > + * Copyright 2019-2020 NXP
>
> @NXP: 2021?
>
> > */
> >
> > /dts-v1/;
> > @@ -14,6 +15,13 @@ / {
> > chosen {
> > stdout-path = "serial0:115200n8";
> > };
> > +
> > + memory@80000000 {
> > + device_type = "memory";
> > + /* 4GB RAM */
> > + reg = <0 0x80000000 0 0x80000000>,
> > + <8 0x80000000 0 0x80000000>;
> > + };
>
> Same comments as for EVB.
>
> > };
> >
> > &uart0 {
>
> Regards,
> Andreas
>
> --
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Felix Imendörffer
> HRB 36809 (AG Nürnberg)
>
next prev parent reply other threads:[~2021-08-13 14:58 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 6:54 [PATCH 0/8] arm64: dts: initial NXP S32G2 support Chester Lin
2021-08-05 6:54 ` [PATCH 1/8] dt-bindings: arm: fsl: add NXP S32G2 boards Chester Lin
2021-08-12 15:46 ` Andreas Färber
2021-08-13 17:49 ` Rob Herring
2021-08-13 17:53 ` Rob Herring
2021-08-18 14:34 ` Chester Lin
2021-09-06 20:38 ` Andreas Färber
2021-09-07 6:59 ` Krzysztof Kozlowski
2021-09-07 8:59 ` Andreas Färber
2021-09-06 19:35 ` Andreas Färber
2021-08-05 6:54 ` [PATCH 2/8] dt-bindings: serial: fsl-linflexuart: convert to json-schema format Chester Lin
2021-08-12 16:04 ` Andreas Färber
2021-08-13 11:11 ` Chester Lin
2021-08-13 11:28 ` Krzysztof Kozlowski
2021-08-13 11:43 ` Chester Lin
2021-08-13 18:04 ` Rob Herring
2021-08-13 18:07 ` Rob Herring
2021-08-05 6:54 ` [PATCH 3/8] dt-bindings: serial: fsl-linflexuart: Add compatible for S32G2 Chester Lin
2021-08-12 16:27 ` Andreas Färber
2021-08-13 14:27 ` Radu Nicolae Pirea (NXP OSS)
2021-08-13 18:11 ` Rob Herring
2021-08-13 18:09 ` Rob Herring
2021-08-05 6:54 ` [PATCH 4/8] arm64: dts: add NXP S32G2 support Chester Lin
2021-08-12 17:26 ` Andreas Färber
2021-08-13 3:28 ` Chester Lin
2021-08-13 7:05 ` Andreas Färber
2021-08-20 13:12 ` Marc Zyngier
2021-08-20 15:15 ` Chester Lin
2021-08-20 15:29 ` Marc Zyngier
2021-08-21 12:39 ` Chester Lin
2021-08-21 14:20 ` Marc Zyngier
2021-08-05 6:54 ` [PATCH 5/8] arm64: dts: s32g2: add serial/uart support Chester Lin
2021-08-12 17:42 ` Andreas Färber
2021-08-13 9:54 ` Radu Nicolae Pirea (NXP OSS)
2021-08-05 6:54 ` [PATCH 6/8] arm64: dts: s32g2: add VNP-EVB and VNP-RDB2 support Chester Lin
2021-08-12 18:00 ` Andreas Färber
2021-08-13 8:47 ` Chester Lin
2021-08-05 6:54 ` [PATCH 7/8] arm64: dts: s32g2: add memory nodes for evb and rdb2 Chester Lin
2021-08-12 18:25 ` Andreas Färber
2021-08-13 14:58 ` Chester Lin [this message]
2021-08-05 6:54 ` [PATCH 8/8] MAINTAINERS: Add an entry for NXP S32G2 boards Chester Lin
2021-08-05 7:49 ` Krzysztof Kozlowski
2021-08-09 8:03 ` Shawn Guo
2021-08-12 15:30 ` Andreas Färber
2021-08-12 15:54 ` Krzysztof Kozlowski
2021-08-09 8:06 ` [PATCH 0/8] arm64: dts: initial NXP S32G2 support Shawn Guo
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=YRaIlYiYH6P7UolW@linux-8mug \
--to=clin@suse.com \
--cc=afaerber@suse.de \
--cc=bogdan.folea@nxp.com \
--cc=bogdan.hamciuc@nxp.com \
--cc=catalin-dan.udma@nxp.com \
--cc=ciprianmarian.costea@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=ghennadi.procopciuc@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=iivanov@suse.de \
--cc=jagan@amarulasolutions.com \
--cc=jlee@suse.com \
--cc=krzk@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=matteo.lisi@engicam.com \
--cc=matthias.bgg@gmail.com \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=radu-nicolae.pirea@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.riedmueller@phytec.de \
--cc=s32@nxp.com \
--cc=shawnguo@kernel.org \
--cc=tharvey@gateworks.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).