-
Notifications
You must be signed in to change notification settings - Fork 2k
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
cpu/saml21: add compatibily headers for vendor files migration #20850
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Dylan Laduranty <[email protected]>
Signed-off-by: Dylan Laduranty <[email protected]>
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.
From a quick glance at the generating script and the changes, looks good to me. The CI doesn't complain and using the new defines in the periph_config.h
shows that they are available as expected.
Let's get this merged then - thanks for your work! :)
@dylad Looks like CI did find some issue with
|
Yup, |
Contribution description
This PR introduces new compatibility headers for SAML21 MCUs.
New vendor files introduces a small syntax changes in the name of single bit bitfield. There are all now all suffixed with
_Msk
For instance, using the old vendor files, a single bit bitfield would look like:
register = FOO_BAR_1 | FOO_BAR_2;
With the new headers, it should now look like:
register = FOO_BAR_1_Msk | FOO_BAR_2_Msk;
Thus, the idea is to introduce compatibility headers alongside the current (old) headers that RIOT have. Then, to update boards and peripherals driver to match the new syntax.
These files will be deleted as well as old headers at the end of the migration phase.
These files were created using this script
SAML21-based boards configuration using old syntax were convert while at it.
Testing procedure
CI should be enough. This doesn't have any impact on the code or binary size.
Issues/PRs references
Second step of the ongoing Microchip vendor files migration (see #20457)