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"
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.
110 tristate "Test driver/device"
112 If you say yes here you get support for the
113 RTC test driver. It's a software RTC which can be
114 used to test the RTC subsystem APIs. It gets
115 the time from the system clock.
116 You want this driver only if you are doing development
117 on the RTC subsystem. Please read the source code
120 This driver can also be built as a module. If so, the module
121 will be called rtc-test.
123 comment "I2C RTC drivers"
128 config RTC_DRV_88PM860X
129 tristate "Marvell 88PM860x"
130 depends on RTC_CLASS && I2C && MFD_88PM860X
132 If you say yes here you get support for RTC function in Marvell
135 This driver can also be built as a module. If so, the module
136 will be called rtc-88pm860x.
138 config RTC_DRV_DS1307
139 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
141 If you say yes here you get support for various compatible RTC
142 chips (often with battery backup) connected with I2C. This driver
143 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
144 EPSON RX-8025 and probably other chips. In some cases the RTC
145 must already have been initialized (by manufacturing or a
148 The first seven registers on these chips hold an RTC, and other
149 registers may add features such as NVRAM, a trickle charger for
150 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
151 sysfs, but other chip features may not be available.
153 This driver can also be built as a module. If so, the module
154 will be called rtc-ds1307.
156 config RTC_DRV_DS1374
157 tristate "Dallas/Maxim DS1374"
158 depends on RTC_CLASS && I2C
160 If you say yes here you get support for Dallas Semiconductor
161 DS1374 real-time clock chips. If an interrupt is associated
162 with the device, the alarm functionality is supported.
164 This driver can also be built as a module. If so, the module
165 will be called rtc-ds1374.
167 config RTC_DRV_DS1672
168 tristate "Dallas/Maxim DS1672"
170 If you say yes here you get support for the
171 Dallas/Maxim DS1672 timekeeping chip.
173 This driver can also be built as a module. If so, the module
174 will be called rtc-ds1672.
176 config RTC_DRV_DS3232
177 tristate "Dallas/Maxim DS3232"
178 depends on RTC_CLASS && I2C
180 If you say yes here you get support for Dallas Semiconductor
181 DS3232 real-time clock chips. If an interrupt is associated
182 with the device, the alarm functionality is supported.
184 This driver can also be built as a module. If so, the module
185 will be called rtc-ds3232.
187 config RTC_DRV_MAX6900
188 tristate "Maxim MAX6900"
190 If you say yes here you will get support for the
191 Maxim MAX6900 I2C RTC chip.
193 This driver can also be built as a module. If so, the module
194 will be called rtc-max6900.
196 config RTC_DRV_MAX8925
197 tristate "Maxim MAX8925"
198 depends on MFD_MAX8925
200 If you say yes here you will get support for the
201 RTC of Maxim MAX8925 PMIC.
203 This driver can also be built as a module. If so, the module
204 will be called rtc-max8925.
206 config RTC_DRV_MAX8998
207 tristate "Maxim MAX8998"
208 depends on MFD_MAX8998
210 If you say yes here you will get support for the
211 RTC of Maxim MAX8998 PMIC.
213 This driver can also be built as a module. If so, the module
214 will be called rtc-max8998.
216 config RTC_DRV_MAX77686
217 tristate "Maxim MAX77686"
218 depends on MFD_MAX77686
220 If you say yes here you will get support for the
221 RTC of Maxim MAX77686 PMIC.
223 This driver can also be built as a module. If so, the module
224 will be called rtc-max77686.
226 config RTC_DRV_RS5C372
227 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
229 If you say yes here you get support for the
230 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
232 This driver can also be built as a module. If so, the module
233 will be called rtc-rs5c372.
235 config RTC_DRV_ISL1208
236 tristate "Intersil ISL1208"
238 If you say yes here you get support for the
239 Intersil ISL1208 RTC chip.
241 This driver can also be built as a module. If so, the module
242 will be called rtc-isl1208.
244 config RTC_DRV_ISL12022
245 tristate "Intersil ISL12022"
247 If you say yes here you get support for the
248 Intersil ISL12022 RTC chip.
250 This driver can also be built as a module. If so, the module
251 will be called rtc-isl12022.
254 tristate "Xicor/Intersil X1205"
256 If you say yes here you get support for the
257 Xicor/Intersil X1205 RTC chip.
259 This driver can also be built as a module. If so, the module
260 will be called rtc-x1205.
262 config RTC_DRV_PCF8563
263 tristate "Philips PCF8563/Epson RTC8564"
265 If you say yes here you get support for the
266 Philips PCF8563 RTC chip. The Epson RTC8564
269 This driver can also be built as a module. If so, the module
270 will be called rtc-pcf8563.
272 config RTC_DRV_PCF8583
273 tristate "Philips PCF8583"
275 If you say yes here you get support for the Philips PCF8583
276 RTC chip found on Acorn RiscPCs. This driver supports the
277 platform specific method of retrieving the current year from
278 the RTC's SRAM. It will work on other platforms with the same
279 chip, but the year will probably have to be tweaked.
281 This driver can also be built as a module. If so, the module
282 will be called rtc-pcf8583.
284 config RTC_DRV_M41T80
285 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
287 If you say Y here you will get support for the ST M41T60
288 and M41T80 RTC chips series. Currently, the following chips are
289 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
290 M41ST85, and M41ST87.
292 This driver can also be built as a module. If so, the module
293 will be called rtc-m41t80.
295 config RTC_DRV_M41T80_WDT
296 bool "ST M41T65/M41T80 series RTC watchdog timer"
297 depends on RTC_DRV_M41T80
299 If you say Y here you will get support for the
300 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
303 tristate "TI BQ32000"
305 If you say Y here you will get support for the TI
306 BQ32000 I2C RTC chip.
308 This driver can also be built as a module. If so, the module
309 will be called rtc-bq32k.
311 config RTC_DRV_DM355EVM
312 tristate "TI DaVinci DM355 EVM RTC"
313 depends on MFD_DM355EVM_MSP
315 Supports the RTC firmware in the MSP430 on the DM355 EVM.
317 config RTC_DRV_TWL92330
318 boolean "TI TWL92330/Menelaus"
321 If you say yes here you get support for the RTC on the
322 TWL92330 "Menelaus" power management chip, used with OMAP2
323 platforms. The support is integrated with the rest of
324 the Menelaus driver; it's not separate module.
326 config RTC_DRV_TWL4030
327 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
328 depends on RTC_CLASS && TWL4030_CORE
330 If you say yes here you get support for the RTC on the
331 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
333 This driver can also be built as a module. If so, the module
334 will be called rtc-twl.
336 config RTC_DRV_S35390A
337 tristate "Seiko Instruments S-35390A"
340 If you say yes here you will get support for the Seiko
341 Instruments S-35390A.
343 This driver can also be built as a module. If so the module
344 will be called rtc-s35390a.
346 config RTC_DRV_FM3130
347 tristate "Ramtron FM3130"
349 If you say Y here you will get support for the
350 Ramtron FM3130 RTC chips.
351 Ramtron FM3130 is a chip with two separate devices inside,
352 RTC clock and FRAM. This driver provides only RTC functionality.
354 This driver can also be built as a module. If so the module
355 will be called rtc-fm3130.
357 config RTC_DRV_RX8581
358 tristate "Epson RX-8581"
360 If you say yes here you will get support for the Epson RX-8581.
362 This driver can also be built as a module. If so the module
363 will be called rtc-rx8581.
365 config RTC_DRV_RX8025
366 tristate "Epson RX-8025SA/NB"
368 If you say yes here you get support for the Epson
369 RX-8025SA/NB RTC chips.
371 This driver can also be built as a module. If so, the module
372 will be called rtc-rx8025.
374 config RTC_DRV_EM3027
375 tristate "EM Microelectronic EM3027"
377 If you say yes here you get support for the EM
378 Microelectronic EM3027 RTC chips.
380 This driver can also be built as a module. If so, the module
381 will be called rtc-em3027.
383 config RTC_DRV_RV3029C2
384 tristate "Micro Crystal RTC"
386 If you say yes here you get support for the Micro Crystal
389 This driver can also be built as a module. If so, the module
390 will be called rtc-rv3029c2.
394 comment "SPI RTC drivers"
398 config RTC_DRV_M41T93
401 If you say yes here you will get support for the
402 ST M41T93 SPI RTC chip.
404 This driver can also be built as a module. If so, the module
405 will be called rtc-m41t93.
407 config RTC_DRV_M41T94
410 If you say yes here you will get support for the
411 ST M41T94 SPI RTC chip.
413 This driver can also be built as a module. If so, the module
414 will be called rtc-m41t94.
416 config RTC_DRV_DS1305
417 tristate "Dallas/Maxim DS1305/DS1306"
419 Select this driver to get support for the Dallas/Maxim DS1305
420 and DS1306 real time clock chips. These support a trickle
421 charger, alarms, and NVRAM in addition to the clock.
423 This driver can also be built as a module. If so, the module
424 will be called rtc-ds1305.
426 config RTC_DRV_DS1390
427 tristate "Dallas/Maxim DS1390/93/94"
429 If you say yes here you get support for the
430 Dallas/Maxim DS1390/93/94 chips.
432 This driver only supports the RTC feature, and not other chip
433 features such as alarms and trickle charging.
435 This driver can also be built as a module. If so, the module
436 will be called rtc-ds1390.
438 config RTC_DRV_MAX6902
439 tristate "Maxim MAX6902"
441 If you say yes here you will get support for the
442 Maxim MAX6902 SPI RTC chip.
444 This driver can also be built as a module. If so, the module
445 will be called rtc-max6902.
448 tristate "Epson RTC-9701JE"
450 If you say yes here you will get support for the
451 Epson RTC-9701JE SPI RTC chip.
453 This driver can also be built as a module. If so, the module
454 will be called rtc-r9701.
456 config RTC_DRV_RS5C348
457 tristate "Ricoh RS5C348A/B"
459 If you say yes here you get support for the
460 Ricoh RS5C348A and RS5C348B RTC chips.
462 This driver can also be built as a module. If so, the module
463 will be called rtc-rs5c348.
465 config RTC_DRV_DS3234
466 tristate "Maxim/Dallas DS3234"
468 If you say yes here you get support for the
469 Maxim/Dallas DS3234 SPI RTC chip.
471 This driver can also be built as a module. If so, the module
472 will be called rtc-ds3234.
474 config RTC_DRV_PCF2123
475 tristate "NXP PCF2123"
477 If you say yes here you get support for the NXP PCF2123
480 This driver can also be built as a module. If so, the module
481 will be called rtc-pcf2123.
485 comment "Platform RTC drivers"
487 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
488 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
489 # global rtc_lock ... it's not yet just another platform_device.
492 tristate "PC-style 'CMOS'"
493 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
496 Say "yes" here to get direct support for the real time clock
497 found in every PC or ACPI-based system, and some other boards.
498 Specifically the original MC146818, compatibles like those in
499 PC south bridges, the DS12887 or M48T86, some multifunction
500 or LPC bus chips, and so on.
502 Your system will need to define the platform device used by
503 this driver, otherwise it won't be accessible. This means
504 you can safely enable this driver if you don't know whether
505 or not your board has this kind of hardware.
507 This driver can also be built as a module. If so, the module
508 will be called rtc-cmos.
511 tristate "Virtual RTC for Intel MID platforms"
512 depends on X86_INTEL_MID
513 default y if X86_INTEL_MID
516 Say "yes" here to get direct support for the real time clock
517 found on Moorestown platforms. The VRTC is a emulated RTC that
518 derives its clock source from a real RTC in the PMIC. The MC146818
519 style programming interface is mostly conserved, but any
520 updates are done via IPC calls to the system controller FW.
522 config RTC_DRV_DS1216
523 tristate "Dallas DS1216"
526 If you say yes here you get support for the Dallas DS1216 RTC chips.
528 config RTC_DRV_DS1286
529 tristate "Dallas DS1286"
531 If you say yes here you get support for the Dallas DS1286 RTC chips.
533 config RTC_DRV_DS1302
534 tristate "Dallas DS1302"
535 depends on SH_SECUREEDGE5410
537 If you say yes here you get support for the Dallas DS1302 RTC chips.
539 config RTC_DRV_DS1511
540 tristate "Dallas DS1511"
543 If you say yes here you get support for the
544 Dallas DS1511 timekeeping/watchdog chip.
546 This driver can also be built as a module. If so, the module
547 will be called rtc-ds1511.
549 config RTC_DRV_DS1553
550 tristate "Maxim/Dallas DS1553"
552 If you say yes here you get support for the
553 Maxim/Dallas DS1553 timekeeping chip.
555 This driver can also be built as a module. If so, the module
556 will be called rtc-ds1553.
558 config RTC_DRV_DS1742
559 tristate "Maxim/Dallas DS1742/1743"
561 If you say yes here you get support for the
562 Maxim/Dallas DS1742/1743 timekeeping chip.
564 This driver can also be built as a module. If so, the module
565 will be called rtc-ds1742.
567 config RTC_DRV_DA9052
568 tristate "Dialog DA9052/DA9053 RTC"
569 depends on PMIC_DA9052
571 Say y here to support the RTC driver for Dialog Semiconductor
572 DA9052-BC and DA9053-AA/Bx PMICs.
578 If you say yes here you will get support for the EFI
581 This driver can also be built as a module. If so, the module
582 will be called rtc-efi.
584 config RTC_DRV_STK17TA8
585 tristate "Simtek STK17TA8"
588 If you say yes here you get support for the
589 Simtek STK17TA8 timekeeping chip.
591 This driver can also be built as a module. If so, the module
592 will be called rtc-stk17ta8.
594 config RTC_DRV_M48T86
595 tristate "ST M48T86/Dallas DS12887"
597 If you say Y here you will get support for the
598 ST M48T86 and Dallas DS12887 RTC chips.
600 This driver can also be built as a module. If so, the module
601 will be called rtc-m48t86.
603 config RTC_DRV_M48T35
606 If you say Y here you will get support for the
609 This driver can also be built as a module, if so, the module
610 will be called "rtc-m48t35".
612 config RTC_DRV_M48T59
613 tristate "ST M48T59/M48T08/M48T02"
615 If you say Y here you will get support for the
616 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
618 These chips are usually found in Sun SPARC and UltraSPARC
621 This driver can also be built as a module, if so, the module
622 will be called "rtc-m48t59".
624 config RTC_DRV_MSM6242
625 tristate "Oki MSM6242"
627 If you say yes here you get support for the Oki MSM6242
628 timekeeping chip. It is used in some Amiga models (e.g. A2000).
630 This driver can also be built as a module. If so, the module
631 will be called rtc-msm6242.
634 tristate "Freescale IMX DryIce Real Time Clock"
638 Support for Freescale IMX DryIce RTC
640 This driver can also be built as a module, if so, the module
641 will be called "rtc-imxdi".
644 tristate "Freescale MXC Real Time Clock"
648 If you say yes here you get support for the Freescale MXC
651 This driver can also be built as a module, if so, the module
652 will be called "rtc-mxc".
654 config RTC_DRV_BQ4802
657 If you say Y here you will get support for the TI
660 This driver can also be built as a module. If so, the module
661 will be called rtc-bq4802.
663 config RTC_DRV_RP5C01
664 tristate "Ricoh RP5C01"
666 If you say yes here you get support for the Ricoh RP5C01
667 timekeeping chip. It is used in some Amiga models (e.g. A3000
670 This driver can also be built as a module. If so, the module
671 will be called rtc-rp5c01.
674 tristate "EM Microelectronic V3020"
676 If you say yes here you will get support for the
677 EM Microelectronic v3020 RTC chip.
679 This driver can also be built as a module. If so, the module
680 will be called rtc-v3020.
682 config RTC_DRV_WM831X
683 tristate "Wolfson Microelectronics WM831x RTC"
684 depends on MFD_WM831X
686 If you say yes here you will get support for the RTC subsystem
687 of the Wolfson Microelectronics WM831X series PMICs.
689 This driver can also be built as a module. If so, the module
690 will be called "rtc-wm831x".
692 config RTC_DRV_WM8350
693 tristate "Wolfson Microelectronics WM8350 RTC"
694 depends on MFD_WM8350
696 If you say yes here you will get support for the RTC subsystem
697 of the Wolfson Microelectronics WM8350.
699 This driver can also be built as a module. If so, the module
700 will be called "rtc-wm8350".
703 tristate "SPEAR ST RTC"
704 depends on PLAT_SPEAR
707 If you say Y here you will get support for the RTC found on
710 config RTC_DRV_PCF50633
711 depends on MFD_PCF50633
712 tristate "NXP PCF50633 RTC"
714 If you say yes here you get support for the RTC subsystem of the
715 NXP PCF50633 used in embedded systems.
717 config RTC_DRV_AB3100
718 tristate "ST-Ericsson AB3100 RTC"
719 depends on AB3100_CORE
720 default y if AB3100_CORE
722 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
723 support. This chip contains a battery- and capacitor-backed RTC.
725 config RTC_DRV_AB8500
726 tristate "ST-Ericsson AB8500 RTC"
727 depends on AB8500_CORE
729 Select this to enable the ST-Ericsson AB8500 power management IC RTC
730 support. This chip contains a battery- and capacitor-backed RTC.
732 config RTC_DRV_NUC900
733 tristate "NUC910/NUC920 RTC driver"
734 depends on RTC_CLASS && ARCH_W90X900
736 If you say yes here you get support for the RTC subsystem of the
737 NUC910/NUC920 used in embedded systems.
739 comment "on-CPU RTC drivers"
741 config RTC_DRV_DAVINCI
742 tristate "TI DaVinci RTC"
743 depends on ARCH_DAVINCI_DM365
745 If you say yes here you get support for the RTC on the
746 DaVinci platforms (DM365).
748 This driver can also be built as a module. If so, the module
749 will be called rtc-davinci.
753 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
755 Say "yes" here to support the real time clock on TI OMAP1 and
756 DA8xx/OMAP-L13x chips. This driver can also be built as a
757 module called rtc-omap.
762 This will include RTC support for Samsung SoCs. If
763 you want to include RTC support for any machine, kindly
764 select this in the respective mach-XXXX/Kconfig file.
767 tristate "Samsung S3C series SoC RTC"
768 depends on ARCH_S3C64XX || HAVE_S3C_RTC
770 RTC (Realtime Clock) driver for the clock inbuilt into the
771 Samsung S3C24XX series of SoCs. This can provide periodic
772 interrupt rates from 1Hz to 64Hz for user programs, and
775 The driver currently supports the common features on all the
776 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
779 This driver can also be build as a module. If so, the module
780 will be called rtc-s3c.
782 config RTC_DRV_EP93XX
783 tristate "Cirrus Logic EP93XX"
784 depends on ARCH_EP93XX
786 If you say yes here you get support for the
787 RTC embedded in the Cirrus Logic EP93XX processors.
789 This driver can also be built as a module. If so, the module
790 will be called rtc-ep93xx.
792 config RTC_DRV_SA1100
793 tristate "SA11x0/PXA2xx/PXA910"
794 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
796 If you say Y here you will get access to the real time clock
797 built into your SA11x0 or PXA2xx CPU.
799 To compile this driver as a module, choose M here: the
800 module will be called rtc-sa1100.
803 tristate "SuperH On-Chip RTC"
804 depends on RTC_CLASS && SUPERH && HAVE_CLK
806 Say Y here to enable support for the on-chip RTC found in
807 most SuperH processors.
809 To compile this driver as a module, choose M here: the
810 module will be called rtc-sh.
812 config RTC_DRV_VR41XX
813 tristate "NEC VR41XX"
814 depends on CPU_VR41XX
816 If you say Y here you will get access to the real time clock
817 built into your NEC VR41XX CPU.
819 To compile this driver as a module, choose M here: the
820 module will be called rtc-vr41xx.
823 tristate "ARM AMBA PL030 RTC"
826 If you say Y here you will get access to ARM AMBA
827 PrimeCell PL030 RTC found on certain ARM SOCs.
829 To compile this driver as a module, choose M here: the
830 module will be called rtc-pl030.
833 tristate "ARM AMBA PL031 RTC"
836 If you say Y here you will get access to ARM AMBA
837 PrimeCell PL031 RTC found on certain ARM SOCs.
839 To compile this driver as a module, choose M here: the
840 module will be called rtc-pl031.
842 config RTC_DRV_AT32AP700X
843 tristate "AT32AP700X series RTC"
844 depends on PLATFORM_AT32AP
846 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
847 AT32AP700x family processors.
849 config RTC_DRV_AT91RM9200
850 tristate "AT91RM9200 or some AT91SAM9 RTC"
851 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
853 Driver for the internal RTC (Realtime Clock) module found on
854 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
855 this is powered by the backup power supply.
857 config RTC_DRV_AT91SAM9
858 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
859 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
861 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
862 (Real Time Timer). These timers are powered by the backup power
863 supply (such as a small coin cell battery), but do not need to
866 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
867 dedicated RTC module and leave the RTT available for other uses.)
869 config RTC_DRV_AT91SAM9_RTT
873 prompt "RTT module Number" if ARCH_AT91SAM9263
874 depends on RTC_DRV_AT91SAM9
876 More than one RTT module is available. You can choose which
877 one will be used as an RTC. The default of zero is normally
878 OK to use, though some systems use that for non-RTC purposes.
880 config RTC_DRV_AT91SAM9_GPBR
882 range 0 3 if !ARCH_AT91SAM9263
883 range 0 15 if ARCH_AT91SAM9263
885 prompt "Backup Register Number"
886 depends on RTC_DRV_AT91SAM9
888 The RTC driver needs to use one of the General Purpose Backup
889 Registers (GPBRs) as well as the RTT. You can choose which one
890 will be used. The default of zero is normally OK to use, but
891 on some systems other software needs to use that register.
893 config RTC_DRV_AU1XXX
894 tristate "Au1xxx Counter0 RTC support"
895 depends on MIPS_ALCHEMY
897 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
898 counter) to be used as a RTC.
900 This driver can also be built as a module. If so, the module
901 will be called rtc-au1xxx.
904 tristate "Blackfin On-Chip RTC"
905 depends on BLACKFIN && !BF561
907 If you say yes here you will get support for the
908 Blackfin On-Chip Real Time Clock.
910 This driver can also be built as a module. If so, the module
911 will be called rtc-bfin.
913 config RTC_DRV_RS5C313
914 tristate "Ricoh RS5C313"
915 depends on SH_LANDISK
917 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
919 config RTC_DRV_GENERIC
920 tristate "Generic RTC support"
921 # Please consider writing a new RTC driver instead of using the generic
923 depends on PARISC || M68K || PPC || SUPERH32
925 Say Y or M here to enable RTC support on systems using the generic
926 RTC abstraction. If you do not know what you are doing, you should
930 tristate "PXA27x/PXA3xx"
933 If you say Y here you will get access to the real time clock
934 built into your PXA27x or PXA3xx CPU.
936 This RTC driver uses PXA RTC registers available since pxa27x
937 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
939 config RTC_DRV_VT8500
940 tristate "VIA/WonderMedia 85xx SoC RTC"
941 depends on ARCH_VT8500
943 If you say Y here you will get access to the real time clock
944 built into your VIA VT8500 SoC or its relatives.
948 bool "SUN4V Hypervisor RTC"
951 If you say Y here you will get support for the Hypervisor
952 based RTC on SUN4V systems.
954 config RTC_DRV_STARFIRE
958 If you say Y here you will get support for the RTC found on
961 config RTC_DRV_TX4939
962 tristate "TX4939 SoC"
963 depends on SOC_TX4939
965 Driver for the internal RTC (Realtime Clock) module found on
969 tristate "Marvell SoC RTC"
970 depends on ARCH_KIRKWOOD || ARCH_DOVE
972 If you say yes here you will get support for the in-chip RTC
973 that can be found in some of Marvell's SoC devices, such as
974 the Kirkwood 88F6281 and 88F6192.
976 This driver can also be built as a module. If so, the module
977 will be called rtc-mv.
983 If you say yes here you will get support for the RTC on PS3.
985 This driver can also be built as a module. If so, the module
986 will be called rtc-ps3.
988 config RTC_DRV_COH901331
989 tristate "ST-Ericsson COH 901 331 RTC"
992 If you say Y here you will get access to ST-Ericsson
993 COH 901 331 RTC clock found in some ST-Ericsson Mobile
996 This driver can also be built as a module. If so, the module
997 will be called "rtc-coh901331".
1001 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1004 If you say yes here you will get support for the onboard
1005 STMP3xxx/i.MX23/i.MX28 RTC.
1007 This driver can also be built as a module. If so, the module
1008 will be called rtc-stmp3xxx.
1014 If you say Y here you will get support for the RTC found on
1015 the PCAP2 ASIC used on some Motorola phones.
1017 config RTC_DRV_MC13XXX
1018 depends on MFD_MC13XXX
1019 tristate "Freescale MC13xxx RTC"
1021 This enables support for the RTCs found on Freescale's PMICs
1022 MC13783 and MC13892.
1024 config RTC_DRV_MPC5121
1025 tristate "Freescale MPC5121 built-in RTC"
1026 depends on PPC_MPC512x || PPC_MPC52xx
1028 If you say yes here you will get support for the
1029 built-in RTC on MPC5121 or on MPC5200.
1031 This driver can also be built as a module. If so, the module
1032 will be called rtc-mpc5121.
1034 config RTC_DRV_JZ4740
1035 tristate "Ingenic JZ4740 SoC"
1036 depends on RTC_CLASS
1037 depends on MACH_JZ4740
1039 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1042 This driver can also be buillt as a module. If so, the module
1043 will be called rtc-jz4740.
1045 config RTC_DRV_LPC32XX
1046 depends on ARCH_LPC32XX
1047 tristate "NXP LPC32XX RTC"
1049 This enables support for the NXP RTC in the LPC32XX
1051 This driver can also be buillt as a module. If so, the module
1052 will be called rtc-lpc32xx.
1054 config RTC_DRV_PM8XXX
1055 tristate "Qualcomm PMIC8XXX RTC"
1056 depends on MFD_PM8XXX
1058 If you say yes here you get support for the
1059 Qualcomm PMIC8XXX RTC.
1061 To compile this driver as a module, choose M here: the
1062 module will be called rtc-pm8xxx.
1064 config RTC_DRV_TEGRA
1065 tristate "NVIDIA Tegra Internal RTC driver"
1066 depends on RTC_CLASS && ARCH_TEGRA
1068 If you say yes here you get support for the
1069 Tegra 200 series internal RTC module.
1071 This drive can also be built as a module. If so, the module
1072 will be called rtc-tegra.
1075 tristate "Tilera hypervisor RTC support"
1078 Enable support for the Linux driver side of the Tilera
1079 hypervisor's real-time clock interface.
1082 tristate "PKUnity v3 RTC support"
1083 depends on ARCH_PUV3
1085 This enables support for the RTC in the PKUnity-v3 SoCs.
1087 This drive can also be built as a module. If so, the module
1088 will be called rtc-puv3.
1090 config RTC_DRV_LOONGSON1
1091 tristate "loongson1 RTC support"
1092 depends on MACH_LOONGSON1
1094 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1095 counter) to be used as a RTC.
1097 This driver can also be built as a module. If so, the module
1098 will be called rtc-ls1x.