-
Notifications
You must be signed in to change notification settings - Fork 747
Basic system clock management for the STM32F4 family #3528
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
…for full implementation
…2xx and stm32f43xx models onlygit status!
…ock calibration + additional tests.
Hello! As discussed last Friday, I reimplemented this pull request using type parameters and trait bounds. What do you think about it? @bradjc @ppannuto Note that documentation is still missing. I'll fix that once the changes are approved. Also, tests still rely on features. Probably I'll reimplement them using the same strategy as for the implementation itself. |
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.
Wow this is great.
One question, should the chip-specific implementations go in the specific chip crates? Is there a benefit to centralizing them?
Hmm, good question. I assumed that you wanted them to be centralized just like as with features. There might be a small benefit from implementing them in the |
I think from the perspective of "if I'm updating/creating a specific variant, I shouldn't have to change the shared crate" it would make sense to me to put the chip-specific content in the specific crates. |
Moved all |
Pull Request Overview
This pull request adds support for basic clock management for the STM32F4 family:
checks
Testing Strategy
This pull request was thoroughly tested through unit tests, integration tests
and logic analyzer. The tests were run on STM32F429ZI Nucleo-144 and STM32F446
Nucleo-64 boards.
TODO or Help Wanted
TODO:
Documentation Updated
/docs
.Formatting
make prepush
.