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
64 source "kernel/Kconfig.freezer"
66 config LOCKDEP_SUPPORT
69 config STACKTRACE_SUPPORT
72 config TRACE_IRQFLAGS_SUPPORT
78 config VARIANT_IRQ_SWITCH
81 config HAVE_XTENSA_GPIO32
84 config KASAN_SHADOW_OFFSET
88 menu "Processor type and features"
91 prompt "Xtensa Processor Configuration"
92 default XTENSA_VARIANT_FSF
94 config XTENSA_VARIANT_FSF
95 bool "fsf - default (not generic) configuration"
98 config XTENSA_VARIANT_DC232B
99 bool "dc232b - Diamond 232L Standard Core Rev.B (LE)"
101 select HAVE_XTENSA_GPIO32
103 This variant refers to Tensilica's Diamond 232L Standard core Rev.B (LE).
105 config XTENSA_VARIANT_DC233C
106 bool "dc233c - Diamond 233L Standard Core Rev.C (LE)"
108 select HAVE_XTENSA_GPIO32
110 This variant refers to Tensilica's Diamond 233L Standard core Rev.C (LE).
112 config XTENSA_VARIANT_CUSTOM
113 bool "Custom Xtensa processor configuration"
114 select HAVE_XTENSA_GPIO32
116 Select this variant to use a custom Xtensa processor configuration.
117 You will be prompted for a processor variant CORENAME.
120 config XTENSA_VARIANT_CUSTOM_NAME
121 string "Xtensa Processor Custom Core Variant Name"
122 depends on XTENSA_VARIANT_CUSTOM
124 Provide the name of a custom Xtensa processor variant.
125 This CORENAME selects arch/xtensa/variant/CORENAME.
126 Dont forget you have to select MMU if you have one.
128 config XTENSA_VARIANT_NAME
130 default "dc232b" if XTENSA_VARIANT_DC232B
131 default "dc233c" if XTENSA_VARIANT_DC233C
132 default "fsf" if XTENSA_VARIANT_FSF
133 default XTENSA_VARIANT_CUSTOM_NAME if XTENSA_VARIANT_CUSTOM
135 config XTENSA_VARIANT_MMU
136 bool "Core variant has a Full MMU (TLB, Pages, Protection, etc)"
137 depends on XTENSA_VARIANT_CUSTOM
141 Build a Conventional Kernel with full MMU support,
142 ie: it supports a TLB with auto-loading, page protection.
144 config XTENSA_VARIANT_HAVE_PERF_EVENTS
145 bool "Core variant has Performance Monitor Module"
146 depends on XTENSA_VARIANT_CUSTOM
149 Enable if core variant has Performance Monitor Module with
150 External Registers Interface.
154 config XTENSA_FAKE_NMI
155 bool "Treat PMM IRQ as NMI"
156 depends on XTENSA_VARIANT_HAVE_PERF_EVENTS
159 If PMM IRQ is the only IRQ at EXCM level it is safe to
160 treat it as NMI, which improves accuracy of profiling.
162 If there are other interrupts at or above PMM IRQ priority level
163 but not above the EXCM level, PMM IRQ still may be treated as NMI,
164 but only if these IRQs are not used. There will be a build warning
165 saying that this is not safe, and a bugcheck if one of these IRQs
170 config XTENSA_UNALIGNED_USER
171 bool "Unaligned memory access in use space"
173 The Xtensa architecture currently does not handle unaligned
174 memory accesses in hardware but through an exception handler.
175 Per default, unaligned memory accesses are disabled in user space.
177 Say Y here to enable unaligned memory access in user space.
179 source "kernel/Kconfig.preempt"
182 bool "System Supports SMP (MX)"
183 depends on XTENSA_VARIANT_CUSTOM
186 This option is use to indicate that the system-on-a-chip (SOC)
187 supports Multiprocessing. Multiprocessor support implemented above
188 the CPU core definition and currently needs to be selected manually.
190 Multiprocessor support in implemented with external cache and
191 interrupt controllers.
193 The MX interrupt distributer adds Interprocessor Interrupts
194 and causes the IRQ numbers to be increased by 4 for devices
195 like the open cores ethernet driver and the serial interface.
197 You still have to select "Enable SMP" to enable SMP on this SOC.
200 bool "Enable Symmetric multi-processing support"
202 select GENERIC_SMP_IDLE_THREAD
204 Enabled SMP Software; allows more than one CPU/CORE
205 to be activated during startup.
209 int "Maximum number of CPUs (2-32)"
214 bool "Enable CPU hotplug support"
217 Say Y here to allow turning CPUs off and on. CPUs can be
218 controlled through /sys/devices/system/cpu.
220 Say N if you want to disable CPU hotplug.
222 config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
223 bool "Initialize Xtensa MMU inside the Linux kernel code"
224 depends on !XTENSA_VARIANT_FSF && !XTENSA_VARIANT_DC232B
225 default y if XTENSA_VARIANT_DC233C || XTENSA_VARIANT_CUSTOM
227 Earlier version initialized the MMU in the exception vector
228 before jumping to _startup in head.S and had an advantage that
229 it was possible to place a software breakpoint at 'reset' and
230 then enter your normal kernel breakpoints once the MMU was mapped
231 to the kernel mappings (0XC0000000).
233 This unfortunately won't work for U-Boot and likely also wont
234 work for using KEXEC to have a hot kernel ready for doing a
237 So now the MMU is initialized in head.S but it's necessary to
238 use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
239 xt-gdb can't place a Software Breakpoint in the 0XD region prior
240 to mapping the MMU and after mapping even if the area of low memory
241 was mapped gdb wouldn't remove the breakpoint on hitting it as the
242 PC wouldn't match. Since Hardware Breakpoints are recommended for
243 Linux configurations it seems reasonable to just assume they exist
244 and leave this older mechanism for unfortunate souls that choose
245 not to follow Tensilica's recommendation.
247 Selecting this will cause U-Boot to set the KERNEL Load and Entry
248 address at 0x00003000 instead of the mapped std of 0xD0003000.
253 hex "Physical address of the KSEG mapping"
254 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX && MMU
257 This is the physical address where KSEG is mapped. Please refer to
258 the chosen KSEG layout help for the required address alignment.
259 Unpacked kernel image (including vectors) must be located completely
261 Physical memory below this address is not available to linux.
263 If unsure, leave the default value here.
265 config KERNEL_LOAD_ADDRESS
266 hex "Kernel load address"
267 default 0x60003000 if !MMU
268 default 0x00003000 if MMU && INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
269 default 0xd0003000 if MMU && !INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
271 This is the address where the kernel is loaded.
272 It is virtual address for MMUv2 configurations and physical address
273 for all other configurations.
275 If unsure, leave the default value here.
277 config VECTORS_OFFSET
278 hex "Kernel vectors offset"
281 This is the offset of the kernel image from the relocatable vectors
284 If unsure, leave the default value here.
289 default XTENSA_KSEG_MMU_V2
291 config XTENSA_KSEG_MMU_V2
292 bool "MMUv2: 128MB cached + 128MB uncached"
294 MMUv2 compatible kernel memory map: TLB way 5 maps 128MB starting
295 at KSEG_PADDR to 0xd0000000 with cache and to 0xd8000000
297 KSEG_PADDR must be aligned to 128MB.
299 config XTENSA_KSEG_256M
300 bool "256MB cached + 256MB uncached"
301 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
303 TLB way 6 maps 256MB starting at KSEG_PADDR to 0xb0000000
304 with cache and to 0xc0000000 without cache.
305 KSEG_PADDR must be aligned to 256MB.
307 config XTENSA_KSEG_512M
308 bool "512MB cached + 512MB uncached"
309 depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
311 TLB way 6 maps 512MB starting at KSEG_PADDR to 0xa0000000
312 with cache and to 0xc0000000 without cache.
313 KSEG_PADDR must be aligned to 256MB.
318 bool "High Memory Support"
321 Linux can use the full amount of RAM in the system by
322 default. However, the default MMUv2 setup only maps the
323 lowermost 128 MB of memory linearly to the areas starting
324 at 0xd0000000 (cached) and 0xd8000000 (uncached).
325 When there are more than 128 MB memory in the system not
326 all of it can be "permanently mapped" by the kernel.
327 The physical memory that's not permanently mapped is called
330 If you are compiling a kernel which will never run on a
331 machine with more than 128 MB total physical RAM, answer
336 config FAST_SYSCALL_XTENSA
337 bool "Enable fast atomic syscalls"
340 fast_syscall_xtensa is a syscall that can make atomic operations
341 on UP kernel when processor has no s32c1i support.
343 This syscall is deprecated. It may have issues when called with
344 invalid arguments. It is provided only for backwards compatibility.
345 Only enable it if your userspace software requires it.
349 config FAST_SYSCALL_SPILL_REGISTERS
350 bool "Enable spill registers syscall"
353 fast_syscall_spill_registers is a syscall that spills all active
354 register windows of a calling userspace task onto its stack.
356 This syscall is deprecated. It may have issues when called with
357 invalid arguments. It is provided only for backwards compatibility.
358 Only enable it if your userspace software requires it.
364 config XTENSA_CALIBRATE_CCOUNT
367 On some platforms (XT2000, for example), the CPU clock rate can
368 vary. The frequency can be determined, however, by measuring
369 against a well known, fixed frequency, such as an UART oscillator.
371 config SERIAL_CONSOLE
380 Find out whether you have a PCI motherboard. PCI is the name of a
381 bus system, i.e. the way the CPU talks to the other stuff inside
382 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
383 VESA. If you have PCI, say Y, otherwise N.
385 source "drivers/pci/Kconfig"
389 menu "Platform options"
392 prompt "Xtensa System Type"
393 default XTENSA_PLATFORM_ISS
395 config XTENSA_PLATFORM_ISS
397 select XTENSA_CALIBRATE_CCOUNT
398 select SERIAL_CONSOLE
400 ISS is an acronym for Tensilica's Instruction Set Simulator.
402 config XTENSA_PLATFORM_XT2000
406 XT2000 is the name of Tensilica's feature-rich emulation platform.
407 This hardware is capable of running a full Linux distribution.
409 config XTENSA_PLATFORM_XTFPGA
411 select ETHOC if ETHERNET
412 select PLATFORM_WANT_DEFAULT_MEM if !MMU
413 select SERIAL_CONSOLE
414 select XTENSA_CALIBRATE_CCOUNT
416 XTFPGA is the name of Tensilica board family (LX60, LX110, LX200, ML605).
417 This hardware is capable of running a full Linux distribution.
422 config XTENSA_CPU_CLOCK
423 int "CPU clock rate [MHz]"
424 depends on !XTENSA_CALIBRATE_CCOUNT
427 config GENERIC_CALIBRATE_DELAY
428 bool "Auto calibration of the BogoMIPS value"
430 The BogoMIPS value can easily be derived from the CPU frequency.
433 bool "Default bootloader kernel arguments"
436 string "Initial kernel command string"
437 depends on CMDLINE_BOOL
438 default "console=ttyS0,38400 root=/dev/ram"
440 On some architectures (EBSA110 and CATS), there is currently no way
441 for the boot loader to pass arguments to the kernel. For these
442 architectures, you should supply some command-line options at build
443 time by entering them here. As a minimum, you should specify the
444 memory size and the root device (e.g., mem=64M root=/dev/nfs).
447 bool "Flattened Device Tree support"
449 select OF_EARLY_FLATTREE
450 select OF_RESERVED_MEM
452 Include support for flattened device tree machine descriptions.
455 string "DTB to build into the kernel image"
458 config BLK_DEV_SIMDISK
459 tristate "Host file-based simulated block device support"
461 depends on XTENSA_PLATFORM_ISS && BLOCK
463 Create block devices that map to files in the host file system.
464 Device binding to host file may be changed at runtime via proc
465 interface provided the device is not in use.
467 config BLK_DEV_SIMDISK_COUNT
468 int "Number of host file-based simulated block devices"
470 depends on BLK_DEV_SIMDISK
473 This is the default minimal number of created block devices.
474 Kernel/module parameter 'simdisk_count' may be used to change this
475 value at runtime. More file names (but no more than 10) may be
476 specified as parameters, simdisk_count grows accordingly.
478 config SIMDISK0_FILENAME
479 string "Host filename for the first simulated device"
480 depends on BLK_DEV_SIMDISK = y
483 Attach a first simdisk to a host file. Conventionally, this file
484 contains a root file system.
486 config SIMDISK1_FILENAME
487 string "Host filename for the second simulated device"
488 depends on BLK_DEV_SIMDISK = y && BLK_DEV_SIMDISK_COUNT != 1
491 Another simulated disk in a host file for a buildroot-independent
496 config FORCE_MAX_ZONEORDER
497 int "Maximum zone order"
500 The kernel memory allocator divides physically contiguous memory
501 blocks into "zones", where each zone is a power of two number of
502 pages. This option selects the largest power of two that the kernel
503 keeps in the memory allocator. If you need to allocate very large
504 blocks of physically contiguous memory, then you may need to
507 This config option is actually maximum order plus one. For example,
508 a value of 11 means that the largest free memory block is 2^10 pages.
510 source "drivers/pcmcia/Kconfig"
512 config PLATFORM_WANT_DEFAULT_MEM
515 config DEFAULT_MEM_START
516 hex "Physical address of the default memory area start"
517 depends on PLATFORM_WANT_DEFAULT_MEM
518 default 0x00000000 if MMU
519 default 0x60000000 if !MMU
521 This is the base address of the default memory area.
522 Default memory area has platform-specific meaning, it may be used
523 for e.g. early cache initialization.
525 If unsure, leave the default value here.
527 config DEFAULT_MEM_SIZE
528 hex "Maximal size of the default memory area"
529 depends on PLATFORM_WANT_DEFAULT_MEM
532 This is the size of the default memory area.
533 Default memory area has platform-specific meaning, it may be used
534 for e.g. early cache initialization.
536 If unsure, leave the default value here.
539 bool "Enable XTFPGA LCD driver"
540 depends on XTENSA_PLATFORM_XTFPGA
543 There's a 2x16 LCD on most of XTFPGA boards, kernel may output
544 progress messages there during bootup/shutdown. It may be useful
545 during board bringup.
549 config XTFPGA_LCD_BASE_ADDR
550 hex "XTFPGA LCD base address"
551 depends on XTFPGA_LCD
554 Base address of the LCD controller inside KIO region.
555 Different boards from XTFPGA family have LCD controller at different
556 addresses. Please consult prototyping user guide for your board for
557 the correct address. Wrong address here may lead to hardware lockup.
559 config XTFPGA_LCD_8BIT_ACCESS
560 bool "Use 8-bit access to XTFPGA LCD"
561 depends on XTFPGA_LCD
564 LCD may be connected with 4- or 8-bit interface, 8-bit access may
565 only be used with 8-bit interface. Please consult prototyping user
566 guide for your board for the correct interface width.
570 menu "Executable file formats"
572 source "fs/Kconfig.binfmt"
576 menu "Power management options"
578 source "kernel/power/Kconfig"
584 source "drivers/Kconfig"
588 source "arch/xtensa/Kconfig.debug"
590 source "security/Kconfig"
592 source "crypto/Kconfig"