AP_RangeFinder: fixed VL53L0X semaphore usage #9024
Merged
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
OXINARF
reviewed
Jul 26, 2018
| } | ||
|
|
||
| sensor->init(); | ||
| if (!sensor->init()) { |
There was a problem hiding this comment.
This could have been put right after check_id: if (!sensor->check_id() || !sensor->init()), but what I don't like is the assumption that semaphore is taken - I know with current code it does because of blocking take, but a small change from 0 to 1 and this code might have the same issue as before.
|
Thanks very much for this. I'm sure this was discovered during Copter-3.6 beta testing so the fix is greatly appreciated! |
This was referenced Jul 30, 2018
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.
No description provided.