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_AS3722
157 tristate "ams AS3722 RTC driver"
158 depends on MFD_AS3722
160 If you say yes here you get support for the RTC of ams AS3722 PMIC
163 This driver can also be built as a module. If so, the module
164 will be called rtc-as3722.
166 config RTC_DRV_DS1307
167 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
169 If you say yes here you get support for various compatible RTC
170 chips (often with battery backup) connected with I2C. This driver
171 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
172 EPSON RX-8025 and probably other chips. In some cases the RTC
173 must already have been initialized (by manufacturing or a
176 The first seven registers on these chips hold an RTC, and other
177 registers may add features such as NVRAM, a trickle charger for
178 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
179 sysfs, but other chip features may not be available.
181 This driver can also be built as a module. If so, the module
182 will be called rtc-ds1307.
184 config RTC_DRV_DS1374
185 tristate "Dallas/Maxim DS1374"
188 If you say yes here you get support for Dallas Semiconductor
189 DS1374 real-time clock chips. If an interrupt is associated
190 with the device, the alarm functionality is supported.
192 This driver can also be built as a module. If so, the module
193 will be called rtc-ds1374.
195 config RTC_DRV_DS1672
196 tristate "Dallas/Maxim DS1672"
198 If you say yes here you get support for the
199 Dallas/Maxim DS1672 timekeeping chip.
201 This driver can also be built as a module. If so, the module
202 will be called rtc-ds1672.
204 config RTC_DRV_DS3232
205 tristate "Dallas/Maxim DS3232"
208 If you say yes here you get support for Dallas Semiconductor
209 DS3232 real-time clock chips. If an interrupt is associated
210 with the device, the alarm functionality is supported.
212 This driver can also be built as a module. If so, the module
213 will be called rtc-ds3232.
215 config RTC_DRV_HYM8563
216 tristate "Haoyu Microelectronics HYM8563"
219 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
220 from the usual rtc functions it provides a clock output of
223 This driver can also be built as a module. If so, the module
224 will be called rtc-hym8563.
226 config RTC_DRV_LP8788
227 tristate "TI LP8788 RTC driver"
228 depends on MFD_LP8788
230 Say Y to enable support for the LP8788 RTC/ALARM driver.
232 config RTC_DRV_MAX6900
233 tristate "Maxim MAX6900"
235 If you say yes here you will get support for the
236 Maxim MAX6900 I2C RTC chip.
238 This driver can also be built as a module. If so, the module
239 will be called rtc-max6900.
241 config RTC_DRV_MAX8907
242 tristate "Maxim MAX8907"
243 depends on MFD_MAX8907
245 If you say yes here you will get support for the
246 RTC of Maxim MAX8907 PMIC.
248 This driver can also be built as a module. If so, the module
249 will be called rtc-max8907.
251 config RTC_DRV_MAX8925
252 tristate "Maxim MAX8925"
253 depends on MFD_MAX8925
255 If you say yes here you will get support for the
256 RTC of Maxim MAX8925 PMIC.
258 This driver can also be built as a module. If so, the module
259 will be called rtc-max8925.
261 config RTC_DRV_MAX8998
262 tristate "Maxim MAX8998"
263 depends on MFD_MAX8998
265 If you say yes here you will get support for the
266 RTC of Maxim MAX8998 PMIC.
268 This driver can also be built as a module. If so, the module
269 will be called rtc-max8998.
271 config RTC_DRV_MAX8997
272 tristate "Maxim MAX8997"
273 depends on MFD_MAX8997
275 If you say yes here you will get support for the
276 RTC of Maxim MAX8997 PMIC.
278 This driver can also be built as a module. If so, the module
279 will be called rtc-max8997.
281 config RTC_DRV_MAX77686
282 tristate "Maxim MAX77686"
283 depends on MFD_MAX77686
285 If you say yes here you will get support for the
286 RTC of Maxim MAX77686 PMIC.
288 This driver can also be built as a module. If so, the module
289 will be called rtc-max77686.
291 config RTC_DRV_RS5C372
292 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
294 If you say yes here you get support for the
295 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
297 This driver can also be built as a module. If so, the module
298 will be called rtc-rs5c372.
300 config RTC_DRV_ISL1208
301 tristate "Intersil ISL1208"
303 If you say yes here you get support for the
304 Intersil ISL1208 RTC chip.
306 This driver can also be built as a module. If so, the module
307 will be called rtc-isl1208.
309 config RTC_DRV_ISL12022
310 tristate "Intersil ISL12022"
312 If you say yes here you get support for the
313 Intersil ISL12022 RTC chip.
315 This driver can also be built as a module. If so, the module
316 will be called rtc-isl12022.
319 tristate "Xicor/Intersil X1205"
321 If you say yes here you get support for the
322 Xicor/Intersil X1205 RTC chip.
324 This driver can also be built as a module. If so, the module
325 will be called rtc-x1205.
327 config RTC_DRV_PALMAS
328 tristate "TI Palmas RTC driver"
329 depends on MFD_PALMAS
331 If you say yes here you get support for the RTC of TI PALMA series PMIC
334 This driver can also be built as a module. If so, the module
335 will be called rtc-palma.
337 config RTC_DRV_PCF2127
338 tristate "NXP PCF2127"
340 If you say yes here you get support for the NXP PCF2127/29 RTC
343 This driver can also be built as a module. If so, the module
344 will be called rtc-pcf2127.
346 config RTC_DRV_PCF8523
347 tristate "NXP PCF8523"
349 If you say yes here you get support for the NXP PCF8523 RTC
352 This driver can also be built as a module. If so, the module
353 will be called rtc-pcf8523.
355 config RTC_DRV_PCF8563
356 tristate "Philips PCF8563/Epson RTC8564"
358 If you say yes here you get support for the
359 Philips PCF8563 RTC chip. The Epson RTC8564
362 This driver can also be built as a module. If so, the module
363 will be called rtc-pcf8563.
365 config RTC_DRV_PCF8583
366 tristate "Philips PCF8583"
368 If you say yes here you get support for the Philips PCF8583
369 RTC chip found on Acorn RiscPCs. This driver supports the
370 platform specific method of retrieving the current year from
371 the RTC's SRAM. It will work on other platforms with the same
372 chip, but the year will probably have to be tweaked.
374 This driver can also be built as a module. If so, the module
375 will be called rtc-pcf8583.
377 config RTC_DRV_M41T80
378 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
380 If you say Y here you will get support for the ST M41T60
381 and M41T80 RTC chips series. Currently, the following chips are
382 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
383 M41ST85, and M41ST87.
385 This driver can also be built as a module. If so, the module
386 will be called rtc-m41t80.
388 config RTC_DRV_M41T80_WDT
389 bool "ST M41T65/M41T80 series RTC watchdog timer"
390 depends on RTC_DRV_M41T80
392 If you say Y here you will get support for the
393 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
396 tristate "TI BQ32000"
398 If you say Y here you will get support for the TI
399 BQ32000 I2C RTC chip.
401 This driver can also be built as a module. If so, the module
402 will be called rtc-bq32k.
404 config RTC_DRV_DM355EVM
405 tristate "TI DaVinci DM355 EVM RTC"
406 depends on MFD_DM355EVM_MSP
408 Supports the RTC firmware in the MSP430 on the DM355 EVM.
410 config RTC_DRV_TWL92330
411 boolean "TI TWL92330/Menelaus"
414 If you say yes here you get support for the RTC on the
415 TWL92330 "Menelaus" power management chip, used with OMAP2
416 platforms. The support is integrated with the rest of
417 the Menelaus driver; it's not separate module.
419 config RTC_DRV_TWL4030
420 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
421 depends on TWL4030_CORE
423 If you say yes here you get support for the RTC on the
424 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
426 This driver can also be built as a module. If so, the module
427 will be called rtc-twl.
429 config RTC_DRV_TPS6586X
430 tristate "TI TPS6586X RTC driver"
431 depends on MFD_TPS6586X
433 TI Power Management IC TPS6586X supports RTC functionality
434 along with alarm. This driver supports the RTC driver for
435 the TPS6586X RTC module.
437 config RTC_DRV_TPS65910
438 tristate "TI TPS65910 RTC driver"
439 depends on RTC_CLASS && MFD_TPS65910
441 If you say yes here you get support for the RTC on the
444 This driver can also be built as a module. If so, the module
445 will be called rtc-tps65910.
447 config RTC_DRV_TPS80031
448 tristate "TI TPS80031/TPS80032 RTC driver"
449 depends on MFD_TPS80031
451 TI Power Management IC TPS80031 supports RTC functionality
452 along with alarm. This driver supports the RTC driver for
453 the TPS80031 RTC module.
455 config RTC_DRV_RC5T583
456 tristate "RICOH 5T583 RTC driver"
457 depends on MFD_RC5T583
459 If you say yes here you get support for the RTC on the
462 This driver can also be built as a module. If so, the module
463 will be called rtc-rc5t583.
465 config RTC_DRV_S35390A
466 tristate "Seiko Instruments S-35390A"
469 If you say yes here you will get support for the Seiko
470 Instruments S-35390A.
472 This driver can also be built as a module. If so the module
473 will be called rtc-s35390a.
475 config RTC_DRV_FM3130
476 tristate "Ramtron FM3130"
478 If you say Y here you will get support for the
479 Ramtron FM3130 RTC chips.
480 Ramtron FM3130 is a chip with two separate devices inside,
481 RTC clock and FRAM. This driver provides only RTC functionality.
483 This driver can also be built as a module. If so the module
484 will be called rtc-fm3130.
486 config RTC_DRV_RX8581
487 tristate "Epson RX-8581"
489 If you say yes here you will get support for the Epson RX-8581.
491 This driver can also be built as a module. If so the module
492 will be called rtc-rx8581.
494 config RTC_DRV_RX8025
495 tristate "Epson RX-8025SA/NB"
497 If you say yes here you get support for the Epson
498 RX-8025SA/NB RTC chips.
500 This driver can also be built as a module. If so, the module
501 will be called rtc-rx8025.
503 config RTC_DRV_EM3027
504 tristate "EM Microelectronic EM3027"
506 If you say yes here you get support for the EM
507 Microelectronic EM3027 RTC chips.
509 This driver can also be built as a module. If so, the module
510 will be called rtc-em3027.
512 config RTC_DRV_RV3029C2
513 tristate "Micro Crystal RTC"
515 If you say yes here you get support for the Micro Crystal
518 This driver can also be built as a module. If so, the module
519 will be called rtc-rv3029c2.
522 tristate "Samsung S5M series"
523 depends on MFD_SEC_CORE
525 If you say yes here you will get support for the
526 RTC of Samsung S5M PMIC series.
528 This driver can also be built as a module. If so, the module
529 will be called rtc-s5m.
533 comment "SPI RTC drivers"
537 config RTC_DRV_M41T93
540 If you say yes here you will get support for the
541 ST M41T93 SPI RTC chip.
543 This driver can also be built as a module. If so, the module
544 will be called rtc-m41t93.
546 config RTC_DRV_M41T94
549 If you say yes here you will get support for the
550 ST M41T94 SPI RTC chip.
552 This driver can also be built as a module. If so, the module
553 will be called rtc-m41t94.
555 config RTC_DRV_DS1305
556 tristate "Dallas/Maxim DS1305/DS1306"
558 Select this driver to get support for the Dallas/Maxim DS1305
559 and DS1306 real time clock chips. These support a trickle
560 charger, alarms, and NVRAM in addition to the clock.
562 This driver can also be built as a module. If so, the module
563 will be called rtc-ds1305.
565 config RTC_DRV_DS1390
566 tristate "Dallas/Maxim DS1390/93/94"
568 If you say yes here you get support for the
569 Dallas/Maxim DS1390/93/94 chips.
571 This driver only supports the RTC feature, and not other chip
572 features such as alarms and trickle charging.
574 This driver can also be built as a module. If so, the module
575 will be called rtc-ds1390.
577 config RTC_DRV_MAX6902
578 tristate "Maxim MAX6902"
580 If you say yes here you will get support for the
581 Maxim MAX6902 SPI RTC chip.
583 This driver can also be built as a module. If so, the module
584 will be called rtc-max6902.
587 tristate "Epson RTC-9701JE"
589 If you say yes here you will get support for the
590 Epson RTC-9701JE SPI RTC chip.
592 This driver can also be built as a module. If so, the module
593 will be called rtc-r9701.
595 config RTC_DRV_RS5C348
596 tristate "Ricoh RS5C348A/B"
598 If you say yes here you get support for the
599 Ricoh RS5C348A and RS5C348B RTC chips.
601 This driver can also be built as a module. If so, the module
602 will be called rtc-rs5c348.
604 config RTC_DRV_DS3234
605 tristate "Maxim/Dallas DS3234"
607 If you say yes here you get support for the
608 Maxim/Dallas DS3234 SPI RTC chip.
610 This driver can also be built as a module. If so, the module
611 will be called rtc-ds3234.
613 config RTC_DRV_PCF2123
614 tristate "NXP PCF2123"
616 If you say yes here you get support for the NXP PCF2123
619 This driver can also be built as a module. If so, the module
620 will be called rtc-pcf2123.
622 config RTC_DRV_RX4581
623 tristate "Epson RX-4581"
625 If you say yes here you will get support for the Epson RX-4581.
627 This driver can also be built as a module. If so the module
628 will be called rtc-rx4581.
632 comment "Platform RTC drivers"
634 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
635 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
636 # global rtc_lock ... it's not yet just another platform_device.
639 tristate "PC-style 'CMOS'"
640 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
643 Say "yes" here to get direct support for the real time clock
644 found in every PC or ACPI-based system, and some other boards.
645 Specifically the original MC146818, compatibles like those in
646 PC south bridges, the DS12887 or M48T86, some multifunction
647 or LPC bus chips, and so on.
649 Your system will need to define the platform device used by
650 this driver, otherwise it won't be accessible. This means
651 you can safely enable this driver if you don't know whether
652 or not your board has this kind of hardware.
654 This driver can also be built as a module. If so, the module
655 will be called rtc-cmos.
658 bool "Alpha PC-style CMOS"
662 Direct support for the real-time clock found on every Alpha
663 system, specifically MC146818 compatibles. If in doubt, say Y.
666 tristate "Virtual RTC for Intel MID platforms"
667 depends on X86_INTEL_MID
668 default y if X86_INTEL_MID
671 Say "yes" here to get direct support for the real time clock
672 found on Moorestown platforms. The VRTC is a emulated RTC that
673 derives its clock source from a real RTC in the PMIC. The MC146818
674 style programming interface is mostly conserved, but any
675 updates are done via IPC calls to the system controller FW.
677 config RTC_DRV_DS1216
678 tristate "Dallas DS1216"
681 If you say yes here you get support for the Dallas DS1216 RTC chips.
683 config RTC_DRV_DS1286
684 tristate "Dallas DS1286"
686 If you say yes here you get support for the Dallas DS1286 RTC chips.
688 config RTC_DRV_DS1302
689 tristate "Dallas DS1302"
690 depends on SH_SECUREEDGE5410
692 If you say yes here you get support for the Dallas DS1302 RTC chips.
694 config RTC_DRV_DS1511
695 tristate "Dallas DS1511"
697 If you say yes here you get support for the
698 Dallas DS1511 timekeeping/watchdog chip.
700 This driver can also be built as a module. If so, the module
701 will be called rtc-ds1511.
703 config RTC_DRV_DS1553
704 tristate "Maxim/Dallas DS1553"
706 If you say yes here you get support for the
707 Maxim/Dallas DS1553 timekeeping chip.
709 This driver can also be built as a module. If so, the module
710 will be called rtc-ds1553.
712 config RTC_DRV_DS1742
713 tristate "Maxim/Dallas DS1742/1743"
715 If you say yes here you get support for the
716 Maxim/Dallas DS1742/1743 timekeeping chip.
718 This driver can also be built as a module. If so, the module
719 will be called rtc-ds1742.
721 config RTC_DRV_DA9052
722 tristate "Dialog DA9052/DA9053 RTC"
723 depends on PMIC_DA9052
725 Say y here to support the RTC driver for Dialog Semiconductor
726 DA9052-BC and DA9053-AA/Bx PMICs.
728 config RTC_DRV_DA9055
729 tristate "Dialog Semiconductor DA9055 RTC"
730 depends on MFD_DA9055
732 If you say yes here you will get support for the
733 RTC of the Dialog DA9055 PMIC.
735 This driver can also be built as a module. If so, the module
736 will be called rtc-da9055
742 If you say yes here you will get support for the EFI
745 This driver can also be built as a module. If so, the module
746 will be called rtc-efi.
748 config RTC_DRV_STK17TA8
749 tristate "Simtek STK17TA8"
751 If you say yes here you get support for the
752 Simtek STK17TA8 timekeeping chip.
754 This driver can also be built as a module. If so, the module
755 will be called rtc-stk17ta8.
757 config RTC_DRV_M48T86
758 tristate "ST M48T86/Dallas DS12887"
760 If you say Y here you will get support for the
761 ST M48T86 and Dallas DS12887 RTC chips.
763 This driver can also be built as a module. If so, the module
764 will be called rtc-m48t86.
766 config RTC_DRV_M48T35
769 If you say Y here you will get support for the
772 This driver can also be built as a module, if so, the module
773 will be called "rtc-m48t35".
775 config RTC_DRV_M48T59
776 tristate "ST M48T59/M48T08/M48T02"
778 If you say Y here you will get support for the
779 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
781 These chips are usually found in Sun SPARC and UltraSPARC
784 This driver can also be built as a module, if so, the module
785 will be called "rtc-m48t59".
787 config RTC_DRV_MSM6242
788 tristate "Oki MSM6242"
790 If you say yes here you get support for the Oki MSM6242
791 timekeeping chip. It is used in some Amiga models (e.g. A2000).
793 This driver can also be built as a module. If so, the module
794 will be called rtc-msm6242.
796 config RTC_DRV_BQ4802
799 If you say Y here you will get support for the TI
802 This driver can also be built as a module. If so, the module
803 will be called rtc-bq4802.
805 config RTC_DRV_RP5C01
806 tristate "Ricoh RP5C01"
808 If you say yes here you get support for the Ricoh RP5C01
809 timekeeping chip. It is used in some Amiga models (e.g. A3000
812 This driver can also be built as a module. If so, the module
813 will be called rtc-rp5c01.
816 tristate "EM Microelectronic V3020"
818 If you say yes here you will get support for the
819 EM Microelectronic v3020 RTC chip.
821 This driver can also be built as a module. If so, the module
822 will be called rtc-v3020.
824 config RTC_DRV_DS2404
825 tristate "Dallas DS2404"
827 If you say yes here you get support for the
828 Dallas DS2404 RTC chip.
830 This driver can also be built as a module. If so, the module
831 will be called rtc-ds2404.
833 config RTC_DRV_WM831X
834 tristate "Wolfson Microelectronics WM831x RTC"
835 depends on MFD_WM831X
837 If you say yes here you will get support for the RTC subsystem
838 of the Wolfson Microelectronics WM831X series PMICs.
840 This driver can also be built as a module. If so, the module
841 will be called "rtc-wm831x".
843 config RTC_DRV_WM8350
844 tristate "Wolfson Microelectronics WM8350 RTC"
845 depends on MFD_WM8350
847 If you say yes here you will get support for the RTC subsystem
848 of the Wolfson Microelectronics WM8350.
850 This driver can also be built as a module. If so, the module
851 will be called "rtc-wm8350".
854 tristate "SPEAR ST RTC"
855 depends on PLAT_SPEAR
858 If you say Y here you will get support for the RTC found on
861 config RTC_DRV_PCF50633
862 depends on MFD_PCF50633
863 tristate "NXP PCF50633 RTC"
865 If you say yes here you get support for the RTC subsystem of the
866 NXP PCF50633 used in embedded systems.
868 config RTC_DRV_AB3100
869 tristate "ST-Ericsson AB3100 RTC"
870 depends on AB3100_CORE
871 default y if AB3100_CORE
873 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
874 support. This chip contains a battery- and capacitor-backed RTC.
876 config RTC_DRV_AB8500
877 tristate "ST-Ericsson AB8500 RTC"
878 depends on AB8500_CORE
880 select RTC_INTF_DEV_UIE_EMUL
882 Select this to enable the ST-Ericsson AB8500 power management IC RTC
883 support. This chip contains a battery- and capacitor-backed RTC.
885 config RTC_DRV_NUC900
886 tristate "NUC910/NUC920 RTC driver"
887 depends on ARCH_W90X900
889 If you say yes here you get support for the RTC subsystem of the
890 NUC910/NUC920 used in embedded systems.
892 comment "on-CPU RTC drivers"
894 config RTC_DRV_DAVINCI
895 tristate "TI DaVinci RTC"
896 depends on ARCH_DAVINCI_DM365
898 If you say yes here you get support for the RTC on the
899 DaVinci platforms (DM365).
901 This driver can also be built as a module. If so, the module
902 will be called rtc-davinci.
905 tristate "Freescale IMX DryIce Real Time Clock"
908 Support for Freescale IMX DryIce RTC
910 This driver can also be built as a module, if so, the module
911 will be called "rtc-imxdi".
915 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
917 Say "yes" here to support the on chip real time clock
918 present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
920 This driver can also be built as a module, if so, module
921 will be called rtc-omap.
926 This will include RTC support for Samsung SoCs. If
927 you want to include RTC support for any machine, kindly
928 select this in the respective mach-XXXX/Kconfig file.
931 tristate "Samsung S3C series SoC RTC"
932 depends on ARCH_S3C64XX || HAVE_S3C_RTC
934 RTC (Realtime Clock) driver for the clock inbuilt into the
935 Samsung S3C24XX series of SoCs. This can provide periodic
936 interrupt rates from 1Hz to 64Hz for user programs, and
939 The driver currently supports the common features on all the
940 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
943 This driver can also be build as a module. If so, the module
944 will be called rtc-s3c.
946 config RTC_DRV_EP93XX
947 tristate "Cirrus Logic EP93XX"
948 depends on ARCH_EP93XX
950 If you say yes here you get support for the
951 RTC embedded in the Cirrus Logic EP93XX processors.
953 This driver can also be built as a module. If so, the module
954 will be called rtc-ep93xx.
956 config RTC_DRV_SA1100
957 tristate "SA11x0/PXA2xx/PXA910"
958 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
960 If you say Y here you will get access to the real time clock
961 built into your SA11x0 or PXA2xx CPU.
963 To compile this driver as a module, choose M here: the
964 module will be called rtc-sa1100.
967 tristate "SuperH On-Chip RTC"
968 depends on SUPERH && HAVE_CLK
970 Say Y here to enable support for the on-chip RTC found in
971 most SuperH processors.
973 To compile this driver as a module, choose M here: the
974 module will be called rtc-sh.
976 config RTC_DRV_VR41XX
977 tristate "NEC VR41XX"
978 depends on CPU_VR41XX
980 If you say Y here you will get access to the real time clock
981 built into your NEC VR41XX CPU.
983 To compile this driver as a module, choose M here: the
984 module will be called rtc-vr41xx.
987 tristate "ARM AMBA PL030 RTC"
990 If you say Y here you will get access to ARM AMBA
991 PrimeCell PL030 RTC found on certain ARM SOCs.
993 To compile this driver as a module, choose M here: the
994 module will be called rtc-pl030.
997 tristate "ARM AMBA PL031 RTC"
1000 If you say Y here you will get access to ARM AMBA
1001 PrimeCell PL031 RTC found on certain ARM SOCs.
1003 To compile this driver as a module, choose M here: the
1004 module will be called rtc-pl031.
1006 config RTC_DRV_AT32AP700X
1007 tristate "AT32AP700X series RTC"
1008 depends on PLATFORM_AT32AP
1010 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1011 AT32AP700x family processors.
1013 config RTC_DRV_AT91RM9200
1014 tristate "AT91RM9200 or some AT91SAM9 RTC"
1015 depends on ARCH_AT91
1017 Driver for the internal RTC (Realtime Clock) module found on
1018 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1019 this is powered by the backup power supply.
1021 config RTC_DRV_AT91SAM9
1022 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
1023 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
1025 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
1026 (Real Time Timer). These timers are powered by the backup power
1027 supply (such as a small coin cell battery), but do not need to
1030 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
1031 dedicated RTC module and leave the RTT available for other uses.)
1033 config RTC_DRV_AT91SAM9_RTT
1037 prompt "RTT module Number" if ARCH_AT91SAM9263
1038 depends on RTC_DRV_AT91SAM9
1040 More than one RTT module is available. You can choose which
1041 one will be used as an RTC. The default of zero is normally
1042 OK to use, though some systems use that for non-RTC purposes.
1044 config RTC_DRV_AT91SAM9_GPBR
1046 range 0 3 if !ARCH_AT91SAM9263
1047 range 0 15 if ARCH_AT91SAM9263
1049 prompt "Backup Register Number"
1050 depends on RTC_DRV_AT91SAM9
1052 The RTC driver needs to use one of the General Purpose Backup
1053 Registers (GPBRs) as well as the RTT. You can choose which one
1054 will be used. The default of zero is normally OK to use, but
1055 on some systems other software needs to use that register.
1057 config RTC_DRV_AU1XXX
1058 tristate "Au1xxx Counter0 RTC support"
1059 depends on MIPS_ALCHEMY
1061 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1062 counter) to be used as a RTC.
1064 This driver can also be built as a module. If so, the module
1065 will be called rtc-au1xxx.
1068 tristate "Blackfin On-Chip RTC"
1069 depends on BLACKFIN && !BF561
1071 If you say yes here you will get support for the
1072 Blackfin On-Chip Real Time Clock.
1074 This driver can also be built as a module. If so, the module
1075 will be called rtc-bfin.
1077 config RTC_DRV_RS5C313
1078 tristate "Ricoh RS5C313"
1079 depends on SH_LANDISK
1081 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1083 config RTC_DRV_GENERIC
1084 tristate "Generic RTC support"
1085 # Please consider writing a new RTC driver instead of using the generic
1087 depends on PARISC || M68K || PPC || SUPERH32
1089 Say Y or M here to enable RTC support on systems using the generic
1090 RTC abstraction. If you do not know what you are doing, you should
1094 tristate "PXA27x/PXA3xx"
1097 If you say Y here you will get access to the real time clock
1098 built into your PXA27x or PXA3xx CPU.
1100 This RTC driver uses PXA RTC registers available since pxa27x
1101 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1103 config RTC_DRV_VT8500
1104 tristate "VIA/WonderMedia 85xx SoC RTC"
1105 depends on ARCH_VT8500
1107 If you say Y here you will get access to the real time clock
1108 built into your VIA VT8500 SoC or its relatives.
1111 config RTC_DRV_SUN4V
1112 bool "SUN4V Hypervisor RTC"
1115 If you say Y here you will get support for the Hypervisor
1116 based RTC on SUN4V systems.
1118 config RTC_DRV_STARFIRE
1122 If you say Y here you will get support for the RTC found on
1125 config RTC_DRV_TX4939
1126 tristate "TX4939 SoC"
1127 depends on SOC_TX4939
1129 Driver for the internal RTC (Realtime Clock) module found on
1133 tristate "Marvell SoC RTC"
1134 depends on ARCH_KIRKWOOD || ARCH_DOVE || ARCH_MVEBU
1136 If you say yes here you will get support for the in-chip RTC
1137 that can be found in some of Marvell's SoC devices, such as
1138 the Kirkwood 88F6281 and 88F6192.
1140 This driver can also be built as a module. If so, the module
1141 will be called rtc-mv.
1147 If you say yes here you will get support for the RTC on PS3.
1149 This driver can also be built as a module. If so, the module
1150 will be called rtc-ps3.
1152 config RTC_DRV_COH901331
1153 tristate "ST-Ericsson COH 901 331 RTC"
1154 depends on ARCH_U300
1156 If you say Y here you will get access to ST-Ericsson
1157 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1160 This driver can also be built as a module. If so, the module
1161 will be called "rtc-coh901331".
1165 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1168 If you say yes here you will get support for the onboard
1169 STMP3xxx/i.MX23/i.MX28 RTC.
1171 This driver can also be built as a module. If so, the module
1172 will be called rtc-stmp3xxx.
1178 If you say Y here you will get support for the RTC found on
1179 the PCAP2 ASIC used on some Motorola phones.
1181 config RTC_DRV_MC13XXX
1182 depends on MFD_MC13XXX
1183 tristate "Freescale MC13xxx RTC"
1185 This enables support for the RTCs found on Freescale's PMICs
1186 MC13783 and MC13892.
1188 config RTC_DRV_MPC5121
1189 tristate "Freescale MPC5121 built-in RTC"
1190 depends on PPC_MPC512x || PPC_MPC52xx
1192 If you say yes here you will get support for the
1193 built-in RTC on MPC5121 or on MPC5200.
1195 This driver can also be built as a module. If so, the module
1196 will be called rtc-mpc5121.
1198 config RTC_DRV_JZ4740
1199 tristate "Ingenic JZ4740 SoC"
1200 depends on MACH_JZ4740
1202 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1205 This driver can also be buillt as a module. If so, the module
1206 will be called rtc-jz4740.
1208 config RTC_DRV_LPC32XX
1209 depends on ARCH_LPC32XX
1210 tristate "NXP LPC32XX RTC"
1212 This enables support for the NXP RTC in the LPC32XX
1214 This driver can also be buillt as a module. If so, the module
1215 will be called rtc-lpc32xx.
1217 config RTC_DRV_PM8XXX
1218 tristate "Qualcomm PMIC8XXX RTC"
1219 depends on MFD_PM8XXX
1221 If you say yes here you get support for the
1222 Qualcomm PMIC8XXX RTC.
1224 To compile this driver as a module, choose M here: the
1225 module will be called rtc-pm8xxx.
1227 config RTC_DRV_TEGRA
1228 tristate "NVIDIA Tegra Internal RTC driver"
1229 depends on ARCH_TEGRA
1231 If you say yes here you get support for the
1232 Tegra 200 series internal RTC module.
1234 This drive can also be built as a module. If so, the module
1235 will be called rtc-tegra.
1238 tristate "Tilera hypervisor RTC support"
1241 Enable support for the Linux driver side of the Tilera
1242 hypervisor's real-time clock interface.
1245 tristate "PKUnity v3 RTC support"
1246 depends on ARCH_PUV3
1248 This enables support for the RTC in the PKUnity-v3 SoCs.
1250 This drive can also be built as a module. If so, the module
1251 will be called rtc-puv3.
1253 config RTC_DRV_LOONGSON1
1254 tristate "loongson1 RTC support"
1255 depends on MACH_LOONGSON1
1257 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1258 counter) to be used as a RTC.
1260 This driver can also be built as a module. If so, the module
1261 will be called rtc-ls1x.
1264 tristate "Freescale MXC Real Time Clock"
1267 If you say yes here you get support for the Freescale MXC
1270 This driver can also be built as a module, if so, the module
1271 will be called "rtc-mxc".
1274 tristate "Freescale SNVS RTC support"
1275 depends on HAS_IOMEM
1278 If you say yes here you get support for the Freescale SNVS
1279 Low Power (LP) RTC module.
1281 This driver can also be built as a module, if so, the module
1282 will be called "rtc-snvs".
1284 config RTC_DRV_SIRFSOC
1285 tristate "SiRFSOC RTC"
1286 depends on ARCH_SIRF
1288 Say "yes" here to support the real time clock on SiRF SOC chips.
1289 This driver can also be built as a module called rtc-sirfsoc.
1291 config RTC_DRV_MOXART
1292 tristate "MOXA ART RTC"
1294 If you say yes here you get support for the MOXA ART
1297 This driver can also be built as a module. If so, the module
1298 will be called rtc-moxart
1300 comment "HID Sensor RTC drivers"
1302 config RTC_DRV_HID_SENSOR_TIME
1303 tristate "HID Sensor Time"
1306 select HID_SENSOR_HUB
1307 select HID_SENSOR_IIO_COMMON
1309 Say yes here to build support for the HID Sensors of type Time.
1310 This drivers makes such sensors available as RTCs.
1312 If this driver is compiled as a module, it will be named
1313 rtc-hid-sensor-time.