2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
13 The ARM series is a line of low-power-consumption RISC chip designs
14 licensed by ARM Ltd and targeted at embedded applications and
15 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
16 manufactured, but legacy ARM-based PC hardware remains popular in
17 Europe. There is an ARM Linux project with a web page at
18 <http://www.arm.linux.org.uk/>.
31 The Extended Industry Standard Architecture (EISA) bus was
32 developed as an open alternative to the IBM MicroChannel bus.
34 The EISA bus provided some of the features of the IBM MicroChannel
35 bus while maintaining backward compatibility with cards made for
36 the older ISA bus. The EISA bus saw limited use between 1988 and
37 1995 when it was made obsolete by the PCI bus.
39 Say Y here if you are building a kernel for an EISA-based machine.
49 MicroChannel Architecture is found in some IBM PS/2 machines and
50 laptops. It is a bus system similar to PCI or ISA. See
51 <file:Documentation/mca.txt> (and especially the web page given
52 there) before attempting to build an MCA bus kernel.
54 config GENERIC_HARDIRQS
58 config TRACE_IRQFLAGS_SUPPORT
62 config HARDIRQS_SW_RESEND
66 config GENERIC_IRQ_PROBE
70 config RWSEM_GENERIC_SPINLOCK
74 config RWSEM_XCHGADD_ALGORITHM
77 config ARCH_HAS_ILOG2_U32
81 config ARCH_HAS_ILOG2_U64
85 config GENERIC_HWEIGHT
89 config GENERIC_CALIBRATE_DELAY
93 config GENERIC_BUST_SPINLOCK
96 config ARCH_MAY_HAVE_PC_FDC
99 config GENERIC_ISA_DMA
110 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
111 default DRAM_BASE if REMAP_VECTORS_TO_RAM
114 The base address of exception vectors.
116 source "init/Kconfig"
121 prompt "ARM system type"
122 default ARCH_VERSATILE
125 bool "Agilent AAEC-2000 based"
128 This enables support for systems based on the Agilent AAEC-2000
130 config ARCH_INTEGRATOR
131 bool "ARM Ltd. Integrator family"
135 Support for ARM's Integrator platform.
138 bool "ARM Ltd. RealView family"
142 This enables support for ARM Ltd RealView boards.
144 config ARCH_VERSATILE
145 bool "ARM Ltd. Versatile family"
150 This enables support for ARM Ltd Versatile board.
155 This enables support for systems based on the Atmel AT91RM9200
156 and AT91SAM9xxx processors.
159 bool "Cirrus CL-PS7500FE"
163 Support for the Cirrus Logic PS7500FE system-on-a-chip.
166 bool "Cirrus Logic CLPS711x/EP721x-based"
168 Support for Cirrus Logic 711x/721x based boards.
173 select FOOTBRIDGE_ADDIN
175 Support for Intel's EBSA285 companion chip.
181 This is an evaluation board for the StrongARM processor available
182 from Digital. It has limited hardware on-board, including an
183 Ethernet interface, two PCMCIA sockets, two serial ports and a
191 This enables support for the Cirrus EP93xx series of CPUs.
193 config ARCH_FOOTBRIDGE
197 Support for systems based on the DC21285 companion chip
198 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
201 bool "Hilscher NetX based"
204 This enables support for systems based on the Hilscher NetX Soc
207 bool "Hynix HMS720x-based"
210 This enables support for systems based on the Hynix HMS720x
215 Support for Motorola's i.MX family of processors (MX1, MXL).
223 Support for Intel's 80219 and IOP32X (XScale) family of
232 Support for Intel's IOP33X (XScale) family of processors.
238 Support for Intel's IOP13XX (XScale) family of processors.
245 Support for Intel's IXP4XX (XScale) family of processors.
248 bool "IXP2400/2800-based"
252 Support for Intel's IXP2400/2800 (XScale) family of processors.
259 Support for Intel's IXP23xx (XScale) family of processors.
265 Say Y here if you intend to run this kernel on a LinkUp Systems
266 L7200 Software Development Board which uses an ARM720T processor.
267 Information on this board can be obtained at:
269 <http://www.linkupsys.com/>
271 If you have any questions or comments about the Linux kernel port
272 to this board, send e-mail to <sjhill@cotw.com>.
275 bool "Philips Nexperia PNX4008 Mobile"
277 This enables support for Philips PNX4008 mobile platform.
285 Support for Intel's PXA2XX processor line.
292 select ARCH_MAY_HAVE_PC_FDC
295 On the Acorn Risc-PC, Linux can support the internal IDE disk and
296 CD-ROM interface, serial and parallel port, and the floppy drive.
301 select ARCH_DISCONTIGMEM_ENABLE
304 Support for StrongARM 11x0 based boards.
307 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442"
309 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
310 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
311 the Samsung SMDK2410 development board (and derivatives).
319 Support for the StrongARM based Digital DNARD machine, also known
320 as "Shark" (<http://www.shark-linux.de/shark.html>).
325 Say Y here for systems based on one of the Sharp LH7A40X
326 System on a Chip processors. These CPUs include an ARM922T
327 core with a wide array of integrated devices for
328 hand-held and low-power applications.
333 Support for TI's OMAP platform (OMAP1 and OMAP2).
337 source "arch/arm/mach-clps711x/Kconfig"
339 source "arch/arm/mach-ep93xx/Kconfig"
341 source "arch/arm/mach-footbridge/Kconfig"
343 source "arch/arm/mach-integrator/Kconfig"
345 source "arch/arm/mach-iop32x/Kconfig"
347 source "arch/arm/mach-iop33x/Kconfig"
349 source "arch/arm/mach-iop13xx/Kconfig"
351 source "arch/arm/mach-ixp4xx/Kconfig"
353 source "arch/arm/mach-ixp2000/Kconfig"
355 source "arch/arm/mach-ixp23xx/Kconfig"
357 source "arch/arm/mach-pxa/Kconfig"
359 source "arch/arm/mach-sa1100/Kconfig"
361 source "arch/arm/plat-omap/Kconfig"
363 source "arch/arm/mach-omap1/Kconfig"
365 source "arch/arm/mach-omap2/Kconfig"
367 source "arch/arm/mach-s3c2410/Kconfig"
369 source "arch/arm/mach-lh7a40x/Kconfig"
371 source "arch/arm/mach-imx/Kconfig"
373 source "arch/arm/mach-h720x/Kconfig"
375 source "arch/arm/mach-versatile/Kconfig"
377 source "arch/arm/mach-aaec2000/Kconfig"
379 source "arch/arm/mach-realview/Kconfig"
381 source "arch/arm/mach-at91rm9200/Kconfig"
383 source "arch/arm/mach-netx/Kconfig"
385 # Definitions to make life easier
392 source arch/arm/mm/Kconfig
395 bool "Enable iWMMXt support"
396 depends CPU_XSCALE || CPU_XSC3
399 Enable support for iWMMXt context switching at run time if
400 running on a CPU that supports it.
402 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
405 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
409 source "arch/arm/Kconfig-nommu"
414 source "arch/arm/common/Kconfig"
416 config FORCE_MAX_ZONEORDER
429 Find out whether you have ISA slots on your motherboard. ISA is the
430 name of a bus system, i.e. the way the CPU talks to the other stuff
431 inside your box. Other bus systems are PCI, EISA, MicroChannel
432 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
433 newer boards don't support it. If you have ISA, say Y, otherwise N.
435 # Select ISA DMA controller support
440 # Select ISA DMA interface
445 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
447 Find out whether you have a PCI motherboard. PCI is the name of a
448 bus system, i.e. the way the CPU talks to the other stuff inside
449 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
450 VESA. If you have PCI, say Y, otherwise N.
452 The PCI-HOWTO, available from
453 <http://www.tldp.org/docs.html#howto>, contains valuable
454 information about which PCI hardware does work under Linux and which
457 # Select the host bridge type
458 config PCI_HOST_VIA82C505
460 depends on PCI && ARCH_SHARK
463 source "drivers/pci/Kconfig"
465 source "drivers/pcmcia/Kconfig"
469 menu "Kernel Features"
472 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
473 depends on EXPERIMENTAL && REALVIEW_MPCORE
475 This enables support for systems with more than one CPU. If you have
476 a system with only one CPU, like most personal computers, say N. If
477 you have a system with more than one CPU, say Y.
479 If you say N here, the kernel will run on single and multiprocessor
480 machines, but will use only one CPU of a multiprocessor machine. If
481 you say Y here, the kernel will run on many, but not all, single
482 processor machines. On a single processor machine, the kernel will
483 run faster if you say N here.
485 See also the <file:Documentation/smp.txt>,
486 <file:Documentation/i386/IO-APIC.txt>,
487 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
488 <http://www.linuxdoc.org/docs.html#howto>.
490 If you don't know what to do here, say N.
493 int "Maximum number of CPUs (2-32)"
499 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
500 depends on SMP && HOTPLUG && EXPERIMENTAL
502 Say Y here to experiment with turning CPUs off and on. CPUs
503 can be controlled through /sys/devices/system/cpu.
506 bool "Use local timer interrupts"
507 depends on SMP && REALVIEW_MPCORE
510 Enable support for local timers on SMP platforms, rather then the
511 legacy IPI broadcast method. Local timers allows the system
512 accounting to be spread across the timer interval, preventing a
513 "thundering herd" at every timer tick.
516 bool "Preemptible Kernel (EXPERIMENTAL)"
517 depends on EXPERIMENTAL
519 This option reduces the latency of the kernel when reacting to
520 real-time or interactive events by allowing a low priority process to
521 be preempted even if it is in kernel mode executing a system call.
522 This allows applications to run more reliably even when the system is
525 Say Y here if you are building a kernel for a desktop, embedded
526 or real-time system. Say N if you are unsure.
529 bool "Dynamic tick timer"
531 Select this option if you want to disable continuous timer ticks
532 and have them programmed to occur as required. This option saves
533 power as the system can remain in idle state for longer.
535 By default dynamic tick is disabled during the boot, and can be
536 manually enabled with:
538 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
540 Alternatively, if you want dynamic tick automatically enabled
541 during boot, pass "dyntick=enable" via the kernel command string.
543 Please note that dynamic tick may affect the accuracy of
544 timekeeping on some platforms depending on the implementation.
545 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
546 to have accurate timekeeping with dynamic tick.
550 default 128 if ARCH_L7200
551 default 200 if ARCH_EBSA110 || ARCH_S3C2410
552 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
556 bool "Use the ARM EABI to compile the kernel"
558 This option allows for the kernel to be compiled using the latest
559 ARM ABI (aka EABI). This is only useful if you are using a user
560 space environment that is also compiled with EABI.
562 Since there are major incompatibilities between the legacy ABI and
563 EABI, especially with regard to structure member alignment, this
564 option also changes the kernel syscall calling convention to
565 disambiguate both ABIs and allow for backward compatibility support
566 (selected with CONFIG_OABI_COMPAT).
568 To use this you need GCC version 4.0.0 or later.
571 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
572 depends on AEABI && EXPERIMENTAL
575 This option preserves the old syscall interface along with the
576 new (ARM EABI) one. It also provides a compatibility layer to
577 intercept syscalls that have structure arguments which layout
578 in memory differs between the legacy ABI and the new ARM EABI
579 (only for non "thumb" binaries). This option adds a tiny
580 overhead to all syscalls and produces a slightly larger kernel.
581 If you know you'll be using only pure EABI user space then you
582 can say N here. If this option is not selected and you attempt
583 to execute a legacy ABI binary then the result will be
584 UNPREDICTABLE (in fact it can be predicted that it won't work
585 at all). If in doubt say Y.
587 config ARCH_DISCONTIGMEM_ENABLE
589 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
591 Say Y to support efficient handling of discontiguous physical memory,
592 for architectures which are either NUMA (Non-Uniform Memory Access)
593 or have huge holes in the physical address space for other reasons.
594 See <file:Documentation/vm/numa> for more.
598 default "4" if ARCH_LH7A40X
600 depends on NEED_MULTIPLE_NODES
605 bool "Timer and CPU usage LEDs"
606 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
607 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
608 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
609 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
610 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
611 ARCH_AT91 || MACH_TRIZEPS4
613 If you say Y here, the LEDs on your machine will be used
614 to provide useful information about your current system status.
616 If you are compiling a kernel for a NetWinder or EBSA-285, you will
617 be able to select which LEDs are active using the options below. If
618 you are compiling a kernel for the EBSA-110 or the LART however, the
619 red LED will simply flash regularly to indicate that the system is
620 still functional. It is safe to say Y here if you have a CATS
621 system, but the driver will do nothing.
624 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
625 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
627 default y if ARCH_EBSA110
629 If you say Y here, one of the system LEDs (the green one on the
630 NetWinder, the amber one on the EBSA285, or the red one on the LART)
631 will flash regularly to indicate that the system is still
632 operational. This is mainly useful to kernel hackers who are
633 debugging unstable kernels.
635 The LART uses the same LED for both Timer LED and CPU usage LED
636 functions. You may choose to use both, but the Timer LED function
637 will overrule the CPU usage LED.
640 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
641 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
644 If you say Y here, the red LED will be used to give a good real
645 time indication of CPU usage, by lighting whenever the idle task
646 is not currently executing.
648 The LART uses the same LED for both Timer LED and CPU usage LED
649 functions. You may choose to use both, but the Timer LED function
650 will overrule the CPU usage LED.
652 config ALIGNMENT_TRAP
654 depends on CPU_CP15_MMU
655 default y if !ARCH_EBSA110
657 ARM processors cannot fetch/store information which is not
658 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
659 address divisible by 4. On 32-bit ARM processors, these non-aligned
660 fetch/store instructions will be emulated in software if you say
661 here, which has a severe performance impact. This is necessary for
662 correct operation of some network protocols. With an IP-only
663 configuration it is safe to say N, otherwise say Y.
669 # Compressed boot loader in ROM. Yes, we really want to ask about
670 # TEXT and BSS so we preserve their values in the config files.
671 config ZBOOT_ROM_TEXT
672 hex "Compressed ROM boot loader base address"
675 The physical address at which the ROM-able zImage is to be
676 placed in the target. Platforms which normally make use of
677 ROM-able zImage formats normally set this to a suitable
678 value in their defconfig file.
680 If ZBOOT_ROM is not enabled, this has no effect.
683 hex "Compressed ROM boot loader BSS address"
686 The base address of an area of read/write memory in the target
687 for the ROM-able zImage which must be available while the
688 decompressor is running. It must be large enough to hold the
689 entire decompressed kernel plus an additional 128 KiB.
690 Platforms which normally make use of ROM-able zImage formats
691 normally set this to a suitable value in their defconfig file.
693 If ZBOOT_ROM is not enabled, this has no effect.
696 bool "Compressed boot loader in ROM/flash"
697 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
699 Say Y here if you intend to execute your compressed kernel image
700 (zImage) directly from ROM or flash. If unsure, say N.
703 string "Default kernel command string"
706 On some architectures (EBSA110 and CATS), there is currently no way
707 for the boot loader to pass arguments to the kernel. For these
708 architectures, you should supply some command-line options at build
709 time by entering them here. As a minimum, you should specify the
710 memory size and the root device (e.g., mem=64M root=/dev/nfs).
713 bool "Kernel Execute-In-Place from ROM"
714 depends on !ZBOOT_ROM
716 Execute-In-Place allows the kernel to run from non-volatile storage
717 directly addressable by the CPU, such as NOR flash. This saves RAM
718 space since the text section of the kernel is not loaded from flash
719 to RAM. Read-write sections, such as the data section and stack,
720 are still copied to RAM. The XIP kernel is not compressed since
721 it has to run directly from flash, so it will take more space to
722 store it. The flash address used to link the kernel object files,
723 and for storing it, is configuration dependent. Therefore, if you
724 say Y here, you must know the proper physical address where to
725 store the kernel image depending on your own flash memory usage.
727 Also note that the make target becomes "make xipImage" rather than
728 "make zImage" or "make Image". The final kernel binary to put in
729 ROM memory will be arch/arm/boot/xipImage.
734 hex "XIP Kernel Physical Location"
735 depends on XIP_KERNEL
738 This is the physical address in your flash memory the kernel will
739 be linked for and stored to. This address is dependent on your
744 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
746 menu "CPU Frequency scaling"
748 source "drivers/cpufreq/Kconfig"
750 config CPU_FREQ_SA1100
752 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
755 config CPU_FREQ_SA1110
757 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
760 config CPU_FREQ_INTEGRATOR
761 tristate "CPUfreq driver for ARM Integrator CPUs"
762 depends on ARCH_INTEGRATOR && CPU_FREQ
765 This enables the CPUfreq driver for ARM Integrator CPUs.
767 For details, take a look at <file:Documentation/cpu-freq>.
772 tristate "CPUfreq driver for i.MX CPUs"
773 depends on ARCH_IMX && CPU_FREQ
776 This enables the CPUfreq driver for i.MX CPUs.
784 menu "Floating point emulation"
786 comment "At least one emulation must be selected"
789 bool "NWFPE math emulation"
790 depends on !AEABI || OABI_COMPAT
792 Say Y to include the NWFPE floating point emulator in the kernel.
793 This is necessary to run most binaries. Linux does not currently
794 support floating point hardware so you need to say Y here even if
795 your machine has an FPA or floating point co-processor podule.
797 You may say N here if you are going to load the Acorn FPEmulator
801 bool "Support extended precision"
804 Say Y to include 80-bit support in the kernel floating-point
805 emulator. Otherwise, only 32 and 64-bit support is compiled in.
806 Note that gcc does not generate 80-bit operations by default,
807 so in most cases this option only enlarges the size of the
808 floating point emulator without any good reason.
810 You almost surely want to say N here.
813 bool "FastFPE math emulation (EXPERIMENTAL)"
814 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
816 Say Y here to include the FAST floating point emulator in the kernel.
817 This is an experimental much faster emulator which now also has full
818 precision for the mantissa. It does not support any exceptions.
819 It is very simple, and approximately 3-6 times faster than NWFPE.
821 It should be sufficient for most programs. It may be not suitable
822 for scientific calculations, but you have to check this for yourself.
823 If you do not feel you need a faster FP emulation you should better
827 bool "VFP-format floating point maths"
828 depends on CPU_V6 || CPU_ARM926T
830 Say Y to include VFP support code in the kernel. This is needed
831 if your hardware includes a VFP unit.
833 Please see <file:Documentation/arm/VFP/release-notes.txt> for
834 release notes and additional status information.
836 Say N if your target does not have VFP hardware.
840 menu "Userspace binary formats"
842 source "fs/Kconfig.binfmt"
845 tristate "RISC OS personality"
848 Say Y here to include the kernel code necessary if you want to run
849 Acorn RISC OS/Arthur binaries under Linux. This code is still very
850 experimental; if this sounds frightening, say N and sleep in peace.
851 You can also say M here to compile this support as a module (which
852 will be called arthur).
856 menu "Power management options"
858 source "kernel/power/Kconfig"
861 tristate "Advanced Power Management Emulation"
863 APM is a BIOS specification for saving power using several different
864 techniques. This is mostly useful for battery powered laptops with
865 APM compliant BIOSes. If you say Y here, the system time will be
866 reset after a RESUME operation, the /proc/apm device will provide
867 battery status information, and user-space programs will receive
868 notification of APM "events" (e.g. battery status change).
870 In order to use APM, you will need supporting software. For location
871 and more information, read <file:Documentation/pm.txt> and the
872 Battery Powered Linux mini-HOWTO, available from
873 <http://www.tldp.org/docs.html#howto>.
875 This driver does not spin down disk drives (see the hdparm(8)
876 manpage ("man 8 hdparm") for that), and it doesn't turn off
877 VESA-compliant "green" monitors.
879 Generally, if you don't have a battery in your machine, there isn't
880 much point in using this driver and you should say N. If you get
881 random kernel OOPSes or reboots that don't seem to be related to
882 anything, try disabling/enabling this option (or disabling/enabling
889 menu "Device Drivers"
891 source "drivers/base/Kconfig"
893 source "drivers/connector/Kconfig"
895 if ALIGNMENT_TRAP || !CPU_CP15_MMU
896 source "drivers/mtd/Kconfig"
899 source "drivers/parport/Kconfig"
901 source "drivers/pnp/Kconfig"
903 source "drivers/block/Kconfig"
905 source "drivers/acorn/block/Kconfig"
907 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
908 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
909 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
911 source "drivers/ide/Kconfig"
914 source "drivers/scsi/Kconfig"
916 source "drivers/ata/Kconfig"
918 source "drivers/md/Kconfig"
920 source "drivers/message/fusion/Kconfig"
922 source "drivers/ieee1394/Kconfig"
924 source "drivers/message/i2o/Kconfig"
926 source "drivers/net/Kconfig"
928 source "drivers/isdn/Kconfig"
930 # input before char - char/joystick depends on it. As does USB.
932 source "drivers/input/Kconfig"
934 source "drivers/char/Kconfig"
936 source "drivers/i2c/Kconfig"
938 source "drivers/spi/Kconfig"
940 source "drivers/w1/Kconfig"
942 source "drivers/hwmon/Kconfig"
944 #source "drivers/l3/Kconfig"
946 source "drivers/misc/Kconfig"
948 source "drivers/mfd/Kconfig"
950 source "drivers/leds/Kconfig"
952 source "drivers/media/Kconfig"
954 source "drivers/video/Kconfig"
956 source "sound/Kconfig"
958 source "drivers/hid/Kconfig"
960 source "drivers/usb/Kconfig"
962 source "drivers/mmc/Kconfig"
964 source "drivers/rtc/Kconfig"
970 source "arch/arm/oprofile/Kconfig"
972 source "arch/arm/Kconfig.debug"
974 source "security/Kconfig"
976 source "crypto/Kconfig"