Lines Matching refs:new
17 needs to be changed to use new APIs. For a more detailed account of what's
18 implemented, see `docs/use-psa-crypto.md`, where new APIs are about (G2), and
33 (G1 above), as well as the availability of some new APIs (G2 above).
77 It will then require follow-up work to make use of the new PSA API in
132 - Provide a new definition (conditionally on `USE_PSA_CRYPTO`) of wrapper
170 - Provide a new way to set up a context that causes operations on that context
183 There are two variants of this strategy: one where using the new setup
211 - PK (for G2): opt-in use of PSA (new key type)
341 The strategy for steps 1 and 2 above will introduce new situations: code that
347 In order to cater to these new needs, new families of macros are introduced in
359 the new macros in the hope of avoiding confusion.
361 Note: the new macros supplement but do not replace the existing macros:
369 the new macros from `legacy_or_psa.h`.
377 supporting existing features in new types of builds, testing will not involve
378 adding cases to the test suites, but instead adding new components in `all.sh`
433 introducing new context types) would provide to users.
506 (based on IANA values or custom enums), as is currently done in the new