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

Merge "docs: update feature support overview" into integration

Browse source
This commit is contained in:
Madhukar Pappireddy 2023-05-22 14:43:02 +02:00 • committed by TrustedFirmware Code Review
commit d386d53d5c
1 changed files with 31 additions and 27 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

58
docs/about/features.rst
View file

@ -22,8 +22,8 @@ Current features
Cache Coherent Network (CCN), Network Interconnect (NIC) and TrustZone Cache Coherent Network (CCN), Network Interconnect (NIC) and TrustZone
Controller (TZC). Controller (TZC).
- A generic |SCMI| driver to interface with conforming power controllers, for - Secure Monitor library code such as world switching, EL2/EL1 context
example the Arm System Control Processor (SCP). management and interrupt routing.
- SMC (Secure Monitor Call) handling, conforming to the `SMC Calling - SMC (Secure Monitor Call) handling, conforming to the `SMC Calling
Convention`_ using an EL3 runtime services framework. Convention`_ using an EL3 runtime services framework.
@ -34,14 +34,22 @@ Current features
is also suitable for integration with other AArch32 EL3 Runtime Software, is also suitable for integration with other AArch32 EL3 Runtime Software,
for example an AArch32 Secure OS. for example an AArch32 Secure OS.
- A generic |SCMI| driver to interface with conforming power controllers, for
example the Arm System Control Processor (SCP).
- A minimal AArch32 Secure Payload (*SP_MIN*) to demonstrate |PSCI| library - A minimal AArch32 Secure Payload (*SP_MIN*) to demonstrate |PSCI| library
integration with AArch32 EL3 Runtime Software. integration with AArch32 EL3 Runtime Software.
- Secure Monitor library code such as world switching, EL1 context management - Secure partition manager dispatcher(SPMD) with following two configurations:
and interrupt routing.
When a Secure-EL1 Payload (SP) is present, for example a Secure OS, the - S-EL2 SPMC implementation, widely compliant with FF-A v1.1 EAC0 and initial
AArch64 EL3 Runtime Software must be integrated with a Secure Payload support of FF-A v1.2.
Dispatcher (SPD) component to customize the interaction with the SP.
- EL3 SPMC implementation, compliant with a subset of FF-A v1.1 EAC0.
- Support for Arm CCA based on FEAT_RME which supports authenticated boot and
execution of RMM with the necessary routing of RMI commands as specified in
RMM Beta 0 Specification.
- A Test SP and SPD to demonstrate AArch64 Secure Monitor functionality and SP - A Test SP and SPD to demonstrate AArch64 Secure Monitor functionality and SP
interaction with PSCI. interaction with PSCI.
@ -50,12 +58,20 @@ Current features
`Trusty Secure OS`_ and `ProvenCore Secure OS`_. `Trusty Secure OS`_ and `ProvenCore Secure OS`_.
- A Trusted Board Boot implementation, conforming to all mandatory TBBR - A Trusted Board Boot implementation, conforming to all mandatory TBBR
requirements. This includes image authentication, Firmware Update (or requirements. This includes image authentication, Firmware recovery,
recovery mode), and packaging of the various firmware images into a Firmware encryption and packaging of the various firmware images into a
Firmware Image Package (FIP). Firmware Image Package (FIP).
- Pre-integration of TBB with the Arm CryptoCell product, to take advantage of - Measured boot support with PoC to showcase its interaction with firmware TPM
its hardware Root of Trust and crypto acceleration services. (fTPM) service implemneted on top of OP-TEE.
- Support for Dynamic Root of Trust for Measurement (DRTM).
- Following firmware update mechanisms available:
- PSA Firmware Update (PSA FWU)
- TBBR Firmware Update (TBBR FWU)
- Reliability, Availability, and Serviceability (RAS) functionality, including - Reliability, Availability, and Serviceability (RAS) functionality, including
@ -81,6 +97,8 @@ Current features
secure system processor, or where a non-TF-A ROM expects BL2 to be loaded secure system processor, or where a non-TF-A ROM expects BL2 to be loaded
at EL3. at EL3.
- Support for Errata management firmware interface.
- Support for the GCC, LLVM and Arm Compiler 6 toolchains. - Support for the GCC, LLVM and Arm Compiler 6 toolchains.
- Support for combining several libraries into a "romlib" image that may be - Support for combining several libraries into a "romlib" image that may be
@ -88,27 +106,13 @@ Current features
in ROM but is accessed through a jump-table that may be stored in ROM but is accessed through a jump-table that may be stored
in read-write memory, allowing for the library code to be patched. in read-write memory, allowing for the library code to be patched.
- Support for the Secure Partition Manager Dispatcher (SPMD) component as a - Position-Independent Executable (PIE) support.
new standard service.
- Support for ARMv8.3 pointer authentication in the normal and secure worlds.
The use of pointer authentication in the normal world is enabled whenever
architectural support is available, without the need for additional build
flags.
- Position-Independent Executable (PIE) support. Currently for BL2, BL31, and
TSP, with further support to be added in a future release.
Still to come Still to come
------------- -------------
- Support for additional platforms. - Support for additional platforms.
- Refinements to Position Independent Executable (PIE) support.
- Continued support for the FF-A v1.0 (formally known as SPCI) specification, to enable the
use of secure partition management in the secure world.
- Documentation enhancements. - Documentation enhancements.
- Ongoing support for new architectural features, CPUs and System IP. - Ongoing support for new architectural features, CPUs and System IP.
@ -125,4 +129,4 @@ Still to come
-------------- --------------
*Copyright (c) 2019-2021, Arm Limited. All rights reserved.* *Copyright (c) 2019-2023, Arm Limited. All rights reserved.*