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 && !THUMB2_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/>.
46 config SYS_SUPPORTS_APM_EMULATION
49 config HAVE_SCHED_CLOCK
55 config ARCH_USES_GETTIMEOFFSET
59 config GENERIC_CLOCKEVENTS
62 config GENERIC_CLOCKEVENTS_BROADCAST
64 depends on GENERIC_CLOCKEVENTS
73 select GENERIC_ALLOCATOR
84 The Extended Industry Standard Architecture (EISA) bus was
85 developed as an open alternative to the IBM MicroChannel bus.
87 The EISA bus provided some of the features of the IBM MicroChannel
88 bus while maintaining backward compatibility with cards made for
89 the older ISA bus. The EISA bus saw limited use between 1988 and
90 1995 when it was made obsolete by the PCI bus.
92 Say Y here if you are building a kernel for an EISA-based machine.
102 MicroChannel Architecture is found in some IBM PS/2 machines and
103 laptops. It is a bus system similar to PCI or ISA. See
104 <file:Documentation/mca.txt> (and especially the web page given
105 there) before attempting to build an MCA bus kernel.
107 config STACKTRACE_SUPPORT
111 config HAVE_LATENCYTOP_SUPPORT
116 config LOCKDEP_SUPPORT
120 config TRACE_IRQFLAGS_SUPPORT
124 config HARDIRQS_SW_RESEND
128 config GENERIC_IRQ_PROBE
132 config GENERIC_LOCKBREAK
135 depends on SMP && PREEMPT
137 config RWSEM_GENERIC_SPINLOCK
141 config RWSEM_XCHGADD_ALGORITHM
144 config ARCH_HAS_ILOG2_U32
147 config ARCH_HAS_ILOG2_U64
150 config ARCH_HAS_CPUFREQ
153 Internal node to signify that the ARCH has CPUFREQ support
154 and that the relevant menu configurations are displayed for
157 config ARCH_HAS_CPU_IDLE_WAIT
160 config GENERIC_HWEIGHT
164 config GENERIC_CALIBRATE_DELAY
168 config ARCH_MAY_HAVE_PC_FDC
174 config NEED_DMA_MAP_STATE
177 config GENERIC_ISA_DMA
188 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
189 default DRAM_BASE if REMAP_VECTORS_TO_RAM
192 The base address of exception vectors.
194 config ARM_PATCH_PHYS_VIRT
195 bool "Patch physical to virtual translations at runtime (EXPERIMENTAL)"
196 depends on EXPERIMENTAL
197 depends on !XIP_KERNEL && MMU
198 depends on !ARCH_REALVIEW || !SPARSEMEM
200 Patch phys-to-virt and virt-to-phys translation functions at
201 boot and module load time according to the position of the
202 kernel in system memory.
204 This can only be used with non-XIP MMU kernels where the base
205 of physical memory is at a 16MB boundary, or theoretically 64K
206 for the MSM machine class.
208 config ARM_PATCH_PHYS_VIRT_16BIT
210 depends on ARM_PATCH_PHYS_VIRT && ARCH_MSM
212 This option extends the physical to virtual translation patching
213 to allow physical memory down to a theoretical minimum of 64K
216 source "init/Kconfig"
218 source "kernel/Kconfig.freezer"
223 bool "MMU-based Paged Memory Management Support"
226 Select if you want MMU-based virtualised addressing space
227 support by paged memory management. If unsure, say 'Y'.
230 # The "ARM system type" choice list is ordered alphabetically by option
231 # text. Please add new entries in the option alphabetic order.
234 prompt "ARM system type"
235 default ARCH_VERSATILE
237 config ARCH_INTEGRATOR
238 bool "ARM Ltd. Integrator family"
240 select ARCH_HAS_CPUFREQ
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"
254 select GENERIC_CLOCKEVENTS
255 select ARCH_WANT_OPTIONAL_GPIOLIB
256 select PLAT_VERSATILE
257 select PLAT_VERSATILE_CLCD
258 select ARM_TIMER_SP804
259 select GPIO_PL061 if GPIOLIB
261 This enables support for ARM Ltd RealView boards.
263 config ARCH_VERSATILE
264 bool "ARM Ltd. Versatile family"
269 select GENERIC_CLOCKEVENTS
270 select ARCH_WANT_OPTIONAL_GPIOLIB
271 select PLAT_VERSATILE
272 select PLAT_VERSATILE_CLCD
273 select PLAT_VERSATILE_FPGA_IRQ
274 select ARM_TIMER_SP804
276 This enables support for ARM Ltd Versatile board.
279 bool "ARM Ltd. Versatile Express family"
280 select ARCH_WANT_OPTIONAL_GPIOLIB
282 select ARM_TIMER_SP804
284 select GENERIC_CLOCKEVENTS
286 select HAVE_PATA_PLATFORM
288 select PLAT_VERSATILE
289 select PLAT_VERSATILE_CLCD
291 This enables support for the ARM Ltd Versatile Express boards.
295 select ARCH_REQUIRE_GPIOLIB
298 select ARM_PATCH_PHYS_VIRT if MMU
300 This enables support for systems based on the Atmel AT91RM9200,
301 AT91SAM9 and AT91CAP9 processors.
304 bool "Broadcom BCMRING"
309 select GENERIC_CLOCKEVENTS
310 select ARCH_WANT_OPTIONAL_GPIOLIB
312 Support for Broadcom's BCMRing platform.
315 bool "Cirrus Logic CLPS711x/EP721x-based"
317 select ARCH_USES_GETTIMEOFFSET
319 Support for Cirrus Logic 711x/721x based boards.
322 bool "Cavium Networks CNS3XXX family"
324 select GENERIC_CLOCKEVENTS
326 select MIGHT_HAVE_PCI
327 select PCI_DOMAINS if PCI
329 Support for Cavium Networks CNS3XXX platform.
332 bool "Cortina Systems Gemini"
334 select ARCH_REQUIRE_GPIOLIB
335 select ARCH_USES_GETTIMEOFFSET
337 Support for the Cortina Systems Gemini family SoCs
344 select ARCH_USES_GETTIMEOFFSET
346 This is an evaluation board for the StrongARM processor available
347 from Digital. It has limited hardware on-board, including an
348 Ethernet interface, two PCMCIA sockets, two serial ports and a
357 select ARCH_REQUIRE_GPIOLIB
358 select ARCH_HAS_HOLES_MEMORYMODEL
359 select ARCH_USES_GETTIMEOFFSET
361 This enables support for the Cirrus EP93xx series of CPUs.
363 config ARCH_FOOTBRIDGE
367 select GENERIC_CLOCKEVENTS
369 Support for systems based on the DC21285 companion chip
370 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
373 bool "Freescale MXC/iMX-based"
374 select GENERIC_CLOCKEVENTS
375 select ARCH_REQUIRE_GPIOLIB
378 select HAVE_SCHED_CLOCK
380 Support for Freescale MXC/iMX-based family of processors
383 bool "Freescale MXS-based"
384 select GENERIC_CLOCKEVENTS
385 select ARCH_REQUIRE_GPIOLIB
389 Support for Freescale MXS-based family of processors
392 bool "Hilscher NetX based"
396 select GENERIC_CLOCKEVENTS
398 This enables support for systems based on the Hilscher NetX Soc
401 bool "Hynix HMS720x-based"
404 select ARCH_USES_GETTIMEOFFSET
406 This enables support for systems based on the Hynix HMS720x
414 select ARCH_SUPPORTS_MSI
417 Support for Intel's IOP13XX (XScale) family of processors.
425 select ARCH_REQUIRE_GPIOLIB
427 Support for Intel's 80219 and IOP32X (XScale) family of
436 select ARCH_REQUIRE_GPIOLIB
438 Support for Intel's IOP33X (XScale) family of processors.
445 select ARCH_USES_GETTIMEOFFSET
447 Support for Intel's IXP23xx (XScale) family of processors.
450 bool "IXP2400/2800-based"
454 select ARCH_USES_GETTIMEOFFSET
456 Support for Intel's IXP2400/2800 (XScale) family of processors.
464 select GENERIC_CLOCKEVENTS
465 select HAVE_SCHED_CLOCK
466 select MIGHT_HAVE_PCI
467 select DMABOUNCE if PCI
469 Support for Intel's IXP4XX (XScale) family of processors.
475 select ARCH_REQUIRE_GPIOLIB
476 select GENERIC_CLOCKEVENTS
479 Support for the Marvell Dove SoC 88AP510
482 bool "Marvell Kirkwood"
485 select ARCH_REQUIRE_GPIOLIB
486 select GENERIC_CLOCKEVENTS
489 Support for the following Marvell Kirkwood series SoCs:
490 88F6180, 88F6192 and 88F6281.
493 bool "Marvell Loki (88RC8480)"
495 select GENERIC_CLOCKEVENTS
498 Support for the Marvell Loki (88RC8480) SoC.
504 select ARCH_REQUIRE_GPIOLIB
507 select USB_ARCH_HAS_OHCI
510 select GENERIC_CLOCKEVENTS
512 Support for the NXP LPC32XX family of processors
515 bool "Marvell MV78xx0"
518 select ARCH_REQUIRE_GPIOLIB
519 select GENERIC_CLOCKEVENTS
522 Support for the following Marvell MV78xx0 series SoCs:
530 select ARCH_REQUIRE_GPIOLIB
531 select GENERIC_CLOCKEVENTS
534 Support for the following Marvell Orion 5x series SoCs:
535 Orion-1 (5181), Orion-VoIP (5181L), Orion-NAS (5182),
536 Orion-2 (5281), Orion-1-90 (6183).
539 bool "Marvell PXA168/910/MMP2"
541 select ARCH_REQUIRE_GPIOLIB
543 select GENERIC_CLOCKEVENTS
544 select HAVE_SCHED_CLOCK
549 Support for Marvell's PXA168/PXA910(MMP) and MMP2 processor line.
552 bool "Micrel/Kendin KS8695"
554 select ARCH_REQUIRE_GPIOLIB
555 select ARCH_USES_GETTIMEOFFSET
557 Support for Micrel/Kendin KS8695 "Centaur" (ARM922T) based
558 System-on-Chip devices.
561 bool "Nuvoton W90X900 CPU"
563 select ARCH_REQUIRE_GPIOLIB
566 select GENERIC_CLOCKEVENTS
568 Support for Nuvoton (Winbond logic dept.) ARM9 processor,
569 At present, the w90x900 has been renamed nuc900, regarding
570 the ARM series product line, you can login the following
571 link address to know more.
573 <http://www.nuvoton.com/hq/enu/ProductAndSales/ProductLines/
574 ConsumerElectronicsIC/ARMMicrocontroller/ARMMicrocontroller>
577 bool "Nuvoton NUC93X CPU"
581 Support for Nuvoton (Winbond logic dept.) NUC93X MCU,The NUC93X is a
582 low-power and high performance MPEG-4/JPEG multimedia controller chip.
589 select GENERIC_CLOCKEVENTS
592 select HAVE_SCHED_CLOCK
593 select ARCH_HAS_BARRIERS if CACHE_L2X0
594 select ARCH_HAS_CPUFREQ
596 This enables support for NVIDIA Tegra based systems (Tegra APX,
597 Tegra 6xx and Tegra 2 series).
600 bool "Philips Nexperia PNX4008 Mobile"
603 select ARCH_USES_GETTIMEOFFSET
605 This enables support for Philips PNX4008 mobile platform.
608 bool "PXA2xx/PXA3xx-based"
611 select ARCH_HAS_CPUFREQ
614 select ARCH_REQUIRE_GPIOLIB
615 select GENERIC_CLOCKEVENTS
616 select HAVE_SCHED_CLOCK
621 Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
626 select GENERIC_CLOCKEVENTS
627 select ARCH_REQUIRE_GPIOLIB
630 Support for Qualcomm MSM/QSD based systems. This runs on the
631 apps processor of the MSM/QSD and depends on a shared memory
632 interface to the modem processor which runs the baseband
633 stack and controls some vital subsystems
634 (clock and power control, etc).
637 bool "Renesas SH-Mobile / R-Mobile"
640 select GENERIC_CLOCKEVENTS
643 select MULTI_IRQ_HANDLER
645 Support for Renesas's SH-Mobile and R-Mobile ARM platforms.
652 select ARCH_MAY_HAVE_PC_FDC
653 select HAVE_PATA_PLATFORM
656 select ARCH_SPARSEMEM_ENABLE
657 select ARCH_USES_GETTIMEOFFSET
659 On the Acorn Risc-PC, Linux can support the internal IDE disk and
660 CD-ROM interface, serial and parallel port, and the floppy drive.
667 select ARCH_SPARSEMEM_ENABLE
669 select ARCH_HAS_CPUFREQ
671 select GENERIC_CLOCKEVENTS
673 select HAVE_SCHED_CLOCK
675 select ARCH_REQUIRE_GPIOLIB
677 Support for StrongARM 11x0 based boards.
680 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2416, S3C2440, S3C2442, S3C2443, S3C2450"
682 select ARCH_HAS_CPUFREQ
684 select ARCH_USES_GETTIMEOFFSET
685 select HAVE_S3C2410_I2C if I2C
687 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
688 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
689 the Samsung SMDK2410 development board (and derivatives).
691 Note, the S3C2416 and the S3C2450 are so close that they even share
692 the same SoC ID code. This means that there is no separate machine
693 directory (no arch/arm/mach-s3c2450) as the S3C2416 was first.
696 bool "Samsung S3C64XX"
702 select ARCH_USES_GETTIMEOFFSET
703 select ARCH_HAS_CPUFREQ
704 select ARCH_REQUIRE_GPIOLIB
705 select SAMSUNG_CLKSRC
706 select SAMSUNG_IRQ_VIC_TIMER
707 select SAMSUNG_IRQ_UART
708 select S3C_GPIO_TRACK
709 select S3C_GPIO_PULL_UPDOWN
710 select S3C_GPIO_CFG_S3C24XX
711 select S3C_GPIO_CFG_S3C64XX
713 select USB_ARCH_HAS_OHCI
714 select SAMSUNG_GPIOLIB_4BIT
715 select HAVE_S3C2410_I2C if I2C
716 select HAVE_S3C2410_WATCHDOG if WATCHDOG
718 Samsung S3C64XX series based systems
721 bool "Samsung S5P6440 S5P6450"
725 select HAVE_S3C2410_WATCHDOG if WATCHDOG
726 select GENERIC_CLOCKEVENTS
727 select HAVE_SCHED_CLOCK
728 select HAVE_S3C2410_I2C if I2C
729 select HAVE_S3C_RTC if RTC_CLASS
731 Samsung S5P64X0 CPU based systems, such as the Samsung SMDK6440,
735 bool "Samsung S5P6442"
739 select ARCH_USES_GETTIMEOFFSET
740 select HAVE_S3C2410_WATCHDOG if WATCHDOG
742 Samsung S5P6442 CPU based systems
745 bool "Samsung S5PC100"
749 select ARM_L1_CACHE_SHIFT_6
750 select ARCH_USES_GETTIMEOFFSET
751 select HAVE_S3C2410_I2C if I2C
752 select HAVE_S3C_RTC if RTC_CLASS
753 select HAVE_S3C2410_WATCHDOG if WATCHDOG
755 Samsung S5PC100 series based systems
758 bool "Samsung S5PV210/S5PC110"
760 select ARCH_SPARSEMEM_ENABLE
763 select ARM_L1_CACHE_SHIFT_6
764 select ARCH_HAS_CPUFREQ
765 select GENERIC_CLOCKEVENTS
766 select HAVE_SCHED_CLOCK
767 select HAVE_S3C2410_I2C if I2C
768 select HAVE_S3C_RTC if RTC_CLASS
769 select HAVE_S3C2410_WATCHDOG if WATCHDOG
771 Samsung S5PV210/S5PC110 series based systems
774 bool "Samsung EXYNOS4"
776 select ARCH_SPARSEMEM_ENABLE
779 select ARCH_HAS_CPUFREQ
780 select GENERIC_CLOCKEVENTS
781 select HAVE_S3C_RTC if RTC_CLASS
782 select HAVE_S3C2410_I2C if I2C
783 select HAVE_S3C2410_WATCHDOG if WATCHDOG
785 Samsung EXYNOS4 series based systems
794 select ARCH_USES_GETTIMEOFFSET
796 Support for the StrongARM based Digital DNARD machine, also known
797 as "Shark" (<http://www.shark-linux.de/shark.html>).
800 bool "Telechips TCC ARM926-based systems"
805 select GENERIC_CLOCKEVENTS
807 Support for Telechips TCC ARM926-based systems.
810 bool "ST-Ericsson U300 Series"
814 select HAVE_SCHED_CLOCK
818 select GENERIC_CLOCKEVENTS
822 Support for ST-Ericsson U300 series mobile platforms.
825 bool "ST-Ericsson U8500 Series"
828 select GENERIC_CLOCKEVENTS
830 select ARCH_REQUIRE_GPIOLIB
831 select ARCH_HAS_CPUFREQ
833 Support for ST-Ericsson's Ux500 architecture
836 bool "STMicroelectronics Nomadik"
841 select GENERIC_CLOCKEVENTS
842 select ARCH_REQUIRE_GPIOLIB
844 Support for the Nomadik platform by ST-Ericsson
848 select GENERIC_CLOCKEVENTS
849 select ARCH_REQUIRE_GPIOLIB
853 select GENERIC_ALLOCATOR
854 select ARCH_HAS_HOLES_MEMORYMODEL
856 Support for TI's DaVinci platform.
861 select ARCH_REQUIRE_GPIOLIB
862 select ARCH_HAS_CPUFREQ
863 select GENERIC_CLOCKEVENTS
864 select HAVE_SCHED_CLOCK
865 select ARCH_HAS_HOLES_MEMORYMODEL
867 Support for TI's OMAP platform (OMAP1/2/3/4).
872 select ARCH_REQUIRE_GPIOLIB
875 select GENERIC_CLOCKEVENTS
878 Support for ST's SPEAr platform (SPEAr3xx, SPEAr6xx and SPEAr13xx).
881 bool "VIA/WonderMedia 85xx"
884 select ARCH_HAS_CPUFREQ
885 select GENERIC_CLOCKEVENTS
886 select ARCH_REQUIRE_GPIOLIB
889 Support for VIA/WonderMedia VT8500/WM85xx System-on-Chip.
892 bool "Xilinx Zynq ARM Cortex A9 Platform"
895 select GENERIC_CLOCKEVENTS
900 Support for Xilinx Zynq ARM Cortex A9 Platform
905 # This is sorted alphabetically by mach-* pathname. However, plat-*
906 # Kconfigs may be included either alphabetically (according to the
907 # plat- suffix) or along side the corresponding mach-* source.
909 source "arch/arm/mach-at91/Kconfig"
911 source "arch/arm/mach-bcmring/Kconfig"
913 source "arch/arm/mach-clps711x/Kconfig"
915 source "arch/arm/mach-cns3xxx/Kconfig"
917 source "arch/arm/mach-davinci/Kconfig"
919 source "arch/arm/mach-dove/Kconfig"
921 source "arch/arm/mach-ep93xx/Kconfig"
923 source "arch/arm/mach-footbridge/Kconfig"
925 source "arch/arm/mach-gemini/Kconfig"
927 source "arch/arm/mach-h720x/Kconfig"
929 source "arch/arm/mach-integrator/Kconfig"
931 source "arch/arm/mach-iop32x/Kconfig"
933 source "arch/arm/mach-iop33x/Kconfig"
935 source "arch/arm/mach-iop13xx/Kconfig"
937 source "arch/arm/mach-ixp4xx/Kconfig"
939 source "arch/arm/mach-ixp2000/Kconfig"
941 source "arch/arm/mach-ixp23xx/Kconfig"
943 source "arch/arm/mach-kirkwood/Kconfig"
945 source "arch/arm/mach-ks8695/Kconfig"
947 source "arch/arm/mach-loki/Kconfig"
949 source "arch/arm/mach-lpc32xx/Kconfig"
951 source "arch/arm/mach-msm/Kconfig"
953 source "arch/arm/mach-mv78xx0/Kconfig"
955 source "arch/arm/plat-mxc/Kconfig"
957 source "arch/arm/mach-mxs/Kconfig"
959 source "arch/arm/mach-netx/Kconfig"
961 source "arch/arm/mach-nomadik/Kconfig"
962 source "arch/arm/plat-nomadik/Kconfig"
964 source "arch/arm/mach-nuc93x/Kconfig"
966 source "arch/arm/plat-omap/Kconfig"
968 source "arch/arm/mach-omap1/Kconfig"
970 source "arch/arm/mach-omap2/Kconfig"
972 source "arch/arm/mach-orion5x/Kconfig"
974 source "arch/arm/mach-pxa/Kconfig"
975 source "arch/arm/plat-pxa/Kconfig"
977 source "arch/arm/mach-mmp/Kconfig"
979 source "arch/arm/mach-realview/Kconfig"
981 source "arch/arm/mach-sa1100/Kconfig"
983 source "arch/arm/plat-samsung/Kconfig"
984 source "arch/arm/plat-s3c24xx/Kconfig"
985 source "arch/arm/plat-s5p/Kconfig"
987 source "arch/arm/plat-spear/Kconfig"
989 source "arch/arm/plat-tcc/Kconfig"
992 source "arch/arm/mach-s3c2400/Kconfig"
993 source "arch/arm/mach-s3c2410/Kconfig"
994 source "arch/arm/mach-s3c2412/Kconfig"
995 source "arch/arm/mach-s3c2416/Kconfig"
996 source "arch/arm/mach-s3c2440/Kconfig"
997 source "arch/arm/mach-s3c2443/Kconfig"
1001 source "arch/arm/mach-s3c64xx/Kconfig"
1004 source "arch/arm/mach-s5p64x0/Kconfig"
1006 source "arch/arm/mach-s5p6442/Kconfig"
1008 source "arch/arm/mach-s5pc100/Kconfig"
1010 source "arch/arm/mach-s5pv210/Kconfig"
1012 source "arch/arm/mach-exynos4/Kconfig"
1014 source "arch/arm/mach-shmobile/Kconfig"
1016 source "arch/arm/mach-tegra/Kconfig"
1018 source "arch/arm/mach-u300/Kconfig"
1020 source "arch/arm/mach-ux500/Kconfig"
1022 source "arch/arm/mach-versatile/Kconfig"
1024 source "arch/arm/mach-vexpress/Kconfig"
1025 source "arch/arm/plat-versatile/Kconfig"
1027 source "arch/arm/mach-vt8500/Kconfig"
1029 source "arch/arm/mach-w90x900/Kconfig"
1031 source "arch/arm/mach-zynq/Kconfig"
1033 # Definitions to make life easier
1039 select GENERIC_CLOCKEVENTS
1040 select HAVE_SCHED_CLOCK
1045 select HAVE_SCHED_CLOCK
1050 config PLAT_VERSATILE
1053 config ARM_TIMER_SP804
1057 source arch/arm/mm/Kconfig
1060 bool "Enable iWMMXt support"
1061 depends on CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_PJ4
1062 default y if PXA27x || PXA3xx || PXA95x || ARCH_MMP
1064 Enable support for iWMMXt context switching at run time if
1065 running on a CPU that supports it.
1067 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
1070 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
1074 depends on (CPU_V6 || CPU_V6K || CPU_V7 || XSCALE_PMU) && \
1075 (!ARCH_OMAP3 || OMAP3_EMU)
1079 config MULTI_IRQ_HANDLER
1082 Allow each machine to specify it's own IRQ handler at run time.
1085 source "arch/arm/Kconfig-nommu"
1088 config ARM_ERRATA_411920
1089 bool "ARM errata: Invalidation of the Instruction Cache operation can fail"
1090 depends on CPU_V6 || CPU_V6K
1092 Invalidation of the Instruction Cache operation can
1093 fail. This erratum is present in 1136 (before r1p4), 1156 and 1176.
1094 It does not affect the MPCore. This option enables the ARM Ltd.
1095 recommended workaround.
1097 config ARM_ERRATA_430973
1098 bool "ARM errata: Stale prediction on replaced interworking branch"
1101 This option enables the workaround for the 430973 Cortex-A8
1102 (r1p0..r1p2) erratum. If a code sequence containing an ARM/Thumb
1103 interworking branch is replaced with another code sequence at the
1104 same virtual address, whether due to self-modifying code or virtual
1105 to physical address re-mapping, Cortex-A8 does not recover from the
1106 stale interworking branch prediction. This results in Cortex-A8
1107 executing the new code sequence in the incorrect ARM or Thumb state.
1108 The workaround enables the BTB/BTAC operations by setting ACTLR.IBE
1109 and also flushes the branch target cache at every context switch.
1110 Note that setting specific bits in the ACTLR register may not be
1111 available in non-secure mode.
1113 config ARM_ERRATA_458693
1114 bool "ARM errata: Processor deadlock when a false hazard is created"
1117 This option enables the workaround for the 458693 Cortex-A8 (r2p0)
1118 erratum. For very specific sequences of memory operations, it is
1119 possible for a hazard condition intended for a cache line to instead
1120 be incorrectly associated with a different cache line. This false
1121 hazard might then cause a processor deadlock. The workaround enables
1122 the L1 caching of the NEON accesses and disables the PLD instruction
1123 in the ACTLR register. Note that setting specific bits in the ACTLR
1124 register may not be available in non-secure mode.
1126 config ARM_ERRATA_460075
1127 bool "ARM errata: Data written to the L2 cache can be overwritten with stale data"
1130 This option enables the workaround for the 460075 Cortex-A8 (r2p0)
1131 erratum. Any asynchronous access to the L2 cache may encounter a
1132 situation in which recent store transactions to the L2 cache are lost
1133 and overwritten with stale memory contents from external memory. The
1134 workaround disables the write-allocate mode for the L2 cache via the
1135 ACTLR register. Note that setting specific bits in the ACTLR register
1136 may not be available in non-secure mode.
1138 config ARM_ERRATA_742230
1139 bool "ARM errata: DMB operation may be faulty"
1140 depends on CPU_V7 && SMP
1142 This option enables the workaround for the 742230 Cortex-A9
1143 (r1p0..r2p2) erratum. Under rare circumstances, a DMB instruction
1144 between two write operations may not ensure the correct visibility
1145 ordering of the two writes. This workaround sets a specific bit in
1146 the diagnostic register of the Cortex-A9 which causes the DMB
1147 instruction to behave as a DSB, ensuring the correct behaviour of
1150 config ARM_ERRATA_742231
1151 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
1152 depends on CPU_V7 && SMP
1154 This option enables the workaround for the 742231 Cortex-A9
1155 (r2p0..r2p2) erratum. Under certain conditions, specific to the
1156 Cortex-A9 MPCore micro-architecture, two CPUs working in SMP mode,
1157 accessing some data located in the same cache line, may get corrupted
1158 data due to bad handling of the address hazard when the line gets
1159 replaced from one of the CPUs at the same time as another CPU is
1160 accessing it. This workaround sets specific bits in the diagnostic
1161 register of the Cortex-A9 which reduces the linefill issuing
1162 capabilities of the processor.
1164 config PL310_ERRATA_588369
1165 bool "Clean & Invalidate maintenance operations do not invalidate clean lines"
1166 depends on CACHE_L2X0
1168 The PL310 L2 cache controller implements three types of Clean &
1169 Invalidate maintenance operations: by Physical Address
1170 (offset 0x7F0), by Index/Way (0x7F8) and by Way (0x7FC).
1171 They are architecturally defined to behave as the execution of a
1172 clean operation followed immediately by an invalidate operation,
1173 both performing to the same memory location. This functionality
1174 is not correctly implemented in PL310 as clean lines are not
1175 invalidated as a result of these operations.
1177 config ARM_ERRATA_720789
1178 bool "ARM errata: TLBIASIDIS and TLBIMVAIS operations can broadcast a faulty ASID"
1179 depends on CPU_V7 && SMP
1181 This option enables the workaround for the 720789 Cortex-A9 (prior to
1182 r2p0) erratum. A faulty ASID can be sent to the other CPUs for the
1183 broadcasted CP15 TLB maintenance operations TLBIASIDIS and TLBIMVAIS.
1184 As a consequence of this erratum, some TLB entries which should be
1185 invalidated are not, resulting in an incoherency in the system page
1186 tables. The workaround changes the TLB flushing routines to invalidate
1187 entries regardless of the ASID.
1189 config PL310_ERRATA_727915
1190 bool "Background Clean & Invalidate by Way operation can cause data corruption"
1191 depends on CACHE_L2X0
1193 PL310 implements the Clean & Invalidate by Way L2 cache maintenance
1194 operation (offset 0x7FC). This operation runs in background so that
1195 PL310 can handle normal accesses while it is in progress. Under very
1196 rare circumstances, due to this erratum, write data can be lost when
1197 PL310 treats a cacheable write transaction during a Clean &
1198 Invalidate by Way operation.
1200 config ARM_ERRATA_743622
1201 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
1204 This option enables the workaround for the 743622 Cortex-A9
1205 (r2p0..r2p2) erratum. Under very rare conditions, a faulty
1206 optimisation in the Cortex-A9 Store Buffer may lead to data
1207 corruption. This workaround sets a specific bit in the diagnostic
1208 register of the Cortex-A9 which disables the Store Buffer
1209 optimisation, preventing the defect from occurring. This has no
1210 visible impact on the overall performance or power consumption of the
1213 config ARM_ERRATA_751472
1214 bool "ARM errata: Interrupted ICIALLUIS may prevent completion of broadcasted operation"
1215 depends on CPU_V7 && SMP
1217 This option enables the workaround for the 751472 Cortex-A9 (prior
1218 to r3p0) erratum. An interrupted ICIALLUIS operation may prevent the
1219 completion of a following broadcasted operation if the second
1220 operation is received by a CPU before the ICIALLUIS has completed,
1221 potentially leading to corrupted entries in the cache or TLB.
1223 config ARM_ERRATA_753970
1224 bool "ARM errata: cache sync operation may be faulty"
1225 depends on CACHE_PL310
1227 This option enables the workaround for the 753970 PL310 (r3p0) erratum.
1229 Under some condition the effect of cache sync operation on
1230 the store buffer still remains when the operation completes.
1231 This means that the store buffer is always asked to drain and
1232 this prevents it from merging any further writes. The workaround
1233 is to replace the normal offset of cache sync operation (0x730)
1234 by another offset targeting an unmapped PL310 register 0x740.
1235 This has the same effect as the cache sync operation: store buffer
1236 drain and waiting for all buffers empty.
1238 config ARM_ERRATA_754322
1239 bool "ARM errata: possible faulty MMU translations following an ASID switch"
1242 This option enables the workaround for the 754322 Cortex-A9 (r2p*,
1243 r3p*) erratum. A speculative memory access may cause a page table walk
1244 which starts prior to an ASID switch but completes afterwards. This
1245 can populate the micro-TLB with a stale entry which may be hit with
1246 the new ASID. This workaround places two dsb instructions in the mm
1247 switching code so that no page table walks can cross the ASID switch.
1249 config ARM_ERRATA_754327
1250 bool "ARM errata: no automatic Store Buffer drain"
1251 depends on CPU_V7 && SMP
1253 This option enables the workaround for the 754327 Cortex-A9 (prior to
1254 r2p0) erratum. The Store Buffer does not have any automatic draining
1255 mechanism and therefore a livelock may occur if an external agent
1256 continuously polls a memory location waiting to observe an update.
1257 This workaround defines cpu_relax() as smp_mb(), preventing correctly
1258 written polling loops from denying visibility of updates to memory.
1262 source "arch/arm/common/Kconfig"
1272 Find out whether you have ISA slots on your motherboard. ISA is the
1273 name of a bus system, i.e. the way the CPU talks to the other stuff
1274 inside your box. Other bus systems are PCI, EISA, MicroChannel
1275 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1276 newer boards don't support it. If you have ISA, say Y, otherwise N.
1278 # Select ISA DMA controller support
1283 # Select ISA DMA interface
1288 bool "PCI support" if MIGHT_HAVE_PCI
1290 Find out whether you have a PCI motherboard. PCI is the name of a
1291 bus system, i.e. the way the CPU talks to the other stuff inside
1292 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1293 VESA. If you have PCI, say Y, otherwise N.
1299 config PCI_NANOENGINE
1300 bool "BSE nanoEngine PCI support"
1301 depends on SA1100_NANOENGINE
1303 Enable PCI on the BSE nanoEngine board.
1308 # Select the host bridge type
1309 config PCI_HOST_VIA82C505
1311 depends on PCI && ARCH_SHARK
1314 config PCI_HOST_ITE8152
1316 depends on PCI && MACH_ARMCORE
1320 source "drivers/pci/Kconfig"
1322 source "drivers/pcmcia/Kconfig"
1326 menu "Kernel Features"
1328 source "kernel/time/Kconfig"
1331 bool "Symmetric Multi-Processing"
1332 depends on CPU_V6K || CPU_V7
1333 depends on GENERIC_CLOCKEVENTS
1334 depends on REALVIEW_EB_ARM11MP || REALVIEW_EB_A9MP || \
1335 MACH_REALVIEW_PB11MP || MACH_REALVIEW_PBX || ARCH_OMAP4 || \
1336 ARCH_EXYNOS4 || ARCH_TEGRA || ARCH_U8500 || ARCH_VEXPRESS_CA9X4 || \
1337 ARCH_MSM_SCORPIONMP || ARCH_SHMOBILE
1338 select USE_GENERIC_SMP_HELPERS
1339 select HAVE_ARM_SCU if !ARCH_MSM_SCORPIONMP
1341 This enables support for systems with more than one CPU. If you have
1342 a system with only one CPU, like most personal computers, say N. If
1343 you have a system with more than one CPU, say Y.
1345 If you say N here, the kernel will run on single and multiprocessor
1346 machines, but will use only one CPU of a multiprocessor machine. If
1347 you say Y here, the kernel will run on many, but not all, single
1348 processor machines. On a single processor machine, the kernel will
1349 run faster if you say N here.
1351 See also <file:Documentation/i386/IO-APIC.txt>,
1352 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
1353 <http://tldp.org/HOWTO/SMP-HOWTO.html>.
1355 If you don't know what to do here, say N.
1358 bool "Allow booting SMP kernel on uniprocessor systems (EXPERIMENTAL)"
1359 depends on EXPERIMENTAL
1360 depends on SMP && !XIP_KERNEL
1363 SMP kernels contain instructions which fail on non-SMP processors.
1364 Enabling this option allows the kernel to modify itself to make
1365 these instructions safe. Disabling it allows about 1K of space
1368 If you don't know what to do here, say Y.
1374 This option enables support for the ARM system coherency unit
1381 This options enables support for the ARM timer and watchdog unit
1384 prompt "Memory split"
1387 Select the desired split between kernel and user memory.
1389 If you are not absolutely sure what you are doing, leave this
1393 bool "3G/1G user/kernel split"
1395 bool "2G/2G user/kernel split"
1397 bool "1G/3G user/kernel split"
1402 default 0x40000000 if VMSPLIT_1G
1403 default 0x80000000 if VMSPLIT_2G
1407 int "Maximum number of CPUs (2-32)"
1413 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
1414 depends on SMP && HOTPLUG && EXPERIMENTAL
1415 depends on !ARCH_MSM
1417 Say Y here to experiment with turning CPUs off and on. CPUs
1418 can be controlled through /sys/devices/system/cpu.
1421 bool "Use local timer interrupts"
1424 select HAVE_ARM_TWD if (!ARCH_MSM_SCORPIONMP && !EXYNOS4_MCT)
1426 Enable support for local timers on SMP platforms, rather then the
1427 legacy IPI broadcast method. Local timers allows the system
1428 accounting to be spread across the timer interval, preventing a
1429 "thundering herd" at every timer tick.
1431 source kernel/Kconfig.preempt
1435 default 200 if ARCH_EBSA110 || ARCH_S3C2410 || ARCH_S5P64X0 || \
1436 ARCH_S5P6442 || ARCH_S5PV210 || ARCH_EXYNOS4
1437 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
1438 default AT91_TIMER_HZ if ARCH_AT91
1439 default SHMOBILE_TIMER_HZ if ARCH_SHMOBILE
1442 config THUMB2_KERNEL
1443 bool "Compile the kernel in Thumb-2 mode (EXPERIMENTAL)"
1444 depends on CPU_V7 && !CPU_V6 && !CPU_V6K && EXPERIMENTAL
1446 select ARM_ASM_UNIFIED
1448 By enabling this option, the kernel will be compiled in
1449 Thumb-2 mode. A compiler/assembler that understand the unified
1450 ARM-Thumb syntax is needed.
1454 config THUMB2_AVOID_R_ARM_THM_JUMP11
1455 bool "Work around buggy Thumb-2 short branch relocations in gas"
1456 depends on THUMB2_KERNEL && MODULES
1459 Various binutils versions can resolve Thumb-2 branches to
1460 locally-defined, preemptible global symbols as short-range "b.n"
1461 branch instructions.
1463 This is a problem, because there's no guarantee the final
1464 destination of the symbol, or any candidate locations for a
1465 trampoline, are within range of the branch. For this reason, the
1466 kernel does not support fixing up the R_ARM_THM_JUMP11 (102)
1467 relocation in modules at all, and it makes little sense to add
1470 The symptom is that the kernel fails with an "unsupported
1471 relocation" error when loading some modules.
1473 Until fixed tools are available, passing
1474 -fno-optimize-sibling-calls to gcc should prevent gcc generating
1475 code which hits this problem, at the cost of a bit of extra runtime
1476 stack usage in some cases.
1478 The problem is described in more detail at:
1479 https://bugs.launchpad.net/binutils-linaro/+bug/725126
1481 Only Thumb-2 kernels are affected.
1483 Unless you are sure your tools don't have this problem, say Y.
1485 config ARM_ASM_UNIFIED
1489 bool "Use the ARM EABI to compile the kernel"
1491 This option allows for the kernel to be compiled using the latest
1492 ARM ABI (aka EABI). This is only useful if you are using a user
1493 space environment that is also compiled with EABI.
1495 Since there are major incompatibilities between the legacy ABI and
1496 EABI, especially with regard to structure member alignment, this
1497 option also changes the kernel syscall calling convention to
1498 disambiguate both ABIs and allow for backward compatibility support
1499 (selected with CONFIG_OABI_COMPAT).
1501 To use this you need GCC version 4.0.0 or later.
1504 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
1505 depends on AEABI && EXPERIMENTAL && !THUMB2_KERNEL
1508 This option preserves the old syscall interface along with the
1509 new (ARM EABI) one. It also provides a compatibility layer to
1510 intercept syscalls that have structure arguments which layout
1511 in memory differs between the legacy ABI and the new ARM EABI
1512 (only for non "thumb" binaries). This option adds a tiny
1513 overhead to all syscalls and produces a slightly larger kernel.
1514 If you know you'll be using only pure EABI user space then you
1515 can say N here. If this option is not selected and you attempt
1516 to execute a legacy ABI binary then the result will be
1517 UNPREDICTABLE (in fact it can be predicted that it won't work
1518 at all). If in doubt say Y.
1520 config ARCH_HAS_HOLES_MEMORYMODEL
1523 config ARCH_SPARSEMEM_ENABLE
1526 config ARCH_SPARSEMEM_DEFAULT
1527 def_bool ARCH_SPARSEMEM_ENABLE
1529 config ARCH_SELECT_MEMORY_MODEL
1530 def_bool ARCH_SPARSEMEM_ENABLE
1533 bool "High Memory Support"
1536 The address space of ARM processors is only 4 Gigabytes large
1537 and it has to accommodate user address space, kernel address
1538 space as well as some memory mapped IO. That means that, if you
1539 have a large amount of physical memory and/or IO, not all of the
1540 memory can be "permanently mapped" by the kernel. The physical
1541 memory that is not permanently mapped is called "high memory".
1543 Depending on the selected kernel/user memory split, minimum
1544 vmalloc space and actual amount of RAM, you may not need this
1545 option which should result in a slightly faster kernel.
1550 bool "Allocate 2nd-level pagetables from highmem"
1553 config HW_PERF_EVENTS
1554 bool "Enable hardware performance counter support for perf events"
1555 depends on PERF_EVENTS && CPU_HAS_PMU
1558 Enable hardware performance counter support for perf events. If
1559 disabled, perf events will use software events only.
1563 config FORCE_MAX_ZONEORDER
1564 int "Maximum zone order" if ARCH_SHMOBILE
1565 range 11 64 if ARCH_SHMOBILE
1566 default "9" if SA1111
1569 The kernel memory allocator divides physically contiguous memory
1570 blocks into "zones", where each zone is a power of two number of
1571 pages. This option selects the largest power of two that the kernel
1572 keeps in the memory allocator. If you need to allocate very large
1573 blocks of physically contiguous memory, then you may need to
1574 increase this value.
1576 This config option is actually maximum order plus one. For example,
1577 a value of 11 means that the largest free memory block is 2^10 pages.
1580 bool "Timer and CPU usage LEDs"
1581 depends on ARCH_CDB89712 || ARCH_EBSA110 || \
1582 ARCH_EBSA285 || ARCH_INTEGRATOR || \
1583 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
1584 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
1585 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
1586 ARCH_AT91 || ARCH_DAVINCI || \
1587 ARCH_KS8695 || MACH_RD88F5182 || ARCH_REALVIEW
1589 If you say Y here, the LEDs on your machine will be used
1590 to provide useful information about your current system status.
1592 If you are compiling a kernel for a NetWinder or EBSA-285, you will
1593 be able to select which LEDs are active using the options below. If
1594 you are compiling a kernel for the EBSA-110 or the LART however, the
1595 red LED will simply flash regularly to indicate that the system is
1596 still functional. It is safe to say Y here if you have a CATS
1597 system, but the driver will do nothing.
1600 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
1601 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1602 || MACH_OMAP_PERSEUS2
1604 depends on !GENERIC_CLOCKEVENTS
1605 default y if ARCH_EBSA110
1607 If you say Y here, one of the system LEDs (the green one on the
1608 NetWinder, the amber one on the EBSA285, or the red one on the LART)
1609 will flash regularly to indicate that the system is still
1610 operational. This is mainly useful to kernel hackers who are
1611 debugging unstable kernels.
1613 The LART uses the same LED for both Timer LED and CPU usage LED
1614 functions. You may choose to use both, but the Timer LED function
1615 will overrule the CPU usage LED.
1618 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
1620 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1621 || MACH_OMAP_PERSEUS2
1624 If you say Y here, the red LED will be used to give a good real
1625 time indication of CPU usage, by lighting whenever the idle task
1626 is not currently executing.
1628 The LART uses the same LED for both Timer LED and CPU usage LED
1629 functions. You may choose to use both, but the Timer LED function
1630 will overrule the CPU usage LED.
1632 config ALIGNMENT_TRAP
1634 depends on CPU_CP15_MMU
1635 default y if !ARCH_EBSA110
1636 select HAVE_PROC_CPU if PROC_FS
1638 ARM processors cannot fetch/store information which is not
1639 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
1640 address divisible by 4. On 32-bit ARM processors, these non-aligned
1641 fetch/store instructions will be emulated in software if you say
1642 here, which has a severe performance impact. This is necessary for
1643 correct operation of some network protocols. With an IP-only
1644 configuration it is safe to say N, otherwise say Y.
1646 config UACCESS_WITH_MEMCPY
1647 bool "Use kernel mem{cpy,set}() for {copy_to,clear}_user() (EXPERIMENTAL)"
1648 depends on MMU && EXPERIMENTAL
1649 default y if CPU_FEROCEON
1651 Implement faster copy_to_user and clear_user methods for CPU
1652 cores where a 8-word STM instruction give significantly higher
1653 memory write throughput than a sequence of individual 32bit stores.
1655 A possible side effect is a slight increase in scheduling latency
1656 between threads sharing the same address space if they invoke
1657 such copy operations with large buffers.
1659 However, if the CPU data cache is using a write-allocate mode,
1660 this option is unlikely to provide any performance gain.
1664 prompt "Enable seccomp to safely compute untrusted bytecode"
1666 This kernel feature is useful for number crunching applications
1667 that may need to compute untrusted bytecode during their
1668 execution. By using pipes or other transports made available to
1669 the process as file descriptors supporting the read/write
1670 syscalls, it's possible to isolate those applications in
1671 their own address space using seccomp. Once seccomp is
1672 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1673 and the task is only allowed to execute a few safe syscalls
1674 defined by each seccomp mode.
1676 config CC_STACKPROTECTOR
1677 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1678 depends on EXPERIMENTAL
1680 This option turns on the -fstack-protector GCC feature. This
1681 feature puts, at the beginning of functions, a canary value on
1682 the stack just before the return address, and validates
1683 the value just before actually returning. Stack based buffer
1684 overflows (that need to overwrite this return address) now also
1685 overwrite the canary, which gets detected and the attack is then
1686 neutralized via a kernel panic.
1687 This feature requires gcc version 4.2 or above.
1689 config DEPRECATED_PARAM_STRUCT
1690 bool "Provide old way to pass kernel parameters"
1692 This was deprecated in 2001 and announced to live on for 5 years.
1693 Some old boot loaders still use this way.
1700 bool "Flattened Device Tree support"
1702 select OF_EARLY_FLATTREE
1704 Include support for flattened device tree machine descriptions.
1706 # Compressed boot loader in ROM. Yes, we really want to ask about
1707 # TEXT and BSS so we preserve their values in the config files.
1708 config ZBOOT_ROM_TEXT
1709 hex "Compressed ROM boot loader base address"
1712 The physical address at which the ROM-able zImage is to be
1713 placed in the target. Platforms which normally make use of
1714 ROM-able zImage formats normally set this to a suitable
1715 value in their defconfig file.
1717 If ZBOOT_ROM is not enabled, this has no effect.
1719 config ZBOOT_ROM_BSS
1720 hex "Compressed ROM boot loader BSS address"
1723 The base address of an area of read/write memory in the target
1724 for the ROM-able zImage which must be available while the
1725 decompressor is running. It must be large enough to hold the
1726 entire decompressed kernel plus an additional 128 KiB.
1727 Platforms which normally make use of ROM-able zImage formats
1728 normally set this to a suitable value in their defconfig file.
1730 If ZBOOT_ROM is not enabled, this has no effect.
1733 bool "Compressed boot loader in ROM/flash"
1734 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
1736 Say Y here if you intend to execute your compressed kernel image
1737 (zImage) directly from ROM or flash. If unsure, say N.
1739 config ZBOOT_ROM_MMCIF
1740 bool "Include MMCIF loader in zImage (EXPERIMENTAL)"
1741 depends on ZBOOT_ROM && ARCH_SH7372 && EXPERIMENTAL
1743 Say Y here to include experimental MMCIF loading code in the
1744 ROM-able zImage. With this enabled it is possible to write the
1745 the ROM-able zImage kernel image to an MMC card and boot the
1746 kernel straight from the reset vector. At reset the processor
1747 Mask ROM will load the first part of the the ROM-able zImage
1748 which in turn loads the rest the kernel image to RAM using the
1749 MMCIF hardware block.
1752 string "Default kernel command string"
1755 On some architectures (EBSA110 and CATS), there is currently no way
1756 for the boot loader to pass arguments to the kernel. For these
1757 architectures, you should supply some command-line options at build
1758 time by entering them here. As a minimum, you should specify the
1759 memory size and the root device (e.g., mem=64M root=/dev/nfs).
1762 prompt "Kernel command line type" if CMDLINE != ""
1763 default CMDLINE_FROM_BOOTLOADER
1765 config CMDLINE_FROM_BOOTLOADER
1766 bool "Use bootloader kernel arguments if available"
1768 Uses the command-line options passed by the boot loader. If
1769 the boot loader doesn't provide any, the default kernel command
1770 string provided in CMDLINE will be used.
1772 config CMDLINE_EXTEND
1773 bool "Extend bootloader kernel arguments"
1775 The command-line arguments provided by the boot loader will be
1776 appended to the default kernel command string.
1778 config CMDLINE_FORCE
1779 bool "Always use the default kernel command string"
1781 Always use the default kernel command string, even if the boot
1782 loader passes other arguments to the kernel.
1783 This is useful if you cannot or don't want to change the
1784 command-line options your boot loader passes to the kernel.
1788 bool "Kernel Execute-In-Place from ROM"
1789 depends on !ZBOOT_ROM
1791 Execute-In-Place allows the kernel to run from non-volatile storage
1792 directly addressable by the CPU, such as NOR flash. This saves RAM
1793 space since the text section of the kernel is not loaded from flash
1794 to RAM. Read-write sections, such as the data section and stack,
1795 are still copied to RAM. The XIP kernel is not compressed since
1796 it has to run directly from flash, so it will take more space to
1797 store it. The flash address used to link the kernel object files,
1798 and for storing it, is configuration dependent. Therefore, if you
1799 say Y here, you must know the proper physical address where to
1800 store the kernel image depending on your own flash memory usage.
1802 Also note that the make target becomes "make xipImage" rather than
1803 "make zImage" or "make Image". The final kernel binary to put in
1804 ROM memory will be arch/arm/boot/xipImage.
1808 config XIP_PHYS_ADDR
1809 hex "XIP Kernel Physical Location"
1810 depends on XIP_KERNEL
1811 default "0x00080000"
1813 This is the physical address in your flash memory the kernel will
1814 be linked for and stored to. This address is dependent on your
1818 bool "Kexec system call (EXPERIMENTAL)"
1819 depends on EXPERIMENTAL
1821 kexec is a system call that implements the ability to shutdown your
1822 current kernel, and to start another kernel. It is like a reboot
1823 but it is independent of the system firmware. And like a reboot
1824 you can start any kernel with it, not just Linux.
1826 It is an ongoing process to be certain the hardware in a machine
1827 is properly shutdown, so do not be surprised if this code does not
1828 initially work for you. It may help to enable device hotplugging
1832 bool "Export atags in procfs"
1836 Should the atags used to boot the kernel be exported in an "atags"
1837 file in procfs. Useful with kexec.
1840 bool "Build kdump crash kernel (EXPERIMENTAL)"
1841 depends on EXPERIMENTAL
1843 Generate crash dump after being started by kexec. This should
1844 be normally only set in special crash dump kernels which are
1845 loaded in the main kernel with kexec-tools into a specially
1846 reserved region and then later executed after a crash by
1847 kdump/kexec. The crash dump kernel must be compiled to a
1848 memory address not used by the main kernel
1850 For more details see Documentation/kdump/kdump.txt
1852 config AUTO_ZRELADDR
1853 bool "Auto calculation of the decompressed kernel image address"
1854 depends on !ZBOOT_ROM && !ARCH_U300
1856 ZRELADDR is the physical address where the decompressed kernel
1857 image will be placed. If AUTO_ZRELADDR is selected, the address
1858 will be determined at run-time by masking the current IP with
1859 0xf8000000. This assumes the zImage being placed in the first 128MB
1860 from start of memory.
1864 menu "CPU Power Management"
1868 source "drivers/cpufreq/Kconfig"
1871 tristate "CPUfreq driver for i.MX CPUs"
1872 depends on ARCH_MXC && CPU_FREQ
1874 This enables the CPUfreq driver for i.MX CPUs.
1876 config CPU_FREQ_SA1100
1879 config CPU_FREQ_SA1110
1882 config CPU_FREQ_INTEGRATOR
1883 tristate "CPUfreq driver for ARM Integrator CPUs"
1884 depends on ARCH_INTEGRATOR && CPU_FREQ
1887 This enables the CPUfreq driver for ARM Integrator CPUs.
1889 For details, take a look at <file:Documentation/cpu-freq>.
1895 depends on CPU_FREQ && ARCH_PXA && PXA25x
1897 select CPU_FREQ_DEFAULT_GOV_USERSPACE
1899 config CPU_FREQ_S3C64XX
1900 bool "CPUfreq support for Samsung S3C64XX CPUs"
1901 depends on CPU_FREQ && CPU_S3C6410
1906 Internal configuration node for common cpufreq on Samsung SoC
1908 config CPU_FREQ_S3C24XX
1909 bool "CPUfreq driver for Samsung S3C24XX series CPUs (EXPERIMENTAL)"
1910 depends on ARCH_S3C2410 && CPU_FREQ && EXPERIMENTAL
1913 This enables the CPUfreq driver for the Samsung S3C24XX family
1916 For details, take a look at <file:Documentation/cpu-freq>.
1920 config CPU_FREQ_S3C24XX_PLL
1921 bool "Support CPUfreq changing of PLL frequency (EXPERIMENTAL)"
1922 depends on CPU_FREQ_S3C24XX && EXPERIMENTAL
1924 Compile in support for changing the PLL frequency from the
1925 S3C24XX series CPUfreq driver. The PLL takes time to settle
1926 after a frequency change, so by default it is not enabled.
1928 This also means that the PLL tables for the selected CPU(s) will
1929 be built which may increase the size of the kernel image.
1931 config CPU_FREQ_S3C24XX_DEBUG
1932 bool "Debug CPUfreq Samsung driver core"
1933 depends on CPU_FREQ_S3C24XX
1935 Enable s3c_freq_dbg for the Samsung S3C CPUfreq core
1937 config CPU_FREQ_S3C24XX_IODEBUG
1938 bool "Debug CPUfreq Samsung driver IO timing"
1939 depends on CPU_FREQ_S3C24XX
1941 Enable s3c_freq_iodbg for the Samsung S3C CPUfreq core
1943 config CPU_FREQ_S3C24XX_DEBUGFS
1944 bool "Export debugfs for CPUFreq"
1945 depends on CPU_FREQ_S3C24XX && DEBUG_FS
1947 Export status information via debugfs.
1951 source "drivers/cpuidle/Kconfig"
1955 menu "Floating point emulation"
1957 comment "At least one emulation must be selected"
1960 bool "NWFPE math emulation"
1961 depends on (!AEABI || OABI_COMPAT) && !THUMB2_KERNEL
1963 Say Y to include the NWFPE floating point emulator in the kernel.
1964 This is necessary to run most binaries. Linux does not currently
1965 support floating point hardware so you need to say Y here even if
1966 your machine has an FPA or floating point co-processor podule.
1968 You may say N here if you are going to load the Acorn FPEmulator
1969 early in the bootup.
1972 bool "Support extended precision"
1973 depends on FPE_NWFPE
1975 Say Y to include 80-bit support in the kernel floating-point
1976 emulator. Otherwise, only 32 and 64-bit support is compiled in.
1977 Note that gcc does not generate 80-bit operations by default,
1978 so in most cases this option only enlarges the size of the
1979 floating point emulator without any good reason.
1981 You almost surely want to say N here.
1984 bool "FastFPE math emulation (EXPERIMENTAL)"
1985 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
1987 Say Y here to include the FAST floating point emulator in the kernel.
1988 This is an experimental much faster emulator which now also has full
1989 precision for the mantissa. It does not support any exceptions.
1990 It is very simple, and approximately 3-6 times faster than NWFPE.
1992 It should be sufficient for most programs. It may be not suitable
1993 for scientific calculations, but you have to check this for yourself.
1994 If you do not feel you need a faster FP emulation you should better
1998 bool "VFP-format floating point maths"
1999 depends on CPU_V6 || CPU_V6K || CPU_ARM926T || CPU_V7 || CPU_FEROCEON
2001 Say Y to include VFP support code in the kernel. This is needed
2002 if your hardware includes a VFP unit.
2004 Please see <file:Documentation/arm/VFP/release-notes.txt> for
2005 release notes and additional status information.
2007 Say N if your target does not have VFP hardware.
2015 bool "Advanced SIMD (NEON) Extension support"
2016 depends on VFPv3 && CPU_V7
2018 Say Y to include support code for NEON, the ARMv7 Advanced SIMD
2023 menu "Userspace binary formats"
2025 source "fs/Kconfig.binfmt"
2028 tristate "RISC OS personality"
2031 Say Y here to include the kernel code necessary if you want to run
2032 Acorn RISC OS/Arthur binaries under Linux. This code is still very
2033 experimental; if this sounds frightening, say N and sleep in peace.
2034 You can also say M here to compile this support as a module (which
2035 will be called arthur).
2039 menu "Power management options"
2041 source "kernel/power/Kconfig"
2043 config ARCH_SUSPEND_POSSIBLE
2044 depends on !ARCH_S5P64X0 && !ARCH_S5P6442
2045 depends on CPU_ARM920T || CPU_ARM926T || CPU_SA1100 || \
2046 CPU_V6 || CPU_V6K || CPU_V7 || CPU_XSC3 || CPU_XSCALE
2051 source "net/Kconfig"
2053 source "drivers/Kconfig"
2057 source "arch/arm/Kconfig.debug"
2059 source "security/Kconfig"
2061 source "crypto/Kconfig"
2063 source "lib/Kconfig"