arch/xtensa/Kconfig

   1 # SPDX-License-Identifier: GPL-2.0
   2 config XTENSA
   3         def_bool y
   4         select ARCH_HAS_SYNC_DMA_FOR_CPU
   5         select ARCH_HAS_SYNC_DMA_FOR_DEVICE
   6         select ARCH_NO_COHERENT_DMA_MMAP if !MMU
   7         select ARCH_WANT_FRAME_POINTERS
   8         select ARCH_WANT_IPC_PARSE_VERSION
   9         select BUILDTIME_EXTABLE_SORT
  10         select CLONE_BACKWARDS
  11         select COMMON_CLK
  12         select DMA_REMAP if MMU
  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_JUMP_LABEL
  20         select HAVE_ARCH_KASAN if MMU
  21         select HAVE_ARCH_TRACEHOOK
  22         select HAVE_DEBUG_KMEMLEAK
  23         select HAVE_DMA_CONTIGUOUS
  24         select HAVE_EXIT_THREAD
  25         select HAVE_FUNCTION_TRACER
  26         select HAVE_FUTEX_CMPXCHG if !MMU
  27         select HAVE_HW_BREAKPOINT if PERF_EVENTS
  28         select HAVE_IRQ_TIME_ACCOUNTING
  29         select HAVE_OPROFILE
  30         select HAVE_PCI
  31         select HAVE_PERF_EVENTS
  32         select HAVE_STACKPROTECTOR
  33         select HAVE_SYSCALL_TRACEPOINTS
  34         select IRQ_DOMAIN
  35         select MODULES_USE_ELF_RELA
  36         select PERF_USE_VMALLOC
  37         select VIRT_TO_BUS
  38         help
  39           Xtensa processors are 32-bit RISC machines designed by Tensilica
  40           primarily for embedded systems.  These processors are both
  41           configurable and extensible.  The Linux port to the Xtensa
  42           architecture supports all processor configurations and extensions,
  43           with reasonable minimum requirements.  The Xtensa Linux project has
  44           a home page at <http://www.linux-xtensa.org/>.
  45
  46 config RWSEM_XCHGADD_ALGORITHM
  47         def_bool y
  48
  49 config GENERIC_HWEIGHT
  50         def_bool y
  51
  52 config ARCH_HAS_ILOG2_U32
  53         def_bool n
  54
  55 config ARCH_HAS_ILOG2_U64
  56         def_bool n
  57
  58 config NO_IOPORT_MAP
  59         def_bool n
  60
  61 config HZ
  62         int
  63         default 100
  64
  65 config LOCKDEP_SUPPORT
  66         def_bool y
  67
  68 config STACKTRACE_SUPPORT
  69         def_bool y
  70
  71 config TRACE_IRQFLAGS_SUPPORT
  72         def_bool y
  73
  74 config MMU
  75         def_bool n
  76
  77 config HAVE_XTENSA_GPIO32
  78         def_bool n
  79
  80 config KASAN_SHADOW_OFFSET
  81         hex
  82         default 0x6e400000
  83
  84 menu "Processor type and features"
  85
  86 choice
  87         prompt "Xtensa Processor Configuration"
  88         default XTENSA_VARIANT_FSF
  89
  90 config XTENSA_VARIANT_FSF
  91         bool "fsf - default (not generic) configuration"
  92         select MMU
  93
  94 config XTENSA_VARIANT_DC232B
  95         bool "dc232b - Diamond 232L Standard Core Rev.B (LE)"
  96         select MMU
  97         select HAVE_XTENSA_GPIO32
  98         help
  99           This variant refers to Tensilica's Diamond 232L Standard core Rev.B (LE).
 100
 101 config XTENSA_VARIANT_DC233C
 102         bool "dc233c - Diamond 233L Standard Core Rev.C (LE)"
 103         select MMU
 104         select HAVE_XTENSA_GPIO32
 105         help
 106           This variant refers to Tensilica's Diamond 233L Standard core Rev.C (LE).
 107
 108 config XTENSA_VARIANT_CUSTOM
 109         bool "Custom Xtensa processor configuration"
 110         select HAVE_XTENSA_GPIO32
 111         help
 112           Select this variant to use a custom Xtensa processor configuration.
 113           You will be prompted for a processor variant CORENAME.
 114 endchoice
 115
 116 config XTENSA_VARIANT_CUSTOM_NAME
 117         string "Xtensa Processor Custom Core Variant Name"
 118         depends on XTENSA_VARIANT_CUSTOM
 119         help
 120           Provide the name of a custom Xtensa processor variant.
 121           This CORENAME selects arch/xtensa/variant/CORENAME.
 122           Dont forget you have to select MMU if you have one.
 123
 124 config XTENSA_VARIANT_NAME
 125         string
 126         default "dc232b"                        if XTENSA_VARIANT_DC232B
 127         default "dc233c"                        if XTENSA_VARIANT_DC233C
 128         default "fsf"                           if XTENSA_VARIANT_FSF
 129         default XTENSA_VARIANT_CUSTOM_NAME      if XTENSA_VARIANT_CUSTOM
 130
 131 config XTENSA_VARIANT_MMU
 132         bool "Core variant has a Full MMU (TLB, Pages, Protection, etc)"
 133         depends on XTENSA_VARIANT_CUSTOM
 134         default y
 135         select MMU
 136         help
 137           Build a Conventional Kernel with full MMU support,
 138           ie: it supports a TLB with auto-loading, page protection.
 139
 140 config XTENSA_VARIANT_HAVE_PERF_EVENTS
 141         bool "Core variant has Performance Monitor Module"
 142         depends on XTENSA_VARIANT_CUSTOM
 143         default n
 144         help
 145           Enable if core variant has Performance Monitor Module with
 146           External Registers Interface.
 147
 148           If unsure, say N.
 149
 150 config XTENSA_FAKE_NMI
 151         bool "Treat PMM IRQ as NMI"
 152         depends on XTENSA_VARIANT_HAVE_PERF_EVENTS
 153         default n
 154         help
 155           If PMM IRQ is the only IRQ at EXCM level it is safe to
 156           treat it as NMI, which improves accuracy of profiling.
 157
 158           If there are other interrupts at or above PMM IRQ priority level
 159           but not above the EXCM level, PMM IRQ still may be treated as NMI,
 160           but only if these IRQs are not used. There will be a build warning
 161           saying that this is not safe, and a bugcheck if one of these IRQs
 162           actually fire.
 163
 164           If unsure, say N.
 165
 166 config XTENSA_UNALIGNED_USER
 167         bool "Unaligned memory access in user space"
 168         help
 169           The Xtensa architecture currently does not handle unaligned
 170           memory accesses in hardware but through an exception handler.
 171           Per default, unaligned memory accesses are disabled in user space.
 172
 173           Say Y here to enable unaligned memory access in user space.
 174
 175 config HAVE_SMP
 176         bool "System Supports SMP (MX)"
 177         depends on XTENSA_VARIANT_CUSTOM
 178         select XTENSA_MX
 179         help
 180           This option is use to indicate that the system-on-a-chip (SOC)
 181           supports Multiprocessing. Multiprocessor support implemented above
 182           the CPU core definition and currently needs to be selected manually.
 183
 184           Multiprocessor support in implemented with external cache and
 185           interrupt controllers.
 186
 187           The MX interrupt distributer adds Interprocessor Interrupts
 188           and causes the IRQ numbers to be increased by 4 for devices
 189           like the open cores ethernet driver and the serial interface.
 190
 191           You still have to select "Enable SMP" to enable SMP on this SOC.
 192
 193 config SMP
 194         bool "Enable Symmetric multi-processing support"
 195         depends on HAVE_SMP
 196         select GENERIC_SMP_IDLE_THREAD
 197         help
 198           Enabled SMP Software; allows more than one CPU/CORE
 199           to be activated during startup.
 200
 201 config NR_CPUS
 202         depends on SMP
 203         int "Maximum number of CPUs (2-32)"
 204         range 2 32
 205         default "4"
 206
 207 config HOTPLUG_CPU
 208         bool "Enable CPU hotplug support"
 209         depends on SMP
 210         help
 211           Say Y here to allow turning CPUs off and on. CPUs can be
 212           controlled through /sys/devices/system/cpu.
 213
 214           Say N if you want to disable CPU hotplug.
 215
 216 config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
 217         bool "Initialize Xtensa MMU inside the Linux kernel code"
 218         depends on !XTENSA_VARIANT_FSF && !XTENSA_VARIANT_DC232B
 219         default y if XTENSA_VARIANT_DC233C || XTENSA_VARIANT_CUSTOM
 220         help
 221           Earlier version initialized the MMU in the exception vector
 222           before jumping to _startup in head.S and had an advantage that
 223           it was possible to place a software breakpoint at 'reset' and
 224           then enter your normal kernel breakpoints once the MMU was mapped
 225           to the kernel mappings (0XC0000000).
 226
 227           This unfortunately won't work for U-Boot and likely also wont
 228           work for using KEXEC to have a hot kernel ready for doing a
 229           KDUMP.
 230
 231           So now the MMU is initialized in head.S but it's necessary to
 232           use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
 233           xt-gdb can't place a Software Breakpoint in the  0XD region prior
 234           to mapping the MMU and after mapping even if the area of low memory
 235           was mapped gdb wouldn't remove the breakpoint on hitting it as the
 236           PC wouldn't match. Since Hardware Breakpoints are recommended for
 237           Linux configurations it seems reasonable to just assume they exist
 238           and leave this older mechanism for unfortunate souls that choose
 239           not to follow Tensilica's recommendation.
 240
 241           Selecting this will cause U-Boot to set the KERNEL Load and Entry
 242           address at 0x00003000 instead of the mapped std of 0xD0003000.
 243
 244           If in doubt, say Y.
 245
 246 config MEMMAP_CACHEATTR
 247         hex "Cache attributes for the memory address space"
 248         depends on !MMU
 249         default 0x22222222
 250         help
 251           These cache attributes are set up for noMMU systems. Each hex digit
 252           specifies cache attributes for the corresponding 512MB memory
 253           region: bits 0..3 -- for addresses 0x00000000..0x1fffffff,
 254           bits 4..7 -- for addresses 0x20000000..0x3fffffff, and so on.
 255
 256           Cache attribute values are specific for the MMU type, so e.g.
 257           for region protection MMUs: 2 is cache bypass, 4 is WB cached,
 258           1 is WT cached, f is illegal. For ful MMU: bit 0 makes it executable,
 259           bit 1 makes it writable, bits 2..3 meaning is 0: cache bypass,
 260           1: WB cache, 2: WT cache, 3: special (c and e are illegal, f is
 261           reserved).
 262
 263 config KSEG_PADDR
 264         hex "Physical address of the KSEG mapping"
 265         depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX && MMU
 266         default 0x00000000
 267         help
 268           This is the physical address where KSEG is mapped. Please refer to
 269           the chosen KSEG layout help for the required address alignment.
 270           Unpacked kernel image (including vectors) must be located completely
 271           within KSEG.
 272           Physical memory below this address is not available to linux.
 273
 274           If unsure, leave the default value here.
 275
 276 config KERNEL_LOAD_ADDRESS
 277         hex "Kernel load address"
 278         default 0x60003000 if !MMU
 279         default 0x00003000 if MMU && INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
 280         default 0xd0003000 if MMU && !INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
 281         help
 282           This is the address where the kernel is loaded.
 283           It is virtual address for MMUv2 configurations and physical address
 284           for all other configurations.
 285
 286           If unsure, leave the default value here.
 287
 288 config VECTORS_OFFSET
 289         hex "Kernel vectors offset"
 290         default 0x00003000
 291         help
 292           This is the offset of the kernel image from the relocatable vectors
 293           base.
 294
 295           If unsure, leave the default value here.
 296
 297 choice
 298         prompt "KSEG layout"
 299         depends on MMU
 300         default XTENSA_KSEG_MMU_V2
 301
 302 config XTENSA_KSEG_MMU_V2
 303         bool "MMUv2: 128MB cached + 128MB uncached"
 304         help
 305           MMUv2 compatible kernel memory map: TLB way 5 maps 128MB starting
 306           at KSEG_PADDR to 0xd0000000 with cache and to 0xd8000000
 307           without cache.
 308           KSEG_PADDR must be aligned to 128MB.
 309
 310 config XTENSA_KSEG_256M
 311         bool "256MB cached + 256MB uncached"
 312         depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
 313         help
 314           TLB way 6 maps 256MB starting at KSEG_PADDR to 0xb0000000
 315           with cache and to 0xc0000000 without cache.
 316           KSEG_PADDR must be aligned to 256MB.
 317
 318 config XTENSA_KSEG_512M
 319         bool "512MB cached + 512MB uncached"
 320         depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
 321         help
 322           TLB way 6 maps 512MB starting at KSEG_PADDR to 0xa0000000
 323           with cache and to 0xc0000000 without cache.
 324           KSEG_PADDR must be aligned to 256MB.
 325
 326 endchoice
 327
 328 config HIGHMEM
 329         bool "High Memory Support"
 330         depends on MMU
 331         help
 332           Linux can use the full amount of RAM in the system by
 333           default. However, the default MMUv2 setup only maps the
 334           lowermost 128 MB of memory linearly to the areas starting
 335           at 0xd0000000 (cached) and 0xd8000000 (uncached).
 336           When there are more than 128 MB memory in the system not
 337           all of it can be "permanently mapped" by the kernel.
 338           The physical memory that's not permanently mapped is called
 339           "high memory".
 340
 341           If you are compiling a kernel which will never run on a
 342           machine with more than 128 MB total physical RAM, answer
 343           N here.
 344
 345           If unsure, say Y.
 346
 347 config FAST_SYSCALL_XTENSA
 348         bool "Enable fast atomic syscalls"
 349         default n
 350         help
 351           fast_syscall_xtensa is a syscall that can make atomic operations
 352           on UP kernel when processor has no s32c1i support.
 353
 354           This syscall is deprecated. It may have issues when called with
 355           invalid arguments. It is provided only for backwards compatibility.
 356           Only enable it if your userspace software requires it.
 357
 358           If unsure, say N.
 359
 360 config FAST_SYSCALL_SPILL_REGISTERS
 361         bool "Enable spill registers syscall"
 362         default n
 363         help
 364           fast_syscall_spill_registers is a syscall that spills all active
 365           register windows of a calling userspace task onto its stack.
 366
 367           This syscall is deprecated. It may have issues when called with
 368           invalid arguments. It is provided only for backwards compatibility.
 369           Only enable it if your userspace software requires it.
 370
 371           If unsure, say N.
 372
 373 endmenu
 374
 375 config XTENSA_CALIBRATE_CCOUNT
 376         def_bool n
 377         help
 378           On some platforms (XT2000, for example), the CPU clock rate can
 379           vary.  The frequency can be determined, however, by measuring
 380           against a well known, fixed frequency, such as an UART oscillator.
 381
 382 config SERIAL_CONSOLE
 383         def_bool n
 384
 385 menu "Platform options"
 386
 387 choice
 388         prompt "Xtensa System Type"
 389         default XTENSA_PLATFORM_ISS
 390
 391 config XTENSA_PLATFORM_ISS
 392         bool "ISS"
 393         select XTENSA_CALIBRATE_CCOUNT
 394         select SERIAL_CONSOLE
 395         help
 396           ISS is an acronym for Tensilica's Instruction Set Simulator.
 397
 398 config XTENSA_PLATFORM_XT2000
 399         bool "XT2000"
 400         select HAVE_IDE
 401         help
 402           XT2000 is the name of Tensilica's feature-rich emulation platform.
 403           This hardware is capable of running a full Linux distribution.
 404
 405 config XTENSA_PLATFORM_XTFPGA
 406         bool "XTFPGA"
 407         select ETHOC if ETHERNET
 408         select PLATFORM_WANT_DEFAULT_MEM if !MMU
 409         select SERIAL_CONSOLE
 410         select XTENSA_CALIBRATE_CCOUNT
 411         help
 412           XTFPGA is the name of Tensilica board family (LX60, LX110, LX200, ML605).
 413           This hardware is capable of running a full Linux distribution.
 414
 415 endchoice
 416
 417 config PLATFORM_NR_IRQS
 418         int
 419         default 3 if XTENSA_PLATFORM_XT2000
 420         default 0
 421
 422 config XTENSA_CPU_CLOCK
 423         int "CPU clock rate [MHz]"
 424         depends on !XTENSA_CALIBRATE_CCOUNT
 425         default 16
 426
 427 config GENERIC_CALIBRATE_DELAY
 428         bool "Auto calibration of the BogoMIPS value"
 429         help
 430           The BogoMIPS value can easily be derived from the CPU frequency.
 431
 432 config CMDLINE_BOOL
 433         bool "Default bootloader kernel arguments"
 434
 435 config CMDLINE
 436         string "Initial kernel command string"
 437         depends on CMDLINE_BOOL
 438         default "console=ttyS0,38400 root=/dev/ram"
 439         help
 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).
 445
 446 config USE_OF
 447         bool "Flattened Device Tree support"
 448         select OF
 449         select OF_EARLY_FLATTREE
 450         select OF_RESERVED_MEM
 451         help
 452           Include support for flattened device tree machine descriptions.
 453
 454 config BUILTIN_DTB_SOURCE
 455         string "DTB to build into the kernel image"
 456         depends on OF
 457
 458 config PARSE_BOOTPARAM
 459         bool "Parse bootparam block"
 460         default y
 461         help
 462           Parse parameters passed to the kernel from the bootloader. It may
 463           be disabled if the kernel is known to run without the bootloader.
 464
 465           If unsure, say Y.
 466
 467 config BLK_DEV_SIMDISK
 468         tristate "Host file-based simulated block device support"
 469         default n
 470         depends on XTENSA_PLATFORM_ISS && BLOCK
 471         help
 472           Create block devices that map to files in the host file system.
 473           Device binding to host file may be changed at runtime via proc
 474           interface provided the device is not in use.
 475
 476 config BLK_DEV_SIMDISK_COUNT
 477         int "Number of host file-based simulated block devices"
 478         range 1 10
 479         depends on BLK_DEV_SIMDISK
 480         default 2
 481         help
 482           This is the default minimal number of created block devices.
 483           Kernel/module parameter 'simdisk_count' may be used to change this
 484           value at runtime. More file names (but no more than 10) may be
 485           specified as parameters, simdisk_count grows accordingly.
 486
 487 config SIMDISK0_FILENAME
 488         string "Host filename for the first simulated device"
 489         depends on BLK_DEV_SIMDISK = y
 490         default ""
 491         help
 492           Attach a first simdisk to a host file. Conventionally, this file
 493           contains a root file system.
 494
 495 config SIMDISK1_FILENAME
 496         string "Host filename for the second simulated device"
 497         depends on BLK_DEV_SIMDISK = y && BLK_DEV_SIMDISK_COUNT != 1
 498         default ""
 499         help
 500           Another simulated disk in a host file for a buildroot-independent
 501           storage.
 502
 503 config FORCE_MAX_ZONEORDER
 504         int "Maximum zone order"
 505         default "11"
 506         help
 507           The kernel memory allocator divides physically contiguous memory
 508           blocks into "zones", where each zone is a power of two number of
 509           pages.  This option selects the largest power of two that the kernel
 510           keeps in the memory allocator.  If you need to allocate very large
 511           blocks of physically contiguous memory, then you may need to
 512           increase this value.
 513
 514           This config option is actually maximum order plus one. For example,
 515           a value of 11 means that the largest free memory block is 2^10 pages.
 516
 517 config PLATFORM_WANT_DEFAULT_MEM
 518         def_bool n
 519
 520 config DEFAULT_MEM_START
 521         hex
 522         prompt "PAGE_OFFSET/PHYS_OFFSET" if !MMU && PLATFORM_WANT_DEFAULT_MEM
 523         default 0x60000000 if PLATFORM_WANT_DEFAULT_MEM
 524         default 0x00000000
 525         help
 526           This is the base address used for both PAGE_OFFSET and PHYS_OFFSET
 527           in noMMU configurations.
 528
 529           If unsure, leave the default value here.
 530
 531 config XTFPGA_LCD
 532         bool "Enable XTFPGA LCD driver"
 533         depends on XTENSA_PLATFORM_XTFPGA
 534         default n
 535         help
 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.
 539
 540           If unsure, say N.
 541
 542 config XTFPGA_LCD_BASE_ADDR
 543         hex "XTFPGA LCD base address"
 544         depends on XTFPGA_LCD
 545         default "0x0d0c0000"
 546         help
 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.
 551
 552 config XTFPGA_LCD_8BIT_ACCESS
 553         bool "Use 8-bit access to XTFPGA LCD"
 554         depends on XTFPGA_LCD
 555         default n
 556         help
 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.
 560
 561 endmenu
 562
 563 menu "Power management options"
 564
 565 source "kernel/power/Kconfig"
 566
 567 endmenu