tests/configs/user-config-test-driver-extension.h in TF-PSA-Crypto contains macro definitions that all follow a specific pattern, and it is supposed to cover all supported cryptographic mechanisms (or at least all the ones for which we have driver support, although including the ones that don't is harmless).
If we add a new mechanism and forget to update this file, we won't be testing the corresponding driver dispatch as expected.
The goal of this task is to generate tests/configs/user-config-test-driver-extension.h automatically, which means some Python code (in generate_test_driver.py?) using our existing code to enumerate PSA crypto mechanisms, plus the instructions for CMake to build this file and have it as a dependency.
3.6 has a similar file, but it is out of scope, since we won't add any more mechanisms to 3.6.
tests/configs/user-config-test-driver-extension.hin TF-PSA-Crypto contains macro definitions that all follow a specific pattern, and it is supposed to cover all supported cryptographic mechanisms (or at least all the ones for which we have driver support, although including the ones that don't is harmless).If we add a new mechanism and forget to update this file, we won't be testing the corresponding driver dispatch as expected.
The goal of this task is to generate
tests/configs/user-config-test-driver-extension.hautomatically, which means some Python code (ingenerate_test_driver.py?) using our existing code to enumerate PSA crypto mechanisms, plus the instructions for CMake to build this file and have it as a dependency.3.6 has a similar file, but it is out of scope, since we won't add any more mechanisms to 3.6.