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.
195 This is an evaluation board for the StrongARM processor available
196 from Digital. It has limited hardware on-board, including an
197 Ethernet interface, two PCMCIA sockets, two serial ports and a
205 This enables support for the Cirrus EP93xx series of CPUs.
207 config ARCH_FOOTBRIDGE
211 Support for systems based on the DC21285 companion chip
212 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
215 bool "Hilscher NetX based"
218 This enables support for systems based on the Hilscher NetX Soc
221 bool "Hynix HMS720x-based"
224 This enables support for systems based on the Hynix HMS720x
229 Support for Motorola's i.MX family of processors (MX1, MXL).
237 Support for Intel's 80219 and IOP32X (XScale) family of
246 Support for Intel's IOP33X (XScale) family of processors.
254 Support for Intel's IOP13XX (XScale) family of processors.
261 Support for Intel's IXP4XX (XScale) family of processors.
264 bool "IXP2400/2800-based"
268 Support for Intel's IXP2400/2800 (XScale) family of processors.
275 Support for Intel's IXP23xx (XScale) family of processors.
281 Say Y here if you intend to run this kernel on a LinkUp Systems
282 L7200 Software Development Board which uses an ARM720T processor.
283 Information on this board can be obtained at:
285 <http://www.linkupsys.com/>
287 If you have any questions or comments about the Linux kernel port
288 to this board, send e-mail to <sjhill@cotw.com>.
291 bool "NetSilicon NS9xxx"
293 Say Y here if you intend to run this kernel on a NetSilicon NS9xxx
296 <http://www.digi.com/products/microprocessors/index.jsp>
299 bool "Philips Nexperia PNX4008 Mobile"
301 This enables support for Philips PNX4008 mobile platform.
309 Support for Intel's PXA2XX processor line.
316 select ARCH_MAY_HAVE_PC_FDC
320 On the Acorn Risc-PC, Linux can support the internal IDE disk and
321 CD-ROM interface, serial and parallel port, and the floppy drive.
326 select ARCH_DISCONTIGMEM_ENABLE
329 Support for StrongARM 11x0 based boards.
332 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
334 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
335 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
336 the Samsung SMDK2410 development board (and derivatives).
344 Support for the StrongARM based Digital DNARD machine, also known
345 as "Shark" (<http://www.shark-linux.de/shark.html>).
350 Say Y here for systems based on one of the Sharp LH7A40X
351 System on a Chip processors. These CPUs include an ARM922T
352 core with a wide array of integrated devices for
353 hand-held and low-power applications.
358 Support for TI's OMAP platform (OMAP1 and OMAP2).
362 source "arch/arm/mach-clps711x/Kconfig"
364 source "arch/arm/mach-ep93xx/Kconfig"
366 source "arch/arm/mach-footbridge/Kconfig"
368 source "arch/arm/mach-integrator/Kconfig"
370 source "arch/arm/mach-iop32x/Kconfig"
372 source "arch/arm/mach-iop33x/Kconfig"
374 source "arch/arm/mach-iop13xx/Kconfig"
376 source "arch/arm/mach-ixp4xx/Kconfig"
378 source "arch/arm/mach-ixp2000/Kconfig"
380 source "arch/arm/mach-ixp23xx/Kconfig"
382 source "arch/arm/mach-pxa/Kconfig"
384 source "arch/arm/mach-sa1100/Kconfig"
386 source "arch/arm/plat-omap/Kconfig"
388 source "arch/arm/mach-omap1/Kconfig"
390 source "arch/arm/mach-omap2/Kconfig"
392 source "arch/arm/plat-s3c24xx/Kconfig"
395 source "arch/arm/mach-s3c2400/Kconfig"
396 source "arch/arm/mach-s3c2410/Kconfig"
397 source "arch/arm/mach-s3c2412/Kconfig"
398 source "arch/arm/mach-s3c2440/Kconfig"
399 source "arch/arm/mach-s3c2442/Kconfig"
400 source "arch/arm/mach-s3c2443/Kconfig"
403 source "arch/arm/mach-lh7a40x/Kconfig"
405 source "arch/arm/mach-imx/Kconfig"
407 source "arch/arm/mach-h720x/Kconfig"
409 source "arch/arm/mach-versatile/Kconfig"
411 source "arch/arm/mach-aaec2000/Kconfig"
413 source "arch/arm/mach-realview/Kconfig"
415 source "arch/arm/mach-at91/Kconfig"
417 source "arch/arm/mach-netx/Kconfig"
419 source "arch/arm/mach-ns9xxx/Kconfig"
421 # Definitions to make life easier
428 source arch/arm/mm/Kconfig
431 bool "Enable iWMMXt support"
432 depends on CPU_XSCALE || CPU_XSC3
435 Enable support for iWMMXt context switching at run time if
436 running on a CPU that supports it.
438 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
441 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
445 source "arch/arm/Kconfig-nommu"
450 source "arch/arm/common/Kconfig"
452 config FORCE_MAX_ZONEORDER
465 Find out whether you have ISA slots on your motherboard. ISA is the
466 name of a bus system, i.e. the way the CPU talks to the other stuff
467 inside your box. Other bus systems are PCI, EISA, MicroChannel
468 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
469 newer boards don't support it. If you have ISA, say Y, otherwise N.
471 # Select ISA DMA controller support
476 # Select ISA DMA interface
481 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
483 Find out whether you have a PCI motherboard. PCI is the name of a
484 bus system, i.e. the way the CPU talks to the other stuff inside
485 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
486 VESA. If you have PCI, say Y, otherwise N.
488 The PCI-HOWTO, available from
489 <http://www.tldp.org/docs.html#howto>, contains valuable
490 information about which PCI hardware does work under Linux and which
493 # Select the host bridge type
494 config PCI_HOST_VIA82C505
496 depends on PCI && ARCH_SHARK
499 source "drivers/pci/Kconfig"
501 source "drivers/pcmcia/Kconfig"
505 menu "Kernel Features"
508 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
509 depends on EXPERIMENTAL && REALVIEW_MPCORE
511 This enables support for systems with more than one CPU. If you have
512 a system with only one CPU, like most personal computers, say N. If
513 you have a system with more than one CPU, say Y.
515 If you say N here, the kernel will run on single and multiprocessor
516 machines, but will use only one CPU of a multiprocessor machine. If
517 you say Y here, the kernel will run on many, but not all, single
518 processor machines. On a single processor machine, the kernel will
519 run faster if you say N here.
521 See also the <file:Documentation/smp.txt>,
522 <file:Documentation/i386/IO-APIC.txt>,
523 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
524 <http://www.linuxdoc.org/docs.html#howto>.
526 If you don't know what to do here, say N.
529 int "Maximum number of CPUs (2-32)"
535 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
536 depends on SMP && HOTPLUG && EXPERIMENTAL
538 Say Y here to experiment with turning CPUs off and on. CPUs
539 can be controlled through /sys/devices/system/cpu.
542 bool "Use local timer interrupts"
543 depends on SMP && REALVIEW_MPCORE
546 Enable support for local timers on SMP platforms, rather then the
547 legacy IPI broadcast method. Local timers allows the system
548 accounting to be spread across the timer interval, preventing a
549 "thundering herd" at every timer tick.
552 bool "Preemptible Kernel (EXPERIMENTAL)"
553 depends on EXPERIMENTAL
555 This option reduces the latency of the kernel when reacting to
556 real-time or interactive events by allowing a low priority process to
557 be preempted even if it is in kernel mode executing a system call.
558 This allows applications to run more reliably even when the system is
561 Say Y here if you are building a kernel for a desktop, embedded
562 or real-time system. Say N if you are unsure.
565 bool "Dynamic tick timer"
567 Select this option if you want to disable continuous timer ticks
568 and have them programmed to occur as required. This option saves
569 power as the system can remain in idle state for longer.
571 By default dynamic tick is disabled during the boot, and can be
572 manually enabled with:
574 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
576 Alternatively, if you want dynamic tick automatically enabled
577 during boot, pass "dyntick=enable" via the kernel command string.
579 Please note that dynamic tick may affect the accuracy of
580 timekeeping on some platforms depending on the implementation.
581 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
582 to have accurate timekeeping with dynamic tick.
586 default 128 if ARCH_L7200
587 default 200 if ARCH_EBSA110 || ARCH_S3C2410
588 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
592 bool "Use the ARM EABI to compile the kernel"
594 This option allows for the kernel to be compiled using the latest
595 ARM ABI (aka EABI). This is only useful if you are using a user
596 space environment that is also compiled with EABI.
598 Since there are major incompatibilities between the legacy ABI and
599 EABI, especially with regard to structure member alignment, this
600 option also changes the kernel syscall calling convention to
601 disambiguate both ABIs and allow for backward compatibility support
602 (selected with CONFIG_OABI_COMPAT).
604 To use this you need GCC version 4.0.0 or later.
607 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
608 depends on AEABI && EXPERIMENTAL
611 This option preserves the old syscall interface along with the
612 new (ARM EABI) one. It also provides a compatibility layer to
613 intercept syscalls that have structure arguments which layout
614 in memory differs between the legacy ABI and the new ARM EABI
615 (only for non "thumb" binaries). This option adds a tiny
616 overhead to all syscalls and produces a slightly larger kernel.
617 If you know you'll be using only pure EABI user space then you
618 can say N here. If this option is not selected and you attempt
619 to execute a legacy ABI binary then the result will be
620 UNPREDICTABLE (in fact it can be predicted that it won't work
621 at all). If in doubt say Y.
623 config ARCH_DISCONTIGMEM_ENABLE
625 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
627 Say Y to support efficient handling of discontiguous physical memory,
628 for architectures which are either NUMA (Non-Uniform Memory Access)
629 or have huge holes in the physical address space for other reasons.
630 See <file:Documentation/vm/numa> for more.
634 default "4" if ARCH_LH7A40X
636 depends on NEED_MULTIPLE_NODES
641 bool "Timer and CPU usage LEDs"
642 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
643 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
644 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
645 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
646 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
647 ARCH_AT91 || MACH_TRIZEPS4
649 If you say Y here, the LEDs on your machine will be used
650 to provide useful information about your current system status.
652 If you are compiling a kernel for a NetWinder or EBSA-285, you will
653 be able to select which LEDs are active using the options below. If
654 you are compiling a kernel for the EBSA-110 or the LART however, the
655 red LED will simply flash regularly to indicate that the system is
656 still functional. It is safe to say Y here if you have a CATS
657 system, but the driver will do nothing.
660 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
661 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
663 default y if ARCH_EBSA110
665 If you say Y here, one of the system LEDs (the green one on the
666 NetWinder, the amber one on the EBSA285, or the red one on the LART)
667 will flash regularly to indicate that the system is still
668 operational. This is mainly useful to kernel hackers who are
669 debugging unstable kernels.
671 The LART uses the same LED for both Timer LED and CPU usage LED
672 functions. You may choose to use both, but the Timer LED function
673 will overrule the CPU usage LED.
676 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
677 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
680 If you say Y here, the red LED will be used to give a good real
681 time indication of CPU usage, by lighting whenever the idle task
682 is not currently executing.
684 The LART uses the same LED for both Timer LED and CPU usage LED
685 functions. You may choose to use both, but the Timer LED function
686 will overrule the CPU usage LED.
688 config ALIGNMENT_TRAP
690 depends on CPU_CP15_MMU
691 default y if !ARCH_EBSA110
693 ARM processors cannot fetch/store information which is not
694 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
695 address divisible by 4. On 32-bit ARM processors, these non-aligned
696 fetch/store instructions will be emulated in software if you say
697 here, which has a severe performance impact. This is necessary for
698 correct operation of some network protocols. With an IP-only
699 configuration it is safe to say N, otherwise say Y.
705 # Compressed boot loader in ROM. Yes, we really want to ask about
706 # TEXT and BSS so we preserve their values in the config files.
707 config ZBOOT_ROM_TEXT
708 hex "Compressed ROM boot loader base address"
711 The physical address at which the ROM-able zImage is to be
712 placed in the target. Platforms which normally make use of
713 ROM-able zImage formats normally set this to a suitable
714 value in their defconfig file.
716 If ZBOOT_ROM is not enabled, this has no effect.
719 hex "Compressed ROM boot loader BSS address"
722 The base address of an area of read/write memory in the target
723 for the ROM-able zImage which must be available while the
724 decompressor is running. It must be large enough to hold the
725 entire decompressed kernel plus an additional 128 KiB.
726 Platforms which normally make use of ROM-able zImage formats
727 normally set this to a suitable value in their defconfig file.
729 If ZBOOT_ROM is not enabled, this has no effect.
732 bool "Compressed boot loader in ROM/flash"
733 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
735 Say Y here if you intend to execute your compressed kernel image
736 (zImage) directly from ROM or flash. If unsure, say N.
739 string "Default kernel command string"
742 On some architectures (EBSA110 and CATS), there is currently no way
743 for the boot loader to pass arguments to the kernel. For these
744 architectures, you should supply some command-line options at build
745 time by entering them here. As a minimum, you should specify the
746 memory size and the root device (e.g., mem=64M root=/dev/nfs).
749 bool "Kernel Execute-In-Place from ROM"
750 depends on !ZBOOT_ROM
752 Execute-In-Place allows the kernel to run from non-volatile storage
753 directly addressable by the CPU, such as NOR flash. This saves RAM
754 space since the text section of the kernel is not loaded from flash
755 to RAM. Read-write sections, such as the data section and stack,
756 are still copied to RAM. The XIP kernel is not compressed since
757 it has to run directly from flash, so it will take more space to
758 store it. The flash address used to link the kernel object files,
759 and for storing it, is configuration dependent. Therefore, if you
760 say Y here, you must know the proper physical address where to
761 store the kernel image depending on your own flash memory usage.
763 Also note that the make target becomes "make xipImage" rather than
764 "make zImage" or "make Image". The final kernel binary to put in
765 ROM memory will be arch/arm/boot/xipImage.
770 hex "XIP Kernel Physical Location"
771 depends on XIP_KERNEL
774 This is the physical address in your flash memory the kernel will
775 be linked for and stored to. This address is dependent on your
779 bool "Kexec system call (EXPERIMENTAL)"
780 depends on EXPERIMENTAL
782 kexec is a system call that implements the ability to shutdown your
783 current kernel, and to start another kernel. It is like a reboot
784 but it is indepedent of the system firmware. And like a reboot
785 you can start any kernel with it, not just Linux.
787 It is an ongoing process to be certain the hardware in a machine
788 is properly shutdown, so do not be surprised if this code does not
789 initially work for you. It may help to enable device hotplugging
794 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
796 menu "CPU Frequency scaling"
798 source "drivers/cpufreq/Kconfig"
800 config CPU_FREQ_SA1100
802 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
805 config CPU_FREQ_SA1110
807 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
810 config CPU_FREQ_INTEGRATOR
811 tristate "CPUfreq driver for ARM Integrator CPUs"
812 depends on ARCH_INTEGRATOR && CPU_FREQ
815 This enables the CPUfreq driver for ARM Integrator CPUs.
817 For details, take a look at <file:Documentation/cpu-freq>.
822 tristate "CPUfreq driver for i.MX CPUs"
823 depends on ARCH_IMX && CPU_FREQ
826 This enables the CPUfreq driver for i.MX CPUs.
834 menu "Floating point emulation"
836 comment "At least one emulation must be selected"
839 bool "NWFPE math emulation"
840 depends on !AEABI || OABI_COMPAT
842 Say Y to include the NWFPE floating point emulator in the kernel.
843 This is necessary to run most binaries. Linux does not currently
844 support floating point hardware so you need to say Y here even if
845 your machine has an FPA or floating point co-processor podule.
847 You may say N here if you are going to load the Acorn FPEmulator
851 bool "Support extended precision"
854 Say Y to include 80-bit support in the kernel floating-point
855 emulator. Otherwise, only 32 and 64-bit support is compiled in.
856 Note that gcc does not generate 80-bit operations by default,
857 so in most cases this option only enlarges the size of the
858 floating point emulator without any good reason.
860 You almost surely want to say N here.
863 bool "FastFPE math emulation (EXPERIMENTAL)"
864 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
866 Say Y here to include the FAST floating point emulator in the kernel.
867 This is an experimental much faster emulator which now also has full
868 precision for the mantissa. It does not support any exceptions.
869 It is very simple, and approximately 3-6 times faster than NWFPE.
871 It should be sufficient for most programs. It may be not suitable
872 for scientific calculations, but you have to check this for yourself.
873 If you do not feel you need a faster FP emulation you should better
877 bool "VFP-format floating point maths"
878 depends on CPU_V6 || CPU_ARM926T
880 Say Y to include VFP support code in the kernel. This is needed
881 if your hardware includes a VFP unit.
883 Please see <file:Documentation/arm/VFP/release-notes.txt> for
884 release notes and additional status information.
886 Say N if your target does not have VFP hardware.
890 menu "Userspace binary formats"
892 source "fs/Kconfig.binfmt"
895 tristate "RISC OS personality"
898 Say Y here to include the kernel code necessary if you want to run
899 Acorn RISC OS/Arthur binaries under Linux. This code is still very
900 experimental; if this sounds frightening, say N and sleep in peace.
901 You can also say M here to compile this support as a module (which
902 will be called arthur).
906 menu "Power management options"
908 source "kernel/power/Kconfig"
914 menu "Device Drivers"
916 source "drivers/base/Kconfig"
918 source "drivers/connector/Kconfig"
920 if ALIGNMENT_TRAP || !CPU_CP15_MMU
921 source "drivers/mtd/Kconfig"
924 source "drivers/parport/Kconfig"
926 source "drivers/pnp/Kconfig"
928 source "drivers/block/Kconfig"
930 source "drivers/acorn/block/Kconfig"
932 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
933 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
934 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
936 source "drivers/ide/Kconfig"
939 source "drivers/scsi/Kconfig"
941 source "drivers/ata/Kconfig"
943 source "drivers/md/Kconfig"
945 source "drivers/message/fusion/Kconfig"
947 source "drivers/ieee1394/Kconfig"
949 source "drivers/message/i2o/Kconfig"
951 source "drivers/net/Kconfig"
953 source "drivers/isdn/Kconfig"
955 # input before char - char/joystick depends on it. As does USB.
957 source "drivers/input/Kconfig"
959 source "drivers/char/Kconfig"
961 source "drivers/i2c/Kconfig"
963 source "drivers/spi/Kconfig"
965 source "drivers/w1/Kconfig"
967 source "drivers/hwmon/Kconfig"
969 #source "drivers/l3/Kconfig"
971 source "drivers/misc/Kconfig"
973 source "drivers/mfd/Kconfig"
975 source "drivers/leds/Kconfig"
977 source "drivers/media/Kconfig"
979 source "drivers/video/Kconfig"
981 source "sound/Kconfig"
983 source "drivers/hid/Kconfig"
985 source "drivers/usb/Kconfig"
987 source "drivers/mmc/Kconfig"
989 source "drivers/rtc/Kconfig"
995 source "arch/arm/oprofile/Kconfig"
997 source "arch/arm/Kconfig.debug"
999 source "security/Kconfig"
1001 source "crypto/Kconfig"
1003 source "lib/Kconfig"