From c93c4ed6533ee0f840068ddedcad9d9988916590 Mon Sep 17 00:00:00 2001 From: Gilles Peskine Date: Mon, 3 Aug 2020 13:38:03 +0200 Subject: [PATCH] Remove the paragraph about declaring application needs It's out of scope. Signed-off-by: Gilles Peskine --- docs/proposed/psa-driver-interface.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/docs/proposed/psa-driver-interface.md b/docs/proposed/psa-driver-interface.md index 4402540d2..3ffcc361c 100644 --- a/docs/proposed/psa-driver-interface.md +++ b/docs/proposed/psa-driver-interface.md @@ -5,7 +5,7 @@ This document describes an interface for cryptoprocessor drivers in the PSA cryp This specification is work in progress and should be considered to be in a beta stage. There is ongoing work to implement this interface in Mbed TLS, which is the reference implementation of the PSA Cryptography API. At this stage, Arm does not expect major changes, but minor changes are expected based on experience from the first implementation and on external feedback. -Time-stamp: "2020/08/03 09:34:23 GMT" +Time-stamp: "2020/08/03 11:27:22 GMT" ## Introduction @@ -514,10 +514,6 @@ In a multithreaded environment, the driver may only call these two functions fro ## How to use drivers from an application -### Declaring which cryptographic mechanism an application needs - -TODO: an application requirements description, broadly similar to driver capabilities. - ### Using transparent drivers Transparent drivers linked into the library are automatically used for the mechanisms that they implement.