diff options
author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2025-04-25 14:36:21 +0300 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2025-04-28 15:36:41 +0300 |
commit | b79028039f440e7d2c4df6ab243060c4e3803e84 (patch) | |
tree | d43c68fe6df26b914ac8033be2ae06b0a54cb44c /tools/lib/api/fs/tracing_path.c | |
parent | 3d59224947b024c9b2aa6e149a1537d449adb828 (diff) | |
download | linux-b79028039f440e7d2c4df6ab243060c4e3803e84.tar.xz |
cpufreq: Fix setting policy limits when frequency tables are used
Commit 7491cdf46b5c ("cpufreq: Avoid using inconsistent policy->min and
policy->max") overlooked the fact that policy->min and policy->max were
accessed directly in cpufreq_frequency_table_target() and in the
functions called by it. Consequently, the changes made by that commit
led to problems with setting policy limits.
Address this by passing the target frequency limits to __resolve_freq()
and cpufreq_frequency_table_target() and propagating them to the
functions called by the latter.
Fixes: 7491cdf46b5c ("cpufreq: Avoid using inconsistent policy->min and policy->max")
Cc: 5.16+ <stable@vger.kernel.org> # 5.16+
Closes: https://lore.kernel.org/linux-pm/aAplED3IA_J0eZN0@linaro.org/
Reported-by: Stephan Gerhold <stephan.gerhold@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Stephan Gerhold <stephan.gerhold@linaro.org>
Reviewed-by: Lifeng Zheng <zhenglifeng1@huawei.com>
Link: https://patch.msgid.link/5896780.DvuYhMxLoT@rjwysocki.net
Diffstat (limited to 'tools/lib/api/fs/tracing_path.c')
0 files changed, 0 insertions, 0 deletions