fix for the case where there are multiple tickers firing at nearly the s... #583
Conversation
This file contains hidden or 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
|
Hi, does this fix #539 ? You can reference the issues from github via commit message, or name of the branch. It will be closed automatically once merged. |
0xc0170
added a commit
that referenced
this pull request
Oct 21, 2014
HAL: NRF51 - fix for the case where there are multiple tickers firing (issue #539)
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.
...ame time
Here's the main fix:
There is a limit on how close app_timers can be setup to fire one after another; and I was not respect these thresholds. This would get exposed when users would setup tickers to fire at nearly the same time.