"plat/git@web.lueluesay.top:root/arm-trusted-firmware.git" did not exist on "ad19911c72db1da8f05d4f846b15fb5386290493"
xilinx: versal: Add PM_INIT_FINALIZE API for versal
Tejas Patel authored
PM_INIT_FINALIZE is not required for versal. To use Linux
Zynqmp PM driver for versal, handle PM_INIT_FINALIZE API
in ATF for versal by always returning SUCCESS.
Signed-off-by: default avatarTejas Patel <tejas.patel@xilinx.com>
Signed-off-by: default avatarJolly Shah <jolly.shah@xilinx.com>
Change-Id: I6fe5445d78e713d70282ac8931ff8b17c96b2a14
ad19911c
Name Last commit Last update
bl1 Merge "PIE: make call to GDT relocation fixup generalized" into integration
bl2 Merge "PIE: make call to GDT relocation fixup generalized" into integration
bl2u Reduce space lost to object alignment
bl31 bl31: Split into two separate memory regions
bl32 pmf: Make the runtime instrumentation work on AArch32
common Refactor load_auth_image_internal().
docs Merge "bl31: Split into two separate memory regions" into integration
drivers drivers: add a driver for snoop control unit
fdts fdts: a5ds: cleanup enable-method in devicetree
include drivers: add a driver for snoop control unit
lib Workaround for Hercules erratum 1688305
make_helpers bl31: Split into two separate memory regions
plat xilinx: versal: Add PM_INIT_FINALIZE API for versal
services spm-mm: Rename aarch64 assembly files
tools tools: Add show_memory script
.checkpatch.conf Re-apply GIT_COMMIT_ID check for checkpatch
.editorconfig doc: Final, pre-release fixes and updates
.gitignore meson: Rename platform directory to amlogic
Makefile bl31: Split into two separate memory regions
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.