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.
176 source "kernel/Kconfig.preempt"
179 bool "System Supports SMP (MX)"
180 depends on XTENSA_VARIANT_CUSTOM
183 This option is use to indicate that the system-on-a-chip (SOC)
184 supports Multiprocessing. Multiprocessor support implemented above
185 the CPU core definition and currently needs to be selected manually.
187 Multiprocessor support in implemented with external cache and
188 interrupt controllers.
190 The MX interrupt distributer adds Interprocessor Interrupts
191 and causes the IRQ numbers to be increased by 4 for devices
192 like the open cores ethernet driver and the serial interface.
194 You still have to select "Enable SMP" to enable SMP on this SOC.
197 bool "Enable Symmetric multi-processing support"
199 select GENERIC_SMP_IDLE_THREAD
201 Enabled SMP Software; allows more than one CPU/CORE
202 to be activated during startup.
206 int "Maximum number of CPUs (2-32)"
211 bool "Enable CPU hotplug support"
214 Say Y here to allow turning CPUs off and on. CPUs can be
215 controlled through /sys/devices/system/cpu.
217 Say N if you want to disable CPU hotplug.
219 config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
220 bool "Initialize Xtensa MMU inside the Linux kernel code"
221 depends on !XTENSA_VARIANT_FSF && !XTENSA_VARIANT_DC232B
222 default y if XTENSA_VARIANT_DC233C || XTENSA_VARIANT_CUSTOM
224 Earlier version initialized the MMU in the exception vector
225 before jumping to _startup in head.S and had an advantage that
226 it was possible to place a software breakpoint at 'reset' and
227 then enter your normal kernel breakpoints once the MMU was mapped
228 to the kernel mappings (0XC0000000).
230 This unfortunately won't work for U-Boot and likely also wont
231 work for using KEXEC to have a hot kernel ready for doing a
234 So now the MMU is initialized in head.S but it's necessary to
235 use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
236 xt-gdb can't place a Software Breakpoint in the 0XD region prior
237 to mapping the MMU and after mapping even if the area of low memory
238 was mapped gdb wouldn't remove the breakpoint on hitting it as the
239 PC wouldn't match. Since Hardware Breakpoints are recommended for
240 Linux configurations it seems reasonable to just assume they exist
241 and leave this older mechanism for unfortunate souls that choose
242 not to follow Tensilica's recommendation.
244 Selecting this will cause U-Boot to set the KERNEL Load and Entry
245 address at 0x00003000 instead of the mapped std of 0xD0003000.
250 hex "Physical address of the KSEG mapping"
251 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX && MMU
254 This is the physical address where KSEG is mapped. Please refer to
255 the chosen KSEG layout help for the required address alignment.
256 Unpacked kernel image (including vectors) must be located completely
258 Physical memory below this address is not available to linux.
260 If unsure, leave the default value here.
262 config KERNEL_LOAD_ADDRESS
263 hex "Kernel load address"
264 default 0x60003000 if !MMU
265 default 0x00003000 if MMU && INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
266 default 0xd0003000 if MMU && !INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
268 This is the address where the kernel is loaded.
269 It is virtual address for MMUv2 configurations and physical address
270 for all other configurations.
272 If unsure, leave the default value here.
274 config VECTORS_OFFSET
275 hex "Kernel vectors offset"
278 This is the offset of the kernel image from the relocatable vectors
281 If unsure, leave the default value here.
286 default XTENSA_KSEG_MMU_V2
288 config XTENSA_KSEG_MMU_V2
289 bool "MMUv2: 128MB cached + 128MB uncached"
291 MMUv2 compatible kernel memory map: TLB way 5 maps 128MB starting
292 at KSEG_PADDR to 0xd0000000 with cache and to 0xd8000000
294 KSEG_PADDR must be aligned to 128MB.
296 config XTENSA_KSEG_256M
297 bool "256MB cached + 256MB uncached"
298 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
300 TLB way 6 maps 256MB starting at KSEG_PADDR to 0xb0000000
301 with cache and to 0xc0000000 without cache.
302 KSEG_PADDR must be aligned to 256MB.
304 config XTENSA_KSEG_512M
305 bool "512MB cached + 512MB uncached"
306 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
308 TLB way 6 maps 512MB starting at KSEG_PADDR to 0xa0000000
309 with cache and to 0xc0000000 without cache.
310 KSEG_PADDR must be aligned to 256MB.
315 bool "High Memory Support"
318 Linux can use the full amount of RAM in the system by
319 default. However, the default MMUv2 setup only maps the
320 lowermost 128 MB of memory linearly to the areas starting
321 at 0xd0000000 (cached) and 0xd8000000 (uncached).
322 When there are more than 128 MB memory in the system not
323 all of it can be "permanently mapped" by the kernel.
324 The physical memory that's not permanently mapped is called
327 If you are compiling a kernel which will never run on a
328 machine with more than 128 MB total physical RAM, answer
333 config FAST_SYSCALL_XTENSA
334 bool "Enable fast atomic syscalls"
337 fast_syscall_xtensa is a syscall that can make atomic operations
338 on UP kernel when processor has no s32c1i support.
340 This syscall is deprecated. It may have issues when called with
341 invalid arguments. It is provided only for backwards compatibility.
342 Only enable it if your userspace software requires it.
346 config FAST_SYSCALL_SPILL_REGISTERS
347 bool "Enable spill registers syscall"
350 fast_syscall_spill_registers is a syscall that spills all active
351 register windows of a calling userspace task onto its stack.
353 This syscall is deprecated. It may have issues when called with
354 invalid arguments. It is provided only for backwards compatibility.
355 Only enable it if your userspace software requires it.
361 config XTENSA_CALIBRATE_CCOUNT
364 On some platforms (XT2000, for example), the CPU clock rate can
365 vary. The frequency can be determined, however, by measuring
366 against a well known, fixed frequency, such as an UART oscillator.
368 config SERIAL_CONSOLE
377 Find out whether you have a PCI motherboard. PCI is the name of a
378 bus system, i.e. the way the CPU talks to the other stuff inside
379 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
380 VESA. If you have PCI, say Y, otherwise N.
382 source "drivers/pci/Kconfig"
386 menu "Platform options"
389 prompt "Xtensa System Type"
390 default XTENSA_PLATFORM_ISS
392 config XTENSA_PLATFORM_ISS
394 select XTENSA_CALIBRATE_CCOUNT
395 select SERIAL_CONSOLE
397 ISS is an acronym for Tensilica's Instruction Set Simulator.
399 config XTENSA_PLATFORM_XT2000
403 XT2000 is the name of Tensilica's feature-rich emulation platform.
404 This hardware is capable of running a full Linux distribution.
406 config XTENSA_PLATFORM_XTFPGA
408 select ETHOC if ETHERNET
409 select PLATFORM_WANT_DEFAULT_MEM if !MMU
410 select SERIAL_CONSOLE
411 select XTENSA_CALIBRATE_CCOUNT
413 XTFPGA is the name of Tensilica board family (LX60, LX110, LX200, ML605).
414 This hardware is capable of running a full Linux distribution.
419 config XTENSA_CPU_CLOCK
420 int "CPU clock rate [MHz]"
421 depends on !XTENSA_CALIBRATE_CCOUNT
424 config GENERIC_CALIBRATE_DELAY
425 bool "Auto calibration of the BogoMIPS value"
427 The BogoMIPS value can easily be derived from the CPU frequency.
430 bool "Default bootloader kernel arguments"
433 string "Initial kernel command string"
434 depends on CMDLINE_BOOL
435 default "console=ttyS0,38400 root=/dev/ram"
437 On some architectures (EBSA110 and CATS), there is currently no way
438 for the boot loader to pass arguments to the kernel. For these
439 architectures, you should supply some command-line options at build
440 time by entering them here. As a minimum, you should specify the
441 memory size and the root device (e.g., mem=64M root=/dev/nfs).
444 bool "Flattened Device Tree support"
446 select OF_EARLY_FLATTREE
447 select OF_RESERVED_MEM
449 Include support for flattened device tree machine descriptions.
452 string "DTB to build into the kernel image"
455 config BLK_DEV_SIMDISK
456 tristate "Host file-based simulated block device support"
458 depends on XTENSA_PLATFORM_ISS && BLOCK
460 Create block devices that map to files in the host file system.
461 Device binding to host file may be changed at runtime via proc
462 interface provided the device is not in use.
464 config BLK_DEV_SIMDISK_COUNT
465 int "Number of host file-based simulated block devices"
467 depends on BLK_DEV_SIMDISK
470 This is the default minimal number of created block devices.
471 Kernel/module parameter 'simdisk_count' may be used to change this
472 value at runtime. More file names (but no more than 10) may be
473 specified as parameters, simdisk_count grows accordingly.
475 config SIMDISK0_FILENAME
476 string "Host filename for the first simulated device"
477 depends on BLK_DEV_SIMDISK = y
480 Attach a first simdisk to a host file. Conventionally, this file
481 contains a root file system.
483 config SIMDISK1_FILENAME
484 string "Host filename for the second simulated device"
485 depends on BLK_DEV_SIMDISK = y && BLK_DEV_SIMDISK_COUNT != 1
488 Another simulated disk in a host file for a buildroot-independent
491 config FORCE_MAX_ZONEORDER
492 int "Maximum zone order"
495 The kernel memory allocator divides physically contiguous memory
496 blocks into "zones", where each zone is a power of two number of
497 pages. This option selects the largest power of two that the kernel
498 keeps in the memory allocator. If you need to allocate very large
499 blocks of physically contiguous memory, then you may need to
502 This config option is actually maximum order plus one. For example,
503 a value of 11 means that the largest free memory block is 2^10 pages.
505 source "drivers/pcmcia/Kconfig"
507 config PLATFORM_WANT_DEFAULT_MEM
510 config DEFAULT_MEM_START
511 hex "Physical address of the default memory area start"
512 depends on PLATFORM_WANT_DEFAULT_MEM
513 default 0x00000000 if MMU
514 default 0x60000000 if !MMU
516 This is the base address of the default memory area.
517 Default memory area has platform-specific meaning, it may be used
518 for e.g. early cache initialization.
520 If unsure, leave the default value here.
522 config DEFAULT_MEM_SIZE
523 hex "Maximal size of the default memory area"
524 depends on PLATFORM_WANT_DEFAULT_MEM
527 This is the size of the default memory area.
528 Default memory area has platform-specific meaning, it may be used
529 for e.g. early cache initialization.
531 If unsure, leave the default value here.
534 bool "Enable XTFPGA LCD driver"
535 depends on XTENSA_PLATFORM_XTFPGA
538 There's a 2x16 LCD on most of XTFPGA boards, kernel may output
539 progress messages there during bootup/shutdown. It may be useful
540 during board bringup.
544 config XTFPGA_LCD_BASE_ADDR
545 hex "XTFPGA LCD base address"
546 depends on XTFPGA_LCD
549 Base address of the LCD controller inside KIO region.
550 Different boards from XTFPGA family have LCD controller at different
551 addresses. Please consult prototyping user guide for your board for
552 the correct address. Wrong address here may lead to hardware lockup.
554 config XTFPGA_LCD_8BIT_ACCESS
555 bool "Use 8-bit access to XTFPGA LCD"
556 depends on XTFPGA_LCD
559 LCD may be connected with 4- or 8-bit interface, 8-bit access may
560 only be used with 8-bit interface. Please consult prototyping user
561 guide for your board for the correct interface width.
565 menu "Power management options"
567 source "kernel/power/Kconfig"