Hello Bartlomiej,

On Wed, Jul 1, 2015 at 3:10 PM, Bartlomiej Zolnierkiewicz
[off-list ref] wrote:

Exynos5250 based platforms have switched over to use generic
cpufreq driver for cpufreq functionality. So the Exynos
specific cpufreq support for these platforms can be removed.

Based on the earlier work by Thomas Abraham.

Cc: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Javier Martinez Canillas <javier@dowhile0.org>
Cc: Thomas Abraham <redacted>
Reviewed-by: Krzysztof Kozlowski <redacted>
Signed-off-by: Bartlomiej Zolnierkiewicz <redacted>
---
 drivers/cpufreq/Kconfig.arm          |  11 --
 drivers/cpufreq/Makefile             |   1 -
 drivers/cpufreq/exynos-cpufreq.c     |   3 -
 drivers/cpufreq/exynos-cpufreq.h     |  17 ---
 drivers/cpufreq/exynos5250-cpufreq.c | 210 -----------------------------------
 5 files changed, 242 deletions(-)
 delete mode 100644 drivers/cpufreq/exynos5250-cpufreq.c

Reviewed-by: Javier Martinez Canillas <javier@dowhile0.org>

I also tested and on an Exynos5250 Snow Chromebook with
exynos_defconfig + CONFIG_CPUFREQ_DT + CONFIG_CPU_FREQ_GOV_*, using
different governors and see that the cpu0 and cpu1 frequencies are
scaled and that the total number of CPU frequency transitions in
total_trans are incremented.

Tested-by: Javier Martinez Canillas <javier@dowhile0.org>

Best regards,
Javier