mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Marcin Niestroj <m.niestroj@grinn-global.com>,
	barebox@lists.infradead.org
Cc: Marcin Niestroj <m.niestroj@emb.dev>
Subject: Re: [PATCH] ARM: rpi: parse memory from vc fdt
Date: Tue, 10 Jan 2023 20:56:13 +0100	[thread overview]
Message-ID: <fca0dd20-a957-e6da-4dad-bd268b8b8953@pengutronix.de> (raw)
In-Reply-To: <20230110193251.2821638-1-m.niestroj@grinn-global.com>

On 10.01.23 20:32, Marcin Niestroj wrote:
> From: Marcin Niestroj <m.niestroj@emb.dev>
> 
> Currently for RaspberryPi platform there is only one memory bank
> created, based on information fetched over mailbox. This is fine for
> booting Barebox, but unfortunately all the other memory banks are not
> propagated to Linux during boot, thus cannot be utilized. In fact, even
> when using /vc.dtb as device-tree for Linux, all memory nodes in FDT are
> deleted and new ones are created by Barebox by memory fixup mechanism,
> using exising RAM information. As a result RaspberryPi 4 boots Linux
> with 1GB RAM available, instead of 2GB (2 banks, each 1GB).
> 
> At the end of VideoCore FDT parsing, do the same as of_probe_memory() in
> mem_initcall does, but for VideoCore provided devicetree/memory
> information. During Linux boot this information is used for memory fixup
> mechanism and in case of RaspberryPi 4 this results in 2 memory banks
> being propagated:
> 
>   # ls /proc/device-tree/memory*
>   /proc/device-tree/memory@0:
>   device_type  name         reg
> 
>   /proc/device-tree/memory@40000000:
>   device_type  name         reg
> 
> Signed-off-by: Marcin Niestroj <m.niestroj@emb.dev>

Thanks for your patch. I suggest this be applied to master.

I think it may be worthwhile in future to only query the mailbox
interface for memory in PBL (lowlevel.c) for use as early mem and
depend solely on DT in barebox proper.

> ---
>  arch/arm/boards/raspberry-pi/rpi-common.c | 16 +++++++++++++++-
>  1 file changed, 15 insertions(+), 1 deletion(-)

> +		err = of_add_memory(memory, false);
> +		if (err)
> +			ret = err;

No one does anything wither either err or ret, so you can drop that.
Anyways:

Reviewed-by: Ahmad Fatoum <a.fatoum@pengutronix.de>

> +	}
> +
>  out:
>  	if (root)
>  		of_delete_node(root);

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




  reply	other threads:[~2023-01-10 19:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 19:32 Marcin Niestroj
2023-01-10 19:56 ` Ahmad Fatoum [this message]
2023-01-11  8:28   ` Sascha Hauer

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=fca0dd20-a957-e6da-4dad-bd268b8b8953@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=m.niestroj@emb.dev \
    --cc=m.niestroj@grinn-global.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