boards/xg23-pk6068a: remove HFXO_FREQ and LFXO_FREQ#22295
Merged
Conversation
5871753 to
5d6b27f
Compare
5d6b27f to
659ad66
Compare
benpicco
approved these changes
May 19, 2026
Member
Author
|
The only validation I can do, is to see if the variables end up at the right place. That's the case: |
Prior to the use of Gecko SDK 4.5, RIOT shipped with patched vendor files, such as `system_xxx.c`. These system files included `periph_config.h`, which allowd one to redefine `HFXO_FREQ` and `LFXO_FREQ`. This was not intended, and other EFM32-based boards documented this to redefine this using compiler defines. After all, a board configuration is considered to be somewhat pre-defined and static. With the new Gecko SDK 4.5, this (unintended) feature got lost for the `xg23-pk6068a` board. To bring it in-line with the other boards, remove the defines, and document how it should be used. Within the codebase, `LFXO_FREQ` was used for ztimer configuration. Similar to the other boards, this has been replaced with a static value. Behind the scenes, the vendor `system_xxx.c` file will still use the same values.
659ad66 to
dc9133c
Compare
Member
Author
|
Rebased to see if this fixes the build sanity checks: |
Contributor
|
No, merging this would fix it though: #22307 I merged some PRs for the RIOT docker container. |
Contributor
|
And since #22255 was merged, you don't even have to rebase afterwards. Just rerun the static test job. |
This file contains hidden or 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
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
Prior to the use of Gecko SDK 4.5, RIOT shipped with patched vendor files, such as
system_xxx.c. These system files includedperiph_config.h, which allowed one to redefineHFXO_FREQandLFXO_FREQ.This was not intended, and other EFM32-based boards documented this to redefine this using compiler defines. After all, a board configuration is considered to be somewhat pre-defined and static.
With the new Gecko SDK 4.5, this (unintended) feature got lost for the
xg23-pk6068aboard. To bring it in-line with the other boards, remove the defines, and document how it should be used. Do note that, for some reason, Silicon Labs decided not to prefix the aforementioned defines withEFM32_.Within the codebase,
LFXO_FREQwas used for ztimer configuration. Similar to the other boards, this has been replaced with a static value.Behind the scenes, the vendor
system_xxx.cfile will still use the same values.Testing procedure
The compiler defines are equal to the values used in
system_efr32zg.c, so there is effectively no change if you don't override these values. See https://github.com/basilfx/RIOT-gecko-sdk/blob/master/dist/platform/Device/SiliconLabs/EFR32ZG23/Source/system_efr32zg23.c.I do not own this board, so I cannot test if the documented alternative works.
Issues/PRs references
Regression introduced in #22040
Fixes #22283
Declaration of AI-Tools / LLMs usage:
AI-Tools / LLMs that were used are: