Closed colemickens closed 4 years ago
I think the cpu changes are there too:
analyzing CPU 0:
driver: cpufreq-dt
CPUs which run at the same hardware frequency: 0 1 2 3
CPUs which need to have their frequency coordinated by software: 0 1 2 3
maximum transition latency: 40.0 us
hardware limits: 408 MHz - 1.42 GHz
available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz
available cpufreq governors: ondemand userspace performance schedutil
current policy: frequency should be within 1.20 GHz and 1.42 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency: 1.42 GHz (asserted by call to hardware)
The frequency range looks like the minimum is clamped to 1.2 like the diff specifies.
Thank you!
I'm still working on verifying some of this, but I wanted to send it before I completely forget.
Fixes #16 (supposedly) and fixes #17 (for sure) and changes CPU frequency settings (not totally sure how to confirm).
I'm also wondering if we should set the scheduler to "schedutil" too?