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_MAX77802
302 tristate "Maxim 77802 RTC"
303 depends on MFD_MAX77686
305 If you say yes here you will get support for the
306 RTC of Maxim MAX77802 PMIC.
308 This driver can also be built as a module. If so, the module
309 will be called rtc-max77802.
311 config RTC_DRV_RS5C372
312 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
314 If you say yes here you get support for the
315 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
317 This driver can also be built as a module. If so, the module
318 will be called rtc-rs5c372.
320 config RTC_DRV_ISL1208
321 tristate "Intersil ISL1208"
323 If you say yes here you get support for the
324 Intersil ISL1208 RTC chip.
326 This driver can also be built as a module. If so, the module
327 will be called rtc-isl1208.
329 config RTC_DRV_ISL12022
330 tristate "Intersil ISL12022"
332 If you say yes here you get support for the
333 Intersil ISL12022 RTC chip.
335 This driver can also be built as a module. If so, the module
336 will be called rtc-isl12022.
338 config RTC_DRV_ISL12057
341 tristate "Intersil ISL12057"
343 If you say yes here you get support for the Intersil ISL12057
346 This driver can also be built as a module. If so, the module
347 will be called rtc-isl12057.
350 tristate "Xicor/Intersil X1205"
352 If you say yes here you get support for the
353 Xicor/Intersil X1205 RTC chip.
355 This driver can also be built as a module. If so, the module
356 will be called rtc-x1205.
358 config RTC_DRV_PALMAS
359 tristate "TI Palmas RTC driver"
360 depends on MFD_PALMAS
362 If you say yes here you get support for the RTC of TI PALMA series PMIC
365 This driver can also be built as a module. If so, the module
366 will be called rtc-palma.
368 config RTC_DRV_PCF2127
369 tristate "NXP PCF2127"
371 If you say yes here you get support for the NXP PCF2127/29 RTC
374 This driver can also be built as a module. If so, the module
375 will be called rtc-pcf2127.
377 config RTC_DRV_PCF8523
378 tristate "NXP PCF8523"
380 If you say yes here you get support for the NXP PCF8523 RTC
383 This driver can also be built as a module. If so, the module
384 will be called rtc-pcf8523.
386 config RTC_DRV_PCF8563
387 tristate "Philips PCF8563/Epson RTC8564"
389 If you say yes here you get support for the
390 Philips PCF8563 RTC chip. The Epson RTC8564
393 This driver can also be built as a module. If so, the module
394 will be called rtc-pcf8563.
396 config RTC_DRV_PCF85063
397 tristate "nxp PCF85063"
399 If you say yes here you get support for the PCF85063 RTC chip
401 This driver can also be built as a module. If so, the module
402 will be called rtc-pcf85063.
404 config RTC_DRV_PCF8583
405 tristate "Philips PCF8583"
407 If you say yes here you get support for the Philips PCF8583
408 RTC chip found on Acorn RiscPCs. This driver supports the
409 platform specific method of retrieving the current year from
410 the RTC's SRAM. It will work on other platforms with the same
411 chip, but the year will probably have to be tweaked.
413 This driver can also be built as a module. If so, the module
414 will be called rtc-pcf8583.
416 config RTC_DRV_M41T80
417 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
419 If you say Y here you will get support for the ST M41T60
420 and M41T80 RTC chips series. Currently, the following chips are
421 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
422 M41ST85, M41ST87, and MicroCrystal RV4162.
424 This driver can also be built as a module. If so, the module
425 will be called rtc-m41t80.
427 config RTC_DRV_M41T80_WDT
428 bool "ST M41T65/M41T80 series RTC watchdog timer"
429 depends on RTC_DRV_M41T80
431 If you say Y here you will get support for the
432 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
435 tristate "TI BQ32000"
437 If you say Y here you will get support for the TI
438 BQ32000 I2C RTC chip.
440 This driver can also be built as a module. If so, the module
441 will be called rtc-bq32k.
443 config RTC_DRV_DM355EVM
444 tristate "TI DaVinci DM355 EVM RTC"
445 depends on MFD_DM355EVM_MSP
447 Supports the RTC firmware in the MSP430 on the DM355 EVM.
449 config RTC_DRV_TWL92330
450 boolean "TI TWL92330/Menelaus"
453 If you say yes here you get support for the RTC on the
454 TWL92330 "Menelaus" power management chip, used with OMAP2
455 platforms. The support is integrated with the rest of
456 the Menelaus driver; it's not separate module.
458 config RTC_DRV_TWL4030
459 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
460 depends on TWL4030_CORE
462 If you say yes here you get support for the RTC on the
463 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
465 This driver can also be built as a module. If so, the module
466 will be called rtc-twl.
468 config RTC_DRV_TPS6586X
469 tristate "TI TPS6586X RTC driver"
470 depends on MFD_TPS6586X
472 TI Power Management IC TPS6586X supports RTC functionality
473 along with alarm. This driver supports the RTC driver for
474 the TPS6586X RTC module.
476 config RTC_DRV_TPS65910
477 tristate "TI TPS65910 RTC driver"
478 depends on RTC_CLASS && MFD_TPS65910
480 If you say yes here you get support for the RTC on the
483 This driver can also be built as a module. If so, the module
484 will be called rtc-tps65910.
486 config RTC_DRV_TPS80031
487 tristate "TI TPS80031/TPS80032 RTC driver"
488 depends on MFD_TPS80031
490 TI Power Management IC TPS80031 supports RTC functionality
491 along with alarm. This driver supports the RTC driver for
492 the TPS80031 RTC module.
494 config RTC_DRV_RC5T583
495 tristate "RICOH 5T583 RTC driver"
496 depends on MFD_RC5T583
498 If you say yes here you get support for the RTC on the
501 This driver can also be built as a module. If so, the module
502 will be called rtc-rc5t583.
504 config RTC_DRV_S35390A
505 tristate "Seiko Instruments S-35390A"
508 If you say yes here you will get support for the Seiko
509 Instruments S-35390A.
511 This driver can also be built as a module. If so the module
512 will be called rtc-s35390a.
514 config RTC_DRV_FM3130
515 tristate "Ramtron FM3130"
517 If you say Y here you will get support for the
518 Ramtron FM3130 RTC chips.
519 Ramtron FM3130 is a chip with two separate devices inside,
520 RTC clock and FRAM. This driver provides only RTC functionality.
522 This driver can also be built as a module. If so the module
523 will be called rtc-fm3130.
525 config RTC_DRV_RX8581
526 tristate "Epson RX-8581"
528 If you say yes here you will get support for the Epson RX-8581.
530 This driver can also be built as a module. If so the module
531 will be called rtc-rx8581.
533 config RTC_DRV_RX8025
534 tristate "Epson RX-8025SA/NB"
536 If you say yes here you get support for the Epson
537 RX-8025SA/NB RTC chips.
539 This driver can also be built as a module. If so, the module
540 will be called rtc-rx8025.
542 config RTC_DRV_EM3027
543 tristate "EM Microelectronic EM3027"
545 If you say yes here you get support for the EM
546 Microelectronic EM3027 RTC chips.
548 This driver can also be built as a module. If so, the module
549 will be called rtc-em3027.
551 config RTC_DRV_RV3029C2
552 tristate "Micro Crystal RTC"
554 If you say yes here you get support for the Micro Crystal
557 This driver can also be built as a module. If so, the module
558 will be called rtc-rv3029c2.
561 tristate "Samsung S2M/S5M series"
562 depends on MFD_SEC_CORE
564 If you say yes here you will get support for the
565 RTC of Samsung S2MPS14 and S5M PMIC series.
567 This driver can also be built as a module. If so, the module
568 will be called rtc-s5m.
572 comment "SPI RTC drivers"
576 config RTC_DRV_M41T93
579 If you say yes here you will get support for the
580 ST M41T93 SPI RTC chip.
582 This driver can also be built as a module. If so, the module
583 will be called rtc-m41t93.
585 config RTC_DRV_M41T94
588 If you say yes here you will get support for the
589 ST M41T94 SPI RTC chip.
591 This driver can also be built as a module. If so, the module
592 will be called rtc-m41t94.
594 config RTC_DRV_DS1305
595 tristate "Dallas/Maxim DS1305/DS1306"
597 Select this driver to get support for the Dallas/Maxim DS1305
598 and DS1306 real time clock chips. These support a trickle
599 charger, alarms, and NVRAM in addition to the clock.
601 This driver can also be built as a module. If so, the module
602 will be called rtc-ds1305.
604 config RTC_DRV_DS1343
606 tristate "Dallas/Maxim DS1343/DS1344"
608 If you say yes here you get support for the
609 Dallas/Maxim DS1343 and DS1344 real time clock chips.
610 Support for trickle charger, alarm is provided.
612 This driver can also be built as a module. If so, the module
613 will be called rtc-ds1343.
615 config RTC_DRV_DS1347
616 tristate "Dallas/Maxim DS1347"
618 If you say yes here you get support for the
619 Dallas/Maxim DS1347 chips.
621 This driver only supports the RTC feature, and not other chip
622 features such as alarms.
624 This driver can also be built as a module. If so, the module
625 will be called rtc-ds1347.
627 config RTC_DRV_DS1390
628 tristate "Dallas/Maxim DS1390/93/94"
630 If you say yes here you get support for the
631 Dallas/Maxim DS1390/93/94 chips.
633 This driver only supports the RTC feature, and not other chip
634 features such as alarms and trickle charging.
636 This driver can also be built as a module. If so, the module
637 will be called rtc-ds1390.
639 config RTC_DRV_MAX6902
640 tristate "Maxim MAX6902"
642 If you say yes here you will get support for the
643 Maxim MAX6902 SPI RTC chip.
645 This driver can also be built as a module. If so, the module
646 will be called rtc-max6902.
649 tristate "Epson RTC-9701JE"
651 If you say yes here you will get support for the
652 Epson RTC-9701JE SPI RTC chip.
654 This driver can also be built as a module. If so, the module
655 will be called rtc-r9701.
657 config RTC_DRV_RS5C348
658 tristate "Ricoh RS5C348A/B"
660 If you say yes here you get support for the
661 Ricoh RS5C348A and RS5C348B RTC chips.
663 This driver can also be built as a module. If so, the module
664 will be called rtc-rs5c348.
666 config RTC_DRV_DS3234
667 tristate "Maxim/Dallas DS3234"
669 If you say yes here you get support for the
670 Maxim/Dallas DS3234 SPI RTC chip.
672 This driver can also be built as a module. If so, the module
673 will be called rtc-ds3234.
675 config RTC_DRV_PCF2123
676 tristate "NXP PCF2123"
678 If you say yes here you get support for the NXP PCF2123
681 This driver can also be built as a module. If so, the module
682 will be called rtc-pcf2123.
684 config RTC_DRV_RX4581
685 tristate "Epson RX-4581"
687 If you say yes here you will get support for the Epson RX-4581.
689 This driver can also be built as a module. If so the module
690 will be called rtc-rx4581.
692 config RTC_DRV_MCP795
693 tristate "Microchip MCP795"
695 If you say yes here you will get support for the Microchip MCP795.
697 This driver can also be built as a module. If so the module
698 will be called rtc-mcp795.
702 comment "Platform RTC drivers"
704 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
705 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
706 # global rtc_lock ... it's not yet just another platform_device.
709 tristate "PC-style 'CMOS'"
710 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
713 Say "yes" here to get direct support for the real time clock
714 found in every PC or ACPI-based system, and some other boards.
715 Specifically the original MC146818, compatibles like those in
716 PC south bridges, the DS12887 or M48T86, some multifunction
717 or LPC bus chips, and so on.
719 Your system will need to define the platform device used by
720 this driver, otherwise it won't be accessible. This means
721 you can safely enable this driver if you don't know whether
722 or not your board has this kind of hardware.
724 This driver can also be built as a module. If so, the module
725 will be called rtc-cmos.
728 bool "Alpha PC-style CMOS"
732 Direct support for the real-time clock found on every Alpha
733 system, specifically MC146818 compatibles. If in doubt, say Y.
736 tristate "Virtual RTC for Intel MID platforms"
737 depends on X86_INTEL_MID
738 default y if X86_INTEL_MID
741 Say "yes" here to get direct support for the real time clock
742 found on Moorestown platforms. The VRTC is a emulated RTC that
743 derives its clock source from a real RTC in the PMIC. The MC146818
744 style programming interface is mostly conserved, but any
745 updates are done via IPC calls to the system controller FW.
747 config RTC_DRV_DS1216
748 tristate "Dallas DS1216"
751 If you say yes here you get support for the Dallas DS1216 RTC chips.
753 config RTC_DRV_DS1286
754 tristate "Dallas DS1286"
757 If you say yes here you get support for the Dallas DS1286 RTC chips.
759 config RTC_DRV_DS1302
760 tristate "Dallas DS1302"
761 depends on SH_SECUREEDGE5410
763 If you say yes here you get support for the Dallas DS1302 RTC chips.
765 config RTC_DRV_DS1511
766 tristate "Dallas DS1511"
769 If you say yes here you get support for the
770 Dallas DS1511 timekeeping/watchdog chip.
772 This driver can also be built as a module. If so, the module
773 will be called rtc-ds1511.
775 config RTC_DRV_DS1553
776 tristate "Maxim/Dallas DS1553"
779 If you say yes here you get support for the
780 Maxim/Dallas DS1553 timekeeping chip.
782 This driver can also be built as a module. If so, the module
783 will be called rtc-ds1553.
785 config RTC_DRV_DS1742
786 tristate "Maxim/Dallas DS1742/1743"
789 If you say yes here you get support for the
790 Maxim/Dallas DS1742/1743 timekeeping chip.
792 This driver can also be built as a module. If so, the module
793 will be called rtc-ds1742.
795 config RTC_DRV_DS2404
796 tristate "Maxim/Dallas DS2404"
798 If you say yes here you get support for the
799 Dallas DS2404 RTC chip.
801 This driver can also be built as a module. If so, the module
802 will be called rtc-ds2404.
804 config RTC_DRV_DA9052
805 tristate "Dialog DA9052/DA9053 RTC"
806 depends on PMIC_DA9052
808 Say y here to support the RTC driver for Dialog Semiconductor
809 DA9052-BC and DA9053-AA/Bx PMICs.
811 config RTC_DRV_DA9055
812 tristate "Dialog Semiconductor DA9055 RTC"
813 depends on MFD_DA9055
815 If you say yes here you will get support for the
816 RTC of the Dialog DA9055 PMIC.
818 This driver can also be built as a module. If so, the module
819 will be called rtc-da9055
821 config RTC_DRV_DA9063
822 tristate "Dialog Semiconductor DA9063 RTC"
823 depends on MFD_DA9063
825 If you say yes here you will get support for the RTC subsystem
826 of the Dialog Semiconductor DA9063.
828 This driver can also be built as a module. If so, the module
829 will be called "rtc-da9063".
833 depends on EFI && !X86
835 If you say yes here you will get support for the EFI
838 This driver can also be built as a module. If so, the module
839 will be called rtc-efi.
841 config RTC_DRV_STK17TA8
842 tristate "Simtek STK17TA8"
845 If you say yes here you get support for the
846 Simtek STK17TA8 timekeeping chip.
848 This driver can also be built as a module. If so, the module
849 will be called rtc-stk17ta8.
851 config RTC_DRV_M48T86
852 tristate "ST M48T86/Dallas DS12887"
854 If you say Y here you will get support for the
855 ST M48T86 and Dallas DS12887 RTC chips.
857 This driver can also be built as a module. If so, the module
858 will be called rtc-m48t86.
860 config RTC_DRV_M48T35
864 If you say Y here you will get support for the
867 This driver can also be built as a module, if so, the module
868 will be called "rtc-m48t35".
870 config RTC_DRV_M48T59
871 tristate "ST M48T59/M48T08/M48T02"
874 If you say Y here you will get support for the
875 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
877 These chips are usually found in Sun SPARC and UltraSPARC
880 This driver can also be built as a module, if so, the module
881 will be called "rtc-m48t59".
883 config RTC_DRV_MSM6242
884 tristate "Oki MSM6242"
887 If you say yes here you get support for the Oki MSM6242
888 timekeeping chip. It is used in some Amiga models (e.g. A2000).
890 This driver can also be built as a module. If so, the module
891 will be called rtc-msm6242.
893 config RTC_DRV_BQ4802
897 If you say Y here you will get support for the TI
900 This driver can also be built as a module. If so, the module
901 will be called rtc-bq4802.
903 config RTC_DRV_RP5C01
904 tristate "Ricoh RP5C01"
907 If you say yes here you get support for the Ricoh RP5C01
908 timekeeping chip. It is used in some Amiga models (e.g. A3000
911 This driver can also be built as a module. If so, the module
912 will be called rtc-rp5c01.
915 tristate "EM Microelectronic V3020"
917 If you say yes here you will get support for the
918 EM Microelectronic v3020 RTC chip.
920 This driver can also be built as a module. If so, the module
921 will be called rtc-v3020.
923 config RTC_DRV_WM831X
924 tristate "Wolfson Microelectronics WM831x RTC"
925 depends on MFD_WM831X
927 If you say yes here you will get support for the RTC subsystem
928 of the Wolfson Microelectronics WM831X series PMICs.
930 This driver can also be built as a module. If so, the module
931 will be called "rtc-wm831x".
933 config RTC_DRV_WM8350
934 tristate "Wolfson Microelectronics WM8350 RTC"
935 depends on MFD_WM8350
937 If you say yes here you will get support for the RTC subsystem
938 of the Wolfson Microelectronics WM8350.
940 This driver can also be built as a module. If so, the module
941 will be called "rtc-wm8350".
944 tristate "SPEAR ST RTC"
945 depends on PLAT_SPEAR
948 If you say Y here you will get support for the RTC found on
951 config RTC_DRV_PCF50633
952 depends on MFD_PCF50633
953 tristate "NXP PCF50633 RTC"
955 If you say yes here you get support for the RTC subsystem of the
956 NXP PCF50633 used in embedded systems.
958 config RTC_DRV_AB3100
959 tristate "ST-Ericsson AB3100 RTC"
960 depends on AB3100_CORE
961 default y if AB3100_CORE
963 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
964 support. This chip contains a battery- and capacitor-backed RTC.
966 config RTC_DRV_AB8500
967 tristate "ST-Ericsson AB8500 RTC"
968 depends on AB8500_CORE
970 select RTC_INTF_DEV_UIE_EMUL
972 Select this to enable the ST-Ericsson AB8500 power management IC RTC
973 support. This chip contains a battery- and capacitor-backed RTC.
975 config RTC_DRV_NUC900
976 tristate "NUC910/NUC920 RTC driver"
977 depends on ARCH_W90X900
979 If you say yes here you get support for the RTC subsystem of the
980 NUC910/NUC920 used in embedded systems.
982 comment "on-CPU RTC drivers"
984 config RTC_DRV_DAVINCI
985 tristate "TI DaVinci RTC"
986 depends on ARCH_DAVINCI_DM365
988 If you say yes here you get support for the RTC on the
989 DaVinci platforms (DM365).
991 This driver can also be built as a module. If so, the module
992 will be called rtc-davinci.
995 tristate "Freescale IMX DryIce Real Time Clock"
998 Support for Freescale IMX DryIce RTC
1000 This driver can also be built as a module, if so, the module
1001 will be called "rtc-imxdi".
1005 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
1007 Say "yes" here to support the on chip real time clock
1008 present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
1010 This driver can also be built as a module, if so, module
1011 will be called rtc-omap.
1016 This will include RTC support for Samsung SoCs. If
1017 you want to include RTC support for any machine, kindly
1018 select this in the respective mach-XXXX/Kconfig file.
1021 tristate "Samsung S3C series SoC RTC"
1022 depends on ARCH_S3C64XX || HAVE_S3C_RTC
1024 RTC (Realtime Clock) driver for the clock inbuilt into the
1025 Samsung S3C24XX series of SoCs. This can provide periodic
1026 interrupt rates from 1Hz to 64Hz for user programs, and
1029 The driver currently supports the common features on all the
1030 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1033 This driver can also be build as a module. If so, the module
1034 will be called rtc-s3c.
1036 config RTC_DRV_EP93XX
1037 tristate "Cirrus Logic EP93XX"
1038 depends on ARCH_EP93XX
1040 If you say yes here you get support for the
1041 RTC embedded in the Cirrus Logic EP93XX processors.
1043 This driver can also be built as a module. If so, the module
1044 will be called rtc-ep93xx.
1046 config RTC_DRV_SA1100
1047 tristate "SA11x0/PXA2xx/PXA910"
1048 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1050 If you say Y here you will get access to the real time clock
1051 built into your SA11x0 or PXA2xx CPU.
1053 To compile this driver as a module, choose M here: the
1054 module will be called rtc-sa1100.
1057 tristate "SuperH On-Chip RTC"
1058 depends on SUPERH && HAVE_CLK
1060 Say Y here to enable support for the on-chip RTC found in
1061 most SuperH processors.
1063 To compile this driver as a module, choose M here: the
1064 module will be called rtc-sh.
1066 config RTC_DRV_VR41XX
1067 tristate "NEC VR41XX"
1068 depends on CPU_VR41XX
1070 If you say Y here you will get access to the real time clock
1071 built into your NEC VR41XX CPU.
1073 To compile this driver as a module, choose M here: the
1074 module will be called rtc-vr41xx.
1076 config RTC_DRV_PL030
1077 tristate "ARM AMBA PL030 RTC"
1080 If you say Y here you will get access to ARM AMBA
1081 PrimeCell PL030 RTC found on certain ARM SOCs.
1083 To compile this driver as a module, choose M here: the
1084 module will be called rtc-pl030.
1086 config RTC_DRV_PL031
1087 tristate "ARM AMBA PL031 RTC"
1090 If you say Y here you will get access to ARM AMBA
1091 PrimeCell PL031 RTC found on certain ARM SOCs.
1093 To compile this driver as a module, choose M here: the
1094 module will be called rtc-pl031.
1096 config RTC_DRV_AT32AP700X
1097 tristate "AT32AP700X series RTC"
1098 depends on PLATFORM_AT32AP
1100 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1101 AT32AP700x family processors.
1103 config RTC_DRV_AT91RM9200
1104 tristate "AT91RM9200 or some AT91SAM9 RTC"
1105 depends on ARCH_AT91
1107 Driver for the internal RTC (Realtime Clock) module found on
1108 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1109 this is powered by the backup power supply.
1111 config RTC_DRV_AT91SAM9
1112 tristate "AT91SAM9 RTT as RTC"
1113 depends on ARCH_AT91 && !ARCH_AT91RM9200
1116 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1117 can be used as an RTC thanks to the backup power supply (e.g. a
1118 small coin cell battery) which keeps this block and the GPBR
1119 (General Purpose Backup Registers) block powered when the device
1121 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1122 probably want to use the real RTC block instead of the "RTT as an
1125 config RTC_DRV_AT91SAM9_RTT
1129 prompt "RTT module Number" if ARCH_AT91SAM9263
1130 depends on RTC_DRV_AT91SAM9
1132 This option is only relevant for legacy board support and
1133 won't be used when booting a DT board.
1135 More than one RTT module is available. You can choose which
1136 one will be used as an RTC. The default of zero is normally
1137 OK to use, though some systems use that for non-RTC purposes.
1139 config RTC_DRV_AT91SAM9_GPBR
1141 range 0 3 if !ARCH_AT91SAM9263
1142 range 0 15 if ARCH_AT91SAM9263
1144 prompt "Backup Register Number"
1145 depends on RTC_DRV_AT91SAM9
1147 This option is only relevant for legacy board support and
1148 won't be used when booting a DT board.
1150 The RTC driver needs to use one of the General Purpose Backup
1151 Registers (GPBRs) as well as the RTT. You can choose which one
1152 will be used. The default of zero is normally OK to use, but
1153 on some systems other software needs to use that register.
1155 config RTC_DRV_AU1XXX
1156 tristate "Au1xxx Counter0 RTC support"
1157 depends on MIPS_ALCHEMY
1159 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1160 counter) to be used as a RTC.
1162 This driver can also be built as a module. If so, the module
1163 will be called rtc-au1xxx.
1166 tristate "Blackfin On-Chip RTC"
1167 depends on BLACKFIN && !BF561
1169 If you say yes here you will get support for the
1170 Blackfin On-Chip Real Time Clock.
1172 This driver can also be built as a module. If so, the module
1173 will be called rtc-bfin.
1175 config RTC_DRV_RS5C313
1176 tristate "Ricoh RS5C313"
1177 depends on SH_LANDISK
1179 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1181 config RTC_DRV_GENERIC
1182 tristate "Generic RTC support"
1183 # Please consider writing a new RTC driver instead of using the generic
1185 depends on PARISC || M68K || PPC || SUPERH32
1187 Say Y or M here to enable RTC support on systems using the generic
1188 RTC abstraction. If you do not know what you are doing, you should
1192 tristate "PXA27x/PXA3xx"
1195 If you say Y here you will get access to the real time clock
1196 built into your PXA27x or PXA3xx CPU.
1198 This RTC driver uses PXA RTC registers available since pxa27x
1199 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1201 config RTC_DRV_VT8500
1202 tristate "VIA/WonderMedia 85xx SoC RTC"
1203 depends on ARCH_VT8500
1205 If you say Y here you will get access to the real time clock
1206 built into your VIA VT8500 SoC or its relatives.
1209 config RTC_DRV_SUN4V
1210 bool "SUN4V Hypervisor RTC"
1213 If you say Y here you will get support for the Hypervisor
1214 based RTC on SUN4V systems.
1216 config RTC_DRV_SUN6I
1217 tristate "Allwinner A31 RTC"
1218 depends on MACH_SUN6I || MACH_SUN8I
1220 If you say Y here you will get support for the RTC found on
1223 config RTC_DRV_SUNXI
1224 tristate "Allwinner sun4i/sun7i RTC"
1225 depends on MACH_SUN4I || MACH_SUN7I
1227 If you say Y here you will get support for the RTC found on
1230 config RTC_DRV_STARFIRE
1234 If you say Y here you will get support for the RTC found on
1237 config RTC_DRV_TX4939
1238 tristate "TX4939 SoC"
1239 depends on SOC_TX4939
1241 Driver for the internal RTC (Realtime Clock) module found on
1245 tristate "Marvell SoC RTC"
1246 depends on ARCH_DOVE || ARCH_MVEBU
1248 If you say yes here you will get support for the in-chip RTC
1249 that can be found in some of Marvell's SoC devices, such as
1250 the Kirkwood 88F6281 and 88F6192.
1252 This driver can also be built as a module. If so, the module
1253 will be called rtc-mv.
1259 If you say yes here you will get support for the RTC on PS3.
1261 This driver can also be built as a module. If so, the module
1262 will be called rtc-ps3.
1264 config RTC_DRV_COH901331
1265 tristate "ST-Ericsson COH 901 331 RTC"
1266 depends on ARCH_U300
1268 If you say Y here you will get access to ST-Ericsson
1269 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1272 This driver can also be built as a module. If so, the module
1273 will be called "rtc-coh901331".
1277 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1280 If you say yes here you will get support for the onboard
1281 STMP3xxx/i.MX23/i.MX28 RTC.
1283 This driver can also be built as a module. If so, the module
1284 will be called rtc-stmp3xxx.
1290 If you say Y here you will get support for the RTC found on
1291 the PCAP2 ASIC used on some Motorola phones.
1293 config RTC_DRV_MC13XXX
1294 depends on MFD_MC13XXX
1295 tristate "Freescale MC13xxx RTC"
1297 This enables support for the RTCs found on Freescale's PMICs
1298 MC13783 and MC13892.
1300 config RTC_DRV_MPC5121
1301 tristate "Freescale MPC5121 built-in RTC"
1302 depends on PPC_MPC512x || PPC_MPC52xx
1304 If you say yes here you will get support for the
1305 built-in RTC on MPC5121 or on MPC5200.
1307 This driver can also be built as a module. If so, the module
1308 will be called rtc-mpc5121.
1310 config RTC_DRV_JZ4740
1311 tristate "Ingenic JZ4740 SoC"
1312 depends on MACH_JZ4740
1314 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1317 This driver can also be buillt as a module. If so, the module
1318 will be called rtc-jz4740.
1320 config RTC_DRV_LPC32XX
1321 depends on ARCH_LPC32XX
1322 tristate "NXP LPC32XX RTC"
1324 This enables support for the NXP RTC in the LPC32XX
1326 This driver can also be buillt as a module. If so, the module
1327 will be called rtc-lpc32xx.
1329 config RTC_DRV_PM8XXX
1330 tristate "Qualcomm PMIC8XXX RTC"
1331 depends on MFD_PM8XXX || MFD_SPMI_PMIC
1333 If you say yes here you get support for the
1334 Qualcomm PMIC8XXX RTC.
1336 To compile this driver as a module, choose M here: the
1337 module will be called rtc-pm8xxx.
1339 config RTC_DRV_TEGRA
1340 tristate "NVIDIA Tegra Internal RTC driver"
1341 depends on ARCH_TEGRA
1343 If you say yes here you get support for the
1344 Tegra 200 series internal RTC module.
1346 This drive can also be built as a module. If so, the module
1347 will be called rtc-tegra.
1350 tristate "Tilera hypervisor RTC support"
1353 Enable support for the Linux driver side of the Tilera
1354 hypervisor's real-time clock interface.
1357 tristate "PKUnity v3 RTC support"
1358 depends on ARCH_PUV3
1360 This enables support for the RTC in the PKUnity-v3 SoCs.
1362 This drive can also be built as a module. If so, the module
1363 will be called rtc-puv3.
1365 config RTC_DRV_LOONGSON1
1366 tristate "loongson1 RTC support"
1367 depends on MACH_LOONGSON1
1369 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1370 counter) to be used as a RTC.
1372 This driver can also be built as a module. If so, the module
1373 will be called rtc-ls1x.
1376 tristate "Freescale MXC Real Time Clock"
1379 If you say yes here you get support for the Freescale MXC
1382 This driver can also be built as a module, if so, the module
1383 will be called "rtc-mxc".
1386 tristate "Freescale SNVS RTC support"
1387 depends on HAS_IOMEM
1390 If you say yes here you get support for the Freescale SNVS
1391 Low Power (LP) RTC module.
1393 This driver can also be built as a module, if so, the module
1394 will be called "rtc-snvs".
1396 config RTC_DRV_SIRFSOC
1397 tristate "SiRFSOC RTC"
1398 depends on ARCH_SIRF
1400 Say "yes" here to support the real time clock on SiRF SOC chips.
1401 This driver can also be built as a module called rtc-sirfsoc.
1403 config RTC_DRV_MOXART
1404 tristate "MOXA ART RTC"
1405 depends on ARCH_MOXART || COMPILE_TEST
1407 If you say yes here you get support for the MOXA ART
1410 This driver can also be built as a module. If so, the module
1411 will be called rtc-moxart
1413 config RTC_DRV_XGENE
1414 tristate "APM X-Gene RTC"
1415 depends on HAS_IOMEM
1417 If you say yes here you get support for the APM X-Gene SoC real time
1420 This driver can also be built as a module, if so, the module
1421 will be called "rtc-xgene".
1423 comment "HID Sensor RTC drivers"
1425 config RTC_DRV_HID_SENSOR_TIME
1426 tristate "HID Sensor Time"
1429 select HID_SENSOR_HUB
1430 select HID_SENSOR_IIO_COMMON
1432 Say yes here to build support for the HID Sensors of type Time.
1433 This drivers makes such sensors available as RTCs.
1435 If this driver is compiled as a module, it will be named
1436 rtc-hid-sensor-time.