PM / devfreq: Set scaling_max_freq to max on OPP notifier error

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>

diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index 4de70bd..66f0a79 100644 (file)
--- a/drivers/devfreq/devfreq.c
+++ b/drivers/devfreq/devfreq.c
@@ -577,8 +577,10 @@ static int devfreq_notifier_call(struct notifier_block *nb, unsigned long type,
                goto out;
 
        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;
+       }
 
        err = update_devfreq(devfreq);