sys/ztimer: rework Kconfig#17165
Conversation
|
I'm fine with this change, I would maybe like the commit message to be more descriptive mentioning that this is a special case. I'm wondering if when tackling the network stack we will to do this kinds of things as well... |
IMO we should try hard to avoid this. The main reason to switch the entry point of ztimer module selection was the (special) case of native RTC, which we still seem to want to work out of the box. In a more conservative point of view native actually does not provide |
There was a problem hiding this comment.
i tested: #17137 with this PR, it does no longer need the the patch to tests/driver_io1_xplained/app.config.test ✔️ -> i like it. (it would have saved me a lot of time.
reviewing the KConfig this looks good to me (but I haven't much experience with Kconfig): this seems to create a intemediate config value which is then used to determine whether the MODULE_XTIMER_ON_ZTIMER is need (sound good to me).
Lets have murdock take a look at this.
There was a problem hiding this comment.
I think this is good to go -maybe you want to ask for a second opinion from someone with more KConfig experience.
My Test: ✔️ , Read: ✔️ , Murdock: ✔️
If merging is done with the current commits (messages) please provide a very descriptive Merge message.
I spent some time looking into this in detail and helping come up with a solution and agree that it is sufficient. |
|
Hmm I was not fast enough to address @fjmolinas comment before this got merged |
I think the merge message that @MrKevinWeiss wrote is very good and solves the "commit message not being descriptive" issue without doing another Murdock cycle. Only the word "special case" maybe missing. |
Ahh cool, missed that. Thanks for the review BTW! |
|
This was the first time I wrote something in the merge commit :) (I also just wanted to prevent another CI cycle) |
Contribution description
This changes the entry point for the ztimer modules in Kconfig, trying to fix:
Testing procedure
Issues/PRs references
Alternative to #17160