diff options
author | Roberto Vargas <roberto.vargas@arm.com> | 2017-12-12 10:39:44 +0000 |
---|---|---|
committer | Roberto Vargas <roberto.vargas@arm.com> | 2018-01-10 09:21:22 +0000 |
commit | 2a350dffedf2b8c2c33a2664afd4e59568a1070c (patch) | |
tree | ef990beca80a91c94357af3b16c26daff4824822 /docs | |
parent | 8d356425e5020a9e9dd31058f6916f811a36ec4b (diff) |
Add documentation about plat_try_next_boot_source to bl1_platform_setup
If boot redundancy is required in BL1 then the initialization
of the boot sequence must be done in bl1_platform_setup. In BL2,
we had to add a new function, bl2_preload_setup, because
bl2_platform_setup is called after the images are loaded, making it
invalid for the boot sequence initialization.
Change-Id: I5c177ff142608ed38b4192288b06614343b2b83b
Signed-off-by: Roberto Vargas <roberto.vargas@arm.com>
Diffstat (limited to 'docs')
-rw-r--r-- | docs/porting-guide.rst | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/porting-guide.rst b/docs/porting-guide.rst index f020ec97..402cc5d3 100644 --- a/docs/porting-guide.rst +++ b/docs/porting-guide.rst @@ -1128,6 +1128,9 @@ This function executes with the MMU and data caches enabled. It is responsible for performing any remaining platform-specific setup that can occur after the MMU and data cache have been enabled. +if support for multiple boot sources is required, it initializes the boot +sequence used by plat\_try\_next\_boot\_source(). + In ARM standard platforms, this function initializes the storage abstraction layer used to load the next bootloader image. |