4 select ARCH_HAVE_CUSTOM_GPIO_H
6 select HAVE_DMA_API_DEBUG
7 select HAVE_IDE if PCI || ISA || PCMCIA
9 select HAVE_DMA_CONTIGUOUS if MMU
12 select SYS_SUPPORTS_APM_EMULATION
13 select GENERIC_ATOMIC64 if (CPU_V6 || !CPU_32v6K || !AEABI)
14 select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
15 select HAVE_OPROFILE if (HAVE_PERF_EVENTS)
16 select HAVE_ARCH_JUMP_LABEL if !XIP_KERNEL
18 select HAVE_ARCH_TRACEHOOK
19 select HAVE_KPROBES if !XIP_KERNEL
20 select HAVE_KRETPROBES if (HAVE_KPROBES)
21 select HAVE_FUNCTION_TRACER if (!XIP_KERNEL)
22 select HAVE_FTRACE_MCOUNT_RECORD if (!XIP_KERNEL)
23 select HAVE_DYNAMIC_FTRACE if (!XIP_KERNEL)
24 select HAVE_FUNCTION_GRAPH_TRACER if (!THUMB2_KERNEL)
25 select ARCH_BINFMT_ELF_RANDOMIZE_PIE
26 select HAVE_GENERIC_DMA_COHERENT
27 select HAVE_KERNEL_GZIP
28 select HAVE_KERNEL_LZO
29 select HAVE_KERNEL_LZMA
32 select HAVE_PERF_EVENTS
33 select PERF_USE_VMALLOC
34 select HAVE_REGS_AND_STACK_ACCESS_API
35 select HAVE_HW_BREAKPOINT if (PERF_EVENTS && (CPU_V6 || CPU_V6K || CPU_V7))
36 select HAVE_C_RECORDMCOUNT
37 select HAVE_GENERIC_HARDIRQS
38 select HARDIRQS_SW_RESEND
39 select GENERIC_IRQ_PROBE
40 select GENERIC_IRQ_SHOW
41 select ARCH_WANT_IPC_PARSE_VERSION
42 select HARDIRQS_SW_RESEND
43 select CPU_PM if (SUSPEND || CPU_IDLE)
44 select GENERIC_PCI_IOMAP
46 select GENERIC_SMP_IDLE_THREAD
48 select GENERIC_CLOCKEVENTS_BROADCAST if SMP
49 select GENERIC_STRNCPY_FROM_USER
50 select GENERIC_STRNLEN_USER
51 select DCACHE_WORD_ACCESS if (CPU_V6 || CPU_V6K || CPU_V7) && !CPU_BIG_ENDIAN
53 The ARM series is a line of low-power-consumption RISC chip designs
54 licensed by ARM Ltd and targeted at embedded applications and
55 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
56 manufactured, but legacy ARM-based PC hardware remains popular in
57 Europe. There is an ARM Linux project with a web page at
58 <http://www.arm.linux.org.uk/>.
60 config ARM_HAS_SG_CHAIN
63 config NEED_SG_DMA_LENGTH
66 config ARM_DMA_USE_IOMMU
67 select NEED_SG_DMA_LENGTH
68 select ARM_HAS_SG_CHAIN
77 config SYS_SUPPORTS_APM_EMULATION
85 select GENERIC_ALLOCATOR
96 The Extended Industry Standard Architecture (EISA) bus was
97 developed as an open alternative to the IBM MicroChannel bus.
99 The EISA bus provided some of the features of the IBM MicroChannel
100 bus while maintaining backward compatibility with cards made for
101 the older ISA bus. The EISA bus saw limited use between 1988 and
102 1995 when it was made obsolete by the PCI bus.
104 Say Y here if you are building a kernel for an EISA-based machine.
111 config STACKTRACE_SUPPORT
115 config HAVE_LATENCYTOP_SUPPORT
120 config LOCKDEP_SUPPORT
124 config TRACE_IRQFLAGS_SUPPORT
128 config RWSEM_GENERIC_SPINLOCK
132 config RWSEM_XCHGADD_ALGORITHM
135 config ARCH_HAS_ILOG2_U32
138 config ARCH_HAS_ILOG2_U64
141 config ARCH_HAS_CPUFREQ
144 Internal node to signify that the ARCH has CPUFREQ support
145 and that the relevant menu configurations are displayed for
148 config GENERIC_HWEIGHT
152 config GENERIC_CALIBRATE_DELAY
156 config ARCH_MAY_HAVE_PC_FDC
162 config NEED_DMA_MAP_STATE
165 config ARCH_HAS_DMA_SET_COHERENT_MASK
168 config GENERIC_ISA_DMA
174 config NEED_RET_TO_USER
182 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
183 default DRAM_BASE if REMAP_VECTORS_TO_RAM
186 The base address of exception vectors.
188 config ARM_PATCH_PHYS_VIRT
189 bool "Patch physical to virtual translations at runtime" if EMBEDDED
191 depends on !XIP_KERNEL && MMU
192 depends on !ARCH_REALVIEW || !SPARSEMEM
194 Patch phys-to-virt and virt-to-phys translation functions at
195 boot and module load time according to the position of the
196 kernel in system memory.
198 This can only be used with non-XIP MMU kernels where the base
199 of physical memory is at a 16MB boundary.
201 Only disable this option if you know that you do not require
202 this feature (eg, building a kernel for a single machine) and
203 you need to shrink the kernel to the minimal size.
205 config NEED_MACH_IO_H
208 Select this when mach/io.h is required to provide special
209 definitions for this platform. The need for mach/io.h should
210 be avoided when possible.
212 config NEED_MACH_MEMORY_H
215 Select this when mach/memory.h is required to provide special
216 definitions for this platform. The need for mach/memory.h should
217 be avoided when possible.
220 hex "Physical address of main memory" if MMU
221 depends on !ARM_PATCH_PHYS_VIRT && !NEED_MACH_MEMORY_H
222 default DRAM_BASE if !MMU
224 Please provide the physical address corresponding to the
225 location of main memory in your system.
231 source "init/Kconfig"
233 source "kernel/Kconfig.freezer"
238 bool "MMU-based Paged Memory Management Support"
241 Select if you want MMU-based virtualised addressing space
242 support by paged memory management. If unsure, say 'Y'.
245 # The "ARM system type" choice list is ordered alphabetically by option
246 # text. Please add new entries in the option alphabetic order.
249 prompt "ARM system type"
250 default ARCH_VERSATILE
253 bool "Altera SOCFPGA family"
254 select ARCH_WANT_OPTIONAL_GPIOLIB
262 select DW_APB_TIMER_OF
263 select GENERIC_CLOCKEVENTS
264 select GPIO_PL061 if GPIOLIB
269 This enables support for Altera SOCFPGA Cyclone V platform
271 config ARCH_INTEGRATOR
272 bool "ARM Ltd. Integrator family"
274 select ARCH_HAS_CPUFREQ
279 select GENERIC_CLOCKEVENTS
280 select PLAT_VERSATILE
281 select PLAT_VERSATILE_FPGA_IRQ
282 select NEED_MACH_IO_H
283 select NEED_MACH_MEMORY_H
285 select MULTI_IRQ_HANDLER
287 Support for ARM's Integrator platform.
290 bool "ARM Ltd. RealView family"
293 select HAVE_MACH_CLKDEV
295 select GENERIC_CLOCKEVENTS
296 select ARCH_WANT_OPTIONAL_GPIOLIB
297 select PLAT_VERSATILE
298 select PLAT_VERSATILE_CLOCK
299 select PLAT_VERSATILE_CLCD
300 select ARM_TIMER_SP804
301 select GPIO_PL061 if GPIOLIB
302 select NEED_MACH_MEMORY_H
304 This enables support for ARM Ltd RealView boards.
306 config ARCH_VERSATILE
307 bool "ARM Ltd. Versatile family"
311 select HAVE_MACH_CLKDEV
313 select GENERIC_CLOCKEVENTS
314 select ARCH_WANT_OPTIONAL_GPIOLIB
315 select NEED_MACH_IO_H if PCI
316 select PLAT_VERSATILE
317 select PLAT_VERSATILE_CLOCK
318 select PLAT_VERSATILE_CLCD
319 select PLAT_VERSATILE_FPGA_IRQ
320 select ARM_TIMER_SP804
322 This enables support for ARM Ltd Versatile board.
325 bool "ARM Ltd. Versatile Express family"
326 select ARCH_WANT_OPTIONAL_GPIOLIB
328 select ARM_TIMER_SP804
331 select GENERIC_CLOCKEVENTS
333 select HAVE_PATA_PLATFORM
336 select PLAT_VERSATILE
337 select PLAT_VERSATILE_CLCD
338 select REGULATOR_FIXED_VOLTAGE if REGULATOR
340 This enables support for the ARM Ltd Versatile Express boards.
344 select ARCH_REQUIRE_GPIOLIB
348 select NEED_MACH_IO_H if PCCARD
350 This enables support for systems based on Atmel
351 AT91RM9200 and AT91SAM9* processors.
354 bool "Calxeda Highbank-based"
355 select ARCH_WANT_OPTIONAL_GPIOLIB
358 select ARM_TIMER_SP804
363 select GENERIC_CLOCKEVENTS
369 Support for the Calxeda Highbank SoC based boards.
372 bool "Cirrus Logic CLPS711x/EP721x/EP731x-based"
374 select ARCH_USES_GETTIMEOFFSET
377 select NEED_MACH_MEMORY_H
379 Support for Cirrus Logic 711x/721x/731x based boards.
382 bool "Cavium Networks CNS3XXX family"
384 select GENERIC_CLOCKEVENTS
386 select MIGHT_HAVE_CACHE_L2X0
387 select MIGHT_HAVE_PCI
388 select PCI_DOMAINS if PCI
390 Support for Cavium Networks CNS3XXX platform.
393 bool "Cortina Systems Gemini"
395 select ARCH_REQUIRE_GPIOLIB
396 select ARCH_USES_GETTIMEOFFSET
398 Support for the Cortina Systems Gemini family SoCs
401 bool "CSR SiRFSoC PRIMA2 ARM Cortex A9 Platform"
404 select ARCH_REQUIRE_GPIOLIB
405 select GENERIC_CLOCKEVENTS
407 select GENERIC_IRQ_CHIP
408 select MIGHT_HAVE_CACHE_L2X0
414 Support for CSR SiRFSoC ARM Cortex A9 Platform
421 select ARCH_USES_GETTIMEOFFSET
422 select NEED_MACH_IO_H
423 select NEED_MACH_MEMORY_H
425 This is an evaluation board for the StrongARM processor available
426 from Digital. It has limited hardware on-board, including an
427 Ethernet interface, two PCMCIA sockets, two serial ports and a
436 select ARCH_REQUIRE_GPIOLIB
437 select ARCH_HAS_HOLES_MEMORYMODEL
438 select ARCH_USES_GETTIMEOFFSET
439 select NEED_MACH_MEMORY_H
441 This enables support for the Cirrus EP93xx series of CPUs.
443 config ARCH_FOOTBRIDGE
447 select GENERIC_CLOCKEVENTS
449 select NEED_MACH_IO_H
450 select NEED_MACH_MEMORY_H
452 Support for systems based on the DC21285 companion chip
453 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
456 bool "Freescale MXC/iMX-based"
457 select GENERIC_CLOCKEVENTS
458 select ARCH_REQUIRE_GPIOLIB
461 select GENERIC_IRQ_CHIP
462 select MULTI_IRQ_HANDLER
466 Support for Freescale MXC/iMX-based family of processors
469 bool "Freescale MXS-based"
470 select GENERIC_CLOCKEVENTS
471 select ARCH_REQUIRE_GPIOLIB
475 select HAVE_CLK_PREPARE
479 Support for Freescale MXS-based family of processors
482 bool "Hilscher NetX based"
486 select GENERIC_CLOCKEVENTS
488 This enables support for systems based on the Hilscher NetX Soc
491 bool "Hynix HMS720x-based"
494 select ARCH_USES_GETTIMEOFFSET
496 This enables support for systems based on the Hynix HMS720x
504 select ARCH_SUPPORTS_MSI
506 select NEED_MACH_IO_H
507 select NEED_MACH_MEMORY_H
508 select NEED_RET_TO_USER
510 Support for Intel's IOP13XX (XScale) family of processors.
516 select NEED_MACH_IO_H
517 select NEED_RET_TO_USER
520 select ARCH_REQUIRE_GPIOLIB
522 Support for Intel's 80219 and IOP32X (XScale) family of
529 select NEED_MACH_IO_H
530 select NEED_RET_TO_USER
533 select ARCH_REQUIRE_GPIOLIB
535 Support for Intel's IOP33X (XScale) family of processors.
540 select ARCH_HAS_DMA_SET_COHERENT_MASK
543 select ARCH_REQUIRE_GPIOLIB
544 select GENERIC_CLOCKEVENTS
545 select MIGHT_HAVE_PCI
546 select NEED_MACH_IO_H
547 select DMABOUNCE if PCI
549 Support for Intel's IXP4XX (XScale) family of processors.
552 bool "Marvell SOCs with Device Tree support"
553 select GENERIC_CLOCKEVENTS
554 select MULTI_IRQ_HANDLER
557 select GENERIC_IRQ_CHIP
561 Support for the Marvell SoC Family with device tree support
567 select ARCH_REQUIRE_GPIOLIB
568 select GENERIC_CLOCKEVENTS
569 select NEED_MACH_IO_H
572 Support for the Marvell Dove SoC 88AP510
575 bool "Marvell Kirkwood"
578 select ARCH_REQUIRE_GPIOLIB
579 select GENERIC_CLOCKEVENTS
580 select NEED_MACH_IO_H
583 Support for the following Marvell Kirkwood series SoCs:
584 88F6180, 88F6192 and 88F6281.
590 select ARCH_REQUIRE_GPIOLIB
593 select USB_ARCH_HAS_OHCI
595 select GENERIC_CLOCKEVENTS
599 Support for the NXP LPC32XX family of processors
602 bool "Marvell MV78xx0"
605 select ARCH_REQUIRE_GPIOLIB
606 select GENERIC_CLOCKEVENTS
607 select NEED_MACH_IO_H
610 Support for the following Marvell MV78xx0 series SoCs:
618 select ARCH_REQUIRE_GPIOLIB
619 select GENERIC_CLOCKEVENTS
620 select NEED_MACH_IO_H
623 Support for the following Marvell Orion 5x series SoCs:
624 Orion-1 (5181), Orion-VoIP (5181L), Orion-NAS (5182),
625 Orion-2 (5281), Orion-1-90 (6183).
628 bool "Marvell PXA168/910/MMP2"
630 select ARCH_REQUIRE_GPIOLIB
632 select GENERIC_CLOCKEVENTS
637 select GENERIC_ALLOCATOR
639 Support for Marvell's PXA168/PXA910(MMP) and MMP2 processor line.
642 bool "Micrel/Kendin KS8695"
644 select ARCH_REQUIRE_GPIOLIB
645 select ARCH_USES_GETTIMEOFFSET
646 select NEED_MACH_MEMORY_H
648 Support for Micrel/Kendin KS8695 "Centaur" (ARM922T) based
649 System-on-Chip devices.
652 bool "Nuvoton W90X900 CPU"
654 select ARCH_REQUIRE_GPIOLIB
657 select GENERIC_CLOCKEVENTS
659 Support for Nuvoton (Winbond logic dept.) ARM9 processor,
660 At present, the w90x900 has been renamed nuc900, regarding
661 the ARM series product line, you can login the following
662 link address to know more.
664 <http://www.nuvoton.com/hq/enu/ProductAndSales/ProductLines/
665 ConsumerElectronicsIC/ARMMicrocontroller/ARMMicrocontroller>
671 select GENERIC_CLOCKEVENTS
675 select MIGHT_HAVE_CACHE_L2X0
676 select NEED_MACH_IO_H if PCI
677 select ARCH_HAS_CPUFREQ
681 This enables support for NVIDIA Tegra based systems (Tegra APX,
682 Tegra 6xx and Tegra 2 series).
684 config ARCH_PICOXCELL
685 bool "Picochip picoXcell"
686 select ARCH_REQUIRE_GPIOLIB
687 select ARM_PATCH_PHYS_VIRT
691 select DW_APB_TIMER_OF
692 select GENERIC_CLOCKEVENTS
699 This enables support for systems based on the Picochip picoXcell
700 family of Femtocell devices. The picoxcell support requires device tree
704 bool "Philips Nexperia PNX4008 Mobile"
707 select ARCH_USES_GETTIMEOFFSET
709 This enables support for Philips PNX4008 mobile platform.
712 bool "PXA2xx/PXA3xx-based"
715 select ARCH_HAS_CPUFREQ
718 select ARCH_REQUIRE_GPIOLIB
719 select GENERIC_CLOCKEVENTS
724 select MULTI_IRQ_HANDLER
725 select ARM_CPU_SUSPEND if PM
728 Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
733 select GENERIC_CLOCKEVENTS
734 select ARCH_REQUIRE_GPIOLIB
737 Support for Qualcomm MSM/QSD based systems. This runs on the
738 apps processor of the MSM/QSD and depends on a shared memory
739 interface to the modem processor which runs the baseband
740 stack and controls some vital subsystems
741 (clock and power control, etc).
744 bool "Renesas SH-Mobile / R-Mobile"
747 select HAVE_MACH_CLKDEV
749 select GENERIC_CLOCKEVENTS
750 select MIGHT_HAVE_CACHE_L2X0
753 select MULTI_IRQ_HANDLER
754 select PM_GENERIC_DOMAINS if PM
755 select NEED_MACH_MEMORY_H
757 Support for Renesas's SH-Mobile and R-Mobile ARM platforms.
763 select ARCH_MAY_HAVE_PC_FDC
764 select HAVE_PATA_PLATFORM
767 select ARCH_SPARSEMEM_ENABLE
768 select ARCH_USES_GETTIMEOFFSET
770 select NEED_MACH_IO_H
771 select NEED_MACH_MEMORY_H
773 On the Acorn Risc-PC, Linux can support the internal IDE disk and
774 CD-ROM interface, serial and parallel port, and the floppy drive.
781 select ARCH_SPARSEMEM_ENABLE
783 select ARCH_HAS_CPUFREQ
785 select GENERIC_CLOCKEVENTS
787 select ARCH_REQUIRE_GPIOLIB
789 select NEED_MACH_MEMORY_H
792 Support for StrongARM 11x0 based boards.
795 bool "Samsung S3C24XX SoCs"
797 select ARCH_HAS_CPUFREQ
800 select ARCH_USES_GETTIMEOFFSET
801 select HAVE_S3C2410_I2C if I2C
802 select HAVE_S3C_RTC if RTC_CLASS
803 select HAVE_S3C2410_WATCHDOG if WATCHDOG
804 select NEED_MACH_IO_H
806 Samsung S3C2410, S3C2412, S3C2413, S3C2416, S3C2440, S3C2442, S3C2443
807 and S3C2450 SoCs based systems, such as the Simtec Electronics BAST
808 (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or the
809 Samsung SMDK2410 development board (and derivatives).
812 bool "Samsung S3C64XX"
820 select ARCH_USES_GETTIMEOFFSET
821 select ARCH_HAS_CPUFREQ
822 select ARCH_REQUIRE_GPIOLIB
823 select SAMSUNG_CLKSRC
824 select SAMSUNG_IRQ_VIC_TIMER
825 select S3C_GPIO_TRACK
827 select USB_ARCH_HAS_OHCI
828 select SAMSUNG_GPIOLIB_4BIT
829 select HAVE_S3C2410_I2C if I2C
830 select HAVE_S3C2410_WATCHDOG if WATCHDOG
832 Samsung S3C64XX series based systems
835 bool "Samsung S5P6440 S5P6450"
841 select HAVE_S3C2410_WATCHDOG if WATCHDOG
842 select GENERIC_CLOCKEVENTS
843 select HAVE_S3C2410_I2C if I2C
844 select HAVE_S3C_RTC if RTC_CLASS
846 Samsung S5P64X0 CPU based systems, such as the Samsung SMDK6440,
850 bool "Samsung S5PC100"
855 select ARCH_USES_GETTIMEOFFSET
856 select HAVE_S3C2410_I2C if I2C
857 select HAVE_S3C_RTC if RTC_CLASS
858 select HAVE_S3C2410_WATCHDOG if WATCHDOG
860 Samsung S5PC100 series based systems
863 bool "Samsung S5PV210/S5PC110"
865 select ARCH_SPARSEMEM_ENABLE
866 select ARCH_HAS_HOLES_MEMORYMODEL
871 select ARCH_HAS_CPUFREQ
872 select GENERIC_CLOCKEVENTS
873 select HAVE_S3C2410_I2C if I2C
874 select HAVE_S3C_RTC if RTC_CLASS
875 select HAVE_S3C2410_WATCHDOG if WATCHDOG
876 select NEED_MACH_MEMORY_H
878 Samsung S5PV210/S5PC110 series based systems
881 bool "SAMSUNG EXYNOS"
883 select ARCH_SPARSEMEM_ENABLE
884 select ARCH_HAS_HOLES_MEMORYMODEL
888 select ARCH_HAS_CPUFREQ
889 select GENERIC_CLOCKEVENTS
890 select HAVE_S3C_RTC if RTC_CLASS
891 select HAVE_S3C2410_I2C if I2C
892 select HAVE_S3C2410_WATCHDOG if WATCHDOG
893 select NEED_MACH_MEMORY_H
895 Support for SAMSUNG's EXYNOS SoCs (EXYNOS4/5)
904 select ARCH_USES_GETTIMEOFFSET
905 select NEED_MACH_MEMORY_H
906 select NEED_MACH_IO_H
908 Support for the StrongARM based Digital DNARD machine, also known
909 as "Shark" (<http://www.shark-linux.de/shark.html>).
912 bool "ST-Ericsson U300 Series"
918 select ARM_PATCH_PHYS_VIRT
920 select GENERIC_CLOCKEVENTS
924 select ARCH_REQUIRE_GPIOLIB
926 Support for ST-Ericsson U300 series mobile platforms.
929 bool "ST-Ericsson U8500 Series"
933 select GENERIC_CLOCKEVENTS
935 select ARCH_REQUIRE_GPIOLIB
936 select ARCH_HAS_CPUFREQ
938 select MIGHT_HAVE_CACHE_L2X0
940 Support for ST-Ericsson's Ux500 architecture
943 bool "STMicroelectronics Nomadik"
948 select GENERIC_CLOCKEVENTS
950 select MIGHT_HAVE_CACHE_L2X0
951 select ARCH_REQUIRE_GPIOLIB
953 Support for the Nomadik platform by ST-Ericsson
957 select GENERIC_CLOCKEVENTS
958 select ARCH_REQUIRE_GPIOLIB
962 select GENERIC_ALLOCATOR
963 select GENERIC_IRQ_CHIP
964 select ARCH_HAS_HOLES_MEMORYMODEL
966 Support for TI's DaVinci platform.
972 select ARCH_REQUIRE_GPIOLIB
973 select ARCH_HAS_CPUFREQ
975 select GENERIC_CLOCKEVENTS
976 select ARCH_HAS_HOLES_MEMORYMODEL
978 Support for TI's OMAP platform (OMAP1/2/3/4).
983 select ARCH_REQUIRE_GPIOLIB
987 select GENERIC_CLOCKEVENTS
990 Support for ST's SPEAr platform (SPEAr3xx, SPEAr6xx and SPEAr13xx).
993 bool "VIA/WonderMedia 85xx"
996 select ARCH_HAS_CPUFREQ
997 select GENERIC_CLOCKEVENTS
998 select ARCH_REQUIRE_GPIOLIB
1000 Support for VIA/WonderMedia VT8500/WM85xx System-on-Chip.
1003 bool "Xilinx Zynq ARM Cortex A9 Platform"
1005 select GENERIC_CLOCKEVENTS
1006 select CLKDEV_LOOKUP
1010 select MIGHT_HAVE_CACHE_L2X0
1013 Support for Xilinx Zynq ARM Cortex A9 Platform
1017 # This is sorted alphabetically by mach-* pathname. However, plat-*
1018 # Kconfigs may be included either alphabetically (according to the
1019 # plat- suffix) or along side the corresponding mach-* source.
1021 source "arch/arm/mach-mvebu/Kconfig"
1023 source "arch/arm/mach-at91/Kconfig"
1025 source "arch/arm/mach-clps711x/Kconfig"
1027 source "arch/arm/mach-cns3xxx/Kconfig"
1029 source "arch/arm/mach-davinci/Kconfig"
1031 source "arch/arm/mach-dove/Kconfig"
1033 source "arch/arm/mach-ep93xx/Kconfig"
1035 source "arch/arm/mach-footbridge/Kconfig"
1037 source "arch/arm/mach-gemini/Kconfig"
1039 source "arch/arm/mach-h720x/Kconfig"
1041 source "arch/arm/mach-integrator/Kconfig"
1043 source "arch/arm/mach-iop32x/Kconfig"
1045 source "arch/arm/mach-iop33x/Kconfig"
1047 source "arch/arm/mach-iop13xx/Kconfig"
1049 source "arch/arm/mach-ixp4xx/Kconfig"
1051 source "arch/arm/mach-kirkwood/Kconfig"
1053 source "arch/arm/mach-ks8695/Kconfig"
1055 source "arch/arm/mach-msm/Kconfig"
1057 source "arch/arm/mach-mv78xx0/Kconfig"
1059 source "arch/arm/plat-mxc/Kconfig"
1061 source "arch/arm/mach-mxs/Kconfig"
1063 source "arch/arm/mach-netx/Kconfig"
1065 source "arch/arm/mach-nomadik/Kconfig"
1066 source "arch/arm/plat-nomadik/Kconfig"
1068 source "arch/arm/plat-omap/Kconfig"
1070 source "arch/arm/mach-omap1/Kconfig"
1072 source "arch/arm/mach-omap2/Kconfig"
1074 source "arch/arm/mach-orion5x/Kconfig"
1076 source "arch/arm/mach-pxa/Kconfig"
1077 source "arch/arm/plat-pxa/Kconfig"
1079 source "arch/arm/mach-mmp/Kconfig"
1081 source "arch/arm/mach-realview/Kconfig"
1083 source "arch/arm/mach-sa1100/Kconfig"
1085 source "arch/arm/plat-samsung/Kconfig"
1086 source "arch/arm/plat-s3c24xx/Kconfig"
1088 source "arch/arm/plat-spear/Kconfig"
1090 source "arch/arm/mach-s3c24xx/Kconfig"
1092 source "arch/arm/mach-s3c2412/Kconfig"
1093 source "arch/arm/mach-s3c2440/Kconfig"
1097 source "arch/arm/mach-s3c64xx/Kconfig"
1100 source "arch/arm/mach-s5p64x0/Kconfig"
1102 source "arch/arm/mach-s5pc100/Kconfig"
1104 source "arch/arm/mach-s5pv210/Kconfig"
1106 source "arch/arm/mach-exynos/Kconfig"
1108 source "arch/arm/mach-shmobile/Kconfig"
1110 source "arch/arm/mach-tegra/Kconfig"
1112 source "arch/arm/mach-u300/Kconfig"
1114 source "arch/arm/mach-ux500/Kconfig"
1116 source "arch/arm/mach-versatile/Kconfig"
1118 source "arch/arm/mach-vexpress/Kconfig"
1119 source "arch/arm/plat-versatile/Kconfig"
1121 source "arch/arm/mach-vt8500/Kconfig"
1123 source "arch/arm/mach-w90x900/Kconfig"
1125 # Definitions to make life easier
1131 select GENERIC_CLOCKEVENTS
1136 select GENERIC_IRQ_CHIP
1143 config PLAT_VERSATILE
1146 config ARM_TIMER_SP804
1149 select HAVE_SCHED_CLOCK
1151 source arch/arm/mm/Kconfig
1155 default 16 if ARCH_EP93XX
1159 bool "Enable iWMMXt support"
1160 depends on CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_PJ4
1161 default y if PXA27x || PXA3xx || PXA95x || ARCH_MMP
1163 Enable support for iWMMXt context switching at run time if
1164 running on a CPU that supports it.
1168 depends on CPU_XSCALE
1172 depends on (CPU_V6 || CPU_V6K || CPU_V7 || XSCALE_PMU) && \
1173 (!ARCH_OMAP3 || OMAP3_EMU)
1177 config MULTI_IRQ_HANDLER
1180 Allow each machine to specify it's own IRQ handler at run time.
1183 source "arch/arm/Kconfig-nommu"
1186 config ARM_ERRATA_326103
1187 bool "ARM errata: FSR write bit incorrect on a SWP to read-only memory"
1190 Executing a SWP instruction to read-only memory does not set bit 11
1191 of the FSR on the ARM 1136 prior to r1p0. This causes the kernel to
1192 treat the access as a read, preventing a COW from occurring and
1193 causing the faulting task to livelock.
1195 config ARM_ERRATA_411920
1196 bool "ARM errata: Invalidation of the Instruction Cache operation can fail"
1197 depends on CPU_V6 || CPU_V6K
1199 Invalidation of the Instruction Cache operation can
1200 fail. This erratum is present in 1136 (before r1p4), 1156 and 1176.
1201 It does not affect the MPCore. This option enables the ARM Ltd.
1202 recommended workaround.
1204 config ARM_ERRATA_430973
1205 bool "ARM errata: Stale prediction on replaced interworking branch"
1208 This option enables the workaround for the 430973 Cortex-A8
1209 (r1p0..r1p2) erratum. If a code sequence containing an ARM/Thumb
1210 interworking branch is replaced with another code sequence at the
1211 same virtual address, whether due to self-modifying code or virtual
1212 to physical address re-mapping, Cortex-A8 does not recover from the
1213 stale interworking branch prediction. This results in Cortex-A8
1214 executing the new code sequence in the incorrect ARM or Thumb state.
1215 The workaround enables the BTB/BTAC operations by setting ACTLR.IBE
1216 and also flushes the branch target cache at every context switch.
1217 Note that setting specific bits in the ACTLR register may not be
1218 available in non-secure mode.
1220 config ARM_ERRATA_458693
1221 bool "ARM errata: Processor deadlock when a false hazard is created"
1224 This option enables the workaround for the 458693 Cortex-A8 (r2p0)
1225 erratum. For very specific sequences of memory operations, it is
1226 possible for a hazard condition intended for a cache line to instead
1227 be incorrectly associated with a different cache line. This false
1228 hazard might then cause a processor deadlock. The workaround enables
1229 the L1 caching of the NEON accesses and disables the PLD instruction
1230 in the ACTLR register. Note that setting specific bits in the ACTLR
1231 register may not be available in non-secure mode.
1233 config ARM_ERRATA_460075
1234 bool "ARM errata: Data written to the L2 cache can be overwritten with stale data"
1237 This option enables the workaround for the 460075 Cortex-A8 (r2p0)
1238 erratum. Any asynchronous access to the L2 cache may encounter a
1239 situation in which recent store transactions to the L2 cache are lost
1240 and overwritten with stale memory contents from external memory. The
1241 workaround disables the write-allocate mode for the L2 cache via the
1242 ACTLR register. Note that setting specific bits in the ACTLR register
1243 may not be available in non-secure mode.
1245 config ARM_ERRATA_742230
1246 bool "ARM errata: DMB operation may be faulty"
1247 depends on CPU_V7 && SMP
1249 This option enables the workaround for the 742230 Cortex-A9
1250 (r1p0..r2p2) erratum. Under rare circumstances, a DMB instruction
1251 between two write operations may not ensure the correct visibility
1252 ordering of the two writes. This workaround sets a specific bit in
1253 the diagnostic register of the Cortex-A9 which causes the DMB
1254 instruction to behave as a DSB, ensuring the correct behaviour of
1257 config ARM_ERRATA_742231
1258 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
1259 depends on CPU_V7 && SMP
1261 This option enables the workaround for the 742231 Cortex-A9
1262 (r2p0..r2p2) erratum. Under certain conditions, specific to the
1263 Cortex-A9 MPCore micro-architecture, two CPUs working in SMP mode,
1264 accessing some data located in the same cache line, may get corrupted
1265 data due to bad handling of the address hazard when the line gets
1266 replaced from one of the CPUs at the same time as another CPU is
1267 accessing it. This workaround sets specific bits in the diagnostic
1268 register of the Cortex-A9 which reduces the linefill issuing
1269 capabilities of the processor.
1271 config PL310_ERRATA_588369
1272 bool "PL310 errata: Clean & Invalidate maintenance operations do not invalidate clean lines"
1273 depends on CACHE_L2X0
1275 The PL310 L2 cache controller implements three types of Clean &
1276 Invalidate maintenance operations: by Physical Address
1277 (offset 0x7F0), by Index/Way (0x7F8) and by Way (0x7FC).
1278 They are architecturally defined to behave as the execution of a
1279 clean operation followed immediately by an invalidate operation,
1280 both performing to the same memory location. This functionality
1281 is not correctly implemented in PL310 as clean lines are not
1282 invalidated as a result of these operations.
1284 config ARM_ERRATA_720789
1285 bool "ARM errata: TLBIASIDIS and TLBIMVAIS operations can broadcast a faulty ASID"
1288 This option enables the workaround for the 720789 Cortex-A9 (prior to
1289 r2p0) erratum. A faulty ASID can be sent to the other CPUs for the
1290 broadcasted CP15 TLB maintenance operations TLBIASIDIS and TLBIMVAIS.
1291 As a consequence of this erratum, some TLB entries which should be
1292 invalidated are not, resulting in an incoherency in the system page
1293 tables. The workaround changes the TLB flushing routines to invalidate
1294 entries regardless of the ASID.
1296 config PL310_ERRATA_727915
1297 bool "PL310 errata: Background Clean & Invalidate by Way operation can cause data corruption"
1298 depends on CACHE_L2X0
1300 PL310 implements the Clean & Invalidate by Way L2 cache maintenance
1301 operation (offset 0x7FC). This operation runs in background so that
1302 PL310 can handle normal accesses while it is in progress. Under very
1303 rare circumstances, due to this erratum, write data can be lost when
1304 PL310 treats a cacheable write transaction during a Clean &
1305 Invalidate by Way operation.
1307 config ARM_ERRATA_743622
1308 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
1311 This option enables the workaround for the 743622 Cortex-A9
1312 (r2p*) erratum. Under very rare conditions, a faulty
1313 optimisation in the Cortex-A9 Store Buffer may lead to data
1314 corruption. This workaround sets a specific bit in the diagnostic
1315 register of the Cortex-A9 which disables the Store Buffer
1316 optimisation, preventing the defect from occurring. This has no
1317 visible impact on the overall performance or power consumption of the
1320 config ARM_ERRATA_751472
1321 bool "ARM errata: Interrupted ICIALLUIS may prevent completion of broadcasted operation"
1324 This option enables the workaround for the 751472 Cortex-A9 (prior
1325 to r3p0) erratum. An interrupted ICIALLUIS operation may prevent the
1326 completion of a following broadcasted operation if the second
1327 operation is received by a CPU before the ICIALLUIS has completed,
1328 potentially leading to corrupted entries in the cache or TLB.
1330 config PL310_ERRATA_753970
1331 bool "PL310 errata: cache sync operation may be faulty"
1332 depends on CACHE_PL310
1334 This option enables the workaround for the 753970 PL310 (r3p0) erratum.
1336 Under some condition the effect of cache sync operation on
1337 the store buffer still remains when the operation completes.
1338 This means that the store buffer is always asked to drain and
1339 this prevents it from merging any further writes. The workaround
1340 is to replace the normal offset of cache sync operation (0x730)
1341 by another offset targeting an unmapped PL310 register 0x740.
1342 This has the same effect as the cache sync operation: store buffer
1343 drain and waiting for all buffers empty.
1345 config ARM_ERRATA_754322
1346 bool "ARM errata: possible faulty MMU translations following an ASID switch"
1349 This option enables the workaround for the 754322 Cortex-A9 (r2p*,
1350 r3p*) erratum. A speculative memory access may cause a page table walk
1351 which starts prior to an ASID switch but completes afterwards. This
1352 can populate the micro-TLB with a stale entry which may be hit with
1353 the new ASID. This workaround places two dsb instructions in the mm
1354 switching code so that no page table walks can cross the ASID switch.
1356 config ARM_ERRATA_754327
1357 bool "ARM errata: no automatic Store Buffer drain"
1358 depends on CPU_V7 && SMP
1360 This option enables the workaround for the 754327 Cortex-A9 (prior to
1361 r2p0) erratum. The Store Buffer does not have any automatic draining
1362 mechanism and therefore a livelock may occur if an external agent
1363 continuously polls a memory location waiting to observe an update.
1364 This workaround defines cpu_relax() as smp_mb(), preventing correctly
1365 written polling loops from denying visibility of updates to memory.
1367 config ARM_ERRATA_364296
1368 bool "ARM errata: Possible cache data corruption with hit-under-miss enabled"
1369 depends on CPU_V6 && !SMP
1371 This options enables the workaround for the 364296 ARM1136
1372 r0p2 erratum (possible cache data corruption with
1373 hit-under-miss enabled). It sets the undocumented bit 31 in
1374 the auxiliary control register and the FI bit in the control
1375 register, thus disabling hit-under-miss without putting the
1376 processor into full low interrupt latency mode. ARM11MPCore
1379 config ARM_ERRATA_764369
1380 bool "ARM errata: Data cache line maintenance operation by MVA may not succeed"
1381 depends on CPU_V7 && SMP
1383 This option enables the workaround for erratum 764369
1384 affecting Cortex-A9 MPCore with two or more processors (all
1385 current revisions). Under certain timing circumstances, a data
1386 cache line maintenance operation by MVA targeting an Inner
1387 Shareable memory region may fail to proceed up to either the
1388 Point of Coherency or to the Point of Unification of the
1389 system. This workaround adds a DSB instruction before the
1390 relevant cache maintenance functions and sets a specific bit
1391 in the diagnostic control register of the SCU.
1393 config PL310_ERRATA_769419
1394 bool "PL310 errata: no automatic Store Buffer drain"
1395 depends on CACHE_L2X0
1397 On revisions of the PL310 prior to r3p2, the Store Buffer does
1398 not automatically drain. This can cause normal, non-cacheable
1399 writes to be retained when the memory system is idle, leading
1400 to suboptimal I/O performance for drivers using coherent DMA.
1401 This option adds a write barrier to the cpu_idle loop so that,
1402 on systems with an outer cache, the store buffer is drained
1407 source "arch/arm/common/Kconfig"
1417 Find out whether you have ISA slots on your motherboard. ISA is the
1418 name of a bus system, i.e. the way the CPU talks to the other stuff
1419 inside your box. Other bus systems are PCI, EISA, MicroChannel
1420 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1421 newer boards don't support it. If you have ISA, say Y, otherwise N.
1423 # Select ISA DMA controller support
1428 # Select ISA DMA interface
1433 bool "PCI support" if MIGHT_HAVE_PCI
1435 Find out whether you have a PCI motherboard. PCI is the name of a
1436 bus system, i.e. the way the CPU talks to the other stuff inside
1437 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1438 VESA. If you have PCI, say Y, otherwise N.
1444 config PCI_NANOENGINE
1445 bool "BSE nanoEngine PCI support"
1446 depends on SA1100_NANOENGINE
1448 Enable PCI on the BSE nanoEngine board.
1453 # Select the host bridge type
1454 config PCI_HOST_VIA82C505
1456 depends on PCI && ARCH_SHARK
1459 config PCI_HOST_ITE8152
1461 depends on PCI && MACH_ARMCORE
1465 source "drivers/pci/Kconfig"
1467 source "drivers/pcmcia/Kconfig"
1471 menu "Kernel Features"
1476 This option should be selected by machines which have an SMP-
1479 The only effect of this option is to make the SMP-related
1480 options available to the user for configuration.
1483 bool "Symmetric Multi-Processing"
1484 depends on CPU_V6K || CPU_V7
1485 depends on GENERIC_CLOCKEVENTS
1488 select USE_GENERIC_SMP_HELPERS
1489 select HAVE_ARM_SCU if !ARCH_MSM_SCORPIONMP
1491 This enables support for systems with more than one CPU. If you have
1492 a system with only one CPU, like most personal computers, say N. If
1493 you have a system with more than one CPU, say Y.
1495 If you say N here, the kernel will run on single and multiprocessor
1496 machines, but will use only one CPU of a multiprocessor machine. If
1497 you say Y here, the kernel will run on many, but not all, single
1498 processor machines. On a single processor machine, the kernel will
1499 run faster if you say N here.
1501 See also <file:Documentation/x86/i386/IO-APIC.txt>,
1502 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
1503 <http://tldp.org/HOWTO/SMP-HOWTO.html>.
1505 If you don't know what to do here, say N.
1508 bool "Allow booting SMP kernel on uniprocessor systems (EXPERIMENTAL)"
1509 depends on EXPERIMENTAL
1510 depends on SMP && !XIP_KERNEL
1513 SMP kernels contain instructions which fail on non-SMP processors.
1514 Enabling this option allows the kernel to modify itself to make
1515 these instructions safe. Disabling it allows about 1K of space
1518 If you don't know what to do here, say Y.
1520 config ARM_CPU_TOPOLOGY
1521 bool "Support cpu topology definition"
1522 depends on SMP && CPU_V7
1525 Support ARM cpu topology definition. The MPIDR register defines
1526 affinity between processors which is then used to describe the cpu
1527 topology of an ARM System.
1530 bool "Multi-core scheduler support"
1531 depends on ARM_CPU_TOPOLOGY
1533 Multi-core scheduler support improves the CPU scheduler's decision
1534 making when dealing with multi-core CPU chips at a cost of slightly
1535 increased overhead in some places. If unsure say N here.
1538 bool "SMT scheduler support"
1539 depends on ARM_CPU_TOPOLOGY
1541 Improves the CPU scheduler's decision making when dealing with
1542 MultiThreading at a cost of slightly increased overhead in some
1543 places. If unsure say N here.
1548 This option enables support for the ARM system coherency unit
1550 config ARM_ARCH_TIMER
1551 bool "Architected timer support"
1554 This option enables support for the ARM architected timer
1560 This options enables support for the ARM timer and watchdog unit
1563 prompt "Memory split"
1566 Select the desired split between kernel and user memory.
1568 If you are not absolutely sure what you are doing, leave this
1572 bool "3G/1G user/kernel split"
1574 bool "2G/2G user/kernel split"
1576 bool "1G/3G user/kernel split"
1581 default 0x40000000 if VMSPLIT_1G
1582 default 0x80000000 if VMSPLIT_2G
1586 int "Maximum number of CPUs (2-32)"
1592 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
1593 depends on SMP && HOTPLUG && EXPERIMENTAL
1595 Say Y here to experiment with turning CPUs off and on. CPUs
1596 can be controlled through /sys/devices/system/cpu.
1599 bool "Use local timer interrupts"
1602 select HAVE_ARM_TWD if (!ARCH_MSM_SCORPIONMP && !EXYNOS4_MCT)
1604 Enable support for local timers on SMP platforms, rather then the
1605 legacy IPI broadcast method. Local timers allows the system
1606 accounting to be spread across the timer interval, preventing a
1607 "thundering herd" at every timer tick.
1611 default 1024 if ARCH_SHMOBILE || ARCH_TEGRA
1612 default 355 if ARCH_U8500
1613 default 264 if MACH_H4700
1614 default 512 if SOC_OMAP5
1617 Maximum number of GPIOs in the system.
1619 If unsure, leave the default value.
1621 source kernel/Kconfig.preempt
1625 default 200 if ARCH_EBSA110 || ARCH_S3C24XX || ARCH_S5P64X0 || \
1626 ARCH_S5PV210 || ARCH_EXYNOS4
1627 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
1628 default AT91_TIMER_HZ if ARCH_AT91
1629 default SHMOBILE_TIMER_HZ if ARCH_SHMOBILE
1632 config THUMB2_KERNEL
1633 bool "Compile the kernel in Thumb-2 mode (EXPERIMENTAL)"
1634 depends on CPU_V7 && !CPU_V6 && !CPU_V6K && EXPERIMENTAL
1636 select ARM_ASM_UNIFIED
1639 By enabling this option, the kernel will be compiled in
1640 Thumb-2 mode. A compiler/assembler that understand the unified
1641 ARM-Thumb syntax is needed.
1645 config THUMB2_AVOID_R_ARM_THM_JUMP11
1646 bool "Work around buggy Thumb-2 short branch relocations in gas"
1647 depends on THUMB2_KERNEL && MODULES
1650 Various binutils versions can resolve Thumb-2 branches to
1651 locally-defined, preemptible global symbols as short-range "b.n"
1652 branch instructions.
1654 This is a problem, because there's no guarantee the final
1655 destination of the symbol, or any candidate locations for a
1656 trampoline, are within range of the branch. For this reason, the
1657 kernel does not support fixing up the R_ARM_THM_JUMP11 (102)
1658 relocation in modules at all, and it makes little sense to add
1661 The symptom is that the kernel fails with an "unsupported
1662 relocation" error when loading some modules.
1664 Until fixed tools are available, passing
1665 -fno-optimize-sibling-calls to gcc should prevent gcc generating
1666 code which hits this problem, at the cost of a bit of extra runtime
1667 stack usage in some cases.
1669 The problem is described in more detail at:
1670 https://bugs.launchpad.net/binutils-linaro/+bug/725126
1672 Only Thumb-2 kernels are affected.
1674 Unless you are sure your tools don't have this problem, say Y.
1676 config ARM_ASM_UNIFIED
1680 bool "Use the ARM EABI to compile the kernel"
1682 This option allows for the kernel to be compiled using the latest
1683 ARM ABI (aka EABI). This is only useful if you are using a user
1684 space environment that is also compiled with EABI.
1686 Since there are major incompatibilities between the legacy ABI and
1687 EABI, especially with regard to structure member alignment, this
1688 option also changes the kernel syscall calling convention to
1689 disambiguate both ABIs and allow for backward compatibility support
1690 (selected with CONFIG_OABI_COMPAT).
1692 To use this you need GCC version 4.0.0 or later.
1695 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
1696 depends on AEABI && EXPERIMENTAL && !THUMB2_KERNEL
1699 This option preserves the old syscall interface along with the
1700 new (ARM EABI) one. It also provides a compatibility layer to
1701 intercept syscalls that have structure arguments which layout
1702 in memory differs between the legacy ABI and the new ARM EABI
1703 (only for non "thumb" binaries). This option adds a tiny
1704 overhead to all syscalls and produces a slightly larger kernel.
1705 If you know you'll be using only pure EABI user space then you
1706 can say N here. If this option is not selected and you attempt
1707 to execute a legacy ABI binary then the result will be
1708 UNPREDICTABLE (in fact it can be predicted that it won't work
1709 at all). If in doubt say Y.
1711 config ARCH_HAS_HOLES_MEMORYMODEL
1714 config ARCH_SPARSEMEM_ENABLE
1717 config ARCH_SPARSEMEM_DEFAULT
1718 def_bool ARCH_SPARSEMEM_ENABLE
1720 config ARCH_SELECT_MEMORY_MODEL
1721 def_bool ARCH_SPARSEMEM_ENABLE
1723 config HAVE_ARCH_PFN_VALID
1724 def_bool ARCH_HAS_HOLES_MEMORYMODEL || !SPARSEMEM
1727 bool "High Memory Support"
1730 The address space of ARM processors is only 4 Gigabytes large
1731 and it has to accommodate user address space, kernel address
1732 space as well as some memory mapped IO. That means that, if you
1733 have a large amount of physical memory and/or IO, not all of the
1734 memory can be "permanently mapped" by the kernel. The physical
1735 memory that is not permanently mapped is called "high memory".
1737 Depending on the selected kernel/user memory split, minimum
1738 vmalloc space and actual amount of RAM, you may not need this
1739 option which should result in a slightly faster kernel.
1744 bool "Allocate 2nd-level pagetables from highmem"
1747 config HW_PERF_EVENTS
1748 bool "Enable hardware performance counter support for perf events"
1749 depends on PERF_EVENTS && CPU_HAS_PMU
1752 Enable hardware performance counter support for perf events. If
1753 disabled, perf events will use software events only.
1757 config FORCE_MAX_ZONEORDER
1758 int "Maximum zone order" if ARCH_SHMOBILE
1759 range 11 64 if ARCH_SHMOBILE
1760 default "9" if SA1111
1763 The kernel memory allocator divides physically contiguous memory
1764 blocks into "zones", where each zone is a power of two number of
1765 pages. This option selects the largest power of two that the kernel
1766 keeps in the memory allocator. If you need to allocate very large
1767 blocks of physically contiguous memory, then you may need to
1768 increase this value.
1770 This config option is actually maximum order plus one. For example,
1771 a value of 11 means that the largest free memory block is 2^10 pages.
1774 bool "Timer and CPU usage LEDs"
1775 depends on ARCH_CDB89712 || ARCH_EBSA110 || \
1776 ARCH_EBSA285 || ARCH_INTEGRATOR || \
1777 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
1778 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
1779 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
1780 ARCH_AT91 || ARCH_DAVINCI || \
1781 ARCH_KS8695 || MACH_RD88F5182 || ARCH_REALVIEW
1783 If you say Y here, the LEDs on your machine will be used
1784 to provide useful information about your current system status.
1786 If you are compiling a kernel for a NetWinder or EBSA-285, you will
1787 be able to select which LEDs are active using the options below. If
1788 you are compiling a kernel for the EBSA-110 or the LART however, the
1789 red LED will simply flash regularly to indicate that the system is
1790 still functional. It is safe to say Y here if you have a CATS
1791 system, but the driver will do nothing.
1794 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
1795 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1796 || MACH_OMAP_PERSEUS2
1798 depends on !GENERIC_CLOCKEVENTS
1799 default y if ARCH_EBSA110
1801 If you say Y here, one of the system LEDs (the green one on the
1802 NetWinder, the amber one on the EBSA285, or the red one on the LART)
1803 will flash regularly to indicate that the system is still
1804 operational. This is mainly useful to kernel hackers who are
1805 debugging unstable kernels.
1807 The LART uses the same LED for both Timer LED and CPU usage LED
1808 functions. You may choose to use both, but the Timer LED function
1809 will overrule the CPU usage LED.
1812 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
1814 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1815 || MACH_OMAP_PERSEUS2
1818 If you say Y here, the red LED will be used to give a good real
1819 time indication of CPU usage, by lighting whenever the idle task
1820 is not currently executing.
1822 The LART uses the same LED for both Timer LED and CPU usage LED
1823 functions. You may choose to use both, but the Timer LED function
1824 will overrule the CPU usage LED.
1826 config ALIGNMENT_TRAP
1828 depends on CPU_CP15_MMU
1829 default y if !ARCH_EBSA110
1830 select HAVE_PROC_CPU if PROC_FS
1832 ARM processors cannot fetch/store information which is not
1833 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
1834 address divisible by 4. On 32-bit ARM processors, these non-aligned
1835 fetch/store instructions will be emulated in software if you say
1836 here, which has a severe performance impact. This is necessary for
1837 correct operation of some network protocols. With an IP-only
1838 configuration it is safe to say N, otherwise say Y.
1840 config UACCESS_WITH_MEMCPY
1841 bool "Use kernel mem{cpy,set}() for {copy_to,clear}_user() (EXPERIMENTAL)"
1842 depends on MMU && EXPERIMENTAL
1843 default y if CPU_FEROCEON
1845 Implement faster copy_to_user and clear_user methods for CPU
1846 cores where a 8-word STM instruction give significantly higher
1847 memory write throughput than a sequence of individual 32bit stores.
1849 A possible side effect is a slight increase in scheduling latency
1850 between threads sharing the same address space if they invoke
1851 such copy operations with large buffers.
1853 However, if the CPU data cache is using a write-allocate mode,
1854 this option is unlikely to provide any performance gain.
1858 prompt "Enable seccomp to safely compute untrusted bytecode"
1860 This kernel feature is useful for number crunching applications
1861 that may need to compute untrusted bytecode during their
1862 execution. By using pipes or other transports made available to
1863 the process as file descriptors supporting the read/write
1864 syscalls, it's possible to isolate those applications in
1865 their own address space using seccomp. Once seccomp is
1866 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1867 and the task is only allowed to execute a few safe syscalls
1868 defined by each seccomp mode.
1870 config CC_STACKPROTECTOR
1871 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1872 depends on EXPERIMENTAL
1874 This option turns on the -fstack-protector GCC feature. This
1875 feature puts, at the beginning of functions, a canary value on
1876 the stack just before the return address, and validates
1877 the value just before actually returning. Stack based buffer
1878 overflows (that need to overwrite this return address) now also
1879 overwrite the canary, which gets detected and the attack is then
1880 neutralized via a kernel panic.
1881 This feature requires gcc version 4.2 or above.
1883 config DEPRECATED_PARAM_STRUCT
1884 bool "Provide old way to pass kernel parameters"
1886 This was deprecated in 2001 and announced to live on for 5 years.
1887 Some old boot loaders still use this way.
1894 bool "Flattened Device Tree support"
1896 select OF_EARLY_FLATTREE
1899 Include support for flattened device tree machine descriptions.
1901 # Compressed boot loader in ROM. Yes, we really want to ask about
1902 # TEXT and BSS so we preserve their values in the config files.
1903 config ZBOOT_ROM_TEXT
1904 hex "Compressed ROM boot loader base address"
1907 The physical address at which the ROM-able zImage is to be
1908 placed in the target. Platforms which normally make use of
1909 ROM-able zImage formats normally set this to a suitable
1910 value in their defconfig file.
1912 If ZBOOT_ROM is not enabled, this has no effect.
1914 config ZBOOT_ROM_BSS
1915 hex "Compressed ROM boot loader BSS address"
1918 The base address of an area of read/write memory in the target
1919 for the ROM-able zImage which must be available while the
1920 decompressor is running. It must be large enough to hold the
1921 entire decompressed kernel plus an additional 128 KiB.
1922 Platforms which normally make use of ROM-able zImage formats
1923 normally set this to a suitable value in their defconfig file.
1925 If ZBOOT_ROM is not enabled, this has no effect.
1928 bool "Compressed boot loader in ROM/flash"
1929 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
1931 Say Y here if you intend to execute your compressed kernel image
1932 (zImage) directly from ROM or flash. If unsure, say N.
1935 prompt "Include SD/MMC loader in zImage (EXPERIMENTAL)"
1936 depends on ZBOOT_ROM && ARCH_SH7372 && EXPERIMENTAL
1937 default ZBOOT_ROM_NONE
1939 Include experimental SD/MMC loading code in the ROM-able zImage.
1940 With this enabled it is possible to write the ROM-able zImage
1941 kernel image to an MMC or SD card and boot the kernel straight
1942 from the reset vector. At reset the processor Mask ROM will load
1943 the first part of the ROM-able zImage which in turn loads the
1944 rest the kernel image to RAM.
1946 config ZBOOT_ROM_NONE
1947 bool "No SD/MMC loader in zImage (EXPERIMENTAL)"
1949 Do not load image from SD or MMC
1951 config ZBOOT_ROM_MMCIF
1952 bool "Include MMCIF loader in zImage (EXPERIMENTAL)"
1954 Load image from MMCIF hardware block.
1956 config ZBOOT_ROM_SH_MOBILE_SDHI
1957 bool "Include SuperH Mobile SDHI loader in zImage (EXPERIMENTAL)"
1959 Load image from SDHI hardware block
1963 config ARM_APPENDED_DTB
1964 bool "Use appended device tree blob to zImage (EXPERIMENTAL)"
1965 depends on OF && !ZBOOT_ROM && EXPERIMENTAL
1967 With this option, the boot code will look for a device tree binary
1968 (DTB) appended to zImage
1969 (e.g. cat zImage <filename>.dtb > zImage_w_dtb).
1971 This is meant as a backward compatibility convenience for those
1972 systems with a bootloader that can't be upgraded to accommodate
1973 the documented boot protocol using a device tree.
1975 Beware that there is very little in terms of protection against
1976 this option being confused by leftover garbage in memory that might
1977 look like a DTB header after a reboot if no actual DTB is appended
1978 to zImage. Do not leave this option active in a production kernel
1979 if you don't intend to always append a DTB. Proper passing of the
1980 location into r2 of a bootloader provided DTB is always preferable
1983 config ARM_ATAG_DTB_COMPAT
1984 bool "Supplement the appended DTB with traditional ATAG information"
1985 depends on ARM_APPENDED_DTB
1987 Some old bootloaders can't be updated to a DTB capable one, yet
1988 they provide ATAGs with memory configuration, the ramdisk address,
1989 the kernel cmdline string, etc. Such information is dynamically
1990 provided by the bootloader and can't always be stored in a static
1991 DTB. To allow a device tree enabled kernel to be used with such
1992 bootloaders, this option allows zImage to extract the information
1993 from the ATAG list and store it at run time into the appended DTB.
1996 prompt "Kernel command line type" if ARM_ATAG_DTB_COMPAT
1997 default ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER
1999 config ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER
2000 bool "Use bootloader kernel arguments if available"
2002 Uses the command-line options passed by the boot loader instead of
2003 the device tree bootargs property. If the boot loader doesn't provide
2004 any, the device tree bootargs property will be used.
2006 config ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND
2007 bool "Extend with bootloader kernel arguments"
2009 The command-line arguments provided by the boot loader will be
2010 appended to the the device tree bootargs property.
2015 string "Default kernel command string"
2018 On some architectures (EBSA110 and CATS), there is currently no way
2019 for the boot loader to pass arguments to the kernel. For these
2020 architectures, you should supply some command-line options at build
2021 time by entering them here. As a minimum, you should specify the
2022 memory size and the root device (e.g., mem=64M root=/dev/nfs).
2025 prompt "Kernel command line type" if CMDLINE != ""
2026 default CMDLINE_FROM_BOOTLOADER
2028 config CMDLINE_FROM_BOOTLOADER
2029 bool "Use bootloader kernel arguments if available"
2031 Uses the command-line options passed by the boot loader. If
2032 the boot loader doesn't provide any, the default kernel command
2033 string provided in CMDLINE will be used.
2035 config CMDLINE_EXTEND
2036 bool "Extend bootloader kernel arguments"
2038 The command-line arguments provided by the boot loader will be
2039 appended to the default kernel command string.
2041 config CMDLINE_FORCE
2042 bool "Always use the default kernel command string"
2044 Always use the default kernel command string, even if the boot
2045 loader passes other arguments to the kernel.
2046 This is useful if you cannot or don't want to change the
2047 command-line options your boot loader passes to the kernel.
2051 bool "Kernel Execute-In-Place from ROM"
2052 depends on !ZBOOT_ROM && !ARM_LPAE
2054 Execute-In-Place allows the kernel to run from non-volatile storage
2055 directly addressable by the CPU, such as NOR flash. This saves RAM
2056 space since the text section of the kernel is not loaded from flash
2057 to RAM. Read-write sections, such as the data section and stack,
2058 are still copied to RAM. The XIP kernel is not compressed since
2059 it has to run directly from flash, so it will take more space to
2060 store it. The flash address used to link the kernel object files,
2061 and for storing it, is configuration dependent. Therefore, if you
2062 say Y here, you must know the proper physical address where to
2063 store the kernel image depending on your own flash memory usage.
2065 Also note that the make target becomes "make xipImage" rather than
2066 "make zImage" or "make Image". The final kernel binary to put in
2067 ROM memory will be arch/arm/boot/xipImage.
2071 config XIP_PHYS_ADDR
2072 hex "XIP Kernel Physical Location"
2073 depends on XIP_KERNEL
2074 default "0x00080000"
2076 This is the physical address in your flash memory the kernel will
2077 be linked for and stored to. This address is dependent on your
2081 bool "Kexec system call (EXPERIMENTAL)"
2082 depends on EXPERIMENTAL && (!SMP || HOTPLUG_CPU)
2084 kexec is a system call that implements the ability to shutdown your
2085 current kernel, and to start another kernel. It is like a reboot
2086 but it is independent of the system firmware. And like a reboot
2087 you can start any kernel with it, not just Linux.
2089 It is an ongoing process to be certain the hardware in a machine
2090 is properly shutdown, so do not be surprised if this code does not
2091 initially work for you. It may help to enable device hotplugging
2095 bool "Export atags in procfs"
2099 Should the atags used to boot the kernel be exported in an "atags"
2100 file in procfs. Useful with kexec.
2103 bool "Build kdump crash kernel (EXPERIMENTAL)"
2104 depends on EXPERIMENTAL
2106 Generate crash dump after being started by kexec. This should
2107 be normally only set in special crash dump kernels which are
2108 loaded in the main kernel with kexec-tools into a specially
2109 reserved region and then later executed after a crash by
2110 kdump/kexec. The crash dump kernel must be compiled to a
2111 memory address not used by the main kernel
2113 For more details see Documentation/kdump/kdump.txt
2115 config AUTO_ZRELADDR
2116 bool "Auto calculation of the decompressed kernel image address"
2117 depends on !ZBOOT_ROM && !ARCH_U300
2119 ZRELADDR is the physical address where the decompressed kernel
2120 image will be placed. If AUTO_ZRELADDR is selected, the address
2121 will be determined at run-time by masking the current IP with
2122 0xf8000000. This assumes the zImage being placed in the first 128MB
2123 from start of memory.
2127 menu "CPU Power Management"
2131 source "drivers/cpufreq/Kconfig"
2134 tristate "CPUfreq driver for i.MX CPUs"
2135 depends on ARCH_MXC && CPU_FREQ
2136 select CPU_FREQ_TABLE
2138 This enables the CPUfreq driver for i.MX CPUs.
2140 config CPU_FREQ_SA1100
2143 config CPU_FREQ_SA1110
2146 config CPU_FREQ_INTEGRATOR
2147 tristate "CPUfreq driver for ARM Integrator CPUs"
2148 depends on ARCH_INTEGRATOR && CPU_FREQ
2151 This enables the CPUfreq driver for ARM Integrator CPUs.
2153 For details, take a look at <file:Documentation/cpu-freq>.
2159 depends on CPU_FREQ && ARCH_PXA && PXA25x
2161 select CPU_FREQ_TABLE
2162 select CPU_FREQ_DEFAULT_GOV_USERSPACE
2167 Internal configuration node for common cpufreq on Samsung SoC
2169 config CPU_FREQ_S3C24XX
2170 bool "CPUfreq driver for Samsung S3C24XX series CPUs (EXPERIMENTAL)"
2171 depends on ARCH_S3C24XX && CPU_FREQ && EXPERIMENTAL
2174 This enables the CPUfreq driver for the Samsung S3C24XX family
2177 For details, take a look at <file:Documentation/cpu-freq>.
2181 config CPU_FREQ_S3C24XX_PLL
2182 bool "Support CPUfreq changing of PLL frequency (EXPERIMENTAL)"
2183 depends on CPU_FREQ_S3C24XX && EXPERIMENTAL
2185 Compile in support for changing the PLL frequency from the
2186 S3C24XX series CPUfreq driver. The PLL takes time to settle
2187 after a frequency change, so by default it is not enabled.
2189 This also means that the PLL tables for the selected CPU(s) will
2190 be built which may increase the size of the kernel image.
2192 config CPU_FREQ_S3C24XX_DEBUG
2193 bool "Debug CPUfreq Samsung driver core"
2194 depends on CPU_FREQ_S3C24XX
2196 Enable s3c_freq_dbg for the Samsung S3C CPUfreq core
2198 config CPU_FREQ_S3C24XX_IODEBUG
2199 bool "Debug CPUfreq Samsung driver IO timing"
2200 depends on CPU_FREQ_S3C24XX
2202 Enable s3c_freq_iodbg for the Samsung S3C CPUfreq core
2204 config CPU_FREQ_S3C24XX_DEBUGFS
2205 bool "Export debugfs for CPUFreq"
2206 depends on CPU_FREQ_S3C24XX && DEBUG_FS
2208 Export status information via debugfs.
2212 source "drivers/cpuidle/Kconfig"
2216 menu "Floating point emulation"
2218 comment "At least one emulation must be selected"
2221 bool "NWFPE math emulation"
2222 depends on (!AEABI || OABI_COMPAT) && !THUMB2_KERNEL
2224 Say Y to include the NWFPE floating point emulator in the kernel.
2225 This is necessary to run most binaries. Linux does not currently
2226 support floating point hardware so you need to say Y here even if
2227 your machine has an FPA or floating point co-processor podule.
2229 You may say N here if you are going to load the Acorn FPEmulator
2230 early in the bootup.
2233 bool "Support extended precision"
2234 depends on FPE_NWFPE
2236 Say Y to include 80-bit support in the kernel floating-point
2237 emulator. Otherwise, only 32 and 64-bit support is compiled in.
2238 Note that gcc does not generate 80-bit operations by default,
2239 so in most cases this option only enlarges the size of the
2240 floating point emulator without any good reason.
2242 You almost surely want to say N here.
2245 bool "FastFPE math emulation (EXPERIMENTAL)"
2246 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
2248 Say Y here to include the FAST floating point emulator in the kernel.
2249 This is an experimental much faster emulator which now also has full
2250 precision for the mantissa. It does not support any exceptions.
2251 It is very simple, and approximately 3-6 times faster than NWFPE.
2253 It should be sufficient for most programs. It may be not suitable
2254 for scientific calculations, but you have to check this for yourself.
2255 If you do not feel you need a faster FP emulation you should better
2259 bool "VFP-format floating point maths"
2260 depends on CPU_V6 || CPU_V6K || CPU_ARM926T || CPU_V7 || CPU_FEROCEON
2262 Say Y to include VFP support code in the kernel. This is needed
2263 if your hardware includes a VFP unit.
2265 Please see <file:Documentation/arm/VFP/release-notes.txt> for
2266 release notes and additional status information.
2268 Say N if your target does not have VFP hardware.
2276 bool "Advanced SIMD (NEON) Extension support"
2277 depends on VFPv3 && CPU_V7
2279 Say Y to include support code for NEON, the ARMv7 Advanced SIMD
2284 menu "Userspace binary formats"
2286 source "fs/Kconfig.binfmt"
2289 tristate "RISC OS personality"
2292 Say Y here to include the kernel code necessary if you want to run
2293 Acorn RISC OS/Arthur binaries under Linux. This code is still very
2294 experimental; if this sounds frightening, say N and sleep in peace.
2295 You can also say M here to compile this support as a module (which
2296 will be called arthur).
2300 menu "Power management options"
2302 source "kernel/power/Kconfig"
2304 config ARCH_SUSPEND_POSSIBLE
2305 depends on !ARCH_S5PC100 && !ARCH_TEGRA
2306 depends on CPU_ARM920T || CPU_ARM926T || CPU_SA1100 || \
2307 CPU_V6 || CPU_V6K || CPU_V7 || CPU_XSC3 || CPU_XSCALE || CPU_MOHAWK
2310 config ARM_CPU_SUSPEND
2315 source "net/Kconfig"
2317 source "drivers/Kconfig"
2321 source "arch/arm/Kconfig.debug"
2323 source "security/Kconfig"
2325 source "crypto/Kconfig"
2327 source "lib/Kconfig"