summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorShashank Balaji <shashank.mahadasyam@sony.com>2025-05-27 21:59:10 +0900
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2025-06-18 21:33:01 +0200
commit221504a63419bc3ef6e72deb42f9f8476eb83538 (patch)
tree9921a61db032d1278ea90915ce700979633b8fb1
parent2e1185c9d7b4f890614e891ae1414653b35b88e3 (diff)
cpufreq: docs: userspace: Explain HW coordination influence
Extend the "scaling_setspeed" sysfs attribute description in the userspace governor documentation to cover possible differences between the requested and actual CPU frequency. Signed-off-by: Shashank Balaji <shashank.mahadasyam@sony.com> Link: https://patch.msgid.link/20250527-userspace-governor-doc-v2-2-0e22c69920f2@sony.com [ rjw: Subject and changelog edits ] Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
-rw-r--r--Documentation/admin-guide/pm/cpufreq.rst4
1 files changed, 3 insertions, 1 deletions
diff --git a/Documentation/admin-guide/pm/cpufreq.rst b/Documentation/admin-guide/pm/cpufreq.rst
index 2d74af7f0efe..cacb9f0307dd 100644
--- a/Documentation/admin-guide/pm/cpufreq.rst
+++ b/Documentation/admin-guide/pm/cpufreq.rst
@@ -398,7 +398,9 @@ policy limits change after that.
This governor does not do anything by itself. Instead, it allows user space
to set the CPU frequency for the policy it is attached to by writing to the
-``scaling_setspeed`` attribute of that policy.
+``scaling_setspeed`` attribute of that policy. Though the intention may be to
+set an exact frequency for the policy, the actual frequency may vary depending
+on hardware coordination, thermal and power limits, and other factors.
``schedutil``
-------------