Searched refs:receiver (Results 1 – 6 of 6) sorted by relevance
| /trusted-firmware-a-3.7.0/bl32/tsp/ |
| D | ffa_helpers.c | 16 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()
|
| D | ffa_helpers.h | 103 ffa_endpoint_id16_t receiver,
110 ffa_endpoint_id16_t receiver,
|
| D | tsp_ffa_main.c | 92 ffa_endpoint_id16_t receiver = arg5; in ffa_test_relay() local
95 receiver, in ffa_test_relay()
437 uint16_t receiver = ffa_endpoint_destination(arg1); in handle_partition_message() local
477 return ffa_msg_send_direct_resp(receiver, sender, status, 0, 0, 0, 0); in handle_partition_message()
|
| /trusted-firmware-a-3.7.0/docs/design_documents/ |
| D | rss.rst | 35 The MHU comes in pairs. There is a sender and receiver side. They are connected
37 one receiver on both sides. Bidirectional communication is possible over an
39 from RSS to AP. The sender and receiver are connected via channels. There is an
40 IMPDEF number of channels (e.g: 4-16) between a sender and a receiver module.
47 receiver can read the data from the channel on the other side. One dedicated
50 so the receiver can read them. The receiver uses the same channel to signal
53 multiple rounds. Both, sender and receiver allocate a local buffer for the
58 copied over by RSS core (or by DMA) between the sender and the receiver. This
83 | MHU sender | | MHU receiver | | | Copy data |
89 | MHU receiver | | MHU sender | | +->| DMA | |
|
| /trusted-firmware-a-3.7.0/docs/threat_model/ |
| D | threat_model_el3_spm.rst | 181 | Threat | **An endpoint impersonates the receiver |
221 | | This component checks the sender/receiver fields |
577 | | if receiver encountered a fatal exception.** |
|
| /trusted-firmware-a-3.7.0/docs/components/ |
| D | secure-partition-manager.rst | 744 A sender can signal notifications once the receiver has provided it with
749 they are considered to be in a pending sate. The receiver can retrieve its
756 which FF-A endpoints have pending notifications. The receiver scheduler is
758 receiver.
773 the FF-A driver within the receiver scheduler. At initialization the SPMC
779 receiver of the notification. Set when there are pending notifications for the
950 If the receiver doesn't have notification support enabled in its FF-A manifest,
974 reset when receiver called FFA_NOTIFICATION_GET to retrieve them.
1037 Hafnium copies a message from the sender TX buffer into receiver's RX buffer.
1039 the receiver's RX buffer.
[all …]
|
