Merge branch 'upstream' of git://ftp.linux-mips.org/pub/scm/upstream-linus

[linux-drm-fsl-dcu.git] / drivers / rtc / Kconfig

diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
index 62c804af9fbe473a5f20816d8f5fbaad3a1ff785..4bbca500d3d212bf264ddff889da7c05b258b5f5 100644 (file)
--- a/drivers/rtc/Kconfig
+++ b/drivers/rtc/Kconfig
@@ -1,4 +1,4 @@
-\#
+#
 # RTC class/drivers configuration
 #
 
@@ -37,6 +37,13 @@ config RTC_HCTOSYS_DEVICE
          The RTC device that will be used as the source for
          the system time, usually rtc0.
 
+config RTC_DEBUG
+       bool "RTC debug support"
+       depends on RTC_CLASS = y
+       help
+         Say yes here to enable debugging support in the RTC framework
+         and individual RTC drivers.
+
 comment "RTC interfaces"
        depends on RTC_CLASS
 
@@ -45,8 +52,8 @@ config RTC_INTF_SYSFS
        depends on RTC_CLASS && SYSFS
        default RTC_CLASS
        help
-         Say yes here if you want to use your RTC using the sysfs
-         interface, /sys/class/rtc/rtcX .
+         Say yes here if you want to use your RTCs using sysfs interfaces,
+         /sys/class/rtc/rtc0 through /sys/.../rtcN.
 
          This driver can also be built as a module. If so, the module
          will be called rtc-sysfs.
@@ -56,8 +63,9 @@ config RTC_INTF_PROC
        depends on RTC_CLASS && PROC_FS
        default RTC_CLASS
        help
-         Say yes here if you want to use your RTC using the proc
-         interface, /proc/driver/rtc .
+         Say yes here if you want to use your first RTC through the proc
+         interface, /proc/driver/rtc.  Other RTCs will not be available
+         through that API.
 
          This driver can also be built as a module. If so, the module
          will be called rtc-proc.
@@ -67,8 +75,11 @@ config RTC_INTF_DEV
        depends on RTC_CLASS
        default RTC_CLASS
        help
-         Say yes here if you want to use your RTC using the dev
-         interface, /dev/rtc .
+         Say yes here if you want to use your RTCs using the /dev
+         interfaces, which "udev" sets up as /dev/rtc0 through
+         /dev/rtcN.  You may want to set up a symbolic link so one
+         of these can be accessed as /dev/rtc, which is a name
+         expected by "hwclock" and some other programs.
 
          This driver can also be built as a module. If so, the module
          will be called rtc-dev.
@@ -78,11 +89,35 @@ config RTC_INTF_DEV_UIE_EMUL
        depends on RTC_INTF_DEV
        help
          Provides an emulation for RTC_UIE if the underlaying rtc chip
-         driver did not provide RTC_UIE ioctls.
+         driver does not expose RTC_UIE ioctls.  Those requests generate
+         once-per-second update interrupts, used for synchronization.
 
 comment "RTC drivers"
        depends on RTC_CLASS
 
+# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
+# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
+# global rtc_lock ... it's not yet just another platform_device.
+
+config RTC_DRV_CMOS
+       tristate "PC-style 'CMOS' real time clock"
+       depends on RTC_CLASS && (X86_PC || ALPHA || ARM26 || ARM \
+               || M32R || ATARI || POWERPC)
+       help
+         Say "yes" here to get direct support for the real time clock
+         found in every PC or ACPI-based system, and some other boards.
+         Specifically the original MC146818, compatibles like those in
+         PC south bridges, the DS12887 or M48T86, some multifunction
+         or LPC bus chips, and so on.
+
+         Your system will need to define the platform device used by
+         this driver, otherwise it won't be accessible.  This means
+         you can safely enable this driver if you don't know whether
+         or not your board has this kind of hardware.
+
+         This driver can also be built as a module. If so, the module
+         will be called rtc-cmos.
+
 config RTC_DRV_X1205
        tristate "Xicor/Intersil X1205"
        depends on RTC_CLASS && I2C
@@ -142,15 +177,23 @@ config RTC_DRV_DS1672
          will be called rtc-ds1672.
 
 config RTC_DRV_DS1742
-       tristate "Dallas DS1742"
+       tristate "Dallas DS1742/1743"
        depends on RTC_CLASS
        help
          If you say yes here you get support for the
-         Dallas DS1742 timekeeping chip.
+         Dallas DS1742/1743 timekeeping chip.
 
          This driver can also be built as a module. If so, the module
          will be called rtc-ds1742.
 
+config RTC_DRV_OMAP
+       tristate "TI OMAP1"
+       depends on RTC_CLASS && ( \
+               ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 )
+       help
+         Say "yes" here to support the real time clock on TI OMAP1 chips.
+         This driver can also be built as a module called rtc-omap.
+
 config RTC_DRV_PCF8563
        tristate "Philips PCF8563/Epson RTC8564"
        depends on RTC_CLASS && I2C
@@ -268,7 +311,7 @@ config RTC_DRV_PL031
          To compile this driver as a module, choose M here: the
          module will be called rtc-pl031.
 
-config RTC_DRV_AT91
+config RTC_DRV_AT91RM9200
        tristate "AT91RM9200"
        depends on RTC_CLASS && ARCH_AT91RM9200
        help