tree wide: update TEE Internal Core Client API revision
Since end 2022, OP-TEE have upgraded from TEE Internal Core API version
1.1.1 to version 1.3.1. Updates documentation accordingly.
Fixes: https://github.com/OP-TEE/optee_os/issues/6134
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
Acked-by: Zhijun Chen <zhijunc@netflix.com>
Signed-off-by: Etienne Carriere <etienne.carriere@foss.st.com>
diff --git a/architecture/globalplatform_api.rst b/architecture/globalplatform_api.rst
index d676ac6..1289b2b 100644
--- a/architecture/globalplatform_api.rst
+++ b/architecture/globalplatform_api.rst
@@ -9,7 +9,7 @@
specifications which facilitate the secure and interoperable deployment and
management of multiple embedded applications on secure chip technology. OP-TEE
has support for GlobalPlatform TEE Client API Specification_ v1.0 (GPD_SPE_007)
-and TEE Internal Core API Specification v1.1.2 (GPD_SPE_010).
+and TEE Internal Core API Specification v1.3.1 (GPD_SPE_010).
.. _tee_client_api:
@@ -103,7 +103,7 @@
================
Calling the Internal Core API is done in the same way as described above using
Client API. The best place to find information how this should be done is in the
-TEE Internal Core API Specification_ v1.1.2 which contains many examples of how
+TEE Internal Core API Specification_ which contains many examples of how
to call the various APIs. One can also have a look at the examples in the
optee_examples_ git.
@@ -238,7 +238,7 @@
**API extension**
-To support Concat KDF, the :ref:`tee_internal_core_api` v1.1 was extended with
+To support Concat KDF, the :ref:`tee_internal_core_api` v1.3.1 was extended with
new algorithm descriptors, new object types, and new object attributes as
described below.
@@ -419,10 +419,10 @@
====
OP-TEE implements the *HMAC-based Extract-and-Expand Key Derivation Function
(HKDF)* as specified in `RFC 5869`_. This file documents the extensions to the
-:ref:`tee_internal_core_api` v1.1 that were implemented to support this
+:ref:`tee_internal_core_api` v1.3.1 that were implemented to support this
algorithm.
-Note that the implementation follows the recommendations of version 1.1 of the
+Note that the implementation follows the recommendations of version 1.3.1 of the
specification for adding new algorithms. It should make it compatible with
future changes to the official specification. You can disable this extension by
setting the following in ``conf.mk``:
@@ -627,7 +627,7 @@
**API extension**
-To support PBKDF2, the :ref:`tee_internal_core_api` v1.1 was extended with a new
+To support PBKDF2, the :ref:`tee_internal_core_api` v1.3.1 was extended with a new
algorithm descriptor, new object types, and new object attributes as described
below.
diff --git a/faq/faq.rst b/faq/faq.rst
index 78af9dd..bd2a830 100644
--- a/faq/faq.rst
+++ b/faq/faq.rst
@@ -383,7 +383,7 @@
===============================================
- GlobalPlatform (see :ref:`globalplatform_api` for more details).
- GlobalPlatform's TEE Client API v1.1 specification
- - GlobalPlatform's TEE Internal Core API v1.1 specification.
+ - GlobalPlatform's TEE Internal Core API v1.3.1 specification.
- GlobalPlatform's Secure Elements v1.0 (**now deprecated**, see ``git
log``).
- GlobalPlatform's Socket API v1.0 (TCP and UDP, but not TLS).
diff --git a/general/about.rst b/general/about.rst
index aece7bb..87cfb85 100644
--- a/general/about.rst
+++ b/general/about.rst
@@ -3,7 +3,7 @@
############
OP-TEE is a Trusted Execution Environment (TEE) designed as companion to a
non-secure Linux kernel running on Arm; Cortex-A cores using the TrustZone
-technology. OP-TEE implements :ref:`tee_internal_core_api` v1.1.x which is the
+technology. OP-TEE implements :ref:`tee_internal_core_api` v1.3.1 which is the
API exposed to Trusted Applications and the :ref:`tee_client_api` v1.0, which is
the API describing how to communicate with a TEE. Those APIs are defined in the
:ref:`globalplatform_api` specifications.