EXYNOS: bugfix on retrieving old_index from freqs.old
authorJonghwa Lee <jonghwa3.lee@samsung.com>
Fri, 20 Jul 2012 02:54:02 +0000 (02:54 +0000)
committerRafael J. Wysocki <rjw@sisk.pl>
Fri, 20 Jul 2012 09:58:34 +0000 (11:58 +0200)
commit53df1ad52545854fc34d336b26f3086b2fb2d6f7
treeb861a4e6f166e6accf9bcaf0a60a95d73acd5ba4
parent84a1caf1453c3d44050bd22db958af4a7f99315c
EXYNOS: bugfix on retrieving old_index from freqs.old

The policy might have been changed since last call of target().
Thus, using cpufreq_frequency_table_target(), which depends on
policy to find the corresponding index from a frequency, may return
inconsistent index for freqs.old. Thus, old_index should be
calculated not based on the current policy.

We have been observing such issue when scaling_min/max_freq were
updated and sometimes cuased system lockups deu to incorrectly
configured voltages.

Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
drivers/cpufreq/exynos-cpufreq.c