Searched refs:destination (Results 1 – 10 of 10) sorted by relevance
96 sfcp_node_id_t *destination) in sfcp_helpers_packet_requires_forwarding_get_destination() argument105 *destination = receiver; in sfcp_helpers_packet_requires_forwarding_get_destination()112 *destination = sender; in sfcp_helpers_packet_requires_forwarding_get_destination()
35 sfcp_node_id_t *destination);
10 Specified destination address.
109 Note that if the destination FIP file exists, the create, update and113 destination. In that case, use -f or --force to continue.
97 API to get the status and events is called from NS world passing destination
287 This convention helps the SPM to determine the origin and destination worlds in293 (FF-A ID bit 15 clear) and destination world to be secure (FF-A ID bit 15296 for both origin and destination IDs.
311 if (image destination address + image_size overflows) return -ENOMEM324 The destination address is provided by the platform code.
147 arguments (destination and clobber) to materialize the per-CPU pointer without
52 | | message request to SPMC targeting LSP as destination. |171 | | spoof the origin and destination worlds (e.g. a NWd|
21 depending on the FF-A version of the source and destination.22 E.g. a call from a v1.1 caller to a v1.2 destination will zero5271 …- fix destination ID in direct request ([ed23d27](https://review.trustedfirmware.org/plugins/gitil…10846 setting for H3, M3, M3N, change fixed destination address of BL31 and BL32,