Home
last modified time | relevance | path

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

/rk3399_ARM-atf/docs/resources/diagrams/plantuml/
H A Dfirmware_handoff_dfd.puml9 receiver [label="Receiver"]
26 libtl -> receiver [label="DF7" ltail=cluster_trusted]
/rk3399_ARM-atf/bl32/tsp/
H 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()
H A Dffa_helpers.h103 ffa_endpoint_id16_t receiver,
110 ffa_endpoint_id16_t receiver,
H A Dtsp_ffa_main.c93 ffa_endpoint_id16_t receiver = arg5; in ffa_test_relay() local
96 receiver, in ffa_test_relay()
438 uint16_t receiver = ffa_endpoint_destination(arg1); in handle_partition_message() local
478 return ffa_msg_send_direct_resp(receiver, sender, status, 0, 0, 0, 0); in handle_partition_message()
/rk3399_ARM-atf/docs/design_documents/
H A Drse.rst41 The MHU comes in pairs. There is a sender and receiver side. They are connected
43 one receiver on both sides. Bidirectional communication is possible over an
45 from RSE to AP. The sender and receiver are connected via channels. There is an
46 IMPDEF number of channels (e.g: 4-16) between a sender and a receiver module.
53 receiver can read the data from the channel on the other side. One dedicated
56 so the receiver can read them. The receiver uses the same channel to signal
59 multiple rounds. Both, sender and receiver allocate a local buffer for the
64 copied over by RSE core (or by DMA) between the sender and the receiver. This
89 | MHU sender | | MHU receiver | | | Cop
[all...]
/rk3399_ARM-atf/docs/threat_model/firmware_threat_model/
H A Dthreat_model_firmware_handoff.rst31 the receiver.
40 between a TL producer and receiver is presented below. The dataflow DF7 in this
H A Dthreat_model_el3_spm.rst181 | Threat | **An endpoint impersonates the receiver |
221 | | This component checks the sender/receiver fields |
577 | | if receiver encountered a fatal exception.** |