xref: /linux/arch/arm/Kconfig (revision 9ce7677cfd7cd871adb457c80bea3b581b839641)
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 UID16
50	bool
51	default y
52
53config RWSEM_GENERIC_SPINLOCK
54	bool
55	default y
56
57config RWSEM_XCHGADD_ALGORITHM
58	bool
59
60config GENERIC_CALIBRATE_DELAY
61	bool
62	default y
63
64config GENERIC_BUST_SPINLOCK
65	bool
66
67config ARCH_MAY_HAVE_PC_FDC
68	bool
69
70config GENERIC_ISA_DMA
71	bool
72
73config FIQ
74	bool
75
76source "init/Kconfig"
77
78menu "System Type"
79
80choice
81	prompt "ARM system type"
82	default ARCH_RPC
83
84config ARCH_CLPS7500
85	bool "Cirrus-CL-PS7500FE"
86	select TIMER_ACORN
87	select ISA
88
89config ARCH_CLPS711X
90	bool "CLPS711x/EP721x-based"
91
92config ARCH_CO285
93	bool "Co-EBSA285"
94	select FOOTBRIDGE
95	select FOOTBRIDGE_ADDIN
96
97config ARCH_EBSA110
98	bool "EBSA-110"
99	select ISA
100	help
101	  This is an evaluation board for the StrongARM processor available
102	  from Digital. It has limited hardware on-board, including an onboard
103	  Ethernet interface, two PCMCIA sockets, two serial ports and a
104	  parallel port.
105
106config ARCH_CAMELOT
107	bool "Epxa10db"
108	help
109	  This enables support for Altera's Excalibur XA10 development board.
110	  If you would like to build your kernel to run on one of these boards
111	  then you must say 'Y' here. Otherwise say 'N'
112
113config ARCH_FOOTBRIDGE
114	bool "FootBridge"
115	select FOOTBRIDGE
116
117config ARCH_INTEGRATOR
118	bool "Integrator"
119	select ARM_AMBA
120	select ICST525
121
122config ARCH_IOP3XX
123	bool "IOP3xx-based"
124	select PCI
125
126config ARCH_IXP4XX
127	bool "IXP4xx-based"
128	select DMABOUNCE
129	select PCI
130
131config ARCH_IXP2000
132	bool "IXP2400/2800-based"
133	select PCI
134
135config ARCH_L7200
136	bool "LinkUp-L7200"
137	select FIQ
138	help
139	  Say Y here if you intend to run this kernel on a LinkUp Systems
140	  L7200 Software Development Board which uses an ARM720T processor.
141	  Information on this board can be obtained at:
142
143	  <http://www.linkupsys.com/>
144
145	  If you have any questions or comments about the Linux kernel port
146	  to this board, send e-mail to <sjhill@cotw.com>.
147
148config ARCH_PXA
149	bool "PXA2xx-based"
150
151config ARCH_RPC
152	bool "RiscPC"
153	select ARCH_ACORN
154	select FIQ
155	select TIMER_ACORN
156	select ARCH_MAY_HAVE_PC_FDC
157	help
158	  On the Acorn Risc-PC, Linux can support the internal IDE disk and
159	  CD-ROM interface, serial and parallel port, and the floppy drive.
160
161config ARCH_SA1100
162	bool "SA1100-based"
163	select ISA
164	select ARCH_DISCONTIGMEM_ENABLE
165
166config ARCH_S3C2410
167	bool "Samsung S3C2410"
168	help
169	  Samsung S3C2410X CPU based systems, such as the Simtec Electronics
170	  BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
171	  the Samsung SMDK2410 development board (and derviatives).
172
173config ARCH_SHARK
174	bool "Shark"
175	select ISA
176	select ISA_DMA
177	select PCI
178
179config ARCH_LH7A40X
180	bool "Sharp LH7A40X"
181	help
182	  Say Y here for systems based on one of the Sharp LH7A40X
183	  System on a Chip processors.  These CPUs include an ARM922T
184	  core with a wide array of integrated devices for
185	  hand-held and low-power applications.
186
187config ARCH_OMAP
188	bool "TI OMAP"
189
190config ARCH_VERSATILE
191	bool "Versatile"
192	select ARM_AMBA
193	select ICST307
194	help
195	  This enables support for ARM Ltd Versatile board.
196
197config ARCH_REALVIEW
198	bool "RealView"
199	select ARM_AMBA
200	select ICST307
201	help
202	  This enables support for ARM Ltd RealView boards.
203
204config ARCH_IMX
205	bool "IMX"
206
207config ARCH_H720X
208	bool "Hynix-HMS720x-based"
209	help
210	  This enables support for systems based on the Hynix HMS720x
211
212config ARCH_AAEC2000
213	bool "Agilent AAEC-2000 based"
214	select ARM_AMBA
215	help
216	  This enables support for systems based on the Agilent AAEC-2000
217
218endchoice
219
220source "arch/arm/mach-clps711x/Kconfig"
221
222source "arch/arm/mach-epxa10db/Kconfig"
223
224source "arch/arm/mach-footbridge/Kconfig"
225
226source "arch/arm/mach-integrator/Kconfig"
227
228source "arch/arm/mach-iop3xx/Kconfig"
229
230source "arch/arm/mach-ixp4xx/Kconfig"
231
232source "arch/arm/mach-ixp2000/Kconfig"
233
234source "arch/arm/mach-pxa/Kconfig"
235
236source "arch/arm/mach-sa1100/Kconfig"
237
238source "arch/arm/plat-omap/Kconfig"
239
240source "arch/arm/mach-omap1/Kconfig"
241
242source "arch/arm/mach-omap2/Kconfig"
243
244source "arch/arm/mach-s3c2410/Kconfig"
245
246source "arch/arm/mach-lh7a40x/Kconfig"
247
248source "arch/arm/mach-imx/Kconfig"
249
250source "arch/arm/mach-h720x/Kconfig"
251
252source "arch/arm/mach-versatile/Kconfig"
253
254source "arch/arm/mach-aaec2000/Kconfig"
255
256source "arch/arm/mach-realview/Kconfig"
257
258# Definitions to make life easier
259config ARCH_ACORN
260	bool
261
262source arch/arm/mm/Kconfig
263
264#  bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
265config XSCALE_PMU
266	bool
267	depends on CPU_XSCALE && !XSCALE_PMU_TIMER
268	default y
269
270endmenu
271
272source "arch/arm/common/Kconfig"
273
274config FORCE_MAX_ZONEORDER
275	int
276	depends on SA1111
277	default "9"
278
279menu "Bus support"
280
281config ARM_AMBA
282	bool
283
284config ISA
285	bool
286	help
287	  Find out whether you have ISA slots on your motherboard.  ISA is the
288	  name of a bus system, i.e. the way the CPU talks to the other stuff
289	  inside your box.  Other bus systems are PCI, EISA, MicroChannel
290	  (MCA) or VESA.  ISA is an older system, now being displaced by PCI;
291	  newer boards don't support it.  If you have ISA, say Y, otherwise N.
292
293config ISA_DMA
294	bool
295
296config ISA_DMA_API
297	bool
298	default y
299
300config PCI
301	bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
302	help
303	  Find out whether you have a PCI motherboard. PCI is the name of a
304	  bus system, i.e. the way the CPU talks to the other stuff inside
305	  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
306	  VESA. If you have PCI, say Y, otherwise N.
307
308	  The PCI-HOWTO, available from
309	  <http://www.tldp.org/docs.html#howto>, contains valuable
310	  information about which PCI hardware does work under Linux and which
311	  doesn't.
312
313# Select the host bridge type
314config PCI_HOST_VIA82C505
315	bool
316	depends on PCI && ARCH_SHARK
317	default y
318
319source "drivers/pci/Kconfig"
320
321source "drivers/pcmcia/Kconfig"
322
323endmenu
324
325menu "Kernel Features"
326
327config SMP
328	bool "Symmetric Multi-Processing (EXPERIMENTAL)"
329	depends on EXPERIMENTAL && REALVIEW_MPCORE
330	help
331	  This enables support for systems with more than one CPU. If you have
332	  a system with only one CPU, like most personal computers, say N. If
333	  you have a system with more than one CPU, say Y.
334
335	  If you say N here, the kernel will run on single and multiprocessor
336	  machines, but will use only one CPU of a multiprocessor machine. If
337	  you say Y here, the kernel will run on many, but not all, single
338	  processor machines. On a single processor machine, the kernel will
339	  run faster if you say N here.
340
341	  See also the <file:Documentation/smp.txt>,
342	  <file:Documentation/i386/IO-APIC.txt>,
343	  <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
344	  <http://www.linuxdoc.org/docs.html#howto>.
345
346	  If you don't know what to do here, say N.
347
348config NR_CPUS
349	int "Maximum number of CPUs (2-32)"
350	range 2 32
351	depends on SMP
352	default "4"
353
354config HOTPLUG_CPU
355	bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
356	depends on SMP && HOTPLUG && EXPERIMENTAL
357	help
358	  Say Y here to experiment with turning CPUs off and on.  CPUs
359	  can be controlled through /sys/devices/system/cpu.
360
361config LOCAL_TIMERS
362	bool "Use local timer interrupts"
363	depends on SMP && REALVIEW_MPCORE
364	default y
365	help
366	  Enable support for local timers on SMP platforms, rather then the
367	  legacy IPI broadcast method.  Local timers allows the system
368	  accounting to be spread across the timer interval, preventing a
369	  "thundering herd" at every timer tick.
370
371config PREEMPT
372	bool "Preemptible Kernel (EXPERIMENTAL)"
373	depends on EXPERIMENTAL
374	help
375	  This option reduces the latency of the kernel when reacting to
376	  real-time or interactive events by allowing a low priority process to
377	  be preempted even if it is in kernel mode executing a system call.
378	  This allows applications to run more reliably even when the system is
379	  under load.
380
381	  Say Y here if you are building a kernel for a desktop, embedded
382	  or real-time system.  Say N if you are unsure.
383
384config NO_IDLE_HZ
385	bool "Dynamic tick timer"
386	help
387	  Select this option if you want to disable continuous timer ticks
388	  and have them programmed to occur as required. This option saves
389	  power as the system can remain in idle state for longer.
390
391	  By default dynamic tick is disabled during the boot, and can be
392	  manually enabled with:
393
394	    echo 1 > /sys/devices/system/timer/timer0/dyn_tick
395
396	  Alternatively, if you want dynamic tick automatically enabled
397	  during boot, pass "dyntick=enable" via the kernel command string.
398
399	  Please note that dynamic tick may affect the accuracy of
400	  timekeeping on some platforms depending on the implementation.
401	  Currently at least OMAP, PXA2xx and SA11x0 platforms are known
402	  to have accurate timekeeping with dynamic tick.
403
404config ARCH_DISCONTIGMEM_ENABLE
405	bool
406	default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
407	help
408	  Say Y to support efficient handling of discontiguous physical memory,
409	  for architectures which are either NUMA (Non-Uniform Memory Access)
410	  or have huge holes in the physical address space for other reasons.
411	  See <file:Documentation/vm/numa> for more.
412
413source "mm/Kconfig"
414
415config LEDS
416	bool "Timer and CPU usage LEDs"
417	depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
418		   ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
419		   ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
420		   ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
421		   ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE
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	depends on PM_LEGACY
660	---help---
661	  APM is a BIOS specification for saving power using several different
662	  techniques. This is mostly useful for battery powered laptops with
663	  APM compliant BIOSes. If you say Y here, the system time will be
664	  reset after a RESUME operation, the /proc/apm device will provide
665	  battery status information, and user-space programs will receive
666	  notification of APM "events" (e.g. battery status change).
667
668	  In order to use APM, you will need supporting software. For location
669	  and more information, read <file:Documentation/pm.txt> and the
670	  Battery Powered Linux mini-HOWTO, available from
671	  <http://www.tldp.org/docs.html#howto>.
672
673	  This driver does not spin down disk drives (see the hdparm(8)
674	  manpage ("man 8 hdparm") for that), and it doesn't turn off
675	  VESA-compliant "green" monitors.
676
677	  Generally, if you don't have a battery in your machine, there isn't
678	  much point in using this driver and you should say N. If you get
679	  random kernel OOPSes or reboots that don't seem to be related to
680	  anything, try disabling/enabling this option (or disabling/enabling
681	  APM in your BIOS).
682
683endmenu
684
685source "net/Kconfig"
686
687menu "Device Drivers"
688
689source "drivers/base/Kconfig"
690
691source "drivers/connector/Kconfig"
692
693if ALIGNMENT_TRAP
694source "drivers/mtd/Kconfig"
695endif
696
697source "drivers/parport/Kconfig"
698
699source "drivers/pnp/Kconfig"
700
701source "drivers/block/Kconfig"
702
703source "drivers/acorn/block/Kconfig"
704
705if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
706	|| ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
707	|| ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
708source "drivers/ide/Kconfig"
709endif
710
711source "drivers/scsi/Kconfig"
712
713source "drivers/md/Kconfig"
714
715source "drivers/message/fusion/Kconfig"
716
717source "drivers/ieee1394/Kconfig"
718
719source "drivers/message/i2o/Kconfig"
720
721source "drivers/net/Kconfig"
722
723source "drivers/isdn/Kconfig"
724
725# input before char - char/joystick depends on it. As does USB.
726
727source "drivers/input/Kconfig"
728
729source "drivers/char/Kconfig"
730
731source "drivers/i2c/Kconfig"
732
733source "drivers/hwmon/Kconfig"
734
735#source "drivers/l3/Kconfig"
736
737source "drivers/misc/Kconfig"
738
739source "drivers/mfd/Kconfig"
740
741source "drivers/media/Kconfig"
742
743source "drivers/video/Kconfig"
744
745source "sound/Kconfig"
746
747source "drivers/usb/Kconfig"
748
749source "drivers/mmc/Kconfig"
750
751endmenu
752
753source "fs/Kconfig"
754
755source "arch/arm/oprofile/Kconfig"
756
757source "arch/arm/Kconfig.debug"
758
759source "security/Kconfig"
760
761source "crypto/Kconfig"
762
763source "lib/Kconfig"
764