cpus node: Make clock-frequency optional #61
Merged
Conversation
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
Modern CPU implementations overwhelmingly implement frequency scaling,
so there is no real notion of "the current" CPU clock frequency anymore.
Make the "clock-frequency" and "timebase-frequency" property of each CPU
node optional instead of required, and reword the description of the
clock-frequency to only encourage using this property if the CPU speed
is fixed.
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
|
This is the first step to push a patch removing the warning message from arch/arm Linux kernels. I don't think this property makes sense anymore. arm64 Linux seems to ignore it completely, and arm Linux just computes some capacity value for big.LITTLE systems from it. |
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.
Modern CPU implementations overwhelmingly implement frequency scaling, so there is no real notion of "the current" CPU clock frequency anymore.
Make the "clock-frequency" and "timebase-frequency" property of each CPU node optional instead of required, and reword the description of the clock-frequency to only encourage using this property if the CPU speed is fixed.
Signed-off-by: Andre Przywara andre.przywara@arm.com