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_DMA_API_DEBUG
17 select HAVE_EXIT_THREAD
18 select HAVE_FUNCTION_TRACER
19 select HAVE_FUTEX_CMPXCHG if !MMU
20 select HAVE_HW_BREAKPOINT if PERF_EVENTS
21 select HAVE_IRQ_TIME_ACCOUNTING
23 select HAVE_PERF_EVENTS
25 select MODULES_USE_ELF_RELA
26 select PERF_USE_VMALLOC
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
34 a home page at <http://www.linux-xtensa.org/>.
36 config RWSEM_XCHGADD_ALGORITHM
39 config GENERIC_HWEIGHT
42 config ARCH_HAS_ILOG2_U32
45 config ARCH_HAS_ILOG2_U64
56 source "kernel/Kconfig.freezer"
58 config LOCKDEP_SUPPORT
61 config STACKTRACE_SUPPORT
64 config TRACE_IRQFLAGS_SUPPORT
70 config VARIANT_IRQ_SWITCH
73 config HAVE_XTENSA_GPIO32
76 menu "Processor type and features"
79 prompt "Xtensa Processor Configuration"
80 default XTENSA_VARIANT_FSF
82 config XTENSA_VARIANT_FSF
83 bool "fsf - default (not generic) configuration"
86 config XTENSA_VARIANT_DC232B
87 bool "dc232b - Diamond 232L Standard Core Rev.B (LE)"
89 select HAVE_XTENSA_GPIO32
91 This variant refers to Tensilica's Diamond 232L Standard core Rev.B (LE).
93 config XTENSA_VARIANT_DC233C
94 bool "dc233c - Diamond 233L Standard Core Rev.C (LE)"
96 select HAVE_XTENSA_GPIO32
98 This variant refers to Tensilica's Diamond 233L Standard core Rev.C (LE).
100 config XTENSA_VARIANT_CUSTOM
101 bool "Custom Xtensa processor configuration"
102 select HAVE_XTENSA_GPIO32
104 Select this variant to use a custom Xtensa processor configuration.
105 You will be prompted for a processor variant CORENAME.
108 config XTENSA_VARIANT_CUSTOM_NAME
109 string "Xtensa Processor Custom Core Variant Name"
110 depends on XTENSA_VARIANT_CUSTOM
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.
116 config XTENSA_VARIANT_NAME
118 default "dc232b" if XTENSA_VARIANT_DC232B
119 default "dc233c" if XTENSA_VARIANT_DC233C
120 default "fsf" if XTENSA_VARIANT_FSF
121 default XTENSA_VARIANT_CUSTOM_NAME if XTENSA_VARIANT_CUSTOM
123 config XTENSA_VARIANT_MMU
124 bool "Core variant has a Full MMU (TLB, Pages, Protection, etc)"
125 depends on XTENSA_VARIANT_CUSTOM
129 Build a Conventional Kernel with full MMU support,
130 ie: it supports a TLB with auto-loading, page protection.
132 config XTENSA_VARIANT_HAVE_PERF_EVENTS
133 bool "Core variant has Performance Monitor Module"
134 depends on XTENSA_VARIANT_CUSTOM
137 Enable if core variant has Performance Monitor Module with
138 External Registers Interface.
142 config XTENSA_FAKE_NMI
143 bool "Treat PMM IRQ as NMI"
144 depends on XTENSA_VARIANT_HAVE_PERF_EVENTS
147 If PMM IRQ is the only IRQ at EXCM level it is safe to
148 treat it as NMI, which improves accuracy of profiling.
150 If there are other interrupts at or above PMM IRQ priority level
151 but not above the EXCM level, PMM IRQ still may be treated as NMI,
152 but only if these IRQs are not used. There will be a build warning
153 saying that this is not safe, and a bugcheck if one of these IRQs
158 config XTENSA_UNALIGNED_USER
159 bool "Unaligned memory access in use space"
161 The Xtensa architecture currently does not handle unaligned
162 memory accesses in hardware but through an exception handler.
163 Per default, unaligned memory accesses are disabled in user space.
165 Say Y here to enable unaligned memory access in user space.
167 source "kernel/Kconfig.preempt"
170 bool "System Supports SMP (MX)"
171 depends on XTENSA_VARIANT_CUSTOM
174 This option is use to indicate that the system-on-a-chip (SOC)
175 supports Multiprocessing. Multiprocessor support implemented above
176 the CPU core definition and currently needs to be selected manually.
178 Multiprocessor support in implemented with external cache and
179 interrupt controllers.
181 The MX interrupt distributer adds Interprocessor Interrupts
182 and causes the IRQ numbers to be increased by 4 for devices
183 like the open cores ethernet driver and the serial interface.
185 You still have to select "Enable SMP" to enable SMP on this SOC.
188 bool "Enable Symmetric multi-processing support"
190 select GENERIC_SMP_IDLE_THREAD
192 Enabled SMP Software; allows more than one CPU/CORE
193 to be activated during startup.
197 int "Maximum number of CPUs (2-32)"
202 bool "Enable CPU hotplug support"
205 Say Y here to allow turning CPUs off and on. CPUs can be
206 controlled through /sys/devices/system/cpu.
208 Say N if you want to disable CPU hotplug.
210 config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
211 bool "Initialize Xtensa MMU inside the Linux kernel code"
214 Earlier version initialized the MMU in the exception vector
215 before jumping to _startup in head.S and had an advantage that
216 it was possible to place a software breakpoint at 'reset' and
217 then enter your normal kernel breakpoints once the MMU was mapped
218 to the kernel mappings (0XC0000000).
220 This unfortunately doesn't work for U-Boot and likley also wont
221 work for using KEXEC to have a hot kernel ready for doing a
224 So now the MMU is initialized in head.S but it's necessary to
225 use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
226 xt-gdb can't place a Software Breakpoint in the 0XD region prior
227 to mapping the MMU and after mapping even if the area of low memory
228 was mapped gdb wouldn't remove the breakpoint on hitting it as the
229 PC wouldn't match. Since Hardware Breakpoints are recommended for
230 Linux configurations it seems reasonable to just assume they exist
231 and leave this older mechanism for unfortunate souls that choose
232 not to follow Tensilica's recommendation.
234 Selecting this will cause U-Boot to set the KERNEL Load and Entry
235 address at 0x00003000 instead of the mapped std of 0xD0003000.
240 hex "Physical address of the KSEG mapping"
241 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX && MMU
244 This is the physical address where KSEG is mapped. Please refer to
245 the chosen KSEG layout help for the required address alignment.
246 Unpacked kernel image (including vectors) must be located completely
248 Physical memory below this address is not available to linux.
250 If unsure, leave the default value here.
255 default XTENSA_KSEG_MMU_V2
257 config XTENSA_KSEG_MMU_V2
258 bool "MMUv2: 128MB cached + 128MB uncached"
260 MMUv2 compatible kernel memory map: TLB way 5 maps 128MB starting
261 at KSEG_PADDR to 0xd0000000 with cache and to 0xd8000000
263 KSEG_PADDR must be aligned to 128MB.
265 config XTENSA_KSEG_256M
266 bool "256MB cached + 256MB uncached"
267 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
269 TLB way 6 maps 256MB starting at KSEG_PADDR to 0xb0000000
270 with cache and to 0xc0000000 without cache.
271 KSEG_PADDR must be aligned to 256MB.
273 config XTENSA_KSEG_512M
274 bool "512MB cached + 512MB uncached"
275 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
277 TLB way 6 maps 512MB starting at KSEG_PADDR to 0xa0000000
278 with cache and to 0xc0000000 without cache.
279 KSEG_PADDR must be aligned to 256MB.
284 bool "High Memory Support"
287 Linux can use the full amount of RAM in the system by
288 default. However, the default MMUv2 setup only maps the
289 lowermost 128 MB of memory linearly to the areas starting
290 at 0xd0000000 (cached) and 0xd8000000 (uncached).
291 When there are more than 128 MB memory in the system not
292 all of it can be "permanently mapped" by the kernel.
293 The physical memory that's not permanently mapped is called
296 If you are compiling a kernel which will never run on a
297 machine with more than 128 MB total physical RAM, answer
302 config FAST_SYSCALL_XTENSA
303 bool "Enable fast atomic syscalls"
306 fast_syscall_xtensa is a syscall that can make atomic operations
307 on UP kernel when processor has no s32c1i support.
309 This syscall is deprecated. It may have issues when called with
310 invalid arguments. It is provided only for backwards compatibility.
311 Only enable it if your userspace software requires it.
315 config FAST_SYSCALL_SPILL_REGISTERS
316 bool "Enable spill registers syscall"
319 fast_syscall_spill_registers is a syscall that spills all active
320 register windows of a calling userspace task onto its stack.
322 This syscall is deprecated. It may have issues when called with
323 invalid arguments. It is provided only for backwards compatibility.
324 Only enable it if your userspace software requires it.
330 config XTENSA_CALIBRATE_CCOUNT
333 On some platforms (XT2000, for example), the CPU clock rate can
334 vary. The frequency can be determined, however, by measuring
335 against a well known, fixed frequency, such as an UART oscillator.
337 config SERIAL_CONSOLE
346 Find out whether you have a PCI motherboard. PCI is the name of a
347 bus system, i.e. the way the CPU talks to the other stuff inside
348 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
349 VESA. If you have PCI, say Y, otherwise N.
351 source "drivers/pci/Kconfig"
355 menu "Platform options"
358 prompt "Xtensa System Type"
359 default XTENSA_PLATFORM_ISS
361 config XTENSA_PLATFORM_ISS
363 select XTENSA_CALIBRATE_CCOUNT
364 select SERIAL_CONSOLE
366 ISS is an acronym for Tensilica's Instruction Set Simulator.
368 config XTENSA_PLATFORM_XT2000
372 XT2000 is the name of Tensilica's feature-rich emulation platform.
373 This hardware is capable of running a full Linux distribution.
375 config XTENSA_PLATFORM_XTFPGA
377 select ETHOC if ETHERNET
378 select PLATFORM_WANT_DEFAULT_MEM
379 select SERIAL_CONSOLE
380 select XTENSA_CALIBRATE_CCOUNT
382 XTFPGA is the name of Tensilica board family (LX60, LX110, LX200, ML605).
383 This hardware is capable of running a full Linux distribution.
388 config XTENSA_CPU_CLOCK
389 int "CPU clock rate [MHz]"
390 depends on !XTENSA_CALIBRATE_CCOUNT
393 config GENERIC_CALIBRATE_DELAY
394 bool "Auto calibration of the BogoMIPS value"
396 The BogoMIPS value can easily be derived from the CPU frequency.
399 bool "Default bootloader kernel arguments"
402 string "Initial kernel command string"
403 depends on CMDLINE_BOOL
404 default "console=ttyS0,38400 root=/dev/ram"
406 On some architectures (EBSA110 and CATS), there is currently no way
407 for the boot loader to pass arguments to the kernel. For these
408 architectures, you should supply some command-line options at build
409 time by entering them here. As a minimum, you should specify the
410 memory size and the root device (e.g., mem=64M root=/dev/nfs).
413 bool "Flattened Device Tree support"
415 select OF_EARLY_FLATTREE
417 Include support for flattened device tree machine descriptions.
420 string "DTB to build into the kernel image"
423 config BLK_DEV_SIMDISK
424 tristate "Host file-based simulated block device support"
426 depends on XTENSA_PLATFORM_ISS && BLOCK
428 Create block devices that map to files in the host file system.
429 Device binding to host file may be changed at runtime via proc
430 interface provided the device is not in use.
432 config BLK_DEV_SIMDISK_COUNT
433 int "Number of host file-based simulated block devices"
435 depends on BLK_DEV_SIMDISK
438 This is the default minimal number of created block devices.
439 Kernel/module parameter 'simdisk_count' may be used to change this
440 value at runtime. More file names (but no more than 10) may be
441 specified as parameters, simdisk_count grows accordingly.
443 config SIMDISK0_FILENAME
444 string "Host filename for the first simulated device"
445 depends on BLK_DEV_SIMDISK = y
448 Attach a first simdisk to a host file. Conventionally, this file
449 contains a root file system.
451 config SIMDISK1_FILENAME
452 string "Host filename for the second simulated device"
453 depends on BLK_DEV_SIMDISK = y && BLK_DEV_SIMDISK_COUNT != 1
456 Another simulated disk in a host file for a buildroot-independent
461 config FORCE_MAX_ZONEORDER
462 int "Maximum zone order"
465 The kernel memory allocator divides physically contiguous memory
466 blocks into "zones", where each zone is a power of two number of
467 pages. This option selects the largest power of two that the kernel
468 keeps in the memory allocator. If you need to allocate very large
469 blocks of physically contiguous memory, then you may need to
472 This config option is actually maximum order plus one. For example,
473 a value of 11 means that the largest free memory block is 2^10 pages.
475 source "drivers/pcmcia/Kconfig"
477 config PLATFORM_WANT_DEFAULT_MEM
480 config DEFAULT_MEM_START
481 hex "Physical address of the default memory area start"
482 depends on PLATFORM_WANT_DEFAULT_MEM
483 default 0x00000000 if MMU
484 default 0x60000000 if !MMU
486 This is a fallback start address of the default memory area, it is
487 used when no physical memory size is passed through DTB or through
488 boot parameter from bootloader.
490 In noMMU configuration the following parameters are derived from it:
491 - kernel load address;
492 - kernel entry point address;
493 - relocatable vectors base address;
494 - uBoot load address;
497 If unsure, leave the default value here.
499 config DEFAULT_MEM_SIZE
500 hex "Maximal size of the default memory area"
501 depends on PLATFORM_WANT_DEFAULT_MEM
504 This is a fallback size of the default memory area, it is used when
505 no physical memory size is passed through DTB or through boot
506 parameter from bootloader.
508 It's also used for TASK_SIZE calculation in noMMU configuration.
510 If unsure, leave the default value here.
513 bool "Enable XTFPGA LCD driver"
514 depends on XTENSA_PLATFORM_XTFPGA
517 There's a 2x16 LCD on most of XTFPGA boards, kernel may output
518 progress messages there during bootup/shutdown. It may be useful
519 during board bringup.
523 config XTFPGA_LCD_BASE_ADDR
524 hex "XTFPGA LCD base address"
525 depends on XTFPGA_LCD
528 Base address of the LCD controller inside KIO region.
529 Different boards from XTFPGA family have LCD controller at different
530 addresses. Please consult prototyping user guide for your board for
531 the correct address. Wrong address here may lead to hardware lockup.
533 config XTFPGA_LCD_8BIT_ACCESS
534 bool "Use 8-bit access to XTFPGA LCD"
535 depends on XTFPGA_LCD
538 LCD may be connected with 4- or 8-bit interface, 8-bit access may
539 only be used with 8-bit interface. Please consult prototyping user
540 guide for your board for the correct interface width.
544 menu "Executable file formats"
546 source "fs/Kconfig.binfmt"
550 menu "Power management options"
552 source "kernel/power/Kconfig"
558 source "drivers/Kconfig"
562 source "arch/xtensa/Kconfig.debug"
564 source "security/Kconfig"
566 source "crypto/Kconfig"