aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndre Przywara <andre.przywara@arm.com>2022-03-04 16:30:17 +0000
committerTom Rini <trini@konsulko.com>2022-04-01 14:59:15 -0400
commit1a1143a45457161e90ea4cd5f3b0561d924ed8fe (patch)
tree6b9b57a3a30d405ff68b9e8165fd5eebc22f5b70
parent30cacb8123459328c46c25f65196bb4885dcdb05 (diff)
downloadu-boot-1a1143a45457161e90ea4cd5f3b0561d924ed8fe.zip
u-boot-1a1143a45457161e90ea4cd5f3b0561d924ed8fe.tar.gz
u-boot-1a1143a45457161e90ea4cd5f3b0561d924ed8fe.tar.bz2
vexpress64: pick DRAM size from DT
So far the DRAM size for both the Juno and the FVP model were hardcoded in our config header file. For the Juno this is fine, as all models have 8 GiB of DRAM, but the DRAM size can be configured on the model command line. Drop the fixed DRAM size setup, instead look up the size in the device tree, that we now have for every board. This allows a user to inject a DT with the proper size, and be able to use the full amount of DRAM. Signed-off-by: Andre Przywara <andre.przywara@arm.com>
-rw-r--r--board/armltd/vexpress64/vexpress64.c12
1 files changed, 2 insertions, 10 deletions
diff --git a/board/armltd/vexpress64/vexpress64.c b/board/armltd/vexpress64/vexpress64.c
index c3ad1fc..709ebf3 100644
--- a/board/armltd/vexpress64/vexpress64.c
+++ b/board/armltd/vexpress64/vexpress64.c
@@ -88,20 +88,12 @@ int board_init(void)
int dram_init(void)
{
- gd->ram_size = PHYS_SDRAM_1_SIZE;
- return 0;
+ return fdtdec_setup_mem_size_base();
}
int dram_init_banksize(void)
{
- gd->bd->bi_dram[0].start = PHYS_SDRAM_1;
- gd->bd->bi_dram[0].size = PHYS_SDRAM_1_SIZE;
-#ifdef PHYS_SDRAM_2
- gd->bd->bi_dram[1].start = PHYS_SDRAM_2;
- gd->bd->bi_dram[1].size = PHYS_SDRAM_2_SIZE;
-#endif
-
- return 0;
+ return fdtdec_setup_memory_banksize();
}
/* Assigned in lowlevel_init.S