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_HWMON
248 bool "HWMON support for rtc-ds1307"
249 depends on RTC_DRV_DS1307 && HWMON
250 depends on !(RTC_DRV_DS1307=y && HWMON=m)
253 Say Y here if you want to expose temperature sensor data on
254 rtc-ds1307 (only DS3231)
256 config RTC_DRV_DS1307_CENTURY
257 bool "Century bit support for rtc-ds1307"
258 depends on RTC_DRV_DS1307
261 The DS1307 driver suffered from a bug where it was enabling the
262 century bit inconditionnally but never used it when reading the time.
263 It made the driver unable to support dates beyond 2099.
264 Setting this option will add proper support for the century bit but if
265 the time was previously set using a kernel predating this option,
266 reading the date will return a date in the next century.
267 To solve that, you could boot a kernel without this option set, set
268 the RTC date and then boot a kernel with this option set.
270 config RTC_DRV_DS1374
271 tristate "Dallas/Maxim DS1374"
273 If you say yes here you get support for Dallas Semiconductor
274 DS1374 real-time clock chips. If an interrupt is associated
275 with the device, the alarm functionality is supported.
277 This driver can also be built as a module. If so, the module
278 will be called rtc-ds1374.
280 config RTC_DRV_DS1374_WDT
281 bool "Dallas/Maxim DS1374 watchdog timer"
282 depends on RTC_DRV_DS1374
284 If you say Y here you will get support for the
285 watchdog timer in the Dallas Semiconductor DS1374
286 real-time clock chips.
288 config RTC_DRV_DS1672
289 tristate "Dallas/Maxim DS1672"
291 If you say yes here you get support for the
292 Dallas/Maxim DS1672 timekeeping chip.
294 This driver can also be built as a module. If so, the module
295 will be called rtc-ds1672.
297 config RTC_DRV_HYM8563
298 tristate "Haoyu Microelectronics HYM8563"
301 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
302 from the usual rtc functions it provides a clock output of
305 This driver can also be built as a module. If so, the module
306 will be called rtc-hym8563.
308 config RTC_DRV_LP8788
309 tristate "TI LP8788 RTC driver"
310 depends on MFD_LP8788
312 Say Y to enable support for the LP8788 RTC/ALARM driver.
314 config RTC_DRV_MAX6900
315 tristate "Maxim MAX6900"
317 If you say yes here you will get support for the
318 Maxim MAX6900 I2C RTC chip.
320 This driver can also be built as a module. If so, the module
321 will be called rtc-max6900.
323 config RTC_DRV_MAX8907
324 tristate "Maxim MAX8907"
325 depends on MFD_MAX8907 || COMPILE_TEST
328 If you say yes here you will get support for the
329 RTC of Maxim MAX8907 PMIC.
331 This driver can also be built as a module. If so, the module
332 will be called rtc-max8907.
334 config RTC_DRV_MAX8925
335 tristate "Maxim MAX8925"
336 depends on MFD_MAX8925
338 If you say yes here you will get support for the
339 RTC of Maxim MAX8925 PMIC.
341 This driver can also be built as a module. If so, the module
342 will be called rtc-max8925.
344 config RTC_DRV_MAX8998
345 tristate "Maxim MAX8998"
346 depends on MFD_MAX8998
348 If you say yes here you will get support for the
349 RTC of Maxim MAX8998 PMIC.
351 This driver can also be built as a module. If so, the module
352 will be called rtc-max8998.
354 config RTC_DRV_MAX8997
355 tristate "Maxim MAX8997"
356 depends on MFD_MAX8997
358 If you say yes here you will get support for the
359 RTC of Maxim MAX8997 PMIC.
361 This driver can also be built as a module. If so, the module
362 will be called rtc-max8997.
364 config RTC_DRV_MAX77686
365 tristate "Maxim MAX77686"
366 depends on MFD_MAX77686 || MFD_MAX77620 || COMPILE_TEST
368 If you say yes here you will get support for the
369 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
371 This driver can also be built as a module. If so, the module
372 will be called rtc-max77686.
375 tristate "Rockchip RK805/RK808/RK818 RTC"
378 If you say yes here you will get support for the
379 RTC of RK805, RK808 and RK818 PMIC.
381 This driver can also be built as a module. If so, the module
382 will be called rk808-rtc.
384 config RTC_DRV_RS5C372
385 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
387 If you say yes here you get support for the
388 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
390 This driver can also be built as a module. If so, the module
391 will be called rtc-rs5c372.
393 config RTC_DRV_ISL1208
394 tristate "Intersil ISL1208"
396 If you say yes here you get support for the
397 Intersil ISL1208 RTC chip.
399 This driver can also be built as a module. If so, the module
400 will be called rtc-isl1208.
402 config RTC_DRV_ISL12022
403 tristate "Intersil ISL12022"
405 If you say yes here you get support for the
406 Intersil ISL12022 RTC chip.
408 This driver can also be built as a module. If so, the module
409 will be called rtc-isl12022.
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_PCF8563
438 tristate "Philips PCF8563/Epson RTC8564"
440 If you say yes here you get support for the
441 Philips PCF8563 RTC chip. The Epson RTC8564
444 This driver can also be built as a module. If so, the module
445 will be called rtc-pcf8563.
447 config RTC_DRV_PCF8583
448 tristate "Philips PCF8583"
450 If you say yes here you get support for the Philips PCF8583
451 RTC chip found on Acorn RiscPCs. This driver supports the
452 platform specific method of retrieving the current year from
453 the RTC's SRAM. It will work on other platforms with the same
454 chip, but the year will probably have to be tweaked.
456 This driver can also be built as a module. If so, the module
457 will be called rtc-pcf8583.
459 config RTC_DRV_M41T80
460 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
462 If you say Y here you will get support for the ST M41T60
463 and M41T80 RTC chips series. Currently, the following chips are
464 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
465 M41ST85, M41ST87, and MicroCrystal RV4162.
467 This driver can also be built as a module. If so, the module
468 will be called rtc-m41t80.
470 config RTC_DRV_M41T80_WDT
471 bool "ST M41T65/M41T80 series RTC watchdog timer"
472 depends on RTC_DRV_M41T80
474 If you say Y here you will get support for the
475 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
478 tristate "TI BQ32000"
480 If you say Y here you will get support for the TI
481 BQ32000 I2C RTC chip.
483 This driver can also be built as a module. If so, the module
484 will be called rtc-bq32k.
486 config RTC_DRV_DM355EVM
487 tristate "TI DaVinci DM355 EVM RTC"
488 depends on MFD_DM355EVM_MSP
490 Supports the RTC firmware in the MSP430 on the DM355 EVM.
492 config RTC_DRV_TWL92330
493 bool "TI TWL92330/Menelaus"
496 If you say yes here you get support for the RTC on the
497 TWL92330 "Menelaus" power management chip, used with OMAP2
498 platforms. The support is integrated with the rest of
499 the Menelaus driver; it's not separate module.
501 config RTC_DRV_TWL4030
502 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
503 depends on TWL4030_CORE
506 If you say yes here you get support for the RTC on the
507 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
509 This driver can also be built as a module. If so, the module
510 will be called rtc-twl.
512 config RTC_DRV_PALMAS
513 tristate "TI Palmas RTC driver"
514 depends on MFD_PALMAS
516 If you say yes here you get support for the RTC of TI PALMA series PMIC
519 This driver can also be built as a module. If so, the module
520 will be called rtc-palma.
522 config RTC_DRV_TPS6586X
523 tristate "TI TPS6586X RTC driver"
524 depends on MFD_TPS6586X
526 TI Power Management IC TPS6586X supports RTC functionality
527 along with alarm. This driver supports the RTC driver for
528 the TPS6586X RTC module.
530 config RTC_DRV_TPS65910
531 tristate "TI TPS65910 RTC driver"
532 depends on RTC_CLASS && MFD_TPS65910
534 If you say yes here you get support for the RTC on the
537 This driver can also be built as a module. If so, the module
538 will be called rtc-tps65910.
540 config RTC_DRV_TPS80031
541 tristate "TI TPS80031/TPS80032 RTC driver"
542 depends on MFD_TPS80031
544 TI Power Management IC TPS80031 supports RTC functionality
545 along with alarm. This driver supports the RTC driver for
546 the TPS80031 RTC module.
548 config RTC_DRV_RC5T583
549 tristate "RICOH 5T583 RTC driver"
550 depends on MFD_RC5T583
552 If you say yes here you get support for the RTC on the
555 This driver can also be built as a module. If so, the module
556 will be called rtc-rc5t583.
558 config RTC_DRV_S35390A
559 tristate "Seiko Instruments S-35390A"
562 If you say yes here you will get support for the Seiko
563 Instruments S-35390A.
565 This driver can also be built as a module. If so the module
566 will be called rtc-s35390a.
568 config RTC_DRV_FM3130
569 tristate "Ramtron FM3130"
571 If you say Y here you will get support for the
572 Ramtron FM3130 RTC chips.
573 Ramtron FM3130 is a chip with two separate devices inside,
574 RTC clock and FRAM. This driver provides only RTC functionality.
576 This driver can also be built as a module. If so the module
577 will be called rtc-fm3130.
579 config RTC_DRV_RX8010
580 tristate "Epson RX8010SJ"
583 If you say yes here you get support for the Epson RX8010SJ RTC
586 This driver can also be built as a module. If so, the module
587 will be called rtc-rx8010.
589 config RTC_DRV_RX8581
590 tristate "Epson RX-8581"
592 If you say yes here you will get support for the Epson RX-8581.
594 This driver can also be built as a module. If so the module
595 will be called rtc-rx8581.
597 config RTC_DRV_RX8025
598 tristate "Epson RX-8025SA/NB"
600 If you say yes here you get support for the Epson
601 RX-8025SA/NB RTC chips.
603 This driver can also be built as a module. If so, the module
604 will be called rtc-rx8025.
606 config RTC_DRV_EM3027
607 tristate "EM Microelectronic EM3027"
609 If you say yes here you get support for the EM
610 Microelectronic EM3027 RTC chips.
612 This driver can also be built as a module. If so, the module
613 will be called rtc-em3027.
615 config RTC_DRV_RV8803
616 tristate "Micro Crystal RV8803, Epson RX8900"
618 If you say yes here you get support for the Micro Crystal RV8803 and
619 Epson RX8900 RTC chips.
621 This driver can also be built as a module. If so, the module
622 will be called rtc-rv8803.
625 tristate "Samsung S2M/S5M series"
626 depends on MFD_SEC_CORE || COMPILE_TEST
630 If you say yes here you will get support for the
631 RTC of Samsung S2MPS14 and S5M PMIC series.
633 This driver can also be built as a module. If so, the module
634 will be called rtc-s5m.
638 comment "SPI RTC drivers"
642 config RTC_DRV_M41T93
645 If you say yes here you will get support for the
646 ST M41T93 SPI RTC chip.
648 This driver can also be built as a module. If so, the module
649 will be called rtc-m41t93.
651 config RTC_DRV_M41T94
654 If you say yes here you will get support for the
655 ST M41T94 SPI RTC chip.
657 This driver can also be built as a module. If so, the module
658 will be called rtc-m41t94.
660 config RTC_DRV_DS1302
661 tristate "Dallas/Maxim DS1302"
664 If you say yes here you get support for the Dallas DS1302 RTC chips.
666 This driver can also be built as a module. If so, the module
667 will be called rtc-ds1302.
669 config RTC_DRV_DS1305
670 tristate "Dallas/Maxim DS1305/DS1306"
672 Select this driver to get support for the Dallas/Maxim DS1305
673 and DS1306 real time clock chips. These support a trickle
674 charger, alarms, and NVRAM in addition to the clock.
676 This driver can also be built as a module. If so, the module
677 will be called rtc-ds1305.
679 config RTC_DRV_DS1343
681 tristate "Dallas/Maxim DS1343/DS1344"
683 If you say yes here you get support for the
684 Dallas/Maxim DS1343 and DS1344 real time clock chips.
685 Support for trickle charger, alarm is provided.
687 This driver can also be built as a module. If so, the module
688 will be called rtc-ds1343.
690 config RTC_DRV_DS1347
692 tristate "Dallas/Maxim DS1347"
694 If you say yes here you get support for the
695 Dallas/Maxim DS1347 chips.
697 This driver only supports the RTC feature, and not other chip
698 features such as alarms.
700 This driver can also be built as a module. If so, the module
701 will be called rtc-ds1347.
703 config RTC_DRV_DS1390
704 tristate "Dallas/Maxim DS1390/93/94"
706 If you say yes here you get support for the
707 Dallas/Maxim DS1390/93/94 chips.
709 This driver supports the RTC feature and trickle charging but not
710 other chip features such as alarms.
712 This driver can also be built as a module. If so, the module
713 will be called rtc-ds1390.
715 config RTC_DRV_MAX6916
716 tristate "Maxim MAX6916"
718 If you say yes here you will get support for the
719 Maxim MAX6916 SPI RTC chip.
721 This driver only supports the RTC feature, and not other chip
722 features such as alarms.
724 This driver can also be built as a module. If so, the module
725 will be called rtc-max6916.
728 tristate "Epson RTC-9701JE"
730 If you say yes here you will get support for the
731 Epson RTC-9701JE SPI RTC chip.
733 This driver can also be built as a module. If so, the module
734 will be called rtc-r9701.
736 config RTC_DRV_RX4581
737 tristate "Epson RX-4581"
739 If you say yes here you will get support for the Epson RX-4581.
741 This driver can also be built as a module. If so the module
742 will be called rtc-rx4581.
744 config RTC_DRV_RX6110
745 tristate "Epson RX-6110"
748 If you say yes here you will get support for the Epson RX-6610.
750 This driver can also be built as a module. If so the module
751 will be called rtc-rx6110.
753 config RTC_DRV_RS5C348
754 tristate "Ricoh RS5C348A/B"
756 If you say yes here you get support for the
757 Ricoh RS5C348A and RS5C348B RTC chips.
759 This driver can also be built as a module. If so, the module
760 will be called rtc-rs5c348.
762 config RTC_DRV_MAX6902
763 tristate "Maxim MAX6902"
765 If you say yes here you will get support for the
766 Maxim MAX6902 SPI RTC chip.
768 This driver can also be built as a module. If so, the module
769 will be called rtc-max6902.
771 config RTC_DRV_PCF2123
772 tristate "NXP PCF2123"
774 If you say yes here you get support for the NXP PCF2123
777 This driver can also be built as a module. If so, the module
778 will be called rtc-pcf2123.
780 config RTC_DRV_MCP795
781 tristate "Microchip MCP795"
783 If you say yes here you will get support for the Microchip MCP795.
785 This driver can also be built as a module. If so the module
786 will be called rtc-mcp795.
791 # Helper to resolve issues with configs that have SPI enabled but I2C
792 # modular. See SND_SOC_I2C_AND_SPI for more information
794 config RTC_I2C_AND_SPI
798 default y if SPI_MASTER=y
799 select REGMAP_I2C if I2C
800 select REGMAP_SPI if SPI_MASTER
802 comment "SPI and I2C RTC drivers"
804 config RTC_DRV_DS3232
805 tristate "Dallas/Maxim DS3232/DS3234"
806 depends on RTC_I2C_AND_SPI
808 If you say yes here you get support for Dallas Semiconductor
809 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
810 with the device, the alarm functionality is supported.
812 This driver can also be built as a module. If so, the module
813 will be called rtc-ds3232.
815 config RTC_DRV_DS3232_HWMON
816 bool "HWMON support for Dallas/Maxim DS3232/DS3234"
817 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
820 Say Y here if you want to expose temperature sensor data on
823 config RTC_DRV_PCF2127
824 tristate "NXP PCF2127"
825 depends on RTC_I2C_AND_SPI
827 If you say yes here you get support for the NXP PCF2127/29 RTC
830 This driver can also be built as a module. If so, the module
831 will be called rtc-pcf2127.
833 config RTC_DRV_RV3029C2
834 tristate "Micro Crystal RV3029/3049"
835 depends on RTC_I2C_AND_SPI
837 If you say yes here you get support for the Micro Crystal
838 RV3029 and RV3049 RTC chips.
840 This driver can also be built as a module. If so, the module
841 will be called rtc-rv3029c2.
843 config RTC_DRV_RV3029_HWMON
844 bool "HWMON support for RV3029/3049"
845 depends on RTC_DRV_RV3029C2 && HWMON
846 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
849 Say Y here if you want to expose temperature sensor data on
852 comment "Platform RTC drivers"
854 # this 'CMOS' RTC driver is arch dependent because it requires
855 # <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
856 # global rtc_lock ... it's not yet just another platform_device.
859 tristate "PC-style 'CMOS'"
860 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64 || MN10300
862 select RTC_MC146818_LIB
864 Say "yes" here to get direct support for the real time clock
865 found in every PC or ACPI-based system, and some other boards.
866 Specifically the original MC146818, compatibles like those in
867 PC south bridges, the DS12887 or M48T86, some multifunction
868 or LPC bus chips, and so on.
870 Your system will need to define the platform device used by
871 this driver, otherwise it won't be accessible. This means
872 you can safely enable this driver if you don't know whether
873 or not your board has this kind of hardware.
875 This driver can also be built as a module. If so, the module
876 will be called rtc-cmos.
879 bool "Alpha PC-style CMOS"
881 select RTC_MC146818_LIB
884 Direct support for the real-time clock found on every Alpha
885 system, specifically MC146818 compatibles. If in doubt, say Y.
888 tristate "Virtual RTC for Intel MID platforms"
889 depends on X86_INTEL_MID
890 default y if X86_INTEL_MID
893 Say "yes" here to get direct support for the real time clock
894 found on Moorestown platforms. The VRTC is a emulated RTC that
895 derives its clock source from a real RTC in the PMIC. The MC146818
896 style programming interface is mostly conserved, but any
897 updates are done via IPC calls to the system controller FW.
899 config RTC_DRV_DS1216
900 tristate "Dallas DS1216"
903 If you say yes here you get support for the Dallas DS1216 RTC chips.
905 config RTC_DRV_DS1286
906 tristate "Dallas DS1286"
909 If you say yes here you get support for the Dallas DS1286 RTC chips.
911 config RTC_DRV_DS1511
912 tristate "Dallas DS1511"
915 If you say yes here you get support for the
916 Dallas DS1511 timekeeping/watchdog chip.
918 This driver can also be built as a module. If so, the module
919 will be called rtc-ds1511.
921 config RTC_DRV_DS1553
922 tristate "Maxim/Dallas DS1553"
925 If you say yes here you get support for the
926 Maxim/Dallas DS1553 timekeeping chip.
928 This driver can also be built as a module. If so, the module
929 will be called rtc-ds1553.
931 config RTC_DRV_DS1685_FAMILY
932 tristate "Dallas/Maxim DS1685 Family"
934 If you say yes here you get support for the Dallas/Maxim DS1685
935 family of real time chips. This family includes the DS1685/DS1687,
936 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
937 DS17885/DS17887 chips.
939 This driver can also be built as a module. If so, the module
940 will be called rtc-ds1685.
944 depends on RTC_DRV_DS1685_FAMILY
945 default RTC_DRV_DS1685
947 config RTC_DRV_DS1685
950 This enables support for the Dallas/Maxim DS1685/DS1687 real time
953 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
954 systems, as well as EPPC-405-UC modules by electronic system design
957 config RTC_DRV_DS1689
960 This enables support for the Dallas/Maxim DS1689/DS1693 real time
963 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
964 which supports a few minor features such as Vcc, Vbat, and Power
965 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
967 It also works for the even older DS1688/DS1691 RTC chips, which are
968 virtually the same and carry the same model number. Both chips
969 have 114 bytes of user NVRAM.
971 config RTC_DRV_DS17285
972 bool "DS17285/DS17287"
974 This enables support for the Dallas/Maxim DS17285/DS17287 real time
977 This chip features 2kb of extended NV-SRAM. It may possibly be
978 found in some SGI O2 systems (rare).
980 config RTC_DRV_DS17485
981 bool "DS17485/DS17487"
983 This enables support for the Dallas/Maxim DS17485/DS17487 real time
986 This chip features 4kb of extended NV-SRAM.
988 config RTC_DRV_DS17885
989 bool "DS17885/DS17887"
991 This enables support for the Dallas/Maxim DS17885/DS17887 real time
994 This chip features 8kb of extended NV-SRAM.
998 config RTC_DS1685_PROC_REGS
999 bool "Display register values in /proc"
1000 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
1002 Enable this to display a readout of all of the RTC registers in
1003 /proc/drivers/rtc. Keep in mind that this can potentially lead
1004 to lost interrupts, as reading Control Register C will clear
1005 all pending IRQ flags.
1007 Unless you are debugging this driver, choose N.
1009 config RTC_DS1685_SYSFS_REGS
1010 bool "SysFS access to RTC register bits"
1011 depends on RTC_DRV_DS1685_FAMILY && SYSFS
1013 Enable this to provide access to the RTC control register bits
1014 in /sys. Some of the bits are read-write, others are read-only.
1016 Keep in mind that reading Control C's bits automatically clears
1017 all pending IRQ flags - this can cause lost interrupts.
1019 If you know that you need access to these bits, choose Y, Else 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_SPEAR
1180 tristate "SPEAR ST RTC"
1181 depends on PLAT_SPEAR || COMPILE_TEST
1184 If you say Y here you will get support for the RTC found on
1187 config RTC_DRV_PCF50633
1188 depends on MFD_PCF50633
1189 tristate "NXP PCF50633 RTC"
1191 If you say yes here you get support for the RTC subsystem of the
1192 NXP PCF50633 used in embedded systems.
1194 config RTC_DRV_AB3100
1195 tristate "ST-Ericsson AB3100 RTC"
1196 depends on AB3100_CORE
1197 default y if AB3100_CORE
1199 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1200 support. This chip contains a battery- and capacitor-backed RTC.
1202 config RTC_DRV_AB8500
1203 tristate "ST-Ericsson AB8500 RTC"
1204 depends on AB8500_CORE
1206 select RTC_INTF_DEV_UIE_EMUL
1208 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1209 support. This chip contains a battery- and capacitor-backed RTC.
1211 config RTC_DRV_NUC900
1212 tristate "NUC910/NUC920 RTC driver"
1213 depends on ARCH_W90X900 || COMPILE_TEST
1215 If you say yes here you get support for the RTC subsystem of the
1216 NUC910/NUC920 used in embedded systems.
1219 tristate "IBM OPAL RTC driver"
1220 depends on PPC_POWERNV
1223 If you say yes here you get support for the PowerNV platform RTC
1224 driver based on OPAL interfaces.
1226 This driver can also be built as a module. If so, the module
1227 will be called rtc-opal.
1229 config RTC_DRV_ZYNQMP
1230 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1233 If you say yes here you get support for the RTC controller found on
1234 Xilinx Zynq Ultrascale+ MPSoC.
1236 comment "on-CPU RTC drivers"
1238 config RTC_DRV_ASM9260
1239 tristate "Alphascale asm9260 RTC"
1240 depends on MACH_ASM9260 || COMPILE_TEST
1242 If you say yes here you get support for the RTC on the
1243 Alphascale asm9260 SoC.
1245 This driver can also be built as a module. If so, the module
1246 will be called rtc-asm9260.
1248 config RTC_DRV_DAVINCI
1249 tristate "TI DaVinci RTC"
1250 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1252 If you say yes here you get support for the RTC on the
1253 DaVinci platforms (DM365).
1255 This driver can also be built as a module. If so, the module
1256 will be called rtc-davinci.
1258 config RTC_DRV_DIGICOLOR
1259 tristate "Conexant Digicolor RTC"
1260 depends on ARCH_DIGICOLOR || COMPILE_TEST
1262 If you say yes here you get support for the RTC on Conexant
1263 Digicolor platforms. This currently includes the CX92755 SoC.
1265 This driver can also be built as a module. If so, the module
1266 will be called rtc-digicolor.
1268 config RTC_DRV_IMXDI
1269 tristate "Freescale IMX DryIce Real Time Clock"
1272 Support for Freescale IMX DryIce RTC
1274 This driver can also be built as a module, if so, the module
1275 will be called "rtc-imxdi".
1278 tristate "TI OMAP Real Time Clock"
1279 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1282 select GENERIC_PINCONF
1284 Say "yes" here to support the on chip real time clock
1285 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1287 This driver can also be built as a module, if so, module
1288 will be called rtc-omap.
1293 This will include RTC support for Samsung SoCs. If
1294 you want to include RTC support for any machine, kindly
1295 select this in the respective mach-XXXX/Kconfig file.
1298 tristate "Samsung S3C series SoC RTC"
1299 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1301 RTC (Realtime Clock) driver for the clock inbuilt into the
1302 Samsung S3C24XX series of SoCs. This can provide periodic
1303 interrupt rates from 1Hz to 64Hz for user programs, and
1306 The driver currently supports the common features on all the
1307 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1310 This driver can also be build as a module. If so, the module
1311 will be called rtc-s3c.
1313 config RTC_DRV_EP93XX
1314 tristate "Cirrus Logic EP93XX"
1315 depends on ARCH_EP93XX || COMPILE_TEST
1317 If you say yes here you get support for the
1318 RTC embedded in the Cirrus Logic EP93XX processors.
1320 This driver can also be built as a module. If so, the module
1321 will be called rtc-ep93xx.
1323 config RTC_DRV_SA1100
1324 tristate "SA11x0/PXA2xx/PXA910"
1325 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1327 If you say Y here you will get access to the real time clock
1328 built into your SA11x0 or PXA2xx CPU.
1330 To compile this driver as a module, choose M here: the
1331 module will be called rtc-sa1100.
1334 tristate "SuperH On-Chip RTC"
1335 depends on SUPERH || ARCH_RENESAS
1337 Say Y here to enable support for the on-chip RTC found in
1338 most SuperH processors. This RTC is also found in RZ/A SoCs.
1340 To compile this driver as a module, choose M here: the
1341 module will be called rtc-sh.
1343 config RTC_DRV_VR41XX
1344 tristate "NEC VR41XX"
1345 depends on CPU_VR41XX || COMPILE_TEST
1347 If you say Y here you will get access to the real time clock
1348 built into your NEC VR41XX CPU.
1350 To compile this driver as a module, choose M here: the
1351 module will be called rtc-vr41xx.
1353 config RTC_DRV_PL030
1354 tristate "ARM AMBA PL030 RTC"
1357 If you say Y here you will get access to ARM AMBA
1358 PrimeCell PL030 RTC found on certain ARM SOCs.
1360 To compile this driver as a module, choose M here: the
1361 module will be called rtc-pl030.
1363 config RTC_DRV_PL031
1364 tristate "ARM AMBA PL031 RTC"
1367 If you say Y here you will get access to ARM AMBA
1368 PrimeCell PL031 RTC found on certain ARM SOCs.
1370 To compile this driver as a module, choose M here: the
1371 module will be called rtc-pl031.
1373 config RTC_DRV_AT32AP700X
1374 tristate "AT32AP700X series RTC"
1375 depends on PLATFORM_AT32AP || COMPILE_TEST
1377 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1378 AT32AP700x family processors.
1380 config RTC_DRV_AT91RM9200
1381 tristate "AT91RM9200 or some AT91SAM9 RTC"
1382 depends on ARCH_AT91 || COMPILE_TEST
1384 Driver for the internal RTC (Realtime Clock) module found on
1385 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1386 this is powered by the backup power supply.
1388 config RTC_DRV_AT91SAM9
1389 tristate "AT91SAM9 RTT as RTC"
1390 depends on ARCH_AT91 || COMPILE_TEST
1393 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1394 can be used as an RTC thanks to the backup power supply (e.g. a
1395 small coin cell battery) which keeps this block and the GPBR
1396 (General Purpose Backup Registers) block powered when the device
1398 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1399 probably want to use the real RTC block instead of the "RTT as an
1402 config RTC_DRV_AU1XXX
1403 tristate "Au1xxx Counter0 RTC support"
1404 depends on MIPS_ALCHEMY
1406 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1407 counter) to be used as a RTC.
1409 This driver can also be built as a module. If so, the module
1410 will be called rtc-au1xxx.
1413 tristate "Blackfin On-Chip RTC"
1414 depends on BLACKFIN && !BF561
1416 If you say yes here you will get support for the
1417 Blackfin On-Chip Real Time Clock.
1419 This driver can also be built as a module. If so, the module
1420 will be called rtc-bfin.
1422 config RTC_DRV_RS5C313
1423 tristate "Ricoh RS5C313"
1424 depends on SH_LANDISK
1426 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1428 config RTC_DRV_GENERIC
1429 tristate "Generic RTC support"
1430 # Please consider writing a new RTC driver instead of using the generic
1432 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
1434 Say Y or M here to enable RTC support on systems using the generic
1435 RTC abstraction. If you do not know what you are doing, you should
1439 tristate "PXA27x/PXA3xx"
1441 select RTC_DRV_SA1100
1443 If you say Y here you will get access to the real time clock
1444 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1445 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1447 This RTC driver uses PXA RTC registers available since pxa27x
1448 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1450 config RTC_DRV_VT8500
1451 tristate "VIA/WonderMedia 85xx SoC RTC"
1452 depends on ARCH_VT8500 || COMPILE_TEST
1454 If you say Y here you will get access to the real time clock
1455 built into your VIA VT8500 SoC or its relatives.
1458 config RTC_DRV_SUN4V
1459 bool "SUN4V Hypervisor RTC"
1462 If you say Y here you will get support for the Hypervisor
1463 based RTC on SUN4V systems.
1465 config RTC_DRV_SUN6I
1466 bool "Allwinner A31 RTC"
1467 default MACH_SUN6I || MACH_SUN8I
1468 depends on COMMON_CLK
1469 depends on ARCH_SUNXI || COMPILE_TEST
1471 If you say Y here you will get support for the RTC found in
1472 some Allwinner SoCs like the A31 or the A64.
1474 config RTC_DRV_SUNXI
1475 tristate "Allwinner sun4i/sun7i RTC"
1476 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1478 If you say Y here you will get support for the RTC found on
1481 config RTC_DRV_STARFIRE
1485 If you say Y here you will get support for the RTC found on
1488 config RTC_DRV_TX4939
1489 tristate "TX4939 SoC"
1490 depends on SOC_TX4939
1492 Driver for the internal RTC (Realtime Clock) module found on
1496 tristate "Marvell SoC RTC"
1497 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1499 If you say yes here you will get support for the in-chip RTC
1500 that can be found in some of Marvell's SoC devices, such as
1501 the Kirkwood 88F6281 and 88F6192.
1503 This driver can also be built as a module. If so, the module
1504 will be called rtc-mv.
1506 config RTC_DRV_ARMADA38X
1507 tristate "Armada 38x Marvell SoC RTC"
1508 depends on ARCH_MVEBU || COMPILE_TEST
1510 If you say yes here you will get support for the in-chip RTC
1511 that can be found in the Armada 38x Marvell's SoC device
1513 This driver can also be built as a module. If so, the module
1514 will be called armada38x-rtc.
1516 config RTC_DRV_FTRTC010
1517 tristate "Faraday Technology FTRTC010 RTC"
1518 depends on HAS_IOMEM
1521 If you say Y here you will get support for the
1522 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1524 This driver can also be built as a module. If so, the module
1525 will be called rtc-ftrtc010.
1531 If you say yes here you will get support for the RTC on PS3.
1533 This driver can also be built as a module. If so, the module
1534 will be called rtc-ps3.
1536 config RTC_DRV_COH901331
1537 tristate "ST-Ericsson COH 901 331 RTC"
1538 depends on ARCH_U300 || COMPILE_TEST
1540 If you say Y here you will get access to ST-Ericsson
1541 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1544 This driver can also be built as a module. If so, the module
1545 will be called "rtc-coh901331".
1549 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1550 depends on ARCH_MXS || COMPILE_TEST
1553 If you say yes here you will get support for the onboard
1554 STMP3xxx/i.MX23/i.MX28 RTC.
1556 This driver can also be built as a module. If so, the module
1557 will be called rtc-stmp3xxx.
1563 If you say Y here you will get support for the RTC found on
1564 the PCAP2 ASIC used on some Motorola phones.
1566 config RTC_DRV_MC13XXX
1567 depends on MFD_MC13XXX
1568 tristate "Freescale MC13xxx RTC"
1570 This enables support for the RTCs found on Freescale's PMICs
1571 MC13783 and MC13892.
1573 config RTC_DRV_MPC5121
1574 tristate "Freescale MPC5121 built-in RTC"
1575 depends on PPC_MPC512x || PPC_MPC52xx
1577 If you say yes here you will get support for the
1578 built-in RTC on MPC5121 or on MPC5200.
1580 This driver can also be built as a module. If so, the module
1581 will be called rtc-mpc5121.
1583 config RTC_DRV_JZ4740
1584 tristate "Ingenic JZ4740 SoC"
1585 depends on MACH_INGENIC || COMPILE_TEST
1587 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1590 This driver can also be buillt as a module. If so, the module
1591 will be called rtc-jz4740.
1593 config RTC_DRV_LPC24XX
1594 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1595 depends on ARCH_LPC18XX || COMPILE_TEST
1596 depends on OF && HAS_IOMEM
1598 This enables support for the NXP RTC found which can be found on
1599 NXP LPC178x/18xx/408x/43xx devices.
1601 If you have one of the devices above enable this driver to use
1602 the hardware RTC. This driver can also be built as a module. If
1603 so, the module will be called rtc-lpc24xx.
1605 config RTC_DRV_LPC32XX
1606 depends on ARCH_LPC32XX || COMPILE_TEST
1607 tristate "NXP LPC32XX RTC"
1609 This enables support for the NXP RTC in the LPC32XX
1611 This driver can also be built as a module. If so, the module
1612 will be called rtc-lpc32xx.
1614 config RTC_DRV_PM8XXX
1615 tristate "Qualcomm PMIC8XXX RTC"
1616 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1618 If you say yes here you get support for the
1619 Qualcomm PMIC8XXX RTC.
1621 To compile this driver as a module, choose M here: the
1622 module will be called rtc-pm8xxx.
1624 config RTC_DRV_TEGRA
1625 tristate "NVIDIA Tegra Internal RTC driver"
1626 depends on ARCH_TEGRA || COMPILE_TEST
1628 If you say yes here you get support for the
1629 Tegra 200 series internal RTC module.
1631 This drive can also be built as a module. If so, the module
1632 will be called rtc-tegra.
1635 tristate "Tilera hypervisor RTC support"
1638 Enable support for the Linux driver side of the Tilera
1639 hypervisor's real-time clock interface.
1642 tristate "PKUnity v3 RTC support"
1643 depends on ARCH_PUV3
1645 This enables support for the RTC in the PKUnity-v3 SoCs.
1647 This drive can also be built as a module. If so, the module
1648 will be called rtc-puv3.
1650 config RTC_DRV_LOONGSON1
1651 tristate "loongson1 RTC support"
1652 depends on MACH_LOONGSON32
1654 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1655 counter) to be used as a RTC.
1657 This driver can also be built as a module. If so, the module
1658 will be called rtc-ls1x.
1661 tristate "Freescale MXC Real Time Clock"
1664 If you say yes here you get support for the Freescale MXC
1667 This driver can also be built as a module, if so, the module
1668 will be called "rtc-mxc".
1671 tristate "Freescale SNVS RTC support"
1673 depends on HAS_IOMEM
1676 If you say yes here you get support for the Freescale SNVS
1677 Low Power (LP) RTC module.
1679 This driver can also be built as a module, if so, the module
1680 will be called "rtc-snvs".
1682 config RTC_DRV_SIRFSOC
1683 tristate "SiRFSOC RTC"
1684 depends on ARCH_SIRF
1686 Say "yes" here to support the real time clock on SiRF SOC chips.
1687 This driver can also be built as a module called rtc-sirfsoc.
1689 config RTC_DRV_ST_LPC
1690 tristate "STMicroelectronics LPC RTC"
1694 Say Y here to include STMicroelectronics Low Power Controller
1695 (LPC) based RTC support.
1697 To compile this driver as a module, choose M here: the
1698 module will be called rtc-st-lpc.
1700 config RTC_DRV_MOXART
1701 tristate "MOXA ART RTC"
1702 depends on ARCH_MOXART || COMPILE_TEST
1704 If you say yes here you get support for the MOXA ART
1707 This driver can also be built as a module. If so, the module
1708 will be called rtc-moxart
1710 config RTC_DRV_MT6397
1711 tristate "Mediatek Real Time Clock driver"
1712 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1714 This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
1715 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1716 Mediatek(R) RTC driver.
1718 If you want to use Mediatek(R) RTC interface, select Y or M here.
1720 config RTC_DRV_XGENE
1721 tristate "APM X-Gene RTC"
1722 depends on HAS_IOMEM
1723 depends on ARCH_XGENE || COMPILE_TEST
1725 If you say yes here you get support for the APM X-Gene SoC real time
1728 This driver can also be built as a module, if so, the module
1729 will be called "rtc-xgene".
1731 config RTC_DRV_PIC32
1732 tristate "Microchip PIC32 RTC"
1733 depends on MACH_PIC32
1736 If you say yes here you get support for the PIC32 RTC module.
1738 This driver can also be built as a module. If so, the module
1739 will be called rtc-pic32
1741 config RTC_DRV_R7301
1742 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1744 depends on OF && HAS_IOMEM
1746 If you say yes here you get support for the EPSON TOYOCOM
1747 RTC-7301SF/DG chips.
1749 This driver can also be built as a module. If so, the module
1750 will be called rtc-r7301.
1752 config RTC_DRV_STM32
1753 tristate "STM32 RTC"
1755 depends on ARCH_STM32 || COMPILE_TEST
1757 If you say yes here you get support for the STM32 On-Chip
1760 This driver can also be built as a module, if so, the module
1761 will be called "rtc-stm32".
1763 config RTC_DRV_CPCAP
1764 depends on MFD_CPCAP
1765 tristate "Motorola CPCAP RTC"
1767 Say y here for CPCAP rtc found on some Motorola phones
1768 and tablets such as Droid 4.
1770 config RTC_DRV_RTD119X
1771 bool "Realtek RTD129x RTC"
1772 depends on ARCH_REALTEK || COMPILE_TEST
1773 default ARCH_REALTEK
1775 If you say yes here, you get support for the RTD1295 SoC
1778 comment "HID Sensor RTC drivers"
1780 config RTC_DRV_HID_SENSOR_TIME
1781 tristate "HID Sensor Time"
1784 select HID_SENSOR_HUB
1785 select HID_SENSOR_IIO_COMMON
1787 Say yes here to build support for the HID Sensors of type Time.
1788 This drivers makes such sensors available as RTCs.
1790 If this driver is compiled as a module, it will be named
1791 rtc-hid-sensor-time.
1793 config RTC_DRV_GOLDFISH
1794 tristate "Goldfish Real Time Clock"
1795 depends on MIPS && (GOLDFISH || COMPILE_TEST)
1797 Say yes to enable RTC driver for the Goldfish based virtual platform.
1799 Goldfish is a code name for the virtual platform developed by Google
1800 for Android emulation.