docs/components/el3-spmc.rst

40   providing SP description. It is required when
46 - BL32 option is re-purposed to specify the S-EL1 TEE or SP image.
47   BL32 option can be omitted if using TF-A Test Secure Payload as SP.
145 Parsing SP partition manifests
148 SPMC consumes the SP manifest, as defined in `[7]`_.
149 SP manifest fields align with Hafnium SP manifest for easy porting.
166 Passing boot data to the SP
172 exchanged between SPMC and SP.
182 BLOB contains Boot Info Header, followed by SP Manifest contents.
184 The configuration of the boot protocol is done in the SP manifest. As defined by
228 SPMC asserts SP and SPMC are at same FF-A Version.
266 - from SP to SPMC
274 All LSPs and SP are discoverable from FFA_PARTITION_INFO_GET call made by
275 either SP or NWd entities.
292 - A VM-to-SP direct request/response shall set the origin world to be non-secure
295 - Similarly, an SP-to-LSP direct request/response shall set the FF-A ID bit 15
303 An SP sending a direct message request must have bit 15 set in its origin
304 endpoint ID and this can be checked by the SPMC when the SP invokes the ABI.
311 -  or initiated by an SP and thus origin endpoint ID must be a "secure world ID".
323 - An SP can send a direct request to LSP.
324 - An LSP can send a direct response to SP.
325 - An SP cannot send a direct request to an Hypervisor or OS kernel.
326 - An Hypervisor or OS kernel can send a direct request to an SP or LSP.
327 - An SP and LSP can send a direct response to an Hypervisor or OS kernel.
357 - If SP is borrower in the memory transaction, these calls are forwarded to SPMC.
371 - Memory retrieve is supported only from SP.
373 - Performs Relayer responsiilities and sends FFA_MEM_RETRIEVE_RESP back to SP.
385 - SP if FFA_MEM_RETRIEVE_RESP returned descriptor with fragment length less than total length.
426 secure partitions. For this a VM (Hypervisor or OS kernel), or SP invokes one of:
439 An SP can be in one of the following state:
446 An SP will transition to one of the following runtime model when not in waiting state:
456 SPMC only supports a single Pinned MP S-EL1 SP. The *execution-ctx-count*
457 SP manifest field should match the number of physical PE.
465 - SPMC is capable of forwarding Secure interrupt to S-EL1 SP
467 - Interrupt is forwarded to SP using FFA_INTERRUPT interface.
468 - Interrupt Number is not passed, S-EL1 SP can access the GIC registers directly.
469 - Upon completion of Interrupt handling SP is expected to return to
487   - SP initialization on all CPUs.
503         Test: Echo Message to SP.
507         Test: Message Relay vis SP to EL3 LSP.