Fix sentences after removal of USE_PSA

Some sentences or paragraphs became confusing or meaningless after
removing USE_PSA and only fixing the local context/semantics.

Fix the semantics where needed and remove parts that became meaningless.

Signed-off-by: Janos Follath <janos.follath@arm.com>
This commit is contained in:
Janos Follath 2024-12-08 14:51:07 +00:00
parent 3102c5985e
commit b51b73351d
2 changed files with 2 additions and 4 deletions

View File

@ -295,8 +295,6 @@ Arm welcomes feedback on the design of the API. If you think something could be
Mbed TLS includes a reference implementation of the PSA Cryptography API.
However, it does not aim to implement the whole specification; in particular it does not implement all the algorithms.
The X.509 and TLS code can use PSA cryptography for most operations. See `docs/use-psa-crypto.md` for details.
### PSA drivers
Mbed TLS supports drivers for cryptographic accelerators, secure elements and random generators. This is work in progress. Please note that the driver interfaces are not fully stable yet and may change without notice. We intend to preserve backward compatibility for application code (using the PSA Crypto API), but the code of the drivers may have to change in future minor releases of Mbed TLS.

View File

@ -28,8 +28,8 @@ Compile-time options
We currently have a few compile-time options that are relevant to the migration:
- `MBEDTLS_PSA_CRYPTO_C` - enabled by default, controls the presence of the PSA
Crypto APIs.
- `MBEDTLS_PSA_CRYPTO_C` - enabled by default, controls the presence of the
implementation of PSA Crypto APIs.
- `PSA_CRYPTO_CONFIG` - disabled by default, supports builds with drivers and
without the corresponding software implementation (G5 above).