diff options
author | Marek Vasut <marex@denx.de> | 2014-03-28 08:31:01 +0100 |
---|---|---|
committer | Stefano Babic <sbabic@denx.de> | 2014-03-31 18:28:51 +0200 |
commit | 97334c66169af70b665e4726730eadd002cc54b8 (patch) | |
tree | e2b7812b25749f24d7fd81bcf13f8e0f0c72d624 /arch/arm/cpu/arm926ejs | |
parent | 2f844e76daa2141f445009d19fc9dffdaf3f5000 (diff) |
arm: mx5: Avoid hardcoding memory sizes on M53EVK
The DRAM size can be easily detected at runtime on i.MX53. Implement
such detection on M53EVK and adjust the rest of the macros accordingly
to use the detected values.
An important thing to note here is that we had to override the function
for trimming the effective DRAM address, get_effective_memsize(). That
is because the function uses CONFIG_MAX_MEM_MAPPED as the upper bound of
the available DRAM and we don't have gd->bd->bi_dram[0].size set up at
the time the function is called, thus we cannot put this into the macro
CONFIG_MAX_MEM_MAPPED . Instead, we use custom override where we use the
size of the first DRAM block which we just detected.
Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Fabio Estevam <fabio.estevam@freescale.com>
Cc: Stefano Babic <sbabic@denx.de>
Cc: Wolfgang Denk <wd@denx.de>
Diffstat (limited to 'arch/arm/cpu/arm926ejs')
0 files changed, 0 insertions, 0 deletions