boards/stm32f0: introduce default shared clock configuration header #14891
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
aabadie
added
Platform: ARM
aabadie
added
the
CI: ready for build
benpicco
reviewed
Aug 30, 2020
aabadie
force-pushed
the
pr/boards/stm32f0_default_clock
branch
from
e914774 to
48a8d29
Compare
fjmolinas
approved these changes
Sep 1, 2020
41 tasks
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.
Contribution description
This PR is similar to #stm32l1 but applied to the stm32f0 family. In master, all stm32f0 based boards are configured the same way, except the nucleo-f030 and nucleo-f042. There are also some boards that provide an LSE and some not, some having an HSE and others not.
To take this into account, the default configuration has good defaults (HSE set to 8MHz, no LSE and PLL prescalers used in the majority of boards. All theses parameters can be overridden by the boards themselves depending on their configuration.
Doing this removes a bit of code duplication between the boards configurations.
The idea of this PR is first to prepare the migration toward a fully configurable clock like it's done for stm32gx (and stm32l4/wb in #14866), without changing the current situation. Having a common and default configuration file will make things easier (to refactor and to review).
Testing procedure
Issues/PRs references
None