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.
292 tristate "Rockchip RK808 RTC"
295 If you say yes here you will get support for the
298 This driver can also be built as a module. If so, the module
299 will be called rk808-rtc.
301 config RTC_DRV_RS5C372
302 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
304 If you say yes here you get support for the
305 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
307 This driver can also be built as a module. If so, the module
308 will be called rtc-rs5c372.
310 config RTC_DRV_ISL1208
311 tristate "Intersil ISL1208"
313 If you say yes here you get support for the
314 Intersil ISL1208 RTC chip.
316 This driver can also be built as a module. If so, the module
317 will be called rtc-isl1208.
319 config RTC_DRV_ISL12022
320 tristate "Intersil ISL12022"
322 If you say yes here you get support for the
323 Intersil ISL12022 RTC chip.
325 This driver can also be built as a module. If so, the module
326 will be called rtc-isl12022.
328 config RTC_DRV_ISL12057
331 tristate "Intersil ISL12057"
333 If you say yes here you get support for the Intersil ISL12057
336 This driver can also be built as a module. If so, the module
337 will be called rtc-isl12057.
340 tristate "Xicor/Intersil X1205"
342 If you say yes here you get support for the
343 Xicor/Intersil X1205 RTC chip.
345 This driver can also be built as a module. If so, the module
346 will be called rtc-x1205.
348 config RTC_DRV_PALMAS
349 tristate "TI Palmas RTC driver"
350 depends on MFD_PALMAS
352 If you say yes here you get support for the RTC of TI PALMA series PMIC
355 This driver can also be built as a module. If so, the module
356 will be called rtc-palma.
358 config RTC_DRV_PCF2127
359 tristate "NXP PCF2127"
361 If you say yes here you get support for the NXP PCF2127/29 RTC
364 This driver can also be built as a module. If so, the module
365 will be called rtc-pcf2127.
367 config RTC_DRV_PCF8523
368 tristate "NXP PCF8523"
370 If you say yes here you get support for the NXP PCF8523 RTC
373 This driver can also be built as a module. If so, the module
374 will be called rtc-pcf8523.
376 config RTC_DRV_PCF8563
377 tristate "Philips PCF8563/Epson RTC8564"
379 If you say yes here you get support for the
380 Philips PCF8563 RTC chip. The Epson RTC8564
383 This driver can also be built as a module. If so, the module
384 will be called rtc-pcf8563.
386 config RTC_DRV_PCF85063
387 tristate "nxp PCF85063"
389 If you say yes here you get support for the PCF85063 RTC chip
391 This driver can also be built as a module. If so, the module
392 will be called rtc-pcf85063.
394 config RTC_DRV_PCF8583
395 tristate "Philips PCF8583"
397 If you say yes here you get support for the Philips PCF8583
398 RTC chip found on Acorn RiscPCs. This driver supports the
399 platform specific method of retrieving the current year from
400 the RTC's SRAM. It will work on other platforms with the same
401 chip, but the year will probably have to be tweaked.
403 This driver can also be built as a module. If so, the module
404 will be called rtc-pcf8583.
406 config RTC_DRV_M41T80
407 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
409 If you say Y here you will get support for the ST M41T60
410 and M41T80 RTC chips series. Currently, the following chips are
411 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
412 M41ST85, M41ST87, and MicroCrystal RV4162.
414 This driver can also be built as a module. If so, the module
415 will be called rtc-m41t80.
417 config RTC_DRV_M41T80_WDT
418 bool "ST M41T65/M41T80 series RTC watchdog timer"
419 depends on RTC_DRV_M41T80
421 If you say Y here you will get support for the
422 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
425 tristate "TI BQ32000"
427 If you say Y here you will get support for the TI
428 BQ32000 I2C RTC chip.
430 This driver can also be built as a module. If so, the module
431 will be called rtc-bq32k.
433 config RTC_DRV_DM355EVM
434 tristate "TI DaVinci DM355 EVM RTC"
435 depends on MFD_DM355EVM_MSP
437 Supports the RTC firmware in the MSP430 on the DM355 EVM.
439 config RTC_DRV_TWL92330
440 boolean "TI TWL92330/Menelaus"
443 If you say yes here you get support for the RTC on the
444 TWL92330 "Menelaus" power management chip, used with OMAP2
445 platforms. The support is integrated with the rest of
446 the Menelaus driver; it's not separate module.
448 config RTC_DRV_TWL4030
449 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
450 depends on TWL4030_CORE
452 If you say yes here you get support for the RTC on the
453 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
455 This driver can also be built as a module. If so, the module
456 will be called rtc-twl.
458 config RTC_DRV_TPS6586X
459 tristate "TI TPS6586X RTC driver"
460 depends on MFD_TPS6586X
462 TI Power Management IC TPS6586X supports RTC functionality
463 along with alarm. This driver supports the RTC driver for
464 the TPS6586X RTC module.
466 config RTC_DRV_TPS65910
467 tristate "TI TPS65910 RTC driver"
468 depends on RTC_CLASS && MFD_TPS65910
470 If you say yes here you get support for the RTC on the
473 This driver can also be built as a module. If so, the module
474 will be called rtc-tps65910.
476 config RTC_DRV_TPS80031
477 tristate "TI TPS80031/TPS80032 RTC driver"
478 depends on MFD_TPS80031
480 TI Power Management IC TPS80031 supports RTC functionality
481 along with alarm. This driver supports the RTC driver for
482 the TPS80031 RTC module.
484 config RTC_DRV_RC5T583
485 tristate "RICOH 5T583 RTC driver"
486 depends on MFD_RC5T583
488 If you say yes here you get support for the RTC on the
491 This driver can also be built as a module. If so, the module
492 will be called rtc-rc5t583.
494 config RTC_DRV_S35390A
495 tristate "Seiko Instruments S-35390A"
498 If you say yes here you will get support for the Seiko
499 Instruments S-35390A.
501 This driver can also be built as a module. If so the module
502 will be called rtc-s35390a.
504 config RTC_DRV_FM3130
505 tristate "Ramtron FM3130"
507 If you say Y here you will get support for the
508 Ramtron FM3130 RTC chips.
509 Ramtron FM3130 is a chip with two separate devices inside,
510 RTC clock and FRAM. This driver provides only RTC functionality.
512 This driver can also be built as a module. If so the module
513 will be called rtc-fm3130.
515 config RTC_DRV_RX8581
516 tristate "Epson RX-8581"
518 If you say yes here you will get support for the Epson RX-8581.
520 This driver can also be built as a module. If so the module
521 will be called rtc-rx8581.
523 config RTC_DRV_RX8025
524 tristate "Epson RX-8025SA/NB"
526 If you say yes here you get support for the Epson
527 RX-8025SA/NB RTC chips.
529 This driver can also be built as a module. If so, the module
530 will be called rtc-rx8025.
532 config RTC_DRV_EM3027
533 tristate "EM Microelectronic EM3027"
535 If you say yes here you get support for the EM
536 Microelectronic EM3027 RTC chips.
538 This driver can also be built as a module. If so, the module
539 will be called rtc-em3027.
541 config RTC_DRV_RV3029C2
542 tristate "Micro Crystal RTC"
544 If you say yes here you get support for the Micro Crystal
547 This driver can also be built as a module. If so, the module
548 will be called rtc-rv3029c2.
551 tristate "Samsung S2M/S5M series"
552 depends on MFD_SEC_CORE
554 If you say yes here you will get support for the
555 RTC of Samsung S2MPS14 and S5M PMIC series.
557 This driver can also be built as a module. If so, the module
558 will be called rtc-s5m.
562 comment "SPI RTC drivers"
566 config RTC_DRV_M41T93
569 If you say yes here you will get support for the
570 ST M41T93 SPI RTC chip.
572 This driver can also be built as a module. If so, the module
573 will be called rtc-m41t93.
575 config RTC_DRV_M41T94
578 If you say yes here you will get support for the
579 ST M41T94 SPI RTC chip.
581 This driver can also be built as a module. If so, the module
582 will be called rtc-m41t94.
584 config RTC_DRV_DS1305
585 tristate "Dallas/Maxim DS1305/DS1306"
587 Select this driver to get support for the Dallas/Maxim DS1305
588 and DS1306 real time clock chips. These support a trickle
589 charger, alarms, and NVRAM in addition to the clock.
591 This driver can also be built as a module. If so, the module
592 will be called rtc-ds1305.
594 config RTC_DRV_DS1343
596 tristate "Dallas/Maxim DS1343/DS1344"
598 If you say yes here you get support for the
599 Dallas/Maxim DS1343 and DS1344 real time clock chips.
600 Support for trickle charger, alarm is provided.
602 This driver can also be built as a module. If so, the module
603 will be called rtc-ds1343.
605 config RTC_DRV_DS1347
606 tristate "Dallas/Maxim DS1347"
608 If you say yes here you get support for the
609 Dallas/Maxim DS1347 chips.
611 This driver only supports the RTC feature, and not other chip
612 features such as alarms.
614 This driver can also be built as a module. If so, the module
615 will be called rtc-ds1347.
617 config RTC_DRV_DS1390
618 tristate "Dallas/Maxim DS1390/93/94"
620 If you say yes here you get support for the
621 Dallas/Maxim DS1390/93/94 chips.
623 This driver only supports the RTC feature, and not other chip
624 features such as alarms and trickle charging.
626 This driver can also be built as a module. If so, the module
627 will be called rtc-ds1390.
629 config RTC_DRV_MAX6902
630 tristate "Maxim MAX6902"
632 If you say yes here you will get support for the
633 Maxim MAX6902 SPI RTC chip.
635 This driver can also be built as a module. If so, the module
636 will be called rtc-max6902.
639 tristate "Epson RTC-9701JE"
641 If you say yes here you will get support for the
642 Epson RTC-9701JE SPI RTC chip.
644 This driver can also be built as a module. If so, the module
645 will be called rtc-r9701.
647 config RTC_DRV_RS5C348
648 tristate "Ricoh RS5C348A/B"
650 If you say yes here you get support for the
651 Ricoh RS5C348A and RS5C348B RTC chips.
653 This driver can also be built as a module. If so, the module
654 will be called rtc-rs5c348.
656 config RTC_DRV_DS3234
657 tristate "Maxim/Dallas DS3234"
659 If you say yes here you get support for the
660 Maxim/Dallas DS3234 SPI RTC chip.
662 This driver can also be built as a module. If so, the module
663 will be called rtc-ds3234.
665 config RTC_DRV_PCF2123
666 tristate "NXP PCF2123"
668 If you say yes here you get support for the NXP PCF2123
671 This driver can also be built as a module. If so, the module
672 will be called rtc-pcf2123.
674 config RTC_DRV_RX4581
675 tristate "Epson RX-4581"
677 If you say yes here you will get support for the Epson RX-4581.
679 This driver can also be built as a module. If so the module
680 will be called rtc-rx4581.
682 config RTC_DRV_MCP795
683 tristate "Microchip MCP795"
685 If you say yes here you will get support for the Microchip MCP795.
687 This driver can also be built as a module. If so the module
688 will be called rtc-mcp795.
692 comment "Platform RTC drivers"
694 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
695 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
696 # global rtc_lock ... it's not yet just another platform_device.
699 tristate "PC-style 'CMOS'"
700 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
703 Say "yes" here to get direct support for the real time clock
704 found in every PC or ACPI-based system, and some other boards.
705 Specifically the original MC146818, compatibles like those in
706 PC south bridges, the DS12887 or M48T86, some multifunction
707 or LPC bus chips, and so on.
709 Your system will need to define the platform device used by
710 this driver, otherwise it won't be accessible. This means
711 you can safely enable this driver if you don't know whether
712 or not your board has this kind of hardware.
714 This driver can also be built as a module. If so, the module
715 will be called rtc-cmos.
718 bool "Alpha PC-style CMOS"
722 Direct support for the real-time clock found on every Alpha
723 system, specifically MC146818 compatibles. If in doubt, say Y.
726 tristate "Virtual RTC for Intel MID platforms"
727 depends on X86_INTEL_MID
728 default y if X86_INTEL_MID
731 Say "yes" here to get direct support for the real time clock
732 found on Moorestown platforms. The VRTC is a emulated RTC that
733 derives its clock source from a real RTC in the PMIC. The MC146818
734 style programming interface is mostly conserved, but any
735 updates are done via IPC calls to the system controller FW.
737 config RTC_DRV_DS1216
738 tristate "Dallas DS1216"
741 If you say yes here you get support for the Dallas DS1216 RTC chips.
743 config RTC_DRV_DS1286
744 tristate "Dallas DS1286"
746 If you say yes here you get support for the Dallas DS1286 RTC chips.
748 config RTC_DRV_DS1302
749 tristate "Dallas DS1302"
750 depends on SH_SECUREEDGE5410
752 If you say yes here you get support for the Dallas DS1302 RTC chips.
754 config RTC_DRV_DS1511
755 tristate "Dallas DS1511"
757 If you say yes here you get support for the
758 Dallas DS1511 timekeeping/watchdog chip.
760 This driver can also be built as a module. If so, the module
761 will be called rtc-ds1511.
763 config RTC_DRV_DS1553
764 tristate "Maxim/Dallas DS1553"
766 If you say yes here you get support for the
767 Maxim/Dallas DS1553 timekeeping chip.
769 This driver can also be built as a module. If so, the module
770 will be called rtc-ds1553.
772 config RTC_DRV_DS1742
773 tristate "Maxim/Dallas DS1742/1743"
775 If you say yes here you get support for the
776 Maxim/Dallas DS1742/1743 timekeeping chip.
778 This driver can also be built as a module. If so, the module
779 will be called rtc-ds1742.
781 config RTC_DRV_DS2404
782 tristate "Maxim/Dallas DS2404"
784 If you say yes here you get support for the
785 Dallas DS2404 RTC chip.
787 This driver can also be built as a module. If so, the module
788 will be called rtc-ds2404.
790 config RTC_DRV_DA9052
791 tristate "Dialog DA9052/DA9053 RTC"
792 depends on PMIC_DA9052
794 Say y here to support the RTC driver for Dialog Semiconductor
795 DA9052-BC and DA9053-AA/Bx PMICs.
797 config RTC_DRV_DA9055
798 tristate "Dialog Semiconductor DA9055 RTC"
799 depends on MFD_DA9055
801 If you say yes here you will get support for the
802 RTC of the Dialog DA9055 PMIC.
804 This driver can also be built as a module. If so, the module
805 will be called rtc-da9055
807 config RTC_DRV_DA9063
808 tristate "Dialog Semiconductor DA9063 RTC"
809 depends on MFD_DA9063
811 If you say yes here you will get support for the RTC subsystem
812 of the Dialog Semiconductor DA9063.
814 This driver can also be built as a module. If so, the module
815 will be called "rtc-da9063".
821 If you say yes here you will get support for the EFI
824 This driver can also be built as a module. If so, the module
825 will be called rtc-efi.
827 config RTC_DRV_STK17TA8
828 tristate "Simtek STK17TA8"
830 If you say yes here you get support for the
831 Simtek STK17TA8 timekeeping chip.
833 This driver can also be built as a module. If so, the module
834 will be called rtc-stk17ta8.
836 config RTC_DRV_M48T86
837 tristate "ST M48T86/Dallas DS12887"
839 If you say Y here you will get support for the
840 ST M48T86 and Dallas DS12887 RTC chips.
842 This driver can also be built as a module. If so, the module
843 will be called rtc-m48t86.
845 config RTC_DRV_M48T35
848 If you say Y here you will get support for the
851 This driver can also be built as a module, if so, the module
852 will be called "rtc-m48t35".
854 config RTC_DRV_M48T59
855 tristate "ST M48T59/M48T08/M48T02"
857 If you say Y here you will get support for the
858 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
860 These chips are usually found in Sun SPARC and UltraSPARC
863 This driver can also be built as a module, if so, the module
864 will be called "rtc-m48t59".
866 config RTC_DRV_MSM6242
867 tristate "Oki MSM6242"
869 If you say yes here you get support for the Oki MSM6242
870 timekeeping chip. It is used in some Amiga models (e.g. A2000).
872 This driver can also be built as a module. If so, the module
873 will be called rtc-msm6242.
875 config RTC_DRV_BQ4802
878 If you say Y here you will get support for the TI
881 This driver can also be built as a module. If so, the module
882 will be called rtc-bq4802.
884 config RTC_DRV_RP5C01
885 tristate "Ricoh RP5C01"
887 If you say yes here you get support for the Ricoh RP5C01
888 timekeeping chip. It is used in some Amiga models (e.g. A3000
891 This driver can also be built as a module. If so, the module
892 will be called rtc-rp5c01.
895 tristate "EM Microelectronic V3020"
897 If you say yes here you will get support for the
898 EM Microelectronic v3020 RTC chip.
900 This driver can also be built as a module. If so, the module
901 will be called rtc-v3020.
903 config RTC_DRV_WM831X
904 tristate "Wolfson Microelectronics WM831x RTC"
905 depends on MFD_WM831X
907 If you say yes here you will get support for the RTC subsystem
908 of the Wolfson Microelectronics WM831X series PMICs.
910 This driver can also be built as a module. If so, the module
911 will be called "rtc-wm831x".
913 config RTC_DRV_WM8350
914 tristate "Wolfson Microelectronics WM8350 RTC"
915 depends on MFD_WM8350
917 If you say yes here you will get support for the RTC subsystem
918 of the Wolfson Microelectronics WM8350.
920 This driver can also be built as a module. If so, the module
921 will be called "rtc-wm8350".
924 tristate "SPEAR ST RTC"
925 depends on PLAT_SPEAR
928 If you say Y here you will get support for the RTC found on
931 config RTC_DRV_PCF50633
932 depends on MFD_PCF50633
933 tristate "NXP PCF50633 RTC"
935 If you say yes here you get support for the RTC subsystem of the
936 NXP PCF50633 used in embedded systems.
938 config RTC_DRV_AB3100
939 tristate "ST-Ericsson AB3100 RTC"
940 depends on AB3100_CORE
941 default y if AB3100_CORE
943 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
944 support. This chip contains a battery- and capacitor-backed RTC.
946 config RTC_DRV_AB8500
947 tristate "ST-Ericsson AB8500 RTC"
948 depends on AB8500_CORE
950 select RTC_INTF_DEV_UIE_EMUL
952 Select this to enable the ST-Ericsson AB8500 power management IC RTC
953 support. This chip contains a battery- and capacitor-backed RTC.
955 config RTC_DRV_NUC900
956 tristate "NUC910/NUC920 RTC driver"
957 depends on ARCH_W90X900
959 If you say yes here you get support for the RTC subsystem of the
960 NUC910/NUC920 used in embedded systems.
962 comment "on-CPU RTC drivers"
964 config RTC_DRV_DAVINCI
965 tristate "TI DaVinci RTC"
966 depends on ARCH_DAVINCI_DM365
968 If you say yes here you get support for the RTC on the
969 DaVinci platforms (DM365).
971 This driver can also be built as a module. If so, the module
972 will be called rtc-davinci.
975 tristate "Freescale IMX DryIce Real Time Clock"
978 Support for Freescale IMX DryIce RTC
980 This driver can also be built as a module, if so, the module
981 will be called "rtc-imxdi".
985 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
987 Say "yes" here to support the on chip real time clock
988 present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
990 This driver can also be built as a module, if so, module
991 will be called rtc-omap.
996 This will include RTC support for Samsung SoCs. If
997 you want to include RTC support for any machine, kindly
998 select this in the respective mach-XXXX/Kconfig file.
1001 tristate "Samsung S3C series SoC RTC"
1002 depends on ARCH_S3C64XX || HAVE_S3C_RTC
1004 RTC (Realtime Clock) driver for the clock inbuilt into the
1005 Samsung S3C24XX series of SoCs. This can provide periodic
1006 interrupt rates from 1Hz to 64Hz for user programs, and
1009 The driver currently supports the common features on all the
1010 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1013 This driver can also be build as a module. If so, the module
1014 will be called rtc-s3c.
1016 config RTC_DRV_EP93XX
1017 tristate "Cirrus Logic EP93XX"
1018 depends on ARCH_EP93XX
1020 If you say yes here you get support for the
1021 RTC embedded in the Cirrus Logic EP93XX processors.
1023 This driver can also be built as a module. If so, the module
1024 will be called rtc-ep93xx.
1026 config RTC_DRV_SA1100
1027 tristate "SA11x0/PXA2xx/PXA910"
1028 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1030 If you say Y here you will get access to the real time clock
1031 built into your SA11x0 or PXA2xx CPU.
1033 To compile this driver as a module, choose M here: the
1034 module will be called rtc-sa1100.
1037 tristate "SuperH On-Chip RTC"
1038 depends on SUPERH && HAVE_CLK
1040 Say Y here to enable support for the on-chip RTC found in
1041 most SuperH processors.
1043 To compile this driver as a module, choose M here: the
1044 module will be called rtc-sh.
1046 config RTC_DRV_VR41XX
1047 tristate "NEC VR41XX"
1048 depends on CPU_VR41XX
1050 If you say Y here you will get access to the real time clock
1051 built into your NEC VR41XX CPU.
1053 To compile this driver as a module, choose M here: the
1054 module will be called rtc-vr41xx.
1056 config RTC_DRV_PL030
1057 tristate "ARM AMBA PL030 RTC"
1060 If you say Y here you will get access to ARM AMBA
1061 PrimeCell PL030 RTC found on certain ARM SOCs.
1063 To compile this driver as a module, choose M here: the
1064 module will be called rtc-pl030.
1066 config RTC_DRV_PL031
1067 tristate "ARM AMBA PL031 RTC"
1070 If you say Y here you will get access to ARM AMBA
1071 PrimeCell PL031 RTC found on certain ARM SOCs.
1073 To compile this driver as a module, choose M here: the
1074 module will be called rtc-pl031.
1076 config RTC_DRV_AT32AP700X
1077 tristate "AT32AP700X series RTC"
1078 depends on PLATFORM_AT32AP
1080 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1081 AT32AP700x family processors.
1083 config RTC_DRV_AT91RM9200
1084 tristate "AT91RM9200 or some AT91SAM9 RTC"
1085 depends on ARCH_AT91
1087 Driver for the internal RTC (Realtime Clock) module found on
1088 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1089 this is powered by the backup power supply.
1091 config RTC_DRV_AT91SAM9
1092 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
1093 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
1095 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
1096 (Real Time Timer). These timers are powered by the backup power
1097 supply (such as a small coin cell battery), but do not need to
1100 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
1101 dedicated RTC module and leave the RTT available for other uses.)
1103 config RTC_DRV_AT91SAM9_RTT
1107 prompt "RTT module Number" if ARCH_AT91SAM9263
1108 depends on RTC_DRV_AT91SAM9
1110 More than one RTT module is available. You can choose which
1111 one will be used as an RTC. The default of zero is normally
1112 OK to use, though some systems use that for non-RTC purposes.
1114 config RTC_DRV_AT91SAM9_GPBR
1116 range 0 3 if !ARCH_AT91SAM9263
1117 range 0 15 if ARCH_AT91SAM9263
1119 prompt "Backup Register Number"
1120 depends on RTC_DRV_AT91SAM9
1122 The RTC driver needs to use one of the General Purpose Backup
1123 Registers (GPBRs) as well as the RTT. You can choose which one
1124 will be used. The default of zero is normally OK to use, but
1125 on some systems other software needs to use that register.
1127 config RTC_DRV_AU1XXX
1128 tristate "Au1xxx Counter0 RTC support"
1129 depends on MIPS_ALCHEMY
1131 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1132 counter) to be used as a RTC.
1134 This driver can also be built as a module. If so, the module
1135 will be called rtc-au1xxx.
1138 tristate "Blackfin On-Chip RTC"
1139 depends on BLACKFIN && !BF561
1141 If you say yes here you will get support for the
1142 Blackfin On-Chip Real Time Clock.
1144 This driver can also be built as a module. If so, the module
1145 will be called rtc-bfin.
1147 config RTC_DRV_RS5C313
1148 tristate "Ricoh RS5C313"
1149 depends on SH_LANDISK
1151 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1153 config RTC_DRV_GENERIC
1154 tristate "Generic RTC support"
1155 # Please consider writing a new RTC driver instead of using the generic
1157 depends on PARISC || M68K || PPC || SUPERH32
1159 Say Y or M here to enable RTC support on systems using the generic
1160 RTC abstraction. If you do not know what you are doing, you should
1164 tristate "PXA27x/PXA3xx"
1167 If you say Y here you will get access to the real time clock
1168 built into your PXA27x or PXA3xx CPU.
1170 This RTC driver uses PXA RTC registers available since pxa27x
1171 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1173 config RTC_DRV_VT8500
1174 tristate "VIA/WonderMedia 85xx SoC RTC"
1175 depends on ARCH_VT8500
1177 If you say Y here you will get access to the real time clock
1178 built into your VIA VT8500 SoC or its relatives.
1181 config RTC_DRV_SUN4V
1182 bool "SUN4V Hypervisor RTC"
1185 If you say Y here you will get support for the Hypervisor
1186 based RTC on SUN4V systems.
1188 config RTC_DRV_SUN6I
1189 tristate "Allwinner A31 RTC"
1190 depends on MACH_SUN6I || MACH_SUN8I
1192 If you say Y here you will get support for the RTC found on
1195 config RTC_DRV_SUNXI
1196 tristate "Allwinner sun4i/sun7i RTC"
1197 depends on MACH_SUN4I || MACH_SUN7I
1199 If you say Y here you will get support for the RTC found on
1202 config RTC_DRV_STARFIRE
1206 If you say Y here you will get support for the RTC found on
1209 config RTC_DRV_TX4939
1210 tristate "TX4939 SoC"
1211 depends on SOC_TX4939
1213 Driver for the internal RTC (Realtime Clock) module found on
1217 tristate "Marvell SoC RTC"
1218 depends on ARCH_DOVE || ARCH_MVEBU
1220 If you say yes here you will get support for the in-chip RTC
1221 that can be found in some of Marvell's SoC devices, such as
1222 the Kirkwood 88F6281 and 88F6192.
1224 This driver can also be built as a module. If so, the module
1225 will be called rtc-mv.
1231 If you say yes here you will get support for the RTC on PS3.
1233 This driver can also be built as a module. If so, the module
1234 will be called rtc-ps3.
1236 config RTC_DRV_COH901331
1237 tristate "ST-Ericsson COH 901 331 RTC"
1238 depends on ARCH_U300
1240 If you say Y here you will get access to ST-Ericsson
1241 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1244 This driver can also be built as a module. If so, the module
1245 will be called "rtc-coh901331".
1249 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1252 If you say yes here you will get support for the onboard
1253 STMP3xxx/i.MX23/i.MX28 RTC.
1255 This driver can also be built as a module. If so, the module
1256 will be called rtc-stmp3xxx.
1262 If you say Y here you will get support for the RTC found on
1263 the PCAP2 ASIC used on some Motorola phones.
1265 config RTC_DRV_MC13XXX
1266 depends on MFD_MC13XXX
1267 tristate "Freescale MC13xxx RTC"
1269 This enables support for the RTCs found on Freescale's PMICs
1270 MC13783 and MC13892.
1272 config RTC_DRV_MPC5121
1273 tristate "Freescale MPC5121 built-in RTC"
1274 depends on PPC_MPC512x || PPC_MPC52xx
1276 If you say yes here you will get support for the
1277 built-in RTC on MPC5121 or on MPC5200.
1279 This driver can also be built as a module. If so, the module
1280 will be called rtc-mpc5121.
1282 config RTC_DRV_JZ4740
1283 tristate "Ingenic JZ4740 SoC"
1284 depends on MACH_JZ4740
1286 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1289 This driver can also be buillt as a module. If so, the module
1290 will be called rtc-jz4740.
1292 config RTC_DRV_LPC32XX
1293 depends on ARCH_LPC32XX
1294 tristate "NXP LPC32XX RTC"
1296 This enables support for the NXP RTC in the LPC32XX
1298 This driver can also be buillt as a module. If so, the module
1299 will be called rtc-lpc32xx.
1301 config RTC_DRV_PM8XXX
1302 tristate "Qualcomm PMIC8XXX RTC"
1303 depends on MFD_PM8XXX
1305 If you say yes here you get support for the
1306 Qualcomm PMIC8XXX RTC.
1308 To compile this driver as a module, choose M here: the
1309 module will be called rtc-pm8xxx.
1311 config RTC_DRV_TEGRA
1312 tristate "NVIDIA Tegra Internal RTC driver"
1313 depends on ARCH_TEGRA
1315 If you say yes here you get support for the
1316 Tegra 200 series internal RTC module.
1318 This drive can also be built as a module. If so, the module
1319 will be called rtc-tegra.
1322 tristate "Tilera hypervisor RTC support"
1325 Enable support for the Linux driver side of the Tilera
1326 hypervisor's real-time clock interface.
1329 tristate "PKUnity v3 RTC support"
1330 depends on ARCH_PUV3
1332 This enables support for the RTC in the PKUnity-v3 SoCs.
1334 This drive can also be built as a module. If so, the module
1335 will be called rtc-puv3.
1337 config RTC_DRV_LOONGSON1
1338 tristate "loongson1 RTC support"
1339 depends on MACH_LOONGSON1
1341 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1342 counter) to be used as a RTC.
1344 This driver can also be built as a module. If so, the module
1345 will be called rtc-ls1x.
1348 tristate "Freescale MXC Real Time Clock"
1351 If you say yes here you get support for the Freescale MXC
1354 This driver can also be built as a module, if so, the module
1355 will be called "rtc-mxc".
1358 tristate "Freescale SNVS RTC support"
1359 depends on HAS_IOMEM
1362 If you say yes here you get support for the Freescale SNVS
1363 Low Power (LP) RTC module.
1365 This driver can also be built as a module, if so, the module
1366 will be called "rtc-snvs".
1368 config RTC_DRV_SIRFSOC
1369 tristate "SiRFSOC RTC"
1370 depends on ARCH_SIRF
1372 Say "yes" here to support the real time clock on SiRF SOC chips.
1373 This driver can also be built as a module called rtc-sirfsoc.
1375 config RTC_DRV_MOXART
1376 tristate "MOXA ART RTC"
1377 depends on ARCH_MOXART || COMPILE_TEST
1379 If you say yes here you get support for the MOXA ART
1382 This driver can also be built as a module. If so, the module
1383 will be called rtc-moxart
1385 config RTC_DRV_XGENE
1386 tristate "APM X-Gene RTC"
1388 If you say yes here you get support for the APM X-Gene SoC real time
1391 This driver can also be built as a module, if so, the module
1392 will be called "rtc-xgene".
1394 comment "HID Sensor RTC drivers"
1396 config RTC_DRV_HID_SENSOR_TIME
1397 tristate "HID Sensor Time"
1400 select HID_SENSOR_HUB
1401 select HID_SENSOR_IIO_COMMON
1403 Say yes here to build support for the HID Sensors of type Time.
1404 This drivers makes such sensors available as RTCs.
1406 If this driver is compiled as a module, it will be named
1407 rtc-hid-sensor-time.