1 # SPDX-License-Identifier: GPL-2.0-only
3 # RTC class/drivers configuration
9 config RTC_MC146818_LIB
14 bool "Real Time Clock"
16 depends on !S390 && !UML
19 Generic RTC class support. If you say yes here, you will
20 be allowed to plug one or more RTCs to your system. You will
21 probably want to enable one or more of the interfaces below.
26 bool "Set system time from RTC on startup and resume"
29 If you say yes here, the system time (wall clock) will be set using
30 the value read from a specified RTC device. This is useful to avoid
31 unnecessary fsck runs at boot time, and to network better.
33 config RTC_HCTOSYS_DEVICE
34 string "RTC used to set the system time"
35 depends on RTC_HCTOSYS
38 The RTC device that will be used to (re)initialize the system
39 clock, usually rtc0. Initialization is done when the system
40 starts up, and when it resumes from a low power state. This
41 device should record time in UTC, since the kernel won't do
44 This clock should be battery-backed, so that it reads the correct
45 time when the system boots from a power-off state. Otherwise, your
46 system will need an external clock source (like an NTP server).
48 If the clock you specify here is not battery backed, it may still
49 be useful to reinitialize system time when resuming from system
50 sleep states. Do not specify an RTC here unless it stays powered
51 during all this system's supported sleep states.
54 bool "Set the RTC time based on NTP synchronization"
57 If you say yes here, the system time (wall clock) will be stored
58 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
59 minutes if userspace reports synchronized NTP status.
61 config RTC_SYSTOHC_DEVICE
62 string "RTC used to synchronize NTP adjustment"
63 depends on RTC_SYSTOHC
64 default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS
67 The RTC device used for NTP synchronization. The main difference
68 between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this
69 one can sleep when setting time, because it runs in the workqueue
73 bool "RTC debug support"
75 Say yes here to enable debugging support in the RTC framework
76 and individual RTC drivers.
79 bool "RTC non volatile storage support"
83 Say yes here to add support for the non volatile (often battery
84 backed) storage present on RTCs.
86 comment "RTC interfaces"
89 bool "/sys/class/rtc/rtcN (sysfs)"
93 Say yes here if you want to use your RTCs using sysfs interfaces,
94 /sys/class/rtc/rtc0 through /sys/.../rtcN.
99 bool "/proc/driver/rtc (procfs for rtcN)"
103 Say yes here if you want to use your system clock RTC through
104 the proc interface, /proc/driver/rtc.
105 Other RTCs will not be available through that API.
106 If there is no RTC for the system clock, then the first RTC(rtc0)
112 bool "/dev/rtcN (character devices)"
115 Say yes here if you want to use your RTCs using the /dev
116 interfaces, which "udev" sets up as /dev/rtc0 through
119 You may want to set up a symbolic link so one of these
120 can be accessed as /dev/rtc, which is a name
121 expected by "hwclock" and some other programs. Recent
122 versions of "udev" are known to set up the symlink for you.
126 config RTC_INTF_DEV_UIE_EMUL
127 bool "RTC UIE emulation on dev interface"
128 depends on RTC_INTF_DEV
130 Provides an emulation for RTC_UIE if the underlying rtc chip
131 driver does not expose RTC_UIE ioctls. Those requests generate
132 once-per-second update interrupts, used for synchronization.
134 The emulation code will read the time from the hardware
135 clock several times per second, please enable this option
136 only if you know that you really need it.
139 tristate "Test driver/device"
141 If you say yes here you get support for the
142 RTC test driver. It's a software RTC which can be
143 used to test the RTC subsystem APIs. It gets
144 the time from the system clock.
145 You want this driver only if you are doing development
146 on the RTC subsystem. Please read the source code
149 This driver can also be built as a module. If so, the module
150 will be called rtc-test.
152 comment "I2C RTC drivers"
156 config RTC_DRV_88PM860X
157 tristate "Marvell 88PM860x"
158 depends on MFD_88PM860X
160 If you say yes here you get support for RTC function in Marvell
163 This driver can also be built as a module. If so, the module
164 will be called rtc-88pm860x.
166 config RTC_DRV_88PM80X
167 tristate "Marvell 88PM80x"
168 depends on MFD_88PM800
170 If you say yes here you get support for RTC function in Marvell
173 This driver can also be built as a module. If so, the module
174 will be called rtc-88pm80x.
176 config RTC_DRV_ABB5ZES3
178 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
180 If you say yes here you get support for the Abracon
181 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
183 This driver can also be built as a module. If so, the module
184 will be called rtc-ab-b5ze-s3.
186 config RTC_DRV_ABEOZ9
188 tristate "Abracon AB-RTCMC-32.768kHz-EOZ9"
190 If you say yes here you get support for the Abracon
191 AB-RTCMC-32.768kHz-EOA9 I2C RTC chip.
193 This driver can also be built as a module. If so, the module
194 will be called rtc-ab-e0z9.
196 config RTC_DRV_ABX80X
197 tristate "Abracon ABx80x"
198 select WATCHDOG_CORE if WATCHDOG
200 If you say yes here you get support for Abracon AB080X and AB180X
201 families of ultra-low-power battery- and capacitor-backed real-time
204 This driver can also be built as a module. If so, the module
205 will be called rtc-abx80x.
208 tristate "X-Powers AC100"
211 If you say yes here you get support for the real-time clock found
212 in X-Powers AC100 family peripheral ICs.
214 This driver can also be built as a module. If so, the module
215 will be called rtc-ac100.
217 config RTC_DRV_BRCMSTB
218 tristate "Broadcom STB wake-timer"
219 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
220 default ARCH_BRCMSTB || BMIPS_GENERIC
222 If you say yes here you get support for the wake-timer found on
223 Broadcom STB SoCs (BCM7xxx).
225 This driver can also be built as a module. If so, the module will
226 be called rtc-brcmstb-waketimer.
228 config RTC_DRV_AS3722
229 tristate "ams AS3722 RTC driver"
230 depends on MFD_AS3722
232 If you say yes here you get support for the RTC of ams AS3722 PMIC
235 This driver can also be built as a module. If so, the module
236 will be called rtc-as3722.
238 config RTC_DRV_DS1307
239 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"
241 select WATCHDOG_CORE if WATCHDOG
243 If you say yes here you get support for various compatible RTC
244 chips (often with battery backup) connected with I2C. This driver
245 should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341,
246 ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.
247 In some cases the RTC must already have been initialized (by
248 manufacturing or a bootloader).
250 The first seven registers on these chips hold an RTC, and other
251 registers may add features such as NVRAM, a trickle charger for
252 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
253 sysfs, but other chip features may not be available.
255 This driver can also be built as a module. If so, the module
256 will be called rtc-ds1307.
258 config RTC_DRV_DS1307_CENTURY
259 bool "Century bit support for rtc-ds1307"
260 depends on RTC_DRV_DS1307
263 The DS1307 driver suffered from a bug where it was enabling the
264 century bit inconditionnally but never used it when reading the time.
265 It made the driver unable to support dates beyond 2099.
266 Setting this option will add proper support for the century bit but if
267 the time was previously set using a kernel predating this option,
268 reading the date will return a date in the next century.
269 To solve that, you could boot a kernel without this option set, set
270 the RTC date and then boot a kernel with this option set.
272 config RTC_DRV_DS1374
273 tristate "Dallas/Maxim DS1374"
275 If you say yes here you get support for Dallas Semiconductor
276 DS1374 real-time clock chips. If an interrupt is associated
277 with the device, the alarm functionality is supported.
279 This driver can also be built as a module. If so, the module
280 will be called rtc-ds1374.
282 config RTC_DRV_DS1374_WDT
283 bool "Dallas/Maxim DS1374 watchdog timer"
284 depends on RTC_DRV_DS1374 && WATCHDOG
287 If you say Y here you will get support for the
288 watchdog timer in the Dallas Semiconductor DS1374
289 real-time clock chips.
291 config RTC_DRV_DS1672
292 tristate "Dallas/Maxim DS1672"
294 If you say yes here you get support for the
295 Dallas/Maxim DS1672 timekeeping chip.
297 This driver can also be built as a module. If so, the module
298 will be called rtc-ds1672.
300 config RTC_DRV_HYM8563
301 tristate "Haoyu Microelectronics HYM8563"
304 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
305 from the usual rtc functions it provides a clock output of
308 This driver can also be built as a module. If so, the module
309 will be called rtc-hym8563.
311 config RTC_DRV_LP8788
312 tristate "TI LP8788 RTC driver"
313 depends on MFD_LP8788
315 Say Y to enable support for the LP8788 RTC/ALARM driver.
317 config RTC_DRV_MAX6900
318 tristate "Maxim MAX6900"
320 If you say yes here you will get support for the
321 Maxim MAX6900 I2C RTC chip.
323 This driver can also be built as a module. If so, the module
324 will be called rtc-max6900.
326 config RTC_DRV_MAX8907
327 tristate "Maxim MAX8907"
328 depends on MFD_MAX8907 || COMPILE_TEST
331 If you say yes here you will get support for the
332 RTC of Maxim MAX8907 PMIC.
334 This driver can also be built as a module. If so, the module
335 will be called rtc-max8907.
337 config RTC_DRV_MAX8925
338 tristate "Maxim MAX8925"
339 depends on MFD_MAX8925
341 If you say yes here you will get support for the
342 RTC of Maxim MAX8925 PMIC.
344 This driver can also be built as a module. If so, the module
345 will be called rtc-max8925.
347 config RTC_DRV_MAX8998
348 tristate "Maxim MAX8998"
349 depends on MFD_MAX8998
351 If you say yes here you will get support for the
352 RTC of Maxim MAX8998 PMIC.
354 This driver can also be built as a module. If so, the module
355 will be called rtc-max8998.
357 config RTC_DRV_MAX8997
358 tristate "Maxim MAX8997"
359 depends on MFD_MAX8997
361 If you say yes here you will get support for the
362 RTC of Maxim MAX8997 PMIC.
364 This driver can also be built as a module. If so, the module
365 will be called rtc-max8997.
367 config RTC_DRV_MAX77686
368 tristate "Maxim MAX77686"
369 depends on MFD_MAX77686 || MFD_MAX77620 || COMPILE_TEST
371 If you say yes here you will get support for the
372 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
374 This driver can also be built as a module. If so, the module
375 will be called rtc-max77686.
378 tristate "Rockchip RK805/RK808/RK809/RK817/RK818 RTC"
381 If you say yes here you will get support for the
382 RTC of RK805, RK809 and RK817, RK808 and RK818 PMIC.
384 This driver can also be built as a module. If so, the module
385 will be called rk808-rtc.
387 config RTC_DRV_RS5C372
388 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
390 If you say yes here you get support for the
391 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
393 This driver can also be built as a module. If so, the module
394 will be called rtc-rs5c372.
396 config RTC_DRV_ISL1208
397 tristate "Intersil ISL1208"
399 If you say yes here you get support for the
400 Intersil ISL1208 RTC chip.
402 This driver can also be built as a module. If so, the module
403 will be called rtc-isl1208.
405 config RTC_DRV_ISL12022
406 tristate "Intersil ISL12022"
408 If you say yes here you get support for the
409 Intersil ISL12022 RTC chip.
411 This driver can also be built as a module. If so, the module
412 will be called rtc-isl12022.
414 config RTC_DRV_ISL12026
415 tristate "Intersil ISL12026"
416 depends on OF || COMPILE_TEST
418 If you say yes here you get support for the
419 Intersil ISL12026 RTC chip.
421 This driver can also be built as a module. If so, the module
422 will be called rtc-isl12026.
425 tristate "Xicor/Intersil X1205"
427 If you say yes here you get support for the
428 Xicor/Intersil X1205 RTC chip.
430 This driver can also be built as a module. If so, the module
431 will be called rtc-x1205.
433 config RTC_DRV_PCF8523
434 tristate "NXP PCF8523"
436 If you say yes here you get support for the NXP PCF8523 RTC
439 This driver can also be built as a module. If so, the module
440 will be called rtc-pcf8523.
442 config RTC_DRV_PCF85063
443 tristate "NXP PCF85063"
446 If you say yes here you get support for the PCF85063 RTC chip
448 This driver can also be built as a module. If so, the module
449 will be called rtc-pcf85063.
451 config RTC_DRV_PCF85363
452 tristate "NXP PCF85363"
455 If you say yes here you get support for the PCF85363 RTC chip.
457 This driver can also be built as a module. If so, the module
458 will be called rtc-pcf85363.
460 The nvmem interface will be named pcf85363-#, where # is the
461 zero-based instance number.
463 config RTC_DRV_PCF8563
464 tristate "Philips PCF8563/Epson RTC8564"
466 If you say yes here you get support for the
467 Philips PCF8563 RTC chip. The Epson RTC8564
470 This driver can also be built as a module. If so, the module
471 will be called rtc-pcf8563.
473 config RTC_DRV_PCF8583
474 tristate "Philips PCF8583"
476 If you say yes here you get support for the Philips PCF8583
477 RTC chip found on Acorn RiscPCs. This driver supports the
478 platform specific method of retrieving the current year from
479 the RTC's SRAM. It will work on other platforms with the same
480 chip, but the year will probably have to be tweaked.
482 This driver can also be built as a module. If so, the module
483 will be called rtc-pcf8583.
485 config RTC_DRV_M41T80
486 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
488 If you say Y here you will get support for the ST M41T60
489 and M41T80 RTC chips series. Currently, the following chips are
490 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
491 M41ST85, M41ST87, and MicroCrystal RV4162.
493 This driver can also be built as a module. If so, the module
494 will be called rtc-m41t80.
496 config RTC_DRV_M41T80_WDT
497 bool "ST M41T65/M41T80 series RTC watchdog timer"
498 depends on RTC_DRV_M41T80
500 If you say Y here you will get support for the
501 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
503 config RTC_DRV_BD70528
504 tristate "ROHM BD70528 PMIC RTC"
505 depends on MFD_ROHM_BD70528 && (BD70528_WATCHDOG || !BD70528_WATCHDOG)
507 If you say Y here you will get support for the RTC
508 block on ROHM BD70528 and BD71828 Power Management IC.
510 This driver can also be built as a module. If so, the module
511 will be called rtc-bd70528.
514 tristate "TI BQ32000"
516 If you say Y here you will get support for the TI
517 BQ32000 I2C RTC chip.
519 This driver can also be built as a module. If so, the module
520 will be called rtc-bq32k.
522 config RTC_DRV_DM355EVM
523 tristate "TI DaVinci DM355 EVM RTC"
524 depends on MFD_DM355EVM_MSP
526 Supports the RTC firmware in the MSP430 on the DM355 EVM.
528 config RTC_DRV_TWL92330
529 bool "TI TWL92330/Menelaus"
532 If you say yes here you get support for the RTC on the
533 TWL92330 "Menelaus" power management chip, used with OMAP2
534 platforms. The support is integrated with the rest of
535 the Menelaus driver; it's not separate module.
537 config RTC_DRV_TWL4030
538 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
539 depends on TWL4030_CORE
542 If you say yes here you get support for the RTC on the
543 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
545 This driver can also be built as a module. If so, the module
546 will be called rtc-twl.
548 config RTC_DRV_PALMAS
549 tristate "TI Palmas RTC driver"
550 depends on MFD_PALMAS
552 If you say yes here you get support for the RTC of TI PALMA series PMIC
555 This driver can also be built as a module. If so, the module
556 will be called rtc-palma.
558 config RTC_DRV_TPS6586X
559 tristate "TI TPS6586X RTC driver"
560 depends on MFD_TPS6586X
562 TI Power Management IC TPS6586X supports RTC functionality
563 along with alarm. This driver supports the RTC driver for
564 the TPS6586X RTC module.
566 config RTC_DRV_TPS65910
567 tristate "TI TPS65910 RTC driver"
568 depends on MFD_TPS65910
570 If you say yes here you get support for the RTC on the
573 This driver can also be built as a module. If so, the module
574 will be called rtc-tps65910.
576 config RTC_DRV_TPS80031
577 tristate "TI TPS80031/TPS80032 RTC driver"
578 depends on MFD_TPS80031
580 TI Power Management IC TPS80031 supports RTC functionality
581 along with alarm. This driver supports the RTC driver for
582 the TPS80031 RTC module.
584 config RTC_DRV_RC5T583
585 tristate "RICOH 5T583 RTC driver"
586 depends on MFD_RC5T583
588 If you say yes here you get support for the RTC on the
591 This driver can also be built as a module. If so, the module
592 will be called rtc-rc5t583.
594 config RTC_DRV_RC5T619
595 tristate "RICOH RC5T619 RTC driver"
596 depends on MFD_RN5T618
598 If you say yes here you get support for the RTC on the
601 This driver can also be built as a module. If so, the module
602 will be called rtc-rc5t619.
604 config RTC_DRV_S35390A
605 tristate "Seiko Instruments S-35390A"
608 If you say yes here you will get support for the Seiko
609 Instruments S-35390A.
611 This driver can also be built as a module. If so the module
612 will be called rtc-s35390a.
614 config RTC_DRV_FM3130
615 tristate "Ramtron FM3130"
617 If you say Y here you will get support for the
618 Ramtron FM3130 RTC chips.
619 Ramtron FM3130 is a chip with two separate devices inside,
620 RTC clock and FRAM. This driver provides only RTC functionality.
622 This driver can also be built as a module. If so the module
623 will be called rtc-fm3130.
625 config RTC_DRV_RX8010
626 tristate "Epson RX8010SJ"
628 If you say yes here you get support for the Epson RX8010SJ RTC
631 This driver can also be built as a module. If so, the module
632 will be called rtc-rx8010.
634 config RTC_DRV_RX8581
635 tristate "Epson RX-8571/RX-8581"
638 If you say yes here you will get support for the Epson RX-8571/
641 This driver can also be built as a module. If so the module
642 will be called rtc-rx8581.
644 config RTC_DRV_RX8025
645 tristate "Epson RX-8025SA/NB"
647 If you say yes here you get support for the Epson
648 RX-8025SA/NB RTC chips.
650 This driver can also be built as a module. If so, the module
651 will be called rtc-rx8025.
653 config RTC_DRV_EM3027
654 tristate "EM Microelectronic EM3027"
656 If you say yes here you get support for the EM
657 Microelectronic EM3027 RTC chips.
659 This driver can also be built as a module. If so, the module
660 will be called rtc-em3027.
662 config RTC_DRV_RV3028
663 tristate "Micro Crystal RV3028"
666 If you say yes here you get support for the Micro Crystal
669 This driver can also be built as a module. If so, the module
670 will be called rtc-rv3028.
672 config RTC_DRV_RV8803
673 tristate "Micro Crystal RV8803, Epson RX8900"
675 If you say yes here you get support for the Micro Crystal RV8803 and
676 Epson RX8900 RTC chips.
678 This driver can also be built as a module. If so, the module
679 will be called rtc-rv8803.
682 tristate "Samsung S2M/S5M series"
683 depends on MFD_SEC_CORE || COMPILE_TEST
686 If you say yes here you will get support for the
687 RTC of Samsung S2MPS14 and S5M PMIC series.
689 This driver can also be built as a module. If so, the module
690 will be called rtc-s5m.
692 config RTC_DRV_SD3078
693 tristate "ZXW Shenzhen whwave SD3078"
696 If you say yes here you get support for the ZXW Shenzhen whwave
699 This driver can also be built as a module. If so, the module
700 will be called rtc-sd3078
704 comment "SPI RTC drivers"
708 config RTC_DRV_M41T93
711 If you say yes here you will get support for the
712 ST M41T93 SPI RTC chip.
714 This driver can also be built as a module. If so, the module
715 will be called rtc-m41t93.
717 config RTC_DRV_M41T94
720 If you say yes here you will get support for the
721 ST M41T94 SPI RTC chip.
723 This driver can also be built as a module. If so, the module
724 will be called rtc-m41t94.
726 config RTC_DRV_DS1302
727 tristate "Dallas/Maxim DS1302"
730 If you say yes here you get support for the Dallas DS1302 RTC chips.
732 This driver can also be built as a module. If so, the module
733 will be called rtc-ds1302.
735 config RTC_DRV_DS1305
736 tristate "Dallas/Maxim DS1305/DS1306"
738 Select this driver to get support for the Dallas/Maxim DS1305
739 and DS1306 real time clock chips. These support a trickle
740 charger, alarms, and NVRAM in addition to the clock.
742 This driver can also be built as a module. If so, the module
743 will be called rtc-ds1305.
745 config RTC_DRV_DS1343
747 tristate "Dallas/Maxim DS1343/DS1344"
749 If you say yes here you get support for the
750 Dallas/Maxim DS1343 and DS1344 real time clock chips.
751 Support for trickle charger, alarm is provided.
753 This driver can also be built as a module. If so, the module
754 will be called rtc-ds1343.
756 config RTC_DRV_DS1347
758 tristate "Dallas/Maxim DS1347"
760 If you say yes here you get support for the
761 Dallas/Maxim DS1347 chips.
763 This driver only supports the RTC feature, and not other chip
764 features such as alarms.
766 This driver can also be built as a module. If so, the module
767 will be called rtc-ds1347.
769 config RTC_DRV_DS1390
770 tristate "Dallas/Maxim DS1390/93/94"
772 If you say yes here you get support for the
773 Dallas/Maxim DS1390/93/94 chips.
775 This driver supports the RTC feature and trickle charging but not
776 other chip features such as alarms.
778 This driver can also be built as a module. If so, the module
779 will be called rtc-ds1390.
781 config RTC_DRV_MAX6916
782 tristate "Maxim MAX6916"
784 If you say yes here you will get support for the
785 Maxim MAX6916 SPI RTC chip.
787 This driver only supports the RTC feature, and not other chip
788 features such as alarms.
790 This driver can also be built as a module. If so, the module
791 will be called rtc-max6916.
794 tristate "Epson RTC-9701JE"
796 If you say yes here you will get support for the
797 Epson RTC-9701JE SPI RTC chip.
799 This driver can also be built as a module. If so, the module
800 will be called rtc-r9701.
802 config RTC_DRV_RX4581
803 tristate "Epson RX-4581"
805 If you say yes here you will get support for the Epson RX-4581.
807 This driver can also be built as a module. If so the module
808 will be called rtc-rx4581.
810 config RTC_DRV_RX6110
811 tristate "Epson RX-6110"
814 If you say yes here you will get support for the Epson RX-6610.
816 This driver can also be built as a module. If so the module
817 will be called rtc-rx6110.
819 config RTC_DRV_RS5C348
820 tristate "Ricoh RS5C348A/B"
822 If you say yes here you get support for the
823 Ricoh RS5C348A and RS5C348B RTC chips.
825 This driver can also be built as a module. If so, the module
826 will be called rtc-rs5c348.
828 config RTC_DRV_MAX6902
829 tristate "Maxim MAX6902"
831 If you say yes here you will get support for the
832 Maxim MAX6902 SPI RTC chip.
834 This driver can also be built as a module. If so, the module
835 will be called rtc-max6902.
837 config RTC_DRV_PCF2123
838 tristate "NXP PCF2123"
841 If you say yes here you get support for the NXP PCF2123
844 This driver can also be built as a module. If so, the module
845 will be called rtc-pcf2123.
847 config RTC_DRV_MCP795
848 tristate "Microchip MCP795"
850 If you say yes here you will get support for the Microchip MCP795.
852 This driver can also be built as a module. If so the module
853 will be called rtc-mcp795.
858 # Helper to resolve issues with configs that have SPI enabled but I2C
859 # modular. See SND_SOC_I2C_AND_SPI for more information
861 config RTC_I2C_AND_SPI
865 default y if SPI_MASTER=y
867 comment "SPI and I2C RTC drivers"
869 config RTC_DRV_DS3232
870 tristate "Dallas/Maxim DS3232/DS3234"
871 depends on RTC_I2C_AND_SPI
872 select REGMAP_I2C if I2C
873 select REGMAP_SPI if SPI_MASTER
875 If you say yes here you get support for Dallas Semiconductor
876 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
877 with the device, the alarm functionality is supported.
879 This driver can also be built as a module. If so, the module
880 will be called rtc-ds3232.
882 config RTC_DRV_DS3232_HWMON
883 bool "HWMON support for Dallas/Maxim DS3232/DS3234"
884 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
887 Say Y here if you want to expose temperature sensor data on
890 config RTC_DRV_PCF2127
891 tristate "NXP PCF2127"
892 depends on RTC_I2C_AND_SPI
893 select REGMAP_I2C if I2C
894 select REGMAP_SPI if SPI_MASTER
895 select WATCHDOG_CORE if WATCHDOG
897 If you say yes here you get support for the NXP PCF2127/29 RTC
898 chips with integrated quartz crystal for industrial applications.
899 Both chips also have watchdog timer and tamper switch detection
902 PCF2127 has an additional feature of 512 bytes battery backed
903 memory that's accessible using nvmem interface.
905 This driver can also be built as a module. If so, the module
906 will be called rtc-pcf2127.
908 config RTC_DRV_RV3029C2
909 tristate "Micro Crystal RV3029/3049"
910 depends on RTC_I2C_AND_SPI
911 select REGMAP_I2C if I2C
912 select REGMAP_SPI if SPI_MASTER
914 If you say yes here you get support for the Micro Crystal
915 RV3029 and RV3049 RTC chips.
917 This driver can also be built as a module. If so, the module
918 will be called rtc-rv3029c2.
920 config RTC_DRV_RV3029_HWMON
921 bool "HWMON support for RV3029/3049"
922 depends on RTC_DRV_RV3029C2 && HWMON
923 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
926 Say Y here if you want to expose temperature sensor data on
929 comment "Platform RTC drivers"
931 # this 'CMOS' RTC driver is arch dependent because it requires
932 # <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
933 # global rtc_lock ... it's not yet just another platform_device.
936 tristate "PC-style 'CMOS'"
937 depends on X86 || ARM || PPC || MIPS || SPARC64
939 select RTC_MC146818_LIB
941 Say "yes" here to get direct support for the real time clock
942 found in every PC or ACPI-based system, and some other boards.
943 Specifically the original MC146818, compatibles like those in
944 PC south bridges, the DS12887 or M48T86, some multifunction
945 or LPC bus chips, and so on.
947 Your system will need to define the platform device used by
948 this driver, otherwise it won't be accessible. This means
949 you can safely enable this driver if you don't know whether
950 or not your board has this kind of hardware.
952 This driver can also be built as a module. If so, the module
953 will be called rtc-cmos.
956 bool "Alpha PC-style CMOS"
958 select RTC_MC146818_LIB
961 Direct support for the real-time clock found on every Alpha
962 system, specifically MC146818 compatibles. If in doubt, say Y.
965 tristate "Virtual RTC for Intel MID platforms"
966 depends on X86_INTEL_MID
967 default y if X86_INTEL_MID
970 Say "yes" here to get direct support for the real time clock
971 found on Moorestown platforms. The VRTC is a emulated RTC that
972 derives its clock source from a real RTC in the PMIC. The MC146818
973 style programming interface is mostly conserved, but any
974 updates are done via IPC calls to the system controller FW.
976 config RTC_DRV_DS1216
977 tristate "Dallas DS1216"
980 If you say yes here you get support for the Dallas DS1216 RTC chips.
982 config RTC_DRV_DS1286
983 tristate "Dallas DS1286"
986 If you say yes here you get support for the Dallas DS1286 RTC chips.
988 config RTC_DRV_DS1511
989 tristate "Dallas DS1511"
992 If you say yes here you get support for the
993 Dallas DS1511 timekeeping/watchdog chip.
995 This driver can also be built as a module. If so, the module
996 will be called rtc-ds1511.
998 config RTC_DRV_DS1553
999 tristate "Maxim/Dallas DS1553"
1000 depends on HAS_IOMEM
1002 If you say yes here you get support for the
1003 Maxim/Dallas DS1553 timekeeping chip.
1005 This driver can also be built as a module. If so, the module
1006 will be called rtc-ds1553.
1008 config RTC_DRV_DS1685_FAMILY
1009 tristate "Dallas/Maxim DS1685 Family"
1011 If you say yes here you get support for the Dallas/Maxim DS1685
1012 family of real time chips. This family includes the DS1685/DS1687,
1013 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
1014 DS17885/DS17887 chips.
1016 This driver can also be built as a module. If so, the module
1017 will be called rtc-ds1685.
1021 depends on RTC_DRV_DS1685_FAMILY
1022 default RTC_DRV_DS1685
1024 config RTC_DRV_DS1685
1025 bool "DS1685/DS1687"
1027 This enables support for the Dallas/Maxim DS1685/DS1687 real time
1030 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
1031 systems, as well as EPPC-405-UC modules by electronic system design
1034 config RTC_DRV_DS1689
1035 bool "DS1689/DS1693"
1037 This enables support for the Dallas/Maxim DS1689/DS1693 real time
1040 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
1041 which supports a few minor features such as Vcc, Vbat, and Power
1042 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
1044 It also works for the even older DS1688/DS1691 RTC chips, which are
1045 virtually the same and carry the same model number. Both chips
1046 have 114 bytes of user NVRAM.
1048 config RTC_DRV_DS17285
1049 bool "DS17285/DS17287"
1051 This enables support for the Dallas/Maxim DS17285/DS17287 real time
1054 This chip features 2kb of extended NV-SRAM. It may possibly be
1055 found in some SGI O2 systems (rare).
1057 config RTC_DRV_DS17485
1058 bool "DS17485/DS17487"
1060 This enables support for the Dallas/Maxim DS17485/DS17487 real time
1063 This chip features 4kb of extended NV-SRAM.
1065 config RTC_DRV_DS17885
1066 bool "DS17885/DS17887"
1068 This enables support for the Dallas/Maxim DS17885/DS17887 real time
1071 This chip features 8kb of extended NV-SRAM.
1075 config RTC_DRV_DS1742
1076 tristate "Maxim/Dallas DS1742/1743"
1077 depends on HAS_IOMEM
1079 If you say yes here you get support for the
1080 Maxim/Dallas DS1742/1743 timekeeping chip.
1082 This driver can also be built as a module. If so, the module
1083 will be called rtc-ds1742.
1085 config RTC_DRV_DS2404
1086 tristate "Maxim/Dallas DS2404"
1088 If you say yes here you get support for the
1089 Dallas DS2404 RTC chip.
1091 This driver can also be built as a module. If so, the module
1092 will be called rtc-ds2404.
1094 config RTC_DRV_DA9052
1095 tristate "Dialog DA9052/DA9053 RTC"
1096 depends on PMIC_DA9052
1098 Say y here to support the RTC driver for Dialog Semiconductor
1099 DA9052-BC and DA9053-AA/Bx PMICs.
1101 config RTC_DRV_DA9055
1102 tristate "Dialog Semiconductor DA9055 RTC"
1103 depends on MFD_DA9055
1105 If you say yes here you will get support for the
1106 RTC of the Dialog DA9055 PMIC.
1108 This driver can also be built as a module. If so, the module
1109 will be called rtc-da9055
1111 config RTC_DRV_DA9063
1112 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1113 depends on MFD_DA9063 || MFD_DA9062
1115 If you say yes here you will get support for the RTC subsystem
1116 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1118 This driver can also be built as a module. If so, the module
1119 will be called "rtc-da9063".
1123 depends on EFI && !X86
1125 If you say yes here you will get support for the EFI
1128 This driver can also be built as a module. If so, the module
1129 will be called rtc-efi.
1131 config RTC_DRV_STK17TA8
1132 tristate "Simtek STK17TA8"
1133 depends on HAS_IOMEM
1135 If you say yes here you get support for the
1136 Simtek STK17TA8 timekeeping chip.
1138 This driver can also be built as a module. If so, the module
1139 will be called rtc-stk17ta8.
1141 config RTC_DRV_M48T86
1142 tristate "ST M48T86/Dallas DS12887"
1144 If you say Y here you will get support for the
1145 ST M48T86 and Dallas DS12887 RTC chips.
1147 This driver can also be built as a module. If so, the module
1148 will be called rtc-m48t86.
1150 config RTC_DRV_M48T35
1151 tristate "ST M48T35"
1152 depends on HAS_IOMEM
1154 If you say Y here you will get support for the
1157 This driver can also be built as a module, if so, the module
1158 will be called "rtc-m48t35".
1160 config RTC_DRV_M48T59
1161 tristate "ST M48T59/M48T08/M48T02"
1162 depends on HAS_IOMEM
1164 If you say Y here you will get support for the
1165 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1167 These chips are usually found in Sun SPARC and UltraSPARC
1170 This driver can also be built as a module, if so, the module
1171 will be called "rtc-m48t59".
1173 config RTC_DRV_MSM6242
1174 tristate "Oki MSM6242"
1175 depends on HAS_IOMEM
1177 If you say yes here you get support for the Oki MSM6242
1178 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1180 This driver can also be built as a module. If so, the module
1181 will be called rtc-msm6242.
1183 config RTC_DRV_BQ4802
1184 tristate "TI BQ4802"
1185 depends on HAS_IOMEM
1187 If you say Y here you will get support for the TI
1190 This driver can also be built as a module. If so, the module
1191 will be called rtc-bq4802.
1193 config RTC_DRV_RP5C01
1194 tristate "Ricoh RP5C01"
1195 depends on HAS_IOMEM
1197 If you say yes here you get support for the Ricoh RP5C01
1198 timekeeping chip. It is used in some Amiga models (e.g. A3000
1201 This driver can also be built as a module. If so, the module
1202 will be called rtc-rp5c01.
1204 config RTC_DRV_V3020
1205 tristate "EM Microelectronic V3020"
1207 If you say yes here you will get support for the
1208 EM Microelectronic v3020 RTC chip.
1210 This driver can also be built as a module. If so, the module
1211 will be called rtc-v3020.
1213 config RTC_DRV_WM831X
1214 tristate "Wolfson Microelectronics WM831x RTC"
1215 depends on MFD_WM831X
1217 If you say yes here you will get support for the RTC subsystem
1218 of the Wolfson Microelectronics WM831X series PMICs.
1220 This driver can also be built as a module. If so, the module
1221 will be called "rtc-wm831x".
1223 config RTC_DRV_WM8350
1224 tristate "Wolfson Microelectronics WM8350 RTC"
1225 depends on MFD_WM8350
1227 If you say yes here you will get support for the RTC subsystem
1228 of the Wolfson Microelectronics WM8350.
1230 This driver can also be built as a module. If so, the module
1231 will be called "rtc-wm8350".
1233 config RTC_DRV_SC27XX
1234 tristate "Spreadtrum SC27xx RTC"
1235 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1237 If you say Y here you will get support for the RTC subsystem
1238 of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs
1239 includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips.
1241 This driver can also be built as a module. If so, the module
1242 will be called rtc-sc27xx.
1244 config RTC_DRV_SPEAR
1245 tristate "SPEAR ST RTC"
1246 depends on PLAT_SPEAR || COMPILE_TEST
1249 If you say Y here you will get support for the RTC found on
1252 config RTC_DRV_PCF50633
1253 depends on MFD_PCF50633
1254 tristate "NXP PCF50633 RTC"
1256 If you say yes here you get support for the RTC subsystem of the
1257 NXP PCF50633 used in embedded systems.
1259 config RTC_DRV_AB3100
1260 tristate "ST-Ericsson AB3100 RTC"
1261 depends on AB3100_CORE
1262 default y if AB3100_CORE
1264 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1265 support. This chip contains a battery- and capacitor-backed RTC.
1267 config RTC_DRV_AB8500
1268 tristate "ST-Ericsson AB8500 RTC"
1269 depends on AB8500_CORE
1271 select RTC_INTF_DEV_UIE_EMUL
1273 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1274 support. This chip contains a battery- and capacitor-backed RTC.
1277 tristate "IBM OPAL RTC driver"
1278 depends on PPC_POWERNV
1281 If you say yes here you get support for the PowerNV platform RTC
1282 driver based on OPAL interfaces.
1284 This driver can also be built as a module. If so, the module
1285 will be called rtc-opal.
1287 config RTC_DRV_ZYNQMP
1288 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1291 If you say yes here you get support for the RTC controller found on
1292 Xilinx Zynq Ultrascale+ MPSoC.
1294 config RTC_DRV_CROS_EC
1295 tristate "Chrome OS EC RTC driver"
1298 If you say yes here you will get support for the
1299 Chrome OS Embedded Controller's RTC.
1301 This driver can also be built as a module. If so, the module
1302 will be called rtc-cros-ec.
1304 comment "on-CPU RTC drivers"
1306 config RTC_DRV_ASM9260
1307 tristate "Alphascale asm9260 RTC"
1308 depends on MACH_ASM9260 || COMPILE_TEST
1310 If you say yes here you get support for the RTC on the
1311 Alphascale asm9260 SoC.
1313 This driver can also be built as a module. If so, the module
1314 will be called rtc-asm9260.
1316 config RTC_DRV_DAVINCI
1317 tristate "TI DaVinci RTC"
1318 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1320 If you say yes here you get support for the RTC on the
1321 DaVinci platforms (DM365).
1323 This driver can also be built as a module. If so, the module
1324 will be called rtc-davinci.
1326 config RTC_DRV_DIGICOLOR
1327 tristate "Conexant Digicolor RTC"
1328 depends on ARCH_DIGICOLOR || COMPILE_TEST
1330 If you say yes here you get support for the RTC on Conexant
1331 Digicolor platforms. This currently includes the CX92755 SoC.
1333 This driver can also be built as a module. If so, the module
1334 will be called rtc-digicolor.
1336 config RTC_DRV_IMXDI
1337 tristate "Freescale IMX DryIce Real Time Clock"
1340 Support for Freescale IMX DryIce RTC
1342 This driver can also be built as a module, if so, the module
1343 will be called "rtc-imxdi".
1345 config RTC_DRV_FSL_FTM_ALARM
1346 tristate "Freescale FlexTimer alarm timer"
1347 depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST
1349 For the FlexTimer in LS1012A, LS1021A, LS1028A, LS1043A, LS1046A,
1350 LS1088A, LS208xA, we can use FTM as the wakeup source.
1352 Say y here to enable FTM alarm support. The FTM alarm provides
1353 alarm functions for wakeup system from deep sleep.
1355 This driver can also be built as a module, if so, the module
1356 will be called "rtc-fsl-ftm-alarm".
1358 config RTC_DRV_MESON
1359 tristate "Amlogic Meson RTC"
1360 depends on (ARM && ARCH_MESON) || COMPILE_TEST
1363 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1366 This driver can also be built as a module, if so, the module
1367 will be called "rtc-meson".
1369 config RTC_DRV_MESON_VRTC
1370 tristate "Amlogic Meson Virtual RTC"
1371 depends on ARCH_MESON || COMPILE_TEST
1372 default m if ARCH_MESON
1374 If you say yes here you will get support for the
1375 Virtual RTC of Amlogic SoCs.
1377 This driver can also be built as a module. If so, the module
1378 will be called rtc-meson-vrtc.
1381 tristate "TI OMAP Real Time Clock"
1382 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1385 select GENERIC_PINCONF
1387 Say "yes" here to support the on chip real time clock
1388 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1390 This driver can also be built as a module, if so, module
1391 will be called rtc-omap.
1396 This will include RTC support for Samsung SoCs. If
1397 you want to include RTC support for any machine, kindly
1398 select this in the respective mach-XXXX/Kconfig file.
1401 tristate "Samsung S3C series SoC RTC"
1402 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1404 RTC (Realtime Clock) driver for the clock inbuilt into the
1405 Samsung S3C24XX series of SoCs. This can provide periodic
1406 interrupt rates from 1Hz to 64Hz for user programs, and
1409 The driver currently supports the common features on all the
1410 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1413 This driver can also be build as a module. If so, the module
1414 will be called rtc-s3c.
1416 config RTC_DRV_EP93XX
1417 tristate "Cirrus Logic EP93XX"
1418 depends on ARCH_EP93XX || COMPILE_TEST
1420 If you say yes here you get support for the
1421 RTC embedded in the Cirrus Logic EP93XX processors.
1423 This driver can also be built as a module. If so, the module
1424 will be called rtc-ep93xx.
1426 config RTC_DRV_SA1100
1427 tristate "SA11x0/PXA2xx/PXA910"
1428 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1430 If you say Y here you will get access to the real time clock
1431 built into your SA11x0 or PXA2xx CPU.
1433 To compile this driver as a module, choose M here: the
1434 module will be called rtc-sa1100.
1437 tristate "SuperH On-Chip RTC"
1438 depends on SUPERH || ARCH_RENESAS
1440 Say Y here to enable support for the on-chip RTC found in
1441 most SuperH processors. This RTC is also found in RZ/A SoCs.
1443 To compile this driver as a module, choose M here: the
1444 module will be called rtc-sh.
1446 config RTC_DRV_VR41XX
1447 tristate "NEC VR41XX"
1448 depends on CPU_VR41XX || COMPILE_TEST
1450 If you say Y here you will get access to the real time clock
1451 built into your NEC VR41XX CPU.
1453 To compile this driver as a module, choose M here: the
1454 module will be called rtc-vr41xx.
1456 config RTC_DRV_PL030
1457 tristate "ARM AMBA PL030 RTC"
1460 If you say Y here you will get access to ARM AMBA
1461 PrimeCell PL030 RTC found on certain ARM SOCs.
1463 To compile this driver as a module, choose M here: the
1464 module will be called rtc-pl030.
1466 config RTC_DRV_PL031
1467 tristate "ARM AMBA PL031 RTC"
1470 If you say Y here you will get access to ARM AMBA
1471 PrimeCell PL031 RTC found on certain ARM SOCs.
1473 To compile this driver as a module, choose M here: the
1474 module will be called rtc-pl031.
1476 config RTC_DRV_AT91RM9200
1477 tristate "AT91RM9200 or some AT91SAM9 RTC"
1478 depends on ARCH_AT91 || COMPILE_TEST
1481 Driver for the internal RTC (Realtime Clock) module found on
1482 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1483 this is powered by the backup power supply.
1485 config RTC_DRV_AT91SAM9
1486 tristate "AT91SAM9 RTT as RTC"
1487 depends on ARCH_AT91 || COMPILE_TEST
1488 depends on OF && HAS_IOMEM
1491 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1492 can be used as an RTC thanks to the backup power supply (e.g. a
1493 small coin cell battery) which keeps this block and the GPBR
1494 (General Purpose Backup Registers) block powered when the device
1496 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1497 probably want to use the real RTC block instead of the "RTT as an
1500 config RTC_DRV_AU1XXX
1501 tristate "Au1xxx Counter0 RTC support"
1502 depends on MIPS_ALCHEMY
1504 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1505 counter) to be used as a RTC.
1507 This driver can also be built as a module. If so, the module
1508 will be called rtc-au1xxx.
1510 config RTC_DRV_RS5C313
1511 tristate "Ricoh RS5C313"
1512 depends on SH_LANDISK
1514 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1516 config RTC_DRV_GENERIC
1517 tristate "Generic RTC support"
1518 # Please consider writing a new RTC driver instead of using the generic
1520 depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST
1522 Say Y or M here to enable RTC support on systems using the generic
1523 RTC abstraction. If you do not know what you are doing, you should
1527 tristate "PXA27x/PXA3xx"
1529 select RTC_DRV_SA1100
1531 If you say Y here you will get access to the real time clock
1532 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1533 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1535 This RTC driver uses PXA RTC registers available since pxa27x
1536 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1538 config RTC_DRV_VT8500
1539 tristate "VIA/WonderMedia 85xx SoC RTC"
1540 depends on ARCH_VT8500 || COMPILE_TEST
1542 If you say Y here you will get access to the real time clock
1543 built into your VIA VT8500 SoC or its relatives.
1546 config RTC_DRV_SUN4V
1547 bool "SUN4V Hypervisor RTC"
1550 If you say Y here you will get support for the Hypervisor
1551 based RTC on SUN4V systems.
1553 config RTC_DRV_SUN6I
1554 bool "Allwinner A31 RTC"
1555 default MACH_SUN6I || MACH_SUN8I
1556 depends on COMMON_CLK
1557 depends on ARCH_SUNXI || COMPILE_TEST
1559 If you say Y here you will get support for the RTC found in
1560 some Allwinner SoCs like the A31 or the A64.
1562 config RTC_DRV_SUNXI
1563 tristate "Allwinner sun4i/sun7i RTC"
1564 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1566 If you say Y here you will get support for the RTC found on
1569 config RTC_DRV_STARFIRE
1573 If you say Y here you will get support for the RTC found on
1576 config RTC_DRV_TX4939
1577 tristate "TX4939 SoC"
1578 depends on SOC_TX4939 || COMPILE_TEST
1580 Driver for the internal RTC (Realtime Clock) module found on
1584 tristate "Marvell SoC RTC"
1585 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1587 If you say yes here you will get support for the in-chip RTC
1588 that can be found in some of Marvell's SoC devices, such as
1589 the Kirkwood 88F6281 and 88F6192.
1591 This driver can also be built as a module. If so, the module
1592 will be called rtc-mv.
1594 config RTC_DRV_ARMADA38X
1595 tristate "Armada 38x Marvell SoC RTC"
1596 depends on ARCH_MVEBU || COMPILE_TEST
1598 If you say yes here you will get support for the in-chip RTC
1599 that can be found in the Armada 38x Marvell's SoC device
1601 This driver can also be built as a module. If so, the module
1602 will be called armada38x-rtc.
1604 config RTC_DRV_CADENCE
1605 tristate "Cadence RTC driver"
1606 depends on OF && HAS_IOMEM
1608 If you say Y here you will get access to Cadence RTC IP
1609 found on certain SOCs.
1611 To compile this driver as a module, choose M here: the
1612 module will be called rtc-cadence.
1614 config RTC_DRV_FTRTC010
1615 tristate "Faraday Technology FTRTC010 RTC"
1616 depends on HAS_IOMEM
1619 If you say Y here you will get support for the
1620 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1622 This driver can also be built as a module. If so, the module
1623 will be called rtc-ftrtc010.
1629 If you say yes here you will get support for the RTC on PS3.
1631 This driver can also be built as a module. If so, the module
1632 will be called rtc-ps3.
1634 config RTC_DRV_COH901331
1635 tristate "ST-Ericsson COH 901 331 RTC"
1636 depends on ARCH_U300 || COMPILE_TEST
1638 If you say Y here you will get access to ST-Ericsson
1639 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1642 This driver can also be built as a module. If so, the module
1643 will be called "rtc-coh901331".
1647 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1648 depends on ARCH_MXS || COMPILE_TEST
1651 If you say yes here you will get support for the onboard
1652 STMP3xxx/i.MX23/i.MX28 RTC.
1654 This driver can also be built as a module. If so, the module
1655 will be called rtc-stmp3xxx.
1661 If you say Y here you will get support for the RTC found on
1662 the PCAP2 ASIC used on some Motorola phones.
1664 config RTC_DRV_MC13XXX
1665 depends on MFD_MC13XXX
1666 tristate "Freescale MC13xxx RTC"
1668 This enables support for the RTCs found on Freescale's PMICs
1669 MC13783 and MC13892.
1671 config RTC_DRV_MPC5121
1672 tristate "Freescale MPC5121 built-in RTC"
1673 depends on PPC_MPC512x || PPC_MPC52xx
1675 If you say yes here you will get support for the
1676 built-in RTC on MPC5121 or on MPC5200.
1678 This driver can also be built as a module. If so, the module
1679 will be called rtc-mpc5121.
1681 config RTC_DRV_JZ4740
1682 tristate "Ingenic JZ4740 SoC"
1683 depends on MIPS || COMPILE_TEST
1686 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1689 This driver can also be built as a module. If so, the module
1690 will be called rtc-jz4740.
1692 config RTC_DRV_LPC24XX
1693 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1694 depends on ARCH_LPC18XX || COMPILE_TEST
1695 depends on OF && HAS_IOMEM
1697 This enables support for the NXP RTC found which can be found on
1698 NXP LPC178x/18xx/408x/43xx devices.
1700 If you have one of the devices above enable this driver to use
1701 the hardware RTC. This driver can also be built as a module. If
1702 so, the module will be called rtc-lpc24xx.
1704 config RTC_DRV_LPC32XX
1705 depends on ARCH_LPC32XX || COMPILE_TEST
1706 tristate "NXP LPC32XX RTC"
1708 This enables support for the NXP RTC in the LPC32XX
1710 This driver can also be built as a module. If so, the module
1711 will be called rtc-lpc32xx.
1713 config RTC_DRV_PM8XXX
1714 tristate "Qualcomm PMIC8XXX RTC"
1715 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1717 If you say yes here you get support for the
1718 Qualcomm PMIC8XXX RTC.
1720 To compile this driver as a module, choose M here: the
1721 module will be called rtc-pm8xxx.
1723 config RTC_DRV_TEGRA
1724 tristate "NVIDIA Tegra Internal RTC driver"
1725 depends on ARCH_TEGRA || COMPILE_TEST
1727 If you say yes here you get support for the
1728 Tegra 200 series internal RTC module.
1730 This drive can also be built as a module. If so, the module
1731 will be called rtc-tegra.
1733 config RTC_DRV_LOONGSON1
1734 tristate "loongson1 RTC support"
1735 depends on MACH_LOONGSON32
1737 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1738 counter) to be used as a RTC.
1740 This driver can also be built as a module. If so, the module
1741 will be called rtc-ls1x.
1744 tristate "Freescale MXC Real Time Clock"
1747 If you say yes here you get support for the Freescale MXC
1750 This driver can also be built as a module, if so, the module
1751 will be called "rtc-mxc".
1753 config RTC_DRV_MXC_V2
1754 tristate "Freescale MXC Real Time Clock for i.MX53"
1757 If you say yes here you get support for the Freescale MXC
1758 SRTC module in i.MX53 processor.
1760 This driver can also be built as a module, if so, the module
1761 will be called "rtc-mxc_v2".
1764 tristate "Freescale SNVS RTC support"
1766 depends on ARCH_MXC || COMPILE_TEST
1767 depends on HAS_IOMEM
1770 If you say yes here you get support for the Freescale SNVS
1771 Low Power (LP) RTC module.
1773 This driver can also be built as a module, if so, the module
1774 will be called "rtc-snvs".
1776 config RTC_DRV_IMX_SC
1778 depends on HAVE_ARM_SMCCC
1779 tristate "NXP i.MX System Controller RTC support"
1781 If you say yes here you get support for the NXP i.MX System
1782 Controller RTC module.
1784 config RTC_DRV_SIRFSOC
1785 tristate "SiRFSOC RTC"
1786 depends on ARCH_SIRF
1788 Say "yes" here to support the real time clock on SiRF SOC chips.
1789 This driver can also be built as a module called rtc-sirfsoc.
1791 config RTC_DRV_ST_LPC
1792 tristate "STMicroelectronics LPC RTC"
1796 Say Y here to include STMicroelectronics Low Power Controller
1797 (LPC) based RTC support.
1799 To compile this driver as a module, choose M here: the
1800 module will be called rtc-st-lpc.
1802 config RTC_DRV_MOXART
1803 tristate "MOXA ART RTC"
1804 depends on ARCH_MOXART || COMPILE_TEST
1806 If you say yes here you get support for the MOXA ART
1809 This driver can also be built as a module. If so, the module
1810 will be called rtc-moxart
1812 config RTC_DRV_MT2712
1813 tristate "MediaTek MT2712 SoC based RTC"
1814 depends on ARCH_MEDIATEK || COMPILE_TEST
1816 This enables support for the real time clock built in the MediaTek
1819 This drive can also be built as a module. If so, the module
1820 will be called rtc-mt2712.
1822 config RTC_DRV_MT6397
1823 tristate "MediaTek PMIC based RTC"
1824 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1826 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1827 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1828 MediaTek(R) RTC driver.
1830 If you want to use MediaTek(R) RTC interface, select Y or M here.
1832 config RTC_DRV_MT7622
1833 tristate "MediaTek SoC based RTC"
1834 depends on ARCH_MEDIATEK || COMPILE_TEST
1836 This enables support for the real time clock built in the MediaTek
1839 This drive can also be built as a module. If so, the module
1840 will be called rtc-mt7622.
1842 config RTC_DRV_XGENE
1843 tristate "APM X-Gene RTC"
1844 depends on HAS_IOMEM
1845 depends on ARCH_XGENE || COMPILE_TEST
1847 If you say yes here you get support for the APM X-Gene SoC real time
1850 This driver can also be built as a module, if so, the module
1851 will be called "rtc-xgene".
1853 config RTC_DRV_PIC32
1854 tristate "Microchip PIC32 RTC"
1855 depends on MACH_PIC32
1858 If you say yes here you get support for the PIC32 RTC module.
1860 This driver can also be built as a module. If so, the module
1861 will be called rtc-pic32
1863 config RTC_DRV_R7301
1864 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1866 depends on OF && HAS_IOMEM
1868 If you say yes here you get support for the EPSON TOYOCOM
1869 RTC-7301SF/DG chips.
1871 This driver can also be built as a module. If so, the module
1872 will be called rtc-r7301.
1874 config RTC_DRV_STM32
1875 tristate "STM32 RTC"
1877 depends on ARCH_STM32 || COMPILE_TEST
1879 If you say yes here you get support for the STM32 On-Chip
1882 This driver can also be built as a module, if so, the module
1883 will be called "rtc-stm32".
1885 config RTC_DRV_CPCAP
1886 depends on MFD_CPCAP
1887 tristate "Motorola CPCAP RTC"
1889 Say y here for CPCAP rtc found on some Motorola phones
1890 and tablets such as Droid 4.
1892 config RTC_DRV_RTD119X
1893 bool "Realtek RTD129x RTC"
1894 depends on ARCH_REALTEK || COMPILE_TEST
1895 default ARCH_REALTEK
1897 If you say yes here, you get support for the RTD1295 SoC
1900 config RTC_DRV_ASPEED
1901 tristate "ASPEED RTC"
1903 depends on ARCH_ASPEED || COMPILE_TEST
1905 If you say yes here you get support for the ASPEED BMC SoC real time
1908 This driver can also be built as a module, if so, the module
1909 will be called "rtc-aspeed".
1911 comment "HID Sensor RTC drivers"
1913 config RTC_DRV_HID_SENSOR_TIME
1914 tristate "HID Sensor Time"
1916 depends on HID_SENSOR_HUB && IIO
1917 select HID_SENSOR_IIO_COMMON
1919 Say yes here to build support for the HID Sensors of type Time.
1920 This drivers makes such sensors available as RTCs.
1922 If this driver is compiled as a module, it will be named
1923 rtc-hid-sensor-time.
1925 config RTC_DRV_GOLDFISH
1926 tristate "Goldfish Real Time Clock"
1927 depends on OF && HAS_IOMEM
1928 depends on GOLDFISH || COMPILE_TEST
1930 Say yes to enable RTC driver for the Goldfish based virtual platform.
1932 Goldfish is a code name for the virtual platform developed by Google
1933 for Android emulation.
1935 config RTC_DRV_WILCO_EC
1936 tristate "Wilco EC RTC"
1940 If you say yes here, you get read/write support for the Real Time
1941 Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook)
1943 This can also be built as a module. If so, the module will
1944 be named "rtc_wilco_ec".