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_ABX80X
189 tristate "Abracon ABx80x"
191 If you say yes here you get support for Abracon AB080X and AB180X
192 families of ultra-low-power battery- and capacitor-backed real-time
195 This driver can also be built as a module. If so, the module
196 will be called rtc-abx80x.
199 tristate "X-Powers AC100"
202 If you say yes here you get support for the real-time clock found
203 in X-Powers AC100 family peripheral ICs.
205 This driver can also be built as a module. If so, the module
206 will be called rtc-ac100.
208 config RTC_DRV_BRCMSTB
209 tristate "Broadcom STB wake-timer"
210 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
211 default ARCH_BRCMSTB || BMIPS_GENERIC
213 If you say yes here you get support for the wake-timer found on
214 Broadcom STB SoCs (BCM7xxx).
216 This driver can also be built as a module. If so, the module will
217 be called rtc-brcmstb-waketimer.
219 config RTC_DRV_AS3722
220 tristate "ams AS3722 RTC driver"
221 depends on MFD_AS3722
223 If you say yes here you get support for the RTC of ams AS3722 PMIC
226 This driver can also be built as a module. If so, the module
227 will be called rtc-as3722.
229 config RTC_DRV_DS1307
230 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"
232 If you say yes here you get support for various compatible RTC
233 chips (often with battery backup) connected with I2C. This driver
234 should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341,
235 ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.
236 In some cases the RTC must already have been initialized (by
237 manufacturing or a bootloader).
239 The first seven registers on these chips hold an RTC, and other
240 registers may add features such as NVRAM, a trickle charger for
241 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
242 sysfs, but other chip features may not be available.
244 This driver can also be built as a module. If so, the module
245 will be called rtc-ds1307.
247 config RTC_DRV_DS1307_CENTURY
248 bool "Century bit support for rtc-ds1307"
249 depends on RTC_DRV_DS1307
252 The DS1307 driver suffered from a bug where it was enabling the
253 century bit inconditionnally but never used it when reading the time.
254 It made the driver unable to support dates beyond 2099.
255 Setting this option will add proper support for the century bit but if
256 the time was previously set using a kernel predating this option,
257 reading the date will return a date in the next century.
258 To solve that, you could boot a kernel without this option set, set
259 the RTC date and then boot a kernel with this option set.
261 config RTC_DRV_DS1374
262 tristate "Dallas/Maxim DS1374"
264 If you say yes here you get support for Dallas Semiconductor
265 DS1374 real-time clock chips. If an interrupt is associated
266 with the device, the alarm functionality is supported.
268 This driver can also be built as a module. If so, the module
269 will be called rtc-ds1374.
271 config RTC_DRV_DS1374_WDT
272 bool "Dallas/Maxim DS1374 watchdog timer"
273 depends on RTC_DRV_DS1374
275 If you say Y here you will get support for the
276 watchdog timer in the Dallas Semiconductor DS1374
277 real-time clock chips.
279 config RTC_DRV_DS1672
280 tristate "Dallas/Maxim DS1672"
282 If you say yes here you get support for the
283 Dallas/Maxim DS1672 timekeeping chip.
285 This driver can also be built as a module. If so, the module
286 will be called rtc-ds1672.
288 config RTC_DRV_HYM8563
289 tristate "Haoyu Microelectronics HYM8563"
292 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
293 from the usual rtc functions it provides a clock output of
296 This driver can also be built as a module. If so, the module
297 will be called rtc-hym8563.
299 config RTC_DRV_LP8788
300 tristate "TI LP8788 RTC driver"
301 depends on MFD_LP8788
303 Say Y to enable support for the LP8788 RTC/ALARM driver.
305 config RTC_DRV_MAX6900
306 tristate "Maxim MAX6900"
308 If you say yes here you will get support for the
309 Maxim MAX6900 I2C RTC chip.
311 This driver can also be built as a module. If so, the module
312 will be called rtc-max6900.
314 config RTC_DRV_MAX8907
315 tristate "Maxim MAX8907"
316 depends on MFD_MAX8907 || COMPILE_TEST
319 If you say yes here you will get support for the
320 RTC of Maxim MAX8907 PMIC.
322 This driver can also be built as a module. If so, the module
323 will be called rtc-max8907.
325 config RTC_DRV_MAX8925
326 tristate "Maxim MAX8925"
327 depends on MFD_MAX8925
329 If you say yes here you will get support for the
330 RTC of Maxim MAX8925 PMIC.
332 This driver can also be built as a module. If so, the module
333 will be called rtc-max8925.
335 config RTC_DRV_MAX8998
336 tristate "Maxim MAX8998"
337 depends on MFD_MAX8998
339 If you say yes here you will get support for the
340 RTC of Maxim MAX8998 PMIC.
342 This driver can also be built as a module. If so, the module
343 will be called rtc-max8998.
345 config RTC_DRV_MAX8997
346 tristate "Maxim MAX8997"
347 depends on MFD_MAX8997
349 If you say yes here you will get support for the
350 RTC of Maxim MAX8997 PMIC.
352 This driver can also be built as a module. If so, the module
353 will be called rtc-max8997.
355 config RTC_DRV_MAX77686
356 tristate "Maxim MAX77686"
357 depends on MFD_MAX77686 || MFD_MAX77620 || COMPILE_TEST
359 If you say yes here you will get support for the
360 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
362 This driver can also be built as a module. If so, the module
363 will be called rtc-max77686.
366 tristate "Rockchip RK805/RK808/RK818 RTC"
369 If you say yes here you will get support for the
370 RTC of RK805, RK808 and RK818 PMIC.
372 This driver can also be built as a module. If so, the module
373 will be called rk808-rtc.
375 config RTC_DRV_RS5C372
376 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
378 If you say yes here you get support for the
379 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
381 This driver can also be built as a module. If so, the module
382 will be called rtc-rs5c372.
384 config RTC_DRV_ISL1208
385 tristate "Intersil ISL1208"
387 If you say yes here you get support for the
388 Intersil ISL1208 RTC chip.
390 This driver can also be built as a module. If so, the module
391 will be called rtc-isl1208.
393 config RTC_DRV_ISL12022
394 tristate "Intersil ISL12022"
396 If you say yes here you get support for the
397 Intersil ISL12022 RTC chip.
399 This driver can also be built as a module. If so, the module
400 will be called rtc-isl12022.
402 config RTC_DRV_ISL12026
403 tristate "Intersil ISL12026"
404 depends on OF || COMPILE_TEST
406 If you say yes here you get support for the
407 Intersil ISL12026 RTC chip.
409 This driver can also be built as a module. If so, the module
410 will be called rtc-isl12026.
413 tristate "Xicor/Intersil X1205"
415 If you say yes here you get support for the
416 Xicor/Intersil X1205 RTC chip.
418 This driver can also be built as a module. If so, the module
419 will be called rtc-x1205.
421 config RTC_DRV_PCF8523
422 tristate "NXP PCF8523"
424 If you say yes here you get support for the NXP PCF8523 RTC
427 This driver can also be built as a module. If so, the module
428 will be called rtc-pcf8523.
430 config RTC_DRV_PCF85063
431 tristate "NXP PCF85063"
433 If you say yes here you get support for the PCF85063 RTC chip
435 This driver can also be built as a module. If so, the module
436 will be called rtc-pcf85063.
438 config RTC_DRV_PCF85363
439 tristate "NXP PCF85363"
443 If you say yes here you get support for the PCF85363 RTC chip.
445 This driver can also be built as a module. If so, the module
446 will be called rtc-pcf85363.
448 The nvmem interface will be named pcf85363-#, where # is the
449 zero-based instance number.
451 config RTC_DRV_PCF8563
452 tristate "Philips PCF8563/Epson RTC8564"
454 If you say yes here you get support for the
455 Philips PCF8563 RTC chip. The Epson RTC8564
458 This driver can also be built as a module. If so, the module
459 will be called rtc-pcf8563.
461 config RTC_DRV_PCF8583
462 tristate "Philips PCF8583"
464 If you say yes here you get support for the Philips PCF8583
465 RTC chip found on Acorn RiscPCs. This driver supports the
466 platform specific method of retrieving the current year from
467 the RTC's SRAM. It will work on other platforms with the same
468 chip, but the year will probably have to be tweaked.
470 This driver can also be built as a module. If so, the module
471 will be called rtc-pcf8583.
473 config RTC_DRV_M41T80
474 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
476 If you say Y here you will get support for the ST M41T60
477 and M41T80 RTC chips series. Currently, the following chips are
478 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
479 M41ST85, M41ST87, and MicroCrystal RV4162.
481 This driver can also be built as a module. If so, the module
482 will be called rtc-m41t80.
484 config RTC_DRV_M41T80_WDT
485 bool "ST M41T65/M41T80 series RTC watchdog timer"
486 depends on RTC_DRV_M41T80
488 If you say Y here you will get support for the
489 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
492 tristate "TI BQ32000"
494 If you say Y here you will get support for the TI
495 BQ32000 I2C RTC chip.
497 This driver can also be built as a module. If so, the module
498 will be called rtc-bq32k.
500 config RTC_DRV_DM355EVM
501 tristate "TI DaVinci DM355 EVM RTC"
502 depends on MFD_DM355EVM_MSP
504 Supports the RTC firmware in the MSP430 on the DM355 EVM.
506 config RTC_DRV_TWL92330
507 bool "TI TWL92330/Menelaus"
510 If you say yes here you get support for the RTC on the
511 TWL92330 "Menelaus" power management chip, used with OMAP2
512 platforms. The support is integrated with the rest of
513 the Menelaus driver; it's not separate module.
515 config RTC_DRV_TWL4030
516 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
517 depends on TWL4030_CORE
520 If you say yes here you get support for the RTC on the
521 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
523 This driver can also be built as a module. If so, the module
524 will be called rtc-twl.
526 config RTC_DRV_PALMAS
527 tristate "TI Palmas RTC driver"
528 depends on MFD_PALMAS
530 If you say yes here you get support for the RTC of TI PALMA series PMIC
533 This driver can also be built as a module. If so, the module
534 will be called rtc-palma.
536 config RTC_DRV_TPS6586X
537 tristate "TI TPS6586X RTC driver"
538 depends on MFD_TPS6586X
540 TI Power Management IC TPS6586X supports RTC functionality
541 along with alarm. This driver supports the RTC driver for
542 the TPS6586X RTC module.
544 config RTC_DRV_TPS65910
545 tristate "TI TPS65910 RTC driver"
546 depends on RTC_CLASS && MFD_TPS65910
548 If you say yes here you get support for the RTC on the
551 This driver can also be built as a module. If so, the module
552 will be called rtc-tps65910.
554 config RTC_DRV_TPS80031
555 tristate "TI TPS80031/TPS80032 RTC driver"
556 depends on MFD_TPS80031
558 TI Power Management IC TPS80031 supports RTC functionality
559 along with alarm. This driver supports the RTC driver for
560 the TPS80031 RTC module.
562 config RTC_DRV_RC5T583
563 tristate "RICOH 5T583 RTC driver"
564 depends on MFD_RC5T583
566 If you say yes here you get support for the RTC on the
569 This driver can also be built as a module. If so, the module
570 will be called rtc-rc5t583.
572 config RTC_DRV_S35390A
573 tristate "Seiko Instruments S-35390A"
576 If you say yes here you will get support for the Seiko
577 Instruments S-35390A.
579 This driver can also be built as a module. If so the module
580 will be called rtc-s35390a.
582 config RTC_DRV_FM3130
583 tristate "Ramtron FM3130"
585 If you say Y here you will get support for the
586 Ramtron FM3130 RTC chips.
587 Ramtron FM3130 is a chip with two separate devices inside,
588 RTC clock and FRAM. This driver provides only RTC functionality.
590 This driver can also be built as a module. If so the module
591 will be called rtc-fm3130.
593 config RTC_DRV_RX8010
594 tristate "Epson RX8010SJ"
597 If you say yes here you get support for the Epson RX8010SJ RTC
600 This driver can also be built as a module. If so, the module
601 will be called rtc-rx8010.
603 config RTC_DRV_RX8581
604 tristate "Epson RX-8581"
606 If you say yes here you will get support for the Epson RX-8581.
608 This driver can also be built as a module. If so the module
609 will be called rtc-rx8581.
611 config RTC_DRV_RX8025
612 tristate "Epson RX-8025SA/NB"
614 If you say yes here you get support for the Epson
615 RX-8025SA/NB RTC chips.
617 This driver can also be built as a module. If so, the module
618 will be called rtc-rx8025.
620 config RTC_DRV_EM3027
621 tristate "EM Microelectronic EM3027"
623 If you say yes here you get support for the EM
624 Microelectronic EM3027 RTC chips.
626 This driver can also be built as a module. If so, the module
627 will be called rtc-em3027.
629 config RTC_DRV_RV8803
630 tristate "Micro Crystal RV8803, Epson RX8900"
632 If you say yes here you get support for the Micro Crystal RV8803 and
633 Epson RX8900 RTC chips.
635 This driver can also be built as a module. If so, the module
636 will be called rtc-rv8803.
639 tristate "Samsung S2M/S5M series"
640 depends on MFD_SEC_CORE || COMPILE_TEST
644 If you say yes here you will get support for the
645 RTC of Samsung S2MPS14 and S5M PMIC series.
647 This driver can also be built as a module. If so, the module
648 will be called rtc-s5m.
652 comment "SPI RTC drivers"
656 config RTC_DRV_M41T93
659 If you say yes here you will get support for the
660 ST M41T93 SPI RTC chip.
662 This driver can also be built as a module. If so, the module
663 will be called rtc-m41t93.
665 config RTC_DRV_M41T94
668 If you say yes here you will get support for the
669 ST M41T94 SPI RTC chip.
671 This driver can also be built as a module. If so, the module
672 will be called rtc-m41t94.
674 config RTC_DRV_DS1302
675 tristate "Dallas/Maxim DS1302"
678 If you say yes here you get support for the Dallas DS1302 RTC chips.
680 This driver can also be built as a module. If so, the module
681 will be called rtc-ds1302.
683 config RTC_DRV_DS1305
684 tristate "Dallas/Maxim DS1305/DS1306"
686 Select this driver to get support for the Dallas/Maxim DS1305
687 and DS1306 real time clock chips. These support a trickle
688 charger, alarms, and NVRAM in addition to the clock.
690 This driver can also be built as a module. If so, the module
691 will be called rtc-ds1305.
693 config RTC_DRV_DS1343
695 tristate "Dallas/Maxim DS1343/DS1344"
697 If you say yes here you get support for the
698 Dallas/Maxim DS1343 and DS1344 real time clock chips.
699 Support for trickle charger, alarm is provided.
701 This driver can also be built as a module. If so, the module
702 will be called rtc-ds1343.
704 config RTC_DRV_DS1347
706 tristate "Dallas/Maxim DS1347"
708 If you say yes here you get support for the
709 Dallas/Maxim DS1347 chips.
711 This driver only supports the RTC feature, and not other chip
712 features such as alarms.
714 This driver can also be built as a module. If so, the module
715 will be called rtc-ds1347.
717 config RTC_DRV_DS1390
718 tristate "Dallas/Maxim DS1390/93/94"
720 If you say yes here you get support for the
721 Dallas/Maxim DS1390/93/94 chips.
723 This driver supports the RTC feature and trickle charging but not
724 other chip features such as alarms.
726 This driver can also be built as a module. If so, the module
727 will be called rtc-ds1390.
729 config RTC_DRV_MAX6916
730 tristate "Maxim MAX6916"
732 If you say yes here you will get support for the
733 Maxim MAX6916 SPI RTC chip.
735 This driver only supports the RTC feature, and not other chip
736 features such as alarms.
738 This driver can also be built as a module. If so, the module
739 will be called rtc-max6916.
742 tristate "Epson RTC-9701JE"
744 If you say yes here you will get support for the
745 Epson RTC-9701JE SPI RTC chip.
747 This driver can also be built as a module. If so, the module
748 will be called rtc-r9701.
750 config RTC_DRV_RX4581
751 tristate "Epson RX-4581"
753 If you say yes here you will get support for the Epson RX-4581.
755 This driver can also be built as a module. If so the module
756 will be called rtc-rx4581.
758 config RTC_DRV_RX6110
759 tristate "Epson RX-6110"
762 If you say yes here you will get support for the Epson RX-6610.
764 This driver can also be built as a module. If so the module
765 will be called rtc-rx6110.
767 config RTC_DRV_RS5C348
768 tristate "Ricoh RS5C348A/B"
770 If you say yes here you get support for the
771 Ricoh RS5C348A and RS5C348B RTC chips.
773 This driver can also be built as a module. If so, the module
774 will be called rtc-rs5c348.
776 config RTC_DRV_MAX6902
777 tristate "Maxim MAX6902"
779 If you say yes here you will get support for the
780 Maxim MAX6902 SPI RTC chip.
782 This driver can also be built as a module. If so, the module
783 will be called rtc-max6902.
785 config RTC_DRV_PCF2123
786 tristate "NXP PCF2123"
788 If you say yes here you get support for the NXP PCF2123
791 This driver can also be built as a module. If so, the module
792 will be called rtc-pcf2123.
794 config RTC_DRV_MCP795
795 tristate "Microchip MCP795"
797 If you say yes here you will get support for the Microchip MCP795.
799 This driver can also be built as a module. If so the module
800 will be called rtc-mcp795.
805 # Helper to resolve issues with configs that have SPI enabled but I2C
806 # modular. See SND_SOC_I2C_AND_SPI for more information
808 config RTC_I2C_AND_SPI
812 default y if SPI_MASTER=y
813 select REGMAP_I2C if I2C
814 select REGMAP_SPI if SPI_MASTER
816 comment "SPI and I2C RTC drivers"
818 config RTC_DRV_DS3232
819 tristate "Dallas/Maxim DS3232/DS3234"
820 depends on RTC_I2C_AND_SPI
822 If you say yes here you get support for Dallas Semiconductor
823 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
824 with the device, the alarm functionality is supported.
826 This driver can also be built as a module. If so, the module
827 will be called rtc-ds3232.
829 config RTC_DRV_DS3232_HWMON
830 bool "HWMON support for Dallas/Maxim DS3232/DS3234"
831 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
834 Say Y here if you want to expose temperature sensor data on
837 config RTC_DRV_PCF2127
838 tristate "NXP PCF2127"
839 depends on RTC_I2C_AND_SPI
841 If you say yes here you get support for the NXP PCF2127/29 RTC
844 This driver can also be built as a module. If so, the module
845 will be called rtc-pcf2127.
847 config RTC_DRV_RV3029C2
848 tristate "Micro Crystal RV3029/3049"
849 depends on RTC_I2C_AND_SPI
851 If you say yes here you get support for the Micro Crystal
852 RV3029 and RV3049 RTC chips.
854 This driver can also be built as a module. If so, the module
855 will be called rtc-rv3029c2.
857 config RTC_DRV_RV3029_HWMON
858 bool "HWMON support for RV3029/3049"
859 depends on RTC_DRV_RV3029C2 && HWMON
860 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
863 Say Y here if you want to expose temperature sensor data on
866 comment "Platform RTC drivers"
868 # this 'CMOS' RTC driver is arch dependent because it requires
869 # <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
870 # global rtc_lock ... it's not yet just another platform_device.
873 tristate "PC-style 'CMOS'"
874 depends on X86 || ARM || PPC || MIPS || SPARC64
876 select RTC_MC146818_LIB
878 Say "yes" here to get direct support for the real time clock
879 found in every PC or ACPI-based system, and some other boards.
880 Specifically the original MC146818, compatibles like those in
881 PC south bridges, the DS12887 or M48T86, some multifunction
882 or LPC bus chips, and so on.
884 Your system will need to define the platform device used by
885 this driver, otherwise it won't be accessible. This means
886 you can safely enable this driver if you don't know whether
887 or not your board has this kind of hardware.
889 This driver can also be built as a module. If so, the module
890 will be called rtc-cmos.
893 bool "Alpha PC-style CMOS"
895 select RTC_MC146818_LIB
898 Direct support for the real-time clock found on every Alpha
899 system, specifically MC146818 compatibles. If in doubt, say Y.
902 tristate "Virtual RTC for Intel MID platforms"
903 depends on X86_INTEL_MID
904 default y if X86_INTEL_MID
907 Say "yes" here to get direct support for the real time clock
908 found on Moorestown platforms. The VRTC is a emulated RTC that
909 derives its clock source from a real RTC in the PMIC. The MC146818
910 style programming interface is mostly conserved, but any
911 updates are done via IPC calls to the system controller FW.
913 config RTC_DRV_DS1216
914 tristate "Dallas DS1216"
917 If you say yes here you get support for the Dallas DS1216 RTC chips.
919 config RTC_DRV_DS1286
920 tristate "Dallas DS1286"
923 If you say yes here you get support for the Dallas DS1286 RTC chips.
925 config RTC_DRV_DS1511
926 tristate "Dallas DS1511"
929 If you say yes here you get support for the
930 Dallas DS1511 timekeeping/watchdog chip.
932 This driver can also be built as a module. If so, the module
933 will be called rtc-ds1511.
935 config RTC_DRV_DS1553
936 tristate "Maxim/Dallas DS1553"
939 If you say yes here you get support for the
940 Maxim/Dallas DS1553 timekeeping chip.
942 This driver can also be built as a module. If so, the module
943 will be called rtc-ds1553.
945 config RTC_DRV_DS1685_FAMILY
946 tristate "Dallas/Maxim DS1685 Family"
948 If you say yes here you get support for the Dallas/Maxim DS1685
949 family of real time chips. This family includes the DS1685/DS1687,
950 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
951 DS17885/DS17887 chips.
953 This driver can also be built as a module. If so, the module
954 will be called rtc-ds1685.
958 depends on RTC_DRV_DS1685_FAMILY
959 default RTC_DRV_DS1685
961 config RTC_DRV_DS1685
964 This enables support for the Dallas/Maxim DS1685/DS1687 real time
967 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
968 systems, as well as EPPC-405-UC modules by electronic system design
971 config RTC_DRV_DS1689
974 This enables support for the Dallas/Maxim DS1689/DS1693 real time
977 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
978 which supports a few minor features such as Vcc, Vbat, and Power
979 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
981 It also works for the even older DS1688/DS1691 RTC chips, which are
982 virtually the same and carry the same model number. Both chips
983 have 114 bytes of user NVRAM.
985 config RTC_DRV_DS17285
986 bool "DS17285/DS17287"
988 This enables support for the Dallas/Maxim DS17285/DS17287 real time
991 This chip features 2kb of extended NV-SRAM. It may possibly be
992 found in some SGI O2 systems (rare).
994 config RTC_DRV_DS17485
995 bool "DS17485/DS17487"
997 This enables support for the Dallas/Maxim DS17485/DS17487 real time
1000 This chip features 4kb of extended NV-SRAM.
1002 config RTC_DRV_DS17885
1003 bool "DS17885/DS17887"
1005 This enables support for the Dallas/Maxim DS17885/DS17887 real time
1008 This chip features 8kb of extended NV-SRAM.
1012 config RTC_DS1685_PROC_REGS
1013 bool "Display register values in /proc"
1014 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
1016 Enable this to display a readout of all of the RTC registers in
1017 /proc/drivers/rtc. Keep in mind that this can potentially lead
1018 to lost interrupts, as reading Control Register C will clear
1019 all pending IRQ flags.
1021 Unless you are debugging this driver, choose N.
1023 config RTC_DRV_DS1742
1024 tristate "Maxim/Dallas DS1742/1743"
1025 depends on HAS_IOMEM
1027 If you say yes here you get support for the
1028 Maxim/Dallas DS1742/1743 timekeeping chip.
1030 This driver can also be built as a module. If so, the module
1031 will be called rtc-ds1742.
1033 config RTC_DRV_DS2404
1034 tristate "Maxim/Dallas DS2404"
1036 If you say yes here you get support for the
1037 Dallas DS2404 RTC chip.
1039 This driver can also be built as a module. If so, the module
1040 will be called rtc-ds2404.
1042 config RTC_DRV_DA9052
1043 tristate "Dialog DA9052/DA9053 RTC"
1044 depends on PMIC_DA9052
1046 Say y here to support the RTC driver for Dialog Semiconductor
1047 DA9052-BC and DA9053-AA/Bx PMICs.
1049 config RTC_DRV_DA9055
1050 tristate "Dialog Semiconductor DA9055 RTC"
1051 depends on MFD_DA9055
1053 If you say yes here you will get support for the
1054 RTC of the Dialog DA9055 PMIC.
1056 This driver can also be built as a module. If so, the module
1057 will be called rtc-da9055
1059 config RTC_DRV_DA9063
1060 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1061 depends on MFD_DA9063 || MFD_DA9062
1063 If you say yes here you will get support for the RTC subsystem
1064 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1066 This driver can also be built as a module. If so, the module
1067 will be called "rtc-da9063".
1071 depends on EFI && !X86
1073 If you say yes here you will get support for the EFI
1076 This driver can also be built as a module. If so, the module
1077 will be called rtc-efi.
1079 config RTC_DRV_STK17TA8
1080 tristate "Simtek STK17TA8"
1081 depends on HAS_IOMEM
1083 If you say yes here you get support for the
1084 Simtek STK17TA8 timekeeping chip.
1086 This driver can also be built as a module. If so, the module
1087 will be called rtc-stk17ta8.
1089 config RTC_DRV_M48T86
1090 tristate "ST M48T86/Dallas DS12887"
1092 If you say Y here you will get support for the
1093 ST M48T86 and Dallas DS12887 RTC chips.
1095 This driver can also be built as a module. If so, the module
1096 will be called rtc-m48t86.
1098 config RTC_DRV_M48T35
1099 tristate "ST M48T35"
1100 depends on HAS_IOMEM
1102 If you say Y here you will get support for the
1105 This driver can also be built as a module, if so, the module
1106 will be called "rtc-m48t35".
1108 config RTC_DRV_M48T59
1109 tristate "ST M48T59/M48T08/M48T02"
1110 depends on HAS_IOMEM
1112 If you say Y here you will get support for the
1113 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1115 These chips are usually found in Sun SPARC and UltraSPARC
1118 This driver can also be built as a module, if so, the module
1119 will be called "rtc-m48t59".
1121 config RTC_DRV_MSM6242
1122 tristate "Oki MSM6242"
1123 depends on HAS_IOMEM
1125 If you say yes here you get support for the Oki MSM6242
1126 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1128 This driver can also be built as a module. If so, the module
1129 will be called rtc-msm6242.
1131 config RTC_DRV_BQ4802
1132 tristate "TI BQ4802"
1133 depends on HAS_IOMEM
1135 If you say Y here you will get support for the TI
1138 This driver can also be built as a module. If so, the module
1139 will be called rtc-bq4802.
1141 config RTC_DRV_RP5C01
1142 tristate "Ricoh RP5C01"
1143 depends on HAS_IOMEM
1145 If you say yes here you get support for the Ricoh RP5C01
1146 timekeeping chip. It is used in some Amiga models (e.g. A3000
1149 This driver can also be built as a module. If so, the module
1150 will be called rtc-rp5c01.
1152 config RTC_DRV_V3020
1153 tristate "EM Microelectronic V3020"
1155 If you say yes here you will get support for the
1156 EM Microelectronic v3020 RTC chip.
1158 This driver can also be built as a module. If so, the module
1159 will be called rtc-v3020.
1161 config RTC_DRV_WM831X
1162 tristate "Wolfson Microelectronics WM831x RTC"
1163 depends on MFD_WM831X
1165 If you say yes here you will get support for the RTC subsystem
1166 of the Wolfson Microelectronics WM831X series PMICs.
1168 This driver can also be built as a module. If so, the module
1169 will be called "rtc-wm831x".
1171 config RTC_DRV_WM8350
1172 tristate "Wolfson Microelectronics WM8350 RTC"
1173 depends on MFD_WM8350
1175 If you say yes here you will get support for the RTC subsystem
1176 of the Wolfson Microelectronics WM8350.
1178 This driver can also be built as a module. If so, the module
1179 will be called "rtc-wm8350".
1181 config RTC_DRV_SC27XX
1182 tristate "Spreadtrum SC27xx RTC"
1183 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1185 If you say Y here you will get support for the RTC subsystem
1186 of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs
1187 includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips.
1189 This driver can also be built as a module. If so, the module
1190 will be called rtc-sc27xx.
1192 config RTC_DRV_SPEAR
1193 tristate "SPEAR ST RTC"
1194 depends on PLAT_SPEAR || COMPILE_TEST
1197 If you say Y here you will get support for the RTC found on
1200 config RTC_DRV_PCF50633
1201 depends on MFD_PCF50633
1202 tristate "NXP PCF50633 RTC"
1204 If you say yes here you get support for the RTC subsystem of the
1205 NXP PCF50633 used in embedded systems.
1207 config RTC_DRV_AB3100
1208 tristate "ST-Ericsson AB3100 RTC"
1209 depends on AB3100_CORE
1210 default y if AB3100_CORE
1212 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1213 support. This chip contains a battery- and capacitor-backed RTC.
1215 config RTC_DRV_AB8500
1216 tristate "ST-Ericsson AB8500 RTC"
1217 depends on AB8500_CORE
1219 select RTC_INTF_DEV_UIE_EMUL
1221 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1222 support. This chip contains a battery- and capacitor-backed RTC.
1224 config RTC_DRV_NUC900
1225 tristate "NUC910/NUC920 RTC driver"
1226 depends on ARCH_W90X900 || COMPILE_TEST
1228 If you say yes here you get support for the RTC subsystem of the
1229 NUC910/NUC920 used in embedded systems.
1232 tristate "IBM OPAL RTC driver"
1233 depends on PPC_POWERNV
1236 If you say yes here you get support for the PowerNV platform RTC
1237 driver based on OPAL interfaces.
1239 This driver can also be built as a module. If so, the module
1240 will be called rtc-opal.
1242 config RTC_DRV_ZYNQMP
1243 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1246 If you say yes here you get support for the RTC controller found on
1247 Xilinx Zynq Ultrascale+ MPSoC.
1249 config RTC_DRV_CROS_EC
1250 tristate "Chrome OS EC RTC driver"
1251 depends on MFD_CROS_EC
1253 If you say yes here you will get support for the
1254 Chrome OS Embedded Controller's RTC.
1256 This driver can also be built as a module. If so, the module
1257 will be called rtc-cros-ec.
1259 comment "on-CPU RTC drivers"
1261 config RTC_DRV_ASM9260
1262 tristate "Alphascale asm9260 RTC"
1263 depends on MACH_ASM9260 || COMPILE_TEST
1265 If you say yes here you get support for the RTC on the
1266 Alphascale asm9260 SoC.
1268 This driver can also be built as a module. If so, the module
1269 will be called rtc-asm9260.
1271 config RTC_DRV_DAVINCI
1272 tristate "TI DaVinci RTC"
1273 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1275 If you say yes here you get support for the RTC on the
1276 DaVinci platforms (DM365).
1278 This driver can also be built as a module. If so, the module
1279 will be called rtc-davinci.
1281 config RTC_DRV_DIGICOLOR
1282 tristate "Conexant Digicolor RTC"
1283 depends on ARCH_DIGICOLOR || COMPILE_TEST
1285 If you say yes here you get support for the RTC on Conexant
1286 Digicolor platforms. This currently includes the CX92755 SoC.
1288 This driver can also be built as a module. If so, the module
1289 will be called rtc-digicolor.
1291 config RTC_DRV_IMXDI
1292 tristate "Freescale IMX DryIce Real Time Clock"
1295 Support for Freescale IMX DryIce RTC
1297 This driver can also be built as a module, if so, the module
1298 will be called "rtc-imxdi".
1301 tristate "TI OMAP Real Time Clock"
1302 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1305 select GENERIC_PINCONF
1307 Say "yes" here to support the on chip real time clock
1308 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1310 This driver can also be built as a module, if so, module
1311 will be called rtc-omap.
1316 This will include RTC support for Samsung SoCs. If
1317 you want to include RTC support for any machine, kindly
1318 select this in the respective mach-XXXX/Kconfig file.
1321 tristate "Samsung S3C series SoC RTC"
1322 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1324 RTC (Realtime Clock) driver for the clock inbuilt into the
1325 Samsung S3C24XX series of SoCs. This can provide periodic
1326 interrupt rates from 1Hz to 64Hz for user programs, and
1329 The driver currently supports the common features on all the
1330 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1333 This driver can also be build as a module. If so, the module
1334 will be called rtc-s3c.
1336 config RTC_DRV_EP93XX
1337 tristate "Cirrus Logic EP93XX"
1338 depends on ARCH_EP93XX || COMPILE_TEST
1340 If you say yes here you get support for the
1341 RTC embedded in the Cirrus Logic EP93XX processors.
1343 This driver can also be built as a module. If so, the module
1344 will be called rtc-ep93xx.
1346 config RTC_DRV_SA1100
1347 tristate "SA11x0/PXA2xx/PXA910"
1348 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1350 If you say Y here you will get access to the real time clock
1351 built into your SA11x0 or PXA2xx CPU.
1353 To compile this driver as a module, choose M here: the
1354 module will be called rtc-sa1100.
1357 tristate "SuperH On-Chip RTC"
1358 depends on SUPERH || ARCH_RENESAS
1360 Say Y here to enable support for the on-chip RTC found in
1361 most SuperH processors. This RTC is also found in RZ/A SoCs.
1363 To compile this driver as a module, choose M here: the
1364 module will be called rtc-sh.
1366 config RTC_DRV_VR41XX
1367 tristate "NEC VR41XX"
1368 depends on CPU_VR41XX || COMPILE_TEST
1370 If you say Y here you will get access to the real time clock
1371 built into your NEC VR41XX CPU.
1373 To compile this driver as a module, choose M here: the
1374 module will be called rtc-vr41xx.
1376 config RTC_DRV_PL030
1377 tristate "ARM AMBA PL030 RTC"
1380 If you say Y here you will get access to ARM AMBA
1381 PrimeCell PL030 RTC found on certain ARM SOCs.
1383 To compile this driver as a module, choose M here: the
1384 module will be called rtc-pl030.
1386 config RTC_DRV_PL031
1387 tristate "ARM AMBA PL031 RTC"
1390 If you say Y here you will get access to ARM AMBA
1391 PrimeCell PL031 RTC found on certain ARM SOCs.
1393 To compile this driver as a module, choose M here: the
1394 module will be called rtc-pl031.
1396 config RTC_DRV_AT91RM9200
1397 tristate "AT91RM9200 or some AT91SAM9 RTC"
1398 depends on ARCH_AT91 || COMPILE_TEST
1400 Driver for the internal RTC (Realtime Clock) module found on
1401 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1402 this is powered by the backup power supply.
1404 config RTC_DRV_AT91SAM9
1405 tristate "AT91SAM9 RTT as RTC"
1406 depends on ARCH_AT91 || COMPILE_TEST
1407 depends on HAS_IOMEM
1410 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1411 can be used as an RTC thanks to the backup power supply (e.g. a
1412 small coin cell battery) which keeps this block and the GPBR
1413 (General Purpose Backup Registers) block powered when the device
1415 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1416 probably want to use the real RTC block instead of the "RTT as an
1419 config RTC_DRV_AU1XXX
1420 tristate "Au1xxx Counter0 RTC support"
1421 depends on MIPS_ALCHEMY
1423 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1424 counter) to be used as a RTC.
1426 This driver can also be built as a module. If so, the module
1427 will be called rtc-au1xxx.
1429 config RTC_DRV_RS5C313
1430 tristate "Ricoh RS5C313"
1431 depends on SH_LANDISK
1433 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1435 config RTC_DRV_GENERIC
1436 tristate "Generic RTC support"
1437 # Please consider writing a new RTC driver instead of using the generic
1439 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
1441 Say Y or M here to enable RTC support on systems using the generic
1442 RTC abstraction. If you do not know what you are doing, you should
1446 tristate "PXA27x/PXA3xx"
1448 select RTC_DRV_SA1100
1450 If you say Y here you will get access to the real time clock
1451 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1452 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1454 This RTC driver uses PXA RTC registers available since pxa27x
1455 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1457 config RTC_DRV_VT8500
1458 tristate "VIA/WonderMedia 85xx SoC RTC"
1459 depends on ARCH_VT8500 || COMPILE_TEST
1461 If you say Y here you will get access to the real time clock
1462 built into your VIA VT8500 SoC or its relatives.
1465 config RTC_DRV_SUN4V
1466 bool "SUN4V Hypervisor RTC"
1469 If you say Y here you will get support for the Hypervisor
1470 based RTC on SUN4V systems.
1472 config RTC_DRV_SUN6I
1473 bool "Allwinner A31 RTC"
1474 default MACH_SUN6I || MACH_SUN8I
1475 depends on COMMON_CLK
1476 depends on ARCH_SUNXI || COMPILE_TEST
1478 If you say Y here you will get support for the RTC found in
1479 some Allwinner SoCs like the A31 or the A64.
1481 config RTC_DRV_SUNXI
1482 tristate "Allwinner sun4i/sun7i RTC"
1483 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1485 If you say Y here you will get support for the RTC found on
1488 config RTC_DRV_STARFIRE
1492 If you say Y here you will get support for the RTC found on
1495 config RTC_DRV_TX4939
1496 tristate "TX4939 SoC"
1497 depends on SOC_TX4939 || COMPILE_TEST
1499 Driver for the internal RTC (Realtime Clock) module found on
1503 tristate "Marvell SoC RTC"
1504 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1506 If you say yes here you will get support for the in-chip RTC
1507 that can be found in some of Marvell's SoC devices, such as
1508 the Kirkwood 88F6281 and 88F6192.
1510 This driver can also be built as a module. If so, the module
1511 will be called rtc-mv.
1513 config RTC_DRV_ARMADA38X
1514 tristate "Armada 38x Marvell SoC RTC"
1515 depends on ARCH_MVEBU || COMPILE_TEST
1517 If you say yes here you will get support for the in-chip RTC
1518 that can be found in the Armada 38x Marvell's SoC device
1520 This driver can also be built as a module. If so, the module
1521 will be called armada38x-rtc.
1523 config RTC_DRV_FTRTC010
1524 tristate "Faraday Technology FTRTC010 RTC"
1525 depends on HAS_IOMEM
1528 If you say Y here you will get support for the
1529 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1531 This driver can also be built as a module. If so, the module
1532 will be called rtc-ftrtc010.
1538 If you say yes here you will get support for the RTC on PS3.
1540 This driver can also be built as a module. If so, the module
1541 will be called rtc-ps3.
1543 config RTC_DRV_COH901331
1544 tristate "ST-Ericsson COH 901 331 RTC"
1545 depends on ARCH_U300 || COMPILE_TEST
1547 If you say Y here you will get access to ST-Ericsson
1548 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1551 This driver can also be built as a module. If so, the module
1552 will be called "rtc-coh901331".
1556 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1557 depends on ARCH_MXS || COMPILE_TEST
1560 If you say yes here you will get support for the onboard
1561 STMP3xxx/i.MX23/i.MX28 RTC.
1563 This driver can also be built as a module. If so, the module
1564 will be called rtc-stmp3xxx.
1570 If you say Y here you will get support for the RTC found on
1571 the PCAP2 ASIC used on some Motorola phones.
1573 config RTC_DRV_MC13XXX
1574 depends on MFD_MC13XXX
1575 tristate "Freescale MC13xxx RTC"
1577 This enables support for the RTCs found on Freescale's PMICs
1578 MC13783 and MC13892.
1580 config RTC_DRV_MPC5121
1581 tristate "Freescale MPC5121 built-in RTC"
1582 depends on PPC_MPC512x || PPC_MPC52xx
1584 If you say yes here you will get support for the
1585 built-in RTC on MPC5121 or on MPC5200.
1587 This driver can also be built as a module. If so, the module
1588 will be called rtc-mpc5121.
1590 config RTC_DRV_JZ4740
1591 tristate "Ingenic JZ4740 SoC"
1592 depends on MACH_INGENIC || COMPILE_TEST
1594 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1597 This driver can also be built as a module. If so, the module
1598 will be called rtc-jz4740.
1600 config RTC_DRV_LPC24XX
1601 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1602 depends on ARCH_LPC18XX || COMPILE_TEST
1603 depends on OF && HAS_IOMEM
1605 This enables support for the NXP RTC found which can be found on
1606 NXP LPC178x/18xx/408x/43xx devices.
1608 If you have one of the devices above enable this driver to use
1609 the hardware RTC. This driver can also be built as a module. If
1610 so, the module will be called rtc-lpc24xx.
1612 config RTC_DRV_LPC32XX
1613 depends on ARCH_LPC32XX || COMPILE_TEST
1614 tristate "NXP LPC32XX RTC"
1616 This enables support for the NXP RTC in the LPC32XX
1618 This driver can also be built as a module. If so, the module
1619 will be called rtc-lpc32xx.
1621 config RTC_DRV_PM8XXX
1622 tristate "Qualcomm PMIC8XXX RTC"
1623 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1625 If you say yes here you get support for the
1626 Qualcomm PMIC8XXX RTC.
1628 To compile this driver as a module, choose M here: the
1629 module will be called rtc-pm8xxx.
1631 config RTC_DRV_TEGRA
1632 tristate "NVIDIA Tegra Internal RTC driver"
1633 depends on ARCH_TEGRA || COMPILE_TEST
1635 If you say yes here you get support for the
1636 Tegra 200 series internal RTC module.
1638 This drive can also be built as a module. If so, the module
1639 will be called rtc-tegra.
1642 tristate "PKUnity v3 RTC support"
1643 depends on ARCH_PUV3
1645 This enables support for the RTC in the PKUnity-v3 SoCs.
1647 This drive can also be built as a module. If so, the module
1648 will be called rtc-puv3.
1650 config RTC_DRV_LOONGSON1
1651 tristate "loongson1 RTC support"
1652 depends on MACH_LOONGSON32
1654 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1655 counter) to be used as a RTC.
1657 This driver can also be built as a module. If so, the module
1658 will be called rtc-ls1x.
1661 tristate "Freescale MXC Real Time Clock"
1664 If you say yes here you get support for the Freescale MXC
1667 This driver can also be built as a module, if so, the module
1668 will be called "rtc-mxc".
1670 config RTC_DRV_MXC_V2
1671 tristate "Freescale MXC Real Time Clock for i.MX53"
1674 If you say yes here you get support for the Freescale MXC
1675 SRTC module in i.MX53 processor.
1677 This driver can also be built as a module, if so, the module
1678 will be called "rtc-mxc_v2".
1681 tristate "Freescale SNVS RTC support"
1683 depends on HAS_IOMEM
1686 If you say yes here you get support for the Freescale SNVS
1687 Low Power (LP) RTC module.
1689 This driver can also be built as a module, if so, the module
1690 will be called "rtc-snvs".
1692 config RTC_DRV_SIRFSOC
1693 tristate "SiRFSOC RTC"
1694 depends on ARCH_SIRF
1696 Say "yes" here to support the real time clock on SiRF SOC chips.
1697 This driver can also be built as a module called rtc-sirfsoc.
1699 config RTC_DRV_ST_LPC
1700 tristate "STMicroelectronics LPC RTC"
1704 Say Y here to include STMicroelectronics Low Power Controller
1705 (LPC) based RTC support.
1707 To compile this driver as a module, choose M here: the
1708 module will be called rtc-st-lpc.
1710 config RTC_DRV_MOXART
1711 tristate "MOXA ART RTC"
1712 depends on ARCH_MOXART || COMPILE_TEST
1714 If you say yes here you get support for the MOXA ART
1717 This driver can also be built as a module. If so, the module
1718 will be called rtc-moxart
1720 config RTC_DRV_MT6397
1721 tristate "MediaTek PMIC based RTC"
1722 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1724 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1725 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1726 MediaTek(R) RTC driver.
1728 If you want to use MediaTek(R) RTC interface, select Y or M here.
1730 config RTC_DRV_MT7622
1731 tristate "MediaTek SoC based RTC"
1732 depends on ARCH_MEDIATEK || COMPILE_TEST
1734 This enables support for the real time clock built in the MediaTek
1737 This drive can also be built as a module. If so, the module
1738 will be called rtc-mt7622.
1740 config RTC_DRV_XGENE
1741 tristate "APM X-Gene RTC"
1742 depends on HAS_IOMEM
1743 depends on ARCH_XGENE || COMPILE_TEST
1745 If you say yes here you get support for the APM X-Gene SoC real time
1748 This driver can also be built as a module, if so, the module
1749 will be called "rtc-xgene".
1751 config RTC_DRV_PIC32
1752 tristate "Microchip PIC32 RTC"
1753 depends on MACH_PIC32
1756 If you say yes here you get support for the PIC32 RTC module.
1758 This driver can also be built as a module. If so, the module
1759 will be called rtc-pic32
1761 config RTC_DRV_R7301
1762 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1764 depends on OF && HAS_IOMEM
1766 If you say yes here you get support for the EPSON TOYOCOM
1767 RTC-7301SF/DG chips.
1769 This driver can also be built as a module. If so, the module
1770 will be called rtc-r7301.
1772 config RTC_DRV_STM32
1773 tristate "STM32 RTC"
1775 depends on ARCH_STM32 || COMPILE_TEST
1777 If you say yes here you get support for the STM32 On-Chip
1780 This driver can also be built as a module, if so, the module
1781 will be called "rtc-stm32".
1783 config RTC_DRV_CPCAP
1784 depends on MFD_CPCAP
1785 tristate "Motorola CPCAP RTC"
1787 Say y here for CPCAP rtc found on some Motorola phones
1788 and tablets such as Droid 4.
1790 config RTC_DRV_RTD119X
1791 bool "Realtek RTD129x RTC"
1792 depends on ARCH_REALTEK || COMPILE_TEST
1793 default ARCH_REALTEK
1795 If you say yes here, you get support for the RTD1295 SoC
1798 comment "HID Sensor RTC drivers"
1800 config RTC_DRV_HID_SENSOR_TIME
1801 tristate "HID Sensor Time"
1804 select HID_SENSOR_HUB
1805 select HID_SENSOR_IIO_COMMON
1807 Say yes here to build support for the HID Sensors of type Time.
1808 This drivers makes such sensors available as RTCs.
1810 If this driver is compiled as a module, it will be named
1811 rtc-hid-sensor-time.
1813 config RTC_DRV_GOLDFISH
1814 tristate "Goldfish Real Time Clock"
1815 depends on MIPS && (GOLDFISH || COMPILE_TEST)
1817 Say yes to enable RTC driver for the Goldfish based virtual platform.
1819 Goldfish is a code name for the virtual platform developed by Google
1820 for Android emulation.