PSA Crypto: Enabled compatibility with drivers V1 and V2. #170
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rcasallas-silabs
requested review from
jepenven-silabs,
jmartinez-silabs,
mkardous-silabs and
selissia
as code owners
jmartinez-silabs
approved these changes
Feb 14, 2024
mkardous-silabs
approved these changes
Feb 15, 2024
rcasallas-silabs
force-pushed
the
psa_driver_compatibility_v123
branch
from
b51cc8a
to
2e64054
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem / Feature
PSA crypt keys created with drivers V1+V2 cannot be used by applications running driver V3 alone. This causes Matter application to stop working when updated to latest GSDK.
Change overview
Drivers V1 and V2 enabled for all boards. This enables PSA to automatically upgrade old keys to V3.
Testing
Tested on EFR32MG12.