5 select HAVE_DMA_API_DEBUG
9 select SYS_SUPPORTS_APM_EMULATION
10 select GENERIC_ATOMIC64 if (CPU_V6 || !CPU_32v6K || !AEABI)
11 select HAVE_OPROFILE if (HAVE_PERF_EVENTS)
13 select HAVE_KPROBES if !XIP_KERNEL
14 select HAVE_KRETPROBES if (HAVE_KPROBES)
15 select HAVE_FUNCTION_TRACER if (!XIP_KERNEL)
16 select HAVE_FTRACE_MCOUNT_RECORD if (!XIP_KERNEL)
17 select HAVE_DYNAMIC_FTRACE if (!XIP_KERNEL)
18 select HAVE_FUNCTION_GRAPH_TRACER if (!THUMB2_KERNEL)
19 select HAVE_GENERIC_DMA_COHERENT
20 select HAVE_KERNEL_GZIP
21 select HAVE_KERNEL_LZO
22 select HAVE_KERNEL_LZMA
24 select HAVE_PERF_EVENTS
25 select PERF_USE_VMALLOC
26 select HAVE_REGS_AND_STACK_ACCESS_API
27 select HAVE_HW_BREAKPOINT if (PERF_EVENTS && (CPU_V6 || CPU_V6K || CPU_V7))
28 select HAVE_C_RECORDMCOUNT
29 select HAVE_GENERIC_HARDIRQS
30 select HAVE_SPARSE_IRQ
31 select GENERIC_IRQ_SHOW
33 The ARM series is a line of low-power-consumption RISC chip designs
34 licensed by ARM Ltd and targeted at embedded applications and
35 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
36 manufactured, but legacy ARM-based PC hardware remains popular in
37 Europe. There is an ARM Linux project with a web page at
38 <http://www.arm.linux.org.uk/>.
40 config ARM_HAS_SG_CHAIN
49 config SYS_SUPPORTS_APM_EMULATION
52 config HAVE_SCHED_CLOCK
58 config ARCH_USES_GETTIMEOFFSET
62 config GENERIC_CLOCKEVENTS
65 config GENERIC_CLOCKEVENTS_BROADCAST
67 depends on GENERIC_CLOCKEVENTS
76 select GENERIC_ALLOCATOR
87 The Extended Industry Standard Architecture (EISA) bus was
88 developed as an open alternative to the IBM MicroChannel bus.
90 The EISA bus provided some of the features of the IBM MicroChannel
91 bus while maintaining backward compatibility with cards made for
92 the older ISA bus. The EISA bus saw limited use between 1988 and
93 1995 when it was made obsolete by the PCI bus.
95 Say Y here if you are building a kernel for an EISA-based machine.
105 MicroChannel Architecture is found in some IBM PS/2 machines and
106 laptops. It is a bus system similar to PCI or ISA. See
107 <file:Documentation/mca.txt> (and especially the web page given
108 there) before attempting to build an MCA bus kernel.
110 config STACKTRACE_SUPPORT
114 config HAVE_LATENCYTOP_SUPPORT
119 config LOCKDEP_SUPPORT
123 config TRACE_IRQFLAGS_SUPPORT
127 config HARDIRQS_SW_RESEND
131 config GENERIC_IRQ_PROBE
135 config GENERIC_LOCKBREAK
138 depends on SMP && PREEMPT
140 config RWSEM_GENERIC_SPINLOCK
144 config RWSEM_XCHGADD_ALGORITHM
147 config ARCH_HAS_ILOG2_U32
150 config ARCH_HAS_ILOG2_U64
153 config ARCH_HAS_CPUFREQ
156 Internal node to signify that the ARCH has CPUFREQ support
157 and that the relevant menu configurations are displayed for
160 config ARCH_HAS_CPU_IDLE_WAIT
163 config GENERIC_HWEIGHT
167 config GENERIC_CALIBRATE_DELAY
171 config ARCH_MAY_HAVE_PC_FDC
177 config NEED_DMA_MAP_STATE
180 config GENERIC_ISA_DMA
191 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
192 default DRAM_BASE if REMAP_VECTORS_TO_RAM
195 The base address of exception vectors.
197 config ARM_PATCH_PHYS_VIRT
198 bool "Patch physical to virtual translations at runtime (EXPERIMENTAL)"
199 depends on EXPERIMENTAL
200 depends on !XIP_KERNEL && MMU
201 depends on !ARCH_REALVIEW || !SPARSEMEM
203 Patch phys-to-virt and virt-to-phys translation functions at
204 boot and module load time according to the position of the
205 kernel in system memory.
207 This can only be used with non-XIP MMU kernels where the base
208 of physical memory is at a 16MB boundary, or theoretically 64K
209 for the MSM machine class.
211 config ARM_PATCH_PHYS_VIRT_16BIT
213 depends on ARM_PATCH_PHYS_VIRT && ARCH_MSM
215 This option extends the physical to virtual translation patching
216 to allow physical memory down to a theoretical minimum of 64K
219 source "init/Kconfig"
221 source "kernel/Kconfig.freezer"
226 bool "MMU-based Paged Memory Management Support"
229 Select if you want MMU-based virtualised addressing space
230 support by paged memory management. If unsure, say 'Y'.
233 # The "ARM system type" choice list is ordered alphabetically by option
234 # text. Please add new entries in the option alphabetic order.
237 prompt "ARM system type"
238 default ARCH_VERSATILE
240 config ARCH_INTEGRATOR
241 bool "ARM Ltd. Integrator family"
243 select ARCH_HAS_CPUFREQ
246 select GENERIC_CLOCKEVENTS
247 select PLAT_VERSATILE
248 select PLAT_VERSATILE_FPGA_IRQ
250 Support for ARM's Integrator platform.
253 bool "ARM Ltd. RealView family"
257 select GENERIC_CLOCKEVENTS
258 select ARCH_WANT_OPTIONAL_GPIOLIB
259 select PLAT_VERSATILE
260 select PLAT_VERSATILE_CLCD
261 select ARM_TIMER_SP804
262 select GPIO_PL061 if GPIOLIB
264 This enables support for ARM Ltd RealView boards.
266 config ARCH_VERSATILE
267 bool "ARM Ltd. Versatile family"
272 select GENERIC_CLOCKEVENTS
273 select ARCH_WANT_OPTIONAL_GPIOLIB
274 select PLAT_VERSATILE
275 select PLAT_VERSATILE_CLCD
276 select PLAT_VERSATILE_FPGA_IRQ
277 select ARM_TIMER_SP804
279 This enables support for ARM Ltd Versatile board.
282 bool "ARM Ltd. Versatile Express family"
283 select ARCH_WANT_OPTIONAL_GPIOLIB
285 select ARM_TIMER_SP804
287 select GENERIC_CLOCKEVENTS
289 select HAVE_PATA_PLATFORM
291 select PLAT_VERSATILE
292 select PLAT_VERSATILE_CLCD
294 This enables support for the ARM Ltd Versatile Express boards.
298 select ARCH_REQUIRE_GPIOLIB
301 select ARM_PATCH_PHYS_VIRT if MMU
303 This enables support for systems based on the Atmel AT91RM9200,
304 AT91SAM9 and AT91CAP9 processors.
307 bool "Broadcom BCMRING"
311 select ARM_TIMER_SP804
313 select GENERIC_CLOCKEVENTS
314 select ARCH_WANT_OPTIONAL_GPIOLIB
316 Support for Broadcom's BCMRing platform.
319 bool "Cirrus Logic CLPS711x/EP721x-based"
321 select ARCH_USES_GETTIMEOFFSET
323 Support for Cirrus Logic 711x/721x based boards.
326 bool "Cavium Networks CNS3XXX family"
328 select GENERIC_CLOCKEVENTS
330 select MIGHT_HAVE_PCI
331 select PCI_DOMAINS if PCI
333 Support for Cavium Networks CNS3XXX platform.
336 bool "Cortina Systems Gemini"
338 select ARCH_REQUIRE_GPIOLIB
339 select ARCH_USES_GETTIMEOFFSET
341 Support for the Cortina Systems Gemini family SoCs
348 select ARCH_USES_GETTIMEOFFSET
350 This is an evaluation board for the StrongARM processor available
351 from Digital. It has limited hardware on-board, including an
352 Ethernet interface, two PCMCIA sockets, two serial ports and a
361 select ARCH_REQUIRE_GPIOLIB
362 select ARCH_HAS_HOLES_MEMORYMODEL
363 select ARCH_USES_GETTIMEOFFSET
365 This enables support for the Cirrus EP93xx series of CPUs.
367 config ARCH_FOOTBRIDGE
371 select GENERIC_CLOCKEVENTS
373 Support for systems based on the DC21285 companion chip
374 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
377 bool "Freescale MXC/iMX-based"
378 select GENERIC_CLOCKEVENTS
379 select ARCH_REQUIRE_GPIOLIB
382 select HAVE_SCHED_CLOCK
384 Support for Freescale MXC/iMX-based family of processors
387 bool "Freescale MXS-based"
388 select GENERIC_CLOCKEVENTS
389 select ARCH_REQUIRE_GPIOLIB
393 Support for Freescale MXS-based family of processors
396 bool "Hilscher NetX based"
400 select GENERIC_CLOCKEVENTS
402 This enables support for systems based on the Hilscher NetX Soc
405 bool "Hynix HMS720x-based"
408 select ARCH_USES_GETTIMEOFFSET
410 This enables support for systems based on the Hynix HMS720x
418 select ARCH_SUPPORTS_MSI
421 Support for Intel's IOP13XX (XScale) family of processors.
429 select ARCH_REQUIRE_GPIOLIB
431 Support for Intel's 80219 and IOP32X (XScale) family of
440 select ARCH_REQUIRE_GPIOLIB
442 Support for Intel's IOP33X (XScale) family of processors.
449 select ARCH_USES_GETTIMEOFFSET
451 Support for Intel's IXP23xx (XScale) family of processors.
454 bool "IXP2400/2800-based"
458 select ARCH_USES_GETTIMEOFFSET
460 Support for Intel's IXP2400/2800 (XScale) family of processors.
468 select GENERIC_CLOCKEVENTS
469 select HAVE_SCHED_CLOCK
470 select MIGHT_HAVE_PCI
471 select DMABOUNCE if PCI
473 Support for Intel's IXP4XX (XScale) family of processors.
479 select ARCH_REQUIRE_GPIOLIB
480 select GENERIC_CLOCKEVENTS
483 Support for the Marvell Dove SoC 88AP510
486 bool "Marvell Kirkwood"
489 select ARCH_REQUIRE_GPIOLIB
490 select GENERIC_CLOCKEVENTS
493 Support for the following Marvell Kirkwood series SoCs:
494 88F6180, 88F6192 and 88F6281.
497 bool "Marvell Loki (88RC8480)"
499 select GENERIC_CLOCKEVENTS
502 Support for the Marvell Loki (88RC8480) SoC.
508 select ARCH_REQUIRE_GPIOLIB
511 select USB_ARCH_HAS_OHCI
514 select GENERIC_CLOCKEVENTS
516 Support for the NXP LPC32XX family of processors
519 bool "Marvell MV78xx0"
522 select ARCH_REQUIRE_GPIOLIB
523 select GENERIC_CLOCKEVENTS
526 Support for the following Marvell MV78xx0 series SoCs:
534 select ARCH_REQUIRE_GPIOLIB
535 select GENERIC_CLOCKEVENTS
538 Support for the following Marvell Orion 5x series SoCs:
539 Orion-1 (5181), Orion-VoIP (5181L), Orion-NAS (5182),
540 Orion-2 (5281), Orion-1-90 (6183).
543 bool "Marvell PXA168/910/MMP2"
545 select ARCH_REQUIRE_GPIOLIB
547 select GENERIC_CLOCKEVENTS
548 select HAVE_SCHED_CLOCK
553 Support for Marvell's PXA168/PXA910(MMP) and MMP2 processor line.
556 bool "Micrel/Kendin KS8695"
558 select ARCH_REQUIRE_GPIOLIB
559 select ARCH_USES_GETTIMEOFFSET
561 Support for Micrel/Kendin KS8695 "Centaur" (ARM922T) based
562 System-on-Chip devices.
565 bool "Nuvoton W90X900 CPU"
567 select ARCH_REQUIRE_GPIOLIB
570 select GENERIC_CLOCKEVENTS
572 Support for Nuvoton (Winbond logic dept.) ARM9 processor,
573 At present, the w90x900 has been renamed nuc900, regarding
574 the ARM series product line, you can login the following
575 link address to know more.
577 <http://www.nuvoton.com/hq/enu/ProductAndSales/ProductLines/
578 ConsumerElectronicsIC/ARMMicrocontroller/ARMMicrocontroller>
581 bool "Nuvoton NUC93X CPU"
585 Support for Nuvoton (Winbond logic dept.) NUC93X MCU,The NUC93X is a
586 low-power and high performance MPEG-4/JPEG multimedia controller chip.
593 select GENERIC_CLOCKEVENTS
596 select HAVE_SCHED_CLOCK
597 select ARCH_HAS_BARRIERS if CACHE_L2X0
598 select ARCH_HAS_CPUFREQ
600 This enables support for NVIDIA Tegra based systems (Tegra APX,
601 Tegra 6xx and Tegra 2 series).
604 bool "Philips Nexperia PNX4008 Mobile"
607 select ARCH_USES_GETTIMEOFFSET
609 This enables support for Philips PNX4008 mobile platform.
612 bool "PXA2xx/PXA3xx-based"
615 select ARCH_HAS_CPUFREQ
618 select ARCH_REQUIRE_GPIOLIB
619 select GENERIC_CLOCKEVENTS
620 select HAVE_SCHED_CLOCK
625 Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
630 select GENERIC_CLOCKEVENTS
631 select ARCH_REQUIRE_GPIOLIB
634 Support for Qualcomm MSM/QSD based systems. This runs on the
635 apps processor of the MSM/QSD and depends on a shared memory
636 interface to the modem processor which runs the baseband
637 stack and controls some vital subsystems
638 (clock and power control, etc).
641 bool "Renesas SH-Mobile / R-Mobile"
644 select GENERIC_CLOCKEVENTS
647 select MULTI_IRQ_HANDLER
648 select PM_GENERIC_DOMAINS if PM
650 Support for Renesas's SH-Mobile and R-Mobile ARM platforms.
657 select ARCH_MAY_HAVE_PC_FDC
658 select HAVE_PATA_PLATFORM
661 select ARCH_SPARSEMEM_ENABLE
662 select ARCH_USES_GETTIMEOFFSET
664 On the Acorn Risc-PC, Linux can support the internal IDE disk and
665 CD-ROM interface, serial and parallel port, and the floppy drive.
672 select ARCH_SPARSEMEM_ENABLE
674 select ARCH_HAS_CPUFREQ
676 select GENERIC_CLOCKEVENTS
678 select HAVE_SCHED_CLOCK
680 select ARCH_REQUIRE_GPIOLIB
682 Support for StrongARM 11x0 based boards.
685 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2416, S3C2440, S3C2442, S3C2443, S3C2450"
687 select ARCH_HAS_CPUFREQ
689 select ARCH_USES_GETTIMEOFFSET
690 select HAVE_S3C2410_I2C if I2C
692 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
693 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
694 the Samsung SMDK2410 development board (and derivatives).
696 Note, the S3C2416 and the S3C2450 are so close that they even share
697 the same SoC ID code. This means that there is no separate machine
698 directory (no arch/arm/mach-s3c2450) as the S3C2416 was first.
701 bool "Samsung S3C64XX"
707 select ARCH_USES_GETTIMEOFFSET
708 select ARCH_HAS_CPUFREQ
709 select ARCH_REQUIRE_GPIOLIB
710 select SAMSUNG_CLKSRC
711 select SAMSUNG_IRQ_VIC_TIMER
712 select SAMSUNG_IRQ_UART
713 select S3C_GPIO_TRACK
714 select S3C_GPIO_PULL_UPDOWN
715 select S3C_GPIO_CFG_S3C24XX
716 select S3C_GPIO_CFG_S3C64XX
718 select USB_ARCH_HAS_OHCI
719 select SAMSUNG_GPIOLIB_4BIT
720 select HAVE_S3C2410_I2C if I2C
721 select HAVE_S3C2410_WATCHDOG if WATCHDOG
723 Samsung S3C64XX series based systems
726 bool "Samsung S5P6440 S5P6450"
730 select HAVE_S3C2410_WATCHDOG if WATCHDOG
731 select GENERIC_CLOCKEVENTS
732 select HAVE_SCHED_CLOCK
733 select HAVE_S3C2410_I2C if I2C
734 select HAVE_S3C_RTC if RTC_CLASS
736 Samsung S5P64X0 CPU based systems, such as the Samsung SMDK6440,
740 bool "Samsung S5PC100"
744 select ARM_L1_CACHE_SHIFT_6
745 select ARCH_USES_GETTIMEOFFSET
746 select HAVE_S3C2410_I2C if I2C
747 select HAVE_S3C_RTC if RTC_CLASS
748 select HAVE_S3C2410_WATCHDOG if WATCHDOG
750 Samsung S5PC100 series based systems
753 bool "Samsung S5PV210/S5PC110"
755 select ARCH_SPARSEMEM_ENABLE
758 select ARM_L1_CACHE_SHIFT_6
759 select ARCH_HAS_CPUFREQ
760 select GENERIC_CLOCKEVENTS
761 select HAVE_SCHED_CLOCK
762 select HAVE_S3C2410_I2C if I2C
763 select HAVE_S3C_RTC if RTC_CLASS
764 select HAVE_S3C2410_WATCHDOG if WATCHDOG
766 Samsung S5PV210/S5PC110 series based systems
769 bool "Samsung EXYNOS4"
771 select ARCH_SPARSEMEM_ENABLE
774 select ARCH_HAS_CPUFREQ
775 select GENERIC_CLOCKEVENTS
776 select HAVE_S3C_RTC if RTC_CLASS
777 select HAVE_S3C2410_I2C if I2C
778 select HAVE_S3C2410_WATCHDOG if WATCHDOG
780 Samsung EXYNOS4 series based systems
789 select ARCH_USES_GETTIMEOFFSET
791 Support for the StrongARM based Digital DNARD machine, also known
792 as "Shark" (<http://www.shark-linux.de/shark.html>).
795 bool "Telechips TCC ARM926-based systems"
800 select GENERIC_CLOCKEVENTS
802 Support for Telechips TCC ARM926-based systems.
805 bool "ST-Ericsson U300 Series"
809 select HAVE_SCHED_CLOCK
813 select GENERIC_CLOCKEVENTS
817 Support for ST-Ericsson U300 series mobile platforms.
820 bool "ST-Ericsson U8500 Series"
823 select GENERIC_CLOCKEVENTS
825 select ARCH_REQUIRE_GPIOLIB
826 select ARCH_HAS_CPUFREQ
828 Support for ST-Ericsson's Ux500 architecture
831 bool "STMicroelectronics Nomadik"
836 select GENERIC_CLOCKEVENTS
837 select ARCH_REQUIRE_GPIOLIB
839 Support for the Nomadik platform by ST-Ericsson
843 select GENERIC_CLOCKEVENTS
844 select ARCH_REQUIRE_GPIOLIB
848 select GENERIC_ALLOCATOR
849 select GENERIC_IRQ_CHIP
850 select ARCH_HAS_HOLES_MEMORYMODEL
852 Support for TI's DaVinci platform.
857 select ARCH_REQUIRE_GPIOLIB
858 select ARCH_HAS_CPUFREQ
859 select GENERIC_CLOCKEVENTS
860 select HAVE_SCHED_CLOCK
861 select ARCH_HAS_HOLES_MEMORYMODEL
863 Support for TI's OMAP platform (OMAP1/2/3/4).
868 select ARCH_REQUIRE_GPIOLIB
871 select GENERIC_CLOCKEVENTS
874 Support for ST's SPEAr platform (SPEAr3xx, SPEAr6xx and SPEAr13xx).
877 bool "VIA/WonderMedia 85xx"
880 select ARCH_HAS_CPUFREQ
881 select GENERIC_CLOCKEVENTS
882 select ARCH_REQUIRE_GPIOLIB
885 Support for VIA/WonderMedia VT8500/WM85xx System-on-Chip.
889 # This is sorted alphabetically by mach-* pathname. However, plat-*
890 # Kconfigs may be included either alphabetically (according to the
891 # plat- suffix) or along side the corresponding mach-* source.
893 source "arch/arm/mach-at91/Kconfig"
895 source "arch/arm/mach-bcmring/Kconfig"
897 source "arch/arm/mach-clps711x/Kconfig"
899 source "arch/arm/mach-cns3xxx/Kconfig"
901 source "arch/arm/mach-davinci/Kconfig"
903 source "arch/arm/mach-dove/Kconfig"
905 source "arch/arm/mach-ep93xx/Kconfig"
907 source "arch/arm/mach-footbridge/Kconfig"
909 source "arch/arm/mach-gemini/Kconfig"
911 source "arch/arm/mach-h720x/Kconfig"
913 source "arch/arm/mach-integrator/Kconfig"
915 source "arch/arm/mach-iop32x/Kconfig"
917 source "arch/arm/mach-iop33x/Kconfig"
919 source "arch/arm/mach-iop13xx/Kconfig"
921 source "arch/arm/mach-ixp4xx/Kconfig"
923 source "arch/arm/mach-ixp2000/Kconfig"
925 source "arch/arm/mach-ixp23xx/Kconfig"
927 source "arch/arm/mach-kirkwood/Kconfig"
929 source "arch/arm/mach-ks8695/Kconfig"
931 source "arch/arm/mach-loki/Kconfig"
933 source "arch/arm/mach-lpc32xx/Kconfig"
935 source "arch/arm/mach-msm/Kconfig"
937 source "arch/arm/mach-mv78xx0/Kconfig"
939 source "arch/arm/plat-mxc/Kconfig"
941 source "arch/arm/mach-mxs/Kconfig"
943 source "arch/arm/mach-netx/Kconfig"
945 source "arch/arm/mach-nomadik/Kconfig"
946 source "arch/arm/plat-nomadik/Kconfig"
948 source "arch/arm/mach-nuc93x/Kconfig"
950 source "arch/arm/plat-omap/Kconfig"
952 source "arch/arm/mach-omap1/Kconfig"
954 source "arch/arm/mach-omap2/Kconfig"
956 source "arch/arm/mach-orion5x/Kconfig"
958 source "arch/arm/mach-pxa/Kconfig"
959 source "arch/arm/plat-pxa/Kconfig"
961 source "arch/arm/mach-mmp/Kconfig"
963 source "arch/arm/mach-realview/Kconfig"
965 source "arch/arm/mach-sa1100/Kconfig"
967 source "arch/arm/plat-samsung/Kconfig"
968 source "arch/arm/plat-s3c24xx/Kconfig"
969 source "arch/arm/plat-s5p/Kconfig"
971 source "arch/arm/plat-spear/Kconfig"
973 source "arch/arm/plat-tcc/Kconfig"
976 source "arch/arm/mach-s3c2400/Kconfig"
977 source "arch/arm/mach-s3c2410/Kconfig"
978 source "arch/arm/mach-s3c2412/Kconfig"
979 source "arch/arm/mach-s3c2416/Kconfig"
980 source "arch/arm/mach-s3c2440/Kconfig"
981 source "arch/arm/mach-s3c2443/Kconfig"
985 source "arch/arm/mach-s3c64xx/Kconfig"
988 source "arch/arm/mach-s5p64x0/Kconfig"
990 source "arch/arm/mach-s5pc100/Kconfig"
992 source "arch/arm/mach-s5pv210/Kconfig"
994 source "arch/arm/mach-exynos4/Kconfig"
996 source "arch/arm/mach-shmobile/Kconfig"
998 source "arch/arm/mach-tegra/Kconfig"
1000 source "arch/arm/mach-u300/Kconfig"
1002 source "arch/arm/mach-ux500/Kconfig"
1004 source "arch/arm/mach-versatile/Kconfig"
1006 source "arch/arm/mach-vexpress/Kconfig"
1007 source "arch/arm/plat-versatile/Kconfig"
1009 source "arch/arm/mach-vt8500/Kconfig"
1011 source "arch/arm/mach-w90x900/Kconfig"
1013 # Definitions to make life easier
1019 select GENERIC_CLOCKEVENTS
1020 select HAVE_SCHED_CLOCK
1025 select GENERIC_IRQ_CHIP
1026 select HAVE_SCHED_CLOCK
1031 config PLAT_VERSATILE
1034 config ARM_TIMER_SP804
1038 source arch/arm/mm/Kconfig
1041 bool "Enable iWMMXt support"
1042 depends on CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_PJ4
1043 default y if PXA27x || PXA3xx || PXA95x || ARCH_MMP
1045 Enable support for iWMMXt context switching at run time if
1046 running on a CPU that supports it.
1048 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
1051 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
1055 depends on (CPU_V6 || CPU_V6K || CPU_V7 || XSCALE_PMU) && \
1056 (!ARCH_OMAP3 || OMAP3_EMU)
1060 config MULTI_IRQ_HANDLER
1063 Allow each machine to specify it's own IRQ handler at run time.
1066 source "arch/arm/Kconfig-nommu"
1069 config ARM_ERRATA_411920
1070 bool "ARM errata: Invalidation of the Instruction Cache operation can fail"
1071 depends on CPU_V6 || CPU_V6K
1073 Invalidation of the Instruction Cache operation can
1074 fail. This erratum is present in 1136 (before r1p4), 1156 and 1176.
1075 It does not affect the MPCore. This option enables the ARM Ltd.
1076 recommended workaround.
1078 config ARM_ERRATA_430973
1079 bool "ARM errata: Stale prediction on replaced interworking branch"
1082 This option enables the workaround for the 430973 Cortex-A8
1083 (r1p0..r1p2) erratum. If a code sequence containing an ARM/Thumb
1084 interworking branch is replaced with another code sequence at the
1085 same virtual address, whether due to self-modifying code or virtual
1086 to physical address re-mapping, Cortex-A8 does not recover from the
1087 stale interworking branch prediction. This results in Cortex-A8
1088 executing the new code sequence in the incorrect ARM or Thumb state.
1089 The workaround enables the BTB/BTAC operations by setting ACTLR.IBE
1090 and also flushes the branch target cache at every context switch.
1091 Note that setting specific bits in the ACTLR register may not be
1092 available in non-secure mode.
1094 config ARM_ERRATA_458693
1095 bool "ARM errata: Processor deadlock when a false hazard is created"
1098 This option enables the workaround for the 458693 Cortex-A8 (r2p0)
1099 erratum. For very specific sequences of memory operations, it is
1100 possible for a hazard condition intended for a cache line to instead
1101 be incorrectly associated with a different cache line. This false
1102 hazard might then cause a processor deadlock. The workaround enables
1103 the L1 caching of the NEON accesses and disables the PLD instruction
1104 in the ACTLR register. Note that setting specific bits in the ACTLR
1105 register may not be available in non-secure mode.
1107 config ARM_ERRATA_460075
1108 bool "ARM errata: Data written to the L2 cache can be overwritten with stale data"
1111 This option enables the workaround for the 460075 Cortex-A8 (r2p0)
1112 erratum. Any asynchronous access to the L2 cache may encounter a
1113 situation in which recent store transactions to the L2 cache are lost
1114 and overwritten with stale memory contents from external memory. The
1115 workaround disables the write-allocate mode for the L2 cache via the
1116 ACTLR register. Note that setting specific bits in the ACTLR register
1117 may not be available in non-secure mode.
1119 config ARM_ERRATA_742230
1120 bool "ARM errata: DMB operation may be faulty"
1121 depends on CPU_V7 && SMP
1123 This option enables the workaround for the 742230 Cortex-A9
1124 (r1p0..r2p2) erratum. Under rare circumstances, a DMB instruction
1125 between two write operations may not ensure the correct visibility
1126 ordering of the two writes. This workaround sets a specific bit in
1127 the diagnostic register of the Cortex-A9 which causes the DMB
1128 instruction to behave as a DSB, ensuring the correct behaviour of
1131 config ARM_ERRATA_742231
1132 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
1133 depends on CPU_V7 && SMP
1135 This option enables the workaround for the 742231 Cortex-A9
1136 (r2p0..r2p2) erratum. Under certain conditions, specific to the
1137 Cortex-A9 MPCore micro-architecture, two CPUs working in SMP mode,
1138 accessing some data located in the same cache line, may get corrupted
1139 data due to bad handling of the address hazard when the line gets
1140 replaced from one of the CPUs at the same time as another CPU is
1141 accessing it. This workaround sets specific bits in the diagnostic
1142 register of the Cortex-A9 which reduces the linefill issuing
1143 capabilities of the processor.
1145 config PL310_ERRATA_588369
1146 bool "Clean & Invalidate maintenance operations do not invalidate clean lines"
1147 depends on CACHE_L2X0
1149 The PL310 L2 cache controller implements three types of Clean &
1150 Invalidate maintenance operations: by Physical Address
1151 (offset 0x7F0), by Index/Way (0x7F8) and by Way (0x7FC).
1152 They are architecturally defined to behave as the execution of a
1153 clean operation followed immediately by an invalidate operation,
1154 both performing to the same memory location. This functionality
1155 is not correctly implemented in PL310 as clean lines are not
1156 invalidated as a result of these operations.
1158 config ARM_ERRATA_720789
1159 bool "ARM errata: TLBIASIDIS and TLBIMVAIS operations can broadcast a faulty ASID"
1160 depends on CPU_V7 && SMP
1162 This option enables the workaround for the 720789 Cortex-A9 (prior to
1163 r2p0) erratum. A faulty ASID can be sent to the other CPUs for the
1164 broadcasted CP15 TLB maintenance operations TLBIASIDIS and TLBIMVAIS.
1165 As a consequence of this erratum, some TLB entries which should be
1166 invalidated are not, resulting in an incoherency in the system page
1167 tables. The workaround changes the TLB flushing routines to invalidate
1168 entries regardless of the ASID.
1170 config PL310_ERRATA_727915
1171 bool "Background Clean & Invalidate by Way operation can cause data corruption"
1172 depends on CACHE_L2X0
1174 PL310 implements the Clean & Invalidate by Way L2 cache maintenance
1175 operation (offset 0x7FC). This operation runs in background so that
1176 PL310 can handle normal accesses while it is in progress. Under very
1177 rare circumstances, due to this erratum, write data can be lost when
1178 PL310 treats a cacheable write transaction during a Clean &
1179 Invalidate by Way operation.
1181 config ARM_ERRATA_743622
1182 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
1185 This option enables the workaround for the 743622 Cortex-A9
1186 (r2p0..r2p2) erratum. Under very rare conditions, a faulty
1187 optimisation in the Cortex-A9 Store Buffer may lead to data
1188 corruption. This workaround sets a specific bit in the diagnostic
1189 register of the Cortex-A9 which disables the Store Buffer
1190 optimisation, preventing the defect from occurring. This has no
1191 visible impact on the overall performance or power consumption of the
1194 config ARM_ERRATA_751472
1195 bool "ARM errata: Interrupted ICIALLUIS may prevent completion of broadcasted operation"
1196 depends on CPU_V7 && SMP
1198 This option enables the workaround for the 751472 Cortex-A9 (prior
1199 to r3p0) erratum. An interrupted ICIALLUIS operation may prevent the
1200 completion of a following broadcasted operation if the second
1201 operation is received by a CPU before the ICIALLUIS has completed,
1202 potentially leading to corrupted entries in the cache or TLB.
1204 config ARM_ERRATA_753970
1205 bool "ARM errata: cache sync operation may be faulty"
1206 depends on CACHE_PL310
1208 This option enables the workaround for the 753970 PL310 (r3p0) erratum.
1210 Under some condition the effect of cache sync operation on
1211 the store buffer still remains when the operation completes.
1212 This means that the store buffer is always asked to drain and
1213 this prevents it from merging any further writes. The workaround
1214 is to replace the normal offset of cache sync operation (0x730)
1215 by another offset targeting an unmapped PL310 register 0x740.
1216 This has the same effect as the cache sync operation: store buffer
1217 drain and waiting for all buffers empty.
1219 config ARM_ERRATA_754322
1220 bool "ARM errata: possible faulty MMU translations following an ASID switch"
1223 This option enables the workaround for the 754322 Cortex-A9 (r2p*,
1224 r3p*) erratum. A speculative memory access may cause a page table walk
1225 which starts prior to an ASID switch but completes afterwards. This
1226 can populate the micro-TLB with a stale entry which may be hit with
1227 the new ASID. This workaround places two dsb instructions in the mm
1228 switching code so that no page table walks can cross the ASID switch.
1230 config ARM_ERRATA_754327
1231 bool "ARM errata: no automatic Store Buffer drain"
1232 depends on CPU_V7 && SMP
1234 This option enables the workaround for the 754327 Cortex-A9 (prior to
1235 r2p0) erratum. The Store Buffer does not have any automatic draining
1236 mechanism and therefore a livelock may occur if an external agent
1237 continuously polls a memory location waiting to observe an update.
1238 This workaround defines cpu_relax() as smp_mb(), preventing correctly
1239 written polling loops from denying visibility of updates to memory.
1243 source "arch/arm/common/Kconfig"
1253 Find out whether you have ISA slots on your motherboard. ISA is the
1254 name of a bus system, i.e. the way the CPU talks to the other stuff
1255 inside your box. Other bus systems are PCI, EISA, MicroChannel
1256 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1257 newer boards don't support it. If you have ISA, say Y, otherwise N.
1259 # Select ISA DMA controller support
1264 # Select ISA DMA interface
1269 bool "PCI support" if MIGHT_HAVE_PCI
1271 Find out whether you have a PCI motherboard. PCI is the name of a
1272 bus system, i.e. the way the CPU talks to the other stuff inside
1273 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1274 VESA. If you have PCI, say Y, otherwise N.
1280 config PCI_NANOENGINE
1281 bool "BSE nanoEngine PCI support"
1282 depends on SA1100_NANOENGINE
1284 Enable PCI on the BSE nanoEngine board.
1289 # Select the host bridge type
1290 config PCI_HOST_VIA82C505
1292 depends on PCI && ARCH_SHARK
1295 config PCI_HOST_ITE8152
1297 depends on PCI && MACH_ARMCORE
1301 source "drivers/pci/Kconfig"
1303 source "drivers/pcmcia/Kconfig"
1307 menu "Kernel Features"
1309 source "kernel/time/Kconfig"
1312 bool "Symmetric Multi-Processing"
1313 depends on CPU_V6K || CPU_V7
1314 depends on GENERIC_CLOCKEVENTS
1315 depends on REALVIEW_EB_ARM11MP || REALVIEW_EB_A9MP || \
1316 MACH_REALVIEW_PB11MP || MACH_REALVIEW_PBX || ARCH_OMAP4 || \
1317 ARCH_EXYNOS4 || ARCH_TEGRA || ARCH_U8500 || ARCH_VEXPRESS_CA9X4 || \
1318 ARCH_MSM_SCORPIONMP || ARCH_SHMOBILE
1319 select USE_GENERIC_SMP_HELPERS
1320 select HAVE_ARM_SCU if !ARCH_MSM_SCORPIONMP
1322 This enables support for systems with more than one CPU. If you have
1323 a system with only one CPU, like most personal computers, say N. If
1324 you have a system with more than one CPU, say Y.
1326 If you say N here, the kernel will run on single and multiprocessor
1327 machines, but will use only one CPU of a multiprocessor machine. If
1328 you say Y here, the kernel will run on many, but not all, single
1329 processor machines. On a single processor machine, the kernel will
1330 run faster if you say N here.
1332 See also <file:Documentation/i386/IO-APIC.txt>,
1333 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
1334 <http://tldp.org/HOWTO/SMP-HOWTO.html>.
1336 If you don't know what to do here, say N.
1339 bool "Allow booting SMP kernel on uniprocessor systems (EXPERIMENTAL)"
1340 depends on EXPERIMENTAL
1341 depends on SMP && !XIP_KERNEL
1344 SMP kernels contain instructions which fail on non-SMP processors.
1345 Enabling this option allows the kernel to modify itself to make
1346 these instructions safe. Disabling it allows about 1K of space
1349 If you don't know what to do here, say Y.
1354 This option enables support for the ARM system coherency unit
1361 This options enables support for the ARM timer and watchdog unit
1364 prompt "Memory split"
1367 Select the desired split between kernel and user memory.
1369 If you are not absolutely sure what you are doing, leave this
1373 bool "3G/1G user/kernel split"
1375 bool "2G/2G user/kernel split"
1377 bool "1G/3G user/kernel split"
1382 default 0x40000000 if VMSPLIT_1G
1383 default 0x80000000 if VMSPLIT_2G
1387 int "Maximum number of CPUs (2-32)"
1393 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
1394 depends on SMP && HOTPLUG && EXPERIMENTAL
1396 Say Y here to experiment with turning CPUs off and on. CPUs
1397 can be controlled through /sys/devices/system/cpu.
1400 bool "Use local timer interrupts"
1403 select HAVE_ARM_TWD if (!ARCH_MSM_SCORPIONMP && !EXYNOS4_MCT)
1405 Enable support for local timers on SMP platforms, rather then the
1406 legacy IPI broadcast method. Local timers allows the system
1407 accounting to be spread across the timer interval, preventing a
1408 "thundering herd" at every timer tick.
1410 source kernel/Kconfig.preempt
1414 default 200 if ARCH_EBSA110 || ARCH_S3C2410 || ARCH_S5P64X0 || \
1415 ARCH_S5PV210 || ARCH_EXYNOS4
1416 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
1417 default AT91_TIMER_HZ if ARCH_AT91
1418 default SHMOBILE_TIMER_HZ if ARCH_SHMOBILE
1421 config THUMB2_KERNEL
1422 bool "Compile the kernel in Thumb-2 mode (EXPERIMENTAL)"
1423 depends on CPU_V7 && !CPU_V6 && !CPU_V6K && EXPERIMENTAL
1425 select ARM_ASM_UNIFIED
1427 By enabling this option, the kernel will be compiled in
1428 Thumb-2 mode. A compiler/assembler that understand the unified
1429 ARM-Thumb syntax is needed.
1433 config THUMB2_AVOID_R_ARM_THM_JUMP11
1434 bool "Work around buggy Thumb-2 short branch relocations in gas"
1435 depends on THUMB2_KERNEL && MODULES
1438 Various binutils versions can resolve Thumb-2 branches to
1439 locally-defined, preemptible global symbols as short-range "b.n"
1440 branch instructions.
1442 This is a problem, because there's no guarantee the final
1443 destination of the symbol, or any candidate locations for a
1444 trampoline, are within range of the branch. For this reason, the
1445 kernel does not support fixing up the R_ARM_THM_JUMP11 (102)
1446 relocation in modules at all, and it makes little sense to add
1449 The symptom is that the kernel fails with an "unsupported
1450 relocation" error when loading some modules.
1452 Until fixed tools are available, passing
1453 -fno-optimize-sibling-calls to gcc should prevent gcc generating
1454 code which hits this problem, at the cost of a bit of extra runtime
1455 stack usage in some cases.
1457 The problem is described in more detail at:
1458 https://bugs.launchpad.net/binutils-linaro/+bug/725126
1460 Only Thumb-2 kernels are affected.
1462 Unless you are sure your tools don't have this problem, say Y.
1464 config ARM_ASM_UNIFIED
1468 bool "Use the ARM EABI to compile the kernel"
1470 This option allows for the kernel to be compiled using the latest
1471 ARM ABI (aka EABI). This is only useful if you are using a user
1472 space environment that is also compiled with EABI.
1474 Since there are major incompatibilities between the legacy ABI and
1475 EABI, especially with regard to structure member alignment, this
1476 option also changes the kernel syscall calling convention to
1477 disambiguate both ABIs and allow for backward compatibility support
1478 (selected with CONFIG_OABI_COMPAT).
1480 To use this you need GCC version 4.0.0 or later.
1483 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
1484 depends on AEABI && EXPERIMENTAL && !THUMB2_KERNEL
1487 This option preserves the old syscall interface along with the
1488 new (ARM EABI) one. It also provides a compatibility layer to
1489 intercept syscalls that have structure arguments which layout
1490 in memory differs between the legacy ABI and the new ARM EABI
1491 (only for non "thumb" binaries). This option adds a tiny
1492 overhead to all syscalls and produces a slightly larger kernel.
1493 If you know you'll be using only pure EABI user space then you
1494 can say N here. If this option is not selected and you attempt
1495 to execute a legacy ABI binary then the result will be
1496 UNPREDICTABLE (in fact it can be predicted that it won't work
1497 at all). If in doubt say Y.
1499 config ARCH_HAS_HOLES_MEMORYMODEL
1502 config ARCH_SPARSEMEM_ENABLE
1505 config ARCH_SPARSEMEM_DEFAULT
1506 def_bool ARCH_SPARSEMEM_ENABLE
1508 config ARCH_SELECT_MEMORY_MODEL
1509 def_bool ARCH_SPARSEMEM_ENABLE
1511 config HAVE_ARCH_PFN_VALID
1512 def_bool ARCH_HAS_HOLES_MEMORYMODEL || !SPARSEMEM
1515 bool "High Memory Support"
1518 The address space of ARM processors is only 4 Gigabytes large
1519 and it has to accommodate user address space, kernel address
1520 space as well as some memory mapped IO. That means that, if you
1521 have a large amount of physical memory and/or IO, not all of the
1522 memory can be "permanently mapped" by the kernel. The physical
1523 memory that is not permanently mapped is called "high memory".
1525 Depending on the selected kernel/user memory split, minimum
1526 vmalloc space and actual amount of RAM, you may not need this
1527 option which should result in a slightly faster kernel.
1532 bool "Allocate 2nd-level pagetables from highmem"
1535 config HW_PERF_EVENTS
1536 bool "Enable hardware performance counter support for perf events"
1537 depends on PERF_EVENTS && CPU_HAS_PMU
1540 Enable hardware performance counter support for perf events. If
1541 disabled, perf events will use software events only.
1545 config FORCE_MAX_ZONEORDER
1546 int "Maximum zone order" if ARCH_SHMOBILE
1547 range 11 64 if ARCH_SHMOBILE
1548 default "9" if SA1111
1551 The kernel memory allocator divides physically contiguous memory
1552 blocks into "zones", where each zone is a power of two number of
1553 pages. This option selects the largest power of two that the kernel
1554 keeps in the memory allocator. If you need to allocate very large
1555 blocks of physically contiguous memory, then you may need to
1556 increase this value.
1558 This config option is actually maximum order plus one. For example,
1559 a value of 11 means that the largest free memory block is 2^10 pages.
1562 bool "Timer and CPU usage LEDs"
1563 depends on ARCH_CDB89712 || ARCH_EBSA110 || \
1564 ARCH_EBSA285 || ARCH_INTEGRATOR || \
1565 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
1566 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
1567 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
1568 ARCH_AT91 || ARCH_DAVINCI || \
1569 ARCH_KS8695 || MACH_RD88F5182 || ARCH_REALVIEW
1571 If you say Y here, the LEDs on your machine will be used
1572 to provide useful information about your current system status.
1574 If you are compiling a kernel for a NetWinder or EBSA-285, you will
1575 be able to select which LEDs are active using the options below. If
1576 you are compiling a kernel for the EBSA-110 or the LART however, the
1577 red LED will simply flash regularly to indicate that the system is
1578 still functional. It is safe to say Y here if you have a CATS
1579 system, but the driver will do nothing.
1582 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
1583 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1584 || MACH_OMAP_PERSEUS2
1586 depends on !GENERIC_CLOCKEVENTS
1587 default y if ARCH_EBSA110
1589 If you say Y here, one of the system LEDs (the green one on the
1590 NetWinder, the amber one on the EBSA285, or the red one on the LART)
1591 will flash regularly to indicate that the system is still
1592 operational. This is mainly useful to kernel hackers who are
1593 debugging unstable kernels.
1595 The LART uses the same LED for both Timer LED and CPU usage LED
1596 functions. You may choose to use both, but the Timer LED function
1597 will overrule the CPU usage LED.
1600 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
1602 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1603 || MACH_OMAP_PERSEUS2
1606 If you say Y here, the red LED will be used to give a good real
1607 time indication of CPU usage, by lighting whenever the idle task
1608 is not currently executing.
1610 The LART uses the same LED for both Timer LED and CPU usage LED
1611 functions. You may choose to use both, but the Timer LED function
1612 will overrule the CPU usage LED.
1614 config ALIGNMENT_TRAP
1616 depends on CPU_CP15_MMU
1617 default y if !ARCH_EBSA110
1618 select HAVE_PROC_CPU if PROC_FS
1620 ARM processors cannot fetch/store information which is not
1621 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
1622 address divisible by 4. On 32-bit ARM processors, these non-aligned
1623 fetch/store instructions will be emulated in software if you say
1624 here, which has a severe performance impact. This is necessary for
1625 correct operation of some network protocols. With an IP-only
1626 configuration it is safe to say N, otherwise say Y.
1628 config UACCESS_WITH_MEMCPY
1629 bool "Use kernel mem{cpy,set}() for {copy_to,clear}_user() (EXPERIMENTAL)"
1630 depends on MMU && EXPERIMENTAL
1631 default y if CPU_FEROCEON
1633 Implement faster copy_to_user and clear_user methods for CPU
1634 cores where a 8-word STM instruction give significantly higher
1635 memory write throughput than a sequence of individual 32bit stores.
1637 A possible side effect is a slight increase in scheduling latency
1638 between threads sharing the same address space if they invoke
1639 such copy operations with large buffers.
1641 However, if the CPU data cache is using a write-allocate mode,
1642 this option is unlikely to provide any performance gain.
1646 prompt "Enable seccomp to safely compute untrusted bytecode"
1648 This kernel feature is useful for number crunching applications
1649 that may need to compute untrusted bytecode during their
1650 execution. By using pipes or other transports made available to
1651 the process as file descriptors supporting the read/write
1652 syscalls, it's possible to isolate those applications in
1653 their own address space using seccomp. Once seccomp is
1654 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1655 and the task is only allowed to execute a few safe syscalls
1656 defined by each seccomp mode.
1658 config CC_STACKPROTECTOR
1659 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1660 depends on EXPERIMENTAL
1662 This option turns on the -fstack-protector GCC feature. This
1663 feature puts, at the beginning of functions, a canary value on
1664 the stack just before the return address, and validates
1665 the value just before actually returning. Stack based buffer
1666 overflows (that need to overwrite this return address) now also
1667 overwrite the canary, which gets detected and the attack is then
1668 neutralized via a kernel panic.
1669 This feature requires gcc version 4.2 or above.
1671 config DEPRECATED_PARAM_STRUCT
1672 bool "Provide old way to pass kernel parameters"
1674 This was deprecated in 2001 and announced to live on for 5 years.
1675 Some old boot loaders still use this way.
1682 bool "Flattened Device Tree support"
1684 select OF_EARLY_FLATTREE
1686 Include support for flattened device tree machine descriptions.
1688 # Compressed boot loader in ROM. Yes, we really want to ask about
1689 # TEXT and BSS so we preserve their values in the config files.
1690 config ZBOOT_ROM_TEXT
1691 hex "Compressed ROM boot loader base address"
1694 The physical address at which the ROM-able zImage is to be
1695 placed in the target. Platforms which normally make use of
1696 ROM-able zImage formats normally set this to a suitable
1697 value in their defconfig file.
1699 If ZBOOT_ROM is not enabled, this has no effect.
1701 config ZBOOT_ROM_BSS
1702 hex "Compressed ROM boot loader BSS address"
1705 The base address of an area of read/write memory in the target
1706 for the ROM-able zImage which must be available while the
1707 decompressor is running. It must be large enough to hold the
1708 entire decompressed kernel plus an additional 128 KiB.
1709 Platforms which normally make use of ROM-able zImage formats
1710 normally set this to a suitable value in their defconfig file.
1712 If ZBOOT_ROM is not enabled, this has no effect.
1715 bool "Compressed boot loader in ROM/flash"
1716 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
1718 Say Y here if you intend to execute your compressed kernel image
1719 (zImage) directly from ROM or flash. If unsure, say N.
1722 prompt "Include SD/MMC loader in zImage (EXPERIMENTAL)"
1723 depends on ZBOOT_ROM && ARCH_SH7372 && EXPERIMENTAL
1724 default ZBOOT_ROM_NONE
1726 Include experimental SD/MMC loading code in the ROM-able zImage.
1727 With this enabled it is possible to write the the ROM-able zImage
1728 kernel image to an MMC or SD card and boot the kernel straight
1729 from the reset vector. At reset the processor Mask ROM will load
1730 the first part of the the ROM-able zImage which in turn loads the
1731 rest the kernel image to RAM.
1733 config ZBOOT_ROM_NONE
1734 bool "No SD/MMC loader in zImage (EXPERIMENTAL)"
1736 Do not load image from SD or MMC
1738 config ZBOOT_ROM_MMCIF
1739 bool "Include MMCIF loader in zImage (EXPERIMENTAL)"
1741 Load image from MMCIF hardware block.
1743 config ZBOOT_ROM_SH_MOBILE_SDHI
1744 bool "Include SuperH Mobile SDHI loader in zImage (EXPERIMENTAL)"
1746 Load image from SDHI hardware block
1751 string "Default kernel command string"
1754 On some architectures (EBSA110 and CATS), there is currently no way
1755 for the boot loader to pass arguments to the kernel. For these
1756 architectures, you should supply some command-line options at build
1757 time by entering them here. As a minimum, you should specify the
1758 memory size and the root device (e.g., mem=64M root=/dev/nfs).
1761 prompt "Kernel command line type" if CMDLINE != ""
1762 default CMDLINE_FROM_BOOTLOADER
1764 config CMDLINE_FROM_BOOTLOADER
1765 bool "Use bootloader kernel arguments if available"
1767 Uses the command-line options passed by the boot loader. If
1768 the boot loader doesn't provide any, the default kernel command
1769 string provided in CMDLINE will be used.
1771 config CMDLINE_EXTEND
1772 bool "Extend bootloader kernel arguments"
1774 The command-line arguments provided by the boot loader will be
1775 appended to the default kernel command string.
1777 config CMDLINE_FORCE
1778 bool "Always use the default kernel command string"
1780 Always use the default kernel command string, even if the boot
1781 loader passes other arguments to the kernel.
1782 This is useful if you cannot or don't want to change the
1783 command-line options your boot loader passes to the kernel.
1787 bool "Kernel Execute-In-Place from ROM"
1788 depends on !ZBOOT_ROM
1790 Execute-In-Place allows the kernel to run from non-volatile storage
1791 directly addressable by the CPU, such as NOR flash. This saves RAM
1792 space since the text section of the kernel is not loaded from flash
1793 to RAM. Read-write sections, such as the data section and stack,
1794 are still copied to RAM. The XIP kernel is not compressed since
1795 it has to run directly from flash, so it will take more space to
1796 store it. The flash address used to link the kernel object files,
1797 and for storing it, is configuration dependent. Therefore, if you
1798 say Y here, you must know the proper physical address where to
1799 store the kernel image depending on your own flash memory usage.
1801 Also note that the make target becomes "make xipImage" rather than
1802 "make zImage" or "make Image". The final kernel binary to put in
1803 ROM memory will be arch/arm/boot/xipImage.
1807 config XIP_PHYS_ADDR
1808 hex "XIP Kernel Physical Location"
1809 depends on XIP_KERNEL
1810 default "0x00080000"
1812 This is the physical address in your flash memory the kernel will
1813 be linked for and stored to. This address is dependent on your
1817 bool "Kexec system call (EXPERIMENTAL)"
1818 depends on EXPERIMENTAL
1820 kexec is a system call that implements the ability to shutdown your
1821 current kernel, and to start another kernel. It is like a reboot
1822 but it is independent of the system firmware. And like a reboot
1823 you can start any kernel with it, not just Linux.
1825 It is an ongoing process to be certain the hardware in a machine
1826 is properly shutdown, so do not be surprised if this code does not
1827 initially work for you. It may help to enable device hotplugging
1831 bool "Export atags in procfs"
1835 Should the atags used to boot the kernel be exported in an "atags"
1836 file in procfs. Useful with kexec.
1839 bool "Build kdump crash kernel (EXPERIMENTAL)"
1840 depends on EXPERIMENTAL
1842 Generate crash dump after being started by kexec. This should
1843 be normally only set in special crash dump kernels which are
1844 loaded in the main kernel with kexec-tools into a specially
1845 reserved region and then later executed after a crash by
1846 kdump/kexec. The crash dump kernel must be compiled to a
1847 memory address not used by the main kernel
1849 For more details see Documentation/kdump/kdump.txt
1851 config AUTO_ZRELADDR
1852 bool "Auto calculation of the decompressed kernel image address"
1853 depends on !ZBOOT_ROM && !ARCH_U300
1855 ZRELADDR is the physical address where the decompressed kernel
1856 image will be placed. If AUTO_ZRELADDR is selected, the address
1857 will be determined at run-time by masking the current IP with
1858 0xf8000000. This assumes the zImage being placed in the first 128MB
1859 from start of memory.
1863 menu "CPU Power Management"
1867 source "drivers/cpufreq/Kconfig"
1870 tristate "CPUfreq driver for i.MX CPUs"
1871 depends on ARCH_MXC && CPU_FREQ
1873 This enables the CPUfreq driver for i.MX CPUs.
1875 config CPU_FREQ_SA1100
1878 config CPU_FREQ_SA1110
1881 config CPU_FREQ_INTEGRATOR
1882 tristate "CPUfreq driver for ARM Integrator CPUs"
1883 depends on ARCH_INTEGRATOR && CPU_FREQ
1886 This enables the CPUfreq driver for ARM Integrator CPUs.
1888 For details, take a look at <file:Documentation/cpu-freq>.
1894 depends on CPU_FREQ && ARCH_PXA && PXA25x
1896 select CPU_FREQ_DEFAULT_GOV_USERSPACE
1898 config CPU_FREQ_S3C64XX
1899 bool "CPUfreq support for Samsung S3C64XX CPUs"
1900 depends on CPU_FREQ && CPU_S3C6410
1905 Internal configuration node for common cpufreq on Samsung SoC
1907 config CPU_FREQ_S3C24XX
1908 bool "CPUfreq driver for Samsung S3C24XX series CPUs (EXPERIMENTAL)"
1909 depends on ARCH_S3C2410 && CPU_FREQ && EXPERIMENTAL
1912 This enables the CPUfreq driver for the Samsung S3C24XX family
1915 For details, take a look at <file:Documentation/cpu-freq>.
1919 config CPU_FREQ_S3C24XX_PLL
1920 bool "Support CPUfreq changing of PLL frequency (EXPERIMENTAL)"
1921 depends on CPU_FREQ_S3C24XX && EXPERIMENTAL
1923 Compile in support for changing the PLL frequency from the
1924 S3C24XX series CPUfreq driver. The PLL takes time to settle
1925 after a frequency change, so by default it is not enabled.
1927 This also means that the PLL tables for the selected CPU(s) will
1928 be built which may increase the size of the kernel image.
1930 config CPU_FREQ_S3C24XX_DEBUG
1931 bool "Debug CPUfreq Samsung driver core"
1932 depends on CPU_FREQ_S3C24XX
1934 Enable s3c_freq_dbg for the Samsung S3C CPUfreq core
1936 config CPU_FREQ_S3C24XX_IODEBUG
1937 bool "Debug CPUfreq Samsung driver IO timing"
1938 depends on CPU_FREQ_S3C24XX
1940 Enable s3c_freq_iodbg for the Samsung S3C CPUfreq core
1942 config CPU_FREQ_S3C24XX_DEBUGFS
1943 bool "Export debugfs for CPUFreq"
1944 depends on CPU_FREQ_S3C24XX && DEBUG_FS
1946 Export status information via debugfs.
1950 source "drivers/cpuidle/Kconfig"
1954 menu "Floating point emulation"
1956 comment "At least one emulation must be selected"
1959 bool "NWFPE math emulation"
1960 depends on (!AEABI || OABI_COMPAT) && !THUMB2_KERNEL
1962 Say Y to include the NWFPE floating point emulator in the kernel.
1963 This is necessary to run most binaries. Linux does not currently
1964 support floating point hardware so you need to say Y here even if
1965 your machine has an FPA or floating point co-processor podule.
1967 You may say N here if you are going to load the Acorn FPEmulator
1968 early in the bootup.
1971 bool "Support extended precision"
1972 depends on FPE_NWFPE
1974 Say Y to include 80-bit support in the kernel floating-point
1975 emulator. Otherwise, only 32 and 64-bit support is compiled in.
1976 Note that gcc does not generate 80-bit operations by default,
1977 so in most cases this option only enlarges the size of the
1978 floating point emulator without any good reason.
1980 You almost surely want to say N here.
1983 bool "FastFPE math emulation (EXPERIMENTAL)"
1984 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
1986 Say Y here to include the FAST floating point emulator in the kernel.
1987 This is an experimental much faster emulator which now also has full
1988 precision for the mantissa. It does not support any exceptions.
1989 It is very simple, and approximately 3-6 times faster than NWFPE.
1991 It should be sufficient for most programs. It may be not suitable
1992 for scientific calculations, but you have to check this for yourself.
1993 If you do not feel you need a faster FP emulation you should better
1997 bool "VFP-format floating point maths"
1998 depends on CPU_V6 || CPU_V6K || CPU_ARM926T || CPU_V7 || CPU_FEROCEON
2000 Say Y to include VFP support code in the kernel. This is needed
2001 if your hardware includes a VFP unit.
2003 Please see <file:Documentation/arm/VFP/release-notes.txt> for
2004 release notes and additional status information.
2006 Say N if your target does not have VFP hardware.
2014 bool "Advanced SIMD (NEON) Extension support"
2015 depends on VFPv3 && CPU_V7
2017 Say Y to include support code for NEON, the ARMv7 Advanced SIMD
2022 menu "Userspace binary formats"
2024 source "fs/Kconfig.binfmt"
2027 tristate "RISC OS personality"
2030 Say Y here to include the kernel code necessary if you want to run
2031 Acorn RISC OS/Arthur binaries under Linux. This code is still very
2032 experimental; if this sounds frightening, say N and sleep in peace.
2033 You can also say M here to compile this support as a module (which
2034 will be called arthur).
2038 menu "Power management options"
2040 source "kernel/power/Kconfig"
2042 config ARCH_SUSPEND_POSSIBLE
2043 depends on !ARCH_S5P64X0 && !ARCH_S5PC100
2044 depends on CPU_ARM920T || CPU_ARM926T || CPU_SA1100 || \
2045 CPU_V6 || CPU_V6K || CPU_V7 || CPU_XSC3 || CPU_XSCALE
2050 source "net/Kconfig"
2052 source "drivers/Kconfig"
2056 source "arch/arm/Kconfig.debug"
2058 source "security/Kconfig"
2060 source "crypto/Kconfig"
2062 source "lib/Kconfig"