I have seen that the crypto service has been migrated to mbedcrypto implementation, but at the same time, the crypto engine layer has been removed from the crypto service.
Is there the new plan to add the engine layer again based on the mbedcrypto implementation?
the functionalities that were implemented through the crypto engine layer are now part of the functionalities which are provided directly by mbedcrypto. In particular, mbedcrypto is developing a driver model to allow seamless integration of crypto accelerators and secure elements which comply to the interface specified by the crypto driver model. This is still under development and not part of the mbedcrypto version supported by TF-M.
More details are available directly from the Mbed Crypto repository, in https://github.com/ARMmbed/mbed-crypto/tree/development/include/psa, in particular in crypto_accel_driver.h and crypto_se_driver.h, and in the PDF description here: https://github.com/ARMmbed/mbed-crypto/blob/development/docs/PSACryptoDriverModelSpec.pdf
Thanks for your information about the crypto service.
About the driver model to integrate the crypto accelerators, what is the detail plan or schedule to implement this model? How soon TFM will support thtis feature?
Will the mbed-crypto library be still built into TFM crypto service after the driver model has been added? How we think about the TFM code size with that implementation?