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
43 The Extended Industry Standard Architecture (EISA) bus was
44 developed as an open alternative to the IBM MicroChannel bus.
46 The EISA bus provided some of the features of the IBM MicroChannel
47 bus while maintaining backward compatibility with cards made for
48 the older ISA bus. The EISA bus saw limited use between 1988 and
49 1995 when it was made obsolete by the PCI bus.
51 Say Y here if you are building a kernel for an EISA-based machine.
61 MicroChannel Architecture is found in some IBM PS/2 machines and
62 laptops. It is a bus system similar to PCI or ISA. See
63 <file:Documentation/mca.txt> (and especially the web page given
64 there) before attempting to build an MCA bus kernel.
66 config GENERIC_HARDIRQS
70 config TRACE_IRQFLAGS_SUPPORT
74 config HARDIRQS_SW_RESEND
78 config GENERIC_IRQ_PROBE
82 config RWSEM_GENERIC_SPINLOCK
86 config RWSEM_XCHGADD_ALGORITHM
89 config ARCH_HAS_ILOG2_U32
93 config ARCH_HAS_ILOG2_U64
97 config GENERIC_HWEIGHT
101 config GENERIC_CALIBRATE_DELAY
105 config GENERIC_BUST_SPINLOCK
108 config ARCH_MAY_HAVE_PC_FDC
115 config GENERIC_ISA_DMA
126 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
127 default DRAM_BASE if REMAP_VECTORS_TO_RAM
130 The base address of exception vectors.
132 source "init/Kconfig"
137 prompt "ARM system type"
138 default ARCH_VERSATILE
141 bool "Agilent AAEC-2000 based"
144 This enables support for systems based on the Agilent AAEC-2000
146 config ARCH_INTEGRATOR
147 bool "ARM Ltd. Integrator family"
151 Support for ARM's Integrator platform.
154 bool "ARM Ltd. RealView family"
158 This enables support for ARM Ltd RealView boards.
160 config ARCH_VERSATILE
161 bool "ARM Ltd. Versatile family"
166 This enables support for ARM Ltd Versatile board.
172 This enables support for systems based on the Atmel AT91RM9200
173 and AT91SAM9xxx processors.
176 bool "Cirrus CL-PS7500FE"
181 Support for the Cirrus Logic PS7500FE system-on-a-chip.
184 bool "Cirrus Logic CLPS711x/EP721x-based"
186 Support for Cirrus Logic 711x/721x based boards.
191 select FOOTBRIDGE_ADDIN
193 Support for Intel's EBSA285 companion chip.
200 This is an evaluation board for the StrongARM processor available
201 from Digital. It has limited hardware on-board, including an
202 Ethernet interface, two PCMCIA sockets, two serial ports and a
210 This enables support for the Cirrus EP93xx series of CPUs.
212 config ARCH_FOOTBRIDGE
216 Support for systems based on the DC21285 companion chip
217 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
220 bool "Hilscher NetX based"
223 This enables support for systems based on the Hilscher NetX Soc
226 bool "Hynix HMS720x-based"
229 This enables support for systems based on the Hynix HMS720x
234 Support for Motorola's i.MX family of processors (MX1, MXL).
242 Support for Intel's 80219 and IOP32X (XScale) family of
251 Support for Intel's IOP33X (XScale) family of processors.
259 Support for Intel's IOP13XX (XScale) family of processors.
266 Support for Intel's IXP4XX (XScale) family of processors.
269 bool "IXP2400/2800-based"
273 Support for Intel's IXP2400/2800 (XScale) family of processors.
280 Support for Intel's IXP23xx (XScale) family of processors.
286 Say Y here if you intend to run this kernel on a LinkUp Systems
287 L7200 Software Development Board which uses an ARM720T processor.
288 Information on this board can be obtained at:
290 <http://www.linkupsys.com/>
292 If you have any questions or comments about the Linux kernel port
293 to this board, send e-mail to <sjhill@cotw.com>.
296 bool "NetSilicon NS9xxx"
298 Say Y here if you intend to run this kernel on a NetSilicon NS9xxx
301 <http://www.digi.com/products/microprocessors/index.jsp>
304 bool "Philips Nexperia PNX4008 Mobile"
306 This enables support for Philips PNX4008 mobile platform.
315 Support for Intel's PXA2XX processor line.
322 select ARCH_MAY_HAVE_PC_FDC
326 On the Acorn Risc-PC, Linux can support the internal IDE disk and
327 CD-ROM interface, serial and parallel port, and the floppy drive.
332 select ARCH_DISCONTIGMEM_ENABLE
336 Support for StrongARM 11x0 based boards.
339 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
342 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
343 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
344 the Samsung SMDK2410 development board (and derivatives).
352 Support for the StrongARM based Digital DNARD machine, also known
353 as "Shark" (<http://www.shark-linux.de/shark.html>).
358 Say Y here for systems based on one of the Sharp LH7A40X
359 System on a Chip processors. These CPUs include an ARM922T
360 core with a wide array of integrated devices for
361 hand-held and low-power applications.
367 Support for TI's OMAP platform (OMAP1 and OMAP2).
371 source "arch/arm/mach-clps711x/Kconfig"
373 source "arch/arm/mach-ep93xx/Kconfig"
375 source "arch/arm/mach-footbridge/Kconfig"
377 source "arch/arm/mach-integrator/Kconfig"
379 source "arch/arm/mach-iop32x/Kconfig"
381 source "arch/arm/mach-iop33x/Kconfig"
383 source "arch/arm/mach-iop13xx/Kconfig"
385 source "arch/arm/mach-ixp4xx/Kconfig"
387 source "arch/arm/mach-ixp2000/Kconfig"
389 source "arch/arm/mach-ixp23xx/Kconfig"
391 source "arch/arm/mach-pxa/Kconfig"
393 source "arch/arm/mach-sa1100/Kconfig"
395 source "arch/arm/plat-omap/Kconfig"
397 source "arch/arm/mach-omap1/Kconfig"
399 source "arch/arm/mach-omap2/Kconfig"
401 source "arch/arm/plat-s3c24xx/Kconfig"
404 source "arch/arm/mach-s3c2400/Kconfig"
405 source "arch/arm/mach-s3c2410/Kconfig"
406 source "arch/arm/mach-s3c2412/Kconfig"
407 source "arch/arm/mach-s3c2440/Kconfig"
408 source "arch/arm/mach-s3c2442/Kconfig"
409 source "arch/arm/mach-s3c2443/Kconfig"
412 source "arch/arm/mach-lh7a40x/Kconfig"
414 source "arch/arm/mach-imx/Kconfig"
416 source "arch/arm/mach-h720x/Kconfig"
418 source "arch/arm/mach-versatile/Kconfig"
420 source "arch/arm/mach-aaec2000/Kconfig"
422 source "arch/arm/mach-realview/Kconfig"
424 source "arch/arm/mach-at91/Kconfig"
426 source "arch/arm/mach-netx/Kconfig"
428 source "arch/arm/mach-ns9xxx/Kconfig"
430 # Definitions to make life easier
437 source arch/arm/mm/Kconfig
440 bool "Enable iWMMXt support"
441 depends on CPU_XSCALE || CPU_XSC3
444 Enable support for iWMMXt context switching at run time if
445 running on a CPU that supports it.
447 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
450 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
454 source "arch/arm/Kconfig-nommu"
459 source "arch/arm/common/Kconfig"
461 config FORCE_MAX_ZONEORDER
474 Find out whether you have ISA slots on your motherboard. ISA is the
475 name of a bus system, i.e. the way the CPU talks to the other stuff
476 inside your box. Other bus systems are PCI, EISA, MicroChannel
477 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
478 newer boards don't support it. If you have ISA, say Y, otherwise N.
480 # Select ISA DMA controller support
485 # Select ISA DMA interface
490 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
492 Find out whether you have a PCI motherboard. PCI is the name of a
493 bus system, i.e. the way the CPU talks to the other stuff inside
494 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
495 VESA. If you have PCI, say Y, otherwise N.
497 The PCI-HOWTO, available from
498 <http://www.tldp.org/docs.html#howto>, contains valuable
499 information about which PCI hardware does work under Linux and which
502 # Select the host bridge type
503 config PCI_HOST_VIA82C505
505 depends on PCI && ARCH_SHARK
508 source "drivers/pci/Kconfig"
510 source "drivers/pcmcia/Kconfig"
514 menu "Kernel Features"
517 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
518 depends on EXPERIMENTAL && REALVIEW_MPCORE
520 This enables support for systems with more than one CPU. If you have
521 a system with only one CPU, like most personal computers, say N. If
522 you have a system with more than one CPU, say Y.
524 If you say N here, the kernel will run on single and multiprocessor
525 machines, but will use only one CPU of a multiprocessor machine. If
526 you say Y here, the kernel will run on many, but not all, single
527 processor machines. On a single processor machine, the kernel will
528 run faster if you say N here.
530 See also the <file:Documentation/smp.txt>,
531 <file:Documentation/i386/IO-APIC.txt>,
532 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
533 <http://www.linuxdoc.org/docs.html#howto>.
535 If you don't know what to do here, say N.
538 int "Maximum number of CPUs (2-32)"
544 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
545 depends on SMP && HOTPLUG && EXPERIMENTAL
547 Say Y here to experiment with turning CPUs off and on. CPUs
548 can be controlled through /sys/devices/system/cpu.
551 bool "Use local timer interrupts"
552 depends on SMP && REALVIEW_MPCORE
555 Enable support for local timers on SMP platforms, rather then the
556 legacy IPI broadcast method. Local timers allows the system
557 accounting to be spread across the timer interval, preventing a
558 "thundering herd" at every timer tick.
561 bool "Preemptible Kernel (EXPERIMENTAL)"
562 depends on EXPERIMENTAL
564 This option reduces the latency of the kernel when reacting to
565 real-time or interactive events by allowing a low priority process to
566 be preempted even if it is in kernel mode executing a system call.
567 This allows applications to run more reliably even when the system is
570 Say Y here if you are building a kernel for a desktop, embedded
571 or real-time system. Say N if you are unsure.
574 bool "Dynamic tick timer"
576 Select this option if you want to disable continuous timer ticks
577 and have them programmed to occur as required. This option saves
578 power as the system can remain in idle state for longer.
580 By default dynamic tick is disabled during the boot, and can be
581 manually enabled with:
583 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
585 Alternatively, if you want dynamic tick automatically enabled
586 during boot, pass "dyntick=enable" via the kernel command string.
588 Please note that dynamic tick may affect the accuracy of
589 timekeeping on some platforms depending on the implementation.
590 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
591 to have accurate timekeeping with dynamic tick.
595 default 128 if ARCH_L7200
596 default 200 if ARCH_EBSA110 || ARCH_S3C2410
597 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
601 bool "Use the ARM EABI to compile the kernel"
603 This option allows for the kernel to be compiled using the latest
604 ARM ABI (aka EABI). This is only useful if you are using a user
605 space environment that is also compiled with EABI.
607 Since there are major incompatibilities between the legacy ABI and
608 EABI, especially with regard to structure member alignment, this
609 option also changes the kernel syscall calling convention to
610 disambiguate both ABIs and allow for backward compatibility support
611 (selected with CONFIG_OABI_COMPAT).
613 To use this you need GCC version 4.0.0 or later.
616 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
617 depends on AEABI && EXPERIMENTAL
620 This option preserves the old syscall interface along with the
621 new (ARM EABI) one. It also provides a compatibility layer to
622 intercept syscalls that have structure arguments which layout
623 in memory differs between the legacy ABI and the new ARM EABI
624 (only for non "thumb" binaries). This option adds a tiny
625 overhead to all syscalls and produces a slightly larger kernel.
626 If you know you'll be using only pure EABI user space then you
627 can say N here. If this option is not selected and you attempt
628 to execute a legacy ABI binary then the result will be
629 UNPREDICTABLE (in fact it can be predicted that it won't work
630 at all). If in doubt say Y.
632 config ARCH_DISCONTIGMEM_ENABLE
634 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
636 Say Y to support efficient handling of discontiguous physical memory,
637 for architectures which are either NUMA (Non-Uniform Memory Access)
638 or have huge holes in the physical address space for other reasons.
639 See <file:Documentation/vm/numa> for more.
643 default "4" if ARCH_LH7A40X
645 depends on NEED_MULTIPLE_NODES
650 bool "Timer and CPU usage LEDs"
651 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
652 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
653 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
654 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
655 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
656 ARCH_AT91 || MACH_TRIZEPS4
658 If you say Y here, the LEDs on your machine will be used
659 to provide useful information about your current system status.
661 If you are compiling a kernel for a NetWinder or EBSA-285, you will
662 be able to select which LEDs are active using the options below. If
663 you are compiling a kernel for the EBSA-110 or the LART however, the
664 red LED will simply flash regularly to indicate that the system is
665 still functional. It is safe to say Y here if you have a CATS
666 system, but the driver will do nothing.
669 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
670 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
672 default y if ARCH_EBSA110
674 If you say Y here, one of the system LEDs (the green one on the
675 NetWinder, the amber one on the EBSA285, or the red one on the LART)
676 will flash regularly to indicate that the system is still
677 operational. This is mainly useful to kernel hackers who are
678 debugging unstable kernels.
680 The LART uses the same LED for both Timer LED and CPU usage LED
681 functions. You may choose to use both, but the Timer LED function
682 will overrule the CPU usage LED.
685 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
686 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
689 If you say Y here, the red LED will be used to give a good real
690 time indication of CPU usage, by lighting whenever the idle task
691 is not currently executing.
693 The LART uses the same LED for both Timer LED and CPU usage LED
694 functions. You may choose to use both, but the Timer LED function
695 will overrule the CPU usage LED.
697 config ALIGNMENT_TRAP
699 depends on CPU_CP15_MMU
700 default y if !ARCH_EBSA110
702 ARM processors cannot fetch/store information which is not
703 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
704 address divisible by 4. On 32-bit ARM processors, these non-aligned
705 fetch/store instructions will be emulated in software if you say
706 here, which has a severe performance impact. This is necessary for
707 correct operation of some network protocols. With an IP-only
708 configuration it is safe to say N, otherwise say Y.
714 # Compressed boot loader in ROM. Yes, we really want to ask about
715 # TEXT and BSS so we preserve their values in the config files.
716 config ZBOOT_ROM_TEXT
717 hex "Compressed ROM boot loader base address"
720 The physical address at which the ROM-able zImage is to be
721 placed in the target. Platforms which normally make use of
722 ROM-able zImage formats normally set this to a suitable
723 value in their defconfig file.
725 If ZBOOT_ROM is not enabled, this has no effect.
728 hex "Compressed ROM boot loader BSS address"
731 The base address of an area of read/write memory in the target
732 for the ROM-able zImage which must be available while the
733 decompressor is running. It must be large enough to hold the
734 entire decompressed kernel plus an additional 128 KiB.
735 Platforms which normally make use of ROM-able zImage formats
736 normally set this to a suitable value in their defconfig file.
738 If ZBOOT_ROM is not enabled, this has no effect.
741 bool "Compressed boot loader in ROM/flash"
742 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
744 Say Y here if you intend to execute your compressed kernel image
745 (zImage) directly from ROM or flash. If unsure, say N.
748 string "Default kernel command string"
751 On some architectures (EBSA110 and CATS), there is currently no way
752 for the boot loader to pass arguments to the kernel. For these
753 architectures, you should supply some command-line options at build
754 time by entering them here. As a minimum, you should specify the
755 memory size and the root device (e.g., mem=64M root=/dev/nfs).
758 bool "Kernel Execute-In-Place from ROM"
759 depends on !ZBOOT_ROM
761 Execute-In-Place allows the kernel to run from non-volatile storage
762 directly addressable by the CPU, such as NOR flash. This saves RAM
763 space since the text section of the kernel is not loaded from flash
764 to RAM. Read-write sections, such as the data section and stack,
765 are still copied to RAM. The XIP kernel is not compressed since
766 it has to run directly from flash, so it will take more space to
767 store it. The flash address used to link the kernel object files,
768 and for storing it, is configuration dependent. Therefore, if you
769 say Y here, you must know the proper physical address where to
770 store the kernel image depending on your own flash memory usage.
772 Also note that the make target becomes "make xipImage" rather than
773 "make zImage" or "make Image". The final kernel binary to put in
774 ROM memory will be arch/arm/boot/xipImage.
779 hex "XIP Kernel Physical Location"
780 depends on XIP_KERNEL
783 This is the physical address in your flash memory the kernel will
784 be linked for and stored to. This address is dependent on your
788 bool "Kexec system call (EXPERIMENTAL)"
789 depends on EXPERIMENTAL
791 kexec is a system call that implements the ability to shutdown your
792 current kernel, and to start another kernel. It is like a reboot
793 but it is indepedent of the system firmware. And like a reboot
794 you can start any kernel with it, not just Linux.
796 It is an ongoing process to be certain the hardware in a machine
797 is properly shutdown, so do not be surprised if this code does not
798 initially work for you. It may help to enable device hotplugging
803 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
805 menu "CPU Frequency scaling"
807 source "drivers/cpufreq/Kconfig"
809 config CPU_FREQ_SA1100
811 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
814 config CPU_FREQ_SA1110
816 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
819 config CPU_FREQ_INTEGRATOR
820 tristate "CPUfreq driver for ARM Integrator CPUs"
821 depends on ARCH_INTEGRATOR && CPU_FREQ
824 This enables the CPUfreq driver for ARM Integrator CPUs.
826 For details, take a look at <file:Documentation/cpu-freq>.
831 tristate "CPUfreq driver for i.MX CPUs"
832 depends on ARCH_IMX && CPU_FREQ
835 This enables the CPUfreq driver for i.MX CPUs.
843 menu "Floating point emulation"
845 comment "At least one emulation must be selected"
848 bool "NWFPE math emulation"
849 depends on !AEABI || OABI_COMPAT
851 Say Y to include the NWFPE floating point emulator in the kernel.
852 This is necessary to run most binaries. Linux does not currently
853 support floating point hardware so you need to say Y here even if
854 your machine has an FPA or floating point co-processor podule.
856 You may say N here if you are going to load the Acorn FPEmulator
860 bool "Support extended precision"
863 Say Y to include 80-bit support in the kernel floating-point
864 emulator. Otherwise, only 32 and 64-bit support is compiled in.
865 Note that gcc does not generate 80-bit operations by default,
866 so in most cases this option only enlarges the size of the
867 floating point emulator without any good reason.
869 You almost surely want to say N here.
872 bool "FastFPE math emulation (EXPERIMENTAL)"
873 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
875 Say Y here to include the FAST floating point emulator in the kernel.
876 This is an experimental much faster emulator which now also has full
877 precision for the mantissa. It does not support any exceptions.
878 It is very simple, and approximately 3-6 times faster than NWFPE.
880 It should be sufficient for most programs. It may be not suitable
881 for scientific calculations, but you have to check this for yourself.
882 If you do not feel you need a faster FP emulation you should better
886 bool "VFP-format floating point maths"
887 depends on CPU_V6 || CPU_ARM926T
889 Say Y to include VFP support code in the kernel. This is needed
890 if your hardware includes a VFP unit.
892 Please see <file:Documentation/arm/VFP/release-notes.txt> for
893 release notes and additional status information.
895 Say N if your target does not have VFP hardware.
899 menu "Userspace binary formats"
901 source "fs/Kconfig.binfmt"
904 tristate "RISC OS personality"
907 Say Y here to include the kernel code necessary if you want to run
908 Acorn RISC OS/Arthur binaries under Linux. This code is still very
909 experimental; if this sounds frightening, say N and sleep in peace.
910 You can also say M here to compile this support as a module (which
911 will be called arthur).
915 menu "Power management options"
917 source "kernel/power/Kconfig"
923 menu "Device Drivers"
925 source "drivers/base/Kconfig"
927 source "drivers/connector/Kconfig"
929 if ALIGNMENT_TRAP || !CPU_CP15_MMU
930 source "drivers/mtd/Kconfig"
933 source "drivers/parport/Kconfig"
935 source "drivers/pnp/Kconfig"
937 source "drivers/block/Kconfig"
939 source "drivers/acorn/block/Kconfig"
941 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
942 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
943 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
945 source "drivers/ide/Kconfig"
948 source "drivers/scsi/Kconfig"
950 source "drivers/ata/Kconfig"
952 source "drivers/md/Kconfig"
954 source "drivers/message/fusion/Kconfig"
956 source "drivers/ieee1394/Kconfig"
958 source "drivers/message/i2o/Kconfig"
960 source "drivers/net/Kconfig"
962 source "drivers/isdn/Kconfig"
964 # input before char - char/joystick depends on it. As does USB.
966 source "drivers/input/Kconfig"
968 source "drivers/char/Kconfig"
970 source "drivers/i2c/Kconfig"
972 source "drivers/spi/Kconfig"
974 source "drivers/w1/Kconfig"
976 source "drivers/hwmon/Kconfig"
978 #source "drivers/l3/Kconfig"
980 source "drivers/misc/Kconfig"
982 source "drivers/mfd/Kconfig"
984 source "drivers/leds/Kconfig"
986 source "drivers/media/Kconfig"
988 source "drivers/video/Kconfig"
990 source "sound/Kconfig"
992 source "drivers/hid/Kconfig"
994 source "drivers/usb/Kconfig"
996 source "drivers/mmc/Kconfig"
998 source "drivers/rtc/Kconfig"
1004 source "arch/arm/oprofile/Kconfig"
1006 source "arch/arm/Kconfig.debug"
1008 source "security/Kconfig"
1010 source "crypto/Kconfig"
1012 source "lib/Kconfig"