cpu/native: fix bug in periph_timer [backport 2023.10] #20049
Merged
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.
Backport of #20009
Contribution description
While debugging #18977 (comment) it became obvious that the
periph_timer
innative
is broken and issues early IRQs. This replaces the use ofsetitimer
that cannot use a monotonic clock source withtimer_settime()
.Testing procedure
I have some non-publishable code that tests if the time an ISR fires in terms of
timer_read()
is no earlier than the time expected. This occasionally triggered withmaster
, but I didn't see any of these issues anymore with this PR. I guess I should revive my PR to spice up the periph timer tests and add a polished version of this and let this run for an hour or two.The tests ins
tests/periph/timer*
should still succeed onnative
. (They do for me in a container runningriot/riotbuild
).Issues/PRs references
Found while debugging #18977 (comment)