depends on ARCH_OMAP24XX
select OMAP_DM_TIMER
select ARCH_OMAP_OTG
+ select CPU_V6
config ARCH_OMAP2430
bool "OMAP2430 support"
depends on ARCH_OMAP24XX
select ARCH_OMAP_OTG
+ select CPU_V6
config ARCH_OMAP34XX
bool "OMAP34xx Based System"
bool "OMAP3430 support"
depends on ARCH_OMAP3 && ARCH_OMAP34XX
select ARCH_OMAP_OTG
+ select CPU_V7
comment "OMAP Board Type"
depends on ARCH_OMAP2 || ARCH_OMAP3
depends on MACH_NOKIA_N800
select MACH_NOKIA_N810
+config MACH_NOKIA_RX51
+ bool "Nokia RX-51 board"
+ depends on ARCH_OMAP3 && ARCH_OMAP34XX
+
config MACH_OMAP2_TUSB6010
bool
depends on ARCH_OMAP2 && ARCH_OMAP2420
bool "OMAP 2420 H4 board"
depends on ARCH_OMAP2 && ARCH_OMAP2420
select OMAP_DEBUG_DEVICES
- select GPIOEXPANDER_OMAP
config MACH_OMAP_H4_TUSB
bool "TUSB 6010 EVM board"
depends on ARCH_OMAP2 && ARCH_OMAP2430
config MACH_OMAP_LDP
- bool "OMAP 3 LDP board"
+ bool "OMAP3 LDP board"
depends on ARCH_OMAP3 && ARCH_OMAP34XX
config MACH_OMAP2EVM
bool "Gumstix Overo board"
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.
-
+config MACH_OMAP3_PANDORA
+ bool "OMAP3 Pandora"
+ depends on ARCH_OMAP3 && ARCH_OMAP34XX