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"
24 If you say yes here, the system time (wall clock) will be set using
25 the value read from a specified RTC device. This is useful to avoid
26 unnecessary fsck runs at boot time, and to network better.
28 config RTC_HCTOSYS_DEVICE
29 string "RTC used to set the system time"
30 depends on RTC_HCTOSYS = y
33 The RTC device that will be used to (re)initialize the system
34 clock, usually rtc0. Initialization is done when the system
35 starts up, and when it resumes from a low power state. This
36 device should record time in UTC, since the kernel won't do
39 The driver for this RTC device must be loaded before late_initcall
40 functions run, so it must usually be statically linked.
42 This clock should be battery-backed, so that it reads the correct
43 time when the system boots from a power-off state. Otherwise, your
44 system will need an external clock source (like an NTP server).
46 If the clock you specify here is not battery backed, it may still
47 be useful to reinitialize system time when resuming from system
48 sleep states. Do not specify an RTC here unless it stays powered
49 during all this system's supported sleep states.
52 bool "RTC debug support"
54 Say yes here to enable debugging support in the RTC framework
55 and individual RTC drivers.
57 comment "RTC interfaces"
60 boolean "/sys/class/rtc/rtcN (sysfs)"
63 Say yes here if you want to use your RTCs using sysfs interfaces,
64 /sys/class/rtc/rtc0 through /sys/.../rtcN.
69 boolean "/proc/driver/rtc (procfs for rtcN)"
72 Say yes here if you want to use your system clock RTC through
73 the proc interface, /proc/driver/rtc.
74 Other RTCs will not be available through that API.
75 If there is no RTC for the system clock, then the first RTC(rtc0)
81 boolean "/dev/rtcN (character devices)"
83 Say yes here if you want to use your RTCs using the /dev
84 interfaces, which "udev" sets up as /dev/rtc0 through
87 You may want to set up a symbolic link so one of these
88 can be accessed as /dev/rtc, which is a name
89 expected by "hwclock" and some other programs. Recent
90 versions of "udev" are known to set up the symlink for you.
94 config RTC_INTF_DEV_UIE_EMUL
95 bool "RTC UIE emulation on dev interface"
96 depends on RTC_INTF_DEV
98 Provides an emulation for RTC_UIE if the underlying rtc chip
99 driver does not expose RTC_UIE ioctls. Those requests generate
100 once-per-second update interrupts, used for synchronization.
102 The emulation code will read the time from the hardware
103 clock several times per second, please enable this option
104 only if you know that you really need it.
107 tristate "Test driver/device"
109 If you say yes here you get support for the
110 RTC test driver. It's a software RTC which can be
111 used to test the RTC subsystem APIs. It gets
112 the time from the system clock.
113 You want this driver only if you are doing development
114 on the RTC subsystem. Please read the source code
117 This driver can also be built as a module. If so, the module
118 will be called rtc-test.
120 comment "I2C RTC drivers"
125 config RTC_DRV_88PM860X
126 tristate "Marvell 88PM860x"
127 depends on I2C && MFD_88PM860X
129 If you say yes here you get support for RTC function in Marvell
132 This driver can also be built as a module. If so, the module
133 will be called rtc-88pm860x.
135 config RTC_DRV_88PM80X
136 tristate "Marvell 88PM80x"
137 depends on I2C && MFD_88PM800
139 If you say yes here you get support for RTC function in Marvell
142 This driver can also be built as a module. If so, the module
143 will be called rtc-88pm80x.
145 config RTC_DRV_DS1307
146 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
148 If you say yes here you get support for various compatible RTC
149 chips (often with battery backup) connected with I2C. This driver
150 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
151 EPSON RX-8025 and probably other chips. In some cases the RTC
152 must already have been initialized (by manufacturing or a
155 The first seven registers on these chips hold an RTC, and other
156 registers may add features such as NVRAM, a trickle charger for
157 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
158 sysfs, but other chip features may not be available.
160 This driver can also be built as a module. If so, the module
161 will be called rtc-ds1307.
163 config RTC_DRV_DS1374
164 tristate "Dallas/Maxim DS1374"
167 If you say yes here you get support for Dallas Semiconductor
168 DS1374 real-time clock chips. If an interrupt is associated
169 with the device, the alarm functionality is supported.
171 This driver can also be built as a module. If so, the module
172 will be called rtc-ds1374.
174 config RTC_DRV_DS1672
175 tristate "Dallas/Maxim DS1672"
177 If you say yes here you get support for the
178 Dallas/Maxim DS1672 timekeeping chip.
180 This driver can also be built as a module. If so, the module
181 will be called rtc-ds1672.
183 config RTC_DRV_DS3232
184 tristate "Dallas/Maxim DS3232"
187 If you say yes here you get support for Dallas Semiconductor
188 DS3232 real-time clock chips. If an interrupt is associated
189 with the device, the alarm functionality is supported.
191 This driver can also be built as a module. If so, the module
192 will be called rtc-ds3232.
194 config RTC_DRV_MAX6900
195 tristate "Maxim MAX6900"
197 If you say yes here you will get support for the
198 Maxim MAX6900 I2C RTC chip.
200 This driver can also be built as a module. If so, the module
201 will be called rtc-max6900.
203 config RTC_DRV_MAX8907
204 tristate "Maxim MAX8907"
205 depends on MFD_MAX8907
207 If you say yes here you will get support for the
208 RTC of Maxim MAX8907 PMIC.
210 This driver can also be built as a module. If so, the module
211 will be called rtc-max8907.
213 config RTC_DRV_MAX8925
214 tristate "Maxim MAX8925"
215 depends on MFD_MAX8925
217 If you say yes here you will get support for the
218 RTC of Maxim MAX8925 PMIC.
220 This driver can also be built as a module. If so, the module
221 will be called rtc-max8925.
223 config RTC_DRV_MAX8998
224 tristate "Maxim MAX8998"
225 depends on MFD_MAX8998
227 If you say yes here you will get support for the
228 RTC of Maxim MAX8998 PMIC.
230 This driver can also be built as a module. If so, the module
231 will be called rtc-max8998.
233 config RTC_DRV_RS5C372
234 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
236 If you say yes here you get support for the
237 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
239 This driver can also be built as a module. If so, the module
240 will be called rtc-rs5c372.
242 config RTC_DRV_ISL1208
243 tristate "Intersil ISL1208"
245 If you say yes here you get support for the
246 Intersil ISL1208 RTC chip.
248 This driver can also be built as a module. If so, the module
249 will be called rtc-isl1208.
251 config RTC_DRV_ISL12022
252 tristate "Intersil ISL12022"
254 If you say yes here you get support for the
255 Intersil ISL12022 RTC chip.
257 This driver can also be built as a module. If so, the module
258 will be called rtc-isl12022.
261 tristate "Xicor/Intersil X1205"
263 If you say yes here you get support for the
264 Xicor/Intersil X1205 RTC chip.
266 This driver can also be built as a module. If so, the module
267 will be called rtc-x1205.
269 config RTC_DRV_PCF8563
270 tristate "Philips PCF8563/Epson RTC8564"
272 If you say yes here you get support for the
273 Philips PCF8563 RTC chip. The Epson RTC8564
276 This driver can also be built as a module. If so, the module
277 will be called rtc-pcf8563.
279 config RTC_DRV_PCF8583
280 tristate "Philips PCF8583"
282 If you say yes here you get support for the Philips PCF8583
283 RTC chip found on Acorn RiscPCs. This driver supports the
284 platform specific method of retrieving the current year from
285 the RTC's SRAM. It will work on other platforms with the same
286 chip, but the year will probably have to be tweaked.
288 This driver can also be built as a module. If so, the module
289 will be called rtc-pcf8583.
291 config RTC_DRV_M41T80
292 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
294 If you say Y here you will get support for the ST M41T60
295 and M41T80 RTC chips series. Currently, the following chips are
296 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
297 M41ST85, and M41ST87.
299 This driver can also be built as a module. If so, the module
300 will be called rtc-m41t80.
302 config RTC_DRV_M41T80_WDT
303 bool "ST M41T65/M41T80 series RTC watchdog timer"
304 depends on RTC_DRV_M41T80
306 If you say Y here you will get support for the
307 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
310 tristate "TI BQ32000"
312 If you say Y here you will get support for the TI
313 BQ32000 I2C RTC chip.
315 This driver can also be built as a module. If so, the module
316 will be called rtc-bq32k.
318 config RTC_DRV_DM355EVM
319 tristate "TI DaVinci DM355 EVM RTC"
320 depends on MFD_DM355EVM_MSP
322 Supports the RTC firmware in the MSP430 on the DM355 EVM.
324 config RTC_DRV_TWL92330
325 boolean "TI TWL92330/Menelaus"
328 If you say yes here you get support for the RTC on the
329 TWL92330 "Menelaus" power management chip, used with OMAP2
330 platforms. The support is integrated with the rest of
331 the Menelaus driver; it's not separate module.
333 config RTC_DRV_TWL4030
334 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
335 depends on TWL4030_CORE
337 If you say yes here you get support for the RTC on the
338 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
340 This driver can also be built as a module. If so, the module
341 will be called rtc-twl.
343 config RTC_DRV_TPS65910
344 tristate "TI TPS65910 RTC driver"
345 depends on RTC_CLASS && MFD_TPS65910
347 If you say yes here you get support for the RTC on the
350 This driver can also be built as a module. If so, the module
351 will be called rtc-tps65910.
353 config RTC_DRV_S35390A
354 tristate "Seiko Instruments S-35390A"
357 If you say yes here you will get support for the Seiko
358 Instruments S-35390A.
360 This driver can also be built as a module. If so the module
361 will be called rtc-s35390a.
363 config RTC_DRV_FM3130
364 tristate "Ramtron FM3130"
366 If you say Y here you will get support for the
367 Ramtron FM3130 RTC chips.
368 Ramtron FM3130 is a chip with two separate devices inside,
369 RTC clock and FRAM. This driver provides only RTC functionality.
371 This driver can also be built as a module. If so the module
372 will be called rtc-fm3130.
374 config RTC_DRV_RX8581
375 tristate "Epson RX-8581"
377 If you say yes here you will get support for the Epson RX-8581.
379 This driver can also be built as a module. If so the module
380 will be called rtc-rx8581.
382 config RTC_DRV_RX8025
383 tristate "Epson RX-8025SA/NB"
385 If you say yes here you get support for the Epson
386 RX-8025SA/NB RTC chips.
388 This driver can also be built as a module. If so, the module
389 will be called rtc-rx8025.
391 config RTC_DRV_EM3027
392 tristate "EM Microelectronic EM3027"
394 If you say yes here you get support for the EM
395 Microelectronic EM3027 RTC chips.
397 This driver can also be built as a module. If so, the module
398 will be called rtc-em3027.
400 config RTC_DRV_RV3029C2
401 tristate "Micro Crystal RTC"
403 If you say yes here you get support for the Micro Crystal
406 This driver can also be built as a module. If so, the module
407 will be called rtc-rv3029c2.
411 comment "SPI RTC drivers"
415 config RTC_DRV_M41T93
418 If you say yes here you will get support for the
419 ST M41T93 SPI RTC chip.
421 This driver can also be built as a module. If so, the module
422 will be called rtc-m41t93.
424 config RTC_DRV_M41T94
427 If you say yes here you will get support for the
428 ST M41T94 SPI RTC chip.
430 This driver can also be built as a module. If so, the module
431 will be called rtc-m41t94.
433 config RTC_DRV_DS1305
434 tristate "Dallas/Maxim DS1305/DS1306"
436 Select this driver to get support for the Dallas/Maxim DS1305
437 and DS1306 real time clock chips. These support a trickle
438 charger, alarms, and NVRAM in addition to the clock.
440 This driver can also be built as a module. If so, the module
441 will be called rtc-ds1305.
443 config RTC_DRV_DS1390
444 tristate "Dallas/Maxim DS1390/93/94"
446 If you say yes here you get support for the
447 Dallas/Maxim DS1390/93/94 chips.
449 This driver only supports the RTC feature, and not other chip
450 features such as alarms and trickle charging.
452 This driver can also be built as a module. If so, the module
453 will be called rtc-ds1390.
455 config RTC_DRV_MAX6902
456 tristate "Maxim MAX6902"
458 If you say yes here you will get support for the
459 Maxim MAX6902 SPI RTC chip.
461 This driver can also be built as a module. If so, the module
462 will be called rtc-max6902.
465 tristate "Epson RTC-9701JE"
467 If you say yes here you will get support for the
468 Epson RTC-9701JE SPI RTC chip.
470 This driver can also be built as a module. If so, the module
471 will be called rtc-r9701.
473 config RTC_DRV_RS5C348
474 tristate "Ricoh RS5C348A/B"
476 If you say yes here you get support for the
477 Ricoh RS5C348A and RS5C348B RTC chips.
479 This driver can also be built as a module. If so, the module
480 will be called rtc-rs5c348.
482 config RTC_DRV_DS3234
483 tristate "Maxim/Dallas DS3234"
485 If you say yes here you get support for the
486 Maxim/Dallas DS3234 SPI RTC chip.
488 This driver can also be built as a module. If so, the module
489 will be called rtc-ds3234.
491 config RTC_DRV_PCF2123
492 tristate "NXP PCF2123"
494 If you say yes here you get support for the NXP PCF2123
497 This driver can also be built as a module. If so, the module
498 will be called rtc-pcf2123.
502 comment "Platform RTC drivers"
504 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
505 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
506 # global rtc_lock ... it's not yet just another platform_device.
509 tristate "PC-style 'CMOS'"
510 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
513 Say "yes" here to get direct support for the real time clock
514 found in every PC or ACPI-based system, and some other boards.
515 Specifically the original MC146818, compatibles like those in
516 PC south bridges, the DS12887 or M48T86, some multifunction
517 or LPC bus chips, and so on.
519 Your system will need to define the platform device used by
520 this driver, otherwise it won't be accessible. This means
521 you can safely enable this driver if you don't know whether
522 or not your board has this kind of hardware.
524 This driver can also be built as a module. If so, the module
525 will be called rtc-cmos.
528 tristate "Virtual RTC for Intel MID platforms"
529 depends on X86_INTEL_MID
530 default y if X86_INTEL_MID
533 Say "yes" here to get direct support for the real time clock
534 found on Moorestown platforms. The VRTC is a emulated RTC that
535 derives its clock source from a real RTC in the PMIC. The MC146818
536 style programming interface is mostly conserved, but any
537 updates are done via IPC calls to the system controller FW.
539 config RTC_DRV_DS1216
540 tristate "Dallas DS1216"
543 If you say yes here you get support for the Dallas DS1216 RTC chips.
545 config RTC_DRV_DS1286
546 tristate "Dallas DS1286"
548 If you say yes here you get support for the Dallas DS1286 RTC chips.
550 config RTC_DRV_DS1302
551 tristate "Dallas DS1302"
552 depends on SH_SECUREEDGE5410
554 If you say yes here you get support for the Dallas DS1302 RTC chips.
556 config RTC_DRV_DS1511
557 tristate "Dallas DS1511"
559 If you say yes here you get support for the
560 Dallas DS1511 timekeeping/watchdog chip.
562 This driver can also be built as a module. If so, the module
563 will be called rtc-ds1511.
565 config RTC_DRV_DS1553
566 tristate "Maxim/Dallas DS1553"
568 If you say yes here you get support for the
569 Maxim/Dallas DS1553 timekeeping chip.
571 This driver can also be built as a module. If so, the module
572 will be called rtc-ds1553.
574 config RTC_DRV_DS1742
575 tristate "Maxim/Dallas DS1742/1743"
577 If you say yes here you get support for the
578 Maxim/Dallas DS1742/1743 timekeeping chip.
580 This driver can also be built as a module. If so, the module
581 will be called rtc-ds1742.
583 config RTC_DRV_DA9052
584 tristate "Dialog DA9052/DA9053 RTC"
585 depends on PMIC_DA9052
587 Say y here to support the RTC driver for Dialog Semiconductor
588 DA9052-BC and DA9053-AA/Bx PMICs.
594 If you say yes here you will get support for the EFI
597 This driver can also be built as a module. If so, the module
598 will be called rtc-efi.
600 config RTC_DRV_STK17TA8
601 tristate "Simtek STK17TA8"
603 If you say yes here you get support for the
604 Simtek STK17TA8 timekeeping chip.
606 This driver can also be built as a module. If so, the module
607 will be called rtc-stk17ta8.
609 config RTC_DRV_M48T86
610 tristate "ST M48T86/Dallas DS12887"
612 If you say Y here you will get support for the
613 ST M48T86 and Dallas DS12887 RTC chips.
615 This driver can also be built as a module. If so, the module
616 will be called rtc-m48t86.
618 config RTC_DRV_M48T35
621 If you say Y here you will get support for the
624 This driver can also be built as a module, if so, the module
625 will be called "rtc-m48t35".
627 config RTC_DRV_M48T59
628 tristate "ST M48T59/M48T08/M48T02"
630 If you say Y here you will get support for the
631 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
633 These chips are usually found in Sun SPARC and UltraSPARC
636 This driver can also be built as a module, if so, the module
637 will be called "rtc-m48t59".
639 config RTC_DRV_MSM6242
640 tristate "Oki MSM6242"
642 If you say yes here you get support for the Oki MSM6242
643 timekeeping chip. It is used in some Amiga models (e.g. A2000).
645 This driver can also be built as a module. If so, the module
646 will be called rtc-msm6242.
648 config RTC_DRV_BQ4802
651 If you say Y here you will get support for the TI
654 This driver can also be built as a module. If so, the module
655 will be called rtc-bq4802.
657 config RTC_DRV_RP5C01
658 tristate "Ricoh RP5C01"
660 If you say yes here you get support for the Ricoh RP5C01
661 timekeeping chip. It is used in some Amiga models (e.g. A3000
664 This driver can also be built as a module. If so, the module
665 will be called rtc-rp5c01.
668 tristate "EM Microelectronic V3020"
670 If you say yes here you will get support for the
671 EM Microelectronic v3020 RTC chip.
673 This driver can also be built as a module. If so, the module
674 will be called rtc-v3020.
676 config RTC_DRV_DS2404
677 tristate "Dallas DS2404"
679 If you say yes here you get support for the
680 Dallas DS2404 RTC chip.
682 This driver can also be built as a module. If so, the module
683 will be called rtc-ds2404.
685 config RTC_DRV_WM831X
686 tristate "Wolfson Microelectronics WM831x RTC"
687 depends on MFD_WM831X
689 If you say yes here you will get support for the RTC subsystem
690 of the Wolfson Microelectronics WM831X series PMICs.
692 This driver can also be built as a module. If so, the module
693 will be called "rtc-wm831x".
695 config RTC_DRV_WM8350
696 tristate "Wolfson Microelectronics WM8350 RTC"
697 depends on MFD_WM8350
699 If you say yes here you will get support for the RTC subsystem
700 of the Wolfson Microelectronics WM8350.
702 This driver can also be built as a module. If so, the module
703 will be called "rtc-wm8350".
706 tristate "SPEAR ST RTC"
707 depends on PLAT_SPEAR
710 If you say Y here you will get support for the RTC found on
713 config RTC_DRV_PCF50633
714 depends on MFD_PCF50633
715 tristate "NXP PCF50633 RTC"
717 If you say yes here you get support for the RTC subsystem of the
718 NXP PCF50633 used in embedded systems.
720 config RTC_DRV_AB3100
721 tristate "ST-Ericsson AB3100 RTC"
722 depends on AB3100_CORE
723 default y if AB3100_CORE
725 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
726 support. This chip contains a battery- and capacitor-backed RTC.
728 config RTC_DRV_AB8500
729 tristate "ST-Ericsson AB8500 RTC"
730 depends on AB8500_CORE
731 select RTC_INTF_DEV_UIE_EMUL
733 Select this to enable the ST-Ericsson AB8500 power management IC RTC
734 support. This chip contains a battery- and capacitor-backed RTC.
736 config RTC_DRV_NUC900
737 tristate "NUC910/NUC920 RTC driver"
738 depends on ARCH_W90X900
740 If you say yes here you get support for the RTC subsystem of the
741 NUC910/NUC920 used in embedded systems.
743 comment "on-CPU RTC drivers"
745 config RTC_DRV_DAVINCI
746 tristate "TI DaVinci RTC"
747 depends on ARCH_DAVINCI_DM365
749 If you say yes here you get support for the RTC on the
750 DaVinci platforms (DM365).
752 This driver can also be built as a module. If so, the module
753 will be called rtc-davinci.
756 tristate "Freescale IMX DryIce Real Time Clock"
759 Support for Freescale IMX DryIce RTC
761 This driver can also be built as a module, if so, the module
762 will be called "rtc-imxdi".
766 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
768 Say "yes" here to support the real time clock on TI OMAP1 and
769 DA8xx/OMAP-L13x chips. This driver can also be built as a
770 module called rtc-omap.
775 This will include RTC support for Samsung SoCs. If
776 you want to include RTC support for any machine, kindly
777 select this in the respective mach-XXXX/Kconfig file.
780 tristate "Samsung S3C series SoC RTC"
781 depends on ARCH_S3C64XX || HAVE_S3C_RTC
783 RTC (Realtime Clock) driver for the clock inbuilt into the
784 Samsung S3C24XX series of SoCs. This can provide periodic
785 interrupt rates from 1Hz to 64Hz for user programs, and
788 The driver currently supports the common features on all the
789 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
792 This driver can also be build as a module. If so, the module
793 will be called rtc-s3c.
795 config RTC_DRV_EP93XX
796 tristate "Cirrus Logic EP93XX"
797 depends on ARCH_EP93XX
799 If you say yes here you get support for the
800 RTC embedded in the Cirrus Logic EP93XX processors.
802 This driver can also be built as a module. If so, the module
803 will be called rtc-ep93xx.
805 config RTC_DRV_SA1100
806 tristate "SA11x0/PXA2xx/PXA910"
807 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
809 If you say Y here you will get access to the real time clock
810 built into your SA11x0 or PXA2xx CPU.
812 To compile this driver as a module, choose M here: the
813 module will be called rtc-sa1100.
816 tristate "SuperH On-Chip RTC"
817 depends on SUPERH && HAVE_CLK
819 Say Y here to enable support for the on-chip RTC found in
820 most SuperH processors.
822 To compile this driver as a module, choose M here: the
823 module will be called rtc-sh.
825 config RTC_DRV_VR41XX
826 tristate "NEC VR41XX"
827 depends on CPU_VR41XX
829 If you say Y here you will get access to the real time clock
830 built into your NEC VR41XX CPU.
832 To compile this driver as a module, choose M here: the
833 module will be called rtc-vr41xx.
836 tristate "ARM AMBA PL030 RTC"
839 If you say Y here you will get access to ARM AMBA
840 PrimeCell PL030 RTC found on certain ARM SOCs.
842 To compile this driver as a module, choose M here: the
843 module will be called rtc-pl030.
846 tristate "ARM AMBA PL031 RTC"
849 If you say Y here you will get access to ARM AMBA
850 PrimeCell PL031 RTC found on certain ARM SOCs.
852 To compile this driver as a module, choose M here: the
853 module will be called rtc-pl031.
855 config RTC_DRV_AT32AP700X
856 tristate "AT32AP700X series RTC"
857 depends on PLATFORM_AT32AP
859 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
860 AT32AP700x family processors.
862 config RTC_DRV_AT91RM9200
863 tristate "AT91RM9200 or some AT91SAM9 RTC"
866 Driver for the internal RTC (Realtime Clock) module found on
867 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
868 this is powered by the backup power supply.
870 config RTC_DRV_AT91SAM9
871 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
872 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
874 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
875 (Real Time Timer). These timers are powered by the backup power
876 supply (such as a small coin cell battery), but do not need to
879 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
880 dedicated RTC module and leave the RTT available for other uses.)
882 config RTC_DRV_AT91SAM9_RTT
886 prompt "RTT module Number" if ARCH_AT91SAM9263
887 depends on RTC_DRV_AT91SAM9
889 More than one RTT module is available. You can choose which
890 one will be used as an RTC. The default of zero is normally
891 OK to use, though some systems use that for non-RTC purposes.
893 config RTC_DRV_AT91SAM9_GPBR
895 range 0 3 if !ARCH_AT91SAM9263
896 range 0 15 if ARCH_AT91SAM9263
898 prompt "Backup Register Number"
899 depends on RTC_DRV_AT91SAM9
901 The RTC driver needs to use one of the General Purpose Backup
902 Registers (GPBRs) as well as the RTT. You can choose which one
903 will be used. The default of zero is normally OK to use, but
904 on some systems other software needs to use that register.
906 config RTC_DRV_AU1XXX
907 tristate "Au1xxx Counter0 RTC support"
908 depends on MIPS_ALCHEMY
910 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
911 counter) to be used as a RTC.
913 This driver can also be built as a module. If so, the module
914 will be called rtc-au1xxx.
917 tristate "Blackfin On-Chip RTC"
918 depends on BLACKFIN && !BF561
920 If you say yes here you will get support for the
921 Blackfin On-Chip Real Time Clock.
923 This driver can also be built as a module. If so, the module
924 will be called rtc-bfin.
926 config RTC_DRV_RS5C313
927 tristate "Ricoh RS5C313"
928 depends on SH_LANDISK
930 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
932 config RTC_DRV_GENERIC
933 tristate "Generic RTC support"
934 # Please consider writing a new RTC driver instead of using the generic
936 depends on PARISC || M68K || PPC || SUPERH32
938 Say Y or M here to enable RTC support on systems using the generic
939 RTC abstraction. If you do not know what you are doing, you should
943 tristate "PXA27x/PXA3xx"
946 If you say Y here you will get access to the real time clock
947 built into your PXA27x or PXA3xx CPU.
949 This RTC driver uses PXA RTC registers available since pxa27x
950 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
952 config RTC_DRV_VT8500
953 tristate "VIA/WonderMedia 85xx SoC RTC"
954 depends on ARCH_VT8500
956 If you say Y here you will get access to the real time clock
957 built into your VIA VT8500 SoC or its relatives.
961 bool "SUN4V Hypervisor RTC"
964 If you say Y here you will get support for the Hypervisor
965 based RTC on SUN4V systems.
967 config RTC_DRV_STARFIRE
971 If you say Y here you will get support for the RTC found on
974 config RTC_DRV_TX4939
975 tristate "TX4939 SoC"
976 depends on SOC_TX4939
978 Driver for the internal RTC (Realtime Clock) module found on
982 tristate "Marvell SoC RTC"
983 depends on ARCH_KIRKWOOD || ARCH_DOVE
985 If you say yes here you will get support for the in-chip RTC
986 that can be found in some of Marvell's SoC devices, such as
987 the Kirkwood 88F6281 and 88F6192.
989 This driver can also be built as a module. If so, the module
990 will be called rtc-mv.
996 If you say yes here you will get support for the RTC on PS3.
998 This driver can also be built as a module. If so, the module
999 will be called rtc-ps3.
1001 config RTC_DRV_COH901331
1002 tristate "ST-Ericsson COH 901 331 RTC"
1003 depends on ARCH_U300
1005 If you say Y here you will get access to ST-Ericsson
1006 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1009 This driver can also be built as a module. If so, the module
1010 will be called "rtc-coh901331".
1014 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1017 If you say yes here you will get support for the onboard
1018 STMP3xxx/i.MX23/i.MX28 RTC.
1020 This driver can also be built as a module. If so, the module
1021 will be called rtc-stmp3xxx.
1027 If you say Y here you will get support for the RTC found on
1028 the PCAP2 ASIC used on some Motorola phones.
1030 config RTC_DRV_MC13XXX
1031 depends on MFD_MC13XXX
1032 tristate "Freescale MC13xxx RTC"
1034 This enables support for the RTCs found on Freescale's PMICs
1035 MC13783 and MC13892.
1037 config RTC_DRV_MPC5121
1038 tristate "Freescale MPC5121 built-in RTC"
1039 depends on PPC_MPC512x || PPC_MPC52xx
1041 If you say yes here you will get support for the
1042 built-in RTC on MPC5121 or on MPC5200.
1044 This driver can also be built as a module. If so, the module
1045 will be called rtc-mpc5121.
1047 config RTC_DRV_JZ4740
1048 tristate "Ingenic JZ4740 SoC"
1049 depends on MACH_JZ4740
1051 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1054 This driver can also be buillt as a module. If so, the module
1055 will be called rtc-jz4740.
1057 config RTC_DRV_LPC32XX
1058 depends on ARCH_LPC32XX
1059 tristate "NXP LPC32XX RTC"
1061 This enables support for the NXP RTC in the LPC32XX
1063 This driver can also be buillt as a module. If so, the module
1064 will be called rtc-lpc32xx.
1066 config RTC_DRV_PM8XXX
1067 tristate "Qualcomm PMIC8XXX RTC"
1068 depends on MFD_PM8XXX
1070 If you say yes here you get support for the
1071 Qualcomm PMIC8XXX RTC.
1073 To compile this driver as a module, choose M here: the
1074 module will be called rtc-pm8xxx.
1076 config RTC_DRV_TEGRA
1077 tristate "NVIDIA Tegra Internal RTC driver"
1078 depends on ARCH_TEGRA
1080 If you say yes here you get support for the
1081 Tegra 200 series internal RTC module.
1083 This drive can also be built as a module. If so, the module
1084 will be called rtc-tegra.
1087 tristate "Tilera hypervisor RTC support"
1090 Enable support for the Linux driver side of the Tilera
1091 hypervisor's real-time clock interface.
1094 tristate "PKUnity v3 RTC support"
1095 depends on ARCH_PUV3
1097 This enables support for the RTC in the PKUnity-v3 SoCs.
1099 This drive can also be built as a module. If so, the module
1100 will be called rtc-puv3.
1102 config RTC_DRV_LOONGSON1
1103 tristate "loongson1 RTC support"
1104 depends on MACH_LOONGSON1
1106 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1107 counter) to be used as a RTC.
1109 This driver can also be built as a module. If so, the module
1110 will be called rtc-ls1x.
1113 tristate "Freescale MXC Real Time Clock"
1116 If you say yes here you get support for the Freescale MXC
1119 This driver can also be built as a module, if so, the module
1120 will be called "rtc-mxc".
1123 tristate "Freescale SNVS RTC support"
1124 depends on HAS_IOMEM
1127 If you say yes here you get support for the Freescale SNVS
1128 Low Power (LP) RTC module.
1130 This driver can also be built as a module, if so, the module
1131 will be called "rtc-snvs".