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_88PM80X
139 tristate "Marvell 88PM80x"
140 depends on RTC_CLASS && I2C && MFD_88PM800
142 If you say yes here you get support for RTC function in Marvell
145 This driver can also be built as a module. If so, the module
146 will be called rtc-88pm80x.
148 config RTC_DRV_DS1307
149 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
151 If you say yes here you get support for various compatible RTC
152 chips (often with battery backup) connected with I2C. This driver
153 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
154 EPSON RX-8025 and probably other chips. In some cases the RTC
155 must already have been initialized (by manufacturing or a
158 The first seven registers on these chips hold an RTC, and other
159 registers may add features such as NVRAM, a trickle charger for
160 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
161 sysfs, but other chip features may not be available.
163 This driver can also be built as a module. If so, the module
164 will be called rtc-ds1307.
166 config RTC_DRV_DS1374
167 tristate "Dallas/Maxim DS1374"
168 depends on RTC_CLASS && I2C
170 If you say yes here you get support for Dallas Semiconductor
171 DS1374 real-time clock chips. If an interrupt is associated
172 with the device, the alarm functionality is supported.
174 This driver can also be built as a module. If so, the module
175 will be called rtc-ds1374.
177 config RTC_DRV_DS1672
178 tristate "Dallas/Maxim DS1672"
180 If you say yes here you get support for the
181 Dallas/Maxim DS1672 timekeeping chip.
183 This driver can also be built as a module. If so, the module
184 will be called rtc-ds1672.
186 config RTC_DRV_DS3232
187 tristate "Dallas/Maxim DS3232"
188 depends on RTC_CLASS && I2C
190 If you say yes here you get support for Dallas Semiconductor
191 DS3232 real-time clock chips. If an interrupt is associated
192 with the device, the alarm functionality is supported.
194 This driver can also be built as a module. If so, the module
195 will be called rtc-ds3232.
197 config RTC_DRV_MAX6900
198 tristate "Maxim MAX6900"
200 If you say yes here you will get support for the
201 Maxim MAX6900 I2C RTC chip.
203 This driver can also be built as a module. If so, the module
204 will be called rtc-max6900.
206 config RTC_DRV_MAX8925
207 tristate "Maxim MAX8925"
208 depends on MFD_MAX8925
210 If you say yes here you will get support for the
211 RTC of Maxim MAX8925 PMIC.
213 This driver can also be built as a module. If so, the module
214 will be called rtc-max8925.
216 config RTC_DRV_MAX8998
217 tristate "Maxim MAX8998"
218 depends on MFD_MAX8998
220 If you say yes here you will get support for the
221 RTC of Maxim MAX8998 PMIC.
223 This driver can also be built as a module. If so, the module
224 will be called rtc-max8998.
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.
633 config RTC_DRV_BQ4802
636 If you say Y here you will get support for the TI
639 This driver can also be built as a module. If so, the module
640 will be called rtc-bq4802.
642 config RTC_DRV_RP5C01
643 tristate "Ricoh RP5C01"
645 If you say yes here you get support for the Ricoh RP5C01
646 timekeeping chip. It is used in some Amiga models (e.g. A3000
649 This driver can also be built as a module. If so, the module
650 will be called rtc-rp5c01.
653 tristate "EM Microelectronic V3020"
655 If you say yes here you will get support for the
656 EM Microelectronic v3020 RTC chip.
658 This driver can also be built as a module. If so, the module
659 will be called rtc-v3020.
661 config RTC_DRV_WM831X
662 tristate "Wolfson Microelectronics WM831x RTC"
663 depends on MFD_WM831X
665 If you say yes here you will get support for the RTC subsystem
666 of the Wolfson Microelectronics WM831X series PMICs.
668 This driver can also be built as a module. If so, the module
669 will be called "rtc-wm831x".
671 config RTC_DRV_WM8350
672 tristate "Wolfson Microelectronics WM8350 RTC"
673 depends on MFD_WM8350
675 If you say yes here you will get support for the RTC subsystem
676 of the Wolfson Microelectronics WM8350.
678 This driver can also be built as a module. If so, the module
679 will be called "rtc-wm8350".
682 tristate "SPEAR ST RTC"
683 depends on PLAT_SPEAR
686 If you say Y here you will get support for the RTC found on
689 config RTC_DRV_PCF50633
690 depends on MFD_PCF50633
691 tristate "NXP PCF50633 RTC"
693 If you say yes here you get support for the RTC subsystem of the
694 NXP PCF50633 used in embedded systems.
696 config RTC_DRV_AB3100
697 tristate "ST-Ericsson AB3100 RTC"
698 depends on AB3100_CORE
699 default y if AB3100_CORE
701 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
702 support. This chip contains a battery- and capacitor-backed RTC.
704 config RTC_DRV_AB8500
705 tristate "ST-Ericsson AB8500 RTC"
706 depends on AB8500_CORE
708 Select this to enable the ST-Ericsson AB8500 power management IC RTC
709 support. This chip contains a battery- and capacitor-backed RTC.
711 config RTC_DRV_NUC900
712 tristate "NUC910/NUC920 RTC driver"
713 depends on RTC_CLASS && ARCH_W90X900
715 If you say yes here you get support for the RTC subsystem of the
716 NUC910/NUC920 used in embedded systems.
718 comment "on-CPU RTC drivers"
720 config RTC_DRV_DAVINCI
721 tristate "TI DaVinci RTC"
722 depends on ARCH_DAVINCI_DM365
724 If you say yes here you get support for the RTC on the
725 DaVinci platforms (DM365).
727 This driver can also be built as a module. If so, the module
728 will be called rtc-davinci.
731 tristate "Freescale IMX DryIce Real Time Clock"
735 Support for Freescale IMX DryIce RTC
737 This driver can also be built as a module, if so, the module
738 will be called "rtc-imxdi".
742 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
744 Say "yes" here to support the real time clock on TI OMAP1 and
745 DA8xx/OMAP-L13x chips. This driver can also be built as a
746 module called rtc-omap.
751 This will include RTC support for Samsung SoCs. If
752 you want to include RTC support for any machine, kindly
753 select this in the respective mach-XXXX/Kconfig file.
756 tristate "Samsung S3C series SoC RTC"
757 depends on ARCH_S3C64XX || HAVE_S3C_RTC
759 RTC (Realtime Clock) driver for the clock inbuilt into the
760 Samsung S3C24XX series of SoCs. This can provide periodic
761 interrupt rates from 1Hz to 64Hz for user programs, and
764 The driver currently supports the common features on all the
765 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
768 This driver can also be build as a module. If so, the module
769 will be called rtc-s3c.
771 config RTC_DRV_EP93XX
772 tristate "Cirrus Logic EP93XX"
773 depends on ARCH_EP93XX
775 If you say yes here you get support for the
776 RTC embedded in the Cirrus Logic EP93XX processors.
778 This driver can also be built as a module. If so, the module
779 will be called rtc-ep93xx.
781 config RTC_DRV_SA1100
782 tristate "SA11x0/PXA2xx/PXA910"
783 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
785 If you say Y here you will get access to the real time clock
786 built into your SA11x0 or PXA2xx CPU.
788 To compile this driver as a module, choose M here: the
789 module will be called rtc-sa1100.
792 tristate "SuperH On-Chip RTC"
793 depends on RTC_CLASS && SUPERH && HAVE_CLK
795 Say Y here to enable support for the on-chip RTC found in
796 most SuperH processors.
798 To compile this driver as a module, choose M here: the
799 module will be called rtc-sh.
801 config RTC_DRV_VR41XX
802 tristate "NEC VR41XX"
803 depends on CPU_VR41XX
805 If you say Y here you will get access to the real time clock
806 built into your NEC VR41XX CPU.
808 To compile this driver as a module, choose M here: the
809 module will be called rtc-vr41xx.
812 tristate "ARM AMBA PL030 RTC"
815 If you say Y here you will get access to ARM AMBA
816 PrimeCell PL030 RTC found on certain ARM SOCs.
818 To compile this driver as a module, choose M here: the
819 module will be called rtc-pl030.
822 tristate "ARM AMBA PL031 RTC"
825 If you say Y here you will get access to ARM AMBA
826 PrimeCell PL031 RTC found on certain ARM SOCs.
828 To compile this driver as a module, choose M here: the
829 module will be called rtc-pl031.
831 config RTC_DRV_AT32AP700X
832 tristate "AT32AP700X series RTC"
833 depends on PLATFORM_AT32AP
835 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
836 AT32AP700x family processors.
838 config RTC_DRV_AT91RM9200
839 tristate "AT91RM9200 or some AT91SAM9 RTC"
842 Driver for the internal RTC (Realtime Clock) module found on
843 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
844 this is powered by the backup power supply.
846 config RTC_DRV_AT91SAM9
847 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
848 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
850 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
851 (Real Time Timer). These timers are powered by the backup power
852 supply (such as a small coin cell battery), but do not need to
855 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
856 dedicated RTC module and leave the RTT available for other uses.)
858 config RTC_DRV_AT91SAM9_RTT
862 prompt "RTT module Number" if ARCH_AT91SAM9263
863 depends on RTC_DRV_AT91SAM9
865 More than one RTT module is available. You can choose which
866 one will be used as an RTC. The default of zero is normally
867 OK to use, though some systems use that for non-RTC purposes.
869 config RTC_DRV_AT91SAM9_GPBR
871 range 0 3 if !ARCH_AT91SAM9263
872 range 0 15 if ARCH_AT91SAM9263
874 prompt "Backup Register Number"
875 depends on RTC_DRV_AT91SAM9
877 The RTC driver needs to use one of the General Purpose Backup
878 Registers (GPBRs) as well as the RTT. You can choose which one
879 will be used. The default of zero is normally OK to use, but
880 on some systems other software needs to use that register.
882 config RTC_DRV_AU1XXX
883 tristate "Au1xxx Counter0 RTC support"
884 depends on MIPS_ALCHEMY
886 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
887 counter) to be used as a RTC.
889 This driver can also be built as a module. If so, the module
890 will be called rtc-au1xxx.
893 tristate "Blackfin On-Chip RTC"
894 depends on BLACKFIN && !BF561
896 If you say yes here you will get support for the
897 Blackfin On-Chip Real Time Clock.
899 This driver can also be built as a module. If so, the module
900 will be called rtc-bfin.
902 config RTC_DRV_RS5C313
903 tristate "Ricoh RS5C313"
904 depends on SH_LANDISK
906 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
908 config RTC_DRV_GENERIC
909 tristate "Generic RTC support"
910 # Please consider writing a new RTC driver instead of using the generic
912 depends on PARISC || M68K || PPC || SUPERH32
914 Say Y or M here to enable RTC support on systems using the generic
915 RTC abstraction. If you do not know what you are doing, you should
919 tristate "PXA27x/PXA3xx"
922 If you say Y here you will get access to the real time clock
923 built into your PXA27x or PXA3xx CPU.
925 This RTC driver uses PXA RTC registers available since pxa27x
926 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
928 config RTC_DRV_VT8500
929 tristate "VIA/WonderMedia 85xx SoC RTC"
930 depends on ARCH_VT8500
932 If you say Y here you will get access to the real time clock
933 built into your VIA VT8500 SoC or its relatives.
937 bool "SUN4V Hypervisor RTC"
940 If you say Y here you will get support for the Hypervisor
941 based RTC on SUN4V systems.
943 config RTC_DRV_STARFIRE
947 If you say Y here you will get support for the RTC found on
950 config RTC_DRV_TX4939
951 tristate "TX4939 SoC"
952 depends on SOC_TX4939
954 Driver for the internal RTC (Realtime Clock) module found on
958 tristate "Marvell SoC RTC"
959 depends on ARCH_KIRKWOOD || ARCH_DOVE
961 If you say yes here you will get support for the in-chip RTC
962 that can be found in some of Marvell's SoC devices, such as
963 the Kirkwood 88F6281 and 88F6192.
965 This driver can also be built as a module. If so, the module
966 will be called rtc-mv.
972 If you say yes here you will get support for the RTC on PS3.
974 This driver can also be built as a module. If so, the module
975 will be called rtc-ps3.
977 config RTC_DRV_COH901331
978 tristate "ST-Ericsson COH 901 331 RTC"
981 If you say Y here you will get access to ST-Ericsson
982 COH 901 331 RTC clock found in some ST-Ericsson Mobile
985 This driver can also be built as a module. If so, the module
986 will be called "rtc-coh901331".
990 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
993 If you say yes here you will get support for the onboard
994 STMP3xxx/i.MX23/i.MX28 RTC.
996 This driver can also be built as a module. If so, the module
997 will be called rtc-stmp3xxx.
1003 If you say Y here you will get support for the RTC found on
1004 the PCAP2 ASIC used on some Motorola phones.
1006 config RTC_DRV_MC13XXX
1007 depends on MFD_MC13XXX
1008 tristate "Freescale MC13xxx RTC"
1010 This enables support for the RTCs found on Freescale's PMICs
1011 MC13783 and MC13892.
1013 config RTC_DRV_MPC5121
1014 tristate "Freescale MPC5121 built-in RTC"
1015 depends on PPC_MPC512x || PPC_MPC52xx
1017 If you say yes here you will get support for the
1018 built-in RTC on MPC5121 or on MPC5200.
1020 This driver can also be built as a module. If so, the module
1021 will be called rtc-mpc5121.
1023 config RTC_DRV_JZ4740
1024 tristate "Ingenic JZ4740 SoC"
1025 depends on RTC_CLASS
1026 depends on MACH_JZ4740
1028 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1031 This driver can also be buillt as a module. If so, the module
1032 will be called rtc-jz4740.
1034 config RTC_DRV_LPC32XX
1035 depends on ARCH_LPC32XX
1036 tristate "NXP LPC32XX RTC"
1038 This enables support for the NXP RTC in the LPC32XX
1040 This driver can also be buillt as a module. If so, the module
1041 will be called rtc-lpc32xx.
1043 config RTC_DRV_PM8XXX
1044 tristate "Qualcomm PMIC8XXX RTC"
1045 depends on MFD_PM8XXX
1047 If you say yes here you get support for the
1048 Qualcomm PMIC8XXX RTC.
1050 To compile this driver as a module, choose M here: the
1051 module will be called rtc-pm8xxx.
1053 config RTC_DRV_TEGRA
1054 tristate "NVIDIA Tegra Internal RTC driver"
1055 depends on RTC_CLASS && ARCH_TEGRA
1057 If you say yes here you get support for the
1058 Tegra 200 series internal RTC module.
1060 This drive can also be built as a module. If so, the module
1061 will be called rtc-tegra.
1064 tristate "Tilera hypervisor RTC support"
1067 Enable support for the Linux driver side of the Tilera
1068 hypervisor's real-time clock interface.
1071 tristate "PKUnity v3 RTC support"
1072 depends on ARCH_PUV3
1074 This enables support for the RTC in the PKUnity-v3 SoCs.
1076 This drive can also be built as a module. If so, the module
1077 will be called rtc-puv3.
1079 config RTC_DRV_LOONGSON1
1080 tristate "loongson1 RTC support"
1081 depends on MACH_LOONGSON1
1083 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1084 counter) to be used as a RTC.
1086 This driver can also be built as a module. If so, the module
1087 will be called rtc-ls1x.
1090 tristate "Freescale MXC Real Time Clock"
1092 depends on RTC_CLASS
1094 If you say yes here you get support for the Freescale MXC
1097 This driver can also be built as a module, if so, the module
1098 will be called "rtc-mxc".