Skip to contentSkip to conversation

ARM: OMAP: hrtimers/dyntick support for OMAP2 GP-timers

PATCH In review Kevin Hilman 2 participants 2 messages May 11, 2007 – May 16, 2007

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ARM: OMAP: hrtimers/dyntick support for OMAP2 GP-timers

This patch converts the GP-timer layer to use the clocksource/clockevent interface provided by the new GENERIC_TIME and GENERIC_CLOCKEVENT layers.

Doing so enables use of the new hrtimers and dynticks features on OMAP2.

A quick test of hrtimers using Thomas Gleixner's cyclictest on a 2430SDP shows min/avg/max userspace latencies of 38/50/850 usec.

A quick test of dyntick using /proc/timer_stats on an idle system shows an avg. of ~5 events/sec over a 10 second period.

---
 arch/arm/Kconfig               |    1 
 arch/arm/mach-omap2/timer-gp.c |  139 +++++++++++++++++++++++++++++++++++------
 arch/arm/plat-omap/Kconfig     |    3 
 3 files changed, 122 insertions(+), 21 deletions(-)
arch/arm/Kconfig +1 -0
Index: dev/arch/arm/Kconfig
===================================================================
@@ -381,6 +381,7 @@ config ARCH_OMAP
 	bool "TI OMAP"
 	select GENERIC_GPIO
 	select GENERIC_TIME
+	select GENERIC_CLOCKEVENTS
 	help
 	  Support for TI's OMAP platform (OMAP1 and OMAP2).
 
arch/arm/mach-omap2/timer-gp.c +121 -18

175 lines not on this page · raw message

arch/arm/plat-omap/Kconfig +0 -3
Index: dev/arch/arm/plat-omap/Kconfig
===================================================================
@@ -11,7 +11,6 @@ choice
 
 config ARCH_OMAP1
 	bool "TI OMAP1"
-	select GENERIC_CLOCKEVENTS
 
 config ARCH_OMAP2
 	bool "TI OMAP2"
@@ -150,8 +149,6 @@ config OMAP_MPU_TIMER
 config OMAP_32K_TIMER
 	bool "Use 32KHz timer"
 	depends on ARCH_OMAP16XX || ARCH_OMAP24XX
-	select GENERIC_TIME
-	select GENERIC_CLOCKEVENTS
 	help
 	  Select this option if you want to enable the OMAP 32KHz timer.
 	  This timer saves power compared to the OMAP_MPU_TIMER, and has

--

maintainer
#1 lore raw
Quoted 4 lines · Kevin Hilman

This patch converts the GP-timer layer to use the clocksource/clockevent interface provided by the new GENERIC_TIME and GENERIC_CLOCKEVENT layers.

Quoted 8 lines

Doing so enables use of the new hrtimers and dynticks features on OMAP2.

A quick test of hrtimers using Thomas Gleixner's cyclictest on a 2430SDP shows min/avg/max userspace latencies of 38/50/850 usec.

A quick test of dyntick using /proc/timer_stats on an idle system shows an avg. of ~5 events/sec over a 10 second period.

Pushing today.

Tony