commit | b727aab1b407e626eb10b1bad33e64107304d80b | [log] [tgz] |
---|---|---|
author | Balint Dobszay <balint.dobszay@arm.com> | Mon Apr 07 10:24:59 2025 +0200 |
committer | Bálint Dobszay <balint.dobszay@arm.com> | Wed Apr 09 13:01:39 2025 +0200 |
tree | 9e08894c26763eddf10e817e8b2f5cd638825f0c | |
parent | e6fe75f8ae12169a4b2c58a52337181d604bbe14 [diff] |
Add argument for FFA_ERROR Add a new field to Interface::Error to pass the contents of w3/x3 for the FFA_ERROR interface. This is currently only valid when returning RETRY error for FFA_CONSOLE_LOG, MBZ otherwise. Signed-off-by: Balint Dobszay <balint.dobszay@arm.com> Change-Id: I8ecfb2057d5cd130c671087941c96342f8074d27
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).