common: Add an option to relocate on ram top

Right now we only relocate u-boot to the top of the first
memory bank unless the board specific code overwrites it.
This is problematic when loading big binaries as it
fragments the contiguous memory space for no apparent reason.

On certain platforms, it is currently not possible to relocate U-Boot
above the 32bit boundary, due to various dependencies on content located
below the 32bit boundary. One such example is ethernet, where the packet
buffer built into U-Boot binary is placed below the 32bit boundary and
allows loading of data via ethernet even above 32bit boundary due to
memory copy from the packet buffer to the destination location.

A previous patch moves the bi_dram[] info from bd to gd and make
the memory bank information available early. So move the
dram_init_banksize() INITCALL before the relocation address calculation
and use it to derive the address.

Also add a Kconfig option and allow the common code to relocate U-Boot
to the top of the last discovered bank.
It's worth noting that this patch changes when dram_init_banksize()
is called. It's now called  much earlier in the board init process.
That is a significant ordering change for every board with a custom
dram_init_banksize(), and it is unconditional (not gated on RELOC_ADDR_TOP).

Reviewed-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
Tested-by: Simon Glass <sjg@chromium.org>  # Radxa ROCK 5B
Signed-off-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>
Tested-by: Christophe Leroy (CS GROUP) <chleroy@kernel.org>

diff --git a/Kconfig b/Kconfig
index 99b896b6cf1cbf94e2d6e440531f34c4fcb1b43b..8d9a20fe69344c741e698f12515bded2ec4ee2d5 100644 (file)
--- a/Kconfig
+++ b/Kconfig
@@ -503,6 +503,19 @@ config SKIP_RELOCATE_CODE_DATA_OFFSET
          Offset of the read-write memory which contains data, from read-only
          memory which contains executable text.
 
+config RELOC_ADDR_TOP
+       bool "Relocate to the topmost memory address"
+       help
+         When U-Boot relocates, it chooses the end of the first memory bank.
+         Enable this if you have multiple banks and want U-Boot to relocate
+         to the topmost memory address. This will use the information of the
+         board memory banks configured with dram_init_banksize() to calculate
+         the relocation address.
+         Use this if you are certain all of the devices can access memory
+         above the 32bit boundary. Devices that can only DMA below 4GiB will
+         misbehave because their buffers may be allocated above the 32-bit
+         boundary after relocation.
+
 endif # EXPERT
 
 config PHYS_64BIT

diff --git a/common/board_f.c b/common/board_f.c
index b3e633418e1bde319cd85dffac08402c20e0ff81..85b888d4bb85b98fea0872b9e6d6da371e0939a1 100644 (file)
--- a/common/board_f.c
+++ b/common/board_f.c
@@ -31,6 +31,7 @@
 #include <log.h>
 #include <malloc.h>
 #include <mapmem.h>
+#include <memtop.h>
 #include <os.h>
 #include <post.h>
 #include <relocate.h>
@@ -50,6 +51,7 @@
 #include <dm/root.h>
 #include <linux/errno.h>
 #include <linux/log2.h>
+#include <linux/sizes.h>
 
 DECLARE_GLOBAL_DATA_PTR;
 
@@ -308,6 +310,9 @@ __weak int mach_cpu_init(void)
 /* Get the top of usable RAM */
 __weak phys_addr_t board_get_usable_ram_top(phys_size_t total_size)
 {
+       if (CONFIG_IS_ENABLED(RELOC_ADDR_TOP))
+               return gd->ram_top;
+
 #if defined(CFG_SYS_SDRAM_BASE) && CFG_SYS_SDRAM_BASE > 0
        /*
         * Detect whether we have so much RAM that it goes past the end of our
@@ -339,7 +344,23 @@ static int setup_ram_base(void)
 static int setup_ram_config(void)
 {
        debug("Monitor len: %08x\n", gd->mon_len);
-#if CONFIG_VAL(SYS_MEM_TOP_HIDE)
+
+       if (CONFIG_IS_ENABLED(RELOC_ADDR_TOP)) {
+               int i;
+               phys_addr_t top;
+
+               gd->ram_size = 0;
+               for (i = 0; i < CONFIG_NR_DRAM_BANKS; i++) {
+                       top = get_mem_top(gd->dram[i].start, gd->dram[i].size,
+                                         ALIGN(gd->mon_len, SZ_1M),
+                                         (void *)gd->fdt_blob);
+                       gd->ram_top = max(top, gd->ram_top);
+                       gd->ram_size += gd->dram[i].size;
+               }
+       } else {
+               gd->ram_top = gd->ram_base + get_effective_memsize();
+       }
+       gd->ram_top = board_get_usable_ram_top(gd->mon_len);
        /*
         * Subtract specified amount of memory to hide so that it won't
         * get "touched" at all by U-Boot. By fixing up gd->ram_size
@@ -350,10 +371,10 @@ static int setup_ram_config(void)
         * memory size from the SDRAM controller setup will have to
         * get fixed.
         */
+#if CONFIG_VAL(SYS_MEM_TOP_HIDE)
+       gd->ram_top -= CONFIG_SYS_MEM_TOP_HIDE;
        gd->ram_size -= CONFIG_SYS_MEM_TOP_HIDE;
 #endif
-       gd->ram_top = gd->ram_base + get_effective_memsize();
-       gd->ram_top = board_get_usable_ram_top(gd->mon_len);
 
        debug("Ram top: %08llx\n", (unsigned long long)gd->ram_top);
        debug("Ram size: %08llx\n", (unsigned long long)gd->ram_size);
@@ -988,6 +1009,7 @@ static void initcall_run_f(void)
         *  - board info struct
         */
        INITCALL(setup_ram_base);
+       INITCALL(dram_init_banksize);
        INITCALL(setup_ram_config);
        INITCALL(setup_dest_addr);
 #if CONFIG_IS_ENABLED(OF_BOARD_FIXUP) && \
@@ -1016,7 +1038,6 @@ static void initcall_run_f(void)
        INITCALL(reserve_bloblist);
        INITCALL(reserve_arch);
        INITCALL(reserve_stacks);
-       INITCALL(dram_init_banksize);
        INITCALL(show_dram_config);
        WATCHDOG_RESET();
        INITCALL(setup_bdinfo);