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"
175 Support for the Cirrus Logic PS7500FE system-on-a-chip.
178 bool "Cirrus Logic CLPS711x/EP721x-based"
180 Support for Cirrus Logic 711x/721x based boards.
185 select FOOTBRIDGE_ADDIN
187 Support for Intel's EBSA285 companion chip.
193 This is an evaluation board for the StrongARM processor available
194 from Digital. It has limited hardware on-board, including an
195 Ethernet interface, two PCMCIA sockets, two serial ports and a
203 This enables support for the Cirrus EP93xx series of CPUs.
205 config ARCH_FOOTBRIDGE
209 Support for systems based on the DC21285 companion chip
210 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
213 bool "Hilscher NetX based"
216 This enables support for systems based on the Hilscher NetX Soc
219 bool "Hynix HMS720x-based"
222 This enables support for systems based on the Hynix HMS720x
227 Support for Motorola's i.MX family of processors (MX1, MXL).
235 Support for Intel's 80219 and IOP32X (XScale) family of
244 Support for Intel's IOP33X (XScale) family of processors.
252 Support for Intel's IOP13XX (XScale) family of processors.
259 Support for Intel's IXP4XX (XScale) family of processors.
262 bool "IXP2400/2800-based"
266 Support for Intel's IXP2400/2800 (XScale) family of processors.
273 Support for Intel's IXP23xx (XScale) family of processors.
279 Say Y here if you intend to run this kernel on a LinkUp Systems
280 L7200 Software Development Board which uses an ARM720T processor.
281 Information on this board can be obtained at:
283 <http://www.linkupsys.com/>
285 If you have any questions or comments about the Linux kernel port
286 to this board, send e-mail to <sjhill@cotw.com>.
289 bool "NetSilicon NS9xxx"
291 Say Y here if you intend to run this kernel on a NetSilicon NS9xxx
294 <http://www.digi.com/products/microprocessors/index.jsp>
297 bool "Philips Nexperia PNX4008 Mobile"
299 This enables support for Philips PNX4008 mobile platform.
307 Support for Intel's PXA2XX processor line.
314 select ARCH_MAY_HAVE_PC_FDC
318 On the Acorn Risc-PC, Linux can support the internal IDE disk and
319 CD-ROM interface, serial and parallel port, and the floppy drive.
324 select ARCH_DISCONTIGMEM_ENABLE
327 Support for StrongARM 11x0 based boards.
330 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
332 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
333 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
334 the Samsung SMDK2410 development board (and derivatives).
342 Support for the StrongARM based Digital DNARD machine, also known
343 as "Shark" (<http://www.shark-linux.de/shark.html>).
348 Say Y here for systems based on one of the Sharp LH7A40X
349 System on a Chip processors. These CPUs include an ARM922T
350 core with a wide array of integrated devices for
351 hand-held and low-power applications.
356 Support for TI's OMAP platform (OMAP1 and OMAP2).
360 source "arch/arm/mach-clps711x/Kconfig"
362 source "arch/arm/mach-ep93xx/Kconfig"
364 source "arch/arm/mach-footbridge/Kconfig"
366 source "arch/arm/mach-integrator/Kconfig"
368 source "arch/arm/mach-iop32x/Kconfig"
370 source "arch/arm/mach-iop33x/Kconfig"
372 source "arch/arm/mach-iop13xx/Kconfig"
374 source "arch/arm/mach-ixp4xx/Kconfig"
376 source "arch/arm/mach-ixp2000/Kconfig"
378 source "arch/arm/mach-ixp23xx/Kconfig"
380 source "arch/arm/mach-pxa/Kconfig"
382 source "arch/arm/mach-sa1100/Kconfig"
384 source "arch/arm/plat-omap/Kconfig"
386 source "arch/arm/mach-omap1/Kconfig"
388 source "arch/arm/mach-omap2/Kconfig"
390 source "arch/arm/plat-s3c24xx/Kconfig"
393 source "arch/arm/mach-s3c2400/Kconfig"
394 source "arch/arm/mach-s3c2410/Kconfig"
395 source "arch/arm/mach-s3c2412/Kconfig"
396 source "arch/arm/mach-s3c2440/Kconfig"
397 source "arch/arm/mach-s3c2442/Kconfig"
398 source "arch/arm/mach-s3c2443/Kconfig"
401 source "arch/arm/mach-lh7a40x/Kconfig"
403 source "arch/arm/mach-imx/Kconfig"
405 source "arch/arm/mach-h720x/Kconfig"
407 source "arch/arm/mach-versatile/Kconfig"
409 source "arch/arm/mach-aaec2000/Kconfig"
411 source "arch/arm/mach-realview/Kconfig"
413 source "arch/arm/mach-at91/Kconfig"
415 source "arch/arm/mach-netx/Kconfig"
417 source "arch/arm/mach-ns9xxx/Kconfig"
419 # Definitions to make life easier
426 source arch/arm/mm/Kconfig
429 bool "Enable iWMMXt support"
430 depends on CPU_XSCALE || CPU_XSC3
433 Enable support for iWMMXt context switching at run time if
434 running on a CPU that supports it.
436 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
439 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
443 source "arch/arm/Kconfig-nommu"
448 source "arch/arm/common/Kconfig"
450 config FORCE_MAX_ZONEORDER
463 Find out whether you have ISA slots on your motherboard. ISA is the
464 name of a bus system, i.e. the way the CPU talks to the other stuff
465 inside your box. Other bus systems are PCI, EISA, MicroChannel
466 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
467 newer boards don't support it. If you have ISA, say Y, otherwise N.
469 # Select ISA DMA controller support
474 # Select ISA DMA interface
479 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
481 Find out whether you have a PCI motherboard. PCI is the name of a
482 bus system, i.e. the way the CPU talks to the other stuff inside
483 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
484 VESA. If you have PCI, say Y, otherwise N.
486 The PCI-HOWTO, available from
487 <http://www.tldp.org/docs.html#howto>, contains valuable
488 information about which PCI hardware does work under Linux and which
491 # Select the host bridge type
492 config PCI_HOST_VIA82C505
494 depends on PCI && ARCH_SHARK
497 source "drivers/pci/Kconfig"
499 source "drivers/pcmcia/Kconfig"
503 menu "Kernel Features"
506 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
507 depends on EXPERIMENTAL && REALVIEW_MPCORE
509 This enables support for systems with more than one CPU. If you have
510 a system with only one CPU, like most personal computers, say N. If
511 you have a system with more than one CPU, say Y.
513 If you say N here, the kernel will run on single and multiprocessor
514 machines, but will use only one CPU of a multiprocessor machine. If
515 you say Y here, the kernel will run on many, but not all, single
516 processor machines. On a single processor machine, the kernel will
517 run faster if you say N here.
519 See also the <file:Documentation/smp.txt>,
520 <file:Documentation/i386/IO-APIC.txt>,
521 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
522 <http://www.linuxdoc.org/docs.html#howto>.
524 If you don't know what to do here, say N.
527 int "Maximum number of CPUs (2-32)"
533 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
534 depends on SMP && HOTPLUG && EXPERIMENTAL
536 Say Y here to experiment with turning CPUs off and on. CPUs
537 can be controlled through /sys/devices/system/cpu.
540 bool "Use local timer interrupts"
541 depends on SMP && REALVIEW_MPCORE
544 Enable support for local timers on SMP platforms, rather then the
545 legacy IPI broadcast method. Local timers allows the system
546 accounting to be spread across the timer interval, preventing a
547 "thundering herd" at every timer tick.
550 bool "Preemptible Kernel (EXPERIMENTAL)"
551 depends on EXPERIMENTAL
553 This option reduces the latency of the kernel when reacting to
554 real-time or interactive events by allowing a low priority process to
555 be preempted even if it is in kernel mode executing a system call.
556 This allows applications to run more reliably even when the system is
559 Say Y here if you are building a kernel for a desktop, embedded
560 or real-time system. Say N if you are unsure.
563 bool "Dynamic tick timer"
565 Select this option if you want to disable continuous timer ticks
566 and have them programmed to occur as required. This option saves
567 power as the system can remain in idle state for longer.
569 By default dynamic tick is disabled during the boot, and can be
570 manually enabled with:
572 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
574 Alternatively, if you want dynamic tick automatically enabled
575 during boot, pass "dyntick=enable" via the kernel command string.
577 Please note that dynamic tick may affect the accuracy of
578 timekeeping on some platforms depending on the implementation.
579 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
580 to have accurate timekeeping with dynamic tick.
584 default 128 if ARCH_L7200
585 default 200 if ARCH_EBSA110 || ARCH_S3C2410
586 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
590 bool "Use the ARM EABI to compile the kernel"
592 This option allows for the kernel to be compiled using the latest
593 ARM ABI (aka EABI). This is only useful if you are using a user
594 space environment that is also compiled with EABI.
596 Since there are major incompatibilities between the legacy ABI and
597 EABI, especially with regard to structure member alignment, this
598 option also changes the kernel syscall calling convention to
599 disambiguate both ABIs and allow for backward compatibility support
600 (selected with CONFIG_OABI_COMPAT).
602 To use this you need GCC version 4.0.0 or later.
605 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
606 depends on AEABI && EXPERIMENTAL
609 This option preserves the old syscall interface along with the
610 new (ARM EABI) one. It also provides a compatibility layer to
611 intercept syscalls that have structure arguments which layout
612 in memory differs between the legacy ABI and the new ARM EABI
613 (only for non "thumb" binaries). This option adds a tiny
614 overhead to all syscalls and produces a slightly larger kernel.
615 If you know you'll be using only pure EABI user space then you
616 can say N here. If this option is not selected and you attempt
617 to execute a legacy ABI binary then the result will be
618 UNPREDICTABLE (in fact it can be predicted that it won't work
619 at all). If in doubt say Y.
621 config ARCH_DISCONTIGMEM_ENABLE
623 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
625 Say Y to support efficient handling of discontiguous physical memory,
626 for architectures which are either NUMA (Non-Uniform Memory Access)
627 or have huge holes in the physical address space for other reasons.
628 See <file:Documentation/vm/numa> for more.
632 default "4" if ARCH_LH7A40X
634 depends on NEED_MULTIPLE_NODES
639 bool "Timer and CPU usage LEDs"
640 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
641 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
642 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
643 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
644 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
645 ARCH_AT91 || MACH_TRIZEPS4
647 If you say Y here, the LEDs on your machine will be used
648 to provide useful information about your current system status.
650 If you are compiling a kernel for a NetWinder or EBSA-285, you will
651 be able to select which LEDs are active using the options below. If
652 you are compiling a kernel for the EBSA-110 or the LART however, the
653 red LED will simply flash regularly to indicate that the system is
654 still functional. It is safe to say Y here if you have a CATS
655 system, but the driver will do nothing.
658 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
659 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
661 default y if ARCH_EBSA110
663 If you say Y here, one of the system LEDs (the green one on the
664 NetWinder, the amber one on the EBSA285, or the red one on the LART)
665 will flash regularly to indicate that the system is still
666 operational. This is mainly useful to kernel hackers who are
667 debugging unstable kernels.
669 The LART uses the same LED for both Timer LED and CPU usage LED
670 functions. You may choose to use both, but the Timer LED function
671 will overrule the CPU usage LED.
674 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
675 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
678 If you say Y here, the red LED will be used to give a good real
679 time indication of CPU usage, by lighting whenever the idle task
680 is not currently executing.
682 The LART uses the same LED for both Timer LED and CPU usage LED
683 functions. You may choose to use both, but the Timer LED function
684 will overrule the CPU usage LED.
686 config ALIGNMENT_TRAP
688 depends on CPU_CP15_MMU
689 default y if !ARCH_EBSA110
691 ARM processors cannot fetch/store information which is not
692 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
693 address divisible by 4. On 32-bit ARM processors, these non-aligned
694 fetch/store instructions will be emulated in software if you say
695 here, which has a severe performance impact. This is necessary for
696 correct operation of some network protocols. With an IP-only
697 configuration it is safe to say N, otherwise say Y.
703 # Compressed boot loader in ROM. Yes, we really want to ask about
704 # TEXT and BSS so we preserve their values in the config files.
705 config ZBOOT_ROM_TEXT
706 hex "Compressed ROM boot loader base address"
709 The physical address at which the ROM-able zImage is to be
710 placed in the target. Platforms which normally make use of
711 ROM-able zImage formats normally set this to a suitable
712 value in their defconfig file.
714 If ZBOOT_ROM is not enabled, this has no effect.
717 hex "Compressed ROM boot loader BSS address"
720 The base address of an area of read/write memory in the target
721 for the ROM-able zImage which must be available while the
722 decompressor is running. It must be large enough to hold the
723 entire decompressed kernel plus an additional 128 KiB.
724 Platforms which normally make use of ROM-able zImage formats
725 normally set this to a suitable value in their defconfig file.
727 If ZBOOT_ROM is not enabled, this has no effect.
730 bool "Compressed boot loader in ROM/flash"
731 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
733 Say Y here if you intend to execute your compressed kernel image
734 (zImage) directly from ROM or flash. If unsure, say N.
737 string "Default kernel command string"
740 On some architectures (EBSA110 and CATS), there is currently no way
741 for the boot loader to pass arguments to the kernel. For these
742 architectures, you should supply some command-line options at build
743 time by entering them here. As a minimum, you should specify the
744 memory size and the root device (e.g., mem=64M root=/dev/nfs).
747 bool "Kernel Execute-In-Place from ROM"
748 depends on !ZBOOT_ROM
750 Execute-In-Place allows the kernel to run from non-volatile storage
751 directly addressable by the CPU, such as NOR flash. This saves RAM
752 space since the text section of the kernel is not loaded from flash
753 to RAM. Read-write sections, such as the data section and stack,
754 are still copied to RAM. The XIP kernel is not compressed since
755 it has to run directly from flash, so it will take more space to
756 store it. The flash address used to link the kernel object files,
757 and for storing it, is configuration dependent. Therefore, if you
758 say Y here, you must know the proper physical address where to
759 store the kernel image depending on your own flash memory usage.
761 Also note that the make target becomes "make xipImage" rather than
762 "make zImage" or "make Image". The final kernel binary to put in
763 ROM memory will be arch/arm/boot/xipImage.
768 hex "XIP Kernel Physical Location"
769 depends on XIP_KERNEL
772 This is the physical address in your flash memory the kernel will
773 be linked for and stored to. This address is dependent on your
777 bool "Kexec system call (EXPERIMENTAL)"
778 depends on EXPERIMENTAL
780 kexec is a system call that implements the ability to shutdown your
781 current kernel, and to start another kernel. It is like a reboot
782 but it is indepedent of the system firmware. And like a reboot
783 you can start any kernel with it, not just Linux.
785 It is an ongoing process to be certain the hardware in a machine
786 is properly shutdown, so do not be surprised if this code does not
787 initially work for you. It may help to enable device hotplugging
792 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
794 menu "CPU Frequency scaling"
796 source "drivers/cpufreq/Kconfig"
798 config CPU_FREQ_SA1100
800 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
803 config CPU_FREQ_SA1110
805 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
808 config CPU_FREQ_INTEGRATOR
809 tristate "CPUfreq driver for ARM Integrator CPUs"
810 depends on ARCH_INTEGRATOR && CPU_FREQ
813 This enables the CPUfreq driver for ARM Integrator CPUs.
815 For details, take a look at <file:Documentation/cpu-freq>.
820 tristate "CPUfreq driver for i.MX CPUs"
821 depends on ARCH_IMX && CPU_FREQ
824 This enables the CPUfreq driver for i.MX CPUs.
832 menu "Floating point emulation"
834 comment "At least one emulation must be selected"
837 bool "NWFPE math emulation"
838 depends on !AEABI || OABI_COMPAT
840 Say Y to include the NWFPE floating point emulator in the kernel.
841 This is necessary to run most binaries. Linux does not currently
842 support floating point hardware so you need to say Y here even if
843 your machine has an FPA or floating point co-processor podule.
845 You may say N here if you are going to load the Acorn FPEmulator
849 bool "Support extended precision"
852 Say Y to include 80-bit support in the kernel floating-point
853 emulator. Otherwise, only 32 and 64-bit support is compiled in.
854 Note that gcc does not generate 80-bit operations by default,
855 so in most cases this option only enlarges the size of the
856 floating point emulator without any good reason.
858 You almost surely want to say N here.
861 bool "FastFPE math emulation (EXPERIMENTAL)"
862 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
864 Say Y here to include the FAST floating point emulator in the kernel.
865 This is an experimental much faster emulator which now also has full
866 precision for the mantissa. It does not support any exceptions.
867 It is very simple, and approximately 3-6 times faster than NWFPE.
869 It should be sufficient for most programs. It may be not suitable
870 for scientific calculations, but you have to check this for yourself.
871 If you do not feel you need a faster FP emulation you should better
875 bool "VFP-format floating point maths"
876 depends on CPU_V6 || CPU_ARM926T
878 Say Y to include VFP support code in the kernel. This is needed
879 if your hardware includes a VFP unit.
881 Please see <file:Documentation/arm/VFP/release-notes.txt> for
882 release notes and additional status information.
884 Say N if your target does not have VFP hardware.
888 menu "Userspace binary formats"
890 source "fs/Kconfig.binfmt"
893 tristate "RISC OS personality"
896 Say Y here to include the kernel code necessary if you want to run
897 Acorn RISC OS/Arthur binaries under Linux. This code is still very
898 experimental; if this sounds frightening, say N and sleep in peace.
899 You can also say M here to compile this support as a module (which
900 will be called arthur).
904 menu "Power management options"
906 source "kernel/power/Kconfig"
912 menu "Device Drivers"
914 source "drivers/base/Kconfig"
916 source "drivers/connector/Kconfig"
918 if ALIGNMENT_TRAP || !CPU_CP15_MMU
919 source "drivers/mtd/Kconfig"
922 source "drivers/parport/Kconfig"
924 source "drivers/pnp/Kconfig"
926 source "drivers/block/Kconfig"
928 source "drivers/acorn/block/Kconfig"
930 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
931 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
932 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
934 source "drivers/ide/Kconfig"
937 source "drivers/scsi/Kconfig"
939 source "drivers/ata/Kconfig"
941 source "drivers/md/Kconfig"
943 source "drivers/message/fusion/Kconfig"
945 source "drivers/ieee1394/Kconfig"
947 source "drivers/message/i2o/Kconfig"
949 source "drivers/net/Kconfig"
951 source "drivers/isdn/Kconfig"
953 # input before char - char/joystick depends on it. As does USB.
955 source "drivers/input/Kconfig"
957 source "drivers/char/Kconfig"
959 source "drivers/i2c/Kconfig"
961 source "drivers/spi/Kconfig"
963 source "drivers/w1/Kconfig"
965 source "drivers/hwmon/Kconfig"
967 #source "drivers/l3/Kconfig"
969 source "drivers/misc/Kconfig"
971 source "drivers/mfd/Kconfig"
973 source "drivers/leds/Kconfig"
975 source "drivers/media/Kconfig"
977 source "drivers/video/Kconfig"
979 source "sound/Kconfig"
981 source "drivers/hid/Kconfig"
983 source "drivers/usb/Kconfig"
985 source "drivers/mmc/Kconfig"
987 source "drivers/rtc/Kconfig"
993 source "arch/arm/oprofile/Kconfig"
995 source "arch/arm/Kconfig.debug"
997 source "security/Kconfig"
999 source "crypto/Kconfig"
1001 source "lib/Kconfig"