doc/guides: Add Timer Information to Porting Boards Guide#21795
Merged
crasbe merged 1 commit intoRIOT-OS:masterfrom Oct 15, 2025
Merged
doc/guides: Add Timer Information to Porting Boards Guide#21795crasbe merged 1 commit intoRIOT-OS:masterfrom
Porting Boards Guide#21795crasbe merged 1 commit intoRIOT-OS:masterfrom
Conversation
crasbe
added
Type: enhancement
AnnsAnns
requested changes
Oct 15, 2025
crasbe
commented
Oct 15, 2025
Teufelchen1
reviewed
Oct 15, 2025
AnnsAnns
approved these changes
Oct 15, 2025
Member
AnnsAnns
left a comment
AnnsAnns
left a comment
There was a problem hiding this comment.
Good enough for me, ty crasbe :)
crasbe
force-pushed
the
pr/guide_porting_boards
branch
from
2b27155 to
7cacc4f
Compare
Contributor
Author
|
Thanks for the reviews :) |
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
5 participants
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
As discovered in #21776,
ztimerdoes not check if the.maxfield in thetimer_configstructure matches theTIMER_0_MAX_VALUE(if defined at all) definition. If it is not set, it assumes 32-bit width, which can lead to odd effects.I extended the guide a bit to point to this issue.
Testing procedure
Check that the documentation still looks good
Issues/PRs references
Discoverd in #21776.