PM / devfreq: Set scaling_max_freq to max on OPP notifier error
[ Upstream commit e7cc792d00049c874010b398a27c3cc7bc8fef34 ] The devfreq_notifier_call functions will update scaling_min_freq and scaling_max_freq when the OPP table is updated. If fetching the maximum frequency fails then scaling_max_freq remains set to zero which is confusing. Set to ULONG_MAX instead so we don't need special handling for this case in other places. Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com> Reviewed-by: Matthias Kaehlcke <mka@chromium.org> Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
committed by
Greg Kroah-Hartman
parent
6b2c3bb311
commit
56f1c5108d
@@ -547,8 +547,10 @@ static int devfreq_notifier_call(struct notifier_block *nb, unsigned long type,
|
|||||||
goto out;
|
goto out;
|
||||||
|
|
||||||
devfreq->scaling_max_freq = find_available_max_freq(devfreq);
|
devfreq->scaling_max_freq = find_available_max_freq(devfreq);
|
||||||
if (!devfreq->scaling_max_freq)
|
if (!devfreq->scaling_max_freq) {
|
||||||
|
devfreq->scaling_max_freq = ULONG_MAX;
|
||||||
goto out;
|
goto out;
|
||||||
|
}
|
||||||
|
|
||||||
err = update_devfreq(devfreq);
|
err = update_devfreq(devfreq);
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user