arch/xtensa/Kconfig

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