drivers/periph_timer: add periph_timer_freq feature #20131
Conversation
The optional feature allows to query the frequency a timer is actually running at. This is especially useful when the MCU is running of an integrated in-silicon RC oscillator, which may run at an actual frequency that differs a lot from the nominal frequency.
maribu
requested review from
smlng,
leandrolanzieri,
aabadie,
MichelRottleuthner,
fjmolinas and
MrKevinWeiss
as code owners
github-actions
bot
added
Area: tests
|
Would you mind adding a single implementation so I can test it. Other than that it makes sense! |
github-actions
bot
added
Area: boards
Did so now for the fe310. Sadly, that is a pretty boring timer :-/ |
|
I'll also squash the fixup that adds a missing |
The FE310 has only a 32.678 kHz RTT that is either clocked by an external watch crystal or an internal oscillator. Since this timer is always present and requires no board configuration, we can add this feature at CPU level.
maribu
force-pushed
the
drivers/periph_timer/timer_freq
branch
from
512d610 to
0f39866
Compare
maribu
added
the
State: WIP
|
Let's put this on a hold. With #16349 finally on its way in, I'm not sure this is a good idea anymore. With #16349 one can just query prior to I do agree that this API can be easier to use. But as this would need to be implemented for each and every peripheral, I'm not sure if the effort to maintain it is worth the convenience. |
|
After a (short) discussion in the matrix room, I close this in favor of #16349 |
Contribution description
The optional feature allows to query the frequency a timer is actually running at. This is especially useful when the MCU is running of an integrated in-silicon RC oscillator, which may run at an actual frequency that differs a lot from the nominal frequency.
Testing procedure
Some PRs to add this feature will be added soonish. The test app has been extended to print the actual frequency.
Issues/PRs references
None