xref: /openbmc/linux/arch/arm/Kconfig (revision 87c2ce3b) 
1#
2# For a description of the syntax of this configuration file,
3# see Documentation/kbuild/kconfig-language.txt.
4#
5
6mainmenu "Linux Kernel Configuration"
7
8config ARM
9	bool
10	default y
11	help
12	  The ARM series is a line of low-power-consumption RISC chip designs
13	  licensed by ARM ltd and targeted at embedded applications and
14	  handhelds such as the Compaq IPAQ.  ARM-based PCs are no longer
15	  manufactured, but  legacy ARM-based PC hardware remains popular in
16	  Europe.  There is an ARM Linux project with a web page at
17	  <http://www.arm.linux.org.uk/>.
18
19config MMU
20	bool
21	default y
22
23config EISA
24	bool
25	---help---
26	  The Extended Industry Standard Architecture (EISA) bus was
27	  developed as an open alternative to the IBM MicroChannel bus.
28
29	  The EISA bus provided some of the features of the IBM MicroChannel
30	  bus while maintaining backward compatibility with cards made for
31	  the older ISA bus.  The EISA bus saw limited use between 1988 and
32	  1995 when it was made obsolete by the PCI bus.
33
34	  Say Y here if you are building a kernel for an EISA-based machine.
35
36	  Otherwise, say N.
37
38config SBUS
39	bool
40
41config MCA
42	bool
43	help
44	  MicroChannel Architecture is found in some IBM PS/2 machines and
45	  laptops.  It is a bus system similar to PCI or ISA. See
46	  <file:Documentation/mca.txt> (and especially the web page given
47	  there) before attempting to build an MCA bus kernel.
48
49config RWSEM_GENERIC_SPINLOCK
50	bool
51	default y
52
53config RWSEM_XCHGADD_ALGORITHM
54	bool
55
56config GENERIC_CALIBRATE_DELAY
57	bool
58	default y
59
60config GENERIC_BUST_SPINLOCK
61	bool
62
63config ARCH_MAY_HAVE_PC_FDC
64	bool
65
66config GENERIC_ISA_DMA
67	bool
68
69config FIQ
70	bool
71
72source "init/Kconfig"
73
74menu "System Type"
75
76choice
77	prompt "ARM system type"
78	default ARCH_RPC
79
80config ARCH_CLPS7500
81	bool "Cirrus-CL-PS7500FE"
82	select TIMER_ACORN
83	select ISA
84
85config ARCH_CLPS711X
86	bool "CLPS711x/EP721x-based"
87
88config ARCH_CO285
89	bool "Co-EBSA285"
90	select FOOTBRIDGE
91	select FOOTBRIDGE_ADDIN
92
93config ARCH_EBSA110
94	bool "EBSA-110"
95	select ISA
96	help
97	  This is an evaluation board for the StrongARM processor available
98	  from Digital. It has limited hardware on-board, including an onboard
99	  Ethernet interface, two PCMCIA sockets, two serial ports and a
100	  parallel port.
101
102config ARCH_FOOTBRIDGE
103	bool "FootBridge"
104	select FOOTBRIDGE
105
106config ARCH_INTEGRATOR
107	bool "Integrator"
108	select ARM_AMBA
109	select ICST525
110
111config ARCH_IOP3XX
112	bool "IOP3xx-based"
113	select PCI
114
115config ARCH_IXP4XX
116	bool "IXP4xx-based"
117	select DMABOUNCE
118	select PCI
119
120config ARCH_IXP2000
121	bool "IXP2400/2800-based"
122	select PCI
123
124config ARCH_L7200
125	bool "LinkUp-L7200"
126	select FIQ
127	help
128	  Say Y here if you intend to run this kernel on a LinkUp Systems
129	  L7200 Software Development Board which uses an ARM720T processor.
130	  Information on this board can be obtained at:
131
132	  <http://www.linkupsys.com/>
133
134	  If you have any questions or comments about the Linux kernel port
135	  to this board, send e-mail to <sjhill@cotw.com>.
136
137config ARCH_PXA
138	bool "PXA2xx-based"
139
140config ARCH_RPC
141	bool "RiscPC"
142	select ARCH_ACORN
143	select FIQ
144	select TIMER_ACORN
145	select ARCH_MAY_HAVE_PC_FDC
146	select ISA_DMA_API
147	help
148	  On the Acorn Risc-PC, Linux can support the internal IDE disk and
149	  CD-ROM interface, serial and parallel port, and the floppy drive.
150
151config ARCH_SA1100
152	bool "SA1100-based"
153	select ISA
154	select ARCH_DISCONTIGMEM_ENABLE
155
156config ARCH_S3C2410
157	bool "Samsung S3C2410"
158	help
159	  Samsung S3C2410X CPU based systems, such as the Simtec Electronics
160	  BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
161	  the Samsung SMDK2410 development board (and derviatives).
162
163config ARCH_SHARK
164	bool "Shark"
165	select ISA
166	select ISA_DMA
167	select PCI
168
169config ARCH_LH7A40X
170	bool "Sharp LH7A40X"
171	help
172	  Say Y here for systems based on one of the Sharp LH7A40X
173	  System on a Chip processors.  These CPUs include an ARM922T
174	  core with a wide array of integrated devices for
175	  hand-held and low-power applications.
176
177config ARCH_OMAP
178	bool "TI OMAP"
179
180config ARCH_VERSATILE
181	bool "Versatile"
182	select ARM_AMBA
183	select ICST307
184	help
185	  This enables support for ARM Ltd Versatile board.
186
187config ARCH_REALVIEW
188	bool "RealView"
189	select ARM_AMBA
190	select ICST307
191	help
192	  This enables support for ARM Ltd RealView boards.
193
194config ARCH_IMX
195	bool "IMX"
196
197config ARCH_H720X
198	bool "Hynix-HMS720x-based"
199	select ISA_DMA_API
200	help
201	  This enables support for systems based on the Hynix HMS720x
202
203config ARCH_AAEC2000
204	bool "Agilent AAEC-2000 based"
205	select ARM_AMBA
206	help
207	  This enables support for systems based on the Agilent AAEC-2000
208
209config ARCH_AT91RM9200
210	bool "AT91RM9200"
211	help
212	  Say Y here if you intend to run this kernel on an AT91RM9200-based
213	  board.
214
215endchoice
216
217source "arch/arm/mach-clps711x/Kconfig"
218
219source "arch/arm/mach-footbridge/Kconfig"
220
221source "arch/arm/mach-integrator/Kconfig"
222
223source "arch/arm/mach-iop3xx/Kconfig"
224
225source "arch/arm/mach-ixp4xx/Kconfig"
226
227source "arch/arm/mach-ixp2000/Kconfig"
228
229source "arch/arm/mach-pxa/Kconfig"
230
231source "arch/arm/mach-sa1100/Kconfig"
232
233source "arch/arm/plat-omap/Kconfig"
234
235source "arch/arm/mach-omap1/Kconfig"
236
237source "arch/arm/mach-omap2/Kconfig"
238
239source "arch/arm/mach-s3c2410/Kconfig"
240
241source "arch/arm/mach-lh7a40x/Kconfig"
242
243source "arch/arm/mach-imx/Kconfig"
244
245source "arch/arm/mach-h720x/Kconfig"
246
247source "arch/arm/mach-versatile/Kconfig"
248
249source "arch/arm/mach-aaec2000/Kconfig"
250
251source "arch/arm/mach-realview/Kconfig"
252
253source "arch/arm/mach-at91rm9200/Kconfig"
254
255# Definitions to make life easier
256config ARCH_ACORN
257	bool
258
259source arch/arm/mm/Kconfig
260
261#  bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
262config XSCALE_PMU
263	bool
264	depends on CPU_XSCALE && !XSCALE_PMU_TIMER
265	default y
266
267endmenu
268
269source "arch/arm/common/Kconfig"
270
271config FORCE_MAX_ZONEORDER
272	int
273	depends on SA1111
274	default "9"
275
276menu "Bus support"
277
278config ARM_AMBA
279	bool
280
281config ISA
282	bool
283	help
284	  Find out whether you have ISA slots on your motherboard.  ISA is the
285	  name of a bus system, i.e. the way the CPU talks to the other stuff
286	  inside your box.  Other bus systems are PCI, EISA, MicroChannel
287	  (MCA) or VESA.  ISA is an older system, now being displaced by PCI;
288	  newer boards don't support it.  If you have ISA, say Y, otherwise N.
289
290# Select ISA DMA controller support
291config ISA_DMA
292	bool
293	select ISA_DMA_API
294
295# Select ISA DMA interface
296config ISA_DMA_API
297	bool
298
299config PCI
300	bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
301	help
302	  Find out whether you have a PCI motherboard. PCI is the name of a
303	  bus system, i.e. the way the CPU talks to the other stuff inside
304	  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
305	  VESA. If you have PCI, say Y, otherwise N.
306
307	  The PCI-HOWTO, available from
308	  <http://www.tldp.org/docs.html#howto>, contains valuable
309	  information about which PCI hardware does work under Linux and which
310	  doesn't.
311
312# Select the host bridge type
313config PCI_HOST_VIA82C505
314	bool
315	depends on PCI && ARCH_SHARK
316	default y
317
318source "drivers/pci/Kconfig"
319
320source "drivers/pcmcia/Kconfig"
321
322endmenu
323
324menu "Kernel Features"
325
326config SMP
327	bool "Symmetric Multi-Processing (EXPERIMENTAL)"
328	depends on EXPERIMENTAL && REALVIEW_MPCORE
329	help
330	  This enables support for systems with more than one CPU. If you have
331	  a system with only one CPU, like most personal computers, say N. If
332	  you have a system with more than one CPU, say Y.
333
334	  If you say N here, the kernel will run on single and multiprocessor
335	  machines, but will use only one CPU of a multiprocessor machine. If
336	  you say Y here, the kernel will run on many, but not all, single
337	  processor machines. On a single processor machine, the kernel will
338	  run faster if you say N here.
339
340	  See also the <file:Documentation/smp.txt>,
341	  <file:Documentation/i386/IO-APIC.txt>,
342	  <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
343	  <http://www.linuxdoc.org/docs.html#howto>.
344
345	  If you don't know what to do here, say N.
346
347config NR_CPUS
348	int "Maximum number of CPUs (2-32)"
349	range 2 32
350	depends on SMP
351	default "4"
352
353config HOTPLUG_CPU
354	bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
355	depends on SMP && HOTPLUG && EXPERIMENTAL
356	help
357	  Say Y here to experiment with turning CPUs off and on.  CPUs
358	  can be controlled through /sys/devices/system/cpu.
359
360config LOCAL_TIMERS
361	bool "Use local timer interrupts"
362	depends on SMP && REALVIEW_MPCORE
363	default y
364	help
365	  Enable support for local timers on SMP platforms, rather then the
366	  legacy IPI broadcast method.  Local timers allows the system
367	  accounting to be spread across the timer interval, preventing a
368	  "thundering herd" at every timer tick.
369
370config PREEMPT
371	bool "Preemptible Kernel (EXPERIMENTAL)"
372	depends on EXPERIMENTAL
373	help
374	  This option reduces the latency of the kernel when reacting to
375	  real-time or interactive events by allowing a low priority process to
376	  be preempted even if it is in kernel mode executing a system call.
377	  This allows applications to run more reliably even when the system is
378	  under load.
379
380	  Say Y here if you are building a kernel for a desktop, embedded
381	  or real-time system.  Say N if you are unsure.
382
383config NO_IDLE_HZ
384	bool "Dynamic tick timer"
385	help
386	  Select this option if you want to disable continuous timer ticks
387	  and have them programmed to occur as required. This option saves
388	  power as the system can remain in idle state for longer.
389
390	  By default dynamic tick is disabled during the boot, and can be
391	  manually enabled with:
392
393	    echo 1 > /sys/devices/system/timer/timer0/dyn_tick
394
395	  Alternatively, if you want dynamic tick automatically enabled
396	  during boot, pass "dyntick=enable" via the kernel command string.
397
398	  Please note that dynamic tick may affect the accuracy of
399	  timekeeping on some platforms depending on the implementation.
400	  Currently at least OMAP, PXA2xx and SA11x0 platforms are known
401	  to have accurate timekeeping with dynamic tick.
402
403config ARCH_DISCONTIGMEM_ENABLE
404	bool
405	default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
406	help
407	  Say Y to support efficient handling of discontiguous physical memory,
408	  for architectures which are either NUMA (Non-Uniform Memory Access)
409	  or have huge holes in the physical address space for other reasons.
410	  See <file:Documentation/vm/numa> for more.
411
412source "mm/Kconfig"
413
414config LEDS
415	bool "Timer and CPU usage LEDs"
416	depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
417		   ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
418		   ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
419		   ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
420		   ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
421		   ARCH_AT91RM9200
422	help
423	  If you say Y here, the LEDs on your machine will be used
424	  to provide useful information about your current system status.
425
426	  If you are compiling a kernel for a NetWinder or EBSA-285, you will
427	  be able to select which LEDs are active using the options below. If
428	  you are compiling a kernel for the EBSA-110 or the LART however, the
429	  red LED will simply flash regularly to indicate that the system is
430	  still functional. It is safe to say Y here if you have a CATS
431	  system, but the driver will do nothing.
432
433config LEDS_TIMER
434	bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
435			    MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
436	depends on LEDS
437	default y if ARCH_EBSA110
438	help
439	  If you say Y here, one of the system LEDs (the green one on the
440	  NetWinder, the amber one on the EBSA285, or the red one on the LART)
441	  will flash regularly to indicate that the system is still
442	  operational. This is mainly useful to kernel hackers who are
443	  debugging unstable kernels.
444
445	  The LART uses the same LED for both Timer LED and CPU usage LED
446	  functions. You may choose to use both, but the Timer LED function
447	  will overrule the CPU usage LED.
448
449config LEDS_CPU
450	bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
451			!ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
452	depends on LEDS
453	help
454	  If you say Y here, the red LED will be used to give a good real
455	  time indication of CPU usage, by lighting whenever the idle task
456	  is not currently executing.
457
458	  The LART uses the same LED for both Timer LED and CPU usage LED
459	  functions. You may choose to use both, but the Timer LED function
460	  will overrule the CPU usage LED.
461
462config ALIGNMENT_TRAP
463	bool
464	default y if !ARCH_EBSA110
465	help
466	  ARM processors can not fetch/store information which is not
467	  naturally aligned on the bus, i.e., a 4 byte fetch must start at an
468	  address divisible by 4. On 32-bit ARM processors, these non-aligned
469	  fetch/store instructions will be emulated in software if you say
470	  here, which has a severe performance impact. This is necessary for
471	  correct operation of some network protocols. With an IP-only
472	  configuration it is safe to say N, otherwise say Y.
473
474endmenu
475
476menu "Boot options"
477
478# Compressed boot loader in ROM.  Yes, we really want to ask about
479# TEXT and BSS so we preserve their values in the config files.
480config ZBOOT_ROM_TEXT
481	hex "Compressed ROM boot loader base address"
482	default "0"
483	help
484	  The physical address at which the ROM-able zImage is to be
485	  placed in the target.  Platforms which normally make use of
486	  ROM-able zImage formats normally set this to a suitable
487	  value in their defconfig file.
488
489	  If ZBOOT_ROM is not enabled, this has no effect.
490
491config ZBOOT_ROM_BSS
492	hex "Compressed ROM boot loader BSS address"
493	default "0"
494	help
495	  The base address of 64KiB of read/write memory in the target
496	  for the ROM-able zImage, which must be available while the
497	  decompressor is running.  Platforms which normally make use of
498	  ROM-able zImage formats normally set this to a suitable
499	  value in their defconfig file.
500
501	  If ZBOOT_ROM is not enabled, this has no effect.
502
503config ZBOOT_ROM
504	bool "Compressed boot loader in ROM/flash"
505	depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
506	help
507	  Say Y here if you intend to execute your compressed kernel image
508	  (zImage) directly from ROM or flash.  If unsure, say N.
509
510config CMDLINE
511	string "Default kernel command string"
512	default ""
513	help
514	  On some architectures (EBSA110 and CATS), there is currently no way
515	  for the boot loader to pass arguments to the kernel. For these
516	  architectures, you should supply some command-line options at build
517	  time by entering them here. As a minimum, you should specify the
518	  memory size and the root device (e.g., mem=64M root=/dev/nfs).
519
520config XIP_KERNEL
521	bool "Kernel Execute-In-Place from ROM"
522	depends on !ZBOOT_ROM
523	help
524	  Execute-In-Place allows the kernel to run from non-volatile storage
525	  directly addressable by the CPU, such as NOR flash. This saves RAM
526	  space since the text section of the kernel is not loaded from flash
527	  to RAM.  Read-write sections, such as the data section and stack,
528	  are still copied to RAM.  The XIP kernel is not compressed since
529	  it has to run directly from flash, so it will take more space to
530	  store it.  The flash address used to link the kernel object files,
531	  and for storing it, is configuration dependent. Therefore, if you
532	  say Y here, you must know the proper physical address where to
533	  store the kernel image depending on your own flash memory usage.
534
535	  Also note that the make target becomes "make xipImage" rather than
536	  "make zImage" or "make Image".  The final kernel binary to put in
537	  ROM memory will be arch/arm/boot/xipImage.
538
539	  If unsure, say N.
540
541config XIP_PHYS_ADDR
542	hex "XIP Kernel Physical Location"
543	depends on XIP_KERNEL
544	default "0x00080000"
545	help
546	  This is the physical address in your flash memory the kernel will
547	  be linked for and stored to.  This address is dependent on your
548	  own flash usage.
549
550endmenu
551
552if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
553
554menu "CPU Frequency scaling"
555
556source "drivers/cpufreq/Kconfig"
557
558config CPU_FREQ_SA1100
559	bool
560	depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
561	default y
562
563config CPU_FREQ_SA1110
564	bool
565	depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
566	default y
567
568config CPU_FREQ_INTEGRATOR
569	tristate "CPUfreq driver for ARM Integrator CPUs"
570	depends on ARCH_INTEGRATOR && CPU_FREQ
571	default y
572	help
573	  This enables the CPUfreq driver for ARM Integrator CPUs.
574
575	  For details, take a look at <file:Documentation/cpu-freq>.
576
577	  If in doubt, say Y.
578
579endmenu
580
581endif
582
583menu "Floating point emulation"
584
585comment "At least one emulation must be selected"
586
587config FPE_NWFPE
588	bool "NWFPE math emulation"
589	---help---
590	  Say Y to include the NWFPE floating point emulator in the kernel.
591	  This is necessary to run most binaries. Linux does not currently
592	  support floating point hardware so you need to say Y here even if
593	  your machine has an FPA or floating point co-processor podule.
594
595	  You may say N here if you are going to load the Acorn FPEmulator
596	  early in the bootup.
597
598config FPE_NWFPE_XP
599	bool "Support extended precision"
600	depends on FPE_NWFPE
601	help
602	  Say Y to include 80-bit support in the kernel floating-point
603	  emulator.  Otherwise, only 32 and 64-bit support is compiled in.
604	  Note that gcc does not generate 80-bit operations by default,
605	  so in most cases this option only enlarges the size of the
606	  floating point emulator without any good reason.
607
608	  You almost surely want to say N here.
609
610config FPE_FASTFPE
611	bool "FastFPE math emulation (EXPERIMENTAL)"
612	depends on !CPU_32v3 && EXPERIMENTAL
613	---help---
614	  Say Y here to include the FAST floating point emulator in the kernel.
615	  This is an experimental much faster emulator which now also has full
616	  precision for the mantissa.  It does not support any exceptions.
617	  It is very simple, and approximately 3-6 times faster than NWFPE.
618
619	  It should be sufficient for most programs.  It may be not suitable
620	  for scientific calculations, but you have to check this for yourself.
621	  If you do not feel you need a faster FP emulation you should better
622	  choose NWFPE.
623
624config VFP
625	bool "VFP-format floating point maths"
626	depends on CPU_V6 || CPU_ARM926T
627	help
628	  Say Y to include VFP support code in the kernel. This is needed
629	  if your hardware includes a VFP unit.
630
631	  Please see <file:Documentation/arm/VFP/release-notes.txt> for
632	  release notes and additional status information.
633
634	  Say N if your target does not have VFP hardware.
635
636endmenu
637
638menu "Userspace binary formats"
639
640source "fs/Kconfig.binfmt"
641
642config ARTHUR
643	tristate "RISC OS personality"
644	help
645	  Say Y here to include the kernel code necessary if you want to run
646	  Acorn RISC OS/Arthur binaries under Linux. This code is still very
647	  experimental; if this sounds frightening, say N and sleep in peace.
648	  You can also say M here to compile this support as a module (which
649	  will be called arthur).
650
651endmenu
652
653menu "Power management options"
654
655source "kernel/power/Kconfig"
656
657config APM
658	tristate "Advanced Power Management Emulation"
659	---help---
660	  APM is a BIOS specification for saving power using several different
661	  techniques. This is mostly useful for battery powered laptops with
662	  APM compliant BIOSes. If you say Y here, the system time will be
663	  reset after a RESUME operation, the /proc/apm device will provide
664	  battery status information, and user-space programs will receive
665	  notification of APM "events" (e.g. battery status change).
666
667	  In order to use APM, you will need supporting software. For location
668	  and more information, read <file:Documentation/pm.txt> and the
669	  Battery Powered Linux mini-HOWTO, available from
670	  <http://www.tldp.org/docs.html#howto>.
671
672	  This driver does not spin down disk drives (see the hdparm(8)
673	  manpage ("man 8 hdparm") for that), and it doesn't turn off
674	  VESA-compliant "green" monitors.
675
676	  Generally, if you don't have a battery in your machine, there isn't
677	  much point in using this driver and you should say N. If you get
678	  random kernel OOPSes or reboots that don't seem to be related to
679	  anything, try disabling/enabling this option (or disabling/enabling
680	  APM in your BIOS).
681
682endmenu
683
684source "net/Kconfig"
685
686menu "Device Drivers"
687
688source "drivers/base/Kconfig"
689
690source "drivers/connector/Kconfig"
691
692if ALIGNMENT_TRAP
693source "drivers/mtd/Kconfig"
694endif
695
696source "drivers/parport/Kconfig"
697
698source "drivers/pnp/Kconfig"
699
700source "drivers/block/Kconfig"
701
702source "drivers/acorn/block/Kconfig"
703
704if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
705	|| ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
706	|| ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
707source "drivers/ide/Kconfig"
708endif
709
710source "drivers/scsi/Kconfig"
711
712source "drivers/md/Kconfig"
713
714source "drivers/message/fusion/Kconfig"
715
716source "drivers/ieee1394/Kconfig"
717
718source "drivers/message/i2o/Kconfig"
719
720source "drivers/net/Kconfig"
721
722source "drivers/isdn/Kconfig"
723
724# input before char - char/joystick depends on it. As does USB.
725
726source "drivers/input/Kconfig"
727
728source "drivers/char/Kconfig"
729
730source "drivers/i2c/Kconfig"
731
732source "drivers/hwmon/Kconfig"
733
734#source "drivers/l3/Kconfig"
735
736source "drivers/misc/Kconfig"
737
738source "drivers/mfd/Kconfig"
739
740source "drivers/media/Kconfig"
741
742source "drivers/video/Kconfig"
743
744source "sound/Kconfig"
745
746source "drivers/usb/Kconfig"
747
748source "drivers/mmc/Kconfig"
749
750endmenu
751
752source "fs/Kconfig"
753
754source "arch/arm/oprofile/Kconfig"
755
756source "arch/arm/Kconfig.debug"
757
758source "security/Kconfig"
759
760source "crypto/Kconfig"
761
762source "lib/Kconfig"
763