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
282 If you say yes here you will get support for the
283 RTC of Maxim MAX8907 PMIC.
285 This driver can also be built as a module. If so, the module
286 will be called rtc-max8907.
288 config RTC_DRV_MAX8925
289 tristate "Maxim MAX8925"
290 depends on MFD_MAX8925
292 If you say yes here you will get support for the
293 RTC of Maxim MAX8925 PMIC.
295 This driver can also be built as a module. If so, the module
296 will be called rtc-max8925.
298 config RTC_DRV_MAX8998
299 tristate "Maxim MAX8998"
300 depends on MFD_MAX8998
302 If you say yes here you will get support for the
303 RTC of Maxim MAX8998 PMIC.
305 This driver can also be built as a module. If so, the module
306 will be called rtc-max8998.
308 config RTC_DRV_MAX8997
309 tristate "Maxim MAX8997"
310 depends on MFD_MAX8997
312 If you say yes here you will get support for the
313 RTC of Maxim MAX8997 PMIC.
315 This driver can also be built as a module. If so, the module
316 will be called rtc-max8997.
318 config RTC_DRV_MAX77686
319 tristate "Maxim MAX77686"
320 depends on MFD_MAX77686
322 If you say yes here you will get support for the
323 RTC of Maxim MAX77686 PMIC.
325 This driver can also be built as a module. If so, the module
326 will be called rtc-max77686.
329 tristate "Rockchip RK808 RTC"
332 If you say yes here you will get support for the
335 This driver can also be built as a module. If so, the module
336 will be called rk808-rtc.
338 config RTC_DRV_MAX77802
339 tristate "Maxim 77802 RTC"
340 depends on MFD_MAX77686
342 If you say yes here you will get support for the
343 RTC of Maxim MAX77802 PMIC.
345 This driver can also be built as a module. If so, the module
346 will be called rtc-max77802.
348 config RTC_DRV_RS5C372
349 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
351 If you say yes here you get support for the
352 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
354 This driver can also be built as a module. If so, the module
355 will be called rtc-rs5c372.
357 config RTC_DRV_ISL1208
358 tristate "Intersil ISL1208"
360 If you say yes here you get support for the
361 Intersil ISL1208 RTC chip.
363 This driver can also be built as a module. If so, the module
364 will be called rtc-isl1208.
366 config RTC_DRV_ISL12022
367 tristate "Intersil ISL12022"
369 If you say yes here you get support for the
370 Intersil ISL12022 RTC chip.
372 This driver can also be built as a module. If so, the module
373 will be called rtc-isl12022.
375 config RTC_DRV_ISL12057
377 tristate "Intersil ISL12057"
379 If you say yes here you get support for the Intersil ISL12057
382 This driver can also be built as a module. If so, the module
383 will be called rtc-isl12057.
386 tristate "Xicor/Intersil X1205"
388 If you say yes here you get support for the
389 Xicor/Intersil X1205 RTC chip.
391 This driver can also be built as a module. If so, the module
392 will be called rtc-x1205.
394 config RTC_DRV_PALMAS
395 tristate "TI Palmas RTC driver"
396 depends on MFD_PALMAS
398 If you say yes here you get support for the RTC of TI PALMA series PMIC
401 This driver can also be built as a module. If so, the module
402 will be called rtc-palma.
404 config RTC_DRV_PCF2127
405 tristate "NXP PCF2127"
407 If you say yes here you get support for the NXP PCF2127/29 RTC
410 This driver can also be built as a module. If so, the module
411 will be called rtc-pcf2127.
413 config RTC_DRV_PCF8523
414 tristate "NXP PCF8523"
416 If you say yes here you get support for the NXP PCF8523 RTC
419 This driver can also be built as a module. If so, the module
420 will be called rtc-pcf8523.
422 config RTC_DRV_PCF8563
423 tristate "Philips PCF8563/Epson RTC8564"
425 If you say yes here you get support for the
426 Philips PCF8563 RTC chip. The Epson RTC8564
429 This driver can also be built as a module. If so, the module
430 will be called rtc-pcf8563.
432 config RTC_DRV_PCF85063
433 tristate "nxp PCF85063"
435 If you say yes here you get support for the PCF85063 RTC chip
437 This driver can also be built as a module. If so, the module
438 will be called rtc-pcf85063.
440 config RTC_DRV_PCF8583
441 tristate "Philips PCF8583"
443 If you say yes here you get support for the Philips PCF8583
444 RTC chip found on Acorn RiscPCs. This driver supports the
445 platform specific method of retrieving the current year from
446 the RTC's SRAM. It will work on other platforms with the same
447 chip, but the year will probably have to be tweaked.
449 This driver can also be built as a module. If so, the module
450 will be called rtc-pcf8583.
452 config RTC_DRV_M41T80
453 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
455 If you say Y here you will get support for the ST M41T60
456 and M41T80 RTC chips series. Currently, the following chips are
457 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
458 M41ST85, M41ST87, and MicroCrystal RV4162.
460 This driver can also be built as a module. If so, the module
461 will be called rtc-m41t80.
463 config RTC_DRV_M41T80_WDT
464 bool "ST M41T65/M41T80 series RTC watchdog timer"
465 depends on RTC_DRV_M41T80
467 If you say Y here you will get support for the
468 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
471 tristate "TI BQ32000"
473 If you say Y here you will get support for the TI
474 BQ32000 I2C RTC chip.
476 This driver can also be built as a module. If so, the module
477 will be called rtc-bq32k.
479 config RTC_DRV_DM355EVM
480 tristate "TI DaVinci DM355 EVM RTC"
481 depends on MFD_DM355EVM_MSP
483 Supports the RTC firmware in the MSP430 on the DM355 EVM.
485 config RTC_DRV_TWL92330
486 bool "TI TWL92330/Menelaus"
489 If you say yes here you get support for the RTC on the
490 TWL92330 "Menelaus" power management chip, used with OMAP2
491 platforms. The support is integrated with the rest of
492 the Menelaus driver; it's not separate module.
494 config RTC_DRV_TWL4030
495 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
496 depends on TWL4030_CORE
498 If you say yes here you get support for the RTC on the
499 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
501 This driver can also be built as a module. If so, the module
502 will be called rtc-twl.
504 config RTC_DRV_TPS6586X
505 tristate "TI TPS6586X RTC driver"
506 depends on MFD_TPS6586X
508 TI Power Management IC TPS6586X supports RTC functionality
509 along with alarm. This driver supports the RTC driver for
510 the TPS6586X RTC module.
512 config RTC_DRV_TPS65910
513 tristate "TI TPS65910 RTC driver"
514 depends on RTC_CLASS && MFD_TPS65910
516 If you say yes here you get support for the RTC on the
519 This driver can also be built as a module. If so, the module
520 will be called rtc-tps65910.
522 config RTC_DRV_TPS80031
523 tristate "TI TPS80031/TPS80032 RTC driver"
524 depends on MFD_TPS80031
526 TI Power Management IC TPS80031 supports RTC functionality
527 along with alarm. This driver supports the RTC driver for
528 the TPS80031 RTC module.
530 config RTC_DRV_RC5T583
531 tristate "RICOH 5T583 RTC driver"
532 depends on MFD_RC5T583
534 If you say yes here you get support for the RTC on the
537 This driver can also be built as a module. If so, the module
538 will be called rtc-rc5t583.
540 config RTC_DRV_S35390A
541 tristate "Seiko Instruments S-35390A"
544 If you say yes here you will get support for the Seiko
545 Instruments S-35390A.
547 This driver can also be built as a module. If so the module
548 will be called rtc-s35390a.
550 config RTC_DRV_FM3130
551 tristate "Ramtron FM3130"
553 If you say Y here you will get support for the
554 Ramtron FM3130 RTC chips.
555 Ramtron FM3130 is a chip with two separate devices inside,
556 RTC clock and FRAM. This driver provides only RTC functionality.
558 This driver can also be built as a module. If so the module
559 will be called rtc-fm3130.
561 config RTC_DRV_RX8581
562 tristate "Epson RX-8581"
564 If you say yes here you will get support for the Epson RX-8581.
566 This driver can also be built as a module. If so the module
567 will be called rtc-rx8581.
569 config RTC_DRV_RX8025
570 tristate "Epson RX-8025SA/NB"
572 If you say yes here you get support for the Epson
573 RX-8025SA/NB RTC chips.
575 This driver can also be built as a module. If so, the module
576 will be called rtc-rx8025.
578 config RTC_DRV_EM3027
579 tristate "EM Microelectronic EM3027"
581 If you say yes here you get support for the EM
582 Microelectronic EM3027 RTC chips.
584 This driver can also be built as a module. If so, the module
585 will be called rtc-em3027.
587 config RTC_DRV_RV3029C2
588 tristate "Micro Crystal RTC"
590 If you say yes here you get support for the Micro Crystal
593 This driver can also be built as a module. If so, the module
594 will be called rtc-rv3029c2.
597 tristate "Samsung S2M/S5M series"
598 depends on MFD_SEC_CORE
600 If you say yes here you will get support for the
601 RTC of Samsung S2MPS14 and S5M PMIC series.
603 This driver can also be built as a module. If so, the module
604 will be called rtc-s5m.
608 comment "SPI RTC drivers"
612 config RTC_DRV_M41T93
615 If you say yes here you will get support for the
616 ST M41T93 SPI RTC chip.
618 This driver can also be built as a module. If so, the module
619 will be called rtc-m41t93.
621 config RTC_DRV_M41T94
624 If you say yes here you will get support for the
625 ST M41T94 SPI RTC chip.
627 This driver can also be built as a module. If so, the module
628 will be called rtc-m41t94.
630 config RTC_DRV_DS1305
631 tristate "Dallas/Maxim DS1305/DS1306"
633 Select this driver to get support for the Dallas/Maxim DS1305
634 and DS1306 real time clock chips. These support a trickle
635 charger, alarms, and NVRAM in addition to the clock.
637 This driver can also be built as a module. If so, the module
638 will be called rtc-ds1305.
640 config RTC_DRV_DS1343
642 tristate "Dallas/Maxim DS1343/DS1344"
644 If you say yes here you get support for the
645 Dallas/Maxim DS1343 and DS1344 real time clock chips.
646 Support for trickle charger, alarm is provided.
648 This driver can also be built as a module. If so, the module
649 will be called rtc-ds1343.
651 config RTC_DRV_DS1347
652 tristate "Dallas/Maxim DS1347"
654 If you say yes here you get support for the
655 Dallas/Maxim DS1347 chips.
657 This driver only supports the RTC feature, and not other chip
658 features such as alarms.
660 This driver can also be built as a module. If so, the module
661 will be called rtc-ds1347.
663 config RTC_DRV_DS1390
664 tristate "Dallas/Maxim DS1390/93/94"
666 If you say yes here you get support for the
667 Dallas/Maxim DS1390/93/94 chips.
669 This driver only supports the RTC feature, and not other chip
670 features such as alarms and trickle charging.
672 This driver can also be built as a module. If so, the module
673 will be called rtc-ds1390.
675 config RTC_DRV_MAX6902
676 tristate "Maxim MAX6902"
678 If you say yes here you will get support for the
679 Maxim MAX6902 SPI RTC chip.
681 This driver can also be built as a module. If so, the module
682 will be called rtc-max6902.
685 tristate "Epson RTC-9701JE"
687 If you say yes here you will get support for the
688 Epson RTC-9701JE SPI RTC chip.
690 This driver can also be built as a module. If so, the module
691 will be called rtc-r9701.
693 config RTC_DRV_RS5C348
694 tristate "Ricoh RS5C348A/B"
696 If you say yes here you get support for the
697 Ricoh RS5C348A and RS5C348B RTC chips.
699 This driver can also be built as a module. If so, the module
700 will be called rtc-rs5c348.
702 config RTC_DRV_DS3234
703 tristate "Maxim/Dallas DS3234"
705 If you say yes here you get support for the
706 Maxim/Dallas DS3234 SPI RTC chip.
708 This driver can also be built as a module. If so, the module
709 will be called rtc-ds3234.
711 config RTC_DRV_PCF2123
712 tristate "NXP PCF2123"
714 If you say yes here you get support for the NXP PCF2123
717 This driver can also be built as a module. If so, the module
718 will be called rtc-pcf2123.
720 config RTC_DRV_RX4581
721 tristate "Epson RX-4581"
723 If you say yes here you will get support for the Epson RX-4581.
725 This driver can also be built as a module. If so the module
726 will be called rtc-rx4581.
728 config RTC_DRV_MCP795
729 tristate "Microchip MCP795"
731 If you say yes here you will get support for the Microchip MCP795.
733 This driver can also be built as a module. If so the module
734 will be called rtc-mcp795.
738 comment "Platform RTC drivers"
740 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
741 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
742 # global rtc_lock ... it's not yet just another platform_device.
745 tristate "PC-style 'CMOS'"
746 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
749 Say "yes" here to get direct support for the real time clock
750 found in every PC or ACPI-based system, and some other boards.
751 Specifically the original MC146818, compatibles like those in
752 PC south bridges, the DS12887 or M48T86, some multifunction
753 or LPC bus chips, and so on.
755 Your system will need to define the platform device used by
756 this driver, otherwise it won't be accessible. This means
757 you can safely enable this driver if you don't know whether
758 or not your board has this kind of hardware.
760 This driver can also be built as a module. If so, the module
761 will be called rtc-cmos.
764 bool "Alpha PC-style CMOS"
768 Direct support for the real-time clock found on every Alpha
769 system, specifically MC146818 compatibles. If in doubt, say Y.
772 tristate "Virtual RTC for Intel MID platforms"
773 depends on X86_INTEL_MID
774 default y if X86_INTEL_MID
777 Say "yes" here to get direct support for the real time clock
778 found on Moorestown platforms. The VRTC is a emulated RTC that
779 derives its clock source from a real RTC in the PMIC. The MC146818
780 style programming interface is mostly conserved, but any
781 updates are done via IPC calls to the system controller FW.
783 config RTC_DRV_DS1216
784 tristate "Dallas DS1216"
787 If you say yes here you get support for the Dallas DS1216 RTC chips.
789 config RTC_DRV_DS1286
790 tristate "Dallas DS1286"
793 If you say yes here you get support for the Dallas DS1286 RTC chips.
795 config RTC_DRV_DS1302
796 tristate "Dallas DS1302"
797 depends on SH_SECUREEDGE5410
799 If you say yes here you get support for the Dallas DS1302 RTC chips.
801 config RTC_DRV_DS1511
802 tristate "Dallas DS1511"
805 If you say yes here you get support for the
806 Dallas DS1511 timekeeping/watchdog chip.
808 This driver can also be built as a module. If so, the module
809 will be called rtc-ds1511.
811 config RTC_DRV_DS1553
812 tristate "Maxim/Dallas DS1553"
815 If you say yes here you get support for the
816 Maxim/Dallas DS1553 timekeeping chip.
818 This driver can also be built as a module. If so, the module
819 will be called rtc-ds1553.
821 config RTC_DRV_DS1685_FAMILY
822 tristate "Dallas/Maxim DS1685 Family"
824 If you say yes here you get support for the Dallas/Maxim DS1685
825 family of real time chips. This family includes the DS1685/DS1687,
826 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
827 DS17885/DS17887 chips.
829 This driver can also be built as a module. If so, the module
830 will be called rtc-ds1685.
834 depends on RTC_DRV_DS1685_FAMILY
835 default RTC_DRV_DS1685
837 config RTC_DRV_DS1685
840 This enables support for the Dallas/Maxim DS1685/DS1687 real time
843 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
844 systems, as well as EPPC-405-UC modules by electronic system design
847 config RTC_DRV_DS1689
850 This enables support for the Dallas/Maxim DS1689/DS1693 real time
853 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
854 which supports a few minor features such as Vcc, Vbat, and Power
855 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
857 It also works for the even older DS1688/DS1691 RTC chips, which are
858 virtually the same and carry the same model number. Both chips
859 have 114 bytes of user NVRAM.
861 config RTC_DRV_DS17285
862 bool "DS17285/DS17287"
864 This enables support for the Dallas/Maxim DS17285/DS17287 real time
867 This chip features 2kb of extended NV-SRAM. It may possibly be
868 found in some SGI O2 systems (rare).
870 config RTC_DRV_DS17485
871 bool "DS17485/DS17487"
873 This enables support for the Dallas/Maxim DS17485/DS17487 real time
876 This chip features 4kb of extended NV-SRAM.
878 config RTC_DRV_DS17885
879 bool "DS17885/DS17887"
881 This enables support for the Dallas/Maxim DS17885/DS17887 real time
884 This chip features 8kb of extended NV-SRAM.
888 config RTC_DS1685_PROC_REGS
889 bool "Display register values in /proc"
890 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
892 Enable this to display a readout of all of the RTC registers in
893 /proc/drivers/rtc. Keep in mind that this can potentially lead
894 to lost interrupts, as reading Control Register C will clear
895 all pending IRQ flags.
897 Unless you are debugging this driver, choose N.
899 config RTC_DS1685_SYSFS_REGS
900 bool "SysFS access to RTC register bits"
901 depends on RTC_DRV_DS1685_FAMILY && SYSFS
903 Enable this to provide access to the RTC control register bits
904 in /sys. Some of the bits are read-write, others are read-only.
906 Keep in mind that reading Control C's bits automatically clears
907 all pending IRQ flags - this can cause lost interrupts.
909 If you know that you need access to these bits, choose Y, Else N.
911 config RTC_DRV_DS1742
912 tristate "Maxim/Dallas DS1742/1743"
915 If you say yes here you get support for the
916 Maxim/Dallas DS1742/1743 timekeeping chip.
918 This driver can also be built as a module. If so, the module
919 will be called rtc-ds1742.
921 config RTC_DRV_DS2404
922 tristate "Maxim/Dallas DS2404"
924 If you say yes here you get support for the
925 Dallas DS2404 RTC chip.
927 This driver can also be built as a module. If so, the module
928 will be called rtc-ds2404.
930 config RTC_DRV_DA9052
931 tristate "Dialog DA9052/DA9053 RTC"
932 depends on PMIC_DA9052
934 Say y here to support the RTC driver for Dialog Semiconductor
935 DA9052-BC and DA9053-AA/Bx PMICs.
937 config RTC_DRV_DA9055
938 tristate "Dialog Semiconductor DA9055 RTC"
939 depends on MFD_DA9055
941 If you say yes here you will get support for the
942 RTC of the Dialog DA9055 PMIC.
944 This driver can also be built as a module. If so, the module
945 will be called rtc-da9055
947 config RTC_DRV_DA9063
948 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
949 depends on MFD_DA9063 || MFD_DA9062
951 If you say yes here you will get support for the RTC subsystem
952 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
954 This driver can also be built as a module. If so, the module
955 will be called "rtc-da9063".
959 depends on EFI && !X86
961 If you say yes here you will get support for the EFI
964 This driver can also be built as a module. If so, the module
965 will be called rtc-efi.
967 config RTC_DRV_STK17TA8
968 tristate "Simtek STK17TA8"
971 If you say yes here you get support for the
972 Simtek STK17TA8 timekeeping chip.
974 This driver can also be built as a module. If so, the module
975 will be called rtc-stk17ta8.
977 config RTC_DRV_M48T86
978 tristate "ST M48T86/Dallas DS12887"
980 If you say Y here you will get support for the
981 ST M48T86 and Dallas DS12887 RTC chips.
983 This driver can also be built as a module. If so, the module
984 will be called rtc-m48t86.
986 config RTC_DRV_M48T35
990 If you say Y here you will get support for the
993 This driver can also be built as a module, if so, the module
994 will be called "rtc-m48t35".
996 config RTC_DRV_M48T59
997 tristate "ST M48T59/M48T08/M48T02"
1000 If you say Y here you will get support for the
1001 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1003 These chips are usually found in Sun SPARC and UltraSPARC
1006 This driver can also be built as a module, if so, the module
1007 will be called "rtc-m48t59".
1009 config RTC_DRV_MSM6242
1010 tristate "Oki MSM6242"
1011 depends on HAS_IOMEM
1013 If you say yes here you get support for the Oki MSM6242
1014 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1016 This driver can also be built as a module. If so, the module
1017 will be called rtc-msm6242.
1019 config RTC_DRV_BQ4802
1020 tristate "TI BQ4802"
1021 depends on HAS_IOMEM
1023 If you say Y here you will get support for the TI
1026 This driver can also be built as a module. If so, the module
1027 will be called rtc-bq4802.
1029 config RTC_DRV_RP5C01
1030 tristate "Ricoh RP5C01"
1031 depends on HAS_IOMEM
1033 If you say yes here you get support for the Ricoh RP5C01
1034 timekeeping chip. It is used in some Amiga models (e.g. A3000
1037 This driver can also be built as a module. If so, the module
1038 will be called rtc-rp5c01.
1040 config RTC_DRV_V3020
1041 tristate "EM Microelectronic V3020"
1043 If you say yes here you will get support for the
1044 EM Microelectronic v3020 RTC chip.
1046 This driver can also be built as a module. If so, the module
1047 will be called rtc-v3020.
1049 config RTC_DRV_WM831X
1050 tristate "Wolfson Microelectronics WM831x RTC"
1051 depends on MFD_WM831X
1053 If you say yes here you will get support for the RTC subsystem
1054 of the Wolfson Microelectronics WM831X series PMICs.
1056 This driver can also be built as a module. If so, the module
1057 will be called "rtc-wm831x".
1059 config RTC_DRV_WM8350
1060 tristate "Wolfson Microelectronics WM8350 RTC"
1061 depends on MFD_WM8350
1063 If you say yes here you will get support for the RTC subsystem
1064 of the Wolfson Microelectronics WM8350.
1066 This driver can also be built as a module. If so, the module
1067 will be called "rtc-wm8350".
1069 config RTC_DRV_SPEAR
1070 tristate "SPEAR ST RTC"
1071 depends on PLAT_SPEAR
1074 If you say Y here you will get support for the RTC found on
1077 config RTC_DRV_PCF50633
1078 depends on MFD_PCF50633
1079 tristate "NXP PCF50633 RTC"
1081 If you say yes here you get support for the RTC subsystem of the
1082 NXP PCF50633 used in embedded systems.
1084 config RTC_DRV_AB3100
1085 tristate "ST-Ericsson AB3100 RTC"
1086 depends on AB3100_CORE
1087 default y if AB3100_CORE
1089 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1090 support. This chip contains a battery- and capacitor-backed RTC.
1092 config RTC_DRV_AB8500
1093 tristate "ST-Ericsson AB8500 RTC"
1094 depends on AB8500_CORE
1096 select RTC_INTF_DEV_UIE_EMUL
1098 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1099 support. This chip contains a battery- and capacitor-backed RTC.
1101 config RTC_DRV_NUC900
1102 tristate "NUC910/NUC920 RTC driver"
1103 depends on ARCH_W90X900
1105 If you say yes here you get support for the RTC subsystem of the
1106 NUC910/NUC920 used in embedded systems.
1109 tristate "IBM OPAL RTC driver"
1110 depends on PPC_POWERNV
1113 If you say yes here you get support for the PowerNV platform RTC
1114 driver based on OPAL interfaces.
1116 This driver can also be built as a module. If so, the module
1117 will be called rtc-opal.
1119 config RTC_DRV_ZYNQMP
1120 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1123 If you say yes here you get support for the RTC controller found on
1124 Xilinx Zynq Ultrascale+ MPSoC.
1126 comment "on-CPU RTC drivers"
1128 config RTC_DRV_DAVINCI
1129 tristate "TI DaVinci RTC"
1130 depends on ARCH_DAVINCI_DM365
1132 If you say yes here you get support for the RTC on the
1133 DaVinci platforms (DM365).
1135 This driver can also be built as a module. If so, the module
1136 will be called rtc-davinci.
1138 config RTC_DRV_DIGICOLOR
1139 tristate "Conexant Digicolor RTC"
1140 depends on ARCH_DIGICOLOR
1142 If you say yes here you get support for the RTC on Conexant
1143 Digicolor platforms. This currently includes the CX92755 SoC.
1145 This driver can also be built as a module. If so, the module
1146 will be called rtc-digicolor.
1148 config RTC_DRV_IMXDI
1149 tristate "Freescale IMX DryIce Real Time Clock"
1152 Support for Freescale IMX DryIce RTC
1154 This driver can also be built as a module, if so, the module
1155 will be called "rtc-imxdi".
1158 tristate "TI OMAP Real Time Clock"
1159 depends on ARCH_OMAP || ARCH_DAVINCI
1161 Say "yes" here to support the on chip real time clock
1162 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1164 This driver can also be built as a module, if so, module
1165 will be called rtc-omap.
1170 This will include RTC support for Samsung SoCs. If
1171 you want to include RTC support for any machine, kindly
1172 select this in the respective mach-XXXX/Kconfig file.
1175 tristate "Samsung S3C series SoC RTC"
1176 depends on ARCH_S3C64XX || HAVE_S3C_RTC
1178 RTC (Realtime Clock) driver for the clock inbuilt into the
1179 Samsung S3C24XX series of SoCs. This can provide periodic
1180 interrupt rates from 1Hz to 64Hz for user programs, and
1183 The driver currently supports the common features on all the
1184 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1187 This driver can also be build as a module. If so, the module
1188 will be called rtc-s3c.
1190 config RTC_DRV_EP93XX
1191 tristate "Cirrus Logic EP93XX"
1192 depends on ARCH_EP93XX
1194 If you say yes here you get support for the
1195 RTC embedded in the Cirrus Logic EP93XX processors.
1197 This driver can also be built as a module. If so, the module
1198 will be called rtc-ep93xx.
1200 config RTC_DRV_SA1100
1201 tristate "SA11x0/PXA2xx/PXA910"
1202 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1204 If you say Y here you will get access to the real time clock
1205 built into your SA11x0 or PXA2xx CPU.
1207 To compile this driver as a module, choose M here: the
1208 module will be called rtc-sa1100.
1211 tristate "SuperH On-Chip RTC"
1212 depends on SUPERH && HAVE_CLK
1214 Say Y here to enable support for the on-chip RTC found in
1215 most SuperH processors.
1217 To compile this driver as a module, choose M here: the
1218 module will be called rtc-sh.
1220 config RTC_DRV_VR41XX
1221 tristate "NEC VR41XX"
1222 depends on CPU_VR41XX
1224 If you say Y here you will get access to the real time clock
1225 built into your NEC VR41XX CPU.
1227 To compile this driver as a module, choose M here: the
1228 module will be called rtc-vr41xx.
1230 config RTC_DRV_PL030
1231 tristate "ARM AMBA PL030 RTC"
1234 If you say Y here you will get access to ARM AMBA
1235 PrimeCell PL030 RTC found on certain ARM SOCs.
1237 To compile this driver as a module, choose M here: the
1238 module will be called rtc-pl030.
1240 config RTC_DRV_PL031
1241 tristate "ARM AMBA PL031 RTC"
1244 If you say Y here you will get access to ARM AMBA
1245 PrimeCell PL031 RTC found on certain ARM SOCs.
1247 To compile this driver as a module, choose M here: the
1248 module will be called rtc-pl031.
1250 config RTC_DRV_AT32AP700X
1251 tristate "AT32AP700X series RTC"
1252 depends on PLATFORM_AT32AP
1254 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1255 AT32AP700x family processors.
1257 config RTC_DRV_AT91RM9200
1258 tristate "AT91RM9200 or some AT91SAM9 RTC"
1259 depends on ARCH_AT91
1261 Driver for the internal RTC (Realtime Clock) module found on
1262 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1263 this is powered by the backup power supply.
1265 config RTC_DRV_AT91SAM9
1266 tristate "AT91SAM9 RTT as RTC"
1267 depends on ARCH_AT91
1270 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1271 can be used as an RTC thanks to the backup power supply (e.g. a
1272 small coin cell battery) which keeps this block and the GPBR
1273 (General Purpose Backup Registers) block powered when the device
1275 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1276 probably want to use the real RTC block instead of the "RTT as an
1279 config RTC_DRV_AU1XXX
1280 tristate "Au1xxx Counter0 RTC support"
1281 depends on MIPS_ALCHEMY
1283 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1284 counter) to be used as a RTC.
1286 This driver can also be built as a module. If so, the module
1287 will be called rtc-au1xxx.
1290 tristate "Blackfin On-Chip RTC"
1291 depends on BLACKFIN && !BF561
1293 If you say yes here you will get support for the
1294 Blackfin On-Chip Real Time Clock.
1296 This driver can also be built as a module. If so, the module
1297 will be called rtc-bfin.
1299 config RTC_DRV_RS5C313
1300 tristate "Ricoh RS5C313"
1301 depends on SH_LANDISK
1303 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1305 config RTC_DRV_GENERIC
1306 tristate "Generic RTC support"
1307 # Please consider writing a new RTC driver instead of using the generic
1309 depends on PARISC || M68K || PPC || SUPERH32
1311 Say Y or M here to enable RTC support on systems using the generic
1312 RTC abstraction. If you do not know what you are doing, you should
1316 tristate "PXA27x/PXA3xx"
1318 select RTC_DRV_SA1100
1320 If you say Y here you will get access to the real time clock
1321 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1322 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1324 This RTC driver uses PXA RTC registers available since pxa27x
1325 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1327 config RTC_DRV_VT8500
1328 tristate "VIA/WonderMedia 85xx SoC RTC"
1329 depends on ARCH_VT8500
1331 If you say Y here you will get access to the real time clock
1332 built into your VIA VT8500 SoC or its relatives.
1335 config RTC_DRV_SUN4V
1336 bool "SUN4V Hypervisor RTC"
1339 If you say Y here you will get support for the Hypervisor
1340 based RTC on SUN4V systems.
1342 config RTC_DRV_SUN6I
1343 tristate "Allwinner A31 RTC"
1344 depends on MACH_SUN6I || MACH_SUN8I
1346 If you say Y here you will get support for the RTC found on
1349 config RTC_DRV_SUNXI
1350 tristate "Allwinner sun4i/sun7i RTC"
1351 depends on MACH_SUN4I || MACH_SUN7I
1353 If you say Y here you will get support for the RTC found on
1356 config RTC_DRV_STARFIRE
1360 If you say Y here you will get support for the RTC found on
1363 config RTC_DRV_TX4939
1364 tristate "TX4939 SoC"
1365 depends on SOC_TX4939
1367 Driver for the internal RTC (Realtime Clock) module found on
1371 tristate "Marvell SoC RTC"
1372 depends on ARCH_DOVE || ARCH_MVEBU
1374 If you say yes here you will get support for the in-chip RTC
1375 that can be found in some of Marvell's SoC devices, such as
1376 the Kirkwood 88F6281 and 88F6192.
1378 This driver can also be built as a module. If so, the module
1379 will be called rtc-mv.
1381 config RTC_DRV_ARMADA38X
1382 tristate "Armada 38x Marvell SoC RTC"
1383 depends on ARCH_MVEBU
1385 If you say yes here you will get support for the in-chip RTC
1386 that can be found in the Armada 38x Marvell's SoC device
1388 This driver can also be built as a module. If so, the module
1389 will be called armada38x-rtc.
1391 config RTC_DRV_GEMINI
1392 tristate "Gemini SoC RTC"
1393 depends on ARCH_GEMINI || COMPILE_TEST
1394 depends on HAS_IOMEM
1396 If you say Y here you will get support for the
1397 RTC found on Gemini SoC's.
1399 This driver can also be built as a module. If so, the module
1400 will be called rtc-gemini.
1406 If you say yes here you will get support for the RTC on PS3.
1408 This driver can also be built as a module. If so, the module
1409 will be called rtc-ps3.
1411 config RTC_DRV_COH901331
1412 tristate "ST-Ericsson COH 901 331 RTC"
1413 depends on ARCH_U300
1415 If you say Y here you will get access to ST-Ericsson
1416 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1419 This driver can also be built as a module. If so, the module
1420 will be called "rtc-coh901331".
1424 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1428 If you say yes here you will get support for the onboard
1429 STMP3xxx/i.MX23/i.MX28 RTC.
1431 This driver can also be built as a module. If so, the module
1432 will be called rtc-stmp3xxx.
1438 If you say Y here you will get support for the RTC found on
1439 the PCAP2 ASIC used on some Motorola phones.
1441 config RTC_DRV_MC13XXX
1442 depends on MFD_MC13XXX
1443 tristate "Freescale MC13xxx RTC"
1445 This enables support for the RTCs found on Freescale's PMICs
1446 MC13783 and MC13892.
1448 config RTC_DRV_MPC5121
1449 tristate "Freescale MPC5121 built-in RTC"
1450 depends on PPC_MPC512x || PPC_MPC52xx
1452 If you say yes here you will get support for the
1453 built-in RTC on MPC5121 or on MPC5200.
1455 This driver can also be built as a module. If so, the module
1456 will be called rtc-mpc5121.
1458 config RTC_DRV_JZ4740
1459 tristate "Ingenic JZ4740 SoC"
1460 depends on MACH_JZ4740
1462 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1465 This driver can also be buillt as a module. If so, the module
1466 will be called rtc-jz4740.
1468 config RTC_DRV_LPC24XX
1469 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1470 depends on ARCH_LPC18XX || COMPILE_TEST
1471 depends on OF && HAS_IOMEM
1473 This enables support for the NXP RTC found which can be found on
1474 NXP LPC178x/18xx/408x/43xx devices.
1476 If you have one of the devices above enable this driver to use
1477 the hardware RTC. This driver can also be buillt as a module. If
1478 so, the module will be called rtc-lpc24xx.
1480 config RTC_DRV_LPC32XX
1481 depends on ARCH_LPC32XX
1482 tristate "NXP LPC32XX RTC"
1484 This enables support for the NXP RTC in the LPC32XX
1486 This driver can also be buillt as a module. If so, the module
1487 will be called rtc-lpc32xx.
1489 config RTC_DRV_PM8XXX
1490 tristate "Qualcomm PMIC8XXX RTC"
1491 depends on MFD_PM8XXX || MFD_SPMI_PMIC
1493 If you say yes here you get support for the
1494 Qualcomm PMIC8XXX RTC.
1496 To compile this driver as a module, choose M here: the
1497 module will be called rtc-pm8xxx.
1499 config RTC_DRV_TEGRA
1500 tristate "NVIDIA Tegra Internal RTC driver"
1501 depends on ARCH_TEGRA
1503 If you say yes here you get support for the
1504 Tegra 200 series internal RTC module.
1506 This drive can also be built as a module. If so, the module
1507 will be called rtc-tegra.
1510 tristate "Tilera hypervisor RTC support"
1513 Enable support for the Linux driver side of the Tilera
1514 hypervisor's real-time clock interface.
1517 tristate "PKUnity v3 RTC support"
1518 depends on ARCH_PUV3
1520 This enables support for the RTC in the PKUnity-v3 SoCs.
1522 This drive can also be built as a module. If so, the module
1523 will be called rtc-puv3.
1525 config RTC_DRV_LOONGSON1
1526 tristate "loongson1 RTC support"
1527 depends on MACH_LOONGSON32
1529 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1530 counter) to be used as a RTC.
1532 This driver can also be built as a module. If so, the module
1533 will be called rtc-ls1x.
1536 tristate "Freescale MXC Real Time Clock"
1539 If you say yes here you get support for the Freescale MXC
1542 This driver can also be built as a module, if so, the module
1543 will be called "rtc-mxc".
1546 tristate "Freescale SNVS RTC support"
1548 depends on HAS_IOMEM
1551 If you say yes here you get support for the Freescale SNVS
1552 Low Power (LP) RTC module.
1554 This driver can also be built as a module, if so, the module
1555 will be called "rtc-snvs".
1557 config RTC_DRV_SIRFSOC
1558 tristate "SiRFSOC RTC"
1559 depends on ARCH_SIRF
1561 Say "yes" here to support the real time clock on SiRF SOC chips.
1562 This driver can also be built as a module called rtc-sirfsoc.
1564 config RTC_DRV_ST_LPC
1565 tristate "STMicroelectronics LPC RTC"
1569 Say Y here to include STMicroelectronics Low Power Controller
1570 (LPC) based RTC support.
1572 To compile this driver as a module, choose M here: the
1573 module will be called rtc-st-lpc.
1575 config RTC_DRV_MOXART
1576 tristate "MOXA ART RTC"
1577 depends on ARCH_MOXART || COMPILE_TEST
1579 If you say yes here you get support for the MOXA ART
1582 This driver can also be built as a module. If so, the module
1583 will be called rtc-moxart
1585 config RTC_DRV_MT6397
1586 tristate "Mediatek Real Time Clock driver"
1587 depends on MFD_MT6397 || COMPILE_TEST
1589 This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
1590 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1591 Mediatek(R) RTC driver.
1593 If you want to use Mediatek(R) RTC interface, select Y or M here.
1595 config RTC_DRV_XGENE
1596 tristate "APM X-Gene RTC"
1597 depends on HAS_IOMEM
1598 depends on ARCH_XGENE || COMPILE_TEST
1600 If you say yes here you get support for the APM X-Gene SoC real time
1603 This driver can also be built as a module, if so, the module
1604 will be called "rtc-xgene".
1606 comment "HID Sensor RTC drivers"
1608 config RTC_DRV_HID_SENSOR_TIME
1609 tristate "HID Sensor Time"
1612 select HID_SENSOR_HUB
1613 select HID_SENSOR_IIO_COMMON
1615 Say yes here to build support for the HID Sensors of type Time.
1616 This drivers makes such sensors available as RTCs.
1618 If this driver is compiled as a module, it will be named
1619 rtc-hid-sensor-time.