Require FF-A compatibility with v1.2 #138
Conversation
Add a reference to the FF-A specification v1.3 ALP1, to prepare adding requirements around FF-A. Signed-off-by: Vincent Stehlé <[email protected]>
|
As of today, U-Boot wants (caller) FF-A v1.0. |
|
@vstehle "The Arm Firmware Framework for Armv8-A (FF-A) specifies the management of secure partitions and APIs for the communication with these." Including your remark concerning backwards compatibility would also be helpful. |
Sure @xypron; how about adding the following instead? "The Firmware Framework for A-profile (FF-A) is an Arm software architecture describing interfaces that standardize communication between software images and firmware, in the Secure world and the Normal world." Let me know if you are ok putting it in the note only, to keep it clearly separate from the requirements, or if you prefer it as the first sentence of the "AArch64 Firmware Framework" section instead.
Ok, will do. |
|
Added a bit more details in the note regarding versions compatibility, to encompass the actual U-Boot case of caller version 1.0 and callee version 1.2. |
|
As of today EDK II requests FF-A (caller) v1.2. |
Thanks @xypron for the review! |
|
As of today Xen requests FF-A (caller) v1.1. Also, Xen implements "only" FF-A (callee) v1.1 but support for v1.2 is due soon (thanks @bertrand-marquis). |
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]>
|
I added the FF-A introductory sentence to the note. |
|
Today OP-TEE implements FF-A (callee) v1.2 but only v1.1 when Xen is there (this should change soon). |
This is a start at adding requirements on FF-A.
We start by requiring compatibility with v1.2, the version recommended by @achingupta. This is only on AArch64 and only when FF-A is actually implemented.
In the future, we will add more FF-A requirements to support use cases such as TPM-over-FF-A, Virtio-over-FF-A for virtualized environments, etc.