boston: Setup memory ranges in FDT provided to Linux

The boston memory map isn't suited to the simple "all memory starting
from 0" approach that the MIPS arch_fixup_fdt() implementation takes.
Instead we need to indicate the first 256MiB of DDR from 0 and the rest
from 0x90000000. Implement ft_board_setup to do that.

Signed-off-by: Paul Burton <paul.burton@imgtec.com>
Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>

diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index 07488fe651fb913aed95b7143018b63193ddedfc..d07b92d1b442b86be928b28ee08b0cb1fbfe23c4 100644 (file)
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -97,6 +97,7 @@ config TARGET_BOSTON
        select MIPS_CM
        select MIPS_L1_CACHE_SHIFT_6
        select MIPS_L2_CACHE
+       select OF_BOARD_SETUP
        select SUPPORTS_BIG_ENDIAN
        select SUPPORTS_LITTLE_ENDIAN
        select SUPPORTS_CPU_MIPS32_R1

diff --git a/board/imgtec/boston/Makefile b/board/imgtec/boston/Makefile
index deda457f3cdb6103d2731a4f7127214e43f77a45..d3fd49d285ecdb27c9784f9671fadeb41adc39d8 100644 (file)
--- a/board/imgtec/boston/Makefile
+++ b/board/imgtec/boston/Makefile
@@ -6,4 +6,5 @@
 
 obj-y += checkboard.o
 obj-y += ddr.o
+obj-y += dt.o
 obj-y += lowlevel_init.o

diff --git a/board/imgtec/boston/dt.c b/board/imgtec/boston/dt.c
new file mode 100644 (file)
index 0000000..b34f9bc
--- /dev/null
+++ b/board/imgtec/boston/dt.c
@@ -0,0 +1,27 @@
+/*
+ * Copyright (C) 2016 Imagination Technologies
+ *
+ * SPDX-License-Identifier:    GPL-2.0
+ */
+
+#include <common.h>
+#include <fdt_support.h>
+
+int ft_board_setup(void *blob, bd_t *bd)
+{
+       DECLARE_GLOBAL_DATA_PTR;
+       u64 mem_start[2], mem_size[2];
+       int mem_regions;
+
+       mem_start[0] = 0;
+       mem_size[0] = min_t(u64, 256llu << 20, gd->ram_size);
+       mem_regions = 1;
+
+       if (gd->ram_size > mem_size[0]) {
+               mem_start[1] = 0x80000000 + mem_size[0];
+               mem_size[1] = gd->ram_size - mem_size[0];
+               mem_regions++;
+       }
+
+       return fdt_fixup_memory_banks(blob, mem_start, mem_size, mem_regions);
+}