msm: thermal: Initialize Vdd scaling max frequency variable
Currently Vdd scaling max frequency variable is not initialized, which leads to wrong aggregation of thermal cpu scaling max frequency request especially during KTM boot up mitigation. Initialize low temperature scaling max frequency variable to UINT_MAX at probe function. Change-Id: I0220b9390cac33d40af0e4419d7451553ba6c5b5 Signed-off-by: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>
This commit is contained in:
parent
e74f5d6e67
commit
ff76e3f64e
1 changed files with 1 additions and 0 deletions
|
@ -5103,6 +5103,7 @@ static void msm_thermal_init_cpu_mit(enum cpu_mit_type cpu_mit)
|
||||||
cpus[cpu].user_max_freq = UINT_MAX;
|
cpus[cpu].user_max_freq = UINT_MAX;
|
||||||
cpus[cpu].shutdown_max_freq = UINT_MAX;
|
cpus[cpu].shutdown_max_freq = UINT_MAX;
|
||||||
cpus[cpu].suspend_max_freq = UINT_MAX;
|
cpus[cpu].suspend_max_freq = UINT_MAX;
|
||||||
|
cpus[cpu].vdd_max_freq = UINT_MAX;
|
||||||
cpus[cpu].user_min_freq = 0;
|
cpus[cpu].user_min_freq = 0;
|
||||||
cpus[cpu].limited_max_freq = UINT_MAX;
|
cpus[cpu].limited_max_freq = UINT_MAX;
|
||||||
cpus[cpu].limited_min_freq = 0;
|
cpus[cpu].limited_min_freq = 0;
|
||||||
|
|
Loading…
Add table
Reference in a new issue