blob: 4ad831de41adb42f861832b7b6653ff3b61cc35c [file] [log] [blame]
David Brownell7be2c7c2007-02-10 01:46:02 -08001#
Alessandro Zummoc58411e2006-03-27 01:16:34 -08002# RTC class/drivers configuration
3#
4
5config RTC_LIB
Alessandro Zummo0c86edc2006-03-27 01:16:37 -08006 tristate
7
Jan Engelhardtbb35fb22007-07-31 00:39:46 -07008menuconfig RTC_CLASS
9 tristate "Real Time Clock"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080010 default n
Jan Engelhardtbb35fb22007-07-31 00:39:46 -070011 depends on !S390
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080012 select RTC_LIB
13 help
14 Generic RTC class support. If you say yes here, you will
15 be allowed to plug one or more RTCs to your system. You will
Adrian Bunk27ae4102006-06-30 18:18:41 +020016 probably want to enable one or more of the interfaces below.
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080017
18 This driver can also be built as a module. If so, the module
Alessandro Zummo44e04512008-03-19 17:00:51 -070019 will be called rtc-core.
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080020
Jan Engelhardtbb35fb22007-07-31 00:39:46 -070021if RTC_CLASS
22
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080023config RTC_HCTOSYS
David Brownell7ca1d482007-05-08 00:33:42 -070024 bool "Set system time from RTC on startup and resume"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080025 depends on RTC_CLASS = y
26 default y
27 help
David Brownell7ca1d482007-05-08 00:33:42 -070028 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.
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080031
32config RTC_HCTOSYS_DEVICE
David Brownell7ca1d482007-05-08 00:33:42 -070033 string "RTC used to set the system time"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080034 depends on RTC_HCTOSYS = y
35 default "rtc0"
36 help
David Brownell7ca1d482007-05-08 00:33:42 -070037 The RTC device that will be used to (re)initialize the system
Alessandro Zummoae64d162009-01-06 14:42:17 -080038 clock, usually rtc0. Initialization is done when the system
39 starts up, and when it resumes from a low power state. This
David Brownell779d2082007-11-14 16:58:29 -080040 device should record time in UTC, since the kernel won't do
41 timezone correction.
David Brownell7ca1d482007-05-08 00:33:42 -070042
David Brownell55ff1ab2007-07-21 04:37:56 -070043 The driver for this RTC device must be loaded before late_initcall
44 functions run, so it must usually be statically linked.
45
David Brownell7ca1d482007-05-08 00:33:42 -070046 This clock should be battery-backed, so that it reads the correct
Alessandro Zummoae64d162009-01-06 14:42:17 -080047 time when the system boots from a power-off state. Otherwise, your
David Brownell7ca1d482007-05-08 00:33:42 -070048 system will need an external clock source (like an NTP server).
49
50 If the clock you specify here is not battery backed, it may still
51 be useful to reinitialize system time when resuming from system
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -080052 sleep states. Do not specify an RTC here unless it stays powered
David Brownell7ca1d482007-05-08 00:33:42 -070053 during all this system's supported sleep states.
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080054
David Brownell9e86ecb2006-09-30 23:28:14 -070055config RTC_DEBUG
56 bool "RTC debug support"
57 depends on RTC_CLASS = y
58 help
59 Say yes here to enable debugging support in the RTC framework
60 and individual RTC drivers.
61
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080062comment "RTC interfaces"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080063
Alessandro Zummoc5c3e192006-03-27 01:16:39 -080064config RTC_INTF_SYSFS
David Brownelle40659c2007-05-16 22:11:15 -070065 boolean "/sys/class/rtc/rtcN (sysfs)"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -070066 depends on SYSFS
Alessandro Zummoc5c3e192006-03-27 01:16:39 -080067 default RTC_CLASS
68 help
David Brownell9e86ecb2006-09-30 23:28:14 -070069 Say yes here if you want to use your RTCs using sysfs interfaces,
70 /sys/class/rtc/rtc0 through /sys/.../rtcN.
Alessandro Zummoc5c3e192006-03-27 01:16:39 -080071
Alessandro Zummoae64d162009-01-06 14:42:17 -080072 If unsure, say Y.
Alessandro Zummoc5c3e192006-03-27 01:16:39 -080073
Alessandro Zummo728a2942006-03-27 01:16:40 -080074config RTC_INTF_PROC
David Brownelle40659c2007-05-16 22:11:15 -070075 boolean "/proc/driver/rtc (procfs for rtc0)"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -070076 depends on PROC_FS
Alessandro Zummo728a2942006-03-27 01:16:40 -080077 default RTC_CLASS
78 help
David Brownell9e86ecb2006-09-30 23:28:14 -070079 Say yes here if you want to use your first RTC through the proc
Alessandro Zummoae64d162009-01-06 14:42:17 -080080 interface, /proc/driver/rtc. Other RTCs will not be available
David Brownell9e86ecb2006-09-30 23:28:14 -070081 through that API.
Alessandro Zummo728a2942006-03-27 01:16:40 -080082
Alessandro Zummoae64d162009-01-06 14:42:17 -080083 If unsure, say Y.
Alessandro Zummo728a2942006-03-27 01:16:40 -080084
Alessandro Zummoe8242902006-03-27 01:16:41 -080085config RTC_INTF_DEV
David Brownelle40659c2007-05-16 22:11:15 -070086 boolean "/dev/rtcN (character devices)"
Alessandro Zummoe8242902006-03-27 01:16:41 -080087 default RTC_CLASS
88 help
David Brownell9e86ecb2006-09-30 23:28:14 -070089 Say yes here if you want to use your RTCs using the /dev
90 interfaces, which "udev" sets up as /dev/rtc0 through
Alessandro Zummoae64d162009-01-06 14:42:17 -080091 /dev/rtcN.
Alessandro Zummoe8242902006-03-27 01:16:41 -080092
Alessandro Zummoae64d162009-01-06 14:42:17 -080093 You may want to set up a symbolic link so one of these
94 can be accessed as /dev/rtc, which is a name
95 expected by "hwclock" and some other programs. Recent
96 versions of "udev" are known to set up the symlink for you.
97
98 If unsure, say Y.
Alessandro Zummoe8242902006-03-27 01:16:41 -080099
Atsushi Nemoto655066c2006-06-25 05:48:17 -0700100config RTC_INTF_DEV_UIE_EMUL
101 bool "RTC UIE emulation on dev interface"
102 depends on RTC_INTF_DEV
103 help
David Sterba3dde6ad2007-05-09 07:12:20 +0200104 Provides an emulation for RTC_UIE if the underlying rtc chip
Alessandro Zummo099e6572009-01-04 12:00:54 -0800105 driver does not expose RTC_UIE ioctls. Those requests generate
David Brownell9e86ecb2006-09-30 23:28:14 -0700106 once-per-second update interrupts, used for synchronization.
Atsushi Nemoto655066c2006-06-25 05:48:17 -0700107
Alessandro Zummo099e6572009-01-04 12:00:54 -0800108 The emulation code will read the time from the hardware
109 clock several times per second, please enable this option
110 only if you know that you really need it.
111
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700112config RTC_DRV_TEST
113 tristate "Test driver/device"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700114 help
115 If you say yes here you get support for the
116 RTC test driver. It's a software RTC which can be
117 used to test the RTC subsystem APIs. It gets
118 the time from the system clock.
119 You want this driver only if you are doing development
120 on the RTC subsystem. Please read the source code
121 for further details.
122
123 This driver can also be built as a module. If so, the module
124 will be called rtc-test.
125
126comment "I2C RTC drivers"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700127 depends on I2C
128
129if I2C
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700130
131config RTC_DRV_DS1307
132 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700133 help
134 If you say yes here you get support for various compatible RTC
Alessandro Zummoae64d162009-01-06 14:42:17 -0800135 chips (often with battery backup) connected with I2C. This driver
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700136 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
Alessandro Zummoae64d162009-01-06 14:42:17 -0800137 and probably other chips. In some cases the RTC must already
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700138 have been initialized (by manufacturing or a bootloader).
139
140 The first seven registers on these chips hold an RTC, and other
141 registers may add features such as NVRAM, a trickle charger for
Alessandro Zummoae64d162009-01-06 14:42:17 -0800142 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
David Brownell682d73f2007-11-14 16:58:32 -0800143 sysfs, but other chip features may not be available.
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700144
145 This driver can also be built as a module. If so, the module
146 will be called rtc-ds1307.
147
Scott Woodbf4994d2007-10-16 01:28:19 -0700148config RTC_DRV_DS1374
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800149 tristate "Dallas/Maxim DS1374"
Scott Woodbf4994d2007-10-16 01:28:19 -0700150 depends on RTC_CLASS && I2C
151 help
152 If you say yes here you get support for Dallas Semiconductor
Alessandro Zummoae64d162009-01-06 14:42:17 -0800153 DS1374 real-time clock chips. If an interrupt is associated
Scott Woodbf4994d2007-10-16 01:28:19 -0700154 with the device, the alarm functionality is supported.
155
Alessandro Zummoae64d162009-01-06 14:42:17 -0800156 This driver can also be built as a module. If so, the module
Scott Woodbf4994d2007-10-16 01:28:19 -0700157 will be called rtc-ds1374.
158
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700159config RTC_DRV_DS1672
160 tristate "Dallas/Maxim DS1672"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700161 help
162 If you say yes here you get support for the
163 Dallas/Maxim DS1672 timekeeping chip.
164
165 This driver can also be built as a module. If so, the module
166 will be called rtc-ds1672.
167
168config RTC_DRV_MAX6900
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800169 tristate "Maxim MAX6900"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700170 help
171 If you say yes here you will get support for the
172 Maxim MAX6900 I2C RTC chip.
173
174 This driver can also be built as a module. If so, the module
175 will be called rtc-max6900.
176
177config RTC_DRV_RS5C372
Paul Mundt5d4529b2008-10-21 20:12:59 +0900178 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700179 help
180 If you say yes here you get support for the
Paul Mundt5d4529b2008-10-21 20:12:59 +0900181 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700182
183 This driver can also be built as a module. If so, the module
184 will be called rtc-rs5c372.
185
186config RTC_DRV_ISL1208
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800187 tristate "Intersil ISL1208"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700188 help
189 If you say yes here you get support for the
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800190 Intersil ISL1208 RTC chip.
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700191
192 This driver can also be built as a module. If so, the module
193 will be called rtc-isl1208.
194
195config RTC_DRV_X1205
196 tristate "Xicor/Intersil X1205"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700197 help
198 If you say yes here you get support for the
199 Xicor/Intersil X1205 RTC chip.
200
201 This driver can also be built as a module. If so, the module
202 will be called rtc-x1205.
203
204config RTC_DRV_PCF8563
205 tristate "Philips PCF8563/Epson RTC8564"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700206 help
207 If you say yes here you get support for the
208 Philips PCF8563 RTC chip. The Epson RTC8564
209 should work as well.
210
211 This driver can also be built as a module. If so, the module
212 will be called rtc-pcf8563.
213
214config RTC_DRV_PCF8583
215 tristate "Philips PCF8583"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700216 help
217 If you say yes here you get support for the Philips PCF8583
218 RTC chip found on Acorn RiscPCs. This driver supports the
219 platform specific method of retrieving the current year from
220 the RTC's SRAM. It will work on other platforms with the same
221 chip, but the year will probably have to be tweaked.
222
223 This driver can also be built as a module. If so, the module
224 will be called rtc-pcf8583.
225
Atsushi Nemotocaaff562007-07-17 04:05:02 -0700226config RTC_DRV_M41T80
Steven A. Falcod3a126f2008-10-15 22:03:07 -0700227 tristate "ST M41T65/M41T80/81/82/83/84/85/87"
Atsushi Nemotocaaff562007-07-17 04:05:02 -0700228 help
Steven A. Falcod3a126f2008-10-15 22:03:07 -0700229 If you say Y here you will get support for the ST M41T60
230 and M41T80 RTC chips series. Currently, the following chips are
231 supported: M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
232 M41ST85, and M41ST87.
Atsushi Nemotocaaff562007-07-17 04:05:02 -0700233
234 This driver can also be built as a module. If so, the module
235 will be called rtc-m41t80.
236
Atsushi Nemoto617780d2007-07-17 04:05:04 -0700237config RTC_DRV_M41T80_WDT
Steven A. Falcod3a126f2008-10-15 22:03:07 -0700238 bool "ST M41T65/M41T80 series RTC watchdog timer"
Atsushi Nemoto617780d2007-07-17 04:05:04 -0700239 depends on RTC_DRV_M41T80
240 help
241 If you say Y here you will get support for the
Steven A. Falcod3a126f2008-10-15 22:03:07 -0700242 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
Atsushi Nemoto617780d2007-07-17 04:05:04 -0700243
Tony Lindgren0c4a59f2007-07-17 04:06:09 -0700244config RTC_DRV_TWL92330
245 boolean "TI TWL92330/Menelaus"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700246 depends on MENELAUS
Tony Lindgren0c4a59f2007-07-17 04:06:09 -0700247 help
248 If you say yes here you get support for the RTC on the
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200249 TWL92330 "Menelaus" power management chip, used with OMAP2
Alessandro Zummoae64d162009-01-06 14:42:17 -0800250 platforms. The support is integrated with the rest of
Tony Lindgren0c4a59f2007-07-17 04:06:09 -0700251 the Menelaus driver; it's not separate module.
252
David Brownellf96411a2008-10-20 23:50:05 +0200253config RTC_DRV_TWL4030
254 tristate "TI TWL4030/TWL5030/TPS659x0"
255 depends on RTC_CLASS && TWL4030_CORE
256 help
257 If you say yes here you get support for the RTC on the
258 TWL4030 family chips, used mostly with OMAP3 platforms.
259
260 This driver can also be built as a module. If so, the module
261 will be called rtc-twl4030.
262
Byron Bradleyc46288b2008-03-04 14:28:25 -0800263config RTC_DRV_S35390A
264 tristate "Seiko Instruments S-35390A"
Randy Dunlapd4795402008-04-10 21:29:18 -0700265 select BITREVERSE
Byron Bradleyc46288b2008-03-04 14:28:25 -0800266 help
267 If you say yes here you will get support for the Seiko
268 Instruments S-35390A.
269
270 This driver can also be built as a module. If so the module
271 will be called rtc-s35390a.
272
Sergey Lapinc6d8f402008-06-12 15:21:55 -0700273config RTC_DRV_FM3130
274 tristate "Ramtron FM3130"
275 help
276 If you say Y here you will get support for the
277 Ramtron FM3130 RTC chips.
278 Ramtron FM3130 is a chip with two separate devices inside,
279 RTC clock and FRAM. This driver provides only RTC functionality.
280
281 This driver can also be built as a module. If so the module
282 will be called rtc-fm3130.
283
Martyn Welcha7fa9852008-11-12 13:27:06 -0800284config RTC_DRV_RX8581
285 tristate "Epson RX-8581"
286 help
287 If you say yes here you will get support for the Epson RX-8581.
288
289 This driver can also be built as a module. If so the module
290 will be called rtc-rx8581.
291
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700292endif # I2C
293
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700294comment "SPI RTC drivers"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700295
296if SPI_MASTER
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700297
Kim B. Heino8fc2c762008-07-23 21:30:34 -0700298config RTC_DRV_M41T94
299 tristate "ST M41T94"
300 help
301 If you say yes here you will get support for the
302 ST M41T94 SPI RTC chip.
303
304 This driver can also be built as a module. If so, the module
305 will be called rtc-m41t94.
306
David Brownell53e84b62008-07-23 21:30:36 -0700307config RTC_DRV_DS1305
308 tristate "Dallas/Maxim DS1305/DS1306"
309 help
310 Select this driver to get support for the Dallas/Maxim DS1305
Alessandro Zummoae64d162009-01-06 14:42:17 -0800311 and DS1306 real time clock chips. These support a trickle
David Brownell53e84b62008-07-23 21:30:36 -0700312 charger, alarms, and NVRAM in addition to the clock.
313
314 This driver can also be built as a module. If so, the module
315 will be called rtc-ds1305.
316
Mark Jackson06de1802008-11-12 13:27:07 -0800317config RTC_DRV_DS1390
318 tristate "Dallas/Maxim DS1390/93/94"
319 help
Alessandro Zummo7b9b2ef2009-01-06 14:42:16 -0800320 If you say yes here you get support for the
321 Dallas/Maxim DS1390/93/94 chips.
Mark Jackson06de1802008-11-12 13:27:07 -0800322
323 This driver only supports the RTC feature, and not other chip
324 features such as alarms and trickle charging.
325
326 This driver can also be built as a module. If so, the module
327 will be called rtc-ds1390.
328
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800329config RTC_DRV_MAX6902
330 tristate "Maxim MAX6902"
331 help
332 If you say yes here you will get support for the
333 Maxim MAX6902 SPI RTC chip.
334
335 This driver can also be built as a module. If so, the module
336 will be called rtc-max6902.
337
Magnus Damm2805b962008-02-06 01:38:53 -0800338config RTC_DRV_R9701
339 tristate "Epson RTC-9701JE"
340 help
341 If you say yes here you will get support for the
342 Epson RTC-9701JE SPI RTC chip.
343
344 This driver can also be built as a module. If so, the module
345 will be called rtc-r9701.
346
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700347config RTC_DRV_RS5C348
348 tristate "Ricoh RS5C348A/B"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700349 help
350 If you say yes here you get support for the
351 Ricoh RS5C348A and RS5C348B RTC chips.
352
353 This driver can also be built as a module. If so, the module
354 will be called rtc-rs5c348.
355
Dennis Aberilla2f9b75e2008-10-15 22:02:57 -0700356config RTC_DRV_DS3234
357 tristate "Maxim/Dallas DS3234"
358 help
359 If you say yes here you get support for the
360 Maxim/Dallas DS3234 SPI RTC chip.
361
362 This driver can also be built as a module. If so, the module
363 will be called rtc-ds3234.
364
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700365endif # SPI_MASTER
366
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700367comment "Platform RTC drivers"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -0800368
David Brownell7be2c7c2007-02-10 01:46:02 -0800369# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
370# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
371# global rtc_lock ... it's not yet just another platform_device.
372
373config RTC_DRV_CMOS
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700374 tristate "PC-style 'CMOS'"
Andrew Morton5ec87702008-09-22 21:40:04 -0700375 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
David Brownellc7500902008-04-28 02:11:52 -0700376 default y if X86
David Brownell7be2c7c2007-02-10 01:46:02 -0800377 help
378 Say "yes" here to get direct support for the real time clock
379 found in every PC or ACPI-based system, and some other boards.
380 Specifically the original MC146818, compatibles like those in
381 PC south bridges, the DS12887 or M48T86, some multifunction
382 or LPC bus chips, and so on.
383
384 Your system will need to define the platform device used by
Alessandro Zummoae64d162009-01-06 14:42:17 -0800385 this driver, otherwise it won't be accessible. This means
David Brownell7be2c7c2007-02-10 01:46:02 -0800386 you can safely enable this driver if you don't know whether
387 or not your board has this kind of hardware.
388
389 This driver can also be built as a module. If so, the module
390 will be called rtc-cmos.
391
Thomas Bogendoerfer537739d2007-07-17 04:05:06 -0700392config RTC_DRV_DS1216
393 tristate "Dallas DS1216"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700394 depends on SNI_RM
Thomas Bogendoerfer537739d2007-07-17 04:05:06 -0700395 help
396 If you say yes here you get support for the Dallas DS1216 RTC chips.
397
Thomas Bogendoerfer5f119f22008-10-14 17:16:59 +0200398config RTC_DRV_DS1286
399 tristate "Dallas DS1286"
400 help
401 If you say yes here you get support for the Dallas DS1286 RTC chips.
402
Paul Mundt739d3402008-02-06 01:38:44 -0800403config RTC_DRV_DS1302
404 tristate "Dallas DS1302"
405 depends on SH_SECUREEDGE5410
406 help
407 If you say yes here you get support for the Dallas DS1302 RTC chips.
408
Andrew Sharp8f267952008-02-06 01:38:46 -0800409config RTC_DRV_DS1511
410 tristate "Dallas DS1511"
411 depends on RTC_CLASS
412 help
413 If you say yes here you get support for the
414 Dallas DS1511 timekeeping/watchdog chip.
415
416 This driver can also be built as a module. If so, the module
417 will be called rtc-ds1511.
418
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700419config RTC_DRV_DS1553
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800420 tristate "Maxim/Dallas DS1553"
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700421 help
422 If you say yes here you get support for the
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800423 Maxim/Dallas DS1553 timekeeping chip.
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700424
425 This driver can also be built as a module. If so, the module
426 will be called rtc-ds1553.
427
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800428config RTC_DRV_DS1742
429 tristate "Maxim/Dallas DS1742/1743"
430 help
431 If you say yes here you get support for the
432 Maxim/Dallas DS1742/1743 timekeeping chip.
433
434 This driver can also be built as a module. If so, the module
435 will be called rtc-ds1742.
436
Thomas Hommel02964112007-07-21 04:37:58 -0700437config RTC_DRV_STK17TA8
438 tristate "Simtek STK17TA8"
439 depends on RTC_CLASS
440 help
441 If you say yes here you get support for the
442 Simtek STK17TA8 timekeeping chip.
443
444 This driver can also be built as a module. If so, the module
445 will be called rtc-stk17ta8.
446
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700447config RTC_DRV_M48T86
448 tristate "ST M48T86/Dallas DS12887"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700449 help
450 If you say Y here you will get support for the
451 ST M48T86 and Dallas DS12887 RTC chips.
452
453 This driver can also be built as a module. If so, the module
454 will be called rtc-m48t86.
455
Thomas Bogendoerferd1dbd822008-10-14 17:17:32 +0200456config RTC_DRV_M48T35
457 tristate "ST M48T35"
458 help
459 If you say Y here you will get support for the
460 ST M48T35 RTC chip.
461
462 This driver can also be built as a module, if so, the module
463 will be called "rtc-m48t35".
464
Mark Zhan2e774c72007-07-17 04:05:05 -0700465config RTC_DRV_M48T59
Krzysztof Helt94fe7422008-09-03 15:12:34 -0700466 tristate "ST M48T59/M48T08/M48T02"
Mark Zhan2e774c72007-07-17 04:05:05 -0700467 help
468 If you say Y here you will get support for the
Krzysztof Helt94fe7422008-09-03 15:12:34 -0700469 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
470
471 These chips are usually found in Sun SPARC and UltraSPARC
472 workstations.
Mark Zhan2e774c72007-07-17 04:05:05 -0700473
474 This driver can also be built as a module, if so, the module
475 will be called "rtc-m48t59".
476
David S. Millercca4c232008-08-29 01:29:53 -0700477config RTC_DRV_BQ4802
478 tristate "TI BQ4802"
479 help
480 If you say Y here you will get support for the TI
481 BQ4802 RTC chip.
482
483 This driver can also be built as a module. If so, the module
484 will be called rtc-bq4802.
485
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700486config RTC_DRV_V3020
487 tristate "EM Microelectronic V3020"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700488 help
489 If you say yes here you will get support for the
490 EM Microelectronic v3020 RTC chip.
491
492 This driver can also be built as a module. If so, the module
493 will be called rtc-v3020.
494
Mark Brown077eaf52008-11-12 13:27:04 -0800495config RTC_DRV_WM8350
496 tristate "Wolfson Microelectronics WM8350 RTC"
497 depends on MFD_WM8350
498 help
499 If you say yes here you will get support for the RTC subsystem
500 of the Wolfson Microelectronics WM8350.
501
502 This driver can also be built as a module. If so, the module
503 will be called "rtc-wm8350".
504
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700505comment "on-CPU RTC drivers"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700506
David Brownelldb68b182006-12-06 20:38:36 -0800507config RTC_DRV_OMAP
508 tristate "TI OMAP1"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700509 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730
David Brownelldb68b182006-12-06 20:38:36 -0800510 help
511 Say "yes" here to support the real time clock on TI OMAP1 chips.
512 This driver can also be built as a module called rtc-omap.
513
Ben Dooks1add6782006-07-01 04:36:26 -0700514config RTC_DRV_S3C
515 tristate "Samsung S3C series SoC RTC"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700516 depends on ARCH_S3C2410
Ben Dooks1add6782006-07-01 04:36:26 -0700517 help
518 RTC (Realtime Clock) driver for the clock inbuilt into the
519 Samsung S3C24XX series of SoCs. This can provide periodic
520 interrupt rates from 1Hz to 64Hz for user programs, and
521 wakeup from Alarm.
522
523 The driver currently supports the common features on all the
524 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
525 and S3C2442.
526
527 This driver can also be build as a module. If so, the module
528 will be called rtc-s3c.
529
Alessandro Zummofd507e22006-03-27 01:16:45 -0800530config RTC_DRV_EP93XX
531 tristate "Cirrus Logic EP93XX"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700532 depends on ARCH_EP93XX
Alessandro Zummofd507e22006-03-27 01:16:45 -0800533 help
534 If you say yes here you get support for the
535 RTC embedded in the Cirrus Logic EP93XX processors.
536
537 This driver can also be built as a module. If so, the module
538 will be called rtc-ep93xx.
539
Richard Purdiee842f1c2006-03-27 01:16:46 -0800540config RTC_DRV_SA1100
541 tristate "SA11x0/PXA2xx"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700542 depends on ARCH_SA1100 || ARCH_PXA
Richard Purdiee842f1c2006-03-27 01:16:46 -0800543 help
544 If you say Y here you will get access to the real time clock
545 built into your SA11x0 or PXA2xx CPU.
546
547 To compile this driver as a module, choose M here: the
548 module will be called rtc-sa1100.
Alessandro Zummofd507e22006-03-27 01:16:45 -0800549
Paul Mundt317a6102006-09-27 17:13:19 +0900550config RTC_DRV_SH
551 tristate "SuperH On-Chip RTC"
Paul Mundtff1b7502007-11-26 17:56:31 +0900552 depends on RTC_CLASS && SUPERH
Paul Mundt317a6102006-09-27 17:13:19 +0900553 help
554 Say Y here to enable support for the on-chip RTC found in
555 most SuperH processors.
556
557 To compile this driver as a module, choose M here: the
558 module will be called rtc-sh.
559
Yoichi Yuasa8417eb72006-04-10 22:54:47 -0700560config RTC_DRV_VR41XX
Alessandro Zummo3e16f6a2006-04-10 22:54:48 -0700561 tristate "NEC VR41XX"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700562 depends on CPU_VR41XX
Alessandro Zummo3e16f6a2006-04-10 22:54:48 -0700563 help
564 If you say Y here you will get access to the real time clock
565 built into your NEC VR41XX CPU.
566
567 To compile this driver as a module, choose M here: the
568 module will be called rtc-vr41xx.
Yoichi Yuasa8417eb72006-04-10 22:54:47 -0700569
Russell Kinga1909012008-04-20 12:08:36 +0100570config RTC_DRV_PL030
571 tristate "ARM AMBA PL030 RTC"
572 depends on ARM_AMBA
573 help
574 If you say Y here you will get access to ARM AMBA
575 PrimeCell PL030 RTC found on certain ARM SOCs.
576
577 To compile this driver as a module, choose M here: the
578 module will be called rtc-pl030.
579
Deepak Saxena8ae6e162006-06-25 05:47:38 -0700580config RTC_DRV_PL031
581 tristate "ARM AMBA PL031 RTC"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700582 depends on ARM_AMBA
Deepak Saxena8ae6e162006-06-25 05:47:38 -0700583 help
584 If you say Y here you will get access to ARM AMBA
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700585 PrimeCell PL031 RTC found on certain ARM SOCs.
Deepak Saxena8ae6e162006-06-25 05:47:38 -0700586
587 To compile this driver as a module, choose M here: the
588 module will be called rtc-pl031.
589
Hans-Christian Egtvedtfa04e782007-07-17 04:05:00 -0700590config RTC_DRV_AT32AP700X
591 tristate "AT32AP700X series RTC"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700592 depends on PLATFORM_AT32AP
Hans-Christian Egtvedtfa04e782007-07-17 04:05:00 -0700593 help
594 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
595 AT32AP700x family processors.
596
Andrew Victor7fc39f62006-12-10 02:19:03 -0800597config RTC_DRV_AT91RM9200
David Brownell4cdf8542008-02-06 01:38:59 -0800598 tristate "AT91RM9200 or AT91SAM9RL"
599 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
Andrew Victor788b1fc2006-06-25 05:48:27 -0700600 help
David Brownell4cdf8542008-02-06 01:38:59 -0800601 Driver for the internal RTC (Realtime Clock) module found on
Alessandro Zummoae64d162009-01-06 14:42:17 -0800602 Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips
David Brownell4cdf8542008-02-06 01:38:59 -0800603 this is powered by the backup power supply.
604
605config RTC_DRV_AT91SAM9
Stelian Pop6b71dbf2008-04-05 21:16:15 +0100606 tristate "AT91SAM9x/AT91CAP9"
David Brownell4cdf8542008-02-06 01:38:59 -0800607 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
608 help
Stelian Pop6b71dbf2008-04-05 21:16:15 +0100609 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
610 (Real Time Timer). These timers are powered by the backup power
611 supply (such as a small coin cell battery), but do not need to
612 be used as RTCs.
David Brownell4cdf8542008-02-06 01:38:59 -0800613
614 (On AT91SAM9rl chips you probably want to use the dedicated RTC
615 module and leave the RTT available for other uses.)
616
617config RTC_DRV_AT91SAM9_RTT
618 int
619 range 0 1
620 default 0
621 prompt "RTT module Number" if ARCH_AT91SAM9263
622 depends on RTC_DRV_AT91SAM9
623 help
Alessandro Zummoae64d162009-01-06 14:42:17 -0800624 More than one RTT module is available. You can choose which
625 one will be used as an RTC. The default of zero is normally
David Brownell4cdf8542008-02-06 01:38:59 -0800626 OK to use, though some systems use that for non-RTC purposes.
627
628config RTC_DRV_AT91SAM9_GPBR
629 int
630 range 0 3 if !ARCH_AT91SAM9263
631 range 0 15 if ARCH_AT91SAM9263
632 default 0
633 prompt "Backup Register Number"
634 depends on RTC_DRV_AT91SAM9
635 help
636 The RTC driver needs to use one of the General Purpose Backup
Alessandro Zummoae64d162009-01-06 14:42:17 -0800637 Registers (GPBRs) as well as the RTT. You can choose which one
638 will be used. The default of zero is normally OK to use, but
David Brownell4cdf8542008-02-06 01:38:59 -0800639 on some systems other software needs to use that register.
Andrew Victor788b1fc2006-06-25 05:48:27 -0700640
Manuel Lauss45fd8a02009-01-06 14:42:18 -0800641config RTC_DRV_AU1XXX
642 tristate "Au1xxx Counter0 RTC support"
643 depends on SOC_AU1X00
644 help
645 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
646 counter) to be used as a RTC.
647
648 This driver can also be built as a module. If so, the module
649 will be called rtc-au1xxx.
650
Wu, Bryan8cc75c92007-05-06 14:50:32 -0700651config RTC_DRV_BFIN
652 tristate "Blackfin On-Chip RTC"
Graf Yang7f604592008-08-20 14:09:02 -0700653 depends on BLACKFIN && !BF561
Wu, Bryan8cc75c92007-05-06 14:50:32 -0700654 help
655 If you say yes here you will get support for the
656 Blackfin On-Chip Real Time Clock.
657
658 This driver can also be built as a module. If so, the module
659 will be called rtc-bfin.
660
Nobuhiro Iwamatsue9f2bd82007-05-08 00:26:37 -0700661config RTC_DRV_RS5C313
662 tristate "Ricoh RS5C313"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700663 depends on SH_LANDISK
Nobuhiro Iwamatsue9f2bd82007-05-08 00:26:37 -0700664 help
665 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
666
Kyle McMartin9eb16862008-09-10 14:24:07 +0000667config RTC_DRV_PARISC
668 tristate "PA-RISC firmware RTC support"
669 depends on PARISC
670 help
671 Say Y or M here to enable RTC support on PA-RISC systems using
672 firmware calls. If you do not know what you are doing, you should
673 just say Y.
674
David Woodhouseaabe1882008-06-05 22:46:50 -0700675config RTC_DRV_PPC
676 tristate "PowerPC machine dependent RTC support"
Kumar Gala03274572008-10-15 22:03:06 -0700677 depends on PPC
David Woodhouseaabe1882008-06-05 22:46:50 -0700678 help
679 The PowerPC kernel has machine-specific functions for accessing
680 the RTC. This exposes that functionality through the generic RTC
681 class.
682
Robert Jarzmikdc944362009-01-06 14:42:14 -0800683config RTC_DRV_PXA
684 tristate "PXA27x/PXA3xx"
685 depends on ARCH_PXA
686 help
687 If you say Y here you will get access to the real time clock
688 built into your PXA27x or PXA3xx CPU.
689
690 This RTC driver uses PXA RTC registers available since pxa27x
691 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
692
693
David S. Miller7a138ed2008-08-29 01:32:43 -0700694config RTC_DRV_SUN4V
695 bool "SUN4V Hypervisor RTC"
696 depends on SPARC64
697 help
698 If you say Y here you will get support for the Hypervisor
699 based RTC on SUN4V systems.
700
David S. Millerde2cf332008-08-28 23:02:36 -0700701config RTC_DRV_STARFIRE
702 bool "Starfire RTC"
703 depends on SPARC64
704 help
705 If you say Y here you will get support for the RTC found on
706 Starfire systems.
707
Atsushi Nemoto0e149232009-01-06 14:42:22 -0800708config RTC_DRV_TX4939
709 tristate "TX4939 SoC"
710 depends on SOC_TX4939
711 help
712 Driver for the internal RTC (Realtime Clock) module found on
713 Toshiba TX4939 SoC.
714
Saeed Bisharadefb4512009-01-06 14:42:24 -0800715config RTC_DRV_MV
716 tristate "Marvell SoC RTC"
717 depends on ARCH_KIRKWOOD
718 help
719 If you say yes here you will get support for the in-chip RTC
720 that can be found in some of Marvell's SoC devices, such as
721 the Kirkwood 88F6281 and 88F6192.
722
723 This driver can also be built as a module. If so, the module
724 will be called rtc-mv.
725
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700726endif # RTC_CLASS