services: spm_mm: Use sp_boot_info to set SP context
Mayur Gudmeti authored
The current SPM_MM implementations expects the SP image addresses
as static macros. This means platforms wanting to use dynamically
allocated memory addresses are left out. This patch gets sp_boot_info
at the beginning of spm_sp_setup function and uses member variables
of sp_boot_info to setup the context. So member variables of
struct sp_boot_info and consequently the context can be initialized
by static macros or dynamiclly allocated memory address..

Change-Id: I1cb75190ab8026b845ae20a9c6cc416945b5d7b9
Signed-off-by: default avatarMayur Gudmeti <mgudmeti@nvidia.com>
21583a31
Name Last commit Last update
bl1 Add support for FEAT_MTPMU for Armv8.6
bl2 Add support for FEAT_MTPMU for Armv8.6
bl2u linker_script: move .data section to bl_common.ld.h
bl31 Add TRNG Firmware Interface service
bl32 bl32: Enable TRNG service build
common fdt: Use proper #address-cells and #size-cells for reserved-memory
docs docs: Update Mbed TLS supported version
drivers Merge changes from topic "dcc_console" into integration
fdts tc0: update GICR base address
include Merge changes from topic "scmi_v2_0" into integration
lib Merge "lib/cpu: Workaround for Cortex A77 erratum 1946167" into integration
make_helpers tbbr-tools: enable override TRUSTED_KEY_CERT
plat Merge changes from topic "scmi_v2_0" into integration
services services: spm_mm: Use sp_boot_info to set SP context
tools fiptool: Do not call 'make clean' in 'all' target
.checkpatch.conf Re-apply GIT_COMMIT_ID check for checkpatch
.editorconfig .editorconfig: set max line length to 100
.gitignore tools: renesas: Add tool support for RZ/G2 platforms
.gitreview Specify integration as the default branch for git-review
Makefile Merge "fiptool: Do not print duplicate verbose lines about building fiptool" into integration
dco.txt Drop requirement for CLA in contribution.md
license.rst doc: De-duplicate readme and license files
readme.rst doc: Formatting fixes for readme.rst

Trusted Firmware-A

Trusted Firmware-A (TF-A) is a reference implementation of secure world software for Arm A-Profile architectures (Armv8-A and Armv7-A), including an Exception Level 3 (EL3) Secure Monitor. It provides a suitable starting point for productization of secure world boot and runtime firmware, in either the AArch32 or AArch64 execution states.

TF-A implements Arm interface standards, including:

The code is designed to be portable and reusable across hardware platforms and software models that are based on the Armv8-A and Armv7-A architectures.

In collaboration with interested parties, we will continue to enhance TF-A with reference implementations of Arm standards to benefit developers working with Armv7-A and Armv8-A TrustZone technology.

Users are encouraged to do their own security validation, including penetration testing, on any secure world code derived from TF-A.

More Info and Documentation

To find out more about Trusted Firmware-A, please view the full documentation that is available through trustedfirmware.org.


Copyright (c) 2013-2019, Arm Limited and Contributors. All rights reserved.