mirror of
https://github.com/ARM-software/arm-trusted-firmware.git
synced 2026-07-10 03:48:39 +00:00
Manish Pandey
96546b5cc3
To support TPM start method compatible with pre-FFA configuration (to support SPM_MM) introduce an SMC FID el3 vendor specific range. This SMC is forwarded to SPM_MM module which converts into a MM_COMMUNICATE to interact with Secure partition. TPM Start method is mentioned in TCG ACPI spec section 3.3.1 https://trustedcomputinggroup.org/wp-content/uploads/TCG-ACPI-Specification-Version-1.4-Revision-15_pub.pdf As this patch introduces a new sub service, increment minor version of Vendor EL3 service. Signed-off-by: Manish Pandey <manish.pandey2@arm.com> Change-Id: I61698018e6bc33c9b389ac905fe158810af21bfa
105 lines
6.4 KiB
ReStructuredText
105 lines
6.4 KiB
ReStructuredText
Vendor Specific EL3 Monitor Service Calls
|
|
=========================================
|
|
|
|
This document enumerates and describes the Vendor Specific EL3 Monitor Service
|
|
Calls.
|
|
|
|
These are Service Calls defined by the vendor of the EL3 Monitor.
|
|
They are accessed via ``SMC`` ("SMC calls") instruction executed from Exception
|
|
Levels below EL3. SMC calls for Vendor Specific EL3 Monitor Services:
|
|
|
|
- Follow `SMC Calling Convention`_;
|
|
- Use SMC function IDs that fall in the vendor-specific EL3 range, which are
|
|
|
|
+---------------------------+--------------------------------------------------+
|
|
| SMC Function Identifier | Service Type |
|
|
+===========================+==================================================+
|
|
| 0x87000000 - 0x8700FFFF | SMC32: Vendor Specific EL3 Monitor Service Calls |
|
|
+---------------------------+--------------------------------------------------+
|
|
| 0xC7000000 - 0xC700FFFF | SMC64: Vendor Specific EL3 Monitor Service Calls |
|
|
+---------------------------+--------------------------------------------------+
|
|
|
|
Vendor-specific EL3 monitor services are as follows:
|
|
|
|
+-----------------------------------+-----------------------+---------------------------------------------+
|
|
| SMC Function Identifier | Service Type | FID's Usage |
|
|
+===================================+=======================+=============================================+
|
|
| 0x87000010 - 0x8700001F (SMC32) | DebugFS Interface | | 0 - 11 are in use. |
|
|
+-----------------------------------+ | | 12 - 15 are reserved for future expansion.|
|
|
| 0xC7000010 - 0xC700001F (SMC64) | | |
|
|
+-----------------------------------+-----------------------+---------------------------------------------+
|
|
| 0x87000020 - 0x8700002F (SMC32) | Performance | | 0,1 is in use. |
|
|
+-----------------------------------+ Measurement Framework | | 2 - 15 are reserved for future expansion. |
|
|
| 0xC7000020 - 0xC700002F (SMC64) | (PMF) | |
|
|
+-----------------------------------+-----------------------+---------------------------------------------+
|
|
| 0x87000030 - 0x8700003F (SMC32) | ACS (Architecture | | 0 in use. |
|
|
+-----------------------------------+ Compliance Suite) SMC | | 1 - 15 are reserved for future expansion. |
|
|
| 0xC7000030 - 0xC700003F (SMC64) | handler | |
|
|
+-----------------------------------+-----------------------+---------------------------------------------+
|
|
| 0x87000040 - 0x8700004F (SMC32) | TPM Start method | | 0 is in use. |
|
|
+-----------------------------------+ | | 1 - 15 are reserved for future expansion. |
|
|
| 0xC7000040 - 0xC700004F (SMC64) | | |
|
|
+-----------------------------------+-----------------------+---------------------------------------------+
|
|
| 0x87000050 - 0x8700FFFF (SMC32) | Reserved | | reserved for future expansion |
|
|
+-----------------------------------+ | |
|
|
| 0xC7000050 - 0xC700FFFF (SMC64) | | |
|
|
+-----------------------------------+-----------------------+---------------------------------------------+
|
|
|
|
Source definitions for vendor-specific EL3 Monitor Service Calls used by TF-A are located in
|
|
the ``ven_el3_svc.h`` header file.
|
|
|
|
+----------------------------+----------------------------+--------------------------------+
|
|
| VEN_EL3_SVC_VERSION_MAJOR | VEN_EL3_SVC_VERSION_MINOR | Changes |
|
|
+============================+============================+================================+
|
|
| 1 | 0 | Added Debugfs and PMF services.|
|
|
+----------------------------+----------------------------+--------------------------------+
|
|
| 1 | 1 | Added ACS SMC handler services.|
|
|
+------------------------------------------------------------------------------------------+
|
|
| 1 | 2 | Added TPM Start method. |
|
|
+----------------------------+----------------------------+--------------------------------+
|
|
|
|
*Table 1: Showing different versions of Vendor-specific service and changes done with each version*
|
|
|
|
Each sub service will have its own version, one FID allocated for sub service version.
|
|
|
|
Some ground rules when one should update top level version.
|
|
- VEN_EL3_SVC_VERSION_MAJOR is incremented when any of the sub service version discovery
|
|
FID changes or the FID that was allocated for discovery changes. So any breaking subfeature
|
|
discovery changes will lead to major version update.
|
|
- VEN_EL3_SVC_VERSION_MINOR is incremented when we add a new FID or a new sub service.
|
|
For example adding an new monitor service at 0x30, Debugfs starts at 0x10 and PMF
|
|
starts at 0x20 next one will start at 0x30, this will need a update to minor version.
|
|
|
|
Performance Measurement Framework (PMF)
|
|
---------------------------------------
|
|
|
|
The :ref:`Performance Measurement Framework <firmware_design_pmf>`
|
|
allows callers to retrieve timestamps captured at various paths in TF-A
|
|
execution.
|
|
|
|
DebugFS interface
|
|
-----------------
|
|
|
|
The optional DebugFS interface is accessed through Vendor specific EL3 service. Refer
|
|
to :ref:`DebugFS interface` documentation for further details and usage.
|
|
|
|
Architecture Compliance Suite (ACS) SMC handler
|
|
-----------------------------------------------
|
|
|
|
The Architecture Compliance Suite (ACS) SMC handler allows callers to branch
|
|
to their ACS EL3 code based on their respective use-cases.
|
|
For more details on System ACS, `System ACS`_.
|
|
|
|
TPM Start method
|
|
----------------
|
|
|
|
TPM start method as mentioned in `TCG ACPI specification`_ section 3.3.1.
|
|
|
|
--------------
|
|
|
|
*Copyright (c) 2024-2025, Arm Limited and Contributors. All rights reserved.*
|
|
|
|
.. _System ACS: https://developer.arm.com/Architectures/Architectural%20Compliance%20Suite
|
|
.. _SMC Calling Convention: https://developer.arm.com/docs/den0028/latest
|
|
.. _TCG ACPI specification: https://trustedcomputinggroup.org/wp-content/uploads/TCG-ACPI-Specification-Version-1.4-Revision-15_pub.pdf
|