-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drivers/mtd_spi_nor: fix init when only ztimer_msec is used #19908
Conversation
f68cde4
to
6e290fb
Compare
Should we not add an #else so in case neither xtimer nor ztimer m/usec are used it outputs an error (or at least a warning of some sorts)? |
If the driver needs either ztimer [ms/us] or xtimer, why is there no such logic in the Makefile.dep? |
The idea is to have a polling fallback for e.g. use in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK
bors merge |
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Contribution description
If only
ztimer_msec
(and notztimer_usec
) is used, themtd_spi_nor_power()
function will not execute thewait_chip_wake_up
delay.This causes
mtd_init()
to fail (and in a very annoying way: adding debug prints can cause enough of a delay that the init then works again).Testing procedure
tests/drivers/mtd_raw
should work with onlyztimer_msec
instead ofztimer_usec
.Issues/PRs references
wouldn't have happened if we had #19719