2 # RTC class/drivers configuration
11 depends on !S390 && !UML
14 Generic RTC class support. If you say yes here, you will
15 be allowed to plug one or more RTCs to your system. You will
16 probably want to enable one or more of the interfaces below.
21 bool "Set system time from RTC on startup and resume"
24 If you say yes here, the system time (wall clock) will be set using
25 the value read from a specified RTC device. This is useful to avoid
26 unnecessary fsck runs at boot time, and to network better.
28 config RTC_HCTOSYS_DEVICE
29 string "RTC used to set the system time"
30 depends on RTC_HCTOSYS
33 The RTC device that will be used to (re)initialize the system
34 clock, usually rtc0. Initialization is done when the system
35 starts up, and when it resumes from a low power state. This
36 device should record time in UTC, since the kernel won't do
39 The driver for this RTC device must be loaded before late_initcall
40 functions run, so it must usually be statically linked.
42 This clock should be battery-backed, so that it reads the correct
43 time when the system boots from a power-off state. Otherwise, your
44 system will need an external clock source (like an NTP server).
46 If the clock you specify here is not battery backed, it may still
47 be useful to reinitialize system time when resuming from system
48 sleep states. Do not specify an RTC here unless it stays powered
49 during all this system's supported sleep states.
52 bool "Set the RTC time based on NTP synchronization"
55 If you say yes here, the system time (wall clock) will be stored
56 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
57 minutes if userspace reports synchronized NTP status.
59 config RTC_SYSTOHC_DEVICE
60 string "RTC used to synchronize NTP adjustment"
61 depends on RTC_SYSTOHC
62 default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS
65 The RTC device used for NTP synchronization. The main difference
66 between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this
67 one can sleep when setting time, because it runs in the workqueue
71 bool "RTC debug support"
73 Say yes here to enable debugging support in the RTC framework
74 and individual RTC drivers.
76 comment "RTC interfaces"
79 bool "/sys/class/rtc/rtcN (sysfs)"
83 Say yes here if you want to use your RTCs using sysfs interfaces,
84 /sys/class/rtc/rtc0 through /sys/.../rtcN.
89 bool "/proc/driver/rtc (procfs for rtcN)"
93 Say yes here if you want to use your system clock RTC through
94 the proc interface, /proc/driver/rtc.
95 Other RTCs will not be available through that API.
96 If there is no RTC for the system clock, then the first RTC(rtc0)
102 bool "/dev/rtcN (character devices)"
105 Say yes here if you want to use your RTCs using the /dev
106 interfaces, which "udev" sets up as /dev/rtc0 through
109 You may want to set up a symbolic link so one of these
110 can be accessed as /dev/rtc, which is a name
111 expected by "hwclock" and some other programs. Recent
112 versions of "udev" are known to set up the symlink for you.
116 config RTC_INTF_DEV_UIE_EMUL
117 bool "RTC UIE emulation on dev interface"
118 depends on RTC_INTF_DEV
120 Provides an emulation for RTC_UIE if the underlying rtc chip
121 driver does not expose RTC_UIE ioctls. Those requests generate
122 once-per-second update interrupts, used for synchronization.
124 The emulation code will read the time from the hardware
125 clock several times per second, please enable this option
126 only if you know that you really need it.
129 tristate "Test driver/device"
131 If you say yes here you get support for the
132 RTC test driver. It's a software RTC which can be
133 used to test the RTC subsystem APIs. It gets
134 the time from the system clock.
135 You want this driver only if you are doing development
136 on the RTC subsystem. Please read the source code
139 This driver can also be built as a module. If so, the module
140 will be called rtc-test.
142 comment "I2C RTC drivers"
146 config RTC_DRV_88PM860X
147 tristate "Marvell 88PM860x"
148 depends on MFD_88PM860X
150 If you say yes here you get support for RTC function in Marvell
153 This driver can also be built as a module. If so, the module
154 will be called rtc-88pm860x.
156 config RTC_DRV_88PM80X
157 tristate "Marvell 88PM80x"
158 depends on MFD_88PM800
160 If you say yes here you get support for RTC function in Marvell
163 This driver can also be built as a module. If so, the module
164 will be called rtc-88pm80x.
166 config RTC_DRV_ABB5ZES3
168 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
170 If you say yes here you get support for the Abracon
171 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
173 This driver can also be built as a module. If so, the module
174 will be called rtc-ab-b5ze-s3.
176 config RTC_DRV_ABX80X
177 tristate "Abracon ABx80x"
179 If you say yes here you get support for Abracon AB080X and AB180X
180 families of ultra-low-power battery- and capacitor-backed real-time
183 This driver can also be built as a module. If so, the module
184 will be called rtc-abx80x.
186 config RTC_DRV_AS3722
187 tristate "ams AS3722 RTC driver"
188 depends on MFD_AS3722
190 If you say yes here you get support for the RTC of ams AS3722 PMIC
193 This driver can also be built as a module. If so, the module
194 will be called rtc-as3722.
196 config RTC_DRV_DS1307
197 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
199 If you say yes here you get support for various compatible RTC
200 chips (often with battery backup) connected with I2C. This driver
201 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
202 EPSON RX-8025 and probably other chips. In some cases the RTC
203 must already have been initialized (by manufacturing or a
206 The first seven registers on these chips hold an RTC, and other
207 registers may add features such as NVRAM, a trickle charger for
208 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
209 sysfs, but other chip features may not be available.
211 This driver can also be built as a module. If so, the module
212 will be called rtc-ds1307.
214 config RTC_DRV_DS1307_HWMON
215 bool "HWMON support for rtc-ds1307"
216 depends on RTC_DRV_DS1307 && HWMON
217 depends on !(RTC_DRV_DS1307=y && HWMON=m)
220 Say Y here if you want to expose temperature sensor data on
221 rtc-ds1307 (only DS3231)
223 config RTC_DRV_DS1374
224 tristate "Dallas/Maxim DS1374"
226 If you say yes here you get support for Dallas Semiconductor
227 DS1374 real-time clock chips. If an interrupt is associated
228 with the device, the alarm functionality is supported.
230 This driver can also be built as a module. If so, the module
231 will be called rtc-ds1374.
233 config RTC_DRV_DS1374_WDT
234 bool "Dallas/Maxim DS1374 watchdog timer"
235 depends on RTC_DRV_DS1374
237 If you say Y here you will get support for the
238 watchdog timer in the Dallas Semiconductor DS1374
239 real-time clock chips.
241 config RTC_DRV_DS1672
242 tristate "Dallas/Maxim DS1672"
244 If you say yes here you get support for the
245 Dallas/Maxim DS1672 timekeeping chip.
247 This driver can also be built as a module. If so, the module
248 will be called rtc-ds1672.
250 config RTC_DRV_HYM8563
251 tristate "Haoyu Microelectronics HYM8563"
254 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
255 from the usual rtc functions it provides a clock output of
258 This driver can also be built as a module. If so, the module
259 will be called rtc-hym8563.
261 config RTC_DRV_LP8788
262 tristate "TI LP8788 RTC driver"
263 depends on MFD_LP8788
265 Say Y to enable support for the LP8788 RTC/ALARM driver.
267 config RTC_DRV_MAX6900
268 tristate "Maxim MAX6900"
270 If you say yes here you will get support for the
271 Maxim MAX6900 I2C RTC chip.
273 This driver can also be built as a module. If so, the module
274 will be called rtc-max6900.
276 config RTC_DRV_MAX8907
277 tristate "Maxim MAX8907"
278 depends on MFD_MAX8907
280 If you say yes here you will get support for the
281 RTC of Maxim MAX8907 PMIC.
283 This driver can also be built as a module. If so, the module
284 will be called rtc-max8907.
286 config RTC_DRV_MAX8925
287 tristate "Maxim MAX8925"
288 depends on MFD_MAX8925
290 If you say yes here you will get support for the
291 RTC of Maxim MAX8925 PMIC.
293 This driver can also be built as a module. If so, the module
294 will be called rtc-max8925.
296 config RTC_DRV_MAX8998
297 tristate "Maxim MAX8998"
298 depends on MFD_MAX8998
300 If you say yes here you will get support for the
301 RTC of Maxim MAX8998 PMIC.
303 This driver can also be built as a module. If so, the module
304 will be called rtc-max8998.
306 config RTC_DRV_MAX8997
307 tristate "Maxim MAX8997"
308 depends on MFD_MAX8997
310 If you say yes here you will get support for the
311 RTC of Maxim MAX8997 PMIC.
313 This driver can also be built as a module. If so, the module
314 will be called rtc-max8997.
316 config RTC_DRV_MAX77686
317 tristate "Maxim MAX77686"
318 depends on MFD_MAX77686 || MFD_MAX77620
320 If you say yes here you will get support for the
321 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
323 This driver can also be built as a module. If so, the module
324 will be called rtc-max77686.
327 tristate "Rockchip RK808 RTC"
330 If you say yes here you will get support for the
333 This driver can also be built as a module. If so, the module
334 will be called rk808-rtc.
336 config RTC_DRV_RS5C372
337 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
339 If you say yes here you get support for the
340 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
342 This driver can also be built as a module. If so, the module
343 will be called rtc-rs5c372.
345 config RTC_DRV_ISL1208
346 tristate "Intersil ISL1208"
348 If you say yes here you get support for the
349 Intersil ISL1208 RTC chip.
351 This driver can also be built as a module. If so, the module
352 will be called rtc-isl1208.
354 config RTC_DRV_ISL12022
355 tristate "Intersil ISL12022"
357 If you say yes here you get support for the
358 Intersil ISL12022 RTC chip.
360 This driver can also be built as a module. If so, the module
361 will be called rtc-isl12022.
363 config RTC_DRV_ISL12057
365 tristate "Intersil ISL12057"
367 If you say yes here you get support for the Intersil ISL12057
370 This driver can also be built as a module. If so, the module
371 will be called rtc-isl12057.
374 tristate "Xicor/Intersil X1205"
376 If you say yes here you get support for the
377 Xicor/Intersil X1205 RTC chip.
379 This driver can also be built as a module. If so, the module
380 will be called rtc-x1205.
382 config RTC_DRV_PCF2127
383 tristate "NXP PCF2127"
385 If you say yes here you get support for the NXP PCF2127/29 RTC
388 This driver can also be built as a module. If so, the module
389 will be called rtc-pcf2127.
391 config RTC_DRV_PCF8523
392 tristate "NXP PCF8523"
394 If you say yes here you get support for the NXP PCF8523 RTC
397 This driver can also be built as a module. If so, the module
398 will be called rtc-pcf8523.
400 config RTC_DRV_PCF85063
401 tristate "NXP PCF85063"
403 If you say yes here you get support for the PCF85063 RTC chip
405 This driver can also be built as a module. If so, the module
406 will be called rtc-pcf85063.
408 config RTC_DRV_PCF8563
409 tristate "Philips PCF8563/Epson RTC8564"
411 If you say yes here you get support for the
412 Philips PCF8563 RTC chip. The Epson RTC8564
415 This driver can also be built as a module. If so, the module
416 will be called rtc-pcf8563.
418 config RTC_DRV_PCF8583
419 tristate "Philips PCF8583"
421 If you say yes here you get support for the Philips PCF8583
422 RTC chip found on Acorn RiscPCs. This driver supports the
423 platform specific method of retrieving the current year from
424 the RTC's SRAM. It will work on other platforms with the same
425 chip, but the year will probably have to be tweaked.
427 This driver can also be built as a module. If so, the module
428 will be called rtc-pcf8583.
430 config RTC_DRV_M41T80
431 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
433 If you say Y here you will get support for the ST M41T60
434 and M41T80 RTC chips series. Currently, the following chips are
435 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
436 M41ST85, M41ST87, and MicroCrystal RV4162.
438 This driver can also be built as a module. If so, the module
439 will be called rtc-m41t80.
441 config RTC_DRV_M41T80_WDT
442 bool "ST M41T65/M41T80 series RTC watchdog timer"
443 depends on RTC_DRV_M41T80
445 If you say Y here you will get support for the
446 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
449 tristate "TI BQ32000"
451 If you say Y here you will get support for the TI
452 BQ32000 I2C RTC chip.
454 This driver can also be built as a module. If so, the module
455 will be called rtc-bq32k.
457 config RTC_DRV_DM355EVM
458 tristate "TI DaVinci DM355 EVM RTC"
459 depends on MFD_DM355EVM_MSP
461 Supports the RTC firmware in the MSP430 on the DM355 EVM.
463 config RTC_DRV_TWL92330
464 bool "TI TWL92330/Menelaus"
467 If you say yes here you get support for the RTC on the
468 TWL92330 "Menelaus" power management chip, used with OMAP2
469 platforms. The support is integrated with the rest of
470 the Menelaus driver; it's not separate module.
472 config RTC_DRV_TWL4030
473 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
474 depends on TWL4030_CORE
476 If you say yes here you get support for the RTC on the
477 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
479 This driver can also be built as a module. If so, the module
480 will be called rtc-twl.
482 config RTC_DRV_PALMAS
483 tristate "TI Palmas RTC driver"
484 depends on MFD_PALMAS
486 If you say yes here you get support for the RTC of TI PALMA series PMIC
489 This driver can also be built as a module. If so, the module
490 will be called rtc-palma.
492 config RTC_DRV_TPS6586X
493 tristate "TI TPS6586X RTC driver"
494 depends on MFD_TPS6586X
496 TI Power Management IC TPS6586X supports RTC functionality
497 along with alarm. This driver supports the RTC driver for
498 the TPS6586X RTC module.
500 config RTC_DRV_TPS65910
501 tristate "TI TPS65910 RTC driver"
502 depends on RTC_CLASS && MFD_TPS65910
504 If you say yes here you get support for the RTC on the
507 This driver can also be built as a module. If so, the module
508 will be called rtc-tps65910.
510 config RTC_DRV_TPS80031
511 tristate "TI TPS80031/TPS80032 RTC driver"
512 depends on MFD_TPS80031
514 TI Power Management IC TPS80031 supports RTC functionality
515 along with alarm. This driver supports the RTC driver for
516 the TPS80031 RTC module.
518 config RTC_DRV_RC5T583
519 tristate "RICOH 5T583 RTC driver"
520 depends on MFD_RC5T583
522 If you say yes here you get support for the RTC on the
525 This driver can also be built as a module. If so, the module
526 will be called rtc-rc5t583.
528 config RTC_DRV_S35390A
529 tristate "Seiko Instruments S-35390A"
532 If you say yes here you will get support for the Seiko
533 Instruments S-35390A.
535 This driver can also be built as a module. If so the module
536 will be called rtc-s35390a.
538 config RTC_DRV_FM3130
539 tristate "Ramtron FM3130"
541 If you say Y here you will get support for the
542 Ramtron FM3130 RTC chips.
543 Ramtron FM3130 is a chip with two separate devices inside,
544 RTC clock and FRAM. This driver provides only RTC functionality.
546 This driver can also be built as a module. If so the module
547 will be called rtc-fm3130.
549 config RTC_DRV_RX8010
550 tristate "Epson RX8010SJ"
553 If you say yes here you get support for the Epson RX8010SJ RTC
556 This driver can also be built as a module. If so, the module
557 will be called rtc-rx8010.
559 config RTC_DRV_RX8581
560 tristate "Epson RX-8581"
562 If you say yes here you will get support for the Epson RX-8581.
564 This driver can also be built as a module. If so the module
565 will be called rtc-rx8581.
567 config RTC_DRV_RX8025
568 tristate "Epson RX-8025SA/NB"
570 If you say yes here you get support for the Epson
571 RX-8025SA/NB RTC chips.
573 This driver can also be built as a module. If so, the module
574 will be called rtc-rx8025.
576 config RTC_DRV_EM3027
577 tristate "EM Microelectronic EM3027"
579 If you say yes here you get support for the EM
580 Microelectronic EM3027 RTC chips.
582 This driver can also be built as a module. If so, the module
583 will be called rtc-em3027.
585 config RTC_DRV_RV3029C2
586 tristate "Micro Crystal RV3029"
588 If you say yes here you get support for the Micro Crystal
591 This driver can also be built as a module. If so, the module
592 will be called rtc-rv3029c2.
594 config RTC_DRV_RV3029_HWMON
595 bool "HWMON support for RV3029"
596 depends on RTC_DRV_RV3029C2 && HWMON
597 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
600 Say Y here if you want to expose temperature sensor data on
603 config RTC_DRV_RV8803
604 tristate "Micro Crystal RV8803"
606 If you say yes here you get support for the Micro Crystal
609 This driver can also be built as a module. If so, the module
610 will be called rtc-rv8803.
613 tristate "Samsung S2M/S5M series"
614 depends on MFD_SEC_CORE
616 If you say yes here you will get support for the
617 RTC of Samsung S2MPS14 and S5M PMIC series.
619 This driver can also be built as a module. If so, the module
620 will be called rtc-s5m.
624 comment "SPI RTC drivers"
628 config RTC_DRV_M41T93
631 If you say yes here you will get support for the
632 ST M41T93 SPI RTC chip.
634 This driver can also be built as a module. If so, the module
635 will be called rtc-m41t93.
637 config RTC_DRV_M41T94
640 If you say yes here you will get support for the
641 ST M41T94 SPI RTC chip.
643 This driver can also be built as a module. If so, the module
644 will be called rtc-m41t94.
646 config RTC_DRV_DS1305
647 tristate "Dallas/Maxim DS1305/DS1306"
649 Select this driver to get support for the Dallas/Maxim DS1305
650 and DS1306 real time clock chips. These support a trickle
651 charger, alarms, and NVRAM in addition to the clock.
653 This driver can also be built as a module. If so, the module
654 will be called rtc-ds1305.
656 config RTC_DRV_DS1343
658 tristate "Dallas/Maxim DS1343/DS1344"
660 If you say yes here you get support for the
661 Dallas/Maxim DS1343 and DS1344 real time clock chips.
662 Support for trickle charger, alarm is provided.
664 This driver can also be built as a module. If so, the module
665 will be called rtc-ds1343.
667 config RTC_DRV_DS1347
668 tristate "Dallas/Maxim DS1347"
670 If you say yes here you get support for the
671 Dallas/Maxim DS1347 chips.
673 This driver only supports the RTC feature, and not other chip
674 features such as alarms.
676 This driver can also be built as a module. If so, the module
677 will be called rtc-ds1347.
679 config RTC_DRV_DS1390
680 tristate "Dallas/Maxim DS1390/93/94"
682 If you say yes here you get support for the
683 Dallas/Maxim DS1390/93/94 chips.
685 This driver supports the RTC feature and trickle charging but not
686 other chip features such as alarms.
688 This driver can also be built as a module. If so, the module
689 will be called rtc-ds1390.
692 tristate "Epson RTC-9701JE"
694 If you say yes here you will get support for the
695 Epson RTC-9701JE SPI RTC chip.
697 This driver can also be built as a module. If so, the module
698 will be called rtc-r9701.
700 config RTC_DRV_RX4581
701 tristate "Epson RX-4581"
703 If you say yes here you will get support for the Epson RX-4581.
705 This driver can also be built as a module. If so the module
706 will be called rtc-rx4581.
708 config RTC_DRV_RX6110
709 tristate "Epson RX-6110"
712 If you say yes here you will get support for the Epson RX-6610.
714 This driver can also be built as a module. If so the module
715 will be called rtc-rx6110.
717 config RTC_DRV_RS5C348
718 tristate "Ricoh RS5C348A/B"
720 If you say yes here you get support for the
721 Ricoh RS5C348A and RS5C348B RTC chips.
723 This driver can also be built as a module. If so, the module
724 will be called rtc-rs5c348.
726 config RTC_DRV_MAX6902
727 tristate "Maxim MAX6902"
729 If you say yes here you will get support for the
730 Maxim MAX6902 SPI RTC chip.
732 This driver can also be built as a module. If so, the module
733 will be called rtc-max6902.
735 config RTC_DRV_PCF2123
736 tristate "NXP PCF2123"
738 If you say yes here you get support for the NXP PCF2123
741 This driver can also be built as a module. If so, the module
742 will be called rtc-pcf2123.
744 config RTC_DRV_MCP795
745 tristate "Microchip MCP795"
747 If you say yes here you will get support for the Microchip MCP795.
749 This driver can also be built as a module. If so the module
750 will be called rtc-mcp795.
755 # Helper to resolve issues with configs that have SPI enabled but I2C
756 # modular. See SND_SOC_I2C_AND_SPI for more information
758 config RTC_I2C_AND_SPI
762 default y if SPI_MASTER=y
763 select REGMAP_I2C if I2C
764 select REGMAP_SPI if SPI_MASTER
766 comment "SPI and I2C RTC drivers"
768 config RTC_DRV_DS3232
769 tristate "Dallas/Maxim DS3232/DS3234"
770 depends on RTC_I2C_AND_SPI
772 If you say yes here you get support for Dallas Semiconductor
773 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
774 with the device, the alarm functionality is supported.
776 This driver can also be built as a module. If so, the module
777 will be called rtc-ds3232.
779 comment "Platform RTC drivers"
781 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
782 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
783 # global rtc_lock ... it's not yet just another platform_device.
786 tristate "PC-style 'CMOS'"
787 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
790 Say "yes" here to get direct support for the real time clock
791 found in every PC or ACPI-based system, and some other boards.
792 Specifically the original MC146818, compatibles like those in
793 PC south bridges, the DS12887 or M48T86, some multifunction
794 or LPC bus chips, and so on.
796 Your system will need to define the platform device used by
797 this driver, otherwise it won't be accessible. This means
798 you can safely enable this driver if you don't know whether
799 or not your board has this kind of hardware.
801 This driver can also be built as a module. If so, the module
802 will be called rtc-cmos.
805 bool "Alpha PC-style CMOS"
809 Direct support for the real-time clock found on every Alpha
810 system, specifically MC146818 compatibles. If in doubt, say Y.
813 tristate "Virtual RTC for Intel MID platforms"
814 depends on X86_INTEL_MID
815 default y if X86_INTEL_MID
818 Say "yes" here to get direct support for the real time clock
819 found on Moorestown platforms. The VRTC is a emulated RTC that
820 derives its clock source from a real RTC in the PMIC. The MC146818
821 style programming interface is mostly conserved, but any
822 updates are done via IPC calls to the system controller FW.
824 config RTC_DRV_DS1216
825 tristate "Dallas DS1216"
828 If you say yes here you get support for the Dallas DS1216 RTC chips.
830 config RTC_DRV_DS1286
831 tristate "Dallas DS1286"
834 If you say yes here you get support for the Dallas DS1286 RTC chips.
836 config RTC_DRV_DS1302
837 tristate "Dallas DS1302"
838 depends on SH_SECUREEDGE5410
840 If you say yes here you get support for the Dallas DS1302 RTC chips.
842 config RTC_DRV_DS1511
843 tristate "Dallas DS1511"
846 If you say yes here you get support for the
847 Dallas DS1511 timekeeping/watchdog chip.
849 This driver can also be built as a module. If so, the module
850 will be called rtc-ds1511.
852 config RTC_DRV_DS1553
853 tristate "Maxim/Dallas DS1553"
856 If you say yes here you get support for the
857 Maxim/Dallas DS1553 timekeeping chip.
859 This driver can also be built as a module. If so, the module
860 will be called rtc-ds1553.
862 config RTC_DRV_DS1685_FAMILY
863 tristate "Dallas/Maxim DS1685 Family"
865 If you say yes here you get support for the Dallas/Maxim DS1685
866 family of real time chips. This family includes the DS1685/DS1687,
867 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
868 DS17885/DS17887 chips.
870 This driver can also be built as a module. If so, the module
871 will be called rtc-ds1685.
875 depends on RTC_DRV_DS1685_FAMILY
876 default RTC_DRV_DS1685
878 config RTC_DRV_DS1685
881 This enables support for the Dallas/Maxim DS1685/DS1687 real time
884 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
885 systems, as well as EPPC-405-UC modules by electronic system design
888 config RTC_DRV_DS1689
891 This enables support for the Dallas/Maxim DS1689/DS1693 real time
894 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
895 which supports a few minor features such as Vcc, Vbat, and Power
896 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
898 It also works for the even older DS1688/DS1691 RTC chips, which are
899 virtually the same and carry the same model number. Both chips
900 have 114 bytes of user NVRAM.
902 config RTC_DRV_DS17285
903 bool "DS17285/DS17287"
905 This enables support for the Dallas/Maxim DS17285/DS17287 real time
908 This chip features 2kb of extended NV-SRAM. It may possibly be
909 found in some SGI O2 systems (rare).
911 config RTC_DRV_DS17485
912 bool "DS17485/DS17487"
914 This enables support for the Dallas/Maxim DS17485/DS17487 real time
917 This chip features 4kb of extended NV-SRAM.
919 config RTC_DRV_DS17885
920 bool "DS17885/DS17887"
922 This enables support for the Dallas/Maxim DS17885/DS17887 real time
925 This chip features 8kb of extended NV-SRAM.
929 config RTC_DS1685_PROC_REGS
930 bool "Display register values in /proc"
931 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
933 Enable this to display a readout of all of the RTC registers in
934 /proc/drivers/rtc. Keep in mind that this can potentially lead
935 to lost interrupts, as reading Control Register C will clear
936 all pending IRQ flags.
938 Unless you are debugging this driver, choose N.
940 config RTC_DS1685_SYSFS_REGS
941 bool "SysFS access to RTC register bits"
942 depends on RTC_DRV_DS1685_FAMILY && SYSFS
944 Enable this to provide access to the RTC control register bits
945 in /sys. Some of the bits are read-write, others are read-only.
947 Keep in mind that reading Control C's bits automatically clears
948 all pending IRQ flags - this can cause lost interrupts.
950 If you know that you need access to these bits, choose Y, Else N.
952 config RTC_DRV_DS1742
953 tristate "Maxim/Dallas DS1742/1743"
956 If you say yes here you get support for the
957 Maxim/Dallas DS1742/1743 timekeeping chip.
959 This driver can also be built as a module. If so, the module
960 will be called rtc-ds1742.
962 config RTC_DRV_DS2404
963 tristate "Maxim/Dallas DS2404"
965 If you say yes here you get support for the
966 Dallas DS2404 RTC chip.
968 This driver can also be built as a module. If so, the module
969 will be called rtc-ds2404.
971 config RTC_DRV_DA9052
972 tristate "Dialog DA9052/DA9053 RTC"
973 depends on PMIC_DA9052
975 Say y here to support the RTC driver for Dialog Semiconductor
976 DA9052-BC and DA9053-AA/Bx PMICs.
978 config RTC_DRV_DA9055
979 tristate "Dialog Semiconductor DA9055 RTC"
980 depends on MFD_DA9055
982 If you say yes here you will get support for the
983 RTC of the Dialog DA9055 PMIC.
985 This driver can also be built as a module. If so, the module
986 will be called rtc-da9055
988 config RTC_DRV_DA9063
989 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
990 depends on MFD_DA9063 || MFD_DA9062
992 If you say yes here you will get support for the RTC subsystem
993 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
995 This driver can also be built as a module. If so, the module
996 will be called "rtc-da9063".
1000 depends on EFI && !X86
1002 If you say yes here you will get support for the EFI
1005 This driver can also be built as a module. If so, the module
1006 will be called rtc-efi.
1008 config RTC_DRV_STK17TA8
1009 tristate "Simtek STK17TA8"
1010 depends on HAS_IOMEM
1012 If you say yes here you get support for the
1013 Simtek STK17TA8 timekeeping chip.
1015 This driver can also be built as a module. If so, the module
1016 will be called rtc-stk17ta8.
1018 config RTC_DRV_M48T86
1019 tristate "ST M48T86/Dallas DS12887"
1021 If you say Y here you will get support for the
1022 ST M48T86 and Dallas DS12887 RTC chips.
1024 This driver can also be built as a module. If so, the module
1025 will be called rtc-m48t86.
1027 config RTC_DRV_M48T35
1028 tristate "ST M48T35"
1029 depends on HAS_IOMEM
1031 If you say Y here you will get support for the
1034 This driver can also be built as a module, if so, the module
1035 will be called "rtc-m48t35".
1037 config RTC_DRV_M48T59
1038 tristate "ST M48T59/M48T08/M48T02"
1039 depends on HAS_IOMEM
1041 If you say Y here you will get support for the
1042 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1044 These chips are usually found in Sun SPARC and UltraSPARC
1047 This driver can also be built as a module, if so, the module
1048 will be called "rtc-m48t59".
1050 config RTC_DRV_MSM6242
1051 tristate "Oki MSM6242"
1052 depends on HAS_IOMEM
1054 If you say yes here you get support for the Oki MSM6242
1055 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1057 This driver can also be built as a module. If so, the module
1058 will be called rtc-msm6242.
1060 config RTC_DRV_BQ4802
1061 tristate "TI BQ4802"
1062 depends on HAS_IOMEM
1064 If you say Y here you will get support for the TI
1067 This driver can also be built as a module. If so, the module
1068 will be called rtc-bq4802.
1070 config RTC_DRV_RP5C01
1071 tristate "Ricoh RP5C01"
1072 depends on HAS_IOMEM
1074 If you say yes here you get support for the Ricoh RP5C01
1075 timekeeping chip. It is used in some Amiga models (e.g. A3000
1078 This driver can also be built as a module. If so, the module
1079 will be called rtc-rp5c01.
1081 config RTC_DRV_V3020
1082 tristate "EM Microelectronic V3020"
1084 If you say yes here you will get support for the
1085 EM Microelectronic v3020 RTC chip.
1087 This driver can also be built as a module. If so, the module
1088 will be called rtc-v3020.
1090 config RTC_DRV_WM831X
1091 tristate "Wolfson Microelectronics WM831x RTC"
1092 depends on MFD_WM831X
1094 If you say yes here you will get support for the RTC subsystem
1095 of the Wolfson Microelectronics WM831X series PMICs.
1097 This driver can also be built as a module. If so, the module
1098 will be called "rtc-wm831x".
1100 config RTC_DRV_WM8350
1101 tristate "Wolfson Microelectronics WM8350 RTC"
1102 depends on MFD_WM8350
1104 If you say yes here you will get support for the RTC subsystem
1105 of the Wolfson Microelectronics WM8350.
1107 This driver can also be built as a module. If so, the module
1108 will be called "rtc-wm8350".
1110 config RTC_DRV_SPEAR
1111 tristate "SPEAR ST RTC"
1112 depends on PLAT_SPEAR || COMPILE_TEST
1115 If you say Y here you will get support for the RTC found on
1118 config RTC_DRV_PCF50633
1119 depends on MFD_PCF50633
1120 tristate "NXP PCF50633 RTC"
1122 If you say yes here you get support for the RTC subsystem of the
1123 NXP PCF50633 used in embedded systems.
1125 config RTC_DRV_AB3100
1126 tristate "ST-Ericsson AB3100 RTC"
1127 depends on AB3100_CORE
1128 default y if AB3100_CORE
1130 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1131 support. This chip contains a battery- and capacitor-backed RTC.
1133 config RTC_DRV_AB8500
1134 tristate "ST-Ericsson AB8500 RTC"
1135 depends on AB8500_CORE
1137 select RTC_INTF_DEV_UIE_EMUL
1139 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1140 support. This chip contains a battery- and capacitor-backed RTC.
1142 config RTC_DRV_NUC900
1143 tristate "NUC910/NUC920 RTC driver"
1144 depends on ARCH_W90X900 || COMPILE_TEST
1146 If you say yes here you get support for the RTC subsystem of the
1147 NUC910/NUC920 used in embedded systems.
1150 tristate "IBM OPAL RTC driver"
1151 depends on PPC_POWERNV
1154 If you say yes here you get support for the PowerNV platform RTC
1155 driver based on OPAL interfaces.
1157 This driver can also be built as a module. If so, the module
1158 will be called rtc-opal.
1160 config RTC_DRV_ZYNQMP
1161 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1164 If you say yes here you get support for the RTC controller found on
1165 Xilinx Zynq Ultrascale+ MPSoC.
1167 comment "on-CPU RTC drivers"
1169 config RTC_DRV_ASM9260
1170 tristate "Alphascale asm9260 RTC"
1171 depends on MACH_ASM9260
1173 If you say yes here you get support for the RTC on the
1174 Alphascale asm9260 SoC.
1176 This driver can also be built as a module. If so, the module
1177 will be called rtc-asm9260.
1179 config RTC_DRV_DAVINCI
1180 tristate "TI DaVinci RTC"
1181 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1183 If you say yes here you get support for the RTC on the
1184 DaVinci platforms (DM365).
1186 This driver can also be built as a module. If so, the module
1187 will be called rtc-davinci.
1189 config RTC_DRV_DIGICOLOR
1190 tristate "Conexant Digicolor RTC"
1191 depends on ARCH_DIGICOLOR || COMPILE_TEST
1193 If you say yes here you get support for the RTC on Conexant
1194 Digicolor platforms. This currently includes the CX92755 SoC.
1196 This driver can also be built as a module. If so, the module
1197 will be called rtc-digicolor.
1199 config RTC_DRV_IMXDI
1200 tristate "Freescale IMX DryIce Real Time Clock"
1203 Support for Freescale IMX DryIce RTC
1205 This driver can also be built as a module, if so, the module
1206 will be called "rtc-imxdi".
1209 tristate "TI OMAP Real Time Clock"
1210 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1212 Say "yes" here to support the on chip real time clock
1213 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1215 This driver can also be built as a module, if so, module
1216 will be called rtc-omap.
1221 This will include RTC support for Samsung SoCs. If
1222 you want to include RTC support for any machine, kindly
1223 select this in the respective mach-XXXX/Kconfig file.
1226 tristate "Samsung S3C series SoC RTC"
1227 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1229 RTC (Realtime Clock) driver for the clock inbuilt into the
1230 Samsung S3C24XX series of SoCs. This can provide periodic
1231 interrupt rates from 1Hz to 64Hz for user programs, and
1234 The driver currently supports the common features on all the
1235 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1238 This driver can also be build as a module. If so, the module
1239 will be called rtc-s3c.
1241 config RTC_DRV_EP93XX
1242 tristate "Cirrus Logic EP93XX"
1243 depends on ARCH_EP93XX || COMPILE_TEST
1245 If you say yes here you get support for the
1246 RTC embedded in the Cirrus Logic EP93XX processors.
1248 This driver can also be built as a module. If so, the module
1249 will be called rtc-ep93xx.
1251 config RTC_DRV_SA1100
1252 tristate "SA11x0/PXA2xx/PXA910"
1253 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1255 If you say Y here you will get access to the real time clock
1256 built into your SA11x0 or PXA2xx CPU.
1258 To compile this driver as a module, choose M here: the
1259 module will be called rtc-sa1100.
1262 tristate "SuperH On-Chip RTC"
1263 depends on SUPERH && HAVE_CLK
1265 Say Y here to enable support for the on-chip RTC found in
1266 most SuperH processors.
1268 To compile this driver as a module, choose M here: the
1269 module will be called rtc-sh.
1271 config RTC_DRV_VR41XX
1272 tristate "NEC VR41XX"
1273 depends on CPU_VR41XX || COMPILE_TEST
1275 If you say Y here you will get access to the real time clock
1276 built into your NEC VR41XX CPU.
1278 To compile this driver as a module, choose M here: the
1279 module will be called rtc-vr41xx.
1281 config RTC_DRV_PL030
1282 tristate "ARM AMBA PL030 RTC"
1285 If you say Y here you will get access to ARM AMBA
1286 PrimeCell PL030 RTC found on certain ARM SOCs.
1288 To compile this driver as a module, choose M here: the
1289 module will be called rtc-pl030.
1291 config RTC_DRV_PL031
1292 tristate "ARM AMBA PL031 RTC"
1295 If you say Y here you will get access to ARM AMBA
1296 PrimeCell PL031 RTC found on certain ARM SOCs.
1298 To compile this driver as a module, choose M here: the
1299 module will be called rtc-pl031.
1301 config RTC_DRV_AT32AP700X
1302 tristate "AT32AP700X series RTC"
1303 depends on PLATFORM_AT32AP || COMPILE_TEST
1305 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1306 AT32AP700x family processors.
1308 config RTC_DRV_AT91RM9200
1309 tristate "AT91RM9200 or some AT91SAM9 RTC"
1310 depends on ARCH_AT91 || COMPILE_TEST
1312 Driver for the internal RTC (Realtime Clock) module found on
1313 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1314 this is powered by the backup power supply.
1316 config RTC_DRV_AT91SAM9
1317 tristate "AT91SAM9 RTT as RTC"
1318 depends on ARCH_AT91 || COMPILE_TEST
1321 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1322 can be used as an RTC thanks to the backup power supply (e.g. a
1323 small coin cell battery) which keeps this block and the GPBR
1324 (General Purpose Backup Registers) block powered when the device
1326 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1327 probably want to use the real RTC block instead of the "RTT as an
1330 config RTC_DRV_AU1XXX
1331 tristate "Au1xxx Counter0 RTC support"
1332 depends on MIPS_ALCHEMY
1334 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1335 counter) to be used as a RTC.
1337 This driver can also be built as a module. If so, the module
1338 will be called rtc-au1xxx.
1341 tristate "Blackfin On-Chip RTC"
1342 depends on BLACKFIN && !BF561
1344 If you say yes here you will get support for the
1345 Blackfin On-Chip Real Time Clock.
1347 This driver can also be built as a module. If so, the module
1348 will be called rtc-bfin.
1350 config RTC_DRV_RS5C313
1351 tristate "Ricoh RS5C313"
1352 depends on SH_LANDISK
1354 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1356 config RTC_DRV_GENERIC
1357 tristate "Generic RTC support"
1358 # Please consider writing a new RTC driver instead of using the generic
1360 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
1362 Say Y or M here to enable RTC support on systems using the generic
1363 RTC abstraction. If you do not know what you are doing, you should
1367 tristate "PXA27x/PXA3xx"
1369 select RTC_DRV_SA1100
1371 If you say Y here you will get access to the real time clock
1372 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1373 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1375 This RTC driver uses PXA RTC registers available since pxa27x
1376 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1378 config RTC_DRV_VT8500
1379 tristate "VIA/WonderMedia 85xx SoC RTC"
1380 depends on ARCH_VT8500 || COMPILE_TEST
1382 If you say Y here you will get access to the real time clock
1383 built into your VIA VT8500 SoC or its relatives.
1386 config RTC_DRV_SUN4V
1387 bool "SUN4V Hypervisor RTC"
1390 If you say Y here you will get support for the Hypervisor
1391 based RTC on SUN4V systems.
1393 config RTC_DRV_SUN6I
1394 tristate "Allwinner A31 RTC"
1395 default MACH_SUN6I || MACH_SUN8I || COMPILE_TEST
1396 depends on ARCH_SUNXI
1398 If you say Y here you will get support for the RTC found in
1399 some Allwinner SoCs like the A31 or the A64.
1401 config RTC_DRV_SUNXI
1402 tristate "Allwinner sun4i/sun7i RTC"
1403 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1405 If you say Y here you will get support for the RTC found on
1408 config RTC_DRV_STARFIRE
1412 If you say Y here you will get support for the RTC found on
1415 config RTC_DRV_TX4939
1416 tristate "TX4939 SoC"
1417 depends on SOC_TX4939
1419 Driver for the internal RTC (Realtime Clock) module found on
1423 tristate "Marvell SoC RTC"
1424 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1426 If you say yes here you will get support for the in-chip RTC
1427 that can be found in some of Marvell's SoC devices, such as
1428 the Kirkwood 88F6281 and 88F6192.
1430 This driver can also be built as a module. If so, the module
1431 will be called rtc-mv.
1433 config RTC_DRV_ARMADA38X
1434 tristate "Armada 38x Marvell SoC RTC"
1435 depends on ARCH_MVEBU || COMPILE_TEST
1437 If you say yes here you will get support for the in-chip RTC
1438 that can be found in the Armada 38x Marvell's SoC device
1440 This driver can also be built as a module. If so, the module
1441 will be called armada38x-rtc.
1443 config RTC_DRV_GEMINI
1444 tristate "Gemini SoC RTC"
1445 depends on ARCH_GEMINI || COMPILE_TEST
1446 depends on HAS_IOMEM
1448 If you say Y here you will get support for the
1449 RTC found on Gemini SoC's.
1451 This driver can also be built as a module. If so, the module
1452 will be called rtc-gemini.
1458 If you say yes here you will get support for the RTC on PS3.
1460 This driver can also be built as a module. If so, the module
1461 will be called rtc-ps3.
1463 config RTC_DRV_COH901331
1464 tristate "ST-Ericsson COH 901 331 RTC"
1465 depends on ARCH_U300 || COMPILE_TEST
1467 If you say Y here you will get access to ST-Ericsson
1468 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1471 This driver can also be built as a module. If so, the module
1472 will be called "rtc-coh901331".
1476 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1477 depends on ARCH_MXS || COMPILE_TEST
1480 If you say yes here you will get support for the onboard
1481 STMP3xxx/i.MX23/i.MX28 RTC.
1483 This driver can also be built as a module. If so, the module
1484 will be called rtc-stmp3xxx.
1490 If you say Y here you will get support for the RTC found on
1491 the PCAP2 ASIC used on some Motorola phones.
1493 config RTC_DRV_MC13XXX
1494 depends on MFD_MC13XXX
1495 tristate "Freescale MC13xxx RTC"
1497 This enables support for the RTCs found on Freescale's PMICs
1498 MC13783 and MC13892.
1500 config RTC_DRV_MPC5121
1501 tristate "Freescale MPC5121 built-in RTC"
1502 depends on PPC_MPC512x || PPC_MPC52xx
1504 If you say yes here you will get support for the
1505 built-in RTC on MPC5121 or on MPC5200.
1507 This driver can also be built as a module. If so, the module
1508 will be called rtc-mpc5121.
1510 config RTC_DRV_JZ4740
1511 tristate "Ingenic JZ4740 SoC"
1512 depends on MACH_JZ4740 || COMPILE_TEST
1514 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1517 This driver can also be buillt as a module. If so, the module
1518 will be called rtc-jz4740.
1520 config RTC_DRV_LPC24XX
1521 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1522 depends on ARCH_LPC18XX || COMPILE_TEST
1523 depends on OF && HAS_IOMEM
1525 This enables support for the NXP RTC found which can be found on
1526 NXP LPC178x/18xx/408x/43xx devices.
1528 If you have one of the devices above enable this driver to use
1529 the hardware RTC. This driver can also be buillt as a module. If
1530 so, the module will be called rtc-lpc24xx.
1532 config RTC_DRV_LPC32XX
1533 depends on ARCH_LPC32XX || COMPILE_TEST
1534 tristate "NXP LPC32XX RTC"
1536 This enables support for the NXP RTC in the LPC32XX
1538 This driver can also be buillt as a module. If so, the module
1539 will be called rtc-lpc32xx.
1541 config RTC_DRV_PM8XXX
1542 tristate "Qualcomm PMIC8XXX RTC"
1543 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1545 If you say yes here you get support for the
1546 Qualcomm PMIC8XXX RTC.
1548 To compile this driver as a module, choose M here: the
1549 module will be called rtc-pm8xxx.
1551 config RTC_DRV_TEGRA
1552 tristate "NVIDIA Tegra Internal RTC driver"
1553 depends on ARCH_TEGRA || COMPILE_TEST
1555 If you say yes here you get support for the
1556 Tegra 200 series internal RTC module.
1558 This drive can also be built as a module. If so, the module
1559 will be called rtc-tegra.
1562 tristate "Tilera hypervisor RTC support"
1565 Enable support for the Linux driver side of the Tilera
1566 hypervisor's real-time clock interface.
1569 tristate "PKUnity v3 RTC support"
1570 depends on ARCH_PUV3
1572 This enables support for the RTC in the PKUnity-v3 SoCs.
1574 This drive can also be built as a module. If so, the module
1575 will be called rtc-puv3.
1577 config RTC_DRV_LOONGSON1
1578 tristate "loongson1 RTC support"
1579 depends on MACH_LOONGSON32
1581 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1582 counter) to be used as a RTC.
1584 This driver can also be built as a module. If so, the module
1585 will be called rtc-ls1x.
1588 tristate "Freescale MXC Real Time Clock"
1591 If you say yes here you get support for the Freescale MXC
1594 This driver can also be built as a module, if so, the module
1595 will be called "rtc-mxc".
1598 tristate "Freescale SNVS RTC support"
1600 depends on HAS_IOMEM
1603 If you say yes here you get support for the Freescale SNVS
1604 Low Power (LP) RTC module.
1606 This driver can also be built as a module, if so, the module
1607 will be called "rtc-snvs".
1609 config RTC_DRV_SIRFSOC
1610 tristate "SiRFSOC RTC"
1611 depends on ARCH_SIRF
1613 Say "yes" here to support the real time clock on SiRF SOC chips.
1614 This driver can also be built as a module called rtc-sirfsoc.
1616 config RTC_DRV_ST_LPC
1617 tristate "STMicroelectronics LPC RTC"
1621 Say Y here to include STMicroelectronics Low Power Controller
1622 (LPC) based RTC support.
1624 To compile this driver as a module, choose M here: the
1625 module will be called rtc-st-lpc.
1627 config RTC_DRV_MOXART
1628 tristate "MOXA ART RTC"
1629 depends on ARCH_MOXART || COMPILE_TEST
1631 If you say yes here you get support for the MOXA ART
1634 This driver can also be built as a module. If so, the module
1635 will be called rtc-moxart
1637 config RTC_DRV_MT6397
1638 tristate "Mediatek Real Time Clock driver"
1639 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1641 This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
1642 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1643 Mediatek(R) RTC driver.
1645 If you want to use Mediatek(R) RTC interface, select Y or M here.
1647 config RTC_DRV_XGENE
1648 tristate "APM X-Gene RTC"
1649 depends on HAS_IOMEM
1650 depends on ARCH_XGENE || COMPILE_TEST
1652 If you say yes here you get support for the APM X-Gene SoC real time
1655 This driver can also be built as a module, if so, the module
1656 will be called "rtc-xgene".
1658 config RTC_DRV_PIC32
1659 tristate "Microchip PIC32 RTC"
1660 depends on MACH_PIC32
1663 If you say yes here you get support for the PIC32 RTC module.
1665 This driver can also be built as a module. If so, the module
1666 will be called rtc-pic32
1668 comment "HID Sensor RTC drivers"
1670 config RTC_DRV_HID_SENSOR_TIME
1671 tristate "HID Sensor Time"
1674 select HID_SENSOR_HUB
1675 select HID_SENSOR_IIO_COMMON
1677 Say yes here to build support for the HID Sensors of type Time.
1678 This drivers makes such sensors available as RTCs.
1680 If this driver is compiled as a module, it will be named
1681 rtc-hid-sensor-time.