6 select ARCH_WANT_FRAME_POINTERS
7 select ARCH_WANT_IPC_PARSE_VERSION
8 select BUILDTIME_EXTABLE_SORT
11 select GENERIC_ATOMIC64
12 select GENERIC_CLOCKEVENTS
13 select GENERIC_IRQ_SHOW
14 select GENERIC_PCI_IOMAP
15 select GENERIC_SCHED_CLOCK
16 select HAVE_DMA_API_DEBUG
17 select HAVE_FUNCTION_TRACER
18 select HAVE_FUTEX_CMPXCHG if !MMU
19 select HAVE_HW_BREAKPOINT if PERF_EVENTS
20 select HAVE_IRQ_TIME_ACCOUNTING
22 select HAVE_PERF_EVENTS
24 select MODULES_USE_ELF_RELA
25 select PERF_USE_VMALLOC
28 Xtensa processors are 32-bit RISC machines designed by Tensilica
29 primarily for embedded systems. These processors are both
30 configurable and extensible. The Linux port to the Xtensa
31 architecture supports all processor configurations and extensions,
32 with reasonable minimum requirements. The Xtensa Linux project has
33 a home page at <http://www.linux-xtensa.org/>.
35 config RWSEM_XCHGADD_ALGORITHM
38 config GENERIC_HWEIGHT
41 config ARCH_HAS_ILOG2_U32
44 config ARCH_HAS_ILOG2_U64
55 source "kernel/Kconfig.freezer"
57 config LOCKDEP_SUPPORT
60 config STACKTRACE_SUPPORT
63 config TRACE_IRQFLAGS_SUPPORT
69 config VARIANT_IRQ_SWITCH
72 config HAVE_XTENSA_GPIO32
75 menu "Processor type and features"
78 prompt "Xtensa Processor Configuration"
79 default XTENSA_VARIANT_FSF
81 config XTENSA_VARIANT_FSF
82 bool "fsf - default (not generic) configuration"
85 config XTENSA_VARIANT_DC232B
86 bool "dc232b - Diamond 232L Standard Core Rev.B (LE)"
88 select HAVE_XTENSA_GPIO32
90 This variant refers to Tensilica's Diamond 232L Standard core Rev.B (LE).
92 config XTENSA_VARIANT_DC233C
93 bool "dc233c - Diamond 233L Standard Core Rev.C (LE)"
95 select HAVE_XTENSA_GPIO32
97 This variant refers to Tensilica's Diamond 233L Standard core Rev.C (LE).
99 config XTENSA_VARIANT_CUSTOM
100 bool "Custom Xtensa processor configuration"
101 select HAVE_XTENSA_GPIO32
103 Select this variant to use a custom Xtensa processor configuration.
104 You will be prompted for a processor variant CORENAME.
107 config XTENSA_VARIANT_CUSTOM_NAME
108 string "Xtensa Processor Custom Core Variant Name"
109 depends on XTENSA_VARIANT_CUSTOM
111 Provide the name of a custom Xtensa processor variant.
112 This CORENAME selects arch/xtensa/variant/CORENAME.
113 Dont forget you have to select MMU if you have one.
115 config XTENSA_VARIANT_NAME
117 default "dc232b" if XTENSA_VARIANT_DC232B
118 default "dc233c" if XTENSA_VARIANT_DC233C
119 default "fsf" if XTENSA_VARIANT_FSF
120 default XTENSA_VARIANT_CUSTOM_NAME if XTENSA_VARIANT_CUSTOM
122 config XTENSA_VARIANT_MMU
123 bool "Core variant has a Full MMU (TLB, Pages, Protection, etc)"
124 depends on XTENSA_VARIANT_CUSTOM
128 Build a Conventional Kernel with full MMU support,
129 ie: it supports a TLB with auto-loading, page protection.
131 config XTENSA_VARIANT_HAVE_PERF_EVENTS
132 bool "Core variant has Performance Monitor Module"
133 depends on XTENSA_VARIANT_CUSTOM
136 Enable if core variant has Performance Monitor Module with
137 External Registers Interface.
141 config XTENSA_FAKE_NMI
142 bool "Treat PMM IRQ as NMI"
143 depends on XTENSA_VARIANT_HAVE_PERF_EVENTS
146 If PMM IRQ is the only IRQ at EXCM level it is safe to
147 treat it as NMI, which improves accuracy of profiling.
149 If there are other interrupts at or above PMM IRQ priority level
150 but not above the EXCM level, PMM IRQ still may be treated as NMI,
151 but only if these IRQs are not used. There will be a build warning
152 saying that this is not safe, and a bugcheck if one of these IRQs
157 config XTENSA_UNALIGNED_USER
158 bool "Unaligned memory access in use space"
160 The Xtensa architecture currently does not handle unaligned
161 memory accesses in hardware but through an exception handler.
162 Per default, unaligned memory accesses are disabled in user space.
164 Say Y here to enable unaligned memory access in user space.
166 source "kernel/Kconfig.preempt"
169 bool "System Supports SMP (MX)"
170 depends on XTENSA_VARIANT_CUSTOM
173 This option is use to indicate that the system-on-a-chip (SOC)
174 supports Multiprocessing. Multiprocessor support implemented above
175 the CPU core definition and currently needs to be selected manually.
177 Multiprocessor support in implemented with external cache and
178 interrupt controllers.
180 The MX interrupt distributer adds Interprocessor Interrupts
181 and causes the IRQ numbers to be increased by 4 for devices
182 like the open cores ethernet driver and the serial interface.
184 You still have to select "Enable SMP" to enable SMP on this SOC.
187 bool "Enable Symmetric multi-processing support"
189 select GENERIC_SMP_IDLE_THREAD
191 Enabled SMP Software; allows more than one CPU/CORE
192 to be activated during startup.
196 int "Maximum number of CPUs (2-32)"
201 bool "Enable CPU hotplug support"
204 Say Y here to allow turning CPUs off and on. CPUs can be
205 controlled through /sys/devices/system/cpu.
207 Say N if you want to disable CPU hotplug.
209 config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
210 bool "Initialize Xtensa MMU inside the Linux kernel code"
213 Earlier version initialized the MMU in the exception vector
214 before jumping to _startup in head.S and had an advantage that
215 it was possible to place a software breakpoint at 'reset' and
216 then enter your normal kernel breakpoints once the MMU was mapped
217 to the kernel mappings (0XC0000000).
219 This unfortunately doesn't work for U-Boot and likley also wont
220 work for using KEXEC to have a hot kernel ready for doing a
223 So now the MMU is initialized in head.S but it's necessary to
224 use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
225 xt-gdb can't place a Software Breakpoint in the 0XD region prior
226 to mapping the MMU and after mapping even if the area of low memory
227 was mapped gdb wouldn't remove the breakpoint on hitting it as the
228 PC wouldn't match. Since Hardware Breakpoints are recommended for
229 Linux configurations it seems reasonable to just assume they exist
230 and leave this older mechanism for unfortunate souls that choose
231 not to follow Tensilica's recommendation.
233 Selecting this will cause U-Boot to set the KERNEL Load and Entry
234 address at 0x00003000 instead of the mapped std of 0xD0003000.
239 bool "High Memory Support"
242 Linux can use the full amount of RAM in the system by
243 default. However, the default MMUv2 setup only maps the
244 lowermost 128 MB of memory linearly to the areas starting
245 at 0xd0000000 (cached) and 0xd8000000 (uncached).
246 When there are more than 128 MB memory in the system not
247 all of it can be "permanently mapped" by the kernel.
248 The physical memory that's not permanently mapped is called
251 If you are compiling a kernel which will never run on a
252 machine with more than 128 MB total physical RAM, answer
257 config FAST_SYSCALL_XTENSA
258 bool "Enable fast atomic syscalls"
261 fast_syscall_xtensa is a syscall that can make atomic operations
262 on UP kernel when processor has no s32c1i support.
264 This syscall is deprecated. It may have issues when called with
265 invalid arguments. It is provided only for backwards compatibility.
266 Only enable it if your userspace software requires it.
270 config FAST_SYSCALL_SPILL_REGISTERS
271 bool "Enable spill registers syscall"
274 fast_syscall_spill_registers is a syscall that spills all active
275 register windows of a calling userspace task onto its stack.
277 This syscall is deprecated. It may have issues when called with
278 invalid arguments. It is provided only for backwards compatibility.
279 Only enable it if your userspace software requires it.
285 config XTENSA_CALIBRATE_CCOUNT
288 On some platforms (XT2000, for example), the CPU clock rate can
289 vary. The frequency can be determined, however, by measuring
290 against a well known, fixed frequency, such as an UART oscillator.
292 config SERIAL_CONSOLE
301 Find out whether you have a PCI motherboard. PCI is the name of a
302 bus system, i.e. the way the CPU talks to the other stuff inside
303 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
304 VESA. If you have PCI, say Y, otherwise N.
306 source "drivers/pci/Kconfig"
310 menu "Platform options"
313 prompt "Xtensa System Type"
314 default XTENSA_PLATFORM_ISS
316 config XTENSA_PLATFORM_ISS
318 select XTENSA_CALIBRATE_CCOUNT
319 select SERIAL_CONSOLE
321 ISS is an acronym for Tensilica's Instruction Set Simulator.
323 config XTENSA_PLATFORM_XT2000
327 XT2000 is the name of Tensilica's feature-rich emulation platform.
328 This hardware is capable of running a full Linux distribution.
330 config XTENSA_PLATFORM_XTFPGA
332 select ETHOC if ETHERNET
333 select PLATFORM_WANT_DEFAULT_MEM
334 select SERIAL_CONSOLE
335 select XTENSA_CALIBRATE_CCOUNT
337 XTFPGA is the name of Tensilica board family (LX60, LX110, LX200, ML605).
338 This hardware is capable of running a full Linux distribution.
343 config XTENSA_CPU_CLOCK
344 int "CPU clock rate [MHz]"
345 depends on !XTENSA_CALIBRATE_CCOUNT
348 config GENERIC_CALIBRATE_DELAY
349 bool "Auto calibration of the BogoMIPS value"
351 The BogoMIPS value can easily be derived from the CPU frequency.
354 bool "Default bootloader kernel arguments"
357 string "Initial kernel command string"
358 depends on CMDLINE_BOOL
359 default "console=ttyS0,38400 root=/dev/ram"
361 On some architectures (EBSA110 and CATS), there is currently no way
362 for the boot loader to pass arguments to the kernel. For these
363 architectures, you should supply some command-line options at build
364 time by entering them here. As a minimum, you should specify the
365 memory size and the root device (e.g., mem=64M root=/dev/nfs).
368 bool "Flattened Device Tree support"
370 select OF_EARLY_FLATTREE
372 Include support for flattened device tree machine descriptions.
375 string "DTB to build into the kernel image"
378 config BLK_DEV_SIMDISK
379 tristate "Host file-based simulated block device support"
381 depends on XTENSA_PLATFORM_ISS && BLOCK
383 Create block devices that map to files in the host file system.
384 Device binding to host file may be changed at runtime via proc
385 interface provided the device is not in use.
387 config BLK_DEV_SIMDISK_COUNT
388 int "Number of host file-based simulated block devices"
390 depends on BLK_DEV_SIMDISK
393 This is the default minimal number of created block devices.
394 Kernel/module parameter 'simdisk_count' may be used to change this
395 value at runtime. More file names (but no more than 10) may be
396 specified as parameters, simdisk_count grows accordingly.
398 config SIMDISK0_FILENAME
399 string "Host filename for the first simulated device"
400 depends on BLK_DEV_SIMDISK = y
403 Attach a first simdisk to a host file. Conventionally, this file
404 contains a root file system.
406 config SIMDISK1_FILENAME
407 string "Host filename for the second simulated device"
408 depends on BLK_DEV_SIMDISK = y && BLK_DEV_SIMDISK_COUNT != 1
411 Another simulated disk in a host file for a buildroot-independent
416 config FORCE_MAX_ZONEORDER
417 int "Maximum zone order"
420 The kernel memory allocator divides physically contiguous memory
421 blocks into "zones", where each zone is a power of two number of
422 pages. This option selects the largest power of two that the kernel
423 keeps in the memory allocator. If you need to allocate very large
424 blocks of physically contiguous memory, then you may need to
427 This config option is actually maximum order plus one. For example,
428 a value of 11 means that the largest free memory block is 2^10 pages.
430 source "drivers/pcmcia/Kconfig"
432 config PLATFORM_WANT_DEFAULT_MEM
435 config DEFAULT_MEM_START
436 hex "Physical address of the default memory area start"
437 depends on PLATFORM_WANT_DEFAULT_MEM
438 default 0x00000000 if MMU
439 default 0x60000000 if !MMU
441 This is a fallback start address of the default memory area, it is
442 used when no physical memory size is passed through DTB or through
443 boot parameter from bootloader.
445 In noMMU configuration the following parameters are derived from it:
446 - kernel load address;
447 - kernel entry point address;
448 - relocatable vectors base address;
449 - uBoot load address;
452 If unsure, leave the default value here.
454 config DEFAULT_MEM_SIZE
455 hex "Maximal size of the default memory area"
456 depends on PLATFORM_WANT_DEFAULT_MEM
459 This is a fallback size of the default memory area, it is used when
460 no physical memory size is passed through DTB or through boot
461 parameter from bootloader.
463 It's also used for TASK_SIZE calculation in noMMU configuration.
465 If unsure, leave the default value here.
468 bool "Enable XTFPGA LCD driver"
469 depends on XTENSA_PLATFORM_XTFPGA
472 There's a 2x16 LCD on most of XTFPGA boards, kernel may output
473 progress messages there during bootup/shutdown. It may be useful
474 during board bringup.
478 config XTFPGA_LCD_BASE_ADDR
479 hex "XTFPGA LCD base address"
480 depends on XTFPGA_LCD
483 Base address of the LCD controller inside KIO region.
484 Different boards from XTFPGA family have LCD controller at different
485 addresses. Please consult prototyping user guide for your board for
486 the correct address. Wrong address here may lead to hardware lockup.
488 config XTFPGA_LCD_8BIT_ACCESS
489 bool "Use 8-bit access to XTFPGA LCD"
490 depends on XTFPGA_LCD
493 LCD may be connected with 4- or 8-bit interface, 8-bit access may
494 only be used with 8-bit interface. Please consult prototyping user
495 guide for your board for the correct interface width.
499 menu "Executable file formats"
501 source "fs/Kconfig.binfmt"
505 menu "Power management options"
507 source "kernel/power/Kconfig"
513 source "drivers/Kconfig"
517 source "arch/xtensa/Kconfig.debug"
519 source "security/Kconfig"
521 source "crypto/Kconfig"