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.
29 bool "Set the RTC time based on NTP synchronization"
32 If you say yes here, the system time (wall clock) will be stored
33 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
34 minutes if userspace reports synchronized NTP status.
36 config RTC_HCTOSYS_DEVICE
37 string "RTC used to set the system time"
38 depends on RTC_HCTOSYS = y || RTC_SYSTOHC = y
41 The RTC device that will be used to (re)initialize the system
42 clock, usually rtc0. Initialization is done when the system
43 starts up, and when it resumes from a low power state. This
44 device should record time in UTC, since the kernel won't do
47 The driver for this RTC device must be loaded before late_initcall
48 functions run, so it must usually be statically linked.
50 This clock should be battery-backed, so that it reads the correct
51 time when the system boots from a power-off state. Otherwise, your
52 system will need an external clock source (like an NTP server).
54 If the clock you specify here is not battery backed, it may still
55 be useful to reinitialize system time when resuming from system
56 sleep states. Do not specify an RTC here unless it stays powered
57 during all this system's supported sleep states.
60 bool "RTC debug support"
62 Say yes here to enable debugging support in the RTC framework
63 and individual RTC drivers.
65 comment "RTC interfaces"
68 boolean "/sys/class/rtc/rtcN (sysfs)"
72 Say yes here if you want to use your RTCs using sysfs interfaces,
73 /sys/class/rtc/rtc0 through /sys/.../rtcN.
78 boolean "/proc/driver/rtc (procfs for rtcN)"
82 Say yes here if you want to use your system clock RTC through
83 the proc interface, /proc/driver/rtc.
84 Other RTCs will not be available through that API.
85 If there is no RTC for the system clock, then the first RTC(rtc0)
91 boolean "/dev/rtcN (character devices)"
94 Say yes here if you want to use your RTCs using the /dev
95 interfaces, which "udev" sets up as /dev/rtc0 through
98 You may want to set up a symbolic link so one of these
99 can be accessed as /dev/rtc, which is a name
100 expected by "hwclock" and some other programs. Recent
101 versions of "udev" are known to set up the symlink for you.
105 config RTC_INTF_DEV_UIE_EMUL
106 bool "RTC UIE emulation on dev interface"
107 depends on RTC_INTF_DEV
109 Provides an emulation for RTC_UIE if the underlying rtc chip
110 driver does not expose RTC_UIE ioctls. Those requests generate
111 once-per-second update interrupts, used for synchronization.
113 The emulation code will read the time from the hardware
114 clock several times per second, please enable this option
115 only if you know that you really need it.
118 tristate "Test driver/device"
120 If you say yes here you get support for the
121 RTC test driver. It's a software RTC which can be
122 used to test the RTC subsystem APIs. It gets
123 the time from the system clock.
124 You want this driver only if you are doing development
125 on the RTC subsystem. Please read the source code
128 This driver can also be built as a module. If so, the module
129 will be called rtc-test.
131 comment "I2C RTC drivers"
136 config RTC_DRV_88PM860X
137 tristate "Marvell 88PM860x"
138 depends on I2C && MFD_88PM860X
140 If you say yes here you get support for RTC function in Marvell
143 This driver can also be built as a module. If so, the module
144 will be called rtc-88pm860x.
146 config RTC_DRV_88PM80X
147 tristate "Marvell 88PM80x"
148 depends on I2C && MFD_88PM800
150 If you say yes here you get support for RTC function in Marvell
153 This driver can also be built as a module. If so, the module
154 will be called rtc-88pm80x.
156 config RTC_DRV_ABB5ZES3
159 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
161 If you say yes here you get support for the Abracon
162 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
164 This driver can also be built as a module. If so, the module
165 will be called rtc-ab-b5ze-s3.
167 config RTC_DRV_AS3722
168 tristate "ams AS3722 RTC driver"
169 depends on MFD_AS3722
171 If you say yes here you get support for the RTC of ams AS3722 PMIC
174 This driver can also be built as a module. If so, the module
175 will be called rtc-as3722.
177 config RTC_DRV_DS1307
178 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
180 If you say yes here you get support for various compatible RTC
181 chips (often with battery backup) connected with I2C. This driver
182 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
183 EPSON RX-8025 and probably other chips. In some cases the RTC
184 must already have been initialized (by manufacturing or a
187 The first seven registers on these chips hold an RTC, and other
188 registers may add features such as NVRAM, a trickle charger for
189 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
190 sysfs, but other chip features may not be available.
192 This driver can also be built as a module. If so, the module
193 will be called rtc-ds1307.
195 config RTC_DRV_DS1374
196 tristate "Dallas/Maxim DS1374"
199 If you say yes here you get support for Dallas Semiconductor
200 DS1374 real-time clock chips. If an interrupt is associated
201 with the device, the alarm functionality is supported.
203 This driver can also be built as a module. If so, the module
204 will be called rtc-ds1374.
206 config RTC_DRV_DS1374_WDT
207 bool "Dallas/Maxim DS1374 watchdog timer"
208 depends on RTC_DRV_DS1374
210 If you say Y here you will get support for the
211 watchdog timer in the Dallas Semiconductor DS1374
212 real-time clock chips.
214 config RTC_DRV_DS1672
215 tristate "Dallas/Maxim DS1672"
217 If you say yes here you get support for the
218 Dallas/Maxim DS1672 timekeeping chip.
220 This driver can also be built as a module. If so, the module
221 will be called rtc-ds1672.
223 config RTC_DRV_DS3232
224 tristate "Dallas/Maxim DS3232"
227 If you say yes here you get support for Dallas Semiconductor
228 DS3232 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-ds3232.
234 config RTC_DRV_HYM8563
235 tristate "Haoyu Microelectronics HYM8563"
238 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
239 from the usual rtc functions it provides a clock output of
242 This driver can also be built as a module. If so, the module
243 will be called rtc-hym8563.
245 config RTC_DRV_LP8788
246 tristate "TI LP8788 RTC driver"
247 depends on MFD_LP8788
249 Say Y to enable support for the LP8788 RTC/ALARM driver.
251 config RTC_DRV_MAX6900
252 tristate "Maxim MAX6900"
254 If you say yes here you will get support for the
255 Maxim MAX6900 I2C RTC chip.
257 This driver can also be built as a module. If so, the module
258 will be called rtc-max6900.
260 config RTC_DRV_MAX8907
261 tristate "Maxim MAX8907"
262 depends on MFD_MAX8907
264 If you say yes here you will get support for the
265 RTC of Maxim MAX8907 PMIC.
267 This driver can also be built as a module. If so, the module
268 will be called rtc-max8907.
270 config RTC_DRV_MAX8925
271 tristate "Maxim MAX8925"
272 depends on MFD_MAX8925
274 If you say yes here you will get support for the
275 RTC of Maxim MAX8925 PMIC.
277 This driver can also be built as a module. If so, the module
278 will be called rtc-max8925.
280 config RTC_DRV_MAX8998
281 tristate "Maxim MAX8998"
282 depends on MFD_MAX8998
284 If you say yes here you will get support for the
285 RTC of Maxim MAX8998 PMIC.
287 This driver can also be built as a module. If so, the module
288 will be called rtc-max8998.
290 config RTC_DRV_MAX8997
291 tristate "Maxim MAX8997"
292 depends on MFD_MAX8997
294 If you say yes here you will get support for the
295 RTC of Maxim MAX8997 PMIC.
297 This driver can also be built as a module. If so, the module
298 will be called rtc-max8997.
300 config RTC_DRV_MAX77686
301 tristate "Maxim MAX77686"
302 depends on MFD_MAX77686
304 If you say yes here you will get support for the
305 RTC of Maxim MAX77686 PMIC.
307 This driver can also be built as a module. If so, the module
308 will be called rtc-max77686.
311 tristate "Rockchip RK808 RTC"
314 If you say yes here you will get support for the
317 This driver can also be built as a module. If so, the module
318 will be called rk808-rtc.
320 config RTC_DRV_MAX77802
321 tristate "Maxim 77802 RTC"
322 depends on MFD_MAX77686
324 If you say yes here you will get support for the
325 RTC of Maxim MAX77802 PMIC.
327 This driver can also be built as a module. If so, the module
328 will be called rtc-max77802.
330 config RTC_DRV_RS5C372
331 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
333 If you say yes here you get support for the
334 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
336 This driver can also be built as a module. If so, the module
337 will be called rtc-rs5c372.
339 config RTC_DRV_ISL1208
340 tristate "Intersil ISL1208"
342 If you say yes here you get support for the
343 Intersil ISL1208 RTC chip.
345 This driver can also be built as a module. If so, the module
346 will be called rtc-isl1208.
348 config RTC_DRV_ISL12022
349 tristate "Intersil ISL12022"
351 If you say yes here you get support for the
352 Intersil ISL12022 RTC chip.
354 This driver can also be built as a module. If so, the module
355 will be called rtc-isl12022.
357 config RTC_DRV_ISL12057
360 tristate "Intersil ISL12057"
362 If you say yes here you get support for the Intersil ISL12057
365 This driver can also be built as a module. If so, the module
366 will be called rtc-isl12057.
369 tristate "Xicor/Intersil X1205"
371 If you say yes here you get support for the
372 Xicor/Intersil X1205 RTC chip.
374 This driver can also be built as a module. If so, the module
375 will be called rtc-x1205.
377 config RTC_DRV_PALMAS
378 tristate "TI Palmas RTC driver"
379 depends on MFD_PALMAS
381 If you say yes here you get support for the RTC of TI PALMA series PMIC
384 This driver can also be built as a module. If so, the module
385 will be called rtc-palma.
387 config RTC_DRV_PCF2127
388 tristate "NXP PCF2127"
390 If you say yes here you get support for the NXP PCF2127/29 RTC
393 This driver can also be built as a module. If so, the module
394 will be called rtc-pcf2127.
396 config RTC_DRV_PCF8523
397 tristate "NXP PCF8523"
399 If you say yes here you get support for the NXP PCF8523 RTC
402 This driver can also be built as a module. If so, the module
403 will be called rtc-pcf8523.
405 config RTC_DRV_PCF8563
406 tristate "Philips PCF8563/Epson RTC8564"
408 If you say yes here you get support for the
409 Philips PCF8563 RTC chip. The Epson RTC8564
412 This driver can also be built as a module. If so, the module
413 will be called rtc-pcf8563.
415 config RTC_DRV_PCF85063
416 tristate "nxp PCF85063"
418 If you say yes here you get support for the PCF85063 RTC chip
420 This driver can also be built as a module. If so, the module
421 will be called rtc-pcf85063.
423 config RTC_DRV_PCF8583
424 tristate "Philips PCF8583"
426 If you say yes here you get support for the Philips PCF8583
427 RTC chip found on Acorn RiscPCs. This driver supports the
428 platform specific method of retrieving the current year from
429 the RTC's SRAM. It will work on other platforms with the same
430 chip, but the year will probably have to be tweaked.
432 This driver can also be built as a module. If so, the module
433 will be called rtc-pcf8583.
435 config RTC_DRV_M41T80
436 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
438 If you say Y here you will get support for the ST M41T60
439 and M41T80 RTC chips series. Currently, the following chips are
440 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
441 M41ST85, M41ST87, and MicroCrystal RV4162.
443 This driver can also be built as a module. If so, the module
444 will be called rtc-m41t80.
446 config RTC_DRV_M41T80_WDT
447 bool "ST M41T65/M41T80 series RTC watchdog timer"
448 depends on RTC_DRV_M41T80
450 If you say Y here you will get support for the
451 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
454 tristate "TI BQ32000"
456 If you say Y here you will get support for the TI
457 BQ32000 I2C RTC chip.
459 This driver can also be built as a module. If so, the module
460 will be called rtc-bq32k.
462 config RTC_DRV_DM355EVM
463 tristate "TI DaVinci DM355 EVM RTC"
464 depends on MFD_DM355EVM_MSP
466 Supports the RTC firmware in the MSP430 on the DM355 EVM.
468 config RTC_DRV_TWL92330
469 boolean "TI TWL92330/Menelaus"
472 If you say yes here you get support for the RTC on the
473 TWL92330 "Menelaus" power management chip, used with OMAP2
474 platforms. The support is integrated with the rest of
475 the Menelaus driver; it's not separate module.
477 config RTC_DRV_TWL4030
478 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
479 depends on TWL4030_CORE
481 If you say yes here you get support for the RTC on the
482 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
484 This driver can also be built as a module. If so, the module
485 will be called rtc-twl.
487 config RTC_DRV_TPS6586X
488 tristate "TI TPS6586X RTC driver"
489 depends on MFD_TPS6586X
491 TI Power Management IC TPS6586X supports RTC functionality
492 along with alarm. This driver supports the RTC driver for
493 the TPS6586X RTC module.
495 config RTC_DRV_TPS65910
496 tristate "TI TPS65910 RTC driver"
497 depends on RTC_CLASS && MFD_TPS65910
499 If you say yes here you get support for the RTC on the
502 This driver can also be built as a module. If so, the module
503 will be called rtc-tps65910.
505 config RTC_DRV_TPS80031
506 tristate "TI TPS80031/TPS80032 RTC driver"
507 depends on MFD_TPS80031
509 TI Power Management IC TPS80031 supports RTC functionality
510 along with alarm. This driver supports the RTC driver for
511 the TPS80031 RTC module.
513 config RTC_DRV_RC5T583
514 tristate "RICOH 5T583 RTC driver"
515 depends on MFD_RC5T583
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-rc5t583.
523 config RTC_DRV_S35390A
524 tristate "Seiko Instruments S-35390A"
527 If you say yes here you will get support for the Seiko
528 Instruments S-35390A.
530 This driver can also be built as a module. If so the module
531 will be called rtc-s35390a.
533 config RTC_DRV_FM3130
534 tristate "Ramtron FM3130"
536 If you say Y here you will get support for the
537 Ramtron FM3130 RTC chips.
538 Ramtron FM3130 is a chip with two separate devices inside,
539 RTC clock and FRAM. This driver provides only RTC functionality.
541 This driver can also be built as a module. If so the module
542 will be called rtc-fm3130.
544 config RTC_DRV_RX8581
545 tristate "Epson RX-8581"
547 If you say yes here you will get support for the Epson RX-8581.
549 This driver can also be built as a module. If so the module
550 will be called rtc-rx8581.
552 config RTC_DRV_RX8025
553 tristate "Epson RX-8025SA/NB"
555 If you say yes here you get support for the Epson
556 RX-8025SA/NB RTC chips.
558 This driver can also be built as a module. If so, the module
559 will be called rtc-rx8025.
561 config RTC_DRV_EM3027
562 tristate "EM Microelectronic EM3027"
564 If you say yes here you get support for the EM
565 Microelectronic EM3027 RTC chips.
567 This driver can also be built as a module. If so, the module
568 will be called rtc-em3027.
570 config RTC_DRV_RV3029C2
571 tristate "Micro Crystal RTC"
573 If you say yes here you get support for the Micro Crystal
576 This driver can also be built as a module. If so, the module
577 will be called rtc-rv3029c2.
580 tristate "Samsung S2M/S5M series"
581 depends on MFD_SEC_CORE
583 If you say yes here you will get support for the
584 RTC of Samsung S2MPS14 and S5M PMIC series.
586 This driver can also be built as a module. If so, the module
587 will be called rtc-s5m.
591 comment "SPI RTC drivers"
595 config RTC_DRV_M41T93
598 If you say yes here you will get support for the
599 ST M41T93 SPI RTC chip.
601 This driver can also be built as a module. If so, the module
602 will be called rtc-m41t93.
604 config RTC_DRV_M41T94
607 If you say yes here you will get support for the
608 ST M41T94 SPI RTC chip.
610 This driver can also be built as a module. If so, the module
611 will be called rtc-m41t94.
613 config RTC_DRV_DS1305
614 tristate "Dallas/Maxim DS1305/DS1306"
616 Select this driver to get support for the Dallas/Maxim DS1305
617 and DS1306 real time clock chips. These support a trickle
618 charger, alarms, and NVRAM in addition to the clock.
620 This driver can also be built as a module. If so, the module
621 will be called rtc-ds1305.
623 config RTC_DRV_DS1343
625 tristate "Dallas/Maxim DS1343/DS1344"
627 If you say yes here you get support for the
628 Dallas/Maxim DS1343 and DS1344 real time clock chips.
629 Support for trickle charger, alarm is provided.
631 This driver can also be built as a module. If so, the module
632 will be called rtc-ds1343.
634 config RTC_DRV_DS1347
635 tristate "Dallas/Maxim DS1347"
637 If you say yes here you get support for the
638 Dallas/Maxim DS1347 chips.
640 This driver only supports the RTC feature, and not other chip
641 features such as alarms.
643 This driver can also be built as a module. If so, the module
644 will be called rtc-ds1347.
646 config RTC_DRV_DS1390
647 tristate "Dallas/Maxim DS1390/93/94"
649 If you say yes here you get support for the
650 Dallas/Maxim DS1390/93/94 chips.
652 This driver only supports the RTC feature, and not other chip
653 features such as alarms and trickle charging.
655 This driver can also be built as a module. If so, the module
656 will be called rtc-ds1390.
658 config RTC_DRV_MAX6902
659 tristate "Maxim MAX6902"
661 If you say yes here you will get support for the
662 Maxim MAX6902 SPI RTC chip.
664 This driver can also be built as a module. If so, the module
665 will be called rtc-max6902.
668 tristate "Epson RTC-9701JE"
670 If you say yes here you will get support for the
671 Epson RTC-9701JE SPI RTC chip.
673 This driver can also be built as a module. If so, the module
674 will be called rtc-r9701.
676 config RTC_DRV_RS5C348
677 tristate "Ricoh RS5C348A/B"
679 If you say yes here you get support for the
680 Ricoh RS5C348A and RS5C348B RTC chips.
682 This driver can also be built as a module. If so, the module
683 will be called rtc-rs5c348.
685 config RTC_DRV_DS3234
686 tristate "Maxim/Dallas DS3234"
688 If you say yes here you get support for the
689 Maxim/Dallas DS3234 SPI RTC chip.
691 This driver can also be built as a module. If so, the module
692 will be called rtc-ds3234.
694 config RTC_DRV_PCF2123
695 tristate "NXP PCF2123"
697 If you say yes here you get support for the NXP PCF2123
700 This driver can also be built as a module. If so, the module
701 will be called rtc-pcf2123.
703 config RTC_DRV_RX4581
704 tristate "Epson RX-4581"
706 If you say yes here you will get support for the Epson RX-4581.
708 This driver can also be built as a module. If so the module
709 will be called rtc-rx4581.
711 config RTC_DRV_MCP795
712 tristate "Microchip MCP795"
714 If you say yes here you will get support for the Microchip MCP795.
716 This driver can also be built as a module. If so the module
717 will be called rtc-mcp795.
721 comment "Platform RTC drivers"
723 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
724 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
725 # global rtc_lock ... it's not yet just another platform_device.
728 tristate "PC-style 'CMOS'"
729 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
732 Say "yes" here to get direct support for the real time clock
733 found in every PC or ACPI-based system, and some other boards.
734 Specifically the original MC146818, compatibles like those in
735 PC south bridges, the DS12887 or M48T86, some multifunction
736 or LPC bus chips, and so on.
738 Your system will need to define the platform device used by
739 this driver, otherwise it won't be accessible. This means
740 you can safely enable this driver if you don't know whether
741 or not your board has this kind of hardware.
743 This driver can also be built as a module. If so, the module
744 will be called rtc-cmos.
747 bool "Alpha PC-style CMOS"
751 Direct support for the real-time clock found on every Alpha
752 system, specifically MC146818 compatibles. If in doubt, say Y.
755 tristate "Virtual RTC for Intel MID platforms"
756 depends on X86_INTEL_MID
757 default y if X86_INTEL_MID
760 Say "yes" here to get direct support for the real time clock
761 found on Moorestown platforms. The VRTC is a emulated RTC that
762 derives its clock source from a real RTC in the PMIC. The MC146818
763 style programming interface is mostly conserved, but any
764 updates are done via IPC calls to the system controller FW.
766 config RTC_DRV_DS1216
767 tristate "Dallas DS1216"
770 If you say yes here you get support for the Dallas DS1216 RTC chips.
772 config RTC_DRV_DS1286
773 tristate "Dallas DS1286"
776 If you say yes here you get support for the Dallas DS1286 RTC chips.
778 config RTC_DRV_DS1302
779 tristate "Dallas DS1302"
780 depends on SH_SECUREEDGE5410
782 If you say yes here you get support for the Dallas DS1302 RTC chips.
784 config RTC_DRV_DS1511
785 tristate "Dallas DS1511"
788 If you say yes here you get support for the
789 Dallas DS1511 timekeeping/watchdog chip.
791 This driver can also be built as a module. If so, the module
792 will be called rtc-ds1511.
794 config RTC_DRV_DS1553
795 tristate "Maxim/Dallas DS1553"
798 If you say yes here you get support for the
799 Maxim/Dallas DS1553 timekeeping chip.
801 This driver can also be built as a module. If so, the module
802 will be called rtc-ds1553.
804 config RTC_DRV_DS1742
805 tristate "Maxim/Dallas DS1742/1743"
808 If you say yes here you get support for the
809 Maxim/Dallas DS1742/1743 timekeeping chip.
811 This driver can also be built as a module. If so, the module
812 will be called rtc-ds1742.
814 config RTC_DRV_DS2404
815 tristate "Maxim/Dallas DS2404"
817 If you say yes here you get support for the
818 Dallas DS2404 RTC chip.
820 This driver can also be built as a module. If so, the module
821 will be called rtc-ds2404.
823 config RTC_DRV_DA9052
824 tristate "Dialog DA9052/DA9053 RTC"
825 depends on PMIC_DA9052
827 Say y here to support the RTC driver for Dialog Semiconductor
828 DA9052-BC and DA9053-AA/Bx PMICs.
830 config RTC_DRV_DA9055
831 tristate "Dialog Semiconductor DA9055 RTC"
832 depends on MFD_DA9055
834 If you say yes here you will get support for the
835 RTC of the Dialog DA9055 PMIC.
837 This driver can also be built as a module. If so, the module
838 will be called rtc-da9055
840 config RTC_DRV_DA9063
841 tristate "Dialog Semiconductor DA9063 RTC"
842 depends on MFD_DA9063
844 If you say yes here you will get support for the RTC subsystem
845 of the Dialog Semiconductor DA9063.
847 This driver can also be built as a module. If so, the module
848 will be called "rtc-da9063".
852 depends on EFI && !X86
854 If you say yes here you will get support for the EFI
857 This driver can also be built as a module. If so, the module
858 will be called rtc-efi.
860 config RTC_DRV_STK17TA8
861 tristate "Simtek STK17TA8"
864 If you say yes here you get support for the
865 Simtek STK17TA8 timekeeping chip.
867 This driver can also be built as a module. If so, the module
868 will be called rtc-stk17ta8.
870 config RTC_DRV_M48T86
871 tristate "ST M48T86/Dallas DS12887"
873 If you say Y here you will get support for the
874 ST M48T86 and Dallas DS12887 RTC chips.
876 This driver can also be built as a module. If so, the module
877 will be called rtc-m48t86.
879 config RTC_DRV_M48T35
883 If you say Y here you will get support for the
886 This driver can also be built as a module, if so, the module
887 will be called "rtc-m48t35".
889 config RTC_DRV_M48T59
890 tristate "ST M48T59/M48T08/M48T02"
893 If you say Y here you will get support for the
894 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
896 These chips are usually found in Sun SPARC and UltraSPARC
899 This driver can also be built as a module, if so, the module
900 will be called "rtc-m48t59".
902 config RTC_DRV_MSM6242
903 tristate "Oki MSM6242"
906 If you say yes here you get support for the Oki MSM6242
907 timekeeping chip. It is used in some Amiga models (e.g. A2000).
909 This driver can also be built as a module. If so, the module
910 will be called rtc-msm6242.
912 config RTC_DRV_BQ4802
916 If you say Y here you will get support for the TI
919 This driver can also be built as a module. If so, the module
920 will be called rtc-bq4802.
922 config RTC_DRV_RP5C01
923 tristate "Ricoh RP5C01"
926 If you say yes here you get support for the Ricoh RP5C01
927 timekeeping chip. It is used in some Amiga models (e.g. A3000
930 This driver can also be built as a module. If so, the module
931 will be called rtc-rp5c01.
934 tristate "EM Microelectronic V3020"
936 If you say yes here you will get support for the
937 EM Microelectronic v3020 RTC chip.
939 This driver can also be built as a module. If so, the module
940 will be called rtc-v3020.
942 config RTC_DRV_WM831X
943 tristate "Wolfson Microelectronics WM831x RTC"
944 depends on MFD_WM831X
946 If you say yes here you will get support for the RTC subsystem
947 of the Wolfson Microelectronics WM831X series PMICs.
949 This driver can also be built as a module. If so, the module
950 will be called "rtc-wm831x".
952 config RTC_DRV_WM8350
953 tristate "Wolfson Microelectronics WM8350 RTC"
954 depends on MFD_WM8350
956 If you say yes here you will get support for the RTC subsystem
957 of the Wolfson Microelectronics WM8350.
959 This driver can also be built as a module. If so, the module
960 will be called "rtc-wm8350".
963 tristate "SPEAR ST RTC"
964 depends on PLAT_SPEAR
967 If you say Y here you will get support for the RTC found on
970 config RTC_DRV_PCF50633
971 depends on MFD_PCF50633
972 tristate "NXP PCF50633 RTC"
974 If you say yes here you get support for the RTC subsystem of the
975 NXP PCF50633 used in embedded systems.
977 config RTC_DRV_AB3100
978 tristate "ST-Ericsson AB3100 RTC"
979 depends on AB3100_CORE
980 default y if AB3100_CORE
982 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
983 support. This chip contains a battery- and capacitor-backed RTC.
985 config RTC_DRV_AB8500
986 tristate "ST-Ericsson AB8500 RTC"
987 depends on AB8500_CORE
989 select RTC_INTF_DEV_UIE_EMUL
991 Select this to enable the ST-Ericsson AB8500 power management IC RTC
992 support. This chip contains a battery- and capacitor-backed RTC.
994 config RTC_DRV_NUC900
995 tristate "NUC910/NUC920 RTC driver"
996 depends on ARCH_W90X900
998 If you say yes here you get support for the RTC subsystem of the
999 NUC910/NUC920 used in embedded systems.
1002 tristate "IBM OPAL RTC driver"
1003 depends on PPC_POWERNV
1006 If you say yes here you get support for the PowerNV platform RTC
1007 driver based on OPAL interfaces.
1009 This driver can also be built as a module. If so, the module
1010 will be called rtc-opal.
1012 comment "on-CPU RTC drivers"
1014 config RTC_DRV_DAVINCI
1015 tristate "TI DaVinci RTC"
1016 depends on ARCH_DAVINCI_DM365
1018 If you say yes here you get support for the RTC on the
1019 DaVinci platforms (DM365).
1021 This driver can also be built as a module. If so, the module
1022 will be called rtc-davinci.
1024 config RTC_DRV_IMXDI
1025 tristate "Freescale IMX DryIce Real Time Clock"
1028 Support for Freescale IMX DryIce RTC
1030 This driver can also be built as a module, if so, the module
1031 will be called "rtc-imxdi".
1035 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
1037 Say "yes" here to support the on chip real time clock
1038 present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
1040 This driver can also be built as a module, if so, module
1041 will be called rtc-omap.
1046 This will include RTC support for Samsung SoCs. If
1047 you want to include RTC support for any machine, kindly
1048 select this in the respective mach-XXXX/Kconfig file.
1051 tristate "Samsung S3C series SoC RTC"
1052 depends on ARCH_S3C64XX || HAVE_S3C_RTC
1054 RTC (Realtime Clock) driver for the clock inbuilt into the
1055 Samsung S3C24XX series of SoCs. This can provide periodic
1056 interrupt rates from 1Hz to 64Hz for user programs, and
1059 The driver currently supports the common features on all the
1060 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1063 This driver can also be build as a module. If so, the module
1064 will be called rtc-s3c.
1066 config RTC_DRV_EP93XX
1067 tristate "Cirrus Logic EP93XX"
1068 depends on ARCH_EP93XX
1070 If you say yes here you get support for the
1071 RTC embedded in the Cirrus Logic EP93XX processors.
1073 This driver can also be built as a module. If so, the module
1074 will be called rtc-ep93xx.
1076 config RTC_DRV_SA1100
1077 tristate "SA11x0/PXA2xx/PXA910"
1078 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1080 If you say Y here you will get access to the real time clock
1081 built into your SA11x0 or PXA2xx CPU.
1083 To compile this driver as a module, choose M here: the
1084 module will be called rtc-sa1100.
1087 tristate "SuperH On-Chip RTC"
1088 depends on SUPERH && HAVE_CLK
1090 Say Y here to enable support for the on-chip RTC found in
1091 most SuperH processors.
1093 To compile this driver as a module, choose M here: the
1094 module will be called rtc-sh.
1096 config RTC_DRV_VR41XX
1097 tristate "NEC VR41XX"
1098 depends on CPU_VR41XX
1100 If you say Y here you will get access to the real time clock
1101 built into your NEC VR41XX CPU.
1103 To compile this driver as a module, choose M here: the
1104 module will be called rtc-vr41xx.
1106 config RTC_DRV_PL030
1107 tristate "ARM AMBA PL030 RTC"
1110 If you say Y here you will get access to ARM AMBA
1111 PrimeCell PL030 RTC found on certain ARM SOCs.
1113 To compile this driver as a module, choose M here: the
1114 module will be called rtc-pl030.
1116 config RTC_DRV_PL031
1117 tristate "ARM AMBA PL031 RTC"
1120 If you say Y here you will get access to ARM AMBA
1121 PrimeCell PL031 RTC found on certain ARM SOCs.
1123 To compile this driver as a module, choose M here: the
1124 module will be called rtc-pl031.
1126 config RTC_DRV_AT32AP700X
1127 tristate "AT32AP700X series RTC"
1128 depends on PLATFORM_AT32AP
1130 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1131 AT32AP700x family processors.
1133 config RTC_DRV_AT91RM9200
1134 tristate "AT91RM9200 or some AT91SAM9 RTC"
1135 depends on ARCH_AT91
1137 Driver for the internal RTC (Realtime Clock) module found on
1138 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1139 this is powered by the backup power supply.
1141 config RTC_DRV_AT91SAM9
1142 tristate "AT91SAM9 RTT as RTC"
1143 depends on ARCH_AT91
1146 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1147 can be used as an RTC thanks to the backup power supply (e.g. a
1148 small coin cell battery) which keeps this block and the GPBR
1149 (General Purpose Backup Registers) block powered when the device
1151 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1152 probably want to use the real RTC block instead of the "RTT as an
1155 config RTC_DRV_AT91SAM9_RTT
1159 depends on RTC_DRV_AT91SAM9
1161 This option is only relevant for legacy board support and
1162 won't be used when booting a DT board.
1164 More than one RTT module is available. You can choose which
1165 one will be used as an RTC. The default of zero is normally
1166 OK to use, though some systems use that for non-RTC purposes.
1168 config RTC_DRV_AT91SAM9_GPBR
1172 prompt "Backup Register Number"
1173 depends on RTC_DRV_AT91SAM9
1175 This option is only relevant for legacy board support and
1176 won't be used when booting a DT board.
1178 The RTC driver needs to use one of the General Purpose Backup
1179 Registers (GPBRs) as well as the RTT. You can choose which one
1180 will be used. The default of zero is normally OK to use, but
1181 on some systems other software needs to use that register.
1183 config RTC_DRV_AU1XXX
1184 tristate "Au1xxx Counter0 RTC support"
1185 depends on MIPS_ALCHEMY
1187 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1188 counter) to be used as a RTC.
1190 This driver can also be built as a module. If so, the module
1191 will be called rtc-au1xxx.
1194 tristate "Blackfin On-Chip RTC"
1195 depends on BLACKFIN && !BF561
1197 If you say yes here you will get support for the
1198 Blackfin On-Chip Real Time Clock.
1200 This driver can also be built as a module. If so, the module
1201 will be called rtc-bfin.
1203 config RTC_DRV_RS5C313
1204 tristate "Ricoh RS5C313"
1205 depends on SH_LANDISK
1207 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1209 config RTC_DRV_GENERIC
1210 tristate "Generic RTC support"
1211 # Please consider writing a new RTC driver instead of using the generic
1213 depends on PARISC || M68K || PPC || SUPERH32
1215 Say Y or M here to enable RTC support on systems using the generic
1216 RTC abstraction. If you do not know what you are doing, you should
1220 tristate "PXA27x/PXA3xx"
1223 If you say Y here you will get access to the real time clock
1224 built into your PXA27x or PXA3xx CPU.
1226 This RTC driver uses PXA RTC registers available since pxa27x
1227 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1229 config RTC_DRV_VT8500
1230 tristate "VIA/WonderMedia 85xx SoC RTC"
1231 depends on ARCH_VT8500
1233 If you say Y here you will get access to the real time clock
1234 built into your VIA VT8500 SoC or its relatives.
1237 config RTC_DRV_SUN4V
1238 bool "SUN4V Hypervisor RTC"
1241 If you say Y here you will get support for the Hypervisor
1242 based RTC on SUN4V systems.
1244 config RTC_DRV_SUN6I
1245 tristate "Allwinner A31 RTC"
1246 depends on MACH_SUN6I || MACH_SUN8I
1248 If you say Y here you will get support for the RTC found on
1251 config RTC_DRV_SUNXI
1252 tristate "Allwinner sun4i/sun7i RTC"
1253 depends on MACH_SUN4I || MACH_SUN7I
1255 If you say Y here you will get support for the RTC found on
1258 config RTC_DRV_STARFIRE
1262 If you say Y here you will get support for the RTC found on
1265 config RTC_DRV_TX4939
1266 tristate "TX4939 SoC"
1267 depends on SOC_TX4939
1269 Driver for the internal RTC (Realtime Clock) module found on
1273 tristate "Marvell SoC RTC"
1274 depends on ARCH_DOVE || ARCH_MVEBU
1276 If you say yes here you will get support for the in-chip RTC
1277 that can be found in some of Marvell's SoC devices, such as
1278 the Kirkwood 88F6281 and 88F6192.
1280 This driver can also be built as a module. If so, the module
1281 will be called rtc-mv.
1283 config RTC_DRV_ARMADA38X
1284 tristate "Armada 38x Marvell SoC RTC"
1285 depends on ARCH_MVEBU
1287 If you say yes here you will get support for the in-chip RTC
1288 that can be found in the Armada 38x Marvell's SoC device
1290 This driver can also be built as a module. If so, the module
1291 will be called armada38x-rtc.
1297 If you say yes here you will get support for the RTC on PS3.
1299 This driver can also be built as a module. If so, the module
1300 will be called rtc-ps3.
1302 config RTC_DRV_COH901331
1303 tristate "ST-Ericsson COH 901 331 RTC"
1304 depends on ARCH_U300
1306 If you say Y here you will get access to ST-Ericsson
1307 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1310 This driver can also be built as a module. If so, the module
1311 will be called "rtc-coh901331".
1315 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1318 If you say yes here you will get support for the onboard
1319 STMP3xxx/i.MX23/i.MX28 RTC.
1321 This driver can also be built as a module. If so, the module
1322 will be called rtc-stmp3xxx.
1328 If you say Y here you will get support for the RTC found on
1329 the PCAP2 ASIC used on some Motorola phones.
1331 config RTC_DRV_MC13XXX
1332 depends on MFD_MC13XXX
1333 tristate "Freescale MC13xxx RTC"
1335 This enables support for the RTCs found on Freescale's PMICs
1336 MC13783 and MC13892.
1338 config RTC_DRV_MPC5121
1339 tristate "Freescale MPC5121 built-in RTC"
1340 depends on PPC_MPC512x || PPC_MPC52xx
1342 If you say yes here you will get support for the
1343 built-in RTC on MPC5121 or on MPC5200.
1345 This driver can also be built as a module. If so, the module
1346 will be called rtc-mpc5121.
1348 config RTC_DRV_JZ4740
1349 tristate "Ingenic JZ4740 SoC"
1350 depends on MACH_JZ4740
1352 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1355 This driver can also be buillt as a module. If so, the module
1356 will be called rtc-jz4740.
1358 config RTC_DRV_LPC32XX
1359 depends on ARCH_LPC32XX
1360 tristate "NXP LPC32XX RTC"
1362 This enables support for the NXP RTC in the LPC32XX
1364 This driver can also be buillt as a module. If so, the module
1365 will be called rtc-lpc32xx.
1367 config RTC_DRV_PM8XXX
1368 tristate "Qualcomm PMIC8XXX RTC"
1369 depends on MFD_PM8XXX || MFD_SPMI_PMIC
1371 If you say yes here you get support for the
1372 Qualcomm PMIC8XXX RTC.
1374 To compile this driver as a module, choose M here: the
1375 module will be called rtc-pm8xxx.
1377 config RTC_DRV_TEGRA
1378 tristate "NVIDIA Tegra Internal RTC driver"
1379 depends on ARCH_TEGRA
1381 If you say yes here you get support for the
1382 Tegra 200 series internal RTC module.
1384 This drive can also be built as a module. If so, the module
1385 will be called rtc-tegra.
1388 tristate "Tilera hypervisor RTC support"
1391 Enable support for the Linux driver side of the Tilera
1392 hypervisor's real-time clock interface.
1395 tristate "PKUnity v3 RTC support"
1396 depends on ARCH_PUV3
1398 This enables support for the RTC in the PKUnity-v3 SoCs.
1400 This drive can also be built as a module. If so, the module
1401 will be called rtc-puv3.
1403 config RTC_DRV_LOONGSON1
1404 tristate "loongson1 RTC support"
1405 depends on MACH_LOONGSON1
1407 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1408 counter) to be used as a RTC.
1410 This driver can also be built as a module. If so, the module
1411 will be called rtc-ls1x.
1414 tristate "Freescale MXC Real Time Clock"
1417 If you say yes here you get support for the Freescale MXC
1420 This driver can also be built as a module, if so, the module
1421 will be called "rtc-mxc".
1424 tristate "Freescale SNVS RTC support"
1425 depends on HAS_IOMEM
1428 If you say yes here you get support for the Freescale SNVS
1429 Low Power (LP) RTC module.
1431 This driver can also be built as a module, if so, the module
1432 will be called "rtc-snvs".
1434 config RTC_DRV_SIRFSOC
1435 tristate "SiRFSOC RTC"
1436 depends on ARCH_SIRF
1438 Say "yes" here to support the real time clock on SiRF SOC chips.
1439 This driver can also be built as a module called rtc-sirfsoc.
1441 config RTC_DRV_MOXART
1442 tristate "MOXA ART RTC"
1443 depends on ARCH_MOXART || COMPILE_TEST
1445 If you say yes here you get support for the MOXA ART
1448 This driver can also be built as a module. If so, the module
1449 will be called rtc-moxart
1451 config RTC_DRV_XGENE
1452 tristate "APM X-Gene RTC"
1453 depends on HAS_IOMEM
1455 If you say yes here you get support for the APM X-Gene SoC real time
1458 This driver can also be built as a module, if so, the module
1459 will be called "rtc-xgene".
1461 comment "HID Sensor RTC drivers"
1463 config RTC_DRV_HID_SENSOR_TIME
1464 tristate "HID Sensor Time"
1467 select HID_SENSOR_HUB
1468 select HID_SENSOR_IIO_COMMON
1470 Say yes here to build support for the HID Sensors of type Time.
1471 This drivers makes such sensors available as RTCs.
1473 If this driver is compiled as a module, it will be named
1474 rtc-hid-sensor-time.