Lines Matching refs:ID
280 The FF-A ID space is split into a non-secure space and secure space:
282 - FF-A ID with bit 15 clear relates to VMs.
283 - FF-A ID with bit 15 set related to SPs or LSPs.
290 use a secure FF-A ID as origin world by spoofing:
293 (FF-A ID bit 15 clear) and destination world to be secure (FF-A ID bit 15
295 - Similarly, an SP-to-LSP direct request/response shall set the FF-A ID bit 15
301 endpoint ID must be checked by SPMC for being a normal world ID.
304 endpoint ID and this can be checked by the SPMC when the SP invokes the ABI.
307 ID is not consistent:
309 - It is either forwarded by SPMD and thus origin endpoint ID must be a "normal
310 world ID",
311 - or initiated by an SP and thus origin endpoint ID must be a "secure world ID".
333 Returns the FF-A ID allocated to an SPM component which can be one of SPMD
336 At initialization, the SPMC queries the SPMD for the SPMC ID, using the
337 FFA_ID_GET interface, and records it. The SPMC can also query the SPMD ID using
341 the SPMC returns the SPMC ID.
344 SPMD, which returns the SPMC ID.
349 Returns the FF-A ID of the calling endpoint.
388 SPMC validates handle and Endpoint ID and returns response with FFA_MEM_FRAG_TX.