Lines Matching refs:secure
23 and SPMC at EL3, one S-EL1 secure partition, with an optional
41 ``SPMC_AT_EL3`` is enabled, the secure partitions are loaded
100 Other platforms need to allocate a similar secure memory region
132 BL2 loads the BL31 image as a part of (secure) boot process.
233 FF-A features supported by the SPMC may be discovered by secure partitions at
236 The SPMC calling FFA_FEATURES at secure physical FF-A instance always get
249 When invoked from a secure partition FFA_RXTX_MAP maps the provided send and
251 as secure buffers in the MMU descriptors.
258 caller, either it being the Hypervisor or OS kernel, as well as a secure
280 The FF-A ID space is split into a non-secure space and secure space:
290 use a secure FF-A ID as origin world by spoofing:
292 - A VM-to-SP direct request/response shall set the origin world to be non-secure
293 (FF-A ID bit 15 clear) and destination world to be secure (FF-A ID bit 15
311 - or initiated by an SP and thus origin endpoint ID must be a "secure world ID".
320 This is a mandatory interface for secure partitions participating in direct request
338 the FFA_SPM_ID_GET interface at the secure physical FF-A instance.
393 When the SPMC boots, secure partition is initialized on its primary
396 The FFA_SECONDARY_EP_REGISTER interface is to be used by a secure partition
406 In platforms with or without secure virtualization:
426 secure partitions. For this a VM (Hypervisor or OS kernel), or SP invokes one of:
431 Additionally a secure interrupt can pre-empt the normal world execution and give
473 In the scenario when secure interrupt occurs while the secure partition is running,
492 - Ability to handle secure interrupt (timer).