-
由 Simon Glass 提交于
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: NSimon Glass <sjg@chromium.org> For version 1: Acked-by: NAlbert ARIBAUD <albert.u.boot@aribaud.net> Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NBo Shen <voice.shen@atmel.com> Acked-by: NBo Shen <voice.shen@atmel.com> Acked-by: NHeiko Schocher <hs@denx.de> Tested-by: NHeiko Schocher <hs@denx.de> Signed-off-by: NTom Rini <trini@konsulko.com>
db910353