Lines Matching refs:request

577   receive a direct message request originating from any physical core targeting
666 It is possible for an SP to call into another SP through a direct request
847 The request made by an Hypervisor or OS kernel is forwarded to the SPMC and
875 - from Hypervisor or OS kernel to SPMC. The request is relayed by the SPMD.
898 - A VM-to-SP direct request/response shall set the origin world to be non-secure
901 - Similarly, an SP-to-SP direct request/response shall set the FF-A ID bit 15
904 An incoming direct message request arriving at SPMD from NWd is forwarded to
909 An SP sending a direct message request must have bit 15 set in its origin
923 This is a mandatory interface for secure partitions consisting in direct request
926 - An SP can send a direct request to another SP.
927 - An SP can receive a direct request from another SP.
929 - An SP cannot send a direct request to an Hypervisor or OS kernel.
930 - An Hypervisor or OS kernel can send a direct request to an SP.
1056 Using those IDs in source/destination fields of a direct request/response
1059 - SPMC to SPMD direct request/response uses SMC conduit.
1060 - SPMD to SPMC direct request/response uses ERET conduit.
1075 The ``FFA_MEM_RETRIEVE_REQ`` interface is for the borrower to request the
1104 The SPMC supports the hypervisor retrieve request, as defined by the FF-A
1108 of the operation, the hypervisor retrieve request can be used to obtain
1162 request. When execution on a PE is in the secure state, only a single call chain
1389 request message to SP1. Further, SP1 sends a direct request message to SP2. SP1
1411   - 9) Since SP1 direct request completed with FFA_INTERRUPT, it resumes the
1412        direct request to SP2 by invoking FFA_RUN.
1421 request EL3 platform firmware to handle a pending Group0 interrupt.
1455   It consists in a SPMD-to-SPMC direct request/response (`SPMC-SPMD direct