-
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
boards/seeedstudio-gd32: fix HXTAL clock in Kconfig #19129
boards/seeedstudio-gd32: fix HXTAL clock in Kconfig #19129
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.
ACK
The default Kconfig value is the same as the one set by default without Kconfig.
bors merge (backport got already |
🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set. |
bors merge |
Build succeeded: |
Thanks for reviewing and merging. |
19131: boards/seeedstudio-gd32: fix HXTAL clock in Kconfig [backport 2023.01] r=aabadie a=gschorcht # Backport of #19129 ### Contribution description This PR fixes the wrong default value of `CLOCK_HXTAL` in Kconfig introduced with PR #19109. It was accidentally set to the default value of 80 MHz instead of 8 MHz. ### Testing procedure ``` python3 dist/tools/compile_test/compile_like_murdock.py -a tests/shell -b seeedstudio-gd32 -j8 ``` Without the PR the command gives: ``` tests/shell seeedstudio-gd32 FAIL: Kconfig hash mismatch ``` WIth the PR the compile test should pass: ``` tests/shell seeedstudio-gd32 PASS ``` ### Issues/PRs references Co-authored-by: Gunar Schorcht <gunar@schorcht.net>
Contribution description
This PR fixes the wrong default value of
CLOCK_HXTAL
in Kconfig introduced with PR #19109. It was accidentally set to the default value of 80 MHz instead of 8 MHz.Testing procedure
Without the PR the command gives:
WIth the PR the compile test should pass:
Issues/PRs references