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
32 config GENERIC_CLOCKEVENTS
47 The Extended Industry Standard Architecture (EISA) bus was
48 developed as an open alternative to the IBM MicroChannel bus.
50 The EISA bus provided some of the features of the IBM MicroChannel
51 bus while maintaining backward compatibility with cards made for
52 the older ISA bus. The EISA bus saw limited use between 1988 and
53 1995 when it was made obsolete by the PCI bus.
55 Say Y here if you are building a kernel for an EISA-based machine.
65 MicroChannel Architecture is found in some IBM PS/2 machines and
66 laptops. It is a bus system similar to PCI or ISA. See
67 <file:Documentation/mca.txt> (and especially the web page given
68 there) before attempting to build an MCA bus kernel.
70 config GENERIC_HARDIRQS
74 config TRACE_IRQFLAGS_SUPPORT
78 config HARDIRQS_SW_RESEND
82 config GENERIC_IRQ_PROBE
86 config RWSEM_GENERIC_SPINLOCK
90 config RWSEM_XCHGADD_ALGORITHM
93 config ARCH_HAS_ILOG2_U32
97 config ARCH_HAS_ILOG2_U64
101 config GENERIC_HWEIGHT
105 config GENERIC_CALIBRATE_DELAY
109 config GENERIC_BUST_SPINLOCK
112 config ARCH_MAY_HAVE_PC_FDC
119 config GENERIC_ISA_DMA
130 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
131 default DRAM_BASE if REMAP_VECTORS_TO_RAM
134 The base address of exception vectors.
136 source "init/Kconfig"
141 prompt "ARM system type"
142 default ARCH_VERSATILE
145 bool "Agilent AAEC-2000 based"
148 This enables support for systems based on the Agilent AAEC-2000
150 config ARCH_INTEGRATOR
151 bool "ARM Ltd. Integrator family"
155 Support for ARM's Integrator platform.
158 bool "ARM Ltd. RealView family"
162 This enables support for ARM Ltd RealView boards.
164 config ARCH_VERSATILE
165 bool "ARM Ltd. Versatile family"
170 This enables support for ARM Ltd Versatile board.
176 This enables support for systems based on the Atmel AT91RM9200
177 and AT91SAM9xxx processors.
180 bool "Cirrus CL-PS7500FE"
185 Support for the Cirrus Logic PS7500FE system-on-a-chip.
188 bool "Cirrus Logic CLPS711x/EP721x-based"
190 Support for Cirrus Logic 711x/721x based boards.
195 select FOOTBRIDGE_ADDIN
197 Support for Intel's EBSA285 companion chip.
204 This is an evaluation board for the StrongARM processor available
205 from Digital. It has limited hardware on-board, including an
206 Ethernet interface, two PCMCIA sockets, two serial ports and a
214 This enables support for the Cirrus EP93xx series of CPUs.
216 config ARCH_FOOTBRIDGE
220 Support for systems based on the DC21285 companion chip
221 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
224 bool "Hilscher NetX based"
227 This enables support for systems based on the Hilscher NetX Soc
230 bool "Hynix HMS720x-based"
233 This enables support for systems based on the Hynix HMS720x
238 Support for Motorola's i.MX family of processors (MX1, MXL).
246 Support for Intel's 80219 and IOP32X (XScale) family of
255 Support for Intel's IOP33X (XScale) family of processors.
263 Support for Intel's IOP13XX (XScale) family of processors.
269 select GENERIC_CLOCKEVENTS
271 Support for Intel's IXP4XX (XScale) family of processors.
274 bool "IXP2400/2800-based"
278 Support for Intel's IXP2400/2800 (XScale) family of processors.
285 Support for Intel's IXP23xx (XScale) family of processors.
291 Say Y here if you intend to run this kernel on a LinkUp Systems
292 L7200 Software Development Board which uses an ARM720T processor.
293 Information on this board can be obtained at:
295 <http://www.linkupsys.com/>
297 If you have any questions or comments about the Linux kernel port
298 to this board, send e-mail to <sjhill@cotw.com>.
301 bool "NetSilicon NS9xxx"
303 Say Y here if you intend to run this kernel on a NetSilicon NS9xxx
306 <http://www.digi.com/products/microprocessors/index.jsp>
309 bool "Philips Nexperia PNX4008 Mobile"
311 This enables support for Philips PNX4008 mobile platform.
320 Support for Intel's PXA2XX processor line.
327 select ARCH_MAY_HAVE_PC_FDC
331 On the Acorn Risc-PC, Linux can support the internal IDE disk and
332 CD-ROM interface, serial and parallel port, and the floppy drive.
337 select ARCH_DISCONTIGMEM_ENABLE
341 Support for StrongARM 11x0 based boards.
344 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
347 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
348 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
349 the Samsung SMDK2410 development board (and derivatives).
357 Support for the StrongARM based Digital DNARD machine, also known
358 as "Shark" (<http://www.shark-linux.de/shark.html>).
363 Say Y here for systems based on one of the Sharp LH7A40X
364 System on a Chip processors. These CPUs include an ARM922T
365 core with a wide array of integrated devices for
366 hand-held and low-power applications.
372 Support for TI's OMAP platform (OMAP1 and OMAP2).
376 source "arch/arm/mach-clps711x/Kconfig"
378 source "arch/arm/mach-ep93xx/Kconfig"
380 source "arch/arm/mach-footbridge/Kconfig"
382 source "arch/arm/mach-integrator/Kconfig"
384 source "arch/arm/mach-iop32x/Kconfig"
386 source "arch/arm/mach-iop33x/Kconfig"
388 source "arch/arm/mach-iop13xx/Kconfig"
390 source "arch/arm/mach-ixp4xx/Kconfig"
392 source "arch/arm/mach-ixp2000/Kconfig"
394 source "arch/arm/mach-ixp23xx/Kconfig"
396 source "arch/arm/mach-pxa/Kconfig"
398 source "arch/arm/mach-sa1100/Kconfig"
400 source "arch/arm/plat-omap/Kconfig"
402 source "arch/arm/mach-omap1/Kconfig"
404 source "arch/arm/mach-omap2/Kconfig"
406 source "arch/arm/plat-s3c24xx/Kconfig"
409 source "arch/arm/mach-s3c2400/Kconfig"
410 source "arch/arm/mach-s3c2410/Kconfig"
411 source "arch/arm/mach-s3c2412/Kconfig"
412 source "arch/arm/mach-s3c2440/Kconfig"
413 source "arch/arm/mach-s3c2442/Kconfig"
414 source "arch/arm/mach-s3c2443/Kconfig"
417 source "arch/arm/mach-lh7a40x/Kconfig"
419 source "arch/arm/mach-imx/Kconfig"
421 source "arch/arm/mach-h720x/Kconfig"
423 source "arch/arm/mach-versatile/Kconfig"
425 source "arch/arm/mach-aaec2000/Kconfig"
427 source "arch/arm/mach-realview/Kconfig"
429 source "arch/arm/mach-at91/Kconfig"
431 source "arch/arm/mach-netx/Kconfig"
433 source "arch/arm/mach-ns9xxx/Kconfig"
435 # Definitions to make life easier
442 source arch/arm/mm/Kconfig
445 bool "Enable iWMMXt support"
446 depends on CPU_XSCALE || CPU_XSC3
449 Enable support for iWMMXt context switching at run time if
450 running on a CPU that supports it.
452 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
455 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
459 source "arch/arm/Kconfig-nommu"
464 source "arch/arm/common/Kconfig"
466 config FORCE_MAX_ZONEORDER
479 Find out whether you have ISA slots on your motherboard. ISA is the
480 name of a bus system, i.e. the way the CPU talks to the other stuff
481 inside your box. Other bus systems are PCI, EISA, MicroChannel
482 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
483 newer boards don't support it. If you have ISA, say Y, otherwise N.
485 # Select ISA DMA controller support
490 # Select ISA DMA interface
495 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
497 Find out whether you have a PCI motherboard. PCI is the name of a
498 bus system, i.e. the way the CPU talks to the other stuff inside
499 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
500 VESA. If you have PCI, say Y, otherwise N.
502 The PCI-HOWTO, available from
503 <http://www.tldp.org/docs.html#howto>, contains valuable
504 information about which PCI hardware does work under Linux and which
507 # Select the host bridge type
508 config PCI_HOST_VIA82C505
510 depends on PCI && ARCH_SHARK
513 source "drivers/pci/Kconfig"
515 source "drivers/pcmcia/Kconfig"
519 menu "Kernel Features"
521 source "kernel/time/Kconfig"
524 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
525 depends on EXPERIMENTAL && REALVIEW_MPCORE
527 This enables support for systems with more than one CPU. If you have
528 a system with only one CPU, like most personal computers, say N. If
529 you have a system with more than one CPU, say Y.
531 If you say N here, the kernel will run on single and multiprocessor
532 machines, but will use only one CPU of a multiprocessor machine. If
533 you say Y here, the kernel will run on many, but not all, single
534 processor machines. On a single processor machine, the kernel will
535 run faster if you say N here.
537 See also the <file:Documentation/smp.txt>,
538 <file:Documentation/i386/IO-APIC.txt>,
539 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
540 <http://www.linuxdoc.org/docs.html#howto>.
542 If you don't know what to do here, say N.
545 int "Maximum number of CPUs (2-32)"
551 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
552 depends on SMP && HOTPLUG && EXPERIMENTAL
554 Say Y here to experiment with turning CPUs off and on. CPUs
555 can be controlled through /sys/devices/system/cpu.
558 bool "Use local timer interrupts"
559 depends on SMP && REALVIEW_MPCORE
562 Enable support for local timers on SMP platforms, rather then the
563 legacy IPI broadcast method. Local timers allows the system
564 accounting to be spread across the timer interval, preventing a
565 "thundering herd" at every timer tick.
568 bool "Preemptible Kernel (EXPERIMENTAL)"
569 depends on EXPERIMENTAL
571 This option reduces the latency of the kernel when reacting to
572 real-time or interactive events by allowing a low priority process to
573 be preempted even if it is in kernel mode executing a system call.
574 This allows applications to run more reliably even when the system is
577 Say Y here if you are building a kernel for a desktop, embedded
578 or real-time system. Say N if you are unsure.
581 bool "Dynamic tick timer"
582 depends on !GENERIC_CLOCKEVENTS
584 Select this option if you want to disable continuous timer ticks
585 and have them programmed to occur as required. This option saves
586 power as the system can remain in idle state for longer.
588 By default dynamic tick is disabled during the boot, and can be
589 manually enabled with:
591 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
593 Alternatively, if you want dynamic tick automatically enabled
594 during boot, pass "dyntick=enable" via the kernel command string.
596 Please note that dynamic tick may affect the accuracy of
597 timekeeping on some platforms depending on the implementation.
598 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
599 to have accurate timekeeping with dynamic tick.
603 default 128 if ARCH_L7200
604 default 200 if ARCH_EBSA110 || ARCH_S3C2410
605 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
609 bool "Use the ARM EABI to compile the kernel"
611 This option allows for the kernel to be compiled using the latest
612 ARM ABI (aka EABI). This is only useful if you are using a user
613 space environment that is also compiled with EABI.
615 Since there are major incompatibilities between the legacy ABI and
616 EABI, especially with regard to structure member alignment, this
617 option also changes the kernel syscall calling convention to
618 disambiguate both ABIs and allow for backward compatibility support
619 (selected with CONFIG_OABI_COMPAT).
621 To use this you need GCC version 4.0.0 or later.
624 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
625 depends on AEABI && EXPERIMENTAL
628 This option preserves the old syscall interface along with the
629 new (ARM EABI) one. It also provides a compatibility layer to
630 intercept syscalls that have structure arguments which layout
631 in memory differs between the legacy ABI and the new ARM EABI
632 (only for non "thumb" binaries). This option adds a tiny
633 overhead to all syscalls and produces a slightly larger kernel.
634 If you know you'll be using only pure EABI user space then you
635 can say N here. If this option is not selected and you attempt
636 to execute a legacy ABI binary then the result will be
637 UNPREDICTABLE (in fact it can be predicted that it won't work
638 at all). If in doubt say Y.
640 config ARCH_DISCONTIGMEM_ENABLE
642 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
644 Say Y to support efficient handling of discontiguous physical memory,
645 for architectures which are either NUMA (Non-Uniform Memory Access)
646 or have huge holes in the physical address space for other reasons.
647 See <file:Documentation/vm/numa> for more.
651 default "4" if ARCH_LH7A40X
653 depends on NEED_MULTIPLE_NODES
658 bool "Timer and CPU usage LEDs"
659 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
660 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
661 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
662 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
663 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
664 ARCH_AT91 || MACH_TRIZEPS4
666 If you say Y here, the LEDs on your machine will be used
667 to provide useful information about your current system status.
669 If you are compiling a kernel for a NetWinder or EBSA-285, you will
670 be able to select which LEDs are active using the options below. If
671 you are compiling a kernel for the EBSA-110 or the LART however, the
672 red LED will simply flash regularly to indicate that the system is
673 still functional. It is safe to say Y here if you have a CATS
674 system, but the driver will do nothing.
677 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
678 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
680 depends on !GENERIC_CLOCKEVENTS
681 default y if ARCH_EBSA110
683 If you say Y here, one of the system LEDs (the green one on the
684 NetWinder, the amber one on the EBSA285, or the red one on the LART)
685 will flash regularly to indicate that the system is still
686 operational. This is mainly useful to kernel hackers who are
687 debugging unstable kernels.
689 The LART uses the same LED for both Timer LED and CPU usage LED
690 functions. You may choose to use both, but the Timer LED function
691 will overrule the CPU usage LED.
694 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
695 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
698 If you say Y here, the red LED will be used to give a good real
699 time indication of CPU usage, by lighting whenever the idle task
700 is not currently executing.
702 The LART uses the same LED for both Timer LED and CPU usage LED
703 functions. You may choose to use both, but the Timer LED function
704 will overrule the CPU usage LED.
706 config ALIGNMENT_TRAP
708 depends on CPU_CP15_MMU
709 default y if !ARCH_EBSA110
711 ARM processors cannot fetch/store information which is not
712 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
713 address divisible by 4. On 32-bit ARM processors, these non-aligned
714 fetch/store instructions will be emulated in software if you say
715 here, which has a severe performance impact. This is necessary for
716 correct operation of some network protocols. With an IP-only
717 configuration it is safe to say N, otherwise say Y.
723 # Compressed boot loader in ROM. Yes, we really want to ask about
724 # TEXT and BSS so we preserve their values in the config files.
725 config ZBOOT_ROM_TEXT
726 hex "Compressed ROM boot loader base address"
729 The physical address at which the ROM-able zImage is to be
730 placed in the target. Platforms which normally make use of
731 ROM-able zImage formats normally set this to a suitable
732 value in their defconfig file.
734 If ZBOOT_ROM is not enabled, this has no effect.
737 hex "Compressed ROM boot loader BSS address"
740 The base address of an area of read/write memory in the target
741 for the ROM-able zImage which must be available while the
742 decompressor is running. It must be large enough to hold the
743 entire decompressed kernel plus an additional 128 KiB.
744 Platforms which normally make use of ROM-able zImage formats
745 normally set this to a suitable value in their defconfig file.
747 If ZBOOT_ROM is not enabled, this has no effect.
750 bool "Compressed boot loader in ROM/flash"
751 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
753 Say Y here if you intend to execute your compressed kernel image
754 (zImage) directly from ROM or flash. If unsure, say N.
757 string "Default kernel command string"
760 On some architectures (EBSA110 and CATS), there is currently no way
761 for the boot loader to pass arguments to the kernel. For these
762 architectures, you should supply some command-line options at build
763 time by entering them here. As a minimum, you should specify the
764 memory size and the root device (e.g., mem=64M root=/dev/nfs).
767 bool "Kernel Execute-In-Place from ROM"
768 depends on !ZBOOT_ROM
770 Execute-In-Place allows the kernel to run from non-volatile storage
771 directly addressable by the CPU, such as NOR flash. This saves RAM
772 space since the text section of the kernel is not loaded from flash
773 to RAM. Read-write sections, such as the data section and stack,
774 are still copied to RAM. The XIP kernel is not compressed since
775 it has to run directly from flash, so it will take more space to
776 store it. The flash address used to link the kernel object files,
777 and for storing it, is configuration dependent. Therefore, if you
778 say Y here, you must know the proper physical address where to
779 store the kernel image depending on your own flash memory usage.
781 Also note that the make target becomes "make xipImage" rather than
782 "make zImage" or "make Image". The final kernel binary to put in
783 ROM memory will be arch/arm/boot/xipImage.
788 hex "XIP Kernel Physical Location"
789 depends on XIP_KERNEL
792 This is the physical address in your flash memory the kernel will
793 be linked for and stored to. This address is dependent on your
797 bool "Kexec system call (EXPERIMENTAL)"
798 depends on EXPERIMENTAL
800 kexec is a system call that implements the ability to shutdown your
801 current kernel, and to start another kernel. It is like a reboot
802 but it is indepedent of the system firmware. And like a reboot
803 you can start any kernel with it, not just Linux.
805 It is an ongoing process to be certain the hardware in a machine
806 is properly shutdown, so do not be surprised if this code does not
807 initially work for you. It may help to enable device hotplugging
812 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
814 menu "CPU Frequency scaling"
816 source "drivers/cpufreq/Kconfig"
818 config CPU_FREQ_SA1100
820 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
823 config CPU_FREQ_SA1110
825 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
828 config CPU_FREQ_INTEGRATOR
829 tristate "CPUfreq driver for ARM Integrator CPUs"
830 depends on ARCH_INTEGRATOR && CPU_FREQ
833 This enables the CPUfreq driver for ARM Integrator CPUs.
835 For details, take a look at <file:Documentation/cpu-freq>.
840 tristate "CPUfreq driver for i.MX CPUs"
841 depends on ARCH_IMX && CPU_FREQ
844 This enables the CPUfreq driver for i.MX CPUs.
852 menu "Floating point emulation"
854 comment "At least one emulation must be selected"
857 bool "NWFPE math emulation"
858 depends on !AEABI || OABI_COMPAT
860 Say Y to include the NWFPE floating point emulator in the kernel.
861 This is necessary to run most binaries. Linux does not currently
862 support floating point hardware so you need to say Y here even if
863 your machine has an FPA or floating point co-processor podule.
865 You may say N here if you are going to load the Acorn FPEmulator
869 bool "Support extended precision"
872 Say Y to include 80-bit support in the kernel floating-point
873 emulator. Otherwise, only 32 and 64-bit support is compiled in.
874 Note that gcc does not generate 80-bit operations by default,
875 so in most cases this option only enlarges the size of the
876 floating point emulator without any good reason.
878 You almost surely want to say N here.
881 bool "FastFPE math emulation (EXPERIMENTAL)"
882 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
884 Say Y here to include the FAST floating point emulator in the kernel.
885 This is an experimental much faster emulator which now also has full
886 precision for the mantissa. It does not support any exceptions.
887 It is very simple, and approximately 3-6 times faster than NWFPE.
889 It should be sufficient for most programs. It may be not suitable
890 for scientific calculations, but you have to check this for yourself.
891 If you do not feel you need a faster FP emulation you should better
895 bool "VFP-format floating point maths"
896 depends on CPU_V6 || CPU_ARM926T
898 Say Y to include VFP support code in the kernel. This is needed
899 if your hardware includes a VFP unit.
901 Please see <file:Documentation/arm/VFP/release-notes.txt> for
902 release notes and additional status information.
904 Say N if your target does not have VFP hardware.
908 menu "Userspace binary formats"
910 source "fs/Kconfig.binfmt"
913 tristate "RISC OS personality"
916 Say Y here to include the kernel code necessary if you want to run
917 Acorn RISC OS/Arthur binaries under Linux. This code is still very
918 experimental; if this sounds frightening, say N and sleep in peace.
919 You can also say M here to compile this support as a module (which
920 will be called arthur).
924 menu "Power management options"
926 source "kernel/power/Kconfig"
932 menu "Device Drivers"
934 source "drivers/base/Kconfig"
936 source "drivers/connector/Kconfig"
938 if ALIGNMENT_TRAP || !CPU_CP15_MMU
939 source "drivers/mtd/Kconfig"
942 source "drivers/parport/Kconfig"
944 source "drivers/pnp/Kconfig"
946 source "drivers/block/Kconfig"
948 source "drivers/acorn/block/Kconfig"
950 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
951 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
952 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
954 source "drivers/ide/Kconfig"
957 source "drivers/scsi/Kconfig"
959 source "drivers/ata/Kconfig"
961 source "drivers/md/Kconfig"
963 source "drivers/message/fusion/Kconfig"
965 source "drivers/ieee1394/Kconfig"
967 source "drivers/message/i2o/Kconfig"
969 source "drivers/net/Kconfig"
971 source "drivers/isdn/Kconfig"
973 # input before char - char/joystick depends on it. As does USB.
975 source "drivers/input/Kconfig"
977 source "drivers/char/Kconfig"
979 source "drivers/i2c/Kconfig"
981 source "drivers/spi/Kconfig"
983 source "drivers/w1/Kconfig"
985 source "drivers/hwmon/Kconfig"
987 #source "drivers/l3/Kconfig"
989 source "drivers/misc/Kconfig"
991 source "drivers/mfd/Kconfig"
993 source "drivers/leds/Kconfig"
995 source "drivers/media/Kconfig"
997 source "drivers/video/Kconfig"
999 source "sound/Kconfig"
1001 source "drivers/hid/Kconfig"
1003 source "drivers/usb/Kconfig"
1005 source "drivers/mmc/Kconfig"
1007 source "drivers/rtc/Kconfig"
1013 source "arch/arm/oprofile/Kconfig"
1015 source "arch/arm/Kconfig.debug"
1017 source "security/Kconfig"
1019 source "crypto/Kconfig"
1021 source "lib/Kconfig"