summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSimon Horman <horms+renesas@verge.net.au>2013-03-05 07:40:42 +0100
committerSimon Horman <horms+renesas@verge.net.au>2013-03-12 18:24:36 +0100
commitb9773c3f52540ada159dc135c07653be010deee7 (patch)
tree30ece3516def443f5e057c096d42d976c0e54437
parentclocksource: sh_cmt: Set initcall level to subsys (diff)
downloadlinux-b9773c3f52540ada159dc135c07653be010deee7.tar.xz
linux-b9773c3f52540ada159dc135c07653be010deee7.zip
clocksource: sh_tmu: Set initcall level to subsys
The reason for this is to ensure that TMU is probed earlier than with its previous initcall level, module init. This came up as a problem with using CMT as a clock source kzm9g-reference which does not make use of early timers or devices. In that scenario initialisation of SDHI and MMCIF both stall on msleep() calls due to the absence of a initialised clock source. The purpose of this change is to keep the TMU code in sync with the CMT code which has been modified in a similar manner.. Boot tested on: mackerel. Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
-rw-r--r--drivers/clocksource/sh_tmu.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/clocksource/sh_tmu.c b/drivers/clocksource/sh_tmu.c
index b4502edce2a1..78b8dae49628 100644
--- a/drivers/clocksource/sh_tmu.c
+++ b/drivers/clocksource/sh_tmu.c
@@ -549,7 +549,7 @@ static void __exit sh_tmu_exit(void)
}
early_platform_init("earlytimer", &sh_tmu_device_driver);
-module_init(sh_tmu_init);
+subsys_initcall(sh_tmu_init);
module_exit(sh_tmu_exit);
MODULE_AUTHOR("Magnus Damm");