cpufreq: OMAP: use get_cpu_device() instead of omap_device API

OMAP PM core code has moved to using the existing, generic CPU devices
for attaching OPPs, so the CPUfreq driver can now use the generic
get_cpu_device() API instead of the OMAP-specific omap_device API.

This allows us to remove the last <plat/*> include from this driver.

Cc: Paul Walmsley <paul@pwsan.com>
Acked-by: Rafael J. Wysocki <rjw@sisk.pl>
Signed-off-by: Kevin Hilman <khilman@ti.com>

1 files changed, 3 insertions, 5 deletions

diff --git a/drivers/cpufreq/omap-cpufreq.c b/drivers/cpufreq/omap-cpufreq.c
index 5d1f5e442ecc..1f3417a8322d 100644
--- a/drivers/cpufreq/omap-cpufreq.c
+++ b/drivers/cpufreq/omap-cpufreq.c
@@ -30,8 +30,6 @@
 #include <asm/smp_plat.h>
 #include <asm/cpu.h>
 
-#include <plat/omap_device.h>
-
 /* OPP tolerance in percentage */
 #define OPP_TOLERANCE   4
 
@@ -255,10 +253,10 @@ static struct cpufreq_driver omap_driver = {
 
 static int __init omap_cpufreq_init(void)
 {
-        mpu_dev = omap_device_get_by_hwmod_name("mpu");
-        if (IS_ERR(mpu_dev)) {
+        mpu_dev = get_cpu_device(0);
+        if (!mpu_dev) {
                 pr_warning("%s: unable to get the mpu device\n", __func__);
-                return PTR_ERR(mpu_dev);
+                return -EINVAL;
         }
 
         mpu_reg = regulator_get(mpu_dev, "vcc");