From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: spl: Allow board_init_r() to run with a larger stack
Date: Mon, 19 Jan 2015 08:08:43 +0100 [thread overview]
Message-ID: <54BCAD7B.6040804@denx.de> (raw)
In-Reply-To: <1421607336-26934-1-git-send-email-sjg@chromium.org>
On 18.01.2015 19:55, Simon Glass wrote:
> 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 now:
>
> Execution starts with start.S. Two main functions can be provided by the
> board implementation. The purpose and limitations of each is described below.
> After that, the common board_init_r() is called to perform the SPL task.
>
> lowlevel_init():
> - purpose: essential init to permit execution to reach board_init_f()
> - no global_data, but there is a stack
> - must not set up SDRAM or use console
> - must only do the bare minimum to allow execution to continue to
> board_init_f()
> - this is almost never needed
> - return normally from this function
>
> board_init_f():
> - purpose: set up the machine ready for running board_init_r():
> i.e. SDRAM and serial UART
> - global_data is available
> - preloader_console_init() can be called here in extremis
> - stack is in SRAM
> - should set up SDRAM, and anything needed to make the UART work
> - these is no need to clear BSS, it will be done by crt0.S
> - must return normally from this function (don't call board_init_r()
> directly)
>
> Here the BSS is cleared. If CONFIG_SPL_STACK_R is defined, then at this point
> the stack and global_data are relocated to below that address.
>
> board_init_r():
> - purpose: main execution, common code
> - global_data is available
> - SDRAM is available
> - stack is optionally in SDRAM, if CONFIG_SPL_STACK_R is defined and
> points into SDRAM
> - preloader_console_init() can be called here - typically this is
> done by defining CONFIG_SPL_BOARD_INIT and then supplying a
> spl_board_init() function containing this call
> - loads U-Boot or (in falcon mode) Linux
>
> Note: This patch is intended to apply over the top of Tom's SPL changes and
> this series:
>
> https://patchwork.ozlabs.org/patch/423785/
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Stefan Roese <sr@denx.de>
Thanks,
Stefan
next prev parent reply other threads:[~2015-01-19 7:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 18:55 [U-Boot] [PATCH] arm: spl: Allow board_init_r() to run with a larger stack Simon Glass
2015-01-19 6:46 ` Heiko Schocher
2015-01-19 19:38 ` Simon Glass
2015-01-21 14:11 ` Heiko Schocher
2015-01-19 6:54 ` Albert ARIBAUD
2015-01-19 19:39 ` Simon Glass
2015-01-20 6:46 ` Albert ARIBAUD
2015-01-19 7:08 ` Stefan Roese [this message]
2015-01-19 7:31 ` Stefano Babic
2015-01-21 9:48 ` Bo Shen
2015-01-21 10:51 ` Masahiro Yamada
2015-01-21 15:51 ` Simon Glass
2015-01-21 17:12 ` Masahiro YAMADA
2015-01-21 17:38 ` Simon Glass
2015-01-22 6:28 ` Heiko Schocher
2015-01-22 7:33 ` Masahiro Yamada
2015-01-22 15:10 ` Simon Glass
2015-01-23 13:53 ` Masahiro Yamada
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54BCAD7B.6040804@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox