2006-03-27 13:16:37 +04:00
|
|
|
\#
|
2006-03-27 13:16:34 +04:00
|
|
|
# RTC class/drivers configuration
|
|
|
|
|
#
|
|
|
|
|
|
2006-03-27 13:16:37 +04:00
|
|
|
menu "Real Time Clock"
|
|
|
|
|
|
2006-03-27 13:16:34 +04:00
|
|
|
config RTC_LIB
|
2006-03-27 13:16:37 +04:00
|
|
|
tristate
|
|
|
|
|
|
|
|
|
|
config RTC_CLASS
|
|
|
|
|
tristate "RTC class"
|
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
|
default n
|
|
|
|
|
select RTC_LIB
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-class.
|
|
|
|
|
|
|
|
|
|
config RTC_HCTOSYS
|
|
|
|
|
bool "Set system time from RTC on startup"
|
|
|
|
|
depends on RTC_CLASS = y
|
|
|
|
|
default y
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
config RTC_HCTOSYS_DEVICE
|
|
|
|
|
string "The RTC to read the time from"
|
|
|
|
|
depends on RTC_HCTOSYS = y
|
|
|
|
|
default "rtc0"
|
|
|
|
|
help
|
|
|
|
|
The RTC device that will be used as the source for
|
|
|
|
|
the system time, usually rtc0.
|
|
|
|
|
|
|
|
|
|
comment "RTC interfaces"
|
|
|
|
|
depends on RTC_CLASS
|
|
|
|
|
|
2006-03-27 13:16:39 +04:00
|
|
|
config RTC_INTF_SYSFS
|
|
|
|
|
tristate "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 .
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-sysfs.
|
|
|
|
|
|
2006-03-27 13:16:40 +04:00
|
|
|
config RTC_INTF_PROC
|
|
|
|
|
tristate "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 .
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-proc.
|
|
|
|
|
|
2006-03-27 13:16:41 +04:00
|
|
|
config RTC_INTF_DEV
|
|
|
|
|
tristate "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 .
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-dev.
|
|
|
|
|
|
2006-03-27 13:16:37 +04:00
|
|
|
comment "RTC drivers"
|
|
|
|
|
depends on RTC_CLASS
|
|
|
|
|
|
2006-03-27 13:16:42 +04:00
|
|
|
config RTC_DRV_X1205
|
|
|
|
|
tristate "Xicor/Intersil X1205"
|
|
|
|
|
depends on RTC_CLASS && I2C
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
|
|
|
|
Xicor/Intersil X1205 RTC chip.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-x1205.
|
|
|
|
|
|
2006-03-27 13:16:42 +04:00
|
|
|
config RTC_DRV_TEST
|
|
|
|
|
tristate "Test driver/device"
|
|
|
|
|
depends on RTC_CLASS
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
|
|
|
|
RTC test driver. It's a software RTC which can be
|
|
|
|
|
used to test the RTC subsystem APIs. It gets
|
|
|
|
|
the time from the system clock.
|
|
|
|
|
You want this driver only if you are doing development
|
|
|
|
|
on the RTC subsystem. Please read the source code
|
|
|
|
|
for further details.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-test.
|
|
|
|
|
|
2006-03-27 13:16:37 +04:00
|
|
|
endmenu
|
