Lines Matching refs:driver

12 This document assumes that you already have a working driver.
13 Otherwise, please see the [PSA driver example and
14 guide](psa-driver-example-and-guide.md) for information on writing a
15 driver.
17 In order to have some mechanism provided only by a driver, you'll want
23 and want them to have access to the algorithms provided by your driver. (See
31 In addition, for each mechanism you want provided only by your driver:
42 For example, if you want SHA-256 to be provided only by a driver, you'll want
48 driver-only mechanisms. Note that this is already a requirement for any use of
82 It is possible to have all hash operations provided only by a driver.
98 a hash algorithm that is provided only by a driver, as mentioned in [General
103 provided by a driver or built-in, you should use the following macros:
134 It is possible to have most ECC operations provided only by a driver:
141 - you have driver support for ECC public and using private keys (that is,
144 - you have driver support for all ECC curves that are enabled (that is, for
161 - you have driver support for all enabled ECC key pair operations - that is,
173   fully provided by a driver,
175   fully provided by a driver,
189 driver or built-in, you should use the following macros:
199 for the p256-m driver that's provided with the library, those macros are
226 At the moment, there is no driver support for interruptible operations
238 ### Limitations regarding "mixed" builds (driver and built-in)
240 In order for a build to be driver-only (no built-in implementation), all the
254 a driver accelerating `PUBLIC_KEY`, `KEY_PAIR_BASIC`, `KEY_PAIR_IMPORT`,
255 `KEY_PAIR_EXPORT` but not `KEY_PAIR_GENERATE`. (Note: currently the driver
288 It is possible for all RSA operations to be provided only by a driver.
302 Unlike other mechanisms, for now in configurations with driver-only RSA, only
304 driver-only RSA even if `MBEDTLS_USE_PSA_CRYPTO` is enabled.
307 interested in wider driver-only support for RSA, please let us know.
313 driver. More precisely, for each desired combination of key type and
378   for use with `mbedtls_cipher_cmac_xxx`. (Note: if there is driver support for
428 algorithm) in order to work with a driver.
450   a driver.)