5 select HAVE_DMA_API_DEBUG
6 select HAVE_IDE if PCI || ISA || PCMCIA
9 select SYS_SUPPORTS_APM_EMULATION
10 select GENERIC_ATOMIC64 if (CPU_V6 || !CPU_32v6K || !AEABI)
11 select HAVE_OPROFILE if (HAVE_PERF_EVENTS)
13 select HAVE_KPROBES if !XIP_KERNEL
14 select HAVE_KRETPROBES if (HAVE_KPROBES)
15 select HAVE_FUNCTION_TRACER if (!XIP_KERNEL)
16 select HAVE_FTRACE_MCOUNT_RECORD if (!XIP_KERNEL)
17 select HAVE_DYNAMIC_FTRACE if (!XIP_KERNEL)
18 select HAVE_FUNCTION_GRAPH_TRACER if (!THUMB2_KERNEL)
19 select HAVE_GENERIC_DMA_COHERENT
20 select HAVE_KERNEL_GZIP
21 select HAVE_KERNEL_LZO
22 select HAVE_KERNEL_LZMA
24 select HAVE_PERF_EVENTS
25 select PERF_USE_VMALLOC
26 select HAVE_REGS_AND_STACK_ACCESS_API
27 select HAVE_HW_BREAKPOINT if (PERF_EVENTS && (CPU_V6 || CPU_V6K || CPU_V7))
28 select HAVE_C_RECORDMCOUNT
29 select HAVE_GENERIC_HARDIRQS
30 select HAVE_SPARSE_IRQ
31 select GENERIC_IRQ_SHOW
32 select CPU_PM if (SUSPEND || CPU_IDLE)
34 The ARM series is a line of low-power-consumption RISC chip designs
35 licensed by ARM Ltd and targeted at embedded applications and
36 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
37 manufactured, but legacy ARM-based PC hardware remains popular in
38 Europe. There is an ARM Linux project with a web page at
39 <http://www.arm.linux.org.uk/>.
41 config ARM_HAS_SG_CHAIN
50 config SYS_SUPPORTS_APM_EMULATION
53 config HAVE_SCHED_CLOCK
59 config ARCH_USES_GETTIMEOFFSET
63 config GENERIC_CLOCKEVENTS
66 config GENERIC_CLOCKEVENTS_BROADCAST
68 depends on GENERIC_CLOCKEVENTS
77 select GENERIC_ALLOCATOR
88 The Extended Industry Standard Architecture (EISA) bus was
89 developed as an open alternative to the IBM MicroChannel bus.
91 The EISA bus provided some of the features of the IBM MicroChannel
92 bus while maintaining backward compatibility with cards made for
93 the older ISA bus. The EISA bus saw limited use between 1988 and
94 1995 when it was made obsolete by the PCI bus.
96 Say Y here if you are building a kernel for an EISA-based machine.
106 MicroChannel Architecture is found in some IBM PS/2 machines and
107 laptops. It is a bus system similar to PCI or ISA. See
108 <file:Documentation/mca.txt> (and especially the web page given
109 there) before attempting to build an MCA bus kernel.
111 config STACKTRACE_SUPPORT
115 config HAVE_LATENCYTOP_SUPPORT
120 config LOCKDEP_SUPPORT
124 config TRACE_IRQFLAGS_SUPPORT
128 config HARDIRQS_SW_RESEND
132 config GENERIC_IRQ_PROBE
136 config GENERIC_LOCKBREAK
139 depends on SMP && PREEMPT
141 config RWSEM_GENERIC_SPINLOCK
145 config RWSEM_XCHGADD_ALGORITHM
148 config ARCH_HAS_ILOG2_U32
151 config ARCH_HAS_ILOG2_U64
154 config ARCH_HAS_CPUFREQ
157 Internal node to signify that the ARCH has CPUFREQ support
158 and that the relevant menu configurations are displayed for
161 config ARCH_HAS_CPU_IDLE_WAIT
164 config GENERIC_HWEIGHT
168 config GENERIC_CALIBRATE_DELAY
172 config ARCH_MAY_HAVE_PC_FDC
178 config NEED_DMA_MAP_STATE
181 config GENERIC_ISA_DMA
192 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
193 default DRAM_BASE if REMAP_VECTORS_TO_RAM
196 The base address of exception vectors.
198 config ARM_PATCH_PHYS_VIRT
199 bool "Patch physical to virtual translations at runtime" if EMBEDDED
201 depends on !XIP_KERNEL && MMU
202 depends on !ARCH_REALVIEW || !SPARSEMEM
204 Patch phys-to-virt and virt-to-phys translation functions at
205 boot and module load time according to the position of the
206 kernel in system memory.
208 This can only be used with non-XIP MMU kernels where the base
209 of physical memory is at a 16MB boundary.
211 Only disable this option if you know that you do not require
212 this feature (eg, building a kernel for a single machine) and
213 you need to shrink the kernel to the minimal size.
215 config NEED_MACH_MEMORY_H
218 Select this when mach/memory.h is required to provide special
219 definitions for this platform. The need for mach/memory.h should
220 be avoided when possible.
223 hex "Physical address of main memory"
224 depends on !ARM_PATCH_PHYS_VIRT && !NEED_MACH_MEMORY_H
226 Please provide the physical address corresponding to the
227 location of main memory in your system.
233 source "init/Kconfig"
235 source "kernel/Kconfig.freezer"
240 bool "MMU-based Paged Memory Management Support"
243 Select if you want MMU-based virtualised addressing space
244 support by paged memory management. If unsure, say 'Y'.
247 # The "ARM system type" choice list is ordered alphabetically by option
248 # text. Please add new entries in the option alphabetic order.
251 prompt "ARM system type"
252 default ARCH_VERSATILE
254 config ARCH_INTEGRATOR
255 bool "ARM Ltd. Integrator family"
257 select ARCH_HAS_CPUFREQ
259 select HAVE_MACH_CLKDEV
261 select GENERIC_CLOCKEVENTS
262 select PLAT_VERSATILE
263 select PLAT_VERSATILE_FPGA_IRQ
264 select NEED_MACH_MEMORY_H
266 Support for ARM's Integrator platform.
269 bool "ARM Ltd. RealView family"
272 select HAVE_MACH_CLKDEV
274 select GENERIC_CLOCKEVENTS
275 select ARCH_WANT_OPTIONAL_GPIOLIB
276 select PLAT_VERSATILE
277 select PLAT_VERSATILE_CLCD
278 select ARM_TIMER_SP804
279 select GPIO_PL061 if GPIOLIB
280 select NEED_MACH_MEMORY_H
282 This enables support for ARM Ltd RealView boards.
284 config ARCH_VERSATILE
285 bool "ARM Ltd. Versatile family"
289 select HAVE_MACH_CLKDEV
291 select GENERIC_CLOCKEVENTS
292 select ARCH_WANT_OPTIONAL_GPIOLIB
293 select PLAT_VERSATILE
294 select PLAT_VERSATILE_CLCD
295 select PLAT_VERSATILE_FPGA_IRQ
296 select ARM_TIMER_SP804
298 This enables support for ARM Ltd Versatile board.
301 bool "ARM Ltd. Versatile Express family"
302 select ARCH_WANT_OPTIONAL_GPIOLIB
304 select ARM_TIMER_SP804
306 select HAVE_MACH_CLKDEV
307 select GENERIC_CLOCKEVENTS
309 select HAVE_PATA_PLATFORM
311 select PLAT_VERSATILE
312 select PLAT_VERSATILE_CLCD
314 This enables support for the ARM Ltd Versatile Express boards.
318 select ARCH_REQUIRE_GPIOLIB
322 This enables support for systems based on the Atmel AT91RM9200,
323 AT91SAM9 and AT91CAP9 processors.
326 bool "Broadcom BCMRING"
330 select ARM_TIMER_SP804
332 select GENERIC_CLOCKEVENTS
333 select ARCH_WANT_OPTIONAL_GPIOLIB
335 Support for Broadcom's BCMRing platform.
338 bool "Calxeda Highbank-based"
339 select ARCH_WANT_OPTIONAL_GPIOLIB
342 select ARM_TIMER_SP804
345 select GENERIC_CLOCKEVENTS
348 select MIGHT_HAVE_CACHE_L2X0
351 Support for the Calxeda Highbank SoC based boards.
354 bool "Cirrus Logic CLPS711x/EP721x-based"
356 select ARCH_USES_GETTIMEOFFSET
357 select NEED_MACH_MEMORY_H
359 Support for Cirrus Logic 711x/721x based boards.
362 bool "Cavium Networks CNS3XXX family"
364 select GENERIC_CLOCKEVENTS
366 select MIGHT_HAVE_CACHE_L2X0
367 select MIGHT_HAVE_PCI
368 select PCI_DOMAINS if PCI
370 Support for Cavium Networks CNS3XXX platform.
373 bool "Cortina Systems Gemini"
375 select ARCH_REQUIRE_GPIOLIB
376 select ARCH_USES_GETTIMEOFFSET
378 Support for the Cortina Systems Gemini family SoCs
381 bool "CSR SiRFSoC PRIMA2 ARM Cortex A9 Platform"
384 select GENERIC_CLOCKEVENTS
386 select GENERIC_IRQ_CHIP
387 select MIGHT_HAVE_CACHE_L2X0
391 Support for CSR SiRFSoC ARM Cortex A9 Platform
398 select ARCH_USES_GETTIMEOFFSET
399 select NEED_MACH_MEMORY_H
401 This is an evaluation board for the StrongARM processor available
402 from Digital. It has limited hardware on-board, including an
403 Ethernet interface, two PCMCIA sockets, two serial ports and a
412 select ARCH_REQUIRE_GPIOLIB
413 select ARCH_HAS_HOLES_MEMORYMODEL
414 select ARCH_USES_GETTIMEOFFSET
415 select NEED_MACH_MEMORY_H
417 This enables support for the Cirrus EP93xx series of CPUs.
419 config ARCH_FOOTBRIDGE
423 select GENERIC_CLOCKEVENTS
425 select NEED_MACH_MEMORY_H
427 Support for systems based on the DC21285 companion chip
428 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
431 bool "Freescale MXC/iMX-based"
432 select GENERIC_CLOCKEVENTS
433 select ARCH_REQUIRE_GPIOLIB
436 select GENERIC_IRQ_CHIP
437 select HAVE_SCHED_CLOCK
438 select MULTI_IRQ_HANDLER
440 Support for Freescale MXC/iMX-based family of processors
443 bool "Freescale MXS-based"
444 select GENERIC_CLOCKEVENTS
445 select ARCH_REQUIRE_GPIOLIB
449 Support for Freescale MXS-based family of processors
452 bool "Hilscher NetX based"
456 select GENERIC_CLOCKEVENTS
458 This enables support for systems based on the Hilscher NetX Soc
461 bool "Hynix HMS720x-based"
464 select ARCH_USES_GETTIMEOFFSET
466 This enables support for systems based on the Hynix HMS720x
474 select ARCH_SUPPORTS_MSI
476 select NEED_MACH_MEMORY_H
478 Support for Intel's IOP13XX (XScale) family of processors.
486 select ARCH_REQUIRE_GPIOLIB
488 Support for Intel's 80219 and IOP32X (XScale) family of
497 select ARCH_REQUIRE_GPIOLIB
499 Support for Intel's IOP33X (XScale) family of processors.
506 select ARCH_USES_GETTIMEOFFSET
507 select NEED_MACH_MEMORY_H
509 Support for Intel's IXP23xx (XScale) family of processors.
512 bool "IXP2400/2800-based"
516 select ARCH_USES_GETTIMEOFFSET
517 select NEED_MACH_MEMORY_H
519 Support for Intel's IXP2400/2800 (XScale) family of processors.
527 select GENERIC_CLOCKEVENTS
528 select HAVE_SCHED_CLOCK
529 select MIGHT_HAVE_PCI
530 select DMABOUNCE if PCI
532 Support for Intel's IXP4XX (XScale) family of processors.
538 select ARCH_REQUIRE_GPIOLIB
539 select GENERIC_CLOCKEVENTS
542 Support for the Marvell Dove SoC 88AP510
545 bool "Marvell Kirkwood"
548 select ARCH_REQUIRE_GPIOLIB
549 select GENERIC_CLOCKEVENTS
552 Support for the following Marvell Kirkwood series SoCs:
553 88F6180, 88F6192 and 88F6281.
559 select ARCH_REQUIRE_GPIOLIB
562 select USB_ARCH_HAS_OHCI
564 select GENERIC_CLOCKEVENTS
566 Support for the NXP LPC32XX family of processors
569 bool "Marvell MV78xx0"
572 select ARCH_REQUIRE_GPIOLIB
573 select GENERIC_CLOCKEVENTS
576 Support for the following Marvell MV78xx0 series SoCs:
584 select ARCH_REQUIRE_GPIOLIB
585 select GENERIC_CLOCKEVENTS
588 Support for the following Marvell Orion 5x series SoCs:
589 Orion-1 (5181), Orion-VoIP (5181L), Orion-NAS (5182),
590 Orion-2 (5281), Orion-1-90 (6183).
593 bool "Marvell PXA168/910/MMP2"
595 select ARCH_REQUIRE_GPIOLIB
597 select GENERIC_CLOCKEVENTS
598 select HAVE_SCHED_CLOCK
602 select GENERIC_ALLOCATOR
604 Support for Marvell's PXA168/PXA910(MMP) and MMP2 processor line.
607 bool "Micrel/Kendin KS8695"
609 select ARCH_REQUIRE_GPIOLIB
610 select ARCH_USES_GETTIMEOFFSET
611 select NEED_MACH_MEMORY_H
613 Support for Micrel/Kendin KS8695 "Centaur" (ARM922T) based
614 System-on-Chip devices.
617 bool "Nuvoton W90X900 CPU"
619 select ARCH_REQUIRE_GPIOLIB
622 select GENERIC_CLOCKEVENTS
624 Support for Nuvoton (Winbond logic dept.) ARM9 processor,
625 At present, the w90x900 has been renamed nuc900, regarding
626 the ARM series product line, you can login the following
627 link address to know more.
629 <http://www.nuvoton.com/hq/enu/ProductAndSales/ProductLines/
630 ConsumerElectronicsIC/ARMMicrocontroller/ARMMicrocontroller>
636 select GENERIC_CLOCKEVENTS
639 select HAVE_SCHED_CLOCK
641 select MIGHT_HAVE_CACHE_L2X0
642 select ARCH_HAS_CPUFREQ
644 This enables support for NVIDIA Tegra based systems (Tegra APX,
645 Tegra 6xx and Tegra 2 series).
647 config ARCH_PICOXCELL
648 bool "Picochip picoXcell"
649 select ARCH_REQUIRE_GPIOLIB
650 select ARM_PATCH_PHYS_VIRT
654 select GENERIC_CLOCKEVENTS
656 select HAVE_SCHED_CLOCK
661 This enables support for systems based on the Picochip picoXcell
662 family of Femtocell devices. The picoxcell support requires device tree
666 bool "Philips Nexperia PNX4008 Mobile"
669 select ARCH_USES_GETTIMEOFFSET
671 This enables support for Philips PNX4008 mobile platform.
674 bool "PXA2xx/PXA3xx-based"
677 select ARCH_HAS_CPUFREQ
680 select ARCH_REQUIRE_GPIOLIB
681 select GENERIC_CLOCKEVENTS
682 select HAVE_SCHED_CLOCK
687 select MULTI_IRQ_HANDLER
688 select ARM_CPU_SUSPEND if PM
691 Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
696 select GENERIC_CLOCKEVENTS
697 select ARCH_REQUIRE_GPIOLIB
700 Support for Qualcomm MSM/QSD based systems. This runs on the
701 apps processor of the MSM/QSD and depends on a shared memory
702 interface to the modem processor which runs the baseband
703 stack and controls some vital subsystems
704 (clock and power control, etc).
707 bool "Renesas SH-Mobile / R-Mobile"
710 select HAVE_MACH_CLKDEV
712 select GENERIC_CLOCKEVENTS
713 select MIGHT_HAVE_CACHE_L2X0
716 select MULTI_IRQ_HANDLER
717 select PM_GENERIC_DOMAINS if PM
718 select NEED_MACH_MEMORY_H
720 Support for Renesas's SH-Mobile and R-Mobile ARM platforms.
727 select ARCH_MAY_HAVE_PC_FDC
728 select HAVE_PATA_PLATFORM
731 select ARCH_SPARSEMEM_ENABLE
732 select ARCH_USES_GETTIMEOFFSET
734 select NEED_MACH_MEMORY_H
736 On the Acorn Risc-PC, Linux can support the internal IDE disk and
737 CD-ROM interface, serial and parallel port, and the floppy drive.
744 select ARCH_SPARSEMEM_ENABLE
746 select ARCH_HAS_CPUFREQ
748 select GENERIC_CLOCKEVENTS
750 select HAVE_SCHED_CLOCK
752 select ARCH_REQUIRE_GPIOLIB
754 select NEED_MACH_MEMORY_H
756 Support for StrongARM 11x0 based boards.
759 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2416, S3C2440, S3C2442, S3C2443, S3C2450"
761 select ARCH_HAS_CPUFREQ
764 select ARCH_USES_GETTIMEOFFSET
765 select HAVE_S3C2410_I2C if I2C
767 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
768 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
769 the Samsung SMDK2410 development board (and derivatives).
771 Note, the S3C2416 and the S3C2450 are so close that they even share
772 the same SoC ID code. This means that there is no separate machine
773 directory (no arch/arm/mach-s3c2450) as the S3C2416 was first.
776 bool "Samsung S3C64XX"
784 select ARCH_USES_GETTIMEOFFSET
785 select ARCH_HAS_CPUFREQ
786 select ARCH_REQUIRE_GPIOLIB
787 select SAMSUNG_CLKSRC
788 select SAMSUNG_IRQ_VIC_TIMER
789 select S3C_GPIO_TRACK
791 select USB_ARCH_HAS_OHCI
792 select SAMSUNG_GPIOLIB_4BIT
793 select HAVE_S3C2410_I2C if I2C
794 select HAVE_S3C2410_WATCHDOG if WATCHDOG
796 Samsung S3C64XX series based systems
799 bool "Samsung S5P6440 S5P6450"
805 select HAVE_S3C2410_WATCHDOG if WATCHDOG
806 select GENERIC_CLOCKEVENTS
807 select HAVE_SCHED_CLOCK
808 select HAVE_S3C2410_I2C if I2C
809 select HAVE_S3C_RTC if RTC_CLASS
811 Samsung S5P64X0 CPU based systems, such as the Samsung SMDK6440,
815 bool "Samsung S5PC100"
820 select ARM_L1_CACHE_SHIFT_6
821 select ARCH_USES_GETTIMEOFFSET
822 select HAVE_S3C2410_I2C if I2C
823 select HAVE_S3C_RTC if RTC_CLASS
824 select HAVE_S3C2410_WATCHDOG if WATCHDOG
826 Samsung S5PC100 series based systems
829 bool "Samsung S5PV210/S5PC110"
831 select ARCH_SPARSEMEM_ENABLE
832 select ARCH_HAS_HOLES_MEMORYMODEL
837 select ARM_L1_CACHE_SHIFT_6
838 select ARCH_HAS_CPUFREQ
839 select GENERIC_CLOCKEVENTS
840 select HAVE_SCHED_CLOCK
841 select HAVE_S3C2410_I2C if I2C
842 select HAVE_S3C_RTC if RTC_CLASS
843 select HAVE_S3C2410_WATCHDOG if WATCHDOG
844 select NEED_MACH_MEMORY_H
846 Samsung S5PV210/S5PC110 series based systems
849 bool "SAMSUNG EXYNOS"
851 select ARCH_SPARSEMEM_ENABLE
852 select ARCH_HAS_HOLES_MEMORYMODEL
856 select ARCH_HAS_CPUFREQ
857 select GENERIC_CLOCKEVENTS
858 select HAVE_S3C_RTC if RTC_CLASS
859 select HAVE_S3C2410_I2C if I2C
860 select HAVE_S3C2410_WATCHDOG if WATCHDOG
861 select NEED_MACH_MEMORY_H
863 Support for SAMSUNG's EXYNOS SoCs (EXYNOS4/5)
872 select ARCH_USES_GETTIMEOFFSET
873 select NEED_MACH_MEMORY_H
875 Support for the StrongARM based Digital DNARD machine, also known
876 as "Shark" (<http://www.shark-linux.de/shark.html>).
879 bool "Telechips TCC ARM926-based systems"
884 select GENERIC_CLOCKEVENTS
886 Support for Telechips TCC ARM926-based systems.
889 bool "ST-Ericsson U300 Series"
893 select HAVE_SCHED_CLOCK
896 select ARM_PATCH_PHYS_VIRT
898 select GENERIC_CLOCKEVENTS
900 select HAVE_MACH_CLKDEV
902 select ARCH_REQUIRE_GPIOLIB
903 select NEED_MACH_MEMORY_H
905 Support for ST-Ericsson U300 series mobile platforms.
908 bool "ST-Ericsson U8500 Series"
911 select GENERIC_CLOCKEVENTS
913 select ARCH_REQUIRE_GPIOLIB
914 select ARCH_HAS_CPUFREQ
916 select MIGHT_HAVE_CACHE_L2X0
918 Support for ST-Ericsson's Ux500 architecture
921 bool "STMicroelectronics Nomadik"
926 select GENERIC_CLOCKEVENTS
927 select MIGHT_HAVE_CACHE_L2X0
928 select ARCH_REQUIRE_GPIOLIB
930 Support for the Nomadik platform by ST-Ericsson
934 select GENERIC_CLOCKEVENTS
935 select ARCH_REQUIRE_GPIOLIB
939 select GENERIC_ALLOCATOR
940 select GENERIC_IRQ_CHIP
941 select ARCH_HAS_HOLES_MEMORYMODEL
943 Support for TI's DaVinci platform.
948 select ARCH_REQUIRE_GPIOLIB
949 select ARCH_HAS_CPUFREQ
951 select GENERIC_CLOCKEVENTS
952 select HAVE_SCHED_CLOCK
953 select ARCH_HAS_HOLES_MEMORYMODEL
955 Support for TI's OMAP platform (OMAP1/2/3/4).
960 select ARCH_REQUIRE_GPIOLIB
963 select GENERIC_CLOCKEVENTS
966 Support for ST's SPEAr platform (SPEAr3xx, SPEAr6xx and SPEAr13xx).
969 bool "VIA/WonderMedia 85xx"
972 select ARCH_HAS_CPUFREQ
973 select GENERIC_CLOCKEVENTS
974 select ARCH_REQUIRE_GPIOLIB
977 Support for VIA/WonderMedia VT8500/WM85xx System-on-Chip.
980 bool "Xilinx Zynq ARM Cortex A9 Platform"
982 select GENERIC_CLOCKEVENTS
987 select MIGHT_HAVE_CACHE_L2X0
990 Support for Xilinx Zynq ARM Cortex A9 Platform
994 # This is sorted alphabetically by mach-* pathname. However, plat-*
995 # Kconfigs may be included either alphabetically (according to the
996 # plat- suffix) or along side the corresponding mach-* source.
998 source "arch/arm/mach-at91/Kconfig"
1000 source "arch/arm/mach-bcmring/Kconfig"
1002 source "arch/arm/mach-clps711x/Kconfig"
1004 source "arch/arm/mach-cns3xxx/Kconfig"
1006 source "arch/arm/mach-davinci/Kconfig"
1008 source "arch/arm/mach-dove/Kconfig"
1010 source "arch/arm/mach-ep93xx/Kconfig"
1012 source "arch/arm/mach-footbridge/Kconfig"
1014 source "arch/arm/mach-gemini/Kconfig"
1016 source "arch/arm/mach-h720x/Kconfig"
1018 source "arch/arm/mach-integrator/Kconfig"
1020 source "arch/arm/mach-iop32x/Kconfig"
1022 source "arch/arm/mach-iop33x/Kconfig"
1024 source "arch/arm/mach-iop13xx/Kconfig"
1026 source "arch/arm/mach-ixp4xx/Kconfig"
1028 source "arch/arm/mach-ixp2000/Kconfig"
1030 source "arch/arm/mach-ixp23xx/Kconfig"
1032 source "arch/arm/mach-kirkwood/Kconfig"
1034 source "arch/arm/mach-ks8695/Kconfig"
1036 source "arch/arm/mach-lpc32xx/Kconfig"
1038 source "arch/arm/mach-msm/Kconfig"
1040 source "arch/arm/mach-mv78xx0/Kconfig"
1042 source "arch/arm/plat-mxc/Kconfig"
1044 source "arch/arm/mach-mxs/Kconfig"
1046 source "arch/arm/mach-netx/Kconfig"
1048 source "arch/arm/mach-nomadik/Kconfig"
1049 source "arch/arm/plat-nomadik/Kconfig"
1051 source "arch/arm/plat-omap/Kconfig"
1053 source "arch/arm/mach-omap1/Kconfig"
1055 source "arch/arm/mach-omap2/Kconfig"
1057 source "arch/arm/mach-orion5x/Kconfig"
1059 source "arch/arm/mach-pxa/Kconfig"
1060 source "arch/arm/plat-pxa/Kconfig"
1062 source "arch/arm/mach-mmp/Kconfig"
1064 source "arch/arm/mach-realview/Kconfig"
1066 source "arch/arm/mach-sa1100/Kconfig"
1068 source "arch/arm/plat-samsung/Kconfig"
1069 source "arch/arm/plat-s3c24xx/Kconfig"
1070 source "arch/arm/plat-s5p/Kconfig"
1072 source "arch/arm/plat-spear/Kconfig"
1074 source "arch/arm/plat-tcc/Kconfig"
1077 source "arch/arm/mach-s3c2410/Kconfig"
1078 source "arch/arm/mach-s3c2412/Kconfig"
1079 source "arch/arm/mach-s3c2416/Kconfig"
1080 source "arch/arm/mach-s3c2440/Kconfig"
1081 source "arch/arm/mach-s3c2443/Kconfig"
1085 source "arch/arm/mach-s3c64xx/Kconfig"
1088 source "arch/arm/mach-s5p64x0/Kconfig"
1090 source "arch/arm/mach-s5pc100/Kconfig"
1092 source "arch/arm/mach-s5pv210/Kconfig"
1094 source "arch/arm/mach-exynos/Kconfig"
1096 source "arch/arm/mach-shmobile/Kconfig"
1098 source "arch/arm/mach-tegra/Kconfig"
1100 source "arch/arm/mach-u300/Kconfig"
1102 source "arch/arm/mach-ux500/Kconfig"
1104 source "arch/arm/mach-versatile/Kconfig"
1106 source "arch/arm/mach-vexpress/Kconfig"
1107 source "arch/arm/plat-versatile/Kconfig"
1109 source "arch/arm/mach-vt8500/Kconfig"
1111 source "arch/arm/mach-w90x900/Kconfig"
1113 # Definitions to make life easier
1119 select GENERIC_CLOCKEVENTS
1120 select HAVE_SCHED_CLOCK
1125 select GENERIC_IRQ_CHIP
1126 select HAVE_SCHED_CLOCK
1131 config PLAT_VERSATILE
1134 config ARM_TIMER_SP804
1138 source arch/arm/mm/Kconfig
1141 bool "Enable iWMMXt support"
1142 depends on CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_PJ4
1143 default y if PXA27x || PXA3xx || PXA95x || ARCH_MMP
1145 Enable support for iWMMXt context switching at run time if
1146 running on a CPU that supports it.
1148 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
1151 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
1155 depends on (CPU_V6 || CPU_V6K || CPU_V7 || XSCALE_PMU) && \
1156 (!ARCH_OMAP3 || OMAP3_EMU)
1160 config MULTI_IRQ_HANDLER
1163 Allow each machine to specify it's own IRQ handler at run time.
1166 source "arch/arm/Kconfig-nommu"
1169 config ARM_ERRATA_411920
1170 bool "ARM errata: Invalidation of the Instruction Cache operation can fail"
1171 depends on CPU_V6 || CPU_V6K
1173 Invalidation of the Instruction Cache operation can
1174 fail. This erratum is present in 1136 (before r1p4), 1156 and 1176.
1175 It does not affect the MPCore. This option enables the ARM Ltd.
1176 recommended workaround.
1178 config ARM_ERRATA_430973
1179 bool "ARM errata: Stale prediction on replaced interworking branch"
1182 This option enables the workaround for the 430973 Cortex-A8
1183 (r1p0..r1p2) erratum. If a code sequence containing an ARM/Thumb
1184 interworking branch is replaced with another code sequence at the
1185 same virtual address, whether due to self-modifying code or virtual
1186 to physical address re-mapping, Cortex-A8 does not recover from the
1187 stale interworking branch prediction. This results in Cortex-A8
1188 executing the new code sequence in the incorrect ARM or Thumb state.
1189 The workaround enables the BTB/BTAC operations by setting ACTLR.IBE
1190 and also flushes the branch target cache at every context switch.
1191 Note that setting specific bits in the ACTLR register may not be
1192 available in non-secure mode.
1194 config ARM_ERRATA_458693
1195 bool "ARM errata: Processor deadlock when a false hazard is created"
1198 This option enables the workaround for the 458693 Cortex-A8 (r2p0)
1199 erratum. For very specific sequences of memory operations, it is
1200 possible for a hazard condition intended for a cache line to instead
1201 be incorrectly associated with a different cache line. This false
1202 hazard might then cause a processor deadlock. The workaround enables
1203 the L1 caching of the NEON accesses and disables the PLD instruction
1204 in the ACTLR register. Note that setting specific bits in the ACTLR
1205 register may not be available in non-secure mode.
1207 config ARM_ERRATA_460075
1208 bool "ARM errata: Data written to the L2 cache can be overwritten with stale data"
1211 This option enables the workaround for the 460075 Cortex-A8 (r2p0)
1212 erratum. Any asynchronous access to the L2 cache may encounter a
1213 situation in which recent store transactions to the L2 cache are lost
1214 and overwritten with stale memory contents from external memory. The
1215 workaround disables the write-allocate mode for the L2 cache via the
1216 ACTLR register. Note that setting specific bits in the ACTLR register
1217 may not be available in non-secure mode.
1219 config ARM_ERRATA_742230
1220 bool "ARM errata: DMB operation may be faulty"
1221 depends on CPU_V7 && SMP
1223 This option enables the workaround for the 742230 Cortex-A9
1224 (r1p0..r2p2) erratum. Under rare circumstances, a DMB instruction
1225 between two write operations may not ensure the correct visibility
1226 ordering of the two writes. This workaround sets a specific bit in
1227 the diagnostic register of the Cortex-A9 which causes the DMB
1228 instruction to behave as a DSB, ensuring the correct behaviour of
1231 config ARM_ERRATA_742231
1232 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
1233 depends on CPU_V7 && SMP
1235 This option enables the workaround for the 742231 Cortex-A9
1236 (r2p0..r2p2) erratum. Under certain conditions, specific to the
1237 Cortex-A9 MPCore micro-architecture, two CPUs working in SMP mode,
1238 accessing some data located in the same cache line, may get corrupted
1239 data due to bad handling of the address hazard when the line gets
1240 replaced from one of the CPUs at the same time as another CPU is
1241 accessing it. This workaround sets specific bits in the diagnostic
1242 register of the Cortex-A9 which reduces the linefill issuing
1243 capabilities of the processor.
1245 config PL310_ERRATA_588369
1246 bool "Clean & Invalidate maintenance operations do not invalidate clean lines"
1247 depends on CACHE_L2X0
1249 The PL310 L2 cache controller implements three types of Clean &
1250 Invalidate maintenance operations: by Physical Address
1251 (offset 0x7F0), by Index/Way (0x7F8) and by Way (0x7FC).
1252 They are architecturally defined to behave as the execution of a
1253 clean operation followed immediately by an invalidate operation,
1254 both performing to the same memory location. This functionality
1255 is not correctly implemented in PL310 as clean lines are not
1256 invalidated as a result of these operations.
1258 config ARM_ERRATA_720789
1259 bool "ARM errata: TLBIASIDIS and TLBIMVAIS operations can broadcast a faulty ASID"
1260 depends on CPU_V7 && SMP
1262 This option enables the workaround for the 720789 Cortex-A9 (prior to
1263 r2p0) erratum. A faulty ASID can be sent to the other CPUs for the
1264 broadcasted CP15 TLB maintenance operations TLBIASIDIS and TLBIMVAIS.
1265 As a consequence of this erratum, some TLB entries which should be
1266 invalidated are not, resulting in an incoherency in the system page
1267 tables. The workaround changes the TLB flushing routines to invalidate
1268 entries regardless of the ASID.
1270 config PL310_ERRATA_727915
1271 bool "Background Clean & Invalidate by Way operation can cause data corruption"
1272 depends on CACHE_L2X0
1274 PL310 implements the Clean & Invalidate by Way L2 cache maintenance
1275 operation (offset 0x7FC). This operation runs in background so that
1276 PL310 can handle normal accesses while it is in progress. Under very
1277 rare circumstances, due to this erratum, write data can be lost when
1278 PL310 treats a cacheable write transaction during a Clean &
1279 Invalidate by Way operation.
1281 config ARM_ERRATA_743622
1282 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
1285 This option enables the workaround for the 743622 Cortex-A9
1286 (r2p0..r2p2) erratum. Under very rare conditions, a faulty
1287 optimisation in the Cortex-A9 Store Buffer may lead to data
1288 corruption. This workaround sets a specific bit in the diagnostic
1289 register of the Cortex-A9 which disables the Store Buffer
1290 optimisation, preventing the defect from occurring. This has no
1291 visible impact on the overall performance or power consumption of the
1294 config ARM_ERRATA_751472
1295 bool "ARM errata: Interrupted ICIALLUIS may prevent completion of broadcasted operation"
1296 depends on CPU_V7 && SMP
1298 This option enables the workaround for the 751472 Cortex-A9 (prior
1299 to r3p0) erratum. An interrupted ICIALLUIS operation may prevent the
1300 completion of a following broadcasted operation if the second
1301 operation is received by a CPU before the ICIALLUIS has completed,
1302 potentially leading to corrupted entries in the cache or TLB.
1304 config ARM_ERRATA_753970
1305 bool "ARM errata: cache sync operation may be faulty"
1306 depends on CACHE_PL310
1308 This option enables the workaround for the 753970 PL310 (r3p0) erratum.
1310 Under some condition the effect of cache sync operation on
1311 the store buffer still remains when the operation completes.
1312 This means that the store buffer is always asked to drain and
1313 this prevents it from merging any further writes. The workaround
1314 is to replace the normal offset of cache sync operation (0x730)
1315 by another offset targeting an unmapped PL310 register 0x740.
1316 This has the same effect as the cache sync operation: store buffer
1317 drain and waiting for all buffers empty.
1319 config ARM_ERRATA_754322
1320 bool "ARM errata: possible faulty MMU translations following an ASID switch"
1323 This option enables the workaround for the 754322 Cortex-A9 (r2p*,
1324 r3p*) erratum. A speculative memory access may cause a page table walk
1325 which starts prior to an ASID switch but completes afterwards. This
1326 can populate the micro-TLB with a stale entry which may be hit with
1327 the new ASID. This workaround places two dsb instructions in the mm
1328 switching code so that no page table walks can cross the ASID switch.
1330 config ARM_ERRATA_754327
1331 bool "ARM errata: no automatic Store Buffer drain"
1332 depends on CPU_V7 && SMP
1334 This option enables the workaround for the 754327 Cortex-A9 (prior to
1335 r2p0) erratum. The Store Buffer does not have any automatic draining
1336 mechanism and therefore a livelock may occur if an external agent
1337 continuously polls a memory location waiting to observe an update.
1338 This workaround defines cpu_relax() as smp_mb(), preventing correctly
1339 written polling loops from denying visibility of updates to memory.
1341 config ARM_ERRATA_364296
1342 bool "ARM errata: Possible cache data corruption with hit-under-miss enabled"
1343 depends on CPU_V6 && !SMP
1345 This options enables the workaround for the 364296 ARM1136
1346 r0p2 erratum (possible cache data corruption with
1347 hit-under-miss enabled). It sets the undocumented bit 31 in
1348 the auxiliary control register and the FI bit in the control
1349 register, thus disabling hit-under-miss without putting the
1350 processor into full low interrupt latency mode. ARM11MPCore
1353 config ARM_ERRATA_764369
1354 bool "ARM errata: Data cache line maintenance operation by MVA may not succeed"
1355 depends on CPU_V7 && SMP
1357 This option enables the workaround for erratum 764369
1358 affecting Cortex-A9 MPCore with two or more processors (all
1359 current revisions). Under certain timing circumstances, a data
1360 cache line maintenance operation by MVA targeting an Inner
1361 Shareable memory region may fail to proceed up to either the
1362 Point of Coherency or to the Point of Unification of the
1363 system. This workaround adds a DSB instruction before the
1364 relevant cache maintenance functions and sets a specific bit
1365 in the diagnostic control register of the SCU.
1369 source "arch/arm/common/Kconfig"
1379 Find out whether you have ISA slots on your motherboard. ISA is the
1380 name of a bus system, i.e. the way the CPU talks to the other stuff
1381 inside your box. Other bus systems are PCI, EISA, MicroChannel
1382 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1383 newer boards don't support it. If you have ISA, say Y, otherwise N.
1385 # Select ISA DMA controller support
1390 # Select ISA DMA interface
1395 bool "PCI support" if MIGHT_HAVE_PCI
1397 Find out whether you have a PCI motherboard. PCI is the name of a
1398 bus system, i.e. the way the CPU talks to the other stuff inside
1399 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1400 VESA. If you have PCI, say Y, otherwise N.
1406 config PCI_NANOENGINE
1407 bool "BSE nanoEngine PCI support"
1408 depends on SA1100_NANOENGINE
1410 Enable PCI on the BSE nanoEngine board.
1415 # Select the host bridge type
1416 config PCI_HOST_VIA82C505
1418 depends on PCI && ARCH_SHARK
1421 config PCI_HOST_ITE8152
1423 depends on PCI && MACH_ARMCORE
1427 source "drivers/pci/Kconfig"
1429 source "drivers/pcmcia/Kconfig"
1433 menu "Kernel Features"
1435 source "kernel/time/Kconfig"
1440 This option should be selected by machines which have an SMP-
1443 The only effect of this option is to make the SMP-related
1444 options available to the user for configuration.
1447 bool "Symmetric Multi-Processing"
1448 depends on CPU_V6K || CPU_V7
1449 depends on GENERIC_CLOCKEVENTS
1452 select USE_GENERIC_SMP_HELPERS
1453 select HAVE_ARM_SCU if !ARCH_MSM_SCORPIONMP
1455 This enables support for systems with more than one CPU. If you have
1456 a system with only one CPU, like most personal computers, say N. If
1457 you have a system with more than one CPU, say Y.
1459 If you say N here, the kernel will run on single and multiprocessor
1460 machines, but will use only one CPU of a multiprocessor machine. If
1461 you say Y here, the kernel will run on many, but not all, single
1462 processor machines. On a single processor machine, the kernel will
1463 run faster if you say N here.
1465 See also <file:Documentation/x86/i386/IO-APIC.txt>,
1466 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
1467 <http://tldp.org/HOWTO/SMP-HOWTO.html>.
1469 If you don't know what to do here, say N.
1472 bool "Allow booting SMP kernel on uniprocessor systems (EXPERIMENTAL)"
1473 depends on EXPERIMENTAL
1474 depends on SMP && !XIP_KERNEL
1477 SMP kernels contain instructions which fail on non-SMP processors.
1478 Enabling this option allows the kernel to modify itself to make
1479 these instructions safe. Disabling it allows about 1K of space
1482 If you don't know what to do here, say Y.
1484 config ARM_CPU_TOPOLOGY
1485 bool "Support cpu topology definition"
1486 depends on SMP && CPU_V7
1489 Support ARM cpu topology definition. The MPIDR register defines
1490 affinity between processors which is then used to describe the cpu
1491 topology of an ARM System.
1494 bool "Multi-core scheduler support"
1495 depends on ARM_CPU_TOPOLOGY
1497 Multi-core scheduler support improves the CPU scheduler's decision
1498 making when dealing with multi-core CPU chips at a cost of slightly
1499 increased overhead in some places. If unsure say N here.
1502 bool "SMT scheduler support"
1503 depends on ARM_CPU_TOPOLOGY
1505 Improves the CPU scheduler's decision making when dealing with
1506 MultiThreading at a cost of slightly increased overhead in some
1507 places. If unsure say N here.
1512 This option enables support for the ARM system coherency unit
1519 This options enables support for the ARM timer and watchdog unit
1522 prompt "Memory split"
1525 Select the desired split between kernel and user memory.
1527 If you are not absolutely sure what you are doing, leave this
1531 bool "3G/1G user/kernel split"
1533 bool "2G/2G user/kernel split"
1535 bool "1G/3G user/kernel split"
1540 default 0x40000000 if VMSPLIT_1G
1541 default 0x80000000 if VMSPLIT_2G
1545 int "Maximum number of CPUs (2-32)"
1551 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
1552 depends on SMP && HOTPLUG && EXPERIMENTAL
1554 Say Y here to experiment with turning CPUs off and on. CPUs
1555 can be controlled through /sys/devices/system/cpu.
1558 bool "Use local timer interrupts"
1561 select HAVE_ARM_TWD if (!ARCH_MSM_SCORPIONMP && !EXYNOS4_MCT)
1563 Enable support for local timers on SMP platforms, rather then the
1564 legacy IPI broadcast method. Local timers allows the system
1565 accounting to be spread across the timer interval, preventing a
1566 "thundering herd" at every timer tick.
1568 source kernel/Kconfig.preempt
1572 default 200 if ARCH_EBSA110 || ARCH_S3C2410 || ARCH_S5P64X0 || \
1573 ARCH_S5PV210 || ARCH_EXYNOS4
1574 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
1575 default AT91_TIMER_HZ if ARCH_AT91
1576 default SHMOBILE_TIMER_HZ if ARCH_SHMOBILE
1579 config THUMB2_KERNEL
1580 bool "Compile the kernel in Thumb-2 mode (EXPERIMENTAL)"
1581 depends on CPU_V7 && !CPU_V6 && !CPU_V6K && EXPERIMENTAL
1583 select ARM_ASM_UNIFIED
1586 By enabling this option, the kernel will be compiled in
1587 Thumb-2 mode. A compiler/assembler that understand the unified
1588 ARM-Thumb syntax is needed.
1592 config THUMB2_AVOID_R_ARM_THM_JUMP11
1593 bool "Work around buggy Thumb-2 short branch relocations in gas"
1594 depends on THUMB2_KERNEL && MODULES
1597 Various binutils versions can resolve Thumb-2 branches to
1598 locally-defined, preemptible global symbols as short-range "b.n"
1599 branch instructions.
1601 This is a problem, because there's no guarantee the final
1602 destination of the symbol, or any candidate locations for a
1603 trampoline, are within range of the branch. For this reason, the
1604 kernel does not support fixing up the R_ARM_THM_JUMP11 (102)
1605 relocation in modules at all, and it makes little sense to add
1608 The symptom is that the kernel fails with an "unsupported
1609 relocation" error when loading some modules.
1611 Until fixed tools are available, passing
1612 -fno-optimize-sibling-calls to gcc should prevent gcc generating
1613 code which hits this problem, at the cost of a bit of extra runtime
1614 stack usage in some cases.
1616 The problem is described in more detail at:
1617 https://bugs.launchpad.net/binutils-linaro/+bug/725126
1619 Only Thumb-2 kernels are affected.
1621 Unless you are sure your tools don't have this problem, say Y.
1623 config ARM_ASM_UNIFIED
1627 bool "Use the ARM EABI to compile the kernel"
1629 This option allows for the kernel to be compiled using the latest
1630 ARM ABI (aka EABI). This is only useful if you are using a user
1631 space environment that is also compiled with EABI.
1633 Since there are major incompatibilities between the legacy ABI and
1634 EABI, especially with regard to structure member alignment, this
1635 option also changes the kernel syscall calling convention to
1636 disambiguate both ABIs and allow for backward compatibility support
1637 (selected with CONFIG_OABI_COMPAT).
1639 To use this you need GCC version 4.0.0 or later.
1642 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
1643 depends on AEABI && EXPERIMENTAL && !THUMB2_KERNEL
1646 This option preserves the old syscall interface along with the
1647 new (ARM EABI) one. It also provides a compatibility layer to
1648 intercept syscalls that have structure arguments which layout
1649 in memory differs between the legacy ABI and the new ARM EABI
1650 (only for non "thumb" binaries). This option adds a tiny
1651 overhead to all syscalls and produces a slightly larger kernel.
1652 If you know you'll be using only pure EABI user space then you
1653 can say N here. If this option is not selected and you attempt
1654 to execute a legacy ABI binary then the result will be
1655 UNPREDICTABLE (in fact it can be predicted that it won't work
1656 at all). If in doubt say Y.
1658 config ARCH_HAS_HOLES_MEMORYMODEL
1661 config ARCH_SPARSEMEM_ENABLE
1664 config ARCH_SPARSEMEM_DEFAULT
1665 def_bool ARCH_SPARSEMEM_ENABLE
1667 config ARCH_SELECT_MEMORY_MODEL
1668 def_bool ARCH_SPARSEMEM_ENABLE
1670 config HAVE_ARCH_PFN_VALID
1671 def_bool ARCH_HAS_HOLES_MEMORYMODEL || !SPARSEMEM
1674 bool "High Memory Support"
1677 The address space of ARM processors is only 4 Gigabytes large
1678 and it has to accommodate user address space, kernel address
1679 space as well as some memory mapped IO. That means that, if you
1680 have a large amount of physical memory and/or IO, not all of the
1681 memory can be "permanently mapped" by the kernel. The physical
1682 memory that is not permanently mapped is called "high memory".
1684 Depending on the selected kernel/user memory split, minimum
1685 vmalloc space and actual amount of RAM, you may not need this
1686 option which should result in a slightly faster kernel.
1691 bool "Allocate 2nd-level pagetables from highmem"
1694 config HW_PERF_EVENTS
1695 bool "Enable hardware performance counter support for perf events"
1696 depends on PERF_EVENTS && CPU_HAS_PMU
1699 Enable hardware performance counter support for perf events. If
1700 disabled, perf events will use software events only.
1704 config FORCE_MAX_ZONEORDER
1705 int "Maximum zone order" if ARCH_SHMOBILE
1706 range 11 64 if ARCH_SHMOBILE
1707 default "9" if SA1111
1710 The kernel memory allocator divides physically contiguous memory
1711 blocks into "zones", where each zone is a power of two number of
1712 pages. This option selects the largest power of two that the kernel
1713 keeps in the memory allocator. If you need to allocate very large
1714 blocks of physically contiguous memory, then you may need to
1715 increase this value.
1717 This config option is actually maximum order plus one. For example,
1718 a value of 11 means that the largest free memory block is 2^10 pages.
1721 bool "Timer and CPU usage LEDs"
1722 depends on ARCH_CDB89712 || ARCH_EBSA110 || \
1723 ARCH_EBSA285 || ARCH_INTEGRATOR || \
1724 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
1725 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
1726 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
1727 ARCH_AT91 || ARCH_DAVINCI || \
1728 ARCH_KS8695 || MACH_RD88F5182 || ARCH_REALVIEW
1730 If you say Y here, the LEDs on your machine will be used
1731 to provide useful information about your current system status.
1733 If you are compiling a kernel for a NetWinder or EBSA-285, you will
1734 be able to select which LEDs are active using the options below. If
1735 you are compiling a kernel for the EBSA-110 or the LART however, the
1736 red LED will simply flash regularly to indicate that the system is
1737 still functional. It is safe to say Y here if you have a CATS
1738 system, but the driver will do nothing.
1741 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
1742 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1743 || MACH_OMAP_PERSEUS2
1745 depends on !GENERIC_CLOCKEVENTS
1746 default y if ARCH_EBSA110
1748 If you say Y here, one of the system LEDs (the green one on the
1749 NetWinder, the amber one on the EBSA285, or the red one on the LART)
1750 will flash regularly to indicate that the system is still
1751 operational. This is mainly useful to kernel hackers who are
1752 debugging unstable kernels.
1754 The LART uses the same LED for both Timer LED and CPU usage LED
1755 functions. You may choose to use both, but the Timer LED function
1756 will overrule the CPU usage LED.
1759 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
1761 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1762 || MACH_OMAP_PERSEUS2
1765 If you say Y here, the red LED will be used to give a good real
1766 time indication of CPU usage, by lighting whenever the idle task
1767 is not currently executing.
1769 The LART uses the same LED for both Timer LED and CPU usage LED
1770 functions. You may choose to use both, but the Timer LED function
1771 will overrule the CPU usage LED.
1773 config ALIGNMENT_TRAP
1775 depends on CPU_CP15_MMU
1776 default y if !ARCH_EBSA110
1777 select HAVE_PROC_CPU if PROC_FS
1779 ARM processors cannot fetch/store information which is not
1780 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
1781 address divisible by 4. On 32-bit ARM processors, these non-aligned
1782 fetch/store instructions will be emulated in software if you say
1783 here, which has a severe performance impact. This is necessary for
1784 correct operation of some network protocols. With an IP-only
1785 configuration it is safe to say N, otherwise say Y.
1787 config UACCESS_WITH_MEMCPY
1788 bool "Use kernel mem{cpy,set}() for {copy_to,clear}_user() (EXPERIMENTAL)"
1789 depends on MMU && EXPERIMENTAL
1790 default y if CPU_FEROCEON
1792 Implement faster copy_to_user and clear_user methods for CPU
1793 cores where a 8-word STM instruction give significantly higher
1794 memory write throughput than a sequence of individual 32bit stores.
1796 A possible side effect is a slight increase in scheduling latency
1797 between threads sharing the same address space if they invoke
1798 such copy operations with large buffers.
1800 However, if the CPU data cache is using a write-allocate mode,
1801 this option is unlikely to provide any performance gain.
1805 prompt "Enable seccomp to safely compute untrusted bytecode"
1807 This kernel feature is useful for number crunching applications
1808 that may need to compute untrusted bytecode during their
1809 execution. By using pipes or other transports made available to
1810 the process as file descriptors supporting the read/write
1811 syscalls, it's possible to isolate those applications in
1812 their own address space using seccomp. Once seccomp is
1813 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1814 and the task is only allowed to execute a few safe syscalls
1815 defined by each seccomp mode.
1817 config CC_STACKPROTECTOR
1818 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1819 depends on EXPERIMENTAL
1821 This option turns on the -fstack-protector GCC feature. This
1822 feature puts, at the beginning of functions, a canary value on
1823 the stack just before the return address, and validates
1824 the value just before actually returning. Stack based buffer
1825 overflows (that need to overwrite this return address) now also
1826 overwrite the canary, which gets detected and the attack is then
1827 neutralized via a kernel panic.
1828 This feature requires gcc version 4.2 or above.
1830 config DEPRECATED_PARAM_STRUCT
1831 bool "Provide old way to pass kernel parameters"
1833 This was deprecated in 2001 and announced to live on for 5 years.
1834 Some old boot loaders still use this way.
1841 bool "Flattened Device Tree support"
1843 select OF_EARLY_FLATTREE
1846 Include support for flattened device tree machine descriptions.
1848 # Compressed boot loader in ROM. Yes, we really want to ask about
1849 # TEXT and BSS so we preserve their values in the config files.
1850 config ZBOOT_ROM_TEXT
1851 hex "Compressed ROM boot loader base address"
1854 The physical address at which the ROM-able zImage is to be
1855 placed in the target. Platforms which normally make use of
1856 ROM-able zImage formats normally set this to a suitable
1857 value in their defconfig file.
1859 If ZBOOT_ROM is not enabled, this has no effect.
1861 config ZBOOT_ROM_BSS
1862 hex "Compressed ROM boot loader BSS address"
1865 The base address of an area of read/write memory in the target
1866 for the ROM-able zImage which must be available while the
1867 decompressor is running. It must be large enough to hold the
1868 entire decompressed kernel plus an additional 128 KiB.
1869 Platforms which normally make use of ROM-able zImage formats
1870 normally set this to a suitable value in their defconfig file.
1872 If ZBOOT_ROM is not enabled, this has no effect.
1875 bool "Compressed boot loader in ROM/flash"
1876 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
1878 Say Y here if you intend to execute your compressed kernel image
1879 (zImage) directly from ROM or flash. If unsure, say N.
1882 prompt "Include SD/MMC loader in zImage (EXPERIMENTAL)"
1883 depends on ZBOOT_ROM && ARCH_SH7372 && EXPERIMENTAL
1884 default ZBOOT_ROM_NONE
1886 Include experimental SD/MMC loading code in the ROM-able zImage.
1887 With this enabled it is possible to write the the ROM-able zImage
1888 kernel image to an MMC or SD card and boot the kernel straight
1889 from the reset vector. At reset the processor Mask ROM will load
1890 the first part of the the ROM-able zImage which in turn loads the
1891 rest the kernel image to RAM.
1893 config ZBOOT_ROM_NONE
1894 bool "No SD/MMC loader in zImage (EXPERIMENTAL)"
1896 Do not load image from SD or MMC
1898 config ZBOOT_ROM_MMCIF
1899 bool "Include MMCIF loader in zImage (EXPERIMENTAL)"
1901 Load image from MMCIF hardware block.
1903 config ZBOOT_ROM_SH_MOBILE_SDHI
1904 bool "Include SuperH Mobile SDHI loader in zImage (EXPERIMENTAL)"
1906 Load image from SDHI hardware block
1910 config ARM_APPENDED_DTB
1911 bool "Use appended device tree blob to zImage (EXPERIMENTAL)"
1912 depends on OF && !ZBOOT_ROM && EXPERIMENTAL
1914 With this option, the boot code will look for a device tree binary
1915 (DTB) appended to zImage
1916 (e.g. cat zImage <filename>.dtb > zImage_w_dtb).
1918 This is meant as a backward compatibility convenience for those
1919 systems with a bootloader that can't be upgraded to accommodate
1920 the documented boot protocol using a device tree.
1922 Beware that there is very little in terms of protection against
1923 this option being confused by leftover garbage in memory that might
1924 look like a DTB header after a reboot if no actual DTB is appended
1925 to zImage. Do not leave this option active in a production kernel
1926 if you don't intend to always append a DTB. Proper passing of the
1927 location into r2 of a bootloader provided DTB is always preferable
1930 config ARM_ATAG_DTB_COMPAT
1931 bool "Supplement the appended DTB with traditional ATAG information"
1932 depends on ARM_APPENDED_DTB
1934 Some old bootloaders can't be updated to a DTB capable one, yet
1935 they provide ATAGs with memory configuration, the ramdisk address,
1936 the kernel cmdline string, etc. Such information is dynamically
1937 provided by the bootloader and can't always be stored in a static
1938 DTB. To allow a device tree enabled kernel to be used with such
1939 bootloaders, this option allows zImage to extract the information
1940 from the ATAG list and store it at run time into the appended DTB.
1943 string "Default kernel command string"
1946 On some architectures (EBSA110 and CATS), there is currently no way
1947 for the boot loader to pass arguments to the kernel. For these
1948 architectures, you should supply some command-line options at build
1949 time by entering them here. As a minimum, you should specify the
1950 memory size and the root device (e.g., mem=64M root=/dev/nfs).
1953 prompt "Kernel command line type" if CMDLINE != ""
1954 default CMDLINE_FROM_BOOTLOADER
1956 config CMDLINE_FROM_BOOTLOADER
1957 bool "Use bootloader kernel arguments if available"
1959 Uses the command-line options passed by the boot loader. If
1960 the boot loader doesn't provide any, the default kernel command
1961 string provided in CMDLINE will be used.
1963 config CMDLINE_EXTEND
1964 bool "Extend bootloader kernel arguments"
1966 The command-line arguments provided by the boot loader will be
1967 appended to the default kernel command string.
1969 config CMDLINE_FORCE
1970 bool "Always use the default kernel command string"
1972 Always use the default kernel command string, even if the boot
1973 loader passes other arguments to the kernel.
1974 This is useful if you cannot or don't want to change the
1975 command-line options your boot loader passes to the kernel.
1979 bool "Kernel Execute-In-Place from ROM"
1980 depends on !ZBOOT_ROM
1982 Execute-In-Place allows the kernel to run from non-volatile storage
1983 directly addressable by the CPU, such as NOR flash. This saves RAM
1984 space since the text section of the kernel is not loaded from flash
1985 to RAM. Read-write sections, such as the data section and stack,
1986 are still copied to RAM. The XIP kernel is not compressed since
1987 it has to run directly from flash, so it will take more space to
1988 store it. The flash address used to link the kernel object files,
1989 and for storing it, is configuration dependent. Therefore, if you
1990 say Y here, you must know the proper physical address where to
1991 store the kernel image depending on your own flash memory usage.
1993 Also note that the make target becomes "make xipImage" rather than
1994 "make zImage" or "make Image". The final kernel binary to put in
1995 ROM memory will be arch/arm/boot/xipImage.
1999 config XIP_PHYS_ADDR
2000 hex "XIP Kernel Physical Location"
2001 depends on XIP_KERNEL
2002 default "0x00080000"
2004 This is the physical address in your flash memory the kernel will
2005 be linked for and stored to. This address is dependent on your
2009 bool "Kexec system call (EXPERIMENTAL)"
2010 depends on EXPERIMENTAL
2012 kexec is a system call that implements the ability to shutdown your
2013 current kernel, and to start another kernel. It is like a reboot
2014 but it is independent of the system firmware. And like a reboot
2015 you can start any kernel with it, not just Linux.
2017 It is an ongoing process to be certain the hardware in a machine
2018 is properly shutdown, so do not be surprised if this code does not
2019 initially work for you. It may help to enable device hotplugging
2023 bool "Export atags in procfs"
2027 Should the atags used to boot the kernel be exported in an "atags"
2028 file in procfs. Useful with kexec.
2031 bool "Build kdump crash kernel (EXPERIMENTAL)"
2032 depends on EXPERIMENTAL
2034 Generate crash dump after being started by kexec. This should
2035 be normally only set in special crash dump kernels which are
2036 loaded in the main kernel with kexec-tools into a specially
2037 reserved region and then later executed after a crash by
2038 kdump/kexec. The crash dump kernel must be compiled to a
2039 memory address not used by the main kernel
2041 For more details see Documentation/kdump/kdump.txt
2043 config AUTO_ZRELADDR
2044 bool "Auto calculation of the decompressed kernel image address"
2045 depends on !ZBOOT_ROM && !ARCH_U300
2047 ZRELADDR is the physical address where the decompressed kernel
2048 image will be placed. If AUTO_ZRELADDR is selected, the address
2049 will be determined at run-time by masking the current IP with
2050 0xf8000000. This assumes the zImage being placed in the first 128MB
2051 from start of memory.
2055 menu "CPU Power Management"
2059 source "drivers/cpufreq/Kconfig"
2062 tristate "CPUfreq driver for i.MX CPUs"
2063 depends on ARCH_MXC && CPU_FREQ
2065 This enables the CPUfreq driver for i.MX CPUs.
2067 config CPU_FREQ_SA1100
2070 config CPU_FREQ_SA1110
2073 config CPU_FREQ_INTEGRATOR
2074 tristate "CPUfreq driver for ARM Integrator CPUs"
2075 depends on ARCH_INTEGRATOR && CPU_FREQ
2078 This enables the CPUfreq driver for ARM Integrator CPUs.
2080 For details, take a look at <file:Documentation/cpu-freq>.
2086 depends on CPU_FREQ && ARCH_PXA && PXA25x
2088 select CPU_FREQ_TABLE
2089 select CPU_FREQ_DEFAULT_GOV_USERSPACE
2094 Internal configuration node for common cpufreq on Samsung SoC
2096 config CPU_FREQ_S3C24XX
2097 bool "CPUfreq driver for Samsung S3C24XX series CPUs (EXPERIMENTAL)"
2098 depends on ARCH_S3C2410 && CPU_FREQ && EXPERIMENTAL
2101 This enables the CPUfreq driver for the Samsung S3C24XX family
2104 For details, take a look at <file:Documentation/cpu-freq>.
2108 config CPU_FREQ_S3C24XX_PLL
2109 bool "Support CPUfreq changing of PLL frequency (EXPERIMENTAL)"
2110 depends on CPU_FREQ_S3C24XX && EXPERIMENTAL
2112 Compile in support for changing the PLL frequency from the
2113 S3C24XX series CPUfreq driver. The PLL takes time to settle
2114 after a frequency change, so by default it is not enabled.
2116 This also means that the PLL tables for the selected CPU(s) will
2117 be built which may increase the size of the kernel image.
2119 config CPU_FREQ_S3C24XX_DEBUG
2120 bool "Debug CPUfreq Samsung driver core"
2121 depends on CPU_FREQ_S3C24XX
2123 Enable s3c_freq_dbg for the Samsung S3C CPUfreq core
2125 config CPU_FREQ_S3C24XX_IODEBUG
2126 bool "Debug CPUfreq Samsung driver IO timing"
2127 depends on CPU_FREQ_S3C24XX
2129 Enable s3c_freq_iodbg for the Samsung S3C CPUfreq core
2131 config CPU_FREQ_S3C24XX_DEBUGFS
2132 bool "Export debugfs for CPUFreq"
2133 depends on CPU_FREQ_S3C24XX && DEBUG_FS
2135 Export status information via debugfs.
2139 source "drivers/cpuidle/Kconfig"
2143 menu "Floating point emulation"
2145 comment "At least one emulation must be selected"
2148 bool "NWFPE math emulation"
2149 depends on (!AEABI || OABI_COMPAT) && !THUMB2_KERNEL
2151 Say Y to include the NWFPE floating point emulator in the kernel.
2152 This is necessary to run most binaries. Linux does not currently
2153 support floating point hardware so you need to say Y here even if
2154 your machine has an FPA or floating point co-processor podule.
2156 You may say N here if you are going to load the Acorn FPEmulator
2157 early in the bootup.
2160 bool "Support extended precision"
2161 depends on FPE_NWFPE
2163 Say Y to include 80-bit support in the kernel floating-point
2164 emulator. Otherwise, only 32 and 64-bit support is compiled in.
2165 Note that gcc does not generate 80-bit operations by default,
2166 so in most cases this option only enlarges the size of the
2167 floating point emulator without any good reason.
2169 You almost surely want to say N here.
2172 bool "FastFPE math emulation (EXPERIMENTAL)"
2173 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
2175 Say Y here to include the FAST floating point emulator in the kernel.
2176 This is an experimental much faster emulator which now also has full
2177 precision for the mantissa. It does not support any exceptions.
2178 It is very simple, and approximately 3-6 times faster than NWFPE.
2180 It should be sufficient for most programs. It may be not suitable
2181 for scientific calculations, but you have to check this for yourself.
2182 If you do not feel you need a faster FP emulation you should better
2186 bool "VFP-format floating point maths"
2187 depends on CPU_V6 || CPU_V6K || CPU_ARM926T || CPU_V7 || CPU_FEROCEON
2189 Say Y to include VFP support code in the kernel. This is needed
2190 if your hardware includes a VFP unit.
2192 Please see <file:Documentation/arm/VFP/release-notes.txt> for
2193 release notes and additional status information.
2195 Say N if your target does not have VFP hardware.
2203 bool "Advanced SIMD (NEON) Extension support"
2204 depends on VFPv3 && CPU_V7
2206 Say Y to include support code for NEON, the ARMv7 Advanced SIMD
2211 menu "Userspace binary formats"
2213 source "fs/Kconfig.binfmt"
2216 tristate "RISC OS personality"
2219 Say Y here to include the kernel code necessary if you want to run
2220 Acorn RISC OS/Arthur binaries under Linux. This code is still very
2221 experimental; if this sounds frightening, say N and sleep in peace.
2222 You can also say M here to compile this support as a module (which
2223 will be called arthur).
2227 menu "Power management options"
2229 source "kernel/power/Kconfig"
2231 config ARCH_SUSPEND_POSSIBLE
2232 depends on !ARCH_S5PC100
2233 depends on CPU_ARM920T || CPU_ARM926T || CPU_SA1100 || \
2234 CPU_V6 || CPU_V6K || CPU_V7 || CPU_XSC3 || CPU_XSCALE
2237 config ARM_CPU_SUSPEND
2242 source "net/Kconfig"
2244 source "drivers/Kconfig"
2248 source "arch/arm/Kconfig.debug"
2250 source "security/Kconfig"
2252 source "crypto/Kconfig"
2254 source "lib/Kconfig"