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 rtcN)"
76 Say yes here if you want to use your system clock RTC through
77 the proc interface, /proc/driver/rtc.
78 Other RTCs will not be available through that API.
79 If there is no RTC for the system clock, then the first RTC(rtc0)
85 boolean "/dev/rtcN (character devices)"
88 Say yes here if you want to use your RTCs using the /dev
89 interfaces, which "udev" sets up as /dev/rtc0 through
92 You may want to set up a symbolic link so one of these
93 can be accessed as /dev/rtc, which is a name
94 expected by "hwclock" and some other programs. Recent
95 versions of "udev" are known to set up the symlink for you.
99 config RTC_INTF_DEV_UIE_EMUL
100 bool "RTC UIE emulation on dev interface"
101 depends on RTC_INTF_DEV
103 Provides an emulation for RTC_UIE if the underlying rtc chip
104 driver does not expose RTC_UIE ioctls. Those requests generate
105 once-per-second update interrupts, used for synchronization.
107 The emulation code will read the time from the hardware
108 clock several times per second, please enable this option
109 only if you know that you really need it.
112 tristate "Test driver/device"
114 If you say yes here you get support for the
115 RTC test driver. It's a software RTC which can be
116 used to test the RTC subsystem APIs. It gets
117 the time from the system clock.
118 You want this driver only if you are doing development
119 on the RTC subsystem. Please read the source code
122 This driver can also be built as a module. If so, the module
123 will be called rtc-test.
125 comment "I2C RTC drivers"
130 config RTC_DRV_88PM860X
131 tristate "Marvell 88PM860x"
132 depends on RTC_CLASS && I2C && MFD_88PM860X
134 If you say yes here you get support for RTC function in Marvell
137 This driver can also be built as a module. If so, the module
138 will be called rtc-88pm860x.
140 config RTC_DRV_88PM80X
141 tristate "Marvell 88PM80x"
142 depends on RTC_CLASS && I2C && MFD_88PM800
144 If you say yes here you get support for RTC function in Marvell
147 This driver can also be built as a module. If so, the module
148 will be called rtc-88pm80x.
150 config RTC_DRV_DS1307
151 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
153 If you say yes here you get support for various compatible RTC
154 chips (often with battery backup) connected with I2C. This driver
155 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
156 EPSON RX-8025 and probably other chips. In some cases the RTC
157 must already have been initialized (by manufacturing or a
160 The first seven registers on these chips hold an RTC, and other
161 registers may add features such as NVRAM, a trickle charger for
162 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
163 sysfs, but other chip features may not be available.
165 This driver can also be built as a module. If so, the module
166 will be called rtc-ds1307.
168 config RTC_DRV_DS1374
169 tristate "Dallas/Maxim DS1374"
170 depends on RTC_CLASS && I2C
172 If you say yes here you get support for Dallas Semiconductor
173 DS1374 real-time clock chips. If an interrupt is associated
174 with the device, the alarm functionality is supported.
176 This driver can also be built as a module. If so, the module
177 will be called rtc-ds1374.
179 config RTC_DRV_DS1672
180 tristate "Dallas/Maxim DS1672"
182 If you say yes here you get support for the
183 Dallas/Maxim DS1672 timekeeping chip.
185 This driver can also be built as a module. If so, the module
186 will be called rtc-ds1672.
188 config RTC_DRV_DS3232
189 tristate "Dallas/Maxim DS3232"
190 depends on RTC_CLASS && I2C
192 If you say yes here you get support for Dallas Semiconductor
193 DS3232 real-time clock chips. If an interrupt is associated
194 with the device, the alarm functionality is supported.
196 This driver can also be built as a module. If so, the module
197 will be called rtc-ds3232.
199 config RTC_DRV_MAX6900
200 tristate "Maxim MAX6900"
202 If you say yes here you will get support for the
203 Maxim MAX6900 I2C RTC chip.
205 This driver can also be built as a module. If so, the module
206 will be called rtc-max6900.
208 config RTC_DRV_MAX8925
209 tristate "Maxim MAX8925"
210 depends on MFD_MAX8925
212 If you say yes here you will get support for the
213 RTC of Maxim MAX8925 PMIC.
215 This driver can also be built as a module. If so, the module
216 will be called rtc-max8925.
218 config RTC_DRV_MAX8998
219 tristate "Maxim MAX8998"
220 depends on MFD_MAX8998
222 If you say yes here you will get support for the
223 RTC of Maxim MAX8998 PMIC.
225 This driver can also be built as a module. If so, the module
226 will be called rtc-max8998.
228 config RTC_DRV_RS5C372
229 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
231 If you say yes here you get support for the
232 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
234 This driver can also be built as a module. If so, the module
235 will be called rtc-rs5c372.
237 config RTC_DRV_ISL1208
238 tristate "Intersil ISL1208"
240 If you say yes here you get support for the
241 Intersil ISL1208 RTC chip.
243 This driver can also be built as a module. If so, the module
244 will be called rtc-isl1208.
246 config RTC_DRV_ISL12022
247 tristate "Intersil ISL12022"
249 If you say yes here you get support for the
250 Intersil ISL12022 RTC chip.
252 This driver can also be built as a module. If so, the module
253 will be called rtc-isl12022.
256 tristate "Xicor/Intersil X1205"
258 If you say yes here you get support for the
259 Xicor/Intersil X1205 RTC chip.
261 This driver can also be built as a module. If so, the module
262 will be called rtc-x1205.
264 config RTC_DRV_PCF8563
265 tristate "Philips PCF8563/Epson RTC8564"
267 If you say yes here you get support for the
268 Philips PCF8563 RTC chip. The Epson RTC8564
271 This driver can also be built as a module. If so, the module
272 will be called rtc-pcf8563.
274 config RTC_DRV_PCF8583
275 tristate "Philips PCF8583"
277 If you say yes here you get support for the Philips PCF8583
278 RTC chip found on Acorn RiscPCs. This driver supports the
279 platform specific method of retrieving the current year from
280 the RTC's SRAM. It will work on other platforms with the same
281 chip, but the year will probably have to be tweaked.
283 This driver can also be built as a module. If so, the module
284 will be called rtc-pcf8583.
286 config RTC_DRV_M41T80
287 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
289 If you say Y here you will get support for the ST M41T60
290 and M41T80 RTC chips series. Currently, the following chips are
291 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
292 M41ST85, and M41ST87.
294 This driver can also be built as a module. If so, the module
295 will be called rtc-m41t80.
297 config RTC_DRV_M41T80_WDT
298 bool "ST M41T65/M41T80 series RTC watchdog timer"
299 depends on RTC_DRV_M41T80
301 If you say Y here you will get support for the
302 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
305 tristate "TI BQ32000"
307 If you say Y here you will get support for the TI
308 BQ32000 I2C RTC chip.
310 This driver can also be built as a module. If so, the module
311 will be called rtc-bq32k.
313 config RTC_DRV_DM355EVM
314 tristate "TI DaVinci DM355 EVM RTC"
315 depends on MFD_DM355EVM_MSP
317 Supports the RTC firmware in the MSP430 on the DM355 EVM.
319 config RTC_DRV_TWL92330
320 boolean "TI TWL92330/Menelaus"
323 If you say yes here you get support for the RTC on the
324 TWL92330 "Menelaus" power management chip, used with OMAP2
325 platforms. The support is integrated with the rest of
326 the Menelaus driver; it's not separate module.
328 config RTC_DRV_TWL4030
329 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
330 depends on RTC_CLASS && TWL4030_CORE
332 If you say yes here you get support for the RTC on the
333 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
335 This driver can also be built as a module. If so, the module
336 will be called rtc-twl.
338 config RTC_DRV_S35390A
339 tristate "Seiko Instruments S-35390A"
342 If you say yes here you will get support for the Seiko
343 Instruments S-35390A.
345 This driver can also be built as a module. If so the module
346 will be called rtc-s35390a.
348 config RTC_DRV_FM3130
349 tristate "Ramtron FM3130"
351 If you say Y here you will get support for the
352 Ramtron FM3130 RTC chips.
353 Ramtron FM3130 is a chip with two separate devices inside,
354 RTC clock and FRAM. This driver provides only RTC functionality.
356 This driver can also be built as a module. If so the module
357 will be called rtc-fm3130.
359 config RTC_DRV_RX8581
360 tristate "Epson RX-8581"
362 If you say yes here you will get support for the Epson RX-8581.
364 This driver can also be built as a module. If so the module
365 will be called rtc-rx8581.
367 config RTC_DRV_RX8025
368 tristate "Epson RX-8025SA/NB"
370 If you say yes here you get support for the Epson
371 RX-8025SA/NB RTC chips.
373 This driver can also be built as a module. If so, the module
374 will be called rtc-rx8025.
376 config RTC_DRV_EM3027
377 tristate "EM Microelectronic EM3027"
379 If you say yes here you get support for the EM
380 Microelectronic EM3027 RTC chips.
382 This driver can also be built as a module. If so, the module
383 will be called rtc-em3027.
385 config RTC_DRV_RV3029C2
386 tristate "Micro Crystal RTC"
388 If you say yes here you get support for the Micro Crystal
391 This driver can also be built as a module. If so, the module
392 will be called rtc-rv3029c2.
396 comment "SPI RTC drivers"
400 config RTC_DRV_M41T93
403 If you say yes here you will get support for the
404 ST M41T93 SPI RTC chip.
406 This driver can also be built as a module. If so, the module
407 will be called rtc-m41t93.
409 config RTC_DRV_M41T94
412 If you say yes here you will get support for the
413 ST M41T94 SPI RTC chip.
415 This driver can also be built as a module. If so, the module
416 will be called rtc-m41t94.
418 config RTC_DRV_DS1305
419 tristate "Dallas/Maxim DS1305/DS1306"
421 Select this driver to get support for the Dallas/Maxim DS1305
422 and DS1306 real time clock chips. These support a trickle
423 charger, alarms, and NVRAM in addition to the clock.
425 This driver can also be built as a module. If so, the module
426 will be called rtc-ds1305.
428 config RTC_DRV_DS1390
429 tristate "Dallas/Maxim DS1390/93/94"
431 If you say yes here you get support for the
432 Dallas/Maxim DS1390/93/94 chips.
434 This driver only supports the RTC feature, and not other chip
435 features such as alarms and trickle charging.
437 This driver can also be built as a module. If so, the module
438 will be called rtc-ds1390.
440 config RTC_DRV_MAX6902
441 tristate "Maxim MAX6902"
443 If you say yes here you will get support for the
444 Maxim MAX6902 SPI RTC chip.
446 This driver can also be built as a module. If so, the module
447 will be called rtc-max6902.
450 tristate "Epson RTC-9701JE"
452 If you say yes here you will get support for the
453 Epson RTC-9701JE SPI RTC chip.
455 This driver can also be built as a module. If so, the module
456 will be called rtc-r9701.
458 config RTC_DRV_RS5C348
459 tristate "Ricoh RS5C348A/B"
461 If you say yes here you get support for the
462 Ricoh RS5C348A and RS5C348B RTC chips.
464 This driver can also be built as a module. If so, the module
465 will be called rtc-rs5c348.
467 config RTC_DRV_DS3234
468 tristate "Maxim/Dallas DS3234"
470 If you say yes here you get support for the
471 Maxim/Dallas DS3234 SPI RTC chip.
473 This driver can also be built as a module. If so, the module
474 will be called rtc-ds3234.
476 config RTC_DRV_PCF2123
477 tristate "NXP PCF2123"
479 If you say yes here you get support for the NXP PCF2123
482 This driver can also be built as a module. If so, the module
483 will be called rtc-pcf2123.
487 comment "Platform RTC drivers"
489 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
490 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
491 # global rtc_lock ... it's not yet just another platform_device.
494 tristate "PC-style 'CMOS'"
495 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
498 Say "yes" here to get direct support for the real time clock
499 found in every PC or ACPI-based system, and some other boards.
500 Specifically the original MC146818, compatibles like those in
501 PC south bridges, the DS12887 or M48T86, some multifunction
502 or LPC bus chips, and so on.
504 Your system will need to define the platform device used by
505 this driver, otherwise it won't be accessible. This means
506 you can safely enable this driver if you don't know whether
507 or not your board has this kind of hardware.
509 This driver can also be built as a module. If so, the module
510 will be called rtc-cmos.
513 tristate "Virtual RTC for Intel MID platforms"
514 depends on X86_INTEL_MID
515 default y if X86_INTEL_MID
518 Say "yes" here to get direct support for the real time clock
519 found on Moorestown platforms. The VRTC is a emulated RTC that
520 derives its clock source from a real RTC in the PMIC. The MC146818
521 style programming interface is mostly conserved, but any
522 updates are done via IPC calls to the system controller FW.
524 config RTC_DRV_DS1216
525 tristate "Dallas DS1216"
528 If you say yes here you get support for the Dallas DS1216 RTC chips.
530 config RTC_DRV_DS1286
531 tristate "Dallas DS1286"
533 If you say yes here you get support for the Dallas DS1286 RTC chips.
535 config RTC_DRV_DS1302
536 tristate "Dallas DS1302"
537 depends on SH_SECUREEDGE5410
539 If you say yes here you get support for the Dallas DS1302 RTC chips.
541 config RTC_DRV_DS1511
542 tristate "Dallas DS1511"
545 If you say yes here you get support for the
546 Dallas DS1511 timekeeping/watchdog chip.
548 This driver can also be built as a module. If so, the module
549 will be called rtc-ds1511.
551 config RTC_DRV_DS1553
552 tristate "Maxim/Dallas DS1553"
554 If you say yes here you get support for the
555 Maxim/Dallas DS1553 timekeeping chip.
557 This driver can also be built as a module. If so, the module
558 will be called rtc-ds1553.
560 config RTC_DRV_DS1742
561 tristate "Maxim/Dallas DS1742/1743"
563 If you say yes here you get support for the
564 Maxim/Dallas DS1742/1743 timekeeping chip.
566 This driver can also be built as a module. If so, the module
567 will be called rtc-ds1742.
569 config RTC_DRV_DA9052
570 tristate "Dialog DA9052/DA9053 RTC"
571 depends on PMIC_DA9052
573 Say y here to support the RTC driver for Dialog Semiconductor
574 DA9052-BC and DA9053-AA/Bx PMICs.
580 If you say yes here you will get support for the EFI
583 This driver can also be built as a module. If so, the module
584 will be called rtc-efi.
586 config RTC_DRV_STK17TA8
587 tristate "Simtek STK17TA8"
590 If you say yes here you get support for the
591 Simtek STK17TA8 timekeeping chip.
593 This driver can also be built as a module. If so, the module
594 will be called rtc-stk17ta8.
596 config RTC_DRV_M48T86
597 tristate "ST M48T86/Dallas DS12887"
599 If you say Y here you will get support for the
600 ST M48T86 and Dallas DS12887 RTC chips.
602 This driver can also be built as a module. If so, the module
603 will be called rtc-m48t86.
605 config RTC_DRV_M48T35
608 If you say Y here you will get support for the
611 This driver can also be built as a module, if so, the module
612 will be called "rtc-m48t35".
614 config RTC_DRV_M48T59
615 tristate "ST M48T59/M48T08/M48T02"
617 If you say Y here you will get support for the
618 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
620 These chips are usually found in Sun SPARC and UltraSPARC
623 This driver can also be built as a module, if so, the module
624 will be called "rtc-m48t59".
626 config RTC_DRV_MSM6242
627 tristate "Oki MSM6242"
629 If you say yes here you get support for the Oki MSM6242
630 timekeeping chip. It is used in some Amiga models (e.g. A2000).
632 This driver can also be built as a module. If so, the module
633 will be called rtc-msm6242.
635 config RTC_DRV_BQ4802
638 If you say Y here you will get support for the TI
641 This driver can also be built as a module. If so, the module
642 will be called rtc-bq4802.
644 config RTC_DRV_RP5C01
645 tristate "Ricoh RP5C01"
647 If you say yes here you get support for the Ricoh RP5C01
648 timekeeping chip. It is used in some Amiga models (e.g. A3000
651 This driver can also be built as a module. If so, the module
652 will be called rtc-rp5c01.
655 tristate "EM Microelectronic V3020"
657 If you say yes here you will get support for the
658 EM Microelectronic v3020 RTC chip.
660 This driver can also be built as a module. If so, the module
661 will be called rtc-v3020.
663 config RTC_DRV_WM831X
664 tristate "Wolfson Microelectronics WM831x RTC"
665 depends on MFD_WM831X
667 If you say yes here you will get support for the RTC subsystem
668 of the Wolfson Microelectronics WM831X series PMICs.
670 This driver can also be built as a module. If so, the module
671 will be called "rtc-wm831x".
673 config RTC_DRV_WM8350
674 tristate "Wolfson Microelectronics WM8350 RTC"
675 depends on MFD_WM8350
677 If you say yes here you will get support for the RTC subsystem
678 of the Wolfson Microelectronics WM8350.
680 This driver can also be built as a module. If so, the module
681 will be called "rtc-wm8350".
684 tristate "SPEAR ST RTC"
685 depends on PLAT_SPEAR
688 If you say Y here you will get support for the RTC found on
691 config RTC_DRV_PCF50633
692 depends on MFD_PCF50633
693 tristate "NXP PCF50633 RTC"
695 If you say yes here you get support for the RTC subsystem of the
696 NXP PCF50633 used in embedded systems.
698 config RTC_DRV_AB3100
699 tristate "ST-Ericsson AB3100 RTC"
700 depends on AB3100_CORE
701 default y if AB3100_CORE
703 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
704 support. This chip contains a battery- and capacitor-backed RTC.
706 config RTC_DRV_AB8500
707 tristate "ST-Ericsson AB8500 RTC"
708 depends on AB8500_CORE
709 select RTC_INTF_DEV_UIE_EMUL
711 Select this to enable the ST-Ericsson AB8500 power management IC RTC
712 support. This chip contains a battery- and capacitor-backed RTC.
714 config RTC_DRV_NUC900
715 tristate "NUC910/NUC920 RTC driver"
716 depends on RTC_CLASS && ARCH_W90X900
718 If you say yes here you get support for the RTC subsystem of the
719 NUC910/NUC920 used in embedded systems.
721 comment "on-CPU RTC drivers"
723 config RTC_DRV_DAVINCI
724 tristate "TI DaVinci RTC"
725 depends on ARCH_DAVINCI_DM365
727 If you say yes here you get support for the RTC on the
728 DaVinci platforms (DM365).
730 This driver can also be built as a module. If so, the module
731 will be called rtc-davinci.
734 tristate "Freescale IMX DryIce Real Time Clock"
738 Support for Freescale IMX DryIce RTC
740 This driver can also be built as a module, if so, the module
741 will be called "rtc-imxdi".
745 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
747 Say "yes" here to support the real time clock on TI OMAP1 and
748 DA8xx/OMAP-L13x chips. This driver can also be built as a
749 module called rtc-omap.
754 This will include RTC support for Samsung SoCs. If
755 you want to include RTC support for any machine, kindly
756 select this in the respective mach-XXXX/Kconfig file.
759 tristate "Samsung S3C series SoC RTC"
760 depends on ARCH_S3C64XX || HAVE_S3C_RTC
762 RTC (Realtime Clock) driver for the clock inbuilt into the
763 Samsung S3C24XX series of SoCs. This can provide periodic
764 interrupt rates from 1Hz to 64Hz for user programs, and
767 The driver currently supports the common features on all the
768 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
771 This driver can also be build as a module. If so, the module
772 will be called rtc-s3c.
774 config RTC_DRV_EP93XX
775 tristate "Cirrus Logic EP93XX"
776 depends on ARCH_EP93XX
778 If you say yes here you get support for the
779 RTC embedded in the Cirrus Logic EP93XX processors.
781 This driver can also be built as a module. If so, the module
782 will be called rtc-ep93xx.
784 config RTC_DRV_SA1100
785 tristate "SA11x0/PXA2xx/PXA910"
786 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
788 If you say Y here you will get access to the real time clock
789 built into your SA11x0 or PXA2xx CPU.
791 To compile this driver as a module, choose M here: the
792 module will be called rtc-sa1100.
795 tristate "SuperH On-Chip RTC"
796 depends on RTC_CLASS && SUPERH && HAVE_CLK
798 Say Y here to enable support for the on-chip RTC found in
799 most SuperH processors.
801 To compile this driver as a module, choose M here: the
802 module will be called rtc-sh.
804 config RTC_DRV_VR41XX
805 tristate "NEC VR41XX"
806 depends on CPU_VR41XX
808 If you say Y here you will get access to the real time clock
809 built into your NEC VR41XX CPU.
811 To compile this driver as a module, choose M here: the
812 module will be called rtc-vr41xx.
815 tristate "ARM AMBA PL030 RTC"
818 If you say Y here you will get access to ARM AMBA
819 PrimeCell PL030 RTC found on certain ARM SOCs.
821 To compile this driver as a module, choose M here: the
822 module will be called rtc-pl030.
825 tristate "ARM AMBA PL031 RTC"
828 If you say Y here you will get access to ARM AMBA
829 PrimeCell PL031 RTC found on certain ARM SOCs.
831 To compile this driver as a module, choose M here: the
832 module will be called rtc-pl031.
834 config RTC_DRV_AT32AP700X
835 tristate "AT32AP700X series RTC"
836 depends on PLATFORM_AT32AP
838 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
839 AT32AP700x family processors.
841 config RTC_DRV_AT91RM9200
842 tristate "AT91RM9200 or some AT91SAM9 RTC"
845 Driver for the internal RTC (Realtime Clock) module found on
846 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
847 this is powered by the backup power supply.
849 config RTC_DRV_AT91SAM9
850 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
851 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
853 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
854 (Real Time Timer). These timers are powered by the backup power
855 supply (such as a small coin cell battery), but do not need to
858 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
859 dedicated RTC module and leave the RTT available for other uses.)
861 config RTC_DRV_AT91SAM9_RTT
865 prompt "RTT module Number" if ARCH_AT91SAM9263
866 depends on RTC_DRV_AT91SAM9
868 More than one RTT module is available. You can choose which
869 one will be used as an RTC. The default of zero is normally
870 OK to use, though some systems use that for non-RTC purposes.
872 config RTC_DRV_AT91SAM9_GPBR
874 range 0 3 if !ARCH_AT91SAM9263
875 range 0 15 if ARCH_AT91SAM9263
877 prompt "Backup Register Number"
878 depends on RTC_DRV_AT91SAM9
880 The RTC driver needs to use one of the General Purpose Backup
881 Registers (GPBRs) as well as the RTT. You can choose which one
882 will be used. The default of zero is normally OK to use, but
883 on some systems other software needs to use that register.
885 config RTC_DRV_AU1XXX
886 tristate "Au1xxx Counter0 RTC support"
887 depends on MIPS_ALCHEMY
889 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
890 counter) to be used as a RTC.
892 This driver can also be built as a module. If so, the module
893 will be called rtc-au1xxx.
896 tristate "Blackfin On-Chip RTC"
897 depends on BLACKFIN && !BF561
899 If you say yes here you will get support for the
900 Blackfin On-Chip Real Time Clock.
902 This driver can also be built as a module. If so, the module
903 will be called rtc-bfin.
905 config RTC_DRV_RS5C313
906 tristate "Ricoh RS5C313"
907 depends on SH_LANDISK
909 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
911 config RTC_DRV_GENERIC
912 tristate "Generic RTC support"
913 # Please consider writing a new RTC driver instead of using the generic
915 depends on PARISC || M68K || PPC || SUPERH32
917 Say Y or M here to enable RTC support on systems using the generic
918 RTC abstraction. If you do not know what you are doing, you should
922 tristate "PXA27x/PXA3xx"
925 If you say Y here you will get access to the real time clock
926 built into your PXA27x or PXA3xx CPU.
928 This RTC driver uses PXA RTC registers available since pxa27x
929 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
931 config RTC_DRV_VT8500
932 tristate "VIA/WonderMedia 85xx SoC RTC"
933 depends on ARCH_VT8500
935 If you say Y here you will get access to the real time clock
936 built into your VIA VT8500 SoC or its relatives.
940 bool "SUN4V Hypervisor RTC"
943 If you say Y here you will get support for the Hypervisor
944 based RTC on SUN4V systems.
946 config RTC_DRV_STARFIRE
950 If you say Y here you will get support for the RTC found on
953 config RTC_DRV_TX4939
954 tristate "TX4939 SoC"
955 depends on SOC_TX4939
957 Driver for the internal RTC (Realtime Clock) module found on
961 tristate "Marvell SoC RTC"
962 depends on ARCH_KIRKWOOD || ARCH_DOVE
964 If you say yes here you will get support for the in-chip RTC
965 that can be found in some of Marvell's SoC devices, such as
966 the Kirkwood 88F6281 and 88F6192.
968 This driver can also be built as a module. If so, the module
969 will be called rtc-mv.
975 If you say yes here you will get support for the RTC on PS3.
977 This driver can also be built as a module. If so, the module
978 will be called rtc-ps3.
980 config RTC_DRV_COH901331
981 tristate "ST-Ericsson COH 901 331 RTC"
984 If you say Y here you will get access to ST-Ericsson
985 COH 901 331 RTC clock found in some ST-Ericsson Mobile
988 This driver can also be built as a module. If so, the module
989 will be called "rtc-coh901331".
993 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
996 If you say yes here you will get support for the onboard
997 STMP3xxx/i.MX23/i.MX28 RTC.
999 This driver can also be built as a module. If so, the module
1000 will be called rtc-stmp3xxx.
1006 If you say Y here you will get support for the RTC found on
1007 the PCAP2 ASIC used on some Motorola phones.
1009 config RTC_DRV_MC13XXX
1010 depends on MFD_MC13XXX
1011 tristate "Freescale MC13xxx RTC"
1013 This enables support for the RTCs found on Freescale's PMICs
1014 MC13783 and MC13892.
1016 config RTC_DRV_MPC5121
1017 tristate "Freescale MPC5121 built-in RTC"
1018 depends on PPC_MPC512x || PPC_MPC52xx
1020 If you say yes here you will get support for the
1021 built-in RTC on MPC5121 or on MPC5200.
1023 This driver can also be built as a module. If so, the module
1024 will be called rtc-mpc5121.
1026 config RTC_DRV_JZ4740
1027 tristate "Ingenic JZ4740 SoC"
1028 depends on RTC_CLASS
1029 depends on MACH_JZ4740
1031 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1034 This driver can also be buillt as a module. If so, the module
1035 will be called rtc-jz4740.
1037 config RTC_DRV_LPC32XX
1038 depends on ARCH_LPC32XX
1039 tristate "NXP LPC32XX RTC"
1041 This enables support for the NXP RTC in the LPC32XX
1043 This driver can also be buillt as a module. If so, the module
1044 will be called rtc-lpc32xx.
1046 config RTC_DRV_PM8XXX
1047 tristate "Qualcomm PMIC8XXX RTC"
1048 depends on MFD_PM8XXX
1050 If you say yes here you get support for the
1051 Qualcomm PMIC8XXX RTC.
1053 To compile this driver as a module, choose M here: the
1054 module will be called rtc-pm8xxx.
1056 config RTC_DRV_TEGRA
1057 tristate "NVIDIA Tegra Internal RTC driver"
1058 depends on RTC_CLASS && ARCH_TEGRA
1060 If you say yes here you get support for the
1061 Tegra 200 series internal RTC module.
1063 This drive can also be built as a module. If so, the module
1064 will be called rtc-tegra.
1067 tristate "Tilera hypervisor RTC support"
1070 Enable support for the Linux driver side of the Tilera
1071 hypervisor's real-time clock interface.
1074 tristate "PKUnity v3 RTC support"
1075 depends on ARCH_PUV3
1077 This enables support for the RTC in the PKUnity-v3 SoCs.
1079 This drive can also be built as a module. If so, the module
1080 will be called rtc-puv3.
1082 config RTC_DRV_LOONGSON1
1083 tristate "loongson1 RTC support"
1084 depends on MACH_LOONGSON1
1086 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1087 counter) to be used as a RTC.
1089 This driver can also be built as a module. If so, the module
1090 will be called rtc-ls1x.
1093 tristate "Freescale MXC Real Time Clock"
1095 depends on RTC_CLASS
1097 If you say yes here you get support for the Freescale MXC
1100 This driver can also be built as a module, if so, the module
1101 will be called "rtc-mxc".