Enable reading core/h264/v3d/isp frequency minimum from system config if set #25
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
Corrected line mismatch... sorry for that.
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.
In version 0.5.5, the minimum clock frequencies for the GPU cells are hard-coded to 250. This PRs approach is to first see if core_freq_min/h264_freq_min/v3d_freq_min/isp_freq_min is set, if not, check if gpu_freq_min is set, if none of them, default do 250.
Also, there is a change in the limits used for colorization for V3D as I found it is always active (like the Core) and not just on demand (as i.e. the h264).
Fixes #24
Let me know if further information is needed.