diff options
| author | Shivnandan Kumar <quic_kshivnan@quicinc.com> | 2024-02-27 14:43:51 +0530 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-04-03 15:28:22 +0200 |
| commit | ed87a423756a206fb8a5fa0b2c12d1060fa3b2ff (patch) | |
| tree | a8ba79469f89df050d481808bd352dfb414ea4e0 /kernel | |
| parent | 66e2c41b0c80deab19904ce373c229c14080f3c4 (diff) | |
| download | linux-ed87a423756a206fb8a5fa0b2c12d1060fa3b2ff.tar.gz linux-ed87a423756a206fb8a5fa0b2c12d1060fa3b2ff.tar.bz2 linux-ed87a423756a206fb8a5fa0b2c12d1060fa3b2ff.zip | |
cpufreq: Limit resolving a frequency to policy min/max
[ Upstream commit d394abcb12bb1a6f309c1221fdb8e73594ecf1b4 ]
Resolving a frequency to an efficient one should not transgress
policy->max (which can be set for thermal reason) and policy->min.
Currently, there is possibility where scaling_cur_freq can exceed
scaling_max_freq when scaling_max_freq is an inefficient frequency.
Add a check to ensure that resolving a frequency will respect
policy->min/max.
Cc: All applicable <stable@vger.kernel.org>
Fixes: 1f39fa0dccff ("cpufreq: Introducing CPUFREQ_RELATION_E")
Signed-off-by: Shivnandan Kumar <quic_kshivnan@quicinc.com>
[ rjw: Whitespace adjustment, changelog edits ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions