blob: 18c5be168a5a30dd7630b31296e4f085c20275f4 [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
Matthias Fuchsa2166852009-03-31 15:24:58 -0700132 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
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,
Matthias Fuchsa2166852009-03-31 15:24:58 -0700137 EPSON RX-8025 and probably other chips. In some cases the RTC
138 must already have been initialized (by manufacturing or a
139 bootloader).
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700140
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
Alessandro Zummoae64d162009-01-06 14:42:17 -0800143 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
David Brownell682d73f2007-11-14 16:58:32 -0800144 sysfs, but other chip features may not be available.
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700145
146 This driver can also be built as a module. If so, the module
147 will be called rtc-ds1307.
148
Scott Woodbf4994d2007-10-16 01:28:19 -0700149config RTC_DRV_DS1374
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800150 tristate "Dallas/Maxim DS1374"
Scott Woodbf4994d2007-10-16 01:28:19 -0700151 depends on RTC_CLASS && I2C
152 help
153 If you say yes here you get support for Dallas Semiconductor
Alessandro Zummoae64d162009-01-06 14:42:17 -0800154 DS1374 real-time clock chips. If an interrupt is associated
Scott Woodbf4994d2007-10-16 01:28:19 -0700155 with the device, the alarm functionality is supported.
156
Alessandro Zummoae64d162009-01-06 14:42:17 -0800157 This driver can also be built as a module. If so, the module
Scott Woodbf4994d2007-10-16 01:28:19 -0700158 will be called rtc-ds1374.
159
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700160config RTC_DRV_DS1672
161 tristate "Dallas/Maxim DS1672"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700162 help
163 If you say yes here you get support for the
164 Dallas/Maxim DS1672 timekeeping chip.
165
166 This driver can also be built as a module. If so, the module
167 will be called rtc-ds1672.
168
169config RTC_DRV_MAX6900
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800170 tristate "Maxim MAX6900"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700171 help
172 If you say yes here you will get support for the
173 Maxim MAX6900 I2C RTC chip.
174
175 This driver can also be built as a module. If so, the module
176 will be called rtc-max6900.
177
178config RTC_DRV_RS5C372
Paul Mundt5d4529b2008-10-21 20:12:59 +0900179 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700180 help
181 If you say yes here you get support for the
Paul Mundt5d4529b2008-10-21 20:12:59 +0900182 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700183
184 This driver can also be built as a module. If so, the module
185 will be called rtc-rs5c372.
186
187config RTC_DRV_ISL1208
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800188 tristate "Intersil ISL1208"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700189 help
190 If you say yes here you get support for the
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800191 Intersil ISL1208 RTC chip.
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700192
193 This driver can also be built as a module. If so, the module
194 will be called rtc-isl1208.
195
196config RTC_DRV_X1205
197 tristate "Xicor/Intersil X1205"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700198 help
199 If you say yes here you get support for the
200 Xicor/Intersil X1205 RTC chip.
201
202 This driver can also be built as a module. If so, the module
203 will be called rtc-x1205.
204
205config RTC_DRV_PCF8563
206 tristate "Philips PCF8563/Epson RTC8564"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700207 help
208 If you say yes here you get support for the
209 Philips PCF8563 RTC chip. The Epson RTC8564
210 should work as well.
211
212 This driver can also be built as a module. If so, the module
213 will be called rtc-pcf8563.
214
215config RTC_DRV_PCF8583
216 tristate "Philips PCF8583"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700217 help
218 If you say yes here you get support for the Philips PCF8583
219 RTC chip found on Acorn RiscPCs. This driver supports the
220 platform specific method of retrieving the current year from
221 the RTC's SRAM. It will work on other platforms with the same
222 chip, but the year will probably have to be tweaked.
223
224 This driver can also be built as a module. If so, the module
225 will be called rtc-pcf8583.
226
Atsushi Nemotocaaff562007-07-17 04:05:02 -0700227config RTC_DRV_M41T80
Daniel Glocknerf30281f2009-04-02 16:57:03 -0700228 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
Atsushi Nemotocaaff562007-07-17 04:05:02 -0700229 help
Steven A. Falcod3a126f2008-10-15 22:03:07 -0700230 If you say Y here you will get support for the ST M41T60
231 and M41T80 RTC chips series. Currently, the following chips are
Daniel Glocknerf30281f2009-04-02 16:57:03 -0700232 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
Steven A. Falcod3a126f2008-10-15 22:03:07 -0700233 M41ST85, and M41ST87.
Atsushi Nemotocaaff562007-07-17 04:05:02 -0700234
235 This driver can also be built as a module. If so, the module
236 will be called rtc-m41t80.
237
Atsushi Nemoto617780d2007-07-17 04:05:04 -0700238config RTC_DRV_M41T80_WDT
Steven A. Falcod3a126f2008-10-15 22:03:07 -0700239 bool "ST M41T65/M41T80 series RTC watchdog timer"
Atsushi Nemoto617780d2007-07-17 04:05:04 -0700240 depends on RTC_DRV_M41T80
241 help
242 If you say Y here you will get support for the
Steven A. Falcod3a126f2008-10-15 22:03:07 -0700243 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
Atsushi Nemoto617780d2007-07-17 04:05:04 -0700244
David Brownellafd8d0f2009-02-04 15:12:01 -0800245config RTC_DRV_DM355EVM
246 tristate "TI DaVinci DM355 EVM RTC"
247 depends on MFD_DM355EVM_MSP
248 help
249 Supports the RTC firmware in the MSP430 on the DM355 EVM.
250
Tony Lindgren0c4a59f2007-07-17 04:06:09 -0700251config RTC_DRV_TWL92330
252 boolean "TI TWL92330/Menelaus"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700253 depends on MENELAUS
Tony Lindgren0c4a59f2007-07-17 04:06:09 -0700254 help
255 If you say yes here you get support for the RTC on the
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200256 TWL92330 "Menelaus" power management chip, used with OMAP2
Alessandro Zummoae64d162009-01-06 14:42:17 -0800257 platforms. The support is integrated with the rest of
Tony Lindgren0c4a59f2007-07-17 04:06:09 -0700258 the Menelaus driver; it's not separate module.
259
David Brownellf96411a2008-10-20 23:50:05 +0200260config RTC_DRV_TWL4030
261 tristate "TI TWL4030/TWL5030/TPS659x0"
262 depends on RTC_CLASS && TWL4030_CORE
263 help
264 If you say yes here you get support for the RTC on the
265 TWL4030 family chips, used mostly with OMAP3 platforms.
266
267 This driver can also be built as a module. If so, the module
268 will be called rtc-twl4030.
269
Byron Bradleyc46288b2008-03-04 14:28:25 -0800270config RTC_DRV_S35390A
271 tristate "Seiko Instruments S-35390A"
Randy Dunlapd4795402008-04-10 21:29:18 -0700272 select BITREVERSE
Byron Bradleyc46288b2008-03-04 14:28:25 -0800273 help
274 If you say yes here you will get support for the Seiko
275 Instruments S-35390A.
276
277 This driver can also be built as a module. If so the module
278 will be called rtc-s35390a.
279
Sergey Lapinc6d8f402008-06-12 15:21:55 -0700280config RTC_DRV_FM3130
281 tristate "Ramtron FM3130"
282 help
283 If you say Y here you will get support for the
284 Ramtron FM3130 RTC chips.
285 Ramtron FM3130 is a chip with two separate devices inside,
286 RTC clock and FRAM. This driver provides only RTC functionality.
287
288 This driver can also be built as a module. If so the module
289 will be called rtc-fm3130.
290
Martyn Welcha7fa9852008-11-12 13:27:06 -0800291config RTC_DRV_RX8581
292 tristate "Epson RX-8581"
293 help
294 If you say yes here you will get support for the Epson RX-8581.
295
296 This driver can also be built as a module. If so the module
297 will be called rtc-rx8581.
298
Wolfgang Grandegger3c2b9072009-06-17 16:26:11 -0700299config RTC_DRV_RX8025
300 tristate "Epson RX-8025SA/NB"
301 help
302 If you say yes here you get support for the Epson
303 RX-8025SA/NB RTC chips.
304
305 This driver can also be built as a module. If so, the module
306 will be called rtc-rx8025.
307
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700308endif # I2C
309
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700310comment "SPI RTC drivers"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700311
312if SPI_MASTER
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700313
Kim B. Heino8fc2c762008-07-23 21:30:34 -0700314config RTC_DRV_M41T94
315 tristate "ST M41T94"
316 help
317 If you say yes here you will get support for the
318 ST M41T94 SPI RTC chip.
319
320 This driver can also be built as a module. If so, the module
321 will be called rtc-m41t94.
322
David Brownell53e84b62008-07-23 21:30:36 -0700323config RTC_DRV_DS1305
324 tristate "Dallas/Maxim DS1305/DS1306"
325 help
326 Select this driver to get support for the Dallas/Maxim DS1305
Alessandro Zummoae64d162009-01-06 14:42:17 -0800327 and DS1306 real time clock chips. These support a trickle
David Brownell53e84b62008-07-23 21:30:36 -0700328 charger, alarms, and NVRAM in addition to the clock.
329
330 This driver can also be built as a module. If so, the module
331 will be called rtc-ds1305.
332
Mark Jackson06de1802008-11-12 13:27:07 -0800333config RTC_DRV_DS1390
334 tristate "Dallas/Maxim DS1390/93/94"
335 help
Alessandro Zummo7b9b2ef2009-01-06 14:42:16 -0800336 If you say yes here you get support for the
337 Dallas/Maxim DS1390/93/94 chips.
Mark Jackson06de1802008-11-12 13:27:07 -0800338
339 This driver only supports the RTC feature, and not other chip
340 features such as alarms and trickle charging.
341
342 This driver can also be built as a module. If so, the module
343 will be called rtc-ds1390.
344
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800345config RTC_DRV_MAX6902
346 tristate "Maxim MAX6902"
347 help
348 If you say yes here you will get support for the
349 Maxim MAX6902 SPI RTC chip.
350
351 This driver can also be built as a module. If so, the module
352 will be called rtc-max6902.
353
Magnus Damm2805b962008-02-06 01:38:53 -0800354config RTC_DRV_R9701
355 tristate "Epson RTC-9701JE"
356 help
357 If you say yes here you will get support for the
358 Epson RTC-9701JE SPI RTC chip.
359
360 This driver can also be built as a module. If so, the module
361 will be called rtc-r9701.
362
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700363config RTC_DRV_RS5C348
364 tristate "Ricoh RS5C348A/B"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700365 help
366 If you say yes here you get support for the
367 Ricoh RS5C348A and RS5C348B RTC chips.
368
369 This driver can also be built as a module. If so, the module
370 will be called rtc-rs5c348.
371
Dennis Aberilla2f9b75e2008-10-15 22:02:57 -0700372config RTC_DRV_DS3234
373 tristate "Maxim/Dallas DS3234"
374 help
375 If you say yes here you get support for the
376 Maxim/Dallas DS3234 SPI RTC chip.
377
378 This driver can also be built as a module. If so, the module
379 will be called rtc-ds3234.
380
Chris Verges7f3923a2009-09-22 16:46:20 -0700381config RTC_DRV_PCF2123
382 tristate "NXP PCF2123"
383 help
384 If you say yes here you get support for the NXP PCF2123
385 RTC chip.
386
387 This driver can also be built as a module. If so, the module
388 will be called rtc-pcf2123.
389
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700390endif # SPI_MASTER
391
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700392comment "Platform RTC drivers"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -0800393
David Brownell7be2c7c2007-02-10 01:46:02 -0800394# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
395# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
396# global rtc_lock ... it's not yet just another platform_device.
397
398config RTC_DRV_CMOS
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700399 tristate "PC-style 'CMOS'"
Andrew Morton5ec87702008-09-22 21:40:04 -0700400 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
David Brownellc7500902008-04-28 02:11:52 -0700401 default y if X86
David Brownell7be2c7c2007-02-10 01:46:02 -0800402 help
403 Say "yes" here to get direct support for the real time clock
404 found in every PC or ACPI-based system, and some other boards.
405 Specifically the original MC146818, compatibles like those in
406 PC south bridges, the DS12887 or M48T86, some multifunction
407 or LPC bus chips, and so on.
408
409 Your system will need to define the platform device used by
Alessandro Zummoae64d162009-01-06 14:42:17 -0800410 this driver, otherwise it won't be accessible. This means
David Brownell7be2c7c2007-02-10 01:46:02 -0800411 you can safely enable this driver if you don't know whether
412 or not your board has this kind of hardware.
413
414 This driver can also be built as a module. If so, the module
415 will be called rtc-cmos.
416
Thomas Bogendoerfer537739d2007-07-17 04:05:06 -0700417config RTC_DRV_DS1216
418 tristate "Dallas DS1216"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700419 depends on SNI_RM
Thomas Bogendoerfer537739d2007-07-17 04:05:06 -0700420 help
421 If you say yes here you get support for the Dallas DS1216 RTC chips.
422
Thomas Bogendoerfer5f119f22008-10-14 17:16:59 +0200423config RTC_DRV_DS1286
424 tristate "Dallas DS1286"
425 help
426 If you say yes here you get support for the Dallas DS1286 RTC chips.
427
Paul Mundt739d3402008-02-06 01:38:44 -0800428config RTC_DRV_DS1302
429 tristate "Dallas DS1302"
430 depends on SH_SECUREEDGE5410
431 help
432 If you say yes here you get support for the Dallas DS1302 RTC chips.
433
Andrew Sharp8f267952008-02-06 01:38:46 -0800434config RTC_DRV_DS1511
435 tristate "Dallas DS1511"
436 depends on RTC_CLASS
437 help
438 If you say yes here you get support for the
439 Dallas DS1511 timekeeping/watchdog chip.
440
441 This driver can also be built as a module. If so, the module
442 will be called rtc-ds1511.
443
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700444config RTC_DRV_DS1553
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800445 tristate "Maxim/Dallas DS1553"
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700446 help
447 If you say yes here you get support for the
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800448 Maxim/Dallas DS1553 timekeeping chip.
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700449
450 This driver can also be built as a module. If so, the module
451 will be called rtc-ds1553.
452
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800453config RTC_DRV_DS1742
454 tristate "Maxim/Dallas DS1742/1743"
455 help
456 If you say yes here you get support for the
457 Maxim/Dallas DS1742/1743 timekeeping chip.
458
459 This driver can also be built as a module. If so, the module
460 will be called rtc-ds1742.
461
dann frazier5e3fd9e2009-03-31 15:24:48 -0700462config RTC_DRV_EFI
463 tristate "EFI RTC"
464 depends on IA64
465 help
466 If you say yes here you will get support for the EFI
467 Real Time Clock.
468
469 This driver can also be built as a module. If so, the module
470 will be called rtc-efi.
471
Thomas Hommel02964112007-07-21 04:37:58 -0700472config RTC_DRV_STK17TA8
473 tristate "Simtek STK17TA8"
474 depends on RTC_CLASS
475 help
476 If you say yes here you get support for the
477 Simtek STK17TA8 timekeeping chip.
478
479 This driver can also be built as a module. If so, the module
480 will be called rtc-stk17ta8.
481
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700482config RTC_DRV_M48T86
483 tristate "ST M48T86/Dallas DS12887"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700484 help
485 If you say Y here you will get support for the
486 ST M48T86 and Dallas DS12887 RTC chips.
487
488 This driver can also be built as a module. If so, the module
489 will be called rtc-m48t86.
490
Thomas Bogendoerferd1dbd82e2008-10-14 17:17:32 +0200491config RTC_DRV_M48T35
492 tristate "ST M48T35"
493 help
494 If you say Y here you will get support for the
495 ST M48T35 RTC chip.
496
497 This driver can also be built as a module, if so, the module
498 will be called "rtc-m48t35".
499
Mark Zhan2e774c72007-07-17 04:05:05 -0700500config RTC_DRV_M48T59
Krzysztof Helt94fe7422008-09-03 15:12:34 -0700501 tristate "ST M48T59/M48T08/M48T02"
Mark Zhan2e774c72007-07-17 04:05:05 -0700502 help
503 If you say Y here you will get support for the
Krzysztof Helt94fe7422008-09-03 15:12:34 -0700504 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
505
506 These chips are usually found in Sun SPARC and UltraSPARC
507 workstations.
Mark Zhan2e774c72007-07-17 04:05:05 -0700508
509 This driver can also be built as a module, if so, the module
510 will be called "rtc-m48t59".
511
Daniel Mackd00ed3c2009-09-22 16:46:23 -0700512config RTC_MXC
513 tristate "Freescale MXC Real Time Clock"
514 depends on ARCH_MXC
515 depends on RTC_CLASS
516 help
517 If you say yes here you get support for the Freescale MXC
518 RTC module.
519
520 This driver can also be built as a module, if so, the module
521 will be called "rtc-mxc".
522
David S. Millercca4c232008-08-29 01:29:53 -0700523config RTC_DRV_BQ4802
524 tristate "TI BQ4802"
525 help
526 If you say Y here you will get support for the TI
527 BQ4802 RTC chip.
528
529 This driver can also be built as a module. If so, the module
530 will be called rtc-bq4802.
531
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700532config RTC_DRV_V3020
533 tristate "EM Microelectronic V3020"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700534 help
535 If you say yes here you will get support for the
536 EM Microelectronic v3020 RTC chip.
537
538 This driver can also be built as a module. If so, the module
539 will be called rtc-v3020.
540
Mark Brown35c86bf2009-08-27 19:59:05 +0200541config RTC_DRV_WM831X
542 tristate "Wolfson Microelectronics WM831x RTC"
543 depends on MFD_WM831X
544 help
545 If you say yes here you will get support for the RTC subsystem
546 of the Wolfson Microelectronics WM831X series PMICs.
547
548 This driver can also be built as a module. If so, the module
549 will be called "rtc-wm831x".
550
Mark Brown077eaf52008-11-12 13:27:04 -0800551config RTC_DRV_WM8350
552 tristate "Wolfson Microelectronics WM8350 RTC"
553 depends on MFD_WM8350
554 help
555 If you say yes here you will get support for the RTC subsystem
556 of the Wolfson Microelectronics WM8350.
557
558 This driver can also be built as a module. If so, the module
559 will be called "rtc-wm8350".
560
Balaji Raoeae854b2009-01-09 01:50:51 +0100561config RTC_DRV_PCF50633
562 depends on MFD_PCF50633
563 tristate "NXP PCF50633 RTC"
564 help
565 If you say yes here you get support for the RTC subsystem of the
566 NXP PCF50633 used in embedded systems.
567
Linus Walleijbd207cf2009-08-30 23:49:04 +0200568config RTC_DRV_AB3100
569 tristate "ST-Ericsson AB3100 RTC"
570 depends on AB3100_CORE
571 default y if AB3100_CORE
572 help
573 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
574 support. This chip contains a battery- and capacitor-backed RTC.
575
576
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700577comment "on-CPU RTC drivers"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700578
David Brownelldb68b182006-12-06 20:38:36 -0800579config RTC_DRV_OMAP
580 tristate "TI OMAP1"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700581 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730
David Brownelldb68b182006-12-06 20:38:36 -0800582 help
583 Say "yes" here to support the real time clock on TI OMAP1 chips.
584 This driver can also be built as a module called rtc-omap.
585
Ben Dooks1add6782006-07-01 04:36:26 -0700586config RTC_DRV_S3C
587 tristate "Samsung S3C series SoC RTC"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700588 depends on ARCH_S3C2410
Ben Dooks1add6782006-07-01 04:36:26 -0700589 help
590 RTC (Realtime Clock) driver for the clock inbuilt into the
591 Samsung S3C24XX series of SoCs. This can provide periodic
592 interrupt rates from 1Hz to 64Hz for user programs, and
593 wakeup from Alarm.
594
595 The driver currently supports the common features on all the
596 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
597 and S3C2442.
598
599 This driver can also be build as a module. If so, the module
600 will be called rtc-s3c.
601
Alessandro Zummofd507e22006-03-27 01:16:45 -0800602config RTC_DRV_EP93XX
603 tristate "Cirrus Logic EP93XX"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700604 depends on ARCH_EP93XX
Alessandro Zummofd507e22006-03-27 01:16:45 -0800605 help
606 If you say yes here you get support for the
607 RTC embedded in the Cirrus Logic EP93XX processors.
608
609 This driver can also be built as a module. If so, the module
610 will be called rtc-ep93xx.
611
Richard Purdiee842f1c2006-03-27 01:16:46 -0800612config RTC_DRV_SA1100
613 tristate "SA11x0/PXA2xx"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700614 depends on ARCH_SA1100 || ARCH_PXA
Richard Purdiee842f1c2006-03-27 01:16:46 -0800615 help
616 If you say Y here you will get access to the real time clock
617 built into your SA11x0 or PXA2xx CPU.
618
619 To compile this driver as a module, choose M here: the
620 module will be called rtc-sa1100.
Alessandro Zummofd507e22006-03-27 01:16:45 -0800621
Paul Mundt317a6102006-09-27 17:13:19 +0900622config RTC_DRV_SH
623 tristate "SuperH On-Chip RTC"
Paul Mundt063adc72009-04-16 14:12:22 +0900624 depends on RTC_CLASS && SUPERH && HAVE_CLK
Paul Mundt317a6102006-09-27 17:13:19 +0900625 help
626 Say Y here to enable support for the on-chip RTC found in
627 most SuperH processors.
628
629 To compile this driver as a module, choose M here: the
630 module will be called rtc-sh.
631
Yoichi Yuasa8417eb72006-04-10 22:54:47 -0700632config RTC_DRV_VR41XX
Alessandro Zummo3e16f6a2006-04-10 22:54:48 -0700633 tristate "NEC VR41XX"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700634 depends on CPU_VR41XX
Alessandro Zummo3e16f6a2006-04-10 22:54:48 -0700635 help
636 If you say Y here you will get access to the real time clock
637 built into your NEC VR41XX CPU.
638
639 To compile this driver as a module, choose M here: the
640 module will be called rtc-vr41xx.
Yoichi Yuasa8417eb72006-04-10 22:54:47 -0700641
Russell Kinga1909012008-04-20 12:08:36 +0100642config RTC_DRV_PL030
643 tristate "ARM AMBA PL030 RTC"
644 depends on ARM_AMBA
645 help
646 If you say Y here you will get access to ARM AMBA
647 PrimeCell PL030 RTC found on certain ARM SOCs.
648
649 To compile this driver as a module, choose M here: the
650 module will be called rtc-pl030.
651
Deepak Saxena8ae6e162006-06-25 05:47:38 -0700652config RTC_DRV_PL031
653 tristate "ARM AMBA PL031 RTC"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700654 depends on ARM_AMBA
Deepak Saxena8ae6e162006-06-25 05:47:38 -0700655 help
656 If you say Y here you will get access to ARM AMBA
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700657 PrimeCell PL031 RTC found on certain ARM SOCs.
Deepak Saxena8ae6e162006-06-25 05:47:38 -0700658
659 To compile this driver as a module, choose M here: the
660 module will be called rtc-pl031.
661
Hans-Christian Egtvedtfa04e782007-07-17 04:05:00 -0700662config RTC_DRV_AT32AP700X
663 tristate "AT32AP700X series RTC"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700664 depends on PLATFORM_AT32AP
Hans-Christian Egtvedtfa04e782007-07-17 04:05:00 -0700665 help
666 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
667 AT32AP700x family processors.
668
Andrew Victor7fc39f62006-12-10 02:19:03 -0800669config RTC_DRV_AT91RM9200
David Brownell4cdf8542008-02-06 01:38:59 -0800670 tristate "AT91RM9200 or AT91SAM9RL"
671 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
Andrew Victor788b1fc2006-06-25 05:48:27 -0700672 help
David Brownell4cdf8542008-02-06 01:38:59 -0800673 Driver for the internal RTC (Realtime Clock) module found on
Alessandro Zummoae64d162009-01-06 14:42:17 -0800674 Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips
David Brownell4cdf8542008-02-06 01:38:59 -0800675 this is powered by the backup power supply.
676
677config RTC_DRV_AT91SAM9
Stelian Pop6b71dbf2008-04-05 21:16:15 +0100678 tristate "AT91SAM9x/AT91CAP9"
David Brownell4cdf8542008-02-06 01:38:59 -0800679 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
680 help
Stelian Pop6b71dbf2008-04-05 21:16:15 +0100681 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
682 (Real Time Timer). These timers are powered by the backup power
683 supply (such as a small coin cell battery), but do not need to
684 be used as RTCs.
David Brownell4cdf8542008-02-06 01:38:59 -0800685
686 (On AT91SAM9rl chips you probably want to use the dedicated RTC
687 module and leave the RTT available for other uses.)
688
689config RTC_DRV_AT91SAM9_RTT
690 int
691 range 0 1
692 default 0
693 prompt "RTT module Number" if ARCH_AT91SAM9263
694 depends on RTC_DRV_AT91SAM9
695 help
Alessandro Zummoae64d162009-01-06 14:42:17 -0800696 More than one RTT module is available. You can choose which
697 one will be used as an RTC. The default of zero is normally
David Brownell4cdf8542008-02-06 01:38:59 -0800698 OK to use, though some systems use that for non-RTC purposes.
699
700config RTC_DRV_AT91SAM9_GPBR
701 int
702 range 0 3 if !ARCH_AT91SAM9263
703 range 0 15 if ARCH_AT91SAM9263
704 default 0
705 prompt "Backup Register Number"
706 depends on RTC_DRV_AT91SAM9
707 help
708 The RTC driver needs to use one of the General Purpose Backup
Alessandro Zummoae64d162009-01-06 14:42:17 -0800709 Registers (GPBRs) as well as the RTT. You can choose which one
710 will be used. The default of zero is normally OK to use, but
David Brownell4cdf8542008-02-06 01:38:59 -0800711 on some systems other software needs to use that register.
Andrew Victor788b1fc2006-06-25 05:48:27 -0700712
Manuel Lauss45fd8a02009-01-06 14:42:18 -0800713config RTC_DRV_AU1XXX
714 tristate "Au1xxx Counter0 RTC support"
715 depends on SOC_AU1X00
716 help
717 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
718 counter) to be used as a RTC.
719
720 This driver can also be built as a module. If so, the module
721 will be called rtc-au1xxx.
722
Wu, Bryan8cc75c92007-05-06 14:50:32 -0700723config RTC_DRV_BFIN
724 tristate "Blackfin On-Chip RTC"
Graf Yang7f604592008-08-20 14:09:02 -0700725 depends on BLACKFIN && !BF561
Wu, Bryan8cc75c92007-05-06 14:50:32 -0700726 help
727 If you say yes here you will get support for the
728 Blackfin On-Chip Real Time Clock.
729
730 This driver can also be built as a module. If so, the module
731 will be called rtc-bfin.
732
Nobuhiro Iwamatsue9f2bd82007-05-08 00:26:37 -0700733config RTC_DRV_RS5C313
734 tristate "Ricoh RS5C313"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700735 depends on SH_LANDISK
Nobuhiro Iwamatsue9f2bd82007-05-08 00:26:37 -0700736 help
737 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
738
Geert Uytterhoeven3afe6d02009-02-19 16:46:49 +0100739config RTC_DRV_GENERIC
740 tristate "Generic RTC support"
741 # Please consider writing a new RTC driver instead of using the generic
742 # RTC abstraction
Paul Mundt47c8a082009-04-27 17:34:39 +0900743 depends on PARISC || M68K || PPC || SUPERH32
Kyle McMartin9eb16862008-09-10 14:24:07 +0000744 help
Geert Uytterhoeven3afe6d02009-02-19 16:46:49 +0100745 Say Y or M here to enable RTC support on systems using the generic
746 RTC abstraction. If you do not know what you are doing, you should
Kyle McMartin9eb16862008-09-10 14:24:07 +0000747 just say Y.
748
Robert Jarzmikdc944362009-01-06 14:42:14 -0800749config RTC_DRV_PXA
750 tristate "PXA27x/PXA3xx"
751 depends on ARCH_PXA
752 help
753 If you say Y here you will get access to the real time clock
754 built into your PXA27x or PXA3xx CPU.
755
756 This RTC driver uses PXA RTC registers available since pxa27x
757 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
758
759
David S. Miller7a138ed2008-08-29 01:32:43 -0700760config RTC_DRV_SUN4V
761 bool "SUN4V Hypervisor RTC"
762 depends on SPARC64
763 help
764 If you say Y here you will get support for the Hypervisor
765 based RTC on SUN4V systems.
766
David S. Millerde2cf332008-08-28 23:02:36 -0700767config RTC_DRV_STARFIRE
768 bool "Starfire RTC"
769 depends on SPARC64
770 help
771 If you say Y here you will get support for the RTC found on
772 Starfire systems.
773
Atsushi Nemoto0e149232009-01-06 14:42:22 -0800774config RTC_DRV_TX4939
775 tristate "TX4939 SoC"
776 depends on SOC_TX4939
777 help
778 Driver for the internal RTC (Realtime Clock) module found on
779 Toshiba TX4939 SoC.
780
Saeed Bisharadefb4512009-01-06 14:42:24 -0800781config RTC_DRV_MV
782 tristate "Marvell SoC RTC"
783 depends on ARCH_KIRKWOOD
784 help
785 If you say yes here you will get support for the in-chip RTC
786 that can be found in some of Marvell's SoC devices, such as
787 the Kirkwood 88F6281 and 88F6192.
788
789 This driver can also be built as a module. If so, the module
790 will be called rtc-mv.
791
Geert Uytterhoeven0b5f0372009-02-24 14:04:20 +0100792config RTC_DRV_PS3
793 tristate "PS3 RTC"
794 depends on PPC_PS3
795 help
796 If you say yes here you will get support for the RTC on PS3.
797
798 This driver can also be built as a module. If so, the module
799 will be called rtc-ps3.
800
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700801endif # RTC_CLASS