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_DS1307
157 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
159 If you say yes here you get support for various compatible RTC
160 chips (often with battery backup) connected with I2C. This driver
161 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
162 EPSON RX-8025 and probably other chips. In some cases the RTC
163 must already have been initialized (by manufacturing or a
166 The first seven registers on these chips hold an RTC, and other
167 registers may add features such as NVRAM, a trickle charger for
168 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
169 sysfs, but other chip features may not be available.
171 This driver can also be built as a module. If so, the module
172 will be called rtc-ds1307.
174 config RTC_DRV_DS1374
175 tristate "Dallas/Maxim DS1374"
178 If you say yes here you get support for Dallas Semiconductor
179 DS1374 real-time clock chips. If an interrupt is associated
180 with the device, the alarm functionality is supported.
182 This driver can also be built as a module. If so, the module
183 will be called rtc-ds1374.
185 config RTC_DRV_DS1672
186 tristate "Dallas/Maxim DS1672"
188 If you say yes here you get support for the
189 Dallas/Maxim DS1672 timekeeping chip.
191 This driver can also be built as a module. If so, the module
192 will be called rtc-ds1672.
194 config RTC_DRV_DS3232
195 tristate "Dallas/Maxim DS3232"
198 If you say yes here you get support for Dallas Semiconductor
199 DS3232 real-time clock chips. If an interrupt is associated
200 with the device, the alarm functionality is supported.
202 This driver can also be built as a module. If so, the module
203 will be called rtc-ds3232.
205 config RTC_DRV_LP8788
206 tristate "TI LP8788 RTC driver"
207 depends on MFD_LP8788
209 Say Y to enable support for the LP8788 RTC/ALARM driver.
211 config RTC_DRV_MAX6900
212 tristate "Maxim MAX6900"
214 If you say yes here you will get support for the
215 Maxim MAX6900 I2C RTC chip.
217 This driver can also be built as a module. If so, the module
218 will be called rtc-max6900.
220 config RTC_DRV_MAX8907
221 tristate "Maxim MAX8907"
222 depends on MFD_MAX8907
224 If you say yes here you will get support for the
225 RTC of Maxim MAX8907 PMIC.
227 This driver can also be built as a module. If so, the module
228 will be called rtc-max8907.
230 config RTC_DRV_MAX8925
231 tristate "Maxim MAX8925"
232 depends on MFD_MAX8925
234 If you say yes here you will get support for the
235 RTC of Maxim MAX8925 PMIC.
237 This driver can also be built as a module. If so, the module
238 will be called rtc-max8925.
240 config RTC_DRV_MAX8998
241 tristate "Maxim MAX8998"
242 depends on MFD_MAX8998
244 If you say yes here you will get support for the
245 RTC of Maxim MAX8998 PMIC.
247 This driver can also be built as a module. If so, the module
248 will be called rtc-max8998.
250 config RTC_DRV_MAX8997
251 tristate "Maxim MAX8997"
252 depends on MFD_MAX8997
254 If you say yes here you will get support for the
255 RTC of Maxim MAX8997 PMIC.
257 This driver can also be built as a module. If so, the module
258 will be called rtc-max8997.
260 config RTC_DRV_MAX77686
261 tristate "Maxim MAX77686"
262 depends on MFD_MAX77686
264 If you say yes here you will get support for the
265 RTC of Maxim MAX77686 PMIC.
267 This driver can also be built as a module. If so, the module
268 will be called rtc-max77686.
270 config RTC_DRV_RS5C372
271 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
273 If you say yes here you get support for the
274 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
276 This driver can also be built as a module. If so, the module
277 will be called rtc-rs5c372.
279 config RTC_DRV_ISL1208
280 tristate "Intersil ISL1208"
282 If you say yes here you get support for the
283 Intersil ISL1208 RTC chip.
285 This driver can also be built as a module. If so, the module
286 will be called rtc-isl1208.
288 config RTC_DRV_ISL12022
289 tristate "Intersil ISL12022"
291 If you say yes here you get support for the
292 Intersil ISL12022 RTC chip.
294 This driver can also be built as a module. If so, the module
295 will be called rtc-isl12022.
298 tristate "Xicor/Intersil X1205"
300 If you say yes here you get support for the
301 Xicor/Intersil X1205 RTC chip.
303 This driver can also be built as a module. If so, the module
304 will be called rtc-x1205.
306 config RTC_DRV_PALMAS
307 tristate "TI Palmas RTC driver"
308 depends on MFD_PALMAS
310 If you say yes here you get support for the RTC of TI PALMA series PMIC
313 This driver can also be built as a module. If so, the module
314 will be called rtc-palma.
316 config RTC_DRV_PCF8523
317 tristate "NXP PCF8523"
319 If you say yes here you get support for the NXP PCF8523 RTC
322 This driver can also be built as a module. If so, the module
323 will be called rtc-pcf8523.
325 config RTC_DRV_PCF8563
326 tristate "Philips PCF8563/Epson RTC8564"
328 If you say yes here you get support for the
329 Philips PCF8563 RTC chip. The Epson RTC8564
332 This driver can also be built as a module. If so, the module
333 will be called rtc-pcf8563.
335 config RTC_DRV_PCF8583
336 tristate "Philips PCF8583"
338 If you say yes here you get support for the Philips PCF8583
339 RTC chip found on Acorn RiscPCs. This driver supports the
340 platform specific method of retrieving the current year from
341 the RTC's SRAM. It will work on other platforms with the same
342 chip, but the year will probably have to be tweaked.
344 This driver can also be built as a module. If so, the module
345 will be called rtc-pcf8583.
347 config RTC_DRV_M41T80
348 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
350 If you say Y here you will get support for the ST M41T60
351 and M41T80 RTC chips series. Currently, the following chips are
352 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
353 M41ST85, and M41ST87.
355 This driver can also be built as a module. If so, the module
356 will be called rtc-m41t80.
358 config RTC_DRV_M41T80_WDT
359 bool "ST M41T65/M41T80 series RTC watchdog timer"
360 depends on RTC_DRV_M41T80
362 If you say Y here you will get support for the
363 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
366 tristate "TI BQ32000"
368 If you say Y here you will get support for the TI
369 BQ32000 I2C RTC chip.
371 This driver can also be built as a module. If so, the module
372 will be called rtc-bq32k.
374 config RTC_DRV_DM355EVM
375 tristate "TI DaVinci DM355 EVM RTC"
376 depends on MFD_DM355EVM_MSP
378 Supports the RTC firmware in the MSP430 on the DM355 EVM.
380 config RTC_DRV_TWL92330
381 boolean "TI TWL92330/Menelaus"
384 If you say yes here you get support for the RTC on the
385 TWL92330 "Menelaus" power management chip, used with OMAP2
386 platforms. The support is integrated with the rest of
387 the Menelaus driver; it's not separate module.
389 config RTC_DRV_TWL4030
390 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
391 depends on TWL4030_CORE
393 If you say yes here you get support for the RTC on the
394 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
396 This driver can also be built as a module. If so, the module
397 will be called rtc-twl.
399 config RTC_DRV_TPS6586X
400 tristate "TI TPS6586X RTC driver"
401 depends on MFD_TPS6586X
403 TI Power Management IC TPS6586X supports RTC functionality
404 along with alarm. This driver supports the RTC driver for
405 the TPS6586X RTC module.
407 config RTC_DRV_TPS65910
408 tristate "TI TPS65910 RTC driver"
409 depends on RTC_CLASS && MFD_TPS65910
411 If you say yes here you get support for the RTC on the
414 This driver can also be built as a module. If so, the module
415 will be called rtc-tps65910.
418 tristate "rk808 rtc for rk"
421 enable rk808 rtc for system
423 config RTC_DRV_TPS80031
424 tristate "TI TPS80031/TPS80032 RTC driver"
425 depends on MFD_TPS80031
427 TI Power Management IC TPS80031 supports RTC functionality
428 along with alarm. This driver supports the RTC driver for
429 the TPS80031 RTC module.
431 config RTC_DRV_RC5T583
432 tristate "RICOH 5T583 RTC driver"
433 depends on MFD_RC5T583
435 If you say yes here you get support for the RTC on the
438 This driver can also be built as a module. If so, the module
439 will be called rtc-rc5t583.
441 config RTC_DRV_S35390A
442 tristate "Seiko Instruments S-35390A"
445 If you say yes here you will get support for the Seiko
446 Instruments S-35390A.
448 This driver can also be built as a module. If so the module
449 will be called rtc-s35390a.
451 config RTC_DRV_FM3130
452 tristate "Ramtron FM3130"
454 If you say Y here you will get support for the
455 Ramtron FM3130 RTC chips.
456 Ramtron FM3130 is a chip with two separate devices inside,
457 RTC clock and FRAM. This driver provides only RTC functionality.
459 This driver can also be built as a module. If so the module
460 will be called rtc-fm3130.
462 config RTC_DRV_RX8581
463 tristate "Epson RX-8581"
465 If you say yes here you will get support for the Epson RX-8581.
467 This driver can also be built as a module. If so the module
468 will be called rtc-rx8581.
470 config RTC_DRV_RX8025
471 tristate "Epson RX-8025SA/NB"
473 If you say yes here you get support for the Epson
474 RX-8025SA/NB RTC chips.
476 This driver can also be built as a module. If so, the module
477 will be called rtc-rx8025.
479 config RTC_DRV_EM3027
480 tristate "EM Microelectronic EM3027"
482 If you say yes here you get support for the EM
483 Microelectronic EM3027 RTC chips.
485 This driver can also be built as a module. If so, the module
486 will be called rtc-em3027.
488 config RTC_DRV_RV3029C2
489 tristate "Micro Crystal RTC"
491 If you say yes here you get support for the Micro Crystal
494 This driver can also be built as a module. If so, the module
495 will be called rtc-rv3029c2.
499 comment "SPI RTC drivers"
503 config RTC_DRV_M41T93
506 If you say yes here you will get support for the
507 ST M41T93 SPI RTC chip.
509 This driver can also be built as a module. If so, the module
510 will be called rtc-m41t93.
512 config RTC_DRV_M41T94
515 If you say yes here you will get support for the
516 ST M41T94 SPI RTC chip.
518 This driver can also be built as a module. If so, the module
519 will be called rtc-m41t94.
521 config RTC_DRV_DS1305
522 tristate "Dallas/Maxim DS1305/DS1306"
524 Select this driver to get support for the Dallas/Maxim DS1305
525 and DS1306 real time clock chips. These support a trickle
526 charger, alarms, and NVRAM in addition to the clock.
528 This driver can also be built as a module. If so, the module
529 will be called rtc-ds1305.
531 config RTC_DRV_DS1390
532 tristate "Dallas/Maxim DS1390/93/94"
534 If you say yes here you get support for the
535 Dallas/Maxim DS1390/93/94 chips.
537 This driver only supports the RTC feature, and not other chip
538 features such as alarms and trickle charging.
540 This driver can also be built as a module. If so, the module
541 will be called rtc-ds1390.
543 config RTC_DRV_MAX6902
544 tristate "Maxim MAX6902"
546 If you say yes here you will get support for the
547 Maxim MAX6902 SPI RTC chip.
549 This driver can also be built as a module. If so, the module
550 will be called rtc-max6902.
553 tristate "Epson RTC-9701JE"
555 If you say yes here you will get support for the
556 Epson RTC-9701JE SPI RTC chip.
558 This driver can also be built as a module. If so, the module
559 will be called rtc-r9701.
561 config RTC_DRV_RS5C348
562 tristate "Ricoh RS5C348A/B"
564 If you say yes here you get support for the
565 Ricoh RS5C348A and RS5C348B RTC chips.
567 This driver can also be built as a module. If so, the module
568 will be called rtc-rs5c348.
570 config RTC_DRV_DS3234
571 tristate "Maxim/Dallas DS3234"
573 If you say yes here you get support for the
574 Maxim/Dallas DS3234 SPI RTC chip.
576 This driver can also be built as a module. If so, the module
577 will be called rtc-ds3234.
579 config RTC_DRV_PCF2123
580 tristate "NXP PCF2123"
582 If you say yes here you get support for the NXP PCF2123
585 This driver can also be built as a module. If so, the module
586 will be called rtc-pcf2123.
588 config RTC_DRV_RX4581
589 tristate "Epson RX-4581"
591 If you say yes here you will get support for the Epson RX-4581.
593 This driver can also be built as a module. If so the module
594 will be called rtc-rx4581.
598 comment "Platform RTC drivers"
600 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
601 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
602 # global rtc_lock ... it's not yet just another platform_device.
605 tristate "PC-style 'CMOS'"
606 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
609 Say "yes" here to get direct support for the real time clock
610 found in every PC or ACPI-based system, and some other boards.
611 Specifically the original MC146818, compatibles like those in
612 PC south bridges, the DS12887 or M48T86, some multifunction
613 or LPC bus chips, and so on.
615 Your system will need to define the platform device used by
616 this driver, otherwise it won't be accessible. This means
617 you can safely enable this driver if you don't know whether
618 or not your board has this kind of hardware.
620 This driver can also be built as a module. If so, the module
621 will be called rtc-cmos.
624 tristate "Virtual RTC for Intel MID platforms"
625 depends on X86_INTEL_MID
626 default y if X86_INTEL_MID
629 Say "yes" here to get direct support for the real time clock
630 found on Moorestown platforms. The VRTC is a emulated RTC that
631 derives its clock source from a real RTC in the PMIC. The MC146818
632 style programming interface is mostly conserved, but any
633 updates are done via IPC calls to the system controller FW.
635 config RTC_DRV_DS1216
636 tristate "Dallas DS1216"
639 If you say yes here you get support for the Dallas DS1216 RTC chips.
641 config RTC_DRV_DS1286
642 tristate "Dallas DS1286"
644 If you say yes here you get support for the Dallas DS1286 RTC chips.
646 config RTC_DRV_DS1302
647 tristate "Dallas DS1302"
648 depends on SH_SECUREEDGE5410
650 If you say yes here you get support for the Dallas DS1302 RTC chips.
652 config RTC_DRV_DS1511
653 tristate "Dallas DS1511"
655 If you say yes here you get support for the
656 Dallas DS1511 timekeeping/watchdog chip.
658 This driver can also be built as a module. If so, the module
659 will be called rtc-ds1511.
661 config RTC_DRV_DS1553
662 tristate "Maxim/Dallas DS1553"
664 If you say yes here you get support for the
665 Maxim/Dallas DS1553 timekeeping chip.
667 This driver can also be built as a module. If so, the module
668 will be called rtc-ds1553.
670 config RTC_DRV_DS1742
671 tristate "Maxim/Dallas DS1742/1743"
673 If you say yes here you get support for the
674 Maxim/Dallas DS1742/1743 timekeeping chip.
676 This driver can also be built as a module. If so, the module
677 will be called rtc-ds1742.
679 config RTC_DRV_DA9052
680 tristate "Dialog DA9052/DA9053 RTC"
681 depends on PMIC_DA9052
683 Say y here to support the RTC driver for Dialog Semiconductor
684 DA9052-BC and DA9053-AA/Bx PMICs.
686 config RTC_DRV_DA9055
687 tristate "Dialog Semiconductor DA9055 RTC"
688 depends on MFD_DA9055
690 If you say yes here you will get support for the
691 RTC of the Dialog DA9055 PMIC.
693 This driver can also be built as a module. If so, the module
694 will be called rtc-da9055
700 If you say yes here you will get support for the EFI
703 This driver can also be built as a module. If so, the module
704 will be called rtc-efi.
706 config RTC_DRV_STK17TA8
707 tristate "Simtek STK17TA8"
709 If you say yes here you get support for the
710 Simtek STK17TA8 timekeeping chip.
712 This driver can also be built as a module. If so, the module
713 will be called rtc-stk17ta8.
715 config RTC_DRV_M48T86
716 tristate "ST M48T86/Dallas DS12887"
718 If you say Y here you will get support for the
719 ST M48T86 and Dallas DS12887 RTC chips.
721 This driver can also be built as a module. If so, the module
722 will be called rtc-m48t86.
724 config RTC_DRV_M48T35
727 If you say Y here you will get support for the
730 This driver can also be built as a module, if so, the module
731 will be called "rtc-m48t35".
733 config RTC_DRV_M48T59
734 tristate "ST M48T59/M48T08/M48T02"
736 If you say Y here you will get support for the
737 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
739 These chips are usually found in Sun SPARC and UltraSPARC
742 This driver can also be built as a module, if so, the module
743 will be called "rtc-m48t59".
745 config RTC_DRV_MSM6242
746 tristate "Oki MSM6242"
748 If you say yes here you get support for the Oki MSM6242
749 timekeeping chip. It is used in some Amiga models (e.g. A2000).
751 This driver can also be built as a module. If so, the module
752 will be called rtc-msm6242.
754 config RTC_DRV_BQ4802
757 If you say Y here you will get support for the TI
760 This driver can also be built as a module. If so, the module
761 will be called rtc-bq4802.
763 config RTC_DRV_RP5C01
764 tristate "Ricoh RP5C01"
766 If you say yes here you get support for the Ricoh RP5C01
767 timekeeping chip. It is used in some Amiga models (e.g. A3000
770 This driver can also be built as a module. If so, the module
771 will be called rtc-rp5c01.
774 tristate "EM Microelectronic V3020"
776 If you say yes here you will get support for the
777 EM Microelectronic v3020 RTC chip.
779 This driver can also be built as a module. If so, the module
780 will be called rtc-v3020.
782 config RTC_DRV_DS2404
783 tristate "Dallas DS2404"
785 If you say yes here you get support for the
786 Dallas DS2404 RTC chip.
788 This driver can also be built as a module. If so, the module
789 will be called rtc-ds2404.
791 config RTC_DRV_WM831X
792 tristate "Wolfson Microelectronics WM831x RTC"
793 depends on MFD_WM831X
795 If you say yes here you will get support for the RTC subsystem
796 of the Wolfson Microelectronics WM831X series PMICs.
798 This driver can also be built as a module. If so, the module
799 will be called "rtc-wm831x".
801 config RTC_DRV_WM8350
802 tristate "Wolfson Microelectronics WM8350 RTC"
803 depends on MFD_WM8350
805 If you say yes here you will get support for the RTC subsystem
806 of the Wolfson Microelectronics WM8350.
808 This driver can also be built as a module. If so, the module
809 will be called "rtc-wm8350".
812 tristate "SPEAR ST RTC"
813 depends on PLAT_SPEAR
816 If you say Y here you will get support for the RTC found on
819 config RTC_DRV_PCF50633
820 depends on MFD_PCF50633
821 tristate "NXP PCF50633 RTC"
823 If you say yes here you get support for the RTC subsystem of the
824 NXP PCF50633 used in embedded systems.
826 config RTC_DRV_AB3100
827 tristate "ST-Ericsson AB3100 RTC"
828 depends on AB3100_CORE
829 default y if AB3100_CORE
831 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
832 support. This chip contains a battery- and capacitor-backed RTC.
834 config RTC_DRV_AB8500
835 tristate "ST-Ericsson AB8500 RTC"
836 depends on AB8500_CORE
838 select RTC_INTF_DEV_UIE_EMUL
840 Select this to enable the ST-Ericsson AB8500 power management IC RTC
841 support. This chip contains a battery- and capacitor-backed RTC.
843 config RTC_DRV_NUC900
844 tristate "NUC910/NUC920 RTC driver"
845 depends on ARCH_W90X900
847 If you say yes here you get support for the RTC subsystem of the
848 NUC910/NUC920 used in embedded systems.
850 comment "on-CPU RTC drivers"
852 config RTC_DRV_DAVINCI
853 tristate "TI DaVinci RTC"
854 depends on ARCH_DAVINCI_DM365
856 If you say yes here you get support for the RTC on the
857 DaVinci platforms (DM365).
859 This driver can also be built as a module. If so, the module
860 will be called rtc-davinci.
863 tristate "Freescale IMX DryIce Real Time Clock"
866 Support for Freescale IMX DryIce RTC
868 This driver can also be built as a module, if so, the module
869 will be called "rtc-imxdi".
873 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
875 Say "yes" here to support the on chip real time clock
876 present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
878 This driver can also be built as a module, if so, module
879 will be called rtc-omap.
884 This will include RTC support for Samsung SoCs. If
885 you want to include RTC support for any machine, kindly
886 select this in the respective mach-XXXX/Kconfig file.
889 tristate "Samsung S3C series SoC RTC"
890 depends on ARCH_S3C64XX || HAVE_S3C_RTC
892 RTC (Realtime Clock) driver for the clock inbuilt into the
893 Samsung S3C24XX series of SoCs. This can provide periodic
894 interrupt rates from 1Hz to 64Hz for user programs, and
897 The driver currently supports the common features on all the
898 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
901 This driver can also be build as a module. If so, the module
902 will be called rtc-s3c.
904 config RTC_DRV_EP93XX
905 tristate "Cirrus Logic EP93XX"
906 depends on ARCH_EP93XX
908 If you say yes here you get support for the
909 RTC embedded in the Cirrus Logic EP93XX processors.
911 This driver can also be built as a module. If so, the module
912 will be called rtc-ep93xx.
914 config RTC_DRV_SA1100
915 tristate "SA11x0/PXA2xx/PXA910"
916 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
918 If you say Y here you will get access to the real time clock
919 built into your SA11x0 or PXA2xx CPU.
921 To compile this driver as a module, choose M here: the
922 module will be called rtc-sa1100.
925 tristate "SuperH On-Chip RTC"
926 depends on SUPERH && HAVE_CLK
928 Say Y here to enable support for the on-chip RTC found in
929 most SuperH processors.
931 To compile this driver as a module, choose M here: the
932 module will be called rtc-sh.
934 config RTC_DRV_VR41XX
935 tristate "NEC VR41XX"
936 depends on CPU_VR41XX
938 If you say Y here you will get access to the real time clock
939 built into your NEC VR41XX CPU.
941 To compile this driver as a module, choose M here: the
942 module will be called rtc-vr41xx.
945 tristate "ARM AMBA PL030 RTC"
948 If you say Y here you will get access to ARM AMBA
949 PrimeCell PL030 RTC found on certain ARM SOCs.
951 To compile this driver as a module, choose M here: the
952 module will be called rtc-pl030.
955 tristate "ARM AMBA PL031 RTC"
958 If you say Y here you will get access to ARM AMBA
959 PrimeCell PL031 RTC found on certain ARM SOCs.
961 To compile this driver as a module, choose M here: the
962 module will be called rtc-pl031.
964 config RTC_DRV_AT32AP700X
965 tristate "AT32AP700X series RTC"
966 depends on PLATFORM_AT32AP
968 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
969 AT32AP700x family processors.
971 config RTC_DRV_AT91RM9200
972 tristate "AT91RM9200 or some AT91SAM9 RTC"
975 Driver for the internal RTC (Realtime Clock) module found on
976 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
977 this is powered by the backup power supply.
979 config RTC_DRV_AT91SAM9
980 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
981 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
983 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
984 (Real Time Timer). These timers are powered by the backup power
985 supply (such as a small coin cell battery), but do not need to
988 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
989 dedicated RTC module and leave the RTT available for other uses.)
991 config RTC_DRV_AT91SAM9_RTT
995 prompt "RTT module Number" if ARCH_AT91SAM9263
996 depends on RTC_DRV_AT91SAM9
998 More than one RTT module is available. You can choose which
999 one will be used as an RTC. The default of zero is normally
1000 OK to use, though some systems use that for non-RTC purposes.
1002 config RTC_DRV_AT91SAM9_GPBR
1004 range 0 3 if !ARCH_AT91SAM9263
1005 range 0 15 if ARCH_AT91SAM9263
1007 prompt "Backup Register Number"
1008 depends on RTC_DRV_AT91SAM9
1010 The RTC driver needs to use one of the General Purpose Backup
1011 Registers (GPBRs) as well as the RTT. You can choose which one
1012 will be used. The default of zero is normally OK to use, but
1013 on some systems other software needs to use that register.
1015 config RTC_DRV_AU1XXX
1016 tristate "Au1xxx Counter0 RTC support"
1017 depends on MIPS_ALCHEMY
1019 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1020 counter) to be used as a RTC.
1022 This driver can also be built as a module. If so, the module
1023 will be called rtc-au1xxx.
1026 tristate "Blackfin On-Chip RTC"
1027 depends on BLACKFIN && !BF561
1029 If you say yes here you will get support for the
1030 Blackfin On-Chip Real Time Clock.
1032 This driver can also be built as a module. If so, the module
1033 will be called rtc-bfin.
1035 config RTC_DRV_RS5C313
1036 tristate "Ricoh RS5C313"
1037 depends on SH_LANDISK
1039 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1041 config RTC_DRV_GENERIC
1042 tristate "Generic RTC support"
1043 # Please consider writing a new RTC driver instead of using the generic
1045 depends on PARISC || M68K || PPC || SUPERH32
1047 Say Y or M here to enable RTC support on systems using the generic
1048 RTC abstraction. If you do not know what you are doing, you should
1052 tristate "PXA27x/PXA3xx"
1055 If you say Y here you will get access to the real time clock
1056 built into your PXA27x or PXA3xx CPU.
1058 This RTC driver uses PXA RTC registers available since pxa27x
1059 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1061 config RTC_DRV_VT8500
1062 tristate "VIA/WonderMedia 85xx SoC RTC"
1063 depends on ARCH_VT8500
1065 If you say Y here you will get access to the real time clock
1066 built into your VIA VT8500 SoC or its relatives.
1069 config RTC_DRV_SUN4V
1070 bool "SUN4V Hypervisor RTC"
1073 If you say Y here you will get support for the Hypervisor
1074 based RTC on SUN4V systems.
1076 config RTC_DRV_STARFIRE
1080 If you say Y here you will get support for the RTC found on
1083 config RTC_DRV_TX4939
1084 tristate "TX4939 SoC"
1085 depends on SOC_TX4939
1087 Driver for the internal RTC (Realtime Clock) module found on
1091 tristate "Marvell SoC RTC"
1092 depends on ARCH_KIRKWOOD || ARCH_DOVE || ARCH_MVEBU
1094 If you say yes here you will get support for the in-chip RTC
1095 that can be found in some of Marvell's SoC devices, such as
1096 the Kirkwood 88F6281 and 88F6192.
1098 This driver can also be built as a module. If so, the module
1099 will be called rtc-mv.
1105 If you say yes here you will get support for the RTC on PS3.
1107 This driver can also be built as a module. If so, the module
1108 will be called rtc-ps3.
1110 config RTC_DRV_COH901331
1111 tristate "ST-Ericsson COH 901 331 RTC"
1112 depends on ARCH_U300
1114 If you say Y here you will get access to ST-Ericsson
1115 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1118 This driver can also be built as a module. If so, the module
1119 will be called "rtc-coh901331".
1123 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1126 If you say yes here you will get support for the onboard
1127 STMP3xxx/i.MX23/i.MX28 RTC.
1129 This driver can also be built as a module. If so, the module
1130 will be called rtc-stmp3xxx.
1136 If you say Y here you will get support for the RTC found on
1137 the PCAP2 ASIC used on some Motorola phones.
1139 config RTC_DRV_MC13XXX
1140 depends on MFD_MC13XXX
1141 tristate "Freescale MC13xxx RTC"
1143 This enables support for the RTCs found on Freescale's PMICs
1144 MC13783 and MC13892.
1146 config RTC_DRV_MPC5121
1147 tristate "Freescale MPC5121 built-in RTC"
1148 depends on PPC_MPC512x || PPC_MPC52xx
1150 If you say yes here you will get support for the
1151 built-in RTC on MPC5121 or on MPC5200.
1153 This driver can also be built as a module. If so, the module
1154 will be called rtc-mpc5121.
1156 config RTC_DRV_JZ4740
1157 tristate "Ingenic JZ4740 SoC"
1158 depends on MACH_JZ4740
1160 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1163 This driver can also be buillt as a module. If so, the module
1164 will be called rtc-jz4740.
1166 config RTC_DRV_LPC32XX
1167 depends on ARCH_LPC32XX
1168 tristate "NXP LPC32XX RTC"
1170 This enables support for the NXP RTC in the LPC32XX
1172 This driver can also be buillt as a module. If so, the module
1173 will be called rtc-lpc32xx.
1175 config RTC_DRV_PM8XXX
1176 tristate "Qualcomm PMIC8XXX RTC"
1177 depends on MFD_PM8XXX
1179 If you say yes here you get support for the
1180 Qualcomm PMIC8XXX RTC.
1182 To compile this driver as a module, choose M here: the
1183 module will be called rtc-pm8xxx.
1185 config RTC_DRV_TEGRA
1186 tristate "NVIDIA Tegra Internal RTC driver"
1187 depends on ARCH_TEGRA
1189 If you say yes here you get support for the
1190 Tegra 200 series internal RTC module.
1192 This drive can also be built as a module. If so, the module
1193 will be called rtc-tegra.
1196 tristate "Tilera hypervisor RTC support"
1199 Enable support for the Linux driver side of the Tilera
1200 hypervisor's real-time clock interface.
1203 tristate "PKUnity v3 RTC support"
1204 depends on ARCH_PUV3
1206 This enables support for the RTC in the PKUnity-v3 SoCs.
1208 This drive can also be built as a module. If so, the module
1209 will be called rtc-puv3.
1211 config RTC_DRV_LOONGSON1
1212 tristate "loongson1 RTC support"
1213 depends on MACH_LOONGSON1
1215 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1216 counter) to be used as a RTC.
1218 This driver can also be built as a module. If so, the module
1219 will be called rtc-ls1x.
1222 tristate "Freescale MXC Real Time Clock"
1225 If you say yes here you get support for the Freescale MXC
1228 This driver can also be built as a module, if so, the module
1229 will be called "rtc-mxc".
1232 tristate "Freescale SNVS RTC support"
1233 depends on HAS_IOMEM
1236 If you say yes here you get support for the Freescale SNVS
1237 Low Power (LP) RTC module.
1239 This driver can also be built as a module, if so, the module
1240 will be called "rtc-snvs".
1242 comment "HID Sensor RTC drivers"
1244 config RTC_DRV_HID_SENSOR_TIME
1245 tristate "HID Sensor Time"
1248 select HID_SENSOR_HUB
1249 select HID_SENSOR_IIO_COMMON
1251 Say yes here to build support for the HID Sensors of type Time.
1252 This drivers makes such sensors available as RTCs.
1254 If this driver is compiled as a module, it will be named
1255 rtc-hid-sensor-time.