1 comment "OMAP Core Type"
5 bool "OMAP24xx Based System"
9 bool "OMAP2420 support"
10 depends on ARCH_OMAP24XX
16 bool "OMAP2430 support"
17 depends on ARCH_OMAP24XX
22 bool "OMAP34xx Based System"
26 bool "OMAP3430 support"
27 depends on ARCH_OMAP3 && ARCH_OMAP34XX
31 comment "OMAP Board Type"
32 depends on ARCH_OMAP2 || ARCH_OMAP3
34 config MACH_OMAP_GENERIC
35 bool "Generic OMAP board"
36 depends on ARCH_OMAP2 && ARCH_OMAP24XX
38 config MACH_NOKIA_N800
40 depends on ARCH_OMAP2420
41 select VIDEO_TCM825X if VIDEO_OMAP2 && VIDEO_HELPER_CHIPS_AUTO
42 select CBUS if VIDEO_TCM825X
43 select CBUS_RETU if VIDEO_TCM825X
44 select MENELAUS if VIDEO_TCM825X
45 select OMAP_GPIO_SWITCH
47 config MACH_NOKIA_N810
49 depends on MACH_NOKIA_N800
51 config MACH_NOKIA_N810_WIMAX
52 bool "Nokia N810 WiMAX"
53 depends on MACH_NOKIA_N800
54 select MACH_NOKIA_N810
56 config MACH_OMAP2_TUSB6010
58 depends on ARCH_OMAP2 && ARCH_OMAP2420
59 default y if MACH_NOKIA_N800
62 bool "OMAP 2420 H4 board"
63 depends on ARCH_OMAP2 && ARCH_OMAP2420
64 select OMAP_DEBUG_DEVICES
65 select GPIOEXPANDER_OMAP
67 config MACH_OMAP_H4_TUSB
68 bool "TUSB 6010 EVM board"
69 depends on MACH_OMAP_H4
70 select MACH_OMAP2_TUSB6010
72 Set this if you've got a TUSB6010 high speed USB board.
73 You may need to consult the schematics for your revisions
74 of the Menelaus and TUSB boards, and make changes to be
75 sure this is set up properly for your board stack.
77 Be sure to select OTG mode operation, not host-only or
80 config MACH_OMAP_H4_OTG
81 bool "Use USB OTG connector, not device connector (S1.10)"
82 depends on MACH_OMAP_H4
84 Set this if you've set S1.10 (on the mainboard) to use the
85 Mini-AB (OTG) connector and OTG transceiver with the USB0
86 port, instead of the Mini-B ("download") connector with its
89 Note that the "download" connector can be used to bootstrap
90 the system from the OMAP mask ROM. Also, since this is a
91 development platform, you can also force the OTG port into
92 a non-OTG operational mode.
94 config MACH_OMAP2_H4_USB1
95 bool "Use USB1 port, not UART2 (S3.3)"
96 depends on MACH_OMAP_H4
98 Set this if you've set SW3.3 (on the CPU card) so that the
99 expansion connectors receive USB1 signals instead of UART2.
101 config MACH_OMAP_APOLLON
102 bool "OMAP 2420 Apollon board"
103 depends on ARCH_OMAP2 && ARCH_OMAP2420
105 config MACH_OMAP_2430SDP
106 bool "OMAP 2430 SDP board"
107 depends on ARCH_OMAP2 && ARCH_OMAP2430
110 bool "OMAP3 LDP board"
111 depends on ARCH_OMAP3 && ARCH_OMAP34XX
114 bool "OMAP 2530 EVM board"
115 depends on ARCH_OMAP2 && ARCH_OMAP24XX
117 config MACH_OMAP_3430SDP
118 bool "OMAP 3430 SDP board"
119 depends on ARCH_OMAP3 && ARCH_OMAP34XX
122 bool "OMAP 3530 EVM board"
123 depends on ARCH_OMAP3 && ARCH_OMAP34XX
125 config MACH_OMAP3_BEAGLE
126 bool "OMAP3 BEAGLE board"
127 depends on ARCH_OMAP3 && ARCH_OMAP34XX
130 bool "Gumstix Overo board"
131 depends on ARCH_OMAP3 && ARCH_OMAP34XX
133 config MACH_OMAP3_PANDORA
135 depends on ARCH_OMAP3 && ARCH_OMAP34XX
137 config OMAP_TICK_GPTIMER
138 int "GPTIMER used for system tick timer"
139 depends on ARCH_OMAP2 || ARCH_OMAP3
143 Linux uses one of the twelve on-board OMAP GPTIMER blocks to generate
144 system tick interrupts. The twelve GPTIMERs have slightly
145 different powerdomain, source clock, and security properties
146 (mostly documented in the OMAP3 TRMs) that can affect the selection
147 of which GPTIMER to use. The historical default is GPTIMER1.
148 If CONFIG_OMAP_32K_TIMER is selected, Beagle may require GPTIMER12
149 due to hardware sensitivity to glitches on the OMAP 32kHz clock