| commit | 1cbbe37ac5c78fb59ce02f639d6c4f69b610cf5e | |
| author | Thara Gopinath <thara@ti.com> | |
| Mon, 20 Dec 2010 15:47:21 +0000 (20 21:17 +0530) | ||
| committer | Kevin Hilman <khilman@deeprootsystems.com> | |
| Tue, 21 Dec 2010 22:29:34 +0000 (21 14:29 -0800) | ||
| tree | 9afed62ca4629585c95471adbe5c1c0fae0d4dde | treesnapshot (tar.gz zip) |
| parent | c166381d4013fd32512f124c237f4213ae9888e9 | commitdiff |
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>
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>
| arch/arm/mach-omap2/pm.c | diffblobblamehistory |