Lines Matching refs:interface

560 - the FFA_MSG_SEND_DIRECT_REQ interface.
561 - the FFA_RUN interface.
592   to explicitly invoke the ``FFA_RXTX_MAP`` interface. The memory referred
678 `FFA_SECONDARY_EP_REGISTER`_ interface (SMC invocation from the SPMC to the SPMD
740 deployed in NWd, the Hypervisor or OS kernel must invoke the interface
745 permissions. Permissions are provided by invoking the interface
862 synchronization (through FFA_RX_ACQUIRE interface), and to permit SPs to send
923 This is a mandatory interface for secure partitions consisting in direct request
937 Hence, this interface is not to be issued by secure partitions.
969 has been retrieved by this interface. The count is incremented and decremented
983 FFA_ID_GET interface, and records it. The SPMC can also query the SPMD ID using
984 the FFA_SPM_ID_GET interface at the secure physical FF-A instance.
986 Secure partitions call this interface at the virtual FF-A instance, to which
998 The FFA_SECONDARY_EP_REGISTER interface is to be used by a secure partition
1019 The hypervisor must call the FFA_RX_ACQUIRE interface before attempting
1024 The FFA_RX_RELEASE interface is used after the FF-A endpoint is done with
1075 The ``FFA_MEM_RETRIEVE_REQ`` interface is for the borrower to request the
1081 The ``FFA_MEM_RELINQUISH`` interface is for when the borrower is done with using
1084 The ``FFA_MEM_RECLAIM`` interface is for the owner of the memory to reestablish
1176     allocated CPU cycles through FFA_RUN interface.
1178     allocated CPU cycles through FFA_MSG_SEND_DIRECT_REQ interface.
1234     GIC interface.
1258 either the FFA_INTERRUPT interface with ERET conduit or vIRQ signal for signaling
1294 In the current implementation, S-EL1 SPs use the para-virtualized HVC interface
1298 either FFA_MSG_WAIT or FFA_RUN interface if the SP didn't perform the
1400   - 4) SPMC pends vIRQ for SP1 and signals through FFA_INTERRUPT interface.
1640 [2] :ref:`Secure Partition Manager using MM interface<Secure Partition Manager (MM)>`