Skip to content

GitLab

Switch branch/tag
History Find file
Clone
SPMD: extract SPMC DTB header size from SPMD
Olivier Deprez authored 
Currently BL2 passes TOS_FW_CONFIG address and size through registers to
BL31. This corresponds to SPMC manifest load address and size. The SPMC
manifest is mapped in BL31 by dynamic mapping. This patch removes BL2
changes from generic code (which were enclosed by SPD=spmd) and retrieves
SPMC manifest size directly from within SPMD. The SPMC manifest load
address is still passed through a register by generic code.
Signed-off-by: default avatarOlivier Deprez <olivier.deprez@arm.com>
Change-Id: I35c5abd95c616ae25677302f0b1d0c45c51c042f
23d5ba86
Name Last commit Last update
bl1 linker_script: move .data section to bl_common.ld.h
bl2 linker_script: move .data section to bl_common.ld.h
bl2u linker_script: move .data section to bl_common.ld.h
bl31 linker_script: move .data section to bl_common.ld.h
bl32 linker_script: move .data section to bl_common.ld.h
common SPMD: extract SPMC DTB header size from SPMD
docs doc: Add binding document for fconf.
drivers plat/stm32: Use generic fdt_get_reg_props_by_name()
fdts fdts: a5ds: Fix for the system timer issue.
include SPMD: extract SPMC DTB header size from SPMD
lib Merge changes I85eb75cf,Ic6d9f927 into integration
make_helpers Enable MTE support
plat SPMD: extract SPMC DTB header size from SPMD
services SPMD: extract SPMC DTB header size from SPMD
tools Merge changes from topic "sb/dualroot" into integration
.checkpatch.conf Re-apply GIT_COMMIT_ID check for checkpatch
.editorconfig doc: Final, pre-release fixes and updates
.gitignore Ignore the ctags file
.gitreview Specify integration as the default branch for git-review
Makefile Fix build type is empty in version string
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
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.