msm: thermal: Remove proactive vdd restriction during probe
Vdd restriction probe will apply mitigation, which will be cleared later during the KTM boot mitigation. KTM now initializes the data structures to do this mitigation only after vdd restriction probe. So remove this pro-active mitigation in the probe function. KTM boot mitigation will be started immediately after the KTM probe and can take care of this mitigation. CRs-Fixed: 1010111 Change-Id: Ica59aeb0c94581e3c37b5b7df16c187ced45c28a Signed-off-by: Ram Chandrasekar <rkumbako@codeaurora.org>
This commit is contained in:
parent
a58645dc68
commit
a004a8c07b
1 changed files with 0 additions and 14 deletions
|
@ -5378,15 +5378,6 @@ static int vdd_restriction_reg_init(struct platform_device *pdev)
|
|||
for (i = 0; i < rails_cnt; i++) {
|
||||
if (rails[i].freq_req == 1) {
|
||||
usefreq |= BIT(i);
|
||||
check_freq_table();
|
||||
/*
|
||||
* Restrict frequency by default until we have made
|
||||
* our first temp reading
|
||||
*/
|
||||
if (freq_table_get)
|
||||
ret = vdd_restriction_apply_freq(&rails[i], 0);
|
||||
else
|
||||
pr_info("Defer vdd rstr freq init.\n");
|
||||
} else {
|
||||
rails[i].reg = devm_regulator_get(&pdev->dev,
|
||||
rails[i].name);
|
||||
|
@ -5404,11 +5395,6 @@ static int vdd_restriction_reg_init(struct platform_device *pdev)
|
|||
rails[i].name);
|
||||
return ret;
|
||||
}
|
||||
/*
|
||||
* Restrict votlage by default until we have made
|
||||
* our first temp reading
|
||||
*/
|
||||
ret = vdd_restriction_apply_voltage(&rails[i], 0);
|
||||
}
|
||||
}
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue