10 select GENERIC_ATOMIC64
11 select HAVE_GENERIC_HARDIRQS
13 select GENERIC_IRQ_SHOW
14 select GENERIC_CPU_DEVICES
15 select MODULES_USE_ELF_RELA
16 select GENERIC_PCI_IOMAP
17 select ARCH_WANT_IPC_PARSE_VERSION
18 select ARCH_WANT_OPTIONAL_GPIOLIB
19 select CLONE_BACKWARDS
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
39 config ARCH_HAS_ILOG2_U32
42 config ARCH_HAS_ILOG2_U64
53 source "kernel/Kconfig.freezer"
55 config STACKTRACE_SUPPORT
61 config VARIANT_IRQ_SWITCH
64 menu "Processor type and features"
67 prompt "Xtensa Processor Configuration"
68 default XTENSA_VARIANT_FSF
70 config XTENSA_VARIANT_FSF
71 bool "fsf - default (not generic) configuration"
74 config XTENSA_VARIANT_DC232B
75 bool "dc232b - Diamond 232L Standard Core Rev.B (LE)"
78 This variant refers to Tensilica's Diamond 232L Standard core Rev.B (LE).
80 config XTENSA_VARIANT_DC233C
81 bool "dc233c - Diamond 233L Standard Core Rev.C (LE)"
84 This variant refers to Tensilica's Diamond 233L Standard core Rev.C (LE).
86 config XTENSA_VARIANT_S6000
87 bool "s6000 - Stretch software configurable processor"
88 select VARIANT_IRQ_SWITCH
89 select ARCH_REQUIRE_GPIOLIB
90 select XTENSA_CALIBRATE_CCOUNT
93 config XTENSA_UNALIGNED_USER
94 bool "Unaligned memory access in use space"
96 The Xtensa architecture currently does not handle unaligned
97 memory accesses in hardware but through an exception handler.
98 Per default, unaligned memory accesses are disabled in user space.
100 Say Y here to enable unaligned memory access in user space.
102 source "kernel/Kconfig.preempt"
104 config MATH_EMULATION
105 bool "Math emulation"
107 Can we use information of configuration file?
109 config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
110 bool "Initialize Xtensa MMU inside the Linux kernel code"
113 Earlier version initialized the MMU in the exception vector
114 before jumping to _startup in head.S and had an advantage that
115 it was possible to place a software breakpoint at 'reset' and
116 then enter your normal kernel breakpoints once the MMU was mapped
117 to the kernel mappings (0XC0000000).
119 This unfortunately doesn't work for U-Boot and likley also wont
120 work for using KEXEC to have a hot kernel ready for doing a
123 So now the MMU is initialized in head.S but it's necessary to
124 use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
125 xt-gdb can't place a Software Breakpoint in the 0XD region prior
126 to mapping the MMU and after mapping even if the area of low memory
127 was mapped gdb wouldn't remove the breakpoint on hitting it as the
128 PC wouldn't match. Since Hardware Breakpoints are recommended for
129 Linux configurations it seems reasonable to just assume they exist
130 and leave this older mechanism for unfortunate souls that choose
131 not to follow Tensilica's recommendation.
133 Selecting this will cause U-Boot to set the KERNEL Load and Entry
134 address at 0x00003000 instead of the mapped std of 0xD0003000.
140 config XTENSA_CALIBRATE_CCOUNT
143 On some platforms (XT2000, for example), the CPU clock rate can
144 vary. The frequency can be determined, however, by measuring
145 against a well known, fixed frequency, such as an UART oscillator.
147 config SERIAL_CONSOLE
150 config XTENSA_ISS_NETWORK
159 Find out whether you have a PCI motherboard. PCI is the name of a
160 bus system, i.e. the way the CPU talks to the other stuff inside
161 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
162 VESA. If you have PCI, say Y, otherwise N.
164 source "drivers/pci/Kconfig"
168 menu "Platform options"
171 prompt "Xtensa System Type"
172 default XTENSA_PLATFORM_ISS
174 config XTENSA_PLATFORM_ISS
177 select XTENSA_CALIBRATE_CCOUNT
178 select SERIAL_CONSOLE
179 select XTENSA_ISS_NETWORK
181 ISS is an acronym for Tensilica's Instruction Set Simulator.
183 config XTENSA_PLATFORM_XT2000
186 XT2000 is the name of Tensilica's feature-rich emulation platform.
187 This hardware is capable of running a full Linux distribution.
189 config XTENSA_PLATFORM_S6105
191 select SERIAL_CONSOLE
194 config XTENSA_PLATFORM_XTFPGA
196 select SERIAL_CONSOLE
198 select XTENSA_CALIBRATE_CCOUNT
200 XTFPGA is the name of Tensilica board family (LX60, LX110, LX200, ML605).
201 This hardware is capable of running a full Linux distribution.
206 config XTENSA_CPU_CLOCK
207 int "CPU clock rate [MHz]"
208 depends on !XTENSA_CALIBRATE_CCOUNT
211 config GENERIC_CALIBRATE_DELAY
212 bool "Auto calibration of the BogoMIPS value"
214 The BogoMIPS value can easily be derived from the CPU frequency.
217 bool "Default bootloader kernel arguments"
220 string "Initial kernel command string"
221 depends on CMDLINE_BOOL
222 default "console=ttyS0,38400 root=/dev/ram"
224 On some architectures (EBSA110 and CATS), there is currently no way
225 for the boot loader to pass arguments to the kernel. For these
226 architectures, you should supply some command-line options at build
227 time by entering them here. As a minimum, you should specify the
228 memory size and the root device (e.g., mem=64M root=/dev/nfs).
231 bool "Flattened Device Tree support"
233 select OF_EARLY_FLATTREE
235 Include support for flattened device tree machine descriptions.
238 string "DTB to build into the kernel image"
241 config BLK_DEV_SIMDISK
242 tristate "Host file-based simulated block device support"
244 depends on XTENSA_PLATFORM_ISS
246 Create block devices that map to files in the host file system.
247 Device binding to host file may be changed at runtime via proc
248 interface provided the device is not in use.
250 config BLK_DEV_SIMDISK_COUNT
251 int "Number of host file-based simulated block devices"
253 depends on BLK_DEV_SIMDISK
256 This is the default minimal number of created block devices.
257 Kernel/module parameter 'simdisk_count' may be used to change this
258 value at runtime. More file names (but no more than 10) may be
259 specified as parameters, simdisk_count grows accordingly.
261 config SIMDISK0_FILENAME
262 string "Host filename for the first simulated device"
263 depends on BLK_DEV_SIMDISK = y
266 Attach a first simdisk to a host file. Conventionally, this file
267 contains a root file system.
269 config SIMDISK1_FILENAME
270 string "Host filename for the second simulated device"
271 depends on BLK_DEV_SIMDISK = y && BLK_DEV_SIMDISK_COUNT != 1
274 Another simulated disk in a host file for a buildroot-independent
279 source "drivers/pcmcia/Kconfig"
281 source "drivers/pci/hotplug/Kconfig"
285 menu "Executable file formats"
287 source "fs/Kconfig.binfmt"
293 source "drivers/Kconfig"
297 source "arch/xtensa/Kconfig.debug"
299 source "security/Kconfig"
301 source "crypto/Kconfig"