2 # RTC class/drivers configuration
8 config RTC_MC146818_LIB
13 bool "Real Time Clock"
15 depends on !S390 && !UML
18 Generic RTC class support. If you say yes here, you will
19 be allowed to plug one or more RTCs to your system. You will
20 probably want to enable one or more of the interfaces below.
25 bool "Set system time from RTC on startup and resume"
28 If you say yes here, the system time (wall clock) will be set using
29 the value read from a specified RTC device. This is useful to avoid
30 unnecessary fsck runs at boot time, and to network better.
32 config RTC_HCTOSYS_DEVICE
33 string "RTC used to set the system time"
34 depends on RTC_HCTOSYS
37 The RTC device that will be used to (re)initialize the system
38 clock, usually rtc0. Initialization is done when the system
39 starts up, and when it resumes from a low power state. This
40 device should record time in UTC, since the kernel won't do
43 The driver for this RTC device must be loaded before late_initcall
44 functions run, so it must usually be statically linked.
46 This clock should be battery-backed, so that it reads the correct
47 time when the system boots from a power-off state. Otherwise, your
48 system will need an external clock source (like an NTP server).
50 If the clock you specify here is not battery backed, it may still
51 be useful to reinitialize system time when resuming from system
52 sleep states. Do not specify an RTC here unless it stays powered
53 during all this system's supported sleep states.
56 bool "Set the RTC time based on NTP synchronization"
59 If you say yes here, the system time (wall clock) will be stored
60 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
61 minutes if userspace reports synchronized NTP status.
63 config RTC_SYSTOHC_DEVICE
64 string "RTC used to synchronize NTP adjustment"
65 depends on RTC_SYSTOHC
66 default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS
69 The RTC device used for NTP synchronization. The main difference
70 between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this
71 one can sleep when setting time, because it runs in the workqueue
75 bool "RTC debug support"
77 Say yes here to enable debugging support in the RTC framework
78 and individual RTC drivers.
81 bool "RTC non volatile storage support"
85 Say yes here to add support for the non volatile (often battery
86 backed) storage present on RTCs.
88 comment "RTC interfaces"
91 bool "/sys/class/rtc/rtcN (sysfs)"
95 Say yes here if you want to use your RTCs using sysfs interfaces,
96 /sys/class/rtc/rtc0 through /sys/.../rtcN.
101 bool "/proc/driver/rtc (procfs for rtcN)"
105 Say yes here if you want to use your system clock RTC through
106 the proc interface, /proc/driver/rtc.
107 Other RTCs will not be available through that API.
108 If there is no RTC for the system clock, then the first RTC(rtc0)
114 bool "/dev/rtcN (character devices)"
117 Say yes here if you want to use your RTCs using the /dev
118 interfaces, which "udev" sets up as /dev/rtc0 through
121 You may want to set up a symbolic link so one of these
122 can be accessed as /dev/rtc, which is a name
123 expected by "hwclock" and some other programs. Recent
124 versions of "udev" are known to set up the symlink for you.
128 config RTC_INTF_DEV_UIE_EMUL
129 bool "RTC UIE emulation on dev interface"
130 depends on RTC_INTF_DEV
132 Provides an emulation for RTC_UIE if the underlying rtc chip
133 driver does not expose RTC_UIE ioctls. Those requests generate
134 once-per-second update interrupts, used for synchronization.
136 The emulation code will read the time from the hardware
137 clock several times per second, please enable this option
138 only if you know that you really need it.
141 tristate "Test driver/device"
143 If you say yes here you get support for the
144 RTC test driver. It's a software RTC which can be
145 used to test the RTC subsystem APIs. It gets
146 the time from the system clock.
147 You want this driver only if you are doing development
148 on the RTC subsystem. Please read the source code
151 This driver can also be built as a module. If so, the module
152 will be called rtc-test.
154 comment "I2C RTC drivers"
158 config RTC_DRV_88PM860X
159 tristate "Marvell 88PM860x"
160 depends on MFD_88PM860X
162 If you say yes here you get support for RTC function in Marvell
165 This driver can also be built as a module. If so, the module
166 will be called rtc-88pm860x.
168 config RTC_DRV_88PM80X
169 tristate "Marvell 88PM80x"
170 depends on MFD_88PM800
172 If you say yes here you get support for RTC function in Marvell
175 This driver can also be built as a module. If so, the module
176 will be called rtc-88pm80x.
178 config RTC_DRV_ABB5ZES3
180 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
182 If you say yes here you get support for the Abracon
183 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
185 This driver can also be built as a module. If so, the module
186 will be called rtc-ab-b5ze-s3.
188 config RTC_DRV_ABEOZ9
190 tristate "Abracon AB-RTCMC-32.768kHz-EOZ9"
192 If you say yes here you get support for the Abracon
193 AB-RTCMC-32.768kHz-EOA9 I2C RTC chip.
195 This driver can also be built as a module. If so, the module
196 will be called rtc-ab-e0z9.
198 config RTC_DRV_ABX80X
199 tristate "Abracon ABx80x"
200 select WATCHDOG_CORE if WATCHDOG
202 If you say yes here you get support for Abracon AB080X and AB180X
203 families of ultra-low-power battery- and capacitor-backed real-time
206 This driver can also be built as a module. If so, the module
207 will be called rtc-abx80x.
210 tristate "X-Powers AC100"
213 If you say yes here you get support for the real-time clock found
214 in X-Powers AC100 family peripheral ICs.
216 This driver can also be built as a module. If so, the module
217 will be called rtc-ac100.
219 config RTC_DRV_BRCMSTB
220 tristate "Broadcom STB wake-timer"
221 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
222 default ARCH_BRCMSTB || BMIPS_GENERIC
224 If you say yes here you get support for the wake-timer found on
225 Broadcom STB SoCs (BCM7xxx).
227 This driver can also be built as a module. If so, the module will
228 be called rtc-brcmstb-waketimer.
230 config RTC_DRV_AS3722
231 tristate "ams AS3722 RTC driver"
232 depends on MFD_AS3722
234 If you say yes here you get support for the RTC of ams AS3722 PMIC
237 This driver can also be built as a module. If so, the module
238 will be called rtc-as3722.
240 config RTC_DRV_DS1307
241 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"
243 If you say yes here you get support for various compatible RTC
244 chips (often with battery backup) connected with I2C. This driver
245 should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341,
246 ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.
247 In some cases the RTC must already have been initialized (by
248 manufacturing or a bootloader).
250 The first seven registers on these chips hold an RTC, and other
251 registers may add features such as NVRAM, a trickle charger for
252 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
253 sysfs, but other chip features may not be available.
255 This driver can also be built as a module. If so, the module
256 will be called rtc-ds1307.
258 config RTC_DRV_DS1307_CENTURY
259 bool "Century bit support for rtc-ds1307"
260 depends on RTC_DRV_DS1307
263 The DS1307 driver suffered from a bug where it was enabling the
264 century bit inconditionnally but never used it when reading the time.
265 It made the driver unable to support dates beyond 2099.
266 Setting this option will add proper support for the century bit but if
267 the time was previously set using a kernel predating this option,
268 reading the date will return a date in the next century.
269 To solve that, you could boot a kernel without this option set, set
270 the RTC date and then boot a kernel with this option set.
272 config RTC_DRV_DS1374
273 tristate "Dallas/Maxim DS1374"
275 If you say yes here you get support for Dallas Semiconductor
276 DS1374 real-time clock chips. If an interrupt is associated
277 with the device, the alarm functionality is supported.
279 This driver can also be built as a module. If so, the module
280 will be called rtc-ds1374.
282 config RTC_DRV_DS1374_WDT
283 bool "Dallas/Maxim DS1374 watchdog timer"
284 depends on RTC_DRV_DS1374
286 If you say Y here you will get support for the
287 watchdog timer in the Dallas Semiconductor DS1374
288 real-time clock chips.
290 config RTC_DRV_DS1672
291 tristate "Dallas/Maxim DS1672"
293 If you say yes here you get support for the
294 Dallas/Maxim DS1672 timekeeping chip.
296 This driver can also be built as a module. If so, the module
297 will be called rtc-ds1672.
299 config RTC_DRV_HYM8563
300 tristate "Haoyu Microelectronics HYM8563"
303 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
304 from the usual rtc functions it provides a clock output of
307 This driver can also be built as a module. If so, the module
308 will be called rtc-hym8563.
310 config RTC_DRV_LP8788
311 tristate "TI LP8788 RTC driver"
312 depends on MFD_LP8788
314 Say Y to enable support for the LP8788 RTC/ALARM driver.
316 config RTC_DRV_MAX6900
317 tristate "Maxim MAX6900"
319 If you say yes here you will get support for the
320 Maxim MAX6900 I2C RTC chip.
322 This driver can also be built as a module. If so, the module
323 will be called rtc-max6900.
325 config RTC_DRV_MAX8907
326 tristate "Maxim MAX8907"
327 depends on MFD_MAX8907 || COMPILE_TEST
329 If you say yes here you will get support for the
330 RTC of Maxim MAX8907 PMIC.
332 This driver can also be built as a module. If so, the module
333 will be called rtc-max8907.
335 config RTC_DRV_MAX8925
336 tristate "Maxim MAX8925"
337 depends on MFD_MAX8925
339 If you say yes here you will get support for the
340 RTC of Maxim MAX8925 PMIC.
342 This driver can also be built as a module. If so, the module
343 will be called rtc-max8925.
345 config RTC_DRV_MAX8998
346 tristate "Maxim MAX8998"
347 depends on MFD_MAX8998
349 If you say yes here you will get support for the
350 RTC of Maxim MAX8998 PMIC.
352 This driver can also be built as a module. If so, the module
353 will be called rtc-max8998.
355 config RTC_DRV_MAX8997
356 tristate "Maxim MAX8997"
357 depends on MFD_MAX8997
359 If you say yes here you will get support for the
360 RTC of Maxim MAX8997 PMIC.
362 This driver can also be built as a module. If so, the module
363 will be called rtc-max8997.
365 config RTC_DRV_MAX77686
366 tristate "Maxim MAX77686"
367 depends on MFD_MAX77686 || MFD_MAX77620 || COMPILE_TEST
369 If you say yes here you will get support for the
370 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
372 This driver can also be built as a module. If so, the module
373 will be called rtc-max77686.
376 tristate "Rockchip RK805/RK808/RK818 RTC"
379 If you say yes here you will get support for the
380 RTC of RK805, RK808 and RK818 PMIC.
382 This driver can also be built as a module. If so, the module
383 will be called rk808-rtc.
385 config RTC_DRV_RS5C372
386 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
388 If you say yes here you get support for the
389 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
391 This driver can also be built as a module. If so, the module
392 will be called rtc-rs5c372.
394 config RTC_DRV_ISL1208
395 tristate "Intersil ISL1208"
397 If you say yes here you get support for the
398 Intersil ISL1208 RTC chip.
400 This driver can also be built as a module. If so, the module
401 will be called rtc-isl1208.
403 config RTC_DRV_ISL12022
404 tristate "Intersil ISL12022"
406 If you say yes here you get support for the
407 Intersil ISL12022 RTC chip.
409 This driver can also be built as a module. If so, the module
410 will be called rtc-isl12022.
412 config RTC_DRV_ISL12026
413 tristate "Intersil ISL12026"
414 depends on OF || COMPILE_TEST
416 If you say yes here you get support for the
417 Intersil ISL12026 RTC chip.
419 This driver can also be built as a module. If so, the module
420 will be called rtc-isl12026.
423 tristate "Xicor/Intersil X1205"
425 If you say yes here you get support for the
426 Xicor/Intersil X1205 RTC chip.
428 This driver can also be built as a module. If so, the module
429 will be called rtc-x1205.
431 config RTC_DRV_PCF8523
432 tristate "NXP PCF8523"
434 If you say yes here you get support for the NXP PCF8523 RTC
437 This driver can also be built as a module. If so, the module
438 will be called rtc-pcf8523.
440 config RTC_DRV_PCF85063
441 tristate "NXP PCF85063"
444 If you say yes here you get support for the PCF85063 RTC chip
446 This driver can also be built as a module. If so, the module
447 will be called rtc-pcf85063.
449 config RTC_DRV_PCF85363
450 tristate "NXP PCF85363"
453 If you say yes here you get support for the PCF85363 RTC chip.
455 This driver can also be built as a module. If so, the module
456 will be called rtc-pcf85363.
458 The nvmem interface will be named pcf85363-#, where # is the
459 zero-based instance number.
461 config RTC_DRV_PCF8563
462 tristate "Philips PCF8563/Epson RTC8564"
464 If you say yes here you get support for the
465 Philips PCF8563 RTC chip. The Epson RTC8564
468 This driver can also be built as a module. If so, the module
469 will be called rtc-pcf8563.
471 config RTC_DRV_PCF8583
472 tristate "Philips PCF8583"
474 If you say yes here you get support for the Philips PCF8583
475 RTC chip found on Acorn RiscPCs. This driver supports the
476 platform specific method of retrieving the current year from
477 the RTC's SRAM. It will work on other platforms with the same
478 chip, but the year will probably have to be tweaked.
480 This driver can also be built as a module. If so, the module
481 will be called rtc-pcf8583.
483 config RTC_DRV_M41T80
484 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
486 If you say Y here you will get support for the ST M41T60
487 and M41T80 RTC chips series. Currently, the following chips are
488 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
489 M41ST85, M41ST87, and MicroCrystal RV4162.
491 This driver can also be built as a module. If so, the module
492 will be called rtc-m41t80.
494 config RTC_DRV_M41T80_WDT
495 bool "ST M41T65/M41T80 series RTC watchdog timer"
496 depends on RTC_DRV_M41T80
498 If you say Y here you will get support for the
499 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
502 tristate "TI BQ32000"
504 If you say Y here you will get support for the TI
505 BQ32000 I2C RTC chip.
507 This driver can also be built as a module. If so, the module
508 will be called rtc-bq32k.
510 config RTC_DRV_DM355EVM
511 tristate "TI DaVinci DM355 EVM RTC"
512 depends on MFD_DM355EVM_MSP
514 Supports the RTC firmware in the MSP430 on the DM355 EVM.
516 config RTC_DRV_TWL92330
517 bool "TI TWL92330/Menelaus"
520 If you say yes here you get support for the RTC on the
521 TWL92330 "Menelaus" power management chip, used with OMAP2
522 platforms. The support is integrated with the rest of
523 the Menelaus driver; it's not separate module.
525 config RTC_DRV_TWL4030
526 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
527 depends on TWL4030_CORE
530 If you say yes here you get support for the RTC on the
531 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
533 This driver can also be built as a module. If so, the module
534 will be called rtc-twl.
536 config RTC_DRV_PALMAS
537 tristate "TI Palmas RTC driver"
538 depends on MFD_PALMAS
540 If you say yes here you get support for the RTC of TI PALMA series PMIC
543 This driver can also be built as a module. If so, the module
544 will be called rtc-palma.
546 config RTC_DRV_TPS6586X
547 tristate "TI TPS6586X RTC driver"
548 depends on MFD_TPS6586X
550 TI Power Management IC TPS6586X supports RTC functionality
551 along with alarm. This driver supports the RTC driver for
552 the TPS6586X RTC module.
554 config RTC_DRV_TPS65910
555 tristate "TI TPS65910 RTC driver"
556 depends on RTC_CLASS && MFD_TPS65910
558 If you say yes here you get support for the RTC on the
561 This driver can also be built as a module. If so, the module
562 will be called rtc-tps65910.
564 config RTC_DRV_TPS80031
565 tristate "TI TPS80031/TPS80032 RTC driver"
566 depends on MFD_TPS80031
568 TI Power Management IC TPS80031 supports RTC functionality
569 along with alarm. This driver supports the RTC driver for
570 the TPS80031 RTC module.
572 config RTC_DRV_RC5T583
573 tristate "RICOH 5T583 RTC driver"
574 depends on MFD_RC5T583
576 If you say yes here you get support for the RTC on the
579 This driver can also be built as a module. If so, the module
580 will be called rtc-rc5t583.
582 config RTC_DRV_S35390A
583 tristate "Seiko Instruments S-35390A"
586 If you say yes here you will get support for the Seiko
587 Instruments S-35390A.
589 This driver can also be built as a module. If so the module
590 will be called rtc-s35390a.
592 config RTC_DRV_FM3130
593 tristate "Ramtron FM3130"
595 If you say Y here you will get support for the
596 Ramtron FM3130 RTC chips.
597 Ramtron FM3130 is a chip with two separate devices inside,
598 RTC clock and FRAM. This driver provides only RTC functionality.
600 This driver can also be built as a module. If so the module
601 will be called rtc-fm3130.
603 config RTC_DRV_RX8010
604 tristate "Epson RX8010SJ"
606 If you say yes here you get support for the Epson RX8010SJ RTC
609 This driver can also be built as a module. If so, the module
610 will be called rtc-rx8010.
612 config RTC_DRV_RX8581
613 tristate "Epson RX-8571/RX-8581"
615 If you say yes here you will get support for the Epson RX-8571/
618 This driver can also be built as a module. If so the module
619 will be called rtc-rx8581.
621 config RTC_DRV_RX8025
622 tristate "Epson RX-8025SA/NB"
624 If you say yes here you get support for the Epson
625 RX-8025SA/NB RTC chips.
627 This driver can also be built as a module. If so, the module
628 will be called rtc-rx8025.
630 config RTC_DRV_EM3027
631 tristate "EM Microelectronic EM3027"
633 If you say yes here you get support for the EM
634 Microelectronic EM3027 RTC chips.
636 This driver can also be built as a module. If so, the module
637 will be called rtc-em3027.
639 config RTC_DRV_RV3028
640 tristate "Micro Crystal RV3028"
642 If you say yes here you get support for the Micro Crystal
645 This driver can also be built as a module. If so, the module
646 will be called rtc-rv3028.
648 config RTC_DRV_RV8803
649 tristate "Micro Crystal RV8803, Epson RX8900"
651 If you say yes here you get support for the Micro Crystal RV8803 and
652 Epson RX8900 RTC chips.
654 This driver can also be built as a module. If so, the module
655 will be called rtc-rv8803.
658 tristate "Samsung S2M/S5M series"
659 depends on MFD_SEC_CORE || COMPILE_TEST
662 If you say yes here you will get support for the
663 RTC of Samsung S2MPS14 and S5M PMIC series.
665 This driver can also be built as a module. If so, the module
666 will be called rtc-s5m.
668 config RTC_DRV_SD3078
669 tristate "ZXW Shenzhen whwave SD3078"
671 If you say yes here you get support for the ZXW Shenzhen whwave
674 This driver can also be built as a module. If so, the module
675 will be called rtc-sd3078
679 comment "SPI RTC drivers"
683 config RTC_DRV_M41T93
686 If you say yes here you will get support for the
687 ST M41T93 SPI RTC chip.
689 This driver can also be built as a module. If so, the module
690 will be called rtc-m41t93.
692 config RTC_DRV_M41T94
695 If you say yes here you will get support for the
696 ST M41T94 SPI RTC chip.
698 This driver can also be built as a module. If so, the module
699 will be called rtc-m41t94.
701 config RTC_DRV_DS1302
702 tristate "Dallas/Maxim DS1302"
705 If you say yes here you get support for the Dallas DS1302 RTC chips.
707 This driver can also be built as a module. If so, the module
708 will be called rtc-ds1302.
710 config RTC_DRV_DS1305
711 tristate "Dallas/Maxim DS1305/DS1306"
713 Select this driver to get support for the Dallas/Maxim DS1305
714 and DS1306 real time clock chips. These support a trickle
715 charger, alarms, and NVRAM in addition to the clock.
717 This driver can also be built as a module. If so, the module
718 will be called rtc-ds1305.
720 config RTC_DRV_DS1343
722 tristate "Dallas/Maxim DS1343/DS1344"
724 If you say yes here you get support for the
725 Dallas/Maxim DS1343 and DS1344 real time clock chips.
726 Support for trickle charger, alarm is provided.
728 This driver can also be built as a module. If so, the module
729 will be called rtc-ds1343.
731 config RTC_DRV_DS1347
733 tristate "Dallas/Maxim DS1347"
735 If you say yes here you get support for the
736 Dallas/Maxim DS1347 chips.
738 This driver only supports the RTC feature, and not other chip
739 features such as alarms.
741 This driver can also be built as a module. If so, the module
742 will be called rtc-ds1347.
744 config RTC_DRV_DS1390
745 tristate "Dallas/Maxim DS1390/93/94"
747 If you say yes here you get support for the
748 Dallas/Maxim DS1390/93/94 chips.
750 This driver supports the RTC feature and trickle charging but not
751 other chip features such as alarms.
753 This driver can also be built as a module. If so, the module
754 will be called rtc-ds1390.
756 config RTC_DRV_MAX6916
757 tristate "Maxim MAX6916"
759 If you say yes here you will get support for the
760 Maxim MAX6916 SPI RTC chip.
762 This driver only supports the RTC feature, and not other chip
763 features such as alarms.
765 This driver can also be built as a module. If so, the module
766 will be called rtc-max6916.
769 tristate "Epson RTC-9701JE"
771 If you say yes here you will get support for the
772 Epson RTC-9701JE SPI RTC chip.
774 This driver can also be built as a module. If so, the module
775 will be called rtc-r9701.
777 config RTC_DRV_RX4581
778 tristate "Epson RX-4581"
780 If you say yes here you will get support for the Epson RX-4581.
782 This driver can also be built as a module. If so the module
783 will be called rtc-rx4581.
785 config RTC_DRV_RX6110
786 tristate "Epson RX-6110"
789 If you say yes here you will get support for the Epson RX-6610.
791 This driver can also be built as a module. If so the module
792 will be called rtc-rx6110.
794 config RTC_DRV_RS5C348
795 tristate "Ricoh RS5C348A/B"
797 If you say yes here you get support for the
798 Ricoh RS5C348A and RS5C348B RTC chips.
800 This driver can also be built as a module. If so, the module
801 will be called rtc-rs5c348.
803 config RTC_DRV_MAX6902
804 tristate "Maxim MAX6902"
806 If you say yes here you will get support for the
807 Maxim MAX6902 SPI RTC chip.
809 This driver can also be built as a module. If so, the module
810 will be called rtc-max6902.
812 config RTC_DRV_PCF2123
813 tristate "NXP PCF2123"
815 If you say yes here you get support for the NXP PCF2123
818 This driver can also be built as a module. If so, the module
819 will be called rtc-pcf2123.
821 config RTC_DRV_MCP795
822 tristate "Microchip MCP795"
824 If you say yes here you will get support for the Microchip MCP795.
826 This driver can also be built as a module. If so the module
827 will be called rtc-mcp795.
832 # Helper to resolve issues with configs that have SPI enabled but I2C
833 # modular. See SND_SOC_I2C_AND_SPI for more information
835 config RTC_I2C_AND_SPI
839 default y if SPI_MASTER=y
840 select REGMAP_I2C if I2C
841 select REGMAP_SPI if SPI_MASTER
843 comment "SPI and I2C RTC drivers"
845 config RTC_DRV_DS3232
846 tristate "Dallas/Maxim DS3232/DS3234"
847 depends on RTC_I2C_AND_SPI
849 If you say yes here you get support for Dallas Semiconductor
850 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
851 with the device, the alarm functionality is supported.
853 This driver can also be built as a module. If so, the module
854 will be called rtc-ds3232.
856 config RTC_DRV_DS3232_HWMON
857 bool "HWMON support for Dallas/Maxim DS3232/DS3234"
858 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
861 Say Y here if you want to expose temperature sensor data on
864 config RTC_DRV_PCF2127
865 tristate "NXP PCF2127"
866 depends on RTC_I2C_AND_SPI
868 If you say yes here you get support for the NXP PCF2127/29 RTC
871 This driver can also be built as a module. If so, the module
872 will be called rtc-pcf2127.
874 config RTC_DRV_RV3029C2
875 tristate "Micro Crystal RV3029/3049"
876 depends on RTC_I2C_AND_SPI
878 If you say yes here you get support for the Micro Crystal
879 RV3029 and RV3049 RTC chips.
881 This driver can also be built as a module. If so, the module
882 will be called rtc-rv3029c2.
884 config RTC_DRV_RV3029_HWMON
885 bool "HWMON support for RV3029/3049"
886 depends on RTC_DRV_RV3029C2 && HWMON
887 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
890 Say Y here if you want to expose temperature sensor data on
893 comment "Platform RTC drivers"
895 # this 'CMOS' RTC driver is arch dependent because it requires
896 # <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
897 # global rtc_lock ... it's not yet just another platform_device.
900 tristate "PC-style 'CMOS'"
901 depends on X86 || ARM || PPC || MIPS || SPARC64
903 select RTC_MC146818_LIB
905 Say "yes" here to get direct support for the real time clock
906 found in every PC or ACPI-based system, and some other boards.
907 Specifically the original MC146818, compatibles like those in
908 PC south bridges, the DS12887 or M48T86, some multifunction
909 or LPC bus chips, and so on.
911 Your system will need to define the platform device used by
912 this driver, otherwise it won't be accessible. This means
913 you can safely enable this driver if you don't know whether
914 or not your board has this kind of hardware.
916 This driver can also be built as a module. If so, the module
917 will be called rtc-cmos.
920 bool "Alpha PC-style CMOS"
922 select RTC_MC146818_LIB
925 Direct support for the real-time clock found on every Alpha
926 system, specifically MC146818 compatibles. If in doubt, say Y.
929 tristate "Virtual RTC for Intel MID platforms"
930 depends on X86_INTEL_MID
931 default y if X86_INTEL_MID
934 Say "yes" here to get direct support for the real time clock
935 found on Moorestown platforms. The VRTC is a emulated RTC that
936 derives its clock source from a real RTC in the PMIC. The MC146818
937 style programming interface is mostly conserved, but any
938 updates are done via IPC calls to the system controller FW.
940 config RTC_DRV_DS1216
941 tristate "Dallas DS1216"
944 If you say yes here you get support for the Dallas DS1216 RTC chips.
946 config RTC_DRV_DS1286
947 tristate "Dallas DS1286"
950 If you say yes here you get support for the Dallas DS1286 RTC chips.
952 config RTC_DRV_DS1511
953 tristate "Dallas DS1511"
956 If you say yes here you get support for the
957 Dallas DS1511 timekeeping/watchdog chip.
959 This driver can also be built as a module. If so, the module
960 will be called rtc-ds1511.
962 config RTC_DRV_DS1553
963 tristate "Maxim/Dallas DS1553"
966 If you say yes here you get support for the
967 Maxim/Dallas DS1553 timekeeping chip.
969 This driver can also be built as a module. If so, the module
970 will be called rtc-ds1553.
972 config RTC_DRV_DS1685_FAMILY
973 tristate "Dallas/Maxim DS1685 Family"
975 If you say yes here you get support for the Dallas/Maxim DS1685
976 family of real time chips. This family includes the DS1685/DS1687,
977 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
978 DS17885/DS17887 chips.
980 This driver can also be built as a module. If so, the module
981 will be called rtc-ds1685.
985 depends on RTC_DRV_DS1685_FAMILY
986 default RTC_DRV_DS1685
988 config RTC_DRV_DS1685
991 This enables support for the Dallas/Maxim DS1685/DS1687 real time
994 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
995 systems, as well as EPPC-405-UC modules by electronic system design
998 config RTC_DRV_DS1689
1001 This enables support for the Dallas/Maxim DS1689/DS1693 real time
1004 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
1005 which supports a few minor features such as Vcc, Vbat, and Power
1006 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
1008 It also works for the even older DS1688/DS1691 RTC chips, which are
1009 virtually the same and carry the same model number. Both chips
1010 have 114 bytes of user NVRAM.
1012 config RTC_DRV_DS17285
1013 bool "DS17285/DS17287"
1015 This enables support for the Dallas/Maxim DS17285/DS17287 real time
1018 This chip features 2kb of extended NV-SRAM. It may possibly be
1019 found in some SGI O2 systems (rare).
1021 config RTC_DRV_DS17485
1022 bool "DS17485/DS17487"
1024 This enables support for the Dallas/Maxim DS17485/DS17487 real time
1027 This chip features 4kb of extended NV-SRAM.
1029 config RTC_DRV_DS17885
1030 bool "DS17885/DS17887"
1032 This enables support for the Dallas/Maxim DS17885/DS17887 real time
1035 This chip features 8kb of extended NV-SRAM.
1039 config RTC_DRV_DS1742
1040 tristate "Maxim/Dallas DS1742/1743"
1041 depends on HAS_IOMEM
1043 If you say yes here you get support for the
1044 Maxim/Dallas DS1742/1743 timekeeping chip.
1046 This driver can also be built as a module. If so, the module
1047 will be called rtc-ds1742.
1049 config RTC_DRV_DS2404
1050 tristate "Maxim/Dallas DS2404"
1052 If you say yes here you get support for the
1053 Dallas DS2404 RTC chip.
1055 This driver can also be built as a module. If so, the module
1056 will be called rtc-ds2404.
1058 config RTC_DRV_DA9052
1059 tristate "Dialog DA9052/DA9053 RTC"
1060 depends on PMIC_DA9052
1062 Say y here to support the RTC driver for Dialog Semiconductor
1063 DA9052-BC and DA9053-AA/Bx PMICs.
1065 config RTC_DRV_DA9055
1066 tristate "Dialog Semiconductor DA9055 RTC"
1067 depends on MFD_DA9055
1069 If you say yes here you will get support for the
1070 RTC of the Dialog DA9055 PMIC.
1072 This driver can also be built as a module. If so, the module
1073 will be called rtc-da9055
1075 config RTC_DRV_DA9063
1076 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1077 depends on MFD_DA9063 || MFD_DA9062
1079 If you say yes here you will get support for the RTC subsystem
1080 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1082 This driver can also be built as a module. If so, the module
1083 will be called "rtc-da9063".
1087 depends on EFI && !X86
1089 If you say yes here you will get support for the EFI
1092 This driver can also be built as a module. If so, the module
1093 will be called rtc-efi.
1095 config RTC_DRV_STK17TA8
1096 tristate "Simtek STK17TA8"
1097 depends on HAS_IOMEM
1099 If you say yes here you get support for the
1100 Simtek STK17TA8 timekeeping chip.
1102 This driver can also be built as a module. If so, the module
1103 will be called rtc-stk17ta8.
1105 config RTC_DRV_M48T86
1106 tristate "ST M48T86/Dallas DS12887"
1108 If you say Y here you will get support for the
1109 ST M48T86 and Dallas DS12887 RTC chips.
1111 This driver can also be built as a module. If so, the module
1112 will be called rtc-m48t86.
1114 config RTC_DRV_M48T35
1115 tristate "ST M48T35"
1116 depends on HAS_IOMEM
1118 If you say Y here you will get support for the
1121 This driver can also be built as a module, if so, the module
1122 will be called "rtc-m48t35".
1124 config RTC_DRV_M48T59
1125 tristate "ST M48T59/M48T08/M48T02"
1126 depends on HAS_IOMEM
1128 If you say Y here you will get support for the
1129 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1131 These chips are usually found in Sun SPARC and UltraSPARC
1134 This driver can also be built as a module, if so, the module
1135 will be called "rtc-m48t59".
1137 config RTC_DRV_MSM6242
1138 tristate "Oki MSM6242"
1139 depends on HAS_IOMEM
1141 If you say yes here you get support for the Oki MSM6242
1142 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1144 This driver can also be built as a module. If so, the module
1145 will be called rtc-msm6242.
1147 config RTC_DRV_BQ4802
1148 tristate "TI BQ4802"
1149 depends on HAS_IOMEM
1151 If you say Y here you will get support for the TI
1154 This driver can also be built as a module. If so, the module
1155 will be called rtc-bq4802.
1157 config RTC_DRV_RP5C01
1158 tristate "Ricoh RP5C01"
1159 depends on HAS_IOMEM
1161 If you say yes here you get support for the Ricoh RP5C01
1162 timekeeping chip. It is used in some Amiga models (e.g. A3000
1165 This driver can also be built as a module. If so, the module
1166 will be called rtc-rp5c01.
1168 config RTC_DRV_V3020
1169 tristate "EM Microelectronic V3020"
1171 If you say yes here you will get support for the
1172 EM Microelectronic v3020 RTC chip.
1174 This driver can also be built as a module. If so, the module
1175 will be called rtc-v3020.
1177 config RTC_DRV_WM831X
1178 tristate "Wolfson Microelectronics WM831x RTC"
1179 depends on MFD_WM831X
1181 If you say yes here you will get support for the RTC subsystem
1182 of the Wolfson Microelectronics WM831X series PMICs.
1184 This driver can also be built as a module. If so, the module
1185 will be called "rtc-wm831x".
1187 config RTC_DRV_WM8350
1188 tristate "Wolfson Microelectronics WM8350 RTC"
1189 depends on MFD_WM8350
1191 If you say yes here you will get support for the RTC subsystem
1192 of the Wolfson Microelectronics WM8350.
1194 This driver can also be built as a module. If so, the module
1195 will be called "rtc-wm8350".
1197 config RTC_DRV_SC27XX
1198 tristate "Spreadtrum SC27xx RTC"
1199 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1201 If you say Y here you will get support for the RTC subsystem
1202 of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs
1203 includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips.
1205 This driver can also be built as a module. If so, the module
1206 will be called rtc-sc27xx.
1208 config RTC_DRV_SPEAR
1209 tristate "SPEAR ST RTC"
1210 depends on PLAT_SPEAR || COMPILE_TEST
1213 If you say Y here you will get support for the RTC found on
1216 config RTC_DRV_PCF50633
1217 depends on MFD_PCF50633
1218 tristate "NXP PCF50633 RTC"
1220 If you say yes here you get support for the RTC subsystem of the
1221 NXP PCF50633 used in embedded systems.
1223 config RTC_DRV_AB3100
1224 tristate "ST-Ericsson AB3100 RTC"
1225 depends on AB3100_CORE
1226 default y if AB3100_CORE
1228 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1229 support. This chip contains a battery- and capacitor-backed RTC.
1231 config RTC_DRV_AB8500
1232 tristate "ST-Ericsson AB8500 RTC"
1233 depends on AB8500_CORE
1235 select RTC_INTF_DEV_UIE_EMUL
1237 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1238 support. This chip contains a battery- and capacitor-backed RTC.
1240 config RTC_DRV_NUC900
1241 tristate "NUC910/NUC920 RTC driver"
1242 depends on ARCH_W90X900 || COMPILE_TEST
1244 If you say yes here you get support for the RTC subsystem of the
1245 NUC910/NUC920 used in embedded systems.
1248 tristate "IBM OPAL RTC driver"
1249 depends on PPC_POWERNV
1252 If you say yes here you get support for the PowerNV platform RTC
1253 driver based on OPAL interfaces.
1255 This driver can also be built as a module. If so, the module
1256 will be called rtc-opal.
1258 config RTC_DRV_ZYNQMP
1259 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1262 If you say yes here you get support for the RTC controller found on
1263 Xilinx Zynq Ultrascale+ MPSoC.
1265 config RTC_DRV_CROS_EC
1266 tristate "Chrome OS EC RTC driver"
1267 depends on MFD_CROS_EC
1269 If you say yes here you will get support for the
1270 Chrome OS Embedded Controller's RTC.
1272 This driver can also be built as a module. If so, the module
1273 will be called rtc-cros-ec.
1275 comment "on-CPU RTC drivers"
1277 config RTC_DRV_ASM9260
1278 tristate "Alphascale asm9260 RTC"
1279 depends on MACH_ASM9260 || COMPILE_TEST
1281 If you say yes here you get support for the RTC on the
1282 Alphascale asm9260 SoC.
1284 This driver can also be built as a module. If so, the module
1285 will be called rtc-asm9260.
1287 config RTC_DRV_DAVINCI
1288 tristate "TI DaVinci RTC"
1289 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1291 If you say yes here you get support for the RTC on the
1292 DaVinci platforms (DM365).
1294 This driver can also be built as a module. If so, the module
1295 will be called rtc-davinci.
1297 config RTC_DRV_DIGICOLOR
1298 tristate "Conexant Digicolor RTC"
1299 depends on ARCH_DIGICOLOR || COMPILE_TEST
1301 If you say yes here you get support for the RTC on Conexant
1302 Digicolor platforms. This currently includes the CX92755 SoC.
1304 This driver can also be built as a module. If so, the module
1305 will be called rtc-digicolor.
1307 config RTC_DRV_IMXDI
1308 tristate "Freescale IMX DryIce Real Time Clock"
1311 Support for Freescale IMX DryIce RTC
1313 This driver can also be built as a module, if so, the module
1314 will be called "rtc-imxdi".
1316 config RTC_DRV_MESON
1317 tristate "Amlogic Meson RTC"
1318 depends on (ARM && ARCH_MESON) || COMPILE_TEST
1321 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1324 This driver can also be built as a module, if so, the module
1325 will be called "rtc-meson".
1328 tristate "TI OMAP Real Time Clock"
1329 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1332 select GENERIC_PINCONF
1334 Say "yes" here to support the on chip real time clock
1335 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1337 This driver can also be built as a module, if so, module
1338 will be called rtc-omap.
1343 This will include RTC support for Samsung SoCs. If
1344 you want to include RTC support for any machine, kindly
1345 select this in the respective mach-XXXX/Kconfig file.
1348 tristate "Samsung S3C series SoC RTC"
1349 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1351 RTC (Realtime Clock) driver for the clock inbuilt into the
1352 Samsung S3C24XX series of SoCs. This can provide periodic
1353 interrupt rates from 1Hz to 64Hz for user programs, and
1356 The driver currently supports the common features on all the
1357 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1360 This driver can also be build as a module. If so, the module
1361 will be called rtc-s3c.
1363 config RTC_DRV_EP93XX
1364 tristate "Cirrus Logic EP93XX"
1365 depends on ARCH_EP93XX || COMPILE_TEST
1367 If you say yes here you get support for the
1368 RTC embedded in the Cirrus Logic EP93XX processors.
1370 This driver can also be built as a module. If so, the module
1371 will be called rtc-ep93xx.
1373 config RTC_DRV_SA1100
1374 tristate "SA11x0/PXA2xx/PXA910"
1375 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1377 If you say Y here you will get access to the real time clock
1378 built into your SA11x0 or PXA2xx CPU.
1380 To compile this driver as a module, choose M here: the
1381 module will be called rtc-sa1100.
1384 tristate "SuperH On-Chip RTC"
1385 depends on SUPERH || ARCH_RENESAS
1387 Say Y here to enable support for the on-chip RTC found in
1388 most SuperH processors. This RTC is also found in RZ/A SoCs.
1390 To compile this driver as a module, choose M here: the
1391 module will be called rtc-sh.
1393 config RTC_DRV_VR41XX
1394 tristate "NEC VR41XX"
1395 depends on CPU_VR41XX || COMPILE_TEST
1397 If you say Y here you will get access to the real time clock
1398 built into your NEC VR41XX CPU.
1400 To compile this driver as a module, choose M here: the
1401 module will be called rtc-vr41xx.
1403 config RTC_DRV_PL030
1404 tristate "ARM AMBA PL030 RTC"
1407 If you say Y here you will get access to ARM AMBA
1408 PrimeCell PL030 RTC found on certain ARM SOCs.
1410 To compile this driver as a module, choose M here: the
1411 module will be called rtc-pl030.
1413 config RTC_DRV_PL031
1414 tristate "ARM AMBA PL031 RTC"
1417 If you say Y here you will get access to ARM AMBA
1418 PrimeCell PL031 RTC found on certain ARM SOCs.
1420 To compile this driver as a module, choose M here: the
1421 module will be called rtc-pl031.
1423 config RTC_DRV_AT91RM9200
1424 tristate "AT91RM9200 or some AT91SAM9 RTC"
1425 depends on ARCH_AT91 || COMPILE_TEST
1427 Driver for the internal RTC (Realtime Clock) module found on
1428 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1429 this is powered by the backup power supply.
1431 config RTC_DRV_AT91SAM9
1432 tristate "AT91SAM9 RTT as RTC"
1433 depends on ARCH_AT91 || COMPILE_TEST
1434 depends on OF && HAS_IOMEM
1437 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1438 can be used as an RTC thanks to the backup power supply (e.g. a
1439 small coin cell battery) which keeps this block and the GPBR
1440 (General Purpose Backup Registers) block powered when the device
1442 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1443 probably want to use the real RTC block instead of the "RTT as an
1446 config RTC_DRV_AU1XXX
1447 tristate "Au1xxx Counter0 RTC support"
1448 depends on MIPS_ALCHEMY
1450 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1451 counter) to be used as a RTC.
1453 This driver can also be built as a module. If so, the module
1454 will be called rtc-au1xxx.
1456 config RTC_DRV_RS5C313
1457 tristate "Ricoh RS5C313"
1458 depends on SH_LANDISK
1460 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1462 config RTC_DRV_GENERIC
1463 tristate "Generic RTC support"
1464 # Please consider writing a new RTC driver instead of using the generic
1466 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
1468 Say Y or M here to enable RTC support on systems using the generic
1469 RTC abstraction. If you do not know what you are doing, you should
1473 tristate "PXA27x/PXA3xx"
1475 select RTC_DRV_SA1100
1477 If you say Y here you will get access to the real time clock
1478 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1479 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1481 This RTC driver uses PXA RTC registers available since pxa27x
1482 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1484 config RTC_DRV_VT8500
1485 tristate "VIA/WonderMedia 85xx SoC RTC"
1486 depends on ARCH_VT8500 || COMPILE_TEST
1488 If you say Y here you will get access to the real time clock
1489 built into your VIA VT8500 SoC or its relatives.
1492 config RTC_DRV_SUN4V
1493 bool "SUN4V Hypervisor RTC"
1496 If you say Y here you will get support for the Hypervisor
1497 based RTC on SUN4V systems.
1499 config RTC_DRV_SUN6I
1500 bool "Allwinner A31 RTC"
1501 default MACH_SUN6I || MACH_SUN8I
1502 depends on COMMON_CLK
1503 depends on ARCH_SUNXI || COMPILE_TEST
1505 If you say Y here you will get support for the RTC found in
1506 some Allwinner SoCs like the A31 or the A64.
1508 config RTC_DRV_SUNXI
1509 tristate "Allwinner sun4i/sun7i RTC"
1510 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1512 If you say Y here you will get support for the RTC found on
1515 config RTC_DRV_STARFIRE
1519 If you say Y here you will get support for the RTC found on
1522 config RTC_DRV_TX4939
1523 tristate "TX4939 SoC"
1524 depends on SOC_TX4939 || COMPILE_TEST
1526 Driver for the internal RTC (Realtime Clock) module found on
1530 tristate "Marvell SoC RTC"
1531 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1533 If you say yes here you will get support for the in-chip RTC
1534 that can be found in some of Marvell's SoC devices, such as
1535 the Kirkwood 88F6281 and 88F6192.
1537 This driver can also be built as a module. If so, the module
1538 will be called rtc-mv.
1540 config RTC_DRV_ARMADA38X
1541 tristate "Armada 38x Marvell SoC RTC"
1542 depends on ARCH_MVEBU || COMPILE_TEST
1544 If you say yes here you will get support for the in-chip RTC
1545 that can be found in the Armada 38x Marvell's SoC device
1547 This driver can also be built as a module. If so, the module
1548 will be called armada38x-rtc.
1550 config RTC_DRV_CADENCE
1551 tristate "Cadence RTC driver"
1552 depends on OF && HAS_IOMEM
1554 If you say Y here you will get access to Cadence RTC IP
1555 found on certain SOCs.
1557 To compile this driver as a module, choose M here: the
1558 module will be called rtc-cadence.
1560 config RTC_DRV_FTRTC010
1561 tristate "Faraday Technology FTRTC010 RTC"
1562 depends on HAS_IOMEM
1565 If you say Y here you will get support for the
1566 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1568 This driver can also be built as a module. If so, the module
1569 will be called rtc-ftrtc010.
1575 If you say yes here you will get support for the RTC on PS3.
1577 This driver can also be built as a module. If so, the module
1578 will be called rtc-ps3.
1580 config RTC_DRV_COH901331
1581 tristate "ST-Ericsson COH 901 331 RTC"
1582 depends on ARCH_U300 || COMPILE_TEST
1584 If you say Y here you will get access to ST-Ericsson
1585 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1588 This driver can also be built as a module. If so, the module
1589 will be called "rtc-coh901331".
1593 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1594 depends on ARCH_MXS || COMPILE_TEST
1597 If you say yes here you will get support for the onboard
1598 STMP3xxx/i.MX23/i.MX28 RTC.
1600 This driver can also be built as a module. If so, the module
1601 will be called rtc-stmp3xxx.
1607 If you say Y here you will get support for the RTC found on
1608 the PCAP2 ASIC used on some Motorola phones.
1610 config RTC_DRV_MC13XXX
1611 depends on MFD_MC13XXX
1612 tristate "Freescale MC13xxx RTC"
1614 This enables support for the RTCs found on Freescale's PMICs
1615 MC13783 and MC13892.
1617 config RTC_DRV_MPC5121
1618 tristate "Freescale MPC5121 built-in RTC"
1619 depends on PPC_MPC512x || PPC_MPC52xx
1621 If you say yes here you will get support for the
1622 built-in RTC on MPC5121 or on MPC5200.
1624 This driver can also be built as a module. If so, the module
1625 will be called rtc-mpc5121.
1627 config RTC_DRV_JZ4740
1628 tristate "Ingenic JZ4740 SoC"
1629 depends on MIPS || COMPILE_TEST
1631 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1634 This driver can also be built as a module. If so, the module
1635 will be called rtc-jz4740.
1637 config RTC_DRV_LPC24XX
1638 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1639 depends on ARCH_LPC18XX || COMPILE_TEST
1640 depends on OF && HAS_IOMEM
1642 This enables support for the NXP RTC found which can be found on
1643 NXP LPC178x/18xx/408x/43xx devices.
1645 If you have one of the devices above enable this driver to use
1646 the hardware RTC. This driver can also be built as a module. If
1647 so, the module will be called rtc-lpc24xx.
1649 config RTC_DRV_LPC32XX
1650 depends on ARCH_LPC32XX || COMPILE_TEST
1651 tristate "NXP LPC32XX RTC"
1653 This enables support for the NXP RTC in the LPC32XX
1655 This driver can also be built as a module. If so, the module
1656 will be called rtc-lpc32xx.
1658 config RTC_DRV_PM8XXX
1659 tristate "Qualcomm PMIC8XXX RTC"
1660 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1662 If you say yes here you get support for the
1663 Qualcomm PMIC8XXX RTC.
1665 To compile this driver as a module, choose M here: the
1666 module will be called rtc-pm8xxx.
1668 config RTC_DRV_TEGRA
1669 tristate "NVIDIA Tegra Internal RTC driver"
1670 depends on ARCH_TEGRA || COMPILE_TEST
1672 If you say yes here you get support for the
1673 Tegra 200 series internal RTC module.
1675 This drive can also be built as a module. If so, the module
1676 will be called rtc-tegra.
1679 tristate "PKUnity v3 RTC support"
1680 depends on ARCH_PUV3
1682 This enables support for the RTC in the PKUnity-v3 SoCs.
1684 This drive can also be built as a module. If so, the module
1685 will be called rtc-puv3.
1687 config RTC_DRV_LOONGSON1
1688 tristate "loongson1 RTC support"
1689 depends on MACH_LOONGSON32
1691 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1692 counter) to be used as a RTC.
1694 This driver can also be built as a module. If so, the module
1695 will be called rtc-ls1x.
1698 tristate "Freescale MXC Real Time Clock"
1701 If you say yes here you get support for the Freescale MXC
1704 This driver can also be built as a module, if so, the module
1705 will be called "rtc-mxc".
1707 config RTC_DRV_MXC_V2
1708 tristate "Freescale MXC Real Time Clock for i.MX53"
1711 If you say yes here you get support for the Freescale MXC
1712 SRTC module in i.MX53 processor.
1714 This driver can also be built as a module, if so, the module
1715 will be called "rtc-mxc_v2".
1718 tristate "Freescale SNVS RTC support"
1720 depends on HAS_IOMEM
1723 If you say yes here you get support for the Freescale SNVS
1724 Low Power (LP) RTC module.
1726 This driver can also be built as a module, if so, the module
1727 will be called "rtc-snvs".
1729 config RTC_DRV_IMX_SC
1731 depends on HAVE_ARM_SMCCC
1732 tristate "NXP i.MX System Controller RTC support"
1734 If you say yes here you get support for the NXP i.MX System
1735 Controller RTC module.
1737 config RTC_DRV_SIRFSOC
1738 tristate "SiRFSOC RTC"
1739 depends on ARCH_SIRF
1741 Say "yes" here to support the real time clock on SiRF SOC chips.
1742 This driver can also be built as a module called rtc-sirfsoc.
1744 config RTC_DRV_ST_LPC
1745 tristate "STMicroelectronics LPC RTC"
1749 Say Y here to include STMicroelectronics Low Power Controller
1750 (LPC) based RTC support.
1752 To compile this driver as a module, choose M here: the
1753 module will be called rtc-st-lpc.
1755 config RTC_DRV_MOXART
1756 tristate "MOXA ART RTC"
1757 depends on ARCH_MOXART || COMPILE_TEST
1759 If you say yes here you get support for the MOXA ART
1762 This driver can also be built as a module. If so, the module
1763 will be called rtc-moxart
1765 config RTC_DRV_MT6397
1766 tristate "MediaTek PMIC based RTC"
1767 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1769 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1770 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1771 MediaTek(R) RTC driver.
1773 If you want to use MediaTek(R) RTC interface, select Y or M here.
1775 config RTC_DRV_MT7622
1776 tristate "MediaTek SoC based RTC"
1777 depends on ARCH_MEDIATEK || COMPILE_TEST
1779 This enables support for the real time clock built in the MediaTek
1782 This drive can also be built as a module. If so, the module
1783 will be called rtc-mt7622.
1785 config RTC_DRV_XGENE
1786 tristate "APM X-Gene RTC"
1787 depends on HAS_IOMEM
1788 depends on ARCH_XGENE || COMPILE_TEST
1790 If you say yes here you get support for the APM X-Gene SoC real time
1793 This driver can also be built as a module, if so, the module
1794 will be called "rtc-xgene".
1796 config RTC_DRV_PIC32
1797 tristate "Microchip PIC32 RTC"
1798 depends on MACH_PIC32
1801 If you say yes here you get support for the PIC32 RTC module.
1803 This driver can also be built as a module. If so, the module
1804 will be called rtc-pic32
1806 config RTC_DRV_R7301
1807 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1809 depends on OF && HAS_IOMEM
1811 If you say yes here you get support for the EPSON TOYOCOM
1812 RTC-7301SF/DG chips.
1814 This driver can also be built as a module. If so, the module
1815 will be called rtc-r7301.
1817 config RTC_DRV_STM32
1818 tristate "STM32 RTC"
1820 depends on ARCH_STM32 || COMPILE_TEST
1822 If you say yes here you get support for the STM32 On-Chip
1825 This driver can also be built as a module, if so, the module
1826 will be called "rtc-stm32".
1828 config RTC_DRV_CPCAP
1829 depends on MFD_CPCAP
1830 tristate "Motorola CPCAP RTC"
1832 Say y here for CPCAP rtc found on some Motorola phones
1833 and tablets such as Droid 4.
1835 config RTC_DRV_RTD119X
1836 bool "Realtek RTD129x RTC"
1837 depends on ARCH_REALTEK || COMPILE_TEST
1838 default ARCH_REALTEK
1840 If you say yes here, you get support for the RTD1295 SoC
1843 config RTC_DRV_ASPEED
1844 tristate "ASPEED RTC"
1846 depends on ARCH_ASPEED || COMPILE_TEST
1848 If you say yes here you get support for the ASPEED BMC SoC real time
1851 This driver can also be built as a module, if so, the module
1852 will be called "rtc-aspeed".
1854 comment "HID Sensor RTC drivers"
1856 config RTC_DRV_HID_SENSOR_TIME
1857 tristate "HID Sensor Time"
1859 depends on HID_SENSOR_HUB && IIO
1860 select HID_SENSOR_IIO_COMMON
1862 Say yes here to build support for the HID Sensors of type Time.
1863 This drivers makes such sensors available as RTCs.
1865 If this driver is compiled as a module, it will be named
1866 rtc-hid-sensor-time.
1868 config RTC_DRV_GOLDFISH
1869 tristate "Goldfish Real Time Clock"
1870 depends on OF && HAS_IOMEM
1871 depends on GOLDFISH || COMPILE_TEST
1873 Say yes to enable RTC driver for the Goldfish based virtual platform.
1875 Goldfish is a code name for the virtual platform developed by Google
1876 for Android emulation.
1878 config RTC_DRV_WILCO_EC
1879 tristate "Wilco EC RTC"
1883 If you say yes here, you get read/write support for the Real Time
1884 Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook)
1886 This can also be built as a module. If so, the module will
1887 be named "rtc_wilco_ec".