[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 and resume"
	depends on RTC_CLASS = y
	default y
	help
	  If you say yes here, the system time (wall clock) will be set using
	  the value read from a specified RTC device. This is useful to avoid
	  unnecessary fsck runs at boot time, and to network better.

config RTC_HCTOSYS_DEVICE
	string "RTC used to set the system time"
	depends on RTC_HCTOSYS = y
	default "rtc0"
	help
	  The RTC device that will be used to (re)initialize the system
	  clock, usually rtc0.  Initialization is done when the system
	  starts up, and when it resumes from a low power state.

	  This clock should be battery-backed, so that it reads the correct
	  time when the system boots from a power-off state.  Otherwise, your
	  system will need an external clock source (like an NTP server).

	  If the clock you specify here is not battery backed, it may still
	  be useful to reinitialize system time when resuming from system
	  sleep states.  Do not specify an RTC here unless it stays powered
	  during all this system's supported sleep states.

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

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.

comment "I2C RTC drivers"
	depends on RTC_CLASS

config RTC_DRV_DS1307
	tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00"
	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_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_MAX6900
	tristate "Maxim 6900"
	depends on RTC_CLASS && I2C
	help
	  If you say yes here you will get support for the
	  Maxim MAX6900 I2C RTC chip.

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

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_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_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_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 found on Acorn RiscPCs. This driver supports the
	  platform specific method of retrieving the current year from
	  the RTC's SRAM. It will work on other platforms with the same
	  chip, but the year will probably have to be tweaked.

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

comment "SPI RTC drivers"
	depends on RTC_CLASS

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

comment "Platform 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'"
	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_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_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_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_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.

comment "on-CPU RTC drivers"
	depends on RTC_CLASS

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_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_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 RTC 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_BFIN
	tristate "Blackfin On-Chip RTC"
	depends on RTC_CLASS && BFIN
	help
	  If you say yes here you will get support for the
	  Blackfin On-Chip Real Time Clock.

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

config RTC_DRV_RS5C313
	tristate "Ricoh RS5C313"
	depends on RTC_CLASS && BROKEN
	help
	  If you say yes here you get support for the Ricoh RS5C313 RTC chips.

endmenu
Commit	Line	Data
	1	#
	2	# RTC class/drivers configuration
	3	#
	4
	5	menu "Real Time Clock"
	6
	7	config RTC_LIB
	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
	18	probably want to enable one or more of the interfaces below.
	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 and resume"
	25	depends on RTC_CLASS = y
	26	default y
	27	help
	28	If you say yes here, the system time (wall clock) will be set using
	29	the value read from a specified RTC device. This is useful to avoid
	30	unnecessary fsck runs at boot time, and to network better.
	31
	32	config RTC_HCTOSYS_DEVICE
	33	string "RTC used to set the system time"
	34	depends on RTC_HCTOSYS = y
	35	default "rtc0"
	36	help
	37	The RTC device that will be used to (re)initialize the system
	38	clock, usually rtc0. Initialization is done when the system
	39	starts up, and when it resumes from a low power state.
	40
	41	This clock should be battery-backed, so that it reads the correct
	42	time when the system boots from a power-off state. Otherwise, your
	43	system will need an external clock source (like an NTP server).
	44
	45	If the clock you specify here is not battery backed, it may still
	46	be useful to reinitialize system time when resuming from system
	47	sleep states. Do not specify an RTC here unless it stays powered
	48	during all this system's supported sleep states.
	49
	50	config RTC_DEBUG
	51	bool "RTC debug support"
	52	depends on RTC_CLASS = y
	53	help
	54	Say yes here to enable debugging support in the RTC framework
	55	and individual RTC drivers.
	56
	57	comment "RTC interfaces"
	58	depends on RTC_CLASS
	59
	60	config RTC_INTF_SYSFS
	61	boolean "sysfs"
	62	depends on RTC_CLASS && SYSFS
	63	default RTC_CLASS
	64	help
	65	Say yes here if you want to use your RTCs using sysfs interfaces,
	66	/sys/class/rtc/rtc0 through /sys/.../rtcN.
	67
	68	This driver can also be built as a module. If so, the module
	69	will be called rtc-sysfs.
	70
	71	config RTC_INTF_PROC
	72	boolean "proc"
	73	depends on RTC_CLASS && PROC_FS
	74	default RTC_CLASS
	75	help
	76	Say yes here if you want to use your first RTC through the proc
	77	interface, /proc/driver/rtc. Other RTCs will not be available
	78	through that API.
	79
	80	This driver can also be built as a module. If so, the module
	81	will be called rtc-proc.
	82
	83	config RTC_INTF_DEV
	84	boolean "dev"
	85	depends on RTC_CLASS
	86	default RTC_CLASS
	87	help
	88	Say yes here if you want to use your RTCs using the /dev
	89	interfaces, which "udev" sets up as /dev/rtc0 through
	90	/dev/rtcN. You may want to set up a symbolic link so one
	91	of these can be accessed as /dev/rtc, which is a name
	92	expected by "hwclock" and some other programs.
	93
	94	This driver can also be built as a module. If so, the module
	95	will be called rtc-dev.
	96
	97	config RTC_INTF_DEV_UIE_EMUL
	98	bool "RTC UIE emulation on dev interface"
	99	depends on RTC_INTF_DEV
	100	help
	101	Provides an emulation for RTC_UIE if the underlaying rtc chip
	102	driver does not expose RTC_UIE ioctls. Those requests generate
	103	once-per-second update interrupts, used for synchronization.
	104
	105	config RTC_DRV_TEST
	106	tristate "Test driver/device"
	107	depends on RTC_CLASS
	108	help
	109	If you say yes here you get support for the
	110	RTC test driver. It's a software RTC which can be
	111	used to test the RTC subsystem APIs. It gets
	112	the time from the system clock.
	113	You want this driver only if you are doing development
	114	on the RTC subsystem. Please read the source code
	115	for further details.
	116
	117	This driver can also be built as a module. If so, the module
	118	will be called rtc-test.
	119
	120	comment "I2C RTC drivers"
	121	depends on RTC_CLASS
	122
	123	config RTC_DRV_DS1307
	124	tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00"
	125	depends on RTC_CLASS && I2C
	126	help
	127	If you say yes here you get support for various compatible RTC
	128	chips (often with battery backup) connected with I2C. This driver
	129	should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
	130	and probably other chips. In some cases the RTC must already
	131	have been initialized (by manufacturing or a bootloader).
	132
	133	The first seven registers on these chips hold an RTC, and other
	134	registers may add features such as NVRAM, a trickle charger for
	135	the RTC/NVRAM backup power, and alarms. This driver may not
	136	expose all those available chip features.
	137
	138	This driver can also be built as a module. If so, the module
	139	will be called rtc-ds1307.
	140
	141	config RTC_DRV_DS1672
	142	tristate "Dallas/Maxim DS1672"
	143	depends on RTC_CLASS && I2C
	144	help
	145	If you say yes here you get support for the
	146	Dallas/Maxim DS1672 timekeeping chip.
	147
	148	This driver can also be built as a module. If so, the module
	149	will be called rtc-ds1672.
	150
	151	config RTC_DRV_MAX6900
	152	tristate "Maxim 6900"
	153	depends on RTC_CLASS && I2C
	154	help
	155	If you say yes here you will get support for the
	156	Maxim MAX6900 I2C RTC chip.
	157
	158	This driver can also be built as a module. If so, the module
	159	will be called rtc-max6900.
	160
	161	config RTC_DRV_RS5C372
	162	tristate "Ricoh RS5C372A/B"
	163	depends on RTC_CLASS && I2C
	164	help
	165	If you say yes here you get support for the
	166	Ricoh RS5C372A and RS5C372B RTC chips.
	167
	168	This driver can also be built as a module. If so, the module
	169	will be called rtc-rs5c372.
	170
	171	config RTC_DRV_ISL1208
	172	tristate "Intersil 1208"
	173	depends on RTC_CLASS && I2C
	174	help
	175	If you say yes here you get support for the
	176	Intersil 1208 RTC chip.
	177
	178	This driver can also be built as a module. If so, the module
	179	will be called rtc-isl1208.
	180
	181	config RTC_DRV_X1205
	182	tristate "Xicor/Intersil X1205"
	183	depends on RTC_CLASS && I2C
	184	help
	185	If you say yes here you get support for the
	186	Xicor/Intersil X1205 RTC chip.
	187
	188	This driver can also be built as a module. If so, the module
	189	will be called rtc-x1205.
	190
	191	config RTC_DRV_PCF8563
	192	tristate "Philips PCF8563/Epson RTC8564"
	193	depends on RTC_CLASS && I2C
	194	help
	195	If you say yes here you get support for the
	196	Philips PCF8563 RTC chip. The Epson RTC8564
	197	should work as well.
	198
	199	This driver can also be built as a module. If so, the module
	200	will be called rtc-pcf8563.
	201
	202	config RTC_DRV_PCF8583
	203	tristate "Philips PCF8583"
	204	depends on RTC_CLASS && I2C
	205	help
	206	If you say yes here you get support for the Philips PCF8583
	207	RTC chip found on Acorn RiscPCs. This driver supports the
	208	platform specific method of retrieving the current year from
	209	the RTC's SRAM. It will work on other platforms with the same
	210	chip, but the year will probably have to be tweaked.
	211
	212	This driver can also be built as a module. If so, the module
	213	will be called rtc-pcf8583.
	214
	215	comment "SPI RTC drivers"
	216	depends on RTC_CLASS
	217
	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
	228	config RTC_DRV_MAX6902
	229	tristate "Maxim 6902"
	230	depends on RTC_CLASS && SPI
	231	help
	232	If you say yes here you will get support for the
	233	Maxim MAX6902 SPI RTC chip.
	234
	235	This driver can also be built as a module. If so, the module
	236	will be called rtc-max6902.
	237
	238	comment "Platform RTC drivers"
	239	depends on RTC_CLASS
	240
	241	# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
	242	# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
	243	# global rtc_lock ... it's not yet just another platform_device.
	244
	245	config RTC_DRV_CMOS
	246	tristate "PC-style 'CMOS'"
	247	depends on RTC_CLASS && (X86 \|\| ALPHA \|\| ARM26 \|\| ARM \
	248	\|\| M32R \|\| ATARI \|\| POWERPC)
	249	help
	250	Say "yes" here to get direct support for the real time clock
	251	found in every PC or ACPI-based system, and some other boards.
	252	Specifically the original MC146818, compatibles like those in
	253	PC south bridges, the DS12887 or M48T86, some multifunction
	254	or LPC bus chips, and so on.
	255
	256	Your system will need to define the platform device used by
	257	this driver, otherwise it won't be accessible. This means
	258	you can safely enable this driver if you don't know whether
	259	or not your board has this kind of hardware.
	260
	261	This driver can also be built as a module. If so, the module
	262	will be called rtc-cmos.
	263
	264	config RTC_DRV_DS1553
	265	tristate "Dallas DS1553"
	266	depends on RTC_CLASS
	267	help
	268	If you say yes here you get support for the
	269	Dallas DS1553 timekeeping chip.
	270
	271	This driver can also be built as a module. If so, the module
	272	will be called rtc-ds1553.
	273
	274	config RTC_DRV_DS1742
	275	tristate "Dallas DS1742/1743"
	276	depends on RTC_CLASS
	277	help
	278	If you say yes here you get support for the
	279	Dallas DS1742/1743 timekeeping chip.
	280
	281	This driver can also be built as a module. If so, the module
	282	will be called rtc-ds1742.
	283
	284	config RTC_DRV_M48T86
	285	tristate "ST M48T86/Dallas DS12887"
	286	depends on RTC_CLASS
	287	help
	288	If you say Y here you will get support for the
	289	ST M48T86 and Dallas DS12887 RTC chips.
	290
	291	This driver can also be built as a module. If so, the module
	292	will be called rtc-m48t86.
	293
	294	config RTC_DRV_V3020
	295	tristate "EM Microelectronic V3020"
	296	depends on RTC_CLASS
	297	help
	298	If you say yes here you will get support for the
	299	EM Microelectronic v3020 RTC chip.
	300
	301	This driver can also be built as a module. If so, the module
	302	will be called rtc-v3020.
	303
	304	comment "on-CPU RTC drivers"
	305	depends on RTC_CLASS
	306
	307	config RTC_DRV_OMAP
	308	tristate "TI OMAP1"
	309	depends on RTC_CLASS && ( \
	310	ARCH_OMAP15XX \|\| ARCH_OMAP16XX \|\| ARCH_OMAP730 )
	311	help
	312	Say "yes" here to support the real time clock on TI OMAP1 chips.
	313	This driver can also be built as a module called rtc-omap.
	314
	315	config RTC_DRV_S3C
	316	tristate "Samsung S3C series SoC RTC"
	317	depends on RTC_CLASS && ARCH_S3C2410
	318	help
	319	RTC (Realtime Clock) driver for the clock inbuilt into the
	320	Samsung S3C24XX series of SoCs. This can provide periodic
	321	interrupt rates from 1Hz to 64Hz for user programs, and
	322	wakeup from Alarm.
	323
	324	The driver currently supports the common features on all the
	325	S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
	326	and S3C2442.
	327
	328	This driver can also be build as a module. If so, the module
	329	will be called rtc-s3c.
	330
	331	config RTC_DRV_EP93XX
	332	tristate "Cirrus Logic EP93XX"
	333	depends on RTC_CLASS && ARCH_EP93XX
	334	help
	335	If you say yes here you get support for the
	336	RTC embedded in the Cirrus Logic EP93XX processors.
	337
	338	This driver can also be built as a module. If so, the module
	339	will be called rtc-ep93xx.
	340
	341	config RTC_DRV_SA1100
	342	tristate "SA11x0/PXA2xx"
	343	depends on RTC_CLASS && (ARCH_SA1100 \|\| ARCH_PXA)
	344	help
	345	If you say Y here you will get access to the real time clock
	346	built into your SA11x0 or PXA2xx CPU.
	347
	348	To compile this driver as a module, choose M here: the
	349	module will be called rtc-sa1100.
	350
	351	config RTC_DRV_SH
	352	tristate "SuperH On-Chip RTC"
	353	depends on RTC_CLASS && SUPERH
	354	help
	355	Say Y here to enable support for the on-chip RTC found in
	356	most SuperH processors.
	357
	358	To compile this driver as a module, choose M here: the
	359	module will be called rtc-sh.
	360
	361	config RTC_DRV_VR41XX
	362	tristate "NEC VR41XX"
	363	depends on RTC_CLASS && CPU_VR41XX
	364	help
	365	If you say Y here you will get access to the real time clock
	366	built into your NEC VR41XX CPU.
	367
	368	To compile this driver as a module, choose M here: the
	369	module will be called rtc-vr41xx.
	370
	371	config RTC_DRV_PL031
	372	tristate "ARM AMBA PL031 RTC"
	373	depends on RTC_CLASS && ARM_AMBA
	374	help
	375	If you say Y here you will get access to ARM AMBA
	376	PrimeCell PL031 RTC found on certain ARM SOCs.
	377
	378	To compile this driver as a module, choose M here: the
	379	module will be called rtc-pl031.
	380
	381	config RTC_DRV_AT91RM9200
	382	tristate "AT91RM9200"
	383	depends on RTC_CLASS && ARCH_AT91RM9200
	384	help
	385	Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).
	386
	387	config RTC_DRV_BFIN
	388	tristate "Blackfin On-Chip RTC"
	389	depends on RTC_CLASS && BFIN
	390	help
	391	If you say yes here you will get support for the
	392	Blackfin On-Chip Real Time Clock.
	393
	394	This driver can also be built as a module. If so, the module
	395	will be called rtc-bfin.
	396
	397	config RTC_DRV_RS5C313
	398	tristate "Ricoh RS5C313"
	399	depends on RTC_CLASS && BROKEN
	400	help
	401	If you say yes here you get support for the Ricoh RS5C313 RTC chips.
	402
	403	endmenu