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+ <[email protected]> # 5.16+
Closes: https://lore.kernel.org/linux-pm/[email protected]/
Reported-by: Stephan Gerhold <[email protected]>
Signed-off-by: Rafael J. Wysocki <[email protected]>
Tested-by: Stephan Gerhold <[email protected]>
Reviewed-by: Lifeng Zheng <[email protected]>
Link: https://patch.msgid.link/[email protected]

0 files changed, 0 insertions, 0 deletions