1 comment "OMAP Core Type"
5 bool "OMAP24xx Based System"
9 bool "OMAP2420 support"
10 depends on ARCH_OMAP24XX
15 bool "OMAP2430 support"
16 depends on ARCH_OMAP24XX
20 bool "OMAP34xx Based System"
24 bool "OMAP3430 support"
25 depends on ARCH_OMAP3 && ARCH_OMAP34XX
28 comment "OMAP Board Type"
29 depends on ARCH_OMAP2 || ARCH_OMAP3
31 config MACH_OMAP_GENERIC
32 bool "Generic OMAP board"
33 depends on ARCH_OMAP2 && ARCH_OMAP24XX
35 config MACH_NOKIA_N800
37 depends on ARCH_OMAP2420
38 select VIDEO_TCM825X if VIDEO_OMAP2 && VIDEO_HELPER_CHIPS_AUTO
39 select CBUS if VIDEO_TCM825X
40 select CBUS_RETU if VIDEO_TCM825X
41 select MENELAUS if VIDEO_TCM825X
42 select OMAP_GPIO_SWITCH
44 config MACH_NOKIA_N810
46 depends on MACH_NOKIA_N800
48 config MACH_NOKIA_N810_WIMAX
49 bool "Nokia N810 WiMAX"
50 depends on MACH_NOKIA_N800
51 select MACH_NOKIA_N810
53 config MACH_OMAP2_TUSB6010
55 depends on ARCH_OMAP2 && ARCH_OMAP2420
56 default y if MACH_NOKIA_N800
59 bool "OMAP 2420 H4 board"
60 depends on ARCH_OMAP2 && ARCH_OMAP2420
61 select OMAP_DEBUG_DEVICES
62 select GPIOEXPANDER_OMAP
64 config MACH_OMAP_H4_TUSB
65 bool "TUSB 6010 EVM board"
66 depends on MACH_OMAP_H4
67 select MACH_OMAP2_TUSB6010
69 Set this if you've got a TUSB6010 high speed USB board.
70 You may need to consult the schematics for your revisions
71 of the Menelaus and TUSB boards, and make changes to be
72 sure this is set up properly for your board stack.
74 Be sure to select OTG mode operation, not host-only or
77 config MACH_OMAP_H4_OTG
78 bool "Use USB OTG connector, not device connector (S1.10)"
79 depends on MACH_OMAP_H4
81 Set this if you've set S1.10 (on the mainboard) to use the
82 Mini-AB (OTG) connector and OTG transceiver with the USB0
83 port, instead of the Mini-B ("download") connector with its
86 Note that the "download" connector can be used to bootstrap
87 the system from the OMAP mask ROM. Also, since this is a
88 development platform, you can also force the OTG port into
89 a non-OTG operational mode.
91 config MACH_OMAP2_H4_USB1
92 bool "Use USB1 port, not UART2 (S3.3)"
93 depends on MACH_OMAP_H4
95 Set this if you've set SW3.3 (on the CPU card) so that the
96 expansion connectors receive USB1 signals instead of UART2.
98 config MACH_OMAP_APOLLON
99 bool "OMAP 2420 Apollon board"
100 depends on ARCH_OMAP2 && ARCH_OMAP2420
102 config MACH_OMAP_2430SDP
103 bool "OMAP 2430 SDP board"
104 depends on ARCH_OMAP2 && ARCH_OMAP2430
107 bool "OMAP3 LDP board"
108 depends on ARCH_OMAP3 && ARCH_OMAP34XX
111 bool "OMAP 2530 EVM board"
112 depends on ARCH_OMAP2 && ARCH_OMAP24XX
114 config MACH_OMAP_3430SDP
115 bool "OMAP 3430 SDP board"
116 depends on ARCH_OMAP3 && ARCH_OMAP34XX
119 bool "OMAP 3530 EVM board"
120 depends on ARCH_OMAP3 && ARCH_OMAP34XX
122 config MACH_OMAP3_BEAGLE
123 bool "OMAP3 BEAGLE board"
124 depends on ARCH_OMAP3 && ARCH_OMAP34XX
127 bool "Gumstix Overo board"
128 depends on ARCH_OMAP3 && ARCH_OMAP34XX
130 config OMAP_TICK_GPTIMER
131 int "GPTIMER used for system tick timer"
132 depends on ARCH_OMAP2 || ARCH_OMAP3
136 Linux uses one of the twelve on-board OMAP GPTIMER blocks to generate
137 system tick interrupts. The twelve GPTIMERs have slightly
138 different powerdomain, source clock, and security properties
139 (mostly documented in the OMAP3 TRMs) that can affect the selection
140 of which GPTIMER to use. The historical default is GPTIMER1.
141 If CONFIG_OMAP_32K_TIMER is selected, Beagle may require GPTIMER12
142 due to hardware sensitivity to glitches on the OMAP 32kHz clock