ztimer: pull ztimer_periph_rtt for ZTIMER_MSEC if available#16553
ztimer: pull ztimer_periph_rtt for ZTIMER_MSEC if available#16553jia200x merged 2 commits intoRIOT-OS:masterfrom
Conversation
7f0f6ff to
00bd117
Compare
|
Applied offline suggestion from @leandrolanzieri, each CLOCK can configure a different backend. |
|
LGTM, can't say much about the Kconfig part, though. @jia200x @leandrolanzieri mind to take a look? (Murdock shows some errors). |
|
One difference that I see, is that with the change introduced in Kconfig, where each clock allows to select a backend, now the RTC backend is included, which did not happen before. This causes in native to also bring xtimer, as RTC in native is done with xtimer :/ Perhaps add it as an exception? |
Indeed for some reason xtiemr got pulled in... looking into it |
|
Murdock is happy this time, @leandrolanzieri do you think everything is OK? |
The Kconfig looks good to me! |
|
@kaspar030 @leandrolanzieri may I squash? |
|
Go ahead! |
5a079da to
3e4e664
Compare

Contribution description
With #16546
ztimer_periph_rttcan always be included since all rtt are capable of supplying a msec timer, so this PR includes it by default.I'm not sure how the Kconfig dependency should be adapted, I gave it a go but maybe @leandrolanzieri could take a second look.
Testing procedure
Included modules should be the same for the affected pkgs,
rttis included when possible otherwiseztimer_msecfallbacks toperiph_timer,Issues/PRs references
Takeover of #16334