Signed-off-by: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> --- arch/arm/mach-omap2/Kconfig | 2 +- arch/arm/plat-omap/Kconfig | 15 +++++++++++++++ 2 files changed, 16 insertions(+), 1 deletions(-) diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig index 3754b79..1085f04 100644 --- a/arch/arm/mach-omap2/Kconfig +++ b/arch/arm/mach-omap2/Kconfig @@ -58,4 +58,4 @@ config MACH_OVERO config MACH_OMAP3_PANDORA bool "OMAP3 Pandora" - depends on ARCH_OMAP3 && ARCH_OMAP34XX \ No newline at end of file + depends on ARCH_OMAP3 && ARCH_OMAP34XX diff --git a/arch/arm/plat-omap/Kconfig b/arch/arm/plat-omap/Kconfig index 91f8b8b..e37a1a2 100644 --- a/arch/arm/plat-omap/Kconfig +++ b/arch/arm/plat-omap/Kconfig @@ -167,6 +167,21 @@ config OMAP_32K_TIMER_HZ Kernel internal timer frequency should be a divisor of 32768, such as 64 or 128. +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. + config OMAP_DM_TIMER bool "Use dual-mode timer" depends on ARCH_OMAP16XX || ARCH_OMAP24XX || ARCH_OMAP34XX -- 1.6.1 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
