xref: /linux/arch/xtensa/Kconfig (revision 40d1a07b333ef1f7fce11ee20b8f4281d1a75fb9)
1# SPDX-License-Identifier: GPL-2.0
2config ZONE_DMA
3	def_bool y
4
5config XTENSA
6	def_bool y
7	select ARCH_NO_COHERENT_DMA_MMAP if !MMU
8	select ARCH_WANT_FRAME_POINTERS
9	select ARCH_WANT_IPC_PARSE_VERSION
10	select BUILDTIME_EXTABLE_SORT
11	select CLONE_BACKWARDS
12	select COMMON_CLK
13	select GENERIC_ATOMIC64
14	select GENERIC_CLOCKEVENTS
15	select GENERIC_IRQ_SHOW
16	select GENERIC_PCI_IOMAP
17	select GENERIC_SCHED_CLOCK
18	select HAVE_CC_STACKPROTECTOR
19	select HAVE_DEBUG_KMEMLEAK
20	select HAVE_DMA_API_DEBUG
21	select HAVE_DMA_CONTIGUOUS
22	select HAVE_EXIT_THREAD
23	select HAVE_FUNCTION_TRACER
24	select HAVE_FUTEX_CMPXCHG if !MMU
25	select HAVE_HW_BREAKPOINT if PERF_EVENTS
26	select HAVE_IRQ_TIME_ACCOUNTING
27	select HAVE_MEMBLOCK
28	select HAVE_OPROFILE
29	select HAVE_PERF_EVENTS
30	select IRQ_DOMAIN
31	select MODULES_USE_ELF_RELA
32	select NO_BOOTMEM
33	select PERF_USE_VMALLOC
34	select VIRT_TO_BUS
35	help
36	  Xtensa processors are 32-bit RISC machines designed by Tensilica
37	  primarily for embedded systems.  These processors are both
38	  configurable and extensible.  The Linux port to the Xtensa
39	  architecture supports all processor configurations and extensions,
40	  with reasonable minimum requirements.  The Xtensa Linux project has
41	  a home page at <http://www.linux-xtensa.org/>.
42
43config RWSEM_XCHGADD_ALGORITHM
44	def_bool y
45
46config GENERIC_HWEIGHT
47	def_bool y
48
49config ARCH_HAS_ILOG2_U32
50	def_bool n
51
52config ARCH_HAS_ILOG2_U64
53	def_bool n
54
55config NO_IOPORT_MAP
56	def_bool n
57
58config HZ
59	int
60	default 100
61
62source "init/Kconfig"
63source "kernel/Kconfig.freezer"
64
65config LOCKDEP_SUPPORT
66	def_bool y
67
68config STACKTRACE_SUPPORT
69	def_bool y
70
71config TRACE_IRQFLAGS_SUPPORT
72	def_bool y
73
74config MMU
75	def_bool n
76
77config VARIANT_IRQ_SWITCH
78	def_bool n
79
80config HAVE_XTENSA_GPIO32
81	def_bool n
82
83menu "Processor type and features"
84
85choice
86	prompt "Xtensa Processor Configuration"
87	default XTENSA_VARIANT_FSF
88
89config XTENSA_VARIANT_FSF
90	bool "fsf - default (not generic) configuration"
91	select MMU
92
93config XTENSA_VARIANT_DC232B
94	bool "dc232b - Diamond 232L Standard Core Rev.B (LE)"
95	select MMU
96	select HAVE_XTENSA_GPIO32
97	help
98	  This variant refers to Tensilica's Diamond 232L Standard core Rev.B (LE).
99
100config XTENSA_VARIANT_DC233C
101	bool "dc233c - Diamond 233L Standard Core Rev.C (LE)"
102	select MMU
103	select HAVE_XTENSA_GPIO32
104	help
105	  This variant refers to Tensilica's Diamond 233L Standard core Rev.C (LE).
106
107config XTENSA_VARIANT_CUSTOM
108	bool "Custom Xtensa processor configuration"
109	select HAVE_XTENSA_GPIO32
110	help
111	  Select this variant to use a custom Xtensa processor configuration.
112	  You will be prompted for a processor variant CORENAME.
113endchoice
114
115config XTENSA_VARIANT_CUSTOM_NAME
116	string "Xtensa Processor Custom Core Variant Name"
117	depends on XTENSA_VARIANT_CUSTOM
118	help
119	  Provide the name of a custom Xtensa processor variant.
120	  This CORENAME selects arch/xtensa/variant/CORENAME.
121	  Dont forget you have to select MMU if you have one.
122
123config XTENSA_VARIANT_NAME
124	string
125	default "dc232b"			if XTENSA_VARIANT_DC232B
126	default "dc233c"			if XTENSA_VARIANT_DC233C
127	default "fsf"				if XTENSA_VARIANT_FSF
128	default XTENSA_VARIANT_CUSTOM_NAME	if XTENSA_VARIANT_CUSTOM
129
130config XTENSA_VARIANT_MMU
131	bool "Core variant has a Full MMU (TLB, Pages, Protection, etc)"
132	depends on XTENSA_VARIANT_CUSTOM
133	default y
134	select MMU
135	help
136	  Build a Conventional Kernel with full MMU support,
137	  ie: it supports a TLB with auto-loading, page protection.
138
139config XTENSA_VARIANT_HAVE_PERF_EVENTS
140	bool "Core variant has Performance Monitor Module"
141	depends on XTENSA_VARIANT_CUSTOM
142	default n
143	help
144	  Enable if core variant has Performance Monitor Module with
145	  External Registers Interface.
146
147	  If unsure, say N.
148
149config XTENSA_FAKE_NMI
150	bool "Treat PMM IRQ as NMI"
151	depends on XTENSA_VARIANT_HAVE_PERF_EVENTS
152	default n
153	help
154	  If PMM IRQ is the only IRQ at EXCM level it is safe to
155	  treat it as NMI, which improves accuracy of profiling.
156
157	  If there are other interrupts at or above PMM IRQ priority level
158	  but not above the EXCM level, PMM IRQ still may be treated as NMI,
159	  but only if these IRQs are not used. There will be a build warning
160	  saying that this is not safe, and a bugcheck if one of these IRQs
161	  actually fire.
162
163	  If unsure, say N.
164
165config XTENSA_UNALIGNED_USER
166	bool "Unaligned memory access in use space"
167	help
168	  The Xtensa architecture currently does not handle unaligned
169	  memory accesses in hardware but through an exception handler.
170	  Per default, unaligned memory accesses are disabled in user space.
171
172	  Say Y here to enable unaligned memory access in user space.
173
174source "kernel/Kconfig.preempt"
175
176config HAVE_SMP
177	bool "System Supports SMP (MX)"
178	depends on XTENSA_VARIANT_CUSTOM
179	select XTENSA_MX
180	help
181	  This option is use to indicate that the system-on-a-chip (SOC)
182	  supports Multiprocessing. Multiprocessor support implemented above
183	  the CPU core definition and currently needs to be selected manually.
184
185	  Multiprocessor support in implemented with external cache and
186	  interrupt controllers.
187
188	  The MX interrupt distributer adds Interprocessor Interrupts
189	  and causes the IRQ numbers to be increased by 4 for devices
190	  like the open cores ethernet driver and the serial interface.
191
192	  You still have to select "Enable SMP" to enable SMP on this SOC.
193
194config SMP
195	bool "Enable Symmetric multi-processing support"
196	depends on HAVE_SMP
197	select GENERIC_SMP_IDLE_THREAD
198	help
199	  Enabled SMP Software; allows more than one CPU/CORE
200	  to be activated during startup.
201
202config NR_CPUS
203	depends on SMP
204	int "Maximum number of CPUs (2-32)"
205	range 2 32
206	default "4"
207
208config HOTPLUG_CPU
209	bool "Enable CPU hotplug support"
210	depends on SMP
211	help
212	  Say Y here to allow turning CPUs off and on. CPUs can be
213	  controlled through /sys/devices/system/cpu.
214
215	  Say N if you want to disable CPU hotplug.
216
217config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
218	bool "Initialize Xtensa MMU inside the Linux kernel code"
219	depends on !XTENSA_VARIANT_FSF && !XTENSA_VARIANT_DC232B
220	default y if XTENSA_VARIANT_DC233C || XTENSA_VARIANT_CUSTOM
221	help
222	  Earlier version initialized the MMU in the exception vector
223	  before jumping to _startup in head.S and had an advantage that
224	  it was possible to place a software breakpoint at 'reset' and
225	  then enter your normal kernel breakpoints once the MMU was mapped
226	  to the kernel mappings (0XC0000000).
227
228	  This unfortunately doesn't work for U-Boot and likley also wont
229	  work for using KEXEC to have a hot kernel ready for doing a
230	  KDUMP.
231
232	  So now the MMU is initialized in head.S but it's necessary to
233	  use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
234	  xt-gdb can't place a Software Breakpoint in the  0XD region prior
235	  to mapping the MMU and after mapping even if the area of low memory
236	  was mapped gdb wouldn't remove the breakpoint on hitting it as the
237	  PC wouldn't match. Since Hardware Breakpoints are recommended for
238	  Linux configurations it seems reasonable to just assume they exist
239	  and leave this older mechanism for unfortunate souls that choose
240	  not to follow Tensilica's recommendation.
241
242	  Selecting this will cause U-Boot to set the KERNEL Load and Entry
243	  address at 0x00003000 instead of the mapped std of 0xD0003000.
244
245	  If in doubt, say Y.
246
247config KSEG_PADDR
248	hex "Physical address of the KSEG mapping"
249	depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX && MMU
250	default 0x00000000
251	help
252	  This is the physical address where KSEG is mapped. Please refer to
253	  the chosen KSEG layout help for the required address alignment.
254	  Unpacked kernel image (including vectors) must be located completely
255	  within KSEG.
256	  Physical memory below this address is not available to linux.
257
258	  If unsure, leave the default value here.
259
260config KERNEL_LOAD_ADDRESS
261	hex "Kernel load address"
262	default 0x60003000 if !MMU
263	default 0x00003000 if MMU && INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
264	default 0xd0003000 if MMU && !INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
265	help
266	  This is the address where the kernel is loaded.
267	  It is virtual address for MMUv2 configurations and physical address
268	  for all other configurations.
269
270	  If unsure, leave the default value here.
271
272config VECTORS_OFFSET
273	hex "Kernel vectors offset"
274	default 0x00003000
275	help
276	  This is the offset of the kernel image from the relocatable vectors
277	  base.
278
279	  If unsure, leave the default value here.
280
281choice
282	prompt "KSEG layout"
283	depends on MMU
284	default XTENSA_KSEG_MMU_V2
285
286config XTENSA_KSEG_MMU_V2
287	bool "MMUv2: 128MB cached + 128MB uncached"
288	help
289	  MMUv2 compatible kernel memory map: TLB way 5 maps 128MB starting
290	  at KSEG_PADDR to 0xd0000000 with cache and to 0xd8000000
291	  without cache.
292	  KSEG_PADDR must be aligned to 128MB.
293
294config XTENSA_KSEG_256M
295	bool "256MB cached + 256MB uncached"
296	depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
297	help
298	  TLB way 6 maps 256MB starting at KSEG_PADDR to 0xb0000000
299	  with cache and to 0xc0000000 without cache.
300	  KSEG_PADDR must be aligned to 256MB.
301
302config XTENSA_KSEG_512M
303	bool "512MB cached + 512MB uncached"
304	depends on INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
305	help
306	  TLB way 6 maps 512MB starting at KSEG_PADDR to 0xa0000000
307	  with cache and to 0xc0000000 without cache.
308	  KSEG_PADDR must be aligned to 256MB.
309
310endchoice
311
312config HIGHMEM
313	bool "High Memory Support"
314	depends on MMU
315	help
316	  Linux can use the full amount of RAM in the system by
317	  default. However, the default MMUv2 setup only maps the
318	  lowermost 128 MB of memory linearly to the areas starting
319	  at 0xd0000000 (cached) and 0xd8000000 (uncached).
320	  When there are more than 128 MB memory in the system not
321	  all of it can be "permanently mapped" by the kernel.
322	  The physical memory that's not permanently mapped is called
323	  "high memory".
324
325	  If you are compiling a kernel which will never run on a
326	  machine with more than 128 MB total physical RAM, answer
327	  N here.
328
329	  If unsure, say Y.
330
331config FAST_SYSCALL_XTENSA
332	bool "Enable fast atomic syscalls"
333	default n
334	help
335	  fast_syscall_xtensa is a syscall that can make atomic operations
336	  on UP kernel when processor has no s32c1i support.
337
338	  This syscall is deprecated. It may have issues when called with
339	  invalid arguments. It is provided only for backwards compatibility.
340	  Only enable it if your userspace software requires it.
341
342	  If unsure, say N.
343
344config FAST_SYSCALL_SPILL_REGISTERS
345	bool "Enable spill registers syscall"
346	default n
347	help
348	  fast_syscall_spill_registers is a syscall that spills all active
349	  register windows of a calling userspace task onto its stack.
350
351	  This syscall is deprecated. It may have issues when called with
352	  invalid arguments. It is provided only for backwards compatibility.
353	  Only enable it if your userspace software requires it.
354
355	  If unsure, say N.
356
357endmenu
358
359config XTENSA_CALIBRATE_CCOUNT
360	def_bool n
361	help
362	  On some platforms (XT2000, for example), the CPU clock rate can
363	  vary.  The frequency can be determined, however, by measuring
364	  against a well known, fixed frequency, such as an UART oscillator.
365
366config SERIAL_CONSOLE
367	def_bool n
368
369menu "Bus options"
370
371config PCI
372	bool "PCI support"
373	default y
374	help
375	  Find out whether you have a PCI motherboard. PCI is the name of a
376	  bus system, i.e. the way the CPU talks to the other stuff inside
377	  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
378	  VESA. If you have PCI, say Y, otherwise N.
379
380source "drivers/pci/Kconfig"
381
382endmenu
383
384menu "Platform options"
385
386choice
387	prompt "Xtensa System Type"
388	default XTENSA_PLATFORM_ISS
389
390config XTENSA_PLATFORM_ISS
391	bool "ISS"
392	select XTENSA_CALIBRATE_CCOUNT
393	select SERIAL_CONSOLE
394	help
395	  ISS is an acronym for Tensilica's Instruction Set Simulator.
396
397config XTENSA_PLATFORM_XT2000
398	bool "XT2000"
399	select HAVE_IDE
400	help
401	  XT2000 is the name of Tensilica's feature-rich emulation platform.
402	  This hardware is capable of running a full Linux distribution.
403
404config XTENSA_PLATFORM_XTFPGA
405	bool "XTFPGA"
406	select ETHOC if ETHERNET
407	select PLATFORM_WANT_DEFAULT_MEM if !MMU
408	select SERIAL_CONSOLE
409	select XTENSA_CALIBRATE_CCOUNT
410	help
411	  XTFPGA is the name of Tensilica board family (LX60, LX110, LX200, ML605).
412	  This hardware is capable of running a full Linux distribution.
413
414endchoice
415
416
417config XTENSA_CPU_CLOCK
418	int "CPU clock rate [MHz]"
419	depends on !XTENSA_CALIBRATE_CCOUNT
420	default 16
421
422config GENERIC_CALIBRATE_DELAY
423	bool "Auto calibration of the BogoMIPS value"
424	help
425	  The BogoMIPS value can easily be derived from the CPU frequency.
426
427config CMDLINE_BOOL
428	bool "Default bootloader kernel arguments"
429
430config CMDLINE
431	string "Initial kernel command string"
432	depends on CMDLINE_BOOL
433	default "console=ttyS0,38400 root=/dev/ram"
434	help
435	  On some architectures (EBSA110 and CATS), there is currently no way
436	  for the boot loader to pass arguments to the kernel. For these
437	  architectures, you should supply some command-line options at build
438	  time by entering them here. As a minimum, you should specify the
439	  memory size and the root device (e.g., mem=64M root=/dev/nfs).
440
441config USE_OF
442	bool "Flattened Device Tree support"
443	select OF
444	select OF_EARLY_FLATTREE
445	select OF_RESERVED_MEM
446	help
447	  Include support for flattened device tree machine descriptions.
448
449config BUILTIN_DTB
450	string "DTB to build into the kernel image"
451	depends on OF
452
453config BLK_DEV_SIMDISK
454	tristate "Host file-based simulated block device support"
455	default n
456	depends on XTENSA_PLATFORM_ISS && BLOCK
457	help
458	  Create block devices that map to files in the host file system.
459	  Device binding to host file may be changed at runtime via proc
460	  interface provided the device is not in use.
461
462config BLK_DEV_SIMDISK_COUNT
463	int "Number of host file-based simulated block devices"
464	range 1 10
465	depends on BLK_DEV_SIMDISK
466	default 2
467	help
468	  This is the default minimal number of created block devices.
469	  Kernel/module parameter 'simdisk_count' may be used to change this
470	  value at runtime. More file names (but no more than 10) may be
471	  specified as parameters, simdisk_count grows accordingly.
472
473config SIMDISK0_FILENAME
474	string "Host filename for the first simulated device"
475	depends on BLK_DEV_SIMDISK = y
476	default ""
477	help
478	  Attach a first simdisk to a host file. Conventionally, this file
479	  contains a root file system.
480
481config SIMDISK1_FILENAME
482	string "Host filename for the second simulated device"
483	depends on BLK_DEV_SIMDISK = y && BLK_DEV_SIMDISK_COUNT != 1
484	default ""
485	help
486	  Another simulated disk in a host file for a buildroot-independent
487	  storage.
488
489source "mm/Kconfig"
490
491config FORCE_MAX_ZONEORDER
492	int "Maximum zone order"
493	default "11"
494	help
495	  The kernel memory allocator divides physically contiguous memory
496	  blocks into "zones", where each zone is a power of two number of
497	  pages.  This option selects the largest power of two that the kernel
498	  keeps in the memory allocator.  If you need to allocate very large
499	  blocks of physically contiguous memory, then you may need to
500	  increase this value.
501
502	  This config option is actually maximum order plus one. For example,
503	  a value of 11 means that the largest free memory block is 2^10 pages.
504
505source "drivers/pcmcia/Kconfig"
506
507config PLATFORM_WANT_DEFAULT_MEM
508	def_bool n
509
510config DEFAULT_MEM_START
511	hex "Physical address of the default memory area start"
512	depends on PLATFORM_WANT_DEFAULT_MEM
513	default 0x00000000 if MMU
514	default 0x60000000 if !MMU
515	help
516	  This is the base address of the default memory area.
517	  Default memory area has platform-specific meaning, it may be used
518	  for e.g. early cache initialization.
519
520	  If unsure, leave the default value here.
521
522config DEFAULT_MEM_SIZE
523	hex "Maximal size of the default memory area"
524	depends on PLATFORM_WANT_DEFAULT_MEM
525	default 0x04000000
526	help
527	  This is the size of the default memory area.
528	  Default memory area has platform-specific meaning, it may be used
529	  for e.g. early cache initialization.
530
531	  If unsure, leave the default value here.
532
533config XTFPGA_LCD
534	bool "Enable XTFPGA LCD driver"
535	depends on XTENSA_PLATFORM_XTFPGA
536	default n
537	help
538	  There's a 2x16 LCD on most of XTFPGA boards, kernel may output
539	  progress messages there during bootup/shutdown. It may be useful
540	  during board bringup.
541
542	  If unsure, say N.
543
544config XTFPGA_LCD_BASE_ADDR
545	hex "XTFPGA LCD base address"
546	depends on XTFPGA_LCD
547	default "0x0d0c0000"
548	help
549	  Base address of the LCD controller inside KIO region.
550	  Different boards from XTFPGA family have LCD controller at different
551	  addresses. Please consult prototyping user guide for your board for
552	  the correct address. Wrong address here may lead to hardware lockup.
553
554config XTFPGA_LCD_8BIT_ACCESS
555	bool "Use 8-bit access to XTFPGA LCD"
556	depends on XTFPGA_LCD
557	default n
558	help
559	  LCD may be connected with 4- or 8-bit interface, 8-bit access may
560	  only be used with 8-bit interface. Please consult prototyping user
561	  guide for your board for the correct interface width.
562
563endmenu
564
565menu "Executable file formats"
566
567source "fs/Kconfig.binfmt"
568
569endmenu
570
571menu "Power management options"
572
573source "kernel/power/Kconfig"
574
575endmenu
576
577source "net/Kconfig"
578
579source "drivers/Kconfig"
580
581source "fs/Kconfig"
582
583source "arch/xtensa/Kconfig.debug"
584
585source "security/Kconfig"
586
587source "crypto/Kconfig"
588
589source "lib/Kconfig"
590
591
592