summaryrefslogtreecommitdiffstats
path: root/drivers/clocksource
diff options
context:
space:
mode:
authorSimon Horman <horms+renesas@verge.net.au>2013-03-05 15:40:42 +0900
committerSimon Horman <horms+renesas@verge.net.au>2013-03-13 02:24:36 +0900
commite903a031402c8dccc675b2f0cf8af40ac89163b0 (patch)
tree833b8413e5349cea8fdd633fe977ae959a0391dd /drivers/clocksource
parent118aee4dd91cf3c0b9546788ef66b65d3e9e31b1 (diff)
downloadop-kernel-dev-e903a031402c8dccc675b2f0cf8af40ac89163b0.zip
op-kernel-dev-e903a031402c8dccc675b2f0cf8af40ac89163b0.tar.gz
clocksource: sh_cmt: Set initcall level to subsys
The reason for this is to ensure that CMT is probed earlier than with its previous initcall level, module init. This came up as a problem with using 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. Boot tested on: armadillo800eva, mackerel and kzm9g Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Diffstat (limited to 'drivers/clocksource')
-rw-r--r--drivers/clocksource/sh_cmt.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/clocksource/sh_cmt.c b/drivers/clocksource/sh_cmt.c
index b72b724..08d0c41 100644
--- a/drivers/clocksource/sh_cmt.c
+++ b/drivers/clocksource/sh_cmt.c
@@ -838,7 +838,7 @@ static void __exit sh_cmt_exit(void)
}
early_platform_init("earlytimer", &sh_cmt_device_driver);
-module_init(sh_cmt_init);
+subsys_initcall(sh_cmt_init);
module_exit(sh_cmt_exit);
MODULE_AUTHOR("Magnus Damm");
OpenPOWER on IntegriCloud