Commit 8183003e authored by Rafael J. Wysocki's avatar Rafael J. Wysocki

cpufreq: Update scaling_cur_freq documentation

Commit f8475cef "x86: use common aperfmperf_khz_on_cpu() to
calculate KHz using APERF/MPERF" modified the way the scaling_cur_freq
cpufreq policy attribute in sysfs is handled on contemporary
Intel-based x86 systems, so update the documentation to reflect
that change.
Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
parent fab24dcc
...@@ -269,16 +269,16 @@ are the following: ...@@ -269,16 +269,16 @@ are the following:
``scaling_cur_freq`` ``scaling_cur_freq``
Current frequency of all of the CPUs belonging to this policy (in kHz). Current frequency of all of the CPUs belonging to this policy (in kHz).
For the majority of scaling drivers, this is the frequency of the last In the majority of cases, this is the frequency of the last P-state
P-state requested by the driver from the hardware using the scaling requested by the scaling driver from the hardware using the scaling
interface provided by it, which may or may not reflect the frequency interface provided by it, which may or may not reflect the frequency
the CPU is actually running at (due to hardware design and other the CPU is actually running at (due to hardware design and other
limitations). limitations).
Some scaling drivers (e.g. |intel_pstate|) attempt to provide Some architectures (e.g. ``x86``) may attempt to provide information
information more precisely reflecting the current CPU frequency through more precisely reflecting the current CPU frequency through this
this attribute, but that still may not be the exact current CPU attribute, but that still may not be the exact current CPU frequency as
frequency as seen by the hardware at the moment. seen by the hardware at the moment.
``scaling_driver`` ``scaling_driver``
The scaling driver currently in use. The scaling driver currently in use.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment