Lines Matching defs:SPM
74 (SPM)** is responsible for managing the partition. This is semantically
77 The SPM is responsible for the following actions during boot:
87 The SPM is responsible for the following actions during runtime:
97 the control of the SPM. Hence common programming concepts described below are
112 SPM is supported on the Arm FVP exclusively at the moment. The current
117 It is not currently possible for BL31 to integrate SPM support and a Secure
119 SPM bootflow, a Secure Partition image executing at S-EL0 replaces the Secure
129 To enable SPM support in TF-A, the source code must be compiled with the build
138 Then build TF-A with SPM support and include the Standalone MM Secure Partition
167 describe the memory regions that the SPM needs to allocate for a Secure
197 The SPM is responsible for guaranteeing this behaviour. This means that there
206 is statically allocated by the SPM and is expected to be either implicitly known
227 This section describes how the Secure Partition interfaces with the SPM.
229 Interface with SPM
233 S-EL0, the SPM should define the following types of interfaces:
240 - Interfaces that establish the control path between the SPM and the Secure
243 This section describes the APIs currently exported by the SPM that enable a
256 implemented by the SPM.
260 from a Secure Partition as a SMC request to the SPM in EL3. Upon servicing the
273 Communication initiated by SPM
276 A service request is initiated from the SPM through an exception return
301 specification) for each API exported by the SPM. This section defines the
310 SPM to delegate service requests to the Secure Partition. The interface also
313 - Register with the SPM a service that it provides.
314 - Indicate completion of a service request delegated by the SPM
324 Returns the version of the interface exported by SPM.
339 - Bits [30:16]: Major Version. Must be 0 for this revision of the SPM
341 - Bits [15:0]: Minor Version. Must be 1 for this revision of the SPM
346 - ``NOT_SUPPORTED``: SPM interface is not supported or not available for the
377 The SPM is responsible for initialising the architectural execution context to
378 enable initialisation of a service in S-EL0. The responsibilities of the SPM are
395 state unless otherwise specified. The SPM will perform the following
401 The platform port of a Secure Partition specifies to the SPM a list of regions
402 that it needs access to and their attributes. The SPM validates this resource
427 System registers that influence software execution in S-EL0 are setup by the SPM
460 SPM will invoke the entry point of a service by executing an ERET instruction.
470 A non-zero value will indicate that the SPM has initialised the stack pointer
481 Parameters passed by the SPM.
496 The SPM receives requests for Secure Partition services through a synchronous
536 delegated to the partition by the SPM.
552 Address of a buffer shared between the SPM and Secure Partition to pass
573 This function signals to the SPM that the handling of the last event delegated
581 completion of a request that was delegated to it by the SPM.
585 When the SPM receives this call from a Secure Partition, the corresponding
591 The SPM must save this syndrome information and use it to delegate the next
600 The SPM is responsible for enabling access to regions of memory in the system
607 All memory required by the Secure Partition is allocated upfront in the SPM,
623 of its memory regions. The SPM provides this feature through the
628 initialisation is complete, the SPM does not allow changes to the memory
631 This section describes the standard SVC interface that is implemented by the SPM
682 - ``NOT_SUPPORTED`` : The SPM does not support retrieval of attributes of
701 translation regime from the SPM through an implementation defined method.
705 The SPM must not return the memory access controls for a page of memory that
760 - ``DENIED``: The SPM is servicing a request to change the attributes of a
768 - ``NO_MEMORY``: The SPM does not have memory resources to change the
771 - ``NOT_SUPPORTED``: The SPM does not permit change of attributes of any
794 translation regime from the SPM through an implementation defined method.
798 The SPM must preserve the original memory access controls of the region of
799 memory in case of an unsuccessful call. The SPM must preserve the consistency