Remove usage of FreeRTOS timers from asyncFreeRtos #44
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
Until now for implementing async schedule functions FreeRTOS timers were in use. This led to a huge overhead because most (re)setting of a timer caused two additional task switches (first to high prio timer task and then back to the active task). This new implementation uses only the task notification mechanism for both executing events and scheduling by specifying the next required timeout of the task using the parameter xTicksToWait of function xTaskNotifyWait. Change-Id: Ieaa3ef298c39f2b11eca9c1ed9c2b8bde9dc2290
SuhashiniNaik
force-pushed
the
cr-125285
branch
from
2e05701 to
c171695
Compare
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.
originates from CR #125285