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_MAX8907
209 tristate "Maxim MAX8907"
210 depends on MFD_MAX8907
212 If you say yes here you will get support for the
213 RTC of Maxim MAX8907 PMIC.
215 This driver can also be built as a module. If so, the module
216 will be called rtc-max8907.
218 config RTC_DRV_MAX8925
219 tristate "Maxim MAX8925"
220 depends on MFD_MAX8925
222 If you say yes here you will get support for the
223 RTC of Maxim MAX8925 PMIC.
225 This driver can also be built as a module. If so, the module
226 will be called rtc-max8925.
228 config RTC_DRV_MAX8998
229 tristate "Maxim MAX8998"
230 depends on MFD_MAX8998
232 If you say yes here you will get support for the
233 RTC of Maxim MAX8998 PMIC.
235 This driver can also be built as a module. If so, the module
236 will be called rtc-max8998.
238 config RTC_DRV_RS5C372
239 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
241 If you say yes here you get support for the
242 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
244 This driver can also be built as a module. If so, the module
245 will be called rtc-rs5c372.
247 config RTC_DRV_ISL1208
248 tristate "Intersil ISL1208"
250 If you say yes here you get support for the
251 Intersil ISL1208 RTC chip.
253 This driver can also be built as a module. If so, the module
254 will be called rtc-isl1208.
256 config RTC_DRV_ISL12022
257 tristate "Intersil ISL12022"
259 If you say yes here you get support for the
260 Intersil ISL12022 RTC chip.
262 This driver can also be built as a module. If so, the module
263 will be called rtc-isl12022.
266 tristate "Xicor/Intersil X1205"
268 If you say yes here you get support for the
269 Xicor/Intersil X1205 RTC chip.
271 This driver can also be built as a module. If so, the module
272 will be called rtc-x1205.
274 config RTC_DRV_PCF8563
275 tristate "Philips PCF8563/Epson RTC8564"
277 If you say yes here you get support for the
278 Philips PCF8563 RTC chip. The Epson RTC8564
281 This driver can also be built as a module. If so, the module
282 will be called rtc-pcf8563.
284 config RTC_DRV_PCF8583
285 tristate "Philips PCF8583"
287 If you say yes here you get support for the Philips PCF8583
288 RTC chip found on Acorn RiscPCs. This driver supports the
289 platform specific method of retrieving the current year from
290 the RTC's SRAM. It will work on other platforms with the same
291 chip, but the year will probably have to be tweaked.
293 This driver can also be built as a module. If so, the module
294 will be called rtc-pcf8583.
296 config RTC_DRV_M41T80
297 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
299 If you say Y here you will get support for the ST M41T60
300 and M41T80 RTC chips series. Currently, the following chips are
301 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
302 M41ST85, and M41ST87.
304 This driver can also be built as a module. If so, the module
305 will be called rtc-m41t80.
307 config RTC_DRV_M41T80_WDT
308 bool "ST M41T65/M41T80 series RTC watchdog timer"
309 depends on RTC_DRV_M41T80
311 If you say Y here you will get support for the
312 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
315 tristate "TI BQ32000"
317 If you say Y here you will get support for the TI
318 BQ32000 I2C RTC chip.
320 This driver can also be built as a module. If so, the module
321 will be called rtc-bq32k.
323 config RTC_DRV_DM355EVM
324 tristate "TI DaVinci DM355 EVM RTC"
325 depends on MFD_DM355EVM_MSP
327 Supports the RTC firmware in the MSP430 on the DM355 EVM.
329 config RTC_DRV_TWL92330
330 boolean "TI TWL92330/Menelaus"
333 If you say yes here you get support for the RTC on the
334 TWL92330 "Menelaus" power management chip, used with OMAP2
335 platforms. The support is integrated with the rest of
336 the Menelaus driver; it's not separate module.
338 config RTC_DRV_TWL4030
339 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
340 depends on RTC_CLASS && TWL4030_CORE
342 If you say yes here you get support for the RTC on the
343 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
345 This driver can also be built as a module. If so, the module
346 will be called rtc-twl.
348 config RTC_DRV_TPS65910
349 tristate "TI TPS65910 RTC driver"
350 depends on RTC_CLASS && MFD_TPS65910
352 If you say yes here you get support for the RTC on the
355 This driver can also be built as a module. If so, the module
356 will be called rtc-tps65910.
358 config RTC_DRV_S35390A
359 tristate "Seiko Instruments S-35390A"
362 If you say yes here you will get support for the Seiko
363 Instruments S-35390A.
365 This driver can also be built as a module. If so the module
366 will be called rtc-s35390a.
368 config RTC_DRV_FM3130
369 tristate "Ramtron FM3130"
371 If you say Y here you will get support for the
372 Ramtron FM3130 RTC chips.
373 Ramtron FM3130 is a chip with two separate devices inside,
374 RTC clock and FRAM. This driver provides only RTC functionality.
376 This driver can also be built as a module. If so the module
377 will be called rtc-fm3130.
379 config RTC_DRV_RX8581
380 tristate "Epson RX-8581"
382 If you say yes here you will get support for the Epson RX-8581.
384 This driver can also be built as a module. If so the module
385 will be called rtc-rx8581.
387 config RTC_DRV_RX8025
388 tristate "Epson RX-8025SA/NB"
390 If you say yes here you get support for the Epson
391 RX-8025SA/NB RTC chips.
393 This driver can also be built as a module. If so, the module
394 will be called rtc-rx8025.
396 config RTC_DRV_EM3027
397 tristate "EM Microelectronic EM3027"
399 If you say yes here you get support for the EM
400 Microelectronic EM3027 RTC chips.
402 This driver can also be built as a module. If so, the module
403 will be called rtc-em3027.
405 config RTC_DRV_RV3029C2
406 tristate "Micro Crystal RTC"
408 If you say yes here you get support for the Micro Crystal
411 This driver can also be built as a module. If so, the module
412 will be called rtc-rv3029c2.
416 comment "SPI RTC drivers"
420 config RTC_DRV_M41T93
423 If you say yes here you will get support for the
424 ST M41T93 SPI RTC chip.
426 This driver can also be built as a module. If so, the module
427 will be called rtc-m41t93.
429 config RTC_DRV_M41T94
432 If you say yes here you will get support for the
433 ST M41T94 SPI RTC chip.
435 This driver can also be built as a module. If so, the module
436 will be called rtc-m41t94.
438 config RTC_DRV_DS1305
439 tristate "Dallas/Maxim DS1305/DS1306"
441 Select this driver to get support for the Dallas/Maxim DS1305
442 and DS1306 real time clock chips. These support a trickle
443 charger, alarms, and NVRAM in addition to the clock.
445 This driver can also be built as a module. If so, the module
446 will be called rtc-ds1305.
448 config RTC_DRV_DS1390
449 tristate "Dallas/Maxim DS1390/93/94"
451 If you say yes here you get support for the
452 Dallas/Maxim DS1390/93/94 chips.
454 This driver only supports the RTC feature, and not other chip
455 features such as alarms and trickle charging.
457 This driver can also be built as a module. If so, the module
458 will be called rtc-ds1390.
460 config RTC_DRV_MAX6902
461 tristate "Maxim MAX6902"
463 If you say yes here you will get support for the
464 Maxim MAX6902 SPI RTC chip.
466 This driver can also be built as a module. If so, the module
467 will be called rtc-max6902.
470 tristate "Epson RTC-9701JE"
472 If you say yes here you will get support for the
473 Epson RTC-9701JE SPI RTC chip.
475 This driver can also be built as a module. If so, the module
476 will be called rtc-r9701.
478 config RTC_DRV_RS5C348
479 tristate "Ricoh RS5C348A/B"
481 If you say yes here you get support for the
482 Ricoh RS5C348A and RS5C348B RTC chips.
484 This driver can also be built as a module. If so, the module
485 will be called rtc-rs5c348.
487 config RTC_DRV_DS3234
488 tristate "Maxim/Dallas DS3234"
490 If you say yes here you get support for the
491 Maxim/Dallas DS3234 SPI RTC chip.
493 This driver can also be built as a module. If so, the module
494 will be called rtc-ds3234.
496 config RTC_DRV_PCF2123
497 tristate "NXP PCF2123"
499 If you say yes here you get support for the NXP PCF2123
502 This driver can also be built as a module. If so, the module
503 will be called rtc-pcf2123.
507 comment "Platform RTC drivers"
509 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
510 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
511 # global rtc_lock ... it's not yet just another platform_device.
514 tristate "PC-style 'CMOS'"
515 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
518 Say "yes" here to get direct support for the real time clock
519 found in every PC or ACPI-based system, and some other boards.
520 Specifically the original MC146818, compatibles like those in
521 PC south bridges, the DS12887 or M48T86, some multifunction
522 or LPC bus chips, and so on.
524 Your system will need to define the platform device used by
525 this driver, otherwise it won't be accessible. This means
526 you can safely enable this driver if you don't know whether
527 or not your board has this kind of hardware.
529 This driver can also be built as a module. If so, the module
530 will be called rtc-cmos.
533 tristate "Virtual RTC for Intel MID platforms"
534 depends on X86_INTEL_MID
535 default y if X86_INTEL_MID
538 Say "yes" here to get direct support for the real time clock
539 found on Moorestown platforms. The VRTC is a emulated RTC that
540 derives its clock source from a real RTC in the PMIC. The MC146818
541 style programming interface is mostly conserved, but any
542 updates are done via IPC calls to the system controller FW.
544 config RTC_DRV_DS1216
545 tristate "Dallas DS1216"
548 If you say yes here you get support for the Dallas DS1216 RTC chips.
550 config RTC_DRV_DS1286
551 tristate "Dallas DS1286"
553 If you say yes here you get support for the Dallas DS1286 RTC chips.
555 config RTC_DRV_DS1302
556 tristate "Dallas DS1302"
557 depends on SH_SECUREEDGE5410
559 If you say yes here you get support for the Dallas DS1302 RTC chips.
561 config RTC_DRV_DS1511
562 tristate "Dallas DS1511"
565 If you say yes here you get support for the
566 Dallas DS1511 timekeeping/watchdog chip.
568 This driver can also be built as a module. If so, the module
569 will be called rtc-ds1511.
571 config RTC_DRV_DS1553
572 tristate "Maxim/Dallas DS1553"
574 If you say yes here you get support for the
575 Maxim/Dallas DS1553 timekeeping chip.
577 This driver can also be built as a module. If so, the module
578 will be called rtc-ds1553.
580 config RTC_DRV_DS1742
581 tristate "Maxim/Dallas DS1742/1743"
583 If you say yes here you get support for the
584 Maxim/Dallas DS1742/1743 timekeeping chip.
586 This driver can also be built as a module. If so, the module
587 will be called rtc-ds1742.
589 config RTC_DRV_DA9052
590 tristate "Dialog DA9052/DA9053 RTC"
591 depends on PMIC_DA9052
593 Say y here to support the RTC driver for Dialog Semiconductor
594 DA9052-BC and DA9053-AA/Bx PMICs.
600 If you say yes here you will get support for the EFI
603 This driver can also be built as a module. If so, the module
604 will be called rtc-efi.
606 config RTC_DRV_STK17TA8
607 tristate "Simtek STK17TA8"
610 If you say yes here you get support for the
611 Simtek STK17TA8 timekeeping chip.
613 This driver can also be built as a module. If so, the module
614 will be called rtc-stk17ta8.
616 config RTC_DRV_M48T86
617 tristate "ST M48T86/Dallas DS12887"
619 If you say Y here you will get support for the
620 ST M48T86 and Dallas DS12887 RTC chips.
622 This driver can also be built as a module. If so, the module
623 will be called rtc-m48t86.
625 config RTC_DRV_M48T35
628 If you say Y here you will get support for the
631 This driver can also be built as a module, if so, the module
632 will be called "rtc-m48t35".
634 config RTC_DRV_M48T59
635 tristate "ST M48T59/M48T08/M48T02"
637 If you say Y here you will get support for the
638 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
640 These chips are usually found in Sun SPARC and UltraSPARC
643 This driver can also be built as a module, if so, the module
644 will be called "rtc-m48t59".
646 config RTC_DRV_MSM6242
647 tristate "Oki MSM6242"
649 If you say yes here you get support for the Oki MSM6242
650 timekeeping chip. It is used in some Amiga models (e.g. A2000).
652 This driver can also be built as a module. If so, the module
653 will be called rtc-msm6242.
655 config RTC_DRV_BQ4802
658 If you say Y here you will get support for the TI
661 This driver can also be built as a module. If so, the module
662 will be called rtc-bq4802.
664 config RTC_DRV_RP5C01
665 tristate "Ricoh RP5C01"
667 If you say yes here you get support for the Ricoh RP5C01
668 timekeeping chip. It is used in some Amiga models (e.g. A3000
671 This driver can also be built as a module. If so, the module
672 will be called rtc-rp5c01.
675 tristate "EM Microelectronic V3020"
677 If you say yes here you will get support for the
678 EM Microelectronic v3020 RTC chip.
680 This driver can also be built as a module. If so, the module
681 will be called rtc-v3020.
683 config RTC_DRV_DS2404
684 tristate "Dallas DS2404"
686 If you say yes here you get support for the
687 Dallas DS2404 RTC chip.
689 This driver can also be built as a module. If so, the module
690 will be called rtc-ds2404.
692 config RTC_DRV_WM831X
693 tristate "Wolfson Microelectronics WM831x RTC"
694 depends on MFD_WM831X
696 If you say yes here you will get support for the RTC subsystem
697 of the Wolfson Microelectronics WM831X series PMICs.
699 This driver can also be built as a module. If so, the module
700 will be called "rtc-wm831x".
702 config RTC_DRV_WM8350
703 tristate "Wolfson Microelectronics WM8350 RTC"
704 depends on MFD_WM8350
706 If you say yes here you will get support for the RTC subsystem
707 of the Wolfson Microelectronics WM8350.
709 This driver can also be built as a module. If so, the module
710 will be called "rtc-wm8350".
713 tristate "SPEAR ST RTC"
714 depends on PLAT_SPEAR
717 If you say Y here you will get support for the RTC found on
720 config RTC_DRV_PCF50633
721 depends on MFD_PCF50633
722 tristate "NXP PCF50633 RTC"
724 If you say yes here you get support for the RTC subsystem of the
725 NXP PCF50633 used in embedded systems.
727 config RTC_DRV_AB3100
728 tristate "ST-Ericsson AB3100 RTC"
729 depends on AB3100_CORE
730 default y if AB3100_CORE
732 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
733 support. This chip contains a battery- and capacitor-backed RTC.
735 config RTC_DRV_AB8500
736 tristate "ST-Ericsson AB8500 RTC"
737 depends on AB8500_CORE
738 select RTC_INTF_DEV_UIE_EMUL
740 Select this to enable the ST-Ericsson AB8500 power management IC RTC
741 support. This chip contains a battery- and capacitor-backed RTC.
743 config RTC_DRV_NUC900
744 tristate "NUC910/NUC920 RTC driver"
745 depends on RTC_CLASS && ARCH_W90X900
747 If you say yes here you get support for the RTC subsystem of the
748 NUC910/NUC920 used in embedded systems.
750 comment "on-CPU RTC drivers"
752 config RTC_DRV_DAVINCI
753 tristate "TI DaVinci RTC"
754 depends on ARCH_DAVINCI_DM365
756 If you say yes here you get support for the RTC on the
757 DaVinci platforms (DM365).
759 This driver can also be built as a module. If so, the module
760 will be called rtc-davinci.
763 tristate "Freescale IMX DryIce Real Time Clock"
767 Support for Freescale IMX DryIce RTC
769 This driver can also be built as a module, if so, the module
770 will be called "rtc-imxdi".
774 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
776 Say "yes" here to support the real time clock on TI OMAP1 and
777 DA8xx/OMAP-L13x chips. This driver can also be built as a
778 module called rtc-omap.
783 This will include RTC support for Samsung SoCs. If
784 you want to include RTC support for any machine, kindly
785 select this in the respective mach-XXXX/Kconfig file.
788 tristate "Samsung S3C series SoC RTC"
789 depends on ARCH_S3C64XX || HAVE_S3C_RTC
791 RTC (Realtime Clock) driver for the clock inbuilt into the
792 Samsung S3C24XX series of SoCs. This can provide periodic
793 interrupt rates from 1Hz to 64Hz for user programs, and
796 The driver currently supports the common features on all the
797 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
800 This driver can also be build as a module. If so, the module
801 will be called rtc-s3c.
803 config RTC_DRV_EP93XX
804 tristate "Cirrus Logic EP93XX"
805 depends on ARCH_EP93XX
807 If you say yes here you get support for the
808 RTC embedded in the Cirrus Logic EP93XX processors.
810 This driver can also be built as a module. If so, the module
811 will be called rtc-ep93xx.
813 config RTC_DRV_SA1100
814 tristate "SA11x0/PXA2xx/PXA910"
815 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
817 If you say Y here you will get access to the real time clock
818 built into your SA11x0 or PXA2xx CPU.
820 To compile this driver as a module, choose M here: the
821 module will be called rtc-sa1100.
824 tristate "SuperH On-Chip RTC"
825 depends on RTC_CLASS && SUPERH && HAVE_CLK
827 Say Y here to enable support for the on-chip RTC found in
828 most SuperH processors.
830 To compile this driver as a module, choose M here: the
831 module will be called rtc-sh.
833 config RTC_DRV_VR41XX
834 tristate "NEC VR41XX"
835 depends on CPU_VR41XX
837 If you say Y here you will get access to the real time clock
838 built into your NEC VR41XX CPU.
840 To compile this driver as a module, choose M here: the
841 module will be called rtc-vr41xx.
844 tristate "ARM AMBA PL030 RTC"
847 If you say Y here you will get access to ARM AMBA
848 PrimeCell PL030 RTC found on certain ARM SOCs.
850 To compile this driver as a module, choose M here: the
851 module will be called rtc-pl030.
854 tristate "ARM AMBA PL031 RTC"
857 If you say Y here you will get access to ARM AMBA
858 PrimeCell PL031 RTC found on certain ARM SOCs.
860 To compile this driver as a module, choose M here: the
861 module will be called rtc-pl031.
863 config RTC_DRV_AT32AP700X
864 tristate "AT32AP700X series RTC"
865 depends on PLATFORM_AT32AP
867 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
868 AT32AP700x family processors.
870 config RTC_DRV_AT91RM9200
871 tristate "AT91RM9200 or some AT91SAM9 RTC"
874 Driver for the internal RTC (Realtime Clock) module found on
875 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
876 this is powered by the backup power supply.
878 config RTC_DRV_AT91SAM9
879 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
880 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
882 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
883 (Real Time Timer). These timers are powered by the backup power
884 supply (such as a small coin cell battery), but do not need to
887 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
888 dedicated RTC module and leave the RTT available for other uses.)
890 config RTC_DRV_AT91SAM9_RTT
894 prompt "RTT module Number" if ARCH_AT91SAM9263
895 depends on RTC_DRV_AT91SAM9
897 More than one RTT module is available. You can choose which
898 one will be used as an RTC. The default of zero is normally
899 OK to use, though some systems use that for non-RTC purposes.
901 config RTC_DRV_AT91SAM9_GPBR
903 range 0 3 if !ARCH_AT91SAM9263
904 range 0 15 if ARCH_AT91SAM9263
906 prompt "Backup Register Number"
907 depends on RTC_DRV_AT91SAM9
909 The RTC driver needs to use one of the General Purpose Backup
910 Registers (GPBRs) as well as the RTT. You can choose which one
911 will be used. The default of zero is normally OK to use, but
912 on some systems other software needs to use that register.
914 config RTC_DRV_AU1XXX
915 tristate "Au1xxx Counter0 RTC support"
916 depends on MIPS_ALCHEMY
918 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
919 counter) to be used as a RTC.
921 This driver can also be built as a module. If so, the module
922 will be called rtc-au1xxx.
925 tristate "Blackfin On-Chip RTC"
926 depends on BLACKFIN && !BF561
928 If you say yes here you will get support for the
929 Blackfin On-Chip Real Time Clock.
931 This driver can also be built as a module. If so, the module
932 will be called rtc-bfin.
934 config RTC_DRV_RS5C313
935 tristate "Ricoh RS5C313"
936 depends on SH_LANDISK
938 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
940 config RTC_DRV_GENERIC
941 tristate "Generic RTC support"
942 # Please consider writing a new RTC driver instead of using the generic
944 depends on PARISC || M68K || PPC || SUPERH32
946 Say Y or M here to enable RTC support on systems using the generic
947 RTC abstraction. If you do not know what you are doing, you should
951 tristate "PXA27x/PXA3xx"
954 If you say Y here you will get access to the real time clock
955 built into your PXA27x or PXA3xx CPU.
957 This RTC driver uses PXA RTC registers available since pxa27x
958 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
960 config RTC_DRV_VT8500
961 tristate "VIA/WonderMedia 85xx SoC RTC"
962 depends on ARCH_VT8500
964 If you say Y here you will get access to the real time clock
965 built into your VIA VT8500 SoC or its relatives.
969 bool "SUN4V Hypervisor RTC"
972 If you say Y here you will get support for the Hypervisor
973 based RTC on SUN4V systems.
975 config RTC_DRV_STARFIRE
979 If you say Y here you will get support for the RTC found on
982 config RTC_DRV_TX4939
983 tristate "TX4939 SoC"
984 depends on SOC_TX4939
986 Driver for the internal RTC (Realtime Clock) module found on
990 tristate "Marvell SoC RTC"
991 depends on ARCH_KIRKWOOD || ARCH_DOVE
993 If you say yes here you will get support for the in-chip RTC
994 that can be found in some of Marvell's SoC devices, such as
995 the Kirkwood 88F6281 and 88F6192.
997 This driver can also be built as a module. If so, the module
998 will be called rtc-mv.
1004 If you say yes here you will get support for the RTC on PS3.
1006 This driver can also be built as a module. If so, the module
1007 will be called rtc-ps3.
1009 config RTC_DRV_COH901331
1010 tristate "ST-Ericsson COH 901 331 RTC"
1011 depends on ARCH_U300
1013 If you say Y here you will get access to ST-Ericsson
1014 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1017 This driver can also be built as a module. If so, the module
1018 will be called "rtc-coh901331".
1022 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1025 If you say yes here you will get support for the onboard
1026 STMP3xxx/i.MX23/i.MX28 RTC.
1028 This driver can also be built as a module. If so, the module
1029 will be called rtc-stmp3xxx.
1035 If you say Y here you will get support for the RTC found on
1036 the PCAP2 ASIC used on some Motorola phones.
1038 config RTC_DRV_MC13XXX
1039 depends on MFD_MC13XXX
1040 tristate "Freescale MC13xxx RTC"
1042 This enables support for the RTCs found on Freescale's PMICs
1043 MC13783 and MC13892.
1045 config RTC_DRV_MPC5121
1046 tristate "Freescale MPC5121 built-in RTC"
1047 depends on PPC_MPC512x || PPC_MPC52xx
1049 If you say yes here you will get support for the
1050 built-in RTC on MPC5121 or on MPC5200.
1052 This driver can also be built as a module. If so, the module
1053 will be called rtc-mpc5121.
1055 config RTC_DRV_JZ4740
1056 tristate "Ingenic JZ4740 SoC"
1057 depends on RTC_CLASS
1058 depends on MACH_JZ4740
1060 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1063 This driver can also be buillt as a module. If so, the module
1064 will be called rtc-jz4740.
1066 config RTC_DRV_LPC32XX
1067 depends on ARCH_LPC32XX
1068 tristate "NXP LPC32XX RTC"
1070 This enables support for the NXP RTC in the LPC32XX
1072 This driver can also be buillt as a module. If so, the module
1073 will be called rtc-lpc32xx.
1075 config RTC_DRV_PM8XXX
1076 tristate "Qualcomm PMIC8XXX RTC"
1077 depends on MFD_PM8XXX
1079 If you say yes here you get support for the
1080 Qualcomm PMIC8XXX RTC.
1082 To compile this driver as a module, choose M here: the
1083 module will be called rtc-pm8xxx.
1085 config RTC_DRV_TEGRA
1086 tristate "NVIDIA Tegra Internal RTC driver"
1087 depends on RTC_CLASS && ARCH_TEGRA
1089 If you say yes here you get support for the
1090 Tegra 200 series internal RTC module.
1092 This drive can also be built as a module. If so, the module
1093 will be called rtc-tegra.
1096 tristate "Tilera hypervisor RTC support"
1099 Enable support for the Linux driver side of the Tilera
1100 hypervisor's real-time clock interface.
1103 tristate "PKUnity v3 RTC support"
1104 depends on ARCH_PUV3
1106 This enables support for the RTC in the PKUnity-v3 SoCs.
1108 This drive can also be built as a module. If so, the module
1109 will be called rtc-puv3.
1111 config RTC_DRV_LOONGSON1
1112 tristate "loongson1 RTC support"
1113 depends on MACH_LOONGSON1
1115 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1116 counter) to be used as a RTC.
1118 This driver can also be built as a module. If so, the module
1119 will be called rtc-ls1x.
1122 tristate "Freescale MXC Real Time Clock"
1124 depends on RTC_CLASS
1126 If you say yes here you get support for the Freescale MXC
1129 This driver can also be built as a module, if so, the module
1130 will be called "rtc-mxc".
1133 tristate "Freescale SNVS RTC support"
1134 depends on HAS_IOMEM
1137 If you say yes here you get support for the Freescale SNVS
1138 Low Power (LP) RTC module.
1140 This driver can also be built as a module, if so, the module
1141 will be called "rtc-snvs".