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
318 If you say yes here you will get support for the
319 RTC of Maxim MAX8907 PMIC.
321 This driver can also be built as a module. If so, the module
322 will be called rtc-max8907.
324 config RTC_DRV_MAX8925
325 tristate "Maxim MAX8925"
326 depends on MFD_MAX8925
328 If you say yes here you will get support for the
329 RTC of Maxim MAX8925 PMIC.
331 This driver can also be built as a module. If so, the module
332 will be called rtc-max8925.
334 config RTC_DRV_MAX8998
335 tristate "Maxim MAX8998"
336 depends on MFD_MAX8998
338 If you say yes here you will get support for the
339 RTC of Maxim MAX8998 PMIC.
341 This driver can also be built as a module. If so, the module
342 will be called rtc-max8998.
344 config RTC_DRV_MAX8997
345 tristate "Maxim MAX8997"
346 depends on MFD_MAX8997
348 If you say yes here you will get support for the
349 RTC of Maxim MAX8997 PMIC.
351 This driver can also be built as a module. If so, the module
352 will be called rtc-max8997.
354 config RTC_DRV_MAX77686
355 tristate "Maxim MAX77686"
356 depends on MFD_MAX77686 || MFD_MAX77620 || COMPILE_TEST
358 If you say yes here you will get support for the
359 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
361 This driver can also be built as a module. If so, the module
362 will be called rtc-max77686.
365 tristate "Rockchip RK805/RK808/RK818 RTC"
368 If you say yes here you will get support for the
369 RTC of RK805, RK808 and RK818 PMIC.
371 This driver can also be built as a module. If so, the module
372 will be called rk808-rtc.
374 config RTC_DRV_RS5C372
375 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
377 If you say yes here you get support for the
378 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
380 This driver can also be built as a module. If so, the module
381 will be called rtc-rs5c372.
383 config RTC_DRV_ISL1208
384 tristate "Intersil ISL1208"
386 If you say yes here you get support for the
387 Intersil ISL1208 RTC chip.
389 This driver can also be built as a module. If so, the module
390 will be called rtc-isl1208.
392 config RTC_DRV_ISL12022
393 tristate "Intersil ISL12022"
395 If you say yes here you get support for the
396 Intersil ISL12022 RTC chip.
398 This driver can also be built as a module. If so, the module
399 will be called rtc-isl12022.
401 config RTC_DRV_ISL12026
402 tristate "Intersil ISL12026"
403 depends on OF || COMPILE_TEST
405 If you say yes here you get support for the
406 Intersil ISL12026 RTC chip.
408 This driver can also be built as a module. If so, the module
409 will be called rtc-isl12026.
412 tristate "Xicor/Intersil X1205"
414 If you say yes here you get support for the
415 Xicor/Intersil X1205 RTC chip.
417 This driver can also be built as a module. If so, the module
418 will be called rtc-x1205.
420 config RTC_DRV_PCF8523
421 tristate "NXP PCF8523"
423 If you say yes here you get support for the NXP PCF8523 RTC
426 This driver can also be built as a module. If so, the module
427 will be called rtc-pcf8523.
429 config RTC_DRV_PCF85063
430 tristate "NXP PCF85063"
432 If you say yes here you get support for the PCF85063 RTC chip
434 This driver can also be built as a module. If so, the module
435 will be called rtc-pcf85063.
437 config RTC_DRV_PCF85363
438 tristate "NXP PCF85363"
442 If you say yes here you get support for the PCF85363 RTC chip.
444 This driver can also be built as a module. If so, the module
445 will be called rtc-pcf85363.
447 The nvmem interface will be named pcf85363-#, where # is the
448 zero-based instance number.
450 config RTC_DRV_PCF8563
451 tristate "Philips PCF8563/Epson RTC8564"
453 If you say yes here you get support for the
454 Philips PCF8563 RTC chip. The Epson RTC8564
457 This driver can also be built as a module. If so, the module
458 will be called rtc-pcf8563.
460 config RTC_DRV_PCF8583
461 tristate "Philips PCF8583"
463 If you say yes here you get support for the Philips PCF8583
464 RTC chip found on Acorn RiscPCs. This driver supports the
465 platform specific method of retrieving the current year from
466 the RTC's SRAM. It will work on other platforms with the same
467 chip, but the year will probably have to be tweaked.
469 This driver can also be built as a module. If so, the module
470 will be called rtc-pcf8583.
472 config RTC_DRV_M41T80
473 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
475 If you say Y here you will get support for the ST M41T60
476 and M41T80 RTC chips series. Currently, the following chips are
477 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
478 M41ST85, M41ST87, and MicroCrystal RV4162.
480 This driver can also be built as a module. If so, the module
481 will be called rtc-m41t80.
483 config RTC_DRV_M41T80_WDT
484 bool "ST M41T65/M41T80 series RTC watchdog timer"
485 depends on RTC_DRV_M41T80
487 If you say Y here you will get support for the
488 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
491 tristate "TI BQ32000"
493 If you say Y here you will get support for the TI
494 BQ32000 I2C RTC chip.
496 This driver can also be built as a module. If so, the module
497 will be called rtc-bq32k.
499 config RTC_DRV_DM355EVM
500 tristate "TI DaVinci DM355 EVM RTC"
501 depends on MFD_DM355EVM_MSP
503 Supports the RTC firmware in the MSP430 on the DM355 EVM.
505 config RTC_DRV_TWL92330
506 bool "TI TWL92330/Menelaus"
509 If you say yes here you get support for the RTC on the
510 TWL92330 "Menelaus" power management chip, used with OMAP2
511 platforms. The support is integrated with the rest of
512 the Menelaus driver; it's not separate module.
514 config RTC_DRV_TWL4030
515 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
516 depends on TWL4030_CORE
519 If you say yes here you get support for the RTC on the
520 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
522 This driver can also be built as a module. If so, the module
523 will be called rtc-twl.
525 config RTC_DRV_PALMAS
526 tristate "TI Palmas RTC driver"
527 depends on MFD_PALMAS
529 If you say yes here you get support for the RTC of TI PALMA series PMIC
532 This driver can also be built as a module. If so, the module
533 will be called rtc-palma.
535 config RTC_DRV_TPS6586X
536 tristate "TI TPS6586X RTC driver"
537 depends on MFD_TPS6586X
539 TI Power Management IC TPS6586X supports RTC functionality
540 along with alarm. This driver supports the RTC driver for
541 the TPS6586X RTC module.
543 config RTC_DRV_TPS65910
544 tristate "TI TPS65910 RTC driver"
545 depends on RTC_CLASS && MFD_TPS65910
547 If you say yes here you get support for the RTC on the
550 This driver can also be built as a module. If so, the module
551 will be called rtc-tps65910.
553 config RTC_DRV_TPS80031
554 tristate "TI TPS80031/TPS80032 RTC driver"
555 depends on MFD_TPS80031
557 TI Power Management IC TPS80031 supports RTC functionality
558 along with alarm. This driver supports the RTC driver for
559 the TPS80031 RTC module.
561 config RTC_DRV_RC5T583
562 tristate "RICOH 5T583 RTC driver"
563 depends on MFD_RC5T583
565 If you say yes here you get support for the RTC on the
568 This driver can also be built as a module. If so, the module
569 will be called rtc-rc5t583.
571 config RTC_DRV_S35390A
572 tristate "Seiko Instruments S-35390A"
575 If you say yes here you will get support for the Seiko
576 Instruments S-35390A.
578 This driver can also be built as a module. If so the module
579 will be called rtc-s35390a.
581 config RTC_DRV_FM3130
582 tristate "Ramtron FM3130"
584 If you say Y here you will get support for the
585 Ramtron FM3130 RTC chips.
586 Ramtron FM3130 is a chip with two separate devices inside,
587 RTC clock and FRAM. This driver provides only RTC functionality.
589 This driver can also be built as a module. If so the module
590 will be called rtc-fm3130.
592 config RTC_DRV_RX8010
593 tristate "Epson RX8010SJ"
596 If you say yes here you get support for the Epson RX8010SJ RTC
599 This driver can also be built as a module. If so, the module
600 will be called rtc-rx8010.
602 config RTC_DRV_RX8581
603 tristate "Epson RX-8581"
605 If you say yes here you will get support for the Epson RX-8581.
607 This driver can also be built as a module. If so the module
608 will be called rtc-rx8581.
610 config RTC_DRV_RX8025
611 tristate "Epson RX-8025SA/NB"
613 If you say yes here you get support for the Epson
614 RX-8025SA/NB RTC chips.
616 This driver can also be built as a module. If so, the module
617 will be called rtc-rx8025.
619 config RTC_DRV_EM3027
620 tristate "EM Microelectronic EM3027"
622 If you say yes here you get support for the EM
623 Microelectronic EM3027 RTC chips.
625 This driver can also be built as a module. If so, the module
626 will be called rtc-em3027.
628 config RTC_DRV_RV8803
629 tristate "Micro Crystal RV8803, Epson RX8900"
631 If you say yes here you get support for the Micro Crystal RV8803 and
632 Epson RX8900 RTC chips.
634 This driver can also be built as a module. If so, the module
635 will be called rtc-rv8803.
638 tristate "Samsung S2M/S5M series"
639 depends on MFD_SEC_CORE || COMPILE_TEST
642 If you say yes here you will get support for the
643 RTC of Samsung S2MPS14 and S5M PMIC series.
645 This driver can also be built as a module. If so, the module
646 will be called rtc-s5m.
650 comment "SPI RTC drivers"
654 config RTC_DRV_M41T93
657 If you say yes here you will get support for the
658 ST M41T93 SPI RTC chip.
660 This driver can also be built as a module. If so, the module
661 will be called rtc-m41t93.
663 config RTC_DRV_M41T94
666 If you say yes here you will get support for the
667 ST M41T94 SPI RTC chip.
669 This driver can also be built as a module. If so, the module
670 will be called rtc-m41t94.
672 config RTC_DRV_DS1302
673 tristate "Dallas/Maxim DS1302"
676 If you say yes here you get support for the Dallas DS1302 RTC chips.
678 This driver can also be built as a module. If so, the module
679 will be called rtc-ds1302.
681 config RTC_DRV_DS1305
682 tristate "Dallas/Maxim DS1305/DS1306"
684 Select this driver to get support for the Dallas/Maxim DS1305
685 and DS1306 real time clock chips. These support a trickle
686 charger, alarms, and NVRAM in addition to the clock.
688 This driver can also be built as a module. If so, the module
689 will be called rtc-ds1305.
691 config RTC_DRV_DS1343
693 tristate "Dallas/Maxim DS1343/DS1344"
695 If you say yes here you get support for the
696 Dallas/Maxim DS1343 and DS1344 real time clock chips.
697 Support for trickle charger, alarm is provided.
699 This driver can also be built as a module. If so, the module
700 will be called rtc-ds1343.
702 config RTC_DRV_DS1347
704 tristate "Dallas/Maxim DS1347"
706 If you say yes here you get support for the
707 Dallas/Maxim DS1347 chips.
709 This driver only supports the RTC feature, and not other chip
710 features such as alarms.
712 This driver can also be built as a module. If so, the module
713 will be called rtc-ds1347.
715 config RTC_DRV_DS1390
716 tristate "Dallas/Maxim DS1390/93/94"
718 If you say yes here you get support for the
719 Dallas/Maxim DS1390/93/94 chips.
721 This driver supports the RTC feature and trickle charging but not
722 other chip features such as alarms.
724 This driver can also be built as a module. If so, the module
725 will be called rtc-ds1390.
727 config RTC_DRV_MAX6916
728 tristate "Maxim MAX6916"
730 If you say yes here you will get support for the
731 Maxim MAX6916 SPI RTC chip.
733 This driver only supports the RTC feature, and not other chip
734 features such as alarms.
736 This driver can also be built as a module. If so, the module
737 will be called rtc-max6916.
740 tristate "Epson RTC-9701JE"
742 If you say yes here you will get support for the
743 Epson RTC-9701JE SPI RTC chip.
745 This driver can also be built as a module. If so, the module
746 will be called rtc-r9701.
748 config RTC_DRV_RX4581
749 tristate "Epson RX-4581"
751 If you say yes here you will get support for the Epson RX-4581.
753 This driver can also be built as a module. If so the module
754 will be called rtc-rx4581.
756 config RTC_DRV_RX6110
757 tristate "Epson RX-6110"
760 If you say yes here you will get support for the Epson RX-6610.
762 This driver can also be built as a module. If so the module
763 will be called rtc-rx6110.
765 config RTC_DRV_RS5C348
766 tristate "Ricoh RS5C348A/B"
768 If you say yes here you get support for the
769 Ricoh RS5C348A and RS5C348B RTC chips.
771 This driver can also be built as a module. If so, the module
772 will be called rtc-rs5c348.
774 config RTC_DRV_MAX6902
775 tristate "Maxim MAX6902"
777 If you say yes here you will get support for the
778 Maxim MAX6902 SPI RTC chip.
780 This driver can also be built as a module. If so, the module
781 will be called rtc-max6902.
783 config RTC_DRV_PCF2123
784 tristate "NXP PCF2123"
786 If you say yes here you get support for the NXP PCF2123
789 This driver can also be built as a module. If so, the module
790 will be called rtc-pcf2123.
792 config RTC_DRV_MCP795
793 tristate "Microchip MCP795"
795 If you say yes here you will get support for the Microchip MCP795.
797 This driver can also be built as a module. If so the module
798 will be called rtc-mcp795.
803 # Helper to resolve issues with configs that have SPI enabled but I2C
804 # modular. See SND_SOC_I2C_AND_SPI for more information
806 config RTC_I2C_AND_SPI
810 default y if SPI_MASTER=y
811 select REGMAP_I2C if I2C
812 select REGMAP_SPI if SPI_MASTER
814 comment "SPI and I2C RTC drivers"
816 config RTC_DRV_DS3232
817 tristate "Dallas/Maxim DS3232/DS3234"
818 depends on RTC_I2C_AND_SPI
820 If you say yes here you get support for Dallas Semiconductor
821 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
822 with the device, the alarm functionality is supported.
824 This driver can also be built as a module. If so, the module
825 will be called rtc-ds3232.
827 config RTC_DRV_DS3232_HWMON
828 bool "HWMON support for Dallas/Maxim DS3232/DS3234"
829 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
832 Say Y here if you want to expose temperature sensor data on
835 config RTC_DRV_PCF2127
836 tristate "NXP PCF2127"
837 depends on RTC_I2C_AND_SPI
839 If you say yes here you get support for the NXP PCF2127/29 RTC
842 This driver can also be built as a module. If so, the module
843 will be called rtc-pcf2127.
845 config RTC_DRV_RV3029C2
846 tristate "Micro Crystal RV3029/3049"
847 depends on RTC_I2C_AND_SPI
849 If you say yes here you get support for the Micro Crystal
850 RV3029 and RV3049 RTC chips.
852 This driver can also be built as a module. If so, the module
853 will be called rtc-rv3029c2.
855 config RTC_DRV_RV3029_HWMON
856 bool "HWMON support for RV3029/3049"
857 depends on RTC_DRV_RV3029C2 && HWMON
858 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
861 Say Y here if you want to expose temperature sensor data on
864 comment "Platform RTC drivers"
866 # this 'CMOS' RTC driver is arch dependent because it requires
867 # <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
868 # global rtc_lock ... it's not yet just another platform_device.
871 tristate "PC-style 'CMOS'"
872 depends on X86 || ARM || PPC || MIPS || SPARC64
874 select RTC_MC146818_LIB
876 Say "yes" here to get direct support for the real time clock
877 found in every PC or ACPI-based system, and some other boards.
878 Specifically the original MC146818, compatibles like those in
879 PC south bridges, the DS12887 or M48T86, some multifunction
880 or LPC bus chips, and so on.
882 Your system will need to define the platform device used by
883 this driver, otherwise it won't be accessible. This means
884 you can safely enable this driver if you don't know whether
885 or not your board has this kind of hardware.
887 This driver can also be built as a module. If so, the module
888 will be called rtc-cmos.
891 bool "Alpha PC-style CMOS"
893 select RTC_MC146818_LIB
896 Direct support for the real-time clock found on every Alpha
897 system, specifically MC146818 compatibles. If in doubt, say Y.
900 tristate "Virtual RTC for Intel MID platforms"
901 depends on X86_INTEL_MID
902 default y if X86_INTEL_MID
905 Say "yes" here to get direct support for the real time clock
906 found on Moorestown platforms. The VRTC is a emulated RTC that
907 derives its clock source from a real RTC in the PMIC. The MC146818
908 style programming interface is mostly conserved, but any
909 updates are done via IPC calls to the system controller FW.
911 config RTC_DRV_DS1216
912 tristate "Dallas DS1216"
915 If you say yes here you get support for the Dallas DS1216 RTC chips.
917 config RTC_DRV_DS1286
918 tristate "Dallas DS1286"
921 If you say yes here you get support for the Dallas DS1286 RTC chips.
923 config RTC_DRV_DS1511
924 tristate "Dallas DS1511"
927 If you say yes here you get support for the
928 Dallas DS1511 timekeeping/watchdog chip.
930 This driver can also be built as a module. If so, the module
931 will be called rtc-ds1511.
933 config RTC_DRV_DS1553
934 tristate "Maxim/Dallas DS1553"
937 If you say yes here you get support for the
938 Maxim/Dallas DS1553 timekeeping chip.
940 This driver can also be built as a module. If so, the module
941 will be called rtc-ds1553.
943 config RTC_DRV_DS1685_FAMILY
944 tristate "Dallas/Maxim DS1685 Family"
946 If you say yes here you get support for the Dallas/Maxim DS1685
947 family of real time chips. This family includes the DS1685/DS1687,
948 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
949 DS17885/DS17887 chips.
951 This driver can also be built as a module. If so, the module
952 will be called rtc-ds1685.
956 depends on RTC_DRV_DS1685_FAMILY
957 default RTC_DRV_DS1685
959 config RTC_DRV_DS1685
962 This enables support for the Dallas/Maxim DS1685/DS1687 real time
965 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
966 systems, as well as EPPC-405-UC modules by electronic system design
969 config RTC_DRV_DS1689
972 This enables support for the Dallas/Maxim DS1689/DS1693 real time
975 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
976 which supports a few minor features such as Vcc, Vbat, and Power
977 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
979 It also works for the even older DS1688/DS1691 RTC chips, which are
980 virtually the same and carry the same model number. Both chips
981 have 114 bytes of user NVRAM.
983 config RTC_DRV_DS17285
984 bool "DS17285/DS17287"
986 This enables support for the Dallas/Maxim DS17285/DS17287 real time
989 This chip features 2kb of extended NV-SRAM. It may possibly be
990 found in some SGI O2 systems (rare).
992 config RTC_DRV_DS17485
993 bool "DS17485/DS17487"
995 This enables support for the Dallas/Maxim DS17485/DS17487 real time
998 This chip features 4kb of extended NV-SRAM.
1000 config RTC_DRV_DS17885
1001 bool "DS17885/DS17887"
1003 This enables support for the Dallas/Maxim DS17885/DS17887 real time
1006 This chip features 8kb of extended NV-SRAM.
1010 config RTC_DS1685_PROC_REGS
1011 bool "Display register values in /proc"
1012 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
1014 Enable this to display a readout of all of the RTC registers in
1015 /proc/drivers/rtc. Keep in mind that this can potentially lead
1016 to lost interrupts, as reading Control Register C will clear
1017 all pending IRQ flags.
1019 Unless you are debugging this driver, choose N.
1021 config RTC_DRV_DS1742
1022 tristate "Maxim/Dallas DS1742/1743"
1023 depends on HAS_IOMEM
1025 If you say yes here you get support for the
1026 Maxim/Dallas DS1742/1743 timekeeping chip.
1028 This driver can also be built as a module. If so, the module
1029 will be called rtc-ds1742.
1031 config RTC_DRV_DS2404
1032 tristate "Maxim/Dallas DS2404"
1034 If you say yes here you get support for the
1035 Dallas DS2404 RTC chip.
1037 This driver can also be built as a module. If so, the module
1038 will be called rtc-ds2404.
1040 config RTC_DRV_DA9052
1041 tristate "Dialog DA9052/DA9053 RTC"
1042 depends on PMIC_DA9052
1044 Say y here to support the RTC driver for Dialog Semiconductor
1045 DA9052-BC and DA9053-AA/Bx PMICs.
1047 config RTC_DRV_DA9055
1048 tristate "Dialog Semiconductor DA9055 RTC"
1049 depends on MFD_DA9055
1051 If you say yes here you will get support for the
1052 RTC of the Dialog DA9055 PMIC.
1054 This driver can also be built as a module. If so, the module
1055 will be called rtc-da9055
1057 config RTC_DRV_DA9063
1058 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1059 depends on MFD_DA9063 || MFD_DA9062
1061 If you say yes here you will get support for the RTC subsystem
1062 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1064 This driver can also be built as a module. If so, the module
1065 will be called "rtc-da9063".
1069 depends on EFI && !X86
1071 If you say yes here you will get support for the EFI
1074 This driver can also be built as a module. If so, the module
1075 will be called rtc-efi.
1077 config RTC_DRV_STK17TA8
1078 tristate "Simtek STK17TA8"
1079 depends on HAS_IOMEM
1081 If you say yes here you get support for the
1082 Simtek STK17TA8 timekeeping chip.
1084 This driver can also be built as a module. If so, the module
1085 will be called rtc-stk17ta8.
1087 config RTC_DRV_M48T86
1088 tristate "ST M48T86/Dallas DS12887"
1090 If you say Y here you will get support for the
1091 ST M48T86 and Dallas DS12887 RTC chips.
1093 This driver can also be built as a module. If so, the module
1094 will be called rtc-m48t86.
1096 config RTC_DRV_M48T35
1097 tristate "ST M48T35"
1098 depends on HAS_IOMEM
1100 If you say Y here you will get support for the
1103 This driver can also be built as a module, if so, the module
1104 will be called "rtc-m48t35".
1106 config RTC_DRV_M48T59
1107 tristate "ST M48T59/M48T08/M48T02"
1108 depends on HAS_IOMEM
1110 If you say Y here you will get support for the
1111 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1113 These chips are usually found in Sun SPARC and UltraSPARC
1116 This driver can also be built as a module, if so, the module
1117 will be called "rtc-m48t59".
1119 config RTC_DRV_MSM6242
1120 tristate "Oki MSM6242"
1121 depends on HAS_IOMEM
1123 If you say yes here you get support for the Oki MSM6242
1124 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1126 This driver can also be built as a module. If so, the module
1127 will be called rtc-msm6242.
1129 config RTC_DRV_BQ4802
1130 tristate "TI BQ4802"
1131 depends on HAS_IOMEM
1133 If you say Y here you will get support for the TI
1136 This driver can also be built as a module. If so, the module
1137 will be called rtc-bq4802.
1139 config RTC_DRV_RP5C01
1140 tristate "Ricoh RP5C01"
1141 depends on HAS_IOMEM
1143 If you say yes here you get support for the Ricoh RP5C01
1144 timekeeping chip. It is used in some Amiga models (e.g. A3000
1147 This driver can also be built as a module. If so, the module
1148 will be called rtc-rp5c01.
1150 config RTC_DRV_V3020
1151 tristate "EM Microelectronic V3020"
1153 If you say yes here you will get support for the
1154 EM Microelectronic v3020 RTC chip.
1156 This driver can also be built as a module. If so, the module
1157 will be called rtc-v3020.
1159 config RTC_DRV_WM831X
1160 tristate "Wolfson Microelectronics WM831x RTC"
1161 depends on MFD_WM831X
1163 If you say yes here you will get support for the RTC subsystem
1164 of the Wolfson Microelectronics WM831X series PMICs.
1166 This driver can also be built as a module. If so, the module
1167 will be called "rtc-wm831x".
1169 config RTC_DRV_WM8350
1170 tristate "Wolfson Microelectronics WM8350 RTC"
1171 depends on MFD_WM8350
1173 If you say yes here you will get support for the RTC subsystem
1174 of the Wolfson Microelectronics WM8350.
1176 This driver can also be built as a module. If so, the module
1177 will be called "rtc-wm8350".
1179 config RTC_DRV_SC27XX
1180 tristate "Spreadtrum SC27xx RTC"
1181 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1183 If you say Y here you will get support for the RTC subsystem
1184 of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs
1185 includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips.
1187 This driver can also be built as a module. If so, the module
1188 will be called rtc-sc27xx.
1190 config RTC_DRV_SPEAR
1191 tristate "SPEAR ST RTC"
1192 depends on PLAT_SPEAR || COMPILE_TEST
1195 If you say Y here you will get support for the RTC found on
1198 config RTC_DRV_PCF50633
1199 depends on MFD_PCF50633
1200 tristate "NXP PCF50633 RTC"
1202 If you say yes here you get support for the RTC subsystem of the
1203 NXP PCF50633 used in embedded systems.
1205 config RTC_DRV_AB3100
1206 tristate "ST-Ericsson AB3100 RTC"
1207 depends on AB3100_CORE
1208 default y if AB3100_CORE
1210 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1211 support. This chip contains a battery- and capacitor-backed RTC.
1213 config RTC_DRV_AB8500
1214 tristate "ST-Ericsson AB8500 RTC"
1215 depends on AB8500_CORE
1217 select RTC_INTF_DEV_UIE_EMUL
1219 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1220 support. This chip contains a battery- and capacitor-backed RTC.
1222 config RTC_DRV_NUC900
1223 tristate "NUC910/NUC920 RTC driver"
1224 depends on ARCH_W90X900 || COMPILE_TEST
1226 If you say yes here you get support for the RTC subsystem of the
1227 NUC910/NUC920 used in embedded systems.
1230 tristate "IBM OPAL RTC driver"
1231 depends on PPC_POWERNV
1234 If you say yes here you get support for the PowerNV platform RTC
1235 driver based on OPAL interfaces.
1237 This driver can also be built as a module. If so, the module
1238 will be called rtc-opal.
1240 config RTC_DRV_ZYNQMP
1241 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1244 If you say yes here you get support for the RTC controller found on
1245 Xilinx Zynq Ultrascale+ MPSoC.
1247 config RTC_DRV_CROS_EC
1248 tristate "Chrome OS EC RTC driver"
1249 depends on MFD_CROS_EC
1251 If you say yes here you will get support for the
1252 Chrome OS Embedded Controller's RTC.
1254 This driver can also be built as a module. If so, the module
1255 will be called rtc-cros-ec.
1257 comment "on-CPU RTC drivers"
1259 config RTC_DRV_ASM9260
1260 tristate "Alphascale asm9260 RTC"
1261 depends on MACH_ASM9260 || COMPILE_TEST
1263 If you say yes here you get support for the RTC on the
1264 Alphascale asm9260 SoC.
1266 This driver can also be built as a module. If so, the module
1267 will be called rtc-asm9260.
1269 config RTC_DRV_DAVINCI
1270 tristate "TI DaVinci RTC"
1271 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1273 If you say yes here you get support for the RTC on the
1274 DaVinci platforms (DM365).
1276 This driver can also be built as a module. If so, the module
1277 will be called rtc-davinci.
1279 config RTC_DRV_DIGICOLOR
1280 tristate "Conexant Digicolor RTC"
1281 depends on ARCH_DIGICOLOR || COMPILE_TEST
1283 If you say yes here you get support for the RTC on Conexant
1284 Digicolor platforms. This currently includes the CX92755 SoC.
1286 This driver can also be built as a module. If so, the module
1287 will be called rtc-digicolor.
1289 config RTC_DRV_IMXDI
1290 tristate "Freescale IMX DryIce Real Time Clock"
1293 Support for Freescale IMX DryIce RTC
1295 This driver can also be built as a module, if so, the module
1296 will be called "rtc-imxdi".
1299 tristate "TI OMAP Real Time Clock"
1300 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1303 select GENERIC_PINCONF
1305 Say "yes" here to support the on chip real time clock
1306 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1308 This driver can also be built as a module, if so, module
1309 will be called rtc-omap.
1314 This will include RTC support for Samsung SoCs. If
1315 you want to include RTC support for any machine, kindly
1316 select this in the respective mach-XXXX/Kconfig file.
1319 tristate "Samsung S3C series SoC RTC"
1320 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1322 RTC (Realtime Clock) driver for the clock inbuilt into the
1323 Samsung S3C24XX series of SoCs. This can provide periodic
1324 interrupt rates from 1Hz to 64Hz for user programs, and
1327 The driver currently supports the common features on all the
1328 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1331 This driver can also be build as a module. If so, the module
1332 will be called rtc-s3c.
1334 config RTC_DRV_EP93XX
1335 tristate "Cirrus Logic EP93XX"
1336 depends on ARCH_EP93XX || COMPILE_TEST
1338 If you say yes here you get support for the
1339 RTC embedded in the Cirrus Logic EP93XX processors.
1341 This driver can also be built as a module. If so, the module
1342 will be called rtc-ep93xx.
1344 config RTC_DRV_SA1100
1345 tristate "SA11x0/PXA2xx/PXA910"
1346 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1348 If you say Y here you will get access to the real time clock
1349 built into your SA11x0 or PXA2xx CPU.
1351 To compile this driver as a module, choose M here: the
1352 module will be called rtc-sa1100.
1355 tristate "SuperH On-Chip RTC"
1356 depends on SUPERH || ARCH_RENESAS
1358 Say Y here to enable support for the on-chip RTC found in
1359 most SuperH processors. This RTC is also found in RZ/A SoCs.
1361 To compile this driver as a module, choose M here: the
1362 module will be called rtc-sh.
1364 config RTC_DRV_VR41XX
1365 tristate "NEC VR41XX"
1366 depends on CPU_VR41XX || COMPILE_TEST
1368 If you say Y here you will get access to the real time clock
1369 built into your NEC VR41XX CPU.
1371 To compile this driver as a module, choose M here: the
1372 module will be called rtc-vr41xx.
1374 config RTC_DRV_PL030
1375 tristate "ARM AMBA PL030 RTC"
1378 If you say Y here you will get access to ARM AMBA
1379 PrimeCell PL030 RTC found on certain ARM SOCs.
1381 To compile this driver as a module, choose M here: the
1382 module will be called rtc-pl030.
1384 config RTC_DRV_PL031
1385 tristate "ARM AMBA PL031 RTC"
1388 If you say Y here you will get access to ARM AMBA
1389 PrimeCell PL031 RTC found on certain ARM SOCs.
1391 To compile this driver as a module, choose M here: the
1392 module will be called rtc-pl031.
1394 config RTC_DRV_AT91RM9200
1395 tristate "AT91RM9200 or some AT91SAM9 RTC"
1396 depends on ARCH_AT91 || COMPILE_TEST
1398 Driver for the internal RTC (Realtime Clock) module found on
1399 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1400 this is powered by the backup power supply.
1402 config RTC_DRV_AT91SAM9
1403 tristate "AT91SAM9 RTT as RTC"
1404 depends on ARCH_AT91 || COMPILE_TEST
1405 depends on HAS_IOMEM
1408 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1409 can be used as an RTC thanks to the backup power supply (e.g. a
1410 small coin cell battery) which keeps this block and the GPBR
1411 (General Purpose Backup Registers) block powered when the device
1413 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1414 probably want to use the real RTC block instead of the "RTT as an
1417 config RTC_DRV_AU1XXX
1418 tristate "Au1xxx Counter0 RTC support"
1419 depends on MIPS_ALCHEMY
1421 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1422 counter) to be used as a RTC.
1424 This driver can also be built as a module. If so, the module
1425 will be called rtc-au1xxx.
1427 config RTC_DRV_RS5C313
1428 tristate "Ricoh RS5C313"
1429 depends on SH_LANDISK
1431 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1433 config RTC_DRV_GENERIC
1434 tristate "Generic RTC support"
1435 # Please consider writing a new RTC driver instead of using the generic
1437 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
1439 Say Y or M here to enable RTC support on systems using the generic
1440 RTC abstraction. If you do not know what you are doing, you should
1444 tristate "PXA27x/PXA3xx"
1446 select RTC_DRV_SA1100
1448 If you say Y here you will get access to the real time clock
1449 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1450 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1452 This RTC driver uses PXA RTC registers available since pxa27x
1453 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1455 config RTC_DRV_VT8500
1456 tristate "VIA/WonderMedia 85xx SoC RTC"
1457 depends on ARCH_VT8500 || COMPILE_TEST
1459 If you say Y here you will get access to the real time clock
1460 built into your VIA VT8500 SoC or its relatives.
1463 config RTC_DRV_SUN4V
1464 bool "SUN4V Hypervisor RTC"
1467 If you say Y here you will get support for the Hypervisor
1468 based RTC on SUN4V systems.
1470 config RTC_DRV_SUN6I
1471 bool "Allwinner A31 RTC"
1472 default MACH_SUN6I || MACH_SUN8I
1473 depends on COMMON_CLK
1474 depends on ARCH_SUNXI || COMPILE_TEST
1476 If you say Y here you will get support for the RTC found in
1477 some Allwinner SoCs like the A31 or the A64.
1479 config RTC_DRV_SUNXI
1480 tristate "Allwinner sun4i/sun7i RTC"
1481 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1483 If you say Y here you will get support for the RTC found on
1486 config RTC_DRV_STARFIRE
1490 If you say Y here you will get support for the RTC found on
1493 config RTC_DRV_TX4939
1494 tristate "TX4939 SoC"
1495 depends on SOC_TX4939 || COMPILE_TEST
1497 Driver for the internal RTC (Realtime Clock) module found on
1501 tristate "Marvell SoC RTC"
1502 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1504 If you say yes here you will get support for the in-chip RTC
1505 that can be found in some of Marvell's SoC devices, such as
1506 the Kirkwood 88F6281 and 88F6192.
1508 This driver can also be built as a module. If so, the module
1509 will be called rtc-mv.
1511 config RTC_DRV_ARMADA38X
1512 tristate "Armada 38x Marvell SoC RTC"
1513 depends on ARCH_MVEBU || COMPILE_TEST
1515 If you say yes here you will get support for the in-chip RTC
1516 that can be found in the Armada 38x Marvell's SoC device
1518 This driver can also be built as a module. If so, the module
1519 will be called armada38x-rtc.
1521 config RTC_DRV_FTRTC010
1522 tristate "Faraday Technology FTRTC010 RTC"
1523 depends on HAS_IOMEM
1526 If you say Y here you will get support for the
1527 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1529 This driver can also be built as a module. If so, the module
1530 will be called rtc-ftrtc010.
1536 If you say yes here you will get support for the RTC on PS3.
1538 This driver can also be built as a module. If so, the module
1539 will be called rtc-ps3.
1541 config RTC_DRV_COH901331
1542 tristate "ST-Ericsson COH 901 331 RTC"
1543 depends on ARCH_U300 || COMPILE_TEST
1545 If you say Y here you will get access to ST-Ericsson
1546 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1549 This driver can also be built as a module. If so, the module
1550 will be called "rtc-coh901331".
1554 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1555 depends on ARCH_MXS || COMPILE_TEST
1558 If you say yes here you will get support for the onboard
1559 STMP3xxx/i.MX23/i.MX28 RTC.
1561 This driver can also be built as a module. If so, the module
1562 will be called rtc-stmp3xxx.
1568 If you say Y here you will get support for the RTC found on
1569 the PCAP2 ASIC used on some Motorola phones.
1571 config RTC_DRV_MC13XXX
1572 depends on MFD_MC13XXX
1573 tristate "Freescale MC13xxx RTC"
1575 This enables support for the RTCs found on Freescale's PMICs
1576 MC13783 and MC13892.
1578 config RTC_DRV_MPC5121
1579 tristate "Freescale MPC5121 built-in RTC"
1580 depends on PPC_MPC512x || PPC_MPC52xx
1582 If you say yes here you will get support for the
1583 built-in RTC on MPC5121 or on MPC5200.
1585 This driver can also be built as a module. If so, the module
1586 will be called rtc-mpc5121.
1588 config RTC_DRV_JZ4740
1589 tristate "Ingenic JZ4740 SoC"
1590 depends on MACH_INGENIC || COMPILE_TEST
1592 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1595 This driver can also be built as a module. If so, the module
1596 will be called rtc-jz4740.
1598 config RTC_DRV_LPC24XX
1599 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1600 depends on ARCH_LPC18XX || COMPILE_TEST
1601 depends on OF && HAS_IOMEM
1603 This enables support for the NXP RTC found which can be found on
1604 NXP LPC178x/18xx/408x/43xx devices.
1606 If you have one of the devices above enable this driver to use
1607 the hardware RTC. This driver can also be built as a module. If
1608 so, the module will be called rtc-lpc24xx.
1610 config RTC_DRV_LPC32XX
1611 depends on ARCH_LPC32XX || COMPILE_TEST
1612 tristate "NXP LPC32XX RTC"
1614 This enables support for the NXP RTC in the LPC32XX
1616 This driver can also be built as a module. If so, the module
1617 will be called rtc-lpc32xx.
1619 config RTC_DRV_PM8XXX
1620 tristate "Qualcomm PMIC8XXX RTC"
1621 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1623 If you say yes here you get support for the
1624 Qualcomm PMIC8XXX RTC.
1626 To compile this driver as a module, choose M here: the
1627 module will be called rtc-pm8xxx.
1629 config RTC_DRV_TEGRA
1630 tristate "NVIDIA Tegra Internal RTC driver"
1631 depends on ARCH_TEGRA || COMPILE_TEST
1633 If you say yes here you get support for the
1634 Tegra 200 series internal RTC module.
1636 This drive can also be built as a module. If so, the module
1637 will be called rtc-tegra.
1640 tristate "PKUnity v3 RTC support"
1641 depends on ARCH_PUV3
1643 This enables support for the RTC in the PKUnity-v3 SoCs.
1645 This drive can also be built as a module. If so, the module
1646 will be called rtc-puv3.
1648 config RTC_DRV_LOONGSON1
1649 tristate "loongson1 RTC support"
1650 depends on MACH_LOONGSON32
1652 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1653 counter) to be used as a RTC.
1655 This driver can also be built as a module. If so, the module
1656 will be called rtc-ls1x.
1659 tristate "Freescale MXC Real Time Clock"
1662 If you say yes here you get support for the Freescale MXC
1665 This driver can also be built as a module, if so, the module
1666 will be called "rtc-mxc".
1668 config RTC_DRV_MXC_V2
1669 tristate "Freescale MXC Real Time Clock for i.MX53"
1672 If you say yes here you get support for the Freescale MXC
1673 SRTC module in i.MX53 processor.
1675 This driver can also be built as a module, if so, the module
1676 will be called "rtc-mxc_v2".
1679 tristate "Freescale SNVS RTC support"
1681 depends on HAS_IOMEM
1684 If you say yes here you get support for the Freescale SNVS
1685 Low Power (LP) RTC module.
1687 This driver can also be built as a module, if so, the module
1688 will be called "rtc-snvs".
1690 config RTC_DRV_SIRFSOC
1691 tristate "SiRFSOC RTC"
1692 depends on ARCH_SIRF
1694 Say "yes" here to support the real time clock on SiRF SOC chips.
1695 This driver can also be built as a module called rtc-sirfsoc.
1697 config RTC_DRV_ST_LPC
1698 tristate "STMicroelectronics LPC RTC"
1702 Say Y here to include STMicroelectronics Low Power Controller
1703 (LPC) based RTC support.
1705 To compile this driver as a module, choose M here: the
1706 module will be called rtc-st-lpc.
1708 config RTC_DRV_MOXART
1709 tristate "MOXA ART RTC"
1710 depends on ARCH_MOXART || COMPILE_TEST
1712 If you say yes here you get support for the MOXA ART
1715 This driver can also be built as a module. If so, the module
1716 will be called rtc-moxart
1718 config RTC_DRV_MT6397
1719 tristate "MediaTek PMIC based RTC"
1720 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1722 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1723 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1724 MediaTek(R) RTC driver.
1726 If you want to use MediaTek(R) RTC interface, select Y or M here.
1728 config RTC_DRV_MT7622
1729 tristate "MediaTek SoC based RTC"
1730 depends on ARCH_MEDIATEK || COMPILE_TEST
1732 This enables support for the real time clock built in the MediaTek
1735 This drive can also be built as a module. If so, the module
1736 will be called rtc-mt7622.
1738 config RTC_DRV_XGENE
1739 tristate "APM X-Gene RTC"
1740 depends on HAS_IOMEM
1741 depends on ARCH_XGENE || COMPILE_TEST
1743 If you say yes here you get support for the APM X-Gene SoC real time
1746 This driver can also be built as a module, if so, the module
1747 will be called "rtc-xgene".
1749 config RTC_DRV_PIC32
1750 tristate "Microchip PIC32 RTC"
1751 depends on MACH_PIC32
1754 If you say yes here you get support for the PIC32 RTC module.
1756 This driver can also be built as a module. If so, the module
1757 will be called rtc-pic32
1759 config RTC_DRV_R7301
1760 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1762 depends on OF && HAS_IOMEM
1764 If you say yes here you get support for the EPSON TOYOCOM
1765 RTC-7301SF/DG chips.
1767 This driver can also be built as a module. If so, the module
1768 will be called rtc-r7301.
1770 config RTC_DRV_STM32
1771 tristate "STM32 RTC"
1773 depends on ARCH_STM32 || COMPILE_TEST
1775 If you say yes here you get support for the STM32 On-Chip
1778 This driver can also be built as a module, if so, the module
1779 will be called "rtc-stm32".
1781 config RTC_DRV_CPCAP
1782 depends on MFD_CPCAP
1783 tristate "Motorola CPCAP RTC"
1785 Say y here for CPCAP rtc found on some Motorola phones
1786 and tablets such as Droid 4.
1788 config RTC_DRV_RTD119X
1789 bool "Realtek RTD129x RTC"
1790 depends on ARCH_REALTEK || COMPILE_TEST
1791 default ARCH_REALTEK
1793 If you say yes here, you get support for the RTD1295 SoC
1796 comment "HID Sensor RTC drivers"
1798 config RTC_DRV_HID_SENSOR_TIME
1799 tristate "HID Sensor Time"
1802 select HID_SENSOR_HUB
1803 select HID_SENSOR_IIO_COMMON
1805 Say yes here to build support for the HID Sensors of type Time.
1806 This drivers makes such sensors available as RTCs.
1808 If this driver is compiled as a module, it will be named
1809 rtc-hid-sensor-time.
1811 config RTC_DRV_GOLDFISH
1812 tristate "Goldfish Real Time Clock"
1813 depends on MIPS && (GOLDFISH || COMPILE_TEST)
1815 Say yes to enable RTC driver for the Goldfish based virtual platform.
1817 Goldfish is a code name for the virtual platform developed by Google
1818 for Android emulation.