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
23 Xtensa processors are 32-bit RISC machines designed by Tensilica
24 primarily for embedded systems. These processors are both
25 configurable and extensible. The Linux port to the Xtensa
26 architecture supports all processor configurations and extensions,
27 with reasonable minimum requirements. The Xtensa Linux project has
28 a home page at <http://www.linux-xtensa.org/>.
30 config RWSEM_XCHGADD_ALGORITHM
33 config GENERIC_HWEIGHT
36 config ARCH_HAS_ILOG2_U32
39 config ARCH_HAS_ILOG2_U64
50 source "kernel/Kconfig.freezer"
52 config LOCKDEP_SUPPORT
55 config STACKTRACE_SUPPORT
58 config TRACE_IRQFLAGS_SUPPORT
64 config VARIANT_IRQ_SWITCH
70 menu "Processor type and features"
73 prompt "Xtensa Processor Configuration"
74 default XTENSA_VARIANT_FSF
76 config XTENSA_VARIANT_FSF
77 bool "fsf - default (not generic) configuration"
80 config XTENSA_VARIANT_DC232B
81 bool "dc232b - Diamond 232L Standard Core Rev.B (LE)"
84 This variant refers to Tensilica's Diamond 232L Standard core Rev.B (LE).
86 config XTENSA_VARIANT_DC233C
87 bool "dc233c - Diamond 233L Standard Core Rev.C (LE)"
90 This variant refers to Tensilica's Diamond 233L Standard core Rev.C (LE).
92 config XTENSA_VARIANT_S6000
93 bool "s6000 - Stretch software configurable processor"
94 select VARIANT_IRQ_SWITCH
95 select ARCH_REQUIRE_GPIOLIB
96 select XTENSA_CALIBRATE_CCOUNT
99 config XTENSA_UNALIGNED_USER
100 bool "Unaligned memory access in use space"
102 The Xtensa architecture currently does not handle unaligned
103 memory accesses in hardware but through an exception handler.
104 Per default, unaligned memory accesses are disabled in user space.
106 Say Y here to enable unaligned memory access in user space.
108 source "kernel/Kconfig.preempt"
111 bool "System Supports SMP (MX)"
112 depends on MAY_HAVE_SMP
115 This option is use to indicate that the system-on-a-chip (SOC)
116 supports Multiprocessing. Multiprocessor support implemented above
117 the CPU core definition and currently needs to be selected manually.
119 Multiprocessor support in implemented with external cache and
120 interrupt controlers.
122 The MX interrupt distributer adds Interprocessor Interrupts
123 and causes the IRQ numbers to be increased by 4 for devices
124 like the open cores ethernet driver and the serial interface.
126 You still have to select "Enable SMP" to enable SMP on this SOC.
129 bool "Enable Symmetric multi-processing support"
131 select USE_GENERIC_SMP_HELPERS
132 select GENERIC_SMP_IDLE_THREAD
134 Enabled SMP Software; allows more than one CPU/CORE
135 to be activated during startup.
139 int "Maximum number of CPUs (2-32)"
143 config MATH_EMULATION
144 bool "Math emulation"
146 Can we use information of configuration file?
148 config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
149 bool "Initialize Xtensa MMU inside the Linux kernel code"
152 Earlier version initialized the MMU in the exception vector
153 before jumping to _startup in head.S and had an advantage that
154 it was possible to place a software breakpoint at 'reset' and
155 then enter your normal kernel breakpoints once the MMU was mapped
156 to the kernel mappings (0XC0000000).
158 This unfortunately doesn't work for U-Boot and likley also wont
159 work for using KEXEC to have a hot kernel ready for doing a
162 So now the MMU is initialized in head.S but it's necessary to
163 use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
164 xt-gdb can't place a Software Breakpoint in the 0XD region prior
165 to mapping the MMU and after mapping even if the area of low memory
166 was mapped gdb wouldn't remove the breakpoint on hitting it as the
167 PC wouldn't match. Since Hardware Breakpoints are recommended for
168 Linux configurations it seems reasonable to just assume they exist
169 and leave this older mechanism for unfortunate souls that choose
170 not to follow Tensilica's recommendation.
172 Selecting this will cause U-Boot to set the KERNEL Load and Entry
173 address at 0x00003000 instead of the mapped std of 0xD0003000.
179 config XTENSA_CALIBRATE_CCOUNT
182 On some platforms (XT2000, for example), the CPU clock rate can
183 vary. The frequency can be determined, however, by measuring
184 against a well known, fixed frequency, such as an UART oscillator.
186 config SERIAL_CONSOLE
189 config XTENSA_ISS_NETWORK
198 Find out whether you have a PCI motherboard. PCI is the name of a
199 bus system, i.e. the way the CPU talks to the other stuff inside
200 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
201 VESA. If you have PCI, say Y, otherwise N.
203 source "drivers/pci/Kconfig"
207 menu "Platform options"
210 prompt "Xtensa System Type"
211 default XTENSA_PLATFORM_ISS
213 config XTENSA_PLATFORM_ISS
216 select XTENSA_CALIBRATE_CCOUNT
217 select SERIAL_CONSOLE
218 select XTENSA_ISS_NETWORK
220 ISS is an acronym for Tensilica's Instruction Set Simulator.
222 config XTENSA_PLATFORM_XT2000
225 XT2000 is the name of Tensilica's feature-rich emulation platform.
226 This hardware is capable of running a full Linux distribution.
228 config XTENSA_PLATFORM_S6105
230 select SERIAL_CONSOLE
233 config XTENSA_PLATFORM_XTFPGA
235 select SERIAL_CONSOLE
237 select XTENSA_CALIBRATE_CCOUNT
239 XTFPGA is the name of Tensilica board family (LX60, LX110, LX200, ML605).
240 This hardware is capable of running a full Linux distribution.
245 config XTENSA_CPU_CLOCK
246 int "CPU clock rate [MHz]"
247 depends on !XTENSA_CALIBRATE_CCOUNT
250 config GENERIC_CALIBRATE_DELAY
251 bool "Auto calibration of the BogoMIPS value"
253 The BogoMIPS value can easily be derived from the CPU frequency.
256 bool "Default bootloader kernel arguments"
259 string "Initial kernel command string"
260 depends on CMDLINE_BOOL
261 default "console=ttyS0,38400 root=/dev/ram"
263 On some architectures (EBSA110 and CATS), there is currently no way
264 for the boot loader to pass arguments to the kernel. For these
265 architectures, you should supply some command-line options at build
266 time by entering them here. As a minimum, you should specify the
267 memory size and the root device (e.g., mem=64M root=/dev/nfs).
270 bool "Flattened Device Tree support"
272 select OF_EARLY_FLATTREE
274 Include support for flattened device tree machine descriptions.
277 string "DTB to build into the kernel image"
280 config BLK_DEV_SIMDISK
281 tristate "Host file-based simulated block device support"
283 depends on XTENSA_PLATFORM_ISS
285 Create block devices that map to files in the host file system.
286 Device binding to host file may be changed at runtime via proc
287 interface provided the device is not in use.
289 config BLK_DEV_SIMDISK_COUNT
290 int "Number of host file-based simulated block devices"
292 depends on BLK_DEV_SIMDISK
295 This is the default minimal number of created block devices.
296 Kernel/module parameter 'simdisk_count' may be used to change this
297 value at runtime. More file names (but no more than 10) may be
298 specified as parameters, simdisk_count grows accordingly.
300 config SIMDISK0_FILENAME
301 string "Host filename for the first simulated device"
302 depends on BLK_DEV_SIMDISK = y
305 Attach a first simdisk to a host file. Conventionally, this file
306 contains a root file system.
308 config SIMDISK1_FILENAME
309 string "Host filename for the second simulated device"
310 depends on BLK_DEV_SIMDISK = y && BLK_DEV_SIMDISK_COUNT != 1
313 Another simulated disk in a host file for a buildroot-independent
318 source "drivers/pcmcia/Kconfig"
320 source "drivers/pci/hotplug/Kconfig"
324 menu "Executable file formats"
326 source "fs/Kconfig.binfmt"
332 source "drivers/Kconfig"
336 source "arch/xtensa/Kconfig.debug"
338 source "security/Kconfig"
340 source "crypto/Kconfig"