Hardcoding the AE control range of MIPI device - #13465
Merged
Merged
Conversation
Nir-Az
reviewed
Oct 30, 2024
| control_range v4l_mipi_device::get_pu_range(rs2_option option) const | ||
| { | ||
| // Auto controls range is trimed to {0,1} range | ||
| if(option >= RS2_OPTION_ENABLE_AUTO_EXPOSURE && option <= RS2_OPTION_ENABLE_AUTO_WHITE_BALANCE) |
Collaborator
There was a problem hiding this comment.
Do we know what is the actual range sent by FW?
According to that we can decide if it's a FW bug and they should fix or a FW limitation and we will fix here.
Nir-Az
approved these changes
Oct 30, 2024
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.
Tracked on LRS-1193