1 # SPDX-License-Identifier: GPL-2.0
7 select ARCH_NO_COHERENT_DMA_MMAP if !MMU
8 select ARCH_WANT_FRAME_POINTERS
9 select ARCH_WANT_IPC_PARSE_VERSION
10 select BUILDTIME_EXTABLE_SORT
11 select CLONE_BACKWARDS
13 select GENERIC_ATOMIC64
14 select GENERIC_CLOCKEVENTS
15 select GENERIC_IRQ_SHOW
16 select GENERIC_PCI_IOMAP
17 select GENERIC_SCHED_CLOCK
18 select GENERIC_STRNCPY_FROM_USER if KASAN
19 select HAVE_ARCH_KASAN if MMU
20 select HAVE_DEBUG_KMEMLEAK
21 select HAVE_DMA_CONTIGUOUS
22 select HAVE_EXIT_THREAD
23 select HAVE_FUNCTION_TRACER
24 select HAVE_FUTEX_CMPXCHG if !MMU
25 select HAVE_HW_BREAKPOINT if PERF_EVENTS
26 select HAVE_IRQ_TIME_ACCOUNTING
29 select HAVE_PERF_EVENTS
30 select HAVE_STACKPROTECTOR
32 select MODULES_USE_ELF_RELA
34 select PERF_USE_VMALLOC
37 Xtensa processors are 32-bit RISC machines designed by Tensilica
38 primarily for embedded systems. These processors are both
39 configurable and extensible. The Linux port to the Xtensa
40 architecture supports all processor configurations and extensions,
41 with reasonable minimum requirements. The Xtensa Linux project has
42 a home page at <http://www.linux-xtensa.org/>.
44 config RWSEM_XCHGADD_ALGORITHM
47 config GENERIC_HWEIGHT
50 config ARCH_HAS_ILOG2_U32
53 config ARCH_HAS_ILOG2_U64
63 config LOCKDEP_SUPPORT
66 config STACKTRACE_SUPPORT
69 config TRACE_IRQFLAGS_SUPPORT
75 config VARIANT_IRQ_SWITCH
78 config HAVE_XTENSA_GPIO32
81 config KASAN_SHADOW_OFFSET
85 menu "Processor type and features"
88 prompt "Xtensa Processor Configuration"
89 default XTENSA_VARIANT_FSF
91 config XTENSA_VARIANT_FSF
92 bool "fsf - default (not generic) configuration"
95 config XTENSA_VARIANT_DC232B
96 bool "dc232b - Diamond 232L Standard Core Rev.B (LE)"
98 select HAVE_XTENSA_GPIO32
100 This variant refers to Tensilica's Diamond 232L Standard core Rev.B (LE).
102 config XTENSA_VARIANT_DC233C
103 bool "dc233c - Diamond 233L Standard Core Rev.C (LE)"
105 select HAVE_XTENSA_GPIO32
107 This variant refers to Tensilica's Diamond 233L Standard core Rev.C (LE).
109 config XTENSA_VARIANT_CUSTOM
110 bool "Custom Xtensa processor configuration"
111 select HAVE_XTENSA_GPIO32
113 Select this variant to use a custom Xtensa processor configuration.
114 You will be prompted for a processor variant CORENAME.
117 config XTENSA_VARIANT_CUSTOM_NAME
118 string "Xtensa Processor Custom Core Variant Name"
119 depends on XTENSA_VARIANT_CUSTOM
121 Provide the name of a custom Xtensa processor variant.
122 This CORENAME selects arch/xtensa/variant/CORENAME.
123 Dont forget you have to select MMU if you have one.
125 config XTENSA_VARIANT_NAME
127 default "dc232b" if XTENSA_VARIANT_DC232B
128 default "dc233c" if XTENSA_VARIANT_DC233C
129 default "fsf" if XTENSA_VARIANT_FSF
130 default XTENSA_VARIANT_CUSTOM_NAME if XTENSA_VARIANT_CUSTOM
132 config XTENSA_VARIANT_MMU
133 bool "Core variant has a Full MMU (TLB, Pages, Protection, etc)"
134 depends on XTENSA_VARIANT_CUSTOM
138 Build a Conventional Kernel with full MMU support,
139 ie: it supports a TLB with auto-loading, page protection.
141 config XTENSA_VARIANT_HAVE_PERF_EVENTS
142 bool "Core variant has Performance Monitor Module"
143 depends on XTENSA_VARIANT_CUSTOM
146 Enable if core variant has Performance Monitor Module with
147 External Registers Interface.
151 config XTENSA_FAKE_NMI
152 bool "Treat PMM IRQ as NMI"
153 depends on XTENSA_VARIANT_HAVE_PERF_EVENTS
156 If PMM IRQ is the only IRQ at EXCM level it is safe to
157 treat it as NMI, which improves accuracy of profiling.
159 If there are other interrupts at or above PMM IRQ priority level
160 but not above the EXCM level, PMM IRQ still may be treated as NMI,
161 but only if these IRQs are not used. There will be a build warning
162 saying that this is not safe, and a bugcheck if one of these IRQs
167 config XTENSA_UNALIGNED_USER
168 bool "Unaligned memory access in use space"
170 The Xtensa architecture currently does not handle unaligned
171 memory accesses in hardware but through an exception handler.
172 Per default, unaligned memory accesses are disabled in user space.
174 Say Y here to enable unaligned memory access in user space.
177 bool "System Supports SMP (MX)"
178 depends on XTENSA_VARIANT_CUSTOM
181 This option is use to indicate that the system-on-a-chip (SOC)
182 supports Multiprocessing. Multiprocessor support implemented above
183 the CPU core definition and currently needs to be selected manually.
185 Multiprocessor support in implemented with external cache and
186 interrupt controllers.
188 The MX interrupt distributer adds Interprocessor Interrupts
189 and causes the IRQ numbers to be increased by 4 for devices
190 like the open cores ethernet driver and the serial interface.
192 You still have to select "Enable SMP" to enable SMP on this SOC.
195 bool "Enable Symmetric multi-processing support"
197 select GENERIC_SMP_IDLE_THREAD
199 Enabled SMP Software; allows more than one CPU/CORE
200 to be activated during startup.
204 int "Maximum number of CPUs (2-32)"
209 bool "Enable CPU hotplug support"
212 Say Y here to allow turning CPUs off and on. CPUs can be
213 controlled through /sys/devices/system/cpu.
215 Say N if you want to disable CPU hotplug.
217 config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
218 bool "Initialize Xtensa MMU inside the Linux kernel code"
219 depends on !XTENSA_VARIANT_FSF && !XTENSA_VARIANT_DC232B
220 default y if XTENSA_VARIANT_DC233C || XTENSA_VARIANT_CUSTOM
222 Earlier version initialized the MMU in the exception vector
223 before jumping to _startup in head.S and had an advantage that
224 it was possible to place a software breakpoint at 'reset' and
225 then enter your normal kernel breakpoints once the MMU was mapped
226 to the kernel mappings (0XC0000000).
228 This unfortunately won't work for U-Boot and likely also wont
229 work for using KEXEC to have a hot kernel ready for doing a
232 So now the MMU is initialized in head.S but it's necessary to
233 use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
234 xt-gdb can't place a Software Breakpoint in the 0XD region prior
235 to mapping the MMU and after mapping even if the area of low memory
236 was mapped gdb wouldn't remove the breakpoint on hitting it as the
237 PC wouldn't match. Since Hardware Breakpoints are recommended for
238 Linux configurations it seems reasonable to just assume they exist
239 and leave this older mechanism for unfortunate souls that choose
240 not to follow Tensilica's recommendation.
242 Selecting this will cause U-Boot to set the KERNEL Load and Entry
243 address at 0x00003000 instead of the mapped std of 0xD0003000.
248 hex "Physical address of the KSEG mapping"
249 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX && MMU
252 This is the physical address where KSEG is mapped. Please refer to
253 the chosen KSEG layout help for the required address alignment.
254 Unpacked kernel image (including vectors) must be located completely
256 Physical memory below this address is not available to linux.
258 If unsure, leave the default value here.
260 config KERNEL_LOAD_ADDRESS
261 hex "Kernel load address"
262 default 0x60003000 if !MMU
263 default 0x00003000 if MMU && INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
264 default 0xd0003000 if MMU && !INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
266 This is the address where the kernel is loaded.
267 It is virtual address for MMUv2 configurations and physical address
268 for all other configurations.
270 If unsure, leave the default value here.
272 config VECTORS_OFFSET
273 hex "Kernel vectors offset"
276 This is the offset of the kernel image from the relocatable vectors
279 If unsure, leave the default value here.
284 default XTENSA_KSEG_MMU_V2
286 config XTENSA_KSEG_MMU_V2
287 bool "MMUv2: 128MB cached + 128MB uncached"
289 MMUv2 compatible kernel memory map: TLB way 5 maps 128MB starting
290 at KSEG_PADDR to 0xd0000000 with cache and to 0xd8000000
292 KSEG_PADDR must be aligned to 128MB.
294 config XTENSA_KSEG_256M
295 bool "256MB cached + 256MB uncached"
296 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
298 TLB way 6 maps 256MB starting at KSEG_PADDR to 0xb0000000
299 with cache and to 0xc0000000 without cache.
300 KSEG_PADDR must be aligned to 256MB.
302 config XTENSA_KSEG_512M
303 bool "512MB cached + 512MB uncached"
304 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
306 TLB way 6 maps 512MB starting at KSEG_PADDR to 0xa0000000
307 with cache and to 0xc0000000 without cache.
308 KSEG_PADDR must be aligned to 256MB.
313 bool "High Memory Support"
316 Linux can use the full amount of RAM in the system by
317 default. However, the default MMUv2 setup only maps the
318 lowermost 128 MB of memory linearly to the areas starting
319 at 0xd0000000 (cached) and 0xd8000000 (uncached).
320 When there are more than 128 MB memory in the system not
321 all of it can be "permanently mapped" by the kernel.
322 The physical memory that's not permanently mapped is called
325 If you are compiling a kernel which will never run on a
326 machine with more than 128 MB total physical RAM, answer
331 config FAST_SYSCALL_XTENSA
332 bool "Enable fast atomic syscalls"
335 fast_syscall_xtensa is a syscall that can make atomic operations
336 on UP kernel when processor has no s32c1i support.
338 This syscall is deprecated. It may have issues when called with
339 invalid arguments. It is provided only for backwards compatibility.
340 Only enable it if your userspace software requires it.
344 config FAST_SYSCALL_SPILL_REGISTERS
345 bool "Enable spill registers syscall"
348 fast_syscall_spill_registers is a syscall that spills all active
349 register windows of a calling userspace task onto its stack.
351 This syscall is deprecated. It may have issues when called with
352 invalid arguments. It is provided only for backwards compatibility.
353 Only enable it if your userspace software requires it.
359 config XTENSA_CALIBRATE_CCOUNT
362 On some platforms (XT2000, for example), the CPU clock rate can
363 vary. The frequency can be determined, however, by measuring
364 against a well known, fixed frequency, such as an UART oscillator.
366 config SERIAL_CONSOLE
375 Find out whether you have a PCI motherboard. PCI is the name of a
376 bus system, i.e. the way the CPU talks to the other stuff inside
377 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
378 VESA. If you have PCI, say Y, otherwise N.
380 source "drivers/pci/Kconfig"
384 menu "Platform options"
387 prompt "Xtensa System Type"
388 default XTENSA_PLATFORM_ISS
390 config XTENSA_PLATFORM_ISS
392 select XTENSA_CALIBRATE_CCOUNT
393 select SERIAL_CONSOLE
395 ISS is an acronym for Tensilica's Instruction Set Simulator.
397 config XTENSA_PLATFORM_XT2000
401 XT2000 is the name of Tensilica's feature-rich emulation platform.
402 This hardware is capable of running a full Linux distribution.
404 config XTENSA_PLATFORM_XTFPGA
406 select ETHOC if ETHERNET
407 select PLATFORM_WANT_DEFAULT_MEM if !MMU
408 select SERIAL_CONSOLE
409 select XTENSA_CALIBRATE_CCOUNT
411 XTFPGA is the name of Tensilica board family (LX60, LX110, LX200, ML605).
412 This hardware is capable of running a full Linux distribution.
417 config XTENSA_CPU_CLOCK
418 int "CPU clock rate [MHz]"
419 depends on !XTENSA_CALIBRATE_CCOUNT
422 config GENERIC_CALIBRATE_DELAY
423 bool "Auto calibration of the BogoMIPS value"
425 The BogoMIPS value can easily be derived from the CPU frequency.
428 bool "Default bootloader kernel arguments"
431 string "Initial kernel command string"
432 depends on CMDLINE_BOOL
433 default "console=ttyS0,38400 root=/dev/ram"
435 On some architectures (EBSA110 and CATS), there is currently no way
436 for the boot loader to pass arguments to the kernel. For these
437 architectures, you should supply some command-line options at build
438 time by entering them here. As a minimum, you should specify the
439 memory size and the root device (e.g., mem=64M root=/dev/nfs).
442 bool "Flattened Device Tree support"
444 select OF_EARLY_FLATTREE
445 select OF_RESERVED_MEM
447 Include support for flattened device tree machine descriptions.
450 string "DTB to build into the kernel image"
453 config BLK_DEV_SIMDISK
454 tristate "Host file-based simulated block device support"
456 depends on XTENSA_PLATFORM_ISS && BLOCK
458 Create block devices that map to files in the host file system.
459 Device binding to host file may be changed at runtime via proc
460 interface provided the device is not in use.
462 config BLK_DEV_SIMDISK_COUNT
463 int "Number of host file-based simulated block devices"
465 depends on BLK_DEV_SIMDISK
468 This is the default minimal number of created block devices.
469 Kernel/module parameter 'simdisk_count' may be used to change this
470 value at runtime. More file names (but no more than 10) may be
471 specified as parameters, simdisk_count grows accordingly.
473 config SIMDISK0_FILENAME
474 string "Host filename for the first simulated device"
475 depends on BLK_DEV_SIMDISK = y
478 Attach a first simdisk to a host file. Conventionally, this file
479 contains a root file system.
481 config SIMDISK1_FILENAME
482 string "Host filename for the second simulated device"
483 depends on BLK_DEV_SIMDISK = y && BLK_DEV_SIMDISK_COUNT != 1
486 Another simulated disk in a host file for a buildroot-independent
489 config FORCE_MAX_ZONEORDER
490 int "Maximum zone order"
493 The kernel memory allocator divides physically contiguous memory
494 blocks into "zones", where each zone is a power of two number of
495 pages. This option selects the largest power of two that the kernel
496 keeps in the memory allocator. If you need to allocate very large
497 blocks of physically contiguous memory, then you may need to
500 This config option is actually maximum order plus one. For example,
501 a value of 11 means that the largest free memory block is 2^10 pages.
503 source "drivers/pcmcia/Kconfig"
505 config PLATFORM_WANT_DEFAULT_MEM
508 config DEFAULT_MEM_START
509 hex "Physical address of the default memory area start"
510 depends on PLATFORM_WANT_DEFAULT_MEM
511 default 0x00000000 if MMU
512 default 0x60000000 if !MMU
514 This is the base address of the default memory area.
515 Default memory area has platform-specific meaning, it may be used
516 for e.g. early cache initialization.
518 If unsure, leave the default value here.
520 config DEFAULT_MEM_SIZE
521 hex "Maximal size of the default memory area"
522 depends on PLATFORM_WANT_DEFAULT_MEM
525 This is the size of the default memory area.
526 Default memory area has platform-specific meaning, it may be used
527 for e.g. early cache initialization.
529 If unsure, leave the default value here.
532 bool "Enable XTFPGA LCD driver"
533 depends on XTENSA_PLATFORM_XTFPGA
536 There's a 2x16 LCD on most of XTFPGA boards, kernel may output
537 progress messages there during bootup/shutdown. It may be useful
538 during board bringup.
542 config XTFPGA_LCD_BASE_ADDR
543 hex "XTFPGA LCD base address"
544 depends on XTFPGA_LCD
547 Base address of the LCD controller inside KIO region.
548 Different boards from XTFPGA family have LCD controller at different
549 addresses. Please consult prototyping user guide for your board for
550 the correct address. Wrong address here may lead to hardware lockup.
552 config XTFPGA_LCD_8BIT_ACCESS
553 bool "Use 8-bit access to XTFPGA LCD"
554 depends on XTFPGA_LCD
557 LCD may be connected with 4- or 8-bit interface, 8-bit access may
558 only be used with 8-bit interface. Please consult prototyping user
559 guide for your board for the correct interface width.
563 menu "Power management options"
565 source "kernel/power/Kconfig"