2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
13 The ARM series is a line of low-power-consumption RISC chip designs
14 licensed by ARM Ltd and targeted at embedded applications and
15 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
16 manufactured, but legacy ARM-based PC hardware remains popular in
17 Europe. There is an ARM Linux project with a web page at
18 <http://www.arm.linux.org.uk/>.
31 The Extended Industry Standard Architecture (EISA) bus was
32 developed as an open alternative to the IBM MicroChannel bus.
34 The EISA bus provided some of the features of the IBM MicroChannel
35 bus while maintaining backward compatibility with cards made for
36 the older ISA bus. The EISA bus saw limited use between 1988 and
37 1995 when it was made obsolete by the PCI bus.
39 Say Y here if you are building a kernel for an EISA-based machine.
49 MicroChannel Architecture is found in some IBM PS/2 machines and
50 laptops. It is a bus system similar to PCI or ISA. See
51 <file:Documentation/mca.txt> (and especially the web page given
52 there) before attempting to build an MCA bus kernel.
54 config GENERIC_HARDIRQS
58 config TRACE_IRQFLAGS_SUPPORT
62 config HARDIRQS_SW_RESEND
66 config GENERIC_IRQ_PROBE
70 config RWSEM_GENERIC_SPINLOCK
74 config RWSEM_XCHGADD_ALGORITHM
77 config ARCH_HAS_ILOG2_U32
81 config ARCH_HAS_ILOG2_U64
85 config GENERIC_HWEIGHT
89 config GENERIC_CALIBRATE_DELAY
93 config GENERIC_BUST_SPINLOCK
96 config ARCH_MAY_HAVE_PC_FDC
99 config GENERIC_ISA_DMA
110 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
111 default DRAM_BASE if REMAP_VECTORS_TO_RAM
114 The base address of exception vectors.
116 source "init/Kconfig"
121 prompt "ARM system type"
122 default ARCH_VERSATILE
125 bool "Agilent AAEC-2000 based"
128 This enables support for systems based on the Agilent AAEC-2000
130 config ARCH_INTEGRATOR
131 bool "ARM Ltd. Integrator family"
135 Support for ARM's Integrator platform.
138 bool "ARM Ltd. RealView family"
142 This enables support for ARM Ltd RealView boards.
144 config ARCH_VERSATILE
145 bool "ARM Ltd. Versatile family"
150 This enables support for ARM Ltd Versatile board.
155 This enables support for systems based on the Atmel AT91RM9200
156 and AT91SAM9xxx processors.
159 bool "Cirrus CL-PS7500FE"
163 Support for the Cirrus Logic PS7500FE system-on-a-chip.
166 bool "Cirrus Logic CLPS711x/EP721x-based"
168 Support for Cirrus Logic 711x/721x based boards.
173 select FOOTBRIDGE_ADDIN
175 Support for Intel's EBSA285 companion chip.
181 This is an evaluation board for the StrongARM processor available
182 from Digital. It has limited hardware on-board, including an
183 Ethernet interface, two PCMCIA sockets, two serial ports and a
191 This enables support for the Cirrus EP93xx series of CPUs.
193 config ARCH_FOOTBRIDGE
197 Support for systems based on the DC21285 companion chip
198 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
201 bool "Hilscher NetX based"
204 This enables support for systems based on the Hilscher NetX Soc
207 bool "Hynix HMS720x-based"
210 This enables support for systems based on the Hynix HMS720x
215 Support for Motorola's i.MX family of processors (MX1, MXL).
223 Support for Intel's 80219 and IOP32X (XScale) family of
232 Support for Intel's IOP33X (XScale) family of processors.
238 Support for Intel's IOP13XX (XScale) family of processors.
245 Support for Intel's IXP4XX (XScale) family of processors.
248 bool "IXP2400/2800-based"
252 Support for Intel's IXP2400/2800 (XScale) family of processors.
259 Support for Intel's IXP23xx (XScale) family of processors.
265 Say Y here if you intend to run this kernel on a LinkUp Systems
266 L7200 Software Development Board which uses an ARM720T processor.
267 Information on this board can be obtained at:
269 <http://www.linkupsys.com/>
271 If you have any questions or comments about the Linux kernel port
272 to this board, send e-mail to <sjhill@cotw.com>.
275 bool "Philips Nexperia PNX4008 Mobile"
277 This enables support for Philips PNX4008 mobile platform.
284 Support for Intel's PXA2XX processor line.
291 select ARCH_MAY_HAVE_PC_FDC
294 On the Acorn Risc-PC, Linux can support the internal IDE disk and
295 CD-ROM interface, serial and parallel port, and the floppy drive.
300 select ARCH_DISCONTIGMEM_ENABLE
303 Support for StrongARM 11x0 based boards.
306 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
308 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
309 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
310 the Samsung SMDK2410 development board (and derivatives).
318 Support for the StrongARM based Digital DNARD machine, also known
319 as "Shark" (<http://www.shark-linux.de/shark.html>).
324 Say Y here for systems based on one of the Sharp LH7A40X
325 System on a Chip processors. These CPUs include an ARM922T
326 core with a wide array of integrated devices for
327 hand-held and low-power applications.
332 Support for TI's OMAP platform (OMAP1 and OMAP2).
336 source "arch/arm/mach-clps711x/Kconfig"
338 source "arch/arm/mach-ep93xx/Kconfig"
340 source "arch/arm/mach-footbridge/Kconfig"
342 source "arch/arm/mach-integrator/Kconfig"
344 source "arch/arm/mach-iop32x/Kconfig"
346 source "arch/arm/mach-iop33x/Kconfig"
348 source "arch/arm/mach-iop13xx/Kconfig"
350 source "arch/arm/mach-ixp4xx/Kconfig"
352 source "arch/arm/mach-ixp2000/Kconfig"
354 source "arch/arm/mach-ixp23xx/Kconfig"
356 source "arch/arm/mach-pxa/Kconfig"
358 source "arch/arm/mach-sa1100/Kconfig"
360 source "arch/arm/plat-omap/Kconfig"
362 source "arch/arm/mach-omap1/Kconfig"
364 source "arch/arm/mach-omap2/Kconfig"
366 source "arch/arm/plat-s3c24xx/Kconfig"
369 source "arch/arm/mach-s3c2400/Kconfig"
370 source "arch/arm/mach-s3c2410/Kconfig"
371 source "arch/arm/mach-s3c2412/Kconfig"
372 source "arch/arm/mach-s3c2440/Kconfig"
373 source "arch/arm/mach-s3c2442/Kconfig"
374 source "arch/arm/mach-s3c2443/Kconfig"
377 source "arch/arm/mach-lh7a40x/Kconfig"
379 source "arch/arm/mach-imx/Kconfig"
381 source "arch/arm/mach-h720x/Kconfig"
383 source "arch/arm/mach-versatile/Kconfig"
385 source "arch/arm/mach-aaec2000/Kconfig"
387 source "arch/arm/mach-realview/Kconfig"
389 source "arch/arm/mach-at91rm9200/Kconfig"
391 source "arch/arm/mach-netx/Kconfig"
393 # Definitions to make life easier
400 source arch/arm/mm/Kconfig
403 bool "Enable iWMMXt support"
404 depends CPU_XSCALE || CPU_XSC3
407 Enable support for iWMMXt context switching at run time if
408 running on a CPU that supports it.
410 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
413 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
417 source "arch/arm/Kconfig-nommu"
422 source "arch/arm/common/Kconfig"
424 config FORCE_MAX_ZONEORDER
437 Find out whether you have ISA slots on your motherboard. ISA is the
438 name of a bus system, i.e. the way the CPU talks to the other stuff
439 inside your box. Other bus systems are PCI, EISA, MicroChannel
440 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
441 newer boards don't support it. If you have ISA, say Y, otherwise N.
443 # Select ISA DMA controller support
448 # Select ISA DMA interface
453 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
455 Find out whether you have a PCI motherboard. PCI is the name of a
456 bus system, i.e. the way the CPU talks to the other stuff inside
457 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
458 VESA. If you have PCI, say Y, otherwise N.
460 The PCI-HOWTO, available from
461 <http://www.tldp.org/docs.html#howto>, contains valuable
462 information about which PCI hardware does work under Linux and which
465 # Select the host bridge type
466 config PCI_HOST_VIA82C505
468 depends on PCI && ARCH_SHARK
471 source "drivers/pci/Kconfig"
473 source "drivers/pcmcia/Kconfig"
477 menu "Kernel Features"
480 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
481 depends on EXPERIMENTAL && REALVIEW_MPCORE
483 This enables support for systems with more than one CPU. If you have
484 a system with only one CPU, like most personal computers, say N. If
485 you have a system with more than one CPU, say Y.
487 If you say N here, the kernel will run on single and multiprocessor
488 machines, but will use only one CPU of a multiprocessor machine. If
489 you say Y here, the kernel will run on many, but not all, single
490 processor machines. On a single processor machine, the kernel will
491 run faster if you say N here.
493 See also the <file:Documentation/smp.txt>,
494 <file:Documentation/i386/IO-APIC.txt>,
495 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
496 <http://www.linuxdoc.org/docs.html#howto>.
498 If you don't know what to do here, say N.
501 int "Maximum number of CPUs (2-32)"
507 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
508 depends on SMP && HOTPLUG && EXPERIMENTAL
510 Say Y here to experiment with turning CPUs off and on. CPUs
511 can be controlled through /sys/devices/system/cpu.
514 bool "Use local timer interrupts"
515 depends on SMP && REALVIEW_MPCORE
518 Enable support for local timers on SMP platforms, rather then the
519 legacy IPI broadcast method. Local timers allows the system
520 accounting to be spread across the timer interval, preventing a
521 "thundering herd" at every timer tick.
524 bool "Preemptible Kernel (EXPERIMENTAL)"
525 depends on EXPERIMENTAL
527 This option reduces the latency of the kernel when reacting to
528 real-time or interactive events by allowing a low priority process to
529 be preempted even if it is in kernel mode executing a system call.
530 This allows applications to run more reliably even when the system is
533 Say Y here if you are building a kernel for a desktop, embedded
534 or real-time system. Say N if you are unsure.
537 bool "Dynamic tick timer"
539 Select this option if you want to disable continuous timer ticks
540 and have them programmed to occur as required. This option saves
541 power as the system can remain in idle state for longer.
543 By default dynamic tick is disabled during the boot, and can be
544 manually enabled with:
546 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
548 Alternatively, if you want dynamic tick automatically enabled
549 during boot, pass "dyntick=enable" via the kernel command string.
551 Please note that dynamic tick may affect the accuracy of
552 timekeeping on some platforms depending on the implementation.
553 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
554 to have accurate timekeeping with dynamic tick.
558 default 128 if ARCH_L7200
559 default 200 if ARCH_EBSA110 || ARCH_S3C2410
560 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
564 bool "Use the ARM EABI to compile the kernel"
566 This option allows for the kernel to be compiled using the latest
567 ARM ABI (aka EABI). This is only useful if you are using a user
568 space environment that is also compiled with EABI.
570 Since there are major incompatibilities between the legacy ABI and
571 EABI, especially with regard to structure member alignment, this
572 option also changes the kernel syscall calling convention to
573 disambiguate both ABIs and allow for backward compatibility support
574 (selected with CONFIG_OABI_COMPAT).
576 To use this you need GCC version 4.0.0 or later.
579 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
580 depends on AEABI && EXPERIMENTAL
583 This option preserves the old syscall interface along with the
584 new (ARM EABI) one. It also provides a compatibility layer to
585 intercept syscalls that have structure arguments which layout
586 in memory differs between the legacy ABI and the new ARM EABI
587 (only for non "thumb" binaries). This option adds a tiny
588 overhead to all syscalls and produces a slightly larger kernel.
589 If you know you'll be using only pure EABI user space then you
590 can say N here. If this option is not selected and you attempt
591 to execute a legacy ABI binary then the result will be
592 UNPREDICTABLE (in fact it can be predicted that it won't work
593 at all). If in doubt say Y.
595 config ARCH_DISCONTIGMEM_ENABLE
597 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
599 Say Y to support efficient handling of discontiguous physical memory,
600 for architectures which are either NUMA (Non-Uniform Memory Access)
601 or have huge holes in the physical address space for other reasons.
602 See <file:Documentation/vm/numa> for more.
606 default "4" if ARCH_LH7A40X
608 depends on NEED_MULTIPLE_NODES
613 bool "Timer and CPU usage LEDs"
614 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
615 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
616 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
617 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
618 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
619 ARCH_AT91 || MACH_TRIZEPS4
621 If you say Y here, the LEDs on your machine will be used
622 to provide useful information about your current system status.
624 If you are compiling a kernel for a NetWinder or EBSA-285, you will
625 be able to select which LEDs are active using the options below. If
626 you are compiling a kernel for the EBSA-110 or the LART however, the
627 red LED will simply flash regularly to indicate that the system is
628 still functional. It is safe to say Y here if you have a CATS
629 system, but the driver will do nothing.
632 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
633 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
635 default y if ARCH_EBSA110
637 If you say Y here, one of the system LEDs (the green one on the
638 NetWinder, the amber one on the EBSA285, or the red one on the LART)
639 will flash regularly to indicate that the system is still
640 operational. This is mainly useful to kernel hackers who are
641 debugging unstable kernels.
643 The LART uses the same LED for both Timer LED and CPU usage LED
644 functions. You may choose to use both, but the Timer LED function
645 will overrule the CPU usage LED.
648 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
649 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
652 If you say Y here, the red LED will be used to give a good real
653 time indication of CPU usage, by lighting whenever the idle task
654 is not currently executing.
656 The LART uses the same LED for both Timer LED and CPU usage LED
657 functions. You may choose to use both, but the Timer LED function
658 will overrule the CPU usage LED.
660 config ALIGNMENT_TRAP
662 depends on CPU_CP15_MMU
663 default y if !ARCH_EBSA110
665 ARM processors cannot fetch/store information which is not
666 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
667 address divisible by 4. On 32-bit ARM processors, these non-aligned
668 fetch/store instructions will be emulated in software if you say
669 here, which has a severe performance impact. This is necessary for
670 correct operation of some network protocols. With an IP-only
671 configuration it is safe to say N, otherwise say Y.
677 # Compressed boot loader in ROM. Yes, we really want to ask about
678 # TEXT and BSS so we preserve their values in the config files.
679 config ZBOOT_ROM_TEXT
680 hex "Compressed ROM boot loader base address"
683 The physical address at which the ROM-able zImage is to be
684 placed in the target. Platforms which normally make use of
685 ROM-able zImage formats normally set this to a suitable
686 value in their defconfig file.
688 If ZBOOT_ROM is not enabled, this has no effect.
691 hex "Compressed ROM boot loader BSS address"
694 The base address of an area of read/write memory in the target
695 for the ROM-able zImage which must be available while the
696 decompressor is running. It must be large enough to hold the
697 entire decompressed kernel plus an additional 128 KiB.
698 Platforms which normally make use of ROM-able zImage formats
699 normally set this to a suitable value in their defconfig file.
701 If ZBOOT_ROM is not enabled, this has no effect.
704 bool "Compressed boot loader in ROM/flash"
705 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
707 Say Y here if you intend to execute your compressed kernel image
708 (zImage) directly from ROM or flash. If unsure, say N.
711 string "Default kernel command string"
714 On some architectures (EBSA110 and CATS), there is currently no way
715 for the boot loader to pass arguments to the kernel. For these
716 architectures, you should supply some command-line options at build
717 time by entering them here. As a minimum, you should specify the
718 memory size and the root device (e.g., mem=64M root=/dev/nfs).
721 bool "Kernel Execute-In-Place from ROM"
722 depends on !ZBOOT_ROM
724 Execute-In-Place allows the kernel to run from non-volatile storage
725 directly addressable by the CPU, such as NOR flash. This saves RAM
726 space since the text section of the kernel is not loaded from flash
727 to RAM. Read-write sections, such as the data section and stack,
728 are still copied to RAM. The XIP kernel is not compressed since
729 it has to run directly from flash, so it will take more space to
730 store it. The flash address used to link the kernel object files,
731 and for storing it, is configuration dependent. Therefore, if you
732 say Y here, you must know the proper physical address where to
733 store the kernel image depending on your own flash memory usage.
735 Also note that the make target becomes "make xipImage" rather than
736 "make zImage" or "make Image". The final kernel binary to put in
737 ROM memory will be arch/arm/boot/xipImage.
742 hex "XIP Kernel Physical Location"
743 depends on XIP_KERNEL
746 This is the physical address in your flash memory the kernel will
747 be linked for and stored to. This address is dependent on your
752 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
754 menu "CPU Frequency scaling"
756 source "drivers/cpufreq/Kconfig"
758 config CPU_FREQ_SA1100
760 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
763 config CPU_FREQ_SA1110
765 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
768 config CPU_FREQ_INTEGRATOR
769 tristate "CPUfreq driver for ARM Integrator CPUs"
770 depends on ARCH_INTEGRATOR && CPU_FREQ
773 This enables the CPUfreq driver for ARM Integrator CPUs.
775 For details, take a look at <file:Documentation/cpu-freq>.
780 tristate "CPUfreq driver for i.MX CPUs"
781 depends on ARCH_IMX && CPU_FREQ
784 This enables the CPUfreq driver for i.MX CPUs.
792 menu "Floating point emulation"
794 comment "At least one emulation must be selected"
797 bool "NWFPE math emulation"
798 depends on !AEABI || OABI_COMPAT
800 Say Y to include the NWFPE floating point emulator in the kernel.
801 This is necessary to run most binaries. Linux does not currently
802 support floating point hardware so you need to say Y here even if
803 your machine has an FPA or floating point co-processor podule.
805 You may say N here if you are going to load the Acorn FPEmulator
809 bool "Support extended precision"
812 Say Y to include 80-bit support in the kernel floating-point
813 emulator. Otherwise, only 32 and 64-bit support is compiled in.
814 Note that gcc does not generate 80-bit operations by default,
815 so in most cases this option only enlarges the size of the
816 floating point emulator without any good reason.
818 You almost surely want to say N here.
821 bool "FastFPE math emulation (EXPERIMENTAL)"
822 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
824 Say Y here to include the FAST floating point emulator in the kernel.
825 This is an experimental much faster emulator which now also has full
826 precision for the mantissa. It does not support any exceptions.
827 It is very simple, and approximately 3-6 times faster than NWFPE.
829 It should be sufficient for most programs. It may be not suitable
830 for scientific calculations, but you have to check this for yourself.
831 If you do not feel you need a faster FP emulation you should better
835 bool "VFP-format floating point maths"
836 depends on CPU_V6 || CPU_ARM926T
838 Say Y to include VFP support code in the kernel. This is needed
839 if your hardware includes a VFP unit.
841 Please see <file:Documentation/arm/VFP/release-notes.txt> for
842 release notes and additional status information.
844 Say N if your target does not have VFP hardware.
848 menu "Userspace binary formats"
850 source "fs/Kconfig.binfmt"
853 tristate "RISC OS personality"
856 Say Y here to include the kernel code necessary if you want to run
857 Acorn RISC OS/Arthur binaries under Linux. This code is still very
858 experimental; if this sounds frightening, say N and sleep in peace.
859 You can also say M here to compile this support as a module (which
860 will be called arthur).
864 menu "Power management options"
866 source "kernel/power/Kconfig"
869 tristate "Advanced Power Management Emulation"
871 APM is a BIOS specification for saving power using several different
872 techniques. This is mostly useful for battery powered laptops with
873 APM compliant BIOSes. If you say Y here, the system time will be
874 reset after a RESUME operation, the /proc/apm device will provide
875 battery status information, and user-space programs will receive
876 notification of APM "events" (e.g. battery status change).
878 In order to use APM, you will need supporting software. For location
879 and more information, read <file:Documentation/pm.txt> and the
880 Battery Powered Linux mini-HOWTO, available from
881 <http://www.tldp.org/docs.html#howto>.
883 This driver does not spin down disk drives (see the hdparm(8)
884 manpage ("man 8 hdparm") for that), and it doesn't turn off
885 VESA-compliant "green" monitors.
887 Generally, if you don't have a battery in your machine, there isn't
888 much point in using this driver and you should say N. If you get
889 random kernel OOPSes or reboots that don't seem to be related to
890 anything, try disabling/enabling this option (or disabling/enabling
897 menu "Device Drivers"
899 source "drivers/base/Kconfig"
901 source "drivers/connector/Kconfig"
903 if ALIGNMENT_TRAP || !CPU_CP15_MMU
904 source "drivers/mtd/Kconfig"
907 source "drivers/parport/Kconfig"
909 source "drivers/pnp/Kconfig"
911 source "drivers/block/Kconfig"
913 source "drivers/acorn/block/Kconfig"
915 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
916 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
917 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
919 source "drivers/ide/Kconfig"
922 source "drivers/scsi/Kconfig"
924 source "drivers/ata/Kconfig"
926 source "drivers/md/Kconfig"
928 source "drivers/message/fusion/Kconfig"
930 source "drivers/ieee1394/Kconfig"
932 source "drivers/message/i2o/Kconfig"
934 source "drivers/net/Kconfig"
936 source "drivers/isdn/Kconfig"
938 # input before char - char/joystick depends on it. As does USB.
940 source "drivers/input/Kconfig"
942 source "drivers/char/Kconfig"
944 source "drivers/i2c/Kconfig"
946 source "drivers/spi/Kconfig"
948 source "drivers/w1/Kconfig"
950 source "drivers/hwmon/Kconfig"
952 #source "drivers/l3/Kconfig"
954 source "drivers/misc/Kconfig"
956 source "drivers/mfd/Kconfig"
958 source "drivers/leds/Kconfig"
960 source "drivers/media/Kconfig"
962 source "drivers/video/Kconfig"
964 source "sound/Kconfig"
966 source "drivers/hid/Kconfig"
968 source "drivers/usb/Kconfig"
970 source "drivers/mmc/Kconfig"
972 source "drivers/rtc/Kconfig"
978 source "arch/arm/oprofile/Kconfig"
980 source "arch/arm/Kconfig.debug"
982 source "security/Kconfig"
984 source "crypto/Kconfig"