Make OS_TICKS_PER_SEC configurable for the nRF52 family. #2295
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added a syscfg for the nRF52 family to make it so that OS_TICKS_PER_SEC can be customized on a case by case basis. This is particularly useful for cases where the OS event loop needs to respond more quickly, or with more granularity than at 128 ticks per second.
Should only be increased if necessary, as increasing OS_TICKS_PER_SEC increases system power consumption. Note that OS_TICKS_PER_SEC must be a power of 2 on the nRF52. The range values in the syscfg have all been tested working (blinky works) on the nRF52840 dev kit.
Resolves issue #1785.