diff options
author | Marcin Niestroj <m.niestroj@emb.dev> | 2023-01-10 20:32:51 +0100 |
---|---|---|
committer | Sascha Hauer <s.hauer@pengutronix.de> | 2023-01-11 09:28:19 +0100 |
commit | 31e5e23730ea2459d4d370596a43a8c8b4bf8758 (patch) | |
tree | f630c622effd9d3895fcc15d353673504bbec29e /common | |
parent | 12763d0fe56899d3729d0e6755446ed7c740a88a (diff) | |
download | barebox-31e5e23730ea2459d4d370596a43a8c8b4bf8758.tar.gz barebox-31e5e23730ea2459d4d370596a43a8c8b4bf8758.tar.xz |
ARM: rpi: parse memory from vc fdt
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>
Reviewed-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Link: https://lore.barebox.org/20230110193251.2821638-1-m.niestroj@grinn-global.com
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'common')
0 files changed, 0 insertions, 0 deletions