| /rk3399_ARM-atf/common/ |
| H A D | runtime_svc.c | 109 rt_svc_desc_t *service = &rt_svc_descs[index]; in runtime_svc_init() local
116 rc = validate_rt_svc_desc(service); in runtime_svc_init()
119 (void *) service); in runtime_svc_init()
130 if (service->init != NULL) { in runtime_svc_init()
131 rc = service->init(); in runtime_svc_init()
134 service->name); in runtime_svc_init()
145 start_idx = (uint8_t)get_unique_oen(service->start_oen, in runtime_svc_init()
146 service->call_type); in runtime_svc_init()
147 end_idx = (uint8_t)get_unique_oen(service->end_oen, in runtime_svc_init()
148 service->call_type); in runtime_svc_init()
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | rt-svc-writers-guide.rst | 7 This document describes how to add a runtime service to the EL3 Runtime
17 SMC Functions are grouped together based on the implementor of the service, for
24 dispatched to their respective service implementation - the
80 handler will be responsible for all SMC Functions within a given service type.
86 each owning entity can place the implementation of its runtime service. The
89 Runtime service sources will need to include the ``runtime_svc.h`` header file.
91 Registering a runtime service
94 A runtime service is registered using the ``DECLARE_RT_SVC()`` macro, specifying
95 the name of the service, the range of OENs covered, the type of service and
130 During initialization the services framework validates each declared service
[all …]
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | arm-sip-service.rst | 18 - Execution State Switching service
20 Source definitions for Arm SiP service are located in the ``arm_sip_svc.h`` header
31 *Table 1: Showing different versions of arm-sip-service and changes done with each version*
33 Execution State Switching service
36 Execution State Switching service provides a mechanism for a non-secure lower
39 AArch32, or from AArch32 to AArch64, for the calling CPU. This service is only
59 Execution State Switching service being requested. argument
80 The service may return the following error codes:
|
| H A D | ven-el3-service.rst | 61 *Table 1: Showing different versions of Vendor-specific service and changes done with each version*
63 Each sub service will have its own version, one FID allocated for sub service version.
66 - VEN_EL3_SVC_VERSION_MAJOR is incremented when any of the sub service version discovery
69 - VEN_EL3_SVC_VERSION_MINOR is incremented when we add a new FID or a new sub service.
70 For example adding an new monitor service at 0x30, Debugfs starts at 0x10 and PMF
83 The optional DebugFS interface is accessed through Vendor specific EL3 service. Refer
|
| H A D | index.rst | 10 arm-sip-service
29 ven-el3-service
|
| H A D | secure-partition-manager-mm.rst | 20 fulfils the requirements of a security service as described above.
23 in the system, i.e. EL3 in Trusted Firmware-A (TF-A). The service requirements are
33 other interfaces (e.g. ACPI TCG TPM interface, UEFI runtime variable service).
82 fulfil a service request.
90 service requests.
93 accessing the services exported by a Secure Partition. A service can be
114 service always runs to completion (e.g. the requested services cannot be
183 0060A*) is used to invoke a Secure Partition service as a Fast Call.
185 The mechanism used to identify a service within the partition depends on the
186 service implementation. It is assumed that the caller of the service will be
[all …]
|
| H A D | debugfs-design.rst | 103 - On concurrent access, a spinlock is implemented in the BL31 service to protect
125 .. _ARM SiP Services: arm-sip-service.rst
|
| H A D | ven-el3-debugfs.rst | 4 The optional DebugFS interface is accessed through a Vendor specific EL3 service. Refer
|
| H A D | realm-management-extension.rst | 71 RMMD is a new standard runtime service that handles the switch to the Realm
|
| H A D | granule-protection-tables-design.rst | 83 structure used by the granule transition service which will be covered more
182 #. In systems that make use of the granule transition service, runtime
|
| /rk3399_ARM-atf/docs/perf/ |
| H A D | psci-performance-instr.rst | 27 instance, the PSCI Statistics service registers the PMF service
32 values from ``psci_svc`` at runtime. Alternatively, the service may be
35 service.
42 PSCI Statistics is a runtime service that provides residency statistics for
43 power states used by the platform. The service tracks residency time and
85 around the PMF to provide timestamp data. Although the service is not
92 In PSCI, this service provides instrumentation points in the
102 The service captures the cycle count, which allows for the time spent in the
|
| H A D | tsp.rst | 7 The TSP is coupled with a companion runtime service in the BL31 firmware,
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | amd-versal2.rst | 63 CUSTOM SIP service.
66 ``custom_smc_handler`` in this service.
68 - To use this service, the custom package should implement its own SMC handler
135 Call UID Query – Returns a unique identifier of the service provider.
137 Revision Query – Returns revision details of the service implementor.
|
| H A D | xilinx-zynqmp.rst | 133 CUSTOM SIP service support
138 providing CUSTOM SIP service.
141 custom_smc_handler in this service.
143 - to use this service, custom package should implement their
209 Call UID Query – Returns a unique identifier of the service provider.
211 Revision Query – Returns revision details of the service implementor.
213 CUSTOM SIP service support
|
| H A D | xilinx-versal.rst | 80 CUSTOM SIP service.
83 ``custom_smc_handler`` in this service.
85 - To use this service, the custom package should implement its own SMC handler
173 Call UID Query – Returns a unique identifier of the service provider.
175 Revision Query – Returns revision details of the service implementor.
|
| H A D | xilinx-versal-net.rst | 114 Call UID Query – Returns a unique identifier of the service provider.
116 Revision Query – Returns revision details of the service implementor.
|
| H A D | s32g274a.rst | 7 service-oriented gateways, domain controllers, zonal processors, safety
13 engineering for vehicle service-oriented gateway (SoG), domain control
|
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | measured_boot_poc.rst | 20 a firmware TPM (fTPM) service implemented on top of OP-TEE.
25 party (f)TPM service and they try to be as general as possible. Different
28 (or even a different type of service to provide the attestation)
40 contain a third party fTPM service which in turn will be used to process the
44 for convenience. As the fTPM service used is an OP-TEE TA, it was easy to add
50 - **OP-TEE**: As stated earlier, the fTPM service used in this PoC is built as an
59 - **fTPM Service**: We use a third party fTPM service in order to validate
60 the Measured Boot functionality. The chosen fTPM service is a sample
62 reference implementation from Microsoft. The service was updated in order
68 Arm does not provide an fTPM implementation. The fTPM service used here
[all …]
|
| H A D | rse.rst | 138 description, measurement algorithm, etc.). More info on measured boot service
141 delegated attestation key. More info on the delegated attestation service
153 Runtime service API
214 | service | | service |
225 service which is meant to store measurements and associated metadata alongside.
433 The detailed description of the delegated attestation service can be found in
437 attestation service of the RSE to get a realm attestation key and the CCA
438 platform token. BL31 does not use the service for its own purpose, only calls
685 The ``DICE Protection Environment (DPE)`` [8]_ service makes it possible to
688 that act on opaque context handles. The |DPE| service performs |DICE|
[all …]
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | interrupt-framework-design.rst | 275 #. Secure Payload Dispatcher (SPD) service. This service interfaces with the
282 the SPD service. TF-A implements an example Test Secure Payload Dispatcher
283 (TSPD) service.
285 An SPD service plugs into the EL3 runtime firmware and could be common to
290 SPD service to manage communication with non-secure software. TF-A
295 just like the SPD service.
349 particular type of interrupt. A Secure Payload Dispatcher service should use
401 A SPD service is responsible for determining and maintaining the interrupt
408 If the routing model is not known to the SPD service at build time, then it must
415 could either be provided to the SPD service at build time or by the SP at
[all …]
|
| H A D | firmware-design.rst | 12 TF-A also implements the `PSCI`_ as a runtime service. PSCI is the interface
544 The runtime service framework and its initialization is described in more
554 Dispatcher (SPD) service (see later for details). During initialization
555 that service must register a function to carry out initialization of BL32
841 #. Standard service calls
843 This service is for management of the entire system. The Power State
844 Coordination Interface (`PSCI`_) is the first set of standard service calls
847 #. Secure-EL1 Payload Dispatcher service
859 service - within TF-A this service is referred to as the Secure-EL1 Payload
866 #. CPU implementation service
[all …]
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | threat_model_el3_spm.rst | 127 - Denial of service
533 | | SPMC with requests targeting a service within an |
535 | | access this service.** |
538 | | a service within an endpoint such that the latter |
551 | Threat Type | Denial of service |
563 | | Other quality of service monitoring can be achieved|
588 | Threat Type | Denial of service |
|
| /rk3399_ARM-atf/docs/resources/diagrams/plantuml/ |
| H A D | rse_measured_boot_flow.puml | 52 Measured Boot service to\n\ measurement slots.
|
| /rk3399_ARM-atf/docs/components/fconf/ |
| H A D | tb_fw_bindings.rst | 121 - A string identifying the UUID of the service implemented by this partition.
|
| /rk3399_ARM-atf/docs/security_advisories/ |
| H A D | security-advisory-tfv-9.rst | 109 firmware service. This patch also implements ``SMCCC_ARCH_WORKAROUND_3`` for
|