docs/components/ffa-manifest-binding.rst

4 This document defines the nodes and properties used to define a partition,
10 The FF-A partition manifest is consumed by the SPMC to configure the state
28       - X is the major version of FF-A expected by the partition at the FFA
30       - Y is the minor version of FF-A expected by the partition at the FFA
36      identifying the UUID of the services implemented by this partition.
45    - Pre-allocated partition ID.
53    - Name of the partition e.g. for debugging purposes.
60         contexts that a partition implements.
61       - If value of this field = 1 and number of PEs > 1 then the partition is
63       - If the value of this field > 1 then the partition is treated as a MP
64         capable partition irrespective of the number of PEs.
68    - The target exception level for the partition:
76    - The target execution state of the partition:
83    - Physical base address of the partition in memory. Absence of this field
84      indicates that the partition is position independent and can be loaded at
89    - Offset from the base of the partition's binary image to the entry point of
90      the partition. Absence of this field indicates that the entry point is at
91      offset 0x0 from the base of the partition's binary.
95    - Translation granule used with the partition:
103    - A unique number amongst all partitions that specifies if this partition
104      must be booted before others. The partition with the smaller number will be
110      by the partition.
115    - Specifies which messaging methods are supported by the partition, set bit
118       - Bit[0]: partition can receive direct requests via FFA_MSG_SEND_DIRECT_REQ ABI if set
119       - Bit[1]: partition can send direct requests via FFA_MSG_SEND_DIRECT_REQ ABI if set
120       - Bit[2]: partition can send and receive indirect messages
121       - Bit[9]: partition can receive direct requests via FFA_MSG_SEND_DIRECT_REQ2 ABI if set
122       - Bit[10]: partition can send direct requests via FFA_MSG_SEND_DIRECT_REQ2 ABI if set
132    - Indicates if the partition needs managed exit, if supported, to be signaled
174    - Presence of this field indicates that the partition implements the primary
179    - Presence of this field indicates that the partition doesn't expect the
180      partition manager to time slice long running memory management functions.
185      The width is derived from the partition's execution state, as specified in
186      the partition properties. For example, if the number value is 1 then the
189      Presence of this field indicates that the partition expects the address of
195    - Specifies which power management messages a partition subscribes to.
196      A set bit means the partition should be informed of the power event, clear
205    - Specifies which VM availability messages a partition subscribes to. A set
206      bit means the partition should be informed of the event, clear bit - should
214    - Presence of this field indicates support for all partition lifecycle states
219    - Specifies the action that the SPMC takes when a partition encounters a fatal
227    - All other values are unsupported. If a partition does not specify this
264      If the base address is omitted then the partition manager must map a memory
265      region of the specified size into the partition's translation regime and
267      by the partition manager) to the partition.
271    - Offset relative to the load address of the partition.
272      When this is provided in the partition manifest, it should be added to the
273      load address to get the base address of the region. The secure partition
332      identifier is used to inform the partition manager which SMMU the device is
339      to the partition.