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 || 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.
387 tristate "Rockchip RK805/RK808/RK809/RK817/RK818 RTC"
390 If you say yes here you will get support for the
391 RTC of RK805, RK809 and RK817, RK808 and RK818 PMIC.
393 This driver can also be built as a module. If so, the module
394 will be called rk808-rtc.
396 config RTC_DRV_RS5C372
397 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
399 If you say yes here you get support for the
400 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
402 This driver can also be built as a module. If so, the module
403 will be called rtc-rs5c372.
405 config RTC_DRV_ISL1208
406 tristate "Intersil ISL1208"
408 If you say yes here you get support for the
409 Intersil ISL1208 RTC chip.
411 This driver can also be built as a module. If so, the module
412 will be called rtc-isl1208.
414 config RTC_DRV_ISL12022
415 tristate "Intersil ISL12022"
417 If you say yes here you get support for the
418 Intersil ISL12022 RTC chip.
420 This driver can also be built as a module. If so, the module
421 will be called rtc-isl12022.
423 config RTC_DRV_ISL12026
424 tristate "Intersil ISL12026"
425 depends on OF || COMPILE_TEST
427 If you say yes here you get support for the
428 Intersil ISL12026 RTC chip.
430 This driver can also be built as a module. If so, the module
431 will be called rtc-isl12026.
434 tristate "Xicor/Intersil X1205"
436 If you say yes here you get support for the
437 Xicor/Intersil X1205 RTC chip.
439 This driver can also be built as a module. If so, the module
440 will be called rtc-x1205.
442 config RTC_DRV_PCF8523
443 tristate "NXP PCF8523"
445 If you say yes here you get support for the NXP PCF8523 RTC
448 This driver can also be built as a module. If so, the module
449 will be called rtc-pcf8523.
451 config RTC_DRV_PCF85063
452 tristate "NXP PCF85063"
455 If you say yes here you get support for the PCF85063 RTC chip
457 This driver can also be built as a module. If so, the module
458 will be called rtc-pcf85063.
460 config RTC_DRV_PCF85363
461 tristate "NXP PCF85363"
464 If you say yes here you get support for the PCF85363 RTC chip.
466 This driver can also be built as a module. If so, the module
467 will be called rtc-pcf85363.
469 The nvmem interface will be named pcf85363-#, where # is the
470 zero-based instance number.
472 config RTC_DRV_PCF8563
473 tristate "Philips PCF8563/Epson RTC8564"
475 If you say yes here you get support for the
476 Philips PCF8563 RTC chip. The Epson RTC8564
479 This driver can also be built as a module. If so, the module
480 will be called rtc-pcf8563.
482 config RTC_DRV_PCF8583
483 tristate "Philips PCF8583"
485 If you say yes here you get support for the Philips PCF8583
486 RTC chip found on Acorn RiscPCs. This driver supports the
487 platform specific method of retrieving the current year from
488 the RTC's SRAM. It will work on other platforms with the same
489 chip, but the year will probably have to be tweaked.
491 This driver can also be built as a module. If so, the module
492 will be called rtc-pcf8583.
494 config RTC_DRV_M41T80
495 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
497 If you say Y here you will get support for the ST M41T60
498 and M41T80 RTC chips series. Currently, the following chips are
499 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
500 M41ST85, M41ST87, and MicroCrystal RV4162.
502 This driver can also be built as a module. If so, the module
503 will be called rtc-m41t80.
505 config RTC_DRV_M41T80_WDT
506 bool "ST M41T65/M41T80 series RTC watchdog timer"
507 depends on RTC_DRV_M41T80
509 If you say Y here you will get support for the
510 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
512 config RTC_DRV_BD70528
513 tristate "ROHM BD71815 and BD71828 PMIC RTC"
514 depends on MFD_ROHM_BD71828
516 If you say Y here you will get support for the RTC
517 block on ROHM BD71815 and BD71828 Power Management IC.
519 This driver can also be built as a module. If so, the module
520 will be called rtc-bd70528.
523 tristate "TI BQ32000"
525 If you say Y here you will get support for the TI
526 BQ32000 I2C RTC chip.
528 This driver can also be built as a module. If so, the module
529 will be called rtc-bq32k.
531 config RTC_DRV_DM355EVM
532 tristate "TI DaVinci DM355 EVM RTC"
533 depends on MFD_DM355EVM_MSP
535 Supports the RTC firmware in the MSP430 on the DM355 EVM.
537 config RTC_DRV_TWL92330
538 bool "TI TWL92330/Menelaus"
541 If you say yes here you get support for the RTC on the
542 TWL92330 "Menelaus" power management chip, used with OMAP2
543 platforms. The support is integrated with the rest of
544 the Menelaus driver; it's not separate module.
546 config RTC_DRV_TWL4030
547 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
548 depends on TWL4030_CORE
551 If you say yes here you get support for the RTC on the
552 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
554 This driver can also be built as a module. If so, the module
555 will be called rtc-twl.
557 config RTC_DRV_PALMAS
558 tristate "TI Palmas RTC driver"
559 depends on MFD_PALMAS
561 If you say yes here you get support for the RTC of TI PALMA series PMIC
564 This driver can also be built as a module. If so, the module
565 will be called rtc-palma.
567 config RTC_DRV_TPS6586X
568 tristate "TI TPS6586X RTC driver"
569 depends on MFD_TPS6586X
571 TI Power Management IC TPS6586X supports RTC functionality
572 along with alarm. This driver supports the RTC driver for
573 the TPS6586X RTC module.
575 config RTC_DRV_TPS65910
576 tristate "TI TPS65910 RTC driver"
577 depends on MFD_TPS65910
579 If you say yes here you get support for the RTC on the
582 This driver can also be built as a module. If so, the module
583 will be called rtc-tps65910.
585 config RTC_DRV_TPS80031
586 tristate "TI TPS80031/TPS80032 RTC driver"
587 depends on MFD_TPS80031
589 TI Power Management IC TPS80031 supports RTC functionality
590 along with alarm. This driver supports the RTC driver for
591 the TPS80031 RTC module.
593 config RTC_DRV_RC5T583
594 tristate "RICOH 5T583 RTC driver"
595 depends on MFD_RC5T583
597 If you say yes here you get support for the RTC on the
600 This driver can also be built as a module. If so, the module
601 will be called rtc-rc5t583.
603 config RTC_DRV_RC5T619
604 tristate "RICOH RC5T619 RTC driver"
605 depends on MFD_RN5T618
607 If you say yes here you get support for the RTC on the
610 This driver can also be built as a module. If so, the module
611 will be called rtc-rc5t619.
613 config RTC_DRV_S35390A
614 tristate "Seiko Instruments S-35390A"
617 If you say yes here you will get support for the Seiko
618 Instruments S-35390A.
620 This driver can also be built as a module. If so the module
621 will be called rtc-s35390a.
623 config RTC_DRV_FM3130
624 tristate "Ramtron FM3130"
626 If you say Y here you will get support for the
627 Ramtron FM3130 RTC chips.
628 Ramtron FM3130 is a chip with two separate devices inside,
629 RTC clock and FRAM. This driver provides only RTC functionality.
631 This driver can also be built as a module. If so the module
632 will be called rtc-fm3130.
634 config RTC_DRV_RX8010
635 tristate "Epson RX8010SJ"
637 If you say yes here you get support for the Epson RX8010SJ RTC
640 This driver can also be built as a module. If so, the module
641 will be called rtc-rx8010.
643 config RTC_DRV_RX8581
644 tristate "Epson RX-8571/RX-8581"
647 If you say yes here you will get support for the Epson RX-8571/
650 This driver can also be built as a module. If so the module
651 will be called rtc-rx8581.
653 config RTC_DRV_RX8025
654 tristate "Epson RX-8025SA/NB"
656 If you say yes here you get support for the Epson
657 RX-8025SA/NB RTC chips.
659 This driver can also be built as a module. If so, the module
660 will be called rtc-rx8025.
662 config RTC_DRV_EM3027
663 tristate "EM Microelectronic EM3027"
665 If you say yes here you get support for the EM
666 Microelectronic EM3027 RTC chips.
668 This driver can also be built as a module. If so, the module
669 will be called rtc-em3027.
671 config RTC_DRV_RV3028
672 tristate "Micro Crystal RV3028"
675 If you say yes here you get support for the Micro Crystal
678 This driver can also be built as a module. If so, the module
679 will be called rtc-rv3028.
681 config RTC_DRV_RV3032
682 tristate "Micro Crystal RV3032"
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-rv3032.
691 config RTC_DRV_RV8803
692 tristate "Micro Crystal RV8803, Epson RX8900"
694 If you say yes here you get support for the Micro Crystal RV8803 and
695 Epson RX8900 RTC chips.
697 This driver can also be built as a module. If so, the module
698 will be called rtc-rv8803.
701 tristate "Samsung S2M/S5M series"
702 depends on MFD_SEC_CORE || COMPILE_TEST
706 If you say yes here you will get support for the
707 RTC of Samsung S2MPS14 and S5M PMIC series.
709 This driver can also be built as a module. If so, the module
710 will be called rtc-s5m.
712 config RTC_DRV_SD3078
713 tristate "ZXW Shenzhen whwave SD3078"
716 If you say yes here you get support for the ZXW Shenzhen whwave
719 This driver can also be built as a module. If so, the module
720 will be called rtc-sd3078
724 comment "SPI RTC drivers"
728 config RTC_DRV_M41T93
731 If you say yes here you will get support for the
732 ST M41T93 SPI RTC chip.
734 This driver can also be built as a module. If so, the module
735 will be called rtc-m41t93.
737 config RTC_DRV_M41T94
740 If you say yes here you will get support for the
741 ST M41T94 SPI RTC chip.
743 This driver can also be built as a module. If so, the module
744 will be called rtc-m41t94.
746 config RTC_DRV_DS1302
747 tristate "Dallas/Maxim DS1302"
750 If you say yes here you get support for the Dallas DS1302 RTC chips.
752 This driver can also be built as a module. If so, the module
753 will be called rtc-ds1302.
755 config RTC_DRV_DS1305
756 tristate "Dallas/Maxim DS1305/DS1306"
758 Select this driver to get support for the Dallas/Maxim DS1305
759 and DS1306 real time clock chips. These support a trickle
760 charger, alarms, and NVRAM in addition to the clock.
762 This driver can also be built as a module. If so, the module
763 will be called rtc-ds1305.
765 config RTC_DRV_DS1343
767 tristate "Dallas/Maxim DS1343/DS1344"
769 If you say yes here you get support for the
770 Dallas/Maxim DS1343 and DS1344 real time clock chips.
771 Support for trickle charger, alarm is provided.
773 This driver can also be built as a module. If so, the module
774 will be called rtc-ds1343.
776 config RTC_DRV_DS1347
778 tristate "Dallas/Maxim DS1347"
780 If you say yes here you get support for the
781 Dallas/Maxim DS1347 chips.
783 This driver only supports the RTC feature, and not other chip
784 features such as alarms.
786 This driver can also be built as a module. If so, the module
787 will be called rtc-ds1347.
789 config RTC_DRV_DS1390
790 tristate "Dallas/Maxim DS1390/93/94"
792 If you say yes here you get support for the
793 Dallas/Maxim DS1390/93/94 chips.
795 This driver supports the RTC feature and trickle charging but not
796 other chip features such as alarms.
798 This driver can also be built as a module. If so, the module
799 will be called rtc-ds1390.
801 config RTC_DRV_MAX6916
802 tristate "Maxim MAX6916"
804 If you say yes here you will get support for the
805 Maxim MAX6916 SPI RTC chip.
807 This driver only supports the RTC feature, and not other chip
808 features such as alarms.
810 This driver can also be built as a module. If so, the module
811 will be called rtc-max6916.
814 tristate "Epson RTC-9701JE"
816 If you say yes here you will get support for the
817 Epson RTC-9701JE SPI RTC chip.
819 This driver can also be built as a module. If so, the module
820 will be called rtc-r9701.
822 config RTC_DRV_RX4581
823 tristate "Epson RX-4581"
825 If you say yes here you will get support for the Epson RX-4581.
827 This driver can also be built as a module. If so the module
828 will be called rtc-rx4581.
830 config RTC_DRV_RS5C348
831 tristate "Ricoh RS5C348A/B"
833 If you say yes here you get support for the
834 Ricoh RS5C348A and RS5C348B RTC chips.
836 This driver can also be built as a module. If so, the module
837 will be called rtc-rs5c348.
839 config RTC_DRV_MAX6902
840 tristate "Maxim MAX6902"
842 If you say yes here you will get support for the
843 Maxim MAX6902 SPI RTC chip.
845 This driver can also be built as a module. If so, the module
846 will be called rtc-max6902.
848 config RTC_DRV_PCF2123
849 tristate "NXP PCF2123"
852 If you say yes here you get support for the NXP PCF2123
855 This driver can also be built as a module. If so, the module
856 will be called rtc-pcf2123.
858 config RTC_DRV_MCP795
859 tristate "Microchip MCP795"
861 If you say yes here you will get support for the Microchip MCP795.
863 This driver can also be built as a module. If so the module
864 will be called rtc-mcp795.
869 # Helper to resolve issues with configs that have SPI enabled but I2C
870 # modular. See SND_SOC_I2C_AND_SPI for more information
872 config RTC_I2C_AND_SPI
876 default y if SPI_MASTER=y
878 comment "SPI and I2C RTC drivers"
880 config RTC_DRV_DS3232
881 tristate "Dallas/Maxim DS3232/DS3234"
882 depends on RTC_I2C_AND_SPI
883 select REGMAP_I2C if I2C
884 select REGMAP_SPI if SPI_MASTER
886 If you say yes here you get support for Dallas Semiconductor
887 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
888 with the device, the alarm functionality is supported.
890 This driver can also be built as a module. If so, the module
891 will be called rtc-ds3232.
893 config RTC_DRV_DS3232_HWMON
894 bool "HWMON support for Dallas/Maxim DS3232/DS3234"
895 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
898 Say Y here if you want to expose temperature sensor data on
901 config RTC_DRV_PCF2127
902 tristate "NXP PCF2127"
903 depends on RTC_I2C_AND_SPI
904 select REGMAP_I2C if I2C
905 select REGMAP_SPI if SPI_MASTER
906 select WATCHDOG_CORE if WATCHDOG
908 If you say yes here you get support for the NXP PCF2127/29 RTC
909 chips with integrated quartz crystal for industrial applications.
910 Both chips also have watchdog timer and tamper switch detection
913 PCF2127 has an additional feature of 512 bytes battery backed
914 memory that's accessible using nvmem interface.
916 This driver can also be built as a module. If so, the module
917 will be called rtc-pcf2127.
919 config RTC_DRV_RV3029C2
920 tristate "Micro Crystal RV3029/3049"
921 depends on RTC_I2C_AND_SPI
922 select REGMAP_I2C if I2C
923 select REGMAP_SPI if SPI_MASTER
925 If you say yes here you get support for the Micro Crystal
926 RV3029 and RV3049 RTC chips.
928 This driver can also be built as a module. If so, the module
929 will be called rtc-rv3029c2.
931 config RTC_DRV_RV3029_HWMON
932 bool "HWMON support for RV3029/3049"
933 depends on RTC_DRV_RV3029C2 && HWMON
934 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
937 Say Y here if you want to expose temperature sensor data on
940 config RTC_DRV_RX6110
941 tristate "Epson RX-6110"
942 depends on RTC_I2C_AND_SPI
943 select REGMAP_SPI if SPI_MASTER
944 select REGMAP_I2C if I2C
946 If you say yes here you will get support for the Epson RX-6110.
948 This driver can also be built as a module. If so the module
949 will be called rtc-rx6110.
951 comment "Platform RTC drivers"
953 # this 'CMOS' RTC driver is arch dependent because it requires
954 # <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
955 # global rtc_lock ... it's not yet just another platform_device.
958 tristate "PC-style 'CMOS'"
959 depends on X86 || ARM || PPC || MIPS || SPARC64
961 select RTC_MC146818_LIB
963 Say "yes" here to get direct support for the real time clock
964 found in every PC or ACPI-based system, and some other boards.
965 Specifically the original MC146818, compatibles like those in
966 PC south bridges, the DS12887 or M48T86, some multifunction
967 or LPC bus chips, and so on.
969 Your system will need to define the platform device used by
970 this driver, otherwise it won't be accessible. This means
971 you can safely enable this driver if you don't know whether
972 or not your board has this kind of hardware.
974 This driver can also be built as a module. If so, the module
975 will be called rtc-cmos.
978 bool "Alpha PC-style CMOS"
980 select RTC_MC146818_LIB
983 Direct support for the real-time clock found on every Alpha
984 system, specifically MC146818 compatibles. If in doubt, say Y.
986 config RTC_DRV_DS1216
987 tristate "Dallas DS1216"
990 If you say yes here you get support for the Dallas DS1216 RTC chips.
992 config RTC_DRV_DS1286
993 tristate "Dallas DS1286"
996 If you say yes here you get support for the Dallas DS1286 RTC chips.
998 config RTC_DRV_DS1511
999 tristate "Dallas DS1511"
1000 depends on HAS_IOMEM
1002 If you say yes here you get support for the
1003 Dallas DS1511 timekeeping/watchdog chip.
1005 This driver can also be built as a module. If so, the module
1006 will be called rtc-ds1511.
1008 config RTC_DRV_DS1553
1009 tristate "Maxim/Dallas DS1553"
1010 depends on HAS_IOMEM
1012 If you say yes here you get support for the
1013 Maxim/Dallas DS1553 timekeeping chip.
1015 This driver can also be built as a module. If so, the module
1016 will be called rtc-ds1553.
1018 config RTC_DRV_DS1685_FAMILY
1019 tristate "Dallas/Maxim DS1685 Family"
1020 depends on HAS_IOMEM
1022 If you say yes here you get support for the Dallas/Maxim DS1685
1023 family of real time chips. This family includes the DS1685/DS1687,
1024 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
1025 DS17885/DS17887 chips.
1027 This driver can also be built as a module. If so, the module
1028 will be called rtc-ds1685.
1032 depends on RTC_DRV_DS1685_FAMILY
1033 default RTC_DRV_DS1685
1035 config RTC_DRV_DS1685
1036 bool "DS1685/DS1687"
1038 This enables support for the Dallas/Maxim DS1685/DS1687 real time
1041 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
1042 systems, as well as EPPC-405-UC modules by electronic system design
1045 config RTC_DRV_DS1689
1046 bool "DS1689/DS1693"
1048 This enables support for the Dallas/Maxim DS1689/DS1693 real time
1051 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
1052 which supports a few minor features such as Vcc, Vbat, and Power
1053 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
1055 It also works for the even older DS1688/DS1691 RTC chips, which are
1056 virtually the same and carry the same model number. Both chips
1057 have 114 bytes of user NVRAM.
1059 config RTC_DRV_DS17285
1060 bool "DS17285/DS17287"
1062 This enables support for the Dallas/Maxim DS17285/DS17287 real time
1065 This chip features 2kb of extended NV-SRAM. It may possibly be
1066 found in some SGI O2 systems (rare).
1068 config RTC_DRV_DS17485
1069 bool "DS17485/DS17487"
1071 This enables support for the Dallas/Maxim DS17485/DS17487 real time
1074 This chip features 4kb of extended NV-SRAM.
1076 config RTC_DRV_DS17885
1077 bool "DS17885/DS17887"
1079 This enables support for the Dallas/Maxim DS17885/DS17887 real time
1082 This chip features 8kb of extended NV-SRAM.
1086 config RTC_DRV_DS1742
1087 tristate "Maxim/Dallas DS1742/1743"
1088 depends on HAS_IOMEM
1090 If you say yes here you get support for the
1091 Maxim/Dallas DS1742/1743 timekeeping chip.
1093 This driver can also be built as a module. If so, the module
1094 will be called rtc-ds1742.
1096 config RTC_DRV_DS2404
1097 tristate "Maxim/Dallas DS2404"
1099 If you say yes here you get support for the
1100 Dallas DS2404 RTC chip.
1102 This driver can also be built as a module. If so, the module
1103 will be called rtc-ds2404.
1105 config RTC_DRV_DA9052
1106 tristate "Dialog DA9052/DA9053 RTC"
1107 depends on PMIC_DA9052
1109 Say y here to support the RTC driver for Dialog Semiconductor
1110 DA9052-BC and DA9053-AA/Bx PMICs.
1112 config RTC_DRV_DA9055
1113 tristate "Dialog Semiconductor DA9055 RTC"
1114 depends on MFD_DA9055
1116 If you say yes here you will get support for the
1117 RTC of the Dialog DA9055 PMIC.
1119 This driver can also be built as a module. If so, the module
1120 will be called rtc-da9055
1122 config RTC_DRV_DA9063
1123 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1124 depends on MFD_DA9063 || MFD_DA9062
1126 If you say yes here you will get support for the RTC subsystem
1127 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1129 This driver can also be built as a module. If so, the module
1130 will be called "rtc-da9063".
1134 depends on EFI && !X86
1136 If you say yes here you will get support for the EFI
1139 This driver can also be built as a module. If so, the module
1140 will be called rtc-efi.
1142 config RTC_DRV_STK17TA8
1143 tristate "Simtek STK17TA8"
1144 depends on HAS_IOMEM
1146 If you say yes here you get support for the
1147 Simtek STK17TA8 timekeeping chip.
1149 This driver can also be built as a module. If so, the module
1150 will be called rtc-stk17ta8.
1152 config RTC_DRV_M48T86
1153 tristate "ST M48T86/Dallas DS12887"
1154 depends on HAS_IOMEM
1156 If you say Y here you will get support for the
1157 ST M48T86 and Dallas DS12887 RTC chips.
1159 This driver can also be built as a module. If so, the module
1160 will be called rtc-m48t86.
1162 config RTC_DRV_M48T35
1163 tristate "ST M48T35"
1164 depends on HAS_IOMEM
1166 If you say Y here you will get support for the
1169 This driver can also be built as a module, if so, the module
1170 will be called "rtc-m48t35".
1172 config RTC_DRV_M48T59
1173 tristate "ST M48T59/M48T08/M48T02"
1174 depends on HAS_IOMEM
1176 If you say Y here you will get support for the
1177 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1179 These chips are usually found in Sun SPARC and UltraSPARC
1182 This driver can also be built as a module, if so, the module
1183 will be called "rtc-m48t59".
1185 config RTC_DRV_MSM6242
1186 tristate "Oki MSM6242"
1187 depends on HAS_IOMEM
1189 If you say yes here you get support for the Oki MSM6242
1190 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1192 This driver can also be built as a module. If so, the module
1193 will be called rtc-msm6242.
1195 config RTC_DRV_BQ4802
1196 tristate "TI BQ4802"
1197 depends on HAS_IOMEM
1199 If you say Y here you will get support for the TI
1202 This driver can also be built as a module. If so, the module
1203 will be called rtc-bq4802.
1205 config RTC_DRV_RP5C01
1206 tristate "Ricoh RP5C01"
1207 depends on HAS_IOMEM
1209 If you say yes here you get support for the Ricoh RP5C01
1210 timekeeping chip. It is used in some Amiga models (e.g. A3000
1213 This driver can also be built as a module. If so, the module
1214 will be called rtc-rp5c01.
1216 config RTC_DRV_V3020
1217 tristate "EM Microelectronic V3020"
1219 If you say yes here you will get support for the
1220 EM Microelectronic v3020 RTC chip.
1222 This driver can also be built as a module. If so, the module
1223 will be called rtc-v3020.
1225 config RTC_DRV_WM831X
1226 tristate "Wolfson Microelectronics WM831x RTC"
1227 depends on MFD_WM831X
1229 If you say yes here you will get support for the RTC subsystem
1230 of the Wolfson Microelectronics WM831X series PMICs.
1232 This driver can also be built as a module. If so, the module
1233 will be called "rtc-wm831x".
1235 config RTC_DRV_WM8350
1236 tristate "Wolfson Microelectronics WM8350 RTC"
1237 depends on MFD_WM8350
1239 If you say yes here you will get support for the RTC subsystem
1240 of the Wolfson Microelectronics WM8350.
1242 This driver can also be built as a module. If so, the module
1243 will be called "rtc-wm8350".
1245 config RTC_DRV_SC27XX
1246 tristate "Spreadtrum SC27xx RTC"
1247 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1249 If you say Y here you will get support for the RTC subsystem
1250 of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs
1251 includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips.
1253 This driver can also be built as a module. If so, the module
1254 will be called rtc-sc27xx.
1256 config RTC_DRV_SPEAR
1257 tristate "SPEAR ST RTC"
1258 depends on PLAT_SPEAR || COMPILE_TEST
1261 If you say Y here you will get support for the RTC found on
1264 config RTC_DRV_PCF50633
1265 depends on MFD_PCF50633
1266 tristate "NXP PCF50633 RTC"
1268 If you say yes here you get support for the RTC subsystem of the
1269 NXP PCF50633 used in embedded systems.
1271 config RTC_DRV_AB8500
1272 tristate "ST-Ericsson AB8500 RTC"
1273 depends on AB8500_CORE
1275 select RTC_INTF_DEV_UIE_EMUL
1277 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1278 support. This chip contains a battery- and capacitor-backed RTC.
1281 tristate "IBM OPAL RTC driver"
1282 depends on PPC_POWERNV
1285 If you say yes here you get support for the PowerNV platform RTC
1286 driver based on OPAL interfaces.
1288 This driver can also be built as a module. If so, the module
1289 will be called rtc-opal.
1291 config RTC_DRV_ZYNQMP
1292 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1293 depends on OF && HAS_IOMEM
1295 If you say yes here you get support for the RTC controller found on
1296 Xilinx Zynq Ultrascale+ MPSoC.
1298 config RTC_DRV_CROS_EC
1299 tristate "Chrome OS EC RTC driver"
1302 If you say yes here you will get support for the
1303 Chrome OS Embedded Controller's RTC.
1305 This driver can also be built as a module. If so, the module
1306 will be called rtc-cros-ec.
1308 config RTC_DRV_NTXEC
1309 tristate "Netronix embedded controller RTC"
1310 depends on MFD_NTXEC
1312 Say yes here if you want to support the RTC functionality of the
1313 embedded controller found in certain e-book readers designed by the
1314 original design manufacturer Netronix.
1316 comment "on-CPU RTC drivers"
1318 config RTC_DRV_ASM9260
1319 tristate "Alphascale asm9260 RTC"
1320 depends on MACH_ASM9260 || COMPILE_TEST
1322 If you say yes here you get support for the RTC on the
1323 Alphascale asm9260 SoC.
1325 This driver can also be built as a module. If so, the module
1326 will be called rtc-asm9260.
1328 config RTC_DRV_DAVINCI
1329 tristate "TI DaVinci RTC"
1330 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1332 If you say yes here you get support for the RTC on the
1333 DaVinci platforms (DM365).
1335 This driver can also be built as a module. If so, the module
1336 will be called rtc-davinci.
1338 config RTC_DRV_DIGICOLOR
1339 tristate "Conexant Digicolor RTC"
1340 depends on ARCH_DIGICOLOR || COMPILE_TEST
1342 If you say yes here you get support for the RTC on Conexant
1343 Digicolor platforms. This currently includes the CX92755 SoC.
1345 This driver can also be built as a module. If so, the module
1346 will be called rtc-digicolor.
1348 config RTC_DRV_IMXDI
1349 tristate "Freescale IMX DryIce Real Time Clock"
1353 Support for Freescale IMX DryIce RTC
1355 This driver can also be built as a module, if so, the module
1356 will be called "rtc-imxdi".
1358 config RTC_DRV_FSL_FTM_ALARM
1359 tristate "Freescale FlexTimer alarm timer"
1360 depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST
1362 For the FlexTimer in LS1012A, LS1021A, LS1028A, LS1043A, LS1046A,
1363 LS1088A, LS208xA, we can use FTM as the wakeup source.
1365 Say y here to enable FTM alarm support. The FTM alarm provides
1366 alarm functions for wakeup system from deep sleep.
1368 This driver can also be built as a module, if so, the module
1369 will be called "rtc-fsl-ftm-alarm".
1371 config RTC_DRV_MESON
1372 tristate "Amlogic Meson RTC"
1373 depends on (ARM && ARCH_MESON) || COMPILE_TEST
1376 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1379 This driver can also be built as a module, if so, the module
1380 will be called "rtc-meson".
1382 config RTC_DRV_MESON_VRTC
1383 tristate "Amlogic Meson Virtual RTC"
1384 depends on ARCH_MESON || COMPILE_TEST
1385 default m if ARCH_MESON
1387 If you say yes here you will get support for the
1388 Virtual RTC of Amlogic SoCs.
1390 This driver can also be built as a module. If so, the module
1391 will be called rtc-meson-vrtc.
1394 tristate "TI OMAP Real Time Clock"
1395 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1398 select GENERIC_PINCONF
1400 Say "yes" here to support the on chip real time clock
1401 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1403 This driver can also be built as a module, if so, module
1404 will be called rtc-omap.
1409 This will include RTC support for Samsung SoCs. If
1410 you want to include RTC support for any machine, kindly
1411 select this in the respective mach-XXXX/Kconfig file.
1414 tristate "Samsung S3C series SoC RTC"
1415 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1417 RTC (Realtime Clock) driver for the clock inbuilt into the
1418 Samsung S3C24XX series of SoCs. This can provide periodic
1419 interrupt rates from 1Hz to 64Hz for user programs, and
1422 The driver currently supports the common features on all the
1423 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1426 This driver can also be build as a module. If so, the module
1427 will be called rtc-s3c.
1429 config RTC_DRV_EP93XX
1430 tristate "Cirrus Logic EP93XX"
1431 depends on ARCH_EP93XX || COMPILE_TEST
1433 If you say yes here you get support for the
1434 RTC embedded in the Cirrus Logic EP93XX processors.
1436 This driver can also be built as a module. If so, the module
1437 will be called rtc-ep93xx.
1439 config RTC_DRV_SA1100
1440 tristate "SA11x0/PXA2xx/PXA910"
1441 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1443 If you say Y here you will get access to the real time clock
1444 built into your SA11x0 or PXA2xx CPU.
1446 To compile this driver as a module, choose M here: the
1447 module will be called rtc-sa1100.
1450 tristate "SuperH On-Chip RTC"
1451 depends on SUPERH || ARCH_RENESAS
1453 Say Y here to enable support for the on-chip RTC found in
1454 most SuperH processors. This RTC is also found in RZ/A SoCs.
1456 To compile this driver as a module, choose M here: the
1457 module will be called rtc-sh.
1459 config RTC_DRV_VR41XX
1460 tristate "NEC VR41XX"
1461 depends on CPU_VR41XX || COMPILE_TEST
1463 If you say Y here you will get access to the real time clock
1464 built into your NEC VR41XX CPU.
1466 To compile this driver as a module, choose M here: the
1467 module will be called rtc-vr41xx.
1469 config RTC_DRV_PL030
1470 tristate "ARM AMBA PL030 RTC"
1473 If you say Y here you will get access to ARM AMBA
1474 PrimeCell PL030 RTC found on certain ARM SOCs.
1476 To compile this driver as a module, choose M here: the
1477 module will be called rtc-pl030.
1479 config RTC_DRV_PL031
1480 tristate "ARM AMBA PL031 RTC"
1483 If you say Y here you will get access to ARM AMBA
1484 PrimeCell PL031 RTC found on certain ARM SOCs.
1486 To compile this driver as a module, choose M here: the
1487 module will be called rtc-pl031.
1489 config RTC_DRV_AT91RM9200
1490 tristate "AT91RM9200 or some AT91SAM9 RTC"
1491 depends on ARCH_AT91 || COMPILE_TEST
1494 Driver for the internal RTC (Realtime Clock) module found on
1495 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1496 this is powered by the backup power supply.
1498 config RTC_DRV_AT91SAM9
1499 tristate "AT91SAM9 RTT as RTC"
1500 depends on ARCH_AT91 || COMPILE_TEST
1501 depends on OF && HAS_IOMEM
1504 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1505 can be used as an RTC thanks to the backup power supply (e.g. a
1506 small coin cell battery) which keeps this block and the GPBR
1507 (General Purpose Backup Registers) block powered when the device
1509 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1510 probably want to use the real RTC block instead of the "RTT as an
1513 config RTC_DRV_AU1XXX
1514 tristate "Au1xxx Counter0 RTC support"
1515 depends on MIPS_ALCHEMY
1517 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1518 counter) to be used as a RTC.
1520 This driver can also be built as a module. If so, the module
1521 will be called rtc-au1xxx.
1523 config RTC_DRV_RS5C313
1524 tristate "Ricoh RS5C313"
1525 depends on SH_LANDISK
1527 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1529 config RTC_DRV_GENERIC
1530 tristate "Generic RTC support"
1531 # Please consider writing a new RTC driver instead of using the generic
1533 depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST
1535 Say Y or M here to enable RTC support on systems using the generic
1536 RTC abstraction. If you do not know what you are doing, you should
1540 tristate "PXA27x/PXA3xx"
1542 select RTC_DRV_SA1100
1544 If you say Y here you will get access to the real time clock
1545 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1546 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1548 This RTC driver uses PXA RTC registers available since pxa27x
1549 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1551 config RTC_DRV_VT8500
1552 tristate "VIA/WonderMedia 85xx SoC RTC"
1553 depends on ARCH_VT8500 || COMPILE_TEST
1555 If you say Y here you will get access to the real time clock
1556 built into your VIA VT8500 SoC or its relatives.
1559 config RTC_DRV_SUN4V
1560 bool "SUN4V Hypervisor RTC"
1563 If you say Y here you will get support for the Hypervisor
1564 based RTC on SUN4V systems.
1566 config RTC_DRV_SUN6I
1567 bool "Allwinner A31 RTC"
1568 default MACH_SUN6I || MACH_SUN8I
1569 depends on COMMON_CLK
1570 depends on ARCH_SUNXI || COMPILE_TEST
1572 If you say Y here you will get support for the RTC found in
1573 some Allwinner SoCs like the A31 or the A64.
1575 config RTC_DRV_SUNXI
1576 tristate "Allwinner sun4i/sun7i RTC"
1577 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1579 If you say Y here you will get support for the RTC found on
1582 config RTC_DRV_STARFIRE
1586 If you say Y here you will get support for the RTC found on
1590 tristate "Marvell SoC RTC"
1591 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1593 If you say yes here you will get support for the in-chip RTC
1594 that can be found in some of Marvell's SoC devices, such as
1595 the Kirkwood 88F6281 and 88F6192.
1597 This driver can also be built as a module. If so, the module
1598 will be called rtc-mv.
1600 config RTC_DRV_ARMADA38X
1601 tristate "Armada 38x Marvell SoC RTC"
1602 depends on ARCH_MVEBU || COMPILE_TEST
1605 If you say yes here you will get support for the in-chip RTC
1606 that can be found in the Armada 38x Marvell's SoC device
1608 This driver can also be built as a module. If so, the module
1609 will be called armada38x-rtc.
1611 config RTC_DRV_CADENCE
1612 tristate "Cadence RTC driver"
1613 depends on OF && HAS_IOMEM
1615 If you say Y here you will get access to Cadence RTC IP
1616 found on certain SOCs.
1618 To compile this driver as a module, choose M here: the
1619 module will be called rtc-cadence.
1621 config RTC_DRV_FTRTC010
1622 tristate "Faraday Technology FTRTC010 RTC"
1623 depends on HAS_IOMEM
1626 If you say Y here you will get support for the
1627 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1629 This driver can also be built as a module. If so, the module
1630 will be called rtc-ftrtc010.
1636 If you say yes here you will get support for the RTC on PS3.
1638 This driver can also be built as a module. If so, the module
1639 will be called rtc-ps3.
1642 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1643 depends on ARCH_MXS || COMPILE_TEST
1646 If you say yes here you will get support for the onboard
1647 STMP3xxx/i.MX23/i.MX28 RTC.
1649 This driver can also be built as a module. If so, the module
1650 will be called rtc-stmp3xxx.
1656 If you say Y here you will get support for the RTC found on
1657 the PCAP2 ASIC used on some Motorola phones.
1659 config RTC_DRV_MC13XXX
1660 depends on MFD_MC13XXX
1661 tristate "Freescale MC13xxx RTC"
1663 This enables support for the RTCs found on Freescale's PMICs
1664 MC13783 and MC13892.
1666 config RTC_DRV_MPC5121
1667 tristate "Freescale MPC5121 built-in RTC"
1668 depends on PPC_MPC512x || PPC_MPC52xx
1670 If you say yes here you will get support for the
1671 built-in RTC on MPC5121 or on MPC5200.
1673 This driver can also be built as a module. If so, the module
1674 will be called rtc-mpc5121.
1676 config RTC_DRV_JZ4740
1677 tristate "Ingenic JZ4740 SoC"
1678 depends on MIPS || COMPILE_TEST
1681 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1684 This driver can also be built as a module. If so, the module
1685 will be called rtc-jz4740.
1687 config RTC_DRV_LPC24XX
1688 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1689 depends on ARCH_LPC18XX || COMPILE_TEST
1690 depends on OF && HAS_IOMEM
1692 This enables support for the NXP RTC found which can be found on
1693 NXP LPC178x/18xx/408x/43xx devices.
1695 If you have one of the devices above enable this driver to use
1696 the hardware RTC. This driver can also be built as a module. If
1697 so, the module will be called rtc-lpc24xx.
1699 config RTC_DRV_LPC32XX
1700 depends on ARCH_LPC32XX || COMPILE_TEST
1701 tristate "NXP LPC32XX RTC"
1703 This enables support for the NXP RTC in the LPC32XX
1705 This driver can also be built as a module. If so, the module
1706 will be called rtc-lpc32xx.
1708 config RTC_DRV_PM8XXX
1709 tristate "Qualcomm PMIC8XXX RTC"
1710 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1712 If you say yes here you get support for the
1713 Qualcomm PMIC8XXX RTC.
1715 To compile this driver as a module, choose M here: the
1716 module will be called rtc-pm8xxx.
1718 config RTC_DRV_TEGRA
1719 tristate "NVIDIA Tegra Internal RTC driver"
1720 depends on ARCH_TEGRA || COMPILE_TEST
1722 If you say yes here you get support for the
1723 Tegra 200 series internal RTC module.
1725 This drive can also be built as a module. If so, the module
1726 will be called rtc-tegra.
1728 config RTC_DRV_LOONGSON1
1729 tristate "loongson1 RTC support"
1730 depends on MACH_LOONGSON32
1732 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1733 counter) to be used as a RTC.
1735 This driver can also be built as a module. If so, the module
1736 will be called rtc-ls1x.
1739 tristate "Freescale MXC Real Time Clock"
1740 depends on ARCH_MXC || COMPILE_TEST
1741 depends on HAS_IOMEM
1744 If you say yes here you get support for the Freescale MXC
1747 This driver can also be built as a module, if so, the module
1748 will be called "rtc-mxc".
1750 config RTC_DRV_MXC_V2
1751 tristate "Freescale MXC Real Time Clock for i.MX53"
1752 depends on ARCH_MXC || COMPILE_TEST
1753 depends on HAS_IOMEM
1756 If you say yes here you get support for the Freescale MXC
1757 SRTC module in i.MX53 processor.
1759 This driver can also be built as a module, if so, the module
1760 will be called "rtc-mxc_v2".
1763 tristate "Freescale SNVS RTC support"
1765 depends on ARCH_MXC || COMPILE_TEST
1766 depends on HAS_IOMEM
1769 If you say yes here you get support for the Freescale SNVS
1770 Low Power (LP) RTC module.
1772 This driver can also be built as a module, if so, the module
1773 will be called "rtc-snvs".
1775 config RTC_DRV_IMX_SC
1777 depends on HAVE_ARM_SMCCC
1778 tristate "NXP i.MX System Controller RTC support"
1780 If you say yes here you get support for the NXP i.MX System
1781 Controller RTC module.
1783 config RTC_DRV_ST_LPC
1784 tristate "STMicroelectronics LPC RTC"
1788 Say Y here to include STMicroelectronics Low Power Controller
1789 (LPC) based RTC support.
1791 To compile this driver as a module, choose M here: the
1792 module will be called rtc-st-lpc.
1794 config RTC_DRV_MOXART
1795 tristate "MOXA ART RTC"
1796 depends on ARCH_MOXART || COMPILE_TEST
1798 If you say yes here you get support for the MOXA ART
1801 This driver can also be built as a module. If so, the module
1802 will be called rtc-moxart
1804 config RTC_DRV_MT2712
1805 tristate "MediaTek MT2712 SoC based RTC"
1806 depends on ARCH_MEDIATEK || COMPILE_TEST
1808 This enables support for the real time clock built in the MediaTek
1811 This drive can also be built as a module. If so, the module
1812 will be called rtc-mt2712.
1814 config RTC_DRV_MT6397
1815 tristate "MediaTek PMIC based RTC"
1816 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1818 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1819 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1820 MediaTek(R) RTC driver.
1822 If you want to use MediaTek(R) RTC interface, select Y or M here.
1824 config RTC_DRV_MT7622
1825 tristate "MediaTek SoC based RTC"
1826 depends on ARCH_MEDIATEK || COMPILE_TEST
1828 This enables support for the real time clock built in the MediaTek
1831 This drive can also be built as a module. If so, the module
1832 will be called rtc-mt7622.
1834 config RTC_DRV_XGENE
1835 tristate "APM X-Gene RTC"
1836 depends on HAS_IOMEM
1837 depends on ARCH_XGENE || COMPILE_TEST
1839 If you say yes here you get support for the APM X-Gene SoC real time
1842 This driver can also be built as a module, if so, the module
1843 will be called "rtc-xgene".
1845 config RTC_DRV_PIC32
1846 tristate "Microchip PIC32 RTC"
1847 depends on MACH_PIC32
1850 If you say yes here you get support for the PIC32 RTC module.
1852 This driver can also be built as a module. If so, the module
1853 will be called rtc-pic32
1855 config RTC_DRV_R7301
1856 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1858 depends on OF && HAS_IOMEM
1860 If you say yes here you get support for the EPSON TOYOCOM
1861 RTC-7301SF/DG chips.
1863 This driver can also be built as a module. If so, the module
1864 will be called rtc-r7301.
1866 config RTC_DRV_STM32
1867 tristate "STM32 RTC"
1869 depends on ARCH_STM32 || COMPILE_TEST
1871 If you say yes here you get support for the STM32 On-Chip
1874 This driver can also be built as a module, if so, the module
1875 will be called "rtc-stm32".
1877 config RTC_DRV_CPCAP
1878 depends on MFD_CPCAP
1879 tristate "Motorola CPCAP RTC"
1881 Say y here for CPCAP rtc found on some Motorola phones
1882 and tablets such as Droid 4.
1884 config RTC_DRV_RTD119X
1885 bool "Realtek RTD129x RTC"
1886 depends on ARCH_REALTEK || COMPILE_TEST
1887 default ARCH_REALTEK
1889 If you say yes here, you get support for the RTD1295 SoC
1892 config RTC_DRV_ASPEED
1893 tristate "ASPEED RTC"
1895 depends on ARCH_ASPEED || COMPILE_TEST
1897 If you say yes here you get support for the ASPEED BMC SoC real time
1900 This driver can also be built as a module, if so, the module
1901 will be called "rtc-aspeed".
1903 comment "HID Sensor RTC drivers"
1905 config RTC_DRV_HID_SENSOR_TIME
1906 tristate "HID Sensor Time"
1908 depends on HID_SENSOR_HUB && IIO
1909 select HID_SENSOR_IIO_COMMON
1911 Say yes here to build support for the HID Sensors of type Time.
1912 This drivers makes such sensors available as RTCs.
1914 If this driver is compiled as a module, it will be named
1915 rtc-hid-sensor-time.
1917 config RTC_DRV_GOLDFISH
1918 tristate "Goldfish Real Time Clock"
1919 depends on HAS_IOMEM
1921 Say yes to enable RTC driver for the Goldfish based virtual platform.
1923 Goldfish is a code name for the virtual platform developed by Google
1924 for Android emulation.
1926 config RTC_DRV_WILCO_EC
1927 tristate "Wilco EC RTC"
1931 If you say yes here, you get read/write support for the Real Time
1932 Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook)
1934 This can also be built as a module. If so, the module will
1935 be named "rtc_wilco_ec".