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 ARCH_BINFMT_ELF_RANDOMIZE_PIE
20 select HAVE_GENERIC_DMA_COHERENT
21 select HAVE_KERNEL_GZIP
22 select HAVE_KERNEL_LZO
23 select HAVE_KERNEL_LZMA
25 select HAVE_PERF_EVENTS
26 select PERF_USE_VMALLOC
27 select HAVE_REGS_AND_STACK_ACCESS_API
28 select HAVE_HW_BREAKPOINT if (PERF_EVENTS && (CPU_V6 || CPU_V6K || CPU_V7))
29 select HAVE_C_RECORDMCOUNT
30 select HAVE_GENERIC_HARDIRQS
31 select HAVE_SPARSE_IRQ
32 select GENERIC_IRQ_SHOW
33 select CPU_PM if (SUSPEND || CPU_IDLE)
34 select GENERIC_PCI_IOMAP
36 The ARM series is a line of low-power-consumption RISC chip designs
37 licensed by ARM Ltd and targeted at embedded applications and
38 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
39 manufactured, but legacy ARM-based PC hardware remains popular in
40 Europe. There is an ARM Linux project with a web page at
41 <http://www.arm.linux.org.uk/>.
43 config ARM_HAS_SG_CHAIN
52 config SYS_SUPPORTS_APM_EMULATION
55 config HAVE_SCHED_CLOCK
61 config ARCH_USES_GETTIMEOFFSET
65 config GENERIC_CLOCKEVENTS
68 config GENERIC_CLOCKEVENTS_BROADCAST
70 depends on GENERIC_CLOCKEVENTS
79 select GENERIC_ALLOCATOR
90 The Extended Industry Standard Architecture (EISA) bus was
91 developed as an open alternative to the IBM MicroChannel bus.
93 The EISA bus provided some of the features of the IBM MicroChannel
94 bus while maintaining backward compatibility with cards made for
95 the older ISA bus. The EISA bus saw limited use between 1988 and
96 1995 when it was made obsolete by the PCI bus.
98 Say Y here if you are building a kernel for an EISA-based machine.
108 MicroChannel Architecture is found in some IBM PS/2 machines and
109 laptops. It is a bus system similar to PCI or ISA. See
110 <file:Documentation/mca.txt> (and especially the web page given
111 there) before attempting to build an MCA bus kernel.
113 config STACKTRACE_SUPPORT
117 config HAVE_LATENCYTOP_SUPPORT
122 config LOCKDEP_SUPPORT
126 config TRACE_IRQFLAGS_SUPPORT
130 config HARDIRQS_SW_RESEND
134 config GENERIC_IRQ_PROBE
138 config GENERIC_LOCKBREAK
141 depends on SMP && PREEMPT
143 config RWSEM_GENERIC_SPINLOCK
147 config RWSEM_XCHGADD_ALGORITHM
150 config ARCH_HAS_ILOG2_U32
153 config ARCH_HAS_ILOG2_U64
156 config ARCH_HAS_CPUFREQ
159 Internal node to signify that the ARCH has CPUFREQ support
160 and that the relevant menu configurations are displayed for
163 config ARCH_HAS_CPU_IDLE_WAIT
166 config GENERIC_HWEIGHT
170 config GENERIC_CALIBRATE_DELAY
174 config ARCH_MAY_HAVE_PC_FDC
180 config NEED_DMA_MAP_STATE
183 config GENERIC_ISA_DMA
189 config NEED_RET_TO_USER
197 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
198 default DRAM_BASE if REMAP_VECTORS_TO_RAM
201 The base address of exception vectors.
203 config ARM_PATCH_PHYS_VIRT
204 bool "Patch physical to virtual translations at runtime" if EMBEDDED
206 depends on !XIP_KERNEL && MMU
207 depends on !ARCH_REALVIEW || !SPARSEMEM
209 Patch phys-to-virt and virt-to-phys translation functions at
210 boot and module load time according to the position of the
211 kernel in system memory.
213 This can only be used with non-XIP MMU kernels where the base
214 of physical memory is at a 16MB boundary.
216 Only disable this option if you know that you do not require
217 this feature (eg, building a kernel for a single machine) and
218 you need to shrink the kernel to the minimal size.
220 config NEED_MACH_MEMORY_H
223 Select this when mach/memory.h is required to provide special
224 definitions for this platform. The need for mach/memory.h should
225 be avoided when possible.
228 hex "Physical address of main memory" if MMU
229 depends on !ARM_PATCH_PHYS_VIRT && !NEED_MACH_MEMORY_H
230 default DRAM_BASE if !MMU
232 Please provide the physical address corresponding to the
233 location of main memory in your system.
239 source "init/Kconfig"
241 source "kernel/Kconfig.freezer"
246 bool "MMU-based Paged Memory Management Support"
249 Select if you want MMU-based virtualised addressing space
250 support by paged memory management. If unsure, say 'Y'.
253 # The "ARM system type" choice list is ordered alphabetically by option
254 # text. Please add new entries in the option alphabetic order.
257 prompt "ARM system type"
258 default ARCH_VERSATILE
260 config ARCH_INTEGRATOR
261 bool "ARM Ltd. Integrator family"
263 select ARCH_HAS_CPUFREQ
265 select HAVE_MACH_CLKDEV
268 select GENERIC_CLOCKEVENTS
269 select PLAT_VERSATILE
270 select PLAT_VERSATILE_FPGA_IRQ
271 select NEED_MACH_MEMORY_H
273 Support for ARM's Integrator platform.
276 bool "ARM Ltd. RealView family"
279 select HAVE_MACH_CLKDEV
281 select GENERIC_CLOCKEVENTS
282 select ARCH_WANT_OPTIONAL_GPIOLIB
283 select PLAT_VERSATILE
284 select PLAT_VERSATILE_CLCD
285 select ARM_TIMER_SP804
286 select GPIO_PL061 if GPIOLIB
287 select NEED_MACH_MEMORY_H
289 This enables support for ARM Ltd RealView boards.
291 config ARCH_VERSATILE
292 bool "ARM Ltd. Versatile family"
296 select HAVE_MACH_CLKDEV
298 select GENERIC_CLOCKEVENTS
299 select ARCH_WANT_OPTIONAL_GPIOLIB
300 select PLAT_VERSATILE
301 select PLAT_VERSATILE_CLCD
302 select PLAT_VERSATILE_FPGA_IRQ
303 select ARM_TIMER_SP804
305 This enables support for ARM Ltd Versatile board.
308 bool "ARM Ltd. Versatile Express family"
309 select ARCH_WANT_OPTIONAL_GPIOLIB
311 select ARM_TIMER_SP804
313 select HAVE_MACH_CLKDEV
314 select GENERIC_CLOCKEVENTS
316 select HAVE_PATA_PLATFORM
318 select PLAT_VERSATILE
319 select PLAT_VERSATILE_CLCD
321 This enables support for the ARM Ltd Versatile Express boards.
325 select ARCH_REQUIRE_GPIOLIB
329 This enables support for systems based on the Atmel AT91RM9200,
330 AT91SAM9 and AT91CAP9 processors.
333 bool "Broadcom BCMRING"
337 select ARM_TIMER_SP804
339 select GENERIC_CLOCKEVENTS
340 select ARCH_WANT_OPTIONAL_GPIOLIB
342 Support for Broadcom's BCMRing platform.
345 bool "Calxeda Highbank-based"
346 select ARCH_WANT_OPTIONAL_GPIOLIB
349 select ARM_TIMER_SP804
353 select GENERIC_CLOCKEVENTS
358 Support for the Calxeda Highbank SoC based boards.
361 bool "Cirrus Logic CLPS711x/EP721x-based"
363 select ARCH_USES_GETTIMEOFFSET
364 select NEED_MACH_MEMORY_H
366 Support for Cirrus Logic 711x/721x based boards.
369 bool "Cavium Networks CNS3XXX family"
371 select GENERIC_CLOCKEVENTS
373 select MIGHT_HAVE_CACHE_L2X0
374 select MIGHT_HAVE_PCI
375 select PCI_DOMAINS if PCI
377 Support for Cavium Networks CNS3XXX platform.
380 bool "Cortina Systems Gemini"
382 select ARCH_REQUIRE_GPIOLIB
383 select ARCH_USES_GETTIMEOFFSET
385 Support for the Cortina Systems Gemini family SoCs
388 bool "CSR SiRFSoC PRIMA2 ARM Cortex A9 Platform"
391 select GENERIC_CLOCKEVENTS
393 select GENERIC_IRQ_CHIP
394 select MIGHT_HAVE_CACHE_L2X0
398 Support for CSR SiRFSoC ARM Cortex A9 Platform
405 select ARCH_USES_GETTIMEOFFSET
406 select NEED_MACH_MEMORY_H
408 This is an evaluation board for the StrongARM processor available
409 from Digital. It has limited hardware on-board, including an
410 Ethernet interface, two PCMCIA sockets, two serial ports and a
419 select ARCH_REQUIRE_GPIOLIB
420 select ARCH_HAS_HOLES_MEMORYMODEL
421 select ARCH_USES_GETTIMEOFFSET
422 select NEED_MACH_MEMORY_H
424 This enables support for the Cirrus EP93xx series of CPUs.
426 config ARCH_FOOTBRIDGE
430 select GENERIC_CLOCKEVENTS
432 select NEED_MACH_MEMORY_H
434 Support for systems based on the DC21285 companion chip
435 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
438 bool "Freescale MXC/iMX-based"
439 select GENERIC_CLOCKEVENTS
440 select ARCH_REQUIRE_GPIOLIB
443 select GENERIC_IRQ_CHIP
444 select HAVE_SCHED_CLOCK
445 select MULTI_IRQ_HANDLER
447 Support for Freescale MXC/iMX-based family of processors
450 bool "Freescale MXS-based"
451 select GENERIC_CLOCKEVENTS
452 select ARCH_REQUIRE_GPIOLIB
455 select HAVE_CLK_PREPARE
457 Support for Freescale MXS-based family of processors
460 bool "Hilscher NetX based"
464 select GENERIC_CLOCKEVENTS
466 This enables support for systems based on the Hilscher NetX Soc
469 bool "Hynix HMS720x-based"
472 select ARCH_USES_GETTIMEOFFSET
474 This enables support for systems based on the Hynix HMS720x
482 select ARCH_SUPPORTS_MSI
484 select NEED_MACH_MEMORY_H
485 select NEED_RET_TO_USER
487 Support for Intel's IOP13XX (XScale) family of processors.
493 select NEED_RET_TO_USER
496 select ARCH_REQUIRE_GPIOLIB
498 Support for Intel's 80219 and IOP32X (XScale) family of
505 select NEED_RET_TO_USER
508 select ARCH_REQUIRE_GPIOLIB
510 Support for Intel's IOP33X (XScale) family of processors.
517 select ARCH_USES_GETTIMEOFFSET
518 select NEED_MACH_MEMORY_H
520 Support for Intel's IXP23xx (XScale) family of processors.
523 bool "IXP2400/2800-based"
527 select ARCH_USES_GETTIMEOFFSET
528 select NEED_MACH_MEMORY_H
530 Support for Intel's IXP2400/2800 (XScale) family of processors.
538 select GENERIC_CLOCKEVENTS
539 select HAVE_SCHED_CLOCK
540 select MIGHT_HAVE_PCI
541 select DMABOUNCE if PCI
543 Support for Intel's IXP4XX (XScale) family of processors.
549 select ARCH_REQUIRE_GPIOLIB
550 select GENERIC_CLOCKEVENTS
553 Support for the Marvell Dove SoC 88AP510
556 bool "Marvell Kirkwood"
559 select ARCH_REQUIRE_GPIOLIB
560 select GENERIC_CLOCKEVENTS
563 Support for the following Marvell Kirkwood series SoCs:
564 88F6180, 88F6192 and 88F6281.
570 select ARCH_REQUIRE_GPIOLIB
573 select USB_ARCH_HAS_OHCI
575 select GENERIC_CLOCKEVENTS
577 Support for the NXP LPC32XX family of processors
580 bool "Marvell MV78xx0"
583 select ARCH_REQUIRE_GPIOLIB
584 select GENERIC_CLOCKEVENTS
587 Support for the following Marvell MV78xx0 series SoCs:
595 select ARCH_REQUIRE_GPIOLIB
596 select GENERIC_CLOCKEVENTS
599 Support for the following Marvell Orion 5x series SoCs:
600 Orion-1 (5181), Orion-VoIP (5181L), Orion-NAS (5182),
601 Orion-2 (5281), Orion-1-90 (6183).
604 bool "Marvell PXA168/910/MMP2"
606 select ARCH_REQUIRE_GPIOLIB
608 select GENERIC_CLOCKEVENTS
610 select HAVE_SCHED_CLOCK
614 select GENERIC_ALLOCATOR
616 Support for Marvell's PXA168/PXA910(MMP) and MMP2 processor line.
619 bool "Micrel/Kendin KS8695"
621 select ARCH_REQUIRE_GPIOLIB
622 select ARCH_USES_GETTIMEOFFSET
623 select NEED_MACH_MEMORY_H
625 Support for Micrel/Kendin KS8695 "Centaur" (ARM922T) based
626 System-on-Chip devices.
629 bool "Nuvoton W90X900 CPU"
631 select ARCH_REQUIRE_GPIOLIB
634 select GENERIC_CLOCKEVENTS
636 Support for Nuvoton (Winbond logic dept.) ARM9 processor,
637 At present, the w90x900 has been renamed nuc900, regarding
638 the ARM series product line, you can login the following
639 link address to know more.
641 <http://www.nuvoton.com/hq/enu/ProductAndSales/ProductLines/
642 ConsumerElectronicsIC/ARMMicrocontroller/ARMMicrocontroller>
648 select GENERIC_CLOCKEVENTS
651 select HAVE_SCHED_CLOCK
653 select MIGHT_HAVE_CACHE_L2X0
654 select ARCH_HAS_CPUFREQ
656 This enables support for NVIDIA Tegra based systems (Tegra APX,
657 Tegra 6xx and Tegra 2 series).
659 config ARCH_PICOXCELL
660 bool "Picochip picoXcell"
661 select ARCH_REQUIRE_GPIOLIB
662 select ARM_PATCH_PHYS_VIRT
666 select GENERIC_CLOCKEVENTS
668 select HAVE_SCHED_CLOCK
674 This enables support for systems based on the Picochip picoXcell
675 family of Femtocell devices. The picoxcell support requires device tree
679 bool "Philips Nexperia PNX4008 Mobile"
682 select ARCH_USES_GETTIMEOFFSET
684 This enables support for Philips PNX4008 mobile platform.
687 bool "PXA2xx/PXA3xx-based"
690 select ARCH_HAS_CPUFREQ
693 select ARCH_REQUIRE_GPIOLIB
694 select GENERIC_CLOCKEVENTS
696 select HAVE_SCHED_CLOCK
701 select MULTI_IRQ_HANDLER
702 select ARM_CPU_SUSPEND if PM
705 Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
710 select GENERIC_CLOCKEVENTS
711 select ARCH_REQUIRE_GPIOLIB
714 Support for Qualcomm MSM/QSD based systems. This runs on the
715 apps processor of the MSM/QSD and depends on a shared memory
716 interface to the modem processor which runs the baseband
717 stack and controls some vital subsystems
718 (clock and power control, etc).
721 bool "Renesas SH-Mobile / R-Mobile"
724 select HAVE_MACH_CLKDEV
726 select GENERIC_CLOCKEVENTS
727 select MIGHT_HAVE_CACHE_L2X0
730 select MULTI_IRQ_HANDLER
731 select PM_GENERIC_DOMAINS if PM
732 select NEED_MACH_MEMORY_H
734 Support for Renesas's SH-Mobile and R-Mobile ARM platforms.
741 select ARCH_MAY_HAVE_PC_FDC
742 select HAVE_PATA_PLATFORM
745 select ARCH_SPARSEMEM_ENABLE
746 select ARCH_USES_GETTIMEOFFSET
748 select NEED_MACH_MEMORY_H
750 On the Acorn Risc-PC, Linux can support the internal IDE disk and
751 CD-ROM interface, serial and parallel port, and the floppy drive.
758 select ARCH_SPARSEMEM_ENABLE
760 select ARCH_HAS_CPUFREQ
762 select GENERIC_CLOCKEVENTS
764 select HAVE_SCHED_CLOCK
766 select ARCH_REQUIRE_GPIOLIB
768 select NEED_MACH_MEMORY_H
770 Support for StrongARM 11x0 based boards.
773 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2416, S3C2440, S3C2442, S3C2443, S3C2450"
775 select ARCH_HAS_CPUFREQ
778 select ARCH_USES_GETTIMEOFFSET
779 select HAVE_S3C2410_I2C if I2C
781 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
782 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
783 the Samsung SMDK2410 development board (and derivatives).
785 Note, the S3C2416 and the S3C2450 are so close that they even share
786 the same SoC ID code. This means that there is no separate machine
787 directory (no arch/arm/mach-s3c2450) as the S3C2416 was first.
790 bool "Samsung S3C64XX"
798 select ARCH_USES_GETTIMEOFFSET
799 select ARCH_HAS_CPUFREQ
800 select ARCH_REQUIRE_GPIOLIB
801 select SAMSUNG_CLKSRC
802 select SAMSUNG_IRQ_VIC_TIMER
803 select S3C_GPIO_TRACK
805 select USB_ARCH_HAS_OHCI
806 select SAMSUNG_GPIOLIB_4BIT
807 select HAVE_S3C2410_I2C if I2C
808 select HAVE_S3C2410_WATCHDOG if WATCHDOG
810 Samsung S3C64XX series based systems
813 bool "Samsung S5P6440 S5P6450"
819 select HAVE_S3C2410_WATCHDOG if WATCHDOG
820 select GENERIC_CLOCKEVENTS
821 select HAVE_SCHED_CLOCK
822 select HAVE_S3C2410_I2C if I2C
823 select HAVE_S3C_RTC if RTC_CLASS
825 Samsung S5P64X0 CPU based systems, such as the Samsung SMDK6440,
829 bool "Samsung S5PC100"
834 select ARCH_USES_GETTIMEOFFSET
835 select HAVE_S3C2410_I2C if I2C
836 select HAVE_S3C_RTC if RTC_CLASS
837 select HAVE_S3C2410_WATCHDOG if WATCHDOG
839 Samsung S5PC100 series based systems
842 bool "Samsung S5PV210/S5PC110"
844 select ARCH_SPARSEMEM_ENABLE
845 select ARCH_HAS_HOLES_MEMORYMODEL
850 select ARCH_HAS_CPUFREQ
851 select GENERIC_CLOCKEVENTS
852 select HAVE_SCHED_CLOCK
853 select HAVE_S3C2410_I2C if I2C
854 select HAVE_S3C_RTC if RTC_CLASS
855 select HAVE_S3C2410_WATCHDOG if WATCHDOG
856 select NEED_MACH_MEMORY_H
858 Samsung S5PV210/S5PC110 series based systems
861 bool "SAMSUNG EXYNOS"
863 select ARCH_SPARSEMEM_ENABLE
864 select ARCH_HAS_HOLES_MEMORYMODEL
868 select ARCH_HAS_CPUFREQ
869 select GENERIC_CLOCKEVENTS
870 select HAVE_S3C_RTC if RTC_CLASS
871 select HAVE_S3C2410_I2C if I2C
872 select HAVE_S3C2410_WATCHDOG if WATCHDOG
873 select NEED_MACH_MEMORY_H
875 Support for SAMSUNG's EXYNOS SoCs (EXYNOS4/5)
884 select ARCH_USES_GETTIMEOFFSET
885 select NEED_MACH_MEMORY_H
887 Support for the StrongARM based Digital DNARD machine, also known
888 as "Shark" (<http://www.shark-linux.de/shark.html>).
891 bool "ST-Ericsson U300 Series"
895 select HAVE_SCHED_CLOCK
898 select ARM_PATCH_PHYS_VIRT
900 select GENERIC_CLOCKEVENTS
902 select HAVE_MACH_CLKDEV
904 select ARCH_REQUIRE_GPIOLIB
906 Support for ST-Ericsson U300 series mobile platforms.
909 bool "ST-Ericsson U8500 Series"
912 select GENERIC_CLOCKEVENTS
914 select ARCH_REQUIRE_GPIOLIB
915 select ARCH_HAS_CPUFREQ
917 select MIGHT_HAVE_CACHE_L2X0
919 Support for ST-Ericsson's Ux500 architecture
922 bool "STMicroelectronics Nomadik"
927 select GENERIC_CLOCKEVENTS
928 select MIGHT_HAVE_CACHE_L2X0
929 select ARCH_REQUIRE_GPIOLIB
931 Support for the Nomadik platform by ST-Ericsson
935 select GENERIC_CLOCKEVENTS
936 select ARCH_REQUIRE_GPIOLIB
940 select GENERIC_ALLOCATOR
941 select GENERIC_IRQ_CHIP
942 select ARCH_HAS_HOLES_MEMORYMODEL
944 Support for TI's DaVinci platform.
949 select ARCH_REQUIRE_GPIOLIB
950 select ARCH_HAS_CPUFREQ
952 select GENERIC_CLOCKEVENTS
953 select HAVE_SCHED_CLOCK
954 select ARCH_HAS_HOLES_MEMORYMODEL
956 Support for TI's OMAP platform (OMAP1/2/3/4).
961 select ARCH_REQUIRE_GPIOLIB
964 select GENERIC_CLOCKEVENTS
967 Support for ST's SPEAr platform (SPEAr3xx, SPEAr6xx and SPEAr13xx).
970 bool "VIA/WonderMedia 85xx"
973 select ARCH_HAS_CPUFREQ
974 select GENERIC_CLOCKEVENTS
975 select ARCH_REQUIRE_GPIOLIB
978 Support for VIA/WonderMedia VT8500/WM85xx System-on-Chip.
981 bool "Xilinx Zynq ARM Cortex A9 Platform"
983 select GENERIC_CLOCKEVENTS
988 select MIGHT_HAVE_CACHE_L2X0
991 Support for Xilinx Zynq ARM Cortex A9 Platform
995 # This is sorted alphabetically by mach-* pathname. However, plat-*
996 # Kconfigs may be included either alphabetically (according to the
997 # plat- suffix) or along side the corresponding mach-* source.
999 source "arch/arm/mach-at91/Kconfig"
1001 source "arch/arm/mach-bcmring/Kconfig"
1003 source "arch/arm/mach-clps711x/Kconfig"
1005 source "arch/arm/mach-cns3xxx/Kconfig"
1007 source "arch/arm/mach-davinci/Kconfig"
1009 source "arch/arm/mach-dove/Kconfig"
1011 source "arch/arm/mach-ep93xx/Kconfig"
1013 source "arch/arm/mach-footbridge/Kconfig"
1015 source "arch/arm/mach-gemini/Kconfig"
1017 source "arch/arm/mach-h720x/Kconfig"
1019 source "arch/arm/mach-integrator/Kconfig"
1021 source "arch/arm/mach-iop32x/Kconfig"
1023 source "arch/arm/mach-iop33x/Kconfig"
1025 source "arch/arm/mach-iop13xx/Kconfig"
1027 source "arch/arm/mach-ixp4xx/Kconfig"
1029 source "arch/arm/mach-ixp2000/Kconfig"
1031 source "arch/arm/mach-ixp23xx/Kconfig"
1033 source "arch/arm/mach-kirkwood/Kconfig"
1035 source "arch/arm/mach-ks8695/Kconfig"
1037 source "arch/arm/mach-lpc32xx/Kconfig"
1039 source "arch/arm/mach-msm/Kconfig"
1041 source "arch/arm/mach-mv78xx0/Kconfig"
1043 source "arch/arm/plat-mxc/Kconfig"
1045 source "arch/arm/mach-mxs/Kconfig"
1047 source "arch/arm/mach-netx/Kconfig"
1049 source "arch/arm/mach-nomadik/Kconfig"
1050 source "arch/arm/plat-nomadik/Kconfig"
1052 source "arch/arm/plat-omap/Kconfig"
1054 source "arch/arm/mach-omap1/Kconfig"
1056 source "arch/arm/mach-omap2/Kconfig"
1058 source "arch/arm/mach-orion5x/Kconfig"
1060 source "arch/arm/mach-pxa/Kconfig"
1061 source "arch/arm/plat-pxa/Kconfig"
1063 source "arch/arm/mach-mmp/Kconfig"
1065 source "arch/arm/mach-realview/Kconfig"
1067 source "arch/arm/mach-sa1100/Kconfig"
1069 source "arch/arm/plat-samsung/Kconfig"
1070 source "arch/arm/plat-s3c24xx/Kconfig"
1071 source "arch/arm/plat-s5p/Kconfig"
1073 source "arch/arm/plat-spear/Kconfig"
1076 source "arch/arm/mach-s3c2410/Kconfig"
1077 source "arch/arm/mach-s3c2412/Kconfig"
1078 source "arch/arm/mach-s3c2416/Kconfig"
1079 source "arch/arm/mach-s3c2440/Kconfig"
1080 source "arch/arm/mach-s3c2443/Kconfig"
1084 source "arch/arm/mach-s3c64xx/Kconfig"
1087 source "arch/arm/mach-s5p64x0/Kconfig"
1089 source "arch/arm/mach-s5pc100/Kconfig"
1091 source "arch/arm/mach-s5pv210/Kconfig"
1093 source "arch/arm/mach-exynos/Kconfig"
1095 source "arch/arm/mach-shmobile/Kconfig"
1097 source "arch/arm/mach-tegra/Kconfig"
1099 source "arch/arm/mach-u300/Kconfig"
1101 source "arch/arm/mach-ux500/Kconfig"
1103 source "arch/arm/mach-versatile/Kconfig"
1105 source "arch/arm/mach-vexpress/Kconfig"
1106 source "arch/arm/plat-versatile/Kconfig"
1108 source "arch/arm/mach-vt8500/Kconfig"
1110 source "arch/arm/mach-w90x900/Kconfig"
1112 # Definitions to make life easier
1118 select GENERIC_CLOCKEVENTS
1119 select HAVE_SCHED_CLOCK
1124 select GENERIC_IRQ_CHIP
1125 select HAVE_SCHED_CLOCK
1130 config PLAT_VERSATILE
1133 config ARM_TIMER_SP804
1137 source arch/arm/mm/Kconfig
1141 default 16 if ARCH_EP93XX
1145 bool "Enable iWMMXt support"
1146 depends on CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_PJ4
1147 default y if PXA27x || PXA3xx || PXA95x || ARCH_MMP
1149 Enable support for iWMMXt context switching at run time if
1150 running on a CPU that supports it.
1154 depends on CPU_XSCALE
1158 depends on (CPU_V6 || CPU_V6K || CPU_V7 || XSCALE_PMU) && \
1159 (!ARCH_OMAP3 || OMAP3_EMU)
1163 config MULTI_IRQ_HANDLER
1166 Allow each machine to specify it's own IRQ handler at run time.
1169 source "arch/arm/Kconfig-nommu"
1172 config ARM_ERRATA_411920
1173 bool "ARM errata: Invalidation of the Instruction Cache operation can fail"
1174 depends on CPU_V6 || CPU_V6K
1176 Invalidation of the Instruction Cache operation can
1177 fail. This erratum is present in 1136 (before r1p4), 1156 and 1176.
1178 It does not affect the MPCore. This option enables the ARM Ltd.
1179 recommended workaround.
1181 config ARM_ERRATA_430973
1182 bool "ARM errata: Stale prediction on replaced interworking branch"
1185 This option enables the workaround for the 430973 Cortex-A8
1186 (r1p0..r1p2) erratum. If a code sequence containing an ARM/Thumb
1187 interworking branch is replaced with another code sequence at the
1188 same virtual address, whether due to self-modifying code or virtual
1189 to physical address re-mapping, Cortex-A8 does not recover from the
1190 stale interworking branch prediction. This results in Cortex-A8
1191 executing the new code sequence in the incorrect ARM or Thumb state.
1192 The workaround enables the BTB/BTAC operations by setting ACTLR.IBE
1193 and also flushes the branch target cache at every context switch.
1194 Note that setting specific bits in the ACTLR register may not be
1195 available in non-secure mode.
1197 config ARM_ERRATA_458693
1198 bool "ARM errata: Processor deadlock when a false hazard is created"
1201 This option enables the workaround for the 458693 Cortex-A8 (r2p0)
1202 erratum. For very specific sequences of memory operations, it is
1203 possible for a hazard condition intended for a cache line to instead
1204 be incorrectly associated with a different cache line. This false
1205 hazard might then cause a processor deadlock. The workaround enables
1206 the L1 caching of the NEON accesses and disables the PLD instruction
1207 in the ACTLR register. Note that setting specific bits in the ACTLR
1208 register may not be available in non-secure mode.
1210 config ARM_ERRATA_460075
1211 bool "ARM errata: Data written to the L2 cache can be overwritten with stale data"
1214 This option enables the workaround for the 460075 Cortex-A8 (r2p0)
1215 erratum. Any asynchronous access to the L2 cache may encounter a
1216 situation in which recent store transactions to the L2 cache are lost
1217 and overwritten with stale memory contents from external memory. The
1218 workaround disables the write-allocate mode for the L2 cache via the
1219 ACTLR register. Note that setting specific bits in the ACTLR register
1220 may not be available in non-secure mode.
1222 config ARM_ERRATA_742230
1223 bool "ARM errata: DMB operation may be faulty"
1224 depends on CPU_V7 && SMP
1226 This option enables the workaround for the 742230 Cortex-A9
1227 (r1p0..r2p2) erratum. Under rare circumstances, a DMB instruction
1228 between two write operations may not ensure the correct visibility
1229 ordering of the two writes. This workaround sets a specific bit in
1230 the diagnostic register of the Cortex-A9 which causes the DMB
1231 instruction to behave as a DSB, ensuring the correct behaviour of
1234 config ARM_ERRATA_742231
1235 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
1236 depends on CPU_V7 && SMP
1238 This option enables the workaround for the 742231 Cortex-A9
1239 (r2p0..r2p2) erratum. Under certain conditions, specific to the
1240 Cortex-A9 MPCore micro-architecture, two CPUs working in SMP mode,
1241 accessing some data located in the same cache line, may get corrupted
1242 data due to bad handling of the address hazard when the line gets
1243 replaced from one of the CPUs at the same time as another CPU is
1244 accessing it. This workaround sets specific bits in the diagnostic
1245 register of the Cortex-A9 which reduces the linefill issuing
1246 capabilities of the processor.
1248 config PL310_ERRATA_588369
1249 bool "PL310 errata: Clean & Invalidate maintenance operations do not invalidate clean lines"
1250 depends on CACHE_L2X0
1252 The PL310 L2 cache controller implements three types of Clean &
1253 Invalidate maintenance operations: by Physical Address
1254 (offset 0x7F0), by Index/Way (0x7F8) and by Way (0x7FC).
1255 They are architecturally defined to behave as the execution of a
1256 clean operation followed immediately by an invalidate operation,
1257 both performing to the same memory location. This functionality
1258 is not correctly implemented in PL310 as clean lines are not
1259 invalidated as a result of these operations.
1261 config ARM_ERRATA_720789
1262 bool "ARM errata: TLBIASIDIS and TLBIMVAIS operations can broadcast a faulty ASID"
1265 This option enables the workaround for the 720789 Cortex-A9 (prior to
1266 r2p0) erratum. A faulty ASID can be sent to the other CPUs for the
1267 broadcasted CP15 TLB maintenance operations TLBIASIDIS and TLBIMVAIS.
1268 As a consequence of this erratum, some TLB entries which should be
1269 invalidated are not, resulting in an incoherency in the system page
1270 tables. The workaround changes the TLB flushing routines to invalidate
1271 entries regardless of the ASID.
1273 config PL310_ERRATA_727915
1274 bool "PL310 errata: Background Clean & Invalidate by Way operation can cause data corruption"
1275 depends on CACHE_L2X0
1277 PL310 implements the Clean & Invalidate by Way L2 cache maintenance
1278 operation (offset 0x7FC). This operation runs in background so that
1279 PL310 can handle normal accesses while it is in progress. Under very
1280 rare circumstances, due to this erratum, write data can be lost when
1281 PL310 treats a cacheable write transaction during a Clean &
1282 Invalidate by Way operation.
1284 config ARM_ERRATA_743622
1285 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
1288 This option enables the workaround for the 743622 Cortex-A9
1289 (r2p*) erratum. Under very rare conditions, a faulty
1290 optimisation in the Cortex-A9 Store Buffer may lead to data
1291 corruption. This workaround sets a specific bit in the diagnostic
1292 register of the Cortex-A9 which disables the Store Buffer
1293 optimisation, preventing the defect from occurring. This has no
1294 visible impact on the overall performance or power consumption of the
1297 config ARM_ERRATA_751472
1298 bool "ARM errata: Interrupted ICIALLUIS may prevent completion of broadcasted operation"
1301 This option enables the workaround for the 751472 Cortex-A9 (prior
1302 to r3p0) erratum. An interrupted ICIALLUIS operation may prevent the
1303 completion of a following broadcasted operation if the second
1304 operation is received by a CPU before the ICIALLUIS has completed,
1305 potentially leading to corrupted entries in the cache or TLB.
1307 config PL310_ERRATA_753970
1308 bool "PL310 errata: cache sync operation may be faulty"
1309 depends on CACHE_PL310
1311 This option enables the workaround for the 753970 PL310 (r3p0) erratum.
1313 Under some condition the effect of cache sync operation on
1314 the store buffer still remains when the operation completes.
1315 This means that the store buffer is always asked to drain and
1316 this prevents it from merging any further writes. The workaround
1317 is to replace the normal offset of cache sync operation (0x730)
1318 by another offset targeting an unmapped PL310 register 0x740.
1319 This has the same effect as the cache sync operation: store buffer
1320 drain and waiting for all buffers empty.
1322 config ARM_ERRATA_754322
1323 bool "ARM errata: possible faulty MMU translations following an ASID switch"
1326 This option enables the workaround for the 754322 Cortex-A9 (r2p*,
1327 r3p*) erratum. A speculative memory access may cause a page table walk
1328 which starts prior to an ASID switch but completes afterwards. This
1329 can populate the micro-TLB with a stale entry which may be hit with
1330 the new ASID. This workaround places two dsb instructions in the mm
1331 switching code so that no page table walks can cross the ASID switch.
1333 config ARM_ERRATA_754327
1334 bool "ARM errata: no automatic Store Buffer drain"
1335 depends on CPU_V7 && SMP
1337 This option enables the workaround for the 754327 Cortex-A9 (prior to
1338 r2p0) erratum. The Store Buffer does not have any automatic draining
1339 mechanism and therefore a livelock may occur if an external agent
1340 continuously polls a memory location waiting to observe an update.
1341 This workaround defines cpu_relax() as smp_mb(), preventing correctly
1342 written polling loops from denying visibility of updates to memory.
1344 config ARM_ERRATA_364296
1345 bool "ARM errata: Possible cache data corruption with hit-under-miss enabled"
1346 depends on CPU_V6 && !SMP
1348 This options enables the workaround for the 364296 ARM1136
1349 r0p2 erratum (possible cache data corruption with
1350 hit-under-miss enabled). It sets the undocumented bit 31 in
1351 the auxiliary control register and the FI bit in the control
1352 register, thus disabling hit-under-miss without putting the
1353 processor into full low interrupt latency mode. ARM11MPCore
1356 config ARM_ERRATA_764369
1357 bool "ARM errata: Data cache line maintenance operation by MVA may not succeed"
1358 depends on CPU_V7 && SMP
1360 This option enables the workaround for erratum 764369
1361 affecting Cortex-A9 MPCore with two or more processors (all
1362 current revisions). Under certain timing circumstances, a data
1363 cache line maintenance operation by MVA targeting an Inner
1364 Shareable memory region may fail to proceed up to either the
1365 Point of Coherency or to the Point of Unification of the
1366 system. This workaround adds a DSB instruction before the
1367 relevant cache maintenance functions and sets a specific bit
1368 in the diagnostic control register of the SCU.
1370 config PL310_ERRATA_769419
1371 bool "PL310 errata: no automatic Store Buffer drain"
1372 depends on CACHE_L2X0
1374 On revisions of the PL310 prior to r3p2, the Store Buffer does
1375 not automatically drain. This can cause normal, non-cacheable
1376 writes to be retained when the memory system is idle, leading
1377 to suboptimal I/O performance for drivers using coherent DMA.
1378 This option adds a write barrier to the cpu_idle loop so that,
1379 on systems with an outer cache, the store buffer is drained
1384 source "arch/arm/common/Kconfig"
1394 Find out whether you have ISA slots on your motherboard. ISA is the
1395 name of a bus system, i.e. the way the CPU talks to the other stuff
1396 inside your box. Other bus systems are PCI, EISA, MicroChannel
1397 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1398 newer boards don't support it. If you have ISA, say Y, otherwise N.
1400 # Select ISA DMA controller support
1405 # Select ISA DMA interface
1410 bool "PCI support" if MIGHT_HAVE_PCI
1412 Find out whether you have a PCI motherboard. PCI is the name of a
1413 bus system, i.e. the way the CPU talks to the other stuff inside
1414 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1415 VESA. If you have PCI, say Y, otherwise N.
1421 config PCI_NANOENGINE
1422 bool "BSE nanoEngine PCI support"
1423 depends on SA1100_NANOENGINE
1425 Enable PCI on the BSE nanoEngine board.
1430 # Select the host bridge type
1431 config PCI_HOST_VIA82C505
1433 depends on PCI && ARCH_SHARK
1436 config PCI_HOST_ITE8152
1438 depends on PCI && MACH_ARMCORE
1442 source "drivers/pci/Kconfig"
1444 source "drivers/pcmcia/Kconfig"
1448 menu "Kernel Features"
1450 source "kernel/time/Kconfig"
1455 This option should be selected by machines which have an SMP-
1458 The only effect of this option is to make the SMP-related
1459 options available to the user for configuration.
1462 bool "Symmetric Multi-Processing"
1463 depends on CPU_V6K || CPU_V7
1464 depends on GENERIC_CLOCKEVENTS
1467 select USE_GENERIC_SMP_HELPERS
1468 select HAVE_ARM_SCU if !ARCH_MSM_SCORPIONMP
1470 This enables support for systems with more than one CPU. If you have
1471 a system with only one CPU, like most personal computers, say N. If
1472 you have a system with more than one CPU, say Y.
1474 If you say N here, the kernel will run on single and multiprocessor
1475 machines, but will use only one CPU of a multiprocessor machine. If
1476 you say Y here, the kernel will run on many, but not all, single
1477 processor machines. On a single processor machine, the kernel will
1478 run faster if you say N here.
1480 See also <file:Documentation/x86/i386/IO-APIC.txt>,
1481 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
1482 <http://tldp.org/HOWTO/SMP-HOWTO.html>.
1484 If you don't know what to do here, say N.
1487 bool "Allow booting SMP kernel on uniprocessor systems (EXPERIMENTAL)"
1488 depends on EXPERIMENTAL
1489 depends on SMP && !XIP_KERNEL
1492 SMP kernels contain instructions which fail on non-SMP processors.
1493 Enabling this option allows the kernel to modify itself to make
1494 these instructions safe. Disabling it allows about 1K of space
1497 If you don't know what to do here, say Y.
1499 config ARM_CPU_TOPOLOGY
1500 bool "Support cpu topology definition"
1501 depends on SMP && CPU_V7
1504 Support ARM cpu topology definition. The MPIDR register defines
1505 affinity between processors which is then used to describe the cpu
1506 topology of an ARM System.
1509 bool "Multi-core scheduler support"
1510 depends on ARM_CPU_TOPOLOGY
1512 Multi-core scheduler support improves the CPU scheduler's decision
1513 making when dealing with multi-core CPU chips at a cost of slightly
1514 increased overhead in some places. If unsure say N here.
1517 bool "SMT scheduler support"
1518 depends on ARM_CPU_TOPOLOGY
1520 Improves the CPU scheduler's decision making when dealing with
1521 MultiThreading at a cost of slightly increased overhead in some
1522 places. If unsure say N here.
1527 This option enables support for the ARM system coherency unit
1534 This options enables support for the ARM timer and watchdog unit
1537 prompt "Memory split"
1540 Select the desired split between kernel and user memory.
1542 If you are not absolutely sure what you are doing, leave this
1546 bool "3G/1G user/kernel split"
1548 bool "2G/2G user/kernel split"
1550 bool "1G/3G user/kernel split"
1555 default 0x40000000 if VMSPLIT_1G
1556 default 0x80000000 if VMSPLIT_2G
1560 int "Maximum number of CPUs (2-32)"
1566 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
1567 depends on SMP && HOTPLUG && EXPERIMENTAL
1569 Say Y here to experiment with turning CPUs off and on. CPUs
1570 can be controlled through /sys/devices/system/cpu.
1573 bool "Use local timer interrupts"
1576 select HAVE_ARM_TWD if (!ARCH_MSM_SCORPIONMP && !EXYNOS4_MCT)
1578 Enable support for local timers on SMP platforms, rather then the
1579 legacy IPI broadcast method. Local timers allows the system
1580 accounting to be spread across the timer interval, preventing a
1581 "thundering herd" at every timer tick.
1585 default 1024 if ARCH_SHMOBILE || ARCH_TEGRA
1586 default 350 if ARCH_U8500
1589 Maximum number of GPIOs in the system.
1591 If unsure, leave the default value.
1593 source kernel/Kconfig.preempt
1597 default 200 if ARCH_EBSA110 || ARCH_S3C2410 || ARCH_S5P64X0 || \
1598 ARCH_S5PV210 || ARCH_EXYNOS4
1599 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
1600 default AT91_TIMER_HZ if ARCH_AT91
1601 default SHMOBILE_TIMER_HZ if ARCH_SHMOBILE
1604 config THUMB2_KERNEL
1605 bool "Compile the kernel in Thumb-2 mode (EXPERIMENTAL)"
1606 depends on CPU_V7 && !CPU_V6 && !CPU_V6K && EXPERIMENTAL
1608 select ARM_ASM_UNIFIED
1611 By enabling this option, the kernel will be compiled in
1612 Thumb-2 mode. A compiler/assembler that understand the unified
1613 ARM-Thumb syntax is needed.
1617 config THUMB2_AVOID_R_ARM_THM_JUMP11
1618 bool "Work around buggy Thumb-2 short branch relocations in gas"
1619 depends on THUMB2_KERNEL && MODULES
1622 Various binutils versions can resolve Thumb-2 branches to
1623 locally-defined, preemptible global symbols as short-range "b.n"
1624 branch instructions.
1626 This is a problem, because there's no guarantee the final
1627 destination of the symbol, or any candidate locations for a
1628 trampoline, are within range of the branch. For this reason, the
1629 kernel does not support fixing up the R_ARM_THM_JUMP11 (102)
1630 relocation in modules at all, and it makes little sense to add
1633 The symptom is that the kernel fails with an "unsupported
1634 relocation" error when loading some modules.
1636 Until fixed tools are available, passing
1637 -fno-optimize-sibling-calls to gcc should prevent gcc generating
1638 code which hits this problem, at the cost of a bit of extra runtime
1639 stack usage in some cases.
1641 The problem is described in more detail at:
1642 https://bugs.launchpad.net/binutils-linaro/+bug/725126
1644 Only Thumb-2 kernels are affected.
1646 Unless you are sure your tools don't have this problem, say Y.
1648 config ARM_ASM_UNIFIED
1652 bool "Use the ARM EABI to compile the kernel"
1654 This option allows for the kernel to be compiled using the latest
1655 ARM ABI (aka EABI). This is only useful if you are using a user
1656 space environment that is also compiled with EABI.
1658 Since there are major incompatibilities between the legacy ABI and
1659 EABI, especially with regard to structure member alignment, this
1660 option also changes the kernel syscall calling convention to
1661 disambiguate both ABIs and allow for backward compatibility support
1662 (selected with CONFIG_OABI_COMPAT).
1664 To use this you need GCC version 4.0.0 or later.
1667 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
1668 depends on AEABI && EXPERIMENTAL && !THUMB2_KERNEL
1671 This option preserves the old syscall interface along with the
1672 new (ARM EABI) one. It also provides a compatibility layer to
1673 intercept syscalls that have structure arguments which layout
1674 in memory differs between the legacy ABI and the new ARM EABI
1675 (only for non "thumb" binaries). This option adds a tiny
1676 overhead to all syscalls and produces a slightly larger kernel.
1677 If you know you'll be using only pure EABI user space then you
1678 can say N here. If this option is not selected and you attempt
1679 to execute a legacy ABI binary then the result will be
1680 UNPREDICTABLE (in fact it can be predicted that it won't work
1681 at all). If in doubt say Y.
1683 config ARCH_HAS_HOLES_MEMORYMODEL
1686 config ARCH_SPARSEMEM_ENABLE
1689 config ARCH_SPARSEMEM_DEFAULT
1690 def_bool ARCH_SPARSEMEM_ENABLE
1692 config ARCH_SELECT_MEMORY_MODEL
1693 def_bool ARCH_SPARSEMEM_ENABLE
1695 config HAVE_ARCH_PFN_VALID
1696 def_bool ARCH_HAS_HOLES_MEMORYMODEL || !SPARSEMEM
1699 bool "High Memory Support"
1702 The address space of ARM processors is only 4 Gigabytes large
1703 and it has to accommodate user address space, kernel address
1704 space as well as some memory mapped IO. That means that, if you
1705 have a large amount of physical memory and/or IO, not all of the
1706 memory can be "permanently mapped" by the kernel. The physical
1707 memory that is not permanently mapped is called "high memory".
1709 Depending on the selected kernel/user memory split, minimum
1710 vmalloc space and actual amount of RAM, you may not need this
1711 option which should result in a slightly faster kernel.
1716 bool "Allocate 2nd-level pagetables from highmem"
1719 config HW_PERF_EVENTS
1720 bool "Enable hardware performance counter support for perf events"
1721 depends on PERF_EVENTS && CPU_HAS_PMU
1724 Enable hardware performance counter support for perf events. If
1725 disabled, perf events will use software events only.
1729 config FORCE_MAX_ZONEORDER
1730 int "Maximum zone order" if ARCH_SHMOBILE
1731 range 11 64 if ARCH_SHMOBILE
1732 default "9" if SA1111
1735 The kernel memory allocator divides physically contiguous memory
1736 blocks into "zones", where each zone is a power of two number of
1737 pages. This option selects the largest power of two that the kernel
1738 keeps in the memory allocator. If you need to allocate very large
1739 blocks of physically contiguous memory, then you may need to
1740 increase this value.
1742 This config option is actually maximum order plus one. For example,
1743 a value of 11 means that the largest free memory block is 2^10 pages.
1746 bool "Timer and CPU usage LEDs"
1747 depends on ARCH_CDB89712 || ARCH_EBSA110 || \
1748 ARCH_EBSA285 || ARCH_INTEGRATOR || \
1749 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
1750 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
1751 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
1752 ARCH_AT91 || ARCH_DAVINCI || \
1753 ARCH_KS8695 || MACH_RD88F5182 || ARCH_REALVIEW
1755 If you say Y here, the LEDs on your machine will be used
1756 to provide useful information about your current system status.
1758 If you are compiling a kernel for a NetWinder or EBSA-285, you will
1759 be able to select which LEDs are active using the options below. If
1760 you are compiling a kernel for the EBSA-110 or the LART however, the
1761 red LED will simply flash regularly to indicate that the system is
1762 still functional. It is safe to say Y here if you have a CATS
1763 system, but the driver will do nothing.
1766 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
1767 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1768 || MACH_OMAP_PERSEUS2
1770 depends on !GENERIC_CLOCKEVENTS
1771 default y if ARCH_EBSA110
1773 If you say Y here, one of the system LEDs (the green one on the
1774 NetWinder, the amber one on the EBSA285, or the red one on the LART)
1775 will flash regularly to indicate that the system is still
1776 operational. This is mainly useful to kernel hackers who are
1777 debugging unstable kernels.
1779 The LART uses the same LED for both Timer LED and CPU usage LED
1780 functions. You may choose to use both, but the Timer LED function
1781 will overrule the CPU usage LED.
1784 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
1786 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1787 || MACH_OMAP_PERSEUS2
1790 If you say Y here, the red LED will be used to give a good real
1791 time indication of CPU usage, by lighting whenever the idle task
1792 is not currently executing.
1794 The LART uses the same LED for both Timer LED and CPU usage LED
1795 functions. You may choose to use both, but the Timer LED function
1796 will overrule the CPU usage LED.
1798 config ALIGNMENT_TRAP
1800 depends on CPU_CP15_MMU
1801 default y if !ARCH_EBSA110
1802 select HAVE_PROC_CPU if PROC_FS
1804 ARM processors cannot fetch/store information which is not
1805 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
1806 address divisible by 4. On 32-bit ARM processors, these non-aligned
1807 fetch/store instructions will be emulated in software if you say
1808 here, which has a severe performance impact. This is necessary for
1809 correct operation of some network protocols. With an IP-only
1810 configuration it is safe to say N, otherwise say Y.
1812 config UACCESS_WITH_MEMCPY
1813 bool "Use kernel mem{cpy,set}() for {copy_to,clear}_user() (EXPERIMENTAL)"
1814 depends on MMU && EXPERIMENTAL
1815 default y if CPU_FEROCEON
1817 Implement faster copy_to_user and clear_user methods for CPU
1818 cores where a 8-word STM instruction give significantly higher
1819 memory write throughput than a sequence of individual 32bit stores.
1821 A possible side effect is a slight increase in scheduling latency
1822 between threads sharing the same address space if they invoke
1823 such copy operations with large buffers.
1825 However, if the CPU data cache is using a write-allocate mode,
1826 this option is unlikely to provide any performance gain.
1830 prompt "Enable seccomp to safely compute untrusted bytecode"
1832 This kernel feature is useful for number crunching applications
1833 that may need to compute untrusted bytecode during their
1834 execution. By using pipes or other transports made available to
1835 the process as file descriptors supporting the read/write
1836 syscalls, it's possible to isolate those applications in
1837 their own address space using seccomp. Once seccomp is
1838 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1839 and the task is only allowed to execute a few safe syscalls
1840 defined by each seccomp mode.
1842 config CC_STACKPROTECTOR
1843 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1844 depends on EXPERIMENTAL
1846 This option turns on the -fstack-protector GCC feature. This
1847 feature puts, at the beginning of functions, a canary value on
1848 the stack just before the return address, and validates
1849 the value just before actually returning. Stack based buffer
1850 overflows (that need to overwrite this return address) now also
1851 overwrite the canary, which gets detected and the attack is then
1852 neutralized via a kernel panic.
1853 This feature requires gcc version 4.2 or above.
1855 config DEPRECATED_PARAM_STRUCT
1856 bool "Provide old way to pass kernel parameters"
1858 This was deprecated in 2001 and announced to live on for 5 years.
1859 Some old boot loaders still use this way.
1866 bool "Flattened Device Tree support"
1868 select OF_EARLY_FLATTREE
1871 Include support for flattened device tree machine descriptions.
1873 # Compressed boot loader in ROM. Yes, we really want to ask about
1874 # TEXT and BSS so we preserve their values in the config files.
1875 config ZBOOT_ROM_TEXT
1876 hex "Compressed ROM boot loader base address"
1879 The physical address at which the ROM-able zImage is to be
1880 placed in the target. Platforms which normally make use of
1881 ROM-able zImage formats normally set this to a suitable
1882 value in their defconfig file.
1884 If ZBOOT_ROM is not enabled, this has no effect.
1886 config ZBOOT_ROM_BSS
1887 hex "Compressed ROM boot loader BSS address"
1890 The base address of an area of read/write memory in the target
1891 for the ROM-able zImage which must be available while the
1892 decompressor is running. It must be large enough to hold the
1893 entire decompressed kernel plus an additional 128 KiB.
1894 Platforms which normally make use of ROM-able zImage formats
1895 normally set this to a suitable value in their defconfig file.
1897 If ZBOOT_ROM is not enabled, this has no effect.
1900 bool "Compressed boot loader in ROM/flash"
1901 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
1903 Say Y here if you intend to execute your compressed kernel image
1904 (zImage) directly from ROM or flash. If unsure, say N.
1907 prompt "Include SD/MMC loader in zImage (EXPERIMENTAL)"
1908 depends on ZBOOT_ROM && ARCH_SH7372 && EXPERIMENTAL
1909 default ZBOOT_ROM_NONE
1911 Include experimental SD/MMC loading code in the ROM-able zImage.
1912 With this enabled it is possible to write the the ROM-able zImage
1913 kernel image to an MMC or SD card and boot the kernel straight
1914 from the reset vector. At reset the processor Mask ROM will load
1915 the first part of the the ROM-able zImage which in turn loads the
1916 rest the kernel image to RAM.
1918 config ZBOOT_ROM_NONE
1919 bool "No SD/MMC loader in zImage (EXPERIMENTAL)"
1921 Do not load image from SD or MMC
1923 config ZBOOT_ROM_MMCIF
1924 bool "Include MMCIF loader in zImage (EXPERIMENTAL)"
1926 Load image from MMCIF hardware block.
1928 config ZBOOT_ROM_SH_MOBILE_SDHI
1929 bool "Include SuperH Mobile SDHI loader in zImage (EXPERIMENTAL)"
1931 Load image from SDHI hardware block
1935 config ARM_APPENDED_DTB
1936 bool "Use appended device tree blob to zImage (EXPERIMENTAL)"
1937 depends on OF && !ZBOOT_ROM && EXPERIMENTAL
1939 With this option, the boot code will look for a device tree binary
1940 (DTB) appended to zImage
1941 (e.g. cat zImage <filename>.dtb > zImage_w_dtb).
1943 This is meant as a backward compatibility convenience for those
1944 systems with a bootloader that can't be upgraded to accommodate
1945 the documented boot protocol using a device tree.
1947 Beware that there is very little in terms of protection against
1948 this option being confused by leftover garbage in memory that might
1949 look like a DTB header after a reboot if no actual DTB is appended
1950 to zImage. Do not leave this option active in a production kernel
1951 if you don't intend to always append a DTB. Proper passing of the
1952 location into r2 of a bootloader provided DTB is always preferable
1955 config ARM_ATAG_DTB_COMPAT
1956 bool "Supplement the appended DTB with traditional ATAG information"
1957 depends on ARM_APPENDED_DTB
1959 Some old bootloaders can't be updated to a DTB capable one, yet
1960 they provide ATAGs with memory configuration, the ramdisk address,
1961 the kernel cmdline string, etc. Such information is dynamically
1962 provided by the bootloader and can't always be stored in a static
1963 DTB. To allow a device tree enabled kernel to be used with such
1964 bootloaders, this option allows zImage to extract the information
1965 from the ATAG list and store it at run time into the appended DTB.
1968 string "Default kernel command string"
1971 On some architectures (EBSA110 and CATS), there is currently no way
1972 for the boot loader to pass arguments to the kernel. For these
1973 architectures, you should supply some command-line options at build
1974 time by entering them here. As a minimum, you should specify the
1975 memory size and the root device (e.g., mem=64M root=/dev/nfs).
1978 prompt "Kernel command line type" if CMDLINE != ""
1979 default CMDLINE_FROM_BOOTLOADER
1981 config CMDLINE_FROM_BOOTLOADER
1982 bool "Use bootloader kernel arguments if available"
1984 Uses the command-line options passed by the boot loader. If
1985 the boot loader doesn't provide any, the default kernel command
1986 string provided in CMDLINE will be used.
1988 config CMDLINE_EXTEND
1989 bool "Extend bootloader kernel arguments"
1991 The command-line arguments provided by the boot loader will be
1992 appended to the default kernel command string.
1994 config CMDLINE_FORCE
1995 bool "Always use the default kernel command string"
1997 Always use the default kernel command string, even if the boot
1998 loader passes other arguments to the kernel.
1999 This is useful if you cannot or don't want to change the
2000 command-line options your boot loader passes to the kernel.
2004 bool "Kernel Execute-In-Place from ROM"
2005 depends on !ZBOOT_ROM && !ARM_LPAE
2007 Execute-In-Place allows the kernel to run from non-volatile storage
2008 directly addressable by the CPU, such as NOR flash. This saves RAM
2009 space since the text section of the kernel is not loaded from flash
2010 to RAM. Read-write sections, such as the data section and stack,
2011 are still copied to RAM. The XIP kernel is not compressed since
2012 it has to run directly from flash, so it will take more space to
2013 store it. The flash address used to link the kernel object files,
2014 and for storing it, is configuration dependent. Therefore, if you
2015 say Y here, you must know the proper physical address where to
2016 store the kernel image depending on your own flash memory usage.
2018 Also note that the make target becomes "make xipImage" rather than
2019 "make zImage" or "make Image". The final kernel binary to put in
2020 ROM memory will be arch/arm/boot/xipImage.
2024 config XIP_PHYS_ADDR
2025 hex "XIP Kernel Physical Location"
2026 depends on XIP_KERNEL
2027 default "0x00080000"
2029 This is the physical address in your flash memory the kernel will
2030 be linked for and stored to. This address is dependent on your
2034 bool "Kexec system call (EXPERIMENTAL)"
2035 depends on EXPERIMENTAL && (!SMP || HOTPLUG_CPU)
2037 kexec is a system call that implements the ability to shutdown your
2038 current kernel, and to start another kernel. It is like a reboot
2039 but it is independent of the system firmware. And like a reboot
2040 you can start any kernel with it, not just Linux.
2042 It is an ongoing process to be certain the hardware in a machine
2043 is properly shutdown, so do not be surprised if this code does not
2044 initially work for you. It may help to enable device hotplugging
2048 bool "Export atags in procfs"
2052 Should the atags used to boot the kernel be exported in an "atags"
2053 file in procfs. Useful with kexec.
2056 bool "Build kdump crash kernel (EXPERIMENTAL)"
2057 depends on EXPERIMENTAL
2059 Generate crash dump after being started by kexec. This should
2060 be normally only set in special crash dump kernels which are
2061 loaded in the main kernel with kexec-tools into a specially
2062 reserved region and then later executed after a crash by
2063 kdump/kexec. The crash dump kernel must be compiled to a
2064 memory address not used by the main kernel
2066 For more details see Documentation/kdump/kdump.txt
2068 config AUTO_ZRELADDR
2069 bool "Auto calculation of the decompressed kernel image address"
2070 depends on !ZBOOT_ROM && !ARCH_U300
2072 ZRELADDR is the physical address where the decompressed kernel
2073 image will be placed. If AUTO_ZRELADDR is selected, the address
2074 will be determined at run-time by masking the current IP with
2075 0xf8000000. This assumes the zImage being placed in the first 128MB
2076 from start of memory.
2080 menu "CPU Power Management"
2084 source "drivers/cpufreq/Kconfig"
2087 tristate "CPUfreq driver for i.MX CPUs"
2088 depends on ARCH_MXC && CPU_FREQ
2090 This enables the CPUfreq driver for i.MX CPUs.
2092 config CPU_FREQ_SA1100
2095 config CPU_FREQ_SA1110
2098 config CPU_FREQ_INTEGRATOR
2099 tristate "CPUfreq driver for ARM Integrator CPUs"
2100 depends on ARCH_INTEGRATOR && CPU_FREQ
2103 This enables the CPUfreq driver for ARM Integrator CPUs.
2105 For details, take a look at <file:Documentation/cpu-freq>.
2111 depends on CPU_FREQ && ARCH_PXA && PXA25x
2113 select CPU_FREQ_TABLE
2114 select CPU_FREQ_DEFAULT_GOV_USERSPACE
2119 Internal configuration node for common cpufreq on Samsung SoC
2121 config CPU_FREQ_S3C24XX
2122 bool "CPUfreq driver for Samsung S3C24XX series CPUs (EXPERIMENTAL)"
2123 depends on ARCH_S3C2410 && CPU_FREQ && EXPERIMENTAL
2126 This enables the CPUfreq driver for the Samsung S3C24XX family
2129 For details, take a look at <file:Documentation/cpu-freq>.
2133 config CPU_FREQ_S3C24XX_PLL
2134 bool "Support CPUfreq changing of PLL frequency (EXPERIMENTAL)"
2135 depends on CPU_FREQ_S3C24XX && EXPERIMENTAL
2137 Compile in support for changing the PLL frequency from the
2138 S3C24XX series CPUfreq driver. The PLL takes time to settle
2139 after a frequency change, so by default it is not enabled.
2141 This also means that the PLL tables for the selected CPU(s) will
2142 be built which may increase the size of the kernel image.
2144 config CPU_FREQ_S3C24XX_DEBUG
2145 bool "Debug CPUfreq Samsung driver core"
2146 depends on CPU_FREQ_S3C24XX
2148 Enable s3c_freq_dbg for the Samsung S3C CPUfreq core
2150 config CPU_FREQ_S3C24XX_IODEBUG
2151 bool "Debug CPUfreq Samsung driver IO timing"
2152 depends on CPU_FREQ_S3C24XX
2154 Enable s3c_freq_iodbg for the Samsung S3C CPUfreq core
2156 config CPU_FREQ_S3C24XX_DEBUGFS
2157 bool "Export debugfs for CPUFreq"
2158 depends on CPU_FREQ_S3C24XX && DEBUG_FS
2160 Export status information via debugfs.
2164 source "drivers/cpuidle/Kconfig"
2168 menu "Floating point emulation"
2170 comment "At least one emulation must be selected"
2173 bool "NWFPE math emulation"
2174 depends on (!AEABI || OABI_COMPAT) && !THUMB2_KERNEL
2176 Say Y to include the NWFPE floating point emulator in the kernel.
2177 This is necessary to run most binaries. Linux does not currently
2178 support floating point hardware so you need to say Y here even if
2179 your machine has an FPA or floating point co-processor podule.
2181 You may say N here if you are going to load the Acorn FPEmulator
2182 early in the bootup.
2185 bool "Support extended precision"
2186 depends on FPE_NWFPE
2188 Say Y to include 80-bit support in the kernel floating-point
2189 emulator. Otherwise, only 32 and 64-bit support is compiled in.
2190 Note that gcc does not generate 80-bit operations by default,
2191 so in most cases this option only enlarges the size of the
2192 floating point emulator without any good reason.
2194 You almost surely want to say N here.
2197 bool "FastFPE math emulation (EXPERIMENTAL)"
2198 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
2200 Say Y here to include the FAST floating point emulator in the kernel.
2201 This is an experimental much faster emulator which now also has full
2202 precision for the mantissa. It does not support any exceptions.
2203 It is very simple, and approximately 3-6 times faster than NWFPE.
2205 It should be sufficient for most programs. It may be not suitable
2206 for scientific calculations, but you have to check this for yourself.
2207 If you do not feel you need a faster FP emulation you should better
2211 bool "VFP-format floating point maths"
2212 depends on CPU_V6 || CPU_V6K || CPU_ARM926T || CPU_V7 || CPU_FEROCEON
2214 Say Y to include VFP support code in the kernel. This is needed
2215 if your hardware includes a VFP unit.
2217 Please see <file:Documentation/arm/VFP/release-notes.txt> for
2218 release notes and additional status information.
2220 Say N if your target does not have VFP hardware.
2228 bool "Advanced SIMD (NEON) Extension support"
2229 depends on VFPv3 && CPU_V7
2231 Say Y to include support code for NEON, the ARMv7 Advanced SIMD
2236 menu "Userspace binary formats"
2238 source "fs/Kconfig.binfmt"
2241 tristate "RISC OS personality"
2244 Say Y here to include the kernel code necessary if you want to run
2245 Acorn RISC OS/Arthur binaries under Linux. This code is still very
2246 experimental; if this sounds frightening, say N and sleep in peace.
2247 You can also say M here to compile this support as a module (which
2248 will be called arthur).
2252 menu "Power management options"
2254 source "kernel/power/Kconfig"
2256 config ARCH_SUSPEND_POSSIBLE
2257 depends on !ARCH_S5PC100
2258 depends on CPU_ARM920T || CPU_ARM926T || CPU_SA1100 || \
2259 CPU_V6 || CPU_V6K || CPU_V7 || CPU_XSC3 || CPU_XSCALE
2262 config ARM_CPU_SUSPEND
2267 source "net/Kconfig"
2269 source "drivers/Kconfig"
2273 source "arch/arm/Kconfig.debug"
2275 source "security/Kconfig"
2277 source "crypto/Kconfig"
2279 source "lib/Kconfig"