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

#
# RTC class/drivers configuration
#

menu "Real Time Clock"

config RTC_LIB
	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 or 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 fsck 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.

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

config RTC_INTF_SYSFS
	tristate "sysfs"
	depends on RTC_CLASS && SYSFS
	default RTC_CLASS
	help
	  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.

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 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.

config RTC_INTF_DEV
	tristate "dev"
	depends on RTC_CLASS
	default RTC_CLASS
	help
	  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.

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

# 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 || 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
	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.

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
	help
	  If you say yes here you get support for the
	  Dallas/Maxim DS1672 timekeeping chip.

	  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
	help
	  If you say yes here you get support for the
	  Philips PCF8563 RTC chip. The Epson RTC8564
	  should work as well.

	  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
	help
	  If you say yes here you get support for the
	  Ricoh RS5C372A and RS5C372B RTC chips.

	  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
	help
	  If you say Y here you will get support for the
	  ST M48T86 and Dallas DS12887 RTC chips.

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

config RTC_DRV_EP93XX
	tristate "Cirrus Logic EP93XX"
	depends on RTC_CLASS && ARCH_EP93XX
	help
	  If you say yes here you get support for the
	  RTC embedded in the Cirrus Logic EP93XX processors.

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

config RTC_DRV_SA1100
	tristate "SA11x0/PXA2xx"
	depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA)
	help
	  If you say Y here you will get access to the real time clock
	  built into your SA11x0 or PXA2xx CPU.

	  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
	help
	  If you say Y here you will get access to the real time clock
	  built into your NEC VR41XX CPU.

	  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
	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.

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
Commit	Line	Data
7be2c7c9	1	#
c58411e9 AZ	2	# RTC class/drivers configuration
	3	#
	4
0c86edc0 AZ	5	menu "Real Time Clock"
0c86edc0 AZ	6
c58411e9	7	config RTC_LIB
0c86edc0 AZ	8	tristate
	9
	10	config RTC_CLASS
	11	tristate "RTC class"
	12	depends on EXPERIMENTAL
	13	default n
	14	select RTC_LIB
	15	help
	16	Generic RTC class support. If you say yes here, you will
	17	be allowed to plug one or more RTCs to your system. You will
27ae4104	18	probably want to enable one or more of the interfaces below.
0c86edc0 AZ	19
	20	This driver can also be built as a module. If so, the module
	21	will be called rtc-class.
	22
	23	config RTC_HCTOSYS
	24	bool "Set system time from RTC on startup"
	25	depends on RTC_CLASS = y
	26	default y
	27	help
	28	If you say yes here, the system time will be set using
	29	the value read from the specified RTC device. This is useful
af3ffa67	30	in order to avoid unnecessary fsck runs.
0c86edc0 AZ	31
	32	config RTC_HCTOSYS_DEVICE
	33	string "The RTC to read the time from"
	34	depends on RTC_HCTOSYS = y
	35	default "rtc0"
	36	help
	37	The RTC device that will be used as the source for
	38	the system time, usually rtc0.
	39
9e86ecb6 DB	40	config RTC_DEBUG
	41	bool "RTC debug support"
	42	depends on RTC_CLASS = y
	43	help
	44	Say yes here to enable debugging support in the RTC framework
	45	and individual RTC drivers.
	46
0c86edc0 AZ	47	comment "RTC interfaces"
	48	depends on RTC_CLASS
	49
c5c3e192 AZ	50	config RTC_INTF_SYSFS
	51	tristate "sysfs"
	52	depends on RTC_CLASS && SYSFS
	53	default RTC_CLASS
	54	help
9e86ecb6 DB	55	Say yes here if you want to use your RTCs using sysfs interfaces,
9e86ecb6 DB	56	/sys/class/rtc/rtc0 through /sys/.../rtcN.
c5c3e192 AZ	57
	58	This driver can also be built as a module. If so, the module
	59	will be called rtc-sysfs.
	60
728a2947 AZ	61	config RTC_INTF_PROC
	62	tristate "proc"
	63	depends on RTC_CLASS && PROC_FS
	64	default RTC_CLASS
	65	help
9e86ecb6 DB	66	Say yes here if you want to use your first RTC through the proc
	67	interface, /proc/driver/rtc. Other RTCs will not be available
	68	through that API.
728a2947 AZ	69
	70	This driver can also be built as a module. If so, the module
	71	will be called rtc-proc.
	72
e824290e AZ	73	config RTC_INTF_DEV
	74	tristate "dev"
	75	depends on RTC_CLASS
	76	default RTC_CLASS
	77	help
9e86ecb6 DB	78	Say yes here if you want to use your RTCs using the /dev
	79	interfaces, which "udev" sets up as /dev/rtc0 through
	80	/dev/rtcN. You may want to set up a symbolic link so one
	81	of these can be accessed as /dev/rtc, which is a name
	82	expected by "hwclock" and some other programs.
e824290e AZ	83
	84	This driver can also be built as a module. If so, the module
	85	will be called rtc-dev.
	86
655066c3 AN	87	config RTC_INTF_DEV_UIE_EMUL
	88	bool "RTC UIE emulation on dev interface"
	89	depends on RTC_INTF_DEV
	90	help
	91	Provides an emulation for RTC_UIE if the underlaying rtc chip
9e86ecb6 DB	92	driver does not expose RTC_UIE ioctls. Those requests generate
9e86ecb6 DB	93	once-per-second update interrupts, used for synchronization.
655066c3	94
0c86edc0 AZ	95	comment "RTC drivers"
	96	depends on RTC_CLASS
	97
7be2c7c9 DB	98	# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
	99	# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
	100	# global rtc_lock ... it's not yet just another platform_device.
	101
	102	config RTC_DRV_CMOS
	103	tristate "PC-style 'CMOS' real time clock"
c066332f	104	depends on RTC_CLASS && (X86 \|\| ALPHA \|\| ARM26 \|\| ARM \
7be2c7c9 DB	105	\|\| M32R \|\| ATARI \|\| POWERPC)
	106	help
	107	Say "yes" here to get direct support for the real time clock
	108	found in every PC or ACPI-based system, and some other boards.
	109	Specifically the original MC146818, compatibles like those in
	110	PC south bridges, the DS12887 or M48T86, some multifunction
	111	or LPC bus chips, and so on.
	112
	113	Your system will need to define the platform device used by
	114	this driver, otherwise it won't be accessible. This means
	115	you can safely enable this driver if you don't know whether
	116	or not your board has this kind of hardware.
	117
	118	This driver can also be built as a module. If so, the module
	119	will be called rtc-cmos.
	120
1fec7c66 AZ	121	config RTC_DRV_X1205
	122	tristate "Xicor/Intersil X1205"
	123	depends on RTC_CLASS && I2C
	124	help
	125	If you say yes here you get support for the
	126	Xicor/Intersil X1205 RTC chip.
	127
	128	This driver can also be built as a module. If so, the module
	129	will be called rtc-x1205.
	130
1abb0dc9 DB	131	config RTC_DRV_DS1307
	132	tristate "Dallas/Maxim DS1307 and similar I2C RTC chips"
	133	depends on RTC_CLASS && I2C
	134	help
	135	If you say yes here you get support for various compatible RTC
	136	chips (often with battery backup) connected with I2C. This driver
	137	should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
	138	and probably other chips. In some cases the RTC must already
	139	have been initialized (by manufacturing or a bootloader).
	140
	141	The first seven registers on these chips hold an RTC, and other
	142	registers may add features such as NVRAM, a trickle charger for
	143	the RTC/NVRAM backup power, and alarms. This driver may not
	144	expose all those available chip features.
	145
	146	This driver can also be built as a module. If so, the module
	147	will be called rtc-ds1307.
	148
9bf5b4f5 AN	149	config RTC_DRV_DS1553
	150	tristate "Dallas DS1553"
	151	depends on RTC_CLASS
	152	help
	153	If you say yes here you get support for the
	154	Dallas DS1553 timekeeping chip.
	155
	156	This driver can also be built as a module. If so, the module
	157	will be called rtc-ds1553.
	158
7e56a7dc HVR	159	config RTC_DRV_ISL1208
	160	tristate "Intersil 1208"
	161	depends on RTC_CLASS && I2C
	162	help
	163	If you say yes here you get support for the
	164	Intersil 1208 RTC chip.
	165
	166	This driver can also be built as a module. If so, the module
	167	will be called rtc-isl1208.
	168
edf1aaa3 AZ	169	config RTC_DRV_DS1672
	170	tristate "Dallas/Maxim DS1672"
	171	depends on RTC_CLASS && I2C
	172	help
	173	If you say yes here you get support for the
	174	Dallas/Maxim DS1672 timekeeping chip.
	175
	176	This driver can also be built as a module. If so, the module
	177	will be called rtc-ds1672.
	178
5ec3e4b7	179	config RTC_DRV_DS1742
f9231a0c	180	tristate "Dallas DS1742/1743"
5ec3e4b7 AN	181	depends on RTC_CLASS
	182	help
	183	If you say yes here you get support for the
f9231a0c	184	Dallas DS1742/1743 timekeeping chip.
5ec3e4b7 AN	185
	186	This driver can also be built as a module. If so, the module
	187	will be called rtc-ds1742.
	188
db68b189 DB	189	config RTC_DRV_OMAP
	190	tristate "TI OMAP1"
	191	depends on RTC_CLASS && ( \
	192	ARCH_OMAP15XX \|\| ARCH_OMAP16XX \|\| ARCH_OMAP730 )
	193	help
	194	Say "yes" here to support the real time clock on TI OMAP1 chips.
	195	This driver can also be built as a module called rtc-omap.
	196
b5a82d62 AZ	197	config RTC_DRV_PCF8563
	198	tristate "Philips PCF8563/Epson RTC8564"
	199	depends on RTC_CLASS && I2C
	200	help
	201	If you say yes here you get support for the
	202	Philips PCF8563 RTC chip. The Epson RTC8564
	203	should work as well.
	204
	205	This driver can also be built as a module. If so, the module
	206	will be called rtc-pcf8563.
	207
9c0c5705 L	208	config RTC_DRV_PCF8583
	209	tristate "Philips PCF8583"
	210	depends on RTC_CLASS && I2C
	211	help
	212	If you say yes here you get support for the
	213	Philips PCF8583 RTC chip.
	214
	215	This driver can also be built as a module. If so, the module
	216	will be called rtc-pcf8583.
	217
e0ac4761 AN	218	config RTC_DRV_RS5C348
	219	tristate "Ricoh RS5C348A/B"
	220	depends on RTC_CLASS && SPI
	221	help
	222	If you say yes here you get support for the
	223	Ricoh RS5C348A and RS5C348B RTC chips.
	224
	225	This driver can also be built as a module. If so, the module
	226	will be called rtc-rs5c348.
	227
7520b94d AZ	228	config RTC_DRV_RS5C372
	229	tristate "Ricoh RS5C372A/B"
	230	depends on RTC_CLASS && I2C
	231	help
	232	If you say yes here you get support for the
	233	Ricoh RS5C372A and RS5C372B RTC chips.
	234
	235	This driver can also be built as a module. If so, the module
	236	will be called rtc-rs5c372.
	237
1add6781 BD	238	config RTC_DRV_S3C
	239	tristate "Samsung S3C series SoC RTC"
	240	depends on RTC_CLASS && ARCH_S3C2410
	241	help
	242	RTC (Realtime Clock) driver for the clock inbuilt into the
	243	Samsung S3C24XX series of SoCs. This can provide periodic
	244	interrupt rates from 1Hz to 64Hz for user programs, and
	245	wakeup from Alarm.
	246
	247	The driver currently supports the common features on all the
	248	S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
	249	and S3C2442.
	250
	251	This driver can also be build as a module. If so, the module
	252	will be called rtc-s3c.
	253
1d98af87 AZ	254	config RTC_DRV_M48T86
	255	tristate "ST M48T86/Dallas DS12887"
	256	depends on RTC_CLASS
	257	help
	258	If you say Y here you will get support for the
	259	ST M48T86 and Dallas DS12887 RTC chips.
	260
	261	This driver can also be built as a module. If so, the module
	262	will be called rtc-m48t86.
	263
fd507e2f AZ	264	config RTC_DRV_EP93XX
	265	tristate "Cirrus Logic EP93XX"
	266	depends on RTC_CLASS && ARCH_EP93XX
	267	help
	268	If you say yes here you get support for the
	269	RTC embedded in the Cirrus Logic EP93XX processors.
	270
	271	This driver can also be built as a module. If so, the module
	272	will be called rtc-ep93xx.
	273
e842f1c8 RP	274	config RTC_DRV_SA1100
	275	tristate "SA11x0/PXA2xx"
	276	depends on RTC_CLASS && (ARCH_SA1100 \|\| ARCH_PXA)
	277	help
	278	If you say Y here you will get access to the real time clock
	279	built into your SA11x0 or PXA2xx CPU.
	280
	281	To compile this driver as a module, choose M here: the
	282	module will be called rtc-sa1100.
fd507e2f	283
317a6104 PM	284	config RTC_DRV_SH
	285	tristate "SuperH On-Chip RTC"
	286	depends on RTC_CLASS && SUPERH
	287	help
	288	Say Y here to enable support for the on-chip RTC found in
	289	most SuperH processors.
	290
	291	To compile this driver as a module, choose M here: the
	292	module will be called rtc-sh.
	293
8417eb7a	294	config RTC_DRV_VR41XX
3e16f6af	295	tristate "NEC VR41XX"
8417eb7a	296	depends on RTC_CLASS && CPU_VR41XX
3e16f6af AZ	297	help
	298	If you say Y here you will get access to the real time clock
	299	built into your NEC VR41XX CPU.
	300
	301	To compile this driver as a module, choose M here: the
	302	module will be called rtc-vr41xx.
8417eb7a	303
8ae6e163 DS	304	config RTC_DRV_PL031
	305	tristate "ARM AMBA PL031 RTC"
	306	depends on RTC_CLASS && ARM_AMBA
	307	help
	308	If you say Y here you will get access to ARM AMBA
	309	PrimeCell PL031 UART found on certain ARM SOCs.
	310
	311	To compile this driver as a module, choose M here: the
	312	module will be called rtc-pl031.
	313
7fc39f6d	314	config RTC_DRV_AT91RM9200
788b1fc6 AV	315	tristate "AT91RM9200"
	316	depends on RTC_CLASS && ARCH_AT91RM9200
	317	help
	318	Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).
	319
a95579cd AZ	320	config RTC_DRV_TEST
	321	tristate "Test driver/device"
	322	depends on RTC_CLASS
	323	help
	324	If you say yes here you get support for the
	325	RTC test driver. It's a software RTC which can be
	326	used to test the RTC subsystem APIs. It gets
	327	the time from the system clock.
	328	You want this driver only if you are doing development
	329	on the RTC subsystem. Please read the source code
	330	for further details.
	331
	332	This driver can also be built as a module. If so, the module
	333	will be called rtc-test.
	334
8e12ecc2 RA	335	config RTC_DRV_MAX6902
	336	tristate "Maxim 6902"
	337	depends on RTC_CLASS && SPI
	338	help
	339	If you say yes here you will get support for the
	340	Maxim MAX6902 spi RTC chip.
	341
	342	This driver can also be built as a module. If so, the module
	343	will be called rtc-max6902.
	344
362600fe RA	345	config RTC_DRV_V3020
	346	tristate "EM Microelectronic V3020"
	347	depends on RTC_CLASS
	348	help
	349	If you say yes here you will get support for the
	350	EM Microelectronic v3020 RTC chip.
	351
	352	This driver can also be built as a module. If so, the module
	353	will be called rtc-v3020.
	354
0c86edc0	355	endmenu