Skip to content

Commit ba9eaee

Browse files
committed
chapter3: require FF-A compatible with v1.2
On AArch64, when FF-A is implemented, require compatibility with FF-A v1.2. Suggested-by: Achin Gupta <[email protected]> Signed-off-by: Vincent Stehlé <[email protected]>
1 parent 3aa8301 commit ba9eaee

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

source/chapter3-secureworld.rst

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,24 @@ It is recommended that firmware implements PSCI version 1.0 or later
3535
.. [#SMCCCNote] Starting with SMCCC version 1.1, support for the `SMCCC_VERSION`
3636
function is required, for standardized discovery.
3737
38+
AArch64 Firmware Framework
39+
==========================
40+
41+
On AArch64 platforms, when privileged or secure firmware implements the Firmware
42+
Framework for A-profile (FF-A), it must conform to the Arm Firmware Framework
43+
for Arm A-profile specification [FFA]_ and it must support at least one callee
44+
version compatible with caller version 1.2. [#FFANote]_
45+
46+
.. [#FFANote] FF-A is an Arm software architecture describing interfaces that
47+
standardize communication between software images and firmware, in the Secure
48+
world and the Normal world.
49+
FF-A v1.2 introduced support for multiple services UUIDs in a partition,
50+
which eases services discovery, as well as the supporting
51+
`FFA_MSG_SEND_DIRECT_REQ2` ABI.
52+
As per the FF-A specification § 13.2.1 Overview, all callee versions 1.x,
53+
with x >= 2, are compatible with caller versions 1.0 to 1.x, which includes
54+
caller version 1.2.
55+
3856
RISC-V Multiprocessor Startup Protocol
3957
======================================
4058

0 commit comments

Comments
 (0)