Lines Matching refs:this

5 There are two parts in this interface: the boot interface and the runtime
99 …x0,Linear index of this PE. This index starts from 0 and must be less than the maximum number of C…
100    x1,Version for this Boot Interface as defined in :ref:`rmm_el3_ifc_versioning`.
101 …x2,Maximum number of CPUs to be supported at runtime. RMM should ensure that it can support this m…
102 …be of 4KB size (1 page). The Boot Manifest must be present at the base of this shared buffer durin…
103 …tion, the activation token should be set to the value returned by RMM for this CPU during the init…
108 Normal memory attributes (IWB-OWB-ISH) at EL3. At boot, this memory will be
113 EL3 should also ensure that this shared buffer is always available for use by RMM
116 service commands in EL3, this buffer can be used to exchange data between RMM
118 utilizing this buffer during the boot phase, prior to return back to EL3 via
121 RMM should map this memory page into its Stage 1 page-tables using Normal
137 is still pending. The only argument that is required by RMM at this stage is
145 …x0,Linear index of this PE. This index starts from 0 and must be less than the maximum number of C…
146 …tion, the activation token should be set to the value returned by RMM for this CPU during the init…
153 ``RMM_BOOT_COMPLETE`` SMC call. The first argument of this SMC call will
191 in :ref:`rmm_el3_ifc_versioning` apply on this version as well.
196    - plat_data : Pointer to the platform specific data and not specified by this
199      field is optional and platform can choose to zero out this structure if
200      RMM does not need EL3 to send this information during the boot.
203      the console list if this is not needed by the RMM for this platform.
223 and EL3 are allowed to make suitable optimizations based on this assumption.
227 :ref:`rmm_cold_boot_interface` for properties of this shared buffer which both
308 Since this call does not return to RMM, there is no failure condition which
463 the buffer for the first call of this command and the size of the object is
467 If ``c_size`` is not 0, this command could cause regeneration of platform token
470 It is valid for the calls of this command to return ``E_RMM_AGAIN`` error,
471 which is an indication to the caller to retry this command again. Depending on the
472 platform, this mechanism can be used to implement queuing to HES, if HES is
488 … passed in this buffer for the first call of this command. Any subsequent calls, if required to re…
490 …gorithms. Any subsequent calls, if required to retrieve the full token, should set this size to 0."
516 …CSize`` does not represent the size of a supported SHA algorithm for the first call to this command
621 The RMM-EL3 interface for this command is modeled as two separate queues, one for signing requests
688 associated with a given MECID. After the execution of this command, all memory
740 for description of the IDE setup sequence and how this will be invoked by RMM.
743 to call this SMC to program this key to the Rx, Tx ports and for each sub-stream
809 for description of the IDE setup sequence and info on how this will be invoked by RMM.
811 The caller(RMM) needs to ensure the EL3_IDE_KEY_PROG() call had succeeded prior to this call.
870 for description of the IDE setup sequence and info on how this will be invoked by RMM.
931 for description of the IDE setup sequence and info on how this will be invoked by RMM.
933 The response from this call could correspond to any of the last pending requests and the
934 RMM needs to identify the request and populate the response. For blocking calls, this SMC
1056 …ith the ``_EL2`` prefix. The EL2 physical and virtual timer registers must not be included in this.
1061 and it is the responsibility of RMM to preserve this or use this as a return argument.
1078 It is essential that EL3 honors this contract to maintain the Confidentiality and integrity
1081 SMCCC v1.3 allows NS world to specify whether SVE context is in use. In this
1130 The members of this structure are shown in the table below:
1166 The members of this structure are shown in the table below:
1210 The members of this structure are shown in the table below:
1243 The members of this structure are shown in the table below.
1268 The table below describes the members of this structure as per v0.1.