]> git.proxmox.com Git - mirror_ubuntu-bionic-kernel.git/blob - drivers/rtc/Kconfig
rtc: pcf8563: Fix interrupt trigger method
[mirror_ubuntu-bionic-kernel.git] / drivers / rtc / Kconfig
1 #
2 # RTC class/drivers configuration
3 #
4
5 config RTC_LIB
6 bool
7
8 config RTC_MC146818_LIB
9 bool
10 select RTC_LIB
11
12 menuconfig RTC_CLASS
13 bool "Real Time Clock"
14 default n
15 depends on !S390 && !UML
16 select RTC_LIB
17 help
18 Generic RTC class support. If you say yes here, you will
19 be allowed to plug one or more RTCs to your system. You will
20 probably want to enable one or more of the interfaces below.
21
22 if RTC_CLASS
23
24 config RTC_HCTOSYS
25 bool "Set system time from RTC on startup and resume"
26 default y
27 help
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.
31
32 config RTC_HCTOSYS_DEVICE
33 string "RTC used to set the system time"
34 depends on RTC_HCTOSYS
35 default "rtc0"
36 help
37 The RTC device that will be used to (re)initialize the system
38 clock, usually rtc0. Initialization is done when the system
39 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.
42
43 The driver for this RTC device must be loaded before late_initcall
44 functions run, so it must usually be statically linked.
45
46 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
52 sleep states. Do not specify an RTC here unless it stays powered
53 during all this system's supported sleep states.
54
55 config RTC_SYSTOHC
56 bool "Set the RTC time based on NTP synchronization"
57 default y
58 help
59 If you say yes here, the system time (wall clock) will be stored
60 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
61 minutes if userspace reports synchronized NTP status.
62
63 config RTC_SYSTOHC_DEVICE
64 string "RTC used to synchronize NTP adjustment"
65 depends on RTC_SYSTOHC
66 default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS
67 default "rtc0"
68 help
69 The RTC device used for NTP synchronization. The main difference
70 between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this
71 one can sleep when setting time, because it runs in the workqueue
72 context.
73
74 config RTC_DEBUG
75 bool "RTC debug support"
76 help
77 Say yes here to enable debugging support in the RTC framework
78 and individual RTC drivers.
79
80 config RTC_NVMEM
81 bool "RTC non volatile storage support"
82 select NVMEM
83 default RTC_CLASS
84 help
85 Say yes here to add support for the non volatile (often battery
86 backed) storage present on RTCs.
87
88 comment "RTC interfaces"
89
90 config RTC_INTF_SYSFS
91 bool "/sys/class/rtc/rtcN (sysfs)"
92 depends on SYSFS
93 default RTC_CLASS
94 help
95 Say yes here if you want to use your RTCs using sysfs interfaces,
96 /sys/class/rtc/rtc0 through /sys/.../rtcN.
97
98 If unsure, say Y.
99
100 config RTC_INTF_PROC
101 bool "/proc/driver/rtc (procfs for rtcN)"
102 depends on PROC_FS
103 default RTC_CLASS
104 help
105 Say yes here if you want to use your system clock RTC through
106 the proc interface, /proc/driver/rtc.
107 Other RTCs will not be available through that API.
108 If there is no RTC for the system clock, then the first RTC(rtc0)
109 is used by default.
110
111 If unsure, say Y.
112
113 config RTC_INTF_DEV
114 bool "/dev/rtcN (character devices)"
115 default RTC_CLASS
116 help
117 Say yes here if you want to use your RTCs using the /dev
118 interfaces, which "udev" sets up as /dev/rtc0 through
119 /dev/rtcN.
120
121 You may want to set up a symbolic link so one of these
122 can be accessed as /dev/rtc, which is a name
123 expected by "hwclock" and some other programs. Recent
124 versions of "udev" are known to set up the symlink for you.
125
126 If unsure, say Y.
127
128 config RTC_INTF_DEV_UIE_EMUL
129 bool "RTC UIE emulation on dev interface"
130 depends on RTC_INTF_DEV
131 help
132 Provides an emulation for RTC_UIE if the underlying rtc chip
133 driver does not expose RTC_UIE ioctls. Those requests generate
134 once-per-second update interrupts, used for synchronization.
135
136 The emulation code will read the time from the hardware
137 clock several times per second, please enable this option
138 only if you know that you really need it.
139
140 config RTC_DRV_TEST
141 tristate "Test driver/device"
142 help
143 If you say yes here you get support for the
144 RTC test driver. It's a software RTC which can be
145 used to test the RTC subsystem APIs. It gets
146 the time from the system clock.
147 You want this driver only if you are doing development
148 on the RTC subsystem. Please read the source code
149 for further details.
150
151 This driver can also be built as a module. If so, the module
152 will be called rtc-test.
153
154 comment "I2C RTC drivers"
155
156 if I2C
157
158 config RTC_DRV_88PM860X
159 tristate "Marvell 88PM860x"
160 depends on MFD_88PM860X
161 help
162 If you say yes here you get support for RTC function in Marvell
163 88PM860x chips.
164
165 This driver can also be built as a module. If so, the module
166 will be called rtc-88pm860x.
167
168 config RTC_DRV_88PM80X
169 tristate "Marvell 88PM80x"
170 depends on MFD_88PM800
171 help
172 If you say yes here you get support for RTC function in Marvell
173 88PM80x chips.
174
175 This driver can also be built as a module. If so, the module
176 will be called rtc-88pm80x.
177
178 config RTC_DRV_ABB5ZES3
179 select REGMAP_I2C
180 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
181 help
182 If you say yes here you get support for the Abracon
183 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
184
185 This driver can also be built as a module. If so, the module
186 will be called rtc-ab-b5ze-s3.
187
188 config RTC_DRV_ABX80X
189 tristate "Abracon ABx80x"
190 help
191 If you say yes here you get support for Abracon AB080X and AB180X
192 families of ultra-low-power battery- and capacitor-backed real-time
193 clock chips.
194
195 This driver can also be built as a module. If so, the module
196 will be called rtc-abx80x.
197
198 config RTC_DRV_AC100
199 tristate "X-Powers AC100"
200 depends on MFD_AC100
201 help
202 If you say yes here you get support for the real-time clock found
203 in X-Powers AC100 family peripheral ICs.
204
205 This driver can also be built as a module. If so, the module
206 will be called rtc-ac100.
207
208 config RTC_DRV_BRCMSTB
209 tristate "Broadcom STB wake-timer"
210 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
211 default ARCH_BRCMSTB || BMIPS_GENERIC
212 help
213 If you say yes here you get support for the wake-timer found on
214 Broadcom STB SoCs (BCM7xxx).
215
216 This driver can also be built as a module. If so, the module will
217 be called rtc-brcmstb-waketimer.
218
219 config RTC_DRV_AS3722
220 tristate "ams AS3722 RTC driver"
221 depends on MFD_AS3722
222 help
223 If you say yes here you get support for the RTC of ams AS3722 PMIC
224 chips.
225
226 This driver can also be built as a module. If so, the module
227 will be called rtc-as3722.
228
229 config RTC_DRV_DS1307
230 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"
231 help
232 If you say yes here you get support for various compatible RTC
233 chips (often with battery backup) connected with I2C. This driver
234 should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341,
235 ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.
236 In some cases the RTC must already have been initialized (by
237 manufacturing or a bootloader).
238
239 The first seven registers on these chips hold an RTC, and other
240 registers may add features such as NVRAM, a trickle charger for
241 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
242 sysfs, but other chip features may not be available.
243
244 This driver can also be built as a module. If so, the module
245 will be called rtc-ds1307.
246
247 config RTC_DRV_DS1307_HWMON
248 bool "HWMON support for rtc-ds1307"
249 depends on RTC_DRV_DS1307 && HWMON
250 depends on !(RTC_DRV_DS1307=y && HWMON=m)
251 default y
252 help
253 Say Y here if you want to expose temperature sensor data on
254 rtc-ds1307 (only DS3231)
255
256 config RTC_DRV_DS1307_CENTURY
257 bool "Century bit support for rtc-ds1307"
258 depends on RTC_DRV_DS1307
259 default n
260 help
261 The DS1307 driver suffered from a bug where it was enabling the
262 century bit inconditionnally but never used it when reading the time.
263 It made the driver unable to support dates beyond 2099.
264 Setting this option will add proper support for the century bit but if
265 the time was previously set using a kernel predating this option,
266 reading the date will return a date in the next century.
267 To solve that, you could boot a kernel without this option set, set
268 the RTC date and then boot a kernel with this option set.
269
270 config RTC_DRV_DS1374
271 tristate "Dallas/Maxim DS1374"
272 help
273 If you say yes here you get support for Dallas Semiconductor
274 DS1374 real-time clock chips. If an interrupt is associated
275 with the device, the alarm functionality is supported.
276
277 This driver can also be built as a module. If so, the module
278 will be called rtc-ds1374.
279
280 config RTC_DRV_DS1374_WDT
281 bool "Dallas/Maxim DS1374 watchdog timer"
282 depends on RTC_DRV_DS1374
283 help
284 If you say Y here you will get support for the
285 watchdog timer in the Dallas Semiconductor DS1374
286 real-time clock chips.
287
288 config RTC_DRV_DS1672
289 tristate "Dallas/Maxim DS1672"
290 help
291 If you say yes here you get support for the
292 Dallas/Maxim DS1672 timekeeping chip.
293
294 This driver can also be built as a module. If so, the module
295 will be called rtc-ds1672.
296
297 config RTC_DRV_HYM8563
298 tristate "Haoyu Microelectronics HYM8563"
299 depends on OF
300 help
301 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
302 from the usual rtc functions it provides a clock output of
303 up to 32kHz.
304
305 This driver can also be built as a module. If so, the module
306 will be called rtc-hym8563.
307
308 config RTC_DRV_LP8788
309 tristate "TI LP8788 RTC driver"
310 depends on MFD_LP8788
311 help
312 Say Y to enable support for the LP8788 RTC/ALARM driver.
313
314 config RTC_DRV_MAX6900
315 tristate "Maxim MAX6900"
316 help
317 If you say yes here you will get support for the
318 Maxim MAX6900 I2C RTC chip.
319
320 This driver can also be built as a module. If so, the module
321 will be called rtc-max6900.
322
323 config RTC_DRV_MAX8907
324 tristate "Maxim MAX8907"
325 depends on MFD_MAX8907 || COMPILE_TEST
326 help
327 If you say yes here you will get support for the
328 RTC of Maxim MAX8907 PMIC.
329
330 This driver can also be built as a module. If so, the module
331 will be called rtc-max8907.
332
333 config RTC_DRV_MAX8925
334 tristate "Maxim MAX8925"
335 depends on MFD_MAX8925
336 help
337 If you say yes here you will get support for the
338 RTC of Maxim MAX8925 PMIC.
339
340 This driver can also be built as a module. If so, the module
341 will be called rtc-max8925.
342
343 config RTC_DRV_MAX8998
344 tristate "Maxim MAX8998"
345 depends on MFD_MAX8998
346 help
347 If you say yes here you will get support for the
348 RTC of Maxim MAX8998 PMIC.
349
350 This driver can also be built as a module. If so, the module
351 will be called rtc-max8998.
352
353 config RTC_DRV_MAX8997
354 tristate "Maxim MAX8997"
355 depends on MFD_MAX8997
356 help
357 If you say yes here you will get support for the
358 RTC of Maxim MAX8997 PMIC.
359
360 This driver can also be built as a module. If so, the module
361 will be called rtc-max8997.
362
363 config RTC_DRV_MAX77686
364 tristate "Maxim MAX77686"
365 depends on MFD_MAX77686 || MFD_MAX77620 || COMPILE_TEST
366 help
367 If you say yes here you will get support for the
368 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
369
370 This driver can also be built as a module. If so, the module
371 will be called rtc-max77686.
372
373 config RTC_DRV_RK808
374 tristate "Rockchip RK805/RK808/RK818 RTC"
375 depends on MFD_RK808
376 help
377 If you say yes here you will get support for the
378 RTC of RK805, RK808 and RK818 PMIC.
379
380 This driver can also be built as a module. If so, the module
381 will be called rk808-rtc.
382
383 config RTC_DRV_RS5C372
384 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
385 help
386 If you say yes here you get support for the
387 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
388
389 This driver can also be built as a module. If so, the module
390 will be called rtc-rs5c372.
391
392 config RTC_DRV_ISL1208
393 tristate "Intersil ISL1208"
394 help
395 If you say yes here you get support for the
396 Intersil ISL1208 RTC chip.
397
398 This driver can also be built as a module. If so, the module
399 will be called rtc-isl1208.
400
401 config RTC_DRV_ISL12022
402 tristate "Intersil ISL12022"
403 help
404 If you say yes here you get support for the
405 Intersil ISL12022 RTC chip.
406
407 This driver can also be built as a module. If so, the module
408 will be called rtc-isl12022.
409
410 config RTC_DRV_X1205
411 tristate "Xicor/Intersil X1205"
412 help
413 If you say yes here you get support for the
414 Xicor/Intersil X1205 RTC chip.
415
416 This driver can also be built as a module. If so, the module
417 will be called rtc-x1205.
418
419 config RTC_DRV_PCF8523
420 tristate "NXP PCF8523"
421 help
422 If you say yes here you get support for the NXP PCF8523 RTC
423 chips.
424
425 This driver can also be built as a module. If so, the module
426 will be called rtc-pcf8523.
427
428 config RTC_DRV_PCF85063
429 tristate "NXP PCF85063"
430 help
431 If you say yes here you get support for the PCF85063 RTC chip
432
433 This driver can also be built as a module. If so, the module
434 will be called rtc-pcf85063.
435
436 config RTC_DRV_PCF85363
437 tristate "NXP PCF85363"
438 depends on I2C
439 select REGMAP_I2C
440 help
441 If you say yes here you get support for the PCF85363 RTC chip.
442
443 This driver can also be built as a module. If so, the module
444 will be called rtc-pcf85363.
445
446 The nvmem interface will be named pcf85363-#, where # is the
447 zero-based instance number.
448
449 config RTC_DRV_PCF8563
450 tristate "Philips PCF8563/Epson RTC8564"
451 help
452 If you say yes here you get support for the
453 Philips PCF8563 RTC chip. The Epson RTC8564
454 should work as well.
455
456 This driver can also be built as a module. If so, the module
457 will be called rtc-pcf8563.
458
459 config RTC_DRV_PCF8583
460 tristate "Philips PCF8583"
461 help
462 If you say yes here you get support for the Philips PCF8583
463 RTC chip found on Acorn RiscPCs. This driver supports the
464 platform specific method of retrieving the current year from
465 the RTC's SRAM. It will work on other platforms with the same
466 chip, but the year will probably have to be tweaked.
467
468 This driver can also be built as a module. If so, the module
469 will be called rtc-pcf8583.
470
471 config RTC_DRV_M41T80
472 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
473 help
474 If you say Y here you will get support for the ST M41T60
475 and M41T80 RTC chips series. Currently, the following chips are
476 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
477 M41ST85, M41ST87, and MicroCrystal RV4162.
478
479 This driver can also be built as a module. If so, the module
480 will be called rtc-m41t80.
481
482 config RTC_DRV_M41T80_WDT
483 bool "ST M41T65/M41T80 series RTC watchdog timer"
484 depends on RTC_DRV_M41T80
485 help
486 If you say Y here you will get support for the
487 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
488
489 config RTC_DRV_BQ32K
490 tristate "TI BQ32000"
491 help
492 If you say Y here you will get support for the TI
493 BQ32000 I2C RTC chip.
494
495 This driver can also be built as a module. If so, the module
496 will be called rtc-bq32k.
497
498 config RTC_DRV_DM355EVM
499 tristate "TI DaVinci DM355 EVM RTC"
500 depends on MFD_DM355EVM_MSP
501 help
502 Supports the RTC firmware in the MSP430 on the DM355 EVM.
503
504 config RTC_DRV_TWL92330
505 bool "TI TWL92330/Menelaus"
506 depends on MENELAUS
507 help
508 If you say yes here you get support for the RTC on the
509 TWL92330 "Menelaus" power management chip, used with OMAP2
510 platforms. The support is integrated with the rest of
511 the Menelaus driver; it's not separate module.
512
513 config RTC_DRV_TWL4030
514 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
515 depends on TWL4030_CORE
516 depends on OF
517 help
518 If you say yes here you get support for the RTC on the
519 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
520
521 This driver can also be built as a module. If so, the module
522 will be called rtc-twl.
523
524 config RTC_DRV_PALMAS
525 tristate "TI Palmas RTC driver"
526 depends on MFD_PALMAS
527 help
528 If you say yes here you get support for the RTC of TI PALMA series PMIC
529 chips.
530
531 This driver can also be built as a module. If so, the module
532 will be called rtc-palma.
533
534 config RTC_DRV_TPS6586X
535 tristate "TI TPS6586X RTC driver"
536 depends on MFD_TPS6586X
537 help
538 TI Power Management IC TPS6586X supports RTC functionality
539 along with alarm. This driver supports the RTC driver for
540 the TPS6586X RTC module.
541
542 config RTC_DRV_TPS65910
543 tristate "TI TPS65910 RTC driver"
544 depends on RTC_CLASS && MFD_TPS65910
545 help
546 If you say yes here you get support for the RTC on the
547 TPS65910 chips.
548
549 This driver can also be built as a module. If so, the module
550 will be called rtc-tps65910.
551
552 config RTC_DRV_TPS80031
553 tristate "TI TPS80031/TPS80032 RTC driver"
554 depends on MFD_TPS80031
555 help
556 TI Power Management IC TPS80031 supports RTC functionality
557 along with alarm. This driver supports the RTC driver for
558 the TPS80031 RTC module.
559
560 config RTC_DRV_RC5T583
561 tristate "RICOH 5T583 RTC driver"
562 depends on MFD_RC5T583
563 help
564 If you say yes here you get support for the RTC on the
565 RICOH 5T583 chips.
566
567 This driver can also be built as a module. If so, the module
568 will be called rtc-rc5t583.
569
570 config RTC_DRV_S35390A
571 tristate "Seiko Instruments S-35390A"
572 select BITREVERSE
573 help
574 If you say yes here you will get support for the Seiko
575 Instruments S-35390A.
576
577 This driver can also be built as a module. If so the module
578 will be called rtc-s35390a.
579
580 config RTC_DRV_FM3130
581 tristate "Ramtron FM3130"
582 help
583 If you say Y here you will get support for the
584 Ramtron FM3130 RTC chips.
585 Ramtron FM3130 is a chip with two separate devices inside,
586 RTC clock and FRAM. This driver provides only RTC functionality.
587
588 This driver can also be built as a module. If so the module
589 will be called rtc-fm3130.
590
591 config RTC_DRV_RX8010
592 tristate "Epson RX8010SJ"
593 depends on I2C
594 help
595 If you say yes here you get support for the Epson RX8010SJ RTC
596 chip.
597
598 This driver can also be built as a module. If so, the module
599 will be called rtc-rx8010.
600
601 config RTC_DRV_RX8581
602 tristate "Epson RX-8581"
603 help
604 If you say yes here you will get support for the Epson RX-8581.
605
606 This driver can also be built as a module. If so the module
607 will be called rtc-rx8581.
608
609 config RTC_DRV_RX8025
610 tristate "Epson RX-8025SA/NB"
611 help
612 If you say yes here you get support for the Epson
613 RX-8025SA/NB RTC chips.
614
615 This driver can also be built as a module. If so, the module
616 will be called rtc-rx8025.
617
618 config RTC_DRV_EM3027
619 tristate "EM Microelectronic EM3027"
620 help
621 If you say yes here you get support for the EM
622 Microelectronic EM3027 RTC chips.
623
624 This driver can also be built as a module. If so, the module
625 will be called rtc-em3027.
626
627 config RTC_DRV_RV8803
628 tristate "Micro Crystal RV8803, Epson RX8900"
629 help
630 If you say yes here you get support for the Micro Crystal RV8803 and
631 Epson RX8900 RTC chips.
632
633 This driver can also be built as a module. If so, the module
634 will be called rtc-rv8803.
635
636 config RTC_DRV_S5M
637 tristate "Samsung S2M/S5M series"
638 depends on MFD_SEC_CORE || COMPILE_TEST
639 select REGMAP_IRQ
640 help
641 If you say yes here you will get support for the
642 RTC of Samsung S2MPS14 and S5M PMIC series.
643
644 This driver can also be built as a module. If so, the module
645 will be called rtc-s5m.
646
647 endif # I2C
648
649 comment "SPI RTC drivers"
650
651 if SPI_MASTER
652
653 config RTC_DRV_M41T93
654 tristate "ST M41T93"
655 help
656 If you say yes here you will get support for the
657 ST M41T93 SPI RTC chip.
658
659 This driver can also be built as a module. If so, the module
660 will be called rtc-m41t93.
661
662 config RTC_DRV_M41T94
663 tristate "ST M41T94"
664 help
665 If you say yes here you will get support for the
666 ST M41T94 SPI RTC chip.
667
668 This driver can also be built as a module. If so, the module
669 will be called rtc-m41t94.
670
671 config RTC_DRV_DS1302
672 tristate "Dallas/Maxim DS1302"
673 depends on SPI
674 help
675 If you say yes here you get support for the Dallas DS1302 RTC chips.
676
677 This driver can also be built as a module. If so, the module
678 will be called rtc-ds1302.
679
680 config RTC_DRV_DS1305
681 tristate "Dallas/Maxim DS1305/DS1306"
682 help
683 Select this driver to get support for the Dallas/Maxim DS1305
684 and DS1306 real time clock chips. These support a trickle
685 charger, alarms, and NVRAM in addition to the clock.
686
687 This driver can also be built as a module. If so, the module
688 will be called rtc-ds1305.
689
690 config RTC_DRV_DS1343
691 select REGMAP_SPI
692 tristate "Dallas/Maxim DS1343/DS1344"
693 help
694 If you say yes here you get support for the
695 Dallas/Maxim DS1343 and DS1344 real time clock chips.
696 Support for trickle charger, alarm is provided.
697
698 This driver can also be built as a module. If so, the module
699 will be called rtc-ds1343.
700
701 config RTC_DRV_DS1347
702 select REGMAP_SPI
703 tristate "Dallas/Maxim DS1347"
704 help
705 If you say yes here you get support for the
706 Dallas/Maxim DS1347 chips.
707
708 This driver only supports the RTC feature, and not other chip
709 features such as alarms.
710
711 This driver can also be built as a module. If so, the module
712 will be called rtc-ds1347.
713
714 config RTC_DRV_DS1390
715 tristate "Dallas/Maxim DS1390/93/94"
716 help
717 If you say yes here you get support for the
718 Dallas/Maxim DS1390/93/94 chips.
719
720 This driver supports the RTC feature and trickle charging but not
721 other chip features such as alarms.
722
723 This driver can also be built as a module. If so, the module
724 will be called rtc-ds1390.
725
726 config RTC_DRV_MAX6916
727 tristate "Maxim MAX6916"
728 help
729 If you say yes here you will get support for the
730 Maxim MAX6916 SPI RTC chip.
731
732 This driver only supports the RTC feature, and not other chip
733 features such as alarms.
734
735 This driver can also be built as a module. If so, the module
736 will be called rtc-max6916.
737
738 config RTC_DRV_R9701
739 tristate "Epson RTC-9701JE"
740 help
741 If you say yes here you will get support for the
742 Epson RTC-9701JE SPI RTC chip.
743
744 This driver can also be built as a module. If so, the module
745 will be called rtc-r9701.
746
747 config RTC_DRV_RX4581
748 tristate "Epson RX-4581"
749 help
750 If you say yes here you will get support for the Epson RX-4581.
751
752 This driver can also be built as a module. If so the module
753 will be called rtc-rx4581.
754
755 config RTC_DRV_RX6110
756 tristate "Epson RX-6110"
757 select REGMAP_SPI
758 help
759 If you say yes here you will get support for the Epson RX-6610.
760
761 This driver can also be built as a module. If so the module
762 will be called rtc-rx6110.
763
764 config RTC_DRV_RS5C348
765 tristate "Ricoh RS5C348A/B"
766 help
767 If you say yes here you get support for the
768 Ricoh RS5C348A and RS5C348B RTC chips.
769
770 This driver can also be built as a module. If so, the module
771 will be called rtc-rs5c348.
772
773 config RTC_DRV_MAX6902
774 tristate "Maxim MAX6902"
775 help
776 If you say yes here you will get support for the
777 Maxim MAX6902 SPI RTC chip.
778
779 This driver can also be built as a module. If so, the module
780 will be called rtc-max6902.
781
782 config RTC_DRV_PCF2123
783 tristate "NXP PCF2123"
784 help
785 If you say yes here you get support for the NXP PCF2123
786 RTC chip.
787
788 This driver can also be built as a module. If so, the module
789 will be called rtc-pcf2123.
790
791 config RTC_DRV_MCP795
792 tristate "Microchip MCP795"
793 help
794 If you say yes here you will get support for the Microchip MCP795.
795
796 This driver can also be built as a module. If so the module
797 will be called rtc-mcp795.
798
799 endif # SPI_MASTER
800
801 #
802 # Helper to resolve issues with configs that have SPI enabled but I2C
803 # modular. See SND_SOC_I2C_AND_SPI for more information
804 #
805 config RTC_I2C_AND_SPI
806 tristate
807 default m if I2C=m
808 default y if I2C=y
809 default y if SPI_MASTER=y
810 select REGMAP_I2C if I2C
811 select REGMAP_SPI if SPI_MASTER
812
813 comment "SPI and I2C RTC drivers"
814
815 config RTC_DRV_DS3232
816 tristate "Dallas/Maxim DS3232/DS3234"
817 depends on RTC_I2C_AND_SPI
818 help
819 If you say yes here you get support for Dallas Semiconductor
820 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
821 with the device, the alarm functionality is supported.
822
823 This driver can also be built as a module. If so, the module
824 will be called rtc-ds3232.
825
826 config RTC_DRV_DS3232_HWMON
827 bool "HWMON support for Dallas/Maxim DS3232/DS3234"
828 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
829 default y
830 help
831 Say Y here if you want to expose temperature sensor data on
832 rtc-ds3232
833
834 config RTC_DRV_PCF2127
835 tristate "NXP PCF2127"
836 depends on RTC_I2C_AND_SPI
837 help
838 If you say yes here you get support for the NXP PCF2127/29 RTC
839 chips.
840
841 This driver can also be built as a module. If so, the module
842 will be called rtc-pcf2127.
843
844 config RTC_DRV_RV3029C2
845 tristate "Micro Crystal RV3029/3049"
846 depends on RTC_I2C_AND_SPI
847 help
848 If you say yes here you get support for the Micro Crystal
849 RV3029 and RV3049 RTC chips.
850
851 This driver can also be built as a module. If so, the module
852 will be called rtc-rv3029c2.
853
854 config RTC_DRV_RV3029_HWMON
855 bool "HWMON support for RV3029/3049"
856 depends on RTC_DRV_RV3029C2 && HWMON
857 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
858 default y
859 help
860 Say Y here if you want to expose temperature sensor data on
861 rtc-rv3029.
862
863 comment "Platform RTC drivers"
864
865 # this 'CMOS' RTC driver is arch dependent because it requires
866 # <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
867 # global rtc_lock ... it's not yet just another platform_device.
868
869 config RTC_DRV_CMOS
870 tristate "PC-style 'CMOS'"
871 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64 || MN10300
872 default y if X86
873 select RTC_MC146818_LIB
874 help
875 Say "yes" here to get direct support for the real time clock
876 found in every PC or ACPI-based system, and some other boards.
877 Specifically the original MC146818, compatibles like those in
878 PC south bridges, the DS12887 or M48T86, some multifunction
879 or LPC bus chips, and so on.
880
881 Your system will need to define the platform device used by
882 this driver, otherwise it won't be accessible. This means
883 you can safely enable this driver if you don't know whether
884 or not your board has this kind of hardware.
885
886 This driver can also be built as a module. If so, the module
887 will be called rtc-cmos.
888
889 config RTC_DRV_ALPHA
890 bool "Alpha PC-style CMOS"
891 depends on ALPHA
892 select RTC_MC146818_LIB
893 default y
894 help
895 Direct support for the real-time clock found on every Alpha
896 system, specifically MC146818 compatibles. If in doubt, say Y.
897
898 config RTC_DRV_VRTC
899 tristate "Virtual RTC for Intel MID platforms"
900 depends on X86_INTEL_MID
901 default y if X86_INTEL_MID
902
903 help
904 Say "yes" here to get direct support for the real time clock
905 found on Moorestown platforms. The VRTC is a emulated RTC that
906 derives its clock source from a real RTC in the PMIC. The MC146818
907 style programming interface is mostly conserved, but any
908 updates are done via IPC calls to the system controller FW.
909
910 config RTC_DRV_DS1216
911 tristate "Dallas DS1216"
912 depends on SNI_RM
913 help
914 If you say yes here you get support for the Dallas DS1216 RTC chips.
915
916 config RTC_DRV_DS1286
917 tristate "Dallas DS1286"
918 depends on HAS_IOMEM
919 help
920 If you say yes here you get support for the Dallas DS1286 RTC chips.
921
922 config RTC_DRV_DS1511
923 tristate "Dallas DS1511"
924 depends on HAS_IOMEM
925 help
926 If you say yes here you get support for the
927 Dallas DS1511 timekeeping/watchdog chip.
928
929 This driver can also be built as a module. If so, the module
930 will be called rtc-ds1511.
931
932 config RTC_DRV_DS1553
933 tristate "Maxim/Dallas DS1553"
934 depends on HAS_IOMEM
935 help
936 If you say yes here you get support for the
937 Maxim/Dallas DS1553 timekeeping chip.
938
939 This driver can also be built as a module. If so, the module
940 will be called rtc-ds1553.
941
942 config RTC_DRV_DS1685_FAMILY
943 tristate "Dallas/Maxim DS1685 Family"
944 help
945 If you say yes here you get support for the Dallas/Maxim DS1685
946 family of real time chips. This family includes the DS1685/DS1687,
947 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
948 DS17885/DS17887 chips.
949
950 This driver can also be built as a module. If so, the module
951 will be called rtc-ds1685.
952
953 choice
954 prompt "Subtype"
955 depends on RTC_DRV_DS1685_FAMILY
956 default RTC_DRV_DS1685
957
958 config RTC_DRV_DS1685
959 bool "DS1685/DS1687"
960 help
961 This enables support for the Dallas/Maxim DS1685/DS1687 real time
962 clock chip.
963
964 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
965 systems, as well as EPPC-405-UC modules by electronic system design
966 GmbH.
967
968 config RTC_DRV_DS1689
969 bool "DS1689/DS1693"
970 help
971 This enables support for the Dallas/Maxim DS1689/DS1693 real time
972 clock chip.
973
974 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
975 which supports a few minor features such as Vcc, Vbat, and Power
976 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
977
978 It also works for the even older DS1688/DS1691 RTC chips, which are
979 virtually the same and carry the same model number. Both chips
980 have 114 bytes of user NVRAM.
981
982 config RTC_DRV_DS17285
983 bool "DS17285/DS17287"
984 help
985 This enables support for the Dallas/Maxim DS17285/DS17287 real time
986 clock chip.
987
988 This chip features 2kb of extended NV-SRAM. It may possibly be
989 found in some SGI O2 systems (rare).
990
991 config RTC_DRV_DS17485
992 bool "DS17485/DS17487"
993 help
994 This enables support for the Dallas/Maxim DS17485/DS17487 real time
995 clock chip.
996
997 This chip features 4kb of extended NV-SRAM.
998
999 config RTC_DRV_DS17885
1000 bool "DS17885/DS17887"
1001 help
1002 This enables support for the Dallas/Maxim DS17885/DS17887 real time
1003 clock chip.
1004
1005 This chip features 8kb of extended NV-SRAM.
1006
1007 endchoice
1008
1009 config RTC_DS1685_PROC_REGS
1010 bool "Display register values in /proc"
1011 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
1012 help
1013 Enable this to display a readout of all of the RTC registers in
1014 /proc/drivers/rtc. Keep in mind that this can potentially lead
1015 to lost interrupts, as reading Control Register C will clear
1016 all pending IRQ flags.
1017
1018 Unless you are debugging this driver, choose N.
1019
1020 config RTC_DS1685_SYSFS_REGS
1021 bool "SysFS access to RTC register bits"
1022 depends on RTC_DRV_DS1685_FAMILY && SYSFS
1023 help
1024 Enable this to provide access to the RTC control register bits
1025 in /sys. Some of the bits are read-write, others are read-only.
1026
1027 Keep in mind that reading Control C's bits automatically clears
1028 all pending IRQ flags - this can cause lost interrupts.
1029
1030 If you know that you need access to these bits, choose Y, Else N.
1031
1032 config RTC_DRV_DS1742
1033 tristate "Maxim/Dallas DS1742/1743"
1034 depends on HAS_IOMEM
1035 help
1036 If you say yes here you get support for the
1037 Maxim/Dallas DS1742/1743 timekeeping chip.
1038
1039 This driver can also be built as a module. If so, the module
1040 will be called rtc-ds1742.
1041
1042 config RTC_DRV_DS2404
1043 tristate "Maxim/Dallas DS2404"
1044 help
1045 If you say yes here you get support for the
1046 Dallas DS2404 RTC chip.
1047
1048 This driver can also be built as a module. If so, the module
1049 will be called rtc-ds2404.
1050
1051 config RTC_DRV_DA9052
1052 tristate "Dialog DA9052/DA9053 RTC"
1053 depends on PMIC_DA9052
1054 help
1055 Say y here to support the RTC driver for Dialog Semiconductor
1056 DA9052-BC and DA9053-AA/Bx PMICs.
1057
1058 config RTC_DRV_DA9055
1059 tristate "Dialog Semiconductor DA9055 RTC"
1060 depends on MFD_DA9055
1061 help
1062 If you say yes here you will get support for the
1063 RTC of the Dialog DA9055 PMIC.
1064
1065 This driver can also be built as a module. If so, the module
1066 will be called rtc-da9055
1067
1068 config RTC_DRV_DA9063
1069 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1070 depends on MFD_DA9063 || MFD_DA9062
1071 help
1072 If you say yes here you will get support for the RTC subsystem
1073 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1074
1075 This driver can also be built as a module. If so, the module
1076 will be called "rtc-da9063".
1077
1078 config RTC_DRV_EFI
1079 tristate "EFI RTC"
1080 depends on EFI && !X86
1081 help
1082 If you say yes here you will get support for the EFI
1083 Real Time Clock.
1084
1085 This driver can also be built as a module. If so, the module
1086 will be called rtc-efi.
1087
1088 config RTC_DRV_STK17TA8
1089 tristate "Simtek STK17TA8"
1090 depends on HAS_IOMEM
1091 help
1092 If you say yes here you get support for the
1093 Simtek STK17TA8 timekeeping chip.
1094
1095 This driver can also be built as a module. If so, the module
1096 will be called rtc-stk17ta8.
1097
1098 config RTC_DRV_M48T86
1099 tristate "ST M48T86/Dallas DS12887"
1100 help
1101 If you say Y here you will get support for the
1102 ST M48T86 and Dallas DS12887 RTC chips.
1103
1104 This driver can also be built as a module. If so, the module
1105 will be called rtc-m48t86.
1106
1107 config RTC_DRV_M48T35
1108 tristate "ST M48T35"
1109 depends on HAS_IOMEM
1110 help
1111 If you say Y here you will get support for the
1112 ST M48T35 RTC chip.
1113
1114 This driver can also be built as a module, if so, the module
1115 will be called "rtc-m48t35".
1116
1117 config RTC_DRV_M48T59
1118 tristate "ST M48T59/M48T08/M48T02"
1119 depends on HAS_IOMEM
1120 help
1121 If you say Y here you will get support for the
1122 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1123
1124 These chips are usually found in Sun SPARC and UltraSPARC
1125 workstations.
1126
1127 This driver can also be built as a module, if so, the module
1128 will be called "rtc-m48t59".
1129
1130 config RTC_DRV_MSM6242
1131 tristate "Oki MSM6242"
1132 depends on HAS_IOMEM
1133 help
1134 If you say yes here you get support for the Oki MSM6242
1135 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1136
1137 This driver can also be built as a module. If so, the module
1138 will be called rtc-msm6242.
1139
1140 config RTC_DRV_BQ4802
1141 tristate "TI BQ4802"
1142 depends on HAS_IOMEM
1143 help
1144 If you say Y here you will get support for the TI
1145 BQ4802 RTC chip.
1146
1147 This driver can also be built as a module. If so, the module
1148 will be called rtc-bq4802.
1149
1150 config RTC_DRV_RP5C01
1151 tristate "Ricoh RP5C01"
1152 depends on HAS_IOMEM
1153 help
1154 If you say yes here you get support for the Ricoh RP5C01
1155 timekeeping chip. It is used in some Amiga models (e.g. A3000
1156 and A4000).
1157
1158 This driver can also be built as a module. If so, the module
1159 will be called rtc-rp5c01.
1160
1161 config RTC_DRV_V3020
1162 tristate "EM Microelectronic V3020"
1163 help
1164 If you say yes here you will get support for the
1165 EM Microelectronic v3020 RTC chip.
1166
1167 This driver can also be built as a module. If so, the module
1168 will be called rtc-v3020.
1169
1170 config RTC_DRV_WM831X
1171 tristate "Wolfson Microelectronics WM831x RTC"
1172 depends on MFD_WM831X
1173 help
1174 If you say yes here you will get support for the RTC subsystem
1175 of the Wolfson Microelectronics WM831X series PMICs.
1176
1177 This driver can also be built as a module. If so, the module
1178 will be called "rtc-wm831x".
1179
1180 config RTC_DRV_WM8350
1181 tristate "Wolfson Microelectronics WM8350 RTC"
1182 depends on MFD_WM8350
1183 help
1184 If you say yes here you will get support for the RTC subsystem
1185 of the Wolfson Microelectronics WM8350.
1186
1187 This driver can also be built as a module. If so, the module
1188 will be called "rtc-wm8350".
1189
1190 config RTC_DRV_SC27XX
1191 tristate "Spreadtrum SC27xx RTC"
1192 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1193 help
1194 If you say Y here you will get support for the RTC subsystem
1195 of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs
1196 includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips.
1197
1198 This driver can also be built as a module. If so, the module
1199 will be called rtc-sc27xx.
1200
1201 config RTC_DRV_SPEAR
1202 tristate "SPEAR ST RTC"
1203 depends on PLAT_SPEAR || COMPILE_TEST
1204 default y
1205 help
1206 If you say Y here you will get support for the RTC found on
1207 spear
1208
1209 config RTC_DRV_PCF50633
1210 depends on MFD_PCF50633
1211 tristate "NXP PCF50633 RTC"
1212 help
1213 If you say yes here you get support for the RTC subsystem of the
1214 NXP PCF50633 used in embedded systems.
1215
1216 config RTC_DRV_AB3100
1217 tristate "ST-Ericsson AB3100 RTC"
1218 depends on AB3100_CORE
1219 default y if AB3100_CORE
1220 help
1221 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1222 support. This chip contains a battery- and capacitor-backed RTC.
1223
1224 config RTC_DRV_AB8500
1225 tristate "ST-Ericsson AB8500 RTC"
1226 depends on AB8500_CORE
1227 select RTC_INTF_DEV
1228 select RTC_INTF_DEV_UIE_EMUL
1229 help
1230 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1231 support. This chip contains a battery- and capacitor-backed RTC.
1232
1233 config RTC_DRV_NUC900
1234 tristate "NUC910/NUC920 RTC driver"
1235 depends on ARCH_W90X900 || COMPILE_TEST
1236 help
1237 If you say yes here you get support for the RTC subsystem of the
1238 NUC910/NUC920 used in embedded systems.
1239
1240 config RTC_DRV_OPAL
1241 tristate "IBM OPAL RTC driver"
1242 depends on PPC_POWERNV
1243 default y
1244 help
1245 If you say yes here you get support for the PowerNV platform RTC
1246 driver based on OPAL interfaces.
1247
1248 This driver can also be built as a module. If so, the module
1249 will be called rtc-opal.
1250
1251 config RTC_DRV_ZYNQMP
1252 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1253 depends on OF
1254 help
1255 If you say yes here you get support for the RTC controller found on
1256 Xilinx Zynq Ultrascale+ MPSoC.
1257
1258 comment "on-CPU RTC drivers"
1259
1260 config RTC_DRV_ASM9260
1261 tristate "Alphascale asm9260 RTC"
1262 depends on MACH_ASM9260 || COMPILE_TEST
1263 help
1264 If you say yes here you get support for the RTC on the
1265 Alphascale asm9260 SoC.
1266
1267 This driver can also be built as a module. If so, the module
1268 will be called rtc-asm9260.
1269
1270 config RTC_DRV_DAVINCI
1271 tristate "TI DaVinci RTC"
1272 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1273 help
1274 If you say yes here you get support for the RTC on the
1275 DaVinci platforms (DM365).
1276
1277 This driver can also be built as a module. If so, the module
1278 will be called rtc-davinci.
1279
1280 config RTC_DRV_DIGICOLOR
1281 tristate "Conexant Digicolor RTC"
1282 depends on ARCH_DIGICOLOR || COMPILE_TEST
1283 help
1284 If you say yes here you get support for the RTC on Conexant
1285 Digicolor platforms. This currently includes the CX92755 SoC.
1286
1287 This driver can also be built as a module. If so, the module
1288 will be called rtc-digicolor.
1289
1290 config RTC_DRV_IMXDI
1291 tristate "Freescale IMX DryIce Real Time Clock"
1292 depends on ARCH_MXC
1293 help
1294 Support for Freescale IMX DryIce RTC
1295
1296 This driver can also be built as a module, if so, the module
1297 will be called "rtc-imxdi".
1298
1299 config RTC_DRV_OMAP
1300 tristate "TI OMAP Real Time Clock"
1301 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1302 depends on OF
1303 depends on PINCTRL
1304 select GENERIC_PINCONF
1305 help
1306 Say "yes" here to support the on chip real time clock
1307 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1308
1309 This driver can also be built as a module, if so, module
1310 will be called rtc-omap.
1311
1312 config HAVE_S3C_RTC
1313 bool
1314 help
1315 This will include RTC support for Samsung SoCs. If
1316 you want to include RTC support for any machine, kindly
1317 select this in the respective mach-XXXX/Kconfig file.
1318
1319 config RTC_DRV_S3C
1320 tristate "Samsung S3C series SoC RTC"
1321 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1322 help
1323 RTC (Realtime Clock) driver for the clock inbuilt into the
1324 Samsung S3C24XX series of SoCs. This can provide periodic
1325 interrupt rates from 1Hz to 64Hz for user programs, and
1326 wakeup from Alarm.
1327
1328 The driver currently supports the common features on all the
1329 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1330 and S3C2442.
1331
1332 This driver can also be build as a module. If so, the module
1333 will be called rtc-s3c.
1334
1335 config RTC_DRV_EP93XX
1336 tristate "Cirrus Logic EP93XX"
1337 depends on ARCH_EP93XX || COMPILE_TEST
1338 help
1339 If you say yes here you get support for the
1340 RTC embedded in the Cirrus Logic EP93XX processors.
1341
1342 This driver can also be built as a module. If so, the module
1343 will be called rtc-ep93xx.
1344
1345 config RTC_DRV_SA1100
1346 tristate "SA11x0/PXA2xx/PXA910"
1347 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1348 help
1349 If you say Y here you will get access to the real time clock
1350 built into your SA11x0 or PXA2xx CPU.
1351
1352 To compile this driver as a module, choose M here: the
1353 module will be called rtc-sa1100.
1354
1355 config RTC_DRV_SH
1356 tristate "SuperH On-Chip RTC"
1357 depends on SUPERH || ARCH_RENESAS
1358 help
1359 Say Y here to enable support for the on-chip RTC found in
1360 most SuperH processors. This RTC is also found in RZ/A SoCs.
1361
1362 To compile this driver as a module, choose M here: the
1363 module will be called rtc-sh.
1364
1365 config RTC_DRV_VR41XX
1366 tristate "NEC VR41XX"
1367 depends on CPU_VR41XX || COMPILE_TEST
1368 help
1369 If you say Y here you will get access to the real time clock
1370 built into your NEC VR41XX CPU.
1371
1372 To compile this driver as a module, choose M here: the
1373 module will be called rtc-vr41xx.
1374
1375 config RTC_DRV_PL030
1376 tristate "ARM AMBA PL030 RTC"
1377 depends on ARM_AMBA
1378 help
1379 If you say Y here you will get access to ARM AMBA
1380 PrimeCell PL030 RTC found on certain ARM SOCs.
1381
1382 To compile this driver as a module, choose M here: the
1383 module will be called rtc-pl030.
1384
1385 config RTC_DRV_PL031
1386 tristate "ARM AMBA PL031 RTC"
1387 depends on ARM_AMBA
1388 help
1389 If you say Y here you will get access to ARM AMBA
1390 PrimeCell PL031 RTC found on certain ARM SOCs.
1391
1392 To compile this driver as a module, choose M here: the
1393 module will be called rtc-pl031.
1394
1395 config RTC_DRV_AT32AP700X
1396 tristate "AT32AP700X series RTC"
1397 depends on PLATFORM_AT32AP || COMPILE_TEST
1398 help
1399 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1400 AT32AP700x family processors.
1401
1402 config RTC_DRV_AT91RM9200
1403 tristate "AT91RM9200 or some AT91SAM9 RTC"
1404 depends on ARCH_AT91 || COMPILE_TEST
1405 help
1406 Driver for the internal RTC (Realtime Clock) module found on
1407 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1408 this is powered by the backup power supply.
1409
1410 config RTC_DRV_AT91SAM9
1411 tristate "AT91SAM9 RTT as RTC"
1412 depends on ARCH_AT91 || COMPILE_TEST
1413 select MFD_SYSCON
1414 help
1415 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1416 can be used as an RTC thanks to the backup power supply (e.g. a
1417 small coin cell battery) which keeps this block and the GPBR
1418 (General Purpose Backup Registers) block powered when the device
1419 is shutdown.
1420 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1421 probably want to use the real RTC block instead of the "RTT as an
1422 RTC" driver.
1423
1424 config RTC_DRV_AU1XXX
1425 tristate "Au1xxx Counter0 RTC support"
1426 depends on MIPS_ALCHEMY
1427 help
1428 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1429 counter) to be used as a RTC.
1430
1431 This driver can also be built as a module. If so, the module
1432 will be called rtc-au1xxx.
1433
1434 config RTC_DRV_BFIN
1435 tristate "Blackfin On-Chip RTC"
1436 depends on BLACKFIN && !BF561
1437 help
1438 If you say yes here you will get support for the
1439 Blackfin On-Chip Real Time Clock.
1440
1441 This driver can also be built as a module. If so, the module
1442 will be called rtc-bfin.
1443
1444 config RTC_DRV_RS5C313
1445 tristate "Ricoh RS5C313"
1446 depends on SH_LANDISK
1447 help
1448 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1449
1450 config RTC_DRV_GENERIC
1451 tristate "Generic RTC support"
1452 # Please consider writing a new RTC driver instead of using the generic
1453 # RTC abstraction
1454 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
1455 help
1456 Say Y or M here to enable RTC support on systems using the generic
1457 RTC abstraction. If you do not know what you are doing, you should
1458 just say Y.
1459
1460 config RTC_DRV_PXA
1461 tristate "PXA27x/PXA3xx"
1462 depends on ARCH_PXA
1463 select RTC_DRV_SA1100
1464 help
1465 If you say Y here you will get access to the real time clock
1466 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1467 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1468
1469 This RTC driver uses PXA RTC registers available since pxa27x
1470 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1471
1472 config RTC_DRV_VT8500
1473 tristate "VIA/WonderMedia 85xx SoC RTC"
1474 depends on ARCH_VT8500 || COMPILE_TEST
1475 help
1476 If you say Y here you will get access to the real time clock
1477 built into your VIA VT8500 SoC or its relatives.
1478
1479
1480 config RTC_DRV_SUN4V
1481 bool "SUN4V Hypervisor RTC"
1482 depends on SPARC64
1483 help
1484 If you say Y here you will get support for the Hypervisor
1485 based RTC on SUN4V systems.
1486
1487 config RTC_DRV_SUN6I
1488 bool "Allwinner A31 RTC"
1489 default MACH_SUN6I || MACH_SUN8I
1490 depends on COMMON_CLK
1491 depends on ARCH_SUNXI || COMPILE_TEST
1492 help
1493 If you say Y here you will get support for the RTC found in
1494 some Allwinner SoCs like the A31 or the A64.
1495
1496 config RTC_DRV_SUNXI
1497 tristate "Allwinner sun4i/sun7i RTC"
1498 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1499 help
1500 If you say Y here you will get support for the RTC found on
1501 Allwinner A10/A20.
1502
1503 config RTC_DRV_STARFIRE
1504 bool "Starfire RTC"
1505 depends on SPARC64
1506 help
1507 If you say Y here you will get support for the RTC found on
1508 Starfire systems.
1509
1510 config RTC_DRV_TX4939
1511 tristate "TX4939 SoC"
1512 depends on SOC_TX4939
1513 help
1514 Driver for the internal RTC (Realtime Clock) module found on
1515 Toshiba TX4939 SoC.
1516
1517 config RTC_DRV_MV
1518 tristate "Marvell SoC RTC"
1519 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1520 help
1521 If you say yes here you will get support for the in-chip RTC
1522 that can be found in some of Marvell's SoC devices, such as
1523 the Kirkwood 88F6281 and 88F6192.
1524
1525 This driver can also be built as a module. If so, the module
1526 will be called rtc-mv.
1527
1528 config RTC_DRV_ARMADA38X
1529 tristate "Armada 38x Marvell SoC RTC"
1530 depends on ARCH_MVEBU || COMPILE_TEST
1531 help
1532 If you say yes here you will get support for the in-chip RTC
1533 that can be found in the Armada 38x Marvell's SoC device
1534
1535 This driver can also be built as a module. If so, the module
1536 will be called armada38x-rtc.
1537
1538 config RTC_DRV_FTRTC010
1539 tristate "Faraday Technology FTRTC010 RTC"
1540 depends on HAS_IOMEM
1541 default ARCH_GEMINI
1542 help
1543 If you say Y here you will get support for the
1544 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1545
1546 This driver can also be built as a module. If so, the module
1547 will be called rtc-ftrtc010.
1548
1549 config RTC_DRV_PS3
1550 tristate "PS3 RTC"
1551 depends on PPC_PS3
1552 help
1553 If you say yes here you will get support for the RTC on PS3.
1554
1555 This driver can also be built as a module. If so, the module
1556 will be called rtc-ps3.
1557
1558 config RTC_DRV_COH901331
1559 tristate "ST-Ericsson COH 901 331 RTC"
1560 depends on ARCH_U300 || COMPILE_TEST
1561 help
1562 If you say Y here you will get access to ST-Ericsson
1563 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1564 Platforms.
1565
1566 This driver can also be built as a module. If so, the module
1567 will be called "rtc-coh901331".
1568
1569
1570 config RTC_DRV_STMP
1571 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1572 depends on ARCH_MXS || COMPILE_TEST
1573 select STMP_DEVICE
1574 help
1575 If you say yes here you will get support for the onboard
1576 STMP3xxx/i.MX23/i.MX28 RTC.
1577
1578 This driver can also be built as a module. If so, the module
1579 will be called rtc-stmp3xxx.
1580
1581 config RTC_DRV_PCAP
1582 tristate "PCAP RTC"
1583 depends on EZX_PCAP
1584 help
1585 If you say Y here you will get support for the RTC found on
1586 the PCAP2 ASIC used on some Motorola phones.
1587
1588 config RTC_DRV_MC13XXX
1589 depends on MFD_MC13XXX
1590 tristate "Freescale MC13xxx RTC"
1591 help
1592 This enables support for the RTCs found on Freescale's PMICs
1593 MC13783 and MC13892.
1594
1595 config RTC_DRV_MPC5121
1596 tristate "Freescale MPC5121 built-in RTC"
1597 depends on PPC_MPC512x || PPC_MPC52xx
1598 help
1599 If you say yes here you will get support for the
1600 built-in RTC on MPC5121 or on MPC5200.
1601
1602 This driver can also be built as a module. If so, the module
1603 will be called rtc-mpc5121.
1604
1605 config RTC_DRV_JZ4740
1606 tristate "Ingenic JZ4740 SoC"
1607 depends on MACH_INGENIC || COMPILE_TEST
1608 help
1609 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1610 controllers.
1611
1612 This driver can also be buillt as a module. If so, the module
1613 will be called rtc-jz4740.
1614
1615 config RTC_DRV_LPC24XX
1616 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1617 depends on ARCH_LPC18XX || COMPILE_TEST
1618 depends on OF && HAS_IOMEM
1619 help
1620 This enables support for the NXP RTC found which can be found on
1621 NXP LPC178x/18xx/408x/43xx devices.
1622
1623 If you have one of the devices above enable this driver to use
1624 the hardware RTC. This driver can also be built as a module. If
1625 so, the module will be called rtc-lpc24xx.
1626
1627 config RTC_DRV_LPC32XX
1628 depends on ARCH_LPC32XX || COMPILE_TEST
1629 tristate "NXP LPC32XX RTC"
1630 help
1631 This enables support for the NXP RTC in the LPC32XX
1632
1633 This driver can also be built as a module. If so, the module
1634 will be called rtc-lpc32xx.
1635
1636 config RTC_DRV_PM8XXX
1637 tristate "Qualcomm PMIC8XXX RTC"
1638 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1639 help
1640 If you say yes here you get support for the
1641 Qualcomm PMIC8XXX RTC.
1642
1643 To compile this driver as a module, choose M here: the
1644 module will be called rtc-pm8xxx.
1645
1646 config RTC_DRV_TEGRA
1647 tristate "NVIDIA Tegra Internal RTC driver"
1648 depends on ARCH_TEGRA || COMPILE_TEST
1649 help
1650 If you say yes here you get support for the
1651 Tegra 200 series internal RTC module.
1652
1653 This drive can also be built as a module. If so, the module
1654 will be called rtc-tegra.
1655
1656 config RTC_DRV_TILE
1657 tristate "Tilera hypervisor RTC support"
1658 depends on TILE
1659 help
1660 Enable support for the Linux driver side of the Tilera
1661 hypervisor's real-time clock interface.
1662
1663 config RTC_DRV_PUV3
1664 tristate "PKUnity v3 RTC support"
1665 depends on ARCH_PUV3
1666 help
1667 This enables support for the RTC in the PKUnity-v3 SoCs.
1668
1669 This drive can also be built as a module. If so, the module
1670 will be called rtc-puv3.
1671
1672 config RTC_DRV_LOONGSON1
1673 tristate "loongson1 RTC support"
1674 depends on MACH_LOONGSON32
1675 help
1676 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1677 counter) to be used as a RTC.
1678
1679 This driver can also be built as a module. If so, the module
1680 will be called rtc-ls1x.
1681
1682 config RTC_DRV_MXC
1683 tristate "Freescale MXC Real Time Clock"
1684 depends on ARCH_MXC
1685 help
1686 If you say yes here you get support for the Freescale MXC
1687 RTC module.
1688
1689 This driver can also be built as a module, if so, the module
1690 will be called "rtc-mxc".
1691
1692 config RTC_DRV_SNVS
1693 tristate "Freescale SNVS RTC support"
1694 select REGMAP_MMIO
1695 depends on HAS_IOMEM
1696 depends on OF
1697 help
1698 If you say yes here you get support for the Freescale SNVS
1699 Low Power (LP) RTC module.
1700
1701 This driver can also be built as a module, if so, the module
1702 will be called "rtc-snvs".
1703
1704 config RTC_DRV_SIRFSOC
1705 tristate "SiRFSOC RTC"
1706 depends on ARCH_SIRF
1707 help
1708 Say "yes" here to support the real time clock on SiRF SOC chips.
1709 This driver can also be built as a module called rtc-sirfsoc.
1710
1711 config RTC_DRV_ST_LPC
1712 tristate "STMicroelectronics LPC RTC"
1713 depends on ARCH_STI
1714 depends on OF
1715 help
1716 Say Y here to include STMicroelectronics Low Power Controller
1717 (LPC) based RTC support.
1718
1719 To compile this driver as a module, choose M here: the
1720 module will be called rtc-st-lpc.
1721
1722 config RTC_DRV_MOXART
1723 tristate "MOXA ART RTC"
1724 depends on ARCH_MOXART || COMPILE_TEST
1725 help
1726 If you say yes here you get support for the MOXA ART
1727 RTC module.
1728
1729 This driver can also be built as a module. If so, the module
1730 will be called rtc-moxart
1731
1732 config RTC_DRV_MT6397
1733 tristate "MediaTek PMIC based RTC"
1734 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1735 help
1736 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1737 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1738 MediaTek(R) RTC driver.
1739
1740 If you want to use MediaTek(R) RTC interface, select Y or M here.
1741
1742 config RTC_DRV_MT7622
1743 tristate "MediaTek SoC based RTC"
1744 depends on ARCH_MEDIATEK || COMPILE_TEST
1745 help
1746 This enables support for the real time clock built in the MediaTek
1747 SoCs.
1748
1749 This drive can also be built as a module. If so, the module
1750 will be called rtc-mt7622.
1751
1752 config RTC_DRV_XGENE
1753 tristate "APM X-Gene RTC"
1754 depends on HAS_IOMEM
1755 depends on ARCH_XGENE || COMPILE_TEST
1756 help
1757 If you say yes here you get support for the APM X-Gene SoC real time
1758 clock.
1759
1760 This driver can also be built as a module, if so, the module
1761 will be called "rtc-xgene".
1762
1763 config RTC_DRV_PIC32
1764 tristate "Microchip PIC32 RTC"
1765 depends on MACH_PIC32
1766 default y
1767 help
1768 If you say yes here you get support for the PIC32 RTC module.
1769
1770 This driver can also be built as a module. If so, the module
1771 will be called rtc-pic32
1772
1773 config RTC_DRV_R7301
1774 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1775 select REGMAP_MMIO
1776 depends on OF && HAS_IOMEM
1777 help
1778 If you say yes here you get support for the EPSON TOYOCOM
1779 RTC-7301SF/DG chips.
1780
1781 This driver can also be built as a module. If so, the module
1782 will be called rtc-r7301.
1783
1784 config RTC_DRV_STM32
1785 tristate "STM32 RTC"
1786 select REGMAP_MMIO
1787 depends on ARCH_STM32 || COMPILE_TEST
1788 help
1789 If you say yes here you get support for the STM32 On-Chip
1790 Real Time Clock.
1791
1792 This driver can also be built as a module, if so, the module
1793 will be called "rtc-stm32".
1794
1795 config RTC_DRV_CPCAP
1796 depends on MFD_CPCAP
1797 tristate "Motorola CPCAP RTC"
1798 help
1799 Say y here for CPCAP rtc found on some Motorola phones
1800 and tablets such as Droid 4.
1801
1802 config RTC_DRV_RTD119X
1803 bool "Realtek RTD129x RTC"
1804 depends on ARCH_REALTEK || COMPILE_TEST
1805 default ARCH_REALTEK
1806 help
1807 If you say yes here, you get support for the RTD1295 SoC
1808 Real Time Clock.
1809
1810 comment "HID Sensor RTC drivers"
1811
1812 config RTC_DRV_HID_SENSOR_TIME
1813 tristate "HID Sensor Time"
1814 depends on USB_HID
1815 select IIO
1816 select HID_SENSOR_HUB
1817 select HID_SENSOR_IIO_COMMON
1818 help
1819 Say yes here to build support for the HID Sensors of type Time.
1820 This drivers makes such sensors available as RTCs.
1821
1822 If this driver is compiled as a module, it will be named
1823 rtc-hid-sensor-time.
1824
1825 config RTC_DRV_GOLDFISH
1826 tristate "Goldfish Real Time Clock"
1827 depends on MIPS && (GOLDFISH || COMPILE_TEST)
1828 help
1829 Say yes to enable RTC driver for the Goldfish based virtual platform.
1830
1831 Goldfish is a code name for the virtual platform developed by Google
1832 for Android emulation.
1833
1834 endif # RTC_CLASS