ARM: clocksource: Initialise early

Initialise clock sources early, since some subsystems rely on them to
initialize.

This came up when working on DT support for the kzm9g board.
The prototype does not use early timers and I found that the
CMT clocksource needs to be initialised before the MMCIF MMC driver.

Cc: linux-kernel@vger.kernel.org
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>

diff --git a/drivers/Makefile b/drivers/Makefile
index 7863b9fee50bbc33793a2acb2f104c34c22b2bd0..f156db55b455ec1c17dbac37449ee60c614aa7b9 100644 (file)
--- a/drivers/Makefile
+++ b/drivers/Makefile
@@ -37,6 +37,11 @@ obj-$(CONFIG_XEN)            += xen/
 # regulators early, since some subsystems rely on them to initialize
 obj-$(CONFIG_REGULATOR)                += regulator/
 
+# clocksource early, since some subsystems rely on them to initialize
+ifndef CONFIG_ARCH_USES_GETTIMEOFFSET
+obj-y                          += clocksource/
+endif
+
 # tty/ comes before char/ so that the VT console is the boot-time
 # default.
 obj-y                          += tty/
@@ -114,9 +119,6 @@ obj-y                               += firmware/
 obj-$(CONFIG_CRYPTO)           += crypto/
 obj-$(CONFIG_SUPERH)           += sh/
 obj-$(CONFIG_ARCH_SHMOBILE)    += sh/
-ifndef CONFIG_ARCH_USES_GETTIMEOFFSET
-obj-y                          += clocksource/
-endif
 obj-$(CONFIG_DCA)              += dca/
 obj-$(CONFIG_HID)              += hid/
 obj-$(CONFIG_PPC_PS3)          += ps3/