video: edid: initialize HDMI VSDB length - #104
Open
berringtoni36-commits wants to merge 1 commit into
Open
berringtoni36-commits wants to merge 1 commit into
berringtoni36-commits wants to merge 1 commit into
Conversation
Initialize hdmi_len before parsing CEA data blocks so builds without an HDMI VSDB have a defined length.
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
1 participant
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.
Initialize the HDMI VSDB length before parsing CEA data blocks.
When a CEA extension has no HDMI VSDB, hdmi_len remains uninitialized and GCC's -Wmaybe-uninitialized can fail an RK3128 build. Initialize it to zero so the existing HDMI VSDB guard has a defined length.
Fixes #85
Tested:
No target-board HDMI validation was performed.