Merge pull request #400 from gilles-peskine-arm/pages-drivers-20211117
Remove obsolete reference to the old driver interface
diff --git a/docs/psa/index.html b/docs/psa/index.html
index d9fb9a9..67b0ae3 100644
--- a/docs/psa/index.html
+++ b/docs/psa/index.html
@@ -8,10 +8,9 @@
<h3 id="unified-driver-interface">Unified driver interface</h3>
<p>There is work in progress to define a PSA cryptography driver interface, allowing an implementation of the PSA Cryptography API to make use of dedicated hardware (accelerators, secure elements, random generators, etc.) or other external systems such as a remote key store. The driver interface is being tried out in Mbed TLS. Arm expects to make it an official PSA specification once it has been sufficiently validated.</p>
<p>For more information, please see the <a href="https://github.com/ARMmbed/mbedtls/blob/development/docs/proposed/psa-driver-interface.md">proposed driver interface</a> as well as the <a href="https://github.com/ARMmbed/mbedtls/issues?q=+label%3AHwDrivers+">ongoing specification and implementation effort</a>.</p>
-<p>PSA includes functional specifications describing a hardware abstraction layer covering <a href="accel/">cryptographic accelerators</a>, <a href="se/">secure elements</a> and <a href="entropy/">entropy sources</a>.</p>
-<h3 id="secure-element-driver-interface">Secure element driver interface</h3>
+<h3 id="dynamic-secure-element-driver-interface">Dynamic secure element driver interface</h3>
<p>The dynamic secure element driver interface lets you write drivers for external cryptoprocessors such as secure elements (SE), smart cards and hardware security modules (HSM) that perform operations on keys that never leave the external processor and are accessed only through opaque handles. Such drivers can be loaded dynamically into an implementation of the PSA Cryptography API such as Mbed TLS.</p>
-<p>Work on this interface is currently frozen. The <a href="#unified-driver-interface">unified driver interface</a> replaces the older dynamic secure element driver for most purposes. The older interface the advantage of allowing drivers to be dynamically loaded. If there is widespread demand for dynamic loading of secure element drivers, Arm may revive the effort on the older interface or merge it into the unified interface.</p>
+<p>Work on this interface is currently frozen. The <a href="#unified-driver-interface">unified driver interface</a> replaces the older dynamic secure element driver for most purposes. The older interface has the advantage of allowing drivers to be dynamically loaded. If there is widespread demand for dynamic loading of secure element drivers, Arm may revive the effort on the older interface or merge it into the unified interface.</p>
<p>For more information, see <a href="se/">PSA secure element driver interface</a>.</p>
<h2 id="feedback">Feedback</h2>
<p>Arm welcomes feedback on the design of the PSA cryptography interfaces. If you think something could be improved, please open an <a href="https://github.com/ARMmbed/mbedtls/labels/api-spec">issue on the Mbed TLS GitHub repository</a>. Alternatively, if you prefer to provide your feedback privately, please email us at <code>mbed-crypto@arm.com</code>. All feedback received by email is treated confidentially.</p>
diff --git a/docs/psa/index.md b/docs/psa/index.md
index 2d85134..d575f94 100644
--- a/docs/psa/index.md
+++ b/docs/psa/index.md
@@ -22,14 +22,12 @@
For more information, please see the [proposed driver interface](https://github.com/ARMmbed/mbedtls/blob/development/docs/proposed/psa-driver-interface.md) as well as the [ongoing specification and implementation effort](https://github.com/ARMmbed/mbedtls/issues?q=+label%3AHwDrivers+).
-PSA includes functional specifications describing a hardware abstraction layer covering [cryptographic accelerators](accel/), [secure elements](se/) and [entropy sources](entropy/).
-
-### Secure element driver interface
+### Dynamic secure element driver interface
The dynamic secure element driver interface lets you write drivers for external cryptoprocessors such as secure elements (SE), smart cards and hardware security modules (HSM) that perform operations on keys that never leave the external processor and are accessed only through opaque handles.
Such drivers can be loaded dynamically into an implementation of the PSA Cryptography API such as Mbed TLS.
-Work on this interface is currently frozen. The [unified driver interface](#unified-driver-interface) replaces the older dynamic secure element driver for most purposes. The older interface the advantage of allowing drivers to be dynamically loaded. If there is widespread demand for dynamic loading of secure element drivers, Arm may revive the effort on the older interface or merge it into the unified interface.
+Work on this interface is currently frozen. The [unified driver interface](#unified-driver-interface) replaces the older dynamic secure element driver for most purposes. The older interface has the advantage of allowing drivers to be dynamically loaded. If there is widespread demand for dynamic loading of secure element drivers, Arm may revive the effort on the older interface or merge it into the unified interface.
For more information, see [PSA secure element driver interface](se/).
diff --git a/docs/psa/se/index.html b/docs/psa/se/index.html
index 04dc3de..73a1a97 100644
--- a/docs/psa/se/index.html
+++ b/docs/psa/se/index.html
@@ -1,6 +1,6 @@
<h1 id="psa-secure-element-driver-interface">PSA secure element driver interface</h1>
<p>The secure element driver interface lets you write drivers for external cryptoprocessors such as secure elements (SE), smart cards and hardware security modules (HSM) that perform operations on keys that never leave the external processor and are accessed only through opaque handles. You can plug such drivers into any implementation of the <a href="../#application-programming-interface">PSA Cryptography API</a>.</p>
-<p><strong>Status: draft</strong> — major changes are still likely.</p>
+<p><strong>Status: obsolescent</strong> — planned to be replaced by the <a href="../index.html#unified-driver-interface">unified driver interface</a>, although the unified interface does not support runtime driver registration.</p>
<p><strong>Documentation</strong>: for now, please see the header file: <a href="https://github.com/ARMmbed/mbedtls/blob/development/include/psa/crypto_se_driver.h"><code>include/psa/crypto_se_driver.h</code></a></p>
<p><strong>Mbed TLS support status</strong>: Partial. Only a few operations are supported: key pair generation, import, export and destruction; signature and verification.</p>
<p><strong>Example</strong>: You can see the code of an <a href="https://github.com/ARMmbed/mbed-os-atecc608a">example driver</a> for the <a href="https://www.microchip.com/wwwproducts/en/ATECC608A">Microchip ATECC608A secure element</a>. See the instructions for the <a href="https://github.com/ARMmbed/mbed-os-example-atecc608a">example application using this driver</a> for how to build <a href="https://github.com/ARMmbed/mbed-os">Mbed OS</a> with this driver.</p>
diff --git a/docs/psa/se/index.md b/docs/psa/se/index.md
index a7652c7..af7a79b 100644
--- a/docs/psa/se/index.md
+++ b/docs/psa/se/index.md
@@ -3,7 +3,7 @@
The secure element driver interface lets you write drivers for external cryptoprocessors such as secure elements (SE), smart cards and hardware security modules (HSM) that perform operations on keys that never leave the external processor and are accessed only through opaque handles.
You can plug such drivers into any implementation of the [PSA Cryptography API](../#application-programming-interface).
-**Status: draft** — major changes are still likely.
+**Status: obsolescent** — planned to be replaced by the [unified driver interface](../index.html#unified-driver-interface), although the unified interface does not support runtime driver registration.
**Documentation**: for now, please see the header file:
[`include/psa/crypto_se_driver.h`](https://github.com/ARMmbed/mbedtls/blob/development/include/psa/crypto_se_driver.h)