5 select HAVE_DMA_API_DEBUG
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
33 The ARM series is a line of low-power-consumption RISC chip designs
34 licensed by ARM Ltd and targeted at embedded applications and
35 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
36 manufactured, but legacy ARM-based PC hardware remains popular in
37 Europe. There is an ARM Linux project with a web page at
38 <http://www.arm.linux.org.uk/>.
40 config ARM_HAS_SG_CHAIN
49 config SYS_SUPPORTS_APM_EMULATION
52 config HAVE_SCHED_CLOCK
58 config ARCH_USES_GETTIMEOFFSET
62 config GENERIC_CLOCKEVENTS
65 config GENERIC_CLOCKEVENTS_BROADCAST
67 depends on GENERIC_CLOCKEVENTS
76 select GENERIC_ALLOCATOR
87 The Extended Industry Standard Architecture (EISA) bus was
88 developed as an open alternative to the IBM MicroChannel bus.
90 The EISA bus provided some of the features of the IBM MicroChannel
91 bus while maintaining backward compatibility with cards made for
92 the older ISA bus. The EISA bus saw limited use between 1988 and
93 1995 when it was made obsolete by the PCI bus.
95 Say Y here if you are building a kernel for an EISA-based machine.
105 MicroChannel Architecture is found in some IBM PS/2 machines and
106 laptops. It is a bus system similar to PCI or ISA. See
107 <file:Documentation/mca.txt> (and especially the web page given
108 there) before attempting to build an MCA bus kernel.
110 config STACKTRACE_SUPPORT
114 config HAVE_LATENCYTOP_SUPPORT
119 config LOCKDEP_SUPPORT
123 config TRACE_IRQFLAGS_SUPPORT
127 config HARDIRQS_SW_RESEND
131 config GENERIC_IRQ_PROBE
135 config GENERIC_LOCKBREAK
138 depends on SMP && PREEMPT
140 config RWSEM_GENERIC_SPINLOCK
144 config RWSEM_XCHGADD_ALGORITHM
147 config ARCH_HAS_ILOG2_U32
150 config ARCH_HAS_ILOG2_U64
153 config ARCH_HAS_CPUFREQ
156 Internal node to signify that the ARCH has CPUFREQ support
157 and that the relevant menu configurations are displayed for
160 config ARCH_HAS_CPU_IDLE_WAIT
163 config GENERIC_HWEIGHT
167 config GENERIC_CALIBRATE_DELAY
171 config ARCH_MAY_HAVE_PC_FDC
177 config NEED_DMA_MAP_STATE
180 config GENERIC_ISA_DMA
191 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
192 default DRAM_BASE if REMAP_VECTORS_TO_RAM
195 The base address of exception vectors.
197 config ARM_PATCH_PHYS_VIRT
198 bool "Patch physical to virtual translations at runtime" if EMBEDDED
200 depends on !XIP_KERNEL && MMU
201 depends on !ARCH_REALVIEW || !SPARSEMEM
203 Patch phys-to-virt and virt-to-phys translation functions at
204 boot and module load time according to the position of the
205 kernel in system memory.
207 This can only be used with non-XIP MMU kernels where the base
208 of physical memory is at a 16MB boundary.
210 Only disable this option if you know that you do not require
211 this feature (eg, building a kernel for a single machine) and
212 you need to shrink the kernel to the minimal size.
215 source "init/Kconfig"
217 source "kernel/Kconfig.freezer"
222 bool "MMU-based Paged Memory Management Support"
225 Select if you want MMU-based virtualised addressing space
226 support by paged memory management. If unsure, say 'Y'.
229 # The "ARM system type" choice list is ordered alphabetically by option
230 # text. Please add new entries in the option alphabetic order.
233 prompt "ARM system type"
234 default ARCH_VERSATILE
236 config ARCH_INTEGRATOR
237 bool "ARM Ltd. Integrator family"
239 select ARCH_HAS_CPUFREQ
241 select HAVE_MACH_CLKDEV
243 select GENERIC_CLOCKEVENTS
244 select PLAT_VERSATILE
245 select PLAT_VERSATILE_FPGA_IRQ
247 Support for ARM's Integrator platform.
250 bool "ARM Ltd. RealView family"
253 select HAVE_MACH_CLKDEV
255 select GENERIC_CLOCKEVENTS
256 select ARCH_WANT_OPTIONAL_GPIOLIB
257 select PLAT_VERSATILE
258 select PLAT_VERSATILE_CLCD
259 select ARM_TIMER_SP804
260 select GPIO_PL061 if GPIOLIB
262 This enables support for ARM Ltd RealView boards.
264 config ARCH_VERSATILE
265 bool "ARM Ltd. Versatile family"
269 select HAVE_MACH_CLKDEV
271 select GENERIC_CLOCKEVENTS
272 select ARCH_WANT_OPTIONAL_GPIOLIB
273 select PLAT_VERSATILE
274 select PLAT_VERSATILE_CLCD
275 select PLAT_VERSATILE_FPGA_IRQ
276 select ARM_TIMER_SP804
278 This enables support for ARM Ltd Versatile board.
281 bool "ARM Ltd. Versatile Express family"
282 select ARCH_WANT_OPTIONAL_GPIOLIB
284 select ARM_TIMER_SP804
286 select HAVE_MACH_CLKDEV
287 select GENERIC_CLOCKEVENTS
289 select HAVE_PATA_PLATFORM
291 select PLAT_VERSATILE
292 select PLAT_VERSATILE_CLCD
294 This enables support for the ARM Ltd Versatile Express boards.
298 select ARCH_REQUIRE_GPIOLIB
302 This enables support for systems based on the Atmel AT91RM9200,
303 AT91SAM9 and AT91CAP9 processors.
306 bool "Broadcom BCMRING"
310 select ARM_TIMER_SP804
312 select GENERIC_CLOCKEVENTS
313 select ARCH_WANT_OPTIONAL_GPIOLIB
315 Support for Broadcom's BCMRing platform.
318 bool "Cirrus Logic CLPS711x/EP721x-based"
320 select ARCH_USES_GETTIMEOFFSET
322 Support for Cirrus Logic 711x/721x based boards.
325 bool "Cavium Networks CNS3XXX family"
327 select GENERIC_CLOCKEVENTS
329 select MIGHT_HAVE_PCI
330 select PCI_DOMAINS if PCI
332 Support for Cavium Networks CNS3XXX platform.
335 bool "Cortina Systems Gemini"
337 select ARCH_REQUIRE_GPIOLIB
338 select ARCH_USES_GETTIMEOFFSET
340 Support for the Cortina Systems Gemini family SoCs
343 bool "CSR SiRFSoC PRIMA2 ARM Cortex A9 Platform"
347 select GENERIC_CLOCKEVENTS
349 select GENERIC_IRQ_CHIP
353 Support for CSR SiRFSoC ARM Cortex A9 Platform
360 select ARCH_USES_GETTIMEOFFSET
362 This is an evaluation board for the StrongARM processor available
363 from Digital. It has limited hardware on-board, including an
364 Ethernet interface, two PCMCIA sockets, two serial ports and a
373 select ARCH_REQUIRE_GPIOLIB
374 select ARCH_HAS_HOLES_MEMORYMODEL
375 select ARCH_USES_GETTIMEOFFSET
377 This enables support for the Cirrus EP93xx series of CPUs.
379 config ARCH_FOOTBRIDGE
383 select GENERIC_CLOCKEVENTS
385 Support for systems based on the DC21285 companion chip
386 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
389 bool "Freescale MXC/iMX-based"
390 select GENERIC_CLOCKEVENTS
391 select ARCH_REQUIRE_GPIOLIB
394 select GENERIC_IRQ_CHIP
395 select HAVE_SCHED_CLOCK
397 Support for Freescale MXC/iMX-based family of processors
400 bool "Freescale MXS-based"
401 select GENERIC_CLOCKEVENTS
402 select ARCH_REQUIRE_GPIOLIB
406 Support for Freescale MXS-based family of processors
409 bool "Hilscher NetX based"
413 select GENERIC_CLOCKEVENTS
415 This enables support for systems based on the Hilscher NetX Soc
418 bool "Hynix HMS720x-based"
421 select ARCH_USES_GETTIMEOFFSET
423 This enables support for systems based on the Hynix HMS720x
431 select ARCH_SUPPORTS_MSI
434 Support for Intel's IOP13XX (XScale) family of processors.
442 select ARCH_REQUIRE_GPIOLIB
444 Support for Intel's 80219 and IOP32X (XScale) family of
453 select ARCH_REQUIRE_GPIOLIB
455 Support for Intel's IOP33X (XScale) family of processors.
462 select ARCH_USES_GETTIMEOFFSET
464 Support for Intel's IXP23xx (XScale) family of processors.
467 bool "IXP2400/2800-based"
471 select ARCH_USES_GETTIMEOFFSET
473 Support for Intel's IXP2400/2800 (XScale) family of processors.
481 select GENERIC_CLOCKEVENTS
482 select HAVE_SCHED_CLOCK
483 select MIGHT_HAVE_PCI
484 select DMABOUNCE if PCI
486 Support for Intel's IXP4XX (XScale) family of processors.
492 select ARCH_REQUIRE_GPIOLIB
493 select GENERIC_CLOCKEVENTS
496 Support for the Marvell Dove SoC 88AP510
499 bool "Marvell Kirkwood"
502 select ARCH_REQUIRE_GPIOLIB
503 select GENERIC_CLOCKEVENTS
506 Support for the following Marvell Kirkwood series SoCs:
507 88F6180, 88F6192 and 88F6281.
513 select ARCH_REQUIRE_GPIOLIB
516 select USB_ARCH_HAS_OHCI
519 select GENERIC_CLOCKEVENTS
521 Support for the NXP LPC32XX family of processors
524 bool "Marvell MV78xx0"
527 select ARCH_REQUIRE_GPIOLIB
528 select GENERIC_CLOCKEVENTS
531 Support for the following Marvell MV78xx0 series SoCs:
539 select ARCH_REQUIRE_GPIOLIB
540 select GENERIC_CLOCKEVENTS
543 Support for the following Marvell Orion 5x series SoCs:
544 Orion-1 (5181), Orion-VoIP (5181L), Orion-NAS (5182),
545 Orion-2 (5281), Orion-1-90 (6183).
548 bool "Marvell PXA168/910/MMP2"
550 select ARCH_REQUIRE_GPIOLIB
552 select GENERIC_CLOCKEVENTS
553 select HAVE_SCHED_CLOCK
558 Support for Marvell's PXA168/PXA910(MMP) and MMP2 processor line.
561 bool "Micrel/Kendin KS8695"
563 select ARCH_REQUIRE_GPIOLIB
564 select ARCH_USES_GETTIMEOFFSET
566 Support for Micrel/Kendin KS8695 "Centaur" (ARM922T) based
567 System-on-Chip devices.
570 bool "Nuvoton W90X900 CPU"
572 select ARCH_REQUIRE_GPIOLIB
575 select GENERIC_CLOCKEVENTS
577 Support for Nuvoton (Winbond logic dept.) ARM9 processor,
578 At present, the w90x900 has been renamed nuc900, regarding
579 the ARM series product line, you can login the following
580 link address to know more.
582 <http://www.nuvoton.com/hq/enu/ProductAndSales/ProductLines/
583 ConsumerElectronicsIC/ARMMicrocontroller/ARMMicrocontroller>
586 bool "Nuvoton NUC93X CPU"
590 Support for Nuvoton (Winbond logic dept.) NUC93X MCU,The NUC93X is a
591 low-power and high performance MPEG-4/JPEG multimedia controller chip.
598 select GENERIC_CLOCKEVENTS
601 select HAVE_SCHED_CLOCK
602 select ARCH_HAS_CPUFREQ
604 This enables support for NVIDIA Tegra based systems (Tegra APX,
605 Tegra 6xx and Tegra 2 series).
608 bool "Philips Nexperia PNX4008 Mobile"
611 select ARCH_USES_GETTIMEOFFSET
613 This enables support for Philips PNX4008 mobile platform.
616 bool "PXA2xx/PXA3xx-based"
619 select ARCH_HAS_CPUFREQ
622 select ARCH_REQUIRE_GPIOLIB
623 select GENERIC_CLOCKEVENTS
624 select HAVE_SCHED_CLOCK
629 select MULTI_IRQ_HANDLER
631 Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
636 select GENERIC_CLOCKEVENTS
637 select ARCH_REQUIRE_GPIOLIB
640 Support for Qualcomm MSM/QSD based systems. This runs on the
641 apps processor of the MSM/QSD and depends on a shared memory
642 interface to the modem processor which runs the baseband
643 stack and controls some vital subsystems
644 (clock and power control, etc).
647 bool "Renesas SH-Mobile / R-Mobile"
650 select HAVE_MACH_CLKDEV
651 select GENERIC_CLOCKEVENTS
654 select MULTI_IRQ_HANDLER
655 select PM_GENERIC_DOMAINS if PM
657 Support for Renesas's SH-Mobile and R-Mobile ARM platforms.
664 select ARCH_MAY_HAVE_PC_FDC
665 select HAVE_PATA_PLATFORM
668 select ARCH_SPARSEMEM_ENABLE
669 select ARCH_USES_GETTIMEOFFSET
671 On the Acorn Risc-PC, Linux can support the internal IDE disk and
672 CD-ROM interface, serial and parallel port, and the floppy drive.
679 select ARCH_SPARSEMEM_ENABLE
681 select ARCH_HAS_CPUFREQ
683 select GENERIC_CLOCKEVENTS
685 select HAVE_SCHED_CLOCK
687 select ARCH_REQUIRE_GPIOLIB
689 Support for StrongARM 11x0 based boards.
692 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2416, S3C2440, S3C2442, S3C2443, S3C2450"
694 select ARCH_HAS_CPUFREQ
697 select ARCH_USES_GETTIMEOFFSET
698 select HAVE_S3C2410_I2C if I2C
700 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
701 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
702 the Samsung SMDK2410 development board (and derivatives).
704 Note, the S3C2416 and the S3C2450 are so close that they even share
705 the same SoC ID code. This means that there is no separate machine
706 directory (no arch/arm/mach-s3c2450) as the S3C2416 was first.
709 bool "Samsung S3C64XX"
716 select ARCH_USES_GETTIMEOFFSET
717 select ARCH_HAS_CPUFREQ
718 select ARCH_REQUIRE_GPIOLIB
719 select SAMSUNG_CLKSRC
720 select SAMSUNG_IRQ_VIC_TIMER
721 select S3C_GPIO_TRACK
722 select S3C_GPIO_PULL_UPDOWN
723 select S3C_GPIO_CFG_S3C24XX
724 select S3C_GPIO_CFG_S3C64XX
726 select USB_ARCH_HAS_OHCI
727 select SAMSUNG_GPIOLIB_4BIT
728 select HAVE_S3C2410_I2C if I2C
729 select HAVE_S3C2410_WATCHDOG if WATCHDOG
731 Samsung S3C64XX series based systems
734 bool "Samsung S5P6440 S5P6450"
740 select HAVE_S3C2410_WATCHDOG if WATCHDOG
741 select GENERIC_CLOCKEVENTS
742 select HAVE_SCHED_CLOCK
743 select HAVE_S3C2410_I2C if I2C
744 select HAVE_S3C_RTC if RTC_CLASS
746 Samsung S5P64X0 CPU based systems, such as the Samsung SMDK6440,
750 bool "Samsung S5PC100"
755 select ARM_L1_CACHE_SHIFT_6
756 select ARCH_USES_GETTIMEOFFSET
757 select HAVE_S3C2410_I2C if I2C
758 select HAVE_S3C_RTC if RTC_CLASS
759 select HAVE_S3C2410_WATCHDOG if WATCHDOG
761 Samsung S5PC100 series based systems
764 bool "Samsung S5PV210/S5PC110"
766 select ARCH_SPARSEMEM_ENABLE
767 select ARCH_HAS_HOLES_MEMORYMODEL
772 select ARM_L1_CACHE_SHIFT_6
773 select ARCH_HAS_CPUFREQ
774 select GENERIC_CLOCKEVENTS
775 select HAVE_SCHED_CLOCK
776 select HAVE_S3C2410_I2C if I2C
777 select HAVE_S3C_RTC if RTC_CLASS
778 select HAVE_S3C2410_WATCHDOG if WATCHDOG
780 Samsung S5PV210/S5PC110 series based systems
783 bool "Samsung EXYNOS4"
785 select ARCH_SPARSEMEM_ENABLE
786 select ARCH_HAS_HOLES_MEMORYMODEL
790 select ARCH_HAS_CPUFREQ
791 select GENERIC_CLOCKEVENTS
792 select HAVE_S3C_RTC if RTC_CLASS
793 select HAVE_S3C2410_I2C if I2C
794 select HAVE_S3C2410_WATCHDOG if WATCHDOG
796 Samsung EXYNOS4 series based systems
805 select ARCH_USES_GETTIMEOFFSET
807 Support for the StrongARM based Digital DNARD machine, also known
808 as "Shark" (<http://www.shark-linux.de/shark.html>).
811 bool "Telechips TCC ARM926-based systems"
816 select GENERIC_CLOCKEVENTS
818 Support for Telechips TCC ARM926-based systems.
821 bool "ST-Ericsson U300 Series"
825 select HAVE_SCHED_CLOCK
828 select ARM_PATCH_PHYS_VIRT
830 select GENERIC_CLOCKEVENTS
832 select HAVE_MACH_CLKDEV
835 Support for ST-Ericsson U300 series mobile platforms.
838 bool "ST-Ericsson U8500 Series"
841 select GENERIC_CLOCKEVENTS
843 select ARCH_REQUIRE_GPIOLIB
844 select ARCH_HAS_CPUFREQ
846 Support for ST-Ericsson's Ux500 architecture
849 bool "STMicroelectronics Nomadik"
854 select GENERIC_CLOCKEVENTS
855 select ARCH_REQUIRE_GPIOLIB
857 Support for the Nomadik platform by ST-Ericsson
861 select GENERIC_CLOCKEVENTS
862 select ARCH_REQUIRE_GPIOLIB
866 select GENERIC_ALLOCATOR
867 select GENERIC_IRQ_CHIP
868 select ARCH_HAS_HOLES_MEMORYMODEL
870 Support for TI's DaVinci platform.
875 select ARCH_REQUIRE_GPIOLIB
876 select ARCH_HAS_CPUFREQ
878 select GENERIC_CLOCKEVENTS
879 select HAVE_SCHED_CLOCK
880 select ARCH_HAS_HOLES_MEMORYMODEL
882 Support for TI's OMAP platform (OMAP1/2/3/4).
887 select ARCH_REQUIRE_GPIOLIB
890 select GENERIC_CLOCKEVENTS
893 Support for ST's SPEAr platform (SPEAr3xx, SPEAr6xx and SPEAr13xx).
896 bool "VIA/WonderMedia 85xx"
899 select ARCH_HAS_CPUFREQ
900 select GENERIC_CLOCKEVENTS
901 select ARCH_REQUIRE_GPIOLIB
904 Support for VIA/WonderMedia VT8500/WM85xx System-on-Chip.
907 bool "Xilinx Zynq ARM Cortex A9 Platform"
910 select GENERIC_CLOCKEVENTS
917 Support for Xilinx Zynq ARM Cortex A9 Platform
921 # This is sorted alphabetically by mach-* pathname. However, plat-*
922 # Kconfigs may be included either alphabetically (according to the
923 # plat- suffix) or along side the corresponding mach-* source.
925 source "arch/arm/mach-at91/Kconfig"
927 source "arch/arm/mach-bcmring/Kconfig"
929 source "arch/arm/mach-clps711x/Kconfig"
931 source "arch/arm/mach-cns3xxx/Kconfig"
933 source "arch/arm/mach-davinci/Kconfig"
935 source "arch/arm/mach-dove/Kconfig"
937 source "arch/arm/mach-ep93xx/Kconfig"
939 source "arch/arm/mach-footbridge/Kconfig"
941 source "arch/arm/mach-gemini/Kconfig"
943 source "arch/arm/mach-h720x/Kconfig"
945 source "arch/arm/mach-integrator/Kconfig"
947 source "arch/arm/mach-iop32x/Kconfig"
949 source "arch/arm/mach-iop33x/Kconfig"
951 source "arch/arm/mach-iop13xx/Kconfig"
953 source "arch/arm/mach-ixp4xx/Kconfig"
955 source "arch/arm/mach-ixp2000/Kconfig"
957 source "arch/arm/mach-ixp23xx/Kconfig"
959 source "arch/arm/mach-kirkwood/Kconfig"
961 source "arch/arm/mach-ks8695/Kconfig"
963 source "arch/arm/mach-lpc32xx/Kconfig"
965 source "arch/arm/mach-msm/Kconfig"
967 source "arch/arm/mach-mv78xx0/Kconfig"
969 source "arch/arm/plat-mxc/Kconfig"
971 source "arch/arm/mach-mxs/Kconfig"
973 source "arch/arm/mach-netx/Kconfig"
975 source "arch/arm/mach-nomadik/Kconfig"
976 source "arch/arm/plat-nomadik/Kconfig"
978 source "arch/arm/mach-nuc93x/Kconfig"
980 source "arch/arm/plat-omap/Kconfig"
982 source "arch/arm/mach-omap1/Kconfig"
984 source "arch/arm/mach-omap2/Kconfig"
986 source "arch/arm/mach-orion5x/Kconfig"
988 source "arch/arm/mach-pxa/Kconfig"
989 source "arch/arm/plat-pxa/Kconfig"
991 source "arch/arm/mach-mmp/Kconfig"
993 source "arch/arm/mach-realview/Kconfig"
995 source "arch/arm/mach-sa1100/Kconfig"
997 source "arch/arm/plat-samsung/Kconfig"
998 source "arch/arm/plat-s3c24xx/Kconfig"
999 source "arch/arm/plat-s5p/Kconfig"
1001 source "arch/arm/plat-spear/Kconfig"
1003 source "arch/arm/plat-tcc/Kconfig"
1006 source "arch/arm/mach-s3c2410/Kconfig"
1007 source "arch/arm/mach-s3c2412/Kconfig"
1008 source "arch/arm/mach-s3c2416/Kconfig"
1009 source "arch/arm/mach-s3c2440/Kconfig"
1010 source "arch/arm/mach-s3c2443/Kconfig"
1014 source "arch/arm/mach-s3c64xx/Kconfig"
1017 source "arch/arm/mach-s5p64x0/Kconfig"
1019 source "arch/arm/mach-s5pc100/Kconfig"
1021 source "arch/arm/mach-s5pv210/Kconfig"
1023 source "arch/arm/mach-exynos4/Kconfig"
1025 source "arch/arm/mach-shmobile/Kconfig"
1027 source "arch/arm/mach-tegra/Kconfig"
1029 source "arch/arm/mach-u300/Kconfig"
1031 source "arch/arm/mach-ux500/Kconfig"
1033 source "arch/arm/mach-versatile/Kconfig"
1035 source "arch/arm/mach-vexpress/Kconfig"
1036 source "arch/arm/plat-versatile/Kconfig"
1038 source "arch/arm/mach-vt8500/Kconfig"
1040 source "arch/arm/mach-w90x900/Kconfig"
1042 # Definitions to make life easier
1048 select GENERIC_CLOCKEVENTS
1049 select HAVE_SCHED_CLOCK
1054 select GENERIC_IRQ_CHIP
1055 select HAVE_SCHED_CLOCK
1060 config PLAT_VERSATILE
1063 config ARM_TIMER_SP804
1067 source arch/arm/mm/Kconfig
1070 bool "Enable iWMMXt support"
1071 depends on CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_PJ4
1072 default y if PXA27x || PXA3xx || PXA95x || ARCH_MMP
1074 Enable support for iWMMXt context switching at run time if
1075 running on a CPU that supports it.
1077 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
1080 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
1084 depends on (CPU_V6 || CPU_V6K || CPU_V7 || XSCALE_PMU) && \
1085 (!ARCH_OMAP3 || OMAP3_EMU)
1089 config MULTI_IRQ_HANDLER
1092 Allow each machine to specify it's own IRQ handler at run time.
1095 source "arch/arm/Kconfig-nommu"
1098 config ARM_ERRATA_411920
1099 bool "ARM errata: Invalidation of the Instruction Cache operation can fail"
1100 depends on CPU_V6 || CPU_V6K
1102 Invalidation of the Instruction Cache operation can
1103 fail. This erratum is present in 1136 (before r1p4), 1156 and 1176.
1104 It does not affect the MPCore. This option enables the ARM Ltd.
1105 recommended workaround.
1107 config ARM_ERRATA_430973
1108 bool "ARM errata: Stale prediction on replaced interworking branch"
1111 This option enables the workaround for the 430973 Cortex-A8
1112 (r1p0..r1p2) erratum. If a code sequence containing an ARM/Thumb
1113 interworking branch is replaced with another code sequence at the
1114 same virtual address, whether due to self-modifying code or virtual
1115 to physical address re-mapping, Cortex-A8 does not recover from the
1116 stale interworking branch prediction. This results in Cortex-A8
1117 executing the new code sequence in the incorrect ARM or Thumb state.
1118 The workaround enables the BTB/BTAC operations by setting ACTLR.IBE
1119 and also flushes the branch target cache at every context switch.
1120 Note that setting specific bits in the ACTLR register may not be
1121 available in non-secure mode.
1123 config ARM_ERRATA_458693
1124 bool "ARM errata: Processor deadlock when a false hazard is created"
1127 This option enables the workaround for the 458693 Cortex-A8 (r2p0)
1128 erratum. For very specific sequences of memory operations, it is
1129 possible for a hazard condition intended for a cache line to instead
1130 be incorrectly associated with a different cache line. This false
1131 hazard might then cause a processor deadlock. The workaround enables
1132 the L1 caching of the NEON accesses and disables the PLD instruction
1133 in the ACTLR register. Note that setting specific bits in the ACTLR
1134 register may not be available in non-secure mode.
1136 config ARM_ERRATA_460075
1137 bool "ARM errata: Data written to the L2 cache can be overwritten with stale data"
1140 This option enables the workaround for the 460075 Cortex-A8 (r2p0)
1141 erratum. Any asynchronous access to the L2 cache may encounter a
1142 situation in which recent store transactions to the L2 cache are lost
1143 and overwritten with stale memory contents from external memory. The
1144 workaround disables the write-allocate mode for the L2 cache via the
1145 ACTLR register. Note that setting specific bits in the ACTLR register
1146 may not be available in non-secure mode.
1148 config ARM_ERRATA_742230
1149 bool "ARM errata: DMB operation may be faulty"
1150 depends on CPU_V7 && SMP
1152 This option enables the workaround for the 742230 Cortex-A9
1153 (r1p0..r2p2) erratum. Under rare circumstances, a DMB instruction
1154 between two write operations may not ensure the correct visibility
1155 ordering of the two writes. This workaround sets a specific bit in
1156 the diagnostic register of the Cortex-A9 which causes the DMB
1157 instruction to behave as a DSB, ensuring the correct behaviour of
1160 config ARM_ERRATA_742231
1161 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
1162 depends on CPU_V7 && SMP
1164 This option enables the workaround for the 742231 Cortex-A9
1165 (r2p0..r2p2) erratum. Under certain conditions, specific to the
1166 Cortex-A9 MPCore micro-architecture, two CPUs working in SMP mode,
1167 accessing some data located in the same cache line, may get corrupted
1168 data due to bad handling of the address hazard when the line gets
1169 replaced from one of the CPUs at the same time as another CPU is
1170 accessing it. This workaround sets specific bits in the diagnostic
1171 register of the Cortex-A9 which reduces the linefill issuing
1172 capabilities of the processor.
1174 config PL310_ERRATA_588369
1175 bool "Clean & Invalidate maintenance operations do not invalidate clean lines"
1176 depends on CACHE_L2X0
1178 The PL310 L2 cache controller implements three types of Clean &
1179 Invalidate maintenance operations: by Physical Address
1180 (offset 0x7F0), by Index/Way (0x7F8) and by Way (0x7FC).
1181 They are architecturally defined to behave as the execution of a
1182 clean operation followed immediately by an invalidate operation,
1183 both performing to the same memory location. This functionality
1184 is not correctly implemented in PL310 as clean lines are not
1185 invalidated as a result of these operations.
1187 config ARM_ERRATA_720789
1188 bool "ARM errata: TLBIASIDIS and TLBIMVAIS operations can broadcast a faulty ASID"
1189 depends on CPU_V7 && SMP
1191 This option enables the workaround for the 720789 Cortex-A9 (prior to
1192 r2p0) erratum. A faulty ASID can be sent to the other CPUs for the
1193 broadcasted CP15 TLB maintenance operations TLBIASIDIS and TLBIMVAIS.
1194 As a consequence of this erratum, some TLB entries which should be
1195 invalidated are not, resulting in an incoherency in the system page
1196 tables. The workaround changes the TLB flushing routines to invalidate
1197 entries regardless of the ASID.
1199 config PL310_ERRATA_727915
1200 bool "Background Clean & Invalidate by Way operation can cause data corruption"
1201 depends on CACHE_L2X0
1203 PL310 implements the Clean & Invalidate by Way L2 cache maintenance
1204 operation (offset 0x7FC). This operation runs in background so that
1205 PL310 can handle normal accesses while it is in progress. Under very
1206 rare circumstances, due to this erratum, write data can be lost when
1207 PL310 treats a cacheable write transaction during a Clean &
1208 Invalidate by Way operation.
1210 config ARM_ERRATA_743622
1211 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
1214 This option enables the workaround for the 743622 Cortex-A9
1215 (r2p0..r2p2) erratum. Under very rare conditions, a faulty
1216 optimisation in the Cortex-A9 Store Buffer may lead to data
1217 corruption. This workaround sets a specific bit in the diagnostic
1218 register of the Cortex-A9 which disables the Store Buffer
1219 optimisation, preventing the defect from occurring. This has no
1220 visible impact on the overall performance or power consumption of the
1223 config ARM_ERRATA_751472
1224 bool "ARM errata: Interrupted ICIALLUIS may prevent completion of broadcasted operation"
1225 depends on CPU_V7 && SMP
1227 This option enables the workaround for the 751472 Cortex-A9 (prior
1228 to r3p0) erratum. An interrupted ICIALLUIS operation may prevent the
1229 completion of a following broadcasted operation if the second
1230 operation is received by a CPU before the ICIALLUIS has completed,
1231 potentially leading to corrupted entries in the cache or TLB.
1233 config ARM_ERRATA_753970
1234 bool "ARM errata: cache sync operation may be faulty"
1235 depends on CACHE_PL310
1237 This option enables the workaround for the 753970 PL310 (r3p0) erratum.
1239 Under some condition the effect of cache sync operation on
1240 the store buffer still remains when the operation completes.
1241 This means that the store buffer is always asked to drain and
1242 this prevents it from merging any further writes. The workaround
1243 is to replace the normal offset of cache sync operation (0x730)
1244 by another offset targeting an unmapped PL310 register 0x740.
1245 This has the same effect as the cache sync operation: store buffer
1246 drain and waiting for all buffers empty.
1248 config ARM_ERRATA_754322
1249 bool "ARM errata: possible faulty MMU translations following an ASID switch"
1252 This option enables the workaround for the 754322 Cortex-A9 (r2p*,
1253 r3p*) erratum. A speculative memory access may cause a page table walk
1254 which starts prior to an ASID switch but completes afterwards. This
1255 can populate the micro-TLB with a stale entry which may be hit with
1256 the new ASID. This workaround places two dsb instructions in the mm
1257 switching code so that no page table walks can cross the ASID switch.
1259 config ARM_ERRATA_754327
1260 bool "ARM errata: no automatic Store Buffer drain"
1261 depends on CPU_V7 && SMP
1263 This option enables the workaround for the 754327 Cortex-A9 (prior to
1264 r2p0) erratum. The Store Buffer does not have any automatic draining
1265 mechanism and therefore a livelock may occur if an external agent
1266 continuously polls a memory location waiting to observe an update.
1267 This workaround defines cpu_relax() as smp_mb(), preventing correctly
1268 written polling loops from denying visibility of updates to memory.
1270 config ARM_ERRATA_364296
1271 bool "ARM errata: Possible cache data corruption with hit-under-miss enabled"
1272 depends on CPU_V6 && !SMP
1274 This options enables the workaround for the 364296 ARM1136
1275 r0p2 erratum (possible cache data corruption with
1276 hit-under-miss enabled). It sets the undocumented bit 31 in
1277 the auxiliary control register and the FI bit in the control
1278 register, thus disabling hit-under-miss without putting the
1279 processor into full low interrupt latency mode. ARM11MPCore
1284 source "arch/arm/common/Kconfig"
1294 Find out whether you have ISA slots on your motherboard. ISA is the
1295 name of a bus system, i.e. the way the CPU talks to the other stuff
1296 inside your box. Other bus systems are PCI, EISA, MicroChannel
1297 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1298 newer boards don't support it. If you have ISA, say Y, otherwise N.
1300 # Select ISA DMA controller support
1305 # Select ISA DMA interface
1310 bool "PCI support" if MIGHT_HAVE_PCI
1312 Find out whether you have a PCI motherboard. PCI is the name of a
1313 bus system, i.e. the way the CPU talks to the other stuff inside
1314 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1315 VESA. If you have PCI, say Y, otherwise N.
1321 config PCI_NANOENGINE
1322 bool "BSE nanoEngine PCI support"
1323 depends on SA1100_NANOENGINE
1325 Enable PCI on the BSE nanoEngine board.
1330 # Select the host bridge type
1331 config PCI_HOST_VIA82C505
1333 depends on PCI && ARCH_SHARK
1336 config PCI_HOST_ITE8152
1338 depends on PCI && MACH_ARMCORE
1342 source "drivers/pci/Kconfig"
1344 source "drivers/pcmcia/Kconfig"
1348 menu "Kernel Features"
1350 source "kernel/time/Kconfig"
1353 bool "Symmetric Multi-Processing"
1354 depends on CPU_V6K || CPU_V7
1355 depends on GENERIC_CLOCKEVENTS
1356 depends on REALVIEW_EB_ARM11MP || REALVIEW_EB_A9MP || \
1357 MACH_REALVIEW_PB11MP || MACH_REALVIEW_PBX || ARCH_OMAP4 || \
1358 ARCH_EXYNOS4 || ARCH_TEGRA || ARCH_U8500 || ARCH_VEXPRESS_CA9X4 || \
1359 ARCH_MSM_SCORPIONMP || ARCH_SHMOBILE
1360 select USE_GENERIC_SMP_HELPERS
1361 select HAVE_ARM_SCU if !ARCH_MSM_SCORPIONMP
1363 This enables support for systems with more than one CPU. If you have
1364 a system with only one CPU, like most personal computers, say N. If
1365 you have a system with more than one CPU, say Y.
1367 If you say N here, the kernel will run on single and multiprocessor
1368 machines, but will use only one CPU of a multiprocessor machine. If
1369 you say Y here, the kernel will run on many, but not all, single
1370 processor machines. On a single processor machine, the kernel will
1371 run faster if you say N here.
1373 See also <file:Documentation/i386/IO-APIC.txt>,
1374 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
1375 <http://tldp.org/HOWTO/SMP-HOWTO.html>.
1377 If you don't know what to do here, say N.
1380 bool "Allow booting SMP kernel on uniprocessor systems (EXPERIMENTAL)"
1381 depends on EXPERIMENTAL
1382 depends on SMP && !XIP_KERNEL
1385 SMP kernels contain instructions which fail on non-SMP processors.
1386 Enabling this option allows the kernel to modify itself to make
1387 these instructions safe. Disabling it allows about 1K of space
1390 If you don't know what to do here, say Y.
1392 config ARM_CPU_TOPOLOGY
1393 bool "Support cpu topology definition"
1394 depends on SMP && CPU_V7
1397 Support ARM cpu topology definition. The MPIDR register defines
1398 affinity between processors which is then used to describe the cpu
1399 topology of an ARM System.
1402 bool "Multi-core scheduler support"
1403 depends on ARM_CPU_TOPOLOGY
1405 Multi-core scheduler support improves the CPU scheduler's decision
1406 making when dealing with multi-core CPU chips at a cost of slightly
1407 increased overhead in some places. If unsure say N here.
1410 bool "SMT scheduler support"
1411 depends on ARM_CPU_TOPOLOGY
1413 Improves the CPU scheduler's decision making when dealing with
1414 MultiThreading at a cost of slightly increased overhead in some
1415 places. If unsure say N here.
1420 This option enables support for the ARM system coherency unit
1427 This options enables support for the ARM timer and watchdog unit
1430 prompt "Memory split"
1433 Select the desired split between kernel and user memory.
1435 If you are not absolutely sure what you are doing, leave this
1439 bool "3G/1G user/kernel split"
1441 bool "2G/2G user/kernel split"
1443 bool "1G/3G user/kernel split"
1448 default 0x40000000 if VMSPLIT_1G
1449 default 0x80000000 if VMSPLIT_2G
1453 int "Maximum number of CPUs (2-32)"
1459 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
1460 depends on SMP && HOTPLUG && EXPERIMENTAL
1462 Say Y here to experiment with turning CPUs off and on. CPUs
1463 can be controlled through /sys/devices/system/cpu.
1466 bool "Use local timer interrupts"
1469 select HAVE_ARM_TWD if (!ARCH_MSM_SCORPIONMP && !EXYNOS4_MCT)
1471 Enable support for local timers on SMP platforms, rather then the
1472 legacy IPI broadcast method. Local timers allows the system
1473 accounting to be spread across the timer interval, preventing a
1474 "thundering herd" at every timer tick.
1476 source kernel/Kconfig.preempt
1480 default 200 if ARCH_EBSA110 || ARCH_S3C2410 || ARCH_S5P64X0 || \
1481 ARCH_S5PV210 || ARCH_EXYNOS4
1482 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
1483 default AT91_TIMER_HZ if ARCH_AT91
1484 default SHMOBILE_TIMER_HZ if ARCH_SHMOBILE
1487 config THUMB2_KERNEL
1488 bool "Compile the kernel in Thumb-2 mode (EXPERIMENTAL)"
1489 depends on CPU_V7 && !CPU_V6 && !CPU_V6K && EXPERIMENTAL
1491 select ARM_ASM_UNIFIED
1493 By enabling this option, the kernel will be compiled in
1494 Thumb-2 mode. A compiler/assembler that understand the unified
1495 ARM-Thumb syntax is needed.
1499 config THUMB2_AVOID_R_ARM_THM_JUMP11
1500 bool "Work around buggy Thumb-2 short branch relocations in gas"
1501 depends on THUMB2_KERNEL && MODULES
1504 Various binutils versions can resolve Thumb-2 branches to
1505 locally-defined, preemptible global symbols as short-range "b.n"
1506 branch instructions.
1508 This is a problem, because there's no guarantee the final
1509 destination of the symbol, or any candidate locations for a
1510 trampoline, are within range of the branch. For this reason, the
1511 kernel does not support fixing up the R_ARM_THM_JUMP11 (102)
1512 relocation in modules at all, and it makes little sense to add
1515 The symptom is that the kernel fails with an "unsupported
1516 relocation" error when loading some modules.
1518 Until fixed tools are available, passing
1519 -fno-optimize-sibling-calls to gcc should prevent gcc generating
1520 code which hits this problem, at the cost of a bit of extra runtime
1521 stack usage in some cases.
1523 The problem is described in more detail at:
1524 https://bugs.launchpad.net/binutils-linaro/+bug/725126
1526 Only Thumb-2 kernels are affected.
1528 Unless you are sure your tools don't have this problem, say Y.
1530 config ARM_ASM_UNIFIED
1534 bool "Use the ARM EABI to compile the kernel"
1536 This option allows for the kernel to be compiled using the latest
1537 ARM ABI (aka EABI). This is only useful if you are using a user
1538 space environment that is also compiled with EABI.
1540 Since there are major incompatibilities between the legacy ABI and
1541 EABI, especially with regard to structure member alignment, this
1542 option also changes the kernel syscall calling convention to
1543 disambiguate both ABIs and allow for backward compatibility support
1544 (selected with CONFIG_OABI_COMPAT).
1546 To use this you need GCC version 4.0.0 or later.
1549 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
1550 depends on AEABI && EXPERIMENTAL && !THUMB2_KERNEL
1553 This option preserves the old syscall interface along with the
1554 new (ARM EABI) one. It also provides a compatibility layer to
1555 intercept syscalls that have structure arguments which layout
1556 in memory differs between the legacy ABI and the new ARM EABI
1557 (only for non "thumb" binaries). This option adds a tiny
1558 overhead to all syscalls and produces a slightly larger kernel.
1559 If you know you'll be using only pure EABI user space then you
1560 can say N here. If this option is not selected and you attempt
1561 to execute a legacy ABI binary then the result will be
1562 UNPREDICTABLE (in fact it can be predicted that it won't work
1563 at all). If in doubt say Y.
1565 config ARCH_HAS_HOLES_MEMORYMODEL
1568 config ARCH_SPARSEMEM_ENABLE
1571 config ARCH_SPARSEMEM_DEFAULT
1572 def_bool ARCH_SPARSEMEM_ENABLE
1574 config ARCH_SELECT_MEMORY_MODEL
1575 def_bool ARCH_SPARSEMEM_ENABLE
1577 config HAVE_ARCH_PFN_VALID
1578 def_bool ARCH_HAS_HOLES_MEMORYMODEL || !SPARSEMEM
1581 bool "High Memory Support"
1584 The address space of ARM processors is only 4 Gigabytes large
1585 and it has to accommodate user address space, kernel address
1586 space as well as some memory mapped IO. That means that, if you
1587 have a large amount of physical memory and/or IO, not all of the
1588 memory can be "permanently mapped" by the kernel. The physical
1589 memory that is not permanently mapped is called "high memory".
1591 Depending on the selected kernel/user memory split, minimum
1592 vmalloc space and actual amount of RAM, you may not need this
1593 option which should result in a slightly faster kernel.
1598 bool "Allocate 2nd-level pagetables from highmem"
1601 config HW_PERF_EVENTS
1602 bool "Enable hardware performance counter support for perf events"
1603 depends on PERF_EVENTS && CPU_HAS_PMU
1606 Enable hardware performance counter support for perf events. If
1607 disabled, perf events will use software events only.
1611 config FORCE_MAX_ZONEORDER
1612 int "Maximum zone order" if ARCH_SHMOBILE
1613 range 11 64 if ARCH_SHMOBILE
1614 default "9" if SA1111
1617 The kernel memory allocator divides physically contiguous memory
1618 blocks into "zones", where each zone is a power of two number of
1619 pages. This option selects the largest power of two that the kernel
1620 keeps in the memory allocator. If you need to allocate very large
1621 blocks of physically contiguous memory, then you may need to
1622 increase this value.
1624 This config option is actually maximum order plus one. For example,
1625 a value of 11 means that the largest free memory block is 2^10 pages.
1628 bool "Timer and CPU usage LEDs"
1629 depends on ARCH_CDB89712 || ARCH_EBSA110 || \
1630 ARCH_EBSA285 || ARCH_INTEGRATOR || \
1631 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
1632 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
1633 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
1634 ARCH_AT91 || ARCH_DAVINCI || \
1635 ARCH_KS8695 || MACH_RD88F5182 || ARCH_REALVIEW
1637 If you say Y here, the LEDs on your machine will be used
1638 to provide useful information about your current system status.
1640 If you are compiling a kernel for a NetWinder or EBSA-285, you will
1641 be able to select which LEDs are active using the options below. If
1642 you are compiling a kernel for the EBSA-110 or the LART however, the
1643 red LED will simply flash regularly to indicate that the system is
1644 still functional. It is safe to say Y here if you have a CATS
1645 system, but the driver will do nothing.
1648 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
1649 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1650 || MACH_OMAP_PERSEUS2
1652 depends on !GENERIC_CLOCKEVENTS
1653 default y if ARCH_EBSA110
1655 If you say Y here, one of the system LEDs (the green one on the
1656 NetWinder, the amber one on the EBSA285, or the red one on the LART)
1657 will flash regularly to indicate that the system is still
1658 operational. This is mainly useful to kernel hackers who are
1659 debugging unstable kernels.
1661 The LART uses the same LED for both Timer LED and CPU usage LED
1662 functions. You may choose to use both, but the Timer LED function
1663 will overrule the CPU usage LED.
1666 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
1668 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1669 || MACH_OMAP_PERSEUS2
1672 If you say Y here, the red LED will be used to give a good real
1673 time indication of CPU usage, by lighting whenever the idle task
1674 is not currently executing.
1676 The LART uses the same LED for both Timer LED and CPU usage LED
1677 functions. You may choose to use both, but the Timer LED function
1678 will overrule the CPU usage LED.
1680 config ALIGNMENT_TRAP
1682 depends on CPU_CP15_MMU
1683 default y if !ARCH_EBSA110
1684 select HAVE_PROC_CPU if PROC_FS
1686 ARM processors cannot fetch/store information which is not
1687 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
1688 address divisible by 4. On 32-bit ARM processors, these non-aligned
1689 fetch/store instructions will be emulated in software if you say
1690 here, which has a severe performance impact. This is necessary for
1691 correct operation of some network protocols. With an IP-only
1692 configuration it is safe to say N, otherwise say Y.
1694 config UACCESS_WITH_MEMCPY
1695 bool "Use kernel mem{cpy,set}() for {copy_to,clear}_user() (EXPERIMENTAL)"
1696 depends on MMU && EXPERIMENTAL
1697 default y if CPU_FEROCEON
1699 Implement faster copy_to_user and clear_user methods for CPU
1700 cores where a 8-word STM instruction give significantly higher
1701 memory write throughput than a sequence of individual 32bit stores.
1703 A possible side effect is a slight increase in scheduling latency
1704 between threads sharing the same address space if they invoke
1705 such copy operations with large buffers.
1707 However, if the CPU data cache is using a write-allocate mode,
1708 this option is unlikely to provide any performance gain.
1712 prompt "Enable seccomp to safely compute untrusted bytecode"
1714 This kernel feature is useful for number crunching applications
1715 that may need to compute untrusted bytecode during their
1716 execution. By using pipes or other transports made available to
1717 the process as file descriptors supporting the read/write
1718 syscalls, it's possible to isolate those applications in
1719 their own address space using seccomp. Once seccomp is
1720 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1721 and the task is only allowed to execute a few safe syscalls
1722 defined by each seccomp mode.
1724 config CC_STACKPROTECTOR
1725 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1726 depends on EXPERIMENTAL
1728 This option turns on the -fstack-protector GCC feature. This
1729 feature puts, at the beginning of functions, a canary value on
1730 the stack just before the return address, and validates
1731 the value just before actually returning. Stack based buffer
1732 overflows (that need to overwrite this return address) now also
1733 overwrite the canary, which gets detected and the attack is then
1734 neutralized via a kernel panic.
1735 This feature requires gcc version 4.2 or above.
1737 config DEPRECATED_PARAM_STRUCT
1738 bool "Provide old way to pass kernel parameters"
1740 This was deprecated in 2001 and announced to live on for 5 years.
1741 Some old boot loaders still use this way.
1748 bool "Flattened Device Tree support"
1750 select OF_EARLY_FLATTREE
1753 Include support for flattened device tree machine descriptions.
1755 # Compressed boot loader in ROM. Yes, we really want to ask about
1756 # TEXT and BSS so we preserve their values in the config files.
1757 config ZBOOT_ROM_TEXT
1758 hex "Compressed ROM boot loader base address"
1761 The physical address at which the ROM-able zImage is to be
1762 placed in the target. Platforms which normally make use of
1763 ROM-able zImage formats normally set this to a suitable
1764 value in their defconfig file.
1766 If ZBOOT_ROM is not enabled, this has no effect.
1768 config ZBOOT_ROM_BSS
1769 hex "Compressed ROM boot loader BSS address"
1772 The base address of an area of read/write memory in the target
1773 for the ROM-able zImage which must be available while the
1774 decompressor is running. It must be large enough to hold the
1775 entire decompressed kernel plus an additional 128 KiB.
1776 Platforms which normally make use of ROM-able zImage formats
1777 normally set this to a suitable value in their defconfig file.
1779 If ZBOOT_ROM is not enabled, this has no effect.
1782 bool "Compressed boot loader in ROM/flash"
1783 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
1785 Say Y here if you intend to execute your compressed kernel image
1786 (zImage) directly from ROM or flash. If unsure, say N.
1789 prompt "Include SD/MMC loader in zImage (EXPERIMENTAL)"
1790 depends on ZBOOT_ROM && ARCH_SH7372 && EXPERIMENTAL
1791 default ZBOOT_ROM_NONE
1793 Include experimental SD/MMC loading code in the ROM-able zImage.
1794 With this enabled it is possible to write the the ROM-able zImage
1795 kernel image to an MMC or SD card and boot the kernel straight
1796 from the reset vector. At reset the processor Mask ROM will load
1797 the first part of the the ROM-able zImage which in turn loads the
1798 rest the kernel image to RAM.
1800 config ZBOOT_ROM_NONE
1801 bool "No SD/MMC loader in zImage (EXPERIMENTAL)"
1803 Do not load image from SD or MMC
1805 config ZBOOT_ROM_MMCIF
1806 bool "Include MMCIF loader in zImage (EXPERIMENTAL)"
1808 Load image from MMCIF hardware block.
1810 config ZBOOT_ROM_SH_MOBILE_SDHI
1811 bool "Include SuperH Mobile SDHI loader in zImage (EXPERIMENTAL)"
1813 Load image from SDHI hardware block
1818 string "Default kernel command string"
1821 On some architectures (EBSA110 and CATS), there is currently no way
1822 for the boot loader to pass arguments to the kernel. For these
1823 architectures, you should supply some command-line options at build
1824 time by entering them here. As a minimum, you should specify the
1825 memory size and the root device (e.g., mem=64M root=/dev/nfs).
1828 prompt "Kernel command line type" if CMDLINE != ""
1829 default CMDLINE_FROM_BOOTLOADER
1831 config CMDLINE_FROM_BOOTLOADER
1832 bool "Use bootloader kernel arguments if available"
1834 Uses the command-line options passed by the boot loader. If
1835 the boot loader doesn't provide any, the default kernel command
1836 string provided in CMDLINE will be used.
1838 config CMDLINE_EXTEND
1839 bool "Extend bootloader kernel arguments"
1841 The command-line arguments provided by the boot loader will be
1842 appended to the default kernel command string.
1844 config CMDLINE_FORCE
1845 bool "Always use the default kernel command string"
1847 Always use the default kernel command string, even if the boot
1848 loader passes other arguments to the kernel.
1849 This is useful if you cannot or don't want to change the
1850 command-line options your boot loader passes to the kernel.
1854 bool "Kernel Execute-In-Place from ROM"
1855 depends on !ZBOOT_ROM && !ARM_LPAE
1857 Execute-In-Place allows the kernel to run from non-volatile storage
1858 directly addressable by the CPU, such as NOR flash. This saves RAM
1859 space since the text section of the kernel is not loaded from flash
1860 to RAM. Read-write sections, such as the data section and stack,
1861 are still copied to RAM. The XIP kernel is not compressed since
1862 it has to run directly from flash, so it will take more space to
1863 store it. The flash address used to link the kernel object files,
1864 and for storing it, is configuration dependent. Therefore, if you
1865 say Y here, you must know the proper physical address where to
1866 store the kernel image depending on your own flash memory usage.
1868 Also note that the make target becomes "make xipImage" rather than
1869 "make zImage" or "make Image". The final kernel binary to put in
1870 ROM memory will be arch/arm/boot/xipImage.
1874 config XIP_PHYS_ADDR
1875 hex "XIP Kernel Physical Location"
1876 depends on XIP_KERNEL
1877 default "0x00080000"
1879 This is the physical address in your flash memory the kernel will
1880 be linked for and stored to. This address is dependent on your
1884 bool "Kexec system call (EXPERIMENTAL)"
1885 depends on EXPERIMENTAL
1887 kexec is a system call that implements the ability to shutdown your
1888 current kernel, and to start another kernel. It is like a reboot
1889 but it is independent of the system firmware. And like a reboot
1890 you can start any kernel with it, not just Linux.
1892 It is an ongoing process to be certain the hardware in a machine
1893 is properly shutdown, so do not be surprised if this code does not
1894 initially work for you. It may help to enable device hotplugging
1898 bool "Export atags in procfs"
1902 Should the atags used to boot the kernel be exported in an "atags"
1903 file in procfs. Useful with kexec.
1906 bool "Build kdump crash kernel (EXPERIMENTAL)"
1907 depends on EXPERIMENTAL
1909 Generate crash dump after being started by kexec. This should
1910 be normally only set in special crash dump kernels which are
1911 loaded in the main kernel with kexec-tools into a specially
1912 reserved region and then later executed after a crash by
1913 kdump/kexec. The crash dump kernel must be compiled to a
1914 memory address not used by the main kernel
1916 For more details see Documentation/kdump/kdump.txt
1918 config AUTO_ZRELADDR
1919 bool "Auto calculation of the decompressed kernel image address"
1920 depends on !ZBOOT_ROM && !ARCH_U300
1922 ZRELADDR is the physical address where the decompressed kernel
1923 image will be placed. If AUTO_ZRELADDR is selected, the address
1924 will be determined at run-time by masking the current IP with
1925 0xf8000000. This assumes the zImage being placed in the first 128MB
1926 from start of memory.
1930 menu "CPU Power Management"
1934 source "drivers/cpufreq/Kconfig"
1937 tristate "CPUfreq driver for i.MX CPUs"
1938 depends on ARCH_MXC && CPU_FREQ
1940 This enables the CPUfreq driver for i.MX CPUs.
1942 config CPU_FREQ_SA1100
1945 config CPU_FREQ_SA1110
1948 config CPU_FREQ_INTEGRATOR
1949 tristate "CPUfreq driver for ARM Integrator CPUs"
1950 depends on ARCH_INTEGRATOR && CPU_FREQ
1953 This enables the CPUfreq driver for ARM Integrator CPUs.
1955 For details, take a look at <file:Documentation/cpu-freq>.
1961 depends on CPU_FREQ && ARCH_PXA && PXA25x
1963 select CPU_FREQ_DEFAULT_GOV_USERSPACE
1968 Internal configuration node for common cpufreq on Samsung SoC
1970 config CPU_FREQ_S3C24XX
1971 bool "CPUfreq driver for Samsung S3C24XX series CPUs (EXPERIMENTAL)"
1972 depends on ARCH_S3C2410 && CPU_FREQ && EXPERIMENTAL
1975 This enables the CPUfreq driver for the Samsung S3C24XX family
1978 For details, take a look at <file:Documentation/cpu-freq>.
1982 config CPU_FREQ_S3C24XX_PLL
1983 bool "Support CPUfreq changing of PLL frequency (EXPERIMENTAL)"
1984 depends on CPU_FREQ_S3C24XX && EXPERIMENTAL
1986 Compile in support for changing the PLL frequency from the
1987 S3C24XX series CPUfreq driver. The PLL takes time to settle
1988 after a frequency change, so by default it is not enabled.
1990 This also means that the PLL tables for the selected CPU(s) will
1991 be built which may increase the size of the kernel image.
1993 config CPU_FREQ_S3C24XX_DEBUG
1994 bool "Debug CPUfreq Samsung driver core"
1995 depends on CPU_FREQ_S3C24XX
1997 Enable s3c_freq_dbg for the Samsung S3C CPUfreq core
1999 config CPU_FREQ_S3C24XX_IODEBUG
2000 bool "Debug CPUfreq Samsung driver IO timing"
2001 depends on CPU_FREQ_S3C24XX
2003 Enable s3c_freq_iodbg for the Samsung S3C CPUfreq core
2005 config CPU_FREQ_S3C24XX_DEBUGFS
2006 bool "Export debugfs for CPUFreq"
2007 depends on CPU_FREQ_S3C24XX && DEBUG_FS
2009 Export status information via debugfs.
2013 source "drivers/cpuidle/Kconfig"
2017 menu "Floating point emulation"
2019 comment "At least one emulation must be selected"
2022 bool "NWFPE math emulation"
2023 depends on (!AEABI || OABI_COMPAT) && !THUMB2_KERNEL
2025 Say Y to include the NWFPE floating point emulator in the kernel.
2026 This is necessary to run most binaries. Linux does not currently
2027 support floating point hardware so you need to say Y here even if
2028 your machine has an FPA or floating point co-processor podule.
2030 You may say N here if you are going to load the Acorn FPEmulator
2031 early in the bootup.
2034 bool "Support extended precision"
2035 depends on FPE_NWFPE
2037 Say Y to include 80-bit support in the kernel floating-point
2038 emulator. Otherwise, only 32 and 64-bit support is compiled in.
2039 Note that gcc does not generate 80-bit operations by default,
2040 so in most cases this option only enlarges the size of the
2041 floating point emulator without any good reason.
2043 You almost surely want to say N here.
2046 bool "FastFPE math emulation (EXPERIMENTAL)"
2047 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
2049 Say Y here to include the FAST floating point emulator in the kernel.
2050 This is an experimental much faster emulator which now also has full
2051 precision for the mantissa. It does not support any exceptions.
2052 It is very simple, and approximately 3-6 times faster than NWFPE.
2054 It should be sufficient for most programs. It may be not suitable
2055 for scientific calculations, but you have to check this for yourself.
2056 If you do not feel you need a faster FP emulation you should better
2060 bool "VFP-format floating point maths"
2061 depends on CPU_V6 || CPU_V6K || CPU_ARM926T || CPU_V7 || CPU_FEROCEON
2063 Say Y to include VFP support code in the kernel. This is needed
2064 if your hardware includes a VFP unit.
2066 Please see <file:Documentation/arm/VFP/release-notes.txt> for
2067 release notes and additional status information.
2069 Say N if your target does not have VFP hardware.
2077 bool "Advanced SIMD (NEON) Extension support"
2078 depends on VFPv3 && CPU_V7
2080 Say Y to include support code for NEON, the ARMv7 Advanced SIMD
2085 menu "Userspace binary formats"
2087 source "fs/Kconfig.binfmt"
2090 tristate "RISC OS personality"
2093 Say Y here to include the kernel code necessary if you want to run
2094 Acorn RISC OS/Arthur binaries under Linux. This code is still very
2095 experimental; if this sounds frightening, say N and sleep in peace.
2096 You can also say M here to compile this support as a module (which
2097 will be called arthur).
2101 menu "Power management options"
2103 source "kernel/power/Kconfig"
2105 config ARCH_SUSPEND_POSSIBLE
2106 depends on !ARCH_S5P64X0 && !ARCH_S5PC100
2107 depends on CPU_ARM920T || CPU_ARM926T || CPU_SA1100 || \
2108 CPU_V6 || CPU_V6K || CPU_V7 || CPU_XSC3 || CPU_XSCALE
2113 source "net/Kconfig"
2115 source "drivers/Kconfig"
2119 source "arch/arm/Kconfig.debug"
2121 source "security/Kconfig"
2123 source "crypto/Kconfig"
2125 source "lib/Kconfig"