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.
673 config RTC_DRV_MAX6916
674 tristate "Maxim MAX6916"
676 If you say yes here you will get support for the
677 Maxim MAX6916 SPI RTC chip.
679 This driver only supports the RTC feature, and not other chip
680 features such as alarms.
682 This driver can also be built as a module. If so, the module
683 will be called rtc-max6916.
686 tristate "Epson RTC-9701JE"
688 If you say yes here you will get support for the
689 Epson RTC-9701JE SPI RTC chip.
691 This driver can also be built as a module. If so, the module
692 will be called rtc-r9701.
694 config RTC_DRV_RX4581
695 tristate "Epson RX-4581"
697 If you say yes here you will get support for the Epson RX-4581.
699 This driver can also be built as a module. If so the module
700 will be called rtc-rx4581.
702 config RTC_DRV_RX6110
703 tristate "Epson RX-6110"
706 If you say yes here you will get support for the Epson RX-6610.
708 This driver can also be built as a module. If so the module
709 will be called rtc-rx6110.
711 config RTC_DRV_RS5C348
712 tristate "Ricoh RS5C348A/B"
714 If you say yes here you get support for the
715 Ricoh RS5C348A and RS5C348B RTC chips.
717 This driver can also be built as a module. If so, the module
718 will be called rtc-rs5c348.
720 config RTC_DRV_MAX6902
721 tristate "Maxim MAX6902"
723 If you say yes here you will get support for the
724 Maxim MAX6902 SPI RTC chip.
726 This driver can also be built as a module. If so, the module
727 will be called rtc-max6902.
729 config RTC_DRV_PCF2123
730 tristate "NXP PCF2123"
732 If you say yes here you get support for the NXP PCF2123
735 This driver can also be built as a module. If so, the module
736 will be called rtc-pcf2123.
738 config RTC_DRV_MCP795
739 tristate "Microchip MCP795"
741 If you say yes here you will get support for the Microchip MCP795.
743 This driver can also be built as a module. If so the module
744 will be called rtc-mcp795.
749 # Helper to resolve issues with configs that have SPI enabled but I2C
750 # modular. See SND_SOC_I2C_AND_SPI for more information
752 config RTC_I2C_AND_SPI
756 default y if SPI_MASTER=y
757 select REGMAP_I2C if I2C
758 select REGMAP_SPI if SPI_MASTER
760 comment "SPI and I2C RTC drivers"
762 config RTC_DRV_DS3232
763 tristate "Dallas/Maxim DS3232/DS3234"
764 depends on RTC_I2C_AND_SPI
766 If you say yes here you get support for Dallas Semiconductor
767 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
768 with the device, the alarm functionality is supported.
770 This driver can also be built as a module. If so, the module
771 will be called rtc-ds3232.
773 config RTC_DRV_PCF2127
774 tristate "NXP PCF2127"
775 depends on RTC_I2C_AND_SPI
777 If you say yes here you get support for the NXP PCF2127/29 RTC
780 This driver can also be built as a module. If so, the module
781 will be called rtc-pcf2127.
783 config RTC_DRV_RV3029C2
784 tristate "Micro Crystal RV3029/3049"
785 depends on RTC_I2C_AND_SPI
787 If you say yes here you get support for the Micro Crystal
788 RV3029 and RV3049 RTC chips.
790 This driver can also be built as a module. If so, the module
791 will be called rtc-rv3029c2.
793 config RTC_DRV_RV3029_HWMON
794 bool "HWMON support for RV3029/3049"
795 depends on RTC_DRV_RV3029C2 && HWMON
796 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
799 Say Y here if you want to expose temperature sensor data on
802 comment "Platform RTC drivers"
804 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
805 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
806 # global rtc_lock ... it's not yet just another platform_device.
809 tristate "PC-style 'CMOS'"
810 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64 || MN10300
813 Say "yes" here to get direct support for the real time clock
814 found in every PC or ACPI-based system, and some other boards.
815 Specifically the original MC146818, compatibles like those in
816 PC south bridges, the DS12887 or M48T86, some multifunction
817 or LPC bus chips, and so on.
819 Your system will need to define the platform device used by
820 this driver, otherwise it won't be accessible. This means
821 you can safely enable this driver if you don't know whether
822 or not your board has this kind of hardware.
824 This driver can also be built as a module. If so, the module
825 will be called rtc-cmos.
828 bool "Alpha PC-style CMOS"
832 Direct support for the real-time clock found on every Alpha
833 system, specifically MC146818 compatibles. If in doubt, say Y.
836 tristate "Virtual RTC for Intel MID platforms"
837 depends on X86_INTEL_MID
838 default y if X86_INTEL_MID
841 Say "yes" here to get direct support for the real time clock
842 found on Moorestown platforms. The VRTC is a emulated RTC that
843 derives its clock source from a real RTC in the PMIC. The MC146818
844 style programming interface is mostly conserved, but any
845 updates are done via IPC calls to the system controller FW.
847 config RTC_DRV_DS1216
848 tristate "Dallas DS1216"
851 If you say yes here you get support for the Dallas DS1216 RTC chips.
853 config RTC_DRV_DS1286
854 tristate "Dallas DS1286"
857 If you say yes here you get support for the Dallas DS1286 RTC chips.
859 config RTC_DRV_DS1511
860 tristate "Dallas DS1511"
863 If you say yes here you get support for the
864 Dallas DS1511 timekeeping/watchdog chip.
866 This driver can also be built as a module. If so, the module
867 will be called rtc-ds1511.
869 config RTC_DRV_DS1553
870 tristate "Maxim/Dallas DS1553"
873 If you say yes here you get support for the
874 Maxim/Dallas DS1553 timekeeping chip.
876 This driver can also be built as a module. If so, the module
877 will be called rtc-ds1553.
879 config RTC_DRV_DS1685_FAMILY
880 tristate "Dallas/Maxim DS1685 Family"
882 If you say yes here you get support for the Dallas/Maxim DS1685
883 family of real time chips. This family includes the DS1685/DS1687,
884 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
885 DS17885/DS17887 chips.
887 This driver can also be built as a module. If so, the module
888 will be called rtc-ds1685.
892 depends on RTC_DRV_DS1685_FAMILY
893 default RTC_DRV_DS1685
895 config RTC_DRV_DS1685
898 This enables support for the Dallas/Maxim DS1685/DS1687 real time
901 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
902 systems, as well as EPPC-405-UC modules by electronic system design
905 config RTC_DRV_DS1689
908 This enables support for the Dallas/Maxim DS1689/DS1693 real time
911 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
912 which supports a few minor features such as Vcc, Vbat, and Power
913 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
915 It also works for the even older DS1688/DS1691 RTC chips, which are
916 virtually the same and carry the same model number. Both chips
917 have 114 bytes of user NVRAM.
919 config RTC_DRV_DS17285
920 bool "DS17285/DS17287"
922 This enables support for the Dallas/Maxim DS17285/DS17287 real time
925 This chip features 2kb of extended NV-SRAM. It may possibly be
926 found in some SGI O2 systems (rare).
928 config RTC_DRV_DS17485
929 bool "DS17485/DS17487"
931 This enables support for the Dallas/Maxim DS17485/DS17487 real time
934 This chip features 4kb of extended NV-SRAM.
936 config RTC_DRV_DS17885
937 bool "DS17885/DS17887"
939 This enables support for the Dallas/Maxim DS17885/DS17887 real time
942 This chip features 8kb of extended NV-SRAM.
946 config RTC_DS1685_PROC_REGS
947 bool "Display register values in /proc"
948 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
950 Enable this to display a readout of all of the RTC registers in
951 /proc/drivers/rtc. Keep in mind that this can potentially lead
952 to lost interrupts, as reading Control Register C will clear
953 all pending IRQ flags.
955 Unless you are debugging this driver, choose N.
957 config RTC_DS1685_SYSFS_REGS
958 bool "SysFS access to RTC register bits"
959 depends on RTC_DRV_DS1685_FAMILY && SYSFS
961 Enable this to provide access to the RTC control register bits
962 in /sys. Some of the bits are read-write, others are read-only.
964 Keep in mind that reading Control C's bits automatically clears
965 all pending IRQ flags - this can cause lost interrupts.
967 If you know that you need access to these bits, choose Y, Else N.
969 config RTC_DRV_DS1742
970 tristate "Maxim/Dallas DS1742/1743"
973 If you say yes here you get support for the
974 Maxim/Dallas DS1742/1743 timekeeping chip.
976 This driver can also be built as a module. If so, the module
977 will be called rtc-ds1742.
979 config RTC_DRV_DS2404
980 tristate "Maxim/Dallas DS2404"
982 If you say yes here you get support for the
983 Dallas DS2404 RTC chip.
985 This driver can also be built as a module. If so, the module
986 will be called rtc-ds2404.
988 config RTC_DRV_DA9052
989 tristate "Dialog DA9052/DA9053 RTC"
990 depends on PMIC_DA9052
992 Say y here to support the RTC driver for Dialog Semiconductor
993 DA9052-BC and DA9053-AA/Bx PMICs.
995 config RTC_DRV_DA9055
996 tristate "Dialog Semiconductor DA9055 RTC"
997 depends on MFD_DA9055
999 If you say yes here you will get support for the
1000 RTC of the Dialog DA9055 PMIC.
1002 This driver can also be built as a module. If so, the module
1003 will be called rtc-da9055
1005 config RTC_DRV_DA9063
1006 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1007 depends on MFD_DA9063 || MFD_DA9062
1009 If you say yes here you will get support for the RTC subsystem
1010 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1012 This driver can also be built as a module. If so, the module
1013 will be called "rtc-da9063".
1017 depends on EFI && !X86
1019 If you say yes here you will get support for the EFI
1022 This driver can also be built as a module. If so, the module
1023 will be called rtc-efi.
1025 config RTC_DRV_STK17TA8
1026 tristate "Simtek STK17TA8"
1027 depends on HAS_IOMEM
1029 If you say yes here you get support for the
1030 Simtek STK17TA8 timekeeping chip.
1032 This driver can also be built as a module. If so, the module
1033 will be called rtc-stk17ta8.
1035 config RTC_DRV_M48T86
1036 tristate "ST M48T86/Dallas DS12887"
1038 If you say Y here you will get support for the
1039 ST M48T86 and Dallas DS12887 RTC chips.
1041 This driver can also be built as a module. If so, the module
1042 will be called rtc-m48t86.
1044 config RTC_DRV_M48T35
1045 tristate "ST M48T35"
1046 depends on HAS_IOMEM
1048 If you say Y here you will get support for the
1051 This driver can also be built as a module, if so, the module
1052 will be called "rtc-m48t35".
1054 config RTC_DRV_M48T59
1055 tristate "ST M48T59/M48T08/M48T02"
1056 depends on HAS_IOMEM
1058 If you say Y here you will get support for the
1059 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1061 These chips are usually found in Sun SPARC and UltraSPARC
1064 This driver can also be built as a module, if so, the module
1065 will be called "rtc-m48t59".
1067 config RTC_DRV_MSM6242
1068 tristate "Oki MSM6242"
1069 depends on HAS_IOMEM
1071 If you say yes here you get support for the Oki MSM6242
1072 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1074 This driver can also be built as a module. If so, the module
1075 will be called rtc-msm6242.
1077 config RTC_DRV_BQ4802
1078 tristate "TI BQ4802"
1079 depends on HAS_IOMEM
1081 If you say Y here you will get support for the TI
1084 This driver can also be built as a module. If so, the module
1085 will be called rtc-bq4802.
1087 config RTC_DRV_RP5C01
1088 tristate "Ricoh RP5C01"
1089 depends on HAS_IOMEM
1091 If you say yes here you get support for the Ricoh RP5C01
1092 timekeeping chip. It is used in some Amiga models (e.g. A3000
1095 This driver can also be built as a module. If so, the module
1096 will be called rtc-rp5c01.
1098 config RTC_DRV_V3020
1099 tristate "EM Microelectronic V3020"
1101 If you say yes here you will get support for the
1102 EM Microelectronic v3020 RTC chip.
1104 This driver can also be built as a module. If so, the module
1105 will be called rtc-v3020.
1107 config RTC_DRV_WM831X
1108 tristate "Wolfson Microelectronics WM831x RTC"
1109 depends on MFD_WM831X
1111 If you say yes here you will get support for the RTC subsystem
1112 of the Wolfson Microelectronics WM831X series PMICs.
1114 This driver can also be built as a module. If so, the module
1115 will be called "rtc-wm831x".
1117 config RTC_DRV_WM8350
1118 tristate "Wolfson Microelectronics WM8350 RTC"
1119 depends on MFD_WM8350
1121 If you say yes here you will get support for the RTC subsystem
1122 of the Wolfson Microelectronics WM8350.
1124 This driver can also be built as a module. If so, the module
1125 will be called "rtc-wm8350".
1127 config RTC_DRV_SPEAR
1128 tristate "SPEAR ST RTC"
1129 depends on PLAT_SPEAR || COMPILE_TEST
1132 If you say Y here you will get support for the RTC found on
1135 config RTC_DRV_PCF50633
1136 depends on MFD_PCF50633
1137 tristate "NXP PCF50633 RTC"
1139 If you say yes here you get support for the RTC subsystem of the
1140 NXP PCF50633 used in embedded systems.
1142 config RTC_DRV_AB3100
1143 tristate "ST-Ericsson AB3100 RTC"
1144 depends on AB3100_CORE
1145 default y if AB3100_CORE
1147 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1148 support. This chip contains a battery- and capacitor-backed RTC.
1150 config RTC_DRV_AB8500
1151 tristate "ST-Ericsson AB8500 RTC"
1152 depends on AB8500_CORE
1154 select RTC_INTF_DEV_UIE_EMUL
1156 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1157 support. This chip contains a battery- and capacitor-backed RTC.
1159 config RTC_DRV_NUC900
1160 tristate "NUC910/NUC920 RTC driver"
1161 depends on ARCH_W90X900 || COMPILE_TEST
1163 If you say yes here you get support for the RTC subsystem of the
1164 NUC910/NUC920 used in embedded systems.
1167 tristate "IBM OPAL RTC driver"
1168 depends on PPC_POWERNV
1171 If you say yes here you get support for the PowerNV platform RTC
1172 driver based on OPAL interfaces.
1174 This driver can also be built as a module. If so, the module
1175 will be called rtc-opal.
1177 config RTC_DRV_ZYNQMP
1178 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1181 If you say yes here you get support for the RTC controller found on
1182 Xilinx Zynq Ultrascale+ MPSoC.
1184 comment "on-CPU RTC drivers"
1186 config RTC_DRV_ASM9260
1187 tristate "Alphascale asm9260 RTC"
1188 depends on MACH_ASM9260
1190 If you say yes here you get support for the RTC on the
1191 Alphascale asm9260 SoC.
1193 This driver can also be built as a module. If so, the module
1194 will be called rtc-asm9260.
1196 config RTC_DRV_DAVINCI
1197 tristate "TI DaVinci RTC"
1198 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1200 If you say yes here you get support for the RTC on the
1201 DaVinci platforms (DM365).
1203 This driver can also be built as a module. If so, the module
1204 will be called rtc-davinci.
1206 config RTC_DRV_DIGICOLOR
1207 tristate "Conexant Digicolor RTC"
1208 depends on ARCH_DIGICOLOR || COMPILE_TEST
1210 If you say yes here you get support for the RTC on Conexant
1211 Digicolor platforms. This currently includes the CX92755 SoC.
1213 This driver can also be built as a module. If so, the module
1214 will be called rtc-digicolor.
1216 config RTC_DRV_IMXDI
1217 tristate "Freescale IMX DryIce Real Time Clock"
1220 Support for Freescale IMX DryIce RTC
1222 This driver can also be built as a module, if so, the module
1223 will be called "rtc-imxdi".
1226 tristate "TI OMAP Real Time Clock"
1227 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1229 Say "yes" here to support the on chip real time clock
1230 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1232 This driver can also be built as a module, if so, module
1233 will be called rtc-omap.
1238 This will include RTC support for Samsung SoCs. If
1239 you want to include RTC support for any machine, kindly
1240 select this in the respective mach-XXXX/Kconfig file.
1243 tristate "Samsung S3C series SoC RTC"
1244 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1246 RTC (Realtime Clock) driver for the clock inbuilt into the
1247 Samsung S3C24XX series of SoCs. This can provide periodic
1248 interrupt rates from 1Hz to 64Hz for user programs, and
1251 The driver currently supports the common features on all the
1252 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1255 This driver can also be build as a module. If so, the module
1256 will be called rtc-s3c.
1258 config RTC_DRV_EP93XX
1259 tristate "Cirrus Logic EP93XX"
1260 depends on ARCH_EP93XX || COMPILE_TEST
1262 If you say yes here you get support for the
1263 RTC embedded in the Cirrus Logic EP93XX processors.
1265 This driver can also be built as a module. If so, the module
1266 will be called rtc-ep93xx.
1268 config RTC_DRV_SA1100
1269 tristate "SA11x0/PXA2xx/PXA910"
1270 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1272 If you say Y here you will get access to the real time clock
1273 built into your SA11x0 or PXA2xx CPU.
1275 To compile this driver as a module, choose M here: the
1276 module will be called rtc-sa1100.
1279 tristate "SuperH On-Chip RTC"
1280 depends on SUPERH && HAVE_CLK
1282 Say Y here to enable support for the on-chip RTC found in
1283 most SuperH processors.
1285 To compile this driver as a module, choose M here: the
1286 module will be called rtc-sh.
1288 config RTC_DRV_VR41XX
1289 tristate "NEC VR41XX"
1290 depends on CPU_VR41XX || COMPILE_TEST
1292 If you say Y here you will get access to the real time clock
1293 built into your NEC VR41XX CPU.
1295 To compile this driver as a module, choose M here: the
1296 module will be called rtc-vr41xx.
1298 config RTC_DRV_PL030
1299 tristate "ARM AMBA PL030 RTC"
1302 If you say Y here you will get access to ARM AMBA
1303 PrimeCell PL030 RTC found on certain ARM SOCs.
1305 To compile this driver as a module, choose M here: the
1306 module will be called rtc-pl030.
1308 config RTC_DRV_PL031
1309 tristate "ARM AMBA PL031 RTC"
1312 If you say Y here you will get access to ARM AMBA
1313 PrimeCell PL031 RTC found on certain ARM SOCs.
1315 To compile this driver as a module, choose M here: the
1316 module will be called rtc-pl031.
1318 config RTC_DRV_AT32AP700X
1319 tristate "AT32AP700X series RTC"
1320 depends on PLATFORM_AT32AP || COMPILE_TEST
1322 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1323 AT32AP700x family processors.
1325 config RTC_DRV_AT91RM9200
1326 tristate "AT91RM9200 or some AT91SAM9 RTC"
1327 depends on ARCH_AT91 || COMPILE_TEST
1329 Driver for the internal RTC (Realtime Clock) module found on
1330 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1331 this is powered by the backup power supply.
1333 config RTC_DRV_AT91SAM9
1334 tristate "AT91SAM9 RTT as RTC"
1335 depends on ARCH_AT91 || COMPILE_TEST
1338 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1339 can be used as an RTC thanks to the backup power supply (e.g. a
1340 small coin cell battery) which keeps this block and the GPBR
1341 (General Purpose Backup Registers) block powered when the device
1343 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1344 probably want to use the real RTC block instead of the "RTT as an
1347 config RTC_DRV_AU1XXX
1348 tristate "Au1xxx Counter0 RTC support"
1349 depends on MIPS_ALCHEMY
1351 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1352 counter) to be used as a RTC.
1354 This driver can also be built as a module. If so, the module
1355 will be called rtc-au1xxx.
1358 tristate "Blackfin On-Chip RTC"
1359 depends on BLACKFIN && !BF561
1361 If you say yes here you will get support for the
1362 Blackfin On-Chip Real Time Clock.
1364 This driver can also be built as a module. If so, the module
1365 will be called rtc-bfin.
1367 config RTC_DRV_RS5C313
1368 tristate "Ricoh RS5C313"
1369 depends on SH_LANDISK
1371 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1373 config RTC_DRV_GENERIC
1374 tristate "Generic RTC support"
1375 # Please consider writing a new RTC driver instead of using the generic
1377 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
1379 Say Y or M here to enable RTC support on systems using the generic
1380 RTC abstraction. If you do not know what you are doing, you should
1384 tristate "PXA27x/PXA3xx"
1386 select RTC_DRV_SA1100
1388 If you say Y here you will get access to the real time clock
1389 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1390 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1392 This RTC driver uses PXA RTC registers available since pxa27x
1393 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1395 config RTC_DRV_VT8500
1396 tristate "VIA/WonderMedia 85xx SoC RTC"
1397 depends on ARCH_VT8500 || COMPILE_TEST
1399 If you say Y here you will get access to the real time clock
1400 built into your VIA VT8500 SoC or its relatives.
1403 config RTC_DRV_SUN4V
1404 bool "SUN4V Hypervisor RTC"
1407 If you say Y here you will get support for the Hypervisor
1408 based RTC on SUN4V systems.
1410 config RTC_DRV_SUN6I
1411 tristate "Allwinner A31 RTC"
1412 default MACH_SUN6I || MACH_SUN8I || COMPILE_TEST
1413 depends on ARCH_SUNXI
1415 If you say Y here you will get support for the RTC found in
1416 some Allwinner SoCs like the A31 or the A64.
1418 config RTC_DRV_SUNXI
1419 tristate "Allwinner sun4i/sun7i RTC"
1420 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1422 If you say Y here you will get support for the RTC found on
1425 config RTC_DRV_STARFIRE
1429 If you say Y here you will get support for the RTC found on
1432 config RTC_DRV_TX4939
1433 tristate "TX4939 SoC"
1434 depends on SOC_TX4939
1436 Driver for the internal RTC (Realtime Clock) module found on
1440 tristate "Marvell SoC RTC"
1441 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1443 If you say yes here you will get support for the in-chip RTC
1444 that can be found in some of Marvell's SoC devices, such as
1445 the Kirkwood 88F6281 and 88F6192.
1447 This driver can also be built as a module. If so, the module
1448 will be called rtc-mv.
1450 config RTC_DRV_ARMADA38X
1451 tristate "Armada 38x Marvell SoC RTC"
1452 depends on ARCH_MVEBU || COMPILE_TEST
1454 If you say yes here you will get support for the in-chip RTC
1455 that can be found in the Armada 38x Marvell's SoC device
1457 This driver can also be built as a module. If so, the module
1458 will be called armada38x-rtc.
1460 config RTC_DRV_GEMINI
1461 tristate "Gemini SoC RTC"
1462 depends on ARCH_GEMINI || COMPILE_TEST
1463 depends on HAS_IOMEM
1465 If you say Y here you will get support for the
1466 RTC found on Gemini SoC's.
1468 This driver can also be built as a module. If so, the module
1469 will be called rtc-gemini.
1475 If you say yes here you will get support for the RTC on PS3.
1477 This driver can also be built as a module. If so, the module
1478 will be called rtc-ps3.
1480 config RTC_DRV_COH901331
1481 tristate "ST-Ericsson COH 901 331 RTC"
1482 depends on ARCH_U300 || COMPILE_TEST
1484 If you say Y here you will get access to ST-Ericsson
1485 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1488 This driver can also be built as a module. If so, the module
1489 will be called "rtc-coh901331".
1493 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1494 depends on ARCH_MXS || COMPILE_TEST
1497 If you say yes here you will get support for the onboard
1498 STMP3xxx/i.MX23/i.MX28 RTC.
1500 This driver can also be built as a module. If so, the module
1501 will be called rtc-stmp3xxx.
1507 If you say Y here you will get support for the RTC found on
1508 the PCAP2 ASIC used on some Motorola phones.
1510 config RTC_DRV_MC13XXX
1511 depends on MFD_MC13XXX
1512 tristate "Freescale MC13xxx RTC"
1514 This enables support for the RTCs found on Freescale's PMICs
1515 MC13783 and MC13892.
1517 config RTC_DRV_MPC5121
1518 tristate "Freescale MPC5121 built-in RTC"
1519 depends on PPC_MPC512x || PPC_MPC52xx
1521 If you say yes here you will get support for the
1522 built-in RTC on MPC5121 or on MPC5200.
1524 This driver can also be built as a module. If so, the module
1525 will be called rtc-mpc5121.
1527 config RTC_DRV_JZ4740
1528 tristate "Ingenic JZ4740 SoC"
1529 depends on MACH_JZ4740 || COMPILE_TEST
1531 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1534 This driver can also be buillt as a module. If so, the module
1535 will be called rtc-jz4740.
1537 config RTC_DRV_LPC24XX
1538 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1539 depends on ARCH_LPC18XX || COMPILE_TEST
1540 depends on OF && HAS_IOMEM
1542 This enables support for the NXP RTC found which can be found on
1543 NXP LPC178x/18xx/408x/43xx devices.
1545 If you have one of the devices above enable this driver to use
1546 the hardware RTC. This driver can also be buillt as a module. If
1547 so, the module will be called rtc-lpc24xx.
1549 config RTC_DRV_LPC32XX
1550 depends on ARCH_LPC32XX || COMPILE_TEST
1551 tristate "NXP LPC32XX RTC"
1553 This enables support for the NXP RTC in the LPC32XX
1555 This driver can also be buillt as a module. If so, the module
1556 will be called rtc-lpc32xx.
1558 config RTC_DRV_PM8XXX
1559 tristate "Qualcomm PMIC8XXX RTC"
1560 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1562 If you say yes here you get support for the
1563 Qualcomm PMIC8XXX RTC.
1565 To compile this driver as a module, choose M here: the
1566 module will be called rtc-pm8xxx.
1568 config RTC_DRV_TEGRA
1569 tristate "NVIDIA Tegra Internal RTC driver"
1570 depends on ARCH_TEGRA || COMPILE_TEST
1572 If you say yes here you get support for the
1573 Tegra 200 series internal RTC module.
1575 This drive can also be built as a module. If so, the module
1576 will be called rtc-tegra.
1579 tristate "Tilera hypervisor RTC support"
1582 Enable support for the Linux driver side of the Tilera
1583 hypervisor's real-time clock interface.
1586 tristate "PKUnity v3 RTC support"
1587 depends on ARCH_PUV3
1589 This enables support for the RTC in the PKUnity-v3 SoCs.
1591 This drive can also be built as a module. If so, the module
1592 will be called rtc-puv3.
1594 config RTC_DRV_LOONGSON1
1595 tristate "loongson1 RTC support"
1596 depends on MACH_LOONGSON32
1598 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1599 counter) to be used as a RTC.
1601 This driver can also be built as a module. If so, the module
1602 will be called rtc-ls1x.
1605 tristate "Freescale MXC Real Time Clock"
1608 If you say yes here you get support for the Freescale MXC
1611 This driver can also be built as a module, if so, the module
1612 will be called "rtc-mxc".
1615 tristate "Freescale SNVS RTC support"
1617 depends on HAS_IOMEM
1620 If you say yes here you get support for the Freescale SNVS
1621 Low Power (LP) RTC module.
1623 This driver can also be built as a module, if so, the module
1624 will be called "rtc-snvs".
1626 config RTC_DRV_SIRFSOC
1627 tristate "SiRFSOC RTC"
1628 depends on ARCH_SIRF
1630 Say "yes" here to support the real time clock on SiRF SOC chips.
1631 This driver can also be built as a module called rtc-sirfsoc.
1633 config RTC_DRV_ST_LPC
1634 tristate "STMicroelectronics LPC RTC"
1638 Say Y here to include STMicroelectronics Low Power Controller
1639 (LPC) based RTC support.
1641 To compile this driver as a module, choose M here: the
1642 module will be called rtc-st-lpc.
1644 config RTC_DRV_MOXART
1645 tristate "MOXA ART RTC"
1646 depends on ARCH_MOXART || COMPILE_TEST
1648 If you say yes here you get support for the MOXA ART
1651 This driver can also be built as a module. If so, the module
1652 will be called rtc-moxart
1654 config RTC_DRV_MT6397
1655 tristate "Mediatek Real Time Clock driver"
1656 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1658 This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
1659 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1660 Mediatek(R) RTC driver.
1662 If you want to use Mediatek(R) RTC interface, select Y or M here.
1664 config RTC_DRV_XGENE
1665 tristate "APM X-Gene RTC"
1666 depends on HAS_IOMEM
1667 depends on ARCH_XGENE || COMPILE_TEST
1669 If you say yes here you get support for the APM X-Gene SoC real time
1672 This driver can also be built as a module, if so, the module
1673 will be called "rtc-xgene".
1675 config RTC_DRV_PIC32
1676 tristate "Microchip PIC32 RTC"
1677 depends on MACH_PIC32
1680 If you say yes here you get support for the PIC32 RTC module.
1682 This driver can also be built as a module. If so, the module
1683 will be called rtc-pic32
1685 comment "HID Sensor RTC drivers"
1687 config RTC_DRV_HID_SENSOR_TIME
1688 tristate "HID Sensor Time"
1691 select HID_SENSOR_HUB
1692 select HID_SENSOR_IIO_COMMON
1694 Say yes here to build support for the HID Sensors of type Time.
1695 This drivers makes such sensors available as RTCs.
1697 If this driver is compiled as a module, it will be named
1698 rtc-hid-sensor-time.