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
643 If you say yes here you will get support for the
644 RTC of Samsung S2MPS14 and S5M PMIC series.
646 This driver can also be built as a module. If so, the module
647 will be called rtc-s5m.
651 comment "SPI RTC drivers"
655 config RTC_DRV_M41T93
658 If you say yes here you will get support for the
659 ST M41T93 SPI RTC chip.
661 This driver can also be built as a module. If so, the module
662 will be called rtc-m41t93.
664 config RTC_DRV_M41T94
667 If you say yes here you will get support for the
668 ST M41T94 SPI RTC chip.
670 This driver can also be built as a module. If so, the module
671 will be called rtc-m41t94.
673 config RTC_DRV_DS1302
674 tristate "Dallas/Maxim DS1302"
677 If you say yes here you get support for the Dallas DS1302 RTC chips.
679 This driver can also be built as a module. If so, the module
680 will be called rtc-ds1302.
682 config RTC_DRV_DS1305
683 tristate "Dallas/Maxim DS1305/DS1306"
685 Select this driver to get support for the Dallas/Maxim DS1305
686 and DS1306 real time clock chips. These support a trickle
687 charger, alarms, and NVRAM in addition to the clock.
689 This driver can also be built as a module. If so, the module
690 will be called rtc-ds1305.
692 config RTC_DRV_DS1343
694 tristate "Dallas/Maxim DS1343/DS1344"
696 If you say yes here you get support for the
697 Dallas/Maxim DS1343 and DS1344 real time clock chips.
698 Support for trickle charger, alarm is provided.
700 This driver can also be built as a module. If so, the module
701 will be called rtc-ds1343.
703 config RTC_DRV_DS1347
705 tristate "Dallas/Maxim DS1347"
707 If you say yes here you get support for the
708 Dallas/Maxim DS1347 chips.
710 This driver only supports the RTC feature, and not other chip
711 features such as alarms.
713 This driver can also be built as a module. If so, the module
714 will be called rtc-ds1347.
716 config RTC_DRV_DS1390
717 tristate "Dallas/Maxim DS1390/93/94"
719 If you say yes here you get support for the
720 Dallas/Maxim DS1390/93/94 chips.
722 This driver supports the RTC feature and trickle charging but not
723 other chip features such as alarms.
725 This driver can also be built as a module. If so, the module
726 will be called rtc-ds1390.
728 config RTC_DRV_MAX6916
729 tristate "Maxim MAX6916"
731 If you say yes here you will get support for the
732 Maxim MAX6916 SPI RTC chip.
734 This driver only supports the RTC feature, and not other chip
735 features such as alarms.
737 This driver can also be built as a module. If so, the module
738 will be called rtc-max6916.
741 tristate "Epson RTC-9701JE"
743 If you say yes here you will get support for the
744 Epson RTC-9701JE SPI RTC chip.
746 This driver can also be built as a module. If so, the module
747 will be called rtc-r9701.
749 config RTC_DRV_RX4581
750 tristate "Epson RX-4581"
752 If you say yes here you will get support for the Epson RX-4581.
754 This driver can also be built as a module. If so the module
755 will be called rtc-rx4581.
757 config RTC_DRV_RX6110
758 tristate "Epson RX-6110"
761 If you say yes here you will get support for the Epson RX-6610.
763 This driver can also be built as a module. If so the module
764 will be called rtc-rx6110.
766 config RTC_DRV_RS5C348
767 tristate "Ricoh RS5C348A/B"
769 If you say yes here you get support for the
770 Ricoh RS5C348A and RS5C348B RTC chips.
772 This driver can also be built as a module. If so, the module
773 will be called rtc-rs5c348.
775 config RTC_DRV_MAX6902
776 tristate "Maxim MAX6902"
778 If you say yes here you will get support for the
779 Maxim MAX6902 SPI RTC chip.
781 This driver can also be built as a module. If so, the module
782 will be called rtc-max6902.
784 config RTC_DRV_PCF2123
785 tristate "NXP PCF2123"
787 If you say yes here you get support for the NXP PCF2123
790 This driver can also be built as a module. If so, the module
791 will be called rtc-pcf2123.
793 config RTC_DRV_MCP795
794 tristate "Microchip MCP795"
796 If you say yes here you will get support for the Microchip MCP795.
798 This driver can also be built as a module. If so the module
799 will be called rtc-mcp795.
804 # Helper to resolve issues with configs that have SPI enabled but I2C
805 # modular. See SND_SOC_I2C_AND_SPI for more information
807 config RTC_I2C_AND_SPI
811 default y if SPI_MASTER=y
812 select REGMAP_I2C if I2C
813 select REGMAP_SPI if SPI_MASTER
815 comment "SPI and I2C RTC drivers"
817 config RTC_DRV_DS3232
818 tristate "Dallas/Maxim DS3232/DS3234"
819 depends on RTC_I2C_AND_SPI
821 If you say yes here you get support for Dallas Semiconductor
822 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
823 with the device, the alarm functionality is supported.
825 This driver can also be built as a module. If so, the module
826 will be called rtc-ds3232.
828 config RTC_DRV_DS3232_HWMON
829 bool "HWMON support for Dallas/Maxim DS3232/DS3234"
830 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
833 Say Y here if you want to expose temperature sensor data on
836 config RTC_DRV_PCF2127
837 tristate "NXP PCF2127"
838 depends on RTC_I2C_AND_SPI
840 If you say yes here you get support for the NXP PCF2127/29 RTC
843 This driver can also be built as a module. If so, the module
844 will be called rtc-pcf2127.
846 config RTC_DRV_RV3029C2
847 tristate "Micro Crystal RV3029/3049"
848 depends on RTC_I2C_AND_SPI
850 If you say yes here you get support for the Micro Crystal
851 RV3029 and RV3049 RTC chips.
853 This driver can also be built as a module. If so, the module
854 will be called rtc-rv3029c2.
856 config RTC_DRV_RV3029_HWMON
857 bool "HWMON support for RV3029/3049"
858 depends on RTC_DRV_RV3029C2 && HWMON
859 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
862 Say Y here if you want to expose temperature sensor data on
865 comment "Platform RTC drivers"
867 # this 'CMOS' RTC driver is arch dependent because it requires
868 # <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
869 # global rtc_lock ... it's not yet just another platform_device.
872 tristate "PC-style 'CMOS'"
873 depends on X86 || ARM || PPC || MIPS || SPARC64
875 select RTC_MC146818_LIB
877 Say "yes" here to get direct support for the real time clock
878 found in every PC or ACPI-based system, and some other boards.
879 Specifically the original MC146818, compatibles like those in
880 PC south bridges, the DS12887 or M48T86, some multifunction
881 or LPC bus chips, and so on.
883 Your system will need to define the platform device used by
884 this driver, otherwise it won't be accessible. This means
885 you can safely enable this driver if you don't know whether
886 or not your board has this kind of hardware.
888 This driver can also be built as a module. If so, the module
889 will be called rtc-cmos.
892 bool "Alpha PC-style CMOS"
894 select RTC_MC146818_LIB
897 Direct support for the real-time clock found on every Alpha
898 system, specifically MC146818 compatibles. If in doubt, say Y.
901 tristate "Virtual RTC for Intel MID platforms"
902 depends on X86_INTEL_MID
903 default y if X86_INTEL_MID
906 Say "yes" here to get direct support for the real time clock
907 found on Moorestown platforms. The VRTC is a emulated RTC that
908 derives its clock source from a real RTC in the PMIC. The MC146818
909 style programming interface is mostly conserved, but any
910 updates are done via IPC calls to the system controller FW.
912 config RTC_DRV_DS1216
913 tristate "Dallas DS1216"
916 If you say yes here you get support for the Dallas DS1216 RTC chips.
918 config RTC_DRV_DS1286
919 tristate "Dallas DS1286"
922 If you say yes here you get support for the Dallas DS1286 RTC chips.
924 config RTC_DRV_DS1511
925 tristate "Dallas DS1511"
928 If you say yes here you get support for the
929 Dallas DS1511 timekeeping/watchdog chip.
931 This driver can also be built as a module. If so, the module
932 will be called rtc-ds1511.
934 config RTC_DRV_DS1553
935 tristate "Maxim/Dallas DS1553"
938 If you say yes here you get support for the
939 Maxim/Dallas DS1553 timekeeping chip.
941 This driver can also be built as a module. If so, the module
942 will be called rtc-ds1553.
944 config RTC_DRV_DS1685_FAMILY
945 tristate "Dallas/Maxim DS1685 Family"
947 If you say yes here you get support for the Dallas/Maxim DS1685
948 family of real time chips. This family includes the DS1685/DS1687,
949 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
950 DS17885/DS17887 chips.
952 This driver can also be built as a module. If so, the module
953 will be called rtc-ds1685.
957 depends on RTC_DRV_DS1685_FAMILY
958 default RTC_DRV_DS1685
960 config RTC_DRV_DS1685
963 This enables support for the Dallas/Maxim DS1685/DS1687 real time
966 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
967 systems, as well as EPPC-405-UC modules by electronic system design
970 config RTC_DRV_DS1689
973 This enables support for the Dallas/Maxim DS1689/DS1693 real time
976 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
977 which supports a few minor features such as Vcc, Vbat, and Power
978 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
980 It also works for the even older DS1688/DS1691 RTC chips, which are
981 virtually the same and carry the same model number. Both chips
982 have 114 bytes of user NVRAM.
984 config RTC_DRV_DS17285
985 bool "DS17285/DS17287"
987 This enables support for the Dallas/Maxim DS17285/DS17287 real time
990 This chip features 2kb of extended NV-SRAM. It may possibly be
991 found in some SGI O2 systems (rare).
993 config RTC_DRV_DS17485
994 bool "DS17485/DS17487"
996 This enables support for the Dallas/Maxim DS17485/DS17487 real time
999 This chip features 4kb of extended NV-SRAM.
1001 config RTC_DRV_DS17885
1002 bool "DS17885/DS17887"
1004 This enables support for the Dallas/Maxim DS17885/DS17887 real time
1007 This chip features 8kb of extended NV-SRAM.
1011 config RTC_DS1685_PROC_REGS
1012 bool "Display register values in /proc"
1013 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
1015 Enable this to display a readout of all of the RTC registers in
1016 /proc/drivers/rtc. Keep in mind that this can potentially lead
1017 to lost interrupts, as reading Control Register C will clear
1018 all pending IRQ flags.
1020 Unless you are debugging this driver, choose N.
1022 config RTC_DRV_DS1742
1023 tristate "Maxim/Dallas DS1742/1743"
1024 depends on HAS_IOMEM
1026 If you say yes here you get support for the
1027 Maxim/Dallas DS1742/1743 timekeeping chip.
1029 This driver can also be built as a module. If so, the module
1030 will be called rtc-ds1742.
1032 config RTC_DRV_DS2404
1033 tristate "Maxim/Dallas DS2404"
1035 If you say yes here you get support for the
1036 Dallas DS2404 RTC chip.
1038 This driver can also be built as a module. If so, the module
1039 will be called rtc-ds2404.
1041 config RTC_DRV_DA9052
1042 tristate "Dialog DA9052/DA9053 RTC"
1043 depends on PMIC_DA9052
1045 Say y here to support the RTC driver for Dialog Semiconductor
1046 DA9052-BC and DA9053-AA/Bx PMICs.
1048 config RTC_DRV_DA9055
1049 tristate "Dialog Semiconductor DA9055 RTC"
1050 depends on MFD_DA9055
1052 If you say yes here you will get support for the
1053 RTC of the Dialog DA9055 PMIC.
1055 This driver can also be built as a module. If so, the module
1056 will be called rtc-da9055
1058 config RTC_DRV_DA9063
1059 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1060 depends on MFD_DA9063 || MFD_DA9062
1062 If you say yes here you will get support for the RTC subsystem
1063 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1065 This driver can also be built as a module. If so, the module
1066 will be called "rtc-da9063".
1070 depends on EFI && !X86
1072 If you say yes here you will get support for the EFI
1075 This driver can also be built as a module. If so, the module
1076 will be called rtc-efi.
1078 config RTC_DRV_STK17TA8
1079 tristate "Simtek STK17TA8"
1080 depends on HAS_IOMEM
1082 If you say yes here you get support for the
1083 Simtek STK17TA8 timekeeping chip.
1085 This driver can also be built as a module. If so, the module
1086 will be called rtc-stk17ta8.
1088 config RTC_DRV_M48T86
1089 tristate "ST M48T86/Dallas DS12887"
1091 If you say Y here you will get support for the
1092 ST M48T86 and Dallas DS12887 RTC chips.
1094 This driver can also be built as a module. If so, the module
1095 will be called rtc-m48t86.
1097 config RTC_DRV_M48T35
1098 tristate "ST M48T35"
1099 depends on HAS_IOMEM
1101 If you say Y here you will get support for the
1104 This driver can also be built as a module, if so, the module
1105 will be called "rtc-m48t35".
1107 config RTC_DRV_M48T59
1108 tristate "ST M48T59/M48T08/M48T02"
1109 depends on HAS_IOMEM
1111 If you say Y here you will get support for the
1112 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1114 These chips are usually found in Sun SPARC and UltraSPARC
1117 This driver can also be built as a module, if so, the module
1118 will be called "rtc-m48t59".
1120 config RTC_DRV_MSM6242
1121 tristate "Oki MSM6242"
1122 depends on HAS_IOMEM
1124 If you say yes here you get support for the Oki MSM6242
1125 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1127 This driver can also be built as a module. If so, the module
1128 will be called rtc-msm6242.
1130 config RTC_DRV_BQ4802
1131 tristate "TI BQ4802"
1132 depends on HAS_IOMEM
1134 If you say Y here you will get support for the TI
1137 This driver can also be built as a module. If so, the module
1138 will be called rtc-bq4802.
1140 config RTC_DRV_RP5C01
1141 tristate "Ricoh RP5C01"
1142 depends on HAS_IOMEM
1144 If you say yes here you get support for the Ricoh RP5C01
1145 timekeeping chip. It is used in some Amiga models (e.g. A3000
1148 This driver can also be built as a module. If so, the module
1149 will be called rtc-rp5c01.
1151 config RTC_DRV_V3020
1152 tristate "EM Microelectronic V3020"
1154 If you say yes here you will get support for the
1155 EM Microelectronic v3020 RTC chip.
1157 This driver can also be built as a module. If so, the module
1158 will be called rtc-v3020.
1160 config RTC_DRV_WM831X
1161 tristate "Wolfson Microelectronics WM831x RTC"
1162 depends on MFD_WM831X
1164 If you say yes here you will get support for the RTC subsystem
1165 of the Wolfson Microelectronics WM831X series PMICs.
1167 This driver can also be built as a module. If so, the module
1168 will be called "rtc-wm831x".
1170 config RTC_DRV_WM8350
1171 tristate "Wolfson Microelectronics WM8350 RTC"
1172 depends on MFD_WM8350
1174 If you say yes here you will get support for the RTC subsystem
1175 of the Wolfson Microelectronics WM8350.
1177 This driver can also be built as a module. If so, the module
1178 will be called "rtc-wm8350".
1180 config RTC_DRV_SC27XX
1181 tristate "Spreadtrum SC27xx RTC"
1182 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1184 If you say Y here you will get support for the RTC subsystem
1185 of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs
1186 includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips.
1188 This driver can also be built as a module. If so, the module
1189 will be called rtc-sc27xx.
1191 config RTC_DRV_SPEAR
1192 tristate "SPEAR ST RTC"
1193 depends on PLAT_SPEAR || COMPILE_TEST
1196 If you say Y here you will get support for the RTC found on
1199 config RTC_DRV_PCF50633
1200 depends on MFD_PCF50633
1201 tristate "NXP PCF50633 RTC"
1203 If you say yes here you get support for the RTC subsystem of the
1204 NXP PCF50633 used in embedded systems.
1206 config RTC_DRV_AB3100
1207 tristate "ST-Ericsson AB3100 RTC"
1208 depends on AB3100_CORE
1209 default y if AB3100_CORE
1211 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1212 support. This chip contains a battery- and capacitor-backed RTC.
1214 config RTC_DRV_AB8500
1215 tristate "ST-Ericsson AB8500 RTC"
1216 depends on AB8500_CORE
1218 select RTC_INTF_DEV_UIE_EMUL
1220 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1221 support. This chip contains a battery- and capacitor-backed RTC.
1223 config RTC_DRV_NUC900
1224 tristate "NUC910/NUC920 RTC driver"
1225 depends on ARCH_W90X900 || COMPILE_TEST
1227 If you say yes here you get support for the RTC subsystem of the
1228 NUC910/NUC920 used in embedded systems.
1231 tristate "IBM OPAL RTC driver"
1232 depends on PPC_POWERNV
1235 If you say yes here you get support for the PowerNV platform RTC
1236 driver based on OPAL interfaces.
1238 This driver can also be built as a module. If so, the module
1239 will be called rtc-opal.
1241 config RTC_DRV_ZYNQMP
1242 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1245 If you say yes here you get support for the RTC controller found on
1246 Xilinx Zynq Ultrascale+ MPSoC.
1248 config RTC_DRV_CROS_EC
1249 tristate "Chrome OS EC RTC driver"
1250 depends on MFD_CROS_EC
1252 If you say yes here you will get support for the
1253 Chrome OS Embedded Controller's RTC.
1255 This driver can also be built as a module. If so, the module
1256 will be called rtc-cros-ec.
1258 comment "on-CPU RTC drivers"
1260 config RTC_DRV_ASM9260
1261 tristate "Alphascale asm9260 RTC"
1262 depends on MACH_ASM9260 || COMPILE_TEST
1264 If you say yes here you get support for the RTC on the
1265 Alphascale asm9260 SoC.
1267 This driver can also be built as a module. If so, the module
1268 will be called rtc-asm9260.
1270 config RTC_DRV_DAVINCI
1271 tristate "TI DaVinci RTC"
1272 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1274 If you say yes here you get support for the RTC on the
1275 DaVinci platforms (DM365).
1277 This driver can also be built as a module. If so, the module
1278 will be called rtc-davinci.
1280 config RTC_DRV_DIGICOLOR
1281 tristate "Conexant Digicolor RTC"
1282 depends on ARCH_DIGICOLOR || COMPILE_TEST
1284 If you say yes here you get support for the RTC on Conexant
1285 Digicolor platforms. This currently includes the CX92755 SoC.
1287 This driver can also be built as a module. If so, the module
1288 will be called rtc-digicolor.
1290 config RTC_DRV_IMXDI
1291 tristate "Freescale IMX DryIce Real Time Clock"
1294 Support for Freescale IMX DryIce RTC
1296 This driver can also be built as a module, if so, the module
1297 will be called "rtc-imxdi".
1300 tristate "TI OMAP Real Time Clock"
1301 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1304 select GENERIC_PINCONF
1306 Say "yes" here to support the on chip real time clock
1307 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1309 This driver can also be built as a module, if so, module
1310 will be called rtc-omap.
1315 This will include RTC support for Samsung SoCs. If
1316 you want to include RTC support for any machine, kindly
1317 select this in the respective mach-XXXX/Kconfig file.
1320 tristate "Samsung S3C series SoC RTC"
1321 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1323 RTC (Realtime Clock) driver for the clock inbuilt into the
1324 Samsung S3C24XX series of SoCs. This can provide periodic
1325 interrupt rates from 1Hz to 64Hz for user programs, and
1328 The driver currently supports the common features on all the
1329 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1332 This driver can also be build as a module. If so, the module
1333 will be called rtc-s3c.
1335 config RTC_DRV_EP93XX
1336 tristate "Cirrus Logic EP93XX"
1337 depends on ARCH_EP93XX || COMPILE_TEST
1339 If you say yes here you get support for the
1340 RTC embedded in the Cirrus Logic EP93XX processors.
1342 This driver can also be built as a module. If so, the module
1343 will be called rtc-ep93xx.
1345 config RTC_DRV_SA1100
1346 tristate "SA11x0/PXA2xx/PXA910"
1347 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1349 If you say Y here you will get access to the real time clock
1350 built into your SA11x0 or PXA2xx CPU.
1352 To compile this driver as a module, choose M here: the
1353 module will be called rtc-sa1100.
1356 tristate "SuperH On-Chip RTC"
1357 depends on SUPERH || ARCH_RENESAS
1359 Say Y here to enable support for the on-chip RTC found in
1360 most SuperH processors. This RTC is also found in RZ/A SoCs.
1362 To compile this driver as a module, choose M here: the
1363 module will be called rtc-sh.
1365 config RTC_DRV_VR41XX
1366 tristate "NEC VR41XX"
1367 depends on CPU_VR41XX || COMPILE_TEST
1369 If you say Y here you will get access to the real time clock
1370 built into your NEC VR41XX CPU.
1372 To compile this driver as a module, choose M here: the
1373 module will be called rtc-vr41xx.
1375 config RTC_DRV_PL030
1376 tristate "ARM AMBA PL030 RTC"
1379 If you say Y here you will get access to ARM AMBA
1380 PrimeCell PL030 RTC found on certain ARM SOCs.
1382 To compile this driver as a module, choose M here: the
1383 module will be called rtc-pl030.
1385 config RTC_DRV_PL031
1386 tristate "ARM AMBA PL031 RTC"
1389 If you say Y here you will get access to ARM AMBA
1390 PrimeCell PL031 RTC found on certain ARM SOCs.
1392 To compile this driver as a module, choose M here: the
1393 module will be called rtc-pl031.
1395 config RTC_DRV_AT91RM9200
1396 tristate "AT91RM9200 or some AT91SAM9 RTC"
1397 depends on ARCH_AT91 || COMPILE_TEST
1399 Driver for the internal RTC (Realtime Clock) module found on
1400 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1401 this is powered by the backup power supply.
1403 config RTC_DRV_AT91SAM9
1404 tristate "AT91SAM9 RTT as RTC"
1405 depends on ARCH_AT91 || COMPILE_TEST
1406 depends on HAS_IOMEM
1409 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1410 can be used as an RTC thanks to the backup power supply (e.g. a
1411 small coin cell battery) which keeps this block and the GPBR
1412 (General Purpose Backup Registers) block powered when the device
1414 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1415 probably want to use the real RTC block instead of the "RTT as an
1418 config RTC_DRV_AU1XXX
1419 tristate "Au1xxx Counter0 RTC support"
1420 depends on MIPS_ALCHEMY
1422 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1423 counter) to be used as a RTC.
1425 This driver can also be built as a module. If so, the module
1426 will be called rtc-au1xxx.
1428 config RTC_DRV_RS5C313
1429 tristate "Ricoh RS5C313"
1430 depends on SH_LANDISK
1432 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1434 config RTC_DRV_GENERIC
1435 tristate "Generic RTC support"
1436 # Please consider writing a new RTC driver instead of using the generic
1438 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
1440 Say Y or M here to enable RTC support on systems using the generic
1441 RTC abstraction. If you do not know what you are doing, you should
1445 tristate "PXA27x/PXA3xx"
1447 select RTC_DRV_SA1100
1449 If you say Y here you will get access to the real time clock
1450 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1451 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1453 This RTC driver uses PXA RTC registers available since pxa27x
1454 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1456 config RTC_DRV_VT8500
1457 tristate "VIA/WonderMedia 85xx SoC RTC"
1458 depends on ARCH_VT8500 || COMPILE_TEST
1460 If you say Y here you will get access to the real time clock
1461 built into your VIA VT8500 SoC or its relatives.
1464 config RTC_DRV_SUN4V
1465 bool "SUN4V Hypervisor RTC"
1468 If you say Y here you will get support for the Hypervisor
1469 based RTC on SUN4V systems.
1471 config RTC_DRV_SUN6I
1472 bool "Allwinner A31 RTC"
1473 default MACH_SUN6I || MACH_SUN8I
1474 depends on COMMON_CLK
1475 depends on ARCH_SUNXI || COMPILE_TEST
1477 If you say Y here you will get support for the RTC found in
1478 some Allwinner SoCs like the A31 or the A64.
1480 config RTC_DRV_SUNXI
1481 tristate "Allwinner sun4i/sun7i RTC"
1482 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1484 If you say Y here you will get support for the RTC found on
1487 config RTC_DRV_STARFIRE
1491 If you say Y here you will get support for the RTC found on
1494 config RTC_DRV_TX4939
1495 tristate "TX4939 SoC"
1496 depends on SOC_TX4939 || COMPILE_TEST
1498 Driver for the internal RTC (Realtime Clock) module found on
1502 tristate "Marvell SoC RTC"
1503 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1505 If you say yes here you will get support for the in-chip RTC
1506 that can be found in some of Marvell's SoC devices, such as
1507 the Kirkwood 88F6281 and 88F6192.
1509 This driver can also be built as a module. If so, the module
1510 will be called rtc-mv.
1512 config RTC_DRV_ARMADA38X
1513 tristate "Armada 38x Marvell SoC RTC"
1514 depends on ARCH_MVEBU || COMPILE_TEST
1516 If you say yes here you will get support for the in-chip RTC
1517 that can be found in the Armada 38x Marvell's SoC device
1519 This driver can also be built as a module. If so, the module
1520 will be called armada38x-rtc.
1522 config RTC_DRV_FTRTC010
1523 tristate "Faraday Technology FTRTC010 RTC"
1524 depends on HAS_IOMEM
1527 If you say Y here you will get support for the
1528 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1530 This driver can also be built as a module. If so, the module
1531 will be called rtc-ftrtc010.
1537 If you say yes here you will get support for the RTC on PS3.
1539 This driver can also be built as a module. If so, the module
1540 will be called rtc-ps3.
1542 config RTC_DRV_COH901331
1543 tristate "ST-Ericsson COH 901 331 RTC"
1544 depends on ARCH_U300 || COMPILE_TEST
1546 If you say Y here you will get access to ST-Ericsson
1547 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1550 This driver can also be built as a module. If so, the module
1551 will be called "rtc-coh901331".
1555 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1556 depends on ARCH_MXS || COMPILE_TEST
1559 If you say yes here you will get support for the onboard
1560 STMP3xxx/i.MX23/i.MX28 RTC.
1562 This driver can also be built as a module. If so, the module
1563 will be called rtc-stmp3xxx.
1569 If you say Y here you will get support for the RTC found on
1570 the PCAP2 ASIC used on some Motorola phones.
1572 config RTC_DRV_MC13XXX
1573 depends on MFD_MC13XXX
1574 tristate "Freescale MC13xxx RTC"
1576 This enables support for the RTCs found on Freescale's PMICs
1577 MC13783 and MC13892.
1579 config RTC_DRV_MPC5121
1580 tristate "Freescale MPC5121 built-in RTC"
1581 depends on PPC_MPC512x || PPC_MPC52xx
1583 If you say yes here you will get support for the
1584 built-in RTC on MPC5121 or on MPC5200.
1586 This driver can also be built as a module. If so, the module
1587 will be called rtc-mpc5121.
1589 config RTC_DRV_JZ4740
1590 tristate "Ingenic JZ4740 SoC"
1591 depends on MACH_INGENIC || COMPILE_TEST
1593 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1596 This driver can also be built as a module. If so, the module
1597 will be called rtc-jz4740.
1599 config RTC_DRV_LPC24XX
1600 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1601 depends on ARCH_LPC18XX || COMPILE_TEST
1602 depends on OF && HAS_IOMEM
1604 This enables support for the NXP RTC found which can be found on
1605 NXP LPC178x/18xx/408x/43xx devices.
1607 If you have one of the devices above enable this driver to use
1608 the hardware RTC. This driver can also be built as a module. If
1609 so, the module will be called rtc-lpc24xx.
1611 config RTC_DRV_LPC32XX
1612 depends on ARCH_LPC32XX || COMPILE_TEST
1613 tristate "NXP LPC32XX RTC"
1615 This enables support for the NXP RTC in the LPC32XX
1617 This driver can also be built as a module. If so, the module
1618 will be called rtc-lpc32xx.
1620 config RTC_DRV_PM8XXX
1621 tristate "Qualcomm PMIC8XXX RTC"
1622 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1624 If you say yes here you get support for the
1625 Qualcomm PMIC8XXX RTC.
1627 To compile this driver as a module, choose M here: the
1628 module will be called rtc-pm8xxx.
1630 config RTC_DRV_TEGRA
1631 tristate "NVIDIA Tegra Internal RTC driver"
1632 depends on ARCH_TEGRA || COMPILE_TEST
1634 If you say yes here you get support for the
1635 Tegra 200 series internal RTC module.
1637 This drive can also be built as a module. If so, the module
1638 will be called rtc-tegra.
1641 tristate "PKUnity v3 RTC support"
1642 depends on ARCH_PUV3
1644 This enables support for the RTC in the PKUnity-v3 SoCs.
1646 This drive can also be built as a module. If so, the module
1647 will be called rtc-puv3.
1649 config RTC_DRV_LOONGSON1
1650 tristate "loongson1 RTC support"
1651 depends on MACH_LOONGSON32
1653 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1654 counter) to be used as a RTC.
1656 This driver can also be built as a module. If so, the module
1657 will be called rtc-ls1x.
1660 tristate "Freescale MXC Real Time Clock"
1663 If you say yes here you get support for the Freescale MXC
1666 This driver can also be built as a module, if so, the module
1667 will be called "rtc-mxc".
1669 config RTC_DRV_MXC_V2
1670 tristate "Freescale MXC Real Time Clock for i.MX53"
1673 If you say yes here you get support for the Freescale MXC
1674 SRTC module in i.MX53 processor.
1676 This driver can also be built as a module, if so, the module
1677 will be called "rtc-mxc_v2".
1680 tristate "Freescale SNVS RTC support"
1682 depends on HAS_IOMEM
1685 If you say yes here you get support for the Freescale SNVS
1686 Low Power (LP) RTC module.
1688 This driver can also be built as a module, if so, the module
1689 will be called "rtc-snvs".
1691 config RTC_DRV_SIRFSOC
1692 tristate "SiRFSOC RTC"
1693 depends on ARCH_SIRF
1695 Say "yes" here to support the real time clock on SiRF SOC chips.
1696 This driver can also be built as a module called rtc-sirfsoc.
1698 config RTC_DRV_ST_LPC
1699 tristate "STMicroelectronics LPC RTC"
1703 Say Y here to include STMicroelectronics Low Power Controller
1704 (LPC) based RTC support.
1706 To compile this driver as a module, choose M here: the
1707 module will be called rtc-st-lpc.
1709 config RTC_DRV_MOXART
1710 tristate "MOXA ART RTC"
1711 depends on ARCH_MOXART || COMPILE_TEST
1713 If you say yes here you get support for the MOXA ART
1716 This driver can also be built as a module. If so, the module
1717 will be called rtc-moxart
1719 config RTC_DRV_MT6397
1720 tristate "MediaTek PMIC based RTC"
1721 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1723 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1724 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1725 MediaTek(R) RTC driver.
1727 If you want to use MediaTek(R) RTC interface, select Y or M here.
1729 config RTC_DRV_MT7622
1730 tristate "MediaTek SoC based RTC"
1731 depends on ARCH_MEDIATEK || COMPILE_TEST
1733 This enables support for the real time clock built in the MediaTek
1736 This drive can also be built as a module. If so, the module
1737 will be called rtc-mt7622.
1739 config RTC_DRV_XGENE
1740 tristate "APM X-Gene RTC"
1741 depends on HAS_IOMEM
1742 depends on ARCH_XGENE || COMPILE_TEST
1744 If you say yes here you get support for the APM X-Gene SoC real time
1747 This driver can also be built as a module, if so, the module
1748 will be called "rtc-xgene".
1750 config RTC_DRV_PIC32
1751 tristate "Microchip PIC32 RTC"
1752 depends on MACH_PIC32
1755 If you say yes here you get support for the PIC32 RTC module.
1757 This driver can also be built as a module. If so, the module
1758 will be called rtc-pic32
1760 config RTC_DRV_R7301
1761 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1763 depends on OF && HAS_IOMEM
1765 If you say yes here you get support for the EPSON TOYOCOM
1766 RTC-7301SF/DG chips.
1768 This driver can also be built as a module. If so, the module
1769 will be called rtc-r7301.
1771 config RTC_DRV_STM32
1772 tristate "STM32 RTC"
1774 depends on ARCH_STM32 || COMPILE_TEST
1776 If you say yes here you get support for the STM32 On-Chip
1779 This driver can also be built as a module, if so, the module
1780 will be called "rtc-stm32".
1782 config RTC_DRV_CPCAP
1783 depends on MFD_CPCAP
1784 tristate "Motorola CPCAP RTC"
1786 Say y here for CPCAP rtc found on some Motorola phones
1787 and tablets such as Droid 4.
1789 config RTC_DRV_RTD119X
1790 bool "Realtek RTD129x RTC"
1791 depends on ARCH_REALTEK || COMPILE_TEST
1792 default ARCH_REALTEK
1794 If you say yes here, you get support for the RTD1295 SoC
1797 comment "HID Sensor RTC drivers"
1799 config RTC_DRV_HID_SENSOR_TIME
1800 tristate "HID Sensor Time"
1803 select HID_SENSOR_HUB
1804 select HID_SENSOR_IIO_COMMON
1806 Say yes here to build support for the HID Sensors of type Time.
1807 This drivers makes such sensors available as RTCs.
1809 If this driver is compiled as a module, it will be named
1810 rtc-hid-sensor-time.
1812 config RTC_DRV_GOLDFISH
1813 tristate "Goldfish Real Time Clock"
1814 depends on MIPS && (GOLDFISH || COMPILE_TEST)
1816 Say yes to enable RTC driver for the Goldfish based virtual platform.
1818 Goldfish is a code name for the virtual platform developed by Google
1819 for Android emulation.