2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
12 select SYS_SUPPORTS_APM_EMULATION
14 The ARM series is a line of low-power-consumption RISC chip designs
15 licensed by ARM Ltd and targeted at embedded applications and
16 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
17 manufactured, but legacy ARM-based PC hardware remains popular in
18 Europe. There is an ARM Linux project with a web page at
19 <http://www.arm.linux.org.uk/>.
21 config SYS_SUPPORTS_APM_EMULATION
39 The Extended Industry Standard Architecture (EISA) bus was
40 developed as an open alternative to the IBM MicroChannel bus.
42 The EISA bus provided some of the features of the IBM MicroChannel
43 bus while maintaining backward compatibility with cards made for
44 the older ISA bus. The EISA bus saw limited use between 1988 and
45 1995 when it was made obsolete by the PCI bus.
47 Say Y here if you are building a kernel for an EISA-based machine.
57 MicroChannel Architecture is found in some IBM PS/2 machines and
58 laptops. It is a bus system similar to PCI or ISA. See
59 <file:Documentation/mca.txt> (and especially the web page given
60 there) before attempting to build an MCA bus kernel.
62 config GENERIC_HARDIRQS
66 config TRACE_IRQFLAGS_SUPPORT
70 config HARDIRQS_SW_RESEND
74 config GENERIC_IRQ_PROBE
78 config RWSEM_GENERIC_SPINLOCK
82 config RWSEM_XCHGADD_ALGORITHM
85 config ARCH_HAS_ILOG2_U32
89 config ARCH_HAS_ILOG2_U64
93 config GENERIC_HWEIGHT
97 config GENERIC_CALIBRATE_DELAY
101 config GENERIC_BUST_SPINLOCK
104 config ARCH_MAY_HAVE_PC_FDC
111 config GENERIC_ISA_DMA
122 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
123 default DRAM_BASE if REMAP_VECTORS_TO_RAM
126 The base address of exception vectors.
128 source "init/Kconfig"
133 prompt "ARM system type"
134 default ARCH_VERSATILE
137 bool "Agilent AAEC-2000 based"
140 This enables support for systems based on the Agilent AAEC-2000
142 config ARCH_INTEGRATOR
143 bool "ARM Ltd. Integrator family"
147 Support for ARM's Integrator platform.
150 bool "ARM Ltd. RealView family"
154 This enables support for ARM Ltd RealView boards.
156 config ARCH_VERSATILE
157 bool "ARM Ltd. Versatile family"
162 This enables support for ARM Ltd Versatile board.
167 This enables support for systems based on the Atmel AT91RM9200
168 and AT91SAM9xxx processors.
171 bool "Cirrus CL-PS7500FE"
176 Support for the Cirrus Logic PS7500FE system-on-a-chip.
179 bool "Cirrus Logic CLPS711x/EP721x-based"
181 Support for Cirrus Logic 711x/721x based boards.
186 select FOOTBRIDGE_ADDIN
188 Support for Intel's EBSA285 companion chip.
194 This is an evaluation board for the StrongARM processor available
195 from Digital. It has limited hardware on-board, including an
196 Ethernet interface, two PCMCIA sockets, two serial ports and a
204 This enables support for the Cirrus EP93xx series of CPUs.
206 config ARCH_FOOTBRIDGE
210 Support for systems based on the DC21285 companion chip
211 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
214 bool "Hilscher NetX based"
217 This enables support for systems based on the Hilscher NetX Soc
220 bool "Hynix HMS720x-based"
223 This enables support for systems based on the Hynix HMS720x
228 Support for Motorola's i.MX family of processors (MX1, MXL).
236 Support for Intel's 80219 and IOP32X (XScale) family of
245 Support for Intel's IOP33X (XScale) family of processors.
253 Support for Intel's IOP13XX (XScale) family of processors.
260 Support for Intel's IXP4XX (XScale) family of processors.
263 bool "IXP2400/2800-based"
267 Support for Intel's IXP2400/2800 (XScale) family of processors.
274 Support for Intel's IXP23xx (XScale) family of processors.
280 Say Y here if you intend to run this kernel on a LinkUp Systems
281 L7200 Software Development Board which uses an ARM720T processor.
282 Information on this board can be obtained at:
284 <http://www.linkupsys.com/>
286 If you have any questions or comments about the Linux kernel port
287 to this board, send e-mail to <sjhill@cotw.com>.
290 bool "NetSilicon NS9xxx"
292 Say Y here if you intend to run this kernel on a NetSilicon NS9xxx
295 <http://www.digi.com/products/microprocessors/index.jsp>
298 bool "Philips Nexperia PNX4008 Mobile"
300 This enables support for Philips PNX4008 mobile platform.
308 Support for Intel's PXA2XX processor line.
315 select ARCH_MAY_HAVE_PC_FDC
319 On the Acorn Risc-PC, Linux can support the internal IDE disk and
320 CD-ROM interface, serial and parallel port, and the floppy drive.
325 select ARCH_DISCONTIGMEM_ENABLE
328 Support for StrongARM 11x0 based boards.
331 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
333 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
334 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
335 the Samsung SMDK2410 development board (and derivatives).
343 Support for the StrongARM based Digital DNARD machine, also known
344 as "Shark" (<http://www.shark-linux.de/shark.html>).
349 Say Y here for systems based on one of the Sharp LH7A40X
350 System on a Chip processors. These CPUs include an ARM922T
351 core with a wide array of integrated devices for
352 hand-held and low-power applications.
357 Support for TI's OMAP platform (OMAP1 and OMAP2).
361 source "arch/arm/mach-clps711x/Kconfig"
363 source "arch/arm/mach-ep93xx/Kconfig"
365 source "arch/arm/mach-footbridge/Kconfig"
367 source "arch/arm/mach-integrator/Kconfig"
369 source "arch/arm/mach-iop32x/Kconfig"
371 source "arch/arm/mach-iop33x/Kconfig"
373 source "arch/arm/mach-iop13xx/Kconfig"
375 source "arch/arm/mach-ixp4xx/Kconfig"
377 source "arch/arm/mach-ixp2000/Kconfig"
379 source "arch/arm/mach-ixp23xx/Kconfig"
381 source "arch/arm/mach-pxa/Kconfig"
383 source "arch/arm/mach-sa1100/Kconfig"
385 source "arch/arm/plat-omap/Kconfig"
387 source "arch/arm/mach-omap1/Kconfig"
389 source "arch/arm/mach-omap2/Kconfig"
391 source "arch/arm/plat-s3c24xx/Kconfig"
394 source "arch/arm/mach-s3c2400/Kconfig"
395 source "arch/arm/mach-s3c2410/Kconfig"
396 source "arch/arm/mach-s3c2412/Kconfig"
397 source "arch/arm/mach-s3c2440/Kconfig"
398 source "arch/arm/mach-s3c2442/Kconfig"
399 source "arch/arm/mach-s3c2443/Kconfig"
402 source "arch/arm/mach-lh7a40x/Kconfig"
404 source "arch/arm/mach-imx/Kconfig"
406 source "arch/arm/mach-h720x/Kconfig"
408 source "arch/arm/mach-versatile/Kconfig"
410 source "arch/arm/mach-aaec2000/Kconfig"
412 source "arch/arm/mach-realview/Kconfig"
414 source "arch/arm/mach-at91/Kconfig"
416 source "arch/arm/mach-netx/Kconfig"
418 source "arch/arm/mach-ns9xxx/Kconfig"
420 # Definitions to make life easier
427 source arch/arm/mm/Kconfig
430 bool "Enable iWMMXt support"
431 depends on CPU_XSCALE || CPU_XSC3
434 Enable support for iWMMXt context switching at run time if
435 running on a CPU that supports it.
437 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
440 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
444 source "arch/arm/Kconfig-nommu"
449 source "arch/arm/common/Kconfig"
451 config FORCE_MAX_ZONEORDER
464 Find out whether you have ISA slots on your motherboard. ISA is the
465 name of a bus system, i.e. the way the CPU talks to the other stuff
466 inside your box. Other bus systems are PCI, EISA, MicroChannel
467 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
468 newer boards don't support it. If you have ISA, say Y, otherwise N.
470 # Select ISA DMA controller support
475 # Select ISA DMA interface
480 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
482 Find out whether you have a PCI motherboard. PCI is the name of a
483 bus system, i.e. the way the CPU talks to the other stuff inside
484 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
485 VESA. If you have PCI, say Y, otherwise N.
487 The PCI-HOWTO, available from
488 <http://www.tldp.org/docs.html#howto>, contains valuable
489 information about which PCI hardware does work under Linux and which
492 # Select the host bridge type
493 config PCI_HOST_VIA82C505
495 depends on PCI && ARCH_SHARK
498 source "drivers/pci/Kconfig"
500 source "drivers/pcmcia/Kconfig"
504 menu "Kernel Features"
507 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
508 depends on EXPERIMENTAL && REALVIEW_MPCORE
510 This enables support for systems with more than one CPU. If you have
511 a system with only one CPU, like most personal computers, say N. If
512 you have a system with more than one CPU, say Y.
514 If you say N here, the kernel will run on single and multiprocessor
515 machines, but will use only one CPU of a multiprocessor machine. If
516 you say Y here, the kernel will run on many, but not all, single
517 processor machines. On a single processor machine, the kernel will
518 run faster if you say N here.
520 See also the <file:Documentation/smp.txt>,
521 <file:Documentation/i386/IO-APIC.txt>,
522 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
523 <http://www.linuxdoc.org/docs.html#howto>.
525 If you don't know what to do here, say N.
528 int "Maximum number of CPUs (2-32)"
534 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
535 depends on SMP && HOTPLUG && EXPERIMENTAL
537 Say Y here to experiment with turning CPUs off and on. CPUs
538 can be controlled through /sys/devices/system/cpu.
541 bool "Use local timer interrupts"
542 depends on SMP && REALVIEW_MPCORE
545 Enable support for local timers on SMP platforms, rather then the
546 legacy IPI broadcast method. Local timers allows the system
547 accounting to be spread across the timer interval, preventing a
548 "thundering herd" at every timer tick.
551 bool "Preemptible Kernel (EXPERIMENTAL)"
552 depends on EXPERIMENTAL
554 This option reduces the latency of the kernel when reacting to
555 real-time or interactive events by allowing a low priority process to
556 be preempted even if it is in kernel mode executing a system call.
557 This allows applications to run more reliably even when the system is
560 Say Y here if you are building a kernel for a desktop, embedded
561 or real-time system. Say N if you are unsure.
564 bool "Dynamic tick timer"
566 Select this option if you want to disable continuous timer ticks
567 and have them programmed to occur as required. This option saves
568 power as the system can remain in idle state for longer.
570 By default dynamic tick is disabled during the boot, and can be
571 manually enabled with:
573 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
575 Alternatively, if you want dynamic tick automatically enabled
576 during boot, pass "dyntick=enable" via the kernel command string.
578 Please note that dynamic tick may affect the accuracy of
579 timekeeping on some platforms depending on the implementation.
580 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
581 to have accurate timekeeping with dynamic tick.
585 default 128 if ARCH_L7200
586 default 200 if ARCH_EBSA110 || ARCH_S3C2410
587 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
591 bool "Use the ARM EABI to compile the kernel"
593 This option allows for the kernel to be compiled using the latest
594 ARM ABI (aka EABI). This is only useful if you are using a user
595 space environment that is also compiled with EABI.
597 Since there are major incompatibilities between the legacy ABI and
598 EABI, especially with regard to structure member alignment, this
599 option also changes the kernel syscall calling convention to
600 disambiguate both ABIs and allow for backward compatibility support
601 (selected with CONFIG_OABI_COMPAT).
603 To use this you need GCC version 4.0.0 or later.
606 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
607 depends on AEABI && EXPERIMENTAL
610 This option preserves the old syscall interface along with the
611 new (ARM EABI) one. It also provides a compatibility layer to
612 intercept syscalls that have structure arguments which layout
613 in memory differs between the legacy ABI and the new ARM EABI
614 (only for non "thumb" binaries). This option adds a tiny
615 overhead to all syscalls and produces a slightly larger kernel.
616 If you know you'll be using only pure EABI user space then you
617 can say N here. If this option is not selected and you attempt
618 to execute a legacy ABI binary then the result will be
619 UNPREDICTABLE (in fact it can be predicted that it won't work
620 at all). If in doubt say Y.
622 config ARCH_DISCONTIGMEM_ENABLE
624 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
626 Say Y to support efficient handling of discontiguous physical memory,
627 for architectures which are either NUMA (Non-Uniform Memory Access)
628 or have huge holes in the physical address space for other reasons.
629 See <file:Documentation/vm/numa> for more.
633 default "4" if ARCH_LH7A40X
635 depends on NEED_MULTIPLE_NODES
640 bool "Timer and CPU usage LEDs"
641 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
642 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
643 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
644 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
645 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
646 ARCH_AT91 || MACH_TRIZEPS4
648 If you say Y here, the LEDs on your machine will be used
649 to provide useful information about your current system status.
651 If you are compiling a kernel for a NetWinder or EBSA-285, you will
652 be able to select which LEDs are active using the options below. If
653 you are compiling a kernel for the EBSA-110 or the LART however, the
654 red LED will simply flash regularly to indicate that the system is
655 still functional. It is safe to say Y here if you have a CATS
656 system, but the driver will do nothing.
659 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
660 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
662 default y if ARCH_EBSA110
664 If you say Y here, one of the system LEDs (the green one on the
665 NetWinder, the amber one on the EBSA285, or the red one on the LART)
666 will flash regularly to indicate that the system is still
667 operational. This is mainly useful to kernel hackers who are
668 debugging unstable kernels.
670 The LART uses the same LED for both Timer LED and CPU usage LED
671 functions. You may choose to use both, but the Timer LED function
672 will overrule the CPU usage LED.
675 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
676 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
679 If you say Y here, the red LED will be used to give a good real
680 time indication of CPU usage, by lighting whenever the idle task
681 is not currently executing.
683 The LART uses the same LED for both Timer LED and CPU usage LED
684 functions. You may choose to use both, but the Timer LED function
685 will overrule the CPU usage LED.
687 config ALIGNMENT_TRAP
689 depends on CPU_CP15_MMU
690 default y if !ARCH_EBSA110
692 ARM processors cannot fetch/store information which is not
693 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
694 address divisible by 4. On 32-bit ARM processors, these non-aligned
695 fetch/store instructions will be emulated in software if you say
696 here, which has a severe performance impact. This is necessary for
697 correct operation of some network protocols. With an IP-only
698 configuration it is safe to say N, otherwise say Y.
704 # Compressed boot loader in ROM. Yes, we really want to ask about
705 # TEXT and BSS so we preserve their values in the config files.
706 config ZBOOT_ROM_TEXT
707 hex "Compressed ROM boot loader base address"
710 The physical address at which the ROM-able zImage is to be
711 placed in the target. Platforms which normally make use of
712 ROM-able zImage formats normally set this to a suitable
713 value in their defconfig file.
715 If ZBOOT_ROM is not enabled, this has no effect.
718 hex "Compressed ROM boot loader BSS address"
721 The base address of an area of read/write memory in the target
722 for the ROM-able zImage which must be available while the
723 decompressor is running. It must be large enough to hold the
724 entire decompressed kernel plus an additional 128 KiB.
725 Platforms which normally make use of ROM-able zImage formats
726 normally set this to a suitable value in their defconfig file.
728 If ZBOOT_ROM is not enabled, this has no effect.
731 bool "Compressed boot loader in ROM/flash"
732 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
734 Say Y here if you intend to execute your compressed kernel image
735 (zImage) directly from ROM or flash. If unsure, say N.
738 string "Default kernel command string"
741 On some architectures (EBSA110 and CATS), there is currently no way
742 for the boot loader to pass arguments to the kernel. For these
743 architectures, you should supply some command-line options at build
744 time by entering them here. As a minimum, you should specify the
745 memory size and the root device (e.g., mem=64M root=/dev/nfs).
748 bool "Kernel Execute-In-Place from ROM"
749 depends on !ZBOOT_ROM
751 Execute-In-Place allows the kernel to run from non-volatile storage
752 directly addressable by the CPU, such as NOR flash. This saves RAM
753 space since the text section of the kernel is not loaded from flash
754 to RAM. Read-write sections, such as the data section and stack,
755 are still copied to RAM. The XIP kernel is not compressed since
756 it has to run directly from flash, so it will take more space to
757 store it. The flash address used to link the kernel object files,
758 and for storing it, is configuration dependent. Therefore, if you
759 say Y here, you must know the proper physical address where to
760 store the kernel image depending on your own flash memory usage.
762 Also note that the make target becomes "make xipImage" rather than
763 "make zImage" or "make Image". The final kernel binary to put in
764 ROM memory will be arch/arm/boot/xipImage.
769 hex "XIP Kernel Physical Location"
770 depends on XIP_KERNEL
773 This is the physical address in your flash memory the kernel will
774 be linked for and stored to. This address is dependent on your
778 bool "Kexec system call (EXPERIMENTAL)"
779 depends on EXPERIMENTAL
781 kexec is a system call that implements the ability to shutdown your
782 current kernel, and to start another kernel. It is like a reboot
783 but it is indepedent of the system firmware. And like a reboot
784 you can start any kernel with it, not just Linux.
786 It is an ongoing process to be certain the hardware in a machine
787 is properly shutdown, so do not be surprised if this code does not
788 initially work for you. It may help to enable device hotplugging
793 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
795 menu "CPU Frequency scaling"
797 source "drivers/cpufreq/Kconfig"
799 config CPU_FREQ_SA1100
801 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
804 config CPU_FREQ_SA1110
806 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
809 config CPU_FREQ_INTEGRATOR
810 tristate "CPUfreq driver for ARM Integrator CPUs"
811 depends on ARCH_INTEGRATOR && CPU_FREQ
814 This enables the CPUfreq driver for ARM Integrator CPUs.
816 For details, take a look at <file:Documentation/cpu-freq>.
821 tristate "CPUfreq driver for i.MX CPUs"
822 depends on ARCH_IMX && CPU_FREQ
825 This enables the CPUfreq driver for i.MX CPUs.
833 menu "Floating point emulation"
835 comment "At least one emulation must be selected"
838 bool "NWFPE math emulation"
839 depends on !AEABI || OABI_COMPAT
841 Say Y to include the NWFPE floating point emulator in the kernel.
842 This is necessary to run most binaries. Linux does not currently
843 support floating point hardware so you need to say Y here even if
844 your machine has an FPA or floating point co-processor podule.
846 You may say N here if you are going to load the Acorn FPEmulator
850 bool "Support extended precision"
853 Say Y to include 80-bit support in the kernel floating-point
854 emulator. Otherwise, only 32 and 64-bit support is compiled in.
855 Note that gcc does not generate 80-bit operations by default,
856 so in most cases this option only enlarges the size of the
857 floating point emulator without any good reason.
859 You almost surely want to say N here.
862 bool "FastFPE math emulation (EXPERIMENTAL)"
863 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
865 Say Y here to include the FAST floating point emulator in the kernel.
866 This is an experimental much faster emulator which now also has full
867 precision for the mantissa. It does not support any exceptions.
868 It is very simple, and approximately 3-6 times faster than NWFPE.
870 It should be sufficient for most programs. It may be not suitable
871 for scientific calculations, but you have to check this for yourself.
872 If you do not feel you need a faster FP emulation you should better
876 bool "VFP-format floating point maths"
877 depends on CPU_V6 || CPU_ARM926T
879 Say Y to include VFP support code in the kernel. This is needed
880 if your hardware includes a VFP unit.
882 Please see <file:Documentation/arm/VFP/release-notes.txt> for
883 release notes and additional status information.
885 Say N if your target does not have VFP hardware.
889 menu "Userspace binary formats"
891 source "fs/Kconfig.binfmt"
894 tristate "RISC OS personality"
897 Say Y here to include the kernel code necessary if you want to run
898 Acorn RISC OS/Arthur binaries under Linux. This code is still very
899 experimental; if this sounds frightening, say N and sleep in peace.
900 You can also say M here to compile this support as a module (which
901 will be called arthur).
905 menu "Power management options"
907 source "kernel/power/Kconfig"
913 menu "Device Drivers"
915 source "drivers/base/Kconfig"
917 source "drivers/connector/Kconfig"
919 if ALIGNMENT_TRAP || !CPU_CP15_MMU
920 source "drivers/mtd/Kconfig"
923 source "drivers/parport/Kconfig"
925 source "drivers/pnp/Kconfig"
927 source "drivers/block/Kconfig"
929 source "drivers/acorn/block/Kconfig"
931 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
932 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
933 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
935 source "drivers/ide/Kconfig"
938 source "drivers/scsi/Kconfig"
940 source "drivers/ata/Kconfig"
942 source "drivers/md/Kconfig"
944 source "drivers/message/fusion/Kconfig"
946 source "drivers/ieee1394/Kconfig"
948 source "drivers/message/i2o/Kconfig"
950 source "drivers/net/Kconfig"
952 source "drivers/isdn/Kconfig"
954 # input before char - char/joystick depends on it. As does USB.
956 source "drivers/input/Kconfig"
958 source "drivers/char/Kconfig"
960 source "drivers/i2c/Kconfig"
962 source "drivers/spi/Kconfig"
964 source "drivers/w1/Kconfig"
966 source "drivers/hwmon/Kconfig"
968 #source "drivers/l3/Kconfig"
970 source "drivers/misc/Kconfig"
972 source "drivers/mfd/Kconfig"
974 source "drivers/leds/Kconfig"
976 source "drivers/media/Kconfig"
978 source "drivers/video/Kconfig"
980 source "sound/Kconfig"
982 source "drivers/hid/Kconfig"
984 source "drivers/usb/Kconfig"
986 source "drivers/mmc/Kconfig"
988 source "drivers/rtc/Kconfig"
994 source "arch/arm/oprofile/Kconfig"
996 source "arch/arm/Kconfig.debug"
998 source "security/Kconfig"
1000 source "crypto/Kconfig"
1002 source "lib/Kconfig"