]>
Commit | Line | Data |
---|---|---|
66701b14 | 1 | config ZONE_DMA |
35f9cd08 | 2 | def_bool y |
66701b14 | 3 | |
8e1a6dd2 | 4 | config XTENSA |
35f9cd08 | 5 | def_bool y |
8f371c75 | 6 | select ARCH_WANT_FRAME_POINTERS |
e969161b | 7 | select ARCH_WANT_IPC_PARSE_VERSION |
6ed65f37 | 8 | select ARCH_WANT_OPTIONAL_GPIOLIB |
25df8198 | 9 | select BUILDTIME_EXTABLE_SORT |
3e41f9ba | 10 | select CLONE_BACKWARDS |
920f8a39 MF |
11 | select COMMON_CLK |
12 | select GENERIC_ATOMIC64 | |
13 | select GENERIC_CLOCKEVENTS | |
14 | select GENERIC_IRQ_SHOW | |
15 | select GENERIC_PCI_IOMAP | |
16 | select GENERIC_SCHED_CLOCK | |
c75959a6 MF |
17 | select HAVE_DMA_API_DEBUG |
18 | select HAVE_DMA_ATTRS | |
478ba61a | 19 | select HAVE_FUNCTION_TRACER |
d951ba21 | 20 | select HAVE_FUTEX_CMPXCHG if !MMU |
496543c4 | 21 | select HAVE_IRQ_TIME_ACCOUNTING |
920f8a39 | 22 | select HAVE_OPROFILE |
a6f3eefa | 23 | select HAVE_PERF_EVENTS |
920f8a39 MF |
24 | select IRQ_DOMAIN |
25 | select MODULES_USE_ELF_RELA | |
db8165f5 | 26 | select PERF_USE_VMALLOC |
920f8a39 | 27 | select VIRT_TO_BUS |
8e1a6dd2 CZ |
28 | help |
29 | Xtensa processors are 32-bit RISC machines designed by Tensilica | |
30 | primarily for embedded systems. These processors are both | |
31 | configurable and extensible. The Linux port to the Xtensa | |
32 | architecture supports all processor configurations and extensions, | |
33 | with reasonable minimum requirements. The Xtensa Linux project has | |
0ada4490 | 34 | a home page at <http://www.linux-xtensa.org/>. |
8e1a6dd2 | 35 | |
8e1a6dd2 | 36 | config RWSEM_XCHGADD_ALGORITHM |
35f9cd08 | 37 | def_bool y |
8e1a6dd2 | 38 | |
d4337aa5 | 39 | config GENERIC_HWEIGHT |
35f9cd08 | 40 | def_bool y |
d4337aa5 | 41 | |
f0d1b0b3 | 42 | config ARCH_HAS_ILOG2_U32 |
35f9cd08 | 43 | def_bool n |
f0d1b0b3 DH |
44 | |
45 | config ARCH_HAS_ILOG2_U64 | |
35f9cd08 | 46 | def_bool n |
f0d1b0b3 | 47 | |
ce816fa8 | 48 | config NO_IOPORT_MAP |
d046f77e | 49 | def_bool n |
5ea81769 | 50 | |
bdc80787 PA |
51 | config HZ |
52 | int | |
53 | default 100 | |
54 | ||
8e1a6dd2 | 55 | source "init/Kconfig" |
dc52ddc0 | 56 | source "kernel/Kconfig.freezer" |
8e1a6dd2 | 57 | |
8f371c75 MF |
58 | config LOCKDEP_SUPPORT |
59 | def_bool y | |
60 | ||
3e4196a5 MF |
61 | config STACKTRACE_SUPPORT |
62 | def_bool y | |
63 | ||
c92931b2 MF |
64 | config TRACE_IRQFLAGS_SUPPORT |
65 | def_bool y | |
66 | ||
35f9cd08 | 67 | config MMU |
de7c1c78 | 68 | def_bool n |
35f9cd08 | 69 | |
4c0d2141 JW |
70 | config VARIANT_IRQ_SWITCH |
71 | def_bool n | |
72 | ||
a1a2bdec BS |
73 | config HAVE_XTENSA_GPIO32 |
74 | def_bool n | |
75 | ||
8e1a6dd2 CZ |
76 | menu "Processor type and features" |
77 | ||
78 | choice | |
79 | prompt "Xtensa Processor Configuration" | |
173d6681 | 80 | default XTENSA_VARIANT_FSF |
8e1a6dd2 | 81 | |
173d6681 | 82 | config XTENSA_VARIANT_FSF |
0025427e | 83 | bool "fsf - default (not generic) configuration" |
35f9cd08 | 84 | select MMU |
0025427e CZ |
85 | |
86 | config XTENSA_VARIANT_DC232B | |
87 | bool "dc232b - Diamond 232L Standard Core Rev.B (LE)" | |
35f9cd08 | 88 | select MMU |
a1a2bdec | 89 | select HAVE_XTENSA_GPIO32 |
0025427e | 90 | help |
35f9cd08 | 91 | This variant refers to Tensilica's Diamond 232L Standard core Rev.B (LE). |
000af2c5 | 92 | |
d0b73b48 PD |
93 | config XTENSA_VARIANT_DC233C |
94 | bool "dc233c - Diamond 233L Standard Core Rev.C (LE)" | |
95 | select MMU | |
a1a2bdec | 96 | select HAVE_XTENSA_GPIO32 |
d0b73b48 PD |
97 | help |
98 | This variant refers to Tensilica's Diamond 233L Standard core Rev.C (LE). | |
99 | ||
420ae951 MF |
100 | config XTENSA_VARIANT_CUSTOM |
101 | bool "Custom Xtensa processor configuration" | |
420ae951 MF |
102 | select HAVE_XTENSA_GPIO32 |
103 | help | |
104 | Select this variant to use a custom Xtensa processor configuration. | |
105 | You will be prompted for a processor variant CORENAME. | |
8e1a6dd2 CZ |
106 | endchoice |
107 | ||
420ae951 MF |
108 | config XTENSA_VARIANT_CUSTOM_NAME |
109 | string "Xtensa Processor Custom Core Variant Name" | |
110 | depends on XTENSA_VARIANT_CUSTOM | |
111 | help | |
112 | Provide the name of a custom Xtensa processor variant. | |
113 | This CORENAME selects arch/xtensa/variant/CORENAME. | |
114 | Dont forget you have to select MMU if you have one. | |
115 | ||
116 | config XTENSA_VARIANT_NAME | |
117 | string | |
118 | default "dc232b" if XTENSA_VARIANT_DC232B | |
119 | default "dc233c" if XTENSA_VARIANT_DC233C | |
120 | default "fsf" if XTENSA_VARIANT_FSF | |
420ae951 MF |
121 | default XTENSA_VARIANT_CUSTOM_NAME if XTENSA_VARIANT_CUSTOM |
122 | ||
123 | config XTENSA_VARIANT_MMU | |
124 | bool "Core variant has a Full MMU (TLB, Pages, Protection, etc)" | |
125 | depends on XTENSA_VARIANT_CUSTOM | |
126 | default y | |
de7c1c78 | 127 | select MMU |
420ae951 MF |
128 | help |
129 | Build a Conventional Kernel with full MMU support, | |
130 | ie: it supports a TLB with auto-loading, page protection. | |
131 | ||
9bd46da4 MF |
132 | config XTENSA_VARIANT_HAVE_PERF_EVENTS |
133 | bool "Core variant has Performance Monitor Module" | |
134 | depends on XTENSA_VARIANT_CUSTOM | |
135 | default n | |
136 | help | |
137 | Enable if core variant has Performance Monitor Module with | |
138 | External Registers Interface. | |
139 | ||
140 | If unsure, say N. | |
141 | ||
8e1a6dd2 CZ |
142 | config XTENSA_UNALIGNED_USER |
143 | bool "Unaligned memory access in use space" | |
35f9cd08 JW |
144 | help |
145 | The Xtensa architecture currently does not handle unaligned | |
146 | memory accesses in hardware but through an exception handler. | |
147 | Per default, unaligned memory accesses are disabled in user space. | |
8e1a6dd2 | 148 | |
35f9cd08 | 149 | Say Y here to enable unaligned memory access in user space. |
8e1a6dd2 | 150 | |
bd96efe1 | 151 | source "kernel/Kconfig.preempt" |
8e1a6dd2 | 152 | |
f615136c MF |
153 | config HAVE_SMP |
154 | bool "System Supports SMP (MX)" | |
de7c1c78 | 155 | depends on XTENSA_VARIANT_CUSTOM |
f615136c MF |
156 | select XTENSA_MX |
157 | help | |
158 | This option is use to indicate that the system-on-a-chip (SOC) | |
159 | supports Multiprocessing. Multiprocessor support implemented above | |
160 | the CPU core definition and currently needs to be selected manually. | |
161 | ||
162 | Multiprocessor support in implemented with external cache and | |
769a12a9 | 163 | interrupt controllers. |
f615136c MF |
164 | |
165 | The MX interrupt distributer adds Interprocessor Interrupts | |
166 | and causes the IRQ numbers to be increased by 4 for devices | |
167 | like the open cores ethernet driver and the serial interface. | |
168 | ||
169 | You still have to select "Enable SMP" to enable SMP on this SOC. | |
170 | ||
171 | config SMP | |
172 | bool "Enable Symmetric multi-processing support" | |
173 | depends on HAVE_SMP | |
f615136c MF |
174 | select GENERIC_SMP_IDLE_THREAD |
175 | help | |
176 | Enabled SMP Software; allows more than one CPU/CORE | |
177 | to be activated during startup. | |
178 | ||
179 | config NR_CPUS | |
180 | depends on SMP | |
181 | int "Maximum number of CPUs (2-32)" | |
182 | range 2 32 | |
183 | default "4" | |
184 | ||
49b424fe MF |
185 | config HOTPLUG_CPU |
186 | bool "Enable CPU hotplug support" | |
187 | depends on SMP | |
188 | help | |
189 | Say Y here to allow turning CPUs off and on. CPUs can be | |
190 | controlled through /sys/devices/system/cpu. | |
191 | ||
192 | Say N if you want to disable CPU hotplug. | |
193 | ||
e85e335f MF |
194 | config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX |
195 | bool "Initialize Xtensa MMU inside the Linux kernel code" | |
196 | default y | |
197 | help | |
198 | Earlier version initialized the MMU in the exception vector | |
199 | before jumping to _startup in head.S and had an advantage that | |
200 | it was possible to place a software breakpoint at 'reset' and | |
201 | then enter your normal kernel breakpoints once the MMU was mapped | |
202 | to the kernel mappings (0XC0000000). | |
203 | ||
204 | This unfortunately doesn't work for U-Boot and likley also wont | |
205 | work for using KEXEC to have a hot kernel ready for doing a | |
206 | KDUMP. | |
207 | ||
208 | So now the MMU is initialized in head.S but it's necessary to | |
209 | use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup. | |
210 | xt-gdb can't place a Software Breakpoint in the 0XD region prior | |
211 | to mapping the MMU and after mapping even if the area of low memory | |
212 | was mapped gdb wouldn't remove the breakpoint on hitting it as the | |
213 | PC wouldn't match. Since Hardware Breakpoints are recommended for | |
214 | Linux configurations it seems reasonable to just assume they exist | |
215 | and leave this older mechanism for unfortunate souls that choose | |
216 | not to follow Tensilica's recommendation. | |
217 | ||
218 | Selecting this will cause U-Boot to set the KERNEL Load and Entry | |
219 | address at 0x00003000 instead of the mapped std of 0xD0003000. | |
220 | ||
221 | If in doubt, say Y. | |
222 | ||
65559100 MF |
223 | config HIGHMEM |
224 | bool "High Memory Support" | |
8a9de059 | 225 | depends on MMU |
65559100 MF |
226 | help |
227 | Linux can use the full amount of RAM in the system by | |
228 | default. However, the default MMUv2 setup only maps the | |
229 | lowermost 128 MB of memory linearly to the areas starting | |
230 | at 0xd0000000 (cached) and 0xd8000000 (uncached). | |
231 | When there are more than 128 MB memory in the system not | |
232 | all of it can be "permanently mapped" by the kernel. | |
233 | The physical memory that's not permanently mapped is called | |
234 | "high memory". | |
235 | ||
236 | If you are compiling a kernel which will never run on a | |
237 | machine with more than 128 MB total physical RAM, answer | |
238 | N here. | |
239 | ||
240 | If unsure, say Y. | |
241 | ||
9184289c MF |
242 | config FAST_SYSCALL_XTENSA |
243 | bool "Enable fast atomic syscalls" | |
244 | default n | |
245 | help | |
246 | fast_syscall_xtensa is a syscall that can make atomic operations | |
247 | on UP kernel when processor has no s32c1i support. | |
248 | ||
249 | This syscall is deprecated. It may have issues when called with | |
250 | invalid arguments. It is provided only for backwards compatibility. | |
251 | Only enable it if your userspace software requires it. | |
252 | ||
253 | If unsure, say N. | |
254 | ||
255 | config FAST_SYSCALL_SPILL_REGISTERS | |
256 | bool "Enable spill registers syscall" | |
257 | default n | |
258 | help | |
259 | fast_syscall_spill_registers is a syscall that spills all active | |
260 | register windows of a calling userspace task onto its stack. | |
261 | ||
262 | This syscall is deprecated. It may have issues when called with | |
263 | invalid arguments. It is provided only for backwards compatibility. | |
264 | Only enable it if your userspace software requires it. | |
265 | ||
266 | If unsure, say N. | |
267 | ||
8e1a6dd2 CZ |
268 | endmenu |
269 | ||
35f9cd08 JW |
270 | config XTENSA_CALIBRATE_CCOUNT |
271 | def_bool n | |
272 | help | |
273 | On some platforms (XT2000, for example), the CPU clock rate can | |
274 | vary. The frequency can be determined, however, by measuring | |
275 | against a well known, fixed frequency, such as an UART oscillator. | |
276 | ||
277 | config SERIAL_CONSOLE | |
278 | def_bool n | |
279 | ||
35f9cd08 JW |
280 | menu "Bus options" |
281 | ||
282 | config PCI | |
283 | bool "PCI support" | |
284 | default y | |
285 | help | |
286 | Find out whether you have a PCI motherboard. PCI is the name of a | |
287 | bus system, i.e. the way the CPU talks to the other stuff inside | |
288 | your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or | |
289 | VESA. If you have PCI, say Y, otherwise N. | |
290 | ||
291 | source "drivers/pci/Kconfig" | |
292 | ||
35e71f90 CZ |
293 | endmenu |
294 | ||
8e1a6dd2 CZ |
295 | menu "Platform options" |
296 | ||
297 | choice | |
298 | prompt "Xtensa System Type" | |
299 | default XTENSA_PLATFORM_ISS | |
300 | ||
301 | config XTENSA_PLATFORM_ISS | |
302 | bool "ISS" | |
35f9cd08 JW |
303 | select XTENSA_CALIBRATE_CCOUNT |
304 | select SERIAL_CONSOLE | |
8e1a6dd2 CZ |
305 | help |
306 | ISS is an acronym for Tensilica's Instruction Set Simulator. | |
307 | ||
308 | config XTENSA_PLATFORM_XT2000 | |
309 | bool "XT2000" | |
4964527d | 310 | select HAVE_IDE |
8e1a6dd2 CZ |
311 | help |
312 | XT2000 is the name of Tensilica's feature-rich emulation platform. | |
313 | This hardware is capable of running a full Linux distribution. | |
314 | ||
0d456bad MF |
315 | config XTENSA_PLATFORM_XTFPGA |
316 | bool "XTFPGA" | |
61e47e9b | 317 | select ETHOC if ETHERNET |
3932b9ca | 318 | select PLATFORM_WANT_DEFAULT_MEM |
0d456bad | 319 | select SERIAL_CONSOLE |
0d456bad MF |
320 | select XTENSA_CALIBRATE_CCOUNT |
321 | help | |
322 | XTFPGA is the name of Tensilica board family (LX60, LX110, LX200, ML605). | |
323 | This hardware is capable of running a full Linux distribution. | |
324 | ||
8e1a6dd2 CZ |
325 | endchoice |
326 | ||
327 | ||
8e1a6dd2 CZ |
328 | config XTENSA_CPU_CLOCK |
329 | int "CPU clock rate [MHz]" | |
330 | depends on !XTENSA_CALIBRATE_CCOUNT | |
35f9cd08 | 331 | default 16 |
8e1a6dd2 CZ |
332 | |
333 | config GENERIC_CALIBRATE_DELAY | |
334 | bool "Auto calibration of the BogoMIPS value" | |
35f9cd08 | 335 | help |
82300bf4 | 336 | The BogoMIPS value can easily be derived from the CPU frequency. |
8e1a6dd2 CZ |
337 | |
338 | config CMDLINE_BOOL | |
339 | bool "Default bootloader kernel arguments" | |
340 | ||
341 | config CMDLINE | |
342 | string "Initial kernel command string" | |
343 | depends on CMDLINE_BOOL | |
344 | default "console=ttyS0,38400 root=/dev/ram" | |
345 | help | |
346 | On some architectures (EBSA110 and CATS), there is currently no way | |
347 | for the boot loader to pass arguments to the kernel. For these | |
348 | architectures, you should supply some command-line options at build | |
349 | time by entering them here. As a minimum, you should specify the | |
350 | memory size and the root device (e.g., mem=64M root=/dev/nfs). | |
351 | ||
da844a81 MF |
352 | config USE_OF |
353 | bool "Flattened Device Tree support" | |
354 | select OF | |
355 | select OF_EARLY_FLATTREE | |
356 | help | |
357 | Include support for flattened device tree machine descriptions. | |
358 | ||
359 | config BUILTIN_DTB | |
360 | string "DTB to build into the kernel image" | |
361 | depends on OF | |
362 | ||
b6c7e873 VP |
363 | config BLK_DEV_SIMDISK |
364 | tristate "Host file-based simulated block device support" | |
365 | default n | |
7a0684cd | 366 | depends on XTENSA_PLATFORM_ISS && BLOCK |
b6c7e873 VP |
367 | help |
368 | Create block devices that map to files in the host file system. | |
369 | Device binding to host file may be changed at runtime via proc | |
370 | interface provided the device is not in use. | |
371 | ||
372 | config BLK_DEV_SIMDISK_COUNT | |
373 | int "Number of host file-based simulated block devices" | |
374 | range 1 10 | |
375 | depends on BLK_DEV_SIMDISK | |
376 | default 2 | |
377 | help | |
378 | This is the default minimal number of created block devices. | |
379 | Kernel/module parameter 'simdisk_count' may be used to change this | |
380 | value at runtime. More file names (but no more than 10) may be | |
381 | specified as parameters, simdisk_count grows accordingly. | |
382 | ||
383 | config SIMDISK0_FILENAME | |
384 | string "Host filename for the first simulated device" | |
385 | depends on BLK_DEV_SIMDISK = y | |
386 | default "" | |
387 | help | |
388 | Attach a first simdisk to a host file. Conventionally, this file | |
389 | contains a root file system. | |
390 | ||
391 | config SIMDISK1_FILENAME | |
392 | string "Host filename for the second simulated device" | |
393 | depends on BLK_DEV_SIMDISK = y && BLK_DEV_SIMDISK_COUNT != 1 | |
394 | default "" | |
395 | help | |
396 | Another simulated disk in a host file for a buildroot-independent | |
397 | storage. | |
398 | ||
82300bf4 CZ |
399 | source "mm/Kconfig" |
400 | ||
a9df9338 MF |
401 | config FORCE_MAX_ZONEORDER |
402 | int "Maximum zone order" | |
403 | default "11" | |
404 | help | |
405 | The kernel memory allocator divides physically contiguous memory | |
406 | blocks into "zones", where each zone is a power of two number of | |
407 | pages. This option selects the largest power of two that the kernel | |
408 | keeps in the memory allocator. If you need to allocate very large | |
409 | blocks of physically contiguous memory, then you may need to | |
410 | increase this value. | |
411 | ||
412 | This config option is actually maximum order plus one. For example, | |
413 | a value of 11 means that the largest free memory block is 2^10 pages. | |
414 | ||
8e1a6dd2 CZ |
415 | source "drivers/pcmcia/Kconfig" |
416 | ||
417 | source "drivers/pci/hotplug/Kconfig" | |
418 | ||
3932b9ca MF |
419 | config PLATFORM_WANT_DEFAULT_MEM |
420 | def_bool n | |
421 | ||
422 | config DEFAULT_MEM_START | |
423 | hex "Physical address of the default memory area start" | |
424 | depends on PLATFORM_WANT_DEFAULT_MEM | |
425 | default 0x00000000 if MMU | |
d9eb3cb2 | 426 | default 0x60000000 if !MMU |
3932b9ca MF |
427 | help |
428 | This is a fallback start address of the default memory area, it is | |
429 | used when no physical memory size is passed through DTB or through | |
430 | boot parameter from bootloader. | |
431 | ||
432 | In noMMU configuration the following parameters are derived from it: | |
433 | - kernel load address; | |
434 | - kernel entry point address; | |
435 | - relocatable vectors base address; | |
436 | - uBoot load address; | |
437 | - TASK_SIZE. | |
438 | ||
439 | If unsure, leave the default value here. | |
440 | ||
441 | config DEFAULT_MEM_SIZE | |
442 | hex "Maximal size of the default memory area" | |
443 | depends on PLATFORM_WANT_DEFAULT_MEM | |
444 | default 0x04000000 | |
445 | help | |
446 | This is a fallback size of the default memory area, it is used when | |
447 | no physical memory size is passed through DTB or through boot | |
448 | parameter from bootloader. | |
449 | ||
450 | It's also used for TASK_SIZE calculation in noMMU configuration. | |
451 | ||
452 | If unsure, leave the default value here. | |
453 | ||
4949009e MF |
454 | config XTFPGA_LCD |
455 | bool "Enable XTFPGA LCD driver" | |
456 | depends on XTENSA_PLATFORM_XTFPGA | |
457 | default n | |
458 | help | |
459 | There's a 2x16 LCD on most of XTFPGA boards, kernel may output | |
460 | progress messages there during bootup/shutdown. It may be useful | |
461 | during board bringup. | |
462 | ||
463 | If unsure, say N. | |
464 | ||
465 | config XTFPGA_LCD_BASE_ADDR | |
466 | hex "XTFPGA LCD base address" | |
467 | depends on XTFPGA_LCD | |
468 | default "0x0d0c0000" | |
469 | help | |
470 | Base address of the LCD controller inside KIO region. | |
471 | Different boards from XTFPGA family have LCD controller at different | |
472 | addresses. Please consult prototyping user guide for your board for | |
473 | the correct address. Wrong address here may lead to hardware lockup. | |
474 | ||
475 | config XTFPGA_LCD_8BIT_ACCESS | |
476 | bool "Use 8-bit access to XTFPGA LCD" | |
477 | depends on XTFPGA_LCD | |
478 | default n | |
479 | help | |
480 | LCD may be connected with 4- or 8-bit interface, 8-bit access may | |
481 | only be used with 8-bit interface. Please consult prototyping user | |
482 | guide for your board for the correct interface width. | |
483 | ||
8e1a6dd2 CZ |
484 | endmenu |
485 | ||
cab00891 | 486 | menu "Executable file formats" |
8e1a6dd2 | 487 | |
8e1a6dd2 CZ |
488 | source "fs/Kconfig.binfmt" |
489 | ||
490 | endmenu | |
491 | ||
e00d8b2f MF |
492 | menu "Power management options" |
493 | ||
494 | source "kernel/power/Kconfig" | |
495 | ||
496 | endmenu | |
497 | ||
d5950b43 SR |
498 | source "net/Kconfig" |
499 | ||
8e1a6dd2 CZ |
500 | source "drivers/Kconfig" |
501 | ||
502 | source "fs/Kconfig" | |
503 | ||
8e1a6dd2 CZ |
504 | source "arch/xtensa/Kconfig.debug" |
505 | ||
506 | source "security/Kconfig" | |
507 | ||
508 | source "crypto/Kconfig" | |
509 | ||
510 | source "lib/Kconfig" | |
511 | ||
512 |