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.
Adding to cpufrequtils to image, now were able to control the cpu over cpufrequtils .
root@orangepii96:~# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to [email protected], please. analyzing CPU 0:
driver: rda
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 300 us.
hardware limits: 329 MHz - 1.19 GHz
available frequency steps: 329 MHz, 395 MHz, 494 MHz, 988 MHz
available cpufreq governors: ondemand, interactive, performance
current policy: frequency should be within 329 MHz and 988 MHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 988 MHz (asserted by call to hardware).
cpufreq stats: 329 MHz:3.69%, 395 MHz:0.08%, 494 MHz:0.04%, 988 MHz:96.20% (53)