fedora core 6 1.2949 + vserver 2.2.0

[linux-2.6.git] / drivers / rtc / Kconfig

diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
index 65d090d..09660e2 100644 (file)
--- a/drivers/rtc/Kconfig
+++ b/drivers/rtc/Kconfig
@@ -15,7 +15,7 @@ config RTC_CLASS
        help
          Generic RTC class support. If you say yes here, you will
          be allowed to plug one or more RTCs to your system. You will
        help
          Generic RTC class support. If you say yes here, you will
          be allowed to plug one or more RTCs to your system. You will

-         probably want to enable one of more of the interfaces below.
+         probably want to enable one or more of the interfaces below.

 
          This driver can also be built as a module. If so, the module
          will be called rtc-class.
 
          This driver can also be built as a module. If so, the module
          will be called rtc-class.


@@ -27,7 +27,7 @@ config RTC_HCTOSYS
        help
          If you say yes here, the system time will be set using
          the value read from the specified RTC device. This is useful
        help
          If you say yes here, the system time will be set using
          the value read from the specified RTC device. This is useful

-         in order to avoid unnecessary fschk runs.
+         in order to avoid unnecessary fsck runs.

 
 config RTC_HCTOSYS_DEVICE
        string "The RTC to read the time from"
 
 config RTC_HCTOSYS_DEVICE
        string "The RTC to read the time from"


@@ -37,6 +37,13 @@ config RTC_HCTOSYS_DEVICE
          The RTC device that will be used as the source for
          the system time, usually rtc0.
 
          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
 
 comment "RTC interfaces"
        depends on RTC_CLASS
 


@@ -45,8 +52,8 @@ config RTC_INTF_SYSFS
        depends on RTC_CLASS && SYSFS
        default RTC_CLASS
        help
        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.
 
          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
        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.
 
          This driver can also be built as a module. If so, the module
          will be called rtc-proc.


@@ -67,12 +75,23 @@ config RTC_INTF_DEV
        depends on RTC_CLASS
        default RTC_CLASS
        help
        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.
 
 
          This driver can also be built as a module. If so, the module
          will be called rtc-dev.
 

+config RTC_INTF_DEV_UIE_EMUL
+       bool "RTC UIE emulation on dev interface"
+       depends on RTC_INTF_DEV
+       help
+         Provides an emulation for RTC_UIE if the underlaying rtc chip
+         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
 
 comment "RTC drivers"
        depends on RTC_CLASS
 


@@ -86,6 +105,44 @@ config RTC_DRV_X1205
          This driver can also be built as a module. If so, the module
          will be called rtc-x1205.
 
          This driver can also be built as a module. If so, the module
          will be called rtc-x1205.
 

+config RTC_DRV_DS1307
+       tristate "Dallas/Maxim DS1307 and similar I2C RTC chips"
+       depends on RTC_CLASS && I2C
+       help
+         If you say yes here you get support for various compatible RTC
+         chips (often with battery backup) connected with I2C.  This driver
+         should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
+         and probably other chips.  In some cases the RTC must already
+         have been initialized (by manufacturing or a bootloader).
+
+         The first seven registers on these chips hold an RTC, and other
+         registers may add features such as NVRAM, a trickle charger for
+         the RTC/NVRAM backup power, and alarms.  This driver may not
+         expose all those available chip features.
+
+         This driver can also be built as a module. If so, the module
+         will be called rtc-ds1307.
+
+config RTC_DRV_DS1553
+       tristate "Dallas DS1553"
+       depends on RTC_CLASS
+       help
+         If you say yes here you get support for the
+         Dallas DS1553 timekeeping chip.
+
+         This driver can also be built as a module. If so, the module
+         will be called rtc-ds1553.
+
+config RTC_DRV_ISL1208
+       tristate "Intersil 1208"
+       depends on RTC_CLASS && I2C
+       help
+         If you say yes here you get support for the
+         Intersil 1208 RTC chip.
+
+         This driver can also be built as a module. If so, the module
+         will be called rtc-isl1208.
+

 config RTC_DRV_DS1672
        tristate "Dallas/Maxim DS1672"
        depends on RTC_CLASS && I2C
 config RTC_DRV_DS1672
        tristate "Dallas/Maxim DS1672"
        depends on RTC_CLASS && I2C


@@ -96,6 +153,24 @@ config RTC_DRV_DS1672
          This driver can also be built as a module. If so, the module
          will be called rtc-ds1672.
 
          This driver can also be built as a module. If so, the module
          will be called rtc-ds1672.
 

+config RTC_DRV_DS1742
+       tristate "Dallas DS1742/1743"
+       depends on RTC_CLASS
+       help
+         If you say yes here you get support for the
+         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
 config RTC_DRV_PCF8563
        tristate "Philips PCF8563/Epson RTC8564"
        depends on RTC_CLASS && I2C


