2 # RTC class/drivers configuration
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"
22 depends on RTC_CLASS = y
25 If you say yes here, the system time (wall clock) will be set using
26 the value read from a specified RTC device. This is useful to avoid
27 unnecessary fsck runs at boot time, and to network better.
29 config RTC_HCTOSYS_DEVICE
30 string "RTC used to set the system time"
31 depends on RTC_HCTOSYS = y
34 The RTC device that will be used to (re)initialize the system
35 clock, usually rtc0. Initialization is done when the system
36 starts up, and when it resumes from a low power state. This
37 device should record time in UTC, since the kernel won't do
40 The driver for this RTC device must be loaded before late_initcall
41 functions run, so it must usually be statically linked.
43 This clock should be battery-backed, so that it reads the correct
44 time when the system boots from a power-off state. Otherwise, your
45 system will need an external clock source (like an NTP server).
47 If the clock you specify here is not battery backed, it may still
48 be useful to reinitialize system time when resuming from system
49 sleep states. Do not specify an RTC here unless it stays powered
50 during all this system's supported sleep states.
53 bool "RTC debug support"
54 depends on RTC_CLASS = y
56 Say yes here to enable debugging support in the RTC framework
57 and individual RTC drivers.
59 comment "RTC interfaces"
62 boolean "/sys/class/rtc/rtcN (sysfs)"
66 Say yes here if you want to use your RTCs using sysfs interfaces,
67 /sys/class/rtc/rtc0 through /sys/.../rtcN.
72 boolean "/proc/driver/rtc (procfs for rtc0)"
76 Say yes here if you want to use your first RTC through the proc
77 interface, /proc/driver/rtc. Other RTCs will not be available
83 boolean "/dev/rtcN (character devices)"
86 Say yes here if you want to use your RTCs using the /dev
87 interfaces, which "udev" sets up as /dev/rtc0 through
90 You may want to set up a symbolic link so one of these
91 can be accessed as /dev/rtc, which is a name
92 expected by "hwclock" and some other programs. Recent
93 versions of "udev" are known to set up the symlink for you.
97 config RTC_INTF_DEV_UIE_EMUL
98 bool "RTC UIE emulation on dev interface"
99 depends on RTC_INTF_DEV
101 Provides an emulation for RTC_UIE if the underlying rtc chip
102 driver does not expose RTC_UIE ioctls. Those requests generate
103 once-per-second update interrupts, used for synchronization.
105 The emulation code will read the time from the hardware
106 clock several times per second, please enable this option
107 only if you know that you really need it.
109 config RTC_INTF_ALARM
110 bool "Android alarm driver"
114 Provides non-wakeup and rtc backed wakeup alarms based on rtc or
115 elapsed realtime, and a non-wakeup alarm on the monotonic clock.
116 Also provides an interface to set the wall time which must be used
117 for elapsed realtime to work.
119 config RTC_INTF_ALARM_DEV
120 bool "Android alarm device"
121 depends on RTC_INTF_ALARM
124 Exports the alarm interface to user-space.
127 tristate "Support auto wake up"
128 depends on RTC_INTF_ALARM_DEV
130 config AUTO_WAKE_UP_PERIOD
131 int "auto wake up period(sec)"
132 depends on AUTO_WAKE_UP
136 tristate "Test driver/device"
138 If you say yes here you get support for the
139 RTC test driver. It's a software RTC which can be
140 used to test the RTC subsystem APIs. It gets
141 the time from the system clock.
142 You want this driver only if you are doing development
143 on the RTC subsystem. Please read the source code
146 This driver can also be built as a module. If so, the module
147 will be called rtc-test.
149 comment "I2C RTC drivers"
154 config RTC_DRV_88PM860X
155 tristate "Marvell 88PM860x"
156 depends on RTC_CLASS && I2C && MFD_88PM860X
158 If you say yes here you get support for RTC function in Marvell
161 This driver can also be built as a module. If so, the module
162 will be called rtc-88pm860x.
165 tristate "RK2818 or RK29 extern HYM8563 RTC"
166 depends on I2C_RK2818 || I2C_RK29 || I2C_RK30
168 If you say yes here you will get support for the
169 HYM8563 I2C RTC chip.
170 This driver can also be built as a module. If so, the module
171 will be called rtc-HYM8563.
175 depends on I2C_RK2818 || I2C_RK29
177 If you say Y here you will get support for the ST M41T66.
179 config RTC_DRV_DS1307
180 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
182 If you say yes here you get support for various compatible RTC
183 chips (often with battery backup) connected with I2C. This driver
184 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
185 EPSON RX-8025 and probably other chips. In some cases the RTC
186 must already have been initialized (by manufacturing or a
189 The first seven registers on these chips hold an RTC, and other
190 registers may add features such as NVRAM, a trickle charger for
191 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
192 sysfs, but other chip features may not be available.
194 This driver can also be built as a module. If so, the module
195 will be called rtc-ds1307.
197 config RTC_DRV_DS1374
198 tristate "Dallas/Maxim DS1374"
199 depends on RTC_CLASS && I2C
201 If you say yes here you get support for Dallas Semiconductor
202 DS1374 real-time clock chips. If an interrupt is associated
203 with the device, the alarm functionality is supported.
205 This driver can also be built as a module. If so, the module
206 will be called rtc-ds1374.
208 config RTC_DRV_DS1672
209 tristate "Dallas/Maxim DS1672"
211 If you say yes here you get support for the
212 Dallas/Maxim DS1672 timekeeping chip.
214 This driver can also be built as a module. If so, the module
215 will be called rtc-ds1672.
217 config RTC_DRV_DS3232
218 tristate "Dallas/Maxim DS3232"
219 depends on RTC_CLASS && I2C
221 If you say yes here you get support for Dallas Semiconductor
222 DS3232 real-time clock chips. If an interrupt is associated
223 with the device, the alarm functionality is supported.
225 This driver can also be built as a module. If so, the module
226 will be called rtc-ds3232.
228 config RTC_DRV_MAX6900
229 tristate "Maxim MAX6900"
231 If you say yes here you will get support for the
232 Maxim MAX6900 I2C RTC chip.
234 This driver can also be built as a module. If so, the module
235 will be called rtc-max6900.
237 config RTC_DRV_MAX8925
238 tristate "Maxim MAX8925"
239 depends on MFD_MAX8925
241 If you say yes here you will get support for the
242 RTC of Maxim MAX8925 PMIC.
244 This driver can also be built as a module. If so, the module
245 will be called rtc-max8925.
247 config RTC_DRV_MAX8998
248 tristate "Maxim MAX8998"
249 depends on MFD_MAX8998
251 If you say yes here you will get support for the
252 RTC of Maxim MAX8998 PMIC.
254 This driver can also be built as a module. If so, the module
255 will be called rtc-max8998.
257 config RTC_DRV_RS5C372
258 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
260 If you say yes here you get support for the
261 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
263 This driver can also be built as a module. If so, the module
264 will be called rtc-rs5c372.
266 config RTC_DRV_ISL1208
267 tristate "Intersil ISL1208"
269 If you say yes here you get support for the
270 Intersil ISL1208 RTC chip.
272 This driver can also be built as a module. If so, the module
273 will be called rtc-isl1208.
275 config RTC_DRV_ISL12022
276 tristate "Intersil ISL12022"
278 If you say yes here you get support for the
279 Intersil ISL12022 RTC chip.
281 This driver can also be built as a module. If so, the module
282 will be called rtc-isl12022.
285 tristate "Xicor/Intersil X1205"
287 If you say yes here you get support for the
288 Xicor/Intersil X1205 RTC chip.
290 This driver can also be built as a module. If so, the module
291 will be called rtc-x1205.
293 config RTC_DRV_PCF8563
294 tristate "Philips PCF8563/Epson RTC8564"
296 If you say yes here you get support for the
297 Philips PCF8563 RTC chip. The Epson RTC8564
300 This driver can also be built as a module. If so, the module
301 will be called rtc-pcf8563.
303 config RTC_DRV_PCF8583
304 tristate "Philips PCF8583"
306 If you say yes here you get support for the Philips PCF8583
307 RTC chip found on Acorn RiscPCs. This driver supports the
308 platform specific method of retrieving the current year from
309 the RTC's SRAM. It will work on other platforms with the same
310 chip, but the year will probably have to be tweaked.
312 This driver can also be built as a module. If so, the module
313 will be called rtc-pcf8583.
315 config RTC_DRV_M41T80
316 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
318 If you say Y here you will get support for the ST M41T60
319 and M41T80 RTC chips series. Currently, the following chips are
320 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
321 M41ST85, and M41ST87.
323 This driver can also be built as a module. If so, the module
324 will be called rtc-m41t80.
326 config RTC_DRV_M41T80_WDT
327 bool "ST M41T65/M41T80 series RTC watchdog timer"
328 depends on RTC_DRV_M41T80
330 If you say Y here you will get support for the
331 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
334 tristate "TI BQ32000"
336 If you say Y here you will get support for the TI
337 BQ32000 I2C RTC chip.
339 This driver can also be built as a module. If so, the module
340 will be called rtc-bq32k.
342 config RTC_DRV_DM355EVM
343 tristate "TI DaVinci DM355 EVM RTC"
344 depends on MFD_DM355EVM_MSP
346 Supports the RTC firmware in the MSP430 on the DM355 EVM.
348 config RTC_DRV_TWL92330
349 boolean "TI TWL92330/Menelaus"
352 If you say yes here you get support for the RTC on the
353 TWL92330 "Menelaus" power management chip, used with OMAP2
354 platforms. The support is integrated with the rest of
355 the Menelaus driver; it's not separate module.
357 config RTC_DRV_TWL4030
358 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
359 depends on RTC_CLASS && TWL4030_CORE
361 If you say yes here you get support for the RTC on the
362 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
364 This driver can also be built as a module. If so, the module
365 will be called rtc-twl.
367 config RTC_DRV_S35390A
368 tristate "Seiko Instruments S-35390A"
371 If you say yes here you will get support for the Seiko
372 Instruments S-35390A.
374 This driver can also be built as a module. If so the module
375 will be called rtc-s35390a.
377 config RTC_DRV_S35392A
378 tristate "Seiko Instruments S-35392A"
381 If you say yes here you will get support for the Seiko
382 Instruments S-35392A.
384 This driver can also be built as a module. If so the module
385 will be called rtc-s35392a.
387 config RTC_DRV_FM3130
388 tristate "Ramtron FM3130"
390 If you say Y here you will get support for the
391 Ramtron FM3130 RTC chips.
392 Ramtron FM3130 is a chip with two separate devices inside,
393 RTC clock and FRAM. This driver provides only RTC functionality.
395 This driver can also be built as a module. If so the module
396 will be called rtc-fm3130.
398 config RTC_DRV_RX8581
399 tristate "Epson RX-8581"
401 If you say yes here you will get support for the Epson RX-8581.
403 This driver can also be built as a module. If so the module
404 will be called rtc-rx8581.
406 config RTC_DRV_RX8025
407 tristate "Epson RX-8025SA/NB"
409 If you say yes here you get support for the Epson
410 RX-8025SA/NB RTC chips.
412 This driver can also be built as a module. If so, the module
413 will be called rtc-rx8025.
415 config RTC_DRV_EM3027
416 tristate "EM Microelectronic EM3027"
418 If you say yes here you get support for the EM
419 Microelectronic EM3027 RTC chips.
421 This driver can also be built as a module. If so, the module
422 will be called rtc-em3027.
424 config RTC_DRV_RV3029C2
425 tristate "Micro Crystal RTC"
427 If you say yes here you get support for the Micro Crystal
430 This driver can also be built as a module. If so, the module
431 will be called rtc-rv3029c2.
435 comment "SPI RTC drivers"
439 config RTC_DRV_M41T93
442 If you say yes here you will get support for the
443 ST M41T93 SPI RTC chip.
445 This driver can also be built as a module. If so, the module
446 will be called rtc-m41t93.
448 config RTC_DRV_M41T94
451 If you say yes here you will get support for the
452 ST M41T94 SPI RTC chip.
454 This driver can also be built as a module. If so, the module
455 will be called rtc-m41t94.
457 config RTC_DRV_DS1305
458 tristate "Dallas/Maxim DS1305/DS1306"
460 Select this driver to get support for the Dallas/Maxim DS1305
461 and DS1306 real time clock chips. These support a trickle
462 charger, alarms, and NVRAM in addition to the clock.
464 This driver can also be built as a module. If so, the module
465 will be called rtc-ds1305.
467 config RTC_DRV_DS1390
468 tristate "Dallas/Maxim DS1390/93/94"
470 If you say yes here you get support for the
471 Dallas/Maxim DS1390/93/94 chips.
473 This driver only supports the RTC feature, and not other chip
474 features such as alarms and trickle charging.
476 This driver can also be built as a module. If so, the module
477 will be called rtc-ds1390.
479 config RTC_DRV_MAX6902
480 tristate "Maxim MAX6902"
482 If you say yes here you will get support for the
483 Maxim MAX6902 SPI RTC chip.
485 This driver can also be built as a module. If so, the module
486 will be called rtc-max6902.
489 tristate "Epson RTC-9701JE"
491 If you say yes here you will get support for the
492 Epson RTC-9701JE SPI RTC chip.
494 This driver can also be built as a module. If so, the module
495 will be called rtc-r9701.
497 config RTC_DRV_RS5C348
498 tristate "Ricoh RS5C348A/B"
500 If you say yes here you get support for the
501 Ricoh RS5C348A and RS5C348B RTC chips.
503 This driver can also be built as a module. If so, the module
504 will be called rtc-rs5c348.
506 config RTC_DRV_DS3234
507 tristate "Maxim/Dallas DS3234"
509 If you say yes here you get support for the
510 Maxim/Dallas DS3234 SPI RTC chip.
512 This driver can also be built as a module. If so, the module
513 will be called rtc-ds3234.
515 config RTC_DRV_PCF2123
516 tristate "NXP PCF2123"
518 If you say yes here you get support for the NXP PCF2123
521 This driver can also be built as a module. If so, the module
522 will be called rtc-pcf2123.
526 comment "Platform RTC drivers"
528 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
529 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
530 # global rtc_lock ... it's not yet just another platform_device.
533 tristate "PC-style 'CMOS'"
534 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
537 Say "yes" here to get direct support for the real time clock
538 found in every PC or ACPI-based system, and some other boards.
539 Specifically the original MC146818, compatibles like those in
540 PC south bridges, the DS12887 or M48T86, some multifunction
541 or LPC bus chips, and so on.
543 Your system will need to define the platform device used by
544 this driver, otherwise it won't be accessible. This means
545 you can safely enable this driver if you don't know whether
546 or not your board has this kind of hardware.
548 This driver can also be built as a module. If so, the module
549 will be called rtc-cmos.
552 tristate "Virtual RTC for Moorestown platforms"
554 default y if X86_MRST
557 Say "yes" here to get direct support for the real time clock
558 found on Moorestown platforms. The VRTC is a emulated RTC that
559 derives its clock source from a real RTC in the PMIC. The MC146818
560 style programming interface is mostly conserved, but any
561 updates are done via IPC calls to the system controller FW.
563 config RTC_DRV_DS1216
564 tristate "Dallas DS1216"
567 If you say yes here you get support for the Dallas DS1216 RTC chips.
569 config RTC_DRV_DS1286
570 tristate "Dallas DS1286"
572 If you say yes here you get support for the Dallas DS1286 RTC chips.
574 config RTC_DRV_DS1302
575 tristate "Dallas DS1302"
576 depends on SH_SECUREEDGE5410
578 If you say yes here you get support for the Dallas DS1302 RTC chips.
580 config RTC_DRV_DS1511
581 tristate "Dallas DS1511"
584 If you say yes here you get support for the
585 Dallas DS1511 timekeeping/watchdog chip.
587 This driver can also be built as a module. If so, the module
588 will be called rtc-ds1511.
590 config RTC_DRV_DS1553
591 tristate "Maxim/Dallas DS1553"
593 If you say yes here you get support for the
594 Maxim/Dallas DS1553 timekeeping chip.
596 This driver can also be built as a module. If so, the module
597 will be called rtc-ds1553.
599 config RTC_DRV_DS1742
600 tristate "Maxim/Dallas DS1742/1743"
602 If you say yes here you get support for the
603 Maxim/Dallas DS1742/1743 timekeeping chip.
605 This driver can also be built as a module. If so, the module
606 will be called rtc-ds1742.
612 If you say yes here you will get support for the EFI
615 This driver can also be built as a module. If so, the module
616 will be called rtc-efi.
618 config RTC_DRV_STK17TA8
619 tristate "Simtek STK17TA8"
622 If you say yes here you get support for the
623 Simtek STK17TA8 timekeeping chip.
625 This driver can also be built as a module. If so, the module
626 will be called rtc-stk17ta8.
628 config RTC_DRV_M48T86
629 tristate "ST M48T86/Dallas DS12887"
631 If you say Y here you will get support for the
632 ST M48T86 and Dallas DS12887 RTC chips.
634 This driver can also be built as a module. If so, the module
635 will be called rtc-m48t86.
637 config RTC_DRV_M48T35
640 If you say Y here you will get support for the
643 This driver can also be built as a module, if so, the module
644 will be called "rtc-m48t35".
646 config RTC_DRV_M48T59
647 tristate "ST M48T59/M48T08/M48T02"
649 If you say Y here you will get support for the
650 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
652 These chips are usually found in Sun SPARC and UltraSPARC
655 This driver can also be built as a module, if so, the module
656 will be called "rtc-m48t59".
658 config RTC_DRV_MSM6242
659 tristate "Oki MSM6242"
661 If you say yes here you get support for the Oki MSM6242
662 timekeeping chip. It is used in some Amiga models (e.g. A2000).
664 This driver can also be built as a module. If so, the module
665 will be called rtc-msm6242.
668 tristate "Freescale IMX DryIce Real Time Clock"
672 Support for Freescale IMX DryIce RTC
674 This driver can also be built as a module, if so, the module
675 will be called "rtc-imxdi".
678 tristate "Freescale MXC Real Time Clock"
682 If you say yes here you get support for the Freescale MXC
685 This driver can also be built as a module, if so, the module
686 will be called "rtc-mxc".
688 config RTC_DRV_BQ4802
691 If you say Y here you will get support for the TI
694 This driver can also be built as a module. If so, the module
695 will be called rtc-bq4802.
697 config RTC_DRV_RP5C01
698 tristate "Ricoh RP5C01"
700 If you say yes here you get support for the Ricoh RP5C01
701 timekeeping chip. It is used in some Amiga models (e.g. A3000
704 This driver can also be built as a module. If so, the module
705 will be called rtc-rp5c01.
708 tristate "EM Microelectronic V3020"
710 If you say yes here you will get support for the
711 EM Microelectronic v3020 RTC chip.
713 This driver can also be built as a module. If so, the module
714 will be called rtc-v3020.
716 config RTC_DRV_WM831X
717 tristate "Wolfson Microelectronics WM831x RTC"
718 depends on MFD_WM831X
720 If you say yes here you will get support for the RTC subsystem
721 of the Wolfson Microelectronics WM831X series PMICs.
723 This driver can also be built as a module. If so, the module
724 will be called "rtc-wm831x".
726 config RTC_DRV_WM8350
727 tristate "Wolfson Microelectronics WM8350 RTC"
728 depends on MFD_WM8350
730 If you say yes here you will get support for the RTC subsystem
731 of the Wolfson Microelectronics WM8350.
733 This driver can also be built as a module. If so, the module
734 will be called "rtc-wm8350".
737 tristate "SPEAR ST RTC"
738 depends on PLAT_SPEAR
741 If you say Y here you will get support for the RTC found on
744 config RTC_DRV_PCF50633
745 depends on MFD_PCF50633
746 tristate "NXP PCF50633 RTC"
748 If you say yes here you get support for the RTC subsystem of the
749 NXP PCF50633 used in embedded systems.
751 config RTC_DRV_AB3100
752 tristate "ST-Ericsson AB3100 RTC"
753 depends on AB3100_CORE
754 default y if AB3100_CORE
756 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
757 support. This chip contains a battery- and capacitor-backed RTC.
759 config RTC_DRV_AB8500
760 tristate "ST-Ericsson AB8500 RTC"
761 depends on AB8500_CORE
763 Select this to enable the ST-Ericsson AB8500 power management IC RTC
764 support. This chip contains a battery- and capacitor-backed RTC.
766 config RTC_DRV_NUC900
767 tristate "NUC910/NUC920 RTC driver"
768 depends on RTC_CLASS && ARCH_W90X900
770 If you say yes here you get support for the RTC subsystem of the
771 NUC910/NUC920 used in embedded systems.
773 comment "on-CPU RTC drivers"
775 config RTC_DRV_DAVINCI
776 tristate "TI DaVinci RTC"
777 depends on ARCH_DAVINCI_DM365
779 If you say yes here you get support for the RTC on the
780 DaVinci platforms (DM365).
782 This driver can also be built as a module. If so, the module
783 will be called rtc-davinci.
787 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
789 Say "yes" here to support the real time clock on TI OMAP1 and
790 DA8xx/OMAP-L13x chips. This driver can also be built as a
791 module called rtc-omap.
796 This will include RTC support for Samsung SoCs. If
797 you want to include RTC support for any machine, kindly
798 select this in the respective mach-XXXX/Kconfig file.
801 tristate "Samsung S3C series SoC RTC"
802 depends on ARCH_S3C2410 || ARCH_S3C64XX || HAVE_S3C_RTC
804 RTC (Realtime Clock) driver for the clock inbuilt into the
805 Samsung S3C24XX series of SoCs. This can provide periodic
806 interrupt rates from 1Hz to 64Hz for user programs, and
809 The driver currently supports the common features on all the
810 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
813 This driver can also be build as a module. If so, the module
814 will be called rtc-s3c.
816 config RTC_DRV_EP93XX
817 tristate "Cirrus Logic EP93XX"
818 depends on ARCH_EP93XX
820 If you say yes here you get support for the
821 RTC embedded in the Cirrus Logic EP93XX processors.
823 This driver can also be built as a module. If so, the module
824 will be called rtc-ep93xx.
826 config RTC_DRV_SA1100
827 tristate "SA11x0/PXA2xx"
828 depends on ARCH_SA1100 || ARCH_PXA
830 If you say Y here you will get access to the real time clock
831 built into your SA11x0 or PXA2xx CPU.
833 To compile this driver as a module, choose M here: the
834 module will be called rtc-sa1100.
837 tristate "SuperH On-Chip RTC"
838 depends on RTC_CLASS && SUPERH && HAVE_CLK
840 Say Y here to enable support for the on-chip RTC found in
841 most SuperH processors.
843 To compile this driver as a module, choose M here: the
844 module will be called rtc-sh.
846 config RTC_DRV_VR41XX
847 tristate "NEC VR41XX"
848 depends on CPU_VR41XX
850 If you say Y here you will get access to the real time clock
851 built into your NEC VR41XX CPU.
853 To compile this driver as a module, choose M here: the
854 module will be called rtc-vr41xx.
857 tristate "ARM AMBA PL030 RTC"
860 If you say Y here you will get access to ARM AMBA
861 PrimeCell PL030 RTC found on certain ARM SOCs.
863 To compile this driver as a module, choose M here: the
864 module will be called rtc-pl030.
867 tristate "ARM AMBA PL031 RTC"
870 If you say Y here you will get access to ARM AMBA
871 PrimeCell PL031 RTC found on certain ARM SOCs.
873 To compile this driver as a module, choose M here: the
874 module will be called rtc-pl031.
876 config RTC_DRV_AT32AP700X
877 tristate "AT32AP700X series RTC"
878 depends on PLATFORM_AT32AP
880 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
881 AT32AP700x family processors.
883 config RTC_DRV_AT91RM9200
884 tristate "AT91RM9200 or some AT91SAM9 RTC"
885 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
887 Driver for the internal RTC (Realtime Clock) module found on
888 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
889 this is powered by the backup power supply.
891 config RTC_DRV_AT91SAM9
892 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
893 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
895 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
896 (Real Time Timer). These timers are powered by the backup power
897 supply (such as a small coin cell battery), but do not need to
900 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
901 dedicated RTC module and leave the RTT available for other uses.)
903 config RTC_DRV_AT91SAM9_RTT
907 prompt "RTT module Number" if ARCH_AT91SAM9263
908 depends on RTC_DRV_AT91SAM9
910 More than one RTT module is available. You can choose which
911 one will be used as an RTC. The default of zero is normally
912 OK to use, though some systems use that for non-RTC purposes.
914 config RTC_DRV_AT91SAM9_GPBR
916 range 0 3 if !ARCH_AT91SAM9263
917 range 0 15 if ARCH_AT91SAM9263
919 prompt "Backup Register Number"
920 depends on RTC_DRV_AT91SAM9
922 The RTC driver needs to use one of the General Purpose Backup
923 Registers (GPBRs) as well as the RTT. You can choose which one
924 will be used. The default of zero is normally OK to use, but
925 on some systems other software needs to use that register.
927 config RTC_DRV_AU1XXX
928 tristate "Au1xxx Counter0 RTC support"
929 depends on MIPS_ALCHEMY
931 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
932 counter) to be used as a RTC.
934 This driver can also be built as a module. If so, the module
935 will be called rtc-au1xxx.
938 tristate "Blackfin On-Chip RTC"
939 depends on BLACKFIN && !BF561
941 If you say yes here you will get support for the
942 Blackfin On-Chip Real Time Clock.
944 This driver can also be built as a module. If so, the module
945 will be called rtc-bfin.
947 config RTC_DRV_RS5C313
948 tristate "Ricoh RS5C313"
949 depends on SH_LANDISK
951 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
953 config RTC_DRV_GENERIC
954 tristate "Generic RTC support"
955 # Please consider writing a new RTC driver instead of using the generic
957 depends on PARISC || M68K || PPC || SUPERH32
959 Say Y or M here to enable RTC support on systems using the generic
960 RTC abstraction. If you do not know what you are doing, you should
964 tristate "PXA27x/PXA3xx"
967 If you say Y here you will get access to the real time clock
968 built into your PXA27x or PXA3xx CPU.
970 This RTC driver uses PXA RTC registers available since pxa27x
971 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
973 config RTC_DRV_VT8500
974 tristate "VIA/WonderMedia 85xx SoC RTC"
975 depends on ARCH_VT8500
977 If you say Y here you will get access to the real time clock
978 built into your VIA VT8500 SoC or its relatives.
982 bool "SUN4V Hypervisor RTC"
985 If you say Y here you will get support for the Hypervisor
986 based RTC on SUN4V systems.
988 config RTC_DRV_STARFIRE
992 If you say Y here you will get support for the RTC found on
995 config RTC_DRV_TX4939
996 tristate "TX4939 SoC"
997 depends on SOC_TX4939
999 Driver for the internal RTC (Realtime Clock) module found on
1003 tristate "Marvell SoC RTC"
1004 depends on ARCH_KIRKWOOD || ARCH_DOVE
1006 If you say yes here you will get support for the in-chip RTC
1007 that can be found in some of Marvell's SoC devices, such as
1008 the Kirkwood 88F6281 and 88F6192.
1010 This driver can also be built as a module. If so, the module
1011 will be called rtc-mv.
1017 If you say yes here you will get support for the RTC on PS3.
1019 This driver can also be built as a module. If so, the module
1020 will be called rtc-ps3.
1022 config RTC_DRV_COH901331
1023 tristate "ST-Ericsson COH 901 331 RTC"
1024 depends on ARCH_U300
1026 If you say Y here you will get access to ST-Ericsson
1027 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1030 This driver can also be built as a module. If so, the module
1031 will be called "rtc-coh901331".
1035 tristate "Freescale STMP3xxx RTC"
1036 depends on ARCH_STMP3XXX
1038 If you say yes here you will get support for the onboard
1041 This driver can also be built as a module. If so, the module
1042 will be called rtc-stmp3xxx.
1048 If you say Y here you will get support for the RTC found on
1049 the PCAP2 ASIC used on some Motorola phones.
1051 config RTC_DRV_MC13XXX
1052 depends on MFD_MC13XXX
1053 tristate "Freescale MC13xxx RTC"
1055 This enables support for the RTCs found on Freescale's PMICs
1056 MC13783 and MC13892.
1058 config RTC_DRV_MPC5121
1059 tristate "Freescale MPC5121 built-in RTC"
1060 depends on PPC_MPC512x && RTC_CLASS
1062 If you say yes here you will get support for the
1063 built-in RTC MPC5121.
1065 This driver can also be built as a module. If so, the module
1066 will be called rtc-mpc5121.
1068 config RTC_DRV_JZ4740
1069 tristate "Ingenic JZ4740 SoC"
1070 depends on RTC_CLASS
1071 depends on MACH_JZ4740
1073 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1076 This driver can also be buillt as a module. If so, the module
1077 will be called rtc-jz4740.
1079 config RTC_DRV_LPC32XX
1080 depends on ARCH_LPC32XX
1081 tristate "NXP LPC32XX RTC"
1083 This enables support for the NXP RTC in the LPC32XX
1085 This driver can also be buillt as a module. If so, the module
1086 will be called rtc-lpc32xx.
1088 config RTC_DRV_TEGRA
1089 tristate "NVIDIA Tegra Internal RTC driver"
1090 depends on RTC_CLASS && ARCH_TEGRA
1092 If you say yes here you get support for the
1093 Tegra 200 series internal RTC module.
1095 This drive can also be built as a module. If so, the module
1096 will be called rtc-tegra.
1099 tristate "Tilera hypervisor RTC support"
1102 Enable support for the Linux driver side of the Tilera
1103 hypervisor's real-time clock interface.
1106 tristate "PKUnity v3 RTC support"
1107 depends on ARCH_PUV3
1109 This enables support for the RTC in the PKUnity-v3 SoCs.
1111 This drive can also be built as a module. If so, the module
1112 will be called rtc-puv3.
1114 tristate "tps65910 rtc for rk"
1115 depends on MFD_TPS65910
1117 enable tps65910 rtc for system