Merge tag 'sunxi-late-for-4.2' of https://git.kernel.org/pub/scm/linux/kernel/git...
[deliverable/linux.git] / arch / xtensa / Kconfig
CommitLineData
66701b14 1config ZONE_DMA
35f9cd08 2 def_bool y
66701b14 3
8e1a6dd2 4config XTENSA
35f9cd08 5 def_bool y
8f371c75 6 select ARCH_WANT_FRAME_POINTERS
e969161b 7 select ARCH_WANT_IPC_PARSE_VERSION
6ed65f37 8 select ARCH_WANT_OPTIONAL_GPIOLIB
25df8198 9 select BUILDTIME_EXTABLE_SORT
3e41f9ba 10 select CLONE_BACKWARDS
920f8a39
MF
11 select COMMON_CLK
12 select GENERIC_ATOMIC64
13 select GENERIC_CLOCKEVENTS
14 select GENERIC_IRQ_SHOW
15 select GENERIC_PCI_IOMAP
16 select GENERIC_SCHED_CLOCK
478ba61a 17 select HAVE_FUNCTION_TRACER
496543c4 18 select HAVE_IRQ_TIME_ACCOUNTING
920f8a39 19 select HAVE_OPROFILE
a6f3eefa 20 select HAVE_PERF_EVENTS
920f8a39
MF
21 select IRQ_DOMAIN
22 select MODULES_USE_ELF_RELA
23 select VIRT_TO_BUS
8e1a6dd2
CZ
24 help
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
0ada4490 30 a home page at <http://www.linux-xtensa.org/>.
8e1a6dd2 31
8e1a6dd2 32config RWSEM_XCHGADD_ALGORITHM
35f9cd08 33 def_bool y
8e1a6dd2 34
d4337aa5 35config GENERIC_HWEIGHT
35f9cd08 36 def_bool y
d4337aa5 37
f0d1b0b3 38config ARCH_HAS_ILOG2_U32
35f9cd08 39 def_bool n
f0d1b0b3
DH
40
41config ARCH_HAS_ILOG2_U64
35f9cd08 42 def_bool n
f0d1b0b3 43
ce816fa8 44config NO_IOPORT_MAP
d046f77e 45 def_bool n
5ea81769 46
bdc80787
PA
47config HZ
48 int
49 default 100
50
8e1a6dd2 51source "init/Kconfig"
dc52ddc0 52source "kernel/Kconfig.freezer"
8e1a6dd2 53
8f371c75
MF
54config LOCKDEP_SUPPORT
55 def_bool y
56
3e4196a5
MF
57config STACKTRACE_SUPPORT
58 def_bool y
59
c92931b2
MF
60config TRACE_IRQFLAGS_SUPPORT
61 def_bool y
62
35f9cd08 63config MMU
420ae951
MF
64 bool
65 default n if !XTENSA_VARIANT_CUSTOM
66 default XTENSA_VARIANT_MMU if XTENSA_VARIANT_CUSTOM
35f9cd08 67
4c0d2141
JW
68config VARIANT_IRQ_SWITCH
69 def_bool n
70
a1a2bdec
BS
71config HAVE_XTENSA_GPIO32
72 def_bool n
73
f615136c
MF
74config MAY_HAVE_SMP
75 def_bool n
76
8e1a6dd2
CZ
77menu "Processor type and features"
78
79choice
80 prompt "Xtensa Processor Configuration"
173d6681 81 default XTENSA_VARIANT_FSF
8e1a6dd2 82
173d6681 83config XTENSA_VARIANT_FSF
0025427e 84 bool "fsf - default (not generic) configuration"
35f9cd08 85 select MMU
0025427e
CZ
86
87config XTENSA_VARIANT_DC232B
88 bool "dc232b - Diamond 232L Standard Core Rev.B (LE)"
35f9cd08 89 select MMU
a1a2bdec 90 select HAVE_XTENSA_GPIO32
0025427e 91 help
35f9cd08 92 This variant refers to Tensilica's Diamond 232L Standard core Rev.B (LE).
000af2c5 93
d0b73b48
PD
94config XTENSA_VARIANT_DC233C
95 bool "dc233c - Diamond 233L Standard Core Rev.C (LE)"
96 select MMU
a1a2bdec 97 select HAVE_XTENSA_GPIO32
d0b73b48
PD
98 help
99 This variant refers to Tensilica's Diamond 233L Standard core Rev.C (LE).
100
420ae951
MF
101config XTENSA_VARIANT_CUSTOM
102 bool "Custom Xtensa processor configuration"
103 select MAY_HAVE_SMP
104 select HAVE_XTENSA_GPIO32
105 help
106 Select this variant to use a custom Xtensa processor configuration.
107 You will be prompted for a processor variant CORENAME.
8e1a6dd2
CZ
108endchoice
109
420ae951
MF
110config XTENSA_VARIANT_CUSTOM_NAME
111 string "Xtensa Processor Custom Core Variant Name"
112 depends on XTENSA_VARIANT_CUSTOM
113 help
114 Provide the name of a custom Xtensa processor variant.
115 This CORENAME selects arch/xtensa/variant/CORENAME.
116 Dont forget you have to select MMU if you have one.
117
118config XTENSA_VARIANT_NAME
119 string
120 default "dc232b" if XTENSA_VARIANT_DC232B
121 default "dc233c" if XTENSA_VARIANT_DC233C
122 default "fsf" if XTENSA_VARIANT_FSF
420ae951
MF
123 default XTENSA_VARIANT_CUSTOM_NAME if XTENSA_VARIANT_CUSTOM
124
125config XTENSA_VARIANT_MMU
126 bool "Core variant has a Full MMU (TLB, Pages, Protection, etc)"
127 depends on XTENSA_VARIANT_CUSTOM
128 default y
129 help
130 Build a Conventional Kernel with full MMU support,
131 ie: it supports a TLB with auto-loading, page protection.
132
8e1a6dd2
CZ
133config XTENSA_UNALIGNED_USER
134 bool "Unaligned memory access in use space"
35f9cd08
JW
135 help
136 The Xtensa architecture currently does not handle unaligned
137 memory accesses in hardware but through an exception handler.
138 Per default, unaligned memory accesses are disabled in user space.
8e1a6dd2 139
35f9cd08 140 Say Y here to enable unaligned memory access in user space.
8e1a6dd2 141
bd96efe1 142source "kernel/Kconfig.preempt"
8e1a6dd2 143
f615136c
MF
144config HAVE_SMP
145 bool "System Supports SMP (MX)"
146 depends on MAY_HAVE_SMP
147 select XTENSA_MX
148 help
149 This option is use to indicate that the system-on-a-chip (SOC)
150 supports Multiprocessing. Multiprocessor support implemented above
151 the CPU core definition and currently needs to be selected manually.
152
153 Multiprocessor support in implemented with external cache and
769a12a9 154 interrupt controllers.
f615136c
MF
155
156 The MX interrupt distributer adds Interprocessor Interrupts
157 and causes the IRQ numbers to be increased by 4 for devices
158 like the open cores ethernet driver and the serial interface.
159
160 You still have to select "Enable SMP" to enable SMP on this SOC.
161
162config SMP
163 bool "Enable Symmetric multi-processing support"
164 depends on HAVE_SMP
f615136c
MF
165 select GENERIC_SMP_IDLE_THREAD
166 help
167 Enabled SMP Software; allows more than one CPU/CORE
168 to be activated during startup.
169
170config NR_CPUS
171 depends on SMP
172 int "Maximum number of CPUs (2-32)"
173 range 2 32
174 default "4"
175
49b424fe
MF
176config HOTPLUG_CPU
177 bool "Enable CPU hotplug support"
178 depends on SMP
179 help
180 Say Y here to allow turning CPUs off and on. CPUs can be
181 controlled through /sys/devices/system/cpu.
182
183 Say N if you want to disable CPU hotplug.
184
e85e335f
MF
185config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
186 bool "Initialize Xtensa MMU inside the Linux kernel code"
187 default y
188 help
189 Earlier version initialized the MMU in the exception vector
190 before jumping to _startup in head.S and had an advantage that
191 it was possible to place a software breakpoint at 'reset' and
192 then enter your normal kernel breakpoints once the MMU was mapped
193 to the kernel mappings (0XC0000000).
194
195 This unfortunately doesn't work for U-Boot and likley also wont
196 work for using KEXEC to have a hot kernel ready for doing a
197 KDUMP.
198
199 So now the MMU is initialized in head.S but it's necessary to
200 use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
201 xt-gdb can't place a Software Breakpoint in the 0XD region prior
202 to mapping the MMU and after mapping even if the area of low memory
203 was mapped gdb wouldn't remove the breakpoint on hitting it as the
204 PC wouldn't match. Since Hardware Breakpoints are recommended for
205 Linux configurations it seems reasonable to just assume they exist
206 and leave this older mechanism for unfortunate souls that choose
207 not to follow Tensilica's recommendation.
208
209 Selecting this will cause U-Boot to set the KERNEL Load and Entry
210 address at 0x00003000 instead of the mapped std of 0xD0003000.
211
212 If in doubt, say Y.
213
65559100
MF
214config HIGHMEM
215 bool "High Memory Support"
8a9de059 216 depends on MMU
65559100
MF
217 help
218 Linux can use the full amount of RAM in the system by
219 default. However, the default MMUv2 setup only maps the
220 lowermost 128 MB of memory linearly to the areas starting
221 at 0xd0000000 (cached) and 0xd8000000 (uncached).
222 When there are more than 128 MB memory in the system not
223 all of it can be "permanently mapped" by the kernel.
224 The physical memory that's not permanently mapped is called
225 "high memory".
226
227 If you are compiling a kernel which will never run on a
228 machine with more than 128 MB total physical RAM, answer
229 N here.
230
231 If unsure, say Y.
232
9184289c
MF
233config FAST_SYSCALL_XTENSA
234 bool "Enable fast atomic syscalls"
235 default n
236 help
237 fast_syscall_xtensa is a syscall that can make atomic operations
238 on UP kernel when processor has no s32c1i support.
239
240 This syscall is deprecated. It may have issues when called with
241 invalid arguments. It is provided only for backwards compatibility.
242 Only enable it if your userspace software requires it.
243
244 If unsure, say N.
245
246config FAST_SYSCALL_SPILL_REGISTERS
247 bool "Enable spill registers syscall"
248 default n
249 help
250 fast_syscall_spill_registers is a syscall that spills all active
251 register windows of a calling userspace task onto its stack.
252
253 This syscall is deprecated. It may have issues when called with
254 invalid arguments. It is provided only for backwards compatibility.
255 Only enable it if your userspace software requires it.
256
257 If unsure, say N.
258
8e1a6dd2
CZ
259endmenu
260
35f9cd08
JW
261config XTENSA_CALIBRATE_CCOUNT
262 def_bool n
263 help
264 On some platforms (XT2000, for example), the CPU clock rate can
265 vary. The frequency can be determined, however, by measuring
266 against a well known, fixed frequency, such as an UART oscillator.
267
268config SERIAL_CONSOLE
269 def_bool n
270
35f9cd08
JW
271menu "Bus options"
272
273config PCI
274 bool "PCI support"
275 default y
276 help
277 Find out whether you have a PCI motherboard. PCI is the name of a
278 bus system, i.e. the way the CPU talks to the other stuff inside
279 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
280 VESA. If you have PCI, say Y, otherwise N.
281
282source "drivers/pci/Kconfig"
283
35e71f90
CZ
284endmenu
285
8e1a6dd2
CZ
286menu "Platform options"
287
288choice
289 prompt "Xtensa System Type"
290 default XTENSA_PLATFORM_ISS
291
292config XTENSA_PLATFORM_ISS
293 bool "ISS"
35f9cd08
JW
294 select XTENSA_CALIBRATE_CCOUNT
295 select SERIAL_CONSOLE
8e1a6dd2
CZ
296 help
297 ISS is an acronym for Tensilica's Instruction Set Simulator.
298
299config XTENSA_PLATFORM_XT2000
300 bool "XT2000"
4964527d 301 select HAVE_IDE
8e1a6dd2
CZ
302 help
303 XT2000 is the name of Tensilica's feature-rich emulation platform.
304 This hardware is capable of running a full Linux distribution.
305
0d456bad
MF
306config XTENSA_PLATFORM_XTFPGA
307 bool "XTFPGA"
61e47e9b 308 select ETHOC if ETHERNET
3932b9ca 309 select PLATFORM_WANT_DEFAULT_MEM
0d456bad 310 select SERIAL_CONSOLE
0d456bad
MF
311 select XTENSA_CALIBRATE_CCOUNT
312 help
313 XTFPGA is the name of Tensilica board family (LX60, LX110, LX200, ML605).
314 This hardware is capable of running a full Linux distribution.
315
8e1a6dd2
CZ
316endchoice
317
318
8e1a6dd2
CZ
319config XTENSA_CPU_CLOCK
320 int "CPU clock rate [MHz]"
321 depends on !XTENSA_CALIBRATE_CCOUNT
35f9cd08 322 default 16
8e1a6dd2
CZ
323
324config GENERIC_CALIBRATE_DELAY
325 bool "Auto calibration of the BogoMIPS value"
35f9cd08 326 help
82300bf4 327 The BogoMIPS value can easily be derived from the CPU frequency.
8e1a6dd2
CZ
328
329config CMDLINE_BOOL
330 bool "Default bootloader kernel arguments"
331
332config CMDLINE
333 string "Initial kernel command string"
334 depends on CMDLINE_BOOL
335 default "console=ttyS0,38400 root=/dev/ram"
336 help
337 On some architectures (EBSA110 and CATS), there is currently no way
338 for the boot loader to pass arguments to the kernel. For these
339 architectures, you should supply some command-line options at build
340 time by entering them here. As a minimum, you should specify the
341 memory size and the root device (e.g., mem=64M root=/dev/nfs).
342
da844a81
MF
343config USE_OF
344 bool "Flattened Device Tree support"
345 select OF
346 select OF_EARLY_FLATTREE
347 help
348 Include support for flattened device tree machine descriptions.
349
350config BUILTIN_DTB
351 string "DTB to build into the kernel image"
352 depends on OF
353
b6c7e873
VP
354config BLK_DEV_SIMDISK
355 tristate "Host file-based simulated block device support"
356 default n
7a0684cd 357 depends on XTENSA_PLATFORM_ISS && BLOCK
b6c7e873
VP
358 help
359 Create block devices that map to files in the host file system.
360 Device binding to host file may be changed at runtime via proc
361 interface provided the device is not in use.
362
363config BLK_DEV_SIMDISK_COUNT
364 int "Number of host file-based simulated block devices"
365 range 1 10
366 depends on BLK_DEV_SIMDISK
367 default 2
368 help
369 This is the default minimal number of created block devices.
370 Kernel/module parameter 'simdisk_count' may be used to change this
371 value at runtime. More file names (but no more than 10) may be
372 specified as parameters, simdisk_count grows accordingly.
373
374config SIMDISK0_FILENAME
375 string "Host filename for the first simulated device"
376 depends on BLK_DEV_SIMDISK = y
377 default ""
378 help
379 Attach a first simdisk to a host file. Conventionally, this file
380 contains a root file system.
381
382config SIMDISK1_FILENAME
383 string "Host filename for the second simulated device"
384 depends on BLK_DEV_SIMDISK = y && BLK_DEV_SIMDISK_COUNT != 1
385 default ""
386 help
387 Another simulated disk in a host file for a buildroot-independent
388 storage.
389
82300bf4
CZ
390source "mm/Kconfig"
391
8e1a6dd2
CZ
392source "drivers/pcmcia/Kconfig"
393
394source "drivers/pci/hotplug/Kconfig"
395
3932b9ca
MF
396config PLATFORM_WANT_DEFAULT_MEM
397 def_bool n
398
399config DEFAULT_MEM_START
400 hex "Physical address of the default memory area start"
401 depends on PLATFORM_WANT_DEFAULT_MEM
402 default 0x00000000 if MMU
403 default 0x40000000 if !MMU
404 help
405 This is a fallback start address of the default memory area, it is
406 used when no physical memory size is passed through DTB or through
407 boot parameter from bootloader.
408
409 In noMMU configuration the following parameters are derived from it:
410 - kernel load address;
411 - kernel entry point address;
412 - relocatable vectors base address;
413 - uBoot load address;
414 - TASK_SIZE.
415
416 If unsure, leave the default value here.
417
418config DEFAULT_MEM_SIZE
419 hex "Maximal size of the default memory area"
420 depends on PLATFORM_WANT_DEFAULT_MEM
421 default 0x04000000
422 help
423 This is a fallback size of the default memory area, it is used when
424 no physical memory size is passed through DTB or through boot
425 parameter from bootloader.
426
427 It's also used for TASK_SIZE calculation in noMMU configuration.
428
429 If unsure, leave the default value here.
430
4949009e
MF
431config XTFPGA_LCD
432 bool "Enable XTFPGA LCD driver"
433 depends on XTENSA_PLATFORM_XTFPGA
434 default n
435 help
436 There's a 2x16 LCD on most of XTFPGA boards, kernel may output
437 progress messages there during bootup/shutdown. It may be useful
438 during board bringup.
439
440 If unsure, say N.
441
442config XTFPGA_LCD_BASE_ADDR
443 hex "XTFPGA LCD base address"
444 depends on XTFPGA_LCD
445 default "0x0d0c0000"
446 help
447 Base address of the LCD controller inside KIO region.
448 Different boards from XTFPGA family have LCD controller at different
449 addresses. Please consult prototyping user guide for your board for
450 the correct address. Wrong address here may lead to hardware lockup.
451
452config XTFPGA_LCD_8BIT_ACCESS
453 bool "Use 8-bit access to XTFPGA LCD"
454 depends on XTFPGA_LCD
455 default n
456 help
457 LCD may be connected with 4- or 8-bit interface, 8-bit access may
458 only be used with 8-bit interface. Please consult prototyping user
459 guide for your board for the correct interface width.
460
8e1a6dd2
CZ
461endmenu
462
cab00891 463menu "Executable file formats"
8e1a6dd2 464
8e1a6dd2
CZ
465source "fs/Kconfig.binfmt"
466
467endmenu
468
e00d8b2f
MF
469menu "Power management options"
470
471source "kernel/power/Kconfig"
472
473endmenu
474
d5950b43
SR
475source "net/Kconfig"
476
8e1a6dd2
CZ
477source "drivers/Kconfig"
478
479source "fs/Kconfig"
480
8e1a6dd2
CZ
481source "arch/xtensa/Kconfig.debug"
482
483source "security/Kconfig"
484
485source "crypto/Kconfig"
486
487source "lib/Kconfig"
488
489
This page took 0.698627 seconds and 5 git commands to generate.