Thara Gopinath <th...@ti.com> writes: > 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
Why postcore? there are several other inicalls earlier than device_initcall. Also, does this actually work? Is the driver core initialized at postcore_initcall time such that omap_devices w/platform_device creation actually works? Kevin > Signed-off-by: Thara Gopinath <th...@ti.com> > --- > arch/arm/mach-omap2/pm.c | 2 +- > 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); -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
