docs/components/ffa-manifest-binding.rst

16      minor versions of the device tree binding for the FFA manifest represented
20       - X is an integer representing the major version number of this document.
21       - Y is an integer representing the minor version number of this document.
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
35    - An array of comma separated tuples each consisting of 4 <u32> values,
36      identifying the UUID of the services implemented by this partition.
53    - Name of the partition e.g. for debugging purposes.
57    - Number of vCPUs that a VM or SP wants to instantiate.
59       - In the absence of virtualization, this is the number of execution
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.
76    - The target execution state of the partition:
83    - Physical base address of the partition in memory. Absence of this field
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.
127    - This field is deprecated in favor of ns-interrupts-action field in the FF-A
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
189      Presence of this field indicates that the partition expects the address of
196      A set bit means the partition should be informed of the power event, clear
197      bit - should not be informed of event:
206      bit means the partition should be informed of the event, clear bit - should
207      not be informed of event:
214    - Presence of this field indicates support for all partition lifecycle states
241    - Name of the memory region e.g. for debugging purposes.
245    - Count of pages of memory region as a multiple of the translation granule
259    - Base address of the region. The address must be aligned to the translation
265      region of the specified size into the partition's translation regime and
271    - Offset relative to the load address of the partition.
273      load address to get the base address of the region. The secure partition
279    - List of IDs belonging to a DMA capable peripheral device that has access to
290    - List of attributes representing the instruction and data access permissions
305    - Name of the device region e.g. for debugging purposes.
309    - Count of pages of memory region as a multiple of the translation granule
323    - Base address of the region. The address must be aligned to the translation
333      upstream of. If the field is omitted then it is assumed that the device is
334      not upstream of any SMMU.
338    - List of IDs where an ID is a unique <u32> value amongst all devices assigned
343    - A list of (id, attributes) pair describing the device interrupts, where:
375    - A list of (id, mpdir upper bits, mpidr lower bits) tuples describing which
378       - id: The <u32> interrupt ID. Must be one of those specified in the
380       - mpidr upper bits: The <u32> describing the upper bits of the 64 bits
382       - mpidr lower bits: The <u32> describing the lower bits of the 64 bits
387    - Presence of this field implies that this endpoint must be granted exclusive
388      access and ownership of this device's MMIO region.
404    - Major of the FF-A version implemented by the SPMC. SPMD checks against its own
408    - Minor of the FF-A version implemented by the SPMC. SPMD checks against its own
422    - Defines the maximum size of the SPMC binary. It is used with load_address to sanitize the