summaryrefslogtreecommitdiffstats
path: root/drivers/cpufreq/exynos5440-cpufreq.c
diff options
context:
space:
mode:
authorChen Yu <yu.c.chen@intel.com>2018-01-29 03:27:57 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2018-02-08 10:21:38 +0100
commit70f6bf2a3b7e40c3f802b0ea837762a8bc6c1430 (patch)
tree6ca51a0143f0a89d96e89dc9bc09a2a8e57bd732 /drivers/cpufreq/exynos5440-cpufreq.c
parentcpufreq: scpi: fix error return code in scpi_cpufreq_init() (diff)
downloadlinux-70f6bf2a3b7e40c3f802b0ea837762a8bc6c1430.tar.xz
linux-70f6bf2a3b7e40c3f802b0ea837762a8bc6c1430.zip
cpufreq: intel_pstate: Enable HWP during system resume on CPU0
When maxcpus=1 is in the kernel command line, the BP is responsible for re-enabling the HWP - because currently only the APs invoke intel_pstate_hwp_enable() during their online process - which might put the system into unstable state after resume. Fix this by enabling the HWP explicitly on BP during resume. Reported-by: Doug Smythies <dsmythies@telus.net> Suggested-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by: Yu Chen <yu.c.chen@intel.com> [ rjw: Subject/changelog, minor modifications ] Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/cpufreq/exynos5440-cpufreq.c')
0 files changed, 0 insertions, 0 deletions