5 select HAVE_DMA_API_DEBUG
6 select HAVE_IDE if PCI || ISA || PCMCIA
9 select SYS_SUPPORTS_APM_EMULATION
10 select GENERIC_ATOMIC64 if (CPU_V6 || !CPU_32v6K || !AEABI)
11 select HAVE_OPROFILE if (HAVE_PERF_EVENTS)
13 select HAVE_KPROBES if !XIP_KERNEL
14 select HAVE_KRETPROBES if (HAVE_KPROBES)
15 select HAVE_FUNCTION_TRACER if (!XIP_KERNEL)
16 select HAVE_FTRACE_MCOUNT_RECORD if (!XIP_KERNEL)
17 select HAVE_DYNAMIC_FTRACE if (!XIP_KERNEL)
18 select HAVE_FUNCTION_GRAPH_TRACER if (!THUMB2_KERNEL)
19 select HAVE_GENERIC_DMA_COHERENT
20 select HAVE_KERNEL_GZIP
21 select HAVE_KERNEL_LZO
22 select HAVE_KERNEL_LZMA
24 select HAVE_PERF_EVENTS
25 select PERF_USE_VMALLOC
26 select HAVE_REGS_AND_STACK_ACCESS_API
27 select HAVE_HW_BREAKPOINT if (PERF_EVENTS && (CPU_V6 || CPU_V6K || CPU_V7))
28 select HAVE_C_RECORDMCOUNT
29 select HAVE_GENERIC_HARDIRQS
30 select HAVE_SPARSE_IRQ
31 select GENERIC_IRQ_SHOW
32 select CPU_PM if (SUSPEND || CPU_IDLE)
34 The ARM series is a line of low-power-consumption RISC chip designs
35 licensed by ARM Ltd and targeted at embedded applications and
36 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
37 manufactured, but legacy ARM-based PC hardware remains popular in
38 Europe. There is an ARM Linux project with a web page at
39 <http://www.arm.linux.org.uk/>.
41 config ARM_HAS_SG_CHAIN
50 config SYS_SUPPORTS_APM_EMULATION
53 config HAVE_SCHED_CLOCK
59 config ARCH_USES_GETTIMEOFFSET
63 config GENERIC_CLOCKEVENTS
66 config GENERIC_CLOCKEVENTS_BROADCAST
68 depends on GENERIC_CLOCKEVENTS
77 select GENERIC_ALLOCATOR
88 The Extended Industry Standard Architecture (EISA) bus was
89 developed as an open alternative to the IBM MicroChannel bus.
91 The EISA bus provided some of the features of the IBM MicroChannel
92 bus while maintaining backward compatibility with cards made for
93 the older ISA bus. The EISA bus saw limited use between 1988 and
94 1995 when it was made obsolete by the PCI bus.
96 Say Y here if you are building a kernel for an EISA-based machine.
106 MicroChannel Architecture is found in some IBM PS/2 machines and
107 laptops. It is a bus system similar to PCI or ISA. See
108 <file:Documentation/mca.txt> (and especially the web page given
109 there) before attempting to build an MCA bus kernel.
111 config STACKTRACE_SUPPORT
115 config HAVE_LATENCYTOP_SUPPORT
120 config LOCKDEP_SUPPORT
124 config TRACE_IRQFLAGS_SUPPORT
128 config HARDIRQS_SW_RESEND
132 config GENERIC_IRQ_PROBE
136 config GENERIC_LOCKBREAK
139 depends on SMP && PREEMPT
141 config RWSEM_GENERIC_SPINLOCK
145 config RWSEM_XCHGADD_ALGORITHM
148 config ARCH_HAS_ILOG2_U32
151 config ARCH_HAS_ILOG2_U64
154 config ARCH_HAS_CPUFREQ
157 Internal node to signify that the ARCH has CPUFREQ support
158 and that the relevant menu configurations are displayed for
161 config ARCH_HAS_CPU_IDLE_WAIT
164 config GENERIC_HWEIGHT
168 config GENERIC_CALIBRATE_DELAY
172 config ARCH_MAY_HAVE_PC_FDC
178 config NEED_DMA_MAP_STATE
181 config GENERIC_ISA_DMA
192 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
193 default DRAM_BASE if REMAP_VECTORS_TO_RAM
196 The base address of exception vectors.
198 config ARM_PATCH_PHYS_VIRT
199 bool "Patch physical to virtual translations at runtime" if EMBEDDED
201 depends on !XIP_KERNEL && MMU
202 depends on !ARCH_REALVIEW || !SPARSEMEM
204 Patch phys-to-virt and virt-to-phys translation functions at
205 boot and module load time according to the position of the
206 kernel in system memory.
208 This can only be used with non-XIP MMU kernels where the base
209 of physical memory is at a 16MB boundary.
211 Only disable this option if you know that you do not require
212 this feature (eg, building a kernel for a single machine) and
213 you need to shrink the kernel to the minimal size.
215 config NEED_MACH_MEMORY_H
218 Select this when mach/memory.h is required to provide special
219 definitions for this platform. The need for mach/memory.h should
220 be avoided when possible.
223 hex "Physical address of main memory"
224 depends on !ARM_PATCH_PHYS_VIRT && !NEED_MACH_MEMORY_H
226 Please provide the physical address corresponding to the
227 location of main memory in your system.
233 source "init/Kconfig"
235 source "kernel/Kconfig.freezer"
240 bool "MMU-based Paged Memory Management Support"
243 Select if you want MMU-based virtualised addressing space
244 support by paged memory management. If unsure, say 'Y'.
247 # The "ARM system type" choice list is ordered alphabetically by option
248 # text. Please add new entries in the option alphabetic order.
251 prompt "ARM system type"
252 default ARCH_VERSATILE
254 config ARCH_INTEGRATOR
255 bool "ARM Ltd. Integrator family"
257 select ARCH_HAS_CPUFREQ
259 select HAVE_MACH_CLKDEV
261 select GENERIC_CLOCKEVENTS
262 select PLAT_VERSATILE
263 select PLAT_VERSATILE_FPGA_IRQ
264 select NEED_MACH_MEMORY_H
266 Support for ARM's Integrator platform.
269 bool "ARM Ltd. RealView family"
272 select HAVE_MACH_CLKDEV
274 select GENERIC_CLOCKEVENTS
275 select ARCH_WANT_OPTIONAL_GPIOLIB
276 select PLAT_VERSATILE
277 select PLAT_VERSATILE_CLCD
278 select ARM_TIMER_SP804
279 select GPIO_PL061 if GPIOLIB
280 select NEED_MACH_MEMORY_H
282 This enables support for ARM Ltd RealView boards.
284 config ARCH_VERSATILE
285 bool "ARM Ltd. Versatile family"
289 select HAVE_MACH_CLKDEV
291 select GENERIC_CLOCKEVENTS
292 select ARCH_WANT_OPTIONAL_GPIOLIB
293 select PLAT_VERSATILE
294 select PLAT_VERSATILE_CLCD
295 select PLAT_VERSATILE_FPGA_IRQ
296 select ARM_TIMER_SP804
298 This enables support for ARM Ltd Versatile board.
301 bool "ARM Ltd. Versatile Express family"
302 select ARCH_WANT_OPTIONAL_GPIOLIB
304 select ARM_TIMER_SP804
306 select HAVE_MACH_CLKDEV
307 select GENERIC_CLOCKEVENTS
309 select HAVE_PATA_PLATFORM
311 select PLAT_VERSATILE
312 select PLAT_VERSATILE_CLCD
314 This enables support for the ARM Ltd Versatile Express boards.
318 select ARCH_REQUIRE_GPIOLIB
322 This enables support for systems based on the Atmel AT91RM9200,
323 AT91SAM9 and AT91CAP9 processors.
326 bool "Broadcom BCMRING"
330 select ARM_TIMER_SP804
332 select GENERIC_CLOCKEVENTS
333 select ARCH_WANT_OPTIONAL_GPIOLIB
335 Support for Broadcom's BCMRing platform.
338 bool "Calxeda Highbank-based"
339 select ARCH_WANT_OPTIONAL_GPIOLIB
342 select ARM_TIMER_SP804
345 select GENERIC_CLOCKEVENTS
349 Support for the Calxeda Highbank SoC based boards.
352 bool "Cirrus Logic CLPS711x/EP721x-based"
354 select ARCH_USES_GETTIMEOFFSET
355 select NEED_MACH_MEMORY_H
357 Support for Cirrus Logic 711x/721x based boards.
360 bool "Cavium Networks CNS3XXX family"
362 select GENERIC_CLOCKEVENTS
364 select MIGHT_HAVE_PCI
365 select PCI_DOMAINS if PCI
367 Support for Cavium Networks CNS3XXX platform.
370 bool "Cortina Systems Gemini"
372 select ARCH_REQUIRE_GPIOLIB
373 select ARCH_USES_GETTIMEOFFSET
375 Support for the Cortina Systems Gemini family SoCs
378 bool "CSR SiRFSoC PRIMA2 ARM Cortex A9 Platform"
381 select GENERIC_CLOCKEVENTS
383 select GENERIC_IRQ_CHIP
387 Support for CSR SiRFSoC ARM Cortex A9 Platform
394 select ARCH_USES_GETTIMEOFFSET
395 select NEED_MACH_MEMORY_H
397 This is an evaluation board for the StrongARM processor available
398 from Digital. It has limited hardware on-board, including an
399 Ethernet interface, two PCMCIA sockets, two serial ports and a
408 select ARCH_REQUIRE_GPIOLIB
409 select ARCH_HAS_HOLES_MEMORYMODEL
410 select ARCH_USES_GETTIMEOFFSET
411 select NEED_MACH_MEMORY_H
413 This enables support for the Cirrus EP93xx series of CPUs.
415 config ARCH_FOOTBRIDGE
419 select GENERIC_CLOCKEVENTS
421 select NEED_MACH_MEMORY_H
423 Support for systems based on the DC21285 companion chip
424 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
427 bool "Freescale MXC/iMX-based"
428 select GENERIC_CLOCKEVENTS
429 select ARCH_REQUIRE_GPIOLIB
432 select GENERIC_IRQ_CHIP
433 select HAVE_SCHED_CLOCK
434 select MULTI_IRQ_HANDLER
436 Support for Freescale MXC/iMX-based family of processors
439 bool "Freescale MXS-based"
440 select GENERIC_CLOCKEVENTS
441 select ARCH_REQUIRE_GPIOLIB
445 Support for Freescale MXS-based family of processors
448 bool "Hilscher NetX based"
452 select GENERIC_CLOCKEVENTS
454 This enables support for systems based on the Hilscher NetX Soc
457 bool "Hynix HMS720x-based"
460 select ARCH_USES_GETTIMEOFFSET
462 This enables support for systems based on the Hynix HMS720x
470 select ARCH_SUPPORTS_MSI
472 select NEED_MACH_MEMORY_H
474 Support for Intel's IOP13XX (XScale) family of processors.
482 select ARCH_REQUIRE_GPIOLIB
484 Support for Intel's 80219 and IOP32X (XScale) family of
493 select ARCH_REQUIRE_GPIOLIB
495 Support for Intel's IOP33X (XScale) family of processors.
502 select ARCH_USES_GETTIMEOFFSET
503 select NEED_MACH_MEMORY_H
505 Support for Intel's IXP23xx (XScale) family of processors.
508 bool "IXP2400/2800-based"
512 select ARCH_USES_GETTIMEOFFSET
513 select NEED_MACH_MEMORY_H
515 Support for Intel's IXP2400/2800 (XScale) family of processors.
523 select GENERIC_CLOCKEVENTS
524 select HAVE_SCHED_CLOCK
525 select MIGHT_HAVE_PCI
526 select DMABOUNCE if PCI
528 Support for Intel's IXP4XX (XScale) family of processors.
534 select ARCH_REQUIRE_GPIOLIB
535 select GENERIC_CLOCKEVENTS
538 Support for the Marvell Dove SoC 88AP510
541 bool "Marvell Kirkwood"
544 select ARCH_REQUIRE_GPIOLIB
545 select GENERIC_CLOCKEVENTS
548 Support for the following Marvell Kirkwood series SoCs:
549 88F6180, 88F6192 and 88F6281.
555 select ARCH_REQUIRE_GPIOLIB
558 select USB_ARCH_HAS_OHCI
560 select GENERIC_CLOCKEVENTS
562 Support for the NXP LPC32XX family of processors
565 bool "Marvell MV78xx0"
568 select ARCH_REQUIRE_GPIOLIB
569 select GENERIC_CLOCKEVENTS
572 Support for the following Marvell MV78xx0 series SoCs:
580 select ARCH_REQUIRE_GPIOLIB
581 select GENERIC_CLOCKEVENTS
584 Support for the following Marvell Orion 5x series SoCs:
585 Orion-1 (5181), Orion-VoIP (5181L), Orion-NAS (5182),
586 Orion-2 (5281), Orion-1-90 (6183).
589 bool "Marvell PXA168/910/MMP2"
591 select ARCH_REQUIRE_GPIOLIB
593 select GENERIC_CLOCKEVENTS
594 select HAVE_SCHED_CLOCK
598 select GENERIC_ALLOCATOR
600 Support for Marvell's PXA168/PXA910(MMP) and MMP2 processor line.
603 bool "Micrel/Kendin KS8695"
605 select ARCH_REQUIRE_GPIOLIB
606 select ARCH_USES_GETTIMEOFFSET
607 select NEED_MACH_MEMORY_H
609 Support for Micrel/Kendin KS8695 "Centaur" (ARM922T) based
610 System-on-Chip devices.
613 bool "Nuvoton W90X900 CPU"
615 select ARCH_REQUIRE_GPIOLIB
618 select GENERIC_CLOCKEVENTS
620 Support for Nuvoton (Winbond logic dept.) ARM9 processor,
621 At present, the w90x900 has been renamed nuc900, regarding
622 the ARM series product line, you can login the following
623 link address to know more.
625 <http://www.nuvoton.com/hq/enu/ProductAndSales/ProductLines/
626 ConsumerElectronicsIC/ARMMicrocontroller/ARMMicrocontroller>
632 select GENERIC_CLOCKEVENTS
635 select HAVE_SCHED_CLOCK
636 select ARCH_HAS_CPUFREQ
638 This enables support for NVIDIA Tegra based systems (Tegra APX,
639 Tegra 6xx and Tegra 2 series).
641 config ARCH_PICOXCELL
642 bool "Picochip picoXcell"
643 select ARCH_REQUIRE_GPIOLIB
644 select ARM_PATCH_PHYS_VIRT
648 select GENERIC_CLOCKEVENTS
650 select HAVE_SCHED_CLOCK
655 This enables support for systems based on the Picochip picoXcell
656 family of Femtocell devices. The picoxcell support requires device tree
660 bool "Philips Nexperia PNX4008 Mobile"
663 select ARCH_USES_GETTIMEOFFSET
665 This enables support for Philips PNX4008 mobile platform.
668 bool "PXA2xx/PXA3xx-based"
671 select ARCH_HAS_CPUFREQ
674 select ARCH_REQUIRE_GPIOLIB
675 select GENERIC_CLOCKEVENTS
676 select HAVE_SCHED_CLOCK
681 select MULTI_IRQ_HANDLER
682 select ARM_CPU_SUSPEND if PM
685 Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
690 select GENERIC_CLOCKEVENTS
691 select ARCH_REQUIRE_GPIOLIB
694 Support for Qualcomm MSM/QSD based systems. This runs on the
695 apps processor of the MSM/QSD and depends on a shared memory
696 interface to the modem processor which runs the baseband
697 stack and controls some vital subsystems
698 (clock and power control, etc).
701 bool "Renesas SH-Mobile / R-Mobile"
704 select HAVE_MACH_CLKDEV
705 select GENERIC_CLOCKEVENTS
708 select MULTI_IRQ_HANDLER
709 select PM_GENERIC_DOMAINS if PM
710 select NEED_MACH_MEMORY_H
712 Support for Renesas's SH-Mobile and R-Mobile ARM platforms.
719 select ARCH_MAY_HAVE_PC_FDC
720 select HAVE_PATA_PLATFORM
723 select ARCH_SPARSEMEM_ENABLE
724 select ARCH_USES_GETTIMEOFFSET
726 select NEED_MACH_MEMORY_H
728 On the Acorn Risc-PC, Linux can support the internal IDE disk and
729 CD-ROM interface, serial and parallel port, and the floppy drive.
736 select ARCH_SPARSEMEM_ENABLE
738 select ARCH_HAS_CPUFREQ
740 select GENERIC_CLOCKEVENTS
742 select HAVE_SCHED_CLOCK
744 select ARCH_REQUIRE_GPIOLIB
746 select NEED_MACH_MEMORY_H
748 Support for StrongARM 11x0 based boards.
751 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2416, S3C2440, S3C2442, S3C2443, S3C2450"
753 select ARCH_HAS_CPUFREQ
756 select ARCH_USES_GETTIMEOFFSET
757 select HAVE_S3C2410_I2C if I2C
759 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
760 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
761 the Samsung SMDK2410 development board (and derivatives).
763 Note, the S3C2416 and the S3C2450 are so close that they even share
764 the same SoC ID code. This means that there is no separate machine
765 directory (no arch/arm/mach-s3c2450) as the S3C2416 was first.
768 bool "Samsung S3C64XX"
776 select ARCH_USES_GETTIMEOFFSET
777 select ARCH_HAS_CPUFREQ
778 select ARCH_REQUIRE_GPIOLIB
779 select SAMSUNG_CLKSRC
780 select SAMSUNG_IRQ_VIC_TIMER
781 select S3C_GPIO_TRACK
783 select USB_ARCH_HAS_OHCI
784 select SAMSUNG_GPIOLIB_4BIT
785 select HAVE_S3C2410_I2C if I2C
786 select HAVE_S3C2410_WATCHDOG if WATCHDOG
788 Samsung S3C64XX series based systems
791 bool "Samsung S5P6440 S5P6450"
797 select HAVE_S3C2410_WATCHDOG if WATCHDOG
798 select GENERIC_CLOCKEVENTS
799 select HAVE_SCHED_CLOCK
800 select HAVE_S3C2410_I2C if I2C
801 select HAVE_S3C_RTC if RTC_CLASS
803 Samsung S5P64X0 CPU based systems, such as the Samsung SMDK6440,
807 bool "Samsung S5PC100"
812 select ARM_L1_CACHE_SHIFT_6
813 select ARCH_USES_GETTIMEOFFSET
814 select HAVE_S3C2410_I2C if I2C
815 select HAVE_S3C_RTC if RTC_CLASS
816 select HAVE_S3C2410_WATCHDOG if WATCHDOG
818 Samsung S5PC100 series based systems
821 bool "Samsung S5PV210/S5PC110"
823 select ARCH_SPARSEMEM_ENABLE
824 select ARCH_HAS_HOLES_MEMORYMODEL
829 select ARM_L1_CACHE_SHIFT_6
830 select ARCH_HAS_CPUFREQ
831 select GENERIC_CLOCKEVENTS
832 select HAVE_SCHED_CLOCK
833 select HAVE_S3C2410_I2C if I2C
834 select HAVE_S3C_RTC if RTC_CLASS
835 select HAVE_S3C2410_WATCHDOG if WATCHDOG
836 select NEED_MACH_MEMORY_H
838 Samsung S5PV210/S5PC110 series based systems
841 bool "SAMSUNG EXYNOS"
843 select ARCH_SPARSEMEM_ENABLE
844 select ARCH_HAS_HOLES_MEMORYMODEL
848 select ARCH_HAS_CPUFREQ
849 select GENERIC_CLOCKEVENTS
850 select HAVE_S3C_RTC if RTC_CLASS
851 select HAVE_S3C2410_I2C if I2C
852 select HAVE_S3C2410_WATCHDOG if WATCHDOG
853 select NEED_MACH_MEMORY_H
855 Support for SAMSUNG's EXYNOS SoCs (EXYNOS4/5)
864 select ARCH_USES_GETTIMEOFFSET
865 select NEED_MACH_MEMORY_H
867 Support for the StrongARM based Digital DNARD machine, also known
868 as "Shark" (<http://www.shark-linux.de/shark.html>).
871 bool "Telechips TCC ARM926-based systems"
876 select GENERIC_CLOCKEVENTS
878 Support for Telechips TCC ARM926-based systems.
881 bool "ST-Ericsson U300 Series"
885 select HAVE_SCHED_CLOCK
888 select ARM_PATCH_PHYS_VIRT
890 select GENERIC_CLOCKEVENTS
892 select HAVE_MACH_CLKDEV
894 select ARCH_REQUIRE_GPIOLIB
895 select NEED_MACH_MEMORY_H
897 Support for ST-Ericsson U300 series mobile platforms.
900 bool "ST-Ericsson U8500 Series"
903 select GENERIC_CLOCKEVENTS
905 select ARCH_REQUIRE_GPIOLIB
906 select ARCH_HAS_CPUFREQ
908 Support for ST-Ericsson's Ux500 architecture
911 bool "STMicroelectronics Nomadik"
916 select GENERIC_CLOCKEVENTS
917 select ARCH_REQUIRE_GPIOLIB
919 Support for the Nomadik platform by ST-Ericsson
923 select GENERIC_CLOCKEVENTS
924 select ARCH_REQUIRE_GPIOLIB
928 select GENERIC_ALLOCATOR
929 select GENERIC_IRQ_CHIP
930 select ARCH_HAS_HOLES_MEMORYMODEL
932 Support for TI's DaVinci platform.
937 select ARCH_REQUIRE_GPIOLIB
938 select ARCH_HAS_CPUFREQ
940 select GENERIC_CLOCKEVENTS
941 select HAVE_SCHED_CLOCK
942 select ARCH_HAS_HOLES_MEMORYMODEL
944 Support for TI's OMAP platform (OMAP1/2/3/4).
949 select ARCH_REQUIRE_GPIOLIB
952 select GENERIC_CLOCKEVENTS
955 Support for ST's SPEAr platform (SPEAr3xx, SPEAr6xx and SPEAr13xx).
958 bool "VIA/WonderMedia 85xx"
961 select ARCH_HAS_CPUFREQ
962 select GENERIC_CLOCKEVENTS
963 select ARCH_REQUIRE_GPIOLIB
966 Support for VIA/WonderMedia VT8500/WM85xx System-on-Chip.
969 bool "Xilinx Zynq ARM Cortex A9 Platform"
971 select GENERIC_CLOCKEVENTS
978 Support for Xilinx Zynq ARM Cortex A9 Platform
982 # This is sorted alphabetically by mach-* pathname. However, plat-*
983 # Kconfigs may be included either alphabetically (according to the
984 # plat- suffix) or along side the corresponding mach-* source.
986 source "arch/arm/mach-at91/Kconfig"
988 source "arch/arm/mach-bcmring/Kconfig"
990 source "arch/arm/mach-clps711x/Kconfig"
992 source "arch/arm/mach-cns3xxx/Kconfig"
994 source "arch/arm/mach-davinci/Kconfig"
996 source "arch/arm/mach-dove/Kconfig"
998 source "arch/arm/mach-ep93xx/Kconfig"
1000 source "arch/arm/mach-footbridge/Kconfig"
1002 source "arch/arm/mach-gemini/Kconfig"
1004 source "arch/arm/mach-h720x/Kconfig"
1006 source "arch/arm/mach-integrator/Kconfig"
1008 source "arch/arm/mach-iop32x/Kconfig"
1010 source "arch/arm/mach-iop33x/Kconfig"
1012 source "arch/arm/mach-iop13xx/Kconfig"
1014 source "arch/arm/mach-ixp4xx/Kconfig"
1016 source "arch/arm/mach-ixp2000/Kconfig"
1018 source "arch/arm/mach-ixp23xx/Kconfig"
1020 source "arch/arm/mach-kirkwood/Kconfig"
1022 source "arch/arm/mach-ks8695/Kconfig"
1024 source "arch/arm/mach-lpc32xx/Kconfig"
1026 source "arch/arm/mach-msm/Kconfig"
1028 source "arch/arm/mach-mv78xx0/Kconfig"
1030 source "arch/arm/plat-mxc/Kconfig"
1032 source "arch/arm/mach-mxs/Kconfig"
1034 source "arch/arm/mach-netx/Kconfig"
1036 source "arch/arm/mach-nomadik/Kconfig"
1037 source "arch/arm/plat-nomadik/Kconfig"
1039 source "arch/arm/plat-omap/Kconfig"
1041 source "arch/arm/mach-omap1/Kconfig"
1043 source "arch/arm/mach-omap2/Kconfig"
1045 source "arch/arm/mach-orion5x/Kconfig"
1047 source "arch/arm/mach-pxa/Kconfig"
1048 source "arch/arm/plat-pxa/Kconfig"
1050 source "arch/arm/mach-mmp/Kconfig"
1052 source "arch/arm/mach-realview/Kconfig"
1054 source "arch/arm/mach-sa1100/Kconfig"
1056 source "arch/arm/plat-samsung/Kconfig"
1057 source "arch/arm/plat-s3c24xx/Kconfig"
1058 source "arch/arm/plat-s5p/Kconfig"
1060 source "arch/arm/plat-spear/Kconfig"
1062 source "arch/arm/plat-tcc/Kconfig"
1065 source "arch/arm/mach-s3c2410/Kconfig"
1066 source "arch/arm/mach-s3c2412/Kconfig"
1067 source "arch/arm/mach-s3c2416/Kconfig"
1068 source "arch/arm/mach-s3c2440/Kconfig"
1069 source "arch/arm/mach-s3c2443/Kconfig"
1073 source "arch/arm/mach-s3c64xx/Kconfig"
1076 source "arch/arm/mach-s5p64x0/Kconfig"
1078 source "arch/arm/mach-s5pc100/Kconfig"
1080 source "arch/arm/mach-s5pv210/Kconfig"
1082 source "arch/arm/mach-exynos/Kconfig"
1084 source "arch/arm/mach-shmobile/Kconfig"
1086 source "arch/arm/mach-tegra/Kconfig"
1088 source "arch/arm/mach-u300/Kconfig"
1090 source "arch/arm/mach-ux500/Kconfig"
1092 source "arch/arm/mach-versatile/Kconfig"
1094 source "arch/arm/mach-vexpress/Kconfig"
1095 source "arch/arm/plat-versatile/Kconfig"
1097 source "arch/arm/mach-vt8500/Kconfig"
1099 source "arch/arm/mach-w90x900/Kconfig"
1101 # Definitions to make life easier
1107 select GENERIC_CLOCKEVENTS
1108 select HAVE_SCHED_CLOCK
1113 select GENERIC_IRQ_CHIP
1114 select HAVE_SCHED_CLOCK
1119 config PLAT_VERSATILE
1122 config ARM_TIMER_SP804
1126 source arch/arm/mm/Kconfig
1129 bool "Enable iWMMXt support"
1130 depends on CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_PJ4
1131 default y if PXA27x || PXA3xx || PXA95x || ARCH_MMP
1133 Enable support for iWMMXt context switching at run time if
1134 running on a CPU that supports it.
1136 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
1139 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
1143 depends on (CPU_V6 || CPU_V6K || CPU_V7 || XSCALE_PMU) && \
1144 (!ARCH_OMAP3 || OMAP3_EMU)
1148 config MULTI_IRQ_HANDLER
1151 Allow each machine to specify it's own IRQ handler at run time.
1154 source "arch/arm/Kconfig-nommu"
1157 config ARM_ERRATA_411920
1158 bool "ARM errata: Invalidation of the Instruction Cache operation can fail"
1159 depends on CPU_V6 || CPU_V6K
1161 Invalidation of the Instruction Cache operation can
1162 fail. This erratum is present in 1136 (before r1p4), 1156 and 1176.
1163 It does not affect the MPCore. This option enables the ARM Ltd.
1164 recommended workaround.
1166 config ARM_ERRATA_430973
1167 bool "ARM errata: Stale prediction on replaced interworking branch"
1170 This option enables the workaround for the 430973 Cortex-A8
1171 (r1p0..r1p2) erratum. If a code sequence containing an ARM/Thumb
1172 interworking branch is replaced with another code sequence at the
1173 same virtual address, whether due to self-modifying code or virtual
1174 to physical address re-mapping, Cortex-A8 does not recover from the
1175 stale interworking branch prediction. This results in Cortex-A8
1176 executing the new code sequence in the incorrect ARM or Thumb state.
1177 The workaround enables the BTB/BTAC operations by setting ACTLR.IBE
1178 and also flushes the branch target cache at every context switch.
1179 Note that setting specific bits in the ACTLR register may not be
1180 available in non-secure mode.
1182 config ARM_ERRATA_458693
1183 bool "ARM errata: Processor deadlock when a false hazard is created"
1186 This option enables the workaround for the 458693 Cortex-A8 (r2p0)
1187 erratum. For very specific sequences of memory operations, it is
1188 possible for a hazard condition intended for a cache line to instead
1189 be incorrectly associated with a different cache line. This false
1190 hazard might then cause a processor deadlock. The workaround enables
1191 the L1 caching of the NEON accesses and disables the PLD instruction
1192 in the ACTLR register. Note that setting specific bits in the ACTLR
1193 register may not be available in non-secure mode.
1195 config ARM_ERRATA_460075
1196 bool "ARM errata: Data written to the L2 cache can be overwritten with stale data"
1199 This option enables the workaround for the 460075 Cortex-A8 (r2p0)
1200 erratum. Any asynchronous access to the L2 cache may encounter a
1201 situation in which recent store transactions to the L2 cache are lost
1202 and overwritten with stale memory contents from external memory. The
1203 workaround disables the write-allocate mode for the L2 cache via the
1204 ACTLR register. Note that setting specific bits in the ACTLR register
1205 may not be available in non-secure mode.
1207 config ARM_ERRATA_742230
1208 bool "ARM errata: DMB operation may be faulty"
1209 depends on CPU_V7 && SMP
1211 This option enables the workaround for the 742230 Cortex-A9
1212 (r1p0..r2p2) erratum. Under rare circumstances, a DMB instruction
1213 between two write operations may not ensure the correct visibility
1214 ordering of the two writes. This workaround sets a specific bit in
1215 the diagnostic register of the Cortex-A9 which causes the DMB
1216 instruction to behave as a DSB, ensuring the correct behaviour of
1219 config ARM_ERRATA_742231
1220 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
1221 depends on CPU_V7 && SMP
1223 This option enables the workaround for the 742231 Cortex-A9
1224 (r2p0..r2p2) erratum. Under certain conditions, specific to the
1225 Cortex-A9 MPCore micro-architecture, two CPUs working in SMP mode,
1226 accessing some data located in the same cache line, may get corrupted
1227 data due to bad handling of the address hazard when the line gets
1228 replaced from one of the CPUs at the same time as another CPU is
1229 accessing it. This workaround sets specific bits in the diagnostic
1230 register of the Cortex-A9 which reduces the linefill issuing
1231 capabilities of the processor.
1233 config PL310_ERRATA_588369
1234 bool "Clean & Invalidate maintenance operations do not invalidate clean lines"
1235 depends on CACHE_L2X0
1237 The PL310 L2 cache controller implements three types of Clean &
1238 Invalidate maintenance operations: by Physical Address
1239 (offset 0x7F0), by Index/Way (0x7F8) and by Way (0x7FC).
1240 They are architecturally defined to behave as the execution of a
1241 clean operation followed immediately by an invalidate operation,
1242 both performing to the same memory location. This functionality
1243 is not correctly implemented in PL310 as clean lines are not
1244 invalidated as a result of these operations.
1246 config ARM_ERRATA_720789
1247 bool "ARM errata: TLBIASIDIS and TLBIMVAIS operations can broadcast a faulty ASID"
1248 depends on CPU_V7 && SMP
1250 This option enables the workaround for the 720789 Cortex-A9 (prior to
1251 r2p0) erratum. A faulty ASID can be sent to the other CPUs for the
1252 broadcasted CP15 TLB maintenance operations TLBIASIDIS and TLBIMVAIS.
1253 As a consequence of this erratum, some TLB entries which should be
1254 invalidated are not, resulting in an incoherency in the system page
1255 tables. The workaround changes the TLB flushing routines to invalidate
1256 entries regardless of the ASID.
1258 config PL310_ERRATA_727915
1259 bool "Background Clean & Invalidate by Way operation can cause data corruption"
1260 depends on CACHE_L2X0
1262 PL310 implements the Clean & Invalidate by Way L2 cache maintenance
1263 operation (offset 0x7FC). This operation runs in background so that
1264 PL310 can handle normal accesses while it is in progress. Under very
1265 rare circumstances, due to this erratum, write data can be lost when
1266 PL310 treats a cacheable write transaction during a Clean &
1267 Invalidate by Way operation.
1269 config ARM_ERRATA_743622
1270 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
1273 This option enables the workaround for the 743622 Cortex-A9
1274 (r2p0..r2p2) erratum. Under very rare conditions, a faulty
1275 optimisation in the Cortex-A9 Store Buffer may lead to data
1276 corruption. This workaround sets a specific bit in the diagnostic
1277 register of the Cortex-A9 which disables the Store Buffer
1278 optimisation, preventing the defect from occurring. This has no
1279 visible impact on the overall performance or power consumption of the
1282 config ARM_ERRATA_751472
1283 bool "ARM errata: Interrupted ICIALLUIS may prevent completion of broadcasted operation"
1284 depends on CPU_V7 && SMP
1286 This option enables the workaround for the 751472 Cortex-A9 (prior
1287 to r3p0) erratum. An interrupted ICIALLUIS operation may prevent the
1288 completion of a following broadcasted operation if the second
1289 operation is received by a CPU before the ICIALLUIS has completed,
1290 potentially leading to corrupted entries in the cache or TLB.
1292 config ARM_ERRATA_753970
1293 bool "ARM errata: cache sync operation may be faulty"
1294 depends on CACHE_PL310
1296 This option enables the workaround for the 753970 PL310 (r3p0) erratum.
1298 Under some condition the effect of cache sync operation on
1299 the store buffer still remains when the operation completes.
1300 This means that the store buffer is always asked to drain and
1301 this prevents it from merging any further writes. The workaround
1302 is to replace the normal offset of cache sync operation (0x730)
1303 by another offset targeting an unmapped PL310 register 0x740.
1304 This has the same effect as the cache sync operation: store buffer
1305 drain and waiting for all buffers empty.
1307 config ARM_ERRATA_754322
1308 bool "ARM errata: possible faulty MMU translations following an ASID switch"
1311 This option enables the workaround for the 754322 Cortex-A9 (r2p*,
1312 r3p*) erratum. A speculative memory access may cause a page table walk
1313 which starts prior to an ASID switch but completes afterwards. This
1314 can populate the micro-TLB with a stale entry which may be hit with
1315 the new ASID. This workaround places two dsb instructions in the mm
1316 switching code so that no page table walks can cross the ASID switch.
1318 config ARM_ERRATA_754327
1319 bool "ARM errata: no automatic Store Buffer drain"
1320 depends on CPU_V7 && SMP
1322 This option enables the workaround for the 754327 Cortex-A9 (prior to
1323 r2p0) erratum. The Store Buffer does not have any automatic draining
1324 mechanism and therefore a livelock may occur if an external agent
1325 continuously polls a memory location waiting to observe an update.
1326 This workaround defines cpu_relax() as smp_mb(), preventing correctly
1327 written polling loops from denying visibility of updates to memory.
1329 config ARM_ERRATA_364296
1330 bool "ARM errata: Possible cache data corruption with hit-under-miss enabled"
1331 depends on CPU_V6 && !SMP
1333 This options enables the workaround for the 364296 ARM1136
1334 r0p2 erratum (possible cache data corruption with
1335 hit-under-miss enabled). It sets the undocumented bit 31 in
1336 the auxiliary control register and the FI bit in the control
1337 register, thus disabling hit-under-miss without putting the
1338 processor into full low interrupt latency mode. ARM11MPCore
1341 config ARM_ERRATA_764369
1342 bool "ARM errata: Data cache line maintenance operation by MVA may not succeed"
1343 depends on CPU_V7 && SMP
1345 This option enables the workaround for erratum 764369
1346 affecting Cortex-A9 MPCore with two or more processors (all
1347 current revisions). Under certain timing circumstances, a data
1348 cache line maintenance operation by MVA targeting an Inner
1349 Shareable memory region may fail to proceed up to either the
1350 Point of Coherency or to the Point of Unification of the
1351 system. This workaround adds a DSB instruction before the
1352 relevant cache maintenance functions and sets a specific bit
1353 in the diagnostic control register of the SCU.
1357 source "arch/arm/common/Kconfig"
1367 Find out whether you have ISA slots on your motherboard. ISA is the
1368 name of a bus system, i.e. the way the CPU talks to the other stuff
1369 inside your box. Other bus systems are PCI, EISA, MicroChannel
1370 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1371 newer boards don't support it. If you have ISA, say Y, otherwise N.
1373 # Select ISA DMA controller support
1378 # Select ISA DMA interface
1383 bool "PCI support" if MIGHT_HAVE_PCI
1385 Find out whether you have a PCI motherboard. PCI is the name of a
1386 bus system, i.e. the way the CPU talks to the other stuff inside
1387 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1388 VESA. If you have PCI, say Y, otherwise N.
1394 config PCI_NANOENGINE
1395 bool "BSE nanoEngine PCI support"
1396 depends on SA1100_NANOENGINE
1398 Enable PCI on the BSE nanoEngine board.
1403 # Select the host bridge type
1404 config PCI_HOST_VIA82C505
1406 depends on PCI && ARCH_SHARK
1409 config PCI_HOST_ITE8152
1411 depends on PCI && MACH_ARMCORE
1415 source "drivers/pci/Kconfig"
1417 source "drivers/pcmcia/Kconfig"
1421 menu "Kernel Features"
1423 source "kernel/time/Kconfig"
1426 bool "Symmetric Multi-Processing"
1427 depends on CPU_V6K || CPU_V7
1428 depends on GENERIC_CLOCKEVENTS
1429 depends on REALVIEW_EB_ARM11MP || REALVIEW_EB_A9MP || \
1430 MACH_REALVIEW_PB11MP || MACH_REALVIEW_PBX || ARCH_OMAP4 || \
1431 ARCH_EXYNOS4 || ARCH_TEGRA || ARCH_U8500 || ARCH_VEXPRESS_CA9X4 || \
1432 ARCH_MSM_SCORPIONMP || ARCH_SHMOBILE || ARCH_HIGHBANK || SOC_IMX6Q
1434 select USE_GENERIC_SMP_HELPERS
1435 select HAVE_ARM_SCU if !ARCH_MSM_SCORPIONMP
1437 This enables support for systems with more than one CPU. If you have
1438 a system with only one CPU, like most personal computers, say N. If
1439 you have a system with more than one CPU, say Y.
1441 If you say N here, the kernel will run on single and multiprocessor
1442 machines, but will use only one CPU of a multiprocessor machine. If
1443 you say Y here, the kernel will run on many, but not all, single
1444 processor machines. On a single processor machine, the kernel will
1445 run faster if you say N here.
1447 See also <file:Documentation/x86/i386/IO-APIC.txt>,
1448 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
1449 <http://tldp.org/HOWTO/SMP-HOWTO.html>.
1451 If you don't know what to do here, say N.
1454 bool "Allow booting SMP kernel on uniprocessor systems (EXPERIMENTAL)"
1455 depends on EXPERIMENTAL
1456 depends on SMP && !XIP_KERNEL
1459 SMP kernels contain instructions which fail on non-SMP processors.
1460 Enabling this option allows the kernel to modify itself to make
1461 these instructions safe. Disabling it allows about 1K of space
1464 If you don't know what to do here, say Y.
1466 config ARM_CPU_TOPOLOGY
1467 bool "Support cpu topology definition"
1468 depends on SMP && CPU_V7
1471 Support ARM cpu topology definition. The MPIDR register defines
1472 affinity between processors which is then used to describe the cpu
1473 topology of an ARM System.
1476 bool "Multi-core scheduler support"
1477 depends on ARM_CPU_TOPOLOGY
1479 Multi-core scheduler support improves the CPU scheduler's decision
1480 making when dealing with multi-core CPU chips at a cost of slightly
1481 increased overhead in some places. If unsure say N here.
1484 bool "SMT scheduler support"
1485 depends on ARM_CPU_TOPOLOGY
1487 Improves the CPU scheduler's decision making when dealing with
1488 MultiThreading at a cost of slightly increased overhead in some
1489 places. If unsure say N here.
1494 This option enables support for the ARM system coherency unit
1501 This options enables support for the ARM timer and watchdog unit
1504 prompt "Memory split"
1507 Select the desired split between kernel and user memory.
1509 If you are not absolutely sure what you are doing, leave this
1513 bool "3G/1G user/kernel split"
1515 bool "2G/2G user/kernel split"
1517 bool "1G/3G user/kernel split"
1522 default 0x40000000 if VMSPLIT_1G
1523 default 0x80000000 if VMSPLIT_2G
1527 int "Maximum number of CPUs (2-32)"
1533 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
1534 depends on SMP && HOTPLUG && EXPERIMENTAL
1536 Say Y here to experiment with turning CPUs off and on. CPUs
1537 can be controlled through /sys/devices/system/cpu.
1540 bool "Use local timer interrupts"
1543 select HAVE_ARM_TWD if (!ARCH_MSM_SCORPIONMP && !EXYNOS4_MCT)
1545 Enable support for local timers on SMP platforms, rather then the
1546 legacy IPI broadcast method. Local timers allows the system
1547 accounting to be spread across the timer interval, preventing a
1548 "thundering herd" at every timer tick.
1550 source kernel/Kconfig.preempt
1554 default 200 if ARCH_EBSA110 || ARCH_S3C2410 || ARCH_S5P64X0 || \
1555 ARCH_S5PV210 || ARCH_EXYNOS4
1556 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
1557 default AT91_TIMER_HZ if ARCH_AT91
1558 default SHMOBILE_TIMER_HZ if ARCH_SHMOBILE
1561 config THUMB2_KERNEL
1562 bool "Compile the kernel in Thumb-2 mode (EXPERIMENTAL)"
1563 depends on CPU_V7 && !CPU_V6 && !CPU_V6K && EXPERIMENTAL
1565 select ARM_ASM_UNIFIED
1568 By enabling this option, the kernel will be compiled in
1569 Thumb-2 mode. A compiler/assembler that understand the unified
1570 ARM-Thumb syntax is needed.
1574 config THUMB2_AVOID_R_ARM_THM_JUMP11
1575 bool "Work around buggy Thumb-2 short branch relocations in gas"
1576 depends on THUMB2_KERNEL && MODULES
1579 Various binutils versions can resolve Thumb-2 branches to
1580 locally-defined, preemptible global symbols as short-range "b.n"
1581 branch instructions.
1583 This is a problem, because there's no guarantee the final
1584 destination of the symbol, or any candidate locations for a
1585 trampoline, are within range of the branch. For this reason, the
1586 kernel does not support fixing up the R_ARM_THM_JUMP11 (102)
1587 relocation in modules at all, and it makes little sense to add
1590 The symptom is that the kernel fails with an "unsupported
1591 relocation" error when loading some modules.
1593 Until fixed tools are available, passing
1594 -fno-optimize-sibling-calls to gcc should prevent gcc generating
1595 code which hits this problem, at the cost of a bit of extra runtime
1596 stack usage in some cases.
1598 The problem is described in more detail at:
1599 https://bugs.launchpad.net/binutils-linaro/+bug/725126
1601 Only Thumb-2 kernels are affected.
1603 Unless you are sure your tools don't have this problem, say Y.
1605 config ARM_ASM_UNIFIED
1609 bool "Use the ARM EABI to compile the kernel"
1611 This option allows for the kernel to be compiled using the latest
1612 ARM ABI (aka EABI). This is only useful if you are using a user
1613 space environment that is also compiled with EABI.
1615 Since there are major incompatibilities between the legacy ABI and
1616 EABI, especially with regard to structure member alignment, this
1617 option also changes the kernel syscall calling convention to
1618 disambiguate both ABIs and allow for backward compatibility support
1619 (selected with CONFIG_OABI_COMPAT).
1621 To use this you need GCC version 4.0.0 or later.
1624 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
1625 depends on AEABI && EXPERIMENTAL && !THUMB2_KERNEL
1628 This option preserves the old syscall interface along with the
1629 new (ARM EABI) one. It also provides a compatibility layer to
1630 intercept syscalls that have structure arguments which layout
1631 in memory differs between the legacy ABI and the new ARM EABI
1632 (only for non "thumb" binaries). This option adds a tiny
1633 overhead to all syscalls and produces a slightly larger kernel.
1634 If you know you'll be using only pure EABI user space then you
1635 can say N here. If this option is not selected and you attempt
1636 to execute a legacy ABI binary then the result will be
1637 UNPREDICTABLE (in fact it can be predicted that it won't work
1638 at all). If in doubt say Y.
1640 config ARCH_HAS_HOLES_MEMORYMODEL
1643 config ARCH_SPARSEMEM_ENABLE
1646 config ARCH_SPARSEMEM_DEFAULT
1647 def_bool ARCH_SPARSEMEM_ENABLE
1649 config ARCH_SELECT_MEMORY_MODEL
1650 def_bool ARCH_SPARSEMEM_ENABLE
1652 config HAVE_ARCH_PFN_VALID
1653 def_bool ARCH_HAS_HOLES_MEMORYMODEL || !SPARSEMEM
1656 bool "High Memory Support"
1659 The address space of ARM processors is only 4 Gigabytes large
1660 and it has to accommodate user address space, kernel address
1661 space as well as some memory mapped IO. That means that, if you
1662 have a large amount of physical memory and/or IO, not all of the
1663 memory can be "permanently mapped" by the kernel. The physical
1664 memory that is not permanently mapped is called "high memory".
1666 Depending on the selected kernel/user memory split, minimum
1667 vmalloc space and actual amount of RAM, you may not need this
1668 option which should result in a slightly faster kernel.
1673 bool "Allocate 2nd-level pagetables from highmem"
1676 config HW_PERF_EVENTS
1677 bool "Enable hardware performance counter support for perf events"
1678 depends on PERF_EVENTS && CPU_HAS_PMU
1681 Enable hardware performance counter support for perf events. If
1682 disabled, perf events will use software events only.
1686 config FORCE_MAX_ZONEORDER
1687 int "Maximum zone order" if ARCH_SHMOBILE
1688 range 11 64 if ARCH_SHMOBILE
1689 default "9" if SA1111
1692 The kernel memory allocator divides physically contiguous memory
1693 blocks into "zones", where each zone is a power of two number of
1694 pages. This option selects the largest power of two that the kernel
1695 keeps in the memory allocator. If you need to allocate very large
1696 blocks of physically contiguous memory, then you may need to
1697 increase this value.
1699 This config option is actually maximum order plus one. For example,
1700 a value of 11 means that the largest free memory block is 2^10 pages.
1703 bool "Timer and CPU usage LEDs"
1704 depends on ARCH_CDB89712 || ARCH_EBSA110 || \
1705 ARCH_EBSA285 || ARCH_INTEGRATOR || \
1706 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
1707 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
1708 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
1709 ARCH_AT91 || ARCH_DAVINCI || \
1710 ARCH_KS8695 || MACH_RD88F5182 || ARCH_REALVIEW
1712 If you say Y here, the LEDs on your machine will be used
1713 to provide useful information about your current system status.
1715 If you are compiling a kernel for a NetWinder or EBSA-285, you will
1716 be able to select which LEDs are active using the options below. If
1717 you are compiling a kernel for the EBSA-110 or the LART however, the
1718 red LED will simply flash regularly to indicate that the system is
1719 still functional. It is safe to say Y here if you have a CATS
1720 system, but the driver will do nothing.
1723 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
1724 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1725 || MACH_OMAP_PERSEUS2
1727 depends on !GENERIC_CLOCKEVENTS
1728 default y if ARCH_EBSA110
1730 If you say Y here, one of the system LEDs (the green one on the
1731 NetWinder, the amber one on the EBSA285, or the red one on the LART)
1732 will flash regularly to indicate that the system is still
1733 operational. This is mainly useful to kernel hackers who are
1734 debugging unstable kernels.
1736 The LART uses the same LED for both Timer LED and CPU usage LED
1737 functions. You may choose to use both, but the Timer LED function
1738 will overrule the CPU usage LED.
1741 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
1743 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1744 || MACH_OMAP_PERSEUS2
1747 If you say Y here, the red LED will be used to give a good real
1748 time indication of CPU usage, by lighting whenever the idle task
1749 is not currently executing.
1751 The LART uses the same LED for both Timer LED and CPU usage LED
1752 functions. You may choose to use both, but the Timer LED function
1753 will overrule the CPU usage LED.
1755 config ALIGNMENT_TRAP
1757 depends on CPU_CP15_MMU
1758 default y if !ARCH_EBSA110
1759 select HAVE_PROC_CPU if PROC_FS
1761 ARM processors cannot fetch/store information which is not
1762 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
1763 address divisible by 4. On 32-bit ARM processors, these non-aligned
1764 fetch/store instructions will be emulated in software if you say
1765 here, which has a severe performance impact. This is necessary for
1766 correct operation of some network protocols. With an IP-only
1767 configuration it is safe to say N, otherwise say Y.
1769 config UACCESS_WITH_MEMCPY
1770 bool "Use kernel mem{cpy,set}() for {copy_to,clear}_user() (EXPERIMENTAL)"
1771 depends on MMU && EXPERIMENTAL
1772 default y if CPU_FEROCEON
1774 Implement faster copy_to_user and clear_user methods for CPU
1775 cores where a 8-word STM instruction give significantly higher
1776 memory write throughput than a sequence of individual 32bit stores.
1778 A possible side effect is a slight increase in scheduling latency
1779 between threads sharing the same address space if they invoke
1780 such copy operations with large buffers.
1782 However, if the CPU data cache is using a write-allocate mode,
1783 this option is unlikely to provide any performance gain.
1787 prompt "Enable seccomp to safely compute untrusted bytecode"
1789 This kernel feature is useful for number crunching applications
1790 that may need to compute untrusted bytecode during their
1791 execution. By using pipes or other transports made available to
1792 the process as file descriptors supporting the read/write
1793 syscalls, it's possible to isolate those applications in
1794 their own address space using seccomp. Once seccomp is
1795 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1796 and the task is only allowed to execute a few safe syscalls
1797 defined by each seccomp mode.
1799 config CC_STACKPROTECTOR
1800 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1801 depends on EXPERIMENTAL
1803 This option turns on the -fstack-protector GCC feature. This
1804 feature puts, at the beginning of functions, a canary value on
1805 the stack just before the return address, and validates
1806 the value just before actually returning. Stack based buffer
1807 overflows (that need to overwrite this return address) now also
1808 overwrite the canary, which gets detected and the attack is then
1809 neutralized via a kernel panic.
1810 This feature requires gcc version 4.2 or above.
1812 config DEPRECATED_PARAM_STRUCT
1813 bool "Provide old way to pass kernel parameters"
1815 This was deprecated in 2001 and announced to live on for 5 years.
1816 Some old boot loaders still use this way.
1823 bool "Flattened Device Tree support"
1825 select OF_EARLY_FLATTREE
1828 Include support for flattened device tree machine descriptions.
1830 # Compressed boot loader in ROM. Yes, we really want to ask about
1831 # TEXT and BSS so we preserve their values in the config files.
1832 config ZBOOT_ROM_TEXT
1833 hex "Compressed ROM boot loader base address"
1836 The physical address at which the ROM-able zImage is to be
1837 placed in the target. Platforms which normally make use of
1838 ROM-able zImage formats normally set this to a suitable
1839 value in their defconfig file.
1841 If ZBOOT_ROM is not enabled, this has no effect.
1843 config ZBOOT_ROM_BSS
1844 hex "Compressed ROM boot loader BSS address"
1847 The base address of an area of read/write memory in the target
1848 for the ROM-able zImage which must be available while the
1849 decompressor is running. It must be large enough to hold the
1850 entire decompressed kernel plus an additional 128 KiB.
1851 Platforms which normally make use of ROM-able zImage formats
1852 normally set this to a suitable value in their defconfig file.
1854 If ZBOOT_ROM is not enabled, this has no effect.
1857 bool "Compressed boot loader in ROM/flash"
1858 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
1860 Say Y here if you intend to execute your compressed kernel image
1861 (zImage) directly from ROM or flash. If unsure, say N.
1864 prompt "Include SD/MMC loader in zImage (EXPERIMENTAL)"
1865 depends on ZBOOT_ROM && ARCH_SH7372 && EXPERIMENTAL
1866 default ZBOOT_ROM_NONE
1868 Include experimental SD/MMC loading code in the ROM-able zImage.
1869 With this enabled it is possible to write the the ROM-able zImage
1870 kernel image to an MMC or SD card and boot the kernel straight
1871 from the reset vector. At reset the processor Mask ROM will load
1872 the first part of the the ROM-able zImage which in turn loads the
1873 rest the kernel image to RAM.
1875 config ZBOOT_ROM_NONE
1876 bool "No SD/MMC loader in zImage (EXPERIMENTAL)"
1878 Do not load image from SD or MMC
1880 config ZBOOT_ROM_MMCIF
1881 bool "Include MMCIF loader in zImage (EXPERIMENTAL)"
1883 Load image from MMCIF hardware block.
1885 config ZBOOT_ROM_SH_MOBILE_SDHI
1886 bool "Include SuperH Mobile SDHI loader in zImage (EXPERIMENTAL)"
1888 Load image from SDHI hardware block
1892 config ARM_APPENDED_DTB
1893 bool "Use appended device tree blob to zImage (EXPERIMENTAL)"
1894 depends on OF && !ZBOOT_ROM && EXPERIMENTAL
1896 With this option, the boot code will look for a device tree binary
1897 (DTB) appended to zImage
1898 (e.g. cat zImage <filename>.dtb > zImage_w_dtb).
1900 This is meant as a backward compatibility convenience for those
1901 systems with a bootloader that can't be upgraded to accommodate
1902 the documented boot protocol using a device tree.
1904 Beware that there is very little in terms of protection against
1905 this option being confused by leftover garbage in memory that might
1906 look like a DTB header after a reboot if no actual DTB is appended
1907 to zImage. Do not leave this option active in a production kernel
1908 if you don't intend to always append a DTB. Proper passing of the
1909 location into r2 of a bootloader provided DTB is always preferable
1912 config ARM_ATAG_DTB_COMPAT
1913 bool "Supplement the appended DTB with traditional ATAG information"
1914 depends on ARM_APPENDED_DTB
1916 Some old bootloaders can't be updated to a DTB capable one, yet
1917 they provide ATAGs with memory configuration, the ramdisk address,
1918 the kernel cmdline string, etc. Such information is dynamically
1919 provided by the bootloader and can't always be stored in a static
1920 DTB. To allow a device tree enabled kernel to be used with such
1921 bootloaders, this option allows zImage to extract the information
1922 from the ATAG list and store it at run time into the appended DTB.
1925 string "Default kernel command string"
1928 On some architectures (EBSA110 and CATS), there is currently no way
1929 for the boot loader to pass arguments to the kernel. For these
1930 architectures, you should supply some command-line options at build
1931 time by entering them here. As a minimum, you should specify the
1932 memory size and the root device (e.g., mem=64M root=/dev/nfs).
1935 prompt "Kernel command line type" if CMDLINE != ""
1936 default CMDLINE_FROM_BOOTLOADER
1938 config CMDLINE_FROM_BOOTLOADER
1939 bool "Use bootloader kernel arguments if available"
1941 Uses the command-line options passed by the boot loader. If
1942 the boot loader doesn't provide any, the default kernel command
1943 string provided in CMDLINE will be used.
1945 config CMDLINE_EXTEND
1946 bool "Extend bootloader kernel arguments"
1948 The command-line arguments provided by the boot loader will be
1949 appended to the default kernel command string.
1951 config CMDLINE_FORCE
1952 bool "Always use the default kernel command string"
1954 Always use the default kernel command string, even if the boot
1955 loader passes other arguments to the kernel.
1956 This is useful if you cannot or don't want to change the
1957 command-line options your boot loader passes to the kernel.
1961 bool "Kernel Execute-In-Place from ROM"
1962 depends on !ZBOOT_ROM
1964 Execute-In-Place allows the kernel to run from non-volatile storage
1965 directly addressable by the CPU, such as NOR flash. This saves RAM
1966 space since the text section of the kernel is not loaded from flash
1967 to RAM. Read-write sections, such as the data section and stack,
1968 are still copied to RAM. The XIP kernel is not compressed since
1969 it has to run directly from flash, so it will take more space to
1970 store it. The flash address used to link the kernel object files,
1971 and for storing it, is configuration dependent. Therefore, if you
1972 say Y here, you must know the proper physical address where to
1973 store the kernel image depending on your own flash memory usage.
1975 Also note that the make target becomes "make xipImage" rather than
1976 "make zImage" or "make Image". The final kernel binary to put in
1977 ROM memory will be arch/arm/boot/xipImage.
1981 config XIP_PHYS_ADDR
1982 hex "XIP Kernel Physical Location"
1983 depends on XIP_KERNEL
1984 default "0x00080000"
1986 This is the physical address in your flash memory the kernel will
1987 be linked for and stored to. This address is dependent on your
1991 bool "Kexec system call (EXPERIMENTAL)"
1992 depends on EXPERIMENTAL
1994 kexec is a system call that implements the ability to shutdown your
1995 current kernel, and to start another kernel. It is like a reboot
1996 but it is independent of the system firmware. And like a reboot
1997 you can start any kernel with it, not just Linux.
1999 It is an ongoing process to be certain the hardware in a machine
2000 is properly shutdown, so do not be surprised if this code does not
2001 initially work for you. It may help to enable device hotplugging
2005 bool "Export atags in procfs"
2009 Should the atags used to boot the kernel be exported in an "atags"
2010 file in procfs. Useful with kexec.
2013 bool "Build kdump crash kernel (EXPERIMENTAL)"
2014 depends on EXPERIMENTAL
2016 Generate crash dump after being started by kexec. This should
2017 be normally only set in special crash dump kernels which are
2018 loaded in the main kernel with kexec-tools into a specially
2019 reserved region and then later executed after a crash by
2020 kdump/kexec. The crash dump kernel must be compiled to a
2021 memory address not used by the main kernel
2023 For more details see Documentation/kdump/kdump.txt
2025 config AUTO_ZRELADDR
2026 bool "Auto calculation of the decompressed kernel image address"
2027 depends on !ZBOOT_ROM && !ARCH_U300
2029 ZRELADDR is the physical address where the decompressed kernel
2030 image will be placed. If AUTO_ZRELADDR is selected, the address
2031 will be determined at run-time by masking the current IP with
2032 0xf8000000. This assumes the zImage being placed in the first 128MB
2033 from start of memory.
2037 menu "CPU Power Management"
2041 source "drivers/cpufreq/Kconfig"
2044 tristate "CPUfreq driver for i.MX CPUs"
2045 depends on ARCH_MXC && CPU_FREQ
2047 This enables the CPUfreq driver for i.MX CPUs.
2049 config CPU_FREQ_SA1100
2052 config CPU_FREQ_SA1110
2055 config CPU_FREQ_INTEGRATOR
2056 tristate "CPUfreq driver for ARM Integrator CPUs"
2057 depends on ARCH_INTEGRATOR && CPU_FREQ
2060 This enables the CPUfreq driver for ARM Integrator CPUs.
2062 For details, take a look at <file:Documentation/cpu-freq>.
2068 depends on CPU_FREQ && ARCH_PXA && PXA25x
2070 select CPU_FREQ_TABLE
2071 select CPU_FREQ_DEFAULT_GOV_USERSPACE
2076 Internal configuration node for common cpufreq on Samsung SoC
2078 config CPU_FREQ_S3C24XX
2079 bool "CPUfreq driver for Samsung S3C24XX series CPUs (EXPERIMENTAL)"
2080 depends on ARCH_S3C2410 && CPU_FREQ && EXPERIMENTAL
2083 This enables the CPUfreq driver for the Samsung S3C24XX family
2086 For details, take a look at <file:Documentation/cpu-freq>.
2090 config CPU_FREQ_S3C24XX_PLL
2091 bool "Support CPUfreq changing of PLL frequency (EXPERIMENTAL)"
2092 depends on CPU_FREQ_S3C24XX && EXPERIMENTAL
2094 Compile in support for changing the PLL frequency from the
2095 S3C24XX series CPUfreq driver. The PLL takes time to settle
2096 after a frequency change, so by default it is not enabled.
2098 This also means that the PLL tables for the selected CPU(s) will
2099 be built which may increase the size of the kernel image.
2101 config CPU_FREQ_S3C24XX_DEBUG
2102 bool "Debug CPUfreq Samsung driver core"
2103 depends on CPU_FREQ_S3C24XX
2105 Enable s3c_freq_dbg for the Samsung S3C CPUfreq core
2107 config CPU_FREQ_S3C24XX_IODEBUG
2108 bool "Debug CPUfreq Samsung driver IO timing"
2109 depends on CPU_FREQ_S3C24XX
2111 Enable s3c_freq_iodbg for the Samsung S3C CPUfreq core
2113 config CPU_FREQ_S3C24XX_DEBUGFS
2114 bool "Export debugfs for CPUFreq"
2115 depends on CPU_FREQ_S3C24XX && DEBUG_FS
2117 Export status information via debugfs.
2121 source "drivers/cpuidle/Kconfig"
2125 menu "Floating point emulation"
2127 comment "At least one emulation must be selected"
2130 bool "NWFPE math emulation"
2131 depends on (!AEABI || OABI_COMPAT) && !THUMB2_KERNEL
2133 Say Y to include the NWFPE floating point emulator in the kernel.
2134 This is necessary to run most binaries. Linux does not currently
2135 support floating point hardware so you need to say Y here even if
2136 your machine has an FPA or floating point co-processor podule.
2138 You may say N here if you are going to load the Acorn FPEmulator
2139 early in the bootup.
2142 bool "Support extended precision"
2143 depends on FPE_NWFPE
2145 Say Y to include 80-bit support in the kernel floating-point
2146 emulator. Otherwise, only 32 and 64-bit support is compiled in.
2147 Note that gcc does not generate 80-bit operations by default,
2148 so in most cases this option only enlarges the size of the
2149 floating point emulator without any good reason.
2151 You almost surely want to say N here.
2154 bool "FastFPE math emulation (EXPERIMENTAL)"
2155 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
2157 Say Y here to include the FAST floating point emulator in the kernel.
2158 This is an experimental much faster emulator which now also has full
2159 precision for the mantissa. It does not support any exceptions.
2160 It is very simple, and approximately 3-6 times faster than NWFPE.
2162 It should be sufficient for most programs. It may be not suitable
2163 for scientific calculations, but you have to check this for yourself.
2164 If you do not feel you need a faster FP emulation you should better
2168 bool "VFP-format floating point maths"
2169 depends on CPU_V6 || CPU_V6K || CPU_ARM926T || CPU_V7 || CPU_FEROCEON
2171 Say Y to include VFP support code in the kernel. This is needed
2172 if your hardware includes a VFP unit.
2174 Please see <file:Documentation/arm/VFP/release-notes.txt> for
2175 release notes and additional status information.
2177 Say N if your target does not have VFP hardware.
2185 bool "Advanced SIMD (NEON) Extension support"
2186 depends on VFPv3 && CPU_V7
2188 Say Y to include support code for NEON, the ARMv7 Advanced SIMD
2193 menu "Userspace binary formats"
2195 source "fs/Kconfig.binfmt"
2198 tristate "RISC OS personality"
2201 Say Y here to include the kernel code necessary if you want to run
2202 Acorn RISC OS/Arthur binaries under Linux. This code is still very
2203 experimental; if this sounds frightening, say N and sleep in peace.
2204 You can also say M here to compile this support as a module (which
2205 will be called arthur).
2209 menu "Power management options"
2211 source "kernel/power/Kconfig"
2213 config ARCH_SUSPEND_POSSIBLE
2214 depends on !ARCH_S5PC100
2215 depends on CPU_ARM920T || CPU_ARM926T || CPU_SA1100 || \
2216 CPU_V6 || CPU_V6K || CPU_V7 || CPU_XSC3 || CPU_XSCALE
2219 config ARM_CPU_SUSPEND
2224 source "net/Kconfig"
2226 source "drivers/Kconfig"
2230 source "arch/arm/Kconfig.debug"
2232 source "security/Kconfig"
2234 source "crypto/Kconfig"
2236 source "lib/Kconfig"