rtc: driver for the DryIce block found in i.MX25 chips
[deliverable/linux.git] / drivers / rtc / Kconfig
CommitLineData
7be2c7c9 1#
c58411e9
AZ
2# RTC class/drivers configuration
3#
4
5config RTC_LIB
0c86edc0
AZ
6 tristate
7
bb35fb20
JE
8menuconfig RTC_CLASS
9 tristate "Real Time Clock"
0c86edc0 10 default n
bb35fb20 11 depends on !S390
0c86edc0
AZ
12 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
27ae4104 16 probably want to enable one or more of the interfaces below.
0c86edc0
AZ
17
18 This driver can also be built as a module. If so, the module
44e0451d 19 will be called rtc-core.
0c86edc0 20
bb35fb20
JE
21if RTC_CLASS
22
0c86edc0 23config RTC_HCTOSYS
7ca1d488 24 bool "Set system time from RTC on startup and resume"
0c86edc0
AZ
25 depends on RTC_CLASS = y
26 default y
27 help
7ca1d488
DB
28 If you say yes here, the system time (wall clock) will be set using
29 the value read from a specified RTC device. This is useful to avoid
30 unnecessary fsck runs at boot time, and to network better.
0c86edc0
AZ
31
32config RTC_HCTOSYS_DEVICE
7ca1d488 33 string "RTC used to set the system time"
0c86edc0
AZ
34 depends on RTC_HCTOSYS = y
35 default "rtc0"
36 help
7ca1d488 37 The RTC device that will be used to (re)initialize the system
ae64d169
AZ
38 clock, usually rtc0. Initialization is done when the system
39 starts up, and when it resumes from a low power state. This
779d2089
DB
40 device should record time in UTC, since the kernel won't do
41 timezone correction.
7ca1d488 42
55ff1aba
DB
43 The driver for this RTC device must be loaded before late_initcall
44 functions run, so it must usually be statically linked.
45
7ca1d488 46 This clock should be battery-backed, so that it reads the correct
ae64d169 47 time when the system boots from a power-off state. Otherwise, your
7ca1d488
DB
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
09b6bdb3 52 sleep states. Do not specify an RTC here unless it stays powered
7ca1d488 53 during all this system's supported sleep states.
0c86edc0 54
9e86ecb6
DB
55config 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
0c86edc0 62comment "RTC interfaces"
0c86edc0 63
c5c3e192 64config RTC_INTF_SYSFS
e40659c5 65 boolean "/sys/class/rtc/rtcN (sysfs)"
bb35fb20 66 depends on SYSFS
c5c3e192
AZ
67 default RTC_CLASS
68 help
9e86ecb6
DB
69 Say yes here if you want to use your RTCs using sysfs interfaces,
70 /sys/class/rtc/rtc0 through /sys/.../rtcN.
c5c3e192 71
ae64d169 72 If unsure, say Y.
c5c3e192 73
728a2947 74config RTC_INTF_PROC
e40659c5 75 boolean "/proc/driver/rtc (procfs for rtc0)"
bb35fb20 76 depends on PROC_FS
728a2947
AZ
77 default RTC_CLASS
78 help
9e86ecb6 79 Say yes here if you want to use your first RTC through the proc
ae64d169 80 interface, /proc/driver/rtc. Other RTCs will not be available
9e86ecb6 81 through that API.
728a2947 82
ae64d169 83 If unsure, say Y.
728a2947 84
e824290e 85config RTC_INTF_DEV
e40659c5 86 boolean "/dev/rtcN (character devices)"
e824290e
AZ
87 default RTC_CLASS
88 help
9e86ecb6
DB
89 Say yes here if you want to use your RTCs using the /dev
90 interfaces, which "udev" sets up as /dev/rtc0 through
ae64d169 91 /dev/rtcN.
e824290e 92
ae64d169
AZ
93 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.
e824290e 99
655066c3
AN
100config RTC_INTF_DEV_UIE_EMUL
101 bool "RTC UIE emulation on dev interface"
102 depends on RTC_INTF_DEV
103 help
3dde6ad8 104 Provides an emulation for RTC_UIE if the underlying rtc chip
099e6576 105 driver does not expose RTC_UIE ioctls. Those requests generate
9e86ecb6 106 once-per-second update interrupts, used for synchronization.
655066c3 107
099e6576
AZ
108 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
09a21e56
AZ
112config RTC_DRV_TEST
113 tristate "Test driver/device"
1fec7c66
AZ
114 help
115 If you say yes here you get support for the
09a21e56
AZ
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.
1fec7c66
AZ
122
123 This driver can also be built as a module. If so, the module
09a21e56
AZ
124 will be called rtc-test.
125
126comment "I2C RTC drivers"
bb35fb20
JE
127 depends on I2C
128
129if I2C
1fec7c66 130
1abb0dc9 131config RTC_DRV_DS1307
a2166858 132 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
1abb0dc9
DB
133 help
134 If you say yes here you get support for various compatible RTC
ae64d169 135 chips (often with battery backup) connected with I2C. This driver
1abb0dc9 136 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
a2166858
MF
137 EPSON RX-8025 and probably other chips. In some cases the RTC
138 must already have been initialized (by manufacturing or a
139 bootloader).
1abb0dc9
DB
140
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
ae64d169 143 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
682d73f6 144 sysfs, but other chip features may not be available.
1abb0dc9
DB
145
146 This driver can also be built as a module. If so, the module
147 will be called rtc-ds1307.
148
bf4994d7 149config RTC_DRV_DS1374
09b6bdb3 150 tristate "Dallas/Maxim DS1374"
bf4994d7
SW
151 depends on RTC_CLASS && I2C
152 help
153 If you say yes here you get support for Dallas Semiconductor
ae64d169 154 DS1374 real-time clock chips. If an interrupt is associated
bf4994d7
SW
155 with the device, the alarm functionality is supported.
156
ae64d169 157 This driver can also be built as a module. If so, the module
bf4994d7
SW
158 will be called rtc-ds1374.
159
09a21e56
AZ
160config RTC_DRV_DS1672
161 tristate "Dallas/Maxim DS1672"
9bf5b4f5
AN
162 help
163 If you say yes here you get support for the
09a21e56 164 Dallas/Maxim DS1672 timekeeping chip.
9bf5b4f5
AN
165
166 This driver can also be built as a module. If so, the module
09a21e56 167 will be called rtc-ds1672.
9bf5b4f5 168
09a21e56 169config RTC_DRV_MAX6900
09b6bdb3 170 tristate "Maxim MAX6900"
7e56a7dc 171 help
09a21e56
AZ
172 If you say yes here you will get support for the
173 Maxim MAX6900 I2C RTC chip.
7e56a7dc
HVR
174
175 This driver can also be built as a module. If so, the module
09a21e56 176 will be called rtc-max6900.
7e56a7dc 177
a39069f6
HZ
178config RTC_DRV_MAX8925
179 tristate "Maxim MAX8925"
180 depends on MFD_MAX8925
181 help
182 If you say yes here you will get support for the
183 RTC of Maxim MAX8925 PMIC.
184
185 This driver can also be built as a module. If so, the module
186 will be called rtc-max8925.
187
09a21e56 188config RTC_DRV_RS5C372
5d4529be 189 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
edf1aaa3
AZ
190 help
191 If you say yes here you get support for the
5d4529be 192 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
edf1aaa3
AZ
193
194 This driver can also be built as a module. If so, the module
09a21e56 195 will be called rtc-rs5c372.
edf1aaa3 196
09a21e56 197config RTC_DRV_ISL1208
09b6bdb3 198 tristate "Intersil ISL1208"
5ec3e4b7
AN
199 help
200 If you say yes here you get support for the
09b6bdb3 201 Intersil ISL1208 RTC chip.
5ec3e4b7
AN
202
203 This driver can also be built as a module. If so, the module
09a21e56 204 will be called rtc-isl1208.
5ec3e4b7 205
09a21e56
AZ
206config RTC_DRV_X1205
207 tristate "Xicor/Intersil X1205"
db68b189 208 help
09a21e56
AZ
209 If you say yes here you get support for the
210 Xicor/Intersil X1205 RTC chip.
211
212 This driver can also be built as a module. If so, the module
213 will be called rtc-x1205.
db68b189 214
b5a82d62
AZ
215config RTC_DRV_PCF8563
216 tristate "Philips PCF8563/Epson RTC8564"
b5a82d62
AZ
217 help
218 If you say yes here you get support for the
219 Philips PCF8563 RTC chip. The Epson RTC8564
220 should work as well.
221
222 This driver can also be built as a module. If so, the module
223 will be called rtc-pcf8563.
224
9c0c5705
L
225config RTC_DRV_PCF8583
226 tristate "Philips PCF8583"
9c0c5705 227 help
bb71f99f 228 If you say yes here you get support for the Philips PCF8583
09a21e56 229 RTC chip found on Acorn RiscPCs. This driver supports the
bb71f99f 230 platform specific method of retrieving the current year from
09a21e56
AZ
231 the RTC's SRAM. It will work on other platforms with the same
232 chip, but the year will probably have to be tweaked.
9c0c5705
L
233
234 This driver can also be built as a module. If so, the module
235 will be called rtc-pcf8583.
236
caaff562 237config RTC_DRV_M41T80
f30281f4 238 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
caaff562 239 help
d3a126fc
SF
240 If you say Y here you will get support for the ST M41T60
241 and M41T80 RTC chips series. Currently, the following chips are
f30281f4 242 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
d3a126fc 243 M41ST85, and M41ST87.
caaff562
AN
244
245 This driver can also be built as a module. If so, the module
246 will be called rtc-m41t80.
247
617780d2 248config RTC_DRV_M41T80_WDT
d3a126fc 249 bool "ST M41T65/M41T80 series RTC watchdog timer"
617780d2
AN
250 depends on RTC_DRV_M41T80
251 help
252 If you say Y here you will get support for the
d3a126fc 253 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
617780d2 254
1ce7c83f
PZ
255config RTC_DRV_BQ32K
256 tristate "TI BQ32000"
257 help
258 If you say Y here you will get support for the TI
259 BQ32000 I2C RTC chip.
260
261 This driver can also be built as a module. If so, the module
262 will be called rtc-bq32k.
263
afd8d0f9
DB
264config RTC_DRV_DM355EVM
265 tristate "TI DaVinci DM355 EVM RTC"
266 depends on MFD_DM355EVM_MSP
267 help
268 Supports the RTC firmware in the MSP430 on the DM355 EVM.
269
0c4a59fe
TL
270config RTC_DRV_TWL92330
271 boolean "TI TWL92330/Menelaus"
bb35fb20 272 depends on MENELAUS
0c4a59fe
TL
273 help
274 If you say yes here you get support for the RTC on the
01dd2fbf 275 TWL92330 "Menelaus" power management chip, used with OMAP2
ae64d169 276 platforms. The support is integrated with the rest of
0c4a59fe
TL
277 the Menelaus driver; it's not separate module.
278
f96411ab 279config RTC_DRV_TWL4030
a6b49ffd 280 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
f96411ab
DB
281 depends on RTC_CLASS && TWL4030_CORE
282 help
283 If you say yes here you get support for the RTC on the
a6b49ffd 284 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
f96411ab
DB
285
286 This driver can also be built as a module. If so, the module
a6b49ffd 287 will be called rtc-twl.
f96411ab 288
c46288b0
BB
289config RTC_DRV_S35390A
290 tristate "Seiko Instruments S-35390A"
d479540d 291 select BITREVERSE
c46288b0
BB
292 help
293 If you say yes here you will get support for the Seiko
294 Instruments S-35390A.
295
296 This driver can also be built as a module. If so the module
297 will be called rtc-s35390a.
298
c6d8f400
SL
299config RTC_DRV_FM3130
300 tristate "Ramtron FM3130"
301 help
302 If you say Y here you will get support for the
303 Ramtron FM3130 RTC chips.
304 Ramtron FM3130 is a chip with two separate devices inside,
305 RTC clock and FRAM. This driver provides only RTC functionality.
306
307 This driver can also be built as a module. If so the module
308 will be called rtc-fm3130.
309
a7fa9851
MW
310config RTC_DRV_RX8581
311 tristate "Epson RX-8581"
312 help
313 If you say yes here you will get support for the Epson RX-8581.
314
315 This driver can also be built as a module. If so the module
316 will be called rtc-rx8581.
317
3c2b9075
WG
318config RTC_DRV_RX8025
319 tristate "Epson RX-8025SA/NB"
320 help
321 If you say yes here you get support for the Epson
322 RX-8025SA/NB RTC chips.
323
324 This driver can also be built as a module. If so, the module
325 will be called rtc-rx8025.
326
bb35fb20
JE
327endif # I2C
328
09a21e56 329comment "SPI RTC drivers"
bb35fb20
JE
330
331if SPI_MASTER
09a21e56 332
8fc2c767
KH
333config RTC_DRV_M41T94
334 tristate "ST M41T94"
335 help
336 If you say yes here you will get support for the
337 ST M41T94 SPI RTC chip.
338
339 This driver can also be built as a module. If so, the module
340 will be called rtc-m41t94.
341
53e84b67
DB
342config RTC_DRV_DS1305
343 tristate "Dallas/Maxim DS1305/DS1306"
344 help
345 Select this driver to get support for the Dallas/Maxim DS1305
ae64d169 346 and DS1306 real time clock chips. These support a trickle
53e84b67
DB
347 charger, alarms, and NVRAM in addition to the clock.
348
349 This driver can also be built as a module. If so, the module
350 will be called rtc-ds1305.
351
06de1808
MJ
352config RTC_DRV_DS1390
353 tristate "Dallas/Maxim DS1390/93/94"
354 help
7b9b2ef1
AZ
355 If you say yes here you get support for the
356 Dallas/Maxim DS1390/93/94 chips.
06de1808
MJ
357
358 This driver only supports the RTC feature, and not other chip
359 features such as alarms and trickle charging.
360
361 This driver can also be built as a module. If so, the module
362 will be called rtc-ds1390.
363
09b6bdb3
AZ
364config RTC_DRV_MAX6902
365 tristate "Maxim MAX6902"
366 help
367 If you say yes here you will get support for the
368 Maxim MAX6902 SPI RTC chip.
369
370 This driver can also be built as a module. If so, the module
371 will be called rtc-max6902.
372
2805b969
MD
373config RTC_DRV_R9701
374 tristate "Epson RTC-9701JE"
375 help
376 If you say yes here you will get support for the
377 Epson RTC-9701JE SPI RTC chip.
378
379 This driver can also be built as a module. If so, the module
380 will be called rtc-r9701.
381
e0ac4761
AN
382config RTC_DRV_RS5C348
383 tristate "Ricoh RS5C348A/B"
e0ac4761
AN
384 help
385 If you say yes here you get support for the
386 Ricoh RS5C348A and RS5C348B RTC chips.
387
388 This driver can also be built as a module. If so, the module
389 will be called rtc-rs5c348.
390
2f9b75e0
DA
391config RTC_DRV_DS3234
392 tristate "Maxim/Dallas DS3234"
393 help
394 If you say yes here you get support for the
395 Maxim/Dallas DS3234 SPI RTC chip.
396
397 This driver can also be built as a module. If so, the module
398 will be called rtc-ds3234.
399
7f3923a1
CV
400config RTC_DRV_PCF2123
401 tristate "NXP PCF2123"
402 help
403 If you say yes here you get support for the NXP PCF2123
404 RTC chip.
405
406 This driver can also be built as a module. If so, the module
407 will be called rtc-pcf2123.
408
bb35fb20
JE
409endif # SPI_MASTER
410
09a21e56 411comment "Platform RTC drivers"
09a21e56
AZ
412
413# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
414# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
415# global rtc_lock ... it's not yet just another platform_device.
416
417config RTC_DRV_CMOS
418 tristate "PC-style 'CMOS'"
5ec87708 419 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
c7500900 420 default y if X86
09a21e56
AZ
421 help
422 Say "yes" here to get direct support for the real time clock
423 found in every PC or ACPI-based system, and some other boards.
424 Specifically the original MC146818, compatibles like those in
425 PC south bridges, the DS12887 or M48T86, some multifunction
426 or LPC bus chips, and so on.
427
428 Your system will need to define the platform device used by
ae64d169 429 this driver, otherwise it won't be accessible. This means
09a21e56
AZ
430 you can safely enable this driver if you don't know whether
431 or not your board has this kind of hardware.
432
433 This driver can also be built as a module. If so, the module
434 will be called rtc-cmos.
435
537739de
TB
436config RTC_DRV_DS1216
437 tristate "Dallas DS1216"
bb35fb20 438 depends on SNI_RM
537739de
TB
439 help
440 If you say yes here you get support for the Dallas DS1216 RTC chips.
441
5f119f29
TB
442config RTC_DRV_DS1286
443 tristate "Dallas DS1286"
444 help
445 If you say yes here you get support for the Dallas DS1286 RTC chips.
446
739d340d
PM
447config RTC_DRV_DS1302
448 tristate "Dallas DS1302"
449 depends on SH_SECUREEDGE5410
450 help
451 If you say yes here you get support for the Dallas DS1302 RTC chips.
452
8f26795a
AS
453config RTC_DRV_DS1511
454 tristate "Dallas DS1511"
455 depends on RTC_CLASS
456 help
457 If you say yes here you get support for the
458 Dallas DS1511 timekeeping/watchdog chip.
459
460 This driver can also be built as a module. If so, the module
461 will be called rtc-ds1511.
462
09a21e56 463config RTC_DRV_DS1553
09b6bdb3 464 tristate "Maxim/Dallas DS1553"
7520b94d
AZ
465 help
466 If you say yes here you get support for the
09b6bdb3 467 Maxim/Dallas DS1553 timekeeping chip.
7520b94d
AZ
468
469 This driver can also be built as a module. If so, the module
09a21e56
AZ
470 will be called rtc-ds1553.
471
09b6bdb3
AZ
472config RTC_DRV_DS1742
473 tristate "Maxim/Dallas DS1742/1743"
02964115
TH
474 help
475 If you say yes here you get support for the
09b6bdb3 476 Maxim/Dallas DS1742/1743 timekeeping chip.
02964115
TH
477
478 This driver can also be built as a module. If so, the module
09b6bdb3 479 will be called rtc-ds1742.
02964115 480
5e3fd9e5 481config RTC_DRV_EFI
482 tristate "EFI RTC"
483 depends on IA64
484 help
485 If you say yes here you will get support for the EFI
486 Real Time Clock.
487
488 This driver can also be built as a module. If so, the module
489 will be called rtc-efi.
490
09b6bdb3
AZ
491config RTC_DRV_STK17TA8
492 tristate "Simtek STK17TA8"
493 depends on RTC_CLASS
09a21e56
AZ
494 help
495 If you say yes here you get support for the
09b6bdb3 496 Simtek STK17TA8 timekeeping chip.
09a21e56
AZ
497
498 This driver can also be built as a module. If so, the module
09b6bdb3 499 will be called rtc-stk17ta8.
09a21e56
AZ
500
501config RTC_DRV_M48T86
502 tristate "ST M48T86/Dallas DS12887"
09a21e56
AZ
503 help
504 If you say Y here you will get support for the
505 ST M48T86 and Dallas DS12887 RTC chips.
506
507 This driver can also be built as a module. If so, the module
508 will be called rtc-m48t86.
509
d1dbd82e
TB
510config RTC_DRV_M48T35
511 tristate "ST M48T35"
512 help
513 If you say Y here you will get support for the
514 ST M48T35 RTC chip.
515
516 This driver can also be built as a module, if so, the module
517 will be called "rtc-m48t35".
518
2e774c7c 519config RTC_DRV_M48T59
94fe7424 520 tristate "ST M48T59/M48T08/M48T02"
2e774c7c
MZ
521 help
522 If you say Y here you will get support for the
94fe7424
KH
523 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
524
525 These chips are usually found in Sun SPARC and UltraSPARC
526 workstations.
2e774c7c
MZ
527
528 This driver can also be built as a module, if so, the module
529 will be called "rtc-m48t59".
530
4f9b9bba
GU
531config RTC_DRV_MSM6242
532 tristate "Oki MSM6242"
533 help
534 If you say yes here you get support for the Oki MSM6242
535 timekeeping chip. It is used in some Amiga models (e.g. A2000).
536
537 This driver can also be built as a module. If so, the module
538 will be called rtc-msm6242.
539
eba54546
BS
540config RTC_DRV_IMXDI
541 tristate "Freescale IMX DryIce Real Time Clock"
542 depends on ARCH_MX25
543 depends on RTC_CLASS
544 help
545 Support for Freescale IMX DryIce RTC
546
547 This driver can also be built as a module, if so, the module
548 will be called "rtc-imxdi".
549
d00ed3cf
DM
550config RTC_MXC
551 tristate "Freescale MXC Real Time Clock"
552 depends on ARCH_MXC
553 depends on RTC_CLASS
554 help
555 If you say yes here you get support for the Freescale MXC
556 RTC module.
557
558 This driver can also be built as a module, if so, the module
559 will be called "rtc-mxc".
560
cca4c231
DM
561config RTC_DRV_BQ4802
562 tristate "TI BQ4802"
563 help
564 If you say Y here you will get support for the TI
565 BQ4802 RTC chip.
566
567 This driver can also be built as a module. If so, the module
568 will be called rtc-bq4802.
569
4f672ce2
GU
570config RTC_DRV_RP5C01
571 tristate "Ricoh RP5C01"
572 help
573 If you say yes here you get support for the Ricoh RP5C01
574 timekeeping chip. It is used in some Amiga models (e.g. A3000
575 and A4000).
576
577 This driver can also be built as a module. If so, the module
578 will be called rtc-rp5c01.
579
09a21e56
AZ
580config RTC_DRV_V3020
581 tristate "EM Microelectronic V3020"
09a21e56
AZ
582 help
583 If you say yes here you will get support for the
584 EM Microelectronic v3020 RTC chip.
585
586 This driver can also be built as a module. If so, the module
587 will be called rtc-v3020.
588
35c86bf6
MB
589config RTC_DRV_WM831X
590 tristate "Wolfson Microelectronics WM831x RTC"
591 depends on MFD_WM831X
592 help
593 If you say yes here you will get support for the RTC subsystem
594 of the Wolfson Microelectronics WM831X series PMICs.
595
596 This driver can also be built as a module. If so, the module
597 will be called "rtc-wm831x".
598
077eaf5b
MB
599config RTC_DRV_WM8350
600 tristate "Wolfson Microelectronics WM8350 RTC"
601 depends on MFD_WM8350
602 help
603 If you say yes here you will get support for the RTC subsystem
604 of the Wolfson Microelectronics WM8350.
605
606 This driver can also be built as a module. If so, the module
607 will be called "rtc-wm8350".
608
eae854b2
BR
609config RTC_DRV_PCF50633
610 depends on MFD_PCF50633
611 tristate "NXP PCF50633 RTC"
612 help
613 If you say yes here you get support for the RTC subsystem of the
614 NXP PCF50633 used in embedded systems.
615
bd207cfb
LW
616config RTC_DRV_AB3100
617 tristate "ST-Ericsson AB3100 RTC"
618 depends on AB3100_CORE
619 default y if AB3100_CORE
620 help
621 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
622 support. This chip contains a battery- and capacitor-backed RTC.
623
0af62f4d
VS
624config RTC_DRV_AB8500
625 tristate "ST-Ericsson AB8500 RTC"
626 depends on AB8500_CORE
627 help
628 Select this to enable the ST-Ericsson AB8500 power management IC RTC
629 support. This chip contains a battery- and capacitor-backed RTC.
630
afd49a7e
WZ
631config RTC_DRV_NUC900
632 tristate "NUC910/NUC920 RTC driver"
633 depends on RTC_CLASS && ARCH_W90X900
634 help
635 If you say yes here you get support for the RTC subsystem of the
636 NUC910/NUC920 used in embedded systems.
bd207cfb 637
09a21e56 638comment "on-CPU RTC drivers"
09a21e56 639
8ecf6c54
MA
640config RTC_DRV_DAVINCI
641 tristate "TI DaVinci RTC"
642 depends on ARCH_DAVINCI_DM365
643 help
644 If you say yes here you get support for the RTC on the
645 DaVinci platforms (DM365).
646
647 This driver can also be built as a module. If so, the module
648 will be called rtc-davinci.
649
09a21e56
AZ
650config RTC_DRV_OMAP
651 tristate "TI OMAP1"
8cfde8c1 652 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
09a21e56 653 help
8cfde8c1
MG
654 Say "yes" here to support the real time clock on TI OMAP1 and
655 DA8xx/OMAP-L13x chips. This driver can also be built as a
656 module called rtc-omap.
7520b94d 657
1add6781
BD
658config RTC_DRV_S3C
659 tristate "Samsung S3C series SoC RTC"
9f4123b7 660 depends on ARCH_S3C2410 || ARCH_S3C64XX
1add6781
BD
661 help
662 RTC (Realtime Clock) driver for the clock inbuilt into the
663 Samsung S3C24XX series of SoCs. This can provide periodic
664 interrupt rates from 1Hz to 64Hz for user programs, and
665 wakeup from Alarm.
666
667 The driver currently supports the common features on all the
668 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
669 and S3C2442.
670
671 This driver can also be build as a module. If so, the module
672 will be called rtc-s3c.
673
fd507e2f
AZ
674config RTC_DRV_EP93XX
675 tristate "Cirrus Logic EP93XX"
bb35fb20 676 depends on ARCH_EP93XX
fd507e2f
AZ
677 help
678 If you say yes here you get support for the
679 RTC embedded in the Cirrus Logic EP93XX processors.
680
681 This driver can also be built as a module. If so, the module
682 will be called rtc-ep93xx.
683
e842f1c8
RP
684config RTC_DRV_SA1100
685 tristate "SA11x0/PXA2xx"
bb35fb20 686 depends on ARCH_SA1100 || ARCH_PXA
e842f1c8
RP
687 help
688 If you say Y here you will get access to the real time clock
689 built into your SA11x0 or PXA2xx CPU.
690
691 To compile this driver as a module, choose M here: the
692 module will be called rtc-sa1100.
fd507e2f 693
317a6104
PM
694config RTC_DRV_SH
695 tristate "SuperH On-Chip RTC"
063adc75 696 depends on RTC_CLASS && SUPERH && HAVE_CLK
317a6104
PM
697 help
698 Say Y here to enable support for the on-chip RTC found in
699 most SuperH processors.
700
701 To compile this driver as a module, choose M here: the
702 module will be called rtc-sh.
703
8417eb7a 704config RTC_DRV_VR41XX
3e16f6af 705 tristate "NEC VR41XX"
bb35fb20 706 depends on CPU_VR41XX
3e16f6af
AZ
707 help
708 If you say Y here you will get access to the real time clock
709 built into your NEC VR41XX CPU.
710
711 To compile this driver as a module, choose M here: the
712 module will be called rtc-vr41xx.
8417eb7a 713
a190901c
RK
714config RTC_DRV_PL030
715 tristate "ARM AMBA PL030 RTC"
716 depends on ARM_AMBA
717 help
718 If you say Y here you will get access to ARM AMBA
719 PrimeCell PL030 RTC found on certain ARM SOCs.
720
721 To compile this driver as a module, choose M here: the
722 module will be called rtc-pl030.
723
8ae6e163
DS
724config RTC_DRV_PL031
725 tristate "ARM AMBA PL031 RTC"
bb35fb20 726 depends on ARM_AMBA
8ae6e163
DS
727 help
728 If you say Y here you will get access to ARM AMBA
09a21e56 729 PrimeCell PL031 RTC found on certain ARM SOCs.
8ae6e163
DS
730
731 To compile this driver as a module, choose M here: the
732 module will be called rtc-pl031.
733
fa04e78b
HCE
734config RTC_DRV_AT32AP700X
735 tristate "AT32AP700X series RTC"
bb35fb20 736 depends on PLATFORM_AT32AP
fa04e78b
HCE
737 help
738 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
739 AT32AP700x family processors.
740
7fc39f6d 741config RTC_DRV_AT91RM9200
4cdf854f
DB
742 tristate "AT91RM9200 or AT91SAM9RL"
743 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
744 help
745 Driver for the internal RTC (Realtime Clock) module found on
ae64d169 746 Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips
4cdf854f
DB
747 this is powered by the backup power supply.
748
749config RTC_DRV_AT91SAM9
6b71dbf6 750 tristate "AT91SAM9x/AT91CAP9"
4cdf854f
DB
751 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
752 help
6b71dbf6
SP
753 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
754 (Real Time Timer). These timers are powered by the backup power
755 supply (such as a small coin cell battery), but do not need to
756 be used as RTCs.
4cdf854f
DB
757
758 (On AT91SAM9rl chips you probably want to use the dedicated RTC
759 module and leave the RTT available for other uses.)
760
761config RTC_DRV_AT91SAM9_RTT
762 int
763 range 0 1
764 default 0
765 prompt "RTT module Number" if ARCH_AT91SAM9263
766 depends on RTC_DRV_AT91SAM9
767 help
ae64d169
AZ
768 More than one RTT module is available. You can choose which
769 one will be used as an RTC. The default of zero is normally
4cdf854f
DB
770 OK to use, though some systems use that for non-RTC purposes.
771
772config RTC_DRV_AT91SAM9_GPBR
773 int
774 range 0 3 if !ARCH_AT91SAM9263
775 range 0 15 if ARCH_AT91SAM9263
776 default 0
777 prompt "Backup Register Number"
778 depends on RTC_DRV_AT91SAM9
779 help
780 The RTC driver needs to use one of the General Purpose Backup
ae64d169
AZ
781 Registers (GPBRs) as well as the RTT. You can choose which one
782 will be used. The default of zero is normally OK to use, but
4cdf854f 783 on some systems other software needs to use that register.
788b1fc6 784
45fd8a0c
ML
785config RTC_DRV_AU1XXX
786 tristate "Au1xxx Counter0 RTC support"
42a4f17d 787 depends on MIPS_ALCHEMY
45fd8a0c
ML
788 help
789 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
790 counter) to be used as a RTC.
791
792 This driver can also be built as a module. If so, the module
793 will be called rtc-au1xxx.
794
8cc75c9a
WB
795config RTC_DRV_BFIN
796 tristate "Blackfin On-Chip RTC"
7f604599 797 depends on BLACKFIN && !BF561
8cc75c9a
WB
798 help
799 If you say yes here you will get support for the
800 Blackfin On-Chip Real Time Clock.
801
802 This driver can also be built as a module. If so, the module
803 will be called rtc-bfin.
804
e9f2bd81
NI
805config RTC_DRV_RS5C313
806 tristate "Ricoh RS5C313"
bb35fb20 807 depends on SH_LANDISK
e9f2bd81
NI
808 help
809 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
810
3afe6d04
GU
811config RTC_DRV_GENERIC
812 tristate "Generic RTC support"
813 # Please consider writing a new RTC driver instead of using the generic
814 # RTC abstraction
47c8a08b 815 depends on PARISC || M68K || PPC || SUPERH32
9eb16864 816 help
3afe6d04
GU
817 Say Y or M here to enable RTC support on systems using the generic
818 RTC abstraction. If you do not know what you are doing, you should
9eb16864
KM
819 just say Y.
820
dc944368
RJ
821config RTC_DRV_PXA
822 tristate "PXA27x/PXA3xx"
823 depends on ARCH_PXA
824 help
825 If you say Y here you will get access to the real time clock
826 built into your PXA27x or PXA3xx CPU.
827
828 This RTC driver uses PXA RTC registers available since pxa27x
829 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
830
831
7a138ede
DM
832config RTC_DRV_SUN4V
833 bool "SUN4V Hypervisor RTC"
834 depends on SPARC64
835 help
836 If you say Y here you will get support for the Hypervisor
837 based RTC on SUN4V systems.
838
de2cf332
DM
839config RTC_DRV_STARFIRE
840 bool "Starfire RTC"
841 depends on SPARC64
842 help
843 If you say Y here you will get support for the RTC found on
844 Starfire systems.
845
0e149233
AN
846config RTC_DRV_TX4939
847 tristate "TX4939 SoC"
848 depends on SOC_TX4939
849 help
850 Driver for the internal RTC (Realtime Clock) module found on
851 Toshiba TX4939 SoC.
852
defb4514
SB
853config RTC_DRV_MV
854 tristate "Marvell SoC RTC"
da43243e 855 depends on ARCH_KIRKWOOD || ARCH_DOVE
defb4514
SB
856 help
857 If you say yes here you will get support for the in-chip RTC
858 that can be found in some of Marvell's SoC devices, such as
859 the Kirkwood 88F6281 and 88F6192.
860
861 This driver can also be built as a module. If so, the module
862 will be called rtc-mv.
863
0b5f037a
GU
864config RTC_DRV_PS3
865 tristate "PS3 RTC"
866 depends on PPC_PS3
867 help
868 If you say yes here you will get support for the RTC on PS3.
869
870 This driver can also be built as a module. If so, the module
871 will be called rtc-ps3.
872
aa958f57
LW
873config RTC_DRV_COH901331
874 tristate "ST-Ericsson COH 901 331 RTC"
875 depends on ARCH_U300
876 help
877 If you say Y here you will get access to ST-Ericsson
878 COH 901 331 RTC clock found in some ST-Ericsson Mobile
879 Platforms.
880
881 This driver can also be built as a module. If so, the module
882 will be called "rtc-coh901331".
883
884
df17f631 885config RTC_DRV_STMP
886 tristate "Freescale STMP3xxx RTC"
887 depends on ARCH_STMP3XXX
888 help
889 If you say yes here you will get support for the onboard
890 STMP3xxx RTC.
891
892 This driver can also be built as a module. If so, the module
893 will be called rtc-stmp3xxx.
894
d3c7a3f7
DR
895config RTC_DRV_PCAP
896 tristate "PCAP RTC"
897 depends on EZX_PCAP
898 help
899 If you say Y here you will get support for the RTC found on
900 the PCAP2 ASIC used on some Motorola phones.
901
43299f28
UKK
902config RTC_DRV_MC13783
903 depends on MFD_MC13783
904 tristate "Freescale MC13783 RTC"
905 help
906 This enables support for the Freescale MC13783 PMIC RTC
907
50aae724
AG
908config RTC_DRV_MPC5121
909 tristate "Freescale MPC5121 built-in RTC"
910 depends on PPC_MPC512x && RTC_CLASS
911 help
912 If you say yes here you will get support for the
913 built-in RTC MPC5121.
914
915 This driver can also be built as a module. If so, the module
916 will be called rtc-mpc5121.
917
3bf0eea8
LPC
918config RTC_DRV_JZ4740
919 tristate "Ingenic JZ4740 SoC"
920 depends on RTC_CLASS
921 depends on MACH_JZ4740
922 help
923 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
924 controller.
925
926 This driver can also be buillt as a module. If so, the module
927 will be called rtc-jz4740.
928
bb35fb20 929endif # RTC_CLASS
This page took 0.818113 seconds and 5 git commands to generate.