Update GCM buffer overlap documentation
This commit updates the GCM buffer overlap documentation to explicity
state that alternative implementations may not support input/output
buffer overlap for GCM encrypt/decrypt functions.
Signed-off-by: Harry Ramsey <harry.ramsey@arm.com>
diff --git a/tf-psa-crypto/drivers/builtin/include/mbedtls/gcm.h b/tf-psa-crypto/drivers/builtin/include/mbedtls/gcm.h
index e620be7..741c814 100644
--- a/tf-psa-crypto/drivers/builtin/include/mbedtls/gcm.h
+++ b/tf-psa-crypto/drivers/builtin/include/mbedtls/gcm.h
@@ -174,7 +174,9 @@
*
* \note The output buffer \p output can be the same as the input
* buffer \p input. If \p output is greater than \p input, they
- * cannot overlap.
+ * cannot overlap. Implementations which require
+ * MBEDTLS_GCM_ALT to be enabled may not provide support
+ * overlapping buffers.
*
* \param ctx The GCM context. This must be initialized.
* \param length The length of the ciphertext to decrypt, which is also
@@ -282,7 +284,9 @@
*
* \note The output buffer \p output can be the same as the input
* buffer \p input. If \p output is greater than \p input, they
- * cannot overlap.
+ * cannot overlap. Implementations which require
+ * MBEDTLS_GCM_ALT to be enabled may not provide support
+ * overlapping buffers.
*
* \param ctx The GCM context. This must be initialized.
* \param input The buffer holding the input data. If \p input_length