1 # SPDX-License-Identifier: GPL-2.0-only
3 # RTC class/drivers configuration
9 config RTC_MC146818_LIB
14 bool "Real Time Clock"
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.
78 config RTC_LIB_KUNIT_TEST
79 tristate "KUnit test for RTC lib functions" if !KUNIT_ALL_TESTS
81 default KUNIT_ALL_TESTS
83 Enable this option to test RTC library functions.
88 bool "RTC non volatile storage support"
92 Say yes here to add support for the non volatile (often battery
93 backed) storage present on RTCs.
95 comment "RTC interfaces"
98 bool "/sys/class/rtc/rtcN (sysfs)"
102 Say yes here if you want to use your RTCs using sysfs interfaces,
103 /sys/class/rtc/rtc0 through /sys/.../rtcN.
108 bool "/proc/driver/rtc (procfs for rtcN)"
112 Say yes here if you want to use your system clock RTC through
113 the proc interface, /proc/driver/rtc.
114 Other RTCs will not be available through that API.
115 If there is no RTC for the system clock, then the first RTC(rtc0)
121 bool "/dev/rtcN (character devices)"
124 Say yes here if you want to use your RTCs using the /dev
125 interfaces, which "udev" sets up as /dev/rtc0 through
128 You may want to set up a symbolic link so one of these
129 can be accessed as /dev/rtc, which is a name
130 expected by "hwclock" and some other programs. Recent
131 versions of "udev" are known to set up the symlink for you.
135 config RTC_INTF_DEV_UIE_EMUL
136 bool "RTC UIE emulation on dev interface"
137 depends on RTC_INTF_DEV
139 Provides an emulation for RTC_UIE if the underlying rtc chip
140 driver does not expose RTC_UIE ioctls. Those requests generate
141 once-per-second update interrupts, used for synchronization.
143 The emulation code will read the time from the hardware
144 clock several times per second, please enable this option
145 only if you know that you really need it.
148 tristate "Test driver/device"
150 If you say yes here you get support for the
151 RTC test driver. It's a software RTC which can be
152 used to test the RTC subsystem APIs. It gets
153 the time from the system clock.
154 You want this driver only if you are doing development
155 on the RTC subsystem. Please read the source code
158 This driver can also be built as a module. If so, the module
159 will be called rtc-test.
161 comment "I2C RTC drivers"
165 config RTC_DRV_88PM860X
166 tristate "Marvell 88PM860x"
167 depends on MFD_88PM860X
169 If you say yes here you get support for RTC function in Marvell
172 This driver can also be built as a module. If so, the module
173 will be called rtc-88pm860x.
175 config RTC_DRV_88PM80X
176 tristate "Marvell 88PM80x"
177 depends on MFD_88PM800
179 If you say yes here you get support for RTC function in Marvell
182 This driver can also be built as a module. If so, the module
183 will be called rtc-88pm80x.
185 config RTC_DRV_ABB5ZES3
187 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
189 If you say yes here you get support for the Abracon
190 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
192 This driver can also be built as a module. If so, the module
193 will be called rtc-ab-b5ze-s3.
195 config RTC_DRV_ABEOZ9
197 tristate "Abracon AB-RTCMC-32.768kHz-EOZ9"
199 If you say yes here you get support for the Abracon
200 AB-RTCMC-32.768kHz-EOA9 I2C RTC chip.
202 This driver can also be built as a module. If so, the module
203 will be called rtc-ab-e0z9.
205 config RTC_DRV_ABX80X
206 tristate "Abracon ABx80x"
207 select WATCHDOG_CORE if WATCHDOG
209 If you say yes here you get support for Abracon AB080X and AB180X
210 families of ultra-low-power battery- and capacitor-backed real-time
213 This driver can also be built as a module. If so, the module
214 will be called rtc-abx80x.
217 tristate "X-Powers AC100"
220 If you say yes here you get support for the real-time clock found
221 in X-Powers AC100 family peripheral ICs.
223 This driver can also be built as a module. If so, the module
224 will be called rtc-ac100.
226 config RTC_DRV_BRCMSTB
227 tristate "Broadcom STB wake-timer"
228 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
229 default ARCH_BRCMSTB || BMIPS_GENERIC
231 If you say yes here you get support for the wake-timer found on
232 Broadcom STB SoCs (BCM7xxx).
234 This driver can also be built as a module. If so, the module will
235 be called rtc-brcmstb-waketimer.
237 config RTC_DRV_AS3722
238 tristate "ams AS3722 RTC driver"
239 depends on MFD_AS3722
241 If you say yes here you get support for the RTC of ams AS3722 PMIC
244 This driver can also be built as a module. If so, the module
245 will be called rtc-as3722.
247 config RTC_DRV_DS1307
248 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"
250 select WATCHDOG_CORE if WATCHDOG
252 If you say yes here you get support for various compatible RTC
253 chips (often with battery backup) connected with I2C. This driver
254 should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341,
255 ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.
256 In some cases the RTC must already have been initialized (by
257 manufacturing or a bootloader).
259 The first seven registers on these chips hold an RTC, and other
260 registers may add features such as NVRAM, a trickle charger for
261 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
262 sysfs, but other chip features may not be available.
264 This driver can also be built as a module. If so, the module
265 will be called rtc-ds1307.
267 config RTC_DRV_DS1307_CENTURY
268 bool "Century bit support for rtc-ds1307"
269 depends on RTC_DRV_DS1307
272 The DS1307 driver suffered from a bug where it was enabling the
273 century bit inconditionnally but never used it when reading the time.
274 It made the driver unable to support dates beyond 2099.
275 Setting this option will add proper support for the century bit but if
276 the time was previously set using a kernel predating this option,
277 reading the date will return a date in the next century.
278 To solve that, you could boot a kernel without this option set, set
279 the RTC date and then boot a kernel with this option set.
281 config RTC_DRV_DS1374
282 tristate "Dallas/Maxim DS1374"
284 If you say yes here you get support for Dallas Semiconductor
285 DS1374 real-time clock chips. If an interrupt is associated
286 with the device, the alarm functionality is supported.
288 This driver can also be built as a module. If so, the module
289 will be called rtc-ds1374.
291 config RTC_DRV_DS1374_WDT
292 bool "Dallas/Maxim DS1374 watchdog timer"
293 depends on RTC_DRV_DS1374 && WATCHDOG
296 If you say Y here you will get support for the
297 watchdog timer in the Dallas Semiconductor DS1374
298 real-time clock chips.
300 config RTC_DRV_DS1672
301 tristate "Dallas/Maxim DS1672"
303 If you say yes here you get support for the
304 Dallas/Maxim DS1672 timekeeping chip.
306 This driver can also be built as a module. If so, the module
307 will be called rtc-ds1672.
309 config RTC_DRV_HYM8563
310 tristate "Haoyu Microelectronics HYM8563"
313 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
314 from the usual rtc functions it provides a clock output of
317 This driver can also be built as a module. If so, the module
318 will be called rtc-hym8563.
320 config RTC_DRV_LP8788
321 tristate "TI LP8788 RTC driver"
322 depends on MFD_LP8788
324 Say Y to enable support for the LP8788 RTC/ALARM driver.
326 config RTC_DRV_MAX6900
327 tristate "Maxim MAX6900"
329 If you say yes here you will get support for the
330 Maxim MAX6900 I2C RTC chip.
332 This driver can also be built as a module. If so, the module
333 will be called rtc-max6900.
335 config RTC_DRV_MAX8907
336 tristate "Maxim MAX8907"
337 depends on MFD_MAX8907 || COMPILE_TEST
340 If you say yes here you will get support for the
341 RTC of Maxim MAX8907 PMIC.
343 This driver can also be built as a module. If so, the module
344 will be called rtc-max8907.
346 config RTC_DRV_MAX8925
347 tristate "Maxim MAX8925"
348 depends on MFD_MAX8925
350 If you say yes here you will get support for the
351 RTC of Maxim MAX8925 PMIC.
353 This driver can also be built as a module. If so, the module
354 will be called rtc-max8925.
356 config RTC_DRV_MAX8998
357 tristate "Maxim MAX8998"
358 depends on MFD_MAX8998
360 If you say yes here you will get support for the
361 RTC of Maxim MAX8998 PMIC.
363 This driver can also be built as a module. If so, the module
364 will be called rtc-max8998.
366 config RTC_DRV_MAX8997
367 tristate "Maxim MAX8997"
368 depends on MFD_MAX8997
370 If you say yes here you will get support for the
371 RTC of Maxim MAX8997 PMIC.
373 This driver can also be built as a module. If so, the module
374 will be called rtc-max8997.
376 config RTC_DRV_MAX77686
377 tristate "Maxim MAX77686"
378 depends on MFD_MAX77686 || MFD_MAX77620 || MFD_MAX77714 || COMPILE_TEST
380 If you say yes here you will get support for the
381 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
383 This driver can also be built as a module. If so, the module
384 will be called rtc-max77686.
386 config RTC_DRV_NCT3018Y
387 tristate "Nuvoton NCT3018Y"
390 If you say yes here you get support for the Nuvoton NCT3018Y I2C RTC
393 This driver can also be built as a module, if so, the module will be
394 called "rtc-nct3018y".
397 tristate "Rockchip RK805/RK808/RK809/RK817/RK818 RTC"
400 If you say yes here you will get support for the
401 RTC of RK805, RK809 and RK817, RK808 and RK818 PMIC.
403 This driver can also be built as a module. If so, the module
404 will be called rk808-rtc.
406 config RTC_DRV_RS5C372
407 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
409 If you say yes here you get support for the
410 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
412 This driver can also be built as a module. If so, the module
413 will be called rtc-rs5c372.
415 config RTC_DRV_ISL1208
416 tristate "Intersil ISL1208"
418 If you say yes here you get support for the
419 Intersil ISL1208 RTC chip.
421 This driver can also be built as a module. If so, the module
422 will be called rtc-isl1208.
424 config RTC_DRV_ISL12022
425 tristate "Intersil ISL12022"
428 If you say yes here you get support for the
429 Intersil ISL12022 RTC chip.
431 This driver can also be built as a module. If so, the module
432 will be called rtc-isl12022.
434 config RTC_DRV_ISL12026
435 tristate "Intersil ISL12026"
438 If you say yes here you get support for the
439 Intersil ISL12026 RTC chip.
441 This driver can also be built as a module. If so, the module
442 will be called rtc-isl12026.
445 tristate "Xicor/Intersil X1205"
447 If you say yes here you get support for the
448 Xicor/Intersil X1205 RTC chip.
450 This driver can also be built as a module. If so, the module
451 will be called rtc-x1205.
453 config RTC_DRV_PCF8523
454 tristate "NXP PCF8523"
457 If you say yes here you get support for the NXP PCF8523 RTC
460 This driver can also be built as a module. If so, the module
461 will be called rtc-pcf8523.
463 config RTC_DRV_PCF85063
464 tristate "NXP PCF85063"
467 If you say yes here you get support for the PCF85063 RTC chip
469 This driver can also be built as a module. If so, the module
470 will be called rtc-pcf85063.
472 config RTC_DRV_PCF85363
473 tristate "NXP PCF85363"
476 If you say yes here you get support for the PCF85363 RTC chip.
478 This driver can also be built as a module. If so, the module
479 will be called rtc-pcf85363.
481 The nvmem interface will be named pcf85363-#, where # is the
482 zero-based instance number.
484 config RTC_DRV_PCF8563
485 tristate "Philips PCF8563/Epson RTC8564"
487 If you say yes here you get support for the
488 Philips PCF8563 RTC chip. The Epson RTC8564
491 This driver can also be built as a module. If so, the module
492 will be called rtc-pcf8563.
494 config RTC_DRV_PCF8583
495 tristate "Philips PCF8583"
497 If you say yes here you get support for the Philips PCF8583
498 RTC chip found on Acorn RiscPCs. This driver supports the
499 platform specific method of retrieving the current year from
500 the RTC's SRAM. It will work on other platforms with the same
501 chip, but the year will probably have to be tweaked.
503 This driver can also be built as a module. If so, the module
504 will be called rtc-pcf8583.
506 config RTC_DRV_M41T80
507 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
509 If you say Y here you will get support for the ST M41T60
510 and M41T80 RTC chips series. Currently, the following chips are
511 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
512 M41ST85, M41ST87, and MicroCrystal RV4162.
514 This driver can also be built as a module. If so, the module
515 will be called rtc-m41t80.
517 config RTC_DRV_M41T80_WDT
518 bool "ST M41T65/M41T80 series RTC watchdog timer"
519 depends on RTC_DRV_M41T80
521 If you say Y here you will get support for the
522 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
524 config RTC_DRV_BD70528
525 tristate "ROHM BD71815 and BD71828 PMIC RTC"
526 depends on MFD_ROHM_BD71828
528 If you say Y here you will get support for the RTC
529 block on ROHM BD71815 and BD71828 Power Management IC.
531 This driver can also be built as a module. If so, the module
532 will be called rtc-bd70528.
535 tristate "TI BQ32000"
537 If you say Y here you will get support for the TI
538 BQ32000 I2C RTC chip.
540 This driver can also be built as a module. If so, the module
541 will be called rtc-bq32k.
543 config RTC_DRV_TWL92330
544 bool "TI TWL92330/Menelaus"
547 If you say yes here you get support for the RTC on the
548 TWL92330 "Menelaus" power management chip, used with OMAP2
549 platforms. The support is integrated with the rest of
550 the Menelaus driver; it's not separate module.
552 config RTC_DRV_TWL4030
553 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
554 depends on TWL4030_CORE
557 If you say yes here you get support for the RTC on the
558 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
560 This driver can also be built as a module. If so, the module
561 will be called rtc-twl.
563 config RTC_DRV_PALMAS
564 tristate "TI Palmas RTC driver"
565 depends on MFD_PALMAS
567 If you say yes here you get support for the RTC of TI PALMA series PMIC
570 This driver can also be built as a module. If so, the module
571 will be called rtc-palma.
573 config RTC_DRV_TPS6586X
574 tristate "TI TPS6586X RTC driver"
575 depends on MFD_TPS6586X
577 TI Power Management IC TPS6586X supports RTC functionality
578 along with alarm. This driver supports the RTC driver for
579 the TPS6586X RTC module.
581 config RTC_DRV_TPS65910
582 tristate "TI TPS65910 RTC driver"
583 depends on MFD_TPS65910
585 If you say yes here you get support for the RTC on the
588 This driver can also be built as a module. If so, the module
589 will be called rtc-tps65910.
591 config RTC_DRV_RC5T583
592 tristate "RICOH 5T583 RTC driver"
593 depends on MFD_RC5T583
595 If you say yes here you get support for the RTC on the
598 This driver can also be built as a module. If so, the module
599 will be called rtc-rc5t583.
601 config RTC_DRV_RC5T619
602 tristate "RICOH RC5T619 RTC driver"
603 depends on MFD_RN5T618
605 If you say yes here you get support for the RTC on the
608 This driver can also be built as a module. If so, the module
609 will be called rtc-rc5t619.
611 config RTC_DRV_S35390A
612 tristate "Seiko Instruments S-35390A"
615 If you say yes here you will get support for the Seiko
616 Instruments S-35390A.
618 This driver can also be built as a module. If so the module
619 will be called rtc-s35390a.
621 config RTC_DRV_FM3130
622 tristate "Ramtron FM3130"
624 If you say Y here you will get support for the
625 Ramtron FM3130 RTC chips.
626 Ramtron FM3130 is a chip with two separate devices inside,
627 RTC clock and FRAM. This driver provides only RTC functionality.
629 This driver can also be built as a module. If so the module
630 will be called rtc-fm3130.
632 config RTC_DRV_RX8010
633 tristate "Epson RX8010SJ"
636 If you say yes here you get support for the Epson RX8010SJ RTC
639 This driver can also be built as a module. If so, the module
640 will be called rtc-rx8010.
642 config RTC_DRV_RX8581
643 tristate "Epson RX-8571/RX-8581"
646 If you say yes here you will get support for the Epson RX-8571/
649 This driver can also be built as a module. If so the module
650 will be called rtc-rx8581.
652 config RTC_DRV_RX8025
653 tristate "Epson RX-8025SA/NB"
655 If you say yes here you get support for the Epson
656 RX-8025SA/NB RTC chips.
658 This driver can also be built as a module. If so, the module
659 will be called rtc-rx8025.
661 config RTC_DRV_EM3027
662 tristate "EM Microelectronic EM3027"
664 If you say yes here you get support for the EM
665 Microelectronic EM3027 RTC chips.
667 This driver can also be built as a module. If so, the module
668 will be called rtc-em3027.
670 config RTC_DRV_RV3028
671 tristate "Micro Crystal RV3028"
674 If you say yes here you get support for the Micro Crystal
677 This driver can also be built as a module. If so, the module
678 will be called rtc-rv3028.
680 config RTC_DRV_RV3032
681 tristate "Micro Crystal RV3032"
684 If you say yes here you get support for the Micro Crystal
687 This driver can also be built as a module. If so, the module
688 will be called rtc-rv3032.
690 config RTC_DRV_RV8803
691 tristate "Micro Crystal RV8803, Epson RX8900"
693 If you say yes here you get support for the Micro Crystal RV8803 and
694 Epson RX8900 RTC chips.
696 This driver can also be built as a module. If so, the module
697 will be called rtc-rv8803.
700 tristate "Samsung S2M/S5M series"
701 depends on MFD_SEC_CORE || COMPILE_TEST
705 If you say yes here you will get support for the
706 RTC of Samsung S2MPS14 and S5M PMIC series.
708 This driver can also be built as a module. If so, the module
709 will be called rtc-s5m.
711 config RTC_DRV_SD3078
712 tristate "ZXW Shenzhen whwave SD3078"
715 If you say yes here you get support for the ZXW Shenzhen whwave
718 This driver can also be built as a module. If so, the module
719 will be called rtc-sd3078
723 comment "SPI RTC drivers"
727 config RTC_DRV_M41T93
730 If you say yes here you will get support for the
731 ST M41T93 SPI RTC chip.
733 This driver can also be built as a module. If so, the module
734 will be called rtc-m41t93.
736 config RTC_DRV_M41T94
739 If you say yes here you will get support for the
740 ST M41T94 SPI RTC chip.
742 This driver can also be built as a module. If so, the module
743 will be called rtc-m41t94.
745 config RTC_DRV_DS1302
746 tristate "Dallas/Maxim DS1302"
749 If you say yes here you get support for the Dallas DS1302 RTC chips.
751 This driver can also be built as a module. If so, the module
752 will be called rtc-ds1302.
754 config RTC_DRV_DS1305
755 tristate "Dallas/Maxim DS1305/DS1306"
757 Select this driver to get support for the Dallas/Maxim DS1305
758 and DS1306 real time clock chips. These support a trickle
759 charger, alarms, and NVRAM in addition to the clock.
761 This driver can also be built as a module. If so, the module
762 will be called rtc-ds1305.
764 config RTC_DRV_DS1343
766 tristate "Dallas/Maxim DS1343/DS1344"
768 If you say yes here you get support for the
769 Dallas/Maxim DS1343 and DS1344 real time clock chips.
770 Support for trickle charger, alarm is provided.
772 This driver can also be built as a module. If so, the module
773 will be called rtc-ds1343.
775 config RTC_DRV_DS1347
777 tristate "Dallas/Maxim DS1347"
779 If you say yes here you get support for the
780 Dallas/Maxim DS1347 chips.
782 This driver only supports the RTC feature, and not other chip
783 features such as alarms.
785 This driver can also be built as a module. If so, the module
786 will be called rtc-ds1347.
788 config RTC_DRV_DS1390
789 tristate "Dallas/Maxim DS1390/93/94"
791 If you say yes here you get support for the
792 Dallas/Maxim DS1390/93/94 chips.
794 This driver supports the RTC feature and trickle charging but not
795 other chip features such as alarms.
797 This driver can also be built as a module. If so, the module
798 will be called rtc-ds1390.
800 config RTC_DRV_MAX6916
801 tristate "Maxim MAX6916"
803 If you say yes here you will get support for the
804 Maxim MAX6916 SPI RTC chip.
806 This driver only supports the RTC feature, and not other chip
807 features such as alarms.
809 This driver can also be built as a module. If so, the module
810 will be called rtc-max6916.
813 tristate "Epson RTC-9701JE"
815 If you say yes here you will get support for the
816 Epson RTC-9701JE SPI RTC chip.
818 This driver can also be built as a module. If so, the module
819 will be called rtc-r9701.
821 config RTC_DRV_RX4581
822 tristate "Epson RX-4581"
824 If you say yes here you will get support for the Epson RX-4581.
826 This driver can also be built as a module. If so the module
827 will be called rtc-rx4581.
829 config RTC_DRV_RS5C348
830 tristate "Ricoh RS5C348A/B"
832 If you say yes here you get support for the
833 Ricoh RS5C348A and RS5C348B RTC chips.
835 This driver can also be built as a module. If so, the module
836 will be called rtc-rs5c348.
838 config RTC_DRV_MAX6902
839 tristate "Maxim MAX6902"
841 If you say yes here you will get support for the
842 Maxim MAX6902 SPI RTC chip.
844 This driver can also be built as a module. If so, the module
845 will be called rtc-max6902.
847 config RTC_DRV_PCF2123
848 tristate "NXP PCF2123"
851 If you say yes here you get support for the NXP PCF2123
854 This driver can also be built as a module. If so, the module
855 will be called rtc-pcf2123.
857 config RTC_DRV_MCP795
858 tristate "Microchip MCP795"
860 If you say yes here you will get support for the Microchip MCP795.
862 This driver can also be built as a module. If so the module
863 will be called rtc-mcp795.
868 # Helper to resolve issues with configs that have SPI enabled but I2C
869 # modular. See SND_SOC_I2C_AND_SPI for more information
871 config RTC_I2C_AND_SPI
875 default y if SPI_MASTER=y
877 comment "SPI and I2C RTC drivers"
879 config RTC_DRV_DS3232
880 tristate "Dallas/Maxim DS3232/DS3234"
881 depends on RTC_I2C_AND_SPI
882 select REGMAP_I2C if I2C
883 select REGMAP_SPI if SPI_MASTER
885 If you say yes here you get support for Dallas Semiconductor
886 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
887 with the device, the alarm functionality is supported.
889 This driver can also be built as a module. If so, the module
890 will be called rtc-ds3232.
892 config RTC_DRV_DS3232_HWMON
893 bool "HWMON support for Dallas/Maxim DS3232/DS3234"
894 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
897 Say Y here if you want to expose temperature sensor data on
900 config RTC_DRV_PCF2127
901 tristate "NXP PCF2127"
902 depends on RTC_I2C_AND_SPI
903 select REGMAP_I2C if I2C
904 select REGMAP_SPI if SPI_MASTER
905 select WATCHDOG_CORE if WATCHDOG
907 If you say yes here you get support for the NXP PCF2127/29 RTC
908 chips with integrated quartz crystal for industrial applications.
909 Both chips also have watchdog timer and tamper switch detection
912 PCF2127 has an additional feature of 512 bytes battery backed
913 memory that's accessible using nvmem interface.
915 This driver can also be built as a module. If so, the module
916 will be called rtc-pcf2127.
918 config RTC_DRV_RV3029C2
919 tristate "Micro Crystal RV3029/3049"
920 depends on RTC_I2C_AND_SPI
921 select REGMAP_I2C if I2C
922 select REGMAP_SPI if SPI_MASTER
924 If you say yes here you get support for the Micro Crystal
925 RV3029 and RV3049 RTC chips.
927 This driver can also be built as a module. If so, the module
928 will be called rtc-rv3029c2.
930 config RTC_DRV_RV3029_HWMON
931 bool "HWMON support for RV3029/3049"
932 depends on RTC_DRV_RV3029C2 && HWMON
933 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
936 Say Y here if you want to expose temperature sensor data on
939 config RTC_DRV_RX6110
940 tristate "Epson RX-6110"
941 depends on RTC_I2C_AND_SPI
942 select REGMAP_SPI if SPI_MASTER
943 select REGMAP_I2C if I2C
945 If you say yes here you will get support for the Epson RX-6110.
947 This driver can also be built as a module. If so the module
948 will be called rtc-rx6110.
950 comment "Platform RTC drivers"
952 # this 'CMOS' RTC driver is arch dependent because it requires
953 # <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
954 # global rtc_lock ... it's not yet just another platform_device.
957 tristate "PC-style 'CMOS'"
958 depends on X86 || ARM || PPC || MIPS || SPARC64
960 select RTC_MC146818_LIB
962 Say "yes" here to get direct support for the real time clock
963 found in every PC or ACPI-based system, and some other boards.
964 Specifically the original MC146818, compatibles like those in
965 PC south bridges, the DS12887 or M48T86, some multifunction
966 or LPC bus chips, and so on.
968 Your system will need to define the platform device used by
969 this driver, otherwise it won't be accessible. This means
970 you can safely enable this driver if you don't know whether
971 or not your board has this kind of hardware.
973 This driver can also be built as a module. If so, the module
974 will be called rtc-cmos.
977 bool "Alpha PC-style CMOS"
979 select RTC_MC146818_LIB
982 Direct support for the real-time clock found on every Alpha
983 system, specifically MC146818 compatibles. If in doubt, say Y.
985 config RTC_DRV_DS1216
986 tristate "Dallas DS1216"
989 If you say yes here you get support for the Dallas DS1216 RTC chips.
991 config RTC_DRV_DS1286
992 tristate "Dallas DS1286"
995 If you say yes here you get support for the Dallas DS1286 RTC chips.
997 config RTC_DRV_DS1511
998 tristate "Dallas DS1511"
1001 If you say yes here you get support for the
1002 Dallas DS1511 timekeeping/watchdog chip.
1004 This driver can also be built as a module. If so, the module
1005 will be called rtc-ds1511.
1007 config RTC_DRV_DS1553
1008 tristate "Maxim/Dallas DS1553"
1009 depends on HAS_IOMEM
1011 If you say yes here you get support for the
1012 Maxim/Dallas DS1553 timekeeping chip.
1014 This driver can also be built as a module. If so, the module
1015 will be called rtc-ds1553.
1017 config RTC_DRV_DS1685_FAMILY
1018 tristate "Dallas/Maxim DS1685 Family"
1019 depends on HAS_IOMEM
1021 If you say yes here you get support for the Dallas/Maxim DS1685
1022 family of real time chips. This family includes the DS1685/DS1687,
1023 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
1024 DS17885/DS17887 chips.
1026 This driver can also be built as a module. If so, the module
1027 will be called rtc-ds1685.
1031 depends on RTC_DRV_DS1685_FAMILY
1032 default RTC_DRV_DS1685
1034 config RTC_DRV_DS1685
1035 bool "DS1685/DS1687"
1037 This enables support for the Dallas/Maxim DS1685/DS1687 real time
1040 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
1041 systems, as well as EPPC-405-UC modules by electronic system design
1044 config RTC_DRV_DS1689
1045 bool "DS1689/DS1693"
1047 This enables support for the Dallas/Maxim DS1689/DS1693 real time
1050 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
1051 which supports a few minor features such as Vcc, Vbat, and Power
1052 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
1054 It also works for the even older DS1688/DS1691 RTC chips, which are
1055 virtually the same and carry the same model number. Both chips
1056 have 114 bytes of user NVRAM.
1058 config RTC_DRV_DS17285
1059 bool "DS17285/DS17287"
1061 This enables support for the Dallas/Maxim DS17285/DS17287 real time
1064 This chip features 2kb of extended NV-SRAM. It may possibly be
1065 found in some SGI O2 systems (rare).
1067 config RTC_DRV_DS17485
1068 bool "DS17485/DS17487"
1070 This enables support for the Dallas/Maxim DS17485/DS17487 real time
1073 This chip features 4kb of extended NV-SRAM.
1075 config RTC_DRV_DS17885
1076 bool "DS17885/DS17887"
1078 This enables support for the Dallas/Maxim DS17885/DS17887 real time
1081 This chip features 8kb of extended NV-SRAM.
1085 config RTC_DRV_DS1742
1086 tristate "Maxim/Dallas DS1742/1743"
1087 depends on HAS_IOMEM
1089 If you say yes here you get support for the
1090 Maxim/Dallas DS1742/1743 timekeeping chip.
1092 This driver can also be built as a module. If so, the module
1093 will be called rtc-ds1742.
1095 config RTC_DRV_DS2404
1096 tristate "Maxim/Dallas DS2404"
1098 If you say yes here you get support for the
1099 Dallas DS2404 RTC chip.
1101 This driver can also be built as a module. If so, the module
1102 will be called rtc-ds2404.
1104 config RTC_DRV_DA9052
1105 tristate "Dialog DA9052/DA9053 RTC"
1106 depends on PMIC_DA9052
1108 Say y here to support the RTC driver for Dialog Semiconductor
1109 DA9052-BC and DA9053-AA/Bx PMICs.
1111 config RTC_DRV_DA9055
1112 tristate "Dialog Semiconductor DA9055 RTC"
1113 depends on MFD_DA9055
1115 If you say yes here you will get support for the
1116 RTC of the Dialog DA9055 PMIC.
1118 This driver can also be built as a module. If so, the module
1119 will be called rtc-da9055
1121 config RTC_DRV_DA9063
1122 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1123 depends on MFD_DA9063 || MFD_DA9062
1125 If you say yes here you will get support for the RTC subsystem
1126 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1128 This driver can also be built as a module. If so, the module
1129 will be called "rtc-da9063".
1133 depends on EFI && !X86
1135 If you say yes here you will get support for the EFI
1138 This driver can also be built as a module. If so, the module
1139 will be called rtc-efi.
1141 config RTC_DRV_STK17TA8
1142 tristate "Simtek STK17TA8"
1143 depends on HAS_IOMEM
1145 If you say yes here you get support for the
1146 Simtek STK17TA8 timekeeping chip.
1148 This driver can also be built as a module. If so, the module
1149 will be called rtc-stk17ta8.
1151 config RTC_DRV_M48T86
1152 tristate "ST M48T86/Dallas DS12887"
1153 depends on HAS_IOMEM
1155 If you say Y here you will get support for the
1156 ST M48T86 and Dallas DS12887 RTC chips.
1158 This driver can also be built as a module. If so, the module
1159 will be called rtc-m48t86.
1161 config RTC_DRV_M48T35
1162 tristate "ST M48T35"
1163 depends on HAS_IOMEM
1165 If you say Y here you will get support for the
1168 This driver can also be built as a module, if so, the module
1169 will be called "rtc-m48t35".
1171 config RTC_DRV_M48T59
1172 tristate "ST M48T59/M48T08/M48T02"
1173 depends on HAS_IOMEM
1175 If you say Y here you will get support for the
1176 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1178 These chips are usually found in Sun SPARC and UltraSPARC
1181 This driver can also be built as a module, if so, the module
1182 will be called "rtc-m48t59".
1184 config RTC_DRV_MSM6242
1185 tristate "Oki MSM6242"
1186 depends on HAS_IOMEM
1188 If you say yes here you get support for the Oki MSM6242
1189 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1191 This driver can also be built as a module. If so, the module
1192 will be called rtc-msm6242.
1194 config RTC_DRV_BQ4802
1195 tristate "TI BQ4802"
1196 depends on HAS_IOMEM
1198 If you say Y here you will get support for the TI
1201 This driver can also be built as a module. If so, the module
1202 will be called rtc-bq4802.
1204 config RTC_DRV_RP5C01
1205 tristate "Ricoh RP5C01"
1206 depends on HAS_IOMEM
1208 If you say yes here you get support for the Ricoh RP5C01
1209 timekeeping chip. It is used in some Amiga models (e.g. A3000
1212 This driver can also be built as a module. If so, the module
1213 will be called rtc-rp5c01.
1215 config RTC_DRV_V3020
1216 tristate "EM Microelectronic V3020"
1218 If you say yes here you will get support for the
1219 EM Microelectronic v3020 RTC chip.
1221 This driver can also be built as a module. If so, the module
1222 will be called rtc-v3020.
1224 config RTC_DRV_GAMECUBE
1225 tristate "Nintendo GameCube, Wii and Wii U RTC"
1226 depends on GAMECUBE || WII || COMPILE_TEST
1229 If you say yes here you will get support for the RTC subsystem
1230 of the Nintendo GameCube, Wii and Wii U.
1232 This driver can also be built as a module. If so, the module
1233 will be called "rtc-gamecube".
1235 config RTC_DRV_WM831X
1236 tristate "Wolfson Microelectronics WM831x RTC"
1237 depends on MFD_WM831X
1239 If you say yes here you will get support for the RTC subsystem
1240 of the Wolfson Microelectronics WM831X series PMICs.
1242 This driver can also be built as a module. If so, the module
1243 will be called "rtc-wm831x".
1245 config RTC_DRV_WM8350
1246 tristate "Wolfson Microelectronics WM8350 RTC"
1247 depends on MFD_WM8350
1249 If you say yes here you will get support for the RTC subsystem
1250 of the Wolfson Microelectronics WM8350.
1252 This driver can also be built as a module. If so, the module
1253 will be called "rtc-wm8350".
1255 config RTC_DRV_SC27XX
1256 tristate "Spreadtrum SC27xx RTC"
1257 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1259 If you say Y here you will get support for the RTC subsystem
1260 of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs
1261 includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips.
1263 This driver can also be built as a module. If so, the module
1264 will be called rtc-sc27xx.
1266 config RTC_DRV_SPEAR
1267 tristate "SPEAR ST RTC"
1268 depends on PLAT_SPEAR || COMPILE_TEST
1271 If you say Y here you will get support for the RTC found on
1274 config RTC_DRV_PCF50633
1275 depends on MFD_PCF50633
1276 tristate "NXP PCF50633 RTC"
1278 If you say yes here you get support for the RTC subsystem of the
1279 NXP PCF50633 used in embedded systems.
1281 config RTC_DRV_AB8500
1282 tristate "ST-Ericsson AB8500 RTC"
1283 depends on AB8500_CORE
1285 select RTC_INTF_DEV_UIE_EMUL
1287 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1288 support. This chip contains a battery- and capacitor-backed RTC.
1291 tristate "IBM OPAL RTC driver"
1292 depends on PPC_POWERNV
1295 If you say yes here you get support for the PowerNV platform RTC
1296 driver based on OPAL interfaces.
1298 This driver can also be built as a module. If so, the module
1299 will be called rtc-opal.
1301 config RTC_DRV_OPTEE
1302 tristate "OP-TEE based RTC driver"
1305 Select this to get support for OP-TEE based RTC control on SoCs where
1306 RTC are not accessible to the normal world (Linux).
1308 This driver can also be built as a module. If so, the module
1309 will be called rtc-optee.
1311 config RTC_DRV_ZYNQMP
1312 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1313 depends on OF && HAS_IOMEM
1315 If you say yes here you get support for the RTC controller found on
1316 Xilinx Zynq Ultrascale+ MPSoC.
1318 config RTC_DRV_CROS_EC
1319 tristate "Chrome OS EC RTC driver"
1322 If you say yes here you will get support for the
1323 Chrome OS Embedded Controller's RTC.
1325 This driver can also be built as a module. If so, the module
1326 will be called rtc-cros-ec.
1328 config RTC_DRV_NTXEC
1329 tristate "Netronix embedded controller RTC"
1330 depends on MFD_NTXEC
1332 Say yes here if you want to support the RTC functionality of the
1333 embedded controller found in certain e-book readers designed by the
1334 original design manufacturer Netronix.
1336 comment "on-CPU RTC drivers"
1338 config RTC_DRV_ASM9260
1339 tristate "Alphascale asm9260 RTC"
1340 depends on MACH_ASM9260 || COMPILE_TEST
1342 If you say yes here you get support for the RTC on the
1343 Alphascale asm9260 SoC.
1345 This driver can also be built as a module. If so, the module
1346 will be called rtc-asm9260.
1348 config RTC_DRV_DIGICOLOR
1349 tristate "Conexant Digicolor RTC"
1350 depends on ARCH_DIGICOLOR || COMPILE_TEST
1352 If you say yes here you get support for the RTC on Conexant
1353 Digicolor platforms. This currently includes the CX92755 SoC.
1355 This driver can also be built as a module. If so, the module
1356 will be called rtc-digicolor.
1358 config RTC_DRV_IMXDI
1359 tristate "Freescale IMX DryIce Real Time Clock"
1363 Support for Freescale IMX DryIce RTC
1365 This driver can also be built as a module, if so, the module
1366 will be called "rtc-imxdi".
1368 config RTC_DRV_FSL_FTM_ALARM
1369 tristate "Freescale FlexTimer alarm timer"
1370 depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST
1372 For the FlexTimer in LS1012A, LS1021A, LS1028A, LS1043A, LS1046A,
1373 LS1088A, LS208xA, we can use FTM as the wakeup source.
1375 Say y here to enable FTM alarm support. The FTM alarm provides
1376 alarm functions for wakeup system from deep sleep.
1378 This driver can also be built as a module, if so, the module
1379 will be called "rtc-fsl-ftm-alarm".
1381 config RTC_DRV_MESON
1382 tristate "Amlogic Meson RTC"
1383 depends on (ARM && ARCH_MESON) || COMPILE_TEST
1386 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1389 This driver can also be built as a module, if so, the module
1390 will be called "rtc-meson".
1392 config RTC_DRV_MESON_VRTC
1393 tristate "Amlogic Meson Virtual RTC"
1394 depends on ARCH_MESON || COMPILE_TEST
1395 default m if ARCH_MESON
1397 If you say yes here you will get support for the
1398 Virtual RTC of Amlogic SoCs.
1400 This driver can also be built as a module. If so, the module
1401 will be called rtc-meson-vrtc.
1404 tristate "TI OMAP Real Time Clock"
1405 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1408 select GENERIC_PINCONF
1410 Say "yes" here to support the on chip real time clock
1411 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1413 This driver can also be built as a module, if so, module
1414 will be called rtc-omap.
1417 tristate "Samsung S3C series SoC RTC"
1418 depends on ARCH_EXYNOS || ARCH_S3C64XX || ARCH_S3C24XX || ARCH_S5PV210 || \
1421 RTC (Realtime Clock) driver for the clock inbuilt into the
1422 Samsung S3C24XX series of SoCs. This can provide periodic
1423 interrupt rates from 1Hz to 64Hz for user programs, and
1426 The driver currently supports the common features on all the
1427 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1430 This driver can also be build as a module. If so, the module
1431 will be called rtc-s3c.
1433 config RTC_DRV_EP93XX
1434 tristate "Cirrus Logic EP93XX"
1435 depends on ARCH_EP93XX || COMPILE_TEST
1437 If you say yes here you get support for the
1438 RTC embedded in the Cirrus Logic EP93XX processors.
1440 This driver can also be built as a module. If so, the module
1441 will be called rtc-ep93xx.
1443 config RTC_DRV_SA1100
1444 tristate "SA11x0/PXA2xx/PXA910"
1445 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1447 If you say Y here you will get access to the real time clock
1448 built into your SA11x0 or PXA2xx CPU.
1450 To compile this driver as a module, choose M here: the
1451 module will be called rtc-sa1100.
1454 tristate "SuperH On-Chip RTC"
1455 depends on SUPERH || ARCH_RENESAS
1457 Say Y here to enable support for the on-chip RTC found in
1458 most SuperH processors. This RTC is also found in RZ/A SoCs.
1460 To compile this driver as a module, choose M here: the
1461 module will be called rtc-sh.
1463 config RTC_DRV_SUNPLUS
1464 tristate "Sunplus SP7021 RTC"
1465 depends on SOC_SP7021
1467 Say 'yes' to get support for the real-time clock present in
1468 Sunplus SP7021 - a SoC for industrial applications. It provides
1469 RTC status check, timer/alarm functionalities, user data
1470 reservation with the battery over 2.5V, RTC power status check
1473 This driver can also be built as a module. If so, the module
1474 will be called rtc-sunplus.
1476 config RTC_DRV_PL030
1477 tristate "ARM AMBA PL030 RTC"
1480 If you say Y here you will get access to ARM AMBA
1481 PrimeCell PL030 RTC found on certain ARM SOCs.
1483 To compile this driver as a module, choose M here: the
1484 module will be called rtc-pl030.
1486 config RTC_DRV_PL031
1487 tristate "ARM AMBA PL031 RTC"
1490 If you say Y here you will get access to ARM AMBA
1491 PrimeCell PL031 RTC found on certain ARM SOCs.
1493 To compile this driver as a module, choose M here: the
1494 module will be called rtc-pl031.
1496 config RTC_DRV_AT91RM9200
1497 tristate "AT91RM9200 or some AT91SAM9 RTC"
1498 depends on ARCH_AT91 || COMPILE_TEST
1501 Driver for the internal RTC (Realtime Clock) module found on
1502 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1503 this is powered by the backup power supply.
1505 config RTC_DRV_AT91SAM9
1506 tristate "AT91SAM9 RTT as RTC"
1507 depends on ARCH_AT91 || COMPILE_TEST
1508 depends on OF && HAS_IOMEM
1511 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1512 can be used as an RTC thanks to the backup power supply (e.g. a
1513 small coin cell battery) which keeps this block and the GPBR
1514 (General Purpose Backup Registers) block powered when the device
1516 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1517 probably want to use the real RTC block instead of the "RTT as an
1520 config RTC_DRV_AU1XXX
1521 tristate "Au1xxx Counter0 RTC support"
1522 depends on MIPS_ALCHEMY
1524 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1525 counter) to be used as a RTC.
1527 This driver can also be built as a module. If so, the module
1528 will be called rtc-au1xxx.
1530 config RTC_DRV_RS5C313
1531 tristate "Ricoh RS5C313"
1532 depends on SH_LANDISK
1534 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1537 tristate "Renesas RZ/N1 RTC"
1538 depends on ARCH_RZN1 || COMPILE_TEST
1539 depends on OF && HAS_IOMEM
1541 If you say yes here you get support for the Renesas RZ/N1 RTC.
1543 config RTC_DRV_GENERIC
1544 tristate "Generic RTC support"
1545 # Please consider writing a new RTC driver instead of using the generic
1547 depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST
1549 Say Y or M here to enable RTC support on systems using the generic
1550 RTC abstraction. If you do not know what you are doing, you should
1554 tristate "PXA27x/PXA3xx"
1556 select RTC_DRV_SA1100
1558 If you say Y here you will get access to the real time clock
1559 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1560 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1562 This RTC driver uses PXA RTC registers available since pxa27x
1563 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1565 config RTC_DRV_VT8500
1566 tristate "VIA/WonderMedia 85xx SoC RTC"
1567 depends on ARCH_VT8500 || COMPILE_TEST
1569 If you say Y here you will get access to the real time clock
1570 built into your VIA VT8500 SoC or its relatives.
1573 config RTC_DRV_SUN4V
1574 bool "SUN4V Hypervisor RTC"
1577 If you say Y here you will get support for the Hypervisor
1578 based RTC on SUN4V systems.
1580 config RTC_DRV_SUN6I
1581 bool "Allwinner A31 RTC"
1582 default MACH_SUN6I || MACH_SUN8I
1583 depends on COMMON_CLK
1584 depends on ARCH_SUNXI || COMPILE_TEST
1586 If you say Y here you will get support for the RTC found in
1587 some Allwinner SoCs like the A31 or the A64.
1589 config RTC_DRV_SUNXI
1590 tristate "Allwinner sun4i/sun7i RTC"
1591 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1593 If you say Y here you will get support for the RTC found on
1596 config RTC_DRV_STARFIRE
1600 If you say Y here you will get support for the RTC found on
1604 tristate "Marvell SoC RTC"
1605 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1607 If you say yes here you will get support for the in-chip RTC
1608 that can be found in some of Marvell's SoC devices, such as
1609 the Kirkwood 88F6281 and 88F6192.
1611 This driver can also be built as a module. If so, the module
1612 will be called rtc-mv.
1614 config RTC_DRV_ARMADA38X
1615 tristate "Armada 38x Marvell SoC RTC"
1616 depends on ARCH_MVEBU || COMPILE_TEST
1619 If you say yes here you will get support for the in-chip RTC
1620 that can be found in the Armada 38x Marvell's SoC device
1622 This driver can also be built as a module. If so, the module
1623 will be called armada38x-rtc.
1625 config RTC_DRV_CADENCE
1626 tristate "Cadence RTC driver"
1627 depends on OF && HAS_IOMEM
1629 If you say Y here you will get access to Cadence RTC IP
1630 found on certain SOCs.
1632 To compile this driver as a module, choose M here: the
1633 module will be called rtc-cadence.
1635 config RTC_DRV_FTRTC010
1636 tristate "Faraday Technology FTRTC010 RTC"
1637 depends on HAS_IOMEM
1640 If you say Y here you will get support for the
1641 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1643 This driver can also be built as a module. If so, the module
1644 will be called rtc-ftrtc010.
1650 If you say yes here you will get support for the RTC on PS3.
1652 This driver can also be built as a module. If so, the module
1653 will be called rtc-ps3.
1656 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1657 depends on ARCH_MXS || COMPILE_TEST
1660 If you say yes here you will get support for the onboard
1661 STMP3xxx/i.MX23/i.MX28 RTC.
1663 This driver can also be built as a module. If so, the module
1664 will be called rtc-stmp3xxx.
1670 If you say Y here you will get support for the RTC found on
1671 the PCAP2 ASIC used on some Motorola phones.
1673 config RTC_DRV_MC13XXX
1674 depends on MFD_MC13XXX
1675 tristate "Freescale MC13xxx RTC"
1677 This enables support for the RTCs found on Freescale's PMICs
1678 MC13783 and MC13892.
1680 config RTC_DRV_MPC5121
1681 tristate "Freescale MPC5121 built-in RTC"
1682 depends on PPC_MPC512x || PPC_MPC52xx
1684 If you say yes here you will get support for the
1685 built-in RTC on MPC5121 or on MPC5200.
1687 This driver can also be built as a module. If so, the module
1688 will be called rtc-mpc5121.
1690 config RTC_DRV_JZ4740
1691 tristate "Ingenic JZ4740 SoC"
1692 depends on MIPS || COMPILE_TEST
1695 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1698 This driver can also be built as a module. If so, the module
1699 will be called rtc-jz4740.
1701 config RTC_DRV_LPC24XX
1702 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1703 depends on ARCH_LPC18XX || COMPILE_TEST
1704 depends on OF && HAS_IOMEM
1706 This enables support for the NXP RTC found which can be found on
1707 NXP LPC178x/18xx/408x/43xx devices.
1709 If you have one of the devices above enable this driver to use
1710 the hardware RTC. This driver can also be built as a module. If
1711 so, the module will be called rtc-lpc24xx.
1713 config RTC_DRV_LPC32XX
1714 depends on ARCH_LPC32XX || COMPILE_TEST
1715 tristate "NXP LPC32XX RTC"
1717 This enables support for the NXP RTC in the LPC32XX
1719 This driver can also be built as a module. If so, the module
1720 will be called rtc-lpc32xx.
1722 config RTC_DRV_PM8XXX
1723 tristate "Qualcomm PMIC8XXX RTC"
1724 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1726 If you say yes here you get support for the
1727 Qualcomm PMIC8XXX RTC.
1729 To compile this driver as a module, choose M here: the
1730 module will be called rtc-pm8xxx.
1732 config RTC_DRV_TEGRA
1733 tristate "NVIDIA Tegra Internal RTC driver"
1734 depends on ARCH_TEGRA || COMPILE_TEST
1736 If you say yes here you get support for the
1737 Tegra 200 series internal RTC module.
1739 This drive can also be built as a module. If so, the module
1740 will be called rtc-tegra.
1742 config RTC_DRV_LOONGSON1
1743 tristate "loongson1 RTC support"
1744 depends on MACH_LOONGSON32
1746 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1747 counter) to be used as a RTC.
1749 This driver can also be built as a module. If so, the module
1750 will be called rtc-ls1x.
1753 tristate "Freescale MXC Real Time Clock"
1754 depends on ARCH_MXC || COMPILE_TEST
1755 depends on HAS_IOMEM
1758 If you say yes here you get support for the Freescale MXC
1761 This driver can also be built as a module, if so, the module
1762 will be called "rtc-mxc".
1764 config RTC_DRV_MXC_V2
1765 tristate "Freescale MXC Real Time Clock for i.MX53"
1766 depends on ARCH_MXC || COMPILE_TEST
1767 depends on HAS_IOMEM
1770 If you say yes here you get support for the Freescale MXC
1771 SRTC module in i.MX53 processor.
1773 This driver can also be built as a module, if so, the module
1774 will be called "rtc-mxc_v2".
1777 tristate "Freescale SNVS RTC support"
1779 depends on ARCH_MXC || COMPILE_TEST
1780 depends on HAS_IOMEM
1783 If you say yes here you get support for the Freescale SNVS
1784 Low Power (LP) RTC module.
1786 This driver can also be built as a module, if so, the module
1787 will be called "rtc-snvs".
1789 config RTC_DRV_IMX_SC
1791 depends on HAVE_ARM_SMCCC
1792 tristate "NXP i.MX System Controller RTC support"
1794 If you say yes here you get support for the NXP i.MX System
1795 Controller RTC module.
1797 config RTC_DRV_ST_LPC
1798 tristate "STMicroelectronics LPC RTC"
1802 Say Y here to include STMicroelectronics Low Power Controller
1803 (LPC) based RTC support.
1805 To compile this driver as a module, choose M here: the
1806 module will be called rtc-st-lpc.
1808 config RTC_DRV_MOXART
1809 tristate "MOXA ART RTC"
1810 depends on ARCH_MOXART || COMPILE_TEST
1812 If you say yes here you get support for the MOXA ART
1815 This driver can also be built as a module. If so, the module
1816 will be called rtc-moxart
1818 config RTC_DRV_MT2712
1819 tristate "MediaTek MT2712 SoC based RTC"
1820 depends on ARCH_MEDIATEK || COMPILE_TEST
1822 This enables support for the real time clock built in the MediaTek
1825 This drive can also be built as a module. If so, the module
1826 will be called rtc-mt2712.
1828 config RTC_DRV_MT6397
1829 tristate "MediaTek PMIC based RTC"
1830 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1832 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1833 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1834 MediaTek(R) RTC driver.
1836 If you want to use MediaTek(R) RTC interface, select Y or M here.
1838 config RTC_DRV_MT7622
1839 tristate "MediaTek SoC based RTC"
1840 depends on ARCH_MEDIATEK || COMPILE_TEST
1842 This enables support for the real time clock built in the MediaTek
1845 This drive can also be built as a module. If so, the module
1846 will be called rtc-mt7622.
1848 config RTC_DRV_XGENE
1849 tristate "APM X-Gene RTC"
1850 depends on HAS_IOMEM
1851 depends on ARCH_XGENE || COMPILE_TEST
1853 If you say yes here you get support for the APM X-Gene SoC real time
1856 This driver can also be built as a module, if so, the module
1857 will be called "rtc-xgene".
1859 config RTC_DRV_PIC32
1860 tristate "Microchip PIC32 RTC"
1861 depends on MACH_PIC32
1864 If you say yes here you get support for the PIC32 RTC module.
1866 This driver can also be built as a module. If so, the module
1867 will be called rtc-pic32
1869 config RTC_DRV_R7301
1870 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1872 depends on OF && HAS_IOMEM
1874 If you say yes here you get support for the EPSON TOYOCOM
1875 RTC-7301SF/DG chips.
1877 This driver can also be built as a module. If so, the module
1878 will be called rtc-r7301.
1880 config RTC_DRV_STM32
1881 tristate "STM32 RTC"
1883 depends on ARCH_STM32 || COMPILE_TEST
1885 If you say yes here you get support for the STM32 On-Chip
1888 This driver can also be built as a module, if so, the module
1889 will be called "rtc-stm32".
1891 config RTC_DRV_CPCAP
1892 depends on MFD_CPCAP
1893 tristate "Motorola CPCAP RTC"
1895 Say y here for CPCAP rtc found on some Motorola phones
1896 and tablets such as Droid 4.
1898 config RTC_DRV_RTD119X
1899 bool "Realtek RTD129x RTC"
1900 depends on ARCH_REALTEK || COMPILE_TEST
1901 default ARCH_REALTEK
1903 If you say yes here, you get support for the RTD1295 SoC
1906 config RTC_DRV_ASPEED
1907 tristate "ASPEED RTC"
1909 depends on ARCH_ASPEED || COMPILE_TEST
1911 If you say yes here you get support for the ASPEED BMC SoC real time
1914 This driver can also be built as a module, if so, the module
1915 will be called "rtc-aspeed".
1917 config RTC_DRV_TI_K3
1918 tristate "TI K3 RTC"
1919 depends on ARCH_K3 || COMPILE_TEST
1922 If you say yes here you get support for the Texas Instruments's
1923 Real Time Clock for K3 architecture.
1925 This driver can also be built as a module, if so, the module
1926 will be called "rtc-ti-k3".
1928 comment "HID Sensor RTC drivers"
1930 config RTC_DRV_HID_SENSOR_TIME
1931 tristate "HID Sensor Time"
1933 depends on HID_SENSOR_HUB && IIO
1934 select HID_SENSOR_IIO_COMMON
1936 Say yes here to build support for the HID Sensors of type Time.
1937 This drivers makes such sensors available as RTCs.
1939 If this driver is compiled as a module, it will be named
1940 rtc-hid-sensor-time.
1942 config RTC_DRV_GOLDFISH
1943 tristate "Goldfish Real Time Clock"
1944 depends on HAS_IOMEM
1946 Say yes to enable RTC driver for the Goldfish based virtual platform.
1948 Goldfish is a code name for the virtual platform developed by Google
1949 for Android emulation.
1951 config RTC_DRV_WILCO_EC
1952 tristate "Wilco EC RTC"
1956 If you say yes here, you get read/write support for the Real Time
1957 Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook)
1959 This can also be built as a module. If so, the module will
1960 be named "rtc_wilco_ec".
1962 config RTC_DRV_MSC313
1963 tristate "MStar MSC313 RTC"
1964 depends on ARCH_MSTARV7 || COMPILE_TEST
1966 If you say yes here you get support for the Mstar MSC313e On-Chip
1969 This driver can also be built as a module, if so, the module
1970 will be called "rtc-msc313".
1972 config RTC_DRV_POLARFIRE_SOC
1973 tristate "Microchip PolarFire SoC built-in RTC"
1974 depends on SOC_MICROCHIP_POLARFIRE
1976 If you say yes here you will get support for the
1977 built-in RTC on Polarfire SoC.
1979 This driver can also be built as a module, if so, the module
1980 will be called "rtc-mpfs".