Home
last modified time | relevance | path

Searched refs:receiver (Results 1 – 6 of 6) sorted by relevance

/arm-trusted-firmware-2.8.0/bl32/tsp/
A Dffa_helpers.c16 ffa_endpoint_id16_t receiver, in ffa_msg_send_direct_req() argument
24 (receiver << FFA_DIRECT_MSG_DESTINATION_SHIFT); in ffa_msg_send_direct_req()
36 ffa_endpoint_id16_t receiver, in ffa_msg_send_direct_resp() argument
44 (receiver << FFA_DIRECT_MSG_DESTINATION_SHIFT); in ffa_msg_send_direct_resp()
A Dffa_helpers.h103 ffa_endpoint_id16_t receiver,
110 ffa_endpoint_id16_t receiver,
A Dtsp_ffa_main.c92 ffa_endpoint_id16_t receiver = arg5; in ffa_test_relay() local
95 receiver, in ffa_test_relay()
436 uint16_t receiver = ffa_endpoint_destination(arg1); in handle_partition_message() local
476 return ffa_msg_send_direct_resp(receiver, sender, status, 0, 0, 0, 0); in handle_partition_message()
/arm-trusted-firmware-2.8.0/docs/threat_model/
A Dthreat_model_spm.rst166 | ``Threat`` | **An endpoint impersonates the sender or receiver |
203 | | This component checks the sender/receiver fields |
692 | | notifications targeting another receiver using the |
719 | | by the receiver only. The receiver is responsible |
763 | | given receiver. If the sender is an SP, the |
794 | | receiver's ID provided in the input to the call |
796 | | notifications are pending for each receiver. |
797 | | The provided receiver ID must match the ID of the |
800 | | the pending notifications if the receiver had its |
849 | | interfere with both the receiver's and/or primary |
[all …]
A Dthreat_model_el3_spm.rst179 | Threat | **An endpoint impersonates the receiver |
219 | | This component checks the sender/receiver fields |
575 | | if receiver encountered a fatal exception.** |
/arm-trusted-firmware-2.8.0/docs/components/
A Dsecure-partition-manager.rst717 A sender can signal notifications once the receiver has provided it with
722 they are considered to be in a pending sate. The receiver can retrieve its
729 which FF-A endpoints have pending notifications. The receiver scheduler is
731 receiver.
746 the FF-A driver within the receiver scheduler. At initialization the SPMC
923 If the receiver doesn't have notification support enabled in its FF-A manifest,
947 reset when receiver called FFA_NOTIFICATION_GET to retrieve them.
1010 Hafnium copies a message from the sender TX buffer into receiver's RX buffer.
1012 the receiver's RX buffer.
1014 Both receiver and sender need to enable support for indirect messaging,
[all …]

Completed in 12 milliseconds