blob: 82f5ad9c3af479a86e711819b8cea6ddfc42f947 [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
19 will be called rtc-class.
20
Jan Engelhardtbb35fb22007-07-31 00:39:46 -070021if RTC_CLASS
22
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -080023if GEN_RTC || RTC
24comment "Conflicting RTC option has been selected, check GEN_RTC and RTC"
25endif
26
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080027config RTC_HCTOSYS
David Brownell7ca1d482007-05-08 00:33:42 -070028 bool "Set system time from RTC on startup and resume"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080029 depends on RTC_CLASS = y
30 default y
31 help
David Brownell7ca1d482007-05-08 00:33:42 -070032 If you say yes here, the system time (wall clock) will be set using
33 the value read from a specified RTC device. This is useful to avoid
34 unnecessary fsck runs at boot time, and to network better.
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080035
36config RTC_HCTOSYS_DEVICE
David Brownell7ca1d482007-05-08 00:33:42 -070037 string "RTC used to set the system time"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080038 depends on RTC_HCTOSYS = y
39 default "rtc0"
40 help
David Brownell7ca1d482007-05-08 00:33:42 -070041 The RTC device that will be used to (re)initialize the system
42 clock, usually rtc0. Initialization is done when the system
David Brownell779d2082007-11-14 16:58:29 -080043 starts up, and when it resumes from a low power state. This
44 device should record time in UTC, since the kernel won't do
45 timezone correction.
David Brownell7ca1d482007-05-08 00:33:42 -070046
David Brownell55ff1ab2007-07-21 04:37:56 -070047 The driver for this RTC device must be loaded before late_initcall
48 functions run, so it must usually be statically linked.
49
David Brownell7ca1d482007-05-08 00:33:42 -070050 This clock should be battery-backed, so that it reads the correct
51 time when the system boots from a power-off state. Otherwise, your
52 system will need an external clock source (like an NTP server).
53
54 If the clock you specify here is not battery backed, it may still
55 be useful to reinitialize system time when resuming from system
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -080056 sleep states. Do not specify an RTC here unless it stays powered
David Brownell7ca1d482007-05-08 00:33:42 -070057 during all this system's supported sleep states.
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080058
David Brownell9e86ecb2006-09-30 23:28:14 -070059config RTC_DEBUG
60 bool "RTC debug support"
61 depends on RTC_CLASS = y
62 help
63 Say yes here to enable debugging support in the RTC framework
64 and individual RTC drivers.
65
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080066comment "RTC interfaces"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080067
Alessandro Zummoc5c3e192006-03-27 01:16:39 -080068config RTC_INTF_SYSFS
David Brownelle40659c2007-05-16 22:11:15 -070069 boolean "/sys/class/rtc/rtcN (sysfs)"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -070070 depends on SYSFS
Alessandro Zummoc5c3e192006-03-27 01:16:39 -080071 default RTC_CLASS
72 help
David Brownell9e86ecb2006-09-30 23:28:14 -070073 Say yes here if you want to use your RTCs using sysfs interfaces,
74 /sys/class/rtc/rtc0 through /sys/.../rtcN.
Alessandro Zummoc5c3e192006-03-27 01:16:39 -080075
76 This driver can also be built as a module. If so, the module
77 will be called rtc-sysfs.
78
Alessandro Zummo728a2942006-03-27 01:16:40 -080079config RTC_INTF_PROC
David Brownelle40659c2007-05-16 22:11:15 -070080 boolean "/proc/driver/rtc (procfs for rtc0)"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -070081 depends on PROC_FS
Alessandro Zummo728a2942006-03-27 01:16:40 -080082 default RTC_CLASS
83 help
David Brownell9e86ecb2006-09-30 23:28:14 -070084 Say yes here if you want to use your first RTC through the proc
85 interface, /proc/driver/rtc. Other RTCs will not be available
86 through that API.
Alessandro Zummo728a2942006-03-27 01:16:40 -080087
88 This driver can also be built as a module. If so, the module
89 will be called rtc-proc.
90
Alessandro Zummoe8242902006-03-27 01:16:41 -080091config RTC_INTF_DEV
David Brownelle40659c2007-05-16 22:11:15 -070092 boolean "/dev/rtcN (character devices)"
Alessandro Zummoe8242902006-03-27 01:16:41 -080093 default RTC_CLASS
94 help
David Brownell9e86ecb2006-09-30 23:28:14 -070095 Say yes here if you want to use your RTCs using the /dev
96 interfaces, which "udev" sets up as /dev/rtc0 through
97 /dev/rtcN. You may want to set up a symbolic link so one
98 of these can be accessed as /dev/rtc, which is a name
99 expected by "hwclock" and some other programs.
Alessandro Zummoe8242902006-03-27 01:16:41 -0800100
101 This driver can also be built as a module. If so, the module
102 will be called rtc-dev.
103
Atsushi Nemoto655066c2006-06-25 05:48:17 -0700104config RTC_INTF_DEV_UIE_EMUL
105 bool "RTC UIE emulation on dev interface"
106 depends on RTC_INTF_DEV
107 help
David Sterba3dde6ad2007-05-09 07:12:20 +0200108 Provides an emulation for RTC_UIE if the underlying rtc chip
David Brownell9e86ecb2006-09-30 23:28:14 -0700109 driver does not expose RTC_UIE ioctls. Those requests generate
110 once-per-second update interrupts, used for synchronization.
Atsushi Nemoto655066c2006-06-25 05:48:17 -0700111
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
135 chips (often with battery backup) connected with I2C. This driver
136 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
137 and probably other chips. In some cases the RTC must already
138 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
David Brownell682d73f2007-11-14 16:58:32 -0800142 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
143 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
153 DS1374 real-time clock chips. If an interrupt is associated
154 with the device, the alarm functionality is supported.
155
156 This driver can also be built as a module. If so, the module
157 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
David Brownelld8154612007-07-17 04:04:55 -0700178 tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700179 help
180 If you say yes here you get support for the
David Brownelld8154612007-07-17 04:04:55 -0700181 Ricoh 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
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800227 tristate "ST M41T80/81/82/83/84/85/87"
Atsushi Nemotocaaff562007-07-17 04:05:02 -0700228 help
229 If you say Y here you will get support for the
230 ST M41T80 RTC chips series. Currently following chips are
231 supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85
232 and M41ST87.
233
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
238 bool "ST M41T80 series RTC watchdog timer"
239 depends on RTC_DRV_M41T80
240 help
241 If you say Y here you will get support for the
242 watchdog timer in ST M41T80 RTC chips series.
243
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
Tony Lindgren0c4a59f2007-07-17 04:06:09 -0700250 platforms. The support is integrated with the rest of
251 the Menelaus driver; it's not separate module.
252
Byron Bradleyc46288b2008-03-04 14:28:25 -0800253config RTC_DRV_S35390A
254 tristate "Seiko Instruments S-35390A"
255 help
256 If you say yes here you will get support for the Seiko
257 Instruments S-35390A.
258
259 This driver can also be built as a module. If so the module
260 will be called rtc-s35390a.
261
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700262endif # I2C
263
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700264comment "SPI RTC drivers"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700265
266if SPI_MASTER
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700267
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800268config RTC_DRV_MAX6902
269 tristate "Maxim MAX6902"
270 help
271 If you say yes here you will get support for the
272 Maxim MAX6902 SPI RTC chip.
273
274 This driver can also be built as a module. If so, the module
275 will be called rtc-max6902.
276
Magnus Damm2805b962008-02-06 01:38:53 -0800277config RTC_DRV_R9701
278 tristate "Epson RTC-9701JE"
279 help
280 If you say yes here you will get support for the
281 Epson RTC-9701JE SPI RTC chip.
282
283 This driver can also be built as a module. If so, the module
284 will be called rtc-r9701.
285
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700286config RTC_DRV_RS5C348
287 tristate "Ricoh RS5C348A/B"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700288 help
289 If you say yes here you get support for the
290 Ricoh RS5C348A and RS5C348B RTC chips.
291
292 This driver can also be built as a module. If so, the module
293 will be called rtc-rs5c348.
294
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700295endif # SPI_MASTER
296
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700297comment "Platform RTC drivers"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -0800298
David Brownell7be2c7c2007-02-10 01:46:02 -0800299# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
300# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
301# global rtc_lock ... it's not yet just another platform_device.
302
303config RTC_DRV_CMOS
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700304 tristate "PC-style 'CMOS'"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700305 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS
David Brownell7be2c7c2007-02-10 01:46:02 -0800306 help
307 Say "yes" here to get direct support for the real time clock
308 found in every PC or ACPI-based system, and some other boards.
309 Specifically the original MC146818, compatibles like those in
310 PC south bridges, the DS12887 or M48T86, some multifunction
311 or LPC bus chips, and so on.
312
313 Your system will need to define the platform device used by
314 this driver, otherwise it won't be accessible. This means
315 you can safely enable this driver if you don't know whether
316 or not your board has this kind of hardware.
317
318 This driver can also be built as a module. If so, the module
319 will be called rtc-cmos.
320
Thomas Bogendoerfer537739d2007-07-17 04:05:06 -0700321config RTC_DRV_DS1216
322 tristate "Dallas DS1216"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700323 depends on SNI_RM
Thomas Bogendoerfer537739d2007-07-17 04:05:06 -0700324 help
325 If you say yes here you get support for the Dallas DS1216 RTC chips.
326
Paul Mundt739d3402008-02-06 01:38:44 -0800327config RTC_DRV_DS1302
328 tristate "Dallas DS1302"
329 depends on SH_SECUREEDGE5410
330 help
331 If you say yes here you get support for the Dallas DS1302 RTC chips.
332
Andrew Sharp8f267952008-02-06 01:38:46 -0800333config RTC_DRV_DS1511
334 tristate "Dallas DS1511"
335 depends on RTC_CLASS
336 help
337 If you say yes here you get support for the
338 Dallas DS1511 timekeeping/watchdog chip.
339
340 This driver can also be built as a module. If so, the module
341 will be called rtc-ds1511.
342
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700343config RTC_DRV_DS1553
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800344 tristate "Maxim/Dallas DS1553"
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700345 help
346 If you say yes here you get support for the
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800347 Maxim/Dallas DS1553 timekeeping chip.
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700348
349 This driver can also be built as a module. If so, the module
350 will be called rtc-ds1553.
351
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800352config RTC_DRV_DS1742
353 tristate "Maxim/Dallas DS1742/1743"
354 help
355 If you say yes here you get support for the
356 Maxim/Dallas DS1742/1743 timekeeping chip.
357
358 This driver can also be built as a module. If so, the module
359 will be called rtc-ds1742.
360
Thomas Hommel02964112007-07-21 04:37:58 -0700361config RTC_DRV_STK17TA8
362 tristate "Simtek STK17TA8"
363 depends on RTC_CLASS
364 help
365 If you say yes here you get support for the
366 Simtek STK17TA8 timekeeping chip.
367
368 This driver can also be built as a module. If so, the module
369 will be called rtc-stk17ta8.
370
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700371config RTC_DRV_M48T86
372 tristate "ST M48T86/Dallas DS12887"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700373 help
374 If you say Y here you will get support for the
375 ST M48T86 and Dallas DS12887 RTC chips.
376
377 This driver can also be built as a module. If so, the module
378 will be called rtc-m48t86.
379
Mark Zhan2e774c72007-07-17 04:05:05 -0700380config RTC_DRV_M48T59
381 tristate "ST M48T59"
Mark Zhan2e774c72007-07-17 04:05:05 -0700382 help
383 If you say Y here you will get support for the
384 ST M48T59 RTC chip.
385
386 This driver can also be built as a module, if so, the module
387 will be called "rtc-m48t59".
388
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700389config RTC_DRV_V3020
390 tristate "EM Microelectronic V3020"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700391 help
392 If you say yes here you will get support for the
393 EM Microelectronic v3020 RTC chip.
394
395 This driver can also be built as a module. If so, the module
396 will be called rtc-v3020.
397
398comment "on-CPU RTC drivers"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700399
David Brownelldb68b182006-12-06 20:38:36 -0800400config RTC_DRV_OMAP
401 tristate "TI OMAP1"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700402 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730
David Brownelldb68b182006-12-06 20:38:36 -0800403 help
404 Say "yes" here to support the real time clock on TI OMAP1 chips.
405 This driver can also be built as a module called rtc-omap.
406
Ben Dooks1add6782006-07-01 04:36:26 -0700407config RTC_DRV_S3C
408 tristate "Samsung S3C series SoC RTC"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700409 depends on ARCH_S3C2410
Ben Dooks1add6782006-07-01 04:36:26 -0700410 help
411 RTC (Realtime Clock) driver for the clock inbuilt into the
412 Samsung S3C24XX series of SoCs. This can provide periodic
413 interrupt rates from 1Hz to 64Hz for user programs, and
414 wakeup from Alarm.
415
416 The driver currently supports the common features on all the
417 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
418 and S3C2442.
419
420 This driver can also be build as a module. If so, the module
421 will be called rtc-s3c.
422
Alessandro Zummofd507e22006-03-27 01:16:45 -0800423config RTC_DRV_EP93XX
424 tristate "Cirrus Logic EP93XX"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700425 depends on ARCH_EP93XX
Alessandro Zummofd507e22006-03-27 01:16:45 -0800426 help
427 If you say yes here you get support for the
428 RTC embedded in the Cirrus Logic EP93XX processors.
429
430 This driver can also be built as a module. If so, the module
431 will be called rtc-ep93xx.
432
Richard Purdiee842f1c2006-03-27 01:16:46 -0800433config RTC_DRV_SA1100
434 tristate "SA11x0/PXA2xx"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700435 depends on ARCH_SA1100 || ARCH_PXA
Richard Purdiee842f1c2006-03-27 01:16:46 -0800436 help
437 If you say Y here you will get access to the real time clock
438 built into your SA11x0 or PXA2xx CPU.
439
440 To compile this driver as a module, choose M here: the
441 module will be called rtc-sa1100.
Alessandro Zummofd507e22006-03-27 01:16:45 -0800442
Paul Mundt317a6102006-09-27 17:13:19 +0900443config RTC_DRV_SH
444 tristate "SuperH On-Chip RTC"
Paul Mundtff1b7502007-11-26 17:56:31 +0900445 depends on RTC_CLASS && SUPERH
Paul Mundt317a6102006-09-27 17:13:19 +0900446 help
447 Say Y here to enable support for the on-chip RTC found in
448 most SuperH processors.
449
450 To compile this driver as a module, choose M here: the
451 module will be called rtc-sh.
452
Yoichi Yuasa8417eb72006-04-10 22:54:47 -0700453config RTC_DRV_VR41XX
Alessandro Zummo3e16f6a2006-04-10 22:54:48 -0700454 tristate "NEC VR41XX"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700455 depends on CPU_VR41XX
Alessandro Zummo3e16f6a2006-04-10 22:54:48 -0700456 help
457 If you say Y here you will get access to the real time clock
458 built into your NEC VR41XX CPU.
459
460 To compile this driver as a module, choose M here: the
461 module will be called rtc-vr41xx.
Yoichi Yuasa8417eb72006-04-10 22:54:47 -0700462
Deepak Saxena8ae6e162006-06-25 05:47:38 -0700463config RTC_DRV_PL031
464 tristate "ARM AMBA PL031 RTC"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700465 depends on ARM_AMBA
Deepak Saxena8ae6e162006-06-25 05:47:38 -0700466 help
467 If you say Y here you will get access to ARM AMBA
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700468 PrimeCell PL031 RTC found on certain ARM SOCs.
Deepak Saxena8ae6e162006-06-25 05:47:38 -0700469
470 To compile this driver as a module, choose M here: the
471 module will be called rtc-pl031.
472
Hans-Christian Egtvedtfa04e782007-07-17 04:05:00 -0700473config RTC_DRV_AT32AP700X
474 tristate "AT32AP700X series RTC"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700475 depends on PLATFORM_AT32AP
Hans-Christian Egtvedtfa04e782007-07-17 04:05:00 -0700476 help
477 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
478 AT32AP700x family processors.
479
Andrew Victor7fc39f62006-12-10 02:19:03 -0800480config RTC_DRV_AT91RM9200
David Brownell4cdf8542008-02-06 01:38:59 -0800481 tristate "AT91RM9200 or AT91SAM9RL"
482 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
Andrew Victor788b1fc2006-06-25 05:48:27 -0700483 help
David Brownell4cdf8542008-02-06 01:38:59 -0800484 Driver for the internal RTC (Realtime Clock) module found on
485 Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips
486 this is powered by the backup power supply.
487
488config RTC_DRV_AT91SAM9
489 tristate "AT91SAM9x"
490 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
491 help
492 RTC driver for the Atmel AT91SAM9x internal RTT (Real Time Timer).
493 These timers are powered by the backup power supply (such as a
494 small coin cell battery), but do not need to be used as RTCs.
495
496 (On AT91SAM9rl chips you probably want to use the dedicated RTC
497 module and leave the RTT available for other uses.)
498
499config RTC_DRV_AT91SAM9_RTT
500 int
501 range 0 1
502 default 0
503 prompt "RTT module Number" if ARCH_AT91SAM9263
504 depends on RTC_DRV_AT91SAM9
505 help
506 More than one RTT module is available. You can choose which
507 one will be used as an RTC. The default of zero is normally
508 OK to use, though some systems use that for non-RTC purposes.
509
510config RTC_DRV_AT91SAM9_GPBR
511 int
512 range 0 3 if !ARCH_AT91SAM9263
513 range 0 15 if ARCH_AT91SAM9263
514 default 0
515 prompt "Backup Register Number"
516 depends on RTC_DRV_AT91SAM9
517 help
518 The RTC driver needs to use one of the General Purpose Backup
519 Registers (GPBRs) as well as the RTT. You can choose which one
520 will be used. The default of zero is normally OK to use, but
521 on some systems other software needs to use that register.
Andrew Victor788b1fc2006-06-25 05:48:27 -0700522
Wu, Bryan8cc75c92007-05-06 14:50:32 -0700523config RTC_DRV_BFIN
524 tristate "Blackfin On-Chip RTC"
Mike Frysinger529a73f2007-11-23 14:28:44 +0800525 depends on BLACKFIN
Wu, Bryan8cc75c92007-05-06 14:50:32 -0700526 help
527 If you say yes here you will get support for the
528 Blackfin On-Chip Real Time Clock.
529
530 This driver can also be built as a module. If so, the module
531 will be called rtc-bfin.
532
Nobuhiro Iwamatsue9f2bd82007-05-08 00:26:37 -0700533config RTC_DRV_RS5C313
534 tristate "Ricoh RS5C313"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700535 depends on SH_LANDISK
Nobuhiro Iwamatsue9f2bd82007-05-08 00:26:37 -0700536 help
537 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
538
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700539endif # RTC_CLASS