Allow integrators to substitute their own dispatch layer #833

New issue

Open

opened 2026-07-08 12:00:14 -05:00 by gilles-peskine-arm · 0 comments

gilles-peskine-arm commented

2026-07-08 12:00:14 -05:00

(Migrated from github.com)

The goal of this issue is to allow integrators to substitute their own dispatch directory. This means we need to ensure that all of our the dispatch code is in the dispatch directory, and that directory contains no other code. Additionally, there should be a way to specify an alternative location instead of dispatch at build time.

Note that the dispatch code includes not only the files that are currently generated from jinja templates by scripts/generate_driver_wrappers.py, but also the multipart operation structure definitions in include/psa/crypto_driver_contexts_*.h.

Some integrators of TF-PSA-Crypto want to plug in a set of drivers, and they want to maintain dispatch code for those drivers in a separate repository. Their dispatch code is C code, not generated using our script parametrized by a JSON description. The goal of this issue is to allow integrators to substitute their own `dispatch` directory. This means we need to ensure that all of our the dispatch code is in the `dispatch` directory, and that directory contains no other code. Additionally, there should be a way to specify an alternative location instead of `dispatch` at build time. Note that the dispatch code includes not only the files that are currently generated from jinja templates by `scripts/generate_driver_wrappers.py`, but also the multipart operation structure definitions in `include/psa/crypto_driver_contexts_*.h`.

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gh-Mbed-TLS/TF-PSA-Crypto#833

No description provided.

Rows
Columns