Lines Matching refs:SPM
9 - SPM based on the PSA FF-A specification (:ref:`Secure Partition Manager`).
10 - SPM based on the MM interface.
81 (SPM)** is responsible for managing the partition. This is semantically
84 The SPM is responsible for the following actions during boot:
94 The SPM is responsible for the following actions during runtime:
104 the control of the SPM. Hence common programming concepts described below are
119 SPM is supported on the Arm FVP exclusively at the moment. The current
124 It is not currently possible for BL31 to integrate SPM support and a Secure
126 SPM bootflow, a Secure Partition image executing at S-EL0 replaces the Secure
136 To enable SPM support in TF-A, the source code must be compiled with the build
145 Then build TF-A with SPM support and include the Standalone MM Secure Partition
174 describe the memory regions that the SPM needs to allocate for a Secure
204 The SPM is responsible for guaranteeing this behaviour. This means that there
213 is statically allocated by the SPM and is expected to be either implicitly known
234 This section describes how the Secure Partition interfaces with the SPM.
236 Interface with SPM
240 S-EL0, the SPM should define the following types of interfaces:
247 - Interfaces that establish the control path between the SPM and the Secure
250 This section describes the APIs currently exported by the SPM that enable a
263 implemented by the SPM.
267 from a Secure Partition as a SMC request to the SPM in EL3. Upon servicing the
280 Communication initiated by SPM argument
283 A service request is initiated from the SPM through an exception return
308 specification) for each API exported by the SPM. This section defines the
317 SPM to delegate service requests to the Secure Partition. The interface also
320 - Register with the SPM a service that it provides.
321 - Indicate completion of a service request delegated by the SPM
331 Returns the version of the interface exported by SPM.
346 - Bits [30:16]: Major Version. Must be 0 for this revision of the SPM
348 - Bits [15:0]: Minor Version. Must be 1 for this revision of the SPM
353 - ``NOT_SUPPORTED``: SPM interface is not supported or not available for the
384 The SPM is responsible for initialising the architectural execution context to
385 enable initialisation of a service in S-EL0. The responsibilities of the SPM are
402 state unless otherwise specified. The SPM will perform the following
408 The platform port of a Secure Partition specifies to the SPM a list of regions
409 that it needs access to and their attributes. The SPM validates this resource
434 System registers that influence software execution in S-EL0 are setup by the SPM
467 SPM will invoke the entry point of a service by executing an ERET instruction.
477 A non-zero value will indicate that the SPM has initialised the stack pointer
488 Parameters passed by the SPM.
503 The SPM receives requests for Secure Partition services through a synchronous
543 delegated to the partition by the SPM.
559 Address of a buffer shared between the SPM and Secure Partition to pass
580 This function signals to the SPM that the handling of the last event delegated
588 completion of a request that was delegated to it by the SPM.
592 When the SPM receives this call from a Secure Partition, the corresponding
598 The SPM must save this syndrome information and use it to delegate the next
607 The SPM is responsible for enabling access to regions of memory in the system
614 All memory required by the Secure Partition is allocated upfront in the SPM,
630 of its memory regions. The SPM provides this feature through the
635 initialisation is complete, the SPM does not allow changes to the memory
638 This section describes the standard SVC interface that is implemented by the SPM
689 - ``NOT_SUPPORTED`` : The SPM does not support retrieval of attributes of
708 translation regime from the SPM through an implementation defined method.
712 The SPM must not return the memory access controls for a page of memory that
767 - ``DENIED``: The SPM is servicing a request to change the attributes of a
775 - ``NO_MEMORY``: The SPM does not have memory resources to change the
778 - ``NOT_SUPPORTED``: The SPM does not permit change of attributes of any
801 translation regime from the SPM through an implementation defined method.
805 The SPM must preserve the original memory access controls of the region of
806 memory in case of an unsuccessful call. The SPM must preserve the consistency