Arch Linux

t0ken

Member

Registered: 2012-06-29

Posts: 29

[SOLVED] cpupower not showing "available frequency steps"

I have an issue with cpupower not showing the "available frequency steps."  I seem to recall there being a way to see this through /proc or /sys too, though I can't remember.  This is on a 2015 Macbook pro.

agoree@dmacbook ~ % sudo cpupower frequency-info
analyzing CPU 0:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 4.00 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 4.00 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 3.27 GHz (asserted by call to hardware).
  boost state support:
    Supported: yes
    Active: yes

Normally, under 'hardware limits' and above 'available cpufreq governors", there'd be a row titled "available frequency steps", showing which frequencies are available.  Example from https://wiki.debian.org/HowTo/CpuFrequencyScaling:

analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 1000 MHz - 1.83 GHz
  available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
  available cpufreq governors: userspace, powersave, conservative, ondemand, performance
  current policy: frequency should be within 1000 MHz and 1.83 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1000 MHz (asserted by call to hardware).
  cpufreq stats: 1.83 GHz:10.34%, 1.33 GHz:0.62%, 1000 MHz:89.04%  (1068280)

Am I missing something?  I wonder, is it b/c the 'intel_pstate' drive does not show these?

Last edited by t0ken (2016-01-26 23:28:58)

tom.ty89

Member

Registered: 2012-11-15

Posts: 897

Re: [SOLVED] cpupower not showing "available frequency steps"

Well yeah pstate work quite differently than the old drivers: https://www.kernel.org/doc/Documentatio … pstate.txt