drivers/rtc/rtc-ds1343.c: fix potential race condition
[deliverable/linux.git] / drivers / rtc / Kconfig
CommitLineData
7be2c7c9 1#
c58411e9
AZ
2# RTC class/drivers configuration
3#
4
5config RTC_LIB
b4d246b1 6 bool
0c86edc0 7
bb35fb20 8menuconfig RTC_CLASS
b4d246b1 9 bool "Real Time Clock"
0c86edc0 10 default n
3369465e 11 depends on !S390 && !UML
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 17
bb35fb20
JE
18if RTC_CLASS
19
0c86edc0 20config RTC_HCTOSYS
7ca1d488 21 bool "Set system time from RTC on startup and resume"
0c86edc0
AZ
22 default y
23 help
7ca1d488
DB
24 If you say yes here, the system time (wall clock) will be set using
25 the value read from a specified RTC device. This is useful to avoid
26 unnecessary fsck runs at boot time, and to network better.
0c86edc0 27
023f333a
JG
28config RTC_SYSTOHC
29 bool "Set the RTC time based on NTP synchronization"
30 default y
31 help
32 If you say yes here, the system time (wall clock) will be stored
33 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
34 minutes if userspace reports synchronized NTP status.
35
0c86edc0 36config RTC_HCTOSYS_DEVICE
7ca1d488 37 string "RTC used to set the system time"
023f333a 38 depends on RTC_HCTOSYS = y || RTC_SYSTOHC = y
0c86edc0
AZ
39 default "rtc0"
40 help
7ca1d488 41 The RTC device that will be used to (re)initialize the system
ae64d169
AZ
42 clock, usually rtc0. Initialization is done when the system
43 starts up, and when it resumes from a low power state. This
779d2089
DB
44 device should record time in UTC, since the kernel won't do
45 timezone correction.
7ca1d488 46
55ff1aba
DB
47 The driver for this RTC device must be loaded before late_initcall
48 functions run, so it must usually be statically linked.
49
7ca1d488 50 This clock should be battery-backed, so that it reads the correct
ae64d169 51 time when the system boots from a power-off state. Otherwise, your
7ca1d488
DB
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
09b6bdb3 56 sleep states. Do not specify an RTC here unless it stays powered
7ca1d488 57 during all this system's supported sleep states.
0c86edc0 58
9e86ecb6
DB
59config RTC_DEBUG
60 bool "RTC debug support"
9e86ecb6
DB
61 help
62 Say yes here to enable debugging support in the RTC framework
63 and individual RTC drivers.
64
0c86edc0 65comment "RTC interfaces"
0c86edc0 66
c5c3e192 67config RTC_INTF_SYSFS
e40659c5 68 boolean "/sys/class/rtc/rtcN (sysfs)"
bb35fb20 69 depends on SYSFS
8dc08395 70 default RTC_CLASS
c5c3e192 71 help
9e86ecb6
DB
72 Say yes here if you want to use your RTCs using sysfs interfaces,
73 /sys/class/rtc/rtc0 through /sys/.../rtcN.
c5c3e192 74
ae64d169 75 If unsure, say Y.
c5c3e192 76
728a2947 77config RTC_INTF_PROC
92589c98 78 boolean "/proc/driver/rtc (procfs for rtcN)"
bb35fb20 79 depends on PROC_FS
8dc08395 80 default RTC_CLASS
728a2947 81 help
92589c98
KM
82 Say yes here if you want to use your system clock RTC through
83 the proc interface, /proc/driver/rtc.
84 Other RTCs will not be available through that API.
85 If there is no RTC for the system clock, then the first RTC(rtc0)
86 is used by default.
728a2947 87
ae64d169 88 If unsure, say Y.
728a2947 89
e824290e 90config RTC_INTF_DEV
e40659c5 91 boolean "/dev/rtcN (character devices)"
8dc08395 92 default RTC_CLASS
e824290e 93 help
9e86ecb6
DB
94 Say yes here if you want to use your RTCs using the /dev
95 interfaces, which "udev" sets up as /dev/rtc0 through
ae64d169 96 /dev/rtcN.
e824290e 97
ae64d169
AZ
98 You may want to set up a symbolic link so one of these
99 can be accessed as /dev/rtc, which is a name
100 expected by "hwclock" and some other programs. Recent
101 versions of "udev" are known to set up the symlink for you.
102
103 If unsure, say Y.
e824290e 104
6e57b1d6
JS
105config RTC_INTF_DEV_UIE_EMUL
106 bool "RTC UIE emulation on dev interface"
107 depends on RTC_INTF_DEV
108 help
109 Provides an emulation for RTC_UIE if the underlying rtc chip
110 driver does not expose RTC_UIE ioctls. Those requests generate
111 once-per-second update interrupts, used for synchronization.
112
113 The emulation code will read the time from the hardware
114 clock several times per second, please enable this option
115 only if you know that you really need it.
116
09a21e56
AZ
117config RTC_DRV_TEST
118 tristate "Test driver/device"
1fec7c66
AZ
119 help
120 If you say yes here you get support for the
09a21e56
AZ
121 RTC test driver. It's a software RTC which can be
122 used to test the RTC subsystem APIs. It gets
123 the time from the system clock.
124 You want this driver only if you are doing development
125 on the RTC subsystem. Please read the source code
126 for further details.
1fec7c66
AZ
127
128 This driver can also be built as a module. If so, the module
09a21e56
AZ
129 will be called rtc-test.
130
131comment "I2C RTC drivers"
bb35fb20
JE
132 depends on I2C
133
134if I2C
1fec7c66 135
008b3040
HZ
136config RTC_DRV_88PM860X
137 tristate "Marvell 88PM860x"
6b8029fa 138 depends on I2C && MFD_88PM860X
008b3040
HZ
139 help
140 If you say yes here you get support for RTC function in Marvell
141 88PM860x chips.
142
143 This driver can also be built as a module. If so, the module
144 will be called rtc-88pm860x.
145
2985c29c
QZ
146config RTC_DRV_88PM80X
147 tristate "Marvell 88PM80x"
6b8029fa 148 depends on I2C && MFD_88PM800
2985c29c
QZ
149 help
150 If you say yes here you get support for RTC function in Marvell
151 88PM80x chips.
152
153 This driver can also be built as a module. If so, the module
154 will be called rtc-88pm80x.
155
b4506261
LD
156config RTC_DRV_AS3722
157 tristate "ams AS3722 RTC driver"
158 depends on MFD_AS3722
159 help
160 If you say yes here you get support for the RTC of ams AS3722 PMIC
161 chips.
162
163 This driver can also be built as a module. If so, the module
164 will be called rtc-as3722.
165
1abb0dc9 166config RTC_DRV_DS1307
a2166858 167 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
1abb0dc9
DB
168 help
169 If you say yes here you get support for various compatible RTC
ae64d169 170 chips (often with battery backup) connected with I2C. This driver
1abb0dc9 171 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
a2166858
MF
172 EPSON RX-8025 and probably other chips. In some cases the RTC
173 must already have been initialized (by manufacturing or a
174 bootloader).
1abb0dc9
DB
175
176 The first seven registers on these chips hold an RTC, and other
177 registers may add features such as NVRAM, a trickle charger for
ae64d169 178 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
682d73f6 179 sysfs, but other chip features may not be available.
1abb0dc9
DB
180
181 This driver can also be built as a module. If so, the module
182 will be called rtc-ds1307.
183
bf4994d7 184config RTC_DRV_DS1374
09b6bdb3 185 tristate "Dallas/Maxim DS1374"
6b8029fa 186 depends on I2C
bf4994d7
SW
187 help
188 If you say yes here you get support for Dallas Semiconductor
ae64d169 189 DS1374 real-time clock chips. If an interrupt is associated
bf4994d7
SW
190 with the device, the alarm functionality is supported.
191
ae64d169 192 This driver can also be built as a module. If so, the module
bf4994d7
SW
193 will be called rtc-ds1374.
194
09a21e56
AZ
195config RTC_DRV_DS1672
196 tristate "Dallas/Maxim DS1672"
9bf5b4f5
AN
197 help
198 If you say yes here you get support for the
09a21e56 199 Dallas/Maxim DS1672 timekeeping chip.
9bf5b4f5
AN
200
201 This driver can also be built as a module. If so, the module
09a21e56 202 will be called rtc-ds1672.
9bf5b4f5 203
c03675f0
RZ
204config RTC_DRV_DS3232
205 tristate "Dallas/Maxim DS3232"
6b8029fa 206 depends on I2C
c03675f0
RZ
207 help
208 If you say yes here you get support for Dallas Semiconductor
f46418c5
LCB
209 DS3232 real-time clock chips. If an interrupt is associated
210 with the device, the alarm functionality is supported.
c03675f0
RZ
211
212 This driver can also be built as a module. If so, the module
213 will be called rtc-ds3232.
214
dcaf0384
HS
215config RTC_DRV_HYM8563
216 tristate "Haoyu Microelectronics HYM8563"
217 depends on I2C && OF
218 help
219 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
220 from the usual rtc functions it provides a clock output of
221 up to 32kHz.
222
223 This driver can also be built as a module. If so, the module
224 will be called rtc-hym8563.
225
38ae176e
KM
226config RTC_DRV_LP8788
227 tristate "TI LP8788 RTC driver"
228 depends on MFD_LP8788
229 help
230 Say Y to enable support for the LP8788 RTC/ALARM driver.
231
09a21e56 232config RTC_DRV_MAX6900
09b6bdb3 233 tristate "Maxim MAX6900"
7e56a7dc 234 help
09a21e56
AZ
235 If you say yes here you will get support for the
236 Maxim MAX6900 I2C RTC chip.
7e56a7dc
HVR
237
238 This driver can also be built as a module. If so, the module
09a21e56 239 will be called rtc-max6900.
7e56a7dc 240
94c01ab6
SW
241config RTC_DRV_MAX8907
242 tristate "Maxim MAX8907"
243 depends on MFD_MAX8907
244 help
245 If you say yes here you will get support for the
246 RTC of Maxim MAX8907 PMIC.
247
248 This driver can also be built as a module. If so, the module
249 will be called rtc-max8907.
250
a39069f6
HZ
251config RTC_DRV_MAX8925
252 tristate "Maxim MAX8925"
253 depends on MFD_MAX8925
254 help
255 If you say yes here you will get support for the
256 RTC of Maxim MAX8925 PMIC.
257
258 This driver can also be built as a module. If so, the module
259 will be called rtc-max8925.
260
9b16c0a4
JS
261config RTC_DRV_MAX8998
262 tristate "Maxim MAX8998"
263 depends on MFD_MAX8998
264 help
265 If you say yes here you will get support for the
266 RTC of Maxim MAX8998 PMIC.
267
268 This driver can also be built as a module. If so, the module
269 will be called rtc-max8998.
270
5e0b2704
JL
271config RTC_DRV_MAX8997
272 tristate "Maxim MAX8997"
273 depends on MFD_MAX8997
274 help
275 If you say yes here you will get support for the
276 RTC of Maxim MAX8997 PMIC.
277
278 This driver can also be built as a module. If so, the module
279 will be called rtc-max8997.
280
fca1dd03
JL
281config RTC_DRV_MAX77686
282 tristate "Maxim MAX77686"
283 depends on MFD_MAX77686
284 help
285 If you say yes here you will get support for the
286 RTC of Maxim MAX77686 PMIC.
287
288 This driver can also be built as a module. If so, the module
289 will be called rtc-max77686.
290
09a21e56 291config RTC_DRV_RS5C372
5d4529be 292 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
edf1aaa3
AZ
293 help
294 If you say yes here you get support for the
5d4529be 295 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
edf1aaa3
AZ
296
297 This driver can also be built as a module. If so, the module
09a21e56 298 will be called rtc-rs5c372.
edf1aaa3 299
09a21e56 300config RTC_DRV_ISL1208
09b6bdb3 301 tristate "Intersil ISL1208"
5ec3e4b7
AN
302 help
303 If you say yes here you get support for the
09b6bdb3 304 Intersil ISL1208 RTC chip.
5ec3e4b7
AN
305
306 This driver can also be built as a module. If so, the module
09a21e56 307 will be called rtc-isl1208.
5ec3e4b7 308
d6c7428f
RF
309config RTC_DRV_ISL12022
310 tristate "Intersil ISL12022"
311 help
312 If you say yes here you get support for the
313 Intersil ISL12022 RTC chip.
314
315 This driver can also be built as a module. If so, the module
316 will be called rtc-isl12022.
317
70e12337
AE
318config RTC_DRV_ISL12057
319 depends on I2C
320 select REGMAP_I2C
321 tristate "Intersil ISL12057"
322 help
323 If you say yes here you get support for the Intersil ISL12057
324 I2C RTC chip.
325
326 This driver can also be built as a module. If so, the module
327 will be called rtc-isl12057.
328
09a21e56
AZ
329config RTC_DRV_X1205
330 tristate "Xicor/Intersil X1205"
db68b189 331 help
09a21e56
AZ
332 If you say yes here you get support for the
333 Xicor/Intersil X1205 RTC chip.
334
335 This driver can also be built as a module. If so, the module
336 will be called rtc-x1205.
db68b189 337
0101e53c
LD
338config RTC_DRV_PALMAS
339 tristate "TI Palmas RTC driver"
340 depends on MFD_PALMAS
341 help
342 If you say yes here you get support for the RTC of TI PALMA series PMIC
343 chips.
344
345 This driver can also be built as a module. If so, the module
346 will be called rtc-palma.
347
18cb6368
RC
348config RTC_DRV_PCF2127
349 tristate "NXP PCF2127"
350 help
351 If you say yes here you get support for the NXP PCF2127/29 RTC
352 chips.
353
354 This driver can also be built as a module. If so, the module
355 will be called rtc-pcf2127.
356
f803f0d0
TR
357config RTC_DRV_PCF8523
358 tristate "NXP PCF8523"
359 help
360 If you say yes here you get support for the NXP PCF8523 RTC
361 chips.
362
363 This driver can also be built as a module. If so, the module
364 will be called rtc-pcf8523.
365
b5a82d62
AZ
366config RTC_DRV_PCF8563
367 tristate "Philips PCF8563/Epson RTC8564"
b5a82d62
AZ
368 help
369 If you say yes here you get support for the
370 Philips PCF8563 RTC chip. The Epson RTC8564
371 should work as well.
372
373 This driver can also be built as a module. If so, the module
374 will be called rtc-pcf8563.
375
9c0c5705
L
376config RTC_DRV_PCF8583
377 tristate "Philips PCF8583"
9c0c5705 378 help
bb71f99f 379 If you say yes here you get support for the Philips PCF8583
09a21e56 380 RTC chip found on Acorn RiscPCs. This driver supports the
bb71f99f 381 platform specific method of retrieving the current year from
09a21e56
AZ
382 the RTC's SRAM. It will work on other platforms with the same
383 chip, but the year will probably have to be tweaked.
9c0c5705
L
384
385 This driver can also be built as a module. If so, the module
386 will be called rtc-pcf8583.
387
caaff562 388config RTC_DRV_M41T80
6b1a5235 389 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
caaff562 390 help
d3a126fc
SF
391 If you say Y here you will get support for the ST M41T60
392 and M41T80 RTC chips series. Currently, the following chips are
f30281f4 393 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
6b1a5235 394 M41ST85, M41ST87, and MicroCrystal RV4162.
caaff562
AN
395
396 This driver can also be built as a module. If so, the module
397 will be called rtc-m41t80.
398
617780d2 399config RTC_DRV_M41T80_WDT
d3a126fc 400 bool "ST M41T65/M41T80 series RTC watchdog timer"
617780d2
AN
401 depends on RTC_DRV_M41T80
402 help
403 If you say Y here you will get support for the
d3a126fc 404 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
617780d2 405
1ce7c83f
PZ
406config RTC_DRV_BQ32K
407 tristate "TI BQ32000"
408 help
409 If you say Y here you will get support for the TI
410 BQ32000 I2C RTC chip.
411
412 This driver can also be built as a module. If so, the module
413 will be called rtc-bq32k.
414
afd8d0f9
DB
415config RTC_DRV_DM355EVM
416 tristate "TI DaVinci DM355 EVM RTC"
417 depends on MFD_DM355EVM_MSP
418 help
419 Supports the RTC firmware in the MSP430 on the DM355 EVM.
420
0c4a59fe
TL
421config RTC_DRV_TWL92330
422 boolean "TI TWL92330/Menelaus"
bb35fb20 423 depends on MENELAUS
0c4a59fe
TL
424 help
425 If you say yes here you get support for the RTC on the
01dd2fbf 426 TWL92330 "Menelaus" power management chip, used with OMAP2
ae64d169 427 platforms. The support is integrated with the rest of
0c4a59fe
TL
428 the Menelaus driver; it's not separate module.
429
f96411ab 430config RTC_DRV_TWL4030
a6b49ffd 431 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
6b8029fa 432 depends on TWL4030_CORE
f96411ab
DB
433 help
434 If you say yes here you get support for the RTC on the
a6b49ffd 435 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
f96411ab
DB
436
437 This driver can also be built as a module. If so, the module
a6b49ffd 438 will be called rtc-twl.
f96411ab 439
dc59ed38
LD
440config RTC_DRV_TPS6586X
441 tristate "TI TPS6586X RTC driver"
442 depends on MFD_TPS6586X
443 help
a895d57d 444 TI Power Management IC TPS6586X supports RTC functionality
dc59ed38
LD
445 along with alarm. This driver supports the RTC driver for
446 the TPS6586X RTC module.
447
0e783980
VB
448config RTC_DRV_TPS65910
449 tristate "TI TPS65910 RTC driver"
450 depends on RTC_CLASS && MFD_TPS65910
451 help
452 If you say yes here you get support for the RTC on the
453 TPS65910 chips.
454
455 This driver can also be built as a module. If so, the module
456 will be called rtc-tps65910.
457
36d61824
LD
458config RTC_DRV_TPS80031
459 tristate "TI TPS80031/TPS80032 RTC driver"
460 depends on MFD_TPS80031
461 help
a895d57d 462 TI Power Management IC TPS80031 supports RTC functionality
36d61824
LD
463 along with alarm. This driver supports the RTC driver for
464 the TPS80031 RTC module.
465
90829c08
VB
466config RTC_DRV_RC5T583
467 tristate "RICOH 5T583 RTC driver"
468 depends on MFD_RC5T583
469 help
470 If you say yes here you get support for the RTC on the
471 RICOH 5T583 chips.
472
473 This driver can also be built as a module. If so, the module
474 will be called rtc-rc5t583.
475
c46288b0
BB
476config RTC_DRV_S35390A
477 tristate "Seiko Instruments S-35390A"
d479540d 478 select BITREVERSE
c46288b0
BB
479 help
480 If you say yes here you will get support for the Seiko
481 Instruments S-35390A.
482
483 This driver can also be built as a module. If so the module
484 will be called rtc-s35390a.
485
c6d8f400
SL
486config RTC_DRV_FM3130
487 tristate "Ramtron FM3130"
488 help
489 If you say Y here you will get support for the
490 Ramtron FM3130 RTC chips.
491 Ramtron FM3130 is a chip with two separate devices inside,
492 RTC clock and FRAM. This driver provides only RTC functionality.
493
494 This driver can also be built as a module. If so the module
495 will be called rtc-fm3130.
496
a7fa9851
MW
497config RTC_DRV_RX8581
498 tristate "Epson RX-8581"
499 help
500 If you say yes here you will get support for the Epson RX-8581.
501
502 This driver can also be built as a module. If so the module
503 will be called rtc-rx8581.
504
3c2b9075
WG
505config RTC_DRV_RX8025
506 tristate "Epson RX-8025SA/NB"
507 help
508 If you say yes here you get support for the Epson
509 RX-8025SA/NB RTC chips.
510
511 This driver can also be built as a module. If so, the module
512 will be called rtc-rx8025.
513
ae3551f9
MR
514config RTC_DRV_EM3027
515 tristate "EM Microelectronic EM3027"
516 help
517 If you say yes here you get support for the EM
518 Microelectronic EM3027 RTC chips.
519
520 This driver can also be built as a module. If so, the module
521 will be called rtc-em3027.
522
52365230
HS
523config RTC_DRV_RV3029C2
524 tristate "Micro Crystal RTC"
525 help
526 If you say yes here you get support for the Micro Crystal
527 RV3029-C2 RTC chips.
528
529 This driver can also be built as a module. If so, the module
530 will be called rtc-rv3029c2.
531
5bccae6e
SK
532config RTC_DRV_S5M
533 tristate "Samsung S5M series"
534 depends on MFD_SEC_CORE
535 help
536 If you say yes here you will get support for the
537 RTC of Samsung S5M PMIC series.
538
539 This driver can also be built as a module. If so, the module
540 will be called rtc-s5m.
541
bb35fb20
JE
542endif # I2C
543
09a21e56 544comment "SPI RTC drivers"
bb35fb20
JE
545
546if SPI_MASTER
09a21e56 547
74d34d4b
VN
548config RTC_DRV_M41T93
549 tristate "ST M41T93"
550 help
551 If you say yes here you will get support for the
552 ST M41T93 SPI RTC chip.
553
554 This driver can also be built as a module. If so, the module
555 will be called rtc-m41t93.
556
8fc2c767
KH
557config RTC_DRV_M41T94
558 tristate "ST M41T94"
559 help
560 If you say yes here you will get support for the
561 ST M41T94 SPI RTC chip.
562
563 This driver can also be built as a module. If so, the module
564 will be called rtc-m41t94.
565
53e84b67
DB
566config RTC_DRV_DS1305
567 tristate "Dallas/Maxim DS1305/DS1306"
568 help
569 Select this driver to get support for the Dallas/Maxim DS1305
ae64d169 570 and DS1306 real time clock chips. These support a trickle
53e84b67
DB
571 charger, alarms, and NVRAM in addition to the clock.
572
573 This driver can also be built as a module. If so, the module
574 will be called rtc-ds1305.
575
1d6316f5 576config RTC_DRV_DS1343
0dd449b1 577 select REGMAP_SPI
1d6316f5
RG
578 tristate "Dallas/Maxim DS1343/DS1344"
579 help
580 If you say yes here you get support for the
581 Dallas/Maxim DS1343 and DS1344 real time clock chips.
582 Support for trickle charger, alarm is provided.
583
584 This driver can also be built as a module. If so, the module
585 will be called rtc-ds1343.
586
617b26a0
RG
587config RTC_DRV_DS1347
588 tristate "Dallas/Maxim DS1347"
589 help
590 If you say yes here you get support for the
591 Dallas/Maxim DS1347 chips.
592
593 This driver only supports the RTC feature, and not other chip
594 features such as alarms.
595
596 This driver can also be built as a module. If so, the module
597 will be called rtc-ds1347.
598
06de1808
MJ
599config RTC_DRV_DS1390
600 tristate "Dallas/Maxim DS1390/93/94"
601 help
7b9b2ef1
AZ
602 If you say yes here you get support for the
603 Dallas/Maxim DS1390/93/94 chips.
06de1808
MJ
604
605 This driver only supports the RTC feature, and not other chip
606 features such as alarms and trickle charging.
607
608 This driver can also be built as a module. If so, the module
609 will be called rtc-ds1390.
610
09b6bdb3
AZ
611config RTC_DRV_MAX6902
612 tristate "Maxim MAX6902"
613 help
614 If you say yes here you will get support for the
615 Maxim MAX6902 SPI RTC chip.
616
617 This driver can also be built as a module. If so, the module
618 will be called rtc-max6902.
619
2805b969
MD
620config RTC_DRV_R9701
621 tristate "Epson RTC-9701JE"
622 help
623 If you say yes here you will get support for the
624 Epson RTC-9701JE SPI RTC chip.
625
626 This driver can also be built as a module. If so, the module
627 will be called rtc-r9701.
628
e0ac4761
AN
629config RTC_DRV_RS5C348
630 tristate "Ricoh RS5C348A/B"
e0ac4761
AN
631 help
632 If you say yes here you get support for the
633 Ricoh RS5C348A and RS5C348B RTC chips.
634
635 This driver can also be built as a module. If so, the module
636 will be called rtc-rs5c348.
637
2f9b75e0
DA
638config RTC_DRV_DS3234
639 tristate "Maxim/Dallas DS3234"
640 help
641 If you say yes here you get support for the
642 Maxim/Dallas DS3234 SPI RTC chip.
643
644 This driver can also be built as a module. If so, the module
645 will be called rtc-ds3234.
646
7f3923a1
CV
647config RTC_DRV_PCF2123
648 tristate "NXP PCF2123"
649 help
650 If you say yes here you get support for the NXP PCF2123
651 RTC chip.
652
653 This driver can also be built as a module. If so, the module
654 will be called rtc-pcf2123.
655
cce2da9a
TH
656config RTC_DRV_RX4581
657 tristate "Epson RX-4581"
658 help
659 If you say yes here you will get support for the Epson RX-4581.
660
661 This driver can also be built as a module. If so the module
662 will be called rtc-rx4581.
663
bb35fb20
JE
664endif # SPI_MASTER
665
09a21e56 666comment "Platform RTC drivers"
09a21e56
AZ
667
668# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
669# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
670# global rtc_lock ... it's not yet just another platform_device.
671
672config RTC_DRV_CMOS
673 tristate "PC-style 'CMOS'"
41c9dbf4 674 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
c7500900 675 default y if X86
09a21e56
AZ
676 help
677 Say "yes" here to get direct support for the real time clock
678 found in every PC or ACPI-based system, and some other boards.
679 Specifically the original MC146818, compatibles like those in
680 PC south bridges, the DS12887 or M48T86, some multifunction
681 or LPC bus chips, and so on.
682
683 Your system will need to define the platform device used by
ae64d169 684 this driver, otherwise it won't be accessible. This means
09a21e56
AZ
685 you can safely enable this driver if you don't know whether
686 or not your board has this kind of hardware.
687
688 This driver can also be built as a module. If so, the module
689 will be called rtc-cmos.
690
85d0b3a5
RH
691config RTC_DRV_ALPHA
692 bool "Alpha PC-style CMOS"
693 depends on ALPHA
694 default y
695 help
696 Direct support for the real-time clock found on every Alpha
697 system, specifically MC146818 compatibles. If in doubt, say Y.
698
0146f261 699config RTC_DRV_VRTC
933b9463
AC
700 tristate "Virtual RTC for Intel MID platforms"
701 depends on X86_INTEL_MID
702 default y if X86_INTEL_MID
0146f261
FT
703
704 help
705 Say "yes" here to get direct support for the real time clock
706 found on Moorestown platforms. The VRTC is a emulated RTC that
707 derives its clock source from a real RTC in the PMIC. The MC146818
708 style programming interface is mostly conserved, but any
709 updates are done via IPC calls to the system controller FW.
710
537739de
TB
711config RTC_DRV_DS1216
712 tristate "Dallas DS1216"
bb35fb20 713 depends on SNI_RM
537739de
TB
714 help
715 If you say yes here you get support for the Dallas DS1216 RTC chips.
716
5f119f29
TB
717config RTC_DRV_DS1286
718 tristate "Dallas DS1286"
719 help
720 If you say yes here you get support for the Dallas DS1286 RTC chips.
721
739d340d
PM
722config RTC_DRV_DS1302
723 tristate "Dallas DS1302"
724 depends on SH_SECUREEDGE5410
725 help
726 If you say yes here you get support for the Dallas DS1302 RTC chips.
727
8f26795a
AS
728config RTC_DRV_DS1511
729 tristate "Dallas DS1511"
8f26795a
AS
730 help
731 If you say yes here you get support for the
732 Dallas DS1511 timekeeping/watchdog chip.
733
734 This driver can also be built as a module. If so, the module
735 will be called rtc-ds1511.
736
09a21e56 737config RTC_DRV_DS1553
09b6bdb3 738 tristate "Maxim/Dallas DS1553"
7520b94d
AZ
739 help
740 If you say yes here you get support for the
09b6bdb3 741 Maxim/Dallas DS1553 timekeeping chip.
7520b94d
AZ
742
743 This driver can also be built as a module. If so, the module
09a21e56
AZ
744 will be called rtc-ds1553.
745
09b6bdb3
AZ
746config RTC_DRV_DS1742
747 tristate "Maxim/Dallas DS1742/1743"
02964115
TH
748 help
749 If you say yes here you get support for the
09b6bdb3 750 Maxim/Dallas DS1742/1743 timekeeping chip.
02964115
TH
751
752 This driver can also be built as a module. If so, the module
09b6bdb3 753 will be called rtc-ds1742.
02964115 754
fef931ff
AJ
755config RTC_DRV_DA9052
756 tristate "Dialog DA9052/DA9053 RTC"
757 depends on PMIC_DA9052
758 help
759 Say y here to support the RTC driver for Dialog Semiconductor
760 DA9052-BC and DA9053-AA/Bx PMICs.
761
6920d996
AJ
762config RTC_DRV_DA9055
763 tristate "Dialog Semiconductor DA9055 RTC"
764 depends on MFD_DA9055
765 help
766 If you say yes here you will get support for the
767 RTC of the Dialog DA9055 PMIC.
768
769 This driver can also be built as a module. If so, the module
770 will be called rtc-da9055
771
5e3fd9e5 772config RTC_DRV_EFI
773 tristate "EFI RTC"
774 depends on IA64
775 help
776 If you say yes here you will get support for the EFI
777 Real Time Clock.
778
779 This driver can also be built as a module. If so, the module
780 will be called rtc-efi.
781
09b6bdb3
AZ
782config RTC_DRV_STK17TA8
783 tristate "Simtek STK17TA8"
09a21e56
AZ
784 help
785 If you say yes here you get support for the
09b6bdb3 786 Simtek STK17TA8 timekeeping chip.
09a21e56
AZ
787
788 This driver can also be built as a module. If so, the module
09b6bdb3 789 will be called rtc-stk17ta8.
09a21e56
AZ
790
791config RTC_DRV_M48T86
792 tristate "ST M48T86/Dallas DS12887"
09a21e56
AZ
793 help
794 If you say Y here you will get support for the
795 ST M48T86 and Dallas DS12887 RTC chips.
796
797 This driver can also be built as a module. If so, the module
798 will be called rtc-m48t86.
799
d1dbd82e
TB
800config RTC_DRV_M48T35
801 tristate "ST M48T35"
802 help
803 If you say Y here you will get support for the
804 ST M48T35 RTC chip.
805
806 This driver can also be built as a module, if so, the module
807 will be called "rtc-m48t35".
808
2e774c7c 809config RTC_DRV_M48T59
94fe7424 810 tristate "ST M48T59/M48T08/M48T02"
2e774c7c
MZ
811 help
812 If you say Y here you will get support for the
94fe7424
KH
813 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
814
815 These chips are usually found in Sun SPARC and UltraSPARC
816 workstations.
2e774c7c
MZ
817
818 This driver can also be built as a module, if so, the module
819 will be called "rtc-m48t59".
820
4f9b9bba
GU
821config RTC_DRV_MSM6242
822 tristate "Oki MSM6242"
823 help
824 If you say yes here you get support for the Oki MSM6242
825 timekeeping chip. It is used in some Amiga models (e.g. A2000).
826
827 This driver can also be built as a module. If so, the module
828 will be called rtc-msm6242.
829
cca4c231
DM
830config RTC_DRV_BQ4802
831 tristate "TI BQ4802"
832 help
833 If you say Y here you will get support for the TI
834 BQ4802 RTC chip.
835
836 This driver can also be built as a module. If so, the module
837 will be called rtc-bq4802.
838
4f672ce2
GU
839config RTC_DRV_RP5C01
840 tristate "Ricoh RP5C01"
841 help
842 If you say yes here you get support for the Ricoh RP5C01
843 timekeeping chip. It is used in some Amiga models (e.g. A3000
844 and A4000).
845
846 This driver can also be built as a module. If so, the module
847 will be called rtc-rp5c01.
848
09a21e56
AZ
849config RTC_DRV_V3020
850 tristate "EM Microelectronic V3020"
09a21e56
AZ
851 help
852 If you say yes here you will get support for the
853 EM Microelectronic v3020 RTC chip.
854
855 This driver can also be built as a module. If so, the module
856 will be called rtc-v3020.
857
7418a119
SS
858config RTC_DRV_DS2404
859 tristate "Dallas DS2404"
860 help
861 If you say yes here you get support for the
862 Dallas DS2404 RTC chip.
863
864 This driver can also be built as a module. If so, the module
865 will be called rtc-ds2404.
866
35c86bf6
MB
867config RTC_DRV_WM831X
868 tristate "Wolfson Microelectronics WM831x RTC"
869 depends on MFD_WM831X
870 help
871 If you say yes here you will get support for the RTC subsystem
872 of the Wolfson Microelectronics WM831X series PMICs.
873
874 This driver can also be built as a module. If so, the module
875 will be called "rtc-wm831x".
876
077eaf5b
MB
877config RTC_DRV_WM8350
878 tristate "Wolfson Microelectronics WM8350 RTC"
879 depends on MFD_WM8350
880 help
881 If you say yes here you will get support for the RTC subsystem
882 of the Wolfson Microelectronics WM8350.
883
884 This driver can also be built as a module. If so, the module
885 will be called "rtc-wm8350".
886
0942a71e
RK
887config RTC_DRV_SPEAR
888 tristate "SPEAR ST RTC"
889 depends on PLAT_SPEAR
890 default y
891 help
892 If you say Y here you will get support for the RTC found on
893 spear
894
eae854b2
BR
895config RTC_DRV_PCF50633
896 depends on MFD_PCF50633
897 tristate "NXP PCF50633 RTC"
898 help
899 If you say yes here you get support for the RTC subsystem of the
900 NXP PCF50633 used in embedded systems.
901
bd207cfb
LW
902config RTC_DRV_AB3100
903 tristate "ST-Ericsson AB3100 RTC"
904 depends on AB3100_CORE
905 default y if AB3100_CORE
906 help
907 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
908 support. This chip contains a battery- and capacitor-backed RTC.
909
0af62f4d
VS
910config RTC_DRV_AB8500
911 tristate "ST-Ericsson AB8500 RTC"
912 depends on AB8500_CORE
651fb480 913 select RTC_INTF_DEV
dc43d4a2 914 select RTC_INTF_DEV_UIE_EMUL
0af62f4d
VS
915 help
916 Select this to enable the ST-Ericsson AB8500 power management IC RTC
917 support. This chip contains a battery- and capacitor-backed RTC.
918
afd49a7e
WZ
919config RTC_DRV_NUC900
920 tristate "NUC910/NUC920 RTC driver"
6b8029fa 921 depends on ARCH_W90X900
afd49a7e
WZ
922 help
923 If you say yes here you get support for the RTC subsystem of the
924 NUC910/NUC920 used in embedded systems.
bd207cfb 925
09a21e56 926comment "on-CPU RTC drivers"
09a21e56 927
8ecf6c54
MA
928config RTC_DRV_DAVINCI
929 tristate "TI DaVinci RTC"
930 depends on ARCH_DAVINCI_DM365
931 help
932 If you say yes here you get support for the RTC on the
933 DaVinci platforms (DM365).
934
935 This driver can also be built as a module. If so, the module
936 will be called rtc-davinci.
937
b224b9ac
FE
938config RTC_DRV_IMXDI
939 tristate "Freescale IMX DryIce Real Time Clock"
ef216ad0 940 depends on ARCH_MXC
b224b9ac
FE
941 help
942 Support for Freescale IMX DryIce RTC
943
944 This driver can also be built as a module, if so, the module
945 will be called "rtc-imxdi".
946
09a21e56
AZ
947config RTC_DRV_OMAP
948 tristate "TI OMAP1"
427af9a6 949 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
09a21e56 950 help
427af9a6
AM
951 Say "yes" here to support the on chip real time clock
952 present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
953
954 This driver can also be built as a module, if so, module
955 will be called rtc-omap.
7520b94d 956
16f4efe7
AD
957config HAVE_S3C_RTC
958 bool
959 help
960 This will include RTC support for Samsung SoCs. If
961 you want to include RTC support for any machine, kindly
962 select this in the respective mach-XXXX/Kconfig file.
963
1add6781
BD
964config RTC_DRV_S3C
965 tristate "Samsung S3C series SoC RTC"
b130d5c2 966 depends on ARCH_S3C64XX || HAVE_S3C_RTC
1add6781
BD
967 help
968 RTC (Realtime Clock) driver for the clock inbuilt into the
969 Samsung S3C24XX series of SoCs. This can provide periodic
970 interrupt rates from 1Hz to 64Hz for user programs, and
971 wakeup from Alarm.
972
973 The driver currently supports the common features on all the
974 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
975 and S3C2442.
976
977 This driver can also be build as a module. If so, the module
978 will be called rtc-s3c.
979
fd507e2f
AZ
980config RTC_DRV_EP93XX
981 tristate "Cirrus Logic EP93XX"
bb35fb20 982 depends on ARCH_EP93XX
fd507e2f
AZ
983 help
984 If you say yes here you get support for the
985 RTC embedded in the Cirrus Logic EP93XX processors.
986
987 This driver can also be built as a module. If so, the module
988 will be called rtc-ep93xx.
989
e842f1c8 990config RTC_DRV_SA1100
3888c090
HZ
991 tristate "SA11x0/PXA2xx/PXA910"
992 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
e842f1c8
RP
993 help
994 If you say Y here you will get access to the real time clock
995 built into your SA11x0 or PXA2xx CPU.
996
997 To compile this driver as a module, choose M here: the
998 module will be called rtc-sa1100.
fd507e2f 999
317a6104
PM
1000config RTC_DRV_SH
1001 tristate "SuperH On-Chip RTC"
6b8029fa 1002 depends on SUPERH && HAVE_CLK
317a6104
PM
1003 help
1004 Say Y here to enable support for the on-chip RTC found in
1005 most SuperH processors.
1006
1007 To compile this driver as a module, choose M here: the
1008 module will be called rtc-sh.
1009
8417eb7a 1010config RTC_DRV_VR41XX
3e16f6af 1011 tristate "NEC VR41XX"
bb35fb20 1012 depends on CPU_VR41XX
3e16f6af
AZ
1013 help
1014 If you say Y here you will get access to the real time clock
1015 built into your NEC VR41XX CPU.
1016
1017 To compile this driver as a module, choose M here: the
1018 module will be called rtc-vr41xx.
8417eb7a 1019
a190901c
RK
1020config RTC_DRV_PL030
1021 tristate "ARM AMBA PL030 RTC"
1022 depends on ARM_AMBA
1023 help
1024 If you say Y here you will get access to ARM AMBA
1025 PrimeCell PL030 RTC found on certain ARM SOCs.
1026
1027 To compile this driver as a module, choose M here: the
1028 module will be called rtc-pl030.
1029
8ae6e163
DS
1030config RTC_DRV_PL031
1031 tristate "ARM AMBA PL031 RTC"
bb35fb20 1032 depends on ARM_AMBA
8ae6e163
DS
1033 help
1034 If you say Y here you will get access to ARM AMBA
09a21e56 1035 PrimeCell PL031 RTC found on certain ARM SOCs.
8ae6e163
DS
1036
1037 To compile this driver as a module, choose M here: the
1038 module will be called rtc-pl031.
1039
fa04e78b
HCE
1040config RTC_DRV_AT32AP700X
1041 tristate "AT32AP700X series RTC"
bb35fb20 1042 depends on PLATFORM_AT32AP
fa04e78b
HCE
1043 help
1044 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1045 AT32AP700x family processors.
1046
7fc39f6d 1047config RTC_DRV_AT91RM9200
24cecc1b 1048 tristate "AT91RM9200 or some AT91SAM9 RTC"
938f970e 1049 depends on ARCH_AT91
4cdf854f
DB
1050 help
1051 Driver for the internal RTC (Realtime Clock) module found on
24cecc1b 1052 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
4cdf854f
DB
1053 this is powered by the backup power supply.
1054
1055config RTC_DRV_AT91SAM9
24cecc1b 1056 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
4cdf854f
DB
1057 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
1058 help
6b71dbf6
SP
1059 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
1060 (Real Time Timer). These timers are powered by the backup power
1061 supply (such as a small coin cell battery), but do not need to
1062 be used as RTCs.
4cdf854f 1063
24cecc1b
NF
1064 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
1065 dedicated RTC module and leave the RTT available for other uses.)
4cdf854f
DB
1066
1067config RTC_DRV_AT91SAM9_RTT
1068 int
1069 range 0 1
1070 default 0
1071 prompt "RTT module Number" if ARCH_AT91SAM9263
1072 depends on RTC_DRV_AT91SAM9
1073 help
ae64d169
AZ
1074 More than one RTT module is available. You can choose which
1075 one will be used as an RTC. The default of zero is normally
4cdf854f
DB
1076 OK to use, though some systems use that for non-RTC purposes.
1077
1078config RTC_DRV_AT91SAM9_GPBR
1079 int
1080 range 0 3 if !ARCH_AT91SAM9263
1081 range 0 15 if ARCH_AT91SAM9263
1082 default 0
1083 prompt "Backup Register Number"
1084 depends on RTC_DRV_AT91SAM9
1085 help
1086 The RTC driver needs to use one of the General Purpose Backup
ae64d169
AZ
1087 Registers (GPBRs) as well as the RTT. You can choose which one
1088 will be used. The default of zero is normally OK to use, but
4cdf854f 1089 on some systems other software needs to use that register.
788b1fc6 1090
45fd8a0c
ML
1091config RTC_DRV_AU1XXX
1092 tristate "Au1xxx Counter0 RTC support"
42a4f17d 1093 depends on MIPS_ALCHEMY
45fd8a0c
ML
1094 help
1095 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1096 counter) to be used as a RTC.
1097
1098 This driver can also be built as a module. If so, the module
1099 will be called rtc-au1xxx.
1100
8cc75c9a
WB
1101config RTC_DRV_BFIN
1102 tristate "Blackfin On-Chip RTC"
7f604599 1103 depends on BLACKFIN && !BF561
8cc75c9a
WB
1104 help
1105 If you say yes here you will get support for the
1106 Blackfin On-Chip Real Time Clock.
1107
1108 This driver can also be built as a module. If so, the module
1109 will be called rtc-bfin.
1110
e9f2bd81
NI
1111config RTC_DRV_RS5C313
1112 tristate "Ricoh RS5C313"
bb35fb20 1113 depends on SH_LANDISK
e9f2bd81
NI
1114 help
1115 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1116
3afe6d04
GU
1117config RTC_DRV_GENERIC
1118 tristate "Generic RTC support"
1119 # Please consider writing a new RTC driver instead of using the generic
1120 # RTC abstraction
47c8a08b 1121 depends on PARISC || M68K || PPC || SUPERH32
9eb16864 1122 help
3afe6d04
GU
1123 Say Y or M here to enable RTC support on systems using the generic
1124 RTC abstraction. If you do not know what you are doing, you should
9eb16864
KM
1125 just say Y.
1126
dc944368
RJ
1127config RTC_DRV_PXA
1128 tristate "PXA27x/PXA3xx"
1129 depends on ARCH_PXA
1130 help
1131 If you say Y here you will get access to the real time clock
1132 built into your PXA27x or PXA3xx CPU.
1133
1134 This RTC driver uses PXA RTC registers available since pxa27x
1135 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1136
f77fbdf9
AC
1137config RTC_DRV_VT8500
1138 tristate "VIA/WonderMedia 85xx SoC RTC"
1139 depends on ARCH_VT8500
1140 help
1141 If you say Y here you will get access to the real time clock
1142 built into your VIA VT8500 SoC or its relatives.
1143
dc944368 1144
7a138ede
DM
1145config RTC_DRV_SUN4V
1146 bool "SUN4V Hypervisor RTC"
1147 depends on SPARC64
1148 help
1149 If you say Y here you will get support for the Hypervisor
1150 based RTC on SUN4V systems.
1151
594c6fb9
CC
1152config RTC_DRV_SUNXI
1153 tristate "Allwinner sun4i/sun7i RTC"
1154 depends on ARCH_SUNXI
1155 help
1156 If you say Y here you will get support for the RTC found on
1157 Allwinner A10/A20.
1158
de2cf332
DM
1159config RTC_DRV_STARFIRE
1160 bool "Starfire RTC"
1161 depends on SPARC64
1162 help
1163 If you say Y here you will get support for the RTC found on
1164 Starfire systems.
1165
0e149233
AN
1166config RTC_DRV_TX4939
1167 tristate "TX4939 SoC"
1168 depends on SOC_TX4939
1169 help
1170 Driver for the internal RTC (Realtime Clock) module found on
1171 Toshiba TX4939 SoC.
1172
defb4514
SB
1173config RTC_DRV_MV
1174 tristate "Marvell SoC RTC"
a1671da5 1175 depends on ARCH_KIRKWOOD || ARCH_DOVE || ARCH_MVEBU
defb4514
SB
1176 help
1177 If you say yes here you will get support for the in-chip RTC
1178 that can be found in some of Marvell's SoC devices, such as
1179 the Kirkwood 88F6281 and 88F6192.
1180
1181 This driver can also be built as a module. If so, the module
1182 will be called rtc-mv.
1183
0b5f037a
GU
1184config RTC_DRV_PS3
1185 tristate "PS3 RTC"
1186 depends on PPC_PS3
1187 help
1188 If you say yes here you will get support for the RTC on PS3.
1189
1190 This driver can also be built as a module. If so, the module
1191 will be called rtc-ps3.
1192
aa958f57
LW
1193config RTC_DRV_COH901331
1194 tristate "ST-Ericsson COH 901 331 RTC"
1195 depends on ARCH_U300
1196 help
1197 If you say Y here you will get access to ST-Ericsson
1198 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1199 Platforms.
1200
1201 This driver can also be built as a module. If so, the module
1202 will be called "rtc-coh901331".
1203
1204
df17f631 1205config RTC_DRV_STMP
46b21218
WS
1206 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1207 depends on ARCH_MXS
df17f631 1208 help
1209 If you say yes here you will get support for the onboard
46b21218 1210 STMP3xxx/i.MX23/i.MX28 RTC.
df17f631 1211
1212 This driver can also be built as a module. If so, the module
1213 will be called rtc-stmp3xxx.
1214
d3c7a3f7
DR
1215config RTC_DRV_PCAP
1216 tristate "PCAP RTC"
1217 depends on EZX_PCAP
1218 help
1219 If you say Y here you will get support for the RTC found on
1220 the PCAP2 ASIC used on some Motorola phones.
1221
1c97872b
UKK
1222config RTC_DRV_MC13XXX
1223 depends on MFD_MC13XXX
1224 tristate "Freescale MC13xxx RTC"
43299f28 1225 help
1c97872b
UKK
1226 This enables support for the RTCs found on Freescale's PMICs
1227 MC13783 and MC13892.
43299f28 1228
50aae724
AG
1229config RTC_DRV_MPC5121
1230 tristate "Freescale MPC5121 built-in RTC"
955dbea3 1231 depends on PPC_MPC512x || PPC_MPC52xx
50aae724
AG
1232 help
1233 If you say yes here you will get support for the
955dbea3 1234 built-in RTC on MPC5121 or on MPC5200.
50aae724
AG
1235
1236 This driver can also be built as a module. If so, the module
1237 will be called rtc-mpc5121.
1238
3bf0eea8
LPC
1239config RTC_DRV_JZ4740
1240 tristate "Ingenic JZ4740 SoC"
3bf0eea8
LPC
1241 depends on MACH_JZ4740
1242 help
1243 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1244 controller.
1245
1246 This driver can also be buillt as a module. If so, the module
1247 will be called rtc-jz4740.
1248
9aa449be
KW
1249config RTC_DRV_LPC32XX
1250 depends on ARCH_LPC32XX
1251 tristate "NXP LPC32XX RTC"
1252 help
1253 This enables support for the NXP RTC in the LPC32XX
1254
1255 This driver can also be buillt as a module. If so, the module
1256 will be called rtc-lpc32xx.
1257
9a9a54ad
AG
1258config RTC_DRV_PM8XXX
1259 tristate "Qualcomm PMIC8XXX RTC"
1260 depends on MFD_PM8XXX
1261 help
1262 If you say yes here you get support for the
1263 Qualcomm PMIC8XXX RTC.
1264
1265 To compile this driver as a module, choose M here: the
1266 module will be called rtc-pm8xxx.
1267
ff859ba6
AC
1268config RTC_DRV_TEGRA
1269 tristate "NVIDIA Tegra Internal RTC driver"
6b8029fa 1270 depends on ARCH_TEGRA
ff859ba6
AC
1271 help
1272 If you say yes here you get support for the
1273 Tegra 200 series internal RTC module.
1274
1275 This drive can also be built as a module. If so, the module
1276 will be called rtc-tegra.
1277
dd196a2b
CM
1278config RTC_DRV_TILE
1279 tristate "Tilera hypervisor RTC support"
1280 depends on TILE
1281 help
1282 Enable support for the Linux driver side of the Tilera
1283 hypervisor's real-time clock interface.
1284
2809e80b
GX
1285config RTC_DRV_PUV3
1286 tristate "PKUnity v3 RTC support"
1287 depends on ARCH_PUV3
1288 help
1289 This enables support for the RTC in the PKUnity-v3 SoCs.
1290
1291 This drive can also be built as a module. If so, the module
1292 will be called rtc-puv3.
1293
b4f0b880 1294config RTC_DRV_LOONGSON1
1295 tristate "loongson1 RTC support"
1296 depends on MACH_LOONGSON1
1297 help
1298 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1299 counter) to be used as a RTC.
1300
1301 This driver can also be built as a module. If so, the module
1302 will be called rtc-ls1x.
1303
79811595 1304config RTC_DRV_MXC
b224b9ac
FE
1305 tristate "Freescale MXC Real Time Clock"
1306 depends on ARCH_MXC
b224b9ac
FE
1307 help
1308 If you say yes here you get support for the Freescale MXC
1309 RTC module.
1310
1311 This driver can also be built as a module, if so, the module
1312 will be called "rtc-mxc".
1313
179a502f
SG
1314config RTC_DRV_SNVS
1315 tristate "Freescale SNVS RTC support"
1316 depends on HAS_IOMEM
1317 depends on OF
1318 help
1319 If you say yes here you get support for the Freescale SNVS
1320 Low Power (LP) RTC module.
1321
1322 This driver can also be built as a module, if so, the module
1323 will be called "rtc-snvs".
1324
e88b815e
XD
1325config RTC_DRV_SIRFSOC
1326 tristate "SiRFSOC RTC"
1327 depends on ARCH_SIRF
1328 help
1329 Say "yes" here to support the real time clock on SiRF SOC chips.
1330 This driver can also be built as a module called rtc-sirfsoc.
1331
453b4c6d
JJ
1332config RTC_DRV_MOXART
1333 tristate "MOXA ART RTC"
1334 help
1335 If you say yes here you get support for the MOXA ART
1336 RTC module.
1337
1338 This driver can also be built as a module. If so, the module
1339 will be called rtc-moxart
1340
f12d8695
LH
1341config RTC_DRV_XGENE
1342 tristate "APM X-Gene RTC"
1343 help
1344 If you say yes here you get support for the APM X-Gene SoC real time
1345 clock.
1346
1347 This driver can also be built as a module, if so, the module
1348 will be called "rtc-xgene".
1349
62e00cb9
AH
1350comment "HID Sensor RTC drivers"
1351
1352config RTC_DRV_HID_SENSOR_TIME
1353 tristate "HID Sensor Time"
1354 depends on USB_HID
1355 select IIO
1356 select HID_SENSOR_HUB
1357 select HID_SENSOR_IIO_COMMON
1358 help
1359 Say yes here to build support for the HID Sensors of type Time.
1360 This drivers makes such sensors available as RTCs.
1361
1362 If this driver is compiled as a module, it will be named
1363 rtc-hid-sensor-time.
1364
1365
bb35fb20 1366endif # RTC_CLASS
This page took 0.85887 seconds and 5 git commands to generate.