Djam/arm-trusted-firmware
1
0
Fork 0
mirror of https://github.com/ARM-software/arm-trusted-firmware.git synced 2025-04-16 01:24:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

feat(docs): save BL32 image base and size in entry point info

Browse source 
There is no platform function to retrieve the info in the generic code.
Populate the BL32 image base, size and max limit in arg2, arg3 and arg4.

Signed-off-by: Nishant Sharma <nishant.sharma@arm.com>
Change-Id: I35527fb41829102083b488a5150c0c707c5ede15
This commit is contained in:
Nishant Sharma 2023-10-13 11:23:50 +01:00
parent 821b01fa75
commit 31dcf23451
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/design/firmware-design.rst
View file

@ -130,6 +130,12 @@ convention:
- For other BL3x images, if the firmware configuration file is loaded by
BL2, then its address is passed in ``arg0`` and if HW_CONFIG is loaded
then its address is passed in ``arg1``.
- In case SPMC_AT_EL3 is enabled, populate the BL32 image base, size and max
limit in the entry point information, since there is no platform function
to retrieve these in generic code. We choose ``arg2``, ``arg3`` and
``arg4`` since the generic code uses ``arg1`` for stashing the SP manifest
size. The SPMC setup uses these arguments to update SP manifest with
actual SP's base address and it size.
- In case of the Arm FVP platform, FW_CONFIG address passed in ``arg1`` to
BL31/SP_MIN, and the SOC_FW_CONFIG and HW_CONFIG details are retrieved
from FW_CONFIG device tree.