aboutsummaryrefslogtreecommitdiffstats
path: root/mm
diff options
context:
space:
mode:
authorMikulas Patocka <mpatocka@redhat.com>2015-02-09 13:38:17 -0500
committerBen Hutchings <ben@decadent.org.uk>2015-05-09 23:16:16 +0100
commitdc4dc270e30142f941c00f975dfb85a3a332592a (patch)
tree4e4067ba76d15fca86198114b63625910278f275 /mm
parent59195960edc4de55cfa89bdf7e46199ac3638589 (diff)
downloadkernel_samsung_smdk4412-dc4dc270e30142f941c00f975dfb85a3a332592a.zip
kernel_samsung_smdk4412-dc4dc270e30142f941c00f975dfb85a3a332592a.tar.gz
kernel_samsung_smdk4412-dc4dc270e30142f941c00f975dfb85a3a332592a.tar.bz2
cpufreq: speedstep-smi: enable interrupts when waiting
commit d4d4eda23794c701442e55129dd4f8f2fefd5e4d upstream. On Dell Latitude C600 laptop with Pentium 3 850MHz processor, the speedstep-smi driver sometimes loads and sometimes doesn't load with "change to state X failed" message. The hardware sometimes refuses to change frequency and in this case, we need to retry later. I found out that we need to enable interrupts while waiting. When we enable interrupts, the hardware blockage that prevents frequency transition resolves and the transition is possible. With disabled interrupts, the blockage doesn't resolve (no matter how long do we wait). The exact reasons for this hardware behavior are unknown. This patch enables interrupts in the function speedstep_set_state that can be called with disabled interrupts. However, this function is called with disabled interrupts only from speedstep_get_freqs, so it shouldn't cause any problem. Signed-off-by: Mikulas Patocka <mpatocka@redhat.com Acked-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions