diff options
| author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2025-04-25 13:36:21 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-05-09 09:41:36 +0200 |
| commit | 15888cd413f8ffdba42396a764c33eff4ef2ec3c (patch) | |
| tree | b3413b8db45788ce03bda5b2f2dbc90366389f7e /kernel/trace/trace.c | |
| parent | 681400579b88ef35e0e14fcff9c8d205ec0c71c4 (diff) | |
| download | linux-15888cd413f8ffdba42396a764c33eff4ef2ec3c.tar.gz linux-15888cd413f8ffdba42396a764c33eff4ef2ec3c.tar.bz2 linux-15888cd413f8ffdba42396a764c33eff4ef2ec3c.zip | |
cpufreq: Fix setting policy limits when frequency tables are used
commit b79028039f440e7d2c4df6ab243060c4e3803e84 upstream.
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
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/trace/trace.c')
0 files changed, 0 insertions, 0 deletions