Hi,
Regarding question1, we have developed the PSA driver interface for the Arm CryptoCell 312 and the reference code is available here: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/lib/ext/cry...
The upstream work has been tracked here for reference: https://developer.trustedfirmware.org/tag/psa_cryptoprocessor_driver_interfa...
Thanks, Antonio
-----Original Message----- From: mathieu.rondonneau--- via mbed-tls mbed-tls@lists.trustedfirmware.org Sent: Monday, June 27, 2022 18:27 To: mbed-tls@lists.trustedfirmware.org Subject: [mbed-tls] *_ALT vs PSA for HW crypto and upstreaming
Hi mbed-tls Team,
PSA crypto API for HW acceleration seems pretty new. Question1: is there some reference code or project I could poke around to see how it is being used?
Currently I have added (locally) a set of driver to make use of our HW crypto using the *_ALT way (the old way?) and for what I understand, the PSA API is the "new way" to do things. But It is still unclear how vendor do upstream there HW acceleration drivers. If this part is kept in another repo, then the mbedTLS build does not have any "hooks" to pull-in the vendor specific code to build the mbedTLS library with.
The current implementation seems to be agnostic to any vendor specific HW so I am wondering if there is a "standard" way for vendor to upstream their mbedTLS HW acceleration code that would be built as part of mbedTLS library.
I have posted a similar thread to the "issue" ticket of the mbedtls repo for reference: https://github.com/Mbed-TLS/mbedtls/issues/5975 Thanks for any feedback/pointers/ideas. Regards, -Mathieu