OMAP: move GP timer selection alongside other timer options

[linux-2.6-omap-h63xx.git] / arch / arm / mach-omap2 / Kconfig

diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
index ca24a7a37c3c2725b40511568592dc79ccb8f98f..0a86a88d52852349cb6a7ef02f267428eede3b4f 100644 (file)
--- a/arch/arm/mach-omap2/Kconfig
+++ b/arch/arm/mach-omap2/Kconfig
@@ -132,19 +132,3 @@ config MACH_OVERO
 config MACH_OMAP3_PANDORA
        bool "OMAP3 Pandora"
        depends on ARCH_OMAP3 && ARCH_OMAP34XX
-
-config OMAP_TICK_GPTIMER
-       int "GPTIMER used for system tick timer"
-       depends on ARCH_OMAP2 || ARCH_OMAP3
-       range 1 12
-       default 1
-       help
-         Linux uses one of the twelve on-board OMAP GPTIMER blocks to generate
-         system tick interrupts.  The twelve GPTIMERs have slightly
-         different powerdomain, source clock, and security properties
-         (mostly documented in the OMAP3 TRMs) that can affect the selection
-         of which GPTIMER to use.  The historical default is GPTIMER1.
-         If CONFIG_OMAP_32K_TIMER is selected, Beagle may require GPTIMER12
-         due to hardware sensitivity to glitches on the OMAP 32kHz clock
-         input.
-