diff options
| author | Rajendra Nayak <rnayak@ti.com> | 2012-08-09 12:38:22 +0530 |
|---|---|---|
| committer | Kevin Hilman <khilman@ti.com> | 2012-08-09 08:07:54 -0700 |
| commit | 196449de0c886e64b48d01bd7ee153656db92884 (patch) | |
| tree | 3e6b24aa6e93cad3fb7fbe6bfc0eec768c991aca /arch/arm/mach-omap2 | |
| parent | 1b8652142334a8c0729c5c4536a22cfc6fc49297 (diff) | |
| download | linux-3.10-196449de0c886e64b48d01bd7ee153656db92884.tar.gz linux-3.10-196449de0c886e64b48d01bd7ee153656db92884.tar.bz2 linux-3.10-196449de0c886e64b48d01bd7ee153656db92884.zip | |
ARM: OMAP4: Register the OPP table only for 4430 device
The 4430 OPP table was being registered for all other OMAP4 variants
too, like 4460 and 4470 causing issues with cpufreq driver
enabled. 4460 and 4470 devices have different OPPs as compared to
4430, and they should be populated seperately. As long as that
happens, let the OPP table registeration happen only on 4430 device.
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Kevin Hilman <khilman@ti.com>
Diffstat (limited to 'arch/arm/mach-omap2')
| -rw-r--r-- | arch/arm/mach-omap2/opp4xxx_data.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm/mach-omap2/opp4xxx_data.c b/arch/arm/mach-omap2/opp4xxx_data.c index 2293ba27101..c95415da23c 100644 --- a/arch/arm/mach-omap2/opp4xxx_data.c +++ b/arch/arm/mach-omap2/opp4xxx_data.c @@ -94,7 +94,7 @@ int __init omap4_opp_init(void) { int r = -ENODEV; - if (!cpu_is_omap44xx()) + if (!cpu_is_omap443x()) return r; r = omap_init_opp_table(omap44xx_opp_def_list, |