X-Git-Url: http://www.pilppa.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=arch%2Farm%2Fmach-omap2%2FKconfig;h=0a86a88d52852349cb6a7ef02f267428eede3b4f;hb=20752c3fd65bc6e84faebc7341c8495d75c171bc;hp=ca24a7a37c3c2725b40511568592dc79ccb8f98f;hpb=0c8eba8051eb4fd4228e459c0575d6adfe53d13b;p=linux-2.6-omap-h63xx.git

diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
index ca24a7a37c3..0a86a88d528 100644
--- 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.
-