summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorManaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>2016-05-11 12:56:06 +0530
committerKyle Yan <kyan@codeaurora.org>2016-06-03 14:49:03 -0700
commitae40e64b2dafa5451cb0f7413c3bfb2405b886c6 (patch)
tree3a8894e28fde5881c8d3886a1a3adf7e6eab5f71
parent02dd3066a8875959cc66057b37bf37be0f3d6d1c (diff)
msm: thermal: Check clients request just after frequency thread init
KTM frequency mitigation thread initializes during late init call. Prior to this, client can request frequency mitigation. But request will not be processed, since frequency mitigation thread won't be initialized. Notify frequency mitigation thread to aggregate clients current request immediately after thread initialization. Change-Id: Id2425041b14554d58f944794e1b5db273f5ded26 Signed-off-by: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>
-rw-r--r--drivers/thermal/msm_thermal.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/thermal/msm_thermal.c b/drivers/thermal/msm_thermal.c
index 3f435f00e04d..b5cac6cfad60 100644
--- a/drivers/thermal/msm_thermal.c
+++ b/drivers/thermal/msm_thermal.c
@@ -3870,6 +3870,8 @@ init_freq_thread:
pr_err("Failed to create frequency mitigation thread. err:%ld\n",
PTR_ERR(freq_mitigation_task));
return;
+ } else {
+ complete(&freq_mitigation_complete);
}
}