Andreas Rammhold c4849f1818 of/fdt: run soc memory setup when early_init_dt_scan_memory fails ... commit 2a12187d58 upstream. If memory has been found early_init_dt_scan_memory now returns 1. If it hasn't found any memory it will return 0, allowing other memory setup mechanisms to carry on. Previously early_init_dt_scan_memory always returned 0 without distinguishing between any kind of memory setup being done or not. Any code path after the early_init_dt_scan memory call in the ramips plat_mem_setup code wouldn't be executed anymore. Making early_init_dt_scan_memory the only way to initialize the memory. Some boards, including my mt7621 based Cudy X6 board, depend on memory initialization being done via the soc_info.mem_detect function pointer. Those wouldn't be able to obtain memory and panic the kernel during early bootup with the message "early_init_dt_alloc_memory_arch: Failed to allocate 12416 bytes align=0x40". Fixes: 1f012283e9 ("of/fdt: Rework early_init_dt_scan_memory() to call directly") Cc: stable@vger.kernel.org Signed-off-by: Andreas Rammhold <andreas@rammhold.de> Link: https://lore.kernel.org/r/20221223112748.2935235-1-andreas@rammhold.de Signed-off-by: Rob Herring <robh@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2023-01-12 12:02:51 +01:00
..
Kconfig	…
Makefile	…
Platform	…
bootrom.c	…
cevt-rt3352.c	…
clk.c	…
common.h	…
early_printk.c	…
ill_acc.c	…
irq-gic.c	…
irq.c	…
mt7620.c	…
mt7621.c	mips: ralink: mt7621: do not use kzalloc too early	2022-12-21 17:48:03 +01:00
of.c	of/fdt: run soc memory setup when early_init_dt_scan_memory fails	2023-01-12 12:02:51 +01:00
prom.c	…
reset.c	…
rt288x.c	…
rt305x.c	…
rt3883.c	…
timer-gic.c	…
timer.c	…