ARM: omap: split up arch/arm/plat-omap/Kconfig

[linux-2.6-block.git] / arch / arm / mach-omap1 / Kconfig

diff --git a/arch/arm/mach-omap1/Kconfig b/arch/arm/mach-omap1/Kconfig
index 04155b5ce97868c5c8800c2bbd578f4bcabb4a2a..93ea86954a84d122fa38106efa8939368892c646 100644 (file)
--- a/arch/arm/mach-omap1/Kconfig
+++ b/arch/arm/mach-omap1/Kconfig
@@ -28,6 +28,11 @@ config ARCH_OMAP16XX
        select CPU_ARM926T
        select OMAP_DM_TIMER
 
+config ARCH_OMAP
+       bool
+
+comment "OMAP Feature Selections"
+
 config OMAP_MUX
        bool "OMAP multiplexing support"
        default y
@@ -69,6 +74,38 @@ config OMAP_32K_TIMER
          The actual timer selection is done in the board file
          through the (DT_)MACHINE_START structure.
 
+config OMAP_MPU_TIMER
+       bool "Use mpu timer"
+       depends on ARCH_OMAP1
+       help
+         Select this option if you want to use the OMAP mpu timer. This
+         timer provides more intra-tick resolution than the 32KHz timer,
+         but consumes more power.
+
+config OMAP_SERIAL_WAKE
+       bool "Enable wake-up events for serial ports"
+       depends on ARCH_OMAP1 && OMAP_MUX
+       default y
+       help
+         Select this option if you want to have your system wake up
+         to data on the serial RX line. This allows you to wake the
+         system from serial console.
+
+config OMAP_RESET_CLOCKS
+       bool "Reset unused clocks during boot"
+       depends on ARCH_OMAP
+       help
+         Say Y if you want to reset unused clocks during boot.
+         This option saves power, but assumes all drivers are
+         using the clock framework. Broken drivers that do not
+         yet use clock framework may not work with this option.
+         If you are booting from another operating system, you
+         probably do not want this option enabled until your
+         device drivers work properly.
+
+config ARCH_OMAP_OTG
+       bool
+
 comment "OMAP Board Type"
 
 config MACH_OMAP_INNOVATOR