summaryrefslogtreecommitdiff
path: root/src/drivers/emulation/Kconfig
diff options
context:
space:
mode:
authorJulius Werner <jwerner@chromium.org>2014-11-25 13:22:20 -0800
committerPatrick Georgi <pgeorgi@google.com>2015-04-13 17:21:17 +0200
commitf1e321001d5954096f06f9a43138219a9a46536e (patch)
tree55622593340f5a4332505ee25b87e8c1d9bc25db /src/drivers/emulation/Kconfig
parenta512e117b0a550e8d8c8a13e74ebbf971614ebee (diff)
arm: Add bootblock_mainboard_early_init() for pre-console initialization
On most platforms, enabling the console and exception handlers are amongst the very first things you want to do, as they help you see what's going on and debug errors in other early init code. However, most ARM boards require some small amount of board-specific initialization (pinmuxing, maybe clocks) to get the UART running, which is why bootblock_mainboard_init() (and with it almost all of the actual bootblock code) always had to run before console initialization for now. This patch introduces an explicit bootblock_mainboard_early_init() hook for only that part of initialization that absolutely needs to run before console output. The other two hooks for SoC and mainboard are moved below console_init(). This model has already proven its worth before in the tegra124 and tegra132 custom bootblocks. BRANCH=None BUG=chrome-os-partner:32123 TEST=Booted on Pinky. Compiled for Daisy, Storm and Ryu. Change-Id: I510c58189faf0c08c740bcc3b5a654f81f892464 Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Original-Commit-Id: f58e84a2fc1c9951e9c4c65cdec1dbeb6a20d597 Original-Change-Id: I4257b5a8807595140e8c973ca04e68ea8630bf9a Original-Signed-off-by: Julius Werner <jwerner@chromium.org> Original-Reviewed-on: https://chromium-review.googlesource.com/231941 Reviewed-on: http://review.coreboot.org/9603 Tested-by: build bot (Jenkins) Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
Diffstat (limited to 'src/drivers/emulation/Kconfig')
0 files changed, 0 insertions, 0 deletions