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_DS1307_HWMON
216 bool "HWMON support for rtc-ds1307"
217 depends on RTC_DRV_DS1307 && HWMON
218 depends on !(RTC_DRV_DS1307=y && HWMON=m)
221 Say Y here if you want to expose temperature sensor data on
222 rtc-ds1307 (only DS3231)
224 config RTC_DRV_DS1374
225 tristate "Dallas/Maxim DS1374"
227 If you say yes here you get support for Dallas Semiconductor
228 DS1374 real-time clock chips. If an interrupt is associated
229 with the device, the alarm functionality is supported.
231 This driver can also be built as a module. If so, the module
232 will be called rtc-ds1374.
234 config RTC_DRV_DS1374_WDT
235 bool "Dallas/Maxim DS1374 watchdog timer"
236 depends on RTC_DRV_DS1374
238 If you say Y here you will get support for the
239 watchdog timer in the Dallas Semiconductor DS1374
240 real-time clock chips.
242 config RTC_DRV_DS1672
243 tristate "Dallas/Maxim DS1672"
245 If you say yes here you get support for the
246 Dallas/Maxim DS1672 timekeeping chip.
248 This driver can also be built as a module. If so, the module
249 will be called rtc-ds1672.
251 config RTC_DRV_DS3232
252 tristate "Dallas/Maxim DS3232"
254 If you say yes here you get support for Dallas Semiconductor
255 DS3232 real-time clock chips. If an interrupt is associated
256 with the device, the alarm functionality is supported.
258 This driver can also be built as a module. If so, the module
259 will be called rtc-ds3232.
261 config RTC_DRV_HYM8563
262 tristate "Haoyu Microelectronics HYM8563"
265 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
266 from the usual rtc functions it provides a clock output of
269 This driver can also be built as a module. If so, the module
270 will be called rtc-hym8563.
272 config RTC_DRV_LP8788
273 tristate "TI LP8788 RTC driver"
274 depends on MFD_LP8788
276 Say Y to enable support for the LP8788 RTC/ALARM driver.
278 config RTC_DRV_MAX6900
279 tristate "Maxim MAX6900"
281 If you say yes here you will get support for the
282 Maxim MAX6900 I2C RTC chip.
284 This driver can also be built as a module. If so, the module
285 will be called rtc-max6900.
287 config RTC_DRV_MAX8907
288 tristate "Maxim MAX8907"
289 depends on MFD_MAX8907
291 If you say yes here you will get support for the
292 RTC of Maxim MAX8907 PMIC.
294 This driver can also be built as a module. If so, the module
295 will be called rtc-max8907.
297 config RTC_DRV_MAX8925
298 tristate "Maxim MAX8925"
299 depends on MFD_MAX8925
301 If you say yes here you will get support for the
302 RTC of Maxim MAX8925 PMIC.
304 This driver can also be built as a module. If so, the module
305 will be called rtc-max8925.
307 config RTC_DRV_MAX8998
308 tristate "Maxim MAX8998"
309 depends on MFD_MAX8998
311 If you say yes here you will get support for the
312 RTC of Maxim MAX8998 PMIC.
314 This driver can also be built as a module. If so, the module
315 will be called rtc-max8998.
317 config RTC_DRV_MAX8997
318 tristate "Maxim MAX8997"
319 depends on MFD_MAX8997
321 If you say yes here you will get support for the
322 RTC of Maxim MAX8997 PMIC.
324 This driver can also be built as a module. If so, the module
325 will be called rtc-max8997.
327 config RTC_DRV_MAX77686
328 tristate "Maxim MAX77686"
329 depends on MFD_MAX77686
331 If you say yes here you will get support for the
332 RTC of Maxim MAX77686 PMIC.
334 This driver can also be built as a module. If so, the module
335 will be called rtc-max77686.
338 tristate "Rockchip RK808 RTC"
341 If you say yes here you will get support for the
344 This driver can also be built as a module. If so, the module
345 will be called rk808-rtc.
347 config RTC_DRV_RS5C372
348 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
350 If you say yes here you get support for the
351 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
353 This driver can also be built as a module. If so, the module
354 will be called rtc-rs5c372.
356 config RTC_DRV_ISL1208
357 tristate "Intersil ISL1208"
359 If you say yes here you get support for the
360 Intersil ISL1208 RTC chip.
362 This driver can also be built as a module. If so, the module
363 will be called rtc-isl1208.
365 config RTC_DRV_ISL12022
366 tristate "Intersil ISL12022"
368 If you say yes here you get support for the
369 Intersil ISL12022 RTC chip.
371 This driver can also be built as a module. If so, the module
372 will be called rtc-isl12022.
374 config RTC_DRV_ISL12057
376 tristate "Intersil ISL12057"
378 If you say yes here you get support for the Intersil ISL12057
381 This driver can also be built as a module. If so, the module
382 will be called rtc-isl12057.
385 tristate "Xicor/Intersil X1205"
387 If you say yes here you get support for the
388 Xicor/Intersil X1205 RTC chip.
390 This driver can also be built as a module. If so, the module
391 will be called rtc-x1205.
393 config RTC_DRV_PALMAS
394 tristate "TI Palmas RTC driver"
395 depends on MFD_PALMAS
397 If you say yes here you get support for the RTC of TI PALMA series PMIC
400 This driver can also be built as a module. If so, the module
401 will be called rtc-palma.
403 config RTC_DRV_PCF2127
404 tristate "NXP PCF2127"
406 If you say yes here you get support for the NXP PCF2127/29 RTC
409 This driver can also be built as a module. If so, the module
410 will be called rtc-pcf2127.
412 config RTC_DRV_PCF8523
413 tristate "NXP PCF8523"
415 If you say yes here you get support for the NXP PCF8523 RTC
418 This driver can also be built as a module. If so, the module
419 will be called rtc-pcf8523.
421 config RTC_DRV_PCF8563
422 tristate "Philips PCF8563/Epson RTC8564"
424 If you say yes here you get support for the
425 Philips PCF8563 RTC chip. The Epson RTC8564
428 This driver can also be built as a module. If so, the module
429 will be called rtc-pcf8563.
431 config RTC_DRV_PCF85063
432 tristate "nxp PCF85063"
434 If you say yes here you get support for the PCF85063 RTC chip
436 This driver can also be built as a module. If so, the module
437 will be called rtc-pcf85063.
439 config RTC_DRV_PCF8583
440 tristate "Philips PCF8583"
442 If you say yes here you get support for the Philips PCF8583
443 RTC chip found on Acorn RiscPCs. This driver supports the
444 platform specific method of retrieving the current year from
445 the RTC's SRAM. It will work on other platforms with the same
446 chip, but the year will probably have to be tweaked.
448 This driver can also be built as a module. If so, the module
449 will be called rtc-pcf8583.
451 config RTC_DRV_M41T80
452 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
454 If you say Y here you will get support for the ST M41T60
455 and M41T80 RTC chips series. Currently, the following chips are
456 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
457 M41ST85, M41ST87, and MicroCrystal RV4162.
459 This driver can also be built as a module. If so, the module
460 will be called rtc-m41t80.
462 config RTC_DRV_M41T80_WDT
463 bool "ST M41T65/M41T80 series RTC watchdog timer"
464 depends on RTC_DRV_M41T80
466 If you say Y here you will get support for the
467 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
470 tristate "TI BQ32000"
472 If you say Y here you will get support for the TI
473 BQ32000 I2C RTC chip.
475 This driver can also be built as a module. If so, the module
476 will be called rtc-bq32k.
478 config RTC_DRV_DM355EVM
479 tristate "TI DaVinci DM355 EVM RTC"
480 depends on MFD_DM355EVM_MSP
482 Supports the RTC firmware in the MSP430 on the DM355 EVM.
484 config RTC_DRV_TWL92330
485 bool "TI TWL92330/Menelaus"
488 If you say yes here you get support for the RTC on the
489 TWL92330 "Menelaus" power management chip, used with OMAP2
490 platforms. The support is integrated with the rest of
491 the Menelaus driver; it's not separate module.
493 config RTC_DRV_TWL4030
494 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
495 depends on TWL4030_CORE
497 If you say yes here you get support for the RTC on the
498 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
500 This driver can also be built as a module. If so, the module
501 will be called rtc-twl.
503 config RTC_DRV_TPS6586X
504 tristate "TI TPS6586X RTC driver"
505 depends on MFD_TPS6586X
507 TI Power Management IC TPS6586X supports RTC functionality
508 along with alarm. This driver supports the RTC driver for
509 the TPS6586X RTC module.
511 config RTC_DRV_TPS65910
512 tristate "TI TPS65910 RTC driver"
513 depends on RTC_CLASS && MFD_TPS65910
515 If you say yes here you get support for the RTC on the
518 This driver can also be built as a module. If so, the module
519 will be called rtc-tps65910.
521 config RTC_DRV_TPS80031
522 tristate "TI TPS80031/TPS80032 RTC driver"
523 depends on MFD_TPS80031
525 TI Power Management IC TPS80031 supports RTC functionality
526 along with alarm. This driver supports the RTC driver for
527 the TPS80031 RTC module.
529 config RTC_DRV_RC5T583
530 tristate "RICOH 5T583 RTC driver"
531 depends on MFD_RC5T583
533 If you say yes here you get support for the RTC on the
536 This driver can also be built as a module. If so, the module
537 will be called rtc-rc5t583.
539 config RTC_DRV_S35390A
540 tristate "Seiko Instruments S-35390A"
543 If you say yes here you will get support for the Seiko
544 Instruments S-35390A.
546 This driver can also be built as a module. If so the module
547 will be called rtc-s35390a.
549 config RTC_DRV_FM3130
550 tristate "Ramtron FM3130"
552 If you say Y here you will get support for the
553 Ramtron FM3130 RTC chips.
554 Ramtron FM3130 is a chip with two separate devices inside,
555 RTC clock and FRAM. This driver provides only RTC functionality.
557 This driver can also be built as a module. If so the module
558 will be called rtc-fm3130.
560 config RTC_DRV_RX8010
561 tristate "Epson RX8010SJ"
564 If you say yes here you get support for the Epson RX8010SJ RTC
567 This driver can also be built as a module. If so, the module
568 will be called rtc-rx8010.
570 config RTC_DRV_RX8581
571 tristate "Epson RX-8581"
573 If you say yes here you will get support for the Epson RX-8581.
575 This driver can also be built as a module. If so the module
576 will be called rtc-rx8581.
578 config RTC_DRV_RX8025
579 tristate "Epson RX-8025SA/NB"
581 If you say yes here you get support for the Epson
582 RX-8025SA/NB RTC chips.
584 This driver can also be built as a module. If so, the module
585 will be called rtc-rx8025.
587 config RTC_DRV_EM3027
588 tristate "EM Microelectronic EM3027"
590 If you say yes here you get support for the EM
591 Microelectronic EM3027 RTC chips.
593 This driver can also be built as a module. If so, the module
594 will be called rtc-em3027.
596 config RTC_DRV_RV3029C2
597 tristate "Micro Crystal RTC"
599 If you say yes here you get support for the Micro Crystal
602 This driver can also be built as a module. If so, the module
603 will be called rtc-rv3029c2.
605 config RTC_DRV_RV8803
606 tristate "Micro Crystal RV8803"
608 If you say yes here you get support for the Micro Crystal
611 This driver can also be built as a module. If so, the module
612 will be called rtc-rv8803.
615 tristate "Samsung S2M/S5M series"
616 depends on MFD_SEC_CORE
618 If you say yes here you will get support for the
619 RTC of Samsung S2MPS14 and S5M PMIC series.
621 This driver can also be built as a module. If so, the module
622 will be called rtc-s5m.
626 comment "SPI RTC drivers"
630 config RTC_DRV_M41T93
633 If you say yes here you will get support for the
634 ST M41T93 SPI RTC chip.
636 This driver can also be built as a module. If so, the module
637 will be called rtc-m41t93.
639 config RTC_DRV_M41T94
642 If you say yes here you will get support for the
643 ST M41T94 SPI RTC chip.
645 This driver can also be built as a module. If so, the module
646 will be called rtc-m41t94.
648 config RTC_DRV_DS1305
649 tristate "Dallas/Maxim DS1305/DS1306"
651 Select this driver to get support for the Dallas/Maxim DS1305
652 and DS1306 real time clock chips. These support a trickle
653 charger, alarms, and NVRAM in addition to the clock.
655 This driver can also be built as a module. If so, the module
656 will be called rtc-ds1305.
658 config RTC_DRV_DS1343
660 tristate "Dallas/Maxim DS1343/DS1344"
662 If you say yes here you get support for the
663 Dallas/Maxim DS1343 and DS1344 real time clock chips.
664 Support for trickle charger, alarm is provided.
666 This driver can also be built as a module. If so, the module
667 will be called rtc-ds1343.
669 config RTC_DRV_DS1347
670 tristate "Dallas/Maxim DS1347"
672 If you say yes here you get support for the
673 Dallas/Maxim DS1347 chips.
675 This driver only supports the RTC feature, and not other chip
676 features such as alarms.
678 This driver can also be built as a module. If so, the module
679 will be called rtc-ds1347.
681 config RTC_DRV_DS1390
682 tristate "Dallas/Maxim DS1390/93/94"
684 If you say yes here you get support for the
685 Dallas/Maxim DS1390/93/94 chips.
687 This driver supports the RTC feature and trickle charging but not
688 other chip features such as alarms.
690 This driver can also be built as a module. If so, the module
691 will be called rtc-ds1390.
693 config RTC_DRV_MAX6902
694 tristate "Maxim MAX6902"
696 If you say yes here you will get support for the
697 Maxim MAX6902 SPI RTC chip.
699 This driver can also be built as a module. If so, the module
700 will be called rtc-max6902.
703 tristate "Epson RTC-9701JE"
705 If you say yes here you will get support for the
706 Epson RTC-9701JE SPI RTC chip.
708 This driver can also be built as a module. If so, the module
709 will be called rtc-r9701.
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_DS3234
721 tristate "Maxim/Dallas DS3234"
723 If you say yes here you get support for the
724 Maxim/Dallas DS3234 SPI RTC chip.
726 This driver can also be built as a module. If so, the module
727 will be called rtc-ds3234.
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_RX4581
739 tristate "Epson RX-4581"
741 If you say yes here you will get support for the Epson RX-4581.
743 This driver can also be built as a module. If so the module
744 will be called rtc-rx4581.
746 config RTC_DRV_RX6110
747 tristate "Epson RX-6110"
750 If you say yes here you will get support for the Epson RX-6610.
752 This driver can also be built as a module. If so the module
753 will be called rtc-rx6110.
755 config RTC_DRV_MCP795
756 tristate "Microchip MCP795"
758 If you say yes here you will get support for the Microchip MCP795.
760 This driver can also be built as a module. If so the module
761 will be called rtc-mcp795.
765 comment "Platform RTC drivers"
767 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
768 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
769 # global rtc_lock ... it's not yet just another platform_device.
772 tristate "PC-style 'CMOS'"
773 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
776 Say "yes" here to get direct support for the real time clock
777 found in every PC or ACPI-based system, and some other boards.
778 Specifically the original MC146818, compatibles like those in
779 PC south bridges, the DS12887 or M48T86, some multifunction
780 or LPC bus chips, and so on.
782 Your system will need to define the platform device used by
783 this driver, otherwise it won't be accessible. This means
784 you can safely enable this driver if you don't know whether
785 or not your board has this kind of hardware.
787 This driver can also be built as a module. If so, the module
788 will be called rtc-cmos.
791 bool "Alpha PC-style CMOS"
795 Direct support for the real-time clock found on every Alpha
796 system, specifically MC146818 compatibles. If in doubt, say Y.
799 tristate "Virtual RTC for Intel MID platforms"
800 depends on X86_INTEL_MID
801 default y if X86_INTEL_MID
804 Say "yes" here to get direct support for the real time clock
805 found on Moorestown platforms. The VRTC is a emulated RTC that
806 derives its clock source from a real RTC in the PMIC. The MC146818
807 style programming interface is mostly conserved, but any
808 updates are done via IPC calls to the system controller FW.
810 config RTC_DRV_DS1216
811 tristate "Dallas DS1216"
814 If you say yes here you get support for the Dallas DS1216 RTC chips.
816 config RTC_DRV_DS1286
817 tristate "Dallas DS1286"
820 If you say yes here you get support for the Dallas DS1286 RTC chips.
822 config RTC_DRV_DS1302
823 tristate "Dallas DS1302"
824 depends on SH_SECUREEDGE5410
826 If you say yes here you get support for the Dallas DS1302 RTC chips.
828 config RTC_DRV_DS1511
829 tristate "Dallas DS1511"
832 If you say yes here you get support for the
833 Dallas DS1511 timekeeping/watchdog chip.
835 This driver can also be built as a module. If so, the module
836 will be called rtc-ds1511.
838 config RTC_DRV_DS1553
839 tristate "Maxim/Dallas DS1553"
842 If you say yes here you get support for the
843 Maxim/Dallas DS1553 timekeeping chip.
845 This driver can also be built as a module. If so, the module
846 will be called rtc-ds1553.
848 config RTC_DRV_DS1685_FAMILY
849 tristate "Dallas/Maxim DS1685 Family"
851 If you say yes here you get support for the Dallas/Maxim DS1685
852 family of real time chips. This family includes the DS1685/DS1687,
853 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
854 DS17885/DS17887 chips.
856 This driver can also be built as a module. If so, the module
857 will be called rtc-ds1685.
861 depends on RTC_DRV_DS1685_FAMILY
862 default RTC_DRV_DS1685
864 config RTC_DRV_DS1685
867 This enables support for the Dallas/Maxim DS1685/DS1687 real time
870 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
871 systems, as well as EPPC-405-UC modules by electronic system design
874 config RTC_DRV_DS1689
877 This enables support for the Dallas/Maxim DS1689/DS1693 real time
880 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
881 which supports a few minor features such as Vcc, Vbat, and Power
882 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
884 It also works for the even older DS1688/DS1691 RTC chips, which are
885 virtually the same and carry the same model number. Both chips
886 have 114 bytes of user NVRAM.
888 config RTC_DRV_DS17285
889 bool "DS17285/DS17287"
891 This enables support for the Dallas/Maxim DS17285/DS17287 real time
894 This chip features 2kb of extended NV-SRAM. It may possibly be
895 found in some SGI O2 systems (rare).
897 config RTC_DRV_DS17485
898 bool "DS17485/DS17487"
900 This enables support for the Dallas/Maxim DS17485/DS17487 real time
903 This chip features 4kb of extended NV-SRAM.
905 config RTC_DRV_DS17885
906 bool "DS17885/DS17887"
908 This enables support for the Dallas/Maxim DS17885/DS17887 real time
911 This chip features 8kb of extended NV-SRAM.
915 config RTC_DS1685_PROC_REGS
916 bool "Display register values in /proc"
917 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
919 Enable this to display a readout of all of the RTC registers in
920 /proc/drivers/rtc. Keep in mind that this can potentially lead
921 to lost interrupts, as reading Control Register C will clear
922 all pending IRQ flags.
924 Unless you are debugging this driver, choose N.
926 config RTC_DS1685_SYSFS_REGS
927 bool "SysFS access to RTC register bits"
928 depends on RTC_DRV_DS1685_FAMILY && SYSFS
930 Enable this to provide access to the RTC control register bits
931 in /sys. Some of the bits are read-write, others are read-only.
933 Keep in mind that reading Control C's bits automatically clears
934 all pending IRQ flags - this can cause lost interrupts.
936 If you know that you need access to these bits, choose Y, Else N.
938 config RTC_DRV_DS1742
939 tristate "Maxim/Dallas DS1742/1743"
942 If you say yes here you get support for the
943 Maxim/Dallas DS1742/1743 timekeeping chip.
945 This driver can also be built as a module. If so, the module
946 will be called rtc-ds1742.
948 config RTC_DRV_DS2404
949 tristate "Maxim/Dallas DS2404"
951 If you say yes here you get support for the
952 Dallas DS2404 RTC chip.
954 This driver can also be built as a module. If so, the module
955 will be called rtc-ds2404.
957 config RTC_DRV_DA9052
958 tristate "Dialog DA9052/DA9053 RTC"
959 depends on PMIC_DA9052
961 Say y here to support the RTC driver for Dialog Semiconductor
962 DA9052-BC and DA9053-AA/Bx PMICs.
964 config RTC_DRV_DA9055
965 tristate "Dialog Semiconductor DA9055 RTC"
966 depends on MFD_DA9055
968 If you say yes here you will get support for the
969 RTC of the Dialog DA9055 PMIC.
971 This driver can also be built as a module. If so, the module
972 will be called rtc-da9055
974 config RTC_DRV_DA9063
975 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
976 depends on MFD_DA9063 || MFD_DA9062
978 If you say yes here you will get support for the RTC subsystem
979 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
981 This driver can also be built as a module. If so, the module
982 will be called "rtc-da9063".
986 depends on EFI && !X86
988 If you say yes here you will get support for the EFI
991 This driver can also be built as a module. If so, the module
992 will be called rtc-efi.
994 config RTC_DRV_STK17TA8
995 tristate "Simtek STK17TA8"
998 If you say yes here you get support for the
999 Simtek STK17TA8 timekeeping chip.
1001 This driver can also be built as a module. If so, the module
1002 will be called rtc-stk17ta8.
1004 config RTC_DRV_M48T86
1005 tristate "ST M48T86/Dallas DS12887"
1007 If you say Y here you will get support for the
1008 ST M48T86 and Dallas DS12887 RTC chips.
1010 This driver can also be built as a module. If so, the module
1011 will be called rtc-m48t86.
1013 config RTC_DRV_M48T35
1014 tristate "ST M48T35"
1015 depends on HAS_IOMEM
1017 If you say Y here you will get support for the
1020 This driver can also be built as a module, if so, the module
1021 will be called "rtc-m48t35".
1023 config RTC_DRV_M48T59
1024 tristate "ST M48T59/M48T08/M48T02"
1025 depends on HAS_IOMEM
1027 If you say Y here you will get support for the
1028 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1030 These chips are usually found in Sun SPARC and UltraSPARC
1033 This driver can also be built as a module, if so, the module
1034 will be called "rtc-m48t59".
1036 config RTC_DRV_MSM6242
1037 tristate "Oki MSM6242"
1038 depends on HAS_IOMEM
1040 If you say yes here you get support for the Oki MSM6242
1041 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1043 This driver can also be built as a module. If so, the module
1044 will be called rtc-msm6242.
1046 config RTC_DRV_BQ4802
1047 tristate "TI BQ4802"
1048 depends on HAS_IOMEM
1050 If you say Y here you will get support for the TI
1053 This driver can also be built as a module. If so, the module
1054 will be called rtc-bq4802.
1056 config RTC_DRV_RP5C01
1057 tristate "Ricoh RP5C01"
1058 depends on HAS_IOMEM
1060 If you say yes here you get support for the Ricoh RP5C01
1061 timekeeping chip. It is used in some Amiga models (e.g. A3000
1064 This driver can also be built as a module. If so, the module
1065 will be called rtc-rp5c01.
1067 config RTC_DRV_V3020
1068 tristate "EM Microelectronic V3020"
1070 If you say yes here you will get support for the
1071 EM Microelectronic v3020 RTC chip.
1073 This driver can also be built as a module. If so, the module
1074 will be called rtc-v3020.
1076 config RTC_DRV_WM831X
1077 tristate "Wolfson Microelectronics WM831x RTC"
1078 depends on MFD_WM831X
1080 If you say yes here you will get support for the RTC subsystem
1081 of the Wolfson Microelectronics WM831X series PMICs.
1083 This driver can also be built as a module. If so, the module
1084 will be called "rtc-wm831x".
1086 config RTC_DRV_WM8350
1087 tristate "Wolfson Microelectronics WM8350 RTC"
1088 depends on MFD_WM8350
1090 If you say yes here you will get support for the RTC subsystem
1091 of the Wolfson Microelectronics WM8350.
1093 This driver can also be built as a module. If so, the module
1094 will be called "rtc-wm8350".
1096 config RTC_DRV_SPEAR
1097 tristate "SPEAR ST RTC"
1098 depends on PLAT_SPEAR
1101 If you say Y here you will get support for the RTC found on
1104 config RTC_DRV_PCF50633
1105 depends on MFD_PCF50633
1106 tristate "NXP PCF50633 RTC"
1108 If you say yes here you get support for the RTC subsystem of the
1109 NXP PCF50633 used in embedded systems.
1111 config RTC_DRV_AB3100
1112 tristate "ST-Ericsson AB3100 RTC"
1113 depends on AB3100_CORE
1114 default y if AB3100_CORE
1116 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1117 support. This chip contains a battery- and capacitor-backed RTC.
1119 config RTC_DRV_AB8500
1120 tristate "ST-Ericsson AB8500 RTC"
1121 depends on AB8500_CORE
1123 select RTC_INTF_DEV_UIE_EMUL
1125 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1126 support. This chip contains a battery- and capacitor-backed RTC.
1128 config RTC_DRV_NUC900
1129 tristate "NUC910/NUC920 RTC driver"
1130 depends on ARCH_W90X900
1132 If you say yes here you get support for the RTC subsystem of the
1133 NUC910/NUC920 used in embedded systems.
1136 tristate "IBM OPAL RTC driver"
1137 depends on PPC_POWERNV
1140 If you say yes here you get support for the PowerNV platform RTC
1141 driver based on OPAL interfaces.
1143 This driver can also be built as a module. If so, the module
1144 will be called rtc-opal.
1146 config RTC_DRV_ZYNQMP
1147 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1150 If you say yes here you get support for the RTC controller found on
1151 Xilinx Zynq Ultrascale+ MPSoC.
1153 comment "on-CPU RTC drivers"
1155 config RTC_DRV_DAVINCI
1156 tristate "TI DaVinci RTC"
1157 depends on ARCH_DAVINCI_DM365
1159 If you say yes here you get support for the RTC on the
1160 DaVinci platforms (DM365).
1162 This driver can also be built as a module. If so, the module
1163 will be called rtc-davinci.
1165 config RTC_DRV_DIGICOLOR
1166 tristate "Conexant Digicolor RTC"
1167 depends on ARCH_DIGICOLOR
1169 If you say yes here you get support for the RTC on Conexant
1170 Digicolor platforms. This currently includes the CX92755 SoC.
1172 This driver can also be built as a module. If so, the module
1173 will be called rtc-digicolor.
1175 config RTC_DRV_IMXDI
1176 tristate "Freescale IMX DryIce Real Time Clock"
1179 Support for Freescale IMX DryIce RTC
1181 This driver can also be built as a module, if so, the module
1182 will be called "rtc-imxdi".
1185 tristate "TI OMAP Real Time Clock"
1186 depends on ARCH_OMAP || ARCH_DAVINCI
1188 Say "yes" here to support the on chip real time clock
1189 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1191 This driver can also be built as a module, if so, module
1192 will be called rtc-omap.
1197 This will include RTC support for Samsung SoCs. If
1198 you want to include RTC support for any machine, kindly
1199 select this in the respective mach-XXXX/Kconfig file.
1202 tristate "Samsung S3C series SoC RTC"
1203 depends on ARCH_S3C64XX || HAVE_S3C_RTC
1205 RTC (Realtime Clock) driver for the clock inbuilt into the
1206 Samsung S3C24XX series of SoCs. This can provide periodic
1207 interrupt rates from 1Hz to 64Hz for user programs, and
1210 The driver currently supports the common features on all the
1211 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1214 This driver can also be build as a module. If so, the module
1215 will be called rtc-s3c.
1217 config RTC_DRV_EP93XX
1218 tristate "Cirrus Logic EP93XX"
1219 depends on ARCH_EP93XX
1221 If you say yes here you get support for the
1222 RTC embedded in the Cirrus Logic EP93XX processors.
1224 This driver can also be built as a module. If so, the module
1225 will be called rtc-ep93xx.
1227 config RTC_DRV_SA1100
1228 tristate "SA11x0/PXA2xx/PXA910"
1229 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1231 If you say Y here you will get access to the real time clock
1232 built into your SA11x0 or PXA2xx CPU.
1234 To compile this driver as a module, choose M here: the
1235 module will be called rtc-sa1100.
1238 tristate "SuperH On-Chip RTC"
1239 depends on SUPERH && HAVE_CLK
1241 Say Y here to enable support for the on-chip RTC found in
1242 most SuperH processors.
1244 To compile this driver as a module, choose M here: the
1245 module will be called rtc-sh.
1247 config RTC_DRV_VR41XX
1248 tristate "NEC VR41XX"
1249 depends on CPU_VR41XX
1251 If you say Y here you will get access to the real time clock
1252 built into your NEC VR41XX CPU.
1254 To compile this driver as a module, choose M here: the
1255 module will be called rtc-vr41xx.
1257 config RTC_DRV_PL030
1258 tristate "ARM AMBA PL030 RTC"
1261 If you say Y here you will get access to ARM AMBA
1262 PrimeCell PL030 RTC found on certain ARM SOCs.
1264 To compile this driver as a module, choose M here: the
1265 module will be called rtc-pl030.
1267 config RTC_DRV_PL031
1268 tristate "ARM AMBA PL031 RTC"
1271 If you say Y here you will get access to ARM AMBA
1272 PrimeCell PL031 RTC found on certain ARM SOCs.
1274 To compile this driver as a module, choose M here: the
1275 module will be called rtc-pl031.
1277 config RTC_DRV_AT32AP700X
1278 tristate "AT32AP700X series RTC"
1279 depends on PLATFORM_AT32AP
1281 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1282 AT32AP700x family processors.
1284 config RTC_DRV_AT91RM9200
1285 tristate "AT91RM9200 or some AT91SAM9 RTC"
1286 depends on ARCH_AT91
1288 Driver for the internal RTC (Realtime Clock) module found on
1289 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1290 this is powered by the backup power supply.
1292 config RTC_DRV_AT91SAM9
1293 tristate "AT91SAM9 RTT as RTC"
1294 depends on ARCH_AT91
1297 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1298 can be used as an RTC thanks to the backup power supply (e.g. a
1299 small coin cell battery) which keeps this block and the GPBR
1300 (General Purpose Backup Registers) block powered when the device
1302 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1303 probably want to use the real RTC block instead of the "RTT as an
1306 config RTC_DRV_AU1XXX
1307 tristate "Au1xxx Counter0 RTC support"
1308 depends on MIPS_ALCHEMY
1310 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1311 counter) to be used as a RTC.
1313 This driver can also be built as a module. If so, the module
1314 will be called rtc-au1xxx.
1317 tristate "Blackfin On-Chip RTC"
1318 depends on BLACKFIN && !BF561
1320 If you say yes here you will get support for the
1321 Blackfin On-Chip Real Time Clock.
1323 This driver can also be built as a module. If so, the module
1324 will be called rtc-bfin.
1326 config RTC_DRV_RS5C313
1327 tristate "Ricoh RS5C313"
1328 depends on SH_LANDISK
1330 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1332 config RTC_DRV_GENERIC
1333 tristate "Generic RTC support"
1334 # Please consider writing a new RTC driver instead of using the generic
1336 depends on PARISC || M68K || PPC || SUPERH32
1338 Say Y or M here to enable RTC support on systems using the generic
1339 RTC abstraction. If you do not know what you are doing, you should
1343 tristate "PXA27x/PXA3xx"
1345 select RTC_DRV_SA1100
1347 If you say Y here you will get access to the real time clock
1348 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1349 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1351 This RTC driver uses PXA RTC registers available since pxa27x
1352 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1354 config RTC_DRV_VT8500
1355 tristate "VIA/WonderMedia 85xx SoC RTC"
1356 depends on ARCH_VT8500
1358 If you say Y here you will get access to the real time clock
1359 built into your VIA VT8500 SoC or its relatives.
1362 config RTC_DRV_SUN4V
1363 bool "SUN4V Hypervisor RTC"
1366 If you say Y here you will get support for the Hypervisor
1367 based RTC on SUN4V systems.
1369 config RTC_DRV_SUN6I
1370 tristate "Allwinner A31 RTC"
1371 default MACH_SUN6I || MACH_SUN8I
1372 depends on ARCH_SUNXI
1374 If you say Y here you will get support for the RTC found in
1375 some Allwinner SoCs like the A31 or the A64.
1377 config RTC_DRV_SUNXI
1378 tristate "Allwinner sun4i/sun7i RTC"
1379 depends on MACH_SUN4I || MACH_SUN7I
1381 If you say Y here you will get support for the RTC found on
1384 config RTC_DRV_STARFIRE
1388 If you say Y here you will get support for the RTC found on
1391 config RTC_DRV_TX4939
1392 tristate "TX4939 SoC"
1393 depends on SOC_TX4939
1395 Driver for the internal RTC (Realtime Clock) module found on
1399 tristate "Marvell SoC RTC"
1400 depends on ARCH_DOVE || ARCH_MVEBU
1402 If you say yes here you will get support for the in-chip RTC
1403 that can be found in some of Marvell's SoC devices, such as
1404 the Kirkwood 88F6281 and 88F6192.
1406 This driver can also be built as a module. If so, the module
1407 will be called rtc-mv.
1409 config RTC_DRV_ARMADA38X
1410 tristate "Armada 38x Marvell SoC RTC"
1411 depends on ARCH_MVEBU
1413 If you say yes here you will get support for the in-chip RTC
1414 that can be found in the Armada 38x Marvell's SoC device
1416 This driver can also be built as a module. If so, the module
1417 will be called armada38x-rtc.
1419 config RTC_DRV_GEMINI
1420 tristate "Gemini SoC RTC"
1421 depends on ARCH_GEMINI || COMPILE_TEST
1422 depends on HAS_IOMEM
1424 If you say Y here you will get support for the
1425 RTC found on Gemini SoC's.
1427 This driver can also be built as a module. If so, the module
1428 will be called rtc-gemini.
1434 If you say yes here you will get support for the RTC on PS3.
1436 This driver can also be built as a module. If so, the module
1437 will be called rtc-ps3.
1439 config RTC_DRV_COH901331
1440 tristate "ST-Ericsson COH 901 331 RTC"
1441 depends on ARCH_U300
1443 If you say Y here you will get access to ST-Ericsson
1444 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1447 This driver can also be built as a module. If so, the module
1448 will be called "rtc-coh901331".
1452 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1456 If you say yes here you will get support for the onboard
1457 STMP3xxx/i.MX23/i.MX28 RTC.
1459 This driver can also be built as a module. If so, the module
1460 will be called rtc-stmp3xxx.
1466 If you say Y here you will get support for the RTC found on
1467 the PCAP2 ASIC used on some Motorola phones.
1469 config RTC_DRV_MC13XXX
1470 depends on MFD_MC13XXX
1471 tristate "Freescale MC13xxx RTC"
1473 This enables support for the RTCs found on Freescale's PMICs
1474 MC13783 and MC13892.
1476 config RTC_DRV_MPC5121
1477 tristate "Freescale MPC5121 built-in RTC"
1478 depends on PPC_MPC512x || PPC_MPC52xx
1480 If you say yes here you will get support for the
1481 built-in RTC on MPC5121 or on MPC5200.
1483 This driver can also be built as a module. If so, the module
1484 will be called rtc-mpc5121.
1486 config RTC_DRV_JZ4740
1487 tristate "Ingenic JZ4740 SoC"
1488 depends on MACH_JZ4740
1490 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1493 This driver can also be buillt as a module. If so, the module
1494 will be called rtc-jz4740.
1496 config RTC_DRV_LPC24XX
1497 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1498 depends on ARCH_LPC18XX || COMPILE_TEST
1499 depends on OF && HAS_IOMEM
1501 This enables support for the NXP RTC found which can be found on
1502 NXP LPC178x/18xx/408x/43xx devices.
1504 If you have one of the devices above enable this driver to use
1505 the hardware RTC. This driver can also be buillt as a module. If
1506 so, the module will be called rtc-lpc24xx.
1508 config RTC_DRV_LPC32XX
1509 depends on ARCH_LPC32XX
1510 tristate "NXP LPC32XX RTC"
1512 This enables support for the NXP RTC in the LPC32XX
1514 This driver can also be buillt as a module. If so, the module
1515 will be called rtc-lpc32xx.
1517 config RTC_DRV_PM8XXX
1518 tristate "Qualcomm PMIC8XXX RTC"
1519 depends on MFD_PM8XXX || MFD_SPMI_PMIC
1521 If you say yes here you get support for the
1522 Qualcomm PMIC8XXX RTC.
1524 To compile this driver as a module, choose M here: the
1525 module will be called rtc-pm8xxx.
1527 config RTC_DRV_TEGRA
1528 tristate "NVIDIA Tegra Internal RTC driver"
1529 depends on ARCH_TEGRA
1531 If you say yes here you get support for the
1532 Tegra 200 series internal RTC module.
1534 This drive can also be built as a module. If so, the module
1535 will be called rtc-tegra.
1538 tristate "Tilera hypervisor RTC support"
1541 Enable support for the Linux driver side of the Tilera
1542 hypervisor's real-time clock interface.
1545 tristate "PKUnity v3 RTC support"
1546 depends on ARCH_PUV3
1548 This enables support for the RTC in the PKUnity-v3 SoCs.
1550 This drive can also be built as a module. If so, the module
1551 will be called rtc-puv3.
1553 config RTC_DRV_LOONGSON1
1554 tristate "loongson1 RTC support"
1555 depends on MACH_LOONGSON32
1557 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1558 counter) to be used as a RTC.
1560 This driver can also be built as a module. If so, the module
1561 will be called rtc-ls1x.
1564 tristate "Freescale MXC Real Time Clock"
1567 If you say yes here you get support for the Freescale MXC
1570 This driver can also be built as a module, if so, the module
1571 will be called "rtc-mxc".
1574 tristate "Freescale SNVS RTC support"
1576 depends on HAS_IOMEM
1579 If you say yes here you get support for the Freescale SNVS
1580 Low Power (LP) RTC module.
1582 This driver can also be built as a module, if so, the module
1583 will be called "rtc-snvs".
1585 config RTC_DRV_SIRFSOC
1586 tristate "SiRFSOC RTC"
1587 depends on ARCH_SIRF
1589 Say "yes" here to support the real time clock on SiRF SOC chips.
1590 This driver can also be built as a module called rtc-sirfsoc.
1592 config RTC_DRV_ST_LPC
1593 tristate "STMicroelectronics LPC RTC"
1597 Say Y here to include STMicroelectronics Low Power Controller
1598 (LPC) based RTC support.
1600 To compile this driver as a module, choose M here: the
1601 module will be called rtc-st-lpc.
1603 config RTC_DRV_MOXART
1604 tristate "MOXA ART RTC"
1605 depends on ARCH_MOXART || COMPILE_TEST
1607 If you say yes here you get support for the MOXA ART
1610 This driver can also be built as a module. If so, the module
1611 will be called rtc-moxart
1613 config RTC_DRV_MT6397
1614 tristate "Mediatek Real Time Clock driver"
1615 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1617 This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
1618 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1619 Mediatek(R) RTC driver.
1621 If you want to use Mediatek(R) RTC interface, select Y or M here.
1623 config RTC_DRV_XGENE
1624 tristate "APM X-Gene RTC"
1625 depends on HAS_IOMEM
1626 depends on ARCH_XGENE || COMPILE_TEST
1628 If you say yes here you get support for the APM X-Gene SoC real time
1631 This driver can also be built as a module, if so, the module
1632 will be called "rtc-xgene".
1634 comment "HID Sensor RTC drivers"
1636 config RTC_DRV_HID_SENSOR_TIME
1637 tristate "HID Sensor Time"
1640 select HID_SENSOR_HUB
1641 select HID_SENSOR_IIO_COMMON
1643 Say yes here to build support for the HID Sensors of type Time.
1644 This drivers makes such sensors available as RTCs.
1646 If this driver is compiled as a module, it will be named
1647 rtc-hid-sensor-time.