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

docs: remove PSA wording for SPM chapters

Browse source 
PSA wording is not longer associated with FF-A.

Change-Id: Id7c53b9c6c8f383543f6a32a15eb15b7749d8658
Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
This commit is contained in:
Olivier Deprez 2021-04-21 11:22:23 +02:00
parent 08e7cc533e
commit 1b17f4f1f8
5 changed files with 15 additions and 17 deletions

4
docs/about/features.rst
View file

@ -108,7 +108,7 @@ Still to come
- Refinements to Position Independent Executable (PIE) support.
- Continued support for the PSA FF-A v1.0 (formally known as SPCI) specification, to enable the
- 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.
@ -126,4 +126,4 @@ Still to come
--------------
*Copyright (c) 2019-2020, Arm Limited. All rights reserved.*
*Copyright (c) 2019-2021, Arm Limited. All rights reserved.*

8
docs/components/psa-ffa-manifest-binding.rst → docs/components/ffa-manifest-binding.rst
View file

@ -1,8 +1,8 @@
PSA FF-A manifest binding to device tree
FF-A manifest binding to device tree
========================================
This document defines the nodes and properties used to define a partition,
according to the PSA FF-A specification.
according to the FF-A specification.
Version 1.0
-----------
@ -25,9 +25,9 @@ Partition Properties
- Must be two 16 bits values (X, Y), concatenated as 31:16 -> X,
15:0 -> Y, where:
- X is the major version of PSA-FF-A expected by the partition at the FFA
- X is the major version of FF-A expected by the partition at the FFA
instance it will execute.
- Y is the minor version of PSA-FF-A expected by the partition at the FFA
- Y is the minor version of FF-A expected by the partition at the FFA
instance it will execute.
- uuid [mandatory]

2
docs/components/index.rst
View file

@ -19,6 +19,6 @@ Components
sdei
secure-partition-manager
secure-partition-manager-mm
psa-ffa-manifest-binding
ffa-manifest-binding
xlat-tables-lib-v2-design
cot-binding

4
docs/components/secure-partition-manager-mm.rst
View file

@ -6,7 +6,7 @@ Foreword
Two implementations of a Secure Partition Manager co-exist in the TF-A codebase:
- SPM based on the PSA FF-A specification (:ref:`Secure Partition Manager`).
- SPM based on the FF-A specification (:ref:`Secure Partition Manager`).
- SPM based on the MM interface.
Both implementations differ in their architectures and only one can be selected
@ -822,7 +822,7 @@ Error Codes
--------------
*Copyright (c) 2017-2020, Arm Limited and Contributors. All rights reserved.*
*Copyright (c) 2017-2021, Arm Limited and Contributors. All rights reserved.*
.. _Armv8-A ARM: https://developer.arm.com/docs/ddi0487/latest/arm-architecture-reference-manual-armv8-for-armv8-a-architecture-profile
.. _instructions in the EDK2 repository: https://github.com/tianocore/edk2-staging/blob/AArch64StandaloneMm/HowtoBuild.MD

14
docs/components/secure-partition-manager.rst
View file

@ -33,8 +33,6 @@ Acronyms
+--------+-----------------------------------+
| PVM | Primary VM |
+--------+-----------------------------------+
| PSA | Platform Security Architecture |
+--------+-----------------------------------+
| SMMU | System Memory Management Unit |
+--------+-----------------------------------+
| SP | Secure Partition |
@ -61,7 +59,7 @@ Foreword
Two implementations of a Secure Partition Manager co-exist in the TF-A codebase:
- SPM based on the PSA FF-A specification `[1]`_.
- SPM based on the FF-A specification `[1]`_.
- SPM based on the MM interface to communicate with an S-EL0 partition `[2]`_.
Both implementations differ in their architectures and only one can be selected
@ -69,7 +67,7 @@ at build time.
This document:
- describes the PSA FF-A implementation where the Secure Partition Manager
- describes the FF-A implementation where the Secure Partition Manager
resides at EL3 and S-EL2 (or EL3 and S-EL1).
- is not an architecture specification and it might provide assumptions
on sections mandated as implementation-defined in the specification.
@ -565,7 +563,7 @@ either *(under discussion)*:
- Re-purposing the ``PSCI_CPU_ON`` function id. It is
assumed that even if the input arguments are the same as the ones defined in
the PSCI standard, the usage deviates by the fact the secondary EC is not
woken up immediately. At least for the PSA-FF-A EAC where only
woken up immediately. At least for the FF-A EAC where only
direct messaging is allowed, it is only after the first direct
message invocation that the secondary EC is entered. This option
might be preferred when the same code base is re-used for a VM or
@ -949,7 +947,7 @@ References
.. _[1]:
[1] `Platform Security Architecture Firmware Framework for Arm® v8-A 1.0 Platform Design Document <https://developer.arm.com/docs/den0077/latest>`__
[1] `Arm Firmware Framework for Armv8-A <https://developer.arm.com/docs/den0077/latest>`__
.. _[2]:
@ -970,7 +968,7 @@ Client <https://developer.arm.com/docs/den0006/latest/trusted-board-boot-require
.. _[6]:
[6] https://trustedfirmware-a.readthedocs.io/en/latest/components/psa-ffa-manifest-binding.html
[6] https://trustedfirmware-a.readthedocs.io/en/latest/components/ffa-manifest-binding.html
.. _[7]:
@ -982,4 +980,4 @@ Client <https://developer.arm.com/docs/den0006/latest/trusted-board-boot-require
--------------
*Copyright (c) 2020, Arm Limited and Contributors. All rights reserved.*
*Copyright (c) 2020-2021, Arm Limited and Contributors. All rights reserved.*