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 STACKTRACE_SUPPORT
74 config LOCKDEP_SUPPORT
78 config TRACE_IRQFLAGS_SUPPORT
82 config HARDIRQS_SW_RESEND
86 config GENERIC_IRQ_PROBE
90 config RWSEM_GENERIC_SPINLOCK
94 config RWSEM_XCHGADD_ALGORITHM
97 config ARCH_HAS_ILOG2_U32
101 config ARCH_HAS_ILOG2_U64
105 config GENERIC_HWEIGHT
109 config GENERIC_CALIBRATE_DELAY
113 config GENERIC_BUST_SPINLOCK
116 config ARCH_MAY_HAVE_PC_FDC
123 config GENERIC_ISA_DMA
134 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
135 default DRAM_BASE if REMAP_VECTORS_TO_RAM
138 The base address of exception vectors.
140 source "init/Kconfig"
145 prompt "ARM system type"
146 default ARCH_VERSATILE
149 bool "Agilent AAEC-2000 based"
152 This enables support for systems based on the Agilent AAEC-2000
154 config ARCH_INTEGRATOR
155 bool "ARM Ltd. Integrator family"
159 Support for ARM's Integrator platform.
162 bool "ARM Ltd. RealView family"
166 This enables support for ARM Ltd RealView boards.
168 config ARCH_VERSATILE
169 bool "ARM Ltd. Versatile family"
174 This enables support for ARM Ltd Versatile board.
180 This enables support for systems based on the Atmel AT91RM9200
181 and AT91SAM9xxx processors.
184 bool "Cirrus CL-PS7500FE"
189 Support for the Cirrus Logic PS7500FE system-on-a-chip.
192 bool "Cirrus Logic CLPS711x/EP721x-based"
194 Support for Cirrus Logic 711x/721x based boards.
199 select FOOTBRIDGE_ADDIN
201 Support for Intel's EBSA285 companion chip.
208 This is an evaluation board for the StrongARM processor available
209 from Digital. It has limited hardware on-board, including an
210 Ethernet interface, two PCMCIA sockets, two serial ports and a
218 This enables support for the Cirrus EP93xx series of CPUs.
220 config ARCH_FOOTBRIDGE
224 Support for systems based on the DC21285 companion chip
225 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
228 bool "Hilscher NetX based"
231 This enables support for systems based on the Hilscher NetX Soc
234 bool "Hynix HMS720x-based"
237 This enables support for systems based on the Hynix HMS720x
242 Support for Motorola's i.MX family of processors (MX1, MXL).
250 Support for Intel's 80219 and IOP32X (XScale) family of
259 Support for Intel's IOP33X (XScale) family of processors.
267 Support for Intel's IOP13XX (XScale) family of processors.
274 Support for Intel's IXP4XX (XScale) family of processors.
277 bool "IXP2400/2800-based"
281 Support for Intel's IXP2400/2800 (XScale) family of processors.
288 Support for Intel's IXP23xx (XScale) family of processors.
294 Say Y here if you intend to run this kernel on a LinkUp Systems
295 L7200 Software Development Board which uses an ARM720T processor.
296 Information on this board can be obtained at:
298 <http://www.linkupsys.com/>
300 If you have any questions or comments about the Linux kernel port
301 to this board, send e-mail to <sjhill@cotw.com>.
304 bool "NetSilicon NS9xxx"
306 Say Y here if you intend to run this kernel on a NetSilicon NS9xxx
309 <http://www.digi.com/products/microprocessors/index.jsp>
312 bool "Philips Nexperia PNX4008 Mobile"
314 This enables support for Philips PNX4008 mobile platform.
323 Support for Intel's PXA2XX processor line.
330 select ARCH_MAY_HAVE_PC_FDC
334 On the Acorn Risc-PC, Linux can support the internal IDE disk and
335 CD-ROM interface, serial and parallel port, and the floppy drive.
340 select ARCH_DISCONTIGMEM_ENABLE
344 Support for StrongARM 11x0 based boards.
347 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
350 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
351 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
352 the Samsung SMDK2410 development board (and derivatives).
360 Support for the StrongARM based Digital DNARD machine, also known
361 as "Shark" (<http://www.shark-linux.de/shark.html>).
366 Say Y here for systems based on one of the Sharp LH7A40X
367 System on a Chip processors. These CPUs include an ARM922T
368 core with a wide array of integrated devices for
369 hand-held and low-power applications.
375 Support for TI's OMAP platform (OMAP1 and OMAP2).
379 source "arch/arm/mach-clps711x/Kconfig"
381 source "arch/arm/mach-ep93xx/Kconfig"
383 source "arch/arm/mach-footbridge/Kconfig"
385 source "arch/arm/mach-integrator/Kconfig"
387 source "arch/arm/mach-iop32x/Kconfig"
389 source "arch/arm/mach-iop33x/Kconfig"
391 source "arch/arm/mach-iop13xx/Kconfig"
393 source "arch/arm/mach-ixp4xx/Kconfig"
395 source "arch/arm/mach-ixp2000/Kconfig"
397 source "arch/arm/mach-ixp23xx/Kconfig"
399 source "arch/arm/mach-pxa/Kconfig"
401 source "arch/arm/mach-sa1100/Kconfig"
403 source "arch/arm/plat-omap/Kconfig"
405 source "arch/arm/mach-omap1/Kconfig"
407 source "arch/arm/mach-omap2/Kconfig"
409 source "arch/arm/plat-s3c24xx/Kconfig"
412 source "arch/arm/mach-s3c2400/Kconfig"
413 source "arch/arm/mach-s3c2410/Kconfig"
414 source "arch/arm/mach-s3c2412/Kconfig"
415 source "arch/arm/mach-s3c2440/Kconfig"
416 source "arch/arm/mach-s3c2442/Kconfig"
417 source "arch/arm/mach-s3c2443/Kconfig"
420 source "arch/arm/mach-lh7a40x/Kconfig"
422 source "arch/arm/mach-imx/Kconfig"
424 source "arch/arm/mach-h720x/Kconfig"
426 source "arch/arm/mach-versatile/Kconfig"
428 source "arch/arm/mach-aaec2000/Kconfig"
430 source "arch/arm/mach-realview/Kconfig"
432 source "arch/arm/mach-at91/Kconfig"
434 source "arch/arm/mach-netx/Kconfig"
436 source "arch/arm/mach-ns9xxx/Kconfig"
438 # Definitions to make life easier
445 source arch/arm/mm/Kconfig
448 bool "Enable iWMMXt support"
449 depends on CPU_XSCALE || CPU_XSC3
452 Enable support for iWMMXt context switching at run time if
453 running on a CPU that supports it.
455 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
458 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
462 source "arch/arm/Kconfig-nommu"
467 source "arch/arm/common/Kconfig"
469 config FORCE_MAX_ZONEORDER
482 Find out whether you have ISA slots on your motherboard. ISA is the
483 name of a bus system, i.e. the way the CPU talks to the other stuff
484 inside your box. Other bus systems are PCI, EISA, MicroChannel
485 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
486 newer boards don't support it. If you have ISA, say Y, otherwise N.
488 # Select ISA DMA controller support
493 # Select ISA DMA interface
498 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
500 Find out whether you have a PCI motherboard. PCI is the name of a
501 bus system, i.e. the way the CPU talks to the other stuff inside
502 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
503 VESA. If you have PCI, say Y, otherwise N.
505 The PCI-HOWTO, available from
506 <http://www.tldp.org/docs.html#howto>, contains valuable
507 information about which PCI hardware does work under Linux and which
510 # Select the host bridge type
511 config PCI_HOST_VIA82C505
513 depends on PCI && ARCH_SHARK
516 source "drivers/pci/Kconfig"
518 source "drivers/pcmcia/Kconfig"
522 menu "Kernel Features"
525 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
526 depends on EXPERIMENTAL && REALVIEW_MPCORE
528 This enables support for systems with more than one CPU. If you have
529 a system with only one CPU, like most personal computers, say N. If
530 you have a system with more than one CPU, say Y.
532 If you say N here, the kernel will run on single and multiprocessor
533 machines, but will use only one CPU of a multiprocessor machine. If
534 you say Y here, the kernel will run on many, but not all, single
535 processor machines. On a single processor machine, the kernel will
536 run faster if you say N here.
538 See also the <file:Documentation/smp.txt>,
539 <file:Documentation/i386/IO-APIC.txt>,
540 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
541 <http://www.linuxdoc.org/docs.html#howto>.
543 If you don't know what to do here, say N.
546 int "Maximum number of CPUs (2-32)"
552 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
553 depends on SMP && HOTPLUG && EXPERIMENTAL
555 Say Y here to experiment with turning CPUs off and on. CPUs
556 can be controlled through /sys/devices/system/cpu.
559 bool "Use local timer interrupts"
560 depends on SMP && REALVIEW_MPCORE
563 Enable support for local timers on SMP platforms, rather then the
564 legacy IPI broadcast method. Local timers allows the system
565 accounting to be spread across the timer interval, preventing a
566 "thundering herd" at every timer tick.
569 bool "Preemptible Kernel (EXPERIMENTAL)"
570 depends on EXPERIMENTAL
572 This option reduces the latency of the kernel when reacting to
573 real-time or interactive events by allowing a low priority process to
574 be preempted even if it is in kernel mode executing a system call.
575 This allows applications to run more reliably even when the system is
578 Say Y here if you are building a kernel for a desktop, embedded
579 or real-time system. Say N if you are unsure.
582 bool "Dynamic tick timer"
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 default y if ARCH_EBSA110
682 If you say Y here, one of the system LEDs (the green one on the
683 NetWinder, the amber one on the EBSA285, or the red one on the LART)
684 will flash regularly to indicate that the system is still
685 operational. This is mainly useful to kernel hackers who are
686 debugging unstable kernels.
688 The LART uses the same LED for both Timer LED and CPU usage LED
689 functions. You may choose to use both, but the Timer LED function
690 will overrule the CPU usage LED.
693 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
694 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
697 If you say Y here, the red LED will be used to give a good real
698 time indication of CPU usage, by lighting whenever the idle task
699 is not currently executing.
701 The LART uses the same LED for both Timer LED and CPU usage LED
702 functions. You may choose to use both, but the Timer LED function
703 will overrule the CPU usage LED.
705 config ALIGNMENT_TRAP
707 depends on CPU_CP15_MMU
708 default y if !ARCH_EBSA110
710 ARM processors cannot fetch/store information which is not
711 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
712 address divisible by 4. On 32-bit ARM processors, these non-aligned
713 fetch/store instructions will be emulated in software if you say
714 here, which has a severe performance impact. This is necessary for
715 correct operation of some network protocols. With an IP-only
716 configuration it is safe to say N, otherwise say Y.
722 # Compressed boot loader in ROM. Yes, we really want to ask about
723 # TEXT and BSS so we preserve their values in the config files.
724 config ZBOOT_ROM_TEXT
725 hex "Compressed ROM boot loader base address"
728 The physical address at which the ROM-able zImage is to be
729 placed in the target. Platforms which normally make use of
730 ROM-able zImage formats normally set this to a suitable
731 value in their defconfig file.
733 If ZBOOT_ROM is not enabled, this has no effect.
736 hex "Compressed ROM boot loader BSS address"
739 The base address of an area of read/write memory in the target
740 for the ROM-able zImage which must be available while the
741 decompressor is running. It must be large enough to hold the
742 entire decompressed kernel plus an additional 128 KiB.
743 Platforms which normally make use of ROM-able zImage formats
744 normally set this to a suitable value in their defconfig file.
746 If ZBOOT_ROM is not enabled, this has no effect.
749 bool "Compressed boot loader in ROM/flash"
750 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
752 Say Y here if you intend to execute your compressed kernel image
753 (zImage) directly from ROM or flash. If unsure, say N.
756 string "Default kernel command string"
759 On some architectures (EBSA110 and CATS), there is currently no way
760 for the boot loader to pass arguments to the kernel. For these
761 architectures, you should supply some command-line options at build
762 time by entering them here. As a minimum, you should specify the
763 memory size and the root device (e.g., mem=64M root=/dev/nfs).
766 bool "Kernel Execute-In-Place from ROM"
767 depends on !ZBOOT_ROM
769 Execute-In-Place allows the kernel to run from non-volatile storage
770 directly addressable by the CPU, such as NOR flash. This saves RAM
771 space since the text section of the kernel is not loaded from flash
772 to RAM. Read-write sections, such as the data section and stack,
773 are still copied to RAM. The XIP kernel is not compressed since
774 it has to run directly from flash, so it will take more space to
775 store it. The flash address used to link the kernel object files,
776 and for storing it, is configuration dependent. Therefore, if you
777 say Y here, you must know the proper physical address where to
778 store the kernel image depending on your own flash memory usage.
780 Also note that the make target becomes "make xipImage" rather than
781 "make zImage" or "make Image". The final kernel binary to put in
782 ROM memory will be arch/arm/boot/xipImage.
787 hex "XIP Kernel Physical Location"
788 depends on XIP_KERNEL
791 This is the physical address in your flash memory the kernel will
792 be linked for and stored to. This address is dependent on your
796 bool "Kexec system call (EXPERIMENTAL)"
797 depends on EXPERIMENTAL
799 kexec is a system call that implements the ability to shutdown your
800 current kernel, and to start another kernel. It is like a reboot
801 but it is indepedent of the system firmware. And like a reboot
802 you can start any kernel with it, not just Linux.
804 It is an ongoing process to be certain the hardware in a machine
805 is properly shutdown, so do not be surprised if this code does not
806 initially work for you. It may help to enable device hotplugging
811 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
813 menu "CPU Frequency scaling"
815 source "drivers/cpufreq/Kconfig"
817 config CPU_FREQ_SA1100
819 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
822 config CPU_FREQ_SA1110
824 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
827 config CPU_FREQ_INTEGRATOR
828 tristate "CPUfreq driver for ARM Integrator CPUs"
829 depends on ARCH_INTEGRATOR && CPU_FREQ
832 This enables the CPUfreq driver for ARM Integrator CPUs.
834 For details, take a look at <file:Documentation/cpu-freq>.
839 tristate "CPUfreq driver for i.MX CPUs"
840 depends on ARCH_IMX && CPU_FREQ
843 This enables the CPUfreq driver for i.MX CPUs.
851 menu "Floating point emulation"
853 comment "At least one emulation must be selected"
856 bool "NWFPE math emulation"
857 depends on !AEABI || OABI_COMPAT
859 Say Y to include the NWFPE floating point emulator in the kernel.
860 This is necessary to run most binaries. Linux does not currently
861 support floating point hardware so you need to say Y here even if
862 your machine has an FPA or floating point co-processor podule.
864 You may say N here if you are going to load the Acorn FPEmulator
868 bool "Support extended precision"
871 Say Y to include 80-bit support in the kernel floating-point
872 emulator. Otherwise, only 32 and 64-bit support is compiled in.
873 Note that gcc does not generate 80-bit operations by default,
874 so in most cases this option only enlarges the size of the
875 floating point emulator without any good reason.
877 You almost surely want to say N here.
880 bool "FastFPE math emulation (EXPERIMENTAL)"
881 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
883 Say Y here to include the FAST floating point emulator in the kernel.
884 This is an experimental much faster emulator which now also has full
885 precision for the mantissa. It does not support any exceptions.
886 It is very simple, and approximately 3-6 times faster than NWFPE.
888 It should be sufficient for most programs. It may be not suitable
889 for scientific calculations, but you have to check this for yourself.
890 If you do not feel you need a faster FP emulation you should better
894 bool "VFP-format floating point maths"
895 depends on CPU_V6 || CPU_ARM926T
897 Say Y to include VFP support code in the kernel. This is needed
898 if your hardware includes a VFP unit.
900 Please see <file:Documentation/arm/VFP/release-notes.txt> for
901 release notes and additional status information.
903 Say N if your target does not have VFP hardware.
907 menu "Userspace binary formats"
909 source "fs/Kconfig.binfmt"
912 tristate "RISC OS personality"
915 Say Y here to include the kernel code necessary if you want to run
916 Acorn RISC OS/Arthur binaries under Linux. This code is still very
917 experimental; if this sounds frightening, say N and sleep in peace.
918 You can also say M here to compile this support as a module (which
919 will be called arthur).
923 menu "Power management options"
925 source "kernel/power/Kconfig"
931 menu "Device Drivers"
933 source "drivers/base/Kconfig"
935 source "drivers/connector/Kconfig"
937 if ALIGNMENT_TRAP || !CPU_CP15_MMU
938 source "drivers/mtd/Kconfig"
941 source "drivers/parport/Kconfig"
943 source "drivers/pnp/Kconfig"
945 source "drivers/block/Kconfig"
947 source "drivers/acorn/block/Kconfig"
949 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
950 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
951 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
953 source "drivers/ide/Kconfig"
956 source "drivers/scsi/Kconfig"
958 source "drivers/ata/Kconfig"
960 source "drivers/md/Kconfig"
962 source "drivers/message/fusion/Kconfig"
964 source "drivers/ieee1394/Kconfig"
966 source "drivers/message/i2o/Kconfig"
968 source "drivers/net/Kconfig"
970 source "drivers/isdn/Kconfig"
972 # input before char - char/joystick depends on it. As does USB.
974 source "drivers/input/Kconfig"
976 source "drivers/char/Kconfig"
978 source "drivers/i2c/Kconfig"
980 source "drivers/spi/Kconfig"
982 source "drivers/w1/Kconfig"
984 source "drivers/hwmon/Kconfig"
986 #source "drivers/l3/Kconfig"
988 source "drivers/misc/Kconfig"
990 source "drivers/mfd/Kconfig"
992 source "drivers/leds/Kconfig"
994 source "drivers/media/Kconfig"
996 source "drivers/video/Kconfig"
998 source "sound/Kconfig"
1000 source "drivers/hid/Kconfig"
1002 source "drivers/usb/Kconfig"
1004 source "drivers/mmc/Kconfig"
1006 source "drivers/rtc/Kconfig"
1012 source "arch/arm/oprofile/Kconfig"
1014 source "arch/arm/Kconfig.debug"
1016 source "security/Kconfig"
1018 source "crypto/Kconfig"
1020 source "lib/Kconfig"