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
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
19 select HAVE_FUNCTION_TRACER
20 select HAVE_IRQ_TIME_ACCOUNTING
22 select HAVE_PERF_EVENTS
24 select MODULES_USE_ELF_RELA
27 Xtensa processors are 32-bit RISC machines designed by Tensilica
28 primarily for embedded systems. These processors are both
29 configurable and extensible. The Linux port to the Xtensa
30 architecture supports all processor configurations and extensions,
31 with reasonable minimum requirements. The Xtensa Linux project has
32 a home page at <http://www.linux-xtensa.org/>.
34 config RWSEM_XCHGADD_ALGORITHM
37 config GENERIC_HWEIGHT
40 config ARCH_HAS_ILOG2_U32
43 config ARCH_HAS_ILOG2_U64
54 source "kernel/Kconfig.freezer"
56 config LOCKDEP_SUPPORT
59 config STACKTRACE_SUPPORT
62 config TRACE_IRQFLAGS_SUPPORT
67 default n if !XTENSA_VARIANT_CUSTOM
68 default XTENSA_VARIANT_MMU if XTENSA_VARIANT_CUSTOM
70 config VARIANT_IRQ_SWITCH
73 config HAVE_XTENSA_GPIO32
79 menu "Processor type and features"
82 prompt "Xtensa Processor Configuration"
83 default XTENSA_VARIANT_FSF
85 config XTENSA_VARIANT_FSF
86 bool "fsf - default (not generic) configuration"
89 config XTENSA_VARIANT_DC232B
90 bool "dc232b - Diamond 232L Standard Core Rev.B (LE)"
92 select HAVE_XTENSA_GPIO32
94 This variant refers to Tensilica's Diamond 232L Standard core Rev.B (LE).
96 config XTENSA_VARIANT_DC233C
97 bool "dc233c - Diamond 233L Standard Core Rev.C (LE)"
99 select HAVE_XTENSA_GPIO32
101 This variant refers to Tensilica's Diamond 233L Standard core Rev.C (LE).
103 config XTENSA_VARIANT_CUSTOM
104 bool "Custom Xtensa processor configuration"
106 select HAVE_XTENSA_GPIO32
108 Select this variant to use a custom Xtensa processor configuration.
109 You will be prompted for a processor variant CORENAME.
112 config XTENSA_VARIANT_CUSTOM_NAME
113 string "Xtensa Processor Custom Core Variant Name"
114 depends on XTENSA_VARIANT_CUSTOM
116 Provide the name of a custom Xtensa processor variant.
117 This CORENAME selects arch/xtensa/variant/CORENAME.
118 Dont forget you have to select MMU if you have one.
120 config XTENSA_VARIANT_NAME
122 default "dc232b" if XTENSA_VARIANT_DC232B
123 default "dc233c" if XTENSA_VARIANT_DC233C
124 default "fsf" if XTENSA_VARIANT_FSF
125 default XTENSA_VARIANT_CUSTOM_NAME if XTENSA_VARIANT_CUSTOM
127 config XTENSA_VARIANT_MMU
128 bool "Core variant has a Full MMU (TLB, Pages, Protection, etc)"
129 depends on XTENSA_VARIANT_CUSTOM
132 Build a Conventional Kernel with full MMU support,
133 ie: it supports a TLB with auto-loading, page protection.
135 config XTENSA_UNALIGNED_USER
136 bool "Unaligned memory access in use space"
138 The Xtensa architecture currently does not handle unaligned
139 memory accesses in hardware but through an exception handler.
140 Per default, unaligned memory accesses are disabled in user space.
142 Say Y here to enable unaligned memory access in user space.
144 source "kernel/Kconfig.preempt"
147 bool "System Supports SMP (MX)"
148 depends on MAY_HAVE_SMP
151 This option is use to indicate that the system-on-a-chip (SOC)
152 supports Multiprocessing. Multiprocessor support implemented above
153 the CPU core definition and currently needs to be selected manually.
155 Multiprocessor support in implemented with external cache and
156 interrupt controllers.
158 The MX interrupt distributer adds Interprocessor Interrupts
159 and causes the IRQ numbers to be increased by 4 for devices
160 like the open cores ethernet driver and the serial interface.
162 You still have to select "Enable SMP" to enable SMP on this SOC.
165 bool "Enable Symmetric multi-processing support"
167 select GENERIC_SMP_IDLE_THREAD
169 Enabled SMP Software; allows more than one CPU/CORE
170 to be activated during startup.
174 int "Maximum number of CPUs (2-32)"
179 bool "Enable CPU hotplug support"
182 Say Y here to allow turning CPUs off and on. CPUs can be
183 controlled through /sys/devices/system/cpu.
185 Say N if you want to disable CPU hotplug.
187 config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
188 bool "Initialize Xtensa MMU inside the Linux kernel code"
191 Earlier version initialized the MMU in the exception vector
192 before jumping to _startup in head.S and had an advantage that
193 it was possible to place a software breakpoint at 'reset' and
194 then enter your normal kernel breakpoints once the MMU was mapped
195 to the kernel mappings (0XC0000000).
197 This unfortunately doesn't work for U-Boot and likley also wont
198 work for using KEXEC to have a hot kernel ready for doing a
201 So now the MMU is initialized in head.S but it's necessary to
202 use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
203 xt-gdb can't place a Software Breakpoint in the 0XD region prior
204 to mapping the MMU and after mapping even if the area of low memory
205 was mapped gdb wouldn't remove the breakpoint on hitting it as the
206 PC wouldn't match. Since Hardware Breakpoints are recommended for
207 Linux configurations it seems reasonable to just assume they exist
208 and leave this older mechanism for unfortunate souls that choose
209 not to follow Tensilica's recommendation.
211 Selecting this will cause U-Boot to set the KERNEL Load and Entry
212 address at 0x00003000 instead of the mapped std of 0xD0003000.
217 bool "High Memory Support"
220 Linux can use the full amount of RAM in the system by
221 default. However, the default MMUv2 setup only maps the
222 lowermost 128 MB of memory linearly to the areas starting
223 at 0xd0000000 (cached) and 0xd8000000 (uncached).
224 When there are more than 128 MB memory in the system not
225 all of it can be "permanently mapped" by the kernel.
226 The physical memory that's not permanently mapped is called
229 If you are compiling a kernel which will never run on a
230 machine with more than 128 MB total physical RAM, answer
235 config FAST_SYSCALL_XTENSA
236 bool "Enable fast atomic syscalls"
239 fast_syscall_xtensa is a syscall that can make atomic operations
240 on UP kernel when processor has no s32c1i support.
242 This syscall is deprecated. It may have issues when called with
243 invalid arguments. It is provided only for backwards compatibility.
244 Only enable it if your userspace software requires it.
248 config FAST_SYSCALL_SPILL_REGISTERS
249 bool "Enable spill registers syscall"
252 fast_syscall_spill_registers is a syscall that spills all active
253 register windows of a calling userspace task onto its stack.
255 This syscall is deprecated. It may have issues when called with
256 invalid arguments. It is provided only for backwards compatibility.
257 Only enable it if your userspace software requires it.
263 config XTENSA_CALIBRATE_CCOUNT
266 On some platforms (XT2000, for example), the CPU clock rate can
267 vary. The frequency can be determined, however, by measuring
268 against a well known, fixed frequency, such as an UART oscillator.
270 config SERIAL_CONSOLE
279 Find out whether you have a PCI motherboard. PCI is the name of a
280 bus system, i.e. the way the CPU talks to the other stuff inside
281 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
282 VESA. If you have PCI, say Y, otherwise N.
284 source "drivers/pci/Kconfig"
288 menu "Platform options"
291 prompt "Xtensa System Type"
292 default XTENSA_PLATFORM_ISS
294 config XTENSA_PLATFORM_ISS
296 select XTENSA_CALIBRATE_CCOUNT
297 select SERIAL_CONSOLE
299 ISS is an acronym for Tensilica's Instruction Set Simulator.
301 config XTENSA_PLATFORM_XT2000
305 XT2000 is the name of Tensilica's feature-rich emulation platform.
306 This hardware is capable of running a full Linux distribution.
308 config XTENSA_PLATFORM_XTFPGA
310 select ETHOC if ETHERNET
311 select PLATFORM_WANT_DEFAULT_MEM
312 select SERIAL_CONSOLE
313 select XTENSA_CALIBRATE_CCOUNT
315 XTFPGA is the name of Tensilica board family (LX60, LX110, LX200, ML605).
316 This hardware is capable of running a full Linux distribution.
321 config XTENSA_CPU_CLOCK
322 int "CPU clock rate [MHz]"
323 depends on !XTENSA_CALIBRATE_CCOUNT
326 config GENERIC_CALIBRATE_DELAY
327 bool "Auto calibration of the BogoMIPS value"
329 The BogoMIPS value can easily be derived from the CPU frequency.
332 bool "Default bootloader kernel arguments"
335 string "Initial kernel command string"
336 depends on CMDLINE_BOOL
337 default "console=ttyS0,38400 root=/dev/ram"
339 On some architectures (EBSA110 and CATS), there is currently no way
340 for the boot loader to pass arguments to the kernel. For these
341 architectures, you should supply some command-line options at build
342 time by entering them here. As a minimum, you should specify the
343 memory size and the root device (e.g., mem=64M root=/dev/nfs).
346 bool "Flattened Device Tree support"
348 select OF_EARLY_FLATTREE
350 Include support for flattened device tree machine descriptions.
353 string "DTB to build into the kernel image"
356 config BLK_DEV_SIMDISK
357 tristate "Host file-based simulated block device support"
359 depends on XTENSA_PLATFORM_ISS && BLOCK
361 Create block devices that map to files in the host file system.
362 Device binding to host file may be changed at runtime via proc
363 interface provided the device is not in use.
365 config BLK_DEV_SIMDISK_COUNT
366 int "Number of host file-based simulated block devices"
368 depends on BLK_DEV_SIMDISK
371 This is the default minimal number of created block devices.
372 Kernel/module parameter 'simdisk_count' may be used to change this
373 value at runtime. More file names (but no more than 10) may be
374 specified as parameters, simdisk_count grows accordingly.
376 config SIMDISK0_FILENAME
377 string "Host filename for the first simulated device"
378 depends on BLK_DEV_SIMDISK = y
381 Attach a first simdisk to a host file. Conventionally, this file
382 contains a root file system.
384 config SIMDISK1_FILENAME
385 string "Host filename for the second simulated device"
386 depends on BLK_DEV_SIMDISK = y && BLK_DEV_SIMDISK_COUNT != 1
389 Another simulated disk in a host file for a buildroot-independent
394 source "drivers/pcmcia/Kconfig"
396 source "drivers/pci/hotplug/Kconfig"
398 config PLATFORM_WANT_DEFAULT_MEM
401 config DEFAULT_MEM_START
402 hex "Physical address of the default memory area start"
403 depends on PLATFORM_WANT_DEFAULT_MEM
404 default 0x00000000 if MMU
405 default 0x40000000 if !MMU
407 This is a fallback start address of the default memory area, it is
408 used when no physical memory size is passed through DTB or through
409 boot parameter from bootloader.
411 In noMMU configuration the following parameters are derived from it:
412 - kernel load address;
413 - kernel entry point address;
414 - relocatable vectors base address;
415 - uBoot load address;
418 If unsure, leave the default value here.
420 config DEFAULT_MEM_SIZE
421 hex "Maximal size of the default memory area"
422 depends on PLATFORM_WANT_DEFAULT_MEM
425 This is a fallback size of the default memory area, it is used when
426 no physical memory size is passed through DTB or through boot
427 parameter from bootloader.
429 It's also used for TASK_SIZE calculation in noMMU configuration.
431 If unsure, leave the default value here.
434 bool "Enable XTFPGA LCD driver"
435 depends on XTENSA_PLATFORM_XTFPGA
438 There's a 2x16 LCD on most of XTFPGA boards, kernel may output
439 progress messages there during bootup/shutdown. It may be useful
440 during board bringup.
444 config XTFPGA_LCD_BASE_ADDR
445 hex "XTFPGA LCD base address"
446 depends on XTFPGA_LCD
449 Base address of the LCD controller inside KIO region.
450 Different boards from XTFPGA family have LCD controller at different
451 addresses. Please consult prototyping user guide for your board for
452 the correct address. Wrong address here may lead to hardware lockup.
454 config XTFPGA_LCD_8BIT_ACCESS
455 bool "Use 8-bit access to XTFPGA LCD"
456 depends on XTFPGA_LCD
459 LCD may be connected with 4- or 8-bit interface, 8-bit access may
460 only be used with 8-bit interface. Please consult prototyping user
461 guide for your board for the correct interface width.
465 menu "Executable file formats"
467 source "fs/Kconfig.binfmt"
471 menu "Power management options"
473 source "kernel/power/Kconfig"
479 source "drivers/Kconfig"
483 source "arch/xtensa/Kconfig.debug"
485 source "security/Kconfig"
487 source "crypto/Kconfig"