2 # RTC class/drivers configuration
9 tristate "Real Time Clock"
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.
18 This driver can also be built as a module. If so, the module
19 will be called rtc-core.
24 bool "Set system time from RTC on startup and resume"
25 depends on RTC_CLASS = y
28 If you say yes here, the system time (wall clock) will be set using
29 the value read from a specified RTC device. This is useful to avoid
30 unnecessary fsck runs at boot time, and to network better.
32 config RTC_HCTOSYS_DEVICE
33 string "RTC used to set the system time"
34 depends on RTC_HCTOSYS = y
37 The RTC device that will be used to (re)initialize the system
38 clock, usually rtc0. Initialization is done when the system
39 starts up, and when it resumes from a low power state. This
40 device should record time in UTC, since the kernel won't do
43 The driver for this RTC device must be loaded before late_initcall
44 functions run, so it must usually be statically linked.
46 This clock should be battery-backed, so that it reads the correct
47 time when the system boots from a power-off state. Otherwise, your
48 system will need an external clock source (like an NTP server).
50 If the clock you specify here is not battery backed, it may still
51 be useful to reinitialize system time when resuming from system
52 sleep states. Do not specify an RTC here unless it stays powered
53 during all this system's supported sleep states.
56 bool "RTC debug support"
57 depends on RTC_CLASS = y
59 Say yes here to enable debugging support in the RTC framework
60 and individual RTC drivers.
62 comment "RTC interfaces"
65 boolean "/sys/class/rtc/rtcN (sysfs)"
69 Say yes here if you want to use your RTCs using sysfs interfaces,
70 /sys/class/rtc/rtc0 through /sys/.../rtcN.
75 boolean "/proc/driver/rtc (procfs for rtc0)"
79 Say yes here if you want to use your first RTC through the proc
80 interface, /proc/driver/rtc. Other RTCs will not be available
86 boolean "/dev/rtcN (character devices)"
89 Say yes here if you want to use your RTCs using the /dev
90 interfaces, which "udev" sets up as /dev/rtc0 through
93 You may want to set up a symbolic link so one of these
94 can be accessed as /dev/rtc, which is a name
95 expected by "hwclock" and some other programs. Recent
96 versions of "udev" are known to set up the symlink for you.
100 config RTC_INTF_DEV_UIE_EMUL
101 bool "RTC UIE emulation on dev interface"
102 depends on RTC_INTF_DEV
104 Provides an emulation for RTC_UIE if the underlying rtc chip
105 driver does not expose RTC_UIE ioctls. Those requests generate
106 once-per-second update interrupts, used for synchronization.
108 The emulation code will read the time from the hardware
109 clock several times per second, please enable this option
110 only if you know that you really need it.
112 config RTC_INTF_ALARM
113 bool "Android alarm driver"
117 Provides non-wakeup and rtc backed wakeup alarms based on rtc or
118 elapsed realtime, and a non-wakeup alarm on the monotonic clock.
119 Also provides an interface to set the wall time which must be used
120 for elapsed realtime to work.
122 config RTC_INTF_ALARM_DEV
123 bool "Android alarm device"
124 depends on RTC_INTF_ALARM
127 Exports the alarm interface to user-space.
129 config RTC_INTF_CPCAP_SECCLKD
130 bool "Secure Clock Daemon support"
131 depends on RTC_DRV_CPCAP
134 CPCAP RTC driver support for secure clock daemon by maintaining a
135 counter to keep track of changes in RTC time.
138 tristate "Test driver/device"
140 If you say yes here you get support for the
141 RTC test driver. It's a software RTC which can be
142 used to test the RTC subsystem APIs. It gets
143 the time from the system clock.
144 You want this driver only if you are doing development
145 on the RTC subsystem. Please read the source code
148 This driver can also be built as a module. If so, the module
149 will be called rtc-test.
151 comment "I2C RTC drivers"
157 tristate "RK2818 or RK29 extern HYM8563 RTC"
158 depends on I2C_RK2818 || I2C_RK29
160 If you say yes here you will get support for the
161 HYM8563 I2C RTC chip.
162 This driver can also be built as a module. If so, the module
163 will be called rtc-HYM8563.
167 depends on I2C_RK2818 || I2C_RK29
169 If you say Y here you will get support for the ST M41T66.
171 config RTC_DRV_DS1307
172 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
174 If you say yes here you get support for various compatible RTC
175 chips (often with battery backup) connected with I2C. This driver
176 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
177 EPSON RX-8025 and probably other chips. In some cases the RTC
178 must already have been initialized (by manufacturing or a
181 The first seven registers on these chips hold an RTC, and other
182 registers may add features such as NVRAM, a trickle charger for
183 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
184 sysfs, but other chip features may not be available.
186 This driver can also be built as a module. If so, the module
187 will be called rtc-ds1307.
189 config RTC_DRV_DS1374
190 tristate "Dallas/Maxim DS1374"
191 depends on RTC_CLASS && I2C
193 If you say yes here you get support for Dallas Semiconductor
194 DS1374 real-time clock chips. If an interrupt is associated
195 with the device, the alarm functionality is supported.
197 This driver can also be built as a module. If so, the module
198 will be called rtc-ds1374.
200 config RTC_DRV_DS1672
201 tristate "Dallas/Maxim DS1672"
203 If you say yes here you get support for the
204 Dallas/Maxim DS1672 timekeeping chip.
206 This driver can also be built as a module. If so, the module
207 will be called rtc-ds1672.
209 config RTC_DRV_DS3232
210 tristate "Dallas/Maxim DS3232"
211 depends on RTC_CLASS && I2C
213 If you say yes here you get support for Dallas Semiconductor
214 DS3232 real-time clock chips.
216 This driver can also be built as a module. If so, the module
217 will be called rtc-ds3232.
219 config RTC_DRV_MAX6900
220 tristate "Maxim MAX6900"
222 If you say yes here you will get support for the
223 Maxim MAX6900 I2C RTC chip.
225 This driver can also be built as a module. If so, the module
226 will be called rtc-max6900.
228 config RTC_DRV_MAX8925
229 tristate "Maxim MAX8925"
230 depends on MFD_MAX8925
232 If you say yes here you will get support for the
233 RTC of Maxim MAX8925 PMIC.
235 This driver can also be built as a module. If so, the module
236 will be called rtc-max8925.
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_TPS6586X
330 tristate "TI TPS6586X RTC"
334 This driver supports TPS6586X RTC
336 config RTC_DRV_TWL92330
337 boolean "TI TWL92330/Menelaus"
340 If you say yes here you get support for the RTC on the
341 TWL92330 "Menelaus" power management chip, used with OMAP2
342 platforms. The support is integrated with the rest of
343 the Menelaus driver; it's not separate module.
345 config RTC_DRV_TWL4030
346 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
347 depends on RTC_CLASS && TWL4030_CORE
349 If you say yes here you get support for the RTC on the
350 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
352 This driver can also be built as a module. If so, the module
353 will be called rtc-twl.
355 config RTC_DRV_TPS65910
356 boolean "TI TPS65910"
357 depends on RTC_CLASS && TPS65910_CORE
359 If you say yes here you get support for the RTC on the
360 TPS65910 family chips, used mostly with OMAP3/AM35xx platforms.
362 config RTC_DRV_S35390A
363 tristate "Seiko Instruments S-35390A"
366 If you say yes here you will get support for the Seiko
367 Instruments S-35390A.
369 This driver can also be built as a module. If so the module
370 will be called rtc-s35390a.
372 config RTC_DRV_S35392A
373 tristate "Seiko Instruments S-35392A"
376 If you say yes here you will get support for the Seiko
377 Instruments S-35392A.
379 This driver can also be built as a module. If so the module
380 will be called rtc-s35392a.
382 config RTC_DRV_FM3130
383 tristate "Ramtron FM3130"
385 If you say Y here you will get support for the
386 Ramtron FM3130 RTC chips.
387 Ramtron FM3130 is a chip with two separate devices inside,
388 RTC clock and FRAM. This driver provides only RTC functionality.
390 This driver can also be built as a module. If so the module
391 will be called rtc-fm3130.
393 config RTC_DRV_RX8581
394 tristate "Epson RX-8581"
396 If you say yes here you will get support for the Epson RX-8581.
398 This driver can also be built as a module. If so the module
399 will be called rtc-rx8581.
401 config RTC_DRV_RX8025
402 tristate "Epson RX-8025SA/NB"
404 If you say yes here you get support for the Epson
405 RX-8025SA/NB RTC chips.
407 This driver can also be built as a module. If so, the module
408 will be called rtc-rx8025.
412 comment "SPI RTC drivers"
416 config RTC_DRV_M41T94
419 If you say yes here you will get support for the
420 ST M41T94 SPI RTC chip.
422 This driver can also be built as a module. If so, the module
423 will be called rtc-m41t94.
425 config RTC_DRV_DS1305
426 tristate "Dallas/Maxim DS1305/DS1306"
428 Select this driver to get support for the Dallas/Maxim DS1305
429 and DS1306 real time clock chips. These support a trickle
430 charger, alarms, and NVRAM in addition to the clock.
432 This driver can also be built as a module. If so, the module
433 will be called rtc-ds1305.
435 config RTC_DRV_DS1390
436 tristate "Dallas/Maxim DS1390/93/94"
438 If you say yes here you get support for the
439 Dallas/Maxim DS1390/93/94 chips.
441 This driver only supports the RTC feature, and not other chip
442 features such as alarms and trickle charging.
444 This driver can also be built as a module. If so, the module
445 will be called rtc-ds1390.
447 config RTC_DRV_MAX6902
448 tristate "Maxim MAX6902"
450 If you say yes here you will get support for the
451 Maxim MAX6902 SPI RTC chip.
453 This driver can also be built as a module. If so, the module
454 will be called rtc-max6902.
457 tristate "Epson RTC-9701JE"
459 If you say yes here you will get support for the
460 Epson RTC-9701JE SPI RTC chip.
462 This driver can also be built as a module. If so, the module
463 will be called rtc-r9701.
465 config RTC_DRV_RS5C348
466 tristate "Ricoh RS5C348A/B"
468 If you say yes here you get support for the
469 Ricoh RS5C348A and RS5C348B RTC chips.
471 This driver can also be built as a module. If so, the module
472 will be called rtc-rs5c348.
474 config RTC_DRV_DS3234
475 tristate "Maxim/Dallas DS3234"
477 If you say yes here you get support for the
478 Maxim/Dallas DS3234 SPI RTC chip.
480 This driver can also be built as a module. If so, the module
481 will be called rtc-ds3234.
483 config RTC_DRV_PCF2123
484 tristate "NXP PCF2123"
486 If you say yes here you get support for the NXP PCF2123
489 This driver can also be built as a module. If so, the module
490 will be called rtc-pcf2123.
494 comment "Platform RTC drivers"
496 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
497 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
498 # global rtc_lock ... it's not yet just another platform_device.
501 tristate "PC-style 'CMOS'"
502 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
505 Say "yes" here to get direct support for the real time clock
506 found in every PC or ACPI-based system, and some other boards.
507 Specifically the original MC146818, compatibles like those in
508 PC south bridges, the DS12887 or M48T86, some multifunction
509 or LPC bus chips, and so on.
511 Your system will need to define the platform device used by
512 this driver, otherwise it won't be accessible. This means
513 you can safely enable this driver if you don't know whether
514 or not your board has this kind of hardware.
516 This driver can also be built as a module. If so, the module
517 will be called rtc-cmos.
519 config RTC_DRV_DS1216
520 tristate "Dallas DS1216"
523 If you say yes here you get support for the Dallas DS1216 RTC chips.
525 config RTC_DRV_DS1286
526 tristate "Dallas DS1286"
528 If you say yes here you get support for the Dallas DS1286 RTC chips.
530 config RTC_DRV_DS1302
531 tristate "Dallas DS1302"
532 depends on SH_SECUREEDGE5410
534 If you say yes here you get support for the Dallas DS1302 RTC chips.
536 config RTC_DRV_DS1511
537 tristate "Dallas DS1511"
540 If you say yes here you get support for the
541 Dallas DS1511 timekeeping/watchdog chip.
543 This driver can also be built as a module. If so, the module
544 will be called rtc-ds1511.
546 config RTC_DRV_DS1553
547 tristate "Maxim/Dallas DS1553"
549 If you say yes here you get support for the
550 Maxim/Dallas DS1553 timekeeping chip.
552 This driver can also be built as a module. If so, the module
553 will be called rtc-ds1553.
555 config RTC_DRV_DS1742
556 tristate "Maxim/Dallas DS1742/1743"
558 If you say yes here you get support for the
559 Maxim/Dallas DS1742/1743 timekeeping chip.
561 This driver can also be built as a module. If so, the module
562 will be called rtc-ds1742.
568 If you say yes here you will get support for the EFI
571 This driver can also be built as a module. If so, the module
572 will be called rtc-efi.
574 config RTC_DRV_STK17TA8
575 tristate "Simtek STK17TA8"
578 If you say yes here you get support for the
579 Simtek STK17TA8 timekeeping chip.
581 This driver can also be built as a module. If so, the module
582 will be called rtc-stk17ta8.
584 config RTC_DRV_M48T86
585 tristate "ST M48T86/Dallas DS12887"
587 If you say Y here you will get support for the
588 ST M48T86 and Dallas DS12887 RTC chips.
590 This driver can also be built as a module. If so, the module
591 will be called rtc-m48t86.
593 config RTC_DRV_M48T35
596 If you say Y here you will get support for the
599 This driver can also be built as a module, if so, the module
600 will be called "rtc-m48t35".
602 config RTC_DRV_M48T59
603 tristate "ST M48T59/M48T08/M48T02"
605 If you say Y here you will get support for the
606 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
608 These chips are usually found in Sun SPARC and UltraSPARC
611 This driver can also be built as a module, if so, the module
612 will be called "rtc-m48t59".
614 config RTC_DRV_MSM6242
615 tristate "Oki MSM6242"
617 If you say yes here you get support for the Oki MSM6242
618 timekeeping chip. It is used in some Amiga models (e.g. A2000).
620 This driver can also be built as a module. If so, the module
621 will be called rtc-msm6242.
624 tristate "Freescale IMX DryIce Real Time Clock"
628 Support for Freescale IMX DryIce RTC
630 This driver can also be built as a module, if so, the module
631 will be called "rtc-imxdi".
634 tristate "Freescale MXC Real Time Clock"
638 If you say yes here you get support for the Freescale MXC
641 This driver can also be built as a module, if so, the module
642 will be called "rtc-mxc".
644 config RTC_DRV_BQ4802
647 If you say Y here you will get support for the TI
650 This driver can also be built as a module. If so, the module
651 will be called rtc-bq4802.
653 config RTC_DRV_RP5C01
654 tristate "Ricoh RP5C01"
656 If you say yes here you get support for the Ricoh RP5C01
657 timekeeping chip. It is used in some Amiga models (e.g. A3000
660 This driver can also be built as a module. If so, the module
661 will be called rtc-rp5c01.
664 tristate "EM Microelectronic V3020"
666 If you say yes here you will get support for the
667 EM Microelectronic v3020 RTC chip.
669 This driver can also be built as a module. If so, the module
670 will be called rtc-v3020.
672 config RTC_DRV_WM831X
673 tristate "Wolfson Microelectronics WM831x RTC"
674 depends on MFD_WM831X
676 If you say yes here you will get support for the RTC subsystem
677 of the Wolfson Microelectronics WM831X series PMICs.
679 This driver can also be built as a module. If so, the module
680 will be called "rtc-wm831x".
682 config RTC_DRV_WM8350
683 tristate "Wolfson Microelectronics WM8350 RTC"
684 depends on MFD_WM8350
686 If you say yes here you will get support for the RTC subsystem
687 of the Wolfson Microelectronics WM8350.
689 This driver can also be built as a module. If so, the module
690 will be called "rtc-wm8350".
692 config RTC_DRV_PCF50633
693 depends on MFD_PCF50633
694 tristate "NXP PCF50633 RTC"
696 If you say yes here you get support for the RTC subsystem of the
697 NXP PCF50633 used in embedded systems.
699 config RTC_DRV_AB3100
700 tristate "ST-Ericsson AB3100 RTC"
701 depends on AB3100_CORE
702 default y if AB3100_CORE
704 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
705 support. This chip contains a battery- and capacitor-backed RTC.
707 config RTC_DRV_AB8500
708 tristate "ST-Ericsson AB8500 RTC"
709 depends on AB8500_CORE
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.
725 If you say yes here you get support for the RTC subsystem of the
726 CPCAP used in embedded systems.
728 comment "on-CPU RTC drivers"
730 config RTC_DRV_DAVINCI
731 tristate "TI DaVinci RTC"
732 depends on ARCH_DAVINCI_DM365
734 If you say yes here you get support for the RTC on the
735 DaVinci platforms (DM365).
737 This driver can also be built as a module. If so, the module
738 will be called rtc-davinci.
742 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
744 Say "yes" here to support the real time clock on TI OMAP1 and
745 DA8xx/OMAP-L13x chips. This driver can also be built as a
746 module called rtc-omap.
751 This will include RTC support for Samsung SoCs. If
752 you want to include RTC support for any machine, kindly
753 select this in the respective mach-XXXX/Kconfig file.
756 tristate "Samsung S3C series SoC RTC"
757 depends on ARCH_S3C2410 || ARCH_S3C64XX || HAVE_S3C_RTC
759 RTC (Realtime Clock) driver for the clock inbuilt into the
760 Samsung S3C24XX series of SoCs. This can provide periodic
761 interrupt rates from 1Hz to 64Hz for user programs, and
764 The driver currently supports the common features on all the
765 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
768 This driver can also be build as a module. If so, the module
769 will be called rtc-s3c.
771 config RTC_DRV_EP93XX
772 tristate "Cirrus Logic EP93XX"
773 depends on ARCH_EP93XX
775 If you say yes here you get support for the
776 RTC embedded in the Cirrus Logic EP93XX processors.
778 This driver can also be built as a module. If so, the module
779 will be called rtc-ep93xx.
781 config RTC_DRV_SA1100
782 tristate "SA11x0/PXA2xx"
783 depends on ARCH_SA1100 || ARCH_PXA
785 If you say Y here you will get access to the real time clock
786 built into your SA11x0 or PXA2xx CPU.
788 To compile this driver as a module, choose M here: the
789 module will be called rtc-sa1100.
792 tristate "SuperH On-Chip RTC"
793 depends on RTC_CLASS && SUPERH && HAVE_CLK
795 Say Y here to enable support for the on-chip RTC found in
796 most SuperH processors.
798 To compile this driver as a module, choose M here: the
799 module will be called rtc-sh.
801 config RTC_DRV_VR41XX
802 tristate "NEC VR41XX"
803 depends on CPU_VR41XX
805 If you say Y here you will get access to the real time clock
806 built into your NEC VR41XX CPU.
808 To compile this driver as a module, choose M here: the
809 module will be called rtc-vr41xx.
812 tristate "ARM AMBA PL030 RTC"
815 If you say Y here you will get access to ARM AMBA
816 PrimeCell PL030 RTC found on certain ARM SOCs.
818 To compile this driver as a module, choose M here: the
819 module will be called rtc-pl030.
822 tristate "ARM AMBA PL031 RTC"
825 If you say Y here you will get access to ARM AMBA
826 PrimeCell PL031 RTC found on certain ARM SOCs.
828 To compile this driver as a module, choose M here: the
829 module will be called rtc-pl031.
831 config RTC_DRV_AT32AP700X
832 tristate "AT32AP700X series RTC"
833 depends on PLATFORM_AT32AP
835 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
836 AT32AP700x family processors.
838 config RTC_DRV_AT91RM9200
839 tristate "AT91RM9200 or AT91SAM9RL"
840 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
842 Driver for the internal RTC (Realtime Clock) module found on
843 Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips
844 this is powered by the backup power supply.
846 config RTC_DRV_AT91SAM9
847 tristate "AT91SAM9x/AT91CAP9"
848 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
850 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
851 (Real Time Timer). These timers are powered by the backup power
852 supply (such as a small coin cell battery), but do not need to
855 (On AT91SAM9rl chips you probably want to use the dedicated RTC
856 module and leave the RTT available for other uses.)
858 config RTC_DRV_AT91SAM9_RTT
862 prompt "RTT module Number" if ARCH_AT91SAM9263
863 depends on RTC_DRV_AT91SAM9
865 More than one RTT module is available. You can choose which
866 one will be used as an RTC. The default of zero is normally
867 OK to use, though some systems use that for non-RTC purposes.
869 config RTC_DRV_AT91SAM9_GPBR
871 range 0 3 if !ARCH_AT91SAM9263
872 range 0 15 if ARCH_AT91SAM9263
874 prompt "Backup Register Number"
875 depends on RTC_DRV_AT91SAM9
877 The RTC driver needs to use one of the General Purpose Backup
878 Registers (GPBRs) as well as the RTT. You can choose which one
879 will be used. The default of zero is normally OK to use, but
880 on some systems other software needs to use that register.
882 config RTC_DRV_AU1XXX
883 tristate "Au1xxx Counter0 RTC support"
884 depends on MIPS_ALCHEMY
886 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
887 counter) to be used as a RTC.
889 This driver can also be built as a module. If so, the module
890 will be called rtc-au1xxx.
893 tristate "Blackfin On-Chip RTC"
894 depends on BLACKFIN && !BF561
896 If you say yes here you will get support for the
897 Blackfin On-Chip Real Time Clock.
899 This driver can also be built as a module. If so, the module
900 will be called rtc-bfin.
902 config RTC_DRV_RS5C313
903 tristate "Ricoh RS5C313"
904 depends on SH_LANDISK
906 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
908 config RTC_DRV_GENERIC
909 tristate "Generic RTC support"
910 # Please consider writing a new RTC driver instead of using the generic
912 depends on PARISC || M68K || PPC || SUPERH32
914 Say Y or M here to enable RTC support on systems using the generic
915 RTC abstraction. If you do not know what you are doing, you should
919 tristate "PXA27x/PXA3xx"
922 If you say Y here you will get access to the real time clock
923 built into your PXA27x or PXA3xx CPU.
925 This RTC driver uses PXA RTC registers available since pxa27x
926 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
930 bool "SUN4V Hypervisor RTC"
933 If you say Y here you will get support for the Hypervisor
934 based RTC on SUN4V systems.
936 config RTC_DRV_STARFIRE
940 If you say Y here you will get support for the RTC found on
943 config RTC_DRV_TX4939
944 tristate "TX4939 SoC"
945 depends on SOC_TX4939
947 Driver for the internal RTC (Realtime Clock) module found on
951 tristate "Marvell SoC RTC"
952 depends on ARCH_KIRKWOOD || ARCH_DOVE
954 If you say yes here you will get support for the in-chip RTC
955 that can be found in some of Marvell's SoC devices, such as
956 the Kirkwood 88F6281 and 88F6192.
958 This driver can also be built as a module. If so, the module
959 will be called rtc-mv.
965 If you say yes here you will get support for the RTC on PS3.
967 This driver can also be built as a module. If so, the module
968 will be called rtc-ps3.
970 config RTC_DRV_COH901331
971 tristate "ST-Ericsson COH 901 331 RTC"
974 If you say Y here you will get access to ST-Ericsson
975 COH 901 331 RTC clock found in some ST-Ericsson Mobile
978 This driver can also be built as a module. If so, the module
979 will be called "rtc-coh901331".
983 tristate "Freescale STMP3xxx RTC"
984 depends on ARCH_STMP3XXX
986 If you say yes here you will get support for the onboard
989 This driver can also be built as a module. If so, the module
990 will be called rtc-stmp3xxx.
996 If you say Y here you will get support for the RTC found on
997 the PCAP2 ASIC used on some Motorola phones.
999 config RTC_DRV_MC13783
1000 depends on MFD_MC13783
1001 tristate "Freescale MC13783 RTC"
1003 This enables support for the Freescale MC13783 PMIC RTC
1005 config RTC_DRV_MPC5121
1006 tristate "Freescale MPC5121 built-in RTC"
1007 depends on PPC_MPC512x && RTC_CLASS
1009 If you say yes here you will get support for the
1010 built-in RTC MPC5121.
1012 This driver can also be built as a module. If so, the module
1013 will be called rtc-mpc5121.
1015 config RTC_DRV_JZ4740
1016 tristate "Ingenic JZ4740 SoC"
1017 depends on RTC_CLASS
1018 depends on MACH_JZ4740
1020 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1023 This driver can also be buillt as a module. If so, the module
1024 will be called rtc-jz4740.