cpufreq: Documentation: fix sampling_down_factor range

The ondemand governor implementation accepts sampling_down_factor values
from 1 to 100000 via MAX_SAMPLING_DOWN_FACTOR, but the documentation in
admin-guide/pm/cpufreq.rst still says the valid range is 1 to 100.

Update the documentation to match the actual code.

Fixes: 2a0e49279850 ("cpufreq: User/admin documentation update and consolidation")
Reviewed-by: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
Signed-off-by: Pengjie Zhang <zhangpengjie2@huawei.com>
Link: https://patch.msgid.link/20260518133457.2408463-1-zhangpengjie2@huawei.com
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

diff --git a/Documentation/admin-guide/pm/cpufreq.rst b/Documentation/admin-guide/pm/cpufreq.rst
index dbe6d23a5d671dd369a98ed6ae00b8397fd6aa53..fdca59c955dcc9dbb06b303f716711b10944c215 100644 (file)
--- a/Documentation/admin-guide/pm/cpufreq.rst
+++ b/Documentation/admin-guide/pm/cpufreq.rst
@@ -516,7 +516,7 @@ This governor exposes the following tunables:
        of those tasks above 0 and set this attribute to 1.
 
 ``sampling_down_factor``
-       Temporary multiplier, between 1 (default) and 100 inclusive, to apply to
+       Temporary multiplier, between 1 (default) and 100000 inclusive, to apply to
        the ``sampling_rate`` value if the CPU load goes above ``up_threshold``.
 
        This causes the next execution of the governor's worker routine (after