diff options
author | Simon Glass <sjg@chromium.org> | 2015-03-03 08:03:00 -0700 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2015-03-04 14:55:04 -0500 |
commit | db910353a126d84fe8dff7a694ea792f50fcfb6a (patch) | |
tree | 0cca558754e992284820fbc240690c13d0a00cb0 /board/atmark-techno/armadillo-800eva/Makefile | |
parent | bdfb34167f73afc7e04d52499fc14bc1cd33fec0 (diff) | |
download | u-boot-imx-db910353a126d84fe8dff7a694ea792f50fcfb6a.zip u-boot-imx-db910353a126d84fe8dff7a694ea792f50fcfb6a.tar.gz u-boot-imx-db910353a126d84fe8dff7a694ea792f50fcfb6a.tar.bz2 |
arm: spl: Allow board_init_r() to run with a larger stack
At present SPL uses a single stack, either CONFIG_SPL_STACK or
CONFIG_SYS_INIT_SP_ADDR. Since some SPL features (such as MMC and
environment) require a lot of stack, some boards set CONFIG_SPL_STACK to
point into SDRAM. They then set up SDRAM very early, before board_init_f(),
so that the larger stack can be used.
This is an abuse of lowlevel_init(). That function should only be used for
essential start-up code which cannot be delayed. An example of a valid use is
when only part of the SPL code is visible/executable, and the SoC must be set
up so that board_init_f() can be reached. It should not be used for SDRAM
init, console init, etc.
Add a CONFIG_SPL_STACK_R option, which allows the stack to be moved to a new
address before board_init_r() is called in SPL.
The expected SPL flow (for CONFIG_SPL_FRAMEWORK) is documented in the README.
Signed-off-by: Simon Glass <sjg@chromium.org>
For version 1:
Acked-by: Albert ARIBAUD <albert.u.boot@aribaud.net>
Reviewed-by: Stefan Roese <sr@denx.de>
Tested-by: Bo Shen <voice.shen@atmel.com>
Acked-by: Bo Shen <voice.shen@atmel.com>
Acked-by: Heiko Schocher <hs@denx.de>
Tested-by: Heiko Schocher <hs@denx.de>
Signed-off-by: Tom Rini <trini@konsulko.com>
Diffstat (limited to 'board/atmark-techno/armadillo-800eva/Makefile')
0 files changed, 0 insertions, 0 deletions