Version:  2.0.40 2.2.26 2.4.37 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1 4.2 4.3 4.4 4.5

Linux/arch/xtensa/Kconfig

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

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us