features.rst 6.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154
  1. Feature Overview
  2. ================
  3. This page provides an overview of the current |TF-A| feature set. For a full
  4. description of these features and their implementation details, please see
  5. the documents that are part of the *Components* and *System Design* chapters.
  6. The :ref:`Change Log & Release Notes` provides details of changes made since the
  7. last release.
  8. Current features
  9. ----------------
  10. - Initialization of the secure world, for example exception vectors, control
  11. registers and interrupts for the platform.
  12. - Library support for CPU specific reset and power down sequences. This
  13. includes support for errata workarounds and the latest Arm DynamIQ CPUs.
  14. - Drivers to enable standard initialization of Arm System IP, for example
  15. Generic Interrupt Controller (GIC), Cache Coherent Interconnect (CCI),
  16. Cache Coherent Network (CCN), Network Interconnect (NIC) and TrustZone
  17. Controller (TZC).
  18. - Secure Monitor library code such as world switching, EL2/EL1 context
  19. management and interrupt routing.
  20. - SMC (Secure Monitor Call) handling, conforming to the `SMC Calling
  21. Convention`_ using an EL3 runtime services framework.
  22. - |PSCI| library support for CPU, cluster and system power management
  23. use-cases.
  24. This library is pre-integrated with the AArch64 EL3 Runtime Software, and
  25. is also suitable for integration with other AArch32 EL3 Runtime Software,
  26. for example an AArch32 Secure OS.
  27. - A generic |SCMI| driver to interface with conforming power controllers, for
  28. example the Arm System Control Processor (SCP).
  29. - A minimal AArch32 Secure Payload (*SP_MIN*) to demonstrate |PSCI| library
  30. integration with AArch32 EL3 Runtime Software.
  31. - Secure partition manager dispatcher(SPMD) with following two configurations:
  32. - S-EL2 SPMC implementation, widely compliant with FF-A v1.1 EAC0 and initial
  33. support of FF-A v1.2.
  34. - EL3 SPMC implementation, compliant with a subset of FF-A v1.1 EAC0.
  35. - Support for Arm CCA based on FEAT_RME which supports authenticated boot and
  36. execution of RMM with the necessary routing of RMI commands as specified in
  37. RMM Beta 0 Specification.
  38. - A Test SP and SPD to demonstrate AArch64 Secure Monitor functionality and SP
  39. interaction with PSCI.
  40. - SPDs for the `OP-TEE Secure OS`_, `NVIDIA Trusted Little Kernel`_,
  41. `Trusty Secure OS`_ and `ProvenCore Secure OS`_.
  42. - A Trusted Board Boot implementation, conforming to all mandatory TBBR
  43. requirements. This includes image authentication, Firmware recovery,
  44. Firmware encryption and packaging of the various firmware images into a
  45. Firmware Image Package (FIP).
  46. - Measured boot support with PoC to showcase its interaction with firmware TPM
  47. (fTPM) service implemneted on top of OP-TEE.
  48. - Support for Dynamic Root of Trust for Measurement (DRTM).
  49. - Following firmware update mechanisms available:
  50. - PSA Firmware Update (PSA FWU)
  51. - TBBR Firmware Update (TBBR FWU)
  52. - Reliability, Availability, and Serviceability (RAS) functionality, including
  53. - A Secure Partition Manager (SPM) to manage Secure Partitions in
  54. Secure-EL0, which can be used to implement simple management and
  55. security services.
  56. - An |SDEI| dispatcher to route interrupt-based |SDEI| events.
  57. - An Exception Handling Framework (EHF) that allows dispatching of EL3
  58. interrupts to their registered handlers, to facilitate firmware-first
  59. error handling.
  60. - A dynamic configuration framework that enables each of the firmware images
  61. to be configured at runtime if required by the platform. It also enables
  62. loading of a hardware configuration (for example, a kernel device tree)
  63. as part of the FIP, to be passed through the firmware stages.
  64. This feature is now incorporated inside the firmware configuration framework
  65. (fconf).
  66. - Support for alternative boot flows, for example to support platforms where
  67. the EL3 Runtime Software is loaded using other firmware or a separate
  68. secure system processor, or where a non-TF-A ROM expects BL2 to be loaded
  69. at EL3.
  70. - Support for Errata management firmware interface.
  71. - Support for the GCC, LLVM and Arm Compiler 6 toolchains.
  72. - Support for combining several libraries into a "romlib" image that may be
  73. shared across images to reduce memory footprint. The romlib image is stored
  74. in ROM but is accessed through a jump-table that may be stored
  75. in read-write memory, allowing for the library code to be patched.
  76. - Position-Independent Executable (PIE) support.
  77. Experimental features
  78. ---------------------
  79. A feature is considered experimental when still in development or isn't known
  80. to the TF-A team as widely deployed or proven on end products. It is generally
  81. advised such options aren't pulled into real deployments, or done with the
  82. appropriate level of supplementary integration testing.
  83. A feature is no longer considered experimental when it is generally agreed
  84. the said feature has reached a level of maturity and quality comparable to
  85. other features that have been integrated into products.
  86. Experimental build options are found in following section
  87. :ref:`build_options_experimental`. Their use through the build emits a warning
  88. message.
  89. Additionally the following libraries are marked experimental when included
  90. in a platform:
  91. - MPU translation library ``lib/xlat_mpu``
  92. - RSE comms driver ``drivers/arm/rse``
  93. Still to come
  94. -------------
  95. - Support for additional platforms.
  96. - Documentation enhancements.
  97. - Ongoing support for new architectural features, CPUs and System IP.
  98. - Ongoing support for new Arm system architecture specifications.
  99. - Ongoing security hardening, optimization and quality improvements.
  100. .. _SMC Calling Convention: https://developer.arm.com/docs/den0028/latest
  101. .. _OP-TEE Secure OS: https://github.com/OP-TEE/optee_os
  102. .. _NVIDIA Trusted Little Kernel: http://nv-tegra.nvidia.com/gitweb/?p=3rdparty/ote_partner/tlk.git;a=summary
  103. .. _Trusty Secure OS: https://source.android.com/security/trusty
  104. .. _ProvenCore Secure OS: https://provenrun.com/products/provencore/
  105. --------------
  106. *Copyright (c) 2019-2023, Arm Limited. All rights reserved.*