summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorThara Gopinath <thara@ti.com>2010-12-20 21:17:21 +0530
committerKevin Hilman <khilman@deeprootsystems.com>2010-12-21 14:29:34 -0800
commit1cbbe37ac5c78fb59ce02f639d6c4f69b610cf5e (patch)
tree9afed62ca4629585c95471adbe5c1c0fae0d4dde
parentc166381d4013fd32512f124c237f4213ae9888e9 (diff)
downloadop-kernel-dev-1cbbe37ac5c78fb59ce02f639d6c4f69b610cf5e.zip
op-kernel-dev-1cbbe37ac5c78fb59ce02f639d6c4f69b610cf5e.tar.gz
OMAP: pm.c correct the initcall for an early init.
omap2_common_pm_init is the API where generic system devices like mpu, l3 etc get initialized. This has to happen really early on during the boot and not at a later time. This is especially important with the new opp changes as these devices need to be built before the opp tables init happen. Today both are device initcalls and it works just because of the order of compilation. Making this postcore_initcall is ideal because the omap device layer init happens as a core_initcall and typically rest of the driver/device inits are arch_initcall or something lower. Signed-off-by: Thara Gopinath <thara@ti.com> Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
-rw-r--r--arch/arm/mach-omap2/pm.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm/mach-omap2/pm.c b/arch/arm/mach-omap2/pm.c
index 59ca03b..6ec2ee1 100644
--- a/arch/arm/mach-omap2/pm.c
+++ b/arch/arm/mach-omap2/pm.c
@@ -143,5 +143,5 @@ static int __init omap2_common_pm_init(void)
return 0;
}
-device_initcall(omap2_common_pm_init);
+postcore_initcall(omap2_common_pm_init);
OpenPOWER on IntegriCloud