Makefile.dep: periph_init based on USEMODULE#13639
Conversation
gschorcht
left a comment
There was a problem hiding this comment.
Works now with USEMODULE=periph_rtc and FEATURES_RQUIRED=periph_rtc.
|
@fjmolinas Thanks for contributing the change. |
|
Thanks for the review! |
|
Now modules |
Damn, sorry about this. |
Indeed, I didn't realize that. I just focused on the modules I was looking for. Hm. Maybe it is better to revert this PR. I can live with the |
It could be just filtered out as @maribu did here https://github.com/RIOT-OS/RIOT/blob/ea5122e7e466483a136f2cec2bc50b9686ea4e86/Makefile.features_modules. |
I'm not familiar with the revert policy, but I did not test this well enough, so maybe a revert is better. |
I would just create a PR to add filtering this out. As those are pseudo-modules anyway, no harm is done. It is just a cosmetic issue. |
PR RIOT-OS#13639 cused periph_init_common and periph_init_init to be added to USEMODULES, this PR fixes it.
|
Figured out another issue caused by this one, quite a big |
|
If the |
Contribution description
In #13511 @gschorcht pointed out the later PR changed the behaviour when adding
periph_%MODULEs via the commandline. Sinceperiph_initcheck was based onFEATURES_USEDit didn't take into account if it was added directly as aUSEMODULE.This PR now make the rule check
USEMODULEinstead ofFEATURES_USEDto restore the previous behavior.Testing procedure
testing procedure in drivers/periph_common: add periph_init% modules #13511
With this PR
periph_rtc periph_init_rtcshow uponly
periph_rtcin master:NOTE: the right way to add periph depdencies should still be through
FEATURES_REQUIRED, but since it is not how mostMODULEs are added It made sense adding this handling.Issues/PRs references
#13511