-
Notifications
You must be signed in to change notification settings - Fork 2.1k
sys/psa_crypto: usa auto_init module for initialization #21322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes total sense, I did not do this on purpose back then.
You should remove it from the docs, though:
Line 37 in b1932dd
* Call `psa_crypto_init()` before calling any other operation. |
Very good point, thanks. Done. And while at it, I've also moved the documentation to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM :)
26373bb
to
ad80fe9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The doc.txt -> doc.md rename would have been better as a different PR.
Unclear if there are any changes, or just a rename.
At least it's a separate commit: 5e6a539
I've changed The content change can be checked in ad80fe9 |
Thanks everyone! |
Contribution description
Most modules in RIOT are initialized automatically on-start (unless
DISABLE_MODULE += auto_init
is present). Do the same forpsa_crypto
.RFC: Would it be better practice to have a pseudomodule
auto_init_psa_crypto
? I'd argue that the initialization function is pretty small and that I can't think of a reason why one wouldn't want to initialize PSA Crypto from the start up. Maybe @Einhornhool has some opinion on this?Testing procedure
CI should show that the tests still run through.