-
Notifications
You must be signed in to change notification settings - Fork 244
GPIOx cleanup and improvement #717
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
f03a747
to
cc31431
Compare
Please, rebase your branch on master. |
05a94b5
to
8f62eae
Compare
f145153
to
8549c41
Compare
New modifications :
|
It may be better to put the v1,v2,v3 stuff into a separate PR ? |
@adamgreig or @newAM, would you possibly have some spare time to review this ? |
gpio_wl_with_brr.yaml is removed and its content is moved into gpio_wl.yaml
This allows to do some factorisation between STM32G0 and L0 on one side and STM32L5 on the other. Note: v3 is basically the same as v2 but ST seems to have decided to change some names starting from STM32L0.
8549c41
to
2500848
Compare
I just rebased it on top of master and resolved conflicts. |
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.
Thanks for the pull-request!
This looks good to me; I will wait for another person to review because there are a lot of changes here.
change is done to: - GPIOx.BRR.BRx match patterns - GPIOx.LCKR.LCKx match patterns
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.
Checked the generated output, overall much less code; 10107 insertions(+), 16189 deletions(-); lots more variants alias each other. That's really great because GPIOs take the longest to compile because they have the largest volume of code.
bors r+
Build succeeded: |
Uh oh!
There was an error while loading. Please reload this page.