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"
147 config RTC_DRV_88PM860X
148 tristate "Marvell 88PM860x"
149 depends on MFD_88PM860X
151 If you say yes here you get support for RTC function in Marvell
154 This driver can also be built as a module. If so, the module
155 will be called rtc-88pm860x.
157 config RTC_DRV_88PM80X
158 tristate "Marvell 88PM80x"
159 depends on MFD_88PM800
161 If you say yes here you get support for RTC function in Marvell
164 This driver can also be built as a module. If so, the module
165 will be called rtc-88pm80x.
167 config RTC_DRV_ABB5ZES3
169 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
171 If you say yes here you get support for the Abracon
172 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
174 This driver can also be built as a module. If so, the module
175 will be called rtc-ab-b5ze-s3.
177 config RTC_DRV_ABX80X
178 tristate "Abracon ABx80x"
180 If you say yes here you get support for Abracon AB080X and AB180X
181 families of ultra-low-power battery- and capacitor-backed real-time
184 This driver can also be built as a module. If so, the module
185 will be called rtc-abx80x.
187 config RTC_DRV_AS3722
188 tristate "ams AS3722 RTC driver"
189 depends on MFD_AS3722
191 If you say yes here you get support for the RTC of ams AS3722 PMIC
194 This driver can also be built as a module. If so, the module
195 will be called rtc-as3722.
197 config RTC_DRV_DS1307
198 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
200 If you say yes here you get support for various compatible RTC
201 chips (often with battery backup) connected with I2C. This driver
202 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
203 EPSON RX-8025 and probably other chips. In some cases the RTC
204 must already have been initialized (by manufacturing or a
207 The first seven registers on these chips hold an RTC, and other
208 registers may add features such as NVRAM, a trickle charger for
209 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
210 sysfs, but other chip features may not be available.
212 This driver can also be built as a module. If so, the module
213 will be called rtc-ds1307.
215 config RTC_DRV_DS1374
216 tristate "Dallas/Maxim DS1374"
218 If you say yes here you get support for Dallas Semiconductor
219 DS1374 real-time clock chips. If an interrupt is associated
220 with the device, the alarm functionality is supported.
222 This driver can also be built as a module. If so, the module
223 will be called rtc-ds1374.
225 config RTC_DRV_DS1374_WDT
226 bool "Dallas/Maxim DS1374 watchdog timer"
227 depends on RTC_DRV_DS1374
229 If you say Y here you will get support for the
230 watchdog timer in the Dallas Semiconductor DS1374
231 real-time clock chips.
233 config RTC_DRV_DS1672
234 tristate "Dallas/Maxim DS1672"
236 If you say yes here you get support for the
237 Dallas/Maxim DS1672 timekeeping chip.
239 This driver can also be built as a module. If so, the module
240 will be called rtc-ds1672.
242 config RTC_DRV_DS3232
243 tristate "Dallas/Maxim DS3232"
245 If you say yes here you get support for Dallas Semiconductor
246 DS3232 real-time clock chips. If an interrupt is associated
247 with the device, the alarm functionality is supported.
249 This driver can also be built as a module. If so, the module
250 will be called rtc-ds3232.
252 config RTC_DRV_HYM8563
253 tristate "Haoyu Microelectronics HYM8563"
256 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
257 from the usual rtc functions it provides a clock output of
260 This driver can also be built as a module. If so, the module
261 will be called rtc-hym8563.
263 config RTC_DRV_LP8788
264 tristate "TI LP8788 RTC driver"
265 depends on MFD_LP8788
267 Say Y to enable support for the LP8788 RTC/ALARM driver.
269 config RTC_DRV_MAX6900
270 tristate "Maxim MAX6900"
272 If you say yes here you will get support for the
273 Maxim MAX6900 I2C RTC chip.
275 This driver can also be built as a module. If so, the module
276 will be called rtc-max6900.
278 config RTC_DRV_MAX8907
279 tristate "Maxim MAX8907"
280 depends on MFD_MAX8907
283 If you say yes here you will get support for the
284 RTC of Maxim MAX8907 PMIC.
286 This driver can also be built as a module. If so, the module
287 will be called rtc-max8907.
289 config RTC_DRV_MAX8925
290 tristate "Maxim MAX8925"
291 depends on MFD_MAX8925
293 If you say yes here you will get support for the
294 RTC of Maxim MAX8925 PMIC.
296 This driver can also be built as a module. If so, the module
297 will be called rtc-max8925.
299 config RTC_DRV_MAX8998
300 tristate "Maxim MAX8998"
301 depends on MFD_MAX8998
303 If you say yes here you will get support for the
304 RTC of Maxim MAX8998 PMIC.
306 This driver can also be built as a module. If so, the module
307 will be called rtc-max8998.
309 config RTC_DRV_MAX8997
310 tristate "Maxim MAX8997"
311 depends on MFD_MAX8997
313 If you say yes here you will get support for the
314 RTC of Maxim MAX8997 PMIC.
316 This driver can also be built as a module. If so, the module
317 will be called rtc-max8997.
319 config RTC_DRV_MAX77686
320 tristate "Maxim MAX77686"
321 depends on MFD_MAX77686
323 If you say yes here you will get support for the
324 RTC of Maxim MAX77686 PMIC.
326 This driver can also be built as a module. If so, the module
327 will be called rtc-max77686.
330 tristate "Rockchip RK808 RTC"
333 If you say yes here you will get support for the
336 This driver can also be built as a module. If so, the module
337 will be called rk808-rtc.
339 config RTC_DRV_MAX77802
340 tristate "Maxim 77802 RTC"
341 depends on MFD_MAX77686
343 If you say yes here you will get support for the
344 RTC of Maxim MAX77802 PMIC.
346 This driver can also be built as a module. If so, the module
347 will be called rtc-max77802.
349 config RTC_DRV_RS5C372
350 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
352 If you say yes here you get support for the
353 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
355 This driver can also be built as a module. If so, the module
356 will be called rtc-rs5c372.
358 config RTC_DRV_ISL1208
359 tristate "Intersil ISL1208"
361 If you say yes here you get support for the
362 Intersil ISL1208 RTC chip.
364 This driver can also be built as a module. If so, the module
365 will be called rtc-isl1208.
367 config RTC_DRV_ISL12022
368 tristate "Intersil ISL12022"
370 If you say yes here you get support for the
371 Intersil ISL12022 RTC chip.
373 This driver can also be built as a module. If so, the module
374 will be called rtc-isl12022.
376 config RTC_DRV_ISL12057
378 tristate "Intersil ISL12057"
380 If you say yes here you get support for the Intersil ISL12057
383 This driver can also be built as a module. If so, the module
384 will be called rtc-isl12057.
387 tristate "Xicor/Intersil X1205"
389 If you say yes here you get support for the
390 Xicor/Intersil X1205 RTC chip.
392 This driver can also be built as a module. If so, the module
393 will be called rtc-x1205.
395 config RTC_DRV_PALMAS
396 tristate "TI Palmas RTC driver"
397 depends on MFD_PALMAS
399 If you say yes here you get support for the RTC of TI PALMA series PMIC
402 This driver can also be built as a module. If so, the module
403 will be called rtc-palma.
405 config RTC_DRV_PCF2127
406 tristate "NXP PCF2127"
408 If you say yes here you get support for the NXP PCF2127/29 RTC
411 This driver can also be built as a module. If so, the module
412 will be called rtc-pcf2127.
414 config RTC_DRV_PCF8523
415 tristate "NXP PCF8523"
417 If you say yes here you get support for the NXP PCF8523 RTC
420 This driver can also be built as a module. If so, the module
421 will be called rtc-pcf8523.
423 config RTC_DRV_PCF8563
424 tristate "Philips PCF8563/Epson RTC8564"
426 If you say yes here you get support for the
427 Philips PCF8563 RTC chip. The Epson RTC8564
430 This driver can also be built as a module. If so, the module
431 will be called rtc-pcf8563.
433 config RTC_DRV_PCF85063
434 tristate "nxp PCF85063"
436 If you say yes here you get support for the PCF85063 RTC chip
438 This driver can also be built as a module. If so, the module
439 will be called rtc-pcf85063.
441 config RTC_DRV_PCF8583
442 tristate "Philips PCF8583"
444 If you say yes here you get support for the Philips PCF8583
445 RTC chip found on Acorn RiscPCs. This driver supports the
446 platform specific method of retrieving the current year from
447 the RTC's SRAM. It will work on other platforms with the same
448 chip, but the year will probably have to be tweaked.
450 This driver can also be built as a module. If so, the module
451 will be called rtc-pcf8583.
453 config RTC_DRV_M41T80
454 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
456 If you say Y here you will get support for the ST M41T60
457 and M41T80 RTC chips series. Currently, the following chips are
458 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
459 M41ST85, M41ST87, and MicroCrystal RV4162.
461 This driver can also be built as a module. If so, the module
462 will be called rtc-m41t80.
464 config RTC_DRV_M41T80_WDT
465 bool "ST M41T65/M41T80 series RTC watchdog timer"
466 depends on RTC_DRV_M41T80
468 If you say Y here you will get support for the
469 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
472 tristate "TI BQ32000"
474 If you say Y here you will get support for the TI
475 BQ32000 I2C RTC chip.
477 This driver can also be built as a module. If so, the module
478 will be called rtc-bq32k.
480 config RTC_DRV_DM355EVM
481 tristate "TI DaVinci DM355 EVM RTC"
482 depends on MFD_DM355EVM_MSP
484 Supports the RTC firmware in the MSP430 on the DM355 EVM.
486 config RTC_DRV_TWL92330
487 bool "TI TWL92330/Menelaus"
490 If you say yes here you get support for the RTC on the
491 TWL92330 "Menelaus" power management chip, used with OMAP2
492 platforms. The support is integrated with the rest of
493 the Menelaus driver; it's not separate module.
495 config RTC_DRV_TWL4030
496 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
497 depends on TWL4030_CORE
499 If you say yes here you get support for the RTC on the
500 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
502 This driver can also be built as a module. If so, the module
503 will be called rtc-twl.
505 config RTC_DRV_TPS6586X
506 tristate "TI TPS6586X RTC driver"
507 depends on MFD_TPS6586X
509 TI Power Management IC TPS6586X supports RTC functionality
510 along with alarm. This driver supports the RTC driver for
511 the TPS6586X RTC module.
513 config RTC_DRV_TPS65910
514 tristate "TI TPS65910 RTC driver"
515 depends on RTC_CLASS && MFD_TPS65910
517 If you say yes here you get support for the RTC on the
520 This driver can also be built as a module. If so, the module
521 will be called rtc-tps65910.
523 config RTC_DRV_TPS80031
524 tristate "TI TPS80031/TPS80032 RTC driver"
525 depends on MFD_TPS80031
527 TI Power Management IC TPS80031 supports RTC functionality
528 along with alarm. This driver supports the RTC driver for
529 the TPS80031 RTC module.
531 config RTC_DRV_RC5T583
532 tristate "RICOH 5T583 RTC driver"
533 depends on MFD_RC5T583
535 If you say yes here you get support for the RTC on the
538 This driver can also be built as a module. If so, the module
539 will be called rtc-rc5t583.
541 config RTC_DRV_S35390A
542 tristate "Seiko Instruments S-35390A"
545 If you say yes here you will get support for the Seiko
546 Instruments S-35390A.
548 This driver can also be built as a module. If so the module
549 will be called rtc-s35390a.
551 config RTC_DRV_FM3130
552 tristate "Ramtron FM3130"
554 If you say Y here you will get support for the
555 Ramtron FM3130 RTC chips.
556 Ramtron FM3130 is a chip with two separate devices inside,
557 RTC clock and FRAM. This driver provides only RTC functionality.
559 This driver can also be built as a module. If so the module
560 will be called rtc-fm3130.
562 config RTC_DRV_RX8581
563 tristate "Epson RX-8581"
565 If you say yes here you will get support for the Epson RX-8581.
567 This driver can also be built as a module. If so the module
568 will be called rtc-rx8581.
570 config RTC_DRV_RX8025
571 tristate "Epson RX-8025SA/NB"
573 If you say yes here you get support for the Epson
574 RX-8025SA/NB RTC chips.
576 This driver can also be built as a module. If so, the module
577 will be called rtc-rx8025.
579 config RTC_DRV_EM3027
580 tristate "EM Microelectronic EM3027"
582 If you say yes here you get support for the EM
583 Microelectronic EM3027 RTC chips.
585 This driver can also be built as a module. If so, the module
586 will be called rtc-em3027.
588 config RTC_DRV_RV3029C2
589 tristate "Micro Crystal RTC"
591 If you say yes here you get support for the Micro Crystal
594 This driver can also be built as a module. If so, the module
595 will be called rtc-rv3029c2.
597 config RTC_DRV_RV8803
598 tristate "Micro Crystal RV8803"
600 If you say yes here you get support for the Micro Crystal
603 This driver can also be built as a module. If so, the module
604 will be called rtc-rv8803.
607 tristate "Samsung S2M/S5M series"
608 depends on MFD_SEC_CORE
610 If you say yes here you will get support for the
611 RTC of Samsung S2MPS14 and S5M PMIC series.
613 This driver can also be built as a module. If so, the module
614 will be called rtc-s5m.
618 comment "SPI RTC drivers"
622 config RTC_DRV_M41T93
625 If you say yes here you will get support for the
626 ST M41T93 SPI RTC chip.
628 This driver can also be built as a module. If so, the module
629 will be called rtc-m41t93.
631 config RTC_DRV_M41T94
634 If you say yes here you will get support for the
635 ST M41T94 SPI RTC chip.
637 This driver can also be built as a module. If so, the module
638 will be called rtc-m41t94.
640 config RTC_DRV_DS1305
641 tristate "Dallas/Maxim DS1305/DS1306"
643 Select this driver to get support for the Dallas/Maxim DS1305
644 and DS1306 real time clock chips. These support a trickle
645 charger, alarms, and NVRAM in addition to the clock.
647 This driver can also be built as a module. If so, the module
648 will be called rtc-ds1305.
650 config RTC_DRV_DS1343
652 tristate "Dallas/Maxim DS1343/DS1344"
654 If you say yes here you get support for the
655 Dallas/Maxim DS1343 and DS1344 real time clock chips.
656 Support for trickle charger, alarm is provided.
658 This driver can also be built as a module. If so, the module
659 will be called rtc-ds1343.
661 config RTC_DRV_DS1347
662 tristate "Dallas/Maxim DS1347"
664 If you say yes here you get support for the
665 Dallas/Maxim DS1347 chips.
667 This driver only supports the RTC feature, and not other chip
668 features such as alarms.
670 This driver can also be built as a module. If so, the module
671 will be called rtc-ds1347.
673 config RTC_DRV_DS1390
674 tristate "Dallas/Maxim DS1390/93/94"
676 If you say yes here you get support for the
677 Dallas/Maxim DS1390/93/94 chips.
679 This driver supports the RTC feature and trickle charging but not
680 other chip features such as alarms.
682 This driver can also be built as a module. If so, the module
683 will be called rtc-ds1390.
685 config RTC_DRV_MAX6902
686 tristate "Maxim MAX6902"
688 If you say yes here you will get support for the
689 Maxim MAX6902 SPI RTC chip.
691 This driver can also be built as a module. If so, the module
692 will be called rtc-max6902.
695 tristate "Epson RTC-9701JE"
697 If you say yes here you will get support for the
698 Epson RTC-9701JE SPI RTC chip.
700 This driver can also be built as a module. If so, the module
701 will be called rtc-r9701.
703 config RTC_DRV_RS5C348
704 tristate "Ricoh RS5C348A/B"
706 If you say yes here you get support for the
707 Ricoh RS5C348A and RS5C348B RTC chips.
709 This driver can also be built as a module. If so, the module
710 will be called rtc-rs5c348.
712 config RTC_DRV_DS3234
713 tristate "Maxim/Dallas DS3234"
715 If you say yes here you get support for the
716 Maxim/Dallas DS3234 SPI RTC chip.
718 This driver can also be built as a module. If so, the module
719 will be called rtc-ds3234.
721 config RTC_DRV_PCF2123
722 tristate "NXP PCF2123"
724 If you say yes here you get support for the NXP PCF2123
727 This driver can also be built as a module. If so, the module
728 will be called rtc-pcf2123.
730 config RTC_DRV_RX4581
731 tristate "Epson RX-4581"
733 If you say yes here you will get support for the Epson RX-4581.
735 This driver can also be built as a module. If so the module
736 will be called rtc-rx4581.
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.
748 comment "Platform RTC drivers"
750 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
751 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
752 # global rtc_lock ... it's not yet just another platform_device.
755 tristate "PC-style 'CMOS'"
756 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
759 Say "yes" here to get direct support for the real time clock
760 found in every PC or ACPI-based system, and some other boards.
761 Specifically the original MC146818, compatibles like those in
762 PC south bridges, the DS12887 or M48T86, some multifunction
763 or LPC bus chips, and so on.
765 Your system will need to define the platform device used by
766 this driver, otherwise it won't be accessible. This means
767 you can safely enable this driver if you don't know whether
768 or not your board has this kind of hardware.
770 This driver can also be built as a module. If so, the module
771 will be called rtc-cmos.
774 bool "Alpha PC-style CMOS"
778 Direct support for the real-time clock found on every Alpha
779 system, specifically MC146818 compatibles. If in doubt, say Y.
782 tristate "Virtual RTC for Intel MID platforms"
783 depends on X86_INTEL_MID
784 default y if X86_INTEL_MID
787 Say "yes" here to get direct support for the real time clock
788 found on Moorestown platforms. The VRTC is a emulated RTC that
789 derives its clock source from a real RTC in the PMIC. The MC146818
790 style programming interface is mostly conserved, but any
791 updates are done via IPC calls to the system controller FW.
793 config RTC_DRV_DS1216
794 tristate "Dallas DS1216"
797 If you say yes here you get support for the Dallas DS1216 RTC chips.
799 config RTC_DRV_DS1286
800 tristate "Dallas DS1286"
803 If you say yes here you get support for the Dallas DS1286 RTC chips.
805 config RTC_DRV_DS1302
806 tristate "Dallas DS1302"
807 depends on SH_SECUREEDGE5410
809 If you say yes here you get support for the Dallas DS1302 RTC chips.
811 config RTC_DRV_DS1511
812 tristate "Dallas DS1511"
815 If you say yes here you get support for the
816 Dallas DS1511 timekeeping/watchdog chip.
818 This driver can also be built as a module. If so, the module
819 will be called rtc-ds1511.
821 config RTC_DRV_DS1553
822 tristate "Maxim/Dallas DS1553"
825 If you say yes here you get support for the
826 Maxim/Dallas DS1553 timekeeping chip.
828 This driver can also be built as a module. If so, the module
829 will be called rtc-ds1553.
831 config RTC_DRV_DS1685_FAMILY
832 tristate "Dallas/Maxim DS1685 Family"
834 If you say yes here you get support for the Dallas/Maxim DS1685
835 family of real time chips. This family includes the DS1685/DS1687,
836 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
837 DS17885/DS17887 chips.
839 This driver can also be built as a module. If so, the module
840 will be called rtc-ds1685.
844 depends on RTC_DRV_DS1685_FAMILY
845 default RTC_DRV_DS1685
847 config RTC_DRV_DS1685
850 This enables support for the Dallas/Maxim DS1685/DS1687 real time
853 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
854 systems, as well as EPPC-405-UC modules by electronic system design
857 config RTC_DRV_DS1689
860 This enables support for the Dallas/Maxim DS1689/DS1693 real time
863 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
864 which supports a few minor features such as Vcc, Vbat, and Power
865 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
867 It also works for the even older DS1688/DS1691 RTC chips, which are
868 virtually the same and carry the same model number. Both chips
869 have 114 bytes of user NVRAM.
871 config RTC_DRV_DS17285
872 bool "DS17285/DS17287"
874 This enables support for the Dallas/Maxim DS17285/DS17287 real time
877 This chip features 2kb of extended NV-SRAM. It may possibly be
878 found in some SGI O2 systems (rare).
880 config RTC_DRV_DS17485
881 bool "DS17485/DS17487"
883 This enables support for the Dallas/Maxim DS17485/DS17487 real time
886 This chip features 4kb of extended NV-SRAM.
888 config RTC_DRV_DS17885
889 bool "DS17885/DS17887"
891 This enables support for the Dallas/Maxim DS17885/DS17887 real time
894 This chip features 8kb of extended NV-SRAM.
898 config RTC_DS1685_PROC_REGS
899 bool "Display register values in /proc"
900 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
902 Enable this to display a readout of all of the RTC registers in
903 /proc/drivers/rtc. Keep in mind that this can potentially lead
904 to lost interrupts, as reading Control Register C will clear
905 all pending IRQ flags.
907 Unless you are debugging this driver, choose N.
909 config RTC_DS1685_SYSFS_REGS
910 bool "SysFS access to RTC register bits"
911 depends on RTC_DRV_DS1685_FAMILY && SYSFS
913 Enable this to provide access to the RTC control register bits
914 in /sys. Some of the bits are read-write, others are read-only.
916 Keep in mind that reading Control C's bits automatically clears
917 all pending IRQ flags - this can cause lost interrupts.
919 If you know that you need access to these bits, choose Y, Else N.
921 config RTC_DRV_DS1742
922 tristate "Maxim/Dallas DS1742/1743"
925 If you say yes here you get support for the
926 Maxim/Dallas DS1742/1743 timekeeping chip.
928 This driver can also be built as a module. If so, the module
929 will be called rtc-ds1742.
931 config RTC_DRV_DS2404
932 tristate "Maxim/Dallas DS2404"
934 If you say yes here you get support for the
935 Dallas DS2404 RTC chip.
937 This driver can also be built as a module. If so, the module
938 will be called rtc-ds2404.
940 config RTC_DRV_DA9052
941 tristate "Dialog DA9052/DA9053 RTC"
942 depends on PMIC_DA9052
944 Say y here to support the RTC driver for Dialog Semiconductor
945 DA9052-BC and DA9053-AA/Bx PMICs.
947 config RTC_DRV_DA9055
948 tristate "Dialog Semiconductor DA9055 RTC"
949 depends on MFD_DA9055
951 If you say yes here you will get support for the
952 RTC of the Dialog DA9055 PMIC.
954 This driver can also be built as a module. If so, the module
955 will be called rtc-da9055
957 config RTC_DRV_DA9063
958 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
959 depends on MFD_DA9063 || MFD_DA9062
961 If you say yes here you will get support for the RTC subsystem
962 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
964 This driver can also be built as a module. If so, the module
965 will be called "rtc-da9063".
969 depends on EFI && !X86
971 If you say yes here you will get support for the EFI
974 This driver can also be built as a module. If so, the module
975 will be called rtc-efi.
977 config RTC_DRV_STK17TA8
978 tristate "Simtek STK17TA8"
981 If you say yes here you get support for the
982 Simtek STK17TA8 timekeeping chip.
984 This driver can also be built as a module. If so, the module
985 will be called rtc-stk17ta8.
987 config RTC_DRV_M48T86
988 tristate "ST M48T86/Dallas DS12887"
990 If you say Y here you will get support for the
991 ST M48T86 and Dallas DS12887 RTC chips.
993 This driver can also be built as a module. If so, the module
994 will be called rtc-m48t86.
996 config RTC_DRV_M48T35
1000 If you say Y here you will get support for the
1003 This driver can also be built as a module, if so, the module
1004 will be called "rtc-m48t35".
1006 config RTC_DRV_M48T59
1007 tristate "ST M48T59/M48T08/M48T02"
1008 depends on HAS_IOMEM
1010 If you say Y here you will get support for the
1011 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1013 These chips are usually found in Sun SPARC and UltraSPARC
1016 This driver can also be built as a module, if so, the module
1017 will be called "rtc-m48t59".
1019 config RTC_DRV_MSM6242
1020 tristate "Oki MSM6242"
1021 depends on HAS_IOMEM
1023 If you say yes here you get support for the Oki MSM6242
1024 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1026 This driver can also be built as a module. If so, the module
1027 will be called rtc-msm6242.
1029 config RTC_DRV_BQ4802
1030 tristate "TI BQ4802"
1031 depends on HAS_IOMEM
1033 If you say Y here you will get support for the TI
1036 This driver can also be built as a module. If so, the module
1037 will be called rtc-bq4802.
1039 config RTC_DRV_RP5C01
1040 tristate "Ricoh RP5C01"
1041 depends on HAS_IOMEM
1043 If you say yes here you get support for the Ricoh RP5C01
1044 timekeeping chip. It is used in some Amiga models (e.g. A3000
1047 This driver can also be built as a module. If so, the module
1048 will be called rtc-rp5c01.
1050 config RTC_DRV_V3020
1051 tristate "EM Microelectronic V3020"
1053 If you say yes here you will get support for the
1054 EM Microelectronic v3020 RTC chip.
1056 This driver can also be built as a module. If so, the module
1057 will be called rtc-v3020.
1059 config RTC_DRV_WM831X
1060 tristate "Wolfson Microelectronics WM831x RTC"
1061 depends on MFD_WM831X
1063 If you say yes here you will get support for the RTC subsystem
1064 of the Wolfson Microelectronics WM831X series PMICs.
1066 This driver can also be built as a module. If so, the module
1067 will be called "rtc-wm831x".
1069 config RTC_DRV_WM8350
1070 tristate "Wolfson Microelectronics WM8350 RTC"
1071 depends on MFD_WM8350
1073 If you say yes here you will get support for the RTC subsystem
1074 of the Wolfson Microelectronics WM8350.
1076 This driver can also be built as a module. If so, the module
1077 will be called "rtc-wm8350".
1079 config RTC_DRV_SPEAR
1080 tristate "SPEAR ST RTC"
1081 depends on PLAT_SPEAR
1084 If you say Y here you will get support for the RTC found on
1087 config RTC_DRV_PCF50633
1088 depends on MFD_PCF50633
1089 tristate "NXP PCF50633 RTC"
1091 If you say yes here you get support for the RTC subsystem of the
1092 NXP PCF50633 used in embedded systems.
1094 config RTC_DRV_AB3100
1095 tristate "ST-Ericsson AB3100 RTC"
1096 depends on AB3100_CORE
1097 default y if AB3100_CORE
1099 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1100 support. This chip contains a battery- and capacitor-backed RTC.
1102 config RTC_DRV_AB8500
1103 tristate "ST-Ericsson AB8500 RTC"
1104 depends on AB8500_CORE
1106 select RTC_INTF_DEV_UIE_EMUL
1108 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1109 support. This chip contains a battery- and capacitor-backed RTC.
1111 config RTC_DRV_NUC900
1112 tristate "NUC910/NUC920 RTC driver"
1113 depends on ARCH_W90X900
1115 If you say yes here you get support for the RTC subsystem of the
1116 NUC910/NUC920 used in embedded systems.
1119 tristate "IBM OPAL RTC driver"
1120 depends on PPC_POWERNV
1123 If you say yes here you get support for the PowerNV platform RTC
1124 driver based on OPAL interfaces.
1126 This driver can also be built as a module. If so, the module
1127 will be called rtc-opal.
1129 config RTC_DRV_ZYNQMP
1130 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1133 If you say yes here you get support for the RTC controller found on
1134 Xilinx Zynq Ultrascale+ MPSoC.
1136 comment "on-CPU RTC drivers"
1138 config RTC_DRV_DAVINCI
1139 tristate "TI DaVinci RTC"
1140 depends on ARCH_DAVINCI_DM365
1142 If you say yes here you get support for the RTC on the
1143 DaVinci platforms (DM365).
1145 This driver can also be built as a module. If so, the module
1146 will be called rtc-davinci.
1148 config RTC_DRV_DIGICOLOR
1149 tristate "Conexant Digicolor RTC"
1150 depends on ARCH_DIGICOLOR
1152 If you say yes here you get support for the RTC on Conexant
1153 Digicolor platforms. This currently includes the CX92755 SoC.
1155 This driver can also be built as a module. If so, the module
1156 will be called rtc-digicolor.
1158 config RTC_DRV_IMXDI
1159 tristate "Freescale IMX DryIce Real Time Clock"
1162 Support for Freescale IMX DryIce RTC
1164 This driver can also be built as a module, if so, the module
1165 will be called "rtc-imxdi".
1168 tristate "TI OMAP Real Time Clock"
1169 depends on ARCH_OMAP || ARCH_DAVINCI
1171 Say "yes" here to support the on chip real time clock
1172 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1174 This driver can also be built as a module, if so, module
1175 will be called rtc-omap.
1180 This will include RTC support for Samsung SoCs. If
1181 you want to include RTC support for any machine, kindly
1182 select this in the respective mach-XXXX/Kconfig file.
1185 tristate "Samsung S3C series SoC RTC"
1186 depends on ARCH_S3C64XX || HAVE_S3C_RTC
1188 RTC (Realtime Clock) driver for the clock inbuilt into the
1189 Samsung S3C24XX series of SoCs. This can provide periodic
1190 interrupt rates from 1Hz to 64Hz for user programs, and
1193 The driver currently supports the common features on all the
1194 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1197 This driver can also be build as a module. If so, the module
1198 will be called rtc-s3c.
1200 config RTC_DRV_EP93XX
1201 tristate "Cirrus Logic EP93XX"
1202 depends on ARCH_EP93XX
1204 If you say yes here you get support for the
1205 RTC embedded in the Cirrus Logic EP93XX processors.
1207 This driver can also be built as a module. If so, the module
1208 will be called rtc-ep93xx.
1210 config RTC_DRV_SA1100
1211 tristate "SA11x0/PXA2xx/PXA910"
1212 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1214 If you say Y here you will get access to the real time clock
1215 built into your SA11x0 or PXA2xx CPU.
1217 To compile this driver as a module, choose M here: the
1218 module will be called rtc-sa1100.
1221 tristate "SuperH On-Chip RTC"
1222 depends on SUPERH && HAVE_CLK
1224 Say Y here to enable support for the on-chip RTC found in
1225 most SuperH processors.
1227 To compile this driver as a module, choose M here: the
1228 module will be called rtc-sh.
1230 config RTC_DRV_VR41XX
1231 tristate "NEC VR41XX"
1232 depends on CPU_VR41XX
1234 If you say Y here you will get access to the real time clock
1235 built into your NEC VR41XX CPU.
1237 To compile this driver as a module, choose M here: the
1238 module will be called rtc-vr41xx.
1240 config RTC_DRV_PL030
1241 tristate "ARM AMBA PL030 RTC"
1244 If you say Y here you will get access to ARM AMBA
1245 PrimeCell PL030 RTC found on certain ARM SOCs.
1247 To compile this driver as a module, choose M here: the
1248 module will be called rtc-pl030.
1250 config RTC_DRV_PL031
1251 tristate "ARM AMBA PL031 RTC"
1254 If you say Y here you will get access to ARM AMBA
1255 PrimeCell PL031 RTC found on certain ARM SOCs.
1257 To compile this driver as a module, choose M here: the
1258 module will be called rtc-pl031.
1260 config RTC_DRV_AT32AP700X
1261 tristate "AT32AP700X series RTC"
1262 depends on PLATFORM_AT32AP
1264 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1265 AT32AP700x family processors.
1267 config RTC_DRV_AT91RM9200
1268 tristate "AT91RM9200 or some AT91SAM9 RTC"
1269 depends on ARCH_AT91
1271 Driver for the internal RTC (Realtime Clock) module found on
1272 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1273 this is powered by the backup power supply.
1275 config RTC_DRV_AT91SAM9
1276 tristate "AT91SAM9 RTT as RTC"
1277 depends on ARCH_AT91
1280 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1281 can be used as an RTC thanks to the backup power supply (e.g. a
1282 small coin cell battery) which keeps this block and the GPBR
1283 (General Purpose Backup Registers) block powered when the device
1285 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1286 probably want to use the real RTC block instead of the "RTT as an
1289 config RTC_DRV_AU1XXX
1290 tristate "Au1xxx Counter0 RTC support"
1291 depends on MIPS_ALCHEMY
1293 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1294 counter) to be used as a RTC.
1296 This driver can also be built as a module. If so, the module
1297 will be called rtc-au1xxx.
1300 tristate "Blackfin On-Chip RTC"
1301 depends on BLACKFIN && !BF561
1303 If you say yes here you will get support for the
1304 Blackfin On-Chip Real Time Clock.
1306 This driver can also be built as a module. If so, the module
1307 will be called rtc-bfin.
1309 config RTC_DRV_RS5C313
1310 tristate "Ricoh RS5C313"
1311 depends on SH_LANDISK
1313 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1315 config RTC_DRV_GENERIC
1316 tristate "Generic RTC support"
1317 # Please consider writing a new RTC driver instead of using the generic
1319 depends on PARISC || M68K || PPC || SUPERH32
1321 Say Y or M here to enable RTC support on systems using the generic
1322 RTC abstraction. If you do not know what you are doing, you should
1326 tristate "PXA27x/PXA3xx"
1328 select RTC_DRV_SA1100
1330 If you say Y here you will get access to the real time clock
1331 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1332 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1334 This RTC driver uses PXA RTC registers available since pxa27x
1335 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1337 config RTC_DRV_VT8500
1338 tristate "VIA/WonderMedia 85xx SoC RTC"
1339 depends on ARCH_VT8500
1341 If you say Y here you will get access to the real time clock
1342 built into your VIA VT8500 SoC or its relatives.
1345 config RTC_DRV_SUN4V
1346 bool "SUN4V Hypervisor RTC"
1349 If you say Y here you will get support for the Hypervisor
1350 based RTC on SUN4V systems.
1352 config RTC_DRV_SUN6I
1353 tristate "Allwinner A31 RTC"
1354 depends on MACH_SUN6I || MACH_SUN8I
1356 If you say Y here you will get support for the RTC found on
1359 config RTC_DRV_SUNXI
1360 tristate "Allwinner sun4i/sun7i RTC"
1361 depends on MACH_SUN4I || MACH_SUN7I
1363 If you say Y here you will get support for the RTC found on
1366 config RTC_DRV_STARFIRE
1370 If you say Y here you will get support for the RTC found on
1373 config RTC_DRV_TX4939
1374 tristate "TX4939 SoC"
1375 depends on SOC_TX4939
1377 Driver for the internal RTC (Realtime Clock) module found on
1381 tristate "Marvell SoC RTC"
1382 depends on ARCH_DOVE || ARCH_MVEBU
1384 If you say yes here you will get support for the in-chip RTC
1385 that can be found in some of Marvell's SoC devices, such as
1386 the Kirkwood 88F6281 and 88F6192.
1388 This driver can also be built as a module. If so, the module
1389 will be called rtc-mv.
1391 config RTC_DRV_ARMADA38X
1392 tristate "Armada 38x Marvell SoC RTC"
1393 depends on ARCH_MVEBU
1395 If you say yes here you will get support for the in-chip RTC
1396 that can be found in the Armada 38x Marvell's SoC device
1398 This driver can also be built as a module. If so, the module
1399 will be called armada38x-rtc.
1401 config RTC_DRV_GEMINI
1402 tristate "Gemini SoC RTC"
1403 depends on ARCH_GEMINI || COMPILE_TEST
1404 depends on HAS_IOMEM
1406 If you say Y here you will get support for the
1407 RTC found on Gemini SoC's.
1409 This driver can also be built as a module. If so, the module
1410 will be called rtc-gemini.
1416 If you say yes here you will get support for the RTC on PS3.
1418 This driver can also be built as a module. If so, the module
1419 will be called rtc-ps3.
1421 config RTC_DRV_COH901331
1422 tristate "ST-Ericsson COH 901 331 RTC"
1423 depends on ARCH_U300
1425 If you say Y here you will get access to ST-Ericsson
1426 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1429 This driver can also be built as a module. If so, the module
1430 will be called "rtc-coh901331".
1434 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1438 If you say yes here you will get support for the onboard
1439 STMP3xxx/i.MX23/i.MX28 RTC.
1441 This driver can also be built as a module. If so, the module
1442 will be called rtc-stmp3xxx.
1448 If you say Y here you will get support for the RTC found on
1449 the PCAP2 ASIC used on some Motorola phones.
1451 config RTC_DRV_MC13XXX
1452 depends on MFD_MC13XXX
1453 tristate "Freescale MC13xxx RTC"
1455 This enables support for the RTCs found on Freescale's PMICs
1456 MC13783 and MC13892.
1458 config RTC_DRV_MPC5121
1459 tristate "Freescale MPC5121 built-in RTC"
1460 depends on PPC_MPC512x || PPC_MPC52xx
1462 If you say yes here you will get support for the
1463 built-in RTC on MPC5121 or on MPC5200.
1465 This driver can also be built as a module. If so, the module
1466 will be called rtc-mpc5121.
1468 config RTC_DRV_JZ4740
1469 tristate "Ingenic JZ4740 SoC"
1470 depends on MACH_JZ4740
1472 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1475 This driver can also be buillt as a module. If so, the module
1476 will be called rtc-jz4740.
1478 config RTC_DRV_LPC24XX
1479 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1480 depends on ARCH_LPC18XX || COMPILE_TEST
1481 depends on OF && HAS_IOMEM
1483 This enables support for the NXP RTC found which can be found on
1484 NXP LPC178x/18xx/408x/43xx devices.
1486 If you have one of the devices above enable this driver to use
1487 the hardware RTC. This driver can also be buillt as a module. If
1488 so, the module will be called rtc-lpc24xx.
1490 config RTC_DRV_LPC32XX
1491 depends on ARCH_LPC32XX
1492 tristate "NXP LPC32XX RTC"
1494 This enables support for the NXP RTC in the LPC32XX
1496 This driver can also be buillt as a module. If so, the module
1497 will be called rtc-lpc32xx.
1499 config RTC_DRV_PM8XXX
1500 tristate "Qualcomm PMIC8XXX RTC"
1501 depends on MFD_PM8XXX || MFD_SPMI_PMIC
1503 If you say yes here you get support for the
1504 Qualcomm PMIC8XXX RTC.
1506 To compile this driver as a module, choose M here: the
1507 module will be called rtc-pm8xxx.
1509 config RTC_DRV_TEGRA
1510 tristate "NVIDIA Tegra Internal RTC driver"
1511 depends on ARCH_TEGRA
1513 If you say yes here you get support for the
1514 Tegra 200 series internal RTC module.
1516 This drive can also be built as a module. If so, the module
1517 will be called rtc-tegra.
1520 tristate "Tilera hypervisor RTC support"
1523 Enable support for the Linux driver side of the Tilera
1524 hypervisor's real-time clock interface.
1527 tristate "PKUnity v3 RTC support"
1528 depends on ARCH_PUV3
1530 This enables support for the RTC in the PKUnity-v3 SoCs.
1532 This drive can also be built as a module. If so, the module
1533 will be called rtc-puv3.
1535 config RTC_DRV_LOONGSON1
1536 tristate "loongson1 RTC support"
1537 depends on MACH_LOONGSON32
1539 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1540 counter) to be used as a RTC.
1542 This driver can also be built as a module. If so, the module
1543 will be called rtc-ls1x.
1546 tristate "Freescale MXC Real Time Clock"
1549 If you say yes here you get support for the Freescale MXC
1552 This driver can also be built as a module, if so, the module
1553 will be called "rtc-mxc".
1556 tristate "Freescale SNVS RTC support"
1558 depends on HAS_IOMEM
1561 If you say yes here you get support for the Freescale SNVS
1562 Low Power (LP) RTC module.
1564 This driver can also be built as a module, if so, the module
1565 will be called "rtc-snvs".
1567 config RTC_DRV_SIRFSOC
1568 tristate "SiRFSOC RTC"
1569 depends on ARCH_SIRF
1571 Say "yes" here to support the real time clock on SiRF SOC chips.
1572 This driver can also be built as a module called rtc-sirfsoc.
1574 config RTC_DRV_ST_LPC
1575 tristate "STMicroelectronics LPC RTC"
1579 Say Y here to include STMicroelectronics Low Power Controller
1580 (LPC) based RTC support.
1582 To compile this driver as a module, choose M here: the
1583 module will be called rtc-st-lpc.
1585 config RTC_DRV_MOXART
1586 tristate "MOXA ART RTC"
1587 depends on ARCH_MOXART || COMPILE_TEST
1589 If you say yes here you get support for the MOXA ART
1592 This driver can also be built as a module. If so, the module
1593 will be called rtc-moxart
1595 config RTC_DRV_MT6397
1596 tristate "Mediatek Real Time Clock driver"
1597 depends on MFD_MT6397 || COMPILE_TEST
1599 This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
1600 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1601 Mediatek(R) RTC driver.
1603 If you want to use Mediatek(R) RTC interface, select Y or M here.
1605 config RTC_DRV_XGENE
1606 tristate "APM X-Gene RTC"
1607 depends on HAS_IOMEM
1608 depends on ARCH_XGENE || COMPILE_TEST
1610 If you say yes here you get support for the APM X-Gene SoC real time
1613 This driver can also be built as a module, if so, the module
1614 will be called "rtc-xgene".
1616 comment "HID Sensor RTC drivers"
1618 config RTC_DRV_HID_SENSOR_TIME
1619 tristate "HID Sensor Time"
1622 select HID_SENSOR_HUB
1623 select HID_SENSOR_IIO_COMMON
1625 Say yes here to build support for the HID Sensors of type Time.
1626 This drivers makes such sensors available as RTCs.
1628 If this driver is compiled as a module, it will be named
1629 rtc-hid-sensor-time.