commit | e6aa4865e8b087254de66c531ca5e7e3f91fd4ca | [log] [tgz] |
---|---|---|
author | Balint Dobszay <balint.dobszay@arm.com> | Fri Feb 28 16:37:56 2025 +0100 |
committer | Balint Dobszay <balint.dobszay@arm.com> | Mon Mar 03 20:29:04 2025 +0100 |
tree | 8802d1e05d9183555398c51e62e9dbb72450e2c2 | |
parent | de0dc80d2e1a59ec8616495ae58a15911f036d20 [diff] |
Add missing FF-A function IDs Add every missing FF-A function ID that has been specified in FF-A v1.1 and v1.2. Note that this patch doesn't actually implement handling of these, just extends the function ID enum so the FFA_VERSION interface can always get parsed if it contains a valid function ID. Signed-off-by: Balint Dobszay <balint.dobszay@arm.com> Change-Id: I88b63643ee267f73170c654a340711a9b0db3a56
Arm Firmware Framework for Arm A-profile (FF-A) specification
FF-A Memory Management Protocol specification
Library for handling common FF-A related functionality, create and parse interfaces and descriptors defined by FF-A. Starting from FF-A v1.2 the memory management related parts of the specification have been moved to a separate document (link above).
thiserror
) so the library user knows what's wrong.ffa_v1_1
and later modules).zerocopy
traits.The FF-A specification allows different components of a system to use different versions of the specification. The version used at a specific FF-A instance (i.e. an interface between two FF-A components) is discovered at runtime, either by parsing FF-A manifests or using FFA_VERSION
. An FF-A component might have to use multiple versions at runtime on its different interfaces, therefore this library must be able to support this and having a compile time fixed version is not possible. Because of this, most of the functions to create or parse FF-A messages and data structures require passing the FF-A version used at the instance where the serialized data was received from or will be sent to.
FFA_MEM_*
interfaces (partial).The project is MIT and Apache-2.0 dual licensed, see LICENSE-APACHE
and LICENSE-MIT
.
arm-ffa is a trustedfirmware.org maintained project. All contributions are ultimately merged by the maintainers listed below.
Please follow the directions of the Trusted Firmware Processes
Contributions are handled through review.trustedfirmware.org.
Please follow the directions of the Trusted Firmware Security Center
Copyright 2025 Arm Limited and/or its affiliates open-source-office@arm.com
Arm is a registered trademark of Arm Limited (or its subsidiaries or affiliates).