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" if MMU
224 depends on !ARM_PATCH_PHYS_VIRT && !NEED_MACH_MEMORY_H
225 default DRAM_BASE if !MMU
227 Please provide the physical address corresponding to the
228 location of main memory in your system.
234 source "init/Kconfig"
236 source "kernel/Kconfig.freezer"
241 bool "MMU-based Paged Memory Management Support"
244 Select if you want MMU-based virtualised addressing space
245 support by paged memory management. If unsure, say 'Y'.
248 # The "ARM system type" choice list is ordered alphabetically by option
249 # text. Please add new entries in the option alphabetic order.
252 prompt "ARM system type"
253 default ARCH_VERSATILE
255 config ARCH_INTEGRATOR
256 bool "ARM Ltd. Integrator family"
258 select ARCH_HAS_CPUFREQ
260 select HAVE_MACH_CLKDEV
263 select GENERIC_CLOCKEVENTS
264 select PLAT_VERSATILE
265 select PLAT_VERSATILE_FPGA_IRQ
266 select NEED_MACH_MEMORY_H
268 Support for ARM's Integrator platform.
271 bool "ARM Ltd. RealView family"
274 select HAVE_MACH_CLKDEV
276 select GENERIC_CLOCKEVENTS
277 select ARCH_WANT_OPTIONAL_GPIOLIB
278 select PLAT_VERSATILE
279 select PLAT_VERSATILE_CLCD
280 select ARM_TIMER_SP804
281 select GPIO_PL061 if GPIOLIB
282 select NEED_MACH_MEMORY_H
284 This enables support for ARM Ltd RealView boards.
286 config ARCH_VERSATILE
287 bool "ARM Ltd. Versatile family"
291 select HAVE_MACH_CLKDEV
293 select GENERIC_CLOCKEVENTS
294 select ARCH_WANT_OPTIONAL_GPIOLIB
295 select PLAT_VERSATILE
296 select PLAT_VERSATILE_CLCD
297 select PLAT_VERSATILE_FPGA_IRQ
298 select ARM_TIMER_SP804
300 This enables support for ARM Ltd Versatile board.
303 bool "ARM Ltd. Versatile Express family"
304 select ARCH_WANT_OPTIONAL_GPIOLIB
306 select ARM_TIMER_SP804
308 select HAVE_MACH_CLKDEV
309 select GENERIC_CLOCKEVENTS
311 select HAVE_PATA_PLATFORM
313 select PLAT_VERSATILE
314 select PLAT_VERSATILE_CLCD
316 This enables support for the ARM Ltd Versatile Express boards.
320 select ARCH_REQUIRE_GPIOLIB
324 This enables support for systems based on the Atmel AT91RM9200,
325 AT91SAM9 and AT91CAP9 processors.
328 bool "Broadcom BCMRING"
332 select ARM_TIMER_SP804
334 select GENERIC_CLOCKEVENTS
335 select ARCH_WANT_OPTIONAL_GPIOLIB
337 Support for Broadcom's BCMRing platform.
340 bool "Calxeda Highbank-based"
341 select ARCH_WANT_OPTIONAL_GPIOLIB
344 select ARM_TIMER_SP804
348 select GENERIC_CLOCKEVENTS
353 Support for the Calxeda Highbank SoC based boards.
356 bool "Cirrus Logic CLPS711x/EP721x-based"
358 select ARCH_USES_GETTIMEOFFSET
359 select NEED_MACH_MEMORY_H
361 Support for Cirrus Logic 711x/721x based boards.
364 bool "Cavium Networks CNS3XXX family"
366 select GENERIC_CLOCKEVENTS
368 select MIGHT_HAVE_CACHE_L2X0
369 select MIGHT_HAVE_PCI
370 select PCI_DOMAINS if PCI
372 Support for Cavium Networks CNS3XXX platform.
375 bool "Cortina Systems Gemini"
377 select ARCH_REQUIRE_GPIOLIB
378 select ARCH_USES_GETTIMEOFFSET
380 Support for the Cortina Systems Gemini family SoCs
383 bool "CSR SiRFSoC PRIMA2 ARM Cortex A9 Platform"
386 select GENERIC_CLOCKEVENTS
388 select GENERIC_IRQ_CHIP
389 select MIGHT_HAVE_CACHE_L2X0
393 Support for CSR SiRFSoC ARM Cortex A9 Platform
400 select ARCH_USES_GETTIMEOFFSET
401 select NEED_MACH_MEMORY_H
403 This is an evaluation board for the StrongARM processor available
404 from Digital. It has limited hardware on-board, including an
405 Ethernet interface, two PCMCIA sockets, two serial ports and a
414 select ARCH_REQUIRE_GPIOLIB
415 select ARCH_HAS_HOLES_MEMORYMODEL
416 select ARCH_USES_GETTIMEOFFSET
417 select NEED_MACH_MEMORY_H
419 This enables support for the Cirrus EP93xx series of CPUs.
421 config ARCH_FOOTBRIDGE
425 select GENERIC_CLOCKEVENTS
427 select NEED_MACH_MEMORY_H
429 Support for systems based on the DC21285 companion chip
430 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
433 bool "Freescale MXC/iMX-based"
434 select GENERIC_CLOCKEVENTS
435 select ARCH_REQUIRE_GPIOLIB
438 select GENERIC_IRQ_CHIP
439 select HAVE_SCHED_CLOCK
440 select MULTI_IRQ_HANDLER
442 Support for Freescale MXC/iMX-based family of processors
445 bool "Freescale MXS-based"
446 select GENERIC_CLOCKEVENTS
447 select ARCH_REQUIRE_GPIOLIB
451 Support for Freescale MXS-based family of processors
454 bool "Hilscher NetX based"
458 select GENERIC_CLOCKEVENTS
460 This enables support for systems based on the Hilscher NetX Soc
463 bool "Hynix HMS720x-based"
466 select ARCH_USES_GETTIMEOFFSET
468 This enables support for systems based on the Hynix HMS720x
476 select ARCH_SUPPORTS_MSI
478 select NEED_MACH_MEMORY_H
480 Support for Intel's IOP13XX (XScale) family of processors.
488 select ARCH_REQUIRE_GPIOLIB
490 Support for Intel's 80219 and IOP32X (XScale) family of
499 select ARCH_REQUIRE_GPIOLIB
501 Support for Intel's IOP33X (XScale) family of processors.
508 select ARCH_USES_GETTIMEOFFSET
509 select NEED_MACH_MEMORY_H
511 Support for Intel's IXP23xx (XScale) family of processors.
514 bool "IXP2400/2800-based"
518 select ARCH_USES_GETTIMEOFFSET
519 select NEED_MACH_MEMORY_H
521 Support for Intel's IXP2400/2800 (XScale) family of processors.
529 select GENERIC_CLOCKEVENTS
530 select HAVE_SCHED_CLOCK
531 select MIGHT_HAVE_PCI
532 select DMABOUNCE if PCI
534 Support for Intel's IXP4XX (XScale) family of processors.
540 select ARCH_REQUIRE_GPIOLIB
541 select GENERIC_CLOCKEVENTS
544 Support for the Marvell Dove SoC 88AP510
547 bool "Marvell Kirkwood"
550 select ARCH_REQUIRE_GPIOLIB
551 select GENERIC_CLOCKEVENTS
554 Support for the following Marvell Kirkwood series SoCs:
555 88F6180, 88F6192 and 88F6281.
561 select ARCH_REQUIRE_GPIOLIB
564 select USB_ARCH_HAS_OHCI
566 select GENERIC_CLOCKEVENTS
568 Support for the NXP LPC32XX family of processors
571 bool "Marvell MV78xx0"
574 select ARCH_REQUIRE_GPIOLIB
575 select GENERIC_CLOCKEVENTS
578 Support for the following Marvell MV78xx0 series SoCs:
586 select ARCH_REQUIRE_GPIOLIB
587 select GENERIC_CLOCKEVENTS
590 Support for the following Marvell Orion 5x series SoCs:
591 Orion-1 (5181), Orion-VoIP (5181L), Orion-NAS (5182),
592 Orion-2 (5281), Orion-1-90 (6183).
595 bool "Marvell PXA168/910/MMP2"
597 select ARCH_REQUIRE_GPIOLIB
599 select GENERIC_CLOCKEVENTS
600 select HAVE_SCHED_CLOCK
604 select GENERIC_ALLOCATOR
606 Support for Marvell's PXA168/PXA910(MMP) and MMP2 processor line.
609 bool "Micrel/Kendin KS8695"
611 select ARCH_REQUIRE_GPIOLIB
612 select ARCH_USES_GETTIMEOFFSET
613 select NEED_MACH_MEMORY_H
615 Support for Micrel/Kendin KS8695 "Centaur" (ARM922T) based
616 System-on-Chip devices.
619 bool "Nuvoton W90X900 CPU"
621 select ARCH_REQUIRE_GPIOLIB
624 select GENERIC_CLOCKEVENTS
626 Support for Nuvoton (Winbond logic dept.) ARM9 processor,
627 At present, the w90x900 has been renamed nuc900, regarding
628 the ARM series product line, you can login the following
629 link address to know more.
631 <http://www.nuvoton.com/hq/enu/ProductAndSales/ProductLines/
632 ConsumerElectronicsIC/ARMMicrocontroller/ARMMicrocontroller>
638 select GENERIC_CLOCKEVENTS
641 select HAVE_SCHED_CLOCK
643 select MIGHT_HAVE_CACHE_L2X0
644 select ARCH_HAS_CPUFREQ
646 This enables support for NVIDIA Tegra based systems (Tegra APX,
647 Tegra 6xx and Tegra 2 series).
649 config ARCH_PICOXCELL
650 bool "Picochip picoXcell"
651 select ARCH_REQUIRE_GPIOLIB
652 select ARM_PATCH_PHYS_VIRT
656 select GENERIC_CLOCKEVENTS
658 select HAVE_SCHED_CLOCK
663 This enables support for systems based on the Picochip picoXcell
664 family of Femtocell devices. The picoxcell support requires device tree
668 bool "Philips Nexperia PNX4008 Mobile"
671 select ARCH_USES_GETTIMEOFFSET
673 This enables support for Philips PNX4008 mobile platform.
676 bool "PXA2xx/PXA3xx-based"
679 select ARCH_HAS_CPUFREQ
682 select ARCH_REQUIRE_GPIOLIB
683 select GENERIC_CLOCKEVENTS
684 select HAVE_SCHED_CLOCK
689 select MULTI_IRQ_HANDLER
690 select ARM_CPU_SUSPEND if PM
693 Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
698 select GENERIC_CLOCKEVENTS
699 select ARCH_REQUIRE_GPIOLIB
702 Support for Qualcomm MSM/QSD based systems. This runs on the
703 apps processor of the MSM/QSD and depends on a shared memory
704 interface to the modem processor which runs the baseband
705 stack and controls some vital subsystems
706 (clock and power control, etc).
709 bool "Renesas SH-Mobile / R-Mobile"
712 select HAVE_MACH_CLKDEV
714 select GENERIC_CLOCKEVENTS
715 select MIGHT_HAVE_CACHE_L2X0
718 select MULTI_IRQ_HANDLER
719 select PM_GENERIC_DOMAINS if PM
720 select NEED_MACH_MEMORY_H
722 Support for Renesas's SH-Mobile and R-Mobile ARM platforms.
729 select ARCH_MAY_HAVE_PC_FDC
730 select HAVE_PATA_PLATFORM
733 select ARCH_SPARSEMEM_ENABLE
734 select ARCH_USES_GETTIMEOFFSET
736 select NEED_MACH_MEMORY_H
738 On the Acorn Risc-PC, Linux can support the internal IDE disk and
739 CD-ROM interface, serial and parallel port, and the floppy drive.
746 select ARCH_SPARSEMEM_ENABLE
748 select ARCH_HAS_CPUFREQ
750 select GENERIC_CLOCKEVENTS
752 select HAVE_SCHED_CLOCK
754 select ARCH_REQUIRE_GPIOLIB
756 select NEED_MACH_MEMORY_H
758 Support for StrongARM 11x0 based boards.
761 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2416, S3C2440, S3C2442, S3C2443, S3C2450"
763 select ARCH_HAS_CPUFREQ
766 select ARCH_USES_GETTIMEOFFSET
767 select HAVE_S3C2410_I2C if I2C
769 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
770 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
771 the Samsung SMDK2410 development board (and derivatives).
773 Note, the S3C2416 and the S3C2450 are so close that they even share
774 the same SoC ID code. This means that there is no separate machine
775 directory (no arch/arm/mach-s3c2450) as the S3C2416 was first.
778 bool "Samsung S3C64XX"
786 select ARCH_USES_GETTIMEOFFSET
787 select ARCH_HAS_CPUFREQ
788 select ARCH_REQUIRE_GPIOLIB
789 select SAMSUNG_CLKSRC
790 select SAMSUNG_IRQ_VIC_TIMER
791 select S3C_GPIO_TRACK
793 select USB_ARCH_HAS_OHCI
794 select SAMSUNG_GPIOLIB_4BIT
795 select HAVE_S3C2410_I2C if I2C
796 select HAVE_S3C2410_WATCHDOG if WATCHDOG
798 Samsung S3C64XX series based systems
801 bool "Samsung S5P6440 S5P6450"
807 select HAVE_S3C2410_WATCHDOG if WATCHDOG
808 select GENERIC_CLOCKEVENTS
809 select HAVE_SCHED_CLOCK
810 select HAVE_S3C2410_I2C if I2C
811 select HAVE_S3C_RTC if RTC_CLASS
813 Samsung S5P64X0 CPU based systems, such as the Samsung SMDK6440,
817 bool "Samsung S5PC100"
822 select ARM_L1_CACHE_SHIFT_6
823 select ARCH_USES_GETTIMEOFFSET
824 select HAVE_S3C2410_I2C if I2C
825 select HAVE_S3C_RTC if RTC_CLASS
826 select HAVE_S3C2410_WATCHDOG if WATCHDOG
828 Samsung S5PC100 series based systems
831 bool "Samsung S5PV210/S5PC110"
833 select ARCH_SPARSEMEM_ENABLE
834 select ARCH_HAS_HOLES_MEMORYMODEL
839 select ARM_L1_CACHE_SHIFT_6
840 select ARCH_HAS_CPUFREQ
841 select GENERIC_CLOCKEVENTS
842 select HAVE_SCHED_CLOCK
843 select HAVE_S3C2410_I2C if I2C
844 select HAVE_S3C_RTC if RTC_CLASS
845 select HAVE_S3C2410_WATCHDOG if WATCHDOG
846 select NEED_MACH_MEMORY_H
848 Samsung S5PV210/S5PC110 series based systems
851 bool "SAMSUNG EXYNOS"
853 select ARCH_SPARSEMEM_ENABLE
854 select ARCH_HAS_HOLES_MEMORYMODEL
858 select ARCH_HAS_CPUFREQ
859 select GENERIC_CLOCKEVENTS
860 select HAVE_S3C_RTC if RTC_CLASS
861 select HAVE_S3C2410_I2C if I2C
862 select HAVE_S3C2410_WATCHDOG if WATCHDOG
863 select NEED_MACH_MEMORY_H
865 Support for SAMSUNG's EXYNOS SoCs (EXYNOS4/5)
874 select ARCH_USES_GETTIMEOFFSET
875 select NEED_MACH_MEMORY_H
877 Support for the StrongARM based Digital DNARD machine, also known
878 as "Shark" (<http://www.shark-linux.de/shark.html>).
881 bool "ST-Ericsson U300 Series"
885 select HAVE_SCHED_CLOCK
888 select ARM_PATCH_PHYS_VIRT
890 select GENERIC_CLOCKEVENTS
892 select HAVE_MACH_CLKDEV
894 select ARCH_REQUIRE_GPIOLIB
895 select NEED_MACH_MEMORY_H
897 Support for ST-Ericsson U300 series mobile platforms.
900 bool "ST-Ericsson U8500 Series"
903 select GENERIC_CLOCKEVENTS
905 select ARCH_REQUIRE_GPIOLIB
906 select ARCH_HAS_CPUFREQ
908 select MIGHT_HAVE_CACHE_L2X0
910 Support for ST-Ericsson's Ux500 architecture
913 bool "STMicroelectronics Nomadik"
918 select GENERIC_CLOCKEVENTS
919 select MIGHT_HAVE_CACHE_L2X0
920 select ARCH_REQUIRE_GPIOLIB
922 Support for the Nomadik platform by ST-Ericsson
926 select GENERIC_CLOCKEVENTS
927 select ARCH_REQUIRE_GPIOLIB
931 select GENERIC_ALLOCATOR
932 select GENERIC_IRQ_CHIP
933 select ARCH_HAS_HOLES_MEMORYMODEL
935 Support for TI's DaVinci platform.
940 select ARCH_REQUIRE_GPIOLIB
941 select ARCH_HAS_CPUFREQ
943 select GENERIC_CLOCKEVENTS
944 select HAVE_SCHED_CLOCK
945 select ARCH_HAS_HOLES_MEMORYMODEL
947 Support for TI's OMAP platform (OMAP1/2/3/4).
952 select ARCH_REQUIRE_GPIOLIB
955 select GENERIC_CLOCKEVENTS
958 Support for ST's SPEAr platform (SPEAr3xx, SPEAr6xx and SPEAr13xx).
961 bool "VIA/WonderMedia 85xx"
964 select ARCH_HAS_CPUFREQ
965 select GENERIC_CLOCKEVENTS
966 select ARCH_REQUIRE_GPIOLIB
969 Support for VIA/WonderMedia VT8500/WM85xx System-on-Chip.
972 bool "Xilinx Zynq ARM Cortex A9 Platform"
974 select GENERIC_CLOCKEVENTS
979 select MIGHT_HAVE_CACHE_L2X0
982 Support for Xilinx Zynq ARM Cortex A9 Platform
986 # This is sorted alphabetically by mach-* pathname. However, plat-*
987 # Kconfigs may be included either alphabetically (according to the
988 # plat- suffix) or along side the corresponding mach-* source.
990 source "arch/arm/mach-at91/Kconfig"
992 source "arch/arm/mach-bcmring/Kconfig"
994 source "arch/arm/mach-clps711x/Kconfig"
996 source "arch/arm/mach-cns3xxx/Kconfig"
998 source "arch/arm/mach-davinci/Kconfig"
1000 source "arch/arm/mach-dove/Kconfig"
1002 source "arch/arm/mach-ep93xx/Kconfig"
1004 source "arch/arm/mach-footbridge/Kconfig"
1006 source "arch/arm/mach-gemini/Kconfig"
1008 source "arch/arm/mach-h720x/Kconfig"
1010 source "arch/arm/mach-integrator/Kconfig"
1012 source "arch/arm/mach-iop32x/Kconfig"
1014 source "arch/arm/mach-iop33x/Kconfig"
1016 source "arch/arm/mach-iop13xx/Kconfig"
1018 source "arch/arm/mach-ixp4xx/Kconfig"
1020 source "arch/arm/mach-ixp2000/Kconfig"
1022 source "arch/arm/mach-ixp23xx/Kconfig"
1024 source "arch/arm/mach-kirkwood/Kconfig"
1026 source "arch/arm/mach-ks8695/Kconfig"
1028 source "arch/arm/mach-lpc32xx/Kconfig"
1030 source "arch/arm/mach-msm/Kconfig"
1032 source "arch/arm/mach-mv78xx0/Kconfig"
1034 source "arch/arm/plat-mxc/Kconfig"
1036 source "arch/arm/mach-mxs/Kconfig"
1038 source "arch/arm/mach-netx/Kconfig"
1040 source "arch/arm/mach-nomadik/Kconfig"
1041 source "arch/arm/plat-nomadik/Kconfig"
1043 source "arch/arm/plat-omap/Kconfig"
1045 source "arch/arm/mach-omap1/Kconfig"
1047 source "arch/arm/mach-omap2/Kconfig"
1049 source "arch/arm/mach-orion5x/Kconfig"
1051 source "arch/arm/mach-pxa/Kconfig"
1052 source "arch/arm/plat-pxa/Kconfig"
1054 source "arch/arm/mach-mmp/Kconfig"
1056 source "arch/arm/mach-realview/Kconfig"
1058 source "arch/arm/mach-sa1100/Kconfig"
1060 source "arch/arm/plat-samsung/Kconfig"
1061 source "arch/arm/plat-s3c24xx/Kconfig"
1062 source "arch/arm/plat-s5p/Kconfig"
1064 source "arch/arm/plat-spear/Kconfig"
1067 source "arch/arm/mach-s3c2410/Kconfig"
1068 source "arch/arm/mach-s3c2412/Kconfig"
1069 source "arch/arm/mach-s3c2416/Kconfig"
1070 source "arch/arm/mach-s3c2440/Kconfig"
1071 source "arch/arm/mach-s3c2443/Kconfig"
1075 source "arch/arm/mach-s3c64xx/Kconfig"
1078 source "arch/arm/mach-s5p64x0/Kconfig"
1080 source "arch/arm/mach-s5pc100/Kconfig"
1082 source "arch/arm/mach-s5pv210/Kconfig"
1084 source "arch/arm/mach-exynos/Kconfig"
1086 source "arch/arm/mach-shmobile/Kconfig"
1088 source "arch/arm/mach-tegra/Kconfig"
1090 source "arch/arm/mach-u300/Kconfig"
1092 source "arch/arm/mach-ux500/Kconfig"
1094 source "arch/arm/mach-versatile/Kconfig"
1096 source "arch/arm/mach-vexpress/Kconfig"
1097 source "arch/arm/plat-versatile/Kconfig"
1099 source "arch/arm/mach-vt8500/Kconfig"
1101 source "arch/arm/mach-w90x900/Kconfig"
1103 # Definitions to make life easier
1109 select GENERIC_CLOCKEVENTS
1110 select HAVE_SCHED_CLOCK
1115 select GENERIC_IRQ_CHIP
1116 select HAVE_SCHED_CLOCK
1121 config PLAT_VERSATILE
1124 config ARM_TIMER_SP804
1128 source arch/arm/mm/Kconfig
1132 default 16 if ARCH_EP93XX
1136 bool "Enable iWMMXt support"
1137 depends on CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_PJ4
1138 default y if PXA27x || PXA3xx || PXA95x || ARCH_MMP
1140 Enable support for iWMMXt context switching at run time if
1141 running on a CPU that supports it.
1145 depends on CPU_XSCALE
1149 depends on (CPU_V6 || CPU_V6K || CPU_V7 || XSCALE_PMU) && \
1150 (!ARCH_OMAP3 || OMAP3_EMU)
1154 config MULTI_IRQ_HANDLER
1157 Allow each machine to specify it's own IRQ handler at run time.
1160 source "arch/arm/Kconfig-nommu"
1163 config ARM_ERRATA_411920
1164 bool "ARM errata: Invalidation of the Instruction Cache operation can fail"
1165 depends on CPU_V6 || CPU_V6K
1167 Invalidation of the Instruction Cache operation can
1168 fail. This erratum is present in 1136 (before r1p4), 1156 and 1176.
1169 It does not affect the MPCore. This option enables the ARM Ltd.
1170 recommended workaround.
1172 config ARM_ERRATA_430973
1173 bool "ARM errata: Stale prediction on replaced interworking branch"
1176 This option enables the workaround for the 430973 Cortex-A8
1177 (r1p0..r1p2) erratum. If a code sequence containing an ARM/Thumb
1178 interworking branch is replaced with another code sequence at the
1179 same virtual address, whether due to self-modifying code or virtual
1180 to physical address re-mapping, Cortex-A8 does not recover from the
1181 stale interworking branch prediction. This results in Cortex-A8
1182 executing the new code sequence in the incorrect ARM or Thumb state.
1183 The workaround enables the BTB/BTAC operations by setting ACTLR.IBE
1184 and also flushes the branch target cache at every context switch.
1185 Note that setting specific bits in the ACTLR register may not be
1186 available in non-secure mode.
1188 config ARM_ERRATA_458693
1189 bool "ARM errata: Processor deadlock when a false hazard is created"
1192 This option enables the workaround for the 458693 Cortex-A8 (r2p0)
1193 erratum. For very specific sequences of memory operations, it is
1194 possible for a hazard condition intended for a cache line to instead
1195 be incorrectly associated with a different cache line. This false
1196 hazard might then cause a processor deadlock. The workaround enables
1197 the L1 caching of the NEON accesses and disables the PLD instruction
1198 in the ACTLR register. Note that setting specific bits in the ACTLR
1199 register may not be available in non-secure mode.
1201 config ARM_ERRATA_460075
1202 bool "ARM errata: Data written to the L2 cache can be overwritten with stale data"
1205 This option enables the workaround for the 460075 Cortex-A8 (r2p0)
1206 erratum. Any asynchronous access to the L2 cache may encounter a
1207 situation in which recent store transactions to the L2 cache are lost
1208 and overwritten with stale memory contents from external memory. The
1209 workaround disables the write-allocate mode for the L2 cache via the
1210 ACTLR register. Note that setting specific bits in the ACTLR register
1211 may not be available in non-secure mode.
1213 config ARM_ERRATA_742230
1214 bool "ARM errata: DMB operation may be faulty"
1215 depends on CPU_V7 && SMP
1217 This option enables the workaround for the 742230 Cortex-A9
1218 (r1p0..r2p2) erratum. Under rare circumstances, a DMB instruction
1219 between two write operations may not ensure the correct visibility
1220 ordering of the two writes. This workaround sets a specific bit in
1221 the diagnostic register of the Cortex-A9 which causes the DMB
1222 instruction to behave as a DSB, ensuring the correct behaviour of
1225 config ARM_ERRATA_742231
1226 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
1227 depends on CPU_V7 && SMP
1229 This option enables the workaround for the 742231 Cortex-A9
1230 (r2p0..r2p2) erratum. Under certain conditions, specific to the
1231 Cortex-A9 MPCore micro-architecture, two CPUs working in SMP mode,
1232 accessing some data located in the same cache line, may get corrupted
1233 data due to bad handling of the address hazard when the line gets
1234 replaced from one of the CPUs at the same time as another CPU is
1235 accessing it. This workaround sets specific bits in the diagnostic
1236 register of the Cortex-A9 which reduces the linefill issuing
1237 capabilities of the processor.
1239 config PL310_ERRATA_588369
1240 bool "PL310 errata: Clean & Invalidate maintenance operations do not invalidate clean lines"
1241 depends on CACHE_L2X0
1243 The PL310 L2 cache controller implements three types of Clean &
1244 Invalidate maintenance operations: by Physical Address
1245 (offset 0x7F0), by Index/Way (0x7F8) and by Way (0x7FC).
1246 They are architecturally defined to behave as the execution of a
1247 clean operation followed immediately by an invalidate operation,
1248 both performing to the same memory location. This functionality
1249 is not correctly implemented in PL310 as clean lines are not
1250 invalidated as a result of these operations.
1252 config ARM_ERRATA_720789
1253 bool "ARM errata: TLBIASIDIS and TLBIMVAIS operations can broadcast a faulty ASID"
1256 This option enables the workaround for the 720789 Cortex-A9 (prior to
1257 r2p0) erratum. A faulty ASID can be sent to the other CPUs for the
1258 broadcasted CP15 TLB maintenance operations TLBIASIDIS and TLBIMVAIS.
1259 As a consequence of this erratum, some TLB entries which should be
1260 invalidated are not, resulting in an incoherency in the system page
1261 tables. The workaround changes the TLB flushing routines to invalidate
1262 entries regardless of the ASID.
1264 config PL310_ERRATA_727915
1265 bool "PL310 errata: Background Clean & Invalidate by Way operation can cause data corruption"
1266 depends on CACHE_L2X0
1268 PL310 implements the Clean & Invalidate by Way L2 cache maintenance
1269 operation (offset 0x7FC). This operation runs in background so that
1270 PL310 can handle normal accesses while it is in progress. Under very
1271 rare circumstances, due to this erratum, write data can be lost when
1272 PL310 treats a cacheable write transaction during a Clean &
1273 Invalidate by Way operation.
1275 config ARM_ERRATA_743622
1276 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
1279 This option enables the workaround for the 743622 Cortex-A9
1280 (r2p0..r2p2) erratum. Under very rare conditions, a faulty
1281 optimisation in the Cortex-A9 Store Buffer may lead to data
1282 corruption. This workaround sets a specific bit in the diagnostic
1283 register of the Cortex-A9 which disables the Store Buffer
1284 optimisation, preventing the defect from occurring. This has no
1285 visible impact on the overall performance or power consumption of the
1288 config ARM_ERRATA_751472
1289 bool "ARM errata: Interrupted ICIALLUIS may prevent completion of broadcasted operation"
1292 This option enables the workaround for the 751472 Cortex-A9 (prior
1293 to r3p0) erratum. An interrupted ICIALLUIS operation may prevent the
1294 completion of a following broadcasted operation if the second
1295 operation is received by a CPU before the ICIALLUIS has completed,
1296 potentially leading to corrupted entries in the cache or TLB.
1298 config PL310_ERRATA_753970
1299 bool "PL310 errata: cache sync operation may be faulty"
1300 depends on CACHE_PL310
1302 This option enables the workaround for the 753970 PL310 (r3p0) erratum.
1304 Under some condition the effect of cache sync operation on
1305 the store buffer still remains when the operation completes.
1306 This means that the store buffer is always asked to drain and
1307 this prevents it from merging any further writes. The workaround
1308 is to replace the normal offset of cache sync operation (0x730)
1309 by another offset targeting an unmapped PL310 register 0x740.
1310 This has the same effect as the cache sync operation: store buffer
1311 drain and waiting for all buffers empty.
1313 config ARM_ERRATA_754322
1314 bool "ARM errata: possible faulty MMU translations following an ASID switch"
1317 This option enables the workaround for the 754322 Cortex-A9 (r2p*,
1318 r3p*) erratum. A speculative memory access may cause a page table walk
1319 which starts prior to an ASID switch but completes afterwards. This
1320 can populate the micro-TLB with a stale entry which may be hit with
1321 the new ASID. This workaround places two dsb instructions in the mm
1322 switching code so that no page table walks can cross the ASID switch.
1324 config ARM_ERRATA_754327
1325 bool "ARM errata: no automatic Store Buffer drain"
1326 depends on CPU_V7 && SMP
1328 This option enables the workaround for the 754327 Cortex-A9 (prior to
1329 r2p0) erratum. The Store Buffer does not have any automatic draining
1330 mechanism and therefore a livelock may occur if an external agent
1331 continuously polls a memory location waiting to observe an update.
1332 This workaround defines cpu_relax() as smp_mb(), preventing correctly
1333 written polling loops from denying visibility of updates to memory.
1335 config ARM_ERRATA_364296
1336 bool "ARM errata: Possible cache data corruption with hit-under-miss enabled"
1337 depends on CPU_V6 && !SMP
1339 This options enables the workaround for the 364296 ARM1136
1340 r0p2 erratum (possible cache data corruption with
1341 hit-under-miss enabled). It sets the undocumented bit 31 in
1342 the auxiliary control register and the FI bit in the control
1343 register, thus disabling hit-under-miss without putting the
1344 processor into full low interrupt latency mode. ARM11MPCore
1347 config ARM_ERRATA_764369
1348 bool "ARM errata: Data cache line maintenance operation by MVA may not succeed"
1349 depends on CPU_V7 && SMP
1351 This option enables the workaround for erratum 764369
1352 affecting Cortex-A9 MPCore with two or more processors (all
1353 current revisions). Under certain timing circumstances, a data
1354 cache line maintenance operation by MVA targeting an Inner
1355 Shareable memory region may fail to proceed up to either the
1356 Point of Coherency or to the Point of Unification of the
1357 system. This workaround adds a DSB instruction before the
1358 relevant cache maintenance functions and sets a specific bit
1359 in the diagnostic control register of the SCU.
1361 config PL310_ERRATA_769419
1362 bool "PL310 errata: no automatic Store Buffer drain"
1363 depends on CACHE_L2X0
1365 On revisions of the PL310 prior to r3p2, the Store Buffer does
1366 not automatically drain. This can cause normal, non-cacheable
1367 writes to be retained when the memory system is idle, leading
1368 to suboptimal I/O performance for drivers using coherent DMA.
1369 This option adds a write barrier to the cpu_idle loop so that,
1370 on systems with an outer cache, the store buffer is drained
1375 source "arch/arm/common/Kconfig"
1385 Find out whether you have ISA slots on your motherboard. ISA is the
1386 name of a bus system, i.e. the way the CPU talks to the other stuff
1387 inside your box. Other bus systems are PCI, EISA, MicroChannel
1388 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1389 newer boards don't support it. If you have ISA, say Y, otherwise N.
1391 # Select ISA DMA controller support
1396 # Select ISA DMA interface
1401 bool "PCI support" if MIGHT_HAVE_PCI
1403 Find out whether you have a PCI motherboard. PCI is the name of a
1404 bus system, i.e. the way the CPU talks to the other stuff inside
1405 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1406 VESA. If you have PCI, say Y, otherwise N.
1412 config PCI_NANOENGINE
1413 bool "BSE nanoEngine PCI support"
1414 depends on SA1100_NANOENGINE
1416 Enable PCI on the BSE nanoEngine board.
1421 # Select the host bridge type
1422 config PCI_HOST_VIA82C505
1424 depends on PCI && ARCH_SHARK
1427 config PCI_HOST_ITE8152
1429 depends on PCI && MACH_ARMCORE
1433 source "drivers/pci/Kconfig"
1435 source "drivers/pcmcia/Kconfig"
1439 menu "Kernel Features"
1441 source "kernel/time/Kconfig"
1446 This option should be selected by machines which have an SMP-
1449 The only effect of this option is to make the SMP-related
1450 options available to the user for configuration.
1453 bool "Symmetric Multi-Processing"
1454 depends on CPU_V6K || CPU_V7
1455 depends on GENERIC_CLOCKEVENTS
1458 select USE_GENERIC_SMP_HELPERS
1459 select HAVE_ARM_SCU if !ARCH_MSM_SCORPIONMP
1461 This enables support for systems with more than one CPU. If you have
1462 a system with only one CPU, like most personal computers, say N. If
1463 you have a system with more than one CPU, say Y.
1465 If you say N here, the kernel will run on single and multiprocessor
1466 machines, but will use only one CPU of a multiprocessor machine. If
1467 you say Y here, the kernel will run on many, but not all, single
1468 processor machines. On a single processor machine, the kernel will
1469 run faster if you say N here.
1471 See also <file:Documentation/x86/i386/IO-APIC.txt>,
1472 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
1473 <http://tldp.org/HOWTO/SMP-HOWTO.html>.
1475 If you don't know what to do here, say N.
1478 bool "Allow booting SMP kernel on uniprocessor systems (EXPERIMENTAL)"
1479 depends on EXPERIMENTAL
1480 depends on SMP && !XIP_KERNEL
1483 SMP kernels contain instructions which fail on non-SMP processors.
1484 Enabling this option allows the kernel to modify itself to make
1485 these instructions safe. Disabling it allows about 1K of space
1488 If you don't know what to do here, say Y.
1490 config ARM_CPU_TOPOLOGY
1491 bool "Support cpu topology definition"
1492 depends on SMP && CPU_V7
1495 Support ARM cpu topology definition. The MPIDR register defines
1496 affinity between processors which is then used to describe the cpu
1497 topology of an ARM System.
1500 bool "Multi-core scheduler support"
1501 depends on ARM_CPU_TOPOLOGY
1503 Multi-core scheduler support improves the CPU scheduler's decision
1504 making when dealing with multi-core CPU chips at a cost of slightly
1505 increased overhead in some places. If unsure say N here.
1508 bool "SMT scheduler support"
1509 depends on ARM_CPU_TOPOLOGY
1511 Improves the CPU scheduler's decision making when dealing with
1512 MultiThreading at a cost of slightly increased overhead in some
1513 places. If unsure say N here.
1518 This option enables support for the ARM system coherency unit
1525 This options enables support for the ARM timer and watchdog unit
1528 prompt "Memory split"
1531 Select the desired split between kernel and user memory.
1533 If you are not absolutely sure what you are doing, leave this
1537 bool "3G/1G user/kernel split"
1539 bool "2G/2G user/kernel split"
1541 bool "1G/3G user/kernel split"
1546 default 0x40000000 if VMSPLIT_1G
1547 default 0x80000000 if VMSPLIT_2G
1551 int "Maximum number of CPUs (2-32)"
1557 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
1558 depends on SMP && HOTPLUG && EXPERIMENTAL
1560 Say Y here to experiment with turning CPUs off and on. CPUs
1561 can be controlled through /sys/devices/system/cpu.
1564 bool "Use local timer interrupts"
1567 select HAVE_ARM_TWD if (!ARCH_MSM_SCORPIONMP && !EXYNOS4_MCT)
1569 Enable support for local timers on SMP platforms, rather then the
1570 legacy IPI broadcast method. Local timers allows the system
1571 accounting to be spread across the timer interval, preventing a
1572 "thundering herd" at every timer tick.
1576 default 1024 if ARCH_SHMOBILE || ARCH_TEGRA
1577 default 350 if ARCH_U8500
1580 Maximum number of GPIOs in the system.
1582 If unsure, leave the default value.
1584 source kernel/Kconfig.preempt
1588 default 200 if ARCH_EBSA110 || ARCH_S3C2410 || ARCH_S5P64X0 || \
1589 ARCH_S5PV210 || ARCH_EXYNOS4
1590 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
1591 default AT91_TIMER_HZ if ARCH_AT91
1592 default SHMOBILE_TIMER_HZ if ARCH_SHMOBILE
1595 config THUMB2_KERNEL
1596 bool "Compile the kernel in Thumb-2 mode (EXPERIMENTAL)"
1597 depends on CPU_V7 && !CPU_V6 && !CPU_V6K && EXPERIMENTAL
1599 select ARM_ASM_UNIFIED
1602 By enabling this option, the kernel will be compiled in
1603 Thumb-2 mode. A compiler/assembler that understand the unified
1604 ARM-Thumb syntax is needed.
1608 config THUMB2_AVOID_R_ARM_THM_JUMP11
1609 bool "Work around buggy Thumb-2 short branch relocations in gas"
1610 depends on THUMB2_KERNEL && MODULES
1613 Various binutils versions can resolve Thumb-2 branches to
1614 locally-defined, preemptible global symbols as short-range "b.n"
1615 branch instructions.
1617 This is a problem, because there's no guarantee the final
1618 destination of the symbol, or any candidate locations for a
1619 trampoline, are within range of the branch. For this reason, the
1620 kernel does not support fixing up the R_ARM_THM_JUMP11 (102)
1621 relocation in modules at all, and it makes little sense to add
1624 The symptom is that the kernel fails with an "unsupported
1625 relocation" error when loading some modules.
1627 Until fixed tools are available, passing
1628 -fno-optimize-sibling-calls to gcc should prevent gcc generating
1629 code which hits this problem, at the cost of a bit of extra runtime
1630 stack usage in some cases.
1632 The problem is described in more detail at:
1633 https://bugs.launchpad.net/binutils-linaro/+bug/725126
1635 Only Thumb-2 kernels are affected.
1637 Unless you are sure your tools don't have this problem, say Y.
1639 config ARM_ASM_UNIFIED
1643 bool "Use the ARM EABI to compile the kernel"
1645 This option allows for the kernel to be compiled using the latest
1646 ARM ABI (aka EABI). This is only useful if you are using a user
1647 space environment that is also compiled with EABI.
1649 Since there are major incompatibilities between the legacy ABI and
1650 EABI, especially with regard to structure member alignment, this
1651 option also changes the kernel syscall calling convention to
1652 disambiguate both ABIs and allow for backward compatibility support
1653 (selected with CONFIG_OABI_COMPAT).
1655 To use this you need GCC version 4.0.0 or later.
1658 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
1659 depends on AEABI && EXPERIMENTAL && !THUMB2_KERNEL
1662 This option preserves the old syscall interface along with the
1663 new (ARM EABI) one. It also provides a compatibility layer to
1664 intercept syscalls that have structure arguments which layout
1665 in memory differs between the legacy ABI and the new ARM EABI
1666 (only for non "thumb" binaries). This option adds a tiny
1667 overhead to all syscalls and produces a slightly larger kernel.
1668 If you know you'll be using only pure EABI user space then you
1669 can say N here. If this option is not selected and you attempt
1670 to execute a legacy ABI binary then the result will be
1671 UNPREDICTABLE (in fact it can be predicted that it won't work
1672 at all). If in doubt say Y.
1674 config ARCH_HAS_HOLES_MEMORYMODEL
1677 config ARCH_SPARSEMEM_ENABLE
1680 config ARCH_SPARSEMEM_DEFAULT
1681 def_bool ARCH_SPARSEMEM_ENABLE
1683 config ARCH_SELECT_MEMORY_MODEL
1684 def_bool ARCH_SPARSEMEM_ENABLE
1686 config HAVE_ARCH_PFN_VALID
1687 def_bool ARCH_HAS_HOLES_MEMORYMODEL || !SPARSEMEM
1690 bool "High Memory Support"
1693 The address space of ARM processors is only 4 Gigabytes large
1694 and it has to accommodate user address space, kernel address
1695 space as well as some memory mapped IO. That means that, if you
1696 have a large amount of physical memory and/or IO, not all of the
1697 memory can be "permanently mapped" by the kernel. The physical
1698 memory that is not permanently mapped is called "high memory".
1700 Depending on the selected kernel/user memory split, minimum
1701 vmalloc space and actual amount of RAM, you may not need this
1702 option which should result in a slightly faster kernel.
1707 bool "Allocate 2nd-level pagetables from highmem"
1710 config HW_PERF_EVENTS
1711 bool "Enable hardware performance counter support for perf events"
1712 depends on PERF_EVENTS && CPU_HAS_PMU
1715 Enable hardware performance counter support for perf events. If
1716 disabled, perf events will use software events only.
1720 config FORCE_MAX_ZONEORDER
1721 int "Maximum zone order" if ARCH_SHMOBILE
1722 range 11 64 if ARCH_SHMOBILE
1723 default "9" if SA1111
1726 The kernel memory allocator divides physically contiguous memory
1727 blocks into "zones", where each zone is a power of two number of
1728 pages. This option selects the largest power of two that the kernel
1729 keeps in the memory allocator. If you need to allocate very large
1730 blocks of physically contiguous memory, then you may need to
1731 increase this value.
1733 This config option is actually maximum order plus one. For example,
1734 a value of 11 means that the largest free memory block is 2^10 pages.
1737 bool "Timer and CPU usage LEDs"
1738 depends on ARCH_CDB89712 || ARCH_EBSA110 || \
1739 ARCH_EBSA285 || ARCH_INTEGRATOR || \
1740 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
1741 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
1742 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
1743 ARCH_AT91 || ARCH_DAVINCI || \
1744 ARCH_KS8695 || MACH_RD88F5182 || ARCH_REALVIEW
1746 If you say Y here, the LEDs on your machine will be used
1747 to provide useful information about your current system status.
1749 If you are compiling a kernel for a NetWinder or EBSA-285, you will
1750 be able to select which LEDs are active using the options below. If
1751 you are compiling a kernel for the EBSA-110 or the LART however, the
1752 red LED will simply flash regularly to indicate that the system is
1753 still functional. It is safe to say Y here if you have a CATS
1754 system, but the driver will do nothing.
1757 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
1758 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1759 || MACH_OMAP_PERSEUS2
1761 depends on !GENERIC_CLOCKEVENTS
1762 default y if ARCH_EBSA110
1764 If you say Y here, one of the system LEDs (the green one on the
1765 NetWinder, the amber one on the EBSA285, or the red one on the LART)
1766 will flash regularly to indicate that the system is still
1767 operational. This is mainly useful to kernel hackers who are
1768 debugging unstable kernels.
1770 The LART uses the same LED for both Timer LED and CPU usage LED
1771 functions. You may choose to use both, but the Timer LED function
1772 will overrule the CPU usage LED.
1775 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
1777 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1778 || MACH_OMAP_PERSEUS2
1781 If you say Y here, the red LED will be used to give a good real
1782 time indication of CPU usage, by lighting whenever the idle task
1783 is not currently executing.
1785 The LART uses the same LED for both Timer LED and CPU usage LED
1786 functions. You may choose to use both, but the Timer LED function
1787 will overrule the CPU usage LED.
1789 config ALIGNMENT_TRAP
1791 depends on CPU_CP15_MMU
1792 default y if !ARCH_EBSA110
1793 select HAVE_PROC_CPU if PROC_FS
1795 ARM processors cannot fetch/store information which is not
1796 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
1797 address divisible by 4. On 32-bit ARM processors, these non-aligned
1798 fetch/store instructions will be emulated in software if you say
1799 here, which has a severe performance impact. This is necessary for
1800 correct operation of some network protocols. With an IP-only
1801 configuration it is safe to say N, otherwise say Y.
1803 config UACCESS_WITH_MEMCPY
1804 bool "Use kernel mem{cpy,set}() for {copy_to,clear}_user() (EXPERIMENTAL)"
1805 depends on MMU && EXPERIMENTAL
1806 default y if CPU_FEROCEON
1808 Implement faster copy_to_user and clear_user methods for CPU
1809 cores where a 8-word STM instruction give significantly higher
1810 memory write throughput than a sequence of individual 32bit stores.
1812 A possible side effect is a slight increase in scheduling latency
1813 between threads sharing the same address space if they invoke
1814 such copy operations with large buffers.
1816 However, if the CPU data cache is using a write-allocate mode,
1817 this option is unlikely to provide any performance gain.
1821 prompt "Enable seccomp to safely compute untrusted bytecode"
1823 This kernel feature is useful for number crunching applications
1824 that may need to compute untrusted bytecode during their
1825 execution. By using pipes or other transports made available to
1826 the process as file descriptors supporting the read/write
1827 syscalls, it's possible to isolate those applications in
1828 their own address space using seccomp. Once seccomp is
1829 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1830 and the task is only allowed to execute a few safe syscalls
1831 defined by each seccomp mode.
1833 config CC_STACKPROTECTOR
1834 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1835 depends on EXPERIMENTAL
1837 This option turns on the -fstack-protector GCC feature. This
1838 feature puts, at the beginning of functions, a canary value on
1839 the stack just before the return address, and validates
1840 the value just before actually returning. Stack based buffer
1841 overflows (that need to overwrite this return address) now also
1842 overwrite the canary, which gets detected and the attack is then
1843 neutralized via a kernel panic.
1844 This feature requires gcc version 4.2 or above.
1846 config DEPRECATED_PARAM_STRUCT
1847 bool "Provide old way to pass kernel parameters"
1849 This was deprecated in 2001 and announced to live on for 5 years.
1850 Some old boot loaders still use this way.
1857 bool "Flattened Device Tree support"
1859 select OF_EARLY_FLATTREE
1862 Include support for flattened device tree machine descriptions.
1864 # Compressed boot loader in ROM. Yes, we really want to ask about
1865 # TEXT and BSS so we preserve their values in the config files.
1866 config ZBOOT_ROM_TEXT
1867 hex "Compressed ROM boot loader base address"
1870 The physical address at which the ROM-able zImage is to be
1871 placed in the target. Platforms which normally make use of
1872 ROM-able zImage formats normally set this to a suitable
1873 value in their defconfig file.
1875 If ZBOOT_ROM is not enabled, this has no effect.
1877 config ZBOOT_ROM_BSS
1878 hex "Compressed ROM boot loader BSS address"
1881 The base address of an area of read/write memory in the target
1882 for the ROM-able zImage which must be available while the
1883 decompressor is running. It must be large enough to hold the
1884 entire decompressed kernel plus an additional 128 KiB.
1885 Platforms which normally make use of ROM-able zImage formats
1886 normally set this to a suitable value in their defconfig file.
1888 If ZBOOT_ROM is not enabled, this has no effect.
1891 bool "Compressed boot loader in ROM/flash"
1892 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
1894 Say Y here if you intend to execute your compressed kernel image
1895 (zImage) directly from ROM or flash. If unsure, say N.
1898 prompt "Include SD/MMC loader in zImage (EXPERIMENTAL)"
1899 depends on ZBOOT_ROM && ARCH_SH7372 && EXPERIMENTAL
1900 default ZBOOT_ROM_NONE
1902 Include experimental SD/MMC loading code in the ROM-able zImage.
1903 With this enabled it is possible to write the the ROM-able zImage
1904 kernel image to an MMC or SD card and boot the kernel straight
1905 from the reset vector. At reset the processor Mask ROM will load
1906 the first part of the the ROM-able zImage which in turn loads the
1907 rest the kernel image to RAM.
1909 config ZBOOT_ROM_NONE
1910 bool "No SD/MMC loader in zImage (EXPERIMENTAL)"
1912 Do not load image from SD or MMC
1914 config ZBOOT_ROM_MMCIF
1915 bool "Include MMCIF loader in zImage (EXPERIMENTAL)"
1917 Load image from MMCIF hardware block.
1919 config ZBOOT_ROM_SH_MOBILE_SDHI
1920 bool "Include SuperH Mobile SDHI loader in zImage (EXPERIMENTAL)"
1922 Load image from SDHI hardware block
1926 config ARM_APPENDED_DTB
1927 bool "Use appended device tree blob to zImage (EXPERIMENTAL)"
1928 depends on OF && !ZBOOT_ROM && EXPERIMENTAL
1930 With this option, the boot code will look for a device tree binary
1931 (DTB) appended to zImage
1932 (e.g. cat zImage <filename>.dtb > zImage_w_dtb).
1934 This is meant as a backward compatibility convenience for those
1935 systems with a bootloader that can't be upgraded to accommodate
1936 the documented boot protocol using a device tree.
1938 Beware that there is very little in terms of protection against
1939 this option being confused by leftover garbage in memory that might
1940 look like a DTB header after a reboot if no actual DTB is appended
1941 to zImage. Do not leave this option active in a production kernel
1942 if you don't intend to always append a DTB. Proper passing of the
1943 location into r2 of a bootloader provided DTB is always preferable
1946 config ARM_ATAG_DTB_COMPAT
1947 bool "Supplement the appended DTB with traditional ATAG information"
1948 depends on ARM_APPENDED_DTB
1950 Some old bootloaders can't be updated to a DTB capable one, yet
1951 they provide ATAGs with memory configuration, the ramdisk address,
1952 the kernel cmdline string, etc. Such information is dynamically
1953 provided by the bootloader and can't always be stored in a static
1954 DTB. To allow a device tree enabled kernel to be used with such
1955 bootloaders, this option allows zImage to extract the information
1956 from the ATAG list and store it at run time into the appended DTB.
1959 string "Default kernel command string"
1962 On some architectures (EBSA110 and CATS), there is currently no way
1963 for the boot loader to pass arguments to the kernel. For these
1964 architectures, you should supply some command-line options at build
1965 time by entering them here. As a minimum, you should specify the
1966 memory size and the root device (e.g., mem=64M root=/dev/nfs).
1969 prompt "Kernel command line type" if CMDLINE != ""
1970 default CMDLINE_FROM_BOOTLOADER
1972 config CMDLINE_FROM_BOOTLOADER
1973 bool "Use bootloader kernel arguments if available"
1975 Uses the command-line options passed by the boot loader. If
1976 the boot loader doesn't provide any, the default kernel command
1977 string provided in CMDLINE will be used.
1979 config CMDLINE_EXTEND
1980 bool "Extend bootloader kernel arguments"
1982 The command-line arguments provided by the boot loader will be
1983 appended to the default kernel command string.
1985 config CMDLINE_FORCE
1986 bool "Always use the default kernel command string"
1988 Always use the default kernel command string, even if the boot
1989 loader passes other arguments to the kernel.
1990 This is useful if you cannot or don't want to change the
1991 command-line options your boot loader passes to the kernel.
1995 bool "Kernel Execute-In-Place from ROM"
1996 depends on !ZBOOT_ROM && !ARM_LPAE
1998 Execute-In-Place allows the kernel to run from non-volatile storage
1999 directly addressable by the CPU, such as NOR flash. This saves RAM
2000 space since the text section of the kernel is not loaded from flash
2001 to RAM. Read-write sections, such as the data section and stack,
2002 are still copied to RAM. The XIP kernel is not compressed since
2003 it has to run directly from flash, so it will take more space to
2004 store it. The flash address used to link the kernel object files,
2005 and for storing it, is configuration dependent. Therefore, if you
2006 say Y here, you must know the proper physical address where to
2007 store the kernel image depending on your own flash memory usage.
2009 Also note that the make target becomes "make xipImage" rather than
2010 "make zImage" or "make Image". The final kernel binary to put in
2011 ROM memory will be arch/arm/boot/xipImage.
2015 config XIP_PHYS_ADDR
2016 hex "XIP Kernel Physical Location"
2017 depends on XIP_KERNEL
2018 default "0x00080000"
2020 This is the physical address in your flash memory the kernel will
2021 be linked for and stored to. This address is dependent on your
2025 bool "Kexec system call (EXPERIMENTAL)"
2026 depends on EXPERIMENTAL && (!SMP || HOTPLUG_CPU)
2028 kexec is a system call that implements the ability to shutdown your
2029 current kernel, and to start another kernel. It is like a reboot
2030 but it is independent of the system firmware. And like a reboot
2031 you can start any kernel with it, not just Linux.
2033 It is an ongoing process to be certain the hardware in a machine
2034 is properly shutdown, so do not be surprised if this code does not
2035 initially work for you. It may help to enable device hotplugging
2039 bool "Export atags in procfs"
2043 Should the atags used to boot the kernel be exported in an "atags"
2044 file in procfs. Useful with kexec.
2047 bool "Build kdump crash kernel (EXPERIMENTAL)"
2048 depends on EXPERIMENTAL
2050 Generate crash dump after being started by kexec. This should
2051 be normally only set in special crash dump kernels which are
2052 loaded in the main kernel with kexec-tools into a specially
2053 reserved region and then later executed after a crash by
2054 kdump/kexec. The crash dump kernel must be compiled to a
2055 memory address not used by the main kernel
2057 For more details see Documentation/kdump/kdump.txt
2059 config AUTO_ZRELADDR
2060 bool "Auto calculation of the decompressed kernel image address"
2061 depends on !ZBOOT_ROM && !ARCH_U300
2063 ZRELADDR is the physical address where the decompressed kernel
2064 image will be placed. If AUTO_ZRELADDR is selected, the address
2065 will be determined at run-time by masking the current IP with
2066 0xf8000000. This assumes the zImage being placed in the first 128MB
2067 from start of memory.
2071 menu "CPU Power Management"
2075 source "drivers/cpufreq/Kconfig"
2078 tristate "CPUfreq driver for i.MX CPUs"
2079 depends on ARCH_MXC && CPU_FREQ
2081 This enables the CPUfreq driver for i.MX CPUs.
2083 config CPU_FREQ_SA1100
2086 config CPU_FREQ_SA1110
2089 config CPU_FREQ_INTEGRATOR
2090 tristate "CPUfreq driver for ARM Integrator CPUs"
2091 depends on ARCH_INTEGRATOR && CPU_FREQ
2094 This enables the CPUfreq driver for ARM Integrator CPUs.
2096 For details, take a look at <file:Documentation/cpu-freq>.
2102 depends on CPU_FREQ && ARCH_PXA && PXA25x
2104 select CPU_FREQ_TABLE
2105 select CPU_FREQ_DEFAULT_GOV_USERSPACE
2110 Internal configuration node for common cpufreq on Samsung SoC
2112 config CPU_FREQ_S3C24XX
2113 bool "CPUfreq driver for Samsung S3C24XX series CPUs (EXPERIMENTAL)"
2114 depends on ARCH_S3C2410 && CPU_FREQ && EXPERIMENTAL
2117 This enables the CPUfreq driver for the Samsung S3C24XX family
2120 For details, take a look at <file:Documentation/cpu-freq>.
2124 config CPU_FREQ_S3C24XX_PLL
2125 bool "Support CPUfreq changing of PLL frequency (EXPERIMENTAL)"
2126 depends on CPU_FREQ_S3C24XX && EXPERIMENTAL
2128 Compile in support for changing the PLL frequency from the
2129 S3C24XX series CPUfreq driver. The PLL takes time to settle
2130 after a frequency change, so by default it is not enabled.
2132 This also means that the PLL tables for the selected CPU(s) will
2133 be built which may increase the size of the kernel image.
2135 config CPU_FREQ_S3C24XX_DEBUG
2136 bool "Debug CPUfreq Samsung driver core"
2137 depends on CPU_FREQ_S3C24XX
2139 Enable s3c_freq_dbg for the Samsung S3C CPUfreq core
2141 config CPU_FREQ_S3C24XX_IODEBUG
2142 bool "Debug CPUfreq Samsung driver IO timing"
2143 depends on CPU_FREQ_S3C24XX
2145 Enable s3c_freq_iodbg for the Samsung S3C CPUfreq core
2147 config CPU_FREQ_S3C24XX_DEBUGFS
2148 bool "Export debugfs for CPUFreq"
2149 depends on CPU_FREQ_S3C24XX && DEBUG_FS
2151 Export status information via debugfs.
2155 source "drivers/cpuidle/Kconfig"
2159 menu "Floating point emulation"
2161 comment "At least one emulation must be selected"
2164 bool "NWFPE math emulation"
2165 depends on (!AEABI || OABI_COMPAT) && !THUMB2_KERNEL
2167 Say Y to include the NWFPE floating point emulator in the kernel.
2168 This is necessary to run most binaries. Linux does not currently
2169 support floating point hardware so you need to say Y here even if
2170 your machine has an FPA or floating point co-processor podule.
2172 You may say N here if you are going to load the Acorn FPEmulator
2173 early in the bootup.
2176 bool "Support extended precision"
2177 depends on FPE_NWFPE
2179 Say Y to include 80-bit support in the kernel floating-point
2180 emulator. Otherwise, only 32 and 64-bit support is compiled in.
2181 Note that gcc does not generate 80-bit operations by default,
2182 so in most cases this option only enlarges the size of the
2183 floating point emulator without any good reason.
2185 You almost surely want to say N here.
2188 bool "FastFPE math emulation (EXPERIMENTAL)"
2189 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
2191 Say Y here to include the FAST floating point emulator in the kernel.
2192 This is an experimental much faster emulator which now also has full
2193 precision for the mantissa. It does not support any exceptions.
2194 It is very simple, and approximately 3-6 times faster than NWFPE.
2196 It should be sufficient for most programs. It may be not suitable
2197 for scientific calculations, but you have to check this for yourself.
2198 If you do not feel you need a faster FP emulation you should better
2202 bool "VFP-format floating point maths"
2203 depends on CPU_V6 || CPU_V6K || CPU_ARM926T || CPU_V7 || CPU_FEROCEON
2205 Say Y to include VFP support code in the kernel. This is needed
2206 if your hardware includes a VFP unit.
2208 Please see <file:Documentation/arm/VFP/release-notes.txt> for
2209 release notes and additional status information.
2211 Say N if your target does not have VFP hardware.
2219 bool "Advanced SIMD (NEON) Extension support"
2220 depends on VFPv3 && CPU_V7
2222 Say Y to include support code for NEON, the ARMv7 Advanced SIMD
2227 menu "Userspace binary formats"
2229 source "fs/Kconfig.binfmt"
2232 tristate "RISC OS personality"
2235 Say Y here to include the kernel code necessary if you want to run
2236 Acorn RISC OS/Arthur binaries under Linux. This code is still very
2237 experimental; if this sounds frightening, say N and sleep in peace.
2238 You can also say M here to compile this support as a module (which
2239 will be called arthur).
2243 menu "Power management options"
2245 source "kernel/power/Kconfig"
2247 config ARCH_SUSPEND_POSSIBLE
2248 depends on !ARCH_S5PC100
2249 depends on CPU_ARM920T || CPU_ARM926T || CPU_SA1100 || \
2250 CPU_V6 || CPU_V6K || CPU_V7 || CPU_XSC3 || CPU_XSCALE
2253 config ARM_CPU_SUSPEND
2258 source "net/Kconfig"
2260 source "drivers/Kconfig"
2264 source "arch/arm/Kconfig.debug"
2266 source "security/Kconfig"
2268 source "crypto/Kconfig"
2270 source "lib/Kconfig"