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.
227 tristate "Raspberry Pi RTC"
228 depends on ARCH_BRCMSTB || COMPILE_TEST
231 If you say yes here you get support for the RTC found on
232 Raspberry Pi devices.
234 This driver can also be built as a module. If so, the module
235 will be called rtc-rpi.
237 config RTC_DRV_BRCMSTB
238 tristate "Broadcom STB wake-timer"
239 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
240 default ARCH_BRCMSTB || BMIPS_GENERIC
242 If you say yes here you get support for the wake-timer found on
243 Broadcom STB SoCs (BCM7xxx).
245 This driver can also be built as a module. If so, the module will
246 be called rtc-brcmstb-waketimer.
248 config RTC_DRV_AS3722
249 tristate "ams AS3722 RTC driver"
250 depends on MFD_AS3722
252 If you say yes here you get support for the RTC of ams AS3722 PMIC
255 This driver can also be built as a module. If so, the module
256 will be called rtc-as3722.
258 config RTC_DRV_DS1307
259 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"
261 select WATCHDOG_CORE if WATCHDOG
263 If you say yes here you get support for various compatible RTC
264 chips (often with battery backup) connected with I2C. This driver
265 should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341,
266 ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.
267 In some cases the RTC must already have been initialized (by
268 manufacturing or a bootloader).
270 The first seven registers on these chips hold an RTC, and other
271 registers may add features such as NVRAM, a trickle charger for
272 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
273 sysfs, but other chip features may not be available.
275 This driver can also be built as a module. If so, the module
276 will be called rtc-ds1307.
278 config RTC_DRV_DS1307_CENTURY
279 bool "Century bit support for rtc-ds1307"
280 depends on RTC_DRV_DS1307
283 The DS1307 driver suffered from a bug where it was enabling the
284 century bit inconditionnally but never used it when reading the time.
285 It made the driver unable to support dates beyond 2099.
286 Setting this option will add proper support for the century bit but if
287 the time was previously set using a kernel predating this option,
288 reading the date will return a date in the next century.
289 To solve that, you could boot a kernel without this option set, set
290 the RTC date and then boot a kernel with this option set.
292 config RTC_DRV_DS1374
293 tristate "Dallas/Maxim DS1374"
295 If you say yes here you get support for Dallas Semiconductor
296 DS1374 real-time clock chips. If an interrupt is associated
297 with the device, the alarm functionality is supported.
299 This driver can also be built as a module. If so, the module
300 will be called rtc-ds1374.
302 config RTC_DRV_DS1374_WDT
303 bool "Dallas/Maxim DS1374 watchdog timer"
304 depends on RTC_DRV_DS1374 && WATCHDOG
307 If you say Y here you will get support for the
308 watchdog timer in the Dallas Semiconductor DS1374
309 real-time clock chips.
311 config RTC_DRV_DS1672
312 tristate "Dallas/Maxim DS1672"
314 If you say yes here you get support for the
315 Dallas/Maxim DS1672 timekeeping chip.
317 This driver can also be built as a module. If so, the module
318 will be called rtc-ds1672.
320 config RTC_DRV_HYM8563
321 tristate "Haoyu Microelectronics HYM8563"
324 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
325 from the usual rtc functions it provides a clock output of
328 This driver can also be built as a module. If so, the module
329 will be called rtc-hym8563.
331 config RTC_DRV_LP8788
332 tristate "TI LP8788 RTC driver"
333 depends on MFD_LP8788
335 Say Y to enable support for the LP8788 RTC/ALARM driver.
337 config RTC_DRV_MAX6900
338 tristate "Maxim MAX6900"
340 If you say yes here you will get support for the
341 Maxim MAX6900 I2C RTC chip.
343 This driver can also be built as a module. If so, the module
344 will be called rtc-max6900.
346 config RTC_DRV_MAX8907
347 tristate "Maxim MAX8907"
348 depends on MFD_MAX8907 || COMPILE_TEST
351 If you say yes here you will get support for the
352 RTC of Maxim MAX8907 PMIC.
354 This driver can also be built as a module. If so, the module
355 will be called rtc-max8907.
357 config RTC_DRV_MAX8925
358 tristate "Maxim MAX8925"
359 depends on MFD_MAX8925
361 If you say yes here you will get support for the
362 RTC of Maxim MAX8925 PMIC.
364 This driver can also be built as a module. If so, the module
365 will be called rtc-max8925.
367 config RTC_DRV_MAX8998
368 tristate "Maxim MAX8998"
369 depends on MFD_MAX8998
371 If you say yes here you will get support for the
372 RTC of Maxim MAX8998 PMIC.
374 This driver can also be built as a module. If so, the module
375 will be called rtc-max8998.
377 config RTC_DRV_MAX8997
378 tristate "Maxim MAX8997"
379 depends on MFD_MAX8997
381 If you say yes here you will get support for the
382 RTC of Maxim MAX8997 PMIC.
384 This driver can also be built as a module. If so, the module
385 will be called rtc-max8997.
387 config RTC_DRV_MAX77686
388 tristate "Maxim MAX77686"
389 depends on MFD_MAX77686 || MFD_MAX77620 || MFD_MAX77714 || COMPILE_TEST
391 If you say yes here you will get support for the
392 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
394 This driver can also be built as a module. If so, the module
395 will be called rtc-max77686.
397 config RTC_DRV_NCT3018Y
398 tristate "Nuvoton NCT3018Y"
401 If you say yes here you get support for the Nuvoton NCT3018Y I2C RTC
404 This driver can also be built as a module, if so, the module will be
405 called "rtc-nct3018y".
408 tristate "Rockchip RK805/RK808/RK809/RK817/RK818 RTC"
411 If you say yes here you will get support for the
412 RTC of RK805, RK809 and RK817, RK808 and RK818 PMIC.
414 This driver can also be built as a module. If so, the module
415 will be called rk808-rtc.
417 config RTC_DRV_RS5C372
418 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
420 If you say yes here you get support for the
421 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
423 This driver can also be built as a module. If so, the module
424 will be called rtc-rs5c372.
426 config RTC_DRV_ISL1208
427 tristate "Intersil ISL1208"
429 If you say yes here you get support for the
430 Intersil ISL1208 RTC chip.
432 This driver can also be built as a module. If so, the module
433 will be called rtc-isl1208.
435 config RTC_DRV_ISL12022
436 tristate "Intersil ISL12022"
439 If you say yes here you get support for the
440 Intersil ISL12022 RTC chip.
442 This driver can also be built as a module. If so, the module
443 will be called rtc-isl12022.
445 config RTC_DRV_ISL12026
446 tristate "Intersil ISL12026"
449 If you say yes here you get support for the
450 Intersil ISL12026 RTC chip.
452 This driver can also be built as a module. If so, the module
453 will be called rtc-isl12026.
456 tristate "Xicor/Intersil X1205"
458 If you say yes here you get support for the
459 Xicor/Intersil X1205 RTC chip.
461 This driver can also be built as a module. If so, the module
462 will be called rtc-x1205.
464 config RTC_DRV_PCF8523
465 tristate "NXP PCF8523"
468 If you say yes here you get support for the NXP PCF8523 RTC
471 This driver can also be built as a module. If so, the module
472 will be called rtc-pcf8523.
474 config RTC_DRV_PCF85063
475 tristate "NXP PCF85063"
478 If you say yes here you get support for the PCF85063 RTC chip
480 This driver can also be built as a module. If so, the module
481 will be called rtc-pcf85063.
483 config RTC_DRV_PCF85363
484 tristate "NXP PCF85363"
487 If you say yes here you get support for the PCF85363 RTC chip.
489 This driver can also be built as a module. If so, the module
490 will be called rtc-pcf85363.
492 The nvmem interface will be named pcf85363-#, where # is the
493 zero-based instance number.
495 config RTC_DRV_PCF8563
496 tristate "Philips PCF8563/Epson RTC8564"
498 If you say yes here you get support for the
499 Philips PCF8563 RTC chip. The Epson RTC8564
502 This driver can also be built as a module. If so, the module
503 will be called rtc-pcf8563.
505 config RTC_DRV_PCF8583
506 tristate "Philips PCF8583"
508 If you say yes here you get support for the Philips PCF8583
509 RTC chip found on Acorn RiscPCs. This driver supports the
510 platform specific method of retrieving the current year from
511 the RTC's SRAM. It will work on other platforms with the same
512 chip, but the year will probably have to be tweaked.
514 This driver can also be built as a module. If so, the module
515 will be called rtc-pcf8583.
517 config RTC_DRV_M41T80
518 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
520 If you say Y here you will get support for the ST M41T60
521 and M41T80 RTC chips series. Currently, the following chips are
522 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
523 M41ST85, M41ST87, and MicroCrystal RV4162.
525 This driver can also be built as a module. If so, the module
526 will be called rtc-m41t80.
528 config RTC_DRV_M41T80_WDT
529 bool "ST M41T65/M41T80 series RTC watchdog timer"
530 depends on RTC_DRV_M41T80
532 If you say Y here you will get support for the
533 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
535 config RTC_DRV_BD70528
536 tristate "ROHM BD71815 and BD71828 PMIC RTC"
537 depends on MFD_ROHM_BD71828
539 If you say Y here you will get support for the RTC
540 block on ROHM BD71815 and BD71828 Power Management IC.
542 This driver can also be built as a module. If so, the module
543 will be called rtc-bd70528.
546 tristate "TI BQ32000"
548 If you say Y here you will get support for the TI
549 BQ32000 I2C RTC chip.
551 This driver can also be built as a module. If so, the module
552 will be called rtc-bq32k.
554 config RTC_DRV_TWL92330
555 bool "TI TWL92330/Menelaus"
558 If you say yes here you get support for the RTC on the
559 TWL92330 "Menelaus" power management chip, used with OMAP2
560 platforms. The support is integrated with the rest of
561 the Menelaus driver; it's not separate module.
563 config RTC_DRV_TWL4030
564 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
565 depends on TWL4030_CORE
568 If you say yes here you get support for the RTC on the
569 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
571 This driver can also be built as a module. If so, the module
572 will be called rtc-twl.
574 config RTC_DRV_PALMAS
575 tristate "TI Palmas RTC driver"
576 depends on MFD_PALMAS
578 If you say yes here you get support for the RTC of TI PALMA series PMIC
581 This driver can also be built as a module. If so, the module
582 will be called rtc-palma.
584 config RTC_DRV_TPS6586X
585 tristate "TI TPS6586X RTC driver"
586 depends on MFD_TPS6586X
588 TI Power Management IC TPS6586X supports RTC functionality
589 along with alarm. This driver supports the RTC driver for
590 the TPS6586X RTC module.
592 config RTC_DRV_TPS65910
593 tristate "TI TPS65910 RTC driver"
594 depends on MFD_TPS65910
596 If you say yes here you get support for the RTC on the
599 This driver can also be built as a module. If so, the module
600 will be called rtc-tps65910.
602 config RTC_DRV_RC5T583
603 tristate "RICOH 5T583 RTC driver"
604 depends on MFD_RC5T583
606 If you say yes here you get support for the RTC on the
609 This driver can also be built as a module. If so, the module
610 will be called rtc-rc5t583.
612 config RTC_DRV_RC5T619
613 tristate "RICOH RC5T619 RTC driver"
614 depends on MFD_RN5T618
616 If you say yes here you get support for the RTC on the
619 This driver can also be built as a module. If so, the module
620 will be called rtc-rc5t619.
622 config RTC_DRV_S35390A
623 tristate "Seiko Instruments S-35390A"
626 If you say yes here you will get support for the Seiko
627 Instruments S-35390A.
629 This driver can also be built as a module. If so the module
630 will be called rtc-s35390a.
632 config RTC_DRV_FM3130
633 tristate "Ramtron FM3130"
635 If you say Y here you will get support for the
636 Ramtron FM3130 RTC chips.
637 Ramtron FM3130 is a chip with two separate devices inside,
638 RTC clock and FRAM. This driver provides only RTC functionality.
640 This driver can also be built as a module. If so the module
641 will be called rtc-fm3130.
643 config RTC_DRV_RX8010
644 tristate "Epson RX8010SJ"
647 If you say yes here you get support for the Epson RX8010SJ RTC
650 This driver can also be built as a module. If so, the module
651 will be called rtc-rx8010.
653 config RTC_DRV_RX8581
654 tristate "Epson RX-8571/RX-8581"
657 If you say yes here you will get support for the Epson RX-8571/
660 This driver can also be built as a module. If so the module
661 will be called rtc-rx8581.
663 config RTC_DRV_RX8025
664 tristate "Epson RX-8025SA/NB"
666 If you say yes here you get support for the Epson
667 RX-8025SA/NB RTC chips.
669 This driver can also be built as a module. If so, the module
670 will be called rtc-rx8025.
672 config RTC_DRV_EM3027
673 tristate "EM Microelectronic EM3027"
675 If you say yes here you get support for the EM
676 Microelectronic EM3027 RTC chips.
678 This driver can also be built as a module. If so, the module
679 will be called rtc-em3027.
681 config RTC_DRV_RV3028
682 tristate "Micro Crystal RV3028"
685 If you say yes here you get support for the Micro Crystal
688 This driver can also be built as a module. If so, the module
689 will be called rtc-rv3028.
691 config RTC_DRV_RV3032
692 tristate "Micro Crystal RV3032"
695 If you say yes here you get support for the Micro Crystal
698 This driver can also be built as a module. If so, the module
699 will be called rtc-rv3032.
701 config RTC_DRV_RV8803
702 tristate "Micro Crystal RV8803, Epson RX8900"
704 If you say yes here you get support for the Micro Crystal RV8803 and
705 Epson RX8900 RTC chips.
707 This driver can also be built as a module. If so, the module
708 will be called rtc-rv8803.
711 tristate "Samsung S2M/S5M series"
712 depends on MFD_SEC_CORE || COMPILE_TEST
716 If you say yes here you will get support for the
717 RTC of Samsung S2MPS14 and S5M PMIC series.
719 This driver can also be built as a module. If so, the module
720 will be called rtc-s5m.
722 config RTC_DRV_SD3078
723 tristate "ZXW Shenzhen whwave SD3078"
726 If you say yes here you get support for the ZXW Shenzhen whwave
729 This driver can also be built as a module. If so, the module
730 will be called rtc-sd3078
734 comment "SPI RTC drivers"
738 config RTC_DRV_M41T93
741 If you say yes here you will get support for the
742 ST M41T93 SPI RTC chip.
744 This driver can also be built as a module. If so, the module
745 will be called rtc-m41t93.
747 config RTC_DRV_M41T94
750 If you say yes here you will get support for the
751 ST M41T94 SPI RTC chip.
753 This driver can also be built as a module. If so, the module
754 will be called rtc-m41t94.
756 config RTC_DRV_DS1302
757 tristate "Dallas/Maxim DS1302"
760 If you say yes here you get support for the Dallas DS1302 RTC chips.
762 This driver can also be built as a module. If so, the module
763 will be called rtc-ds1302.
765 config RTC_DRV_DS1305
766 tristate "Dallas/Maxim DS1305/DS1306"
768 Select this driver to get support for the Dallas/Maxim DS1305
769 and DS1306 real time clock chips. These support a trickle
770 charger, alarms, and NVRAM in addition to the clock.
772 This driver can also be built as a module. If so, the module
773 will be called rtc-ds1305.
775 config RTC_DRV_DS1343
777 tristate "Dallas/Maxim DS1343/DS1344"
779 If you say yes here you get support for the
780 Dallas/Maxim DS1343 and DS1344 real time clock chips.
781 Support for trickle charger, alarm is provided.
783 This driver can also be built as a module. If so, the module
784 will be called rtc-ds1343.
786 config RTC_DRV_DS1347
788 tristate "Dallas/Maxim DS1347"
790 If you say yes here you get support for the
791 Dallas/Maxim DS1347 chips.
793 This driver only supports the RTC feature, and not other chip
794 features such as alarms.
796 This driver can also be built as a module. If so, the module
797 will be called rtc-ds1347.
799 config RTC_DRV_DS1390
800 tristate "Dallas/Maxim DS1390/93/94"
802 If you say yes here you get support for the
803 Dallas/Maxim DS1390/93/94 chips.
805 This driver supports the RTC feature and trickle charging but not
806 other chip features such as alarms.
808 This driver can also be built as a module. If so, the module
809 will be called rtc-ds1390.
811 config RTC_DRV_MAX6916
812 tristate "Maxim MAX6916"
814 If you say yes here you will get support for the
815 Maxim MAX6916 SPI RTC chip.
817 This driver only supports the RTC feature, and not other chip
818 features such as alarms.
820 This driver can also be built as a module. If so, the module
821 will be called rtc-max6916.
824 tristate "Epson RTC-9701JE"
826 If you say yes here you will get support for the
827 Epson RTC-9701JE SPI RTC chip.
829 This driver can also be built as a module. If so, the module
830 will be called rtc-r9701.
832 config RTC_DRV_RX4581
833 tristate "Epson RX-4581"
835 If you say yes here you will get support for the Epson RX-4581.
837 This driver can also be built as a module. If so the module
838 will be called rtc-rx4581.
840 config RTC_DRV_RS5C348
841 tristate "Ricoh RS5C348A/B"
843 If you say yes here you get support for the
844 Ricoh RS5C348A and RS5C348B RTC chips.
846 This driver can also be built as a module. If so, the module
847 will be called rtc-rs5c348.
849 config RTC_DRV_MAX6902
850 tristate "Maxim MAX6902"
852 If you say yes here you will get support for the
853 Maxim MAX6902 SPI RTC chip.
855 This driver can also be built as a module. If so, the module
856 will be called rtc-max6902.
858 config RTC_DRV_PCF2123
859 tristate "NXP PCF2123"
862 If you say yes here you get support for the NXP PCF2123
865 This driver can also be built as a module. If so, the module
866 will be called rtc-pcf2123.
868 config RTC_DRV_MCP795
869 tristate "Microchip MCP795"
871 If you say yes here you will get support for the Microchip MCP795.
873 This driver can also be built as a module. If so the module
874 will be called rtc-mcp795.
879 # Helper to resolve issues with configs that have SPI enabled but I2C
880 # modular. See SND_SOC_I2C_AND_SPI for more information
882 config RTC_I2C_AND_SPI
886 default y if SPI_MASTER=y
888 comment "SPI and I2C RTC drivers"
890 config RTC_DRV_DS3232
891 tristate "Dallas/Maxim DS3232/DS3234"
892 depends on RTC_I2C_AND_SPI
893 select REGMAP_I2C if I2C
894 select REGMAP_SPI if SPI_MASTER
896 If you say yes here you get support for Dallas Semiconductor
897 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
898 with the device, the alarm functionality is supported.
900 This driver can also be built as a module. If so, the module
901 will be called rtc-ds3232.
903 config RTC_DRV_DS3232_HWMON
904 bool "HWMON support for Dallas/Maxim DS3232/DS3234"
905 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
908 Say Y here if you want to expose temperature sensor data on
911 config RTC_DRV_PCF2127
912 tristate "NXP PCF2127"
913 depends on RTC_I2C_AND_SPI
914 select REGMAP_I2C if I2C
915 select REGMAP_SPI if SPI_MASTER
916 select WATCHDOG_CORE if WATCHDOG
918 If you say yes here you get support for the NXP PCF2127/29/31 RTC
919 chips with integrated quartz crystal for industrial applications.
920 These chips also have watchdog timer and tamper switch detection
923 PCF2127 has an additional feature of 512 bytes battery backed
924 memory that's accessible using nvmem interface.
926 This driver can also be built as a module. If so, the module
927 will be called rtc-pcf2127.
929 config RTC_DRV_RV3029C2
930 tristate "Micro Crystal RV3029/3049"
931 depends on RTC_I2C_AND_SPI
932 select REGMAP_I2C if I2C
933 select REGMAP_SPI if SPI_MASTER
935 If you say yes here you get support for the Micro Crystal
936 RV3029 and RV3049 RTC chips.
938 This driver can also be built as a module. If so, the module
939 will be called rtc-rv3029c2.
941 config RTC_DRV_RV3029_HWMON
942 bool "HWMON support for RV3029/3049"
943 depends on RTC_DRV_RV3029C2 && HWMON
944 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
947 Say Y here if you want to expose temperature sensor data on
950 config RTC_DRV_RX6110
951 tristate "Epson RX-6110"
952 depends on RTC_I2C_AND_SPI
953 select REGMAP_SPI if SPI_MASTER
954 select REGMAP_I2C if I2C
956 If you say yes here you will get support for the Epson RX-6110.
958 This driver can also be built as a module. If so the module
959 will be called rtc-rx6110.
961 comment "Platform RTC drivers"
963 # this 'CMOS' RTC driver is arch dependent because it requires
964 # <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
965 # global rtc_lock ... it's not yet just another platform_device.
968 tristate "PC-style 'CMOS'"
969 depends on X86 || ARM || PPC || MIPS || SPARC64
970 depends on HAS_IOPORT || MACH_DECSTATION
972 select RTC_MC146818_LIB
974 Say "yes" here to get direct support for the real time clock
975 found in every PC or ACPI-based system, and some other boards.
976 Specifically the original MC146818, compatibles like those in
977 PC south bridges, the DS12887 or M48T86, some multifunction
978 or LPC bus chips, and so on.
980 Your system will need to define the platform device used by
981 this driver, otherwise it won't be accessible. This means
982 you can safely enable this driver if you don't know whether
983 or not your board has this kind of hardware.
985 This driver can also be built as a module. If so, the module
986 will be called rtc-cmos.
989 bool "Alpha PC-style CMOS"
991 depends on HAS_IOPORT
992 select RTC_MC146818_LIB
995 Direct support for the real-time clock found on every Alpha
996 system, specifically MC146818 compatibles. If in doubt, say Y.
998 config RTC_DRV_DS1216
999 tristate "Dallas DS1216"
1002 If you say yes here you get support for the Dallas DS1216 RTC chips.
1004 config RTC_DRV_DS1286
1005 tristate "Dallas DS1286"
1006 depends on HAS_IOMEM
1008 If you say yes here you get support for the Dallas DS1286 RTC chips.
1010 config RTC_DRV_DS1511
1011 tristate "Dallas DS1511"
1012 depends on HAS_IOMEM
1014 If you say yes here you get support for the
1015 Dallas DS1511 timekeeping/watchdog chip.
1017 This driver can also be built as a module. If so, the module
1018 will be called rtc-ds1511.
1020 config RTC_DRV_DS1553
1021 tristate "Maxim/Dallas DS1553"
1022 depends on HAS_IOMEM
1024 If you say yes here you get support for the
1025 Maxim/Dallas DS1553 timekeeping chip.
1027 This driver can also be built as a module. If so, the module
1028 will be called rtc-ds1553.
1030 config RTC_DRV_DS1685_FAMILY
1031 tristate "Dallas/Maxim DS1685 Family"
1032 depends on HAS_IOMEM
1034 If you say yes here you get support for the Dallas/Maxim DS1685
1035 family of real time chips. This family includes the DS1685/DS1687,
1036 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
1037 DS17885/DS17887 chips.
1039 This driver can also be built as a module. If so, the module
1040 will be called rtc-ds1685.
1044 depends on RTC_DRV_DS1685_FAMILY
1045 default RTC_DRV_DS1685
1047 config RTC_DRV_DS1685
1048 bool "DS1685/DS1687"
1050 This enables support for the Dallas/Maxim DS1685/DS1687 real time
1053 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
1054 systems, as well as EPPC-405-UC modules by electronic system design
1057 config RTC_DRV_DS1689
1058 bool "DS1689/DS1693"
1060 This enables support for the Dallas/Maxim DS1689/DS1693 real time
1063 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
1064 which supports a few minor features such as Vcc, Vbat, and Power
1065 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
1067 It also works for the even older DS1688/DS1691 RTC chips, which are
1068 virtually the same and carry the same model number. Both chips
1069 have 114 bytes of user NVRAM.
1071 config RTC_DRV_DS17285
1072 bool "DS17285/DS17287"
1074 This enables support for the Dallas/Maxim DS17285/DS17287 real time
1077 This chip features 2kb of extended NV-SRAM. It may possibly be
1078 found in some SGI O2 systems (rare).
1080 config RTC_DRV_DS17485
1081 bool "DS17485/DS17487"
1083 This enables support for the Dallas/Maxim DS17485/DS17487 real time
1086 This chip features 4kb of extended NV-SRAM.
1088 config RTC_DRV_DS17885
1089 bool "DS17885/DS17887"
1091 This enables support for the Dallas/Maxim DS17885/DS17887 real time
1094 This chip features 8kb of extended NV-SRAM.
1098 config RTC_DRV_DS1742
1099 tristate "Maxim/Dallas DS1742/1743"
1100 depends on HAS_IOMEM
1102 If you say yes here you get support for the
1103 Maxim/Dallas DS1742/1743 timekeeping chip.
1105 This driver can also be built as a module. If so, the module
1106 will be called rtc-ds1742.
1108 config RTC_DRV_DS2404
1109 tristate "Maxim/Dallas DS2404"
1111 If you say yes here you get support for the
1112 Dallas DS2404 RTC chip.
1114 This driver can also be built as a module. If so, the module
1115 will be called rtc-ds2404.
1117 config RTC_DRV_DA9052
1118 tristate "Dialog DA9052/DA9053 RTC"
1119 depends on PMIC_DA9052
1121 Say y here to support the RTC driver for Dialog Semiconductor
1122 DA9052-BC and DA9053-AA/Bx PMICs.
1124 config RTC_DRV_DA9055
1125 tristate "Dialog Semiconductor DA9055 RTC"
1126 depends on MFD_DA9055
1128 If you say yes here you will get support for the
1129 RTC of the Dialog DA9055 PMIC.
1131 This driver can also be built as a module. If so, the module
1132 will be called rtc-da9055
1134 config RTC_DRV_DA9063
1135 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1136 depends on MFD_DA9063 || MFD_DA9062
1138 If you say yes here you will get support for the RTC subsystem
1139 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1141 This driver can also be built as a module. If so, the module
1142 will be called "rtc-da9063".
1146 depends on EFI && !X86
1148 If you say yes here you will get support for the EFI
1151 This driver can also be built as a module. If so, the module
1152 will be called rtc-efi.
1154 config RTC_DRV_STK17TA8
1155 tristate "Simtek STK17TA8"
1156 depends on HAS_IOMEM
1158 If you say yes here you get support for the
1159 Simtek STK17TA8 timekeeping chip.
1161 This driver can also be built as a module. If so, the module
1162 will be called rtc-stk17ta8.
1164 config RTC_DRV_M48T86
1165 tristate "ST M48T86/Dallas DS12887"
1166 depends on HAS_IOMEM
1168 If you say Y here you will get support for the
1169 ST M48T86 and Dallas DS12887 RTC chips.
1171 This driver can also be built as a module. If so, the module
1172 will be called rtc-m48t86.
1174 config RTC_DRV_M48T35
1175 tristate "ST M48T35"
1176 depends on HAS_IOMEM
1178 If you say Y here you will get support for the
1181 This driver can also be built as a module, if so, the module
1182 will be called "rtc-m48t35".
1184 config RTC_DRV_M48T59
1185 tristate "ST M48T59/M48T08/M48T02"
1186 depends on HAS_IOMEM
1188 If you say Y here you will get support for the
1189 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1191 These chips are usually found in Sun SPARC and UltraSPARC
1194 This driver can also be built as a module, if so, the module
1195 will be called "rtc-m48t59".
1197 config RTC_DRV_MSM6242
1198 tristate "Oki MSM6242"
1199 depends on HAS_IOMEM
1201 If you say yes here you get support for the Oki MSM6242
1202 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1204 This driver can also be built as a module. If so, the module
1205 will be called rtc-msm6242.
1207 config RTC_DRV_BQ4802
1208 tristate "TI BQ4802"
1209 depends on HAS_IOMEM && HAS_IOPORT
1210 depends on SPARC || COMPILE_TEST
1212 If you say Y here you will get support for the TI
1215 This driver can also be built as a module. If so, the module
1216 will be called rtc-bq4802.
1218 config RTC_DRV_RP5C01
1219 tristate "Ricoh RP5C01"
1220 depends on HAS_IOMEM
1222 If you say yes here you get support for the Ricoh RP5C01
1223 timekeeping chip. It is used in some Amiga models (e.g. A3000
1226 This driver can also be built as a module. If so, the module
1227 will be called rtc-rp5c01.
1229 config RTC_DRV_GAMECUBE
1230 tristate "Nintendo GameCube, Wii and Wii U RTC"
1231 depends on GAMECUBE || WII || COMPILE_TEST
1234 If you say yes here you will get support for the RTC subsystem
1235 of the Nintendo GameCube, Wii and Wii U.
1237 This driver can also be built as a module. If so, the module
1238 will be called "rtc-gamecube".
1240 config RTC_DRV_WM831X
1241 tristate "Wolfson Microelectronics WM831x RTC"
1242 depends on MFD_WM831X
1244 If you say yes here you will get support for the RTC subsystem
1245 of the Wolfson Microelectronics WM831X series PMICs.
1247 This driver can also be built as a module. If so, the module
1248 will be called "rtc-wm831x".
1250 config RTC_DRV_WM8350
1251 tristate "Wolfson Microelectronics WM8350 RTC"
1252 depends on MFD_WM8350
1254 If you say yes here you will get support for the RTC subsystem
1255 of the Wolfson Microelectronics WM8350.
1257 This driver can also be built as a module. If so, the module
1258 will be called "rtc-wm8350".
1260 config RTC_DRV_SC27XX
1261 tristate "Spreadtrum SC27xx RTC"
1262 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1264 If you say Y here you will get support for the RTC subsystem
1265 of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs
1266 includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips.
1268 This driver can also be built as a module. If so, the module
1269 will be called rtc-sc27xx.
1271 config RTC_DRV_SPEAR
1272 tristate "SPEAR ST RTC"
1273 depends on PLAT_SPEAR || COMPILE_TEST
1276 If you say Y here you will get support for the RTC found on
1279 config RTC_DRV_PCF50633
1280 depends on MFD_PCF50633
1281 tristate "NXP PCF50633 RTC"
1283 If you say yes here you get support for the RTC subsystem of the
1284 NXP PCF50633 used in embedded systems.
1286 config RTC_DRV_AB8500
1287 tristate "ST-Ericsson AB8500 RTC"
1288 depends on AB8500_CORE
1290 select RTC_INTF_DEV_UIE_EMUL
1292 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1293 support. This chip contains a battery- and capacitor-backed RTC.
1296 tristate "IBM OPAL RTC driver"
1297 depends on PPC_POWERNV
1300 If you say yes here you get support for the PowerNV platform RTC
1301 driver based on OPAL interfaces.
1303 This driver can also be built as a module. If so, the module
1304 will be called rtc-opal.
1306 config RTC_DRV_OPTEE
1307 tristate "OP-TEE based RTC driver"
1310 Select this to get support for OP-TEE based RTC control on SoCs where
1311 RTC are not accessible to the normal world (Linux).
1313 This driver can also be built as a module. If so, the module
1314 will be called rtc-optee.
1316 config RTC_DRV_ZYNQMP
1317 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1318 depends on OF && HAS_IOMEM
1320 If you say yes here you get support for the RTC controller found on
1321 Xilinx Zynq Ultrascale+ MPSoC.
1323 config RTC_DRV_CROS_EC
1324 tristate "Chrome OS EC RTC driver"
1327 If you say yes here you will get support for the
1328 Chrome OS Embedded Controller's RTC.
1330 This driver can also be built as a module. If so, the module
1331 will be called rtc-cros-ec.
1333 config RTC_DRV_NTXEC
1334 tristate "Netronix embedded controller RTC"
1335 depends on MFD_NTXEC
1337 Say yes here if you want to support the RTC functionality of the
1338 embedded controller found in certain e-book readers designed by the
1339 original design manufacturer Netronix.
1341 comment "on-CPU RTC drivers"
1343 config RTC_DRV_ASM9260
1344 tristate "Alphascale asm9260 RTC"
1345 depends on MACH_ASM9260 || COMPILE_TEST
1347 If you say yes here you get support for the RTC on the
1348 Alphascale asm9260 SoC.
1350 This driver can also be built as a module. If so, the module
1351 will be called rtc-asm9260.
1353 config RTC_DRV_DIGICOLOR
1354 tristate "Conexant Digicolor RTC"
1355 depends on ARCH_DIGICOLOR || COMPILE_TEST
1357 If you say yes here you get support for the RTC on Conexant
1358 Digicolor platforms. This currently includes the CX92755 SoC.
1360 This driver can also be built as a module. If so, the module
1361 will be called rtc-digicolor.
1363 config RTC_DRV_IMXDI
1364 tristate "Freescale IMX DryIce Real Time Clock"
1368 Support for Freescale IMX DryIce RTC
1370 This driver can also be built as a module, if so, the module
1371 will be called "rtc-imxdi".
1373 config RTC_DRV_FSL_FTM_ALARM
1374 tristate "Freescale FlexTimer alarm timer"
1375 depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST
1377 For the FlexTimer in LS1012A, LS1021A, LS1028A, LS1043A, LS1046A,
1378 LS1088A, LS208xA, we can use FTM as the wakeup source.
1380 Say y here to enable FTM alarm support. The FTM alarm provides
1381 alarm functions for wakeup system from deep sleep.
1383 This driver can also be built as a module, if so, the module
1384 will be called "rtc-fsl-ftm-alarm".
1386 config RTC_DRV_MESON
1387 tristate "Amlogic Meson RTC"
1388 depends on (ARM && ARCH_MESON) || COMPILE_TEST
1391 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1394 This driver can also be built as a module, if so, the module
1395 will be called "rtc-meson".
1397 config RTC_DRV_MESON_VRTC
1398 tristate "Amlogic Meson Virtual RTC"
1399 depends on ARCH_MESON || COMPILE_TEST
1400 default m if ARCH_MESON
1402 If you say yes here you will get support for the
1403 Virtual RTC of Amlogic SoCs.
1405 This driver can also be built as a module. If so, the module
1406 will be called rtc-meson-vrtc.
1409 tristate "TI OMAP Real Time Clock"
1410 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1413 select GENERIC_PINCONF
1415 Say "yes" here to support the on chip real time clock
1416 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1418 This driver can also be built as a module, if so, module
1419 will be called rtc-omap.
1422 tristate "Samsung S3C series SoC RTC"
1423 depends on ARCH_EXYNOS || ARCH_S3C64XX || ARCH_S5PV210 || \
1426 RTC (Realtime Clock) driver for the clock inbuilt into the
1427 Samsung S3C64XX series of SoCs. This can provide periodic
1428 interrupt rates from 1Hz to 64Hz for user programs, and
1431 This driver can also be build as a module. If so, the module
1432 will be called rtc-s3c.
1434 config RTC_DRV_EP93XX
1435 tristate "Cirrus Logic EP93XX"
1436 depends on ARCH_EP93XX || COMPILE_TEST
1438 If you say yes here you get support for the
1439 RTC embedded in the Cirrus Logic EP93XX processors.
1441 This driver can also be built as a module. If so, the module
1442 will be called rtc-ep93xx.
1444 config RTC_DRV_SA1100
1445 tristate "SA11x0/PXA2xx/PXA910"
1446 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1448 If you say Y here you will get access to the real time clock
1449 built into your SA11x0 or PXA2xx CPU.
1451 To compile this driver as a module, choose M here: the
1452 module will be called rtc-sa1100.
1455 tristate "SuperH On-Chip RTC"
1456 depends on SUPERH || ARCH_RENESAS
1458 Say Y here to enable support for the on-chip RTC found in
1459 most SuperH processors. This RTC is also found in RZ/A SoCs.
1461 To compile this driver as a module, choose M here: the
1462 module will be called rtc-sh.
1464 config RTC_DRV_SUNPLUS
1465 tristate "Sunplus SP7021 RTC"
1466 depends on SOC_SP7021
1468 Say 'yes' to get support for the real-time clock present in
1469 Sunplus SP7021 - a SoC for industrial applications. It provides
1470 RTC status check, timer/alarm functionalities, user data
1471 reservation with the battery over 2.5V, RTC power status check
1474 This driver can also be built as a module. If so, the module
1475 will be called rtc-sunplus.
1477 config RTC_DRV_PL030
1478 tristate "ARM AMBA PL030 RTC"
1481 If you say Y here you will get access to ARM AMBA
1482 PrimeCell PL030 RTC found on certain ARM SOCs.
1484 To compile this driver as a module, choose M here: the
1485 module will be called rtc-pl030.
1487 config RTC_DRV_PL031
1488 tristate "ARM AMBA PL031 RTC"
1491 If you say Y here you will get access to ARM AMBA
1492 PrimeCell PL031 RTC found on certain ARM SOCs.
1494 To compile this driver as a module, choose M here: the
1495 module will be called rtc-pl031.
1497 config RTC_DRV_AT91RM9200
1498 tristate "AT91RM9200 or some AT91SAM9 RTC"
1499 depends on ARCH_AT91 || COMPILE_TEST
1502 Driver for the internal RTC (Realtime Clock) module found on
1503 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1504 this is powered by the backup power supply.
1506 config RTC_DRV_AT91SAM9
1507 tristate "AT91SAM9 RTT as RTC"
1508 depends on ARCH_AT91 || COMPILE_TEST
1509 depends on OF && HAS_IOMEM
1512 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1513 can be used as an RTC thanks to the backup power supply (e.g. a
1514 small coin cell battery) which keeps this block and the GPBR
1515 (General Purpose Backup Registers) block powered when the device
1517 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1518 probably want to use the real RTC block instead of the "RTT as an
1521 config RTC_DRV_AU1XXX
1522 tristate "Au1xxx Counter0 RTC support"
1523 depends on MIPS_ALCHEMY
1525 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1526 counter) to be used as a RTC.
1528 This driver can also be built as a module. If so, the module
1529 will be called rtc-au1xxx.
1531 config RTC_DRV_RS5C313
1532 tristate "Ricoh RS5C313"
1533 depends on SH_LANDISK
1535 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1538 tristate "Renesas RZ/N1 RTC"
1539 depends on ARCH_RZN1 || COMPILE_TEST
1540 depends on OF && HAS_IOMEM
1542 If you say yes here you get support for the Renesas RZ/N1 RTC.
1544 config RTC_DRV_GENERIC
1545 tristate "Generic RTC support"
1546 # Please consider writing a new RTC driver instead of using the generic
1548 depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST
1550 Say Y or M here to enable RTC support on systems using the generic
1551 RTC abstraction. If you do not know what you are doing, you should
1555 tristate "PXA27x/PXA3xx"
1557 select RTC_DRV_SA1100
1559 If you say Y here you will get access to the real time clock
1560 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1561 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1563 This RTC driver uses PXA RTC registers available since pxa27x
1564 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1566 config RTC_DRV_VT8500
1567 tristate "VIA/WonderMedia 85xx SoC RTC"
1568 depends on ARCH_VT8500 || COMPILE_TEST
1570 If you say Y here you will get access to the real time clock
1571 built into your VIA VT8500 SoC or its relatives.
1574 config RTC_DRV_SUN4V
1575 bool "SUN4V Hypervisor RTC"
1578 If you say Y here you will get support for the Hypervisor
1579 based RTC on SUN4V systems.
1581 config RTC_DRV_SUN6I
1582 bool "Allwinner A31 RTC"
1583 default MACH_SUN6I || MACH_SUN8I
1584 depends on COMMON_CLK
1585 depends on ARCH_SUNXI || COMPILE_TEST
1587 If you say Y here you will get support for the RTC found in
1588 some Allwinner SoCs like the A31 or the A64.
1590 config RTC_DRV_SUNXI
1591 tristate "Allwinner sun4i/sun7i RTC"
1592 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1594 If you say Y here you will get support for the RTC found on
1597 config RTC_DRV_STARFIRE
1601 If you say Y here you will get support for the RTC found on
1605 tristate "Marvell SoC RTC"
1606 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1608 If you say yes here you will get support for the in-chip RTC
1609 that can be found in some of Marvell's SoC devices, such as
1610 the Kirkwood 88F6281 and 88F6192.
1612 This driver can also be built as a module. If so, the module
1613 will be called rtc-mv.
1615 config RTC_DRV_ARMADA38X
1616 tristate "Armada 38x Marvell SoC RTC"
1617 depends on ARCH_MVEBU || COMPILE_TEST
1620 If you say yes here you will get support for the in-chip RTC
1621 that can be found in the Armada 38x Marvell's SoC device
1623 This driver can also be built as a module. If so, the module
1624 will be called armada38x-rtc.
1626 config RTC_DRV_CADENCE
1627 tristate "Cadence RTC driver"
1628 depends on OF && HAS_IOMEM
1630 If you say Y here you will get access to Cadence RTC IP
1631 found on certain SOCs.
1633 To compile this driver as a module, choose M here: the
1634 module will be called rtc-cadence.
1636 config RTC_DRV_FTRTC010
1637 tristate "Faraday Technology FTRTC010 RTC"
1638 depends on HAS_IOMEM
1641 If you say Y here you will get support for the
1642 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1644 This driver can also be built as a module. If so, the module
1645 will be called rtc-ftrtc010.
1651 If you say yes here you will get support for the RTC on PS3.
1653 This driver can also be built as a module. If so, the module
1654 will be called rtc-ps3.
1657 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1658 depends on ARCH_MXS || COMPILE_TEST
1661 If you say yes here you will get support for the onboard
1662 STMP3xxx/i.MX23/i.MX28 RTC.
1664 This driver can also be built as a module. If so, the module
1665 will be called rtc-stmp3xxx.
1671 If you say Y here you will get support for the RTC found on
1672 the PCAP2 ASIC used on some Motorola phones.
1674 config RTC_DRV_MC13XXX
1675 depends on MFD_MC13XXX
1676 tristate "Freescale MC13xxx RTC"
1678 This enables support for the RTCs found on Freescale's PMICs
1679 MC13783 and MC13892.
1681 config RTC_DRV_MPC5121
1682 tristate "Freescale MPC5121 built-in RTC"
1683 depends on PPC_MPC512x || PPC_MPC52xx
1685 If you say yes here you will get support for the
1686 built-in RTC on MPC5121 or on MPC5200.
1688 This driver can also be built as a module. If so, the module
1689 will be called rtc-mpc5121.
1691 config RTC_DRV_JZ4740
1692 tristate "Ingenic JZ4740 SoC"
1693 depends on MIPS || COMPILE_TEST
1694 depends on OF && COMMON_CLK
1696 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1699 This driver can also be built as a module. If so, the module
1700 will be called rtc-jz4740.
1702 config RTC_DRV_LOONGSON
1703 tristate "Loongson On-chip RTC"
1704 depends on MACH_LOONGSON32 || MACH_LOONGSON64 || COMPILE_TEST
1707 This is a driver for the Loongson on-chip Counter0 (Time-Of-Year
1708 counter) to be used as a RTC.
1709 It can be found on Loongson-1 series cpu, Loongson-2K series cpu
1710 and Loongson LS7A bridge chips.
1712 This driver can also be built as a module. If so, the module
1713 will be called rtc-loongson.
1715 config RTC_DRV_LPC24XX
1716 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1717 depends on ARCH_LPC18XX || COMPILE_TEST
1718 depends on OF && HAS_IOMEM
1720 This enables support for the NXP RTC found which can be found on
1721 NXP LPC178x/18xx/408x/43xx devices.
1723 If you have one of the devices above enable this driver to use
1724 the hardware RTC. This driver can also be built as a module. If
1725 so, the module will be called rtc-lpc24xx.
1727 config RTC_DRV_LPC32XX
1728 depends on ARCH_LPC32XX || COMPILE_TEST
1729 tristate "NXP LPC32XX RTC"
1731 This enables support for the NXP RTC in the LPC32XX
1733 This driver can also be built as a module. If so, the module
1734 will be called rtc-lpc32xx.
1736 config RTC_DRV_PM8XXX
1737 tristate "Qualcomm PMIC8XXX RTC"
1738 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1740 If you say yes here you get support for the
1741 Qualcomm PMIC8XXX RTC.
1743 To compile this driver as a module, choose M here: the
1744 module will be called rtc-pm8xxx.
1746 config RTC_DRV_TEGRA
1747 tristate "NVIDIA Tegra Internal RTC driver"
1748 depends on ARCH_TEGRA || COMPILE_TEST
1750 If you say yes here you get support for the
1751 Tegra 200 series internal RTC module.
1753 This drive can also be built as a module. If so, the module
1754 will be called rtc-tegra.
1757 tristate "Freescale MXC Real Time Clock"
1758 depends on ARCH_MXC || COMPILE_TEST
1759 depends on HAS_IOMEM
1762 If you say yes here you get support for the Freescale MXC
1765 This driver can also be built as a module, if so, the module
1766 will be called "rtc-mxc".
1768 config RTC_DRV_MXC_V2
1769 tristate "Freescale MXC Real Time Clock for i.MX53"
1770 depends on ARCH_MXC || COMPILE_TEST
1771 depends on HAS_IOMEM
1774 If you say yes here you get support for the Freescale MXC
1775 SRTC module in i.MX53 processor.
1777 This driver can also be built as a module, if so, the module
1778 will be called "rtc-mxc_v2".
1781 tristate "Freescale SNVS RTC support"
1783 depends on ARCH_MXC || COMPILE_TEST
1784 depends on HAS_IOMEM
1787 If you say yes here you get support for the Freescale SNVS
1788 Low Power (LP) RTC module.
1790 This driver can also be built as a module, if so, the module
1791 will be called "rtc-snvs".
1793 config RTC_DRV_BBNSM
1794 tristate "NXP BBNSM RTC support"
1796 depends on ARCH_MXC || COMPILE_TEST
1797 depends on HAS_IOMEM
1800 If you say yes here you get support for the NXP BBNSM RTC module.
1802 This driver can also be built as a module, if so, the module
1803 will be called "rtc-bbnsm".
1805 config RTC_DRV_IMX_SC
1807 depends on HAVE_ARM_SMCCC
1808 tristate "NXP i.MX System Controller RTC support"
1810 If you say yes here you get support for the NXP i.MX System
1811 Controller RTC module.
1813 config RTC_DRV_ST_LPC
1814 tristate "STMicroelectronics LPC RTC"
1818 Say Y here to include STMicroelectronics Low Power Controller
1819 (LPC) based RTC support.
1821 To compile this driver as a module, choose M here: the
1822 module will be called rtc-st-lpc.
1824 config RTC_DRV_MOXART
1825 tristate "MOXA ART RTC"
1826 depends on ARCH_MOXART || COMPILE_TEST
1828 If you say yes here you get support for the MOXA ART
1831 This driver can also be built as a module. If so, the module
1832 will be called rtc-moxart
1834 config RTC_DRV_MT2712
1835 tristate "MediaTek MT2712 SoC based RTC"
1836 depends on ARCH_MEDIATEK || COMPILE_TEST
1838 This enables support for the real time clock built in the MediaTek
1841 This drive can also be built as a module. If so, the module
1842 will be called rtc-mt2712.
1844 config RTC_DRV_MT6397
1845 tristate "MediaTek PMIC based RTC"
1846 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1848 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1849 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1850 MediaTek(R) RTC driver.
1852 If you want to use MediaTek(R) RTC interface, select Y or M here.
1854 config RTC_DRV_MT7622
1855 tristate "MediaTek SoC based RTC"
1856 depends on ARCH_MEDIATEK || COMPILE_TEST
1858 This enables support for the real time clock built in the MediaTek
1861 This drive can also be built as a module. If so, the module
1862 will be called rtc-mt7622.
1864 config RTC_DRV_XGENE
1865 tristate "APM X-Gene RTC"
1866 depends on HAS_IOMEM
1867 depends on ARCH_XGENE || COMPILE_TEST
1869 If you say yes here you get support for the APM X-Gene SoC real time
1872 This driver can also be built as a module, if so, the module
1873 will be called "rtc-xgene".
1875 config RTC_DRV_PIC32
1876 tristate "Microchip PIC32 RTC"
1877 depends on MACH_PIC32
1880 If you say yes here you get support for the PIC32 RTC module.
1882 This driver can also be built as a module. If so, the module
1883 will be called rtc-pic32
1885 config RTC_DRV_R7301
1886 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1888 depends on OF && HAS_IOMEM
1890 If you say yes here you get support for the EPSON TOYOCOM
1891 RTC-7301SF/DG chips.
1893 This driver can also be built as a module. If so, the module
1894 will be called rtc-r7301.
1896 config RTC_DRV_STM32
1897 tristate "STM32 RTC"
1899 depends on ARCH_STM32 || COMPILE_TEST
1901 If you say yes here you get support for the STM32 On-Chip
1904 This driver can also be built as a module, if so, the module
1905 will be called "rtc-stm32".
1907 config RTC_DRV_CPCAP
1908 depends on MFD_CPCAP
1909 tristate "Motorola CPCAP RTC"
1911 Say y here for CPCAP rtc found on some Motorola phones
1912 and tablets such as Droid 4.
1914 config RTC_DRV_RTD119X
1915 bool "Realtek RTD129x RTC"
1916 depends on ARCH_REALTEK || COMPILE_TEST
1917 default ARCH_REALTEK
1919 If you say yes here, you get support for the RTD1295 SoC
1922 config RTC_DRV_ASPEED
1923 tristate "ASPEED RTC"
1925 depends on ARCH_ASPEED || COMPILE_TEST
1927 If you say yes here you get support for the ASPEED BMC SoC real time
1930 This driver can also be built as a module, if so, the module
1931 will be called "rtc-aspeed".
1933 config RTC_DRV_TI_K3
1934 tristate "TI K3 RTC"
1935 depends on ARCH_K3 || COMPILE_TEST
1938 If you say yes here you get support for the Texas Instruments's
1939 Real Time Clock for K3 architecture.
1941 This driver can also be built as a module, if so, the module
1942 will be called "rtc-ti-k3".
1944 comment "HID Sensor RTC drivers"
1946 config RTC_DRV_HID_SENSOR_TIME
1947 tristate "HID Sensor Time"
1949 depends on HID_SENSOR_HUB && IIO
1950 select HID_SENSOR_IIO_COMMON
1952 Say yes here to build support for the HID Sensors of type Time.
1953 This drivers makes such sensors available as RTCs.
1955 If this driver is compiled as a module, it will be named
1956 rtc-hid-sensor-time.
1958 config RTC_DRV_GOLDFISH
1959 tristate "Goldfish Real Time Clock"
1960 depends on HAS_IOMEM
1962 Say yes to enable RTC driver for the Goldfish based virtual platform.
1964 Goldfish is a code name for the virtual platform developed by Google
1965 for Android emulation.
1967 config RTC_DRV_WILCO_EC
1968 tristate "Wilco EC RTC"
1972 If you say yes here, you get read/write support for the Real Time
1973 Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook)
1975 This can also be built as a module. If so, the module will
1976 be named "rtc_wilco_ec".
1978 config RTC_DRV_MSC313
1979 tristate "MStar MSC313 RTC"
1980 depends on ARCH_MSTARV7 || COMPILE_TEST
1982 If you say yes here you get support for the Mstar MSC313e On-Chip
1985 This driver can also be built as a module, if so, the module
1986 will be called "rtc-msc313".
1988 config RTC_DRV_POLARFIRE_SOC
1989 tristate "Microchip PolarFire SoC built-in RTC"
1990 depends on ARCH_MICROCHIP_POLARFIRE
1992 If you say yes here you will get support for the
1993 built-in RTC on Polarfire SoC.
1995 This driver can also be built as a module, if so, the module
1996 will be called "rtc-mpfs".