1 menu "TI OMAP/AM/DM/DRA Family"
2 depends on ARCH_MULTI_V6 || ARCH_MULTI_V7
6 depends on ARCH_MULTI_V6
9 select SOC_HAS_OMAP2_SDRC
13 depends on ARCH_MULTI_V7
15 select ARM_CPU_SUSPEND if PM
16 select OMAP_INTERCONNECT
18 select PM_RUNTIME if CPU_IDLE
19 select SOC_HAS_OMAP2_SDRC
23 depends on ARCH_MULTI_V7
25 select ARCH_NEEDS_CPU_IDLE_COUPLED if SMP
26 select ARM_CPU_SUSPEND if PM
27 select ARM_ERRATA_720789
29 select HAVE_ARM_SCU if SMP
30 select HAVE_ARM_TWD if SMP
31 select OMAP_INTERCONNECT
32 select PL310_ERRATA_588369 if CACHE_L2X0
33 select PL310_ERRATA_727915 if CACHE_L2X0
35 select PM_RUNTIME if CPU_IDLE
36 select ARM_ERRATA_754322
37 select ARM_ERRATA_775420
41 depends on ARCH_MULTI_V7
43 select ARM_CPU_SUSPEND if PM
45 select HAVE_ARM_SCU if SMP
46 select HAVE_ARM_TWD if SMP
47 select HAVE_ARM_ARCH_TIMER
48 select ARM_ERRATA_798181 if SMP
52 depends on ARCH_MULTI_V7
54 select ARM_CPU_SUSPEND if PM
58 depends on ARCH_MULTI_V7
61 select MACH_OMAP_GENERIC
62 select MIGHT_HAVE_CACHE_L2X0
66 depends on ARCH_MULTI_V7
68 select ARM_CPU_SUSPEND if PM
70 select HAVE_ARM_ARCH_TIMER
75 select ARCH_HAS_BANDGAP
76 select ARCH_HAS_HOLES_MEMORYMODEL
78 select ARCH_REQUIRE_GPIOLIB
80 select GENERIC_IRQ_CHIP
81 select MACH_OMAP_GENERIC
88 Systems based on OMAP2, OMAP3, OMAP4 or OMAP5
93 menu "TI OMAP2/3/4 Specific Features"
95 config ARCH_OMAP2PLUS_TYPICAL
96 bool "Typical OMAP configuration"
102 select MENELAUS if ARCH_OMAP2
103 select NEON if CPU_V7
106 select TWL4030_CORE if ARCH_OMAP3 || ARCH_OMAP4
107 select TWL4030_POWER if ARCH_OMAP3 || ARCH_OMAP4
110 Compile a kernel suitable for booting most boards
112 config SOC_HAS_OMAP2_SDRC
113 bool "OMAP2 SDRAM Controller support"
115 config SOC_HAS_REALTIME_COUNTER
116 bool "Real time free running counter"
117 depends on SOC_OMAP5 || SOC_DRA7XX
120 comment "OMAP Core Type"
121 depends on ARCH_OMAP2
124 bool "OMAP2420 support"
125 depends on ARCH_OMAP2
128 select SOC_HAS_OMAP2_SDRC
131 bool "OMAP2430 support"
132 depends on ARCH_OMAP2
134 select SOC_HAS_OMAP2_SDRC
137 bool "OMAP3430 support"
138 depends on ARCH_OMAP3
140 select SOC_HAS_OMAP2_SDRC
143 bool "TI81XX support"
144 depends on ARCH_OMAP3
147 config OMAP_PACKAGE_CBC
150 config OMAP_PACKAGE_CBB
153 config OMAP_PACKAGE_CUS
156 config OMAP_PACKAGE_CBP
159 comment "OMAP Legacy Platform Data Board Type"
160 depends on ARCH_OMAP2PLUS
162 config MACH_OMAP_GENERIC
165 config MACH_OMAP2_TUSB6010
167 depends on ARCH_OMAP2 && SOC_OMAP2420
168 default y if MACH_NOKIA_N8X0
170 config MACH_OMAP3_BEAGLE
171 bool "OMAP3 BEAGLE board"
172 depends on ARCH_OMAP3
174 select OMAP_PACKAGE_CBB
176 config MACH_DEVKIT8000
177 bool "DEVKIT8000 board"
178 depends on ARCH_OMAP3
180 select OMAP_PACKAGE_CUS
183 bool "OMAP3 LDP board"
184 depends on ARCH_OMAP3
186 select OMAP_PACKAGE_CBB
188 config MACH_OMAP3530_LV_SOM
189 bool "OMAP3 Logic 3530 LV SOM board"
190 depends on ARCH_OMAP3
192 select OMAP_PACKAGE_CBB
194 Support for the LogicPD OMAP3530 SOM Development kit
195 for full description please see the products webpage at
196 http://www.logicpd.com/products/development-kits/texas-instruments-zoom%E2%84%A2-omap35x-development-kit
198 config MACH_OMAP3_TORPEDO
199 bool "OMAP3 Logic 35x Torpedo board"
200 depends on ARCH_OMAP3
202 select OMAP_PACKAGE_CBB
204 Support for the LogicPD OMAP35x Torpedo Development kit
205 for full description please see the products webpage at
206 http://www.logicpd.com/products/development-kits/zoom-omap35x-torpedo-development-kit
209 bool "Gumstix Overo board"
210 depends on ARCH_OMAP3
212 select OMAP_PACKAGE_CBB
214 config MACH_OMAP3517EVM
215 bool "OMAP3517/ AM3517 EVM board"
216 depends on ARCH_OMAP3
218 select OMAP_PACKAGE_CBB
220 config MACH_CRANEBOARD
221 bool "AM3517/05 CRANE board"
222 depends on ARCH_OMAP3
223 select OMAP_PACKAGE_CBB
225 config MACH_OMAP3_PANDORA
227 depends on ARCH_OMAP3
229 select OMAP_PACKAGE_CBB
230 select REGULATOR_FIXED_VOLTAGE if REGULATOR
232 config MACH_TOUCHBOOK
233 bool "OMAP3 Touch Book"
234 depends on ARCH_OMAP3
236 select OMAP_PACKAGE_CBB
238 config MACH_OMAP_3430SDP
239 bool "OMAP 3430 SDP board"
240 depends on ARCH_OMAP3
242 select OMAP_PACKAGE_CBB
244 config MACH_NOKIA_N810
247 config MACH_NOKIA_N810_WIMAX
250 config MACH_NOKIA_N8X0
251 bool "Nokia N800/N810"
252 depends on SOC_OMAP2420
254 select MACH_NOKIA_N810
255 select MACH_NOKIA_N810_WIMAX
257 config MACH_NOKIA_RX51
258 bool "Nokia N900 (RX-51) phone"
259 depends on ARCH_OMAP3
261 select OMAP_PACKAGE_CBB
264 bool "CompuLab CM-T35/CM-T3730 modules"
265 depends on ARCH_OMAP3
268 select OMAP_PACKAGE_CUS
271 bool "CompuLab CM-T3517 module"
272 depends on ARCH_OMAP3
274 select OMAP_PACKAGE_CBB
280 bool "OMAP3 SBC STALKER board"
281 depends on ARCH_OMAP3
283 select OMAP_PACKAGE_CUS
285 config MACH_TI8168EVM
286 bool "TI8168 Evaluation Module"
287 depends on SOC_TI81XX
290 config MACH_TI8148EVM
291 bool "TI8148 Evaluation Module"
292 depends on SOC_TI81XX
296 bool "OMAP3 debugging peripherals"
297 depends on ARCH_OMAP3
301 Say Y here to enable debugging hardware of omap3
303 config OMAP3_SDRC_AC_TIMING
304 bool "Enable SDRC AC timing register changes"
305 depends on ARCH_OMAP3
308 If you know that none of your system initiators will attempt to
309 access SDRAM during CORE DVFS, select Y here. This should boost
310 SDRAM performance at lower CORE OPPs. There are relatively few
311 users who will wish to say yes at this point - almost everyone will
312 wish to say no. Selecting yes without understanding what is
313 going on could result in system crashes;
315 config OMAP4_ERRATA_I688
316 bool "OMAP4 errata: Async Bridge Corruption"
317 depends on (ARCH_OMAP4 || SOC_OMAP5) && !ARCH_MULTIPLATFORM
318 select ARCH_HAS_BARRIERS
320 If a data is stalled inside asynchronous bridge because of back
321 pressure, it may be accepted multiple times, creating pointer
322 misalignment that will corrupt next transfers on that data path
323 until next reset of the system (No recovery procedure once the
324 issue is hit, the path remains consistently broken). Async bridge
325 can be found on path between MPU to EMIF and MPU to L3 interconnect.
326 This situation can happen only when the idle is initiated by a
327 Master Request Disconnection (which is trigged by software when
328 executing WFI on CPU).
329 The work-around for this errata needs all the initiators connected
330 through async bridge must ensure that data path is properly drained
331 before issuing WFI. This condition will be met if one Strongly ordered
332 access is performed to the target right before executing the WFI.
333 In MPU case, L3 T2ASYNC FIFO and DDR T2ASYNC FIFO needs to be drained.
334 IO barrier ensure that there is no synchronisation loss on initiators
335 operating on both interconnect port simultaneously.