There exist SoCs that need some special setup procedure for their 
architected-timer
to work. Therefore allow arch_timer_init to be called from such specialized
clocksources.

Signed-off-by: Heiko Stuebner <[email protected]>
---
 drivers/clocksource/arm_arch_timer.c | 2 +-
 drivers/clocksource/arm_arch_timer.h | 7 +++++++
 2 files changed, 8 insertions(+), 1 deletion(-)
 create mode 100644 drivers/clocksource/arm_arch_timer.h

diff --git a/drivers/clocksource/arm_arch_timer.c 
b/drivers/clocksource/arm_arch_timer.c
index 5163ec1..55116d6 100644
--- a/drivers/clocksource/arm_arch_timer.c
+++ b/drivers/clocksource/arm_arch_timer.c
@@ -635,7 +635,7 @@ static void __init arch_timer_common_init(void)
        arch_timer_arch_init();
 }
 
-static void __init arch_timer_init(struct device_node *np)
+void __init arch_timer_init(struct device_node *np)
 {
        int i;
 
diff --git a/drivers/clocksource/arm_arch_timer.h 
b/drivers/clocksource/arm_arch_timer.h
new file mode 100644
index 0000000..af3974d
--- /dev/null
+++ b/drivers/clocksource/arm_arch_timer.h
@@ -0,0 +1,7 @@
+/*
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+
+void __init arch_timer_init(struct device_node *np);
-- 
1.9.0


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to