[COMMON] thermal: samsung: Remove update cpufreq_state as 0.

Kernel 4.4, CPUFreq's policy will keep after hotplug in/out.
So, we don't need to reset the last cooling state after hotplug in.

Resolved migration conflicts from kernel 4.9 to 4.14.
- rename cpufreq_device -> cpufreq_cdev

Change-Id: I336ef6cec9444108c8c76ae8ea4cce0d2d239590
Signed-off-by: Hyeonseong Gil <hs.gil@samsung.com>

diff --git a/drivers/thermal/samsung/exynos_tmu.c b/drivers/thermal/samsung/exynos_tmu.c
index 628e6148e775845b346cc662d551f06ec52306cf..e3af8479ff5f4fb23b113193fda3602b757b6678 100644 (file)
--- a/drivers/thermal/samsung/exynos_tmu.c
+++ b/drivers/thermal/samsung/exynos_tmu.c
@@ -1198,7 +1198,6 @@ struct pm_qos_request thermal_cpu_hotplug_request;
 static int exynos_throttle_cpu_hotplug(void *p, int temp)
 {
        struct exynos_tmu_data *data = p;
-       struct cpufreq_cooling_device *cpufreq_cdev = (struct cpufreq_cooling_device *)data->cool_dev->devdata;
        int ret = 0;
 
        temp = temp / MCELSIUS;
@@ -1212,7 +1211,6 @@ static int exynos_throttle_cpu_hotplug(void *p, int temp)
                        pm_qos_update_request(&thermal_cpu_hotplug_request,
                                                NR_CPUS);
                        is_cpu_hotplugged_out = false;
-                       cpufreq_cdev->cpufreq_state = 0;
                }
        } else {
                if (temp >= data->hotplug_out_threshold) {