tests/periph/selftest_shield: fix invalid calls to timer_init() #21006
+49
−16
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
maribu
added
Type: enhancement
maribu
requested review from
leandrolanzieri,
aabadie and
MichelRottleuthner
as code owners
Calling `timer_init()` with unsupported frequencies on some MCUs just selects the closest possible frequency. But e.g. on SAM0, using an unsupported frequency will cause `timer_init()` to fail; which probably is the better option. However, a failing calling to `timer_init()` results in a test failure. This is now worked around by using timer_query_freq() to select a suitable timer frequency that is supported.
maribu
force-pushed
the
tests/periph/selftest_shield/fix-timer_init
branch
from
6483bc2
to
c60f128
Compare
maribu
changed the title
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
Calling
timer_init()with unsupported frequencies on some MCUs just selects the closest possible frequency. But e.g. on SAM0, using an unsupported frequency will causetimer_init()to fail; which probably is the better option.However, a failing calling to
timer_init()results in a test failure. This is now worked around by using timer_query_freq() to select a suitable timer frequency that is supported.Testing procedure
On e.g.
wemos-zeroorarduino-zerothe test should now run to completion. (Note: It will not pass the test, though.) Inmasterthe test will abort on a failed call totimer_init()instead.Issues/PRs references
None