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.
284 Support for Intel's PXA2XX processor line.
291 select ARCH_MAY_HAVE_PC_FDC
294 On the Acorn Risc-PC, Linux can support the internal IDE disk and
295 CD-ROM interface, serial and parallel port, and the floppy drive.
300 select ARCH_DISCONTIGMEM_ENABLE
303 Support for StrongARM 11x0 based boards.
306 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442"
308 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
309 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
310 the Samsung SMDK2410 development board (and derivatives).
318 Support for the StrongARM based Digital DNARD machine, also known
319 as "Shark" (<http://www.shark-linux.de/shark.html>).
324 Say Y here for systems based on one of the Sharp LH7A40X
325 System on a Chip processors. These CPUs include an ARM922T
326 core with a wide array of integrated devices for
327 hand-held and low-power applications.
332 Support for TI's OMAP platform (OMAP1 and OMAP2).
336 source "arch/arm/mach-clps711x/Kconfig"
338 source "arch/arm/mach-ep93xx/Kconfig"
340 source "arch/arm/mach-footbridge/Kconfig"
342 source "arch/arm/mach-integrator/Kconfig"
344 source "arch/arm/mach-iop32x/Kconfig"
346 source "arch/arm/mach-iop33x/Kconfig"
348 source "arch/arm/mach-iop13xx/Kconfig"
350 source "arch/arm/mach-ixp4xx/Kconfig"
352 source "arch/arm/mach-ixp2000/Kconfig"
354 source "arch/arm/mach-ixp23xx/Kconfig"
356 source "arch/arm/mach-pxa/Kconfig"
358 source "arch/arm/mach-sa1100/Kconfig"
360 source "arch/arm/plat-omap/Kconfig"
362 source "arch/arm/mach-omap1/Kconfig"
364 source "arch/arm/mach-omap2/Kconfig"
366 source "arch/arm/mach-s3c2410/Kconfig"
368 source "arch/arm/mach-lh7a40x/Kconfig"
370 source "arch/arm/mach-imx/Kconfig"
372 source "arch/arm/mach-h720x/Kconfig"
374 source "arch/arm/mach-versatile/Kconfig"
376 source "arch/arm/mach-aaec2000/Kconfig"
378 source "arch/arm/mach-realview/Kconfig"
380 source "arch/arm/mach-at91rm9200/Kconfig"
382 source "arch/arm/mach-netx/Kconfig"
384 # Definitions to make life easier
391 source arch/arm/mm/Kconfig
394 bool "Enable iWMMXt support"
395 depends CPU_XSCALE || CPU_XSC3
398 Enable support for iWMMXt context switching at run time if
399 running on a CPU that supports it.
401 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
404 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
408 source "arch/arm/Kconfig-nommu"
413 source "arch/arm/common/Kconfig"
415 config FORCE_MAX_ZONEORDER
428 Find out whether you have ISA slots on your motherboard. ISA is the
429 name of a bus system, i.e. the way the CPU talks to the other stuff
430 inside your box. Other bus systems are PCI, EISA, MicroChannel
431 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
432 newer boards don't support it. If you have ISA, say Y, otherwise N.
434 # Select ISA DMA controller support
439 # Select ISA DMA interface
444 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
446 Find out whether you have a PCI motherboard. PCI is the name of a
447 bus system, i.e. the way the CPU talks to the other stuff inside
448 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
449 VESA. If you have PCI, say Y, otherwise N.
451 The PCI-HOWTO, available from
452 <http://www.tldp.org/docs.html#howto>, contains valuable
453 information about which PCI hardware does work under Linux and which
456 # Select the host bridge type
457 config PCI_HOST_VIA82C505
459 depends on PCI && ARCH_SHARK
462 source "drivers/pci/Kconfig"
464 source "drivers/pcmcia/Kconfig"
468 menu "Kernel Features"
471 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
472 depends on EXPERIMENTAL && REALVIEW_MPCORE
474 This enables support for systems with more than one CPU. If you have
475 a system with only one CPU, like most personal computers, say N. If
476 you have a system with more than one CPU, say Y.
478 If you say N here, the kernel will run on single and multiprocessor
479 machines, but will use only one CPU of a multiprocessor machine. If
480 you say Y here, the kernel will run on many, but not all, single
481 processor machines. On a single processor machine, the kernel will
482 run faster if you say N here.
484 See also the <file:Documentation/smp.txt>,
485 <file:Documentation/i386/IO-APIC.txt>,
486 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
487 <http://www.linuxdoc.org/docs.html#howto>.
489 If you don't know what to do here, say N.
492 int "Maximum number of CPUs (2-32)"
498 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
499 depends on SMP && HOTPLUG && EXPERIMENTAL
501 Say Y here to experiment with turning CPUs off and on. CPUs
502 can be controlled through /sys/devices/system/cpu.
505 bool "Use local timer interrupts"
506 depends on SMP && REALVIEW_MPCORE
509 Enable support for local timers on SMP platforms, rather then the
510 legacy IPI broadcast method. Local timers allows the system
511 accounting to be spread across the timer interval, preventing a
512 "thundering herd" at every timer tick.
515 bool "Preemptible Kernel (EXPERIMENTAL)"
516 depends on EXPERIMENTAL
518 This option reduces the latency of the kernel when reacting to
519 real-time or interactive events by allowing a low priority process to
520 be preempted even if it is in kernel mode executing a system call.
521 This allows applications to run more reliably even when the system is
524 Say Y here if you are building a kernel for a desktop, embedded
525 or real-time system. Say N if you are unsure.
528 bool "Dynamic tick timer"
530 Select this option if you want to disable continuous timer ticks
531 and have them programmed to occur as required. This option saves
532 power as the system can remain in idle state for longer.
534 By default dynamic tick is disabled during the boot, and can be
535 manually enabled with:
537 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
539 Alternatively, if you want dynamic tick automatically enabled
540 during boot, pass "dyntick=enable" via the kernel command string.
542 Please note that dynamic tick may affect the accuracy of
543 timekeeping on some platforms depending on the implementation.
544 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
545 to have accurate timekeeping with dynamic tick.
549 default 128 if ARCH_L7200
550 default 200 if ARCH_EBSA110 || ARCH_S3C2410
551 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
555 bool "Use the ARM EABI to compile the kernel"
557 This option allows for the kernel to be compiled using the latest
558 ARM ABI (aka EABI). This is only useful if you are using a user
559 space environment that is also compiled with EABI.
561 Since there are major incompatibilities between the legacy ABI and
562 EABI, especially with regard to structure member alignment, this
563 option also changes the kernel syscall calling convention to
564 disambiguate both ABIs and allow for backward compatibility support
565 (selected with CONFIG_OABI_COMPAT).
567 To use this you need GCC version 4.0.0 or later.
570 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
571 depends on AEABI && EXPERIMENTAL
574 This option preserves the old syscall interface along with the
575 new (ARM EABI) one. It also provides a compatibility layer to
576 intercept syscalls that have structure arguments which layout
577 in memory differs between the legacy ABI and the new ARM EABI
578 (only for non "thumb" binaries). This option adds a tiny
579 overhead to all syscalls and produces a slightly larger kernel.
580 If you know you'll be using only pure EABI user space then you
581 can say N here. If this option is not selected and you attempt
582 to execute a legacy ABI binary then the result will be
583 UNPREDICTABLE (in fact it can be predicted that it won't work
584 at all). If in doubt say Y.
586 config ARCH_DISCONTIGMEM_ENABLE
588 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
590 Say Y to support efficient handling of discontiguous physical memory,
591 for architectures which are either NUMA (Non-Uniform Memory Access)
592 or have huge holes in the physical address space for other reasons.
593 See <file:Documentation/vm/numa> for more.
597 default "4" if ARCH_LH7A40X
599 depends on NEED_MULTIPLE_NODES
604 bool "Timer and CPU usage LEDs"
605 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
606 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
607 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
608 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
609 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
610 ARCH_AT91 || MACH_TRIZEPS4
612 If you say Y here, the LEDs on your machine will be used
613 to provide useful information about your current system status.
615 If you are compiling a kernel for a NetWinder or EBSA-285, you will
616 be able to select which LEDs are active using the options below. If
617 you are compiling a kernel for the EBSA-110 or the LART however, the
618 red LED will simply flash regularly to indicate that the system is
619 still functional. It is safe to say Y here if you have a CATS
620 system, but the driver will do nothing.
623 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
624 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
626 default y if ARCH_EBSA110
628 If you say Y here, one of the system LEDs (the green one on the
629 NetWinder, the amber one on the EBSA285, or the red one on the LART)
630 will flash regularly to indicate that the system is still
631 operational. This is mainly useful to kernel hackers who are
632 debugging unstable kernels.
634 The LART uses the same LED for both Timer LED and CPU usage LED
635 functions. You may choose to use both, but the Timer LED function
636 will overrule the CPU usage LED.
639 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
640 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
643 If you say Y here, the red LED will be used to give a good real
644 time indication of CPU usage, by lighting whenever the idle task
645 is not currently executing.
647 The LART uses the same LED for both Timer LED and CPU usage LED
648 functions. You may choose to use both, but the Timer LED function
649 will overrule the CPU usage LED.
651 config ALIGNMENT_TRAP
653 depends on CPU_CP15_MMU
654 default y if !ARCH_EBSA110
656 ARM processors cannot fetch/store information which is not
657 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
658 address divisible by 4. On 32-bit ARM processors, these non-aligned
659 fetch/store instructions will be emulated in software if you say
660 here, which has a severe performance impact. This is necessary for
661 correct operation of some network protocols. With an IP-only
662 configuration it is safe to say N, otherwise say Y.
668 # Compressed boot loader in ROM. Yes, we really want to ask about
669 # TEXT and BSS so we preserve their values in the config files.
670 config ZBOOT_ROM_TEXT
671 hex "Compressed ROM boot loader base address"
674 The physical address at which the ROM-able zImage is to be
675 placed in the target. Platforms which normally make use of
676 ROM-able zImage formats normally set this to a suitable
677 value in their defconfig file.
679 If ZBOOT_ROM is not enabled, this has no effect.
682 hex "Compressed ROM boot loader BSS address"
685 The base address of an area of read/write memory in the target
686 for the ROM-able zImage which must be available while the
687 decompressor is running. It must be large enough to hold the
688 entire decompressed kernel plus an additional 128 KiB.
689 Platforms which normally make use of ROM-able zImage formats
690 normally set this to a suitable value in their defconfig file.
692 If ZBOOT_ROM is not enabled, this has no effect.
695 bool "Compressed boot loader in ROM/flash"
696 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
698 Say Y here if you intend to execute your compressed kernel image
699 (zImage) directly from ROM or flash. If unsure, say N.
702 string "Default kernel command string"
705 On some architectures (EBSA110 and CATS), there is currently no way
706 for the boot loader to pass arguments to the kernel. For these
707 architectures, you should supply some command-line options at build
708 time by entering them here. As a minimum, you should specify the
709 memory size and the root device (e.g., mem=64M root=/dev/nfs).
712 bool "Kernel Execute-In-Place from ROM"
713 depends on !ZBOOT_ROM
715 Execute-In-Place allows the kernel to run from non-volatile storage
716 directly addressable by the CPU, such as NOR flash. This saves RAM
717 space since the text section of the kernel is not loaded from flash
718 to RAM. Read-write sections, such as the data section and stack,
719 are still copied to RAM. The XIP kernel is not compressed since
720 it has to run directly from flash, so it will take more space to
721 store it. The flash address used to link the kernel object files,
722 and for storing it, is configuration dependent. Therefore, if you
723 say Y here, you must know the proper physical address where to
724 store the kernel image depending on your own flash memory usage.
726 Also note that the make target becomes "make xipImage" rather than
727 "make zImage" or "make Image". The final kernel binary to put in
728 ROM memory will be arch/arm/boot/xipImage.
733 hex "XIP Kernel Physical Location"
734 depends on XIP_KERNEL
737 This is the physical address in your flash memory the kernel will
738 be linked for and stored to. This address is dependent on your
743 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
745 menu "CPU Frequency scaling"
747 source "drivers/cpufreq/Kconfig"
749 config CPU_FREQ_SA1100
751 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
754 config CPU_FREQ_SA1110
756 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
759 config CPU_FREQ_INTEGRATOR
760 tristate "CPUfreq driver for ARM Integrator CPUs"
761 depends on ARCH_INTEGRATOR && CPU_FREQ
764 This enables the CPUfreq driver for ARM Integrator CPUs.
766 For details, take a look at <file:Documentation/cpu-freq>.
771 tristate "CPUfreq driver for i.MX CPUs"
772 depends on ARCH_IMX && CPU_FREQ
775 This enables the CPUfreq driver for i.MX CPUs.
783 menu "Floating point emulation"
785 comment "At least one emulation must be selected"
788 bool "NWFPE math emulation"
789 depends on !AEABI || OABI_COMPAT
791 Say Y to include the NWFPE floating point emulator in the kernel.
792 This is necessary to run most binaries. Linux does not currently
793 support floating point hardware so you need to say Y here even if
794 your machine has an FPA or floating point co-processor podule.
796 You may say N here if you are going to load the Acorn FPEmulator
800 bool "Support extended precision"
803 Say Y to include 80-bit support in the kernel floating-point
804 emulator. Otherwise, only 32 and 64-bit support is compiled in.
805 Note that gcc does not generate 80-bit operations by default,
806 so in most cases this option only enlarges the size of the
807 floating point emulator without any good reason.
809 You almost surely want to say N here.
812 bool "FastFPE math emulation (EXPERIMENTAL)"
813 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
815 Say Y here to include the FAST floating point emulator in the kernel.
816 This is an experimental much faster emulator which now also has full
817 precision for the mantissa. It does not support any exceptions.
818 It is very simple, and approximately 3-6 times faster than NWFPE.
820 It should be sufficient for most programs. It may be not suitable
821 for scientific calculations, but you have to check this for yourself.
822 If you do not feel you need a faster FP emulation you should better
826 bool "VFP-format floating point maths"
827 depends on CPU_V6 || CPU_ARM926T
829 Say Y to include VFP support code in the kernel. This is needed
830 if your hardware includes a VFP unit.
832 Please see <file:Documentation/arm/VFP/release-notes.txt> for
833 release notes and additional status information.
835 Say N if your target does not have VFP hardware.
839 menu "Userspace binary formats"
841 source "fs/Kconfig.binfmt"
844 tristate "RISC OS personality"
847 Say Y here to include the kernel code necessary if you want to run
848 Acorn RISC OS/Arthur binaries under Linux. This code is still very
849 experimental; if this sounds frightening, say N and sleep in peace.
850 You can also say M here to compile this support as a module (which
851 will be called arthur).
855 menu "Power management options"
857 source "kernel/power/Kconfig"
860 tristate "Advanced Power Management Emulation"
862 APM is a BIOS specification for saving power using several different
863 techniques. This is mostly useful for battery powered laptops with
864 APM compliant BIOSes. If you say Y here, the system time will be
865 reset after a RESUME operation, the /proc/apm device will provide
866 battery status information, and user-space programs will receive
867 notification of APM "events" (e.g. battery status change).
869 In order to use APM, you will need supporting software. For location
870 and more information, read <file:Documentation/pm.txt> and the
871 Battery Powered Linux mini-HOWTO, available from
872 <http://www.tldp.org/docs.html#howto>.
874 This driver does not spin down disk drives (see the hdparm(8)
875 manpage ("man 8 hdparm") for that), and it doesn't turn off
876 VESA-compliant "green" monitors.
878 Generally, if you don't have a battery in your machine, there isn't
879 much point in using this driver and you should say N. If you get
880 random kernel OOPSes or reboots that don't seem to be related to
881 anything, try disabling/enabling this option (or disabling/enabling
888 menu "Device Drivers"
890 source "drivers/base/Kconfig"
892 source "drivers/connector/Kconfig"
894 if ALIGNMENT_TRAP || !CPU_CP15_MMU
895 source "drivers/mtd/Kconfig"
898 source "drivers/parport/Kconfig"
900 source "drivers/pnp/Kconfig"
902 source "drivers/block/Kconfig"
904 source "drivers/acorn/block/Kconfig"
906 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
907 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
908 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
910 source "drivers/ide/Kconfig"
913 source "drivers/scsi/Kconfig"
915 source "drivers/ata/Kconfig"
917 source "drivers/md/Kconfig"
919 source "drivers/message/fusion/Kconfig"
921 source "drivers/ieee1394/Kconfig"
923 source "drivers/message/i2o/Kconfig"
925 source "drivers/net/Kconfig"
927 source "drivers/isdn/Kconfig"
929 # input before char - char/joystick depends on it. As does USB.
931 source "drivers/input/Kconfig"
933 source "drivers/char/Kconfig"
935 source "drivers/i2c/Kconfig"
937 source "drivers/spi/Kconfig"
939 source "drivers/w1/Kconfig"
941 source "drivers/hwmon/Kconfig"
943 #source "drivers/l3/Kconfig"
945 source "drivers/misc/Kconfig"
947 source "drivers/mfd/Kconfig"
949 source "drivers/leds/Kconfig"
951 source "drivers/media/Kconfig"
953 source "drivers/video/Kconfig"
955 source "sound/Kconfig"
957 source "drivers/hid/Kconfig"
959 source "drivers/usb/Kconfig"
961 source "drivers/mmc/Kconfig"
963 source "drivers/rtc/Kconfig"
969 source "arch/arm/oprofile/Kconfig"
971 source "arch/arm/Kconfig.debug"
973 source "security/Kconfig"
975 source "crypto/Kconfig"