6 select ARCH_WANT_FRAME_POINTERS
7 select ARCH_WANT_IPC_PARSE_VERSION
8 select BUILDTIME_EXTABLE_SORT
11 select GENERIC_ATOMIC64
12 select GENERIC_CLOCKEVENTS
13 select GENERIC_IRQ_SHOW
14 select GENERIC_PCI_IOMAP
15 select GENERIC_SCHED_CLOCK
16 select HAVE_DEBUG_KMEMLEAK
17 select HAVE_DMA_API_DEBUG
18 select HAVE_DMA_CONTIGUOUS
19 select HAVE_EXIT_THREAD
20 select HAVE_FUNCTION_TRACER
21 select HAVE_FUTEX_CMPXCHG if !MMU
22 select HAVE_HW_BREAKPOINT if PERF_EVENTS
23 select HAVE_IRQ_TIME_ACCOUNTING
26 select HAVE_PERF_EVENTS
28 select MODULES_USE_ELF_RELA
30 select PERF_USE_VMALLOC
33 Xtensa processors are 32-bit RISC machines designed by Tensilica
34 primarily for embedded systems. These processors are both
35 configurable and extensible. The Linux port to the Xtensa
36 architecture supports all processor configurations and extensions,
37 with reasonable minimum requirements. The Xtensa Linux project has
38 a home page at <http://www.linux-xtensa.org/>.
40 config RWSEM_XCHGADD_ALGORITHM
43 config GENERIC_HWEIGHT
46 config ARCH_HAS_ILOG2_U32
49 config ARCH_HAS_ILOG2_U64
60 source "kernel/Kconfig.freezer"
62 config LOCKDEP_SUPPORT
65 config STACKTRACE_SUPPORT
68 config TRACE_IRQFLAGS_SUPPORT
74 config VARIANT_IRQ_SWITCH
77 config HAVE_XTENSA_GPIO32
80 menu "Processor type and features"
83 prompt "Xtensa Processor Configuration"
84 default XTENSA_VARIANT_FSF
86 config XTENSA_VARIANT_FSF
87 bool "fsf - default (not generic) configuration"
90 config XTENSA_VARIANT_DC232B
91 bool "dc232b - Diamond 232L Standard Core Rev.B (LE)"
93 select HAVE_XTENSA_GPIO32
95 This variant refers to Tensilica's Diamond 232L Standard core Rev.B (LE).
97 config XTENSA_VARIANT_DC233C
98 bool "dc233c - Diamond 233L Standard Core Rev.C (LE)"
100 select HAVE_XTENSA_GPIO32
102 This variant refers to Tensilica's Diamond 233L Standard core Rev.C (LE).
104 config XTENSA_VARIANT_CUSTOM
105 bool "Custom Xtensa processor configuration"
106 select HAVE_XTENSA_GPIO32
108 Select this variant to use a custom Xtensa processor configuration.
109 You will be prompted for a processor variant CORENAME.
112 config XTENSA_VARIANT_CUSTOM_NAME
113 string "Xtensa Processor Custom Core Variant Name"
114 depends on XTENSA_VARIANT_CUSTOM
116 Provide the name of a custom Xtensa processor variant.
117 This CORENAME selects arch/xtensa/variant/CORENAME.
118 Dont forget you have to select MMU if you have one.
120 config XTENSA_VARIANT_NAME
122 default "dc232b" if XTENSA_VARIANT_DC232B
123 default "dc233c" if XTENSA_VARIANT_DC233C
124 default "fsf" if XTENSA_VARIANT_FSF
125 default XTENSA_VARIANT_CUSTOM_NAME if XTENSA_VARIANT_CUSTOM
127 config XTENSA_VARIANT_MMU
128 bool "Core variant has a Full MMU (TLB, Pages, Protection, etc)"
129 depends on XTENSA_VARIANT_CUSTOM
133 Build a Conventional Kernel with full MMU support,
134 ie: it supports a TLB with auto-loading, page protection.
136 config XTENSA_VARIANT_HAVE_PERF_EVENTS
137 bool "Core variant has Performance Monitor Module"
138 depends on XTENSA_VARIANT_CUSTOM
141 Enable if core variant has Performance Monitor Module with
142 External Registers Interface.
146 config XTENSA_FAKE_NMI
147 bool "Treat PMM IRQ as NMI"
148 depends on XTENSA_VARIANT_HAVE_PERF_EVENTS
151 If PMM IRQ is the only IRQ at EXCM level it is safe to
152 treat it as NMI, which improves accuracy of profiling.
154 If there are other interrupts at or above PMM IRQ priority level
155 but not above the EXCM level, PMM IRQ still may be treated as NMI,
156 but only if these IRQs are not used. There will be a build warning
157 saying that this is not safe, and a bugcheck if one of these IRQs
162 config XTENSA_UNALIGNED_USER
163 bool "Unaligned memory access in use space"
165 The Xtensa architecture currently does not handle unaligned
166 memory accesses in hardware but through an exception handler.
167 Per default, unaligned memory accesses are disabled in user space.
169 Say Y here to enable unaligned memory access in user space.
171 source "kernel/Kconfig.preempt"
174 bool "System Supports SMP (MX)"
175 depends on XTENSA_VARIANT_CUSTOM
178 This option is use to indicate that the system-on-a-chip (SOC)
179 supports Multiprocessing. Multiprocessor support implemented above
180 the CPU core definition and currently needs to be selected manually.
182 Multiprocessor support in implemented with external cache and
183 interrupt controllers.
185 The MX interrupt distributer adds Interprocessor Interrupts
186 and causes the IRQ numbers to be increased by 4 for devices
187 like the open cores ethernet driver and the serial interface.
189 You still have to select "Enable SMP" to enable SMP on this SOC.
192 bool "Enable Symmetric multi-processing support"
194 select GENERIC_SMP_IDLE_THREAD
196 Enabled SMP Software; allows more than one CPU/CORE
197 to be activated during startup.
201 int "Maximum number of CPUs (2-32)"
206 bool "Enable CPU hotplug support"
209 Say Y here to allow turning CPUs off and on. CPUs can be
210 controlled through /sys/devices/system/cpu.
212 Say N if you want to disable CPU hotplug.
214 config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
215 bool "Initialize Xtensa MMU inside the Linux kernel code"
216 depends on !XTENSA_VARIANT_FSF && !XTENSA_VARIANT_DC232B
217 default y if XTENSA_VARIANT_DC233C || XTENSA_VARIANT_CUSTOM
219 Earlier version initialized the MMU in the exception vector
220 before jumping to _startup in head.S and had an advantage that
221 it was possible to place a software breakpoint at 'reset' and
222 then enter your normal kernel breakpoints once the MMU was mapped
223 to the kernel mappings (0XC0000000).
225 This unfortunately doesn't work for U-Boot and likley also wont
226 work for using KEXEC to have a hot kernel ready for doing a
229 So now the MMU is initialized in head.S but it's necessary to
230 use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
231 xt-gdb can't place a Software Breakpoint in the 0XD region prior
232 to mapping the MMU and after mapping even if the area of low memory
233 was mapped gdb wouldn't remove the breakpoint on hitting it as the
234 PC wouldn't match. Since Hardware Breakpoints are recommended for
235 Linux configurations it seems reasonable to just assume they exist
236 and leave this older mechanism for unfortunate souls that choose
237 not to follow Tensilica's recommendation.
239 Selecting this will cause U-Boot to set the KERNEL Load and Entry
240 address at 0x00003000 instead of the mapped std of 0xD0003000.
245 hex "Physical address of the KSEG mapping"
246 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX && MMU
249 This is the physical address where KSEG is mapped. Please refer to
250 the chosen KSEG layout help for the required address alignment.
251 Unpacked kernel image (including vectors) must be located completely
253 Physical memory below this address is not available to linux.
255 If unsure, leave the default value here.
257 config KERNEL_LOAD_ADDRESS
258 hex "Kernel load address"
259 default 0x60003000 if !MMU
260 default 0x00003000 if MMU && INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
261 default 0xd0003000 if MMU && !INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
263 This is the address where the kernel is loaded.
264 It is virtual address for MMUv2 configurations and physical address
265 for all other configurations.
267 If unsure, leave the default value here.
269 config VECTORS_OFFSET
270 hex "Kernel vectors offset"
273 This is the offset of the kernel image from the relocatable vectors
276 If unsure, leave the default value here.
281 default XTENSA_KSEG_MMU_V2
283 config XTENSA_KSEG_MMU_V2
284 bool "MMUv2: 128MB cached + 128MB uncached"
286 MMUv2 compatible kernel memory map: TLB way 5 maps 128MB starting
287 at KSEG_PADDR to 0xd0000000 with cache and to 0xd8000000
289 KSEG_PADDR must be aligned to 128MB.
291 config XTENSA_KSEG_256M
292 bool "256MB cached + 256MB uncached"
293 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
295 TLB way 6 maps 256MB starting at KSEG_PADDR to 0xb0000000
296 with cache and to 0xc0000000 without cache.
297 KSEG_PADDR must be aligned to 256MB.
299 config XTENSA_KSEG_512M
300 bool "512MB cached + 512MB uncached"
301 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
303 TLB way 6 maps 512MB starting at KSEG_PADDR to 0xa0000000
304 with cache and to 0xc0000000 without cache.
305 KSEG_PADDR must be aligned to 256MB.
310 bool "High Memory Support"
313 Linux can use the full amount of RAM in the system by
314 default. However, the default MMUv2 setup only maps the
315 lowermost 128 MB of memory linearly to the areas starting
316 at 0xd0000000 (cached) and 0xd8000000 (uncached).
317 When there are more than 128 MB memory in the system not
318 all of it can be "permanently mapped" by the kernel.
319 The physical memory that's not permanently mapped is called
322 If you are compiling a kernel which will never run on a
323 machine with more than 128 MB total physical RAM, answer
328 config FAST_SYSCALL_XTENSA
329 bool "Enable fast atomic syscalls"
332 fast_syscall_xtensa is a syscall that can make atomic operations
333 on UP kernel when processor has no s32c1i support.
335 This syscall is deprecated. It may have issues when called with
336 invalid arguments. It is provided only for backwards compatibility.
337 Only enable it if your userspace software requires it.
341 config FAST_SYSCALL_SPILL_REGISTERS
342 bool "Enable spill registers syscall"
345 fast_syscall_spill_registers is a syscall that spills all active
346 register windows of a calling userspace task onto its stack.
348 This syscall is deprecated. It may have issues when called with
349 invalid arguments. It is provided only for backwards compatibility.
350 Only enable it if your userspace software requires it.
356 config XTENSA_CALIBRATE_CCOUNT
359 On some platforms (XT2000, for example), the CPU clock rate can
360 vary. The frequency can be determined, however, by measuring
361 against a well known, fixed frequency, such as an UART oscillator.
363 config SERIAL_CONSOLE
372 Find out whether you have a PCI motherboard. PCI is the name of a
373 bus system, i.e. the way the CPU talks to the other stuff inside
374 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
375 VESA. If you have PCI, say Y, otherwise N.
377 source "drivers/pci/Kconfig"
381 menu "Platform options"
384 prompt "Xtensa System Type"
385 default XTENSA_PLATFORM_ISS
387 config XTENSA_PLATFORM_ISS
389 select XTENSA_CALIBRATE_CCOUNT
390 select SERIAL_CONSOLE
392 ISS is an acronym for Tensilica's Instruction Set Simulator.
394 config XTENSA_PLATFORM_XT2000
398 XT2000 is the name of Tensilica's feature-rich emulation platform.
399 This hardware is capable of running a full Linux distribution.
401 config XTENSA_PLATFORM_XTFPGA
403 select ETHOC if ETHERNET
404 select PLATFORM_WANT_DEFAULT_MEM if !MMU
405 select SERIAL_CONSOLE
406 select XTENSA_CALIBRATE_CCOUNT
408 XTFPGA is the name of Tensilica board family (LX60, LX110, LX200, ML605).
409 This hardware is capable of running a full Linux distribution.
414 config XTENSA_CPU_CLOCK
415 int "CPU clock rate [MHz]"
416 depends on !XTENSA_CALIBRATE_CCOUNT
419 config GENERIC_CALIBRATE_DELAY
420 bool "Auto calibration of the BogoMIPS value"
422 The BogoMIPS value can easily be derived from the CPU frequency.
425 bool "Default bootloader kernel arguments"
428 string "Initial kernel command string"
429 depends on CMDLINE_BOOL
430 default "console=ttyS0,38400 root=/dev/ram"
432 On some architectures (EBSA110 and CATS), there is currently no way
433 for the boot loader to pass arguments to the kernel. For these
434 architectures, you should supply some command-line options at build
435 time by entering them here. As a minimum, you should specify the
436 memory size and the root device (e.g., mem=64M root=/dev/nfs).
439 bool "Flattened Device Tree support"
441 select OF_EARLY_FLATTREE
442 select OF_RESERVED_MEM
444 Include support for flattened device tree machine descriptions.
447 string "DTB to build into the kernel image"
450 config BLK_DEV_SIMDISK
451 tristate "Host file-based simulated block device support"
453 depends on XTENSA_PLATFORM_ISS && BLOCK
455 Create block devices that map to files in the host file system.
456 Device binding to host file may be changed at runtime via proc
457 interface provided the device is not in use.
459 config BLK_DEV_SIMDISK_COUNT
460 int "Number of host file-based simulated block devices"
462 depends on BLK_DEV_SIMDISK
465 This is the default minimal number of created block devices.
466 Kernel/module parameter 'simdisk_count' may be used to change this
467 value at runtime. More file names (but no more than 10) may be
468 specified as parameters, simdisk_count grows accordingly.
470 config SIMDISK0_FILENAME
471 string "Host filename for the first simulated device"
472 depends on BLK_DEV_SIMDISK = y
475 Attach a first simdisk to a host file. Conventionally, this file
476 contains a root file system.
478 config SIMDISK1_FILENAME
479 string "Host filename for the second simulated device"
480 depends on BLK_DEV_SIMDISK = y && BLK_DEV_SIMDISK_COUNT != 1
483 Another simulated disk in a host file for a buildroot-independent
488 config FORCE_MAX_ZONEORDER
489 int "Maximum zone order"
492 The kernel memory allocator divides physically contiguous memory
493 blocks into "zones", where each zone is a power of two number of
494 pages. This option selects the largest power of two that the kernel
495 keeps in the memory allocator. If you need to allocate very large
496 blocks of physically contiguous memory, then you may need to
499 This config option is actually maximum order plus one. For example,
500 a value of 11 means that the largest free memory block is 2^10 pages.
502 source "drivers/pcmcia/Kconfig"
504 config PLATFORM_WANT_DEFAULT_MEM
507 config DEFAULT_MEM_START
508 hex "Physical address of the default memory area start"
509 depends on PLATFORM_WANT_DEFAULT_MEM
510 default 0x00000000 if MMU
511 default 0x60000000 if !MMU
513 This is the base address of the default memory area.
514 Default memory area has platform-specific meaning, it may be used
515 for e.g. early cache initialization.
517 If unsure, leave the default value here.
519 config DEFAULT_MEM_SIZE
520 hex "Maximal size of the default memory area"
521 depends on PLATFORM_WANT_DEFAULT_MEM
524 This is the size of the default memory area.
525 Default memory area has platform-specific meaning, it may be used
526 for e.g. early cache initialization.
528 If unsure, leave the default value here.
531 bool "Enable XTFPGA LCD driver"
532 depends on XTENSA_PLATFORM_XTFPGA
535 There's a 2x16 LCD on most of XTFPGA boards, kernel may output
536 progress messages there during bootup/shutdown. It may be useful
537 during board bringup.
541 config XTFPGA_LCD_BASE_ADDR
542 hex "XTFPGA LCD base address"
543 depends on XTFPGA_LCD
546 Base address of the LCD controller inside KIO region.
547 Different boards from XTFPGA family have LCD controller at different
548 addresses. Please consult prototyping user guide for your board for
549 the correct address. Wrong address here may lead to hardware lockup.
551 config XTFPGA_LCD_8BIT_ACCESS
552 bool "Use 8-bit access to XTFPGA LCD"
553 depends on XTFPGA_LCD
556 LCD may be connected with 4- or 8-bit interface, 8-bit access may
557 only be used with 8-bit interface. Please consult prototyping user
558 guide for your board for the correct interface width.
562 menu "Executable file formats"
564 source "fs/Kconfig.binfmt"
568 menu "Power management options"
570 source "kernel/power/Kconfig"
576 source "drivers/Kconfig"
580 source "arch/xtensa/Kconfig.debug"
582 source "security/Kconfig"
584 source "crypto/Kconfig"