arch/xtensa/Kconfig

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