summaryrefslogtreecommitdiff
path: root/Documentation/admin-guide/pm
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2025-07-17 20:02:51 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2025-07-17 20:02:51 +0200
commit4f95b5bad62c95e840b41ba78ec1f382f2f8c381 (patch)
tree2e605cafdbd3da9b9a400f4c7441f2abc5f8e988 /Documentation/admin-guide/pm
parent84bb8c1897ad6592b4c5f6f29c02d50c127c0114 (diff)
parent0ae204405095abfbc2d694ee0fbb49bcbbe55c57 (diff)
downloadlinux-next-4f95b5bad62c95e840b41ba78ec1f382f2f8c381.tar.gz
linux-next-4f95b5bad62c95e840b41ba78ec1f382f2f8c381.zip
Merge back earlier cpufreq material for 6.17-rc1
Diffstat (limited to 'Documentation/admin-guide/pm')
-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``
-------------