drivers/timers: check CONFIG_BOARD_LOOPSPERMSEC != 0 at runtime #17923
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This config is optional for arch timer/alarm since it is used only in very early boot stage
Impact
arch_timer/arch_alarm may generate the assertion if up_ndelay is called in the very early boot stage without the correct CONFIG_BOARD_LOOPSPERMSEC.
Testing
boot with sim:nsh without assert.