5 select HAVE_DMA_API_DEBUG
9 select SYS_SUPPORTS_APM_EMULATION
10 select GENERIC_ATOMIC64 if (!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_V7))
28 select HAVE_C_RECORDMCOUNT
29 select HAVE_GENERIC_HARDIRQS
30 select HAVE_SPARSE_IRQ
32 The ARM series is a line of low-power-consumption RISC chip designs
33 licensed by ARM Ltd and targeted at embedded applications and
34 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
35 manufactured, but legacy ARM-based PC hardware remains popular in
36 Europe. There is an ARM Linux project with a web page at
37 <http://www.arm.linux.org.uk/>.
45 config SYS_SUPPORTS_APM_EMULATION
48 config HAVE_SCHED_CLOCK
54 config ARCH_USES_GETTIMEOFFSET
58 config GENERIC_CLOCKEVENTS
61 config GENERIC_CLOCKEVENTS_BROADCAST
63 depends on GENERIC_CLOCKEVENTS
72 select GENERIC_ALLOCATOR
83 The Extended Industry Standard Architecture (EISA) bus was
84 developed as an open alternative to the IBM MicroChannel bus.
86 The EISA bus provided some of the features of the IBM MicroChannel
87 bus while maintaining backward compatibility with cards made for
88 the older ISA bus. The EISA bus saw limited use between 1988 and
89 1995 when it was made obsolete by the PCI bus.
91 Say Y here if you are building a kernel for an EISA-based machine.
101 MicroChannel Architecture is found in some IBM PS/2 machines and
102 laptops. It is a bus system similar to PCI or ISA. See
103 <file:Documentation/mca.txt> (and especially the web page given
104 there) before attempting to build an MCA bus kernel.
106 config STACKTRACE_SUPPORT
110 config HAVE_LATENCYTOP_SUPPORT
115 config LOCKDEP_SUPPORT
119 config TRACE_IRQFLAGS_SUPPORT
123 config HARDIRQS_SW_RESEND
127 config GENERIC_IRQ_PROBE
131 config GENERIC_LOCKBREAK
134 depends on SMP && PREEMPT
136 config RWSEM_GENERIC_SPINLOCK
140 config RWSEM_XCHGADD_ALGORITHM
143 config ARCH_HAS_ILOG2_U32
146 config ARCH_HAS_ILOG2_U64
149 config ARCH_HAS_CPUFREQ
152 Internal node to signify that the ARCH has CPUFREQ support
153 and that the relevant menu configurations are displayed for
156 config ARCH_HAS_CPU_IDLE_WAIT
159 config GENERIC_HWEIGHT
163 config GENERIC_CALIBRATE_DELAY
167 config ARCH_MAY_HAVE_PC_FDC
173 config NEED_DMA_MAP_STATE
176 config GENERIC_ISA_DMA
187 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
188 default DRAM_BASE if REMAP_VECTORS_TO_RAM
191 The base address of exception vectors.
193 source "init/Kconfig"
195 source "kernel/Kconfig.freezer"
200 bool "MMU-based Paged Memory Management Support"
203 Select if you want MMU-based virtualised addressing space
204 support by paged memory management. If unsure, say 'Y'.
207 # The "ARM system type" choice list is ordered alphabetically by option
208 # text. Please add new entries in the option alphabetic order.
211 prompt "ARM system type"
212 default ARCH_VERSATILE
215 bool "Agilent AAEC-2000 based"
219 select ARCH_USES_GETTIMEOFFSET
221 This enables support for systems based on the Agilent AAEC-2000
223 config ARCH_INTEGRATOR
224 bool "ARM Ltd. Integrator family"
226 select ARCH_HAS_CPUFREQ
229 select GENERIC_CLOCKEVENTS
230 select PLAT_VERSATILE
232 Support for ARM's Integrator platform.
235 bool "ARM Ltd. RealView family"
238 select HAVE_SCHED_CLOCK
240 select GENERIC_CLOCKEVENTS
241 select ARCH_WANT_OPTIONAL_GPIOLIB
242 select PLAT_VERSATILE
243 select ARM_TIMER_SP804
244 select GPIO_PL061 if GPIOLIB
246 This enables support for ARM Ltd RealView boards.
248 config ARCH_VERSATILE
249 bool "ARM Ltd. Versatile family"
253 select HAVE_SCHED_CLOCK
255 select GENERIC_CLOCKEVENTS
256 select ARCH_WANT_OPTIONAL_GPIOLIB
257 select PLAT_VERSATILE
258 select ARM_TIMER_SP804
260 This enables support for ARM Ltd Versatile board.
263 bool "ARM Ltd. Versatile Express family"
264 select ARCH_WANT_OPTIONAL_GPIOLIB
266 select ARM_TIMER_SP804
268 select GENERIC_CLOCKEVENTS
270 select HAVE_SCHED_CLOCK
272 select PLAT_VERSATILE
274 This enables support for the ARM Ltd Versatile Express boards.
278 select ARCH_REQUIRE_GPIOLIB
281 This enables support for systems based on the Atmel AT91RM9200,
282 AT91SAM9 and AT91CAP9 processors.
285 bool "Broadcom BCMRING"
290 select GENERIC_CLOCKEVENTS
291 select ARCH_WANT_OPTIONAL_GPIOLIB
293 Support for Broadcom's BCMRing platform.
296 bool "Cirrus Logic CLPS711x/EP721x-based"
298 select ARCH_USES_GETTIMEOFFSET
300 Support for Cirrus Logic 711x/721x based boards.
303 bool "Cavium Networks CNS3XXX family"
305 select GENERIC_CLOCKEVENTS
307 select MIGHT_HAVE_PCI
308 select PCI_DOMAINS if PCI
310 Support for Cavium Networks CNS3XXX platform.
313 bool "Cortina Systems Gemini"
315 select ARCH_REQUIRE_GPIOLIB
316 select ARCH_USES_GETTIMEOFFSET
318 Support for the Cortina Systems Gemini family SoCs
325 select ARCH_USES_GETTIMEOFFSET
327 This is an evaluation board for the StrongARM processor available
328 from Digital. It has limited hardware on-board, including an
329 Ethernet interface, two PCMCIA sockets, two serial ports and a
338 select ARCH_REQUIRE_GPIOLIB
339 select ARCH_HAS_HOLES_MEMORYMODEL
340 select ARCH_USES_GETTIMEOFFSET
342 This enables support for the Cirrus EP93xx series of CPUs.
344 config ARCH_FOOTBRIDGE
348 select ARCH_USES_GETTIMEOFFSET
350 Support for systems based on the DC21285 companion chip
351 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
354 bool "Freescale MXC/iMX-based"
355 select GENERIC_CLOCKEVENTS
356 select ARCH_REQUIRE_GPIOLIB
359 Support for Freescale MXC/iMX-based family of processors
362 bool "Freescale MXS-based"
363 select GENERIC_CLOCKEVENTS
364 select ARCH_REQUIRE_GPIOLIB
367 Support for Freescale MXS-based family of processors
370 bool "Freescale STMP3xxx"
373 select ARCH_REQUIRE_GPIOLIB
374 select GENERIC_CLOCKEVENTS
375 select USB_ARCH_HAS_EHCI
377 Support for systems based on the Freescale 3xxx CPUs.
380 bool "Hilscher NetX based"
383 select GENERIC_CLOCKEVENTS
385 This enables support for systems based on the Hilscher NetX Soc
388 bool "Hynix HMS720x-based"
391 select ARCH_USES_GETTIMEOFFSET
393 This enables support for systems based on the Hynix HMS720x
401 select ARCH_SUPPORTS_MSI
404 Support for Intel's IOP13XX (XScale) family of processors.
412 select ARCH_REQUIRE_GPIOLIB
414 Support for Intel's 80219 and IOP32X (XScale) family of
423 select ARCH_REQUIRE_GPIOLIB
425 Support for Intel's IOP33X (XScale) family of processors.
432 select ARCH_USES_GETTIMEOFFSET
434 Support for Intel's IXP23xx (XScale) family of processors.
437 bool "IXP2400/2800-based"
441 select ARCH_USES_GETTIMEOFFSET
443 Support for Intel's IXP2400/2800 (XScale) family of processors.
450 select GENERIC_CLOCKEVENTS
451 select HAVE_SCHED_CLOCK
452 select MIGHT_HAVE_PCI
453 select DMABOUNCE if PCI
455 Support for Intel's IXP4XX (XScale) family of processors.
460 select ARCH_REQUIRE_GPIOLIB
461 select GENERIC_CLOCKEVENTS
464 Support for the Marvell Dove SoC 88AP510
467 bool "Marvell Kirkwood"
470 select ARCH_REQUIRE_GPIOLIB
471 select GENERIC_CLOCKEVENTS
474 Support for the following Marvell Kirkwood series SoCs:
475 88F6180, 88F6192 and 88F6281.
478 bool "Marvell Loki (88RC8480)"
480 select GENERIC_CLOCKEVENTS
483 Support for the Marvell Loki (88RC8480) SoC.
488 select ARCH_REQUIRE_GPIOLIB
491 select USB_ARCH_HAS_OHCI
494 select GENERIC_CLOCKEVENTS
496 Support for the NXP LPC32XX family of processors
499 bool "Marvell MV78xx0"
502 select ARCH_REQUIRE_GPIOLIB
503 select GENERIC_CLOCKEVENTS
506 Support for the following Marvell MV78xx0 series SoCs:
514 select ARCH_REQUIRE_GPIOLIB
515 select GENERIC_CLOCKEVENTS
518 Support for the following Marvell Orion 5x series SoCs:
519 Orion-1 (5181), Orion-VoIP (5181L), Orion-NAS (5182),
520 Orion-2 (5281), Orion-1-90 (6183).
523 bool "Marvell PXA168/910/MMP2"
525 select ARCH_REQUIRE_GPIOLIB
527 select GENERIC_CLOCKEVENTS
528 select HAVE_SCHED_CLOCK
533 Support for Marvell's PXA168/PXA910(MMP) and MMP2 processor line.
536 bool "Micrel/Kendin KS8695"
538 select ARCH_REQUIRE_GPIOLIB
539 select ARCH_USES_GETTIMEOFFSET
541 Support for Micrel/Kendin KS8695 "Centaur" (ARM922T) based
542 System-on-Chip devices.
545 bool "NetSilicon NS9xxx"
548 select GENERIC_CLOCKEVENTS
551 Say Y here if you intend to run this kernel on a NetSilicon NS9xxx
554 <http://www.digi.com/products/microprocessors/index.jsp>
557 bool "Nuvoton W90X900 CPU"
559 select ARCH_REQUIRE_GPIOLIB
561 select GENERIC_CLOCKEVENTS
563 Support for Nuvoton (Winbond logic dept.) ARM9 processor,
564 At present, the w90x900 has been renamed nuc900, regarding
565 the ARM series product line, you can login the following
566 link address to know more.
568 <http://www.nuvoton.com/hq/enu/ProductAndSales/ProductLines/
569 ConsumerElectronicsIC/ARMMicrocontroller/ARMMicrocontroller>
572 bool "Nuvoton NUC93X CPU"
576 Support for Nuvoton (Winbond logic dept.) NUC93X MCU,The NUC93X is a
577 low-power and high performance MPEG-4/JPEG multimedia controller chip.
583 select GENERIC_CLOCKEVENTS
586 select HAVE_SCHED_CLOCK
587 select ARCH_HAS_BARRIERS if CACHE_L2X0
588 select ARCH_HAS_CPUFREQ
590 This enables support for NVIDIA Tegra based systems (Tegra APX,
591 Tegra 6xx and Tegra 2 series).
594 bool "Philips Nexperia PNX4008 Mobile"
597 select ARCH_USES_GETTIMEOFFSET
599 This enables support for Philips PNX4008 mobile platform.
602 bool "PXA2xx/PXA3xx-based"
605 select ARCH_HAS_CPUFREQ
607 select ARCH_REQUIRE_GPIOLIB
608 select GENERIC_CLOCKEVENTS
609 select HAVE_SCHED_CLOCK
614 Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
619 select GENERIC_CLOCKEVENTS
620 select ARCH_REQUIRE_GPIOLIB
622 Support for Qualcomm MSM/QSD based systems. This runs on the
623 apps processor of the MSM/QSD and depends on a shared memory
624 interface to the modem processor which runs the baseband
625 stack and controls some vital subsystems
626 (clock and power control, etc).
629 bool "Renesas SH-Mobile / R-Mobile"
632 select GENERIC_CLOCKEVENTS
635 select MULTI_IRQ_HANDLER
637 Support for Renesas's SH-Mobile and R-Mobile ARM platforms.
644 select ARCH_MAY_HAVE_PC_FDC
645 select HAVE_PATA_PLATFORM
648 select ARCH_SPARSEMEM_ENABLE
649 select ARCH_USES_GETTIMEOFFSET
651 On the Acorn Risc-PC, Linux can support the internal IDE disk and
652 CD-ROM interface, serial and parallel port, and the floppy drive.
658 select ARCH_SPARSEMEM_ENABLE
660 select ARCH_HAS_CPUFREQ
662 select GENERIC_CLOCKEVENTS
664 select HAVE_SCHED_CLOCK
666 select ARCH_REQUIRE_GPIOLIB
668 Support for StrongARM 11x0 based boards.
671 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2416, S3C2440, S3C2442, S3C2443, S3C2450"
673 select ARCH_HAS_CPUFREQ
675 select ARCH_USES_GETTIMEOFFSET
676 select HAVE_S3C2410_I2C if I2C
678 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
679 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
680 the Samsung SMDK2410 development board (and derivatives).
682 Note, the S3C2416 and the S3C2450 are so close that they even share
683 the same SoC ID code. This means that there is no seperate machine
684 directory (no arch/arm/mach-s3c2450) as the S3C2416 was first.
687 bool "Samsung S3C64XX"
693 select ARCH_USES_GETTIMEOFFSET
694 select ARCH_HAS_CPUFREQ
695 select ARCH_REQUIRE_GPIOLIB
696 select SAMSUNG_CLKSRC
697 select SAMSUNG_IRQ_VIC_TIMER
698 select SAMSUNG_IRQ_UART
699 select S3C_GPIO_TRACK
700 select S3C_GPIO_PULL_UPDOWN
701 select S3C_GPIO_CFG_S3C24XX
702 select S3C_GPIO_CFG_S3C64XX
704 select USB_ARCH_HAS_OHCI
705 select SAMSUNG_GPIOLIB_4BIT
706 select HAVE_S3C2410_I2C if I2C
707 select HAVE_S3C2410_WATCHDOG if WATCHDOG
709 Samsung S3C64XX series based systems
712 bool "Samsung S5P6440 S5P6450"
716 select HAVE_S3C2410_WATCHDOG if WATCHDOG
717 select ARCH_USES_GETTIMEOFFSET
718 select HAVE_S3C2410_I2C if I2C
719 select HAVE_S3C_RTC if RTC_CLASS
721 Samsung S5P64X0 CPU based systems, such as the Samsung SMDK6440,
725 bool "Samsung S5P6442"
729 select ARCH_USES_GETTIMEOFFSET
730 select HAVE_S3C2410_WATCHDOG if WATCHDOG
732 Samsung S5P6442 CPU based systems
735 bool "Samsung S5PC100"
739 select ARM_L1_CACHE_SHIFT_6
740 select ARCH_USES_GETTIMEOFFSET
741 select HAVE_S3C2410_I2C if I2C
742 select HAVE_S3C_RTC if RTC_CLASS
743 select HAVE_S3C2410_WATCHDOG if WATCHDOG
745 Samsung S5PC100 series based systems
748 bool "Samsung S5PV210/S5PC110"
750 select ARCH_SPARSEMEM_ENABLE
753 select ARM_L1_CACHE_SHIFT_6
754 select ARCH_HAS_CPUFREQ
755 select ARCH_USES_GETTIMEOFFSET
756 select HAVE_S3C2410_I2C if I2C
757 select HAVE_S3C_RTC if RTC_CLASS
758 select HAVE_S3C2410_WATCHDOG if WATCHDOG
760 Samsung S5PV210/S5PC110 series based systems
763 bool "Samsung S5PV310/S5PC210"
765 select ARCH_SPARSEMEM_ENABLE
768 select ARCH_HAS_CPUFREQ
769 select GENERIC_CLOCKEVENTS
770 select HAVE_S3C_RTC if RTC_CLASS
771 select HAVE_S3C2410_I2C if I2C
772 select HAVE_S3C2410_WATCHDOG if WATCHDOG
774 Samsung S5PV310 series based systems
783 select ARCH_USES_GETTIMEOFFSET
785 Support for the StrongARM based Digital DNARD machine, also known
786 as "Shark" (<http://www.shark-linux.de/shark.html>).
789 bool "Telechips TCC ARM926-based systems"
793 select GENERIC_CLOCKEVENTS
795 Support for Telechips TCC ARM926-based systems.
800 select ARCH_SPARSEMEM_ENABLE if !LH7A40X_CONTIGMEM
801 select ARCH_USES_GETTIMEOFFSET
803 Say Y here for systems based on one of the Sharp LH7A40X
804 System on a Chip processors. These CPUs include an ARM922T
805 core with a wide array of integrated devices for
806 hand-held and low-power applications.
809 bool "ST-Ericsson U300 Series"
812 select HAVE_SCHED_CLOCK
816 select GENERIC_CLOCKEVENTS
820 Support for ST-Ericsson U300 series mobile platforms.
823 bool "ST-Ericsson U8500 Series"
826 select GENERIC_CLOCKEVENTS
828 select ARCH_REQUIRE_GPIOLIB
829 select ARCH_HAS_CPUFREQ
831 Support for ST-Ericsson's Ux500 architecture
834 bool "STMicroelectronics Nomadik"
839 select GENERIC_CLOCKEVENTS
840 select ARCH_REQUIRE_GPIOLIB
842 Support for the Nomadik platform by ST-Ericsson
846 select GENERIC_CLOCKEVENTS
847 select ARCH_REQUIRE_GPIOLIB
851 select GENERIC_ALLOCATOR
852 select ARCH_HAS_HOLES_MEMORYMODEL
854 Support for TI's DaVinci platform.
859 select ARCH_REQUIRE_GPIOLIB
860 select ARCH_HAS_CPUFREQ
861 select GENERIC_CLOCKEVENTS
862 select HAVE_SCHED_CLOCK
863 select ARCH_HAS_HOLES_MEMORYMODEL
865 Support for TI's OMAP platform (OMAP1/2/3/4).
870 select ARCH_REQUIRE_GPIOLIB
872 select GENERIC_CLOCKEVENTS
875 Support for ST's SPEAr platform (SPEAr3xx, SPEAr6xx and SPEAr13xx).
880 # This is sorted alphabetically by mach-* pathname. However, plat-*
881 # Kconfigs may be included either alphabetically (according to the
882 # plat- suffix) or along side the corresponding mach-* source.
884 source "arch/arm/mach-aaec2000/Kconfig"
886 source "arch/arm/mach-at91/Kconfig"
888 source "arch/arm/mach-bcmring/Kconfig"
890 source "arch/arm/mach-clps711x/Kconfig"
892 source "arch/arm/mach-cns3xxx/Kconfig"
894 source "arch/arm/mach-davinci/Kconfig"
896 source "arch/arm/mach-dove/Kconfig"
898 source "arch/arm/mach-ep93xx/Kconfig"
900 source "arch/arm/mach-footbridge/Kconfig"
902 source "arch/arm/mach-gemini/Kconfig"
904 source "arch/arm/mach-h720x/Kconfig"
906 source "arch/arm/mach-integrator/Kconfig"
908 source "arch/arm/mach-iop32x/Kconfig"
910 source "arch/arm/mach-iop33x/Kconfig"
912 source "arch/arm/mach-iop13xx/Kconfig"
914 source "arch/arm/mach-ixp4xx/Kconfig"
916 source "arch/arm/mach-ixp2000/Kconfig"
918 source "arch/arm/mach-ixp23xx/Kconfig"
920 source "arch/arm/mach-kirkwood/Kconfig"
922 source "arch/arm/mach-ks8695/Kconfig"
924 source "arch/arm/mach-lh7a40x/Kconfig"
926 source "arch/arm/mach-loki/Kconfig"
928 source "arch/arm/mach-lpc32xx/Kconfig"
930 source "arch/arm/mach-msm/Kconfig"
932 source "arch/arm/mach-mv78xx0/Kconfig"
934 source "arch/arm/plat-mxc/Kconfig"
936 source "arch/arm/mach-mxs/Kconfig"
938 source "arch/arm/mach-netx/Kconfig"
940 source "arch/arm/mach-nomadik/Kconfig"
941 source "arch/arm/plat-nomadik/Kconfig"
943 source "arch/arm/mach-ns9xxx/Kconfig"
945 source "arch/arm/mach-nuc93x/Kconfig"
947 source "arch/arm/plat-omap/Kconfig"
949 source "arch/arm/mach-omap1/Kconfig"
951 source "arch/arm/mach-omap2/Kconfig"
953 source "arch/arm/mach-orion5x/Kconfig"
955 source "arch/arm/mach-pxa/Kconfig"
956 source "arch/arm/plat-pxa/Kconfig"
958 source "arch/arm/mach-mmp/Kconfig"
960 source "arch/arm/mach-realview/Kconfig"
962 source "arch/arm/mach-sa1100/Kconfig"
964 source "arch/arm/plat-samsung/Kconfig"
965 source "arch/arm/plat-s3c24xx/Kconfig"
966 source "arch/arm/plat-s5p/Kconfig"
968 source "arch/arm/plat-spear/Kconfig"
970 source "arch/arm/plat-tcc/Kconfig"
973 source "arch/arm/mach-s3c2400/Kconfig"
974 source "arch/arm/mach-s3c2410/Kconfig"
975 source "arch/arm/mach-s3c2412/Kconfig"
976 source "arch/arm/mach-s3c2416/Kconfig"
977 source "arch/arm/mach-s3c2440/Kconfig"
978 source "arch/arm/mach-s3c2443/Kconfig"
982 source "arch/arm/mach-s3c64xx/Kconfig"
985 source "arch/arm/mach-s5p64x0/Kconfig"
987 source "arch/arm/mach-s5p6442/Kconfig"
989 source "arch/arm/mach-s5pc100/Kconfig"
991 source "arch/arm/mach-s5pv210/Kconfig"
993 source "arch/arm/mach-s5pv310/Kconfig"
995 source "arch/arm/mach-shmobile/Kconfig"
997 source "arch/arm/plat-stmp3xxx/Kconfig"
999 source "arch/arm/mach-tegra/Kconfig"
1001 source "arch/arm/mach-u300/Kconfig"
1003 source "arch/arm/mach-ux500/Kconfig"
1005 source "arch/arm/mach-versatile/Kconfig"
1007 source "arch/arm/mach-vexpress/Kconfig"
1009 source "arch/arm/mach-w90x900/Kconfig"
1011 # Definitions to make life easier
1017 select GENERIC_CLOCKEVENTS
1018 select HAVE_SCHED_CLOCK
1022 select HAVE_SCHED_CLOCK
1027 config PLAT_VERSATILE
1030 config ARM_TIMER_SP804
1033 source arch/arm/mm/Kconfig
1036 bool "Enable iWMMXt support"
1037 depends on CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_PJ4
1038 default y if PXA27x || PXA3xx || PXA95x || ARCH_MMP
1040 Enable support for iWMMXt context switching at run time if
1041 running on a CPU that supports it.
1043 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
1046 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
1050 depends on (CPU_V6 || CPU_V7 || XSCALE_PMU) && \
1051 (!ARCH_OMAP3 || OMAP3_EMU)
1055 config MULTI_IRQ_HANDLER
1058 Allow each machine to specify it's own IRQ handler at run time.
1061 source "arch/arm/Kconfig-nommu"
1064 config ARM_ERRATA_411920
1065 bool "ARM errata: Invalidation of the Instruction Cache operation can fail"
1068 Invalidation of the Instruction Cache operation can
1069 fail. This erratum is present in 1136 (before r1p4), 1156 and 1176.
1070 It does not affect the MPCore. This option enables the ARM Ltd.
1071 recommended workaround.
1073 config ARM_ERRATA_430973
1074 bool "ARM errata: Stale prediction on replaced interworking branch"
1077 This option enables the workaround for the 430973 Cortex-A8
1078 (r1p0..r1p2) erratum. If a code sequence containing an ARM/Thumb
1079 interworking branch is replaced with another code sequence at the
1080 same virtual address, whether due to self-modifying code or virtual
1081 to physical address re-mapping, Cortex-A8 does not recover from the
1082 stale interworking branch prediction. This results in Cortex-A8
1083 executing the new code sequence in the incorrect ARM or Thumb state.
1084 The workaround enables the BTB/BTAC operations by setting ACTLR.IBE
1085 and also flushes the branch target cache at every context switch.
1086 Note that setting specific bits in the ACTLR register may not be
1087 available in non-secure mode.
1089 config ARM_ERRATA_458693
1090 bool "ARM errata: Processor deadlock when a false hazard is created"
1093 This option enables the workaround for the 458693 Cortex-A8 (r2p0)
1094 erratum. For very specific sequences of memory operations, it is
1095 possible for a hazard condition intended for a cache line to instead
1096 be incorrectly associated with a different cache line. This false
1097 hazard might then cause a processor deadlock. The workaround enables
1098 the L1 caching of the NEON accesses and disables the PLD instruction
1099 in the ACTLR register. Note that setting specific bits in the ACTLR
1100 register may not be available in non-secure mode.
1102 config ARM_ERRATA_460075
1103 bool "ARM errata: Data written to the L2 cache can be overwritten with stale data"
1106 This option enables the workaround for the 460075 Cortex-A8 (r2p0)
1107 erratum. Any asynchronous access to the L2 cache may encounter a
1108 situation in which recent store transactions to the L2 cache are lost
1109 and overwritten with stale memory contents from external memory. The
1110 workaround disables the write-allocate mode for the L2 cache via the
1111 ACTLR register. Note that setting specific bits in the ACTLR register
1112 may not be available in non-secure mode.
1114 config ARM_ERRATA_742230
1115 bool "ARM errata: DMB operation may be faulty"
1116 depends on CPU_V7 && SMP
1118 This option enables the workaround for the 742230 Cortex-A9
1119 (r1p0..r2p2) erratum. Under rare circumstances, a DMB instruction
1120 between two write operations may not ensure the correct visibility
1121 ordering of the two writes. This workaround sets a specific bit in
1122 the diagnostic register of the Cortex-A9 which causes the DMB
1123 instruction to behave as a DSB, ensuring the correct behaviour of
1126 config ARM_ERRATA_742231
1127 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
1128 depends on CPU_V7 && SMP
1130 This option enables the workaround for the 742231 Cortex-A9
1131 (r2p0..r2p2) erratum. Under certain conditions, specific to the
1132 Cortex-A9 MPCore micro-architecture, two CPUs working in SMP mode,
1133 accessing some data located in the same cache line, may get corrupted
1134 data due to bad handling of the address hazard when the line gets
1135 replaced from one of the CPUs at the same time as another CPU is
1136 accessing it. This workaround sets specific bits in the diagnostic
1137 register of the Cortex-A9 which reduces the linefill issuing
1138 capabilities of the processor.
1140 config PL310_ERRATA_588369
1141 bool "Clean & Invalidate maintenance operations do not invalidate clean lines"
1142 depends on CACHE_L2X0
1144 The PL310 L2 cache controller implements three types of Clean &
1145 Invalidate maintenance operations: by Physical Address
1146 (offset 0x7F0), by Index/Way (0x7F8) and by Way (0x7FC).
1147 They are architecturally defined to behave as the execution of a
1148 clean operation followed immediately by an invalidate operation,
1149 both performing to the same memory location. This functionality
1150 is not correctly implemented in PL310 as clean lines are not
1151 invalidated as a result of these operations.
1153 config ARM_ERRATA_720789
1154 bool "ARM errata: TLBIASIDIS and TLBIMVAIS operations can broadcast a faulty ASID"
1155 depends on CPU_V7 && SMP
1157 This option enables the workaround for the 720789 Cortex-A9 (prior to
1158 r2p0) erratum. A faulty ASID can be sent to the other CPUs for the
1159 broadcasted CP15 TLB maintenance operations TLBIASIDIS and TLBIMVAIS.
1160 As a consequence of this erratum, some TLB entries which should be
1161 invalidated are not, resulting in an incoherency in the system page
1162 tables. The workaround changes the TLB flushing routines to invalidate
1163 entries regardless of the ASID.
1165 config ARM_ERRATA_743622
1166 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
1169 This option enables the workaround for the 743622 Cortex-A9
1170 (r2p0..r2p2) erratum. Under very rare conditions, a faulty
1171 optimisation in the Cortex-A9 Store Buffer may lead to data
1172 corruption. This workaround sets a specific bit in the diagnostic
1173 register of the Cortex-A9 which disables the Store Buffer
1174 optimisation, preventing the defect from occurring. This has no
1175 visible impact on the overall performance or power consumption of the
1178 config PL310_ERRATA_727915
1179 bool "Background Clean & Invalidate by Way operation can cause data corruption"
1180 depends on CACHE_L2X0
1182 PL310 implements the Clean & Invalidate by Way L2 cache maintenance
1183 operation (offset 0x7FC). This operation runs in background so that
1184 PL310 can handle normal accesses while it is in progress. Under very
1185 rare circumstances, due to this erratum, write data can be lost when
1186 PL310 treats a cacheable write transaction during a Clean &
1187 Invalidate by Way operation.
1190 source "arch/arm/common/Kconfig"
1200 Find out whether you have ISA slots on your motherboard. ISA is the
1201 name of a bus system, i.e. the way the CPU talks to the other stuff
1202 inside your box. Other bus systems are PCI, EISA, MicroChannel
1203 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1204 newer boards don't support it. If you have ISA, say Y, otherwise N.
1206 # Select ISA DMA controller support
1211 # Select ISA DMA interface
1216 bool "PCI support" if MIGHT_HAVE_PCI
1218 Find out whether you have a PCI motherboard. PCI is the name of a
1219 bus system, i.e. the way the CPU talks to the other stuff inside
1220 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1221 VESA. If you have PCI, say Y, otherwise N.
1227 config PCI_NANOENGINE
1228 bool "BSE nanoEngine PCI support"
1229 depends on SA1100_NANOENGINE
1231 Enable PCI on the BSE nanoEngine board.
1236 # Select the host bridge type
1237 config PCI_HOST_VIA82C505
1239 depends on PCI && ARCH_SHARK
1242 config PCI_HOST_ITE8152
1244 depends on PCI && MACH_ARMCORE
1248 source "drivers/pci/Kconfig"
1250 source "drivers/pcmcia/Kconfig"
1254 menu "Kernel Features"
1256 source "kernel/time/Kconfig"
1259 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
1260 depends on EXPERIMENTAL
1261 depends on GENERIC_CLOCKEVENTS
1262 depends on REALVIEW_EB_ARM11MP || REALVIEW_EB_A9MP || \
1263 MACH_REALVIEW_PB11MP || MACH_REALVIEW_PBX || ARCH_OMAP4 || \
1264 ARCH_S5PV310 || ARCH_TEGRA || ARCH_U8500 || ARCH_VEXPRESS_CA9X4 || \
1265 ARCH_MSM_SCORPIONMP || ARCH_SHMOBILE
1266 select USE_GENERIC_SMP_HELPERS
1267 select HAVE_ARM_SCU if !ARCH_MSM_SCORPIONMP
1269 This enables support for systems with more than one CPU. If you have
1270 a system with only one CPU, like most personal computers, say N. If
1271 you have a system with more than one CPU, say Y.
1273 If you say N here, the kernel will run on single and multiprocessor
1274 machines, but will use only one CPU of a multiprocessor machine. If
1275 you say Y here, the kernel will run on many, but not all, single
1276 processor machines. On a single processor machine, the kernel will
1277 run faster if you say N here.
1279 See also <file:Documentation/i386/IO-APIC.txt>,
1280 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
1281 <http://tldp.org/HOWTO/SMP-HOWTO.html>.
1283 If you don't know what to do here, say N.
1286 bool "Allow booting SMP kernel on uniprocessor systems (EXPERIMENTAL)"
1287 depends on EXPERIMENTAL
1288 depends on SMP && !XIP_KERNEL
1291 SMP kernels contain instructions which fail on non-SMP processors.
1292 Enabling this option allows the kernel to modify itself to make
1293 these instructions safe. Disabling it allows about 1K of space
1296 If you don't know what to do here, say Y.
1302 This option enables support for the ARM system coherency unit
1309 This options enables support for the ARM timer and watchdog unit
1312 prompt "Memory split"
1315 Select the desired split between kernel and user memory.
1317 If you are not absolutely sure what you are doing, leave this
1321 bool "3G/1G user/kernel split"
1323 bool "2G/2G user/kernel split"
1325 bool "1G/3G user/kernel split"
1330 default 0x40000000 if VMSPLIT_1G
1331 default 0x80000000 if VMSPLIT_2G
1335 int "Maximum number of CPUs (2-32)"
1341 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
1342 depends on SMP && HOTPLUG && EXPERIMENTAL
1343 depends on !ARCH_MSM
1345 Say Y here to experiment with turning CPUs off and on. CPUs
1346 can be controlled through /sys/devices/system/cpu.
1349 bool "Use local timer interrupts"
1352 select HAVE_ARM_TWD if !ARCH_MSM_SCORPIONMP
1354 Enable support for local timers on SMP platforms, rather then the
1355 legacy IPI broadcast method. Local timers allows the system
1356 accounting to be spread across the timer interval, preventing a
1357 "thundering herd" at every timer tick.
1359 source kernel/Kconfig.preempt
1363 default 200 if ARCH_EBSA110 || ARCH_S3C2410 || ARCH_S5P64X0 || \
1364 ARCH_S5P6442 || ARCH_S5PV210 || ARCH_S5PV310
1365 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
1366 default AT91_TIMER_HZ if ARCH_AT91
1367 default SHMOBILE_TIMER_HZ if ARCH_SHMOBILE
1370 config THUMB2_KERNEL
1371 bool "Compile the kernel in Thumb-2 mode (EXPERIMENTAL)"
1372 depends on CPU_V7 && !CPU_V6 && EXPERIMENTAL
1374 select ARM_ASM_UNIFIED
1376 By enabling this option, the kernel will be compiled in
1377 Thumb-2 mode. A compiler/assembler that understand the unified
1378 ARM-Thumb syntax is needed.
1382 config ARM_ASM_UNIFIED
1386 bool "Use the ARM EABI to compile the kernel"
1388 This option allows for the kernel to be compiled using the latest
1389 ARM ABI (aka EABI). This is only useful if you are using a user
1390 space environment that is also compiled with EABI.
1392 Since there are major incompatibilities between the legacy ABI and
1393 EABI, especially with regard to structure member alignment, this
1394 option also changes the kernel syscall calling convention to
1395 disambiguate both ABIs and allow for backward compatibility support
1396 (selected with CONFIG_OABI_COMPAT).
1398 To use this you need GCC version 4.0.0 or later.
1401 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
1402 depends on AEABI && EXPERIMENTAL
1405 This option preserves the old syscall interface along with the
1406 new (ARM EABI) one. It also provides a compatibility layer to
1407 intercept syscalls that have structure arguments which layout
1408 in memory differs between the legacy ABI and the new ARM EABI
1409 (only for non "thumb" binaries). This option adds a tiny
1410 overhead to all syscalls and produces a slightly larger kernel.
1411 If you know you'll be using only pure EABI user space then you
1412 can say N here. If this option is not selected and you attempt
1413 to execute a legacy ABI binary then the result will be
1414 UNPREDICTABLE (in fact it can be predicted that it won't work
1415 at all). If in doubt say Y.
1417 config ARCH_HAS_HOLES_MEMORYMODEL
1420 config ARCH_SPARSEMEM_ENABLE
1423 config ARCH_SPARSEMEM_DEFAULT
1424 def_bool ARCH_SPARSEMEM_ENABLE
1426 config ARCH_SELECT_MEMORY_MODEL
1427 def_bool ARCH_SPARSEMEM_ENABLE
1430 bool "High Memory Support (EXPERIMENTAL)"
1431 depends on MMU && EXPERIMENTAL
1433 The address space of ARM processors is only 4 Gigabytes large
1434 and it has to accommodate user address space, kernel address
1435 space as well as some memory mapped IO. That means that, if you
1436 have a large amount of physical memory and/or IO, not all of the
1437 memory can be "permanently mapped" by the kernel. The physical
1438 memory that is not permanently mapped is called "high memory".
1440 Depending on the selected kernel/user memory split, minimum
1441 vmalloc space and actual amount of RAM, you may not need this
1442 option which should result in a slightly faster kernel.
1447 bool "Allocate 2nd-level pagetables from highmem"
1449 depends on !OUTER_CACHE
1451 config HW_PERF_EVENTS
1452 bool "Enable hardware performance counter support for perf events"
1453 depends on PERF_EVENTS && CPU_HAS_PMU
1456 Enable hardware performance counter support for perf events. If
1457 disabled, perf events will use software events only.
1461 config FORCE_MAX_ZONEORDER
1462 int "Maximum zone order" if ARCH_SHMOBILE
1463 range 11 64 if ARCH_SHMOBILE
1464 default "9" if SA1111
1467 The kernel memory allocator divides physically contiguous memory
1468 blocks into "zones", where each zone is a power of two number of
1469 pages. This option selects the largest power of two that the kernel
1470 keeps in the memory allocator. If you need to allocate very large
1471 blocks of physically contiguous memory, then you may need to
1472 increase this value.
1474 This config option is actually maximum order plus one. For example,
1475 a value of 11 means that the largest free memory block is 2^10 pages.
1478 bool "Timer and CPU usage LEDs"
1479 depends on ARCH_CDB89712 || ARCH_EBSA110 || \
1480 ARCH_EBSA285 || ARCH_INTEGRATOR || \
1481 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
1482 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
1483 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
1484 ARCH_AT91 || ARCH_DAVINCI || \
1485 ARCH_KS8695 || MACH_RD88F5182 || ARCH_REALVIEW
1487 If you say Y here, the LEDs on your machine will be used
1488 to provide useful information about your current system status.
1490 If you are compiling a kernel for a NetWinder or EBSA-285, you will
1491 be able to select which LEDs are active using the options below. If
1492 you are compiling a kernel for the EBSA-110 or the LART however, the
1493 red LED will simply flash regularly to indicate that the system is
1494 still functional. It is safe to say Y here if you have a CATS
1495 system, but the driver will do nothing.
1498 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
1499 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1500 || MACH_OMAP_PERSEUS2
1502 depends on !GENERIC_CLOCKEVENTS
1503 default y if ARCH_EBSA110
1505 If you say Y here, one of the system LEDs (the green one on the
1506 NetWinder, the amber one on the EBSA285, or the red one on the LART)
1507 will flash regularly to indicate that the system is still
1508 operational. This is mainly useful to kernel hackers who are
1509 debugging unstable kernels.
1511 The LART uses the same LED for both Timer LED and CPU usage LED
1512 functions. You may choose to use both, but the Timer LED function
1513 will overrule the CPU usage LED.
1516 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
1518 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1519 || MACH_OMAP_PERSEUS2
1522 If you say Y here, the red LED will be used to give a good real
1523 time indication of CPU usage, by lighting whenever the idle task
1524 is not currently executing.
1526 The LART uses the same LED for both Timer LED and CPU usage LED
1527 functions. You may choose to use both, but the Timer LED function
1528 will overrule the CPU usage LED.
1530 config ALIGNMENT_TRAP
1532 depends on CPU_CP15_MMU
1533 default y if !ARCH_EBSA110
1534 select HAVE_PROC_CPU if PROC_FS
1536 ARM processors cannot fetch/store information which is not
1537 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
1538 address divisible by 4. On 32-bit ARM processors, these non-aligned
1539 fetch/store instructions will be emulated in software if you say
1540 here, which has a severe performance impact. This is necessary for
1541 correct operation of some network protocols. With an IP-only
1542 configuration it is safe to say N, otherwise say Y.
1544 config UACCESS_WITH_MEMCPY
1545 bool "Use kernel mem{cpy,set}() for {copy_to,clear}_user() (EXPERIMENTAL)"
1546 depends on MMU && EXPERIMENTAL
1547 default y if CPU_FEROCEON
1549 Implement faster copy_to_user and clear_user methods for CPU
1550 cores where a 8-word STM instruction give significantly higher
1551 memory write throughput than a sequence of individual 32bit stores.
1553 A possible side effect is a slight increase in scheduling latency
1554 between threads sharing the same address space if they invoke
1555 such copy operations with large buffers.
1557 However, if the CPU data cache is using a write-allocate mode,
1558 this option is unlikely to provide any performance gain.
1562 prompt "Enable seccomp to safely compute untrusted bytecode"
1564 This kernel feature is useful for number crunching applications
1565 that may need to compute untrusted bytecode during their
1566 execution. By using pipes or other transports made available to
1567 the process as file descriptors supporting the read/write
1568 syscalls, it's possible to isolate those applications in
1569 their own address space using seccomp. Once seccomp is
1570 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1571 and the task is only allowed to execute a few safe syscalls
1572 defined by each seccomp mode.
1574 config CC_STACKPROTECTOR
1575 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1576 depends on EXPERIMENTAL
1578 This option turns on the -fstack-protector GCC feature. This
1579 feature puts, at the beginning of functions, a canary value on
1580 the stack just before the return address, and validates
1581 the value just before actually returning. Stack based buffer
1582 overflows (that need to overwrite this return address) now also
1583 overwrite the canary, which gets detected and the attack is then
1584 neutralized via a kernel panic.
1585 This feature requires gcc version 4.2 or above.
1587 config DEPRECATED_PARAM_STRUCT
1588 bool "Provide old way to pass kernel parameters"
1590 This was deprecated in 2001 and announced to live on for 5 years.
1591 Some old boot loaders still use this way.
1597 # Compressed boot loader in ROM. Yes, we really want to ask about
1598 # TEXT and BSS so we preserve their values in the config files.
1599 config ZBOOT_ROM_TEXT
1600 hex "Compressed ROM boot loader base address"
1603 The physical address at which the ROM-able zImage is to be
1604 placed in the target. Platforms which normally make use of
1605 ROM-able zImage formats normally set this to a suitable
1606 value in their defconfig file.
1608 If ZBOOT_ROM is not enabled, this has no effect.
1610 config ZBOOT_ROM_BSS
1611 hex "Compressed ROM boot loader BSS address"
1614 The base address of an area of read/write memory in the target
1615 for the ROM-able zImage which must be available while the
1616 decompressor is running. It must be large enough to hold the
1617 entire decompressed kernel plus an additional 128 KiB.
1618 Platforms which normally make use of ROM-able zImage formats
1619 normally set this to a suitable value in their defconfig file.
1621 If ZBOOT_ROM is not enabled, this has no effect.
1624 bool "Compressed boot loader in ROM/flash"
1625 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
1627 Say Y here if you intend to execute your compressed kernel image
1628 (zImage) directly from ROM or flash. If unsure, say N.
1631 string "Default kernel command string"
1634 On some architectures (EBSA110 and CATS), there is currently no way
1635 for the boot loader to pass arguments to the kernel. For these
1636 architectures, you should supply some command-line options at build
1637 time by entering them here. As a minimum, you should specify the
1638 memory size and the root device (e.g., mem=64M root=/dev/nfs).
1640 config CMDLINE_FORCE
1641 bool "Always use the default kernel command string"
1642 depends on CMDLINE != ""
1644 Always use the default kernel command string, even if the boot
1645 loader passes other arguments to the kernel.
1646 This is useful if you cannot or don't want to change the
1647 command-line options your boot loader passes to the kernel.
1652 bool "Kernel Execute-In-Place from ROM"
1653 depends on !ZBOOT_ROM
1655 Execute-In-Place allows the kernel to run from non-volatile storage
1656 directly addressable by the CPU, such as NOR flash. This saves RAM
1657 space since the text section of the kernel is not loaded from flash
1658 to RAM. Read-write sections, such as the data section and stack,
1659 are still copied to RAM. The XIP kernel is not compressed since
1660 it has to run directly from flash, so it will take more space to
1661 store it. The flash address used to link the kernel object files,
1662 and for storing it, is configuration dependent. Therefore, if you
1663 say Y here, you must know the proper physical address where to
1664 store the kernel image depending on your own flash memory usage.
1666 Also note that the make target becomes "make xipImage" rather than
1667 "make zImage" or "make Image". The final kernel binary to put in
1668 ROM memory will be arch/arm/boot/xipImage.
1672 config XIP_PHYS_ADDR
1673 hex "XIP Kernel Physical Location"
1674 depends on XIP_KERNEL
1675 default "0x00080000"
1677 This is the physical address in your flash memory the kernel will
1678 be linked for and stored to. This address is dependent on your
1682 bool "Kexec system call (EXPERIMENTAL)"
1683 depends on EXPERIMENTAL
1685 kexec is a system call that implements the ability to shutdown your
1686 current kernel, and to start another kernel. It is like a reboot
1687 but it is independent of the system firmware. And like a reboot
1688 you can start any kernel with it, not just Linux.
1690 It is an ongoing process to be certain the hardware in a machine
1691 is properly shutdown, so do not be surprised if this code does not
1692 initially work for you. It may help to enable device hotplugging
1696 bool "Export atags in procfs"
1700 Should the atags used to boot the kernel be exported in an "atags"
1701 file in procfs. Useful with kexec.
1704 bool "Build kdump crash kernel (EXPERIMENTAL)"
1705 depends on EXPERIMENTAL
1707 Generate crash dump after being started by kexec. This should
1708 be normally only set in special crash dump kernels which are
1709 loaded in the main kernel with kexec-tools into a specially
1710 reserved region and then later executed after a crash by
1711 kdump/kexec. The crash dump kernel must be compiled to a
1712 memory address not used by the main kernel
1714 For more details see Documentation/kdump/kdump.txt
1716 config AUTO_ZRELADDR
1717 bool "Auto calculation of the decompressed kernel image address"
1718 depends on !ZBOOT_ROM && !ARCH_U300
1720 ZRELADDR is the physical address where the decompressed kernel
1721 image will be placed. If AUTO_ZRELADDR is selected, the address
1722 will be determined at run-time by masking the current IP with
1723 0xf8000000. This assumes the zImage being placed in the first 128MB
1724 from start of memory.
1728 menu "CPU Power Management"
1732 source "drivers/cpufreq/Kconfig"
1735 tristate "CPUfreq driver for i.MX CPUs"
1736 depends on ARCH_MXC && CPU_FREQ
1738 This enables the CPUfreq driver for i.MX CPUs.
1740 config CPU_FREQ_SA1100
1743 config CPU_FREQ_SA1110
1746 config CPU_FREQ_INTEGRATOR
1747 tristate "CPUfreq driver for ARM Integrator CPUs"
1748 depends on ARCH_INTEGRATOR && CPU_FREQ
1751 This enables the CPUfreq driver for ARM Integrator CPUs.
1753 For details, take a look at <file:Documentation/cpu-freq>.
1759 depends on CPU_FREQ && ARCH_PXA && PXA25x
1761 select CPU_FREQ_DEFAULT_GOV_USERSPACE
1763 config CPU_FREQ_S3C64XX
1764 bool "CPUfreq support for Samsung S3C64XX CPUs"
1765 depends on CPU_FREQ && CPU_S3C6410
1770 Internal configuration node for common cpufreq on Samsung SoC
1772 config CPU_FREQ_S3C24XX
1773 bool "CPUfreq driver for Samsung S3C24XX series CPUs (EXPERIMENTAL)"
1774 depends on ARCH_S3C2410 && CPU_FREQ && EXPERIMENTAL
1777 This enables the CPUfreq driver for the Samsung S3C24XX family
1780 For details, take a look at <file:Documentation/cpu-freq>.
1784 config CPU_FREQ_S3C24XX_PLL
1785 bool "Support CPUfreq changing of PLL frequency (EXPERIMENTAL)"
1786 depends on CPU_FREQ_S3C24XX && EXPERIMENTAL
1788 Compile in support for changing the PLL frequency from the
1789 S3C24XX series CPUfreq driver. The PLL takes time to settle
1790 after a frequency change, so by default it is not enabled.
1792 This also means that the PLL tables for the selected CPU(s) will
1793 be built which may increase the size of the kernel image.
1795 config CPU_FREQ_S3C24XX_DEBUG
1796 bool "Debug CPUfreq Samsung driver core"
1797 depends on CPU_FREQ_S3C24XX
1799 Enable s3c_freq_dbg for the Samsung S3C CPUfreq core
1801 config CPU_FREQ_S3C24XX_IODEBUG
1802 bool "Debug CPUfreq Samsung driver IO timing"
1803 depends on CPU_FREQ_S3C24XX
1805 Enable s3c_freq_iodbg for the Samsung S3C CPUfreq core
1807 config CPU_FREQ_S3C24XX_DEBUGFS
1808 bool "Export debugfs for CPUFreq"
1809 depends on CPU_FREQ_S3C24XX && DEBUG_FS
1811 Export status information via debugfs.
1815 source "drivers/cpuidle/Kconfig"
1819 menu "Floating point emulation"
1821 comment "At least one emulation must be selected"
1824 bool "NWFPE math emulation"
1825 depends on (!AEABI || OABI_COMPAT) && !THUMB2_KERNEL
1827 Say Y to include the NWFPE floating point emulator in the kernel.
1828 This is necessary to run most binaries. Linux does not currently
1829 support floating point hardware so you need to say Y here even if
1830 your machine has an FPA or floating point co-processor podule.
1832 You may say N here if you are going to load the Acorn FPEmulator
1833 early in the bootup.
1836 bool "Support extended precision"
1837 depends on FPE_NWFPE
1839 Say Y to include 80-bit support in the kernel floating-point
1840 emulator. Otherwise, only 32 and 64-bit support is compiled in.
1841 Note that gcc does not generate 80-bit operations by default,
1842 so in most cases this option only enlarges the size of the
1843 floating point emulator without any good reason.
1845 You almost surely want to say N here.
1848 bool "FastFPE math emulation (EXPERIMENTAL)"
1849 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
1851 Say Y here to include the FAST floating point emulator in the kernel.
1852 This is an experimental much faster emulator which now also has full
1853 precision for the mantissa. It does not support any exceptions.
1854 It is very simple, and approximately 3-6 times faster than NWFPE.
1856 It should be sufficient for most programs. It may be not suitable
1857 for scientific calculations, but you have to check this for yourself.
1858 If you do not feel you need a faster FP emulation you should better
1862 bool "VFP-format floating point maths"
1863 depends on CPU_V6 || CPU_ARM926T || CPU_V7 || CPU_FEROCEON
1865 Say Y to include VFP support code in the kernel. This is needed
1866 if your hardware includes a VFP unit.
1868 Please see <file:Documentation/arm/VFP/release-notes.txt> for
1869 release notes and additional status information.
1871 Say N if your target does not have VFP hardware.
1879 bool "Advanced SIMD (NEON) Extension support"
1880 depends on VFPv3 && CPU_V7
1882 Say Y to include support code for NEON, the ARMv7 Advanced SIMD
1887 menu "Userspace binary formats"
1889 source "fs/Kconfig.binfmt"
1892 tristate "RISC OS personality"
1895 Say Y here to include the kernel code necessary if you want to run
1896 Acorn RISC OS/Arthur binaries under Linux. This code is still very
1897 experimental; if this sounds frightening, say N and sleep in peace.
1898 You can also say M here to compile this support as a module (which
1899 will be called arthur).
1903 menu "Power management options"
1905 source "kernel/power/Kconfig"
1907 config ARCH_SUSPEND_POSSIBLE
1912 source "net/Kconfig"
1914 source "drivers/Kconfig"
1918 source "arch/arm/Kconfig.debug"
1920 source "security/Kconfig"
1922 source "crypto/Kconfig"
1924 source "lib/Kconfig"