Repository navigation
Description
Origin
TrustedFirmware-M project, tf-psa-crypto-drivers:
https://git.trustedfirmware.org/shared/tf-psa-crypto-drivers
Part of the TrustedFirmware.org project family, alongside trusted-firmware-m, tf-m-tests and psa-arch-tests, all three of which Zephyr already carries as modules.
Purpose
Cryptographic drivers implementing the PSA Cryptoprocessor Driver Interface, so that a PSA Crypto core (such as TF-PSA-Crypto) can dispatch operations to vendor hardware crypto accelerators. Drivers are organised by vendor under vendor/; at the pinned revision the repository contains a single vendor driver, vendor/arm/cc3xx, for the Arm CryptoCell (CC3XX) accelerator.
Mode of Integration
As a module. Proposed repository name: tf-psa-crypto-drivers, mirroring the upstream name.
Proposed path: modules/crypto/tf-psa-crypto-drivers, next to the existing modules/crypto/tf-psa-crypto, since TF-PSA-Crypto is expected to dispatch to these drivers directly in future (see below) and the repository is therefore not TF-M specific.
Today Zephyr code never calls into this driver. It is consumed entirely by TF-M: the board build passes its location to TF-M via PSA_CRYPTO_DRIVER_PATH, and TF-M compiles and links it into the secure enclave images.
That is expected to broaden. As @valeriosetti notes below, there are plans for TF-PSA-Crypto to dispatch to these drivers directly, which would let boards without TF-M, or with TF-M disabled, use vendor hardware acceleration. The work in that direction is Mbed-TLS/TF-PSA-Crypto#809 and #110328. The module is therefore not specific to one board or to TF-M.
Maintainership
- maintainers: @npitre (primary), @d3zd3z, @tomi-font
- collaborators: @Vge0rge, @ithinuel, @valeriosetti, @JordanYates
@npitre will do the integration work and the manifest updates. The remaining names mirror the set already covering the sibling TF-M west projects (tf-m-tests, psa-arch-tests), and are proposed subject to their agreement.
Pull Request
#114821 (labelled DNM)
That PR restores fvp_corstone1000/a320 and is currently blocked by exactly this dependency.
Description
fvp_corstone1000/a320 is the only Zephyr board that builds TF-M's native BL1 and BL2 bootloaders. TF-M's corstone1000 platform builds the CC3XX driver unconditionally and links it into BL1, which uses it to verify boot images, so it is a mandatory dependency of that platform rather than an optional accelerator. Setting CRYPTO_HW_ACCELERATOR=OFF does not avoid it: neither the driver fetch nor the BL1 link is conditional on that option.
TF-M satisfies the dependency by cloning this repository itself while configuring the build. Zephyr does not permit build-time fetches, and twister's check_no_nested_git_repos post-build check fails on the repository that then appears under the build directory, so every test on the board is reported as an error even though the build succeeds. This is the sole remaining blocker for re-enabling the platform in CI.
Two alternatives were attempted and rejected on review:
- Pre-installing the driver in the CI container (Dockerfile.base: add the TF-M PSA crypto drivers docker-image#311). Rejected because the fallback path still cloned a repository outside the
zephyrproject-rtosorganisation, circumventing the module hosting policy. - Carrying the driver inside the Zephyr TF-M fork. Rejected in favour of a proper module, as it would increase divergence from upstream TF-M.
Adding the repository as a module resolves it the same way the other TF-M dependencies are already resolved: fetched by the manifest, mirrored under zephyrproject-rtos, with nothing fetched during a build.
Security
The component is itself a cryptographic driver: it implements PSA Crypto operations (hashing, AES, ECDSA, key derivation and related primitives) on Arm CryptoCell hardware. On this platform it is used by TF-M's BL1 to verify the signatures of the images it loads, so it sits on the secure boot path.
Security issues are handled through the TrustedFirmware.org security incident process that covers the TF-M project family, the same process that already applies to the trusted-firmware-m module Zephyr carries. No open CVEs specific to this repository are known.
Zephyr itself does not call the driver, which limits the exposed surface to whatever TF-M chooses to use on platforms that enable CryptoCell.
Dependencies
The repository is self-contained: no submodules, no build-time downloads, four CMake files, roughly 2.9 MB checked out.
It is used indirectly. TF-M includes the driver into its own build when a platform enables CRYPTO_HW_ACCELERATOR; Zephyr's only involvement is passing the path. No Zephyr-side abstraction or glue code is required, and no new Kconfig surface is introduced.
Version or SHA
3a93566c04c4d77a007e6b149e7c06e7b8f0cd8d (2026-04-09)
This is the revision TF-M v2.3 pins in platform/ext/target/arm/drivers/cc3xx/CMakeLists.txt (PSA_CRYPTO_DRIVER_VERSION), so it is the revision TF-M would otherwise fetch. The pin should track whatever the TF-M module expects.
License (SPDX)
BSD-3-Clause
The repository carries the standard three-clause text in license.rst with the Arm non-endorsement clause, and the CC3XX tree is uniformly tagged SPDX-License-Identifier: BSD-3-Clause. It also ships a dco.txt, matching the Developer Certificate of Origin flow used across TrustedFirmware.org.
This is the same licence, under the same text, as the trusted-firmware-m module Zephyr already carries: TF-M's own license.rst is the identical three-clause Arm notice, and its sources are predominantly BSD-3-Clause (3464 files, against 391 Apache-2.0). The sibling TF-M modules tf-m-tests and psa-arch-tests are BSD-3-Clause as well. Integrating this driver therefore introduces no licence that the project does not already carry in this subtree.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
- StatusShow more project fieldsDone
Activity
valeriosetti commentedon Aug 4, 2026
Based on the current state of things, that's correct, TF-M is the only user. However please note that, as far as I know, there are plans to support this repo also from TF-PSA-Crypto directly. The following PRs help in this direction:
So hopefully in a not so far future also non TF-M boards (or with TF-M disabled) will be able to take advantage of HW accelerators provided by vendors.
Given the above, can I suggest something like
modues/crypto/tf-psa-crypto-driversinstead?npitre commentedon Aug 4, 2026
Makes sense, thanks for the pointers. I have updated the proposal accordingly.
valeriosetti commentedon Aug 12, 2026
@npitre I just discovered that the official repo for
tf-psa-crypto-driverswill be hosted by Mbed TLS and its link is: https://github.com/Mbed-TLS/tf-psa-crypto-drivers. I was told by upstream TF-M developers that the one in trustedfimware will just mirror that one, so I suggest picking the Mbed TLS official repo for the Zephyr fork.nashif commentedon Aug 27, 2026
@npitre https://github.com/zephyrproject-rtos/tf-psa-crypto-drivers