6 select ARCH_WANT_FRAME_POINTERS
8 select GENERIC_ATOMIC64
9 select GENERIC_CLOCKEVENTS
11 select GENERIC_IRQ_SHOW
12 select GENERIC_SCHED_CLOCK
13 select MODULES_USE_ELF_RELA
14 select GENERIC_PCI_IOMAP
15 select ARCH_WANT_IPC_PARSE_VERSION
16 select ARCH_WANT_OPTIONAL_GPIOLIB
17 select CLONE_BACKWARDS
20 select HAVE_FUNCTION_TRACER
21 select HAVE_IRQ_TIME_ACCOUNTING
22 select HAVE_PERF_EVENTS
25 Xtensa processors are 32-bit RISC machines designed by Tensilica
26 primarily for embedded systems. These processors are both
27 configurable and extensible. The Linux port to the Xtensa
28 architecture supports all processor configurations and extensions,
29 with reasonable minimum requirements. The Xtensa Linux project has
30 a home page at <http://www.linux-xtensa.org/>.
32 config RWSEM_XCHGADD_ALGORITHM
35 config GENERIC_HWEIGHT
38 config ARCH_HAS_ILOG2_U32
41 config ARCH_HAS_ILOG2_U64
52 source "kernel/Kconfig.freezer"
54 config LOCKDEP_SUPPORT
57 config STACKTRACE_SUPPORT
60 config TRACE_IRQFLAGS_SUPPORT
66 config VARIANT_IRQ_SWITCH
69 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_S6000
100 bool "s6000 - Stretch software configurable processor"
101 select VARIANT_IRQ_SWITCH
102 select ARCH_REQUIRE_GPIOLIB
103 select XTENSA_CALIBRATE_CCOUNT
106 config XTENSA_UNALIGNED_USER
107 bool "Unaligned memory access in use space"
109 The Xtensa architecture currently does not handle unaligned
110 memory accesses in hardware but through an exception handler.
111 Per default, unaligned memory accesses are disabled in user space.
113 Say Y here to enable unaligned memory access in user space.
115 source "kernel/Kconfig.preempt"
118 bool "System Supports SMP (MX)"
119 depends on MAY_HAVE_SMP
122 This option is use to indicate that the system-on-a-chip (SOC)
123 supports Multiprocessing. Multiprocessor support implemented above
124 the CPU core definition and currently needs to be selected manually.
126 Multiprocessor support in implemented with external cache and
127 interrupt controlers.
129 The MX interrupt distributer adds Interprocessor Interrupts
130 and causes the IRQ numbers to be increased by 4 for devices
131 like the open cores ethernet driver and the serial interface.
133 You still have to select "Enable SMP" to enable SMP on this SOC.
136 bool "Enable Symmetric multi-processing support"
138 select GENERIC_SMP_IDLE_THREAD
140 Enabled SMP Software; allows more than one CPU/CORE
141 to be activated during startup.
145 int "Maximum number of CPUs (2-32)"
150 bool "Enable CPU hotplug support"
153 Say Y here to allow turning CPUs off and on. CPUs can be
154 controlled through /sys/devices/system/cpu.
156 Say N if you want to disable CPU hotplug.
158 config MATH_EMULATION
159 bool "Math emulation"
161 Can we use information of configuration file?
163 config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
164 bool "Initialize Xtensa MMU inside the Linux kernel code"
167 Earlier version initialized the MMU in the exception vector
168 before jumping to _startup in head.S and had an advantage that
169 it was possible to place a software breakpoint at 'reset' and
170 then enter your normal kernel breakpoints once the MMU was mapped
171 to the kernel mappings (0XC0000000).
173 This unfortunately doesn't work for U-Boot and likley also wont
174 work for using KEXEC to have a hot kernel ready for doing a
177 So now the MMU is initialized in head.S but it's necessary to
178 use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
179 xt-gdb can't place a Software Breakpoint in the 0XD region prior
180 to mapping the MMU and after mapping even if the area of low memory
181 was mapped gdb wouldn't remove the breakpoint on hitting it as the
182 PC wouldn't match. Since Hardware Breakpoints are recommended for
183 Linux configurations it seems reasonable to just assume they exist
184 and leave this older mechanism for unfortunate souls that choose
185 not to follow Tensilica's recommendation.
187 Selecting this will cause U-Boot to set the KERNEL Load and Entry
188 address at 0x00003000 instead of the mapped std of 0xD0003000.
194 config XTENSA_CALIBRATE_CCOUNT
197 On some platforms (XT2000, for example), the CPU clock rate can
198 vary. The frequency can be determined, however, by measuring
199 against a well known, fixed frequency, such as an UART oscillator.
201 config SERIAL_CONSOLE
210 Find out whether you have a PCI motherboard. PCI is the name of a
211 bus system, i.e. the way the CPU talks to the other stuff inside
212 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
213 VESA. If you have PCI, say Y, otherwise N.
215 source "drivers/pci/Kconfig"
219 menu "Platform options"
222 prompt "Xtensa System Type"
223 default XTENSA_PLATFORM_ISS
225 config XTENSA_PLATFORM_ISS
228 select XTENSA_CALIBRATE_CCOUNT
229 select SERIAL_CONSOLE
231 ISS is an acronym for Tensilica's Instruction Set Simulator.
233 config XTENSA_PLATFORM_XT2000
236 XT2000 is the name of Tensilica's feature-rich emulation platform.
237 This hardware is capable of running a full Linux distribution.
239 config XTENSA_PLATFORM_S6105
241 select SERIAL_CONSOLE
244 config XTENSA_PLATFORM_XTFPGA
246 select SERIAL_CONSOLE
248 select XTENSA_CALIBRATE_CCOUNT
250 XTFPGA is the name of Tensilica board family (LX60, LX110, LX200, ML605).
251 This hardware is capable of running a full Linux distribution.
256 config XTENSA_CPU_CLOCK
257 int "CPU clock rate [MHz]"
258 depends on !XTENSA_CALIBRATE_CCOUNT
261 config GENERIC_CALIBRATE_DELAY
262 bool "Auto calibration of the BogoMIPS value"
264 The BogoMIPS value can easily be derived from the CPU frequency.
267 bool "Default bootloader kernel arguments"
270 string "Initial kernel command string"
271 depends on CMDLINE_BOOL
272 default "console=ttyS0,38400 root=/dev/ram"
274 On some architectures (EBSA110 and CATS), there is currently no way
275 for the boot loader to pass arguments to the kernel. For these
276 architectures, you should supply some command-line options at build
277 time by entering them here. As a minimum, you should specify the
278 memory size and the root device (e.g., mem=64M root=/dev/nfs).
281 bool "Flattened Device Tree support"
283 select OF_EARLY_FLATTREE
285 Include support for flattened device tree machine descriptions.
288 string "DTB to build into the kernel image"
291 config BLK_DEV_SIMDISK
292 tristate "Host file-based simulated block device support"
294 depends on XTENSA_PLATFORM_ISS
296 Create block devices that map to files in the host file system.
297 Device binding to host file may be changed at runtime via proc
298 interface provided the device is not in use.
300 config BLK_DEV_SIMDISK_COUNT
301 int "Number of host file-based simulated block devices"
303 depends on BLK_DEV_SIMDISK
306 This is the default minimal number of created block devices.
307 Kernel/module parameter 'simdisk_count' may be used to change this
308 value at runtime. More file names (but no more than 10) may be
309 specified as parameters, simdisk_count grows accordingly.
311 config SIMDISK0_FILENAME
312 string "Host filename for the first simulated device"
313 depends on BLK_DEV_SIMDISK = y
316 Attach a first simdisk to a host file. Conventionally, this file
317 contains a root file system.
319 config SIMDISK1_FILENAME
320 string "Host filename for the second simulated device"
321 depends on BLK_DEV_SIMDISK = y && BLK_DEV_SIMDISK_COUNT != 1
324 Another simulated disk in a host file for a buildroot-independent
329 source "drivers/pcmcia/Kconfig"
331 source "drivers/pci/hotplug/Kconfig"
335 menu "Executable file formats"
337 source "fs/Kconfig.binfmt"
340 bool "Enable XTFPGA LCD driver"
341 depends on XTENSA_PLATFORM_XTFPGA
344 There's a 2x16 LCD on most of XTFPGA boards, kernel may output
345 progress messages there during bootup/shutdown. It may be useful
346 during board bringup.
350 config XTFPGA_LCD_BASE_ADDR
351 hex "XTFPGA LCD base address"
352 depends on XTFPGA_LCD
355 Base address of the LCD controller inside KIO region.
356 Different boards from XTFPGA family have LCD controller at different
357 addresses. Please consult prototyping user guide for your board for
358 the correct address. Wrong address here may lead to hardware lockup.
360 config XTFPGA_LCD_8BIT_ACCESS
361 bool "Use 8-bit access to XTFPGA LCD"
362 depends on XTFPGA_LCD
365 LCD may be connected with 4- or 8-bit interface, 8-bit access may
366 only be used with 8-bit interface. Please consult prototyping user
367 guide for your board for the correct interface width.
373 source "drivers/Kconfig"
377 source "arch/xtensa/Kconfig.debug"
379 source "security/Kconfig"
381 source "crypto/Kconfig"