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