blob: 24217008aa35f18f0a2b278564bd89efd1d58629 [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
38 clock, usually rtc0. Initialization is done when the system
David Brownell779d2082007-11-14 16:58:29 -080039 starts up, and when it resumes from a low power state. This
40 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
47 time when the system boots from a power-off state. Otherwise, your
48 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
72 This driver can also be built as a module. If so, the module
73 will be called rtc-sysfs.
74
Alessandro Zummo728a2942006-03-27 01:16:40 -080075config RTC_INTF_PROC
David Brownelle40659c2007-05-16 22:11:15 -070076 boolean "/proc/driver/rtc (procfs for rtc0)"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -070077 depends on PROC_FS
Alessandro Zummo728a2942006-03-27 01:16:40 -080078 default RTC_CLASS
79 help
David Brownell9e86ecb2006-09-30 23:28:14 -070080 Say yes here if you want to use your first RTC through the proc
81 interface, /proc/driver/rtc. Other RTCs will not be available
82 through that API.
Alessandro Zummo728a2942006-03-27 01:16:40 -080083
84 This driver can also be built as a module. If so, the module
85 will be called rtc-proc.
86
Alessandro Zummoe8242902006-03-27 01:16:41 -080087config RTC_INTF_DEV
David Brownelle40659c2007-05-16 22:11:15 -070088 boolean "/dev/rtcN (character devices)"
Alessandro Zummoe8242902006-03-27 01:16:41 -080089 default RTC_CLASS
90 help
David Brownell9e86ecb2006-09-30 23:28:14 -070091 Say yes here if you want to use your RTCs using the /dev
92 interfaces, which "udev" sets up as /dev/rtc0 through
93 /dev/rtcN. You may want to set up a symbolic link so one
94 of these can be accessed as /dev/rtc, which is a name
95 expected by "hwclock" and some other programs.
Alessandro Zummoe8242902006-03-27 01:16:41 -080096
97 This driver can also be built as a module. If so, the module
98 will be called rtc-dev.
99
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
David Brownell9e86ecb2006-09-30 23:28:14 -0700105 driver does not expose RTC_UIE ioctls. Those requests generate
106 once-per-second update interrupts, used for synchronization.
Atsushi Nemoto655066c2006-06-25 05:48:17 -0700107
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700108config RTC_DRV_TEST
109 tristate "Test driver/device"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700110 help
111 If you say yes here you get support for the
112 RTC test driver. It's a software RTC which can be
113 used to test the RTC subsystem APIs. It gets
114 the time from the system clock.
115 You want this driver only if you are doing development
116 on the RTC subsystem. Please read the source code
117 for further details.
118
119 This driver can also be built as a module. If so, the module
120 will be called rtc-test.
121
122comment "I2C RTC drivers"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700123 depends on I2C
124
125if I2C
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700126
127config RTC_DRV_DS1307
128 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700129 help
130 If you say yes here you get support for various compatible RTC
131 chips (often with battery backup) connected with I2C. This driver
132 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
133 and probably other chips. In some cases the RTC must already
134 have been initialized (by manufacturing or a bootloader).
135
136 The first seven registers on these chips hold an RTC, and other
137 registers may add features such as NVRAM, a trickle charger for
David Brownell682d73f2007-11-14 16:58:32 -0800138 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
139 sysfs, but other chip features may not be available.
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700140
141 This driver can also be built as a module. If so, the module
142 will be called rtc-ds1307.
143
Scott Woodbf4994d2007-10-16 01:28:19 -0700144config RTC_DRV_DS1374
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800145 tristate "Dallas/Maxim DS1374"
Scott Woodbf4994d2007-10-16 01:28:19 -0700146 depends on RTC_CLASS && I2C
147 help
148 If you say yes here you get support for Dallas Semiconductor
149 DS1374 real-time clock chips. If an interrupt is associated
150 with the device, the alarm functionality is supported.
151
152 This driver can also be built as a module. If so, the module
153 will be called rtc-ds1374.
154
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700155config RTC_DRV_DS1672
156 tristate "Dallas/Maxim DS1672"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700157 help
158 If you say yes here you get support for the
159 Dallas/Maxim DS1672 timekeeping chip.
160
161 This driver can also be built as a module. If so, the module
162 will be called rtc-ds1672.
163
164config RTC_DRV_MAX6900
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800165 tristate "Maxim MAX6900"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700166 help
167 If you say yes here you will get support for the
168 Maxim MAX6900 I2C RTC chip.
169
170 This driver can also be built as a module. If so, the module
171 will be called rtc-max6900.
172
173config RTC_DRV_RS5C372
David Brownelld8154612007-07-17 04:04:55 -0700174 tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700175 help
176 If you say yes here you get support for the
David Brownelld8154612007-07-17 04:04:55 -0700177 Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700178
179 This driver can also be built as a module. If so, the module
180 will be called rtc-rs5c372.
181
182config RTC_DRV_ISL1208
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800183 tristate "Intersil ISL1208"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700184 help
185 If you say yes here you get support for the
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800186 Intersil ISL1208 RTC chip.
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700187
188 This driver can also be built as a module. If so, the module
189 will be called rtc-isl1208.
190
191config RTC_DRV_X1205
192 tristate "Xicor/Intersil X1205"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700193 help
194 If you say yes here you get support for the
195 Xicor/Intersil X1205 RTC chip.
196
197 This driver can also be built as a module. If so, the module
198 will be called rtc-x1205.
199
200config RTC_DRV_PCF8563
201 tristate "Philips PCF8563/Epson RTC8564"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700202 help
203 If you say yes here you get support for the
204 Philips PCF8563 RTC chip. The Epson RTC8564
205 should work as well.
206
207 This driver can also be built as a module. If so, the module
208 will be called rtc-pcf8563.
209
210config RTC_DRV_PCF8583
211 tristate "Philips PCF8583"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700212 help
213 If you say yes here you get support for the Philips PCF8583
214 RTC chip found on Acorn RiscPCs. This driver supports the
215 platform specific method of retrieving the current year from
216 the RTC's SRAM. It will work on other platforms with the same
217 chip, but the year will probably have to be tweaked.
218
219 This driver can also be built as a module. If so, the module
220 will be called rtc-pcf8583.
221
Atsushi Nemotocaaff562007-07-17 04:05:02 -0700222config RTC_DRV_M41T80
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800223 tristate "ST M41T80/81/82/83/84/85/87"
Atsushi Nemotocaaff562007-07-17 04:05:02 -0700224 help
225 If you say Y here you will get support for the
226 ST M41T80 RTC chips series. Currently following chips are
227 supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85
228 and M41ST87.
229
230 This driver can also be built as a module. If so, the module
231 will be called rtc-m41t80.
232
Atsushi Nemoto617780d2007-07-17 04:05:04 -0700233config RTC_DRV_M41T80_WDT
234 bool "ST M41T80 series RTC watchdog timer"
235 depends on RTC_DRV_M41T80
236 help
237 If you say Y here you will get support for the
238 watchdog timer in ST M41T80 RTC chips series.
239
Tony Lindgren0c4a59f2007-07-17 04:06:09 -0700240config RTC_DRV_TWL92330
241 boolean "TI TWL92330/Menelaus"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700242 depends on MENELAUS
Tony Lindgren0c4a59f2007-07-17 04:06:09 -0700243 help
244 If you say yes here you get support for the RTC on the
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200245 TWL92330 "Menelaus" power management chip, used with OMAP2
Tony Lindgren0c4a59f2007-07-17 04:06:09 -0700246 platforms. The support is integrated with the rest of
247 the Menelaus driver; it's not separate module.
248
Byron Bradleyc46288b2008-03-04 14:28:25 -0800249config RTC_DRV_S35390A
250 tristate "Seiko Instruments S-35390A"
Randy Dunlapd4795402008-04-10 21:29:18 -0700251 select BITREVERSE
Byron Bradleyc46288b2008-03-04 14:28:25 -0800252 help
253 If you say yes here you will get support for the Seiko
254 Instruments S-35390A.
255
256 This driver can also be built as a module. If so the module
257 will be called rtc-s35390a.
258
Sergey Lapinc6d8f402008-06-12 15:21:55 -0700259config RTC_DRV_FM3130
260 tristate "Ramtron FM3130"
261 help
262 If you say Y here you will get support for the
263 Ramtron FM3130 RTC chips.
264 Ramtron FM3130 is a chip with two separate devices inside,
265 RTC clock and FRAM. This driver provides only RTC functionality.
266
267 This driver can also be built as a module. If so the module
268 will be called rtc-fm3130.
269
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700270endif # I2C
271
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700272comment "SPI RTC drivers"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700273
274if SPI_MASTER
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700275
Kim B. Heino8fc2c762008-07-23 21:30:34 -0700276config RTC_DRV_M41T94
277 tristate "ST M41T94"
278 help
279 If you say yes here you will get support for the
280 ST M41T94 SPI RTC chip.
281
282 This driver can also be built as a module. If so, the module
283 will be called rtc-m41t94.
284
David Brownell53e84b62008-07-23 21:30:36 -0700285config RTC_DRV_DS1305
286 tristate "Dallas/Maxim DS1305/DS1306"
287 help
288 Select this driver to get support for the Dallas/Maxim DS1305
289 and DS1306 real time clock chips. These support a trickle
290 charger, alarms, and NVRAM in addition to the clock.
291
292 This driver can also be built as a module. If so, the module
293 will be called rtc-ds1305.
294
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800295config RTC_DRV_MAX6902
296 tristate "Maxim MAX6902"
297 help
298 If you say yes here you will get support for the
299 Maxim MAX6902 SPI RTC chip.
300
301 This driver can also be built as a module. If so, the module
302 will be called rtc-max6902.
303
Magnus Damm2805b962008-02-06 01:38:53 -0800304config RTC_DRV_R9701
305 tristate "Epson RTC-9701JE"
306 help
307 If you say yes here you will get support for the
308 Epson RTC-9701JE SPI RTC chip.
309
310 This driver can also be built as a module. If so, the module
311 will be called rtc-r9701.
312
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700313config RTC_DRV_RS5C348
314 tristate "Ricoh RS5C348A/B"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700315 help
316 If you say yes here you get support for the
317 Ricoh RS5C348A and RS5C348B RTC chips.
318
319 This driver can also be built as a module. If so, the module
320 will be called rtc-rs5c348.
321
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700322endif # SPI_MASTER
323
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700324comment "Platform RTC drivers"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -0800325
David Brownell7be2c7c2007-02-10 01:46:02 -0800326# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
327# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
328# global rtc_lock ... it's not yet just another platform_device.
329
330config RTC_DRV_CMOS
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700331 tristate "PC-style 'CMOS'"
Andrew Morton5ec87702008-09-22 21:40:04 -0700332 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
David Brownellc7500902008-04-28 02:11:52 -0700333 default y if X86
David Brownell7be2c7c2007-02-10 01:46:02 -0800334 help
335 Say "yes" here to get direct support for the real time clock
336 found in every PC or ACPI-based system, and some other boards.
337 Specifically the original MC146818, compatibles like those in
338 PC south bridges, the DS12887 or M48T86, some multifunction
339 or LPC bus chips, and so on.
340
341 Your system will need to define the platform device used by
342 this driver, otherwise it won't be accessible. This means
343 you can safely enable this driver if you don't know whether
344 or not your board has this kind of hardware.
345
346 This driver can also be built as a module. If so, the module
347 will be called rtc-cmos.
348
Thomas Bogendoerfer537739d2007-07-17 04:05:06 -0700349config RTC_DRV_DS1216
350 tristate "Dallas DS1216"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700351 depends on SNI_RM
Thomas Bogendoerfer537739d2007-07-17 04:05:06 -0700352 help
353 If you say yes here you get support for the Dallas DS1216 RTC chips.
354
Thomas Bogendoerfer5f119f22008-10-14 17:16:59 +0200355config RTC_DRV_DS1286
356 tristate "Dallas DS1286"
357 help
358 If you say yes here you get support for the Dallas DS1286 RTC chips.
359
Paul Mundt739d3402008-02-06 01:38:44 -0800360config RTC_DRV_DS1302
361 tristate "Dallas DS1302"
362 depends on SH_SECUREEDGE5410
363 help
364 If you say yes here you get support for the Dallas DS1302 RTC chips.
365
Andrew Sharp8f267952008-02-06 01:38:46 -0800366config RTC_DRV_DS1511
367 tristate "Dallas DS1511"
368 depends on RTC_CLASS
369 help
370 If you say yes here you get support for the
371 Dallas DS1511 timekeeping/watchdog chip.
372
373 This driver can also be built as a module. If so, the module
374 will be called rtc-ds1511.
375
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700376config RTC_DRV_DS1553
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800377 tristate "Maxim/Dallas DS1553"
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700378 help
379 If you say yes here you get support for the
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800380 Maxim/Dallas DS1553 timekeeping chip.
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700381
382 This driver can also be built as a module. If so, the module
383 will be called rtc-ds1553.
384
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800385config RTC_DRV_DS1742
386 tristate "Maxim/Dallas DS1742/1743"
387 help
388 If you say yes here you get support for the
389 Maxim/Dallas DS1742/1743 timekeeping chip.
390
391 This driver can also be built as a module. If so, the module
392 will be called rtc-ds1742.
393
Thomas Hommel02964112007-07-21 04:37:58 -0700394config RTC_DRV_STK17TA8
395 tristate "Simtek STK17TA8"
396 depends on RTC_CLASS
397 help
398 If you say yes here you get support for the
399 Simtek STK17TA8 timekeeping chip.
400
401 This driver can also be built as a module. If so, the module
402 will be called rtc-stk17ta8.
403
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700404config RTC_DRV_M48T86
405 tristate "ST M48T86/Dallas DS12887"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700406 help
407 If you say Y here you will get support for the
408 ST M48T86 and Dallas DS12887 RTC chips.
409
410 This driver can also be built as a module. If so, the module
411 will be called rtc-m48t86.
412
Mark Zhan2e774c72007-07-17 04:05:05 -0700413config RTC_DRV_M48T59
Krzysztof Helt94fe7422008-09-03 15:12:34 -0700414 tristate "ST M48T59/M48T08/M48T02"
Mark Zhan2e774c72007-07-17 04:05:05 -0700415 help
416 If you say Y here you will get support for the
Krzysztof Helt94fe7422008-09-03 15:12:34 -0700417 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
418
419 These chips are usually found in Sun SPARC and UltraSPARC
420 workstations.
Mark Zhan2e774c72007-07-17 04:05:05 -0700421
422 This driver can also be built as a module, if so, the module
423 will be called "rtc-m48t59".
424
David S. Millercca4c232008-08-29 01:29:53 -0700425config RTC_DRV_BQ4802
426 tristate "TI BQ4802"
427 help
428 If you say Y here you will get support for the TI
429 BQ4802 RTC chip.
430
431 This driver can also be built as a module. If so, the module
432 will be called rtc-bq4802.
433
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700434config RTC_DRV_V3020
435 tristate "EM Microelectronic V3020"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700436 help
437 If you say yes here you will get support for the
438 EM Microelectronic v3020 RTC chip.
439
440 This driver can also be built as a module. If so, the module
441 will be called rtc-v3020.
442
443comment "on-CPU RTC drivers"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700444
David Brownelldb68b182006-12-06 20:38:36 -0800445config RTC_DRV_OMAP
446 tristate "TI OMAP1"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700447 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730
David Brownelldb68b182006-12-06 20:38:36 -0800448 help
449 Say "yes" here to support the real time clock on TI OMAP1 chips.
450 This driver can also be built as a module called rtc-omap.
451
Ben Dooks1add6782006-07-01 04:36:26 -0700452config RTC_DRV_S3C
453 tristate "Samsung S3C series SoC RTC"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700454 depends on ARCH_S3C2410
Ben Dooks1add6782006-07-01 04:36:26 -0700455 help
456 RTC (Realtime Clock) driver for the clock inbuilt into the
457 Samsung S3C24XX series of SoCs. This can provide periodic
458 interrupt rates from 1Hz to 64Hz for user programs, and
459 wakeup from Alarm.
460
461 The driver currently supports the common features on all the
462 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
463 and S3C2442.
464
465 This driver can also be build as a module. If so, the module
466 will be called rtc-s3c.
467
Alessandro Zummofd507e22006-03-27 01:16:45 -0800468config RTC_DRV_EP93XX
469 tristate "Cirrus Logic EP93XX"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700470 depends on ARCH_EP93XX
Alessandro Zummofd507e22006-03-27 01:16:45 -0800471 help
472 If you say yes here you get support for the
473 RTC embedded in the Cirrus Logic EP93XX processors.
474
475 This driver can also be built as a module. If so, the module
476 will be called rtc-ep93xx.
477
Richard Purdiee842f1c2006-03-27 01:16:46 -0800478config RTC_DRV_SA1100
479 tristate "SA11x0/PXA2xx"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700480 depends on ARCH_SA1100 || ARCH_PXA
Richard Purdiee842f1c2006-03-27 01:16:46 -0800481 help
482 If you say Y here you will get access to the real time clock
483 built into your SA11x0 or PXA2xx CPU.
484
485 To compile this driver as a module, choose M here: the
486 module will be called rtc-sa1100.
Alessandro Zummofd507e22006-03-27 01:16:45 -0800487
Paul Mundt317a6102006-09-27 17:13:19 +0900488config RTC_DRV_SH
489 tristate "SuperH On-Chip RTC"
Paul Mundtff1b7502007-11-26 17:56:31 +0900490 depends on RTC_CLASS && SUPERH
Paul Mundt317a6102006-09-27 17:13:19 +0900491 help
492 Say Y here to enable support for the on-chip RTC found in
493 most SuperH processors.
494
495 To compile this driver as a module, choose M here: the
496 module will be called rtc-sh.
497
Yoichi Yuasa8417eb72006-04-10 22:54:47 -0700498config RTC_DRV_VR41XX
Alessandro Zummo3e16f6a2006-04-10 22:54:48 -0700499 tristate "NEC VR41XX"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700500 depends on CPU_VR41XX
Alessandro Zummo3e16f6a2006-04-10 22:54:48 -0700501 help
502 If you say Y here you will get access to the real time clock
503 built into your NEC VR41XX CPU.
504
505 To compile this driver as a module, choose M here: the
506 module will be called rtc-vr41xx.
Yoichi Yuasa8417eb72006-04-10 22:54:47 -0700507
Russell Kinga1909012008-04-20 12:08:36 +0100508config RTC_DRV_PL030
509 tristate "ARM AMBA PL030 RTC"
510 depends on ARM_AMBA
511 help
512 If you say Y here you will get access to ARM AMBA
513 PrimeCell PL030 RTC found on certain ARM SOCs.
514
515 To compile this driver as a module, choose M here: the
516 module will be called rtc-pl030.
517
Deepak Saxena8ae6e162006-06-25 05:47:38 -0700518config RTC_DRV_PL031
519 tristate "ARM AMBA PL031 RTC"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700520 depends on ARM_AMBA
Deepak Saxena8ae6e162006-06-25 05:47:38 -0700521 help
522 If you say Y here you will get access to ARM AMBA
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700523 PrimeCell PL031 RTC found on certain ARM SOCs.
Deepak Saxena8ae6e162006-06-25 05:47:38 -0700524
525 To compile this driver as a module, choose M here: the
526 module will be called rtc-pl031.
527
Hans-Christian Egtvedtfa04e782007-07-17 04:05:00 -0700528config RTC_DRV_AT32AP700X
529 tristate "AT32AP700X series RTC"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700530 depends on PLATFORM_AT32AP
Hans-Christian Egtvedtfa04e782007-07-17 04:05:00 -0700531 help
532 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
533 AT32AP700x family processors.
534
Andrew Victor7fc39f62006-12-10 02:19:03 -0800535config RTC_DRV_AT91RM9200
David Brownell4cdf8542008-02-06 01:38:59 -0800536 tristate "AT91RM9200 or AT91SAM9RL"
537 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
Andrew Victor788b1fc2006-06-25 05:48:27 -0700538 help
David Brownell4cdf8542008-02-06 01:38:59 -0800539 Driver for the internal RTC (Realtime Clock) module found on
540 Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips
541 this is powered by the backup power supply.
542
543config RTC_DRV_AT91SAM9
Stelian Pop6b71dbf2008-04-05 21:16:15 +0100544 tristate "AT91SAM9x/AT91CAP9"
David Brownell4cdf8542008-02-06 01:38:59 -0800545 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
546 help
Stelian Pop6b71dbf2008-04-05 21:16:15 +0100547 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
548 (Real Time Timer). These timers are powered by the backup power
549 supply (such as a small coin cell battery), but do not need to
550 be used as RTCs.
David Brownell4cdf8542008-02-06 01:38:59 -0800551
552 (On AT91SAM9rl chips you probably want to use the dedicated RTC
553 module and leave the RTT available for other uses.)
554
555config RTC_DRV_AT91SAM9_RTT
556 int
557 range 0 1
558 default 0
559 prompt "RTT module Number" if ARCH_AT91SAM9263
560 depends on RTC_DRV_AT91SAM9
561 help
562 More than one RTT module is available. You can choose which
563 one will be used as an RTC. The default of zero is normally
564 OK to use, though some systems use that for non-RTC purposes.
565
566config RTC_DRV_AT91SAM9_GPBR
567 int
568 range 0 3 if !ARCH_AT91SAM9263
569 range 0 15 if ARCH_AT91SAM9263
570 default 0
571 prompt "Backup Register Number"
572 depends on RTC_DRV_AT91SAM9
573 help
574 The RTC driver needs to use one of the General Purpose Backup
575 Registers (GPBRs) as well as the RTT. You can choose which one
576 will be used. The default of zero is normally OK to use, but
577 on some systems other software needs to use that register.
Andrew Victor788b1fc2006-06-25 05:48:27 -0700578
Wu, Bryan8cc75c92007-05-06 14:50:32 -0700579config RTC_DRV_BFIN
580 tristate "Blackfin On-Chip RTC"
Graf Yang7f604592008-08-20 14:09:02 -0700581 depends on BLACKFIN && !BF561
Wu, Bryan8cc75c92007-05-06 14:50:32 -0700582 help
583 If you say yes here you will get support for the
584 Blackfin On-Chip Real Time Clock.
585
586 This driver can also be built as a module. If so, the module
587 will be called rtc-bfin.
588
Nobuhiro Iwamatsue9f2bd82007-05-08 00:26:37 -0700589config RTC_DRV_RS5C313
590 tristate "Ricoh RS5C313"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700591 depends on SH_LANDISK
Nobuhiro Iwamatsue9f2bd82007-05-08 00:26:37 -0700592 help
593 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
594
David Woodhouseaabe1882008-06-05 22:46:50 -0700595config RTC_DRV_PPC
596 tristate "PowerPC machine dependent RTC support"
597 depends on PPC_MERGE
598 help
599 The PowerPC kernel has machine-specific functions for accessing
600 the RTC. This exposes that functionality through the generic RTC
601 class.
602
David S. Miller7a138ed2008-08-29 01:32:43 -0700603config RTC_DRV_SUN4V
604 bool "SUN4V Hypervisor RTC"
605 depends on SPARC64
606 help
607 If you say Y here you will get support for the Hypervisor
608 based RTC on SUN4V systems.
609
David S. Millerde2cf332008-08-28 23:02:36 -0700610config RTC_DRV_STARFIRE
611 bool "Starfire RTC"
612 depends on SPARC64
613 help
614 If you say Y here you will get support for the RTC found on
615 Starfire systems.
616
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700617endif # RTC_CLASS