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.
240 Support for Intel's IOP13XX (XScale) family of processors.
247 Support for Intel's IXP4XX (XScale) family of processors.
250 bool "IXP2400/2800-based"
254 Support for Intel's IXP2400/2800 (XScale) family of processors.
261 Support for Intel's IXP23xx (XScale) family of processors.
267 Say Y here if you intend to run this kernel on a LinkUp Systems
268 L7200 Software Development Board which uses an ARM720T processor.
269 Information on this board can be obtained at:
271 <http://www.linkupsys.com/>
273 If you have any questions or comments about the Linux kernel port
274 to this board, send e-mail to <sjhill@cotw.com>.
277 bool "Philips Nexperia PNX4008 Mobile"
279 This enables support for Philips PNX4008 mobile platform.
286 Support for Intel's PXA2XX processor line.
293 select ARCH_MAY_HAVE_PC_FDC
296 On the Acorn Risc-PC, Linux can support the internal IDE disk and
297 CD-ROM interface, serial and parallel port, and the floppy drive.
302 select ARCH_DISCONTIGMEM_ENABLE
305 Support for StrongARM 11x0 based boards.
308 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442"
310 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
311 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
312 the Samsung SMDK2410 development board (and derivatives).
320 Support for the StrongARM based Digital DNARD machine, also known
321 as "Shark" (<http://www.shark-linux.de/shark.html>).
326 Say Y here for systems based on one of the Sharp LH7A40X
327 System on a Chip processors. These CPUs include an ARM922T
328 core with a wide array of integrated devices for
329 hand-held and low-power applications.
334 Support for TI's OMAP platform (OMAP1 and OMAP2).
338 source "arch/arm/mach-clps711x/Kconfig"
340 source "arch/arm/mach-ep93xx/Kconfig"
342 source "arch/arm/mach-footbridge/Kconfig"
344 source "arch/arm/mach-integrator/Kconfig"
346 source "arch/arm/mach-iop32x/Kconfig"
348 source "arch/arm/mach-iop33x/Kconfig"
350 source "arch/arm/mach-iop13xx/Kconfig"
352 source "arch/arm/mach-ixp4xx/Kconfig"
354 source "arch/arm/mach-ixp2000/Kconfig"
356 source "arch/arm/mach-ixp23xx/Kconfig"
358 source "arch/arm/mach-pxa/Kconfig"
360 source "arch/arm/mach-sa1100/Kconfig"
362 source "arch/arm/plat-omap/Kconfig"
364 source "arch/arm/mach-omap1/Kconfig"
366 source "arch/arm/mach-omap2/Kconfig"
368 source "arch/arm/mach-s3c2410/Kconfig"
370 source "arch/arm/mach-lh7a40x/Kconfig"
372 source "arch/arm/mach-imx/Kconfig"
374 source "arch/arm/mach-h720x/Kconfig"
376 source "arch/arm/mach-versatile/Kconfig"
378 source "arch/arm/mach-aaec2000/Kconfig"
380 source "arch/arm/mach-realview/Kconfig"
382 source "arch/arm/mach-at91rm9200/Kconfig"
384 source "arch/arm/mach-netx/Kconfig"
386 # Definitions to make life easier
393 source arch/arm/mm/Kconfig
396 bool "Enable iWMMXt support"
397 depends CPU_XSCALE || CPU_XSC3
400 Enable support for iWMMXt context switching at run time if
401 running on a CPU that supports it.
403 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
406 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
410 source "arch/arm/Kconfig-nommu"
415 source "arch/arm/common/Kconfig"
417 config FORCE_MAX_ZONEORDER
430 Find out whether you have ISA slots on your motherboard. ISA is the
431 name of a bus system, i.e. the way the CPU talks to the other stuff
432 inside your box. Other bus systems are PCI, EISA, MicroChannel
433 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
434 newer boards don't support it. If you have ISA, say Y, otherwise N.
436 # Select ISA DMA controller support
441 # Select ISA DMA interface
446 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
448 Find out whether you have a PCI motherboard. PCI is the name of a
449 bus system, i.e. the way the CPU talks to the other stuff inside
450 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
451 VESA. If you have PCI, say Y, otherwise N.
453 The PCI-HOWTO, available from
454 <http://www.tldp.org/docs.html#howto>, contains valuable
455 information about which PCI hardware does work under Linux and which
458 # Select the host bridge type
459 config PCI_HOST_VIA82C505
461 depends on PCI && ARCH_SHARK
464 source "drivers/pci/Kconfig"
466 source "drivers/pcmcia/Kconfig"
470 menu "Kernel Features"
473 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
474 depends on EXPERIMENTAL && REALVIEW_MPCORE
476 This enables support for systems with more than one CPU. If you have
477 a system with only one CPU, like most personal computers, say N. If
478 you have a system with more than one CPU, say Y.
480 If you say N here, the kernel will run on single and multiprocessor
481 machines, but will use only one CPU of a multiprocessor machine. If
482 you say Y here, the kernel will run on many, but not all, single
483 processor machines. On a single processor machine, the kernel will
484 run faster if you say N here.
486 See also the <file:Documentation/smp.txt>,
487 <file:Documentation/i386/IO-APIC.txt>,
488 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
489 <http://www.linuxdoc.org/docs.html#howto>.
491 If you don't know what to do here, say N.
494 int "Maximum number of CPUs (2-32)"
500 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
501 depends on SMP && HOTPLUG && EXPERIMENTAL
503 Say Y here to experiment with turning CPUs off and on. CPUs
504 can be controlled through /sys/devices/system/cpu.
507 bool "Use local timer interrupts"
508 depends on SMP && REALVIEW_MPCORE
511 Enable support for local timers on SMP platforms, rather then the
512 legacy IPI broadcast method. Local timers allows the system
513 accounting to be spread across the timer interval, preventing a
514 "thundering herd" at every timer tick.
517 bool "Preemptible Kernel (EXPERIMENTAL)"
518 depends on EXPERIMENTAL
520 This option reduces the latency of the kernel when reacting to
521 real-time or interactive events by allowing a low priority process to
522 be preempted even if it is in kernel mode executing a system call.
523 This allows applications to run more reliably even when the system is
526 Say Y here if you are building a kernel for a desktop, embedded
527 or real-time system. Say N if you are unsure.
530 bool "Dynamic tick timer"
532 Select this option if you want to disable continuous timer ticks
533 and have them programmed to occur as required. This option saves
534 power as the system can remain in idle state for longer.
536 By default dynamic tick is disabled during the boot, and can be
537 manually enabled with:
539 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
541 Alternatively, if you want dynamic tick automatically enabled
542 during boot, pass "dyntick=enable" via the kernel command string.
544 Please note that dynamic tick may affect the accuracy of
545 timekeeping on some platforms depending on the implementation.
546 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
547 to have accurate timekeeping with dynamic tick.
551 default 128 if ARCH_L7200
552 default 200 if ARCH_EBSA110 || ARCH_S3C2410
553 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
557 bool "Use the ARM EABI to compile the kernel"
559 This option allows for the kernel to be compiled using the latest
560 ARM ABI (aka EABI). This is only useful if you are using a user
561 space environment that is also compiled with EABI.
563 Since there are major incompatibilities between the legacy ABI and
564 EABI, especially with regard to structure member alignment, this
565 option also changes the kernel syscall calling convention to
566 disambiguate both ABIs and allow for backward compatibility support
567 (selected with CONFIG_OABI_COMPAT).
569 To use this you need GCC version 4.0.0 or later.
572 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
573 depends on AEABI && EXPERIMENTAL
576 This option preserves the old syscall interface along with the
577 new (ARM EABI) one. It also provides a compatibility layer to
578 intercept syscalls that have structure arguments which layout
579 in memory differs between the legacy ABI and the new ARM EABI
580 (only for non "thumb" binaries). This option adds a tiny
581 overhead to all syscalls and produces a slightly larger kernel.
582 If you know you'll be using only pure EABI user space then you
583 can say N here. If this option is not selected and you attempt
584 to execute a legacy ABI binary then the result will be
585 UNPREDICTABLE (in fact it can be predicted that it won't work
586 at all). If in doubt say Y.
588 config ARCH_DISCONTIGMEM_ENABLE
590 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
592 Say Y to support efficient handling of discontiguous physical memory,
593 for architectures which are either NUMA (Non-Uniform Memory Access)
594 or have huge holes in the physical address space for other reasons.
595 See <file:Documentation/vm/numa> for more.
599 default "4" if ARCH_LH7A40X
601 depends on NEED_MULTIPLE_NODES
606 bool "Timer and CPU usage LEDs"
607 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
608 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
609 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
610 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
611 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
612 ARCH_AT91 || MACH_TRIZEPS4
614 If you say Y here, the LEDs on your machine will be used
615 to provide useful information about your current system status.
617 If you are compiling a kernel for a NetWinder or EBSA-285, you will
618 be able to select which LEDs are active using the options below. If
619 you are compiling a kernel for the EBSA-110 or the LART however, the
620 red LED will simply flash regularly to indicate that the system is
621 still functional. It is safe to say Y here if you have a CATS
622 system, but the driver will do nothing.
625 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
626 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
628 default y if ARCH_EBSA110
630 If you say Y here, one of the system LEDs (the green one on the
631 NetWinder, the amber one on the EBSA285, or the red one on the LART)
632 will flash regularly to indicate that the system is still
633 operational. This is mainly useful to kernel hackers who are
634 debugging unstable kernels.
636 The LART uses the same LED for both Timer LED and CPU usage LED
637 functions. You may choose to use both, but the Timer LED function
638 will overrule the CPU usage LED.
641 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
642 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
645 If you say Y here, the red LED will be used to give a good real
646 time indication of CPU usage, by lighting whenever the idle task
647 is not currently executing.
649 The LART uses the same LED for both Timer LED and CPU usage LED
650 functions. You may choose to use both, but the Timer LED function
651 will overrule the CPU usage LED.
653 config ALIGNMENT_TRAP
655 depends on CPU_CP15_MMU
656 default y if !ARCH_EBSA110
658 ARM processors cannot fetch/store information which is not
659 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
660 address divisible by 4. On 32-bit ARM processors, these non-aligned
661 fetch/store instructions will be emulated in software if you say
662 here, which has a severe performance impact. This is necessary for
663 correct operation of some network protocols. With an IP-only
664 configuration it is safe to say N, otherwise say Y.
670 # Compressed boot loader in ROM. Yes, we really want to ask about
671 # TEXT and BSS so we preserve their values in the config files.
672 config ZBOOT_ROM_TEXT
673 hex "Compressed ROM boot loader base address"
676 The physical address at which the ROM-able zImage is to be
677 placed in the target. Platforms which normally make use of
678 ROM-able zImage formats normally set this to a suitable
679 value in their defconfig file.
681 If ZBOOT_ROM is not enabled, this has no effect.
684 hex "Compressed ROM boot loader BSS address"
687 The base address of an area of read/write memory in the target
688 for the ROM-able zImage which must be available while the
689 decompressor is running. It must be large enough to hold the
690 entire decompressed kernel plus an additional 128 KiB.
691 Platforms which normally make use of ROM-able zImage formats
692 normally set this to a suitable value in their defconfig file.
694 If ZBOOT_ROM is not enabled, this has no effect.
697 bool "Compressed boot loader in ROM/flash"
698 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
700 Say Y here if you intend to execute your compressed kernel image
701 (zImage) directly from ROM or flash. If unsure, say N.
704 string "Default kernel command string"
707 On some architectures (EBSA110 and CATS), there is currently no way
708 for the boot loader to pass arguments to the kernel. For these
709 architectures, you should supply some command-line options at build
710 time by entering them here. As a minimum, you should specify the
711 memory size and the root device (e.g., mem=64M root=/dev/nfs).
714 bool "Kernel Execute-In-Place from ROM"
715 depends on !ZBOOT_ROM
717 Execute-In-Place allows the kernel to run from non-volatile storage
718 directly addressable by the CPU, such as NOR flash. This saves RAM
719 space since the text section of the kernel is not loaded from flash
720 to RAM. Read-write sections, such as the data section and stack,
721 are still copied to RAM. The XIP kernel is not compressed since
722 it has to run directly from flash, so it will take more space to
723 store it. The flash address used to link the kernel object files,
724 and for storing it, is configuration dependent. Therefore, if you
725 say Y here, you must know the proper physical address where to
726 store the kernel image depending on your own flash memory usage.
728 Also note that the make target becomes "make xipImage" rather than
729 "make zImage" or "make Image". The final kernel binary to put in
730 ROM memory will be arch/arm/boot/xipImage.
735 hex "XIP Kernel Physical Location"
736 depends on XIP_KERNEL
739 This is the physical address in your flash memory the kernel will
740 be linked for and stored to. This address is dependent on your
745 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
747 menu "CPU Frequency scaling"
749 source "drivers/cpufreq/Kconfig"
751 config CPU_FREQ_SA1100
753 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
756 config CPU_FREQ_SA1110
758 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
761 config CPU_FREQ_INTEGRATOR
762 tristate "CPUfreq driver for ARM Integrator CPUs"
763 depends on ARCH_INTEGRATOR && CPU_FREQ
766 This enables the CPUfreq driver for ARM Integrator CPUs.
768 For details, take a look at <file:Documentation/cpu-freq>.
773 tristate "CPUfreq driver for i.MX CPUs"
774 depends on ARCH_IMX && CPU_FREQ
777 This enables the CPUfreq driver for i.MX CPUs.
785 menu "Floating point emulation"
787 comment "At least one emulation must be selected"
790 bool "NWFPE math emulation"
791 depends on !AEABI || OABI_COMPAT
793 Say Y to include the NWFPE floating point emulator in the kernel.
794 This is necessary to run most binaries. Linux does not currently
795 support floating point hardware so you need to say Y here even if
796 your machine has an FPA or floating point co-processor podule.
798 You may say N here if you are going to load the Acorn FPEmulator
802 bool "Support extended precision"
805 Say Y to include 80-bit support in the kernel floating-point
806 emulator. Otherwise, only 32 and 64-bit support is compiled in.
807 Note that gcc does not generate 80-bit operations by default,
808 so in most cases this option only enlarges the size of the
809 floating point emulator without any good reason.
811 You almost surely want to say N here.
814 bool "FastFPE math emulation (EXPERIMENTAL)"
815 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
817 Say Y here to include the FAST floating point emulator in the kernel.
818 This is an experimental much faster emulator which now also has full
819 precision for the mantissa. It does not support any exceptions.
820 It is very simple, and approximately 3-6 times faster than NWFPE.
822 It should be sufficient for most programs. It may be not suitable
823 for scientific calculations, but you have to check this for yourself.
824 If you do not feel you need a faster FP emulation you should better
828 bool "VFP-format floating point maths"
829 depends on CPU_V6 || CPU_ARM926T
831 Say Y to include VFP support code in the kernel. This is needed
832 if your hardware includes a VFP unit.
834 Please see <file:Documentation/arm/VFP/release-notes.txt> for
835 release notes and additional status information.
837 Say N if your target does not have VFP hardware.
841 menu "Userspace binary formats"
843 source "fs/Kconfig.binfmt"
846 tristate "RISC OS personality"
849 Say Y here to include the kernel code necessary if you want to run
850 Acorn RISC OS/Arthur binaries under Linux. This code is still very
851 experimental; if this sounds frightening, say N and sleep in peace.
852 You can also say M here to compile this support as a module (which
853 will be called arthur).
857 menu "Power management options"
859 source "kernel/power/Kconfig"
862 tristate "Advanced Power Management Emulation"
864 APM is a BIOS specification for saving power using several different
865 techniques. This is mostly useful for battery powered laptops with
866 APM compliant BIOSes. If you say Y here, the system time will be
867 reset after a RESUME operation, the /proc/apm device will provide
868 battery status information, and user-space programs will receive
869 notification of APM "events" (e.g. battery status change).
871 In order to use APM, you will need supporting software. For location
872 and more information, read <file:Documentation/pm.txt> and the
873 Battery Powered Linux mini-HOWTO, available from
874 <http://www.tldp.org/docs.html#howto>.
876 This driver does not spin down disk drives (see the hdparm(8)
877 manpage ("man 8 hdparm") for that), and it doesn't turn off
878 VESA-compliant "green" monitors.
880 Generally, if you don't have a battery in your machine, there isn't
881 much point in using this driver and you should say N. If you get
882 random kernel OOPSes or reboots that don't seem to be related to
883 anything, try disabling/enabling this option (or disabling/enabling
890 menu "Device Drivers"
892 source "drivers/base/Kconfig"
894 source "drivers/connector/Kconfig"
896 if ALIGNMENT_TRAP || !CPU_CP15_MMU
897 source "drivers/mtd/Kconfig"
900 source "drivers/parport/Kconfig"
902 source "drivers/pnp/Kconfig"
904 source "drivers/block/Kconfig"
906 source "drivers/acorn/block/Kconfig"
908 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
909 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
910 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
912 source "drivers/ide/Kconfig"
915 source "drivers/scsi/Kconfig"
917 source "drivers/ata/Kconfig"
919 source "drivers/md/Kconfig"
921 source "drivers/message/fusion/Kconfig"
923 source "drivers/ieee1394/Kconfig"
925 source "drivers/message/i2o/Kconfig"
927 source "drivers/net/Kconfig"
929 source "drivers/isdn/Kconfig"
931 # input before char - char/joystick depends on it. As does USB.
933 source "drivers/input/Kconfig"
935 source "drivers/char/Kconfig"
937 source "drivers/i2c/Kconfig"
939 source "drivers/spi/Kconfig"
941 source "drivers/w1/Kconfig"
943 source "drivers/hwmon/Kconfig"
945 #source "drivers/l3/Kconfig"
947 source "drivers/misc/Kconfig"
949 source "drivers/mfd/Kconfig"
951 source "drivers/leds/Kconfig"
953 source "drivers/media/Kconfig"
955 source "drivers/video/Kconfig"
957 source "sound/Kconfig"
959 source "drivers/hid/Kconfig"
961 source "drivers/usb/Kconfig"
963 source "drivers/mmc/Kconfig"
965 source "drivers/rtc/Kconfig"
971 source "arch/arm/oprofile/Kconfig"
973 source "arch/arm/Kconfig.debug"
975 source "security/Kconfig"
977 source "crypto/Kconfig"