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.
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
dispatchdirectory. This means we need to ensure that all of our the dispatch code is in thedispatchdirectory, and that directory contains no other code. Additionally, there should be a way to specify an alternative location instead ofdispatchat 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 ininclude/psa/crypto_driver_contexts_*.h.