controller: remove RIOT specific initialization hack#367
Merged
andrzej-kaczmarek merged 2 commits intoapache:masterfrom Mar 8, 2019
Merged
controller: remove RIOT specific initialization hack#367andrzej-kaczmarek merged 2 commits intoapache:masterfrom
andrzej-kaczmarek merged 2 commits intoapache:masterfrom
Conversation
Contributor
|
yes, every call to get element from this queue will be done from |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
We finally added some additional functionality to RIOT's event queue implementation to allow for thread context independent event queue implementation. With this, there is no need anymore to treat the event queue initialization in the controller differently then for other ports.
Only caveat: the code now depends on the fact, that the first call to
ble_npl_eventq_get()must be done from the thread's context, that is supposed to host the targeted event queue. But this should be always the case anyway, right?