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_PCF8523
383 tristate "NXP PCF8523"
385 If you say yes here you get support for the NXP PCF8523 RTC
388 This driver can also be built as a module. If so, the module
389 will be called rtc-pcf8523.
391 config RTC_DRV_PCF85063
392 tristate "NXP PCF85063"
394 If you say yes here you get support for the PCF85063 RTC chip
396 This driver can also be built as a module. If so, the module
397 will be called rtc-pcf85063.
399 config RTC_DRV_PCF8563
400 tristate "Philips PCF8563/Epson RTC8564"
402 If you say yes here you get support for the
403 Philips PCF8563 RTC chip. The Epson RTC8564
406 This driver can also be built as a module. If so, the module
407 will be called rtc-pcf8563.
409 config RTC_DRV_PCF8583
410 tristate "Philips PCF8583"
412 If you say yes here you get support for the Philips PCF8583
413 RTC chip found on Acorn RiscPCs. This driver supports the
414 platform specific method of retrieving the current year from
415 the RTC's SRAM. It will work on other platforms with the same
416 chip, but the year will probably have to be tweaked.
418 This driver can also be built as a module. If so, the module
419 will be called rtc-pcf8583.
421 config RTC_DRV_M41T80
422 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
424 If you say Y here you will get support for the ST M41T60
425 and M41T80 RTC chips series. Currently, the following chips are
426 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
427 M41ST85, M41ST87, and MicroCrystal RV4162.
429 This driver can also be built as a module. If so, the module
430 will be called rtc-m41t80.
432 config RTC_DRV_M41T80_WDT
433 bool "ST M41T65/M41T80 series RTC watchdog timer"
434 depends on RTC_DRV_M41T80
436 If you say Y here you will get support for the
437 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
440 tristate "TI BQ32000"
442 If you say Y here you will get support for the TI
443 BQ32000 I2C RTC chip.
445 This driver can also be built as a module. If so, the module
446 will be called rtc-bq32k.
448 config RTC_DRV_DM355EVM
449 tristate "TI DaVinci DM355 EVM RTC"
450 depends on MFD_DM355EVM_MSP
452 Supports the RTC firmware in the MSP430 on the DM355 EVM.
454 config RTC_DRV_TWL92330
455 bool "TI TWL92330/Menelaus"
458 If you say yes here you get support for the RTC on the
459 TWL92330 "Menelaus" power management chip, used with OMAP2
460 platforms. The support is integrated with the rest of
461 the Menelaus driver; it's not separate module.
463 config RTC_DRV_TWL4030
464 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
465 depends on TWL4030_CORE
467 If you say yes here you get support for the RTC on the
468 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
470 This driver can also be built as a module. If so, the module
471 will be called rtc-twl.
473 config RTC_DRV_PALMAS
474 tristate "TI Palmas RTC driver"
475 depends on MFD_PALMAS
477 If you say yes here you get support for the RTC of TI PALMA series PMIC
480 This driver can also be built as a module. If so, the module
481 will be called rtc-palma.
483 config RTC_DRV_TPS6586X
484 tristate "TI TPS6586X RTC driver"
485 depends on MFD_TPS6586X
487 TI Power Management IC TPS6586X supports RTC functionality
488 along with alarm. This driver supports the RTC driver for
489 the TPS6586X RTC module.
491 config RTC_DRV_TPS65910
492 tristate "TI TPS65910 RTC driver"
493 depends on RTC_CLASS && MFD_TPS65910
495 If you say yes here you get support for the RTC on the
498 This driver can also be built as a module. If so, the module
499 will be called rtc-tps65910.
501 config RTC_DRV_TPS80031
502 tristate "TI TPS80031/TPS80032 RTC driver"
503 depends on MFD_TPS80031
505 TI Power Management IC TPS80031 supports RTC functionality
506 along with alarm. This driver supports the RTC driver for
507 the TPS80031 RTC module.
509 config RTC_DRV_RC5T583
510 tristate "RICOH 5T583 RTC driver"
511 depends on MFD_RC5T583
513 If you say yes here you get support for the RTC on the
516 This driver can also be built as a module. If so, the module
517 will be called rtc-rc5t583.
519 config RTC_DRV_S35390A
520 tristate "Seiko Instruments S-35390A"
523 If you say yes here you will get support for the Seiko
524 Instruments S-35390A.
526 This driver can also be built as a module. If so the module
527 will be called rtc-s35390a.
529 config RTC_DRV_FM3130
530 tristate "Ramtron FM3130"
532 If you say Y here you will get support for the
533 Ramtron FM3130 RTC chips.
534 Ramtron FM3130 is a chip with two separate devices inside,
535 RTC clock and FRAM. This driver provides only RTC functionality.
537 This driver can also be built as a module. If so the module
538 will be called rtc-fm3130.
540 config RTC_DRV_RX8010
541 tristate "Epson RX8010SJ"
544 If you say yes here you get support for the Epson RX8010SJ RTC
547 This driver can also be built as a module. If so, the module
548 will be called rtc-rx8010.
550 config RTC_DRV_RX8581
551 tristate "Epson RX-8581"
553 If you say yes here you will get support for the Epson RX-8581.
555 This driver can also be built as a module. If so the module
556 will be called rtc-rx8581.
558 config RTC_DRV_RX8025
559 tristate "Epson RX-8025SA/NB"
561 If you say yes here you get support for the Epson
562 RX-8025SA/NB RTC chips.
564 This driver can also be built as a module. If so, the module
565 will be called rtc-rx8025.
567 config RTC_DRV_EM3027
568 tristate "EM Microelectronic EM3027"
570 If you say yes here you get support for the EM
571 Microelectronic EM3027 RTC chips.
573 This driver can also be built as a module. If so, the module
574 will be called rtc-em3027.
576 config RTC_DRV_RV8803
577 tristate "Micro Crystal RV8803"
579 If you say yes here you get support for the Micro Crystal
582 This driver can also be built as a module. If so, the module
583 will be called rtc-rv8803.
586 tristate "Samsung S2M/S5M series"
587 depends on MFD_SEC_CORE
589 If you say yes here you will get support for the
590 RTC of Samsung S2MPS14 and S5M PMIC series.
592 This driver can also be built as a module. If so, the module
593 will be called rtc-s5m.
597 comment "SPI RTC drivers"
601 config RTC_DRV_M41T93
604 If you say yes here you will get support for the
605 ST M41T93 SPI RTC chip.
607 This driver can also be built as a module. If so, the module
608 will be called rtc-m41t93.
610 config RTC_DRV_M41T94
613 If you say yes here you will get support for the
614 ST M41T94 SPI RTC chip.
616 This driver can also be built as a module. If so, the module
617 will be called rtc-m41t94.
619 config RTC_DRV_DS1302
620 tristate "Dallas/Maxim DS1302"
623 If you say yes here you get support for the Dallas DS1302 RTC chips.
625 This driver can also be built as a module. If so, the module
626 will be called rtc-ds1302.
628 config RTC_DRV_DS1305
629 tristate "Dallas/Maxim DS1305/DS1306"
631 Select this driver to get support for the Dallas/Maxim DS1305
632 and DS1306 real time clock chips. These support a trickle
633 charger, alarms, and NVRAM in addition to the clock.
635 This driver can also be built as a module. If so, the module
636 will be called rtc-ds1305.
638 config RTC_DRV_DS1343
640 tristate "Dallas/Maxim DS1343/DS1344"
642 If you say yes here you get support for the
643 Dallas/Maxim DS1343 and DS1344 real time clock chips.
644 Support for trickle charger, alarm is provided.
646 This driver can also be built as a module. If so, the module
647 will be called rtc-ds1343.
649 config RTC_DRV_DS1347
650 tristate "Dallas/Maxim DS1347"
652 If you say yes here you get support for the
653 Dallas/Maxim DS1347 chips.
655 This driver only supports the RTC feature, and not other chip
656 features such as alarms.
658 This driver can also be built as a module. If so, the module
659 will be called rtc-ds1347.
661 config RTC_DRV_DS1390
662 tristate "Dallas/Maxim DS1390/93/94"
664 If you say yes here you get support for the
665 Dallas/Maxim DS1390/93/94 chips.
667 This driver supports the RTC feature and trickle charging but not
668 other chip features such as alarms.
670 This driver can also be built as a module. If so, the module
671 will be called rtc-ds1390.
674 tristate "Epson RTC-9701JE"
676 If you say yes here you will get support for the
677 Epson RTC-9701JE SPI RTC chip.
679 This driver can also be built as a module. If so, the module
680 will be called rtc-r9701.
682 config RTC_DRV_RX4581
683 tristate "Epson RX-4581"
685 If you say yes here you will get support for the Epson RX-4581.
687 This driver can also be built as a module. If so the module
688 will be called rtc-rx4581.
690 config RTC_DRV_RX6110
691 tristate "Epson RX-6110"
694 If you say yes here you will get support for the Epson RX-6610.
696 This driver can also be built as a module. If so the module
697 will be called rtc-rx6110.
699 config RTC_DRV_RS5C348
700 tristate "Ricoh RS5C348A/B"
702 If you say yes here you get support for the
703 Ricoh RS5C348A and RS5C348B RTC chips.
705 This driver can also be built as a module. If so, the module
706 will be called rtc-rs5c348.
708 config RTC_DRV_MAX6902
709 tristate "Maxim MAX6902"
711 If you say yes here you will get support for the
712 Maxim MAX6902 SPI RTC chip.
714 This driver can also be built as a module. If so, the module
715 will be called rtc-max6902.
717 config RTC_DRV_PCF2123
718 tristate "NXP PCF2123"
720 If you say yes here you get support for the NXP PCF2123
723 This driver can also be built as a module. If so, the module
724 will be called rtc-pcf2123.
726 config RTC_DRV_MCP795
727 tristate "Microchip MCP795"
729 If you say yes here you will get support for the Microchip MCP795.
731 This driver can also be built as a module. If so the module
732 will be called rtc-mcp795.
737 # Helper to resolve issues with configs that have SPI enabled but I2C
738 # modular. See SND_SOC_I2C_AND_SPI for more information
740 config RTC_I2C_AND_SPI
744 default y if SPI_MASTER=y
745 select REGMAP_I2C if I2C
746 select REGMAP_SPI if SPI_MASTER
748 comment "SPI and I2C RTC drivers"
750 config RTC_DRV_DS3232
751 tristate "Dallas/Maxim DS3232/DS3234"
752 depends on RTC_I2C_AND_SPI
754 If you say yes here you get support for Dallas Semiconductor
755 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
756 with the device, the alarm functionality is supported.
758 This driver can also be built as a module. If so, the module
759 will be called rtc-ds3232.
761 config RTC_DRV_PCF2127
762 tristate "NXP PCF2127"
763 depends on RTC_I2C_AND_SPI
765 If you say yes here you get support for the NXP PCF2127/29 RTC
768 This driver can also be built as a module. If so, the module
769 will be called rtc-pcf2127.
771 config RTC_DRV_RV3029C2
772 tristate "Micro Crystal RV3029/3049"
773 depends on RTC_I2C_AND_SPI
775 If you say yes here you get support for the Micro Crystal
776 RV3029 and RV3049 RTC chips.
778 This driver can also be built as a module. If so, the module
779 will be called rtc-rv3029c2.
781 config RTC_DRV_RV3029_HWMON
782 bool "HWMON support for RV3029/3049"
783 depends on RTC_DRV_RV3029C2 && HWMON
784 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
787 Say Y here if you want to expose temperature sensor data on
790 comment "Platform RTC drivers"
792 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
793 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
794 # global rtc_lock ... it's not yet just another platform_device.
797 tristate "PC-style 'CMOS'"
798 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
801 Say "yes" here to get direct support for the real time clock
802 found in every PC or ACPI-based system, and some other boards.
803 Specifically the original MC146818, compatibles like those in
804 PC south bridges, the DS12887 or M48T86, some multifunction
805 or LPC bus chips, and so on.
807 Your system will need to define the platform device used by
808 this driver, otherwise it won't be accessible. This means
809 you can safely enable this driver if you don't know whether
810 or not your board has this kind of hardware.
812 This driver can also be built as a module. If so, the module
813 will be called rtc-cmos.
816 bool "Alpha PC-style CMOS"
820 Direct support for the real-time clock found on every Alpha
821 system, specifically MC146818 compatibles. If in doubt, say Y.
824 tristate "Virtual RTC for Intel MID platforms"
825 depends on X86_INTEL_MID
826 default y if X86_INTEL_MID
829 Say "yes" here to get direct support for the real time clock
830 found on Moorestown platforms. The VRTC is a emulated RTC that
831 derives its clock source from a real RTC in the PMIC. The MC146818
832 style programming interface is mostly conserved, but any
833 updates are done via IPC calls to the system controller FW.
835 config RTC_DRV_DS1216
836 tristate "Dallas DS1216"
839 If you say yes here you get support for the Dallas DS1216 RTC chips.
841 config RTC_DRV_DS1286
842 tristate "Dallas DS1286"
845 If you say yes here you get support for the Dallas DS1286 RTC chips.
847 config RTC_DRV_DS1511
848 tristate "Dallas DS1511"
851 If you say yes here you get support for the
852 Dallas DS1511 timekeeping/watchdog chip.
854 This driver can also be built as a module. If so, the module
855 will be called rtc-ds1511.
857 config RTC_DRV_DS1553
858 tristate "Maxim/Dallas DS1553"
861 If you say yes here you get support for the
862 Maxim/Dallas DS1553 timekeeping chip.
864 This driver can also be built as a module. If so, the module
865 will be called rtc-ds1553.
867 config RTC_DRV_DS1685_FAMILY
868 tristate "Dallas/Maxim DS1685 Family"
870 If you say yes here you get support for the Dallas/Maxim DS1685
871 family of real time chips. This family includes the DS1685/DS1687,
872 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
873 DS17885/DS17887 chips.
875 This driver can also be built as a module. If so, the module
876 will be called rtc-ds1685.
880 depends on RTC_DRV_DS1685_FAMILY
881 default RTC_DRV_DS1685
883 config RTC_DRV_DS1685
886 This enables support for the Dallas/Maxim DS1685/DS1687 real time
889 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
890 systems, as well as EPPC-405-UC modules by electronic system design
893 config RTC_DRV_DS1689
896 This enables support for the Dallas/Maxim DS1689/DS1693 real time
899 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
900 which supports a few minor features such as Vcc, Vbat, and Power
901 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
903 It also works for the even older DS1688/DS1691 RTC chips, which are
904 virtually the same and carry the same model number. Both chips
905 have 114 bytes of user NVRAM.
907 config RTC_DRV_DS17285
908 bool "DS17285/DS17287"
910 This enables support for the Dallas/Maxim DS17285/DS17287 real time
913 This chip features 2kb of extended NV-SRAM. It may possibly be
914 found in some SGI O2 systems (rare).
916 config RTC_DRV_DS17485
917 bool "DS17485/DS17487"
919 This enables support for the Dallas/Maxim DS17485/DS17487 real time
922 This chip features 4kb of extended NV-SRAM.
924 config RTC_DRV_DS17885
925 bool "DS17885/DS17887"
927 This enables support for the Dallas/Maxim DS17885/DS17887 real time
930 This chip features 8kb of extended NV-SRAM.
934 config RTC_DS1685_PROC_REGS
935 bool "Display register values in /proc"
936 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
938 Enable this to display a readout of all of the RTC registers in
939 /proc/drivers/rtc. Keep in mind that this can potentially lead
940 to lost interrupts, as reading Control Register C will clear
941 all pending IRQ flags.
943 Unless you are debugging this driver, choose N.
945 config RTC_DS1685_SYSFS_REGS
946 bool "SysFS access to RTC register bits"
947 depends on RTC_DRV_DS1685_FAMILY && SYSFS
949 Enable this to provide access to the RTC control register bits
950 in /sys. Some of the bits are read-write, others are read-only.
952 Keep in mind that reading Control C's bits automatically clears
953 all pending IRQ flags - this can cause lost interrupts.
955 If you know that you need access to these bits, choose Y, Else N.
957 config RTC_DRV_DS1742
958 tristate "Maxim/Dallas DS1742/1743"
961 If you say yes here you get support for the
962 Maxim/Dallas DS1742/1743 timekeeping chip.
964 This driver can also be built as a module. If so, the module
965 will be called rtc-ds1742.
967 config RTC_DRV_DS2404
968 tristate "Maxim/Dallas DS2404"
970 If you say yes here you get support for the
971 Dallas DS2404 RTC chip.
973 This driver can also be built as a module. If so, the module
974 will be called rtc-ds2404.
976 config RTC_DRV_DA9052
977 tristate "Dialog DA9052/DA9053 RTC"
978 depends on PMIC_DA9052
980 Say y here to support the RTC driver for Dialog Semiconductor
981 DA9052-BC and DA9053-AA/Bx PMICs.
983 config RTC_DRV_DA9055
984 tristate "Dialog Semiconductor DA9055 RTC"
985 depends on MFD_DA9055
987 If you say yes here you will get support for the
988 RTC of the Dialog DA9055 PMIC.
990 This driver can also be built as a module. If so, the module
991 will be called rtc-da9055
993 config RTC_DRV_DA9063
994 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
995 depends on MFD_DA9063 || MFD_DA9062
997 If you say yes here you will get support for the RTC subsystem
998 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1000 This driver can also be built as a module. If so, the module
1001 will be called "rtc-da9063".
1005 depends on EFI && !X86
1007 If you say yes here you will get support for the EFI
1010 This driver can also be built as a module. If so, the module
1011 will be called rtc-efi.
1013 config RTC_DRV_STK17TA8
1014 tristate "Simtek STK17TA8"
1015 depends on HAS_IOMEM
1017 If you say yes here you get support for the
1018 Simtek STK17TA8 timekeeping chip.
1020 This driver can also be built as a module. If so, the module
1021 will be called rtc-stk17ta8.
1023 config RTC_DRV_M48T86
1024 tristate "ST M48T86/Dallas DS12887"
1026 If you say Y here you will get support for the
1027 ST M48T86 and Dallas DS12887 RTC chips.
1029 This driver can also be built as a module. If so, the module
1030 will be called rtc-m48t86.
1032 config RTC_DRV_M48T35
1033 tristate "ST M48T35"
1034 depends on HAS_IOMEM
1036 If you say Y here you will get support for the
1039 This driver can also be built as a module, if so, the module
1040 will be called "rtc-m48t35".
1042 config RTC_DRV_M48T59
1043 tristate "ST M48T59/M48T08/M48T02"
1044 depends on HAS_IOMEM
1046 If you say Y here you will get support for the
1047 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1049 These chips are usually found in Sun SPARC and UltraSPARC
1052 This driver can also be built as a module, if so, the module
1053 will be called "rtc-m48t59".
1055 config RTC_DRV_MSM6242
1056 tristate "Oki MSM6242"
1057 depends on HAS_IOMEM
1059 If you say yes here you get support for the Oki MSM6242
1060 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1062 This driver can also be built as a module. If so, the module
1063 will be called rtc-msm6242.
1065 config RTC_DRV_BQ4802
1066 tristate "TI BQ4802"
1067 depends on HAS_IOMEM
1069 If you say Y here you will get support for the TI
1072 This driver can also be built as a module. If so, the module
1073 will be called rtc-bq4802.
1075 config RTC_DRV_RP5C01
1076 tristate "Ricoh RP5C01"
1077 depends on HAS_IOMEM
1079 If you say yes here you get support for the Ricoh RP5C01
1080 timekeeping chip. It is used in some Amiga models (e.g. A3000
1083 This driver can also be built as a module. If so, the module
1084 will be called rtc-rp5c01.
1086 config RTC_DRV_V3020
1087 tristate "EM Microelectronic V3020"
1089 If you say yes here you will get support for the
1090 EM Microelectronic v3020 RTC chip.
1092 This driver can also be built as a module. If so, the module
1093 will be called rtc-v3020.
1095 config RTC_DRV_WM831X
1096 tristate "Wolfson Microelectronics WM831x RTC"
1097 depends on MFD_WM831X
1099 If you say yes here you will get support for the RTC subsystem
1100 of the Wolfson Microelectronics WM831X series PMICs.
1102 This driver can also be built as a module. If so, the module
1103 will be called "rtc-wm831x".
1105 config RTC_DRV_WM8350
1106 tristate "Wolfson Microelectronics WM8350 RTC"
1107 depends on MFD_WM8350
1109 If you say yes here you will get support for the RTC subsystem
1110 of the Wolfson Microelectronics WM8350.
1112 This driver can also be built as a module. If so, the module
1113 will be called "rtc-wm8350".
1115 config RTC_DRV_SPEAR
1116 tristate "SPEAR ST RTC"
1117 depends on PLAT_SPEAR || COMPILE_TEST
1120 If you say Y here you will get support for the RTC found on
1123 config RTC_DRV_PCF50633
1124 depends on MFD_PCF50633
1125 tristate "NXP PCF50633 RTC"
1127 If you say yes here you get support for the RTC subsystem of the
1128 NXP PCF50633 used in embedded systems.
1130 config RTC_DRV_AB3100
1131 tristate "ST-Ericsson AB3100 RTC"
1132 depends on AB3100_CORE
1133 default y if AB3100_CORE
1135 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1136 support. This chip contains a battery- and capacitor-backed RTC.
1138 config RTC_DRV_AB8500
1139 tristate "ST-Ericsson AB8500 RTC"
1140 depends on AB8500_CORE
1142 select RTC_INTF_DEV_UIE_EMUL
1144 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1145 support. This chip contains a battery- and capacitor-backed RTC.
1147 config RTC_DRV_NUC900
1148 tristate "NUC910/NUC920 RTC driver"
1149 depends on ARCH_W90X900 || COMPILE_TEST
1151 If you say yes here you get support for the RTC subsystem of the
1152 NUC910/NUC920 used in embedded systems.
1155 tristate "IBM OPAL RTC driver"
1156 depends on PPC_POWERNV
1159 If you say yes here you get support for the PowerNV platform RTC
1160 driver based on OPAL interfaces.
1162 This driver can also be built as a module. If so, the module
1163 will be called rtc-opal.
1165 config RTC_DRV_ZYNQMP
1166 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1169 If you say yes here you get support for the RTC controller found on
1170 Xilinx Zynq Ultrascale+ MPSoC.
1172 comment "on-CPU RTC drivers"
1174 config RTC_DRV_ASM9260
1175 tristate "Alphascale asm9260 RTC"
1176 depends on MACH_ASM9260
1178 If you say yes here you get support for the RTC on the
1179 Alphascale asm9260 SoC.
1181 This driver can also be built as a module. If so, the module
1182 will be called rtc-asm9260.
1184 config RTC_DRV_DAVINCI
1185 tristate "TI DaVinci RTC"
1186 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1188 If you say yes here you get support for the RTC on the
1189 DaVinci platforms (DM365).
1191 This driver can also be built as a module. If so, the module
1192 will be called rtc-davinci.
1194 config RTC_DRV_DIGICOLOR
1195 tristate "Conexant Digicolor RTC"
1196 depends on ARCH_DIGICOLOR || COMPILE_TEST
1198 If you say yes here you get support for the RTC on Conexant
1199 Digicolor platforms. This currently includes the CX92755 SoC.
1201 This driver can also be built as a module. If so, the module
1202 will be called rtc-digicolor.
1204 config RTC_DRV_IMXDI
1205 tristate "Freescale IMX DryIce Real Time Clock"
1208 Support for Freescale IMX DryIce RTC
1210 This driver can also be built as a module, if so, the module
1211 will be called "rtc-imxdi".
1214 tristate "TI OMAP Real Time Clock"
1215 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1217 Say "yes" here to support the on chip real time clock
1218 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1220 This driver can also be built as a module, if so, module
1221 will be called rtc-omap.
1226 This will include RTC support for Samsung SoCs. If
1227 you want to include RTC support for any machine, kindly
1228 select this in the respective mach-XXXX/Kconfig file.
1231 tristate "Samsung S3C series SoC RTC"
1232 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1234 RTC (Realtime Clock) driver for the clock inbuilt into the
1235 Samsung S3C24XX series of SoCs. This can provide periodic
1236 interrupt rates from 1Hz to 64Hz for user programs, and
1239 The driver currently supports the common features on all the
1240 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1243 This driver can also be build as a module. If so, the module
1244 will be called rtc-s3c.
1246 config RTC_DRV_EP93XX
1247 tristate "Cirrus Logic EP93XX"
1248 depends on ARCH_EP93XX || COMPILE_TEST
1250 If you say yes here you get support for the
1251 RTC embedded in the Cirrus Logic EP93XX processors.
1253 This driver can also be built as a module. If so, the module
1254 will be called rtc-ep93xx.
1256 config RTC_DRV_SA1100
1257 tristate "SA11x0/PXA2xx/PXA910"
1258 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1260 If you say Y here you will get access to the real time clock
1261 built into your SA11x0 or PXA2xx CPU.
1263 To compile this driver as a module, choose M here: the
1264 module will be called rtc-sa1100.
1267 tristate "SuperH On-Chip RTC"
1268 depends on SUPERH && HAVE_CLK
1270 Say Y here to enable support for the on-chip RTC found in
1271 most SuperH processors.
1273 To compile this driver as a module, choose M here: the
1274 module will be called rtc-sh.
1276 config RTC_DRV_VR41XX
1277 tristate "NEC VR41XX"
1278 depends on CPU_VR41XX || COMPILE_TEST
1280 If you say Y here you will get access to the real time clock
1281 built into your NEC VR41XX CPU.
1283 To compile this driver as a module, choose M here: the
1284 module will be called rtc-vr41xx.
1286 config RTC_DRV_PL030
1287 tristate "ARM AMBA PL030 RTC"
1290 If you say Y here you will get access to ARM AMBA
1291 PrimeCell PL030 RTC found on certain ARM SOCs.
1293 To compile this driver as a module, choose M here: the
1294 module will be called rtc-pl030.
1296 config RTC_DRV_PL031
1297 tristate "ARM AMBA PL031 RTC"
1300 If you say Y here you will get access to ARM AMBA
1301 PrimeCell PL031 RTC found on certain ARM SOCs.
1303 To compile this driver as a module, choose M here: the
1304 module will be called rtc-pl031.
1306 config RTC_DRV_AT32AP700X
1307 tristate "AT32AP700X series RTC"
1308 depends on PLATFORM_AT32AP || COMPILE_TEST
1310 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1311 AT32AP700x family processors.
1313 config RTC_DRV_AT91RM9200
1314 tristate "AT91RM9200 or some AT91SAM9 RTC"
1315 depends on ARCH_AT91 || COMPILE_TEST
1317 Driver for the internal RTC (Realtime Clock) module found on
1318 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1319 this is powered by the backup power supply.
1321 config RTC_DRV_AT91SAM9
1322 tristate "AT91SAM9 RTT as RTC"
1323 depends on ARCH_AT91 || COMPILE_TEST
1326 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1327 can be used as an RTC thanks to the backup power supply (e.g. a
1328 small coin cell battery) which keeps this block and the GPBR
1329 (General Purpose Backup Registers) block powered when the device
1331 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1332 probably want to use the real RTC block instead of the "RTT as an
1335 config RTC_DRV_AU1XXX
1336 tristate "Au1xxx Counter0 RTC support"
1337 depends on MIPS_ALCHEMY
1339 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1340 counter) to be used as a RTC.
1342 This driver can also be built as a module. If so, the module
1343 will be called rtc-au1xxx.
1346 tristate "Blackfin On-Chip RTC"
1347 depends on BLACKFIN && !BF561
1349 If you say yes here you will get support for the
1350 Blackfin On-Chip Real Time Clock.
1352 This driver can also be built as a module. If so, the module
1353 will be called rtc-bfin.
1355 config RTC_DRV_RS5C313
1356 tristate "Ricoh RS5C313"
1357 depends on SH_LANDISK
1359 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1361 config RTC_DRV_GENERIC
1362 tristate "Generic RTC support"
1363 # Please consider writing a new RTC driver instead of using the generic
1365 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
1367 Say Y or M here to enable RTC support on systems using the generic
1368 RTC abstraction. If you do not know what you are doing, you should
1372 tristate "PXA27x/PXA3xx"
1374 select RTC_DRV_SA1100
1376 If you say Y here you will get access to the real time clock
1377 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1378 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1380 This RTC driver uses PXA RTC registers available since pxa27x
1381 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1383 config RTC_DRV_VT8500
1384 tristate "VIA/WonderMedia 85xx SoC RTC"
1385 depends on ARCH_VT8500 || COMPILE_TEST
1387 If you say Y here you will get access to the real time clock
1388 built into your VIA VT8500 SoC or its relatives.
1391 config RTC_DRV_SUN4V
1392 bool "SUN4V Hypervisor RTC"
1395 If you say Y here you will get support for the Hypervisor
1396 based RTC on SUN4V systems.
1398 config RTC_DRV_SUN6I
1399 tristate "Allwinner A31 RTC"
1400 default MACH_SUN6I || MACH_SUN8I || COMPILE_TEST
1401 depends on ARCH_SUNXI
1403 If you say Y here you will get support for the RTC found in
1404 some Allwinner SoCs like the A31 or the A64.
1406 config RTC_DRV_SUNXI
1407 tristate "Allwinner sun4i/sun7i RTC"
1408 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1410 If you say Y here you will get support for the RTC found on
1413 config RTC_DRV_STARFIRE
1417 If you say Y here you will get support for the RTC found on
1420 config RTC_DRV_TX4939
1421 tristate "TX4939 SoC"
1422 depends on SOC_TX4939
1424 Driver for the internal RTC (Realtime Clock) module found on
1428 tristate "Marvell SoC RTC"
1429 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1431 If you say yes here you will get support for the in-chip RTC
1432 that can be found in some of Marvell's SoC devices, such as
1433 the Kirkwood 88F6281 and 88F6192.
1435 This driver can also be built as a module. If so, the module
1436 will be called rtc-mv.
1438 config RTC_DRV_ARMADA38X
1439 tristate "Armada 38x Marvell SoC RTC"
1440 depends on ARCH_MVEBU || COMPILE_TEST
1442 If you say yes here you will get support for the in-chip RTC
1443 that can be found in the Armada 38x Marvell's SoC device
1445 This driver can also be built as a module. If so, the module
1446 will be called armada38x-rtc.
1448 config RTC_DRV_GEMINI
1449 tristate "Gemini SoC RTC"
1450 depends on ARCH_GEMINI || COMPILE_TEST
1451 depends on HAS_IOMEM
1453 If you say Y here you will get support for the
1454 RTC found on Gemini SoC's.
1456 This driver can also be built as a module. If so, the module
1457 will be called rtc-gemini.
1463 If you say yes here you will get support for the RTC on PS3.
1465 This driver can also be built as a module. If so, the module
1466 will be called rtc-ps3.
1468 config RTC_DRV_COH901331
1469 tristate "ST-Ericsson COH 901 331 RTC"
1470 depends on ARCH_U300 || COMPILE_TEST
1472 If you say Y here you will get access to ST-Ericsson
1473 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1476 This driver can also be built as a module. If so, the module
1477 will be called "rtc-coh901331".
1481 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1482 depends on ARCH_MXS || COMPILE_TEST
1485 If you say yes here you will get support for the onboard
1486 STMP3xxx/i.MX23/i.MX28 RTC.
1488 This driver can also be built as a module. If so, the module
1489 will be called rtc-stmp3xxx.
1495 If you say Y here you will get support for the RTC found on
1496 the PCAP2 ASIC used on some Motorola phones.
1498 config RTC_DRV_MC13XXX
1499 depends on MFD_MC13XXX
1500 tristate "Freescale MC13xxx RTC"
1502 This enables support for the RTCs found on Freescale's PMICs
1503 MC13783 and MC13892.
1505 config RTC_DRV_MPC5121
1506 tristate "Freescale MPC5121 built-in RTC"
1507 depends on PPC_MPC512x || PPC_MPC52xx
1509 If you say yes here you will get support for the
1510 built-in RTC on MPC5121 or on MPC5200.
1512 This driver can also be built as a module. If so, the module
1513 will be called rtc-mpc5121.
1515 config RTC_DRV_JZ4740
1516 tristate "Ingenic JZ4740 SoC"
1517 depends on MACH_JZ4740 || COMPILE_TEST
1519 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1522 This driver can also be buillt as a module. If so, the module
1523 will be called rtc-jz4740.
1525 config RTC_DRV_LPC24XX
1526 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1527 depends on ARCH_LPC18XX || COMPILE_TEST
1528 depends on OF && HAS_IOMEM
1530 This enables support for the NXP RTC found which can be found on
1531 NXP LPC178x/18xx/408x/43xx devices.
1533 If you have one of the devices above enable this driver to use
1534 the hardware RTC. This driver can also be buillt as a module. If
1535 so, the module will be called rtc-lpc24xx.
1537 config RTC_DRV_LPC32XX
1538 depends on ARCH_LPC32XX || COMPILE_TEST
1539 tristate "NXP LPC32XX RTC"
1541 This enables support for the NXP RTC in the LPC32XX
1543 This driver can also be buillt as a module. If so, the module
1544 will be called rtc-lpc32xx.
1546 config RTC_DRV_PM8XXX
1547 tristate "Qualcomm PMIC8XXX RTC"
1548 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1550 If you say yes here you get support for the
1551 Qualcomm PMIC8XXX RTC.
1553 To compile this driver as a module, choose M here: the
1554 module will be called rtc-pm8xxx.
1556 config RTC_DRV_TEGRA
1557 tristate "NVIDIA Tegra Internal RTC driver"
1558 depends on ARCH_TEGRA || COMPILE_TEST
1560 If you say yes here you get support for the
1561 Tegra 200 series internal RTC module.
1563 This drive can also be built as a module. If so, the module
1564 will be called rtc-tegra.
1567 tristate "Tilera hypervisor RTC support"
1570 Enable support for the Linux driver side of the Tilera
1571 hypervisor's real-time clock interface.
1574 tristate "PKUnity v3 RTC support"
1575 depends on ARCH_PUV3
1577 This enables support for the RTC in the PKUnity-v3 SoCs.
1579 This drive can also be built as a module. If so, the module
1580 will be called rtc-puv3.
1582 config RTC_DRV_LOONGSON1
1583 tristate "loongson1 RTC support"
1584 depends on MACH_LOONGSON32
1586 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1587 counter) to be used as a RTC.
1589 This driver can also be built as a module. If so, the module
1590 will be called rtc-ls1x.
1593 tristate "Freescale MXC Real Time Clock"
1596 If you say yes here you get support for the Freescale MXC
1599 This driver can also be built as a module, if so, the module
1600 will be called "rtc-mxc".
1603 tristate "Freescale SNVS RTC support"
1605 depends on HAS_IOMEM
1608 If you say yes here you get support for the Freescale SNVS
1609 Low Power (LP) RTC module.
1611 This driver can also be built as a module, if so, the module
1612 will be called "rtc-snvs".
1614 config RTC_DRV_SIRFSOC
1615 tristate "SiRFSOC RTC"
1616 depends on ARCH_SIRF
1618 Say "yes" here to support the real time clock on SiRF SOC chips.
1619 This driver can also be built as a module called rtc-sirfsoc.
1621 config RTC_DRV_ST_LPC
1622 tristate "STMicroelectronics LPC RTC"
1626 Say Y here to include STMicroelectronics Low Power Controller
1627 (LPC) based RTC support.
1629 To compile this driver as a module, choose M here: the
1630 module will be called rtc-st-lpc.
1632 config RTC_DRV_MOXART
1633 tristate "MOXA ART RTC"
1634 depends on ARCH_MOXART || COMPILE_TEST
1636 If you say yes here you get support for the MOXA ART
1639 This driver can also be built as a module. If so, the module
1640 will be called rtc-moxart
1642 config RTC_DRV_MT6397
1643 tristate "Mediatek Real Time Clock driver"
1644 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1646 This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
1647 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1648 Mediatek(R) RTC driver.
1650 If you want to use Mediatek(R) RTC interface, select Y or M here.
1652 config RTC_DRV_XGENE
1653 tristate "APM X-Gene RTC"
1654 depends on HAS_IOMEM
1655 depends on ARCH_XGENE || COMPILE_TEST
1657 If you say yes here you get support for the APM X-Gene SoC real time
1660 This driver can also be built as a module, if so, the module
1661 will be called "rtc-xgene".
1663 config RTC_DRV_PIC32
1664 tristate "Microchip PIC32 RTC"
1665 depends on MACH_PIC32
1668 If you say yes here you get support for the PIC32 RTC module.
1670 This driver can also be built as a module. If so, the module
1671 will be called rtc-pic32
1673 comment "HID Sensor RTC drivers"
1675 config RTC_DRV_HID_SENSOR_TIME
1676 tristate "HID Sensor Time"
1679 select HID_SENSOR_HUB
1680 select HID_SENSOR_IIO_COMMON
1682 Say yes here to build support for the HID Sensors of type Time.
1683 This drivers makes such sensors available as RTCs.
1685 If this driver is compiled as a module, it will be named
1686 rtc-hid-sensor-time.