driver-only-builds: add Restrictions section
Signed-off-by: Valerio Setti <valerio.setti@nordicsemi.no>
diff --git a/docs/driver-only-builds.md b/docs/driver-only-builds.md
index 7b4b480..0fb4378 100644
--- a/docs/driver-only-builds.md
+++ b/docs/driver-only-builds.md
@@ -290,6 +290,15 @@
the driver. Only functions belonging to legacy modules which are disabled won't
be available in this configuration.
+### Restrictions
+
+- If an algorithm other than GCM and CCM (see
+ ["Partial acceleration for CCM/GCM"](#partial-acceleration-for-ccmgcm) below)
+ is enabled but not accelerated, then all key types than can be used with it
+ will need to be built-in;
+- if a key type is enabled but not accelerated, then all algorithms than can be
+ used with it will need to be built-in.
+
### Legacy <-> PSA matching
It should be noticed that the matching between legacy (i.e. `MBEDTLS_xxx_C`)
@@ -339,7 +348,7 @@
with the following conditions on the underlying key types:
- CCM/GCM can either use legacy key type modules `MBEDTLS_[AES|ARIA|CAMELLIA]_C`
or their accelerated version, as described in section
- ["Partial acceleration for CCM/GCM"](#partial-acceleration-for-CCM/GCM).
+ ["Partial acceleration for CCM/GCM"](#partial-acceleration-for-ccmgcm).
- ChaChaPoly instead can only rely on legacy key type module `MBEDTLS_CHACHA20_C`
and algorithm `MBEDTLS_POLY1305_C`.