From 31dcf2345172de50b098d7a080c65ee6faa87df8 Mon Sep 17 00:00:00 2001 From: Nishant Sharma Date: Fri, 13 Oct 2023 11:23:50 +0100 Subject: [PATCH] feat(docs): save BL32 image base and size in entry point info 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 Change-Id: I35527fb41829102083b488a5150c0c707c5ede15 --- docs/design/firmware-design.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/design/firmware-design.rst b/docs/design/firmware-design.rst index ff69b43cf..3fce39395 100644 --- a/docs/design/firmware-design.rst +++ b/docs/design/firmware-design.rst @@ -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.