@@ -107,6 +182,26 @@ config RTC_DRV_PCF8563
          This driver can also be built as a module. If so, the module
          will be called rtc-pcf8563.
 
          This driver can also be built as a module. If so, the module
          will be called rtc-pcf8563.
 

+config RTC_DRV_PCF8583
+       tristate "Philips PCF8583"
+       depends on RTC_CLASS && I2C
+       help
+         If you say yes here you get support for the
+         Philips PCF8583 RTC chip.
+
+         This driver can also be built as a module. If so, the module
+         will be called rtc-pcf8583.
+
+config RTC_DRV_RS5C348
+       tristate "Ricoh RS5C348A/B"
+       depends on RTC_CLASS && SPI
+       help
+         If you say yes here you get support for the
+         Ricoh RS5C348A and RS5C348B RTC chips.
+
+         This driver can also be built as a module. If so, the module
+         will be called rtc-rs5c348.
+

 config RTC_DRV_RS5C372
        tristate "Ricoh RS5C372A/B"
        depends on RTC_CLASS && I2C
 config RTC_DRV_RS5C372
        tristate "Ricoh RS5C372A/B"
        depends on RTC_CLASS && I2C


@@ -117,6 +212,22 @@ config RTC_DRV_RS5C372
          This driver can also be built as a module. If so, the module
          will be called rtc-rs5c372.
 
          This driver can also be built as a module. If so, the module
          will be called rtc-rs5c372.
 

+config RTC_DRV_S3C
+       tristate "Samsung S3C series SoC RTC"
+       depends on RTC_CLASS && ARCH_S3C2410
+       help
+         RTC (Realtime Clock) driver for the clock inbuilt into the
+         Samsung S3C24XX series of SoCs. This can provide periodic
+         interrupt rates from 1Hz to 64Hz for user programs, and
+         wakeup from Alarm.
+
+         The driver currently supports the common features on all the
+         S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
+         and S3C2442.
+
+         This driver can also be build as a module. If so, the module
+         will be called rtc-s3c.
+

 config RTC_DRV_M48T86
        tristate "ST M48T86/Dallas DS12887"
        depends on RTC_CLASS
 config RTC_DRV_M48T86
        tristate "ST M48T86/Dallas DS12887"
        depends on RTC_CLASS


@@ -147,6 +258,16 @@ config RTC_DRV_SA1100
          To compile this driver as a module, choose M here: the
          module will be called rtc-sa1100.
 
          To compile this driver as a module, choose M here: the
          module will be called rtc-sa1100.
 

+config RTC_DRV_SH
+       tristate "SuperH On-Chip RTC"
+       depends on RTC_CLASS && SUPERH
+       help
+         Say Y here to enable support for the on-chip RTC found in
+         most SuperH processors.
+
+         To compile this driver as a module, choose M here: the
+         module will be called rtc-sh.
+

 config RTC_DRV_VR41XX
        tristate "NEC VR41XX"
        depends on RTC_CLASS && CPU_VR41XX
 config RTC_DRV_VR41XX
        tristate "NEC VR41XX"
        depends on RTC_CLASS && CPU_VR41XX


@@ -157,6 +278,22 @@ config RTC_DRV_VR41XX
          To compile this driver as a module, choose M here: the
          module will be called rtc-vr41xx.
 
          To compile this driver as a module, choose M here: the
          module will be called rtc-vr41xx.
 

+config RTC_DRV_PL031
+       tristate "ARM AMBA PL031 RTC"
+       depends on RTC_CLASS && ARM_AMBA
+       help
+         If you say Y here you will get access to ARM AMBA
+         PrimeCell PL031 UART found on certain ARM SOCs.
+
+         To compile this driver as a module, choose M here: the
+         module will be called rtc-pl031.
+
+config RTC_DRV_AT91RM9200
+       tristate "AT91RM9200"
+       depends on RTC_CLASS && ARCH_AT91RM9200
+       help
+         Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).
+

 config RTC_DRV_TEST
        tristate "Test driver/device"
        depends on RTC_CLASS
 config RTC_DRV_TEST
        tristate "Test driver/device"
        depends on RTC_CLASS


@@ -172,4 +309,24 @@ config RTC_DRV_TEST
          This driver can also be built as a module. If so, the module
          will be called rtc-test.
 
          This driver can also be built as a module. If so, the module
          will be called rtc-test.
 

+config RTC_DRV_MAX6902
+       tristate "Maxim 6902"
+       depends on RTC_CLASS && SPI
+       help
+         If you say yes here you will get support for the
+         Maxim MAX6902 spi RTC chip.
+
+         This driver can also be built as a module. If so, the module
+         will be called rtc-max6902.
+
+config RTC_DRV_V3020
+       tristate "EM Microelectronic V3020"
+       depends on RTC_CLASS
+       help
+         If you say yes here you will get support for the
+         EM Microelectronic v3020 RTC chip.
+
+         This driver can also be built as a module. If so, the module
+         will be called rtc-v3020.
+

 endmenu
 endmenu