2 # RTC class/drivers configuration
14 Generic RTC class support. If you say yes here, you will
15 be allowed to plug one or more RTCs to your system. You will
16 probably want to enable one or more of the interfaces below.
21 bool "Set system time from RTC on startup and resume"
22 depends on RTC_CLASS = y
25 If you say yes here, the system time (wall clock) will be set using
26 the value read from a specified RTC device. This is useful to avoid
27 unnecessary fsck runs at boot time, and to network better.
29 config RTC_HCTOSYS_DEVICE
30 string "RTC used to set the system time"
31 depends on RTC_HCTOSYS = y
34 The RTC device that will be used to (re)initialize the system
35 clock, usually rtc0. Initialization is done when the system
36 starts up, and when it resumes from a low power state. This
37 device should record time in UTC, since the kernel won't do
40 The driver for this RTC device must be loaded before late_initcall
41 functions run, so it must usually be statically linked.
43 This clock should be battery-backed, so that it reads the correct
44 time when the system boots from a power-off state. Otherwise, your
45 system will need an external clock source (like an NTP server).
47 If the clock you specify here is not battery backed, it may still
48 be useful to reinitialize system time when resuming from system
49 sleep states. Do not specify an RTC here unless it stays powered
50 during all this system's supported sleep states.
53 bool "RTC debug support"
54 depends on RTC_CLASS = y
56 Say yes here to enable debugging support in the RTC framework
57 and individual RTC drivers.
59 comment "RTC interfaces"
62 boolean "/sys/class/rtc/rtcN (sysfs)"
66 Say yes here if you want to use your RTCs using sysfs interfaces,
67 /sys/class/rtc/rtc0 through /sys/.../rtcN.
72 boolean "/proc/driver/rtc (procfs for rtc0)"
76 Say yes here if you want to use your first RTC through the proc
77 interface, /proc/driver/rtc. Other RTCs will not be available
83 boolean "/dev/rtcN (character devices)"
86 Say yes here if you want to use your RTCs using the /dev
87 interfaces, which "udev" sets up as /dev/rtc0 through
90 You may want to set up a symbolic link so one of these
91 can be accessed as /dev/rtc, which is a name
92 expected by "hwclock" and some other programs. Recent
93 versions of "udev" are known to set up the symlink for you.
97 config RTC_INTF_DEV_UIE_EMUL
98 bool "RTC UIE emulation on dev interface"
99 depends on RTC_INTF_DEV
101 Provides an emulation for RTC_UIE if the underlying rtc chip
102 driver does not expose RTC_UIE ioctls. Those requests generate
103 once-per-second update interrupts, used for synchronization.
105 The emulation code will read the time from the hardware
106 clock several times per second, please enable this option
107 only if you know that you really need it.
110 tristate "Test driver/device"
112 If you say yes here you get support for the
113 RTC test driver. It's a software RTC which can be
114 used to test the RTC subsystem APIs. It gets
115 the time from the system clock.
116 You want this driver only if you are doing development
117 on the RTC subsystem. Please read the source code
120 This driver can also be built as a module. If so, the module
121 will be called rtc-test.
123 comment "I2C RTC drivers"
128 config RTC_DRV_88PM860X
129 tristate "Marvell 88PM860x"
130 depends on RTC_CLASS && I2C && MFD_88PM860X
132 If you say yes here you get support for RTC function in Marvell
135 This driver can also be built as a module. If so, the module
136 will be called rtc-88pm860x.
138 config RTC_DRV_DS1307
139 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
141 If you say yes here you get support for various compatible RTC
142 chips (often with battery backup) connected with I2C. This driver
143 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
144 EPSON RX-8025 and probably other chips. In some cases the RTC
145 must already have been initialized (by manufacturing or a
148 The first seven registers on these chips hold an RTC, and other
149 registers may add features such as NVRAM, a trickle charger for
150 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
151 sysfs, but other chip features may not be available.
153 This driver can also be built as a module. If so, the module
154 will be called rtc-ds1307.
156 config RTC_DRV_DS1374
157 tristate "Dallas/Maxim DS1374"
158 depends on RTC_CLASS && I2C
160 If you say yes here you get support for Dallas Semiconductor
161 DS1374 real-time clock chips. If an interrupt is associated
162 with the device, the alarm functionality is supported.
164 This driver can also be built as a module. If so, the module
165 will be called rtc-ds1374.
167 config RTC_DRV_DS1672
168 tristate "Dallas/Maxim DS1672"
170 If you say yes here you get support for the
171 Dallas/Maxim DS1672 timekeeping chip.
173 This driver can also be built as a module. If so, the module
174 will be called rtc-ds1672.
176 config RTC_DRV_DS3232
177 tristate "Dallas/Maxim DS3232"
178 depends on RTC_CLASS && I2C
180 If you say yes here you get support for Dallas Semiconductor
181 DS3232 real-time clock chips. If an interrupt is associated
182 with the device, the alarm functionality is supported.
184 This driver can also be built as a module. If so, the module
185 will be called rtc-ds3232.
187 config RTC_DRV_MAX6900
188 tristate "Maxim MAX6900"
190 If you say yes here you will get support for the
191 Maxim MAX6900 I2C RTC chip.
193 This driver can also be built as a module. If so, the module
194 will be called rtc-max6900.
196 config RTC_DRV_MAX8925
197 tristate "Maxim MAX8925"
198 depends on MFD_MAX8925
200 If you say yes here you will get support for the
201 RTC of Maxim MAX8925 PMIC.
203 This driver can also be built as a module. If so, the module
204 will be called rtc-max8925.
206 config RTC_DRV_MAX8998
207 tristate "Maxim MAX8998"
208 depends on MFD_MAX8998
210 If you say yes here you will get support for the
211 RTC of Maxim MAX8998 PMIC.
213 This driver can also be built as a module. If so, the module
214 will be called rtc-max8998.
216 config RTC_DRV_RS5C372
217 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
219 If you say yes here you get support for the
220 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
222 This driver can also be built as a module. If so, the module
223 will be called rtc-rs5c372.
225 config RTC_DRV_ISL1208
226 tristate "Intersil ISL1208"
228 If you say yes here you get support for the
229 Intersil ISL1208 RTC chip.
231 This driver can also be built as a module. If so, the module
232 will be called rtc-isl1208.
234 config RTC_DRV_ISL12022
235 tristate "Intersil ISL12022"
237 If you say yes here you get support for the
238 Intersil ISL12022 RTC chip.
240 This driver can also be built as a module. If so, the module
241 will be called rtc-isl12022.
244 tristate "Xicor/Intersil X1205"
246 If you say yes here you get support for the
247 Xicor/Intersil X1205 RTC chip.
249 This driver can also be built as a module. If so, the module
250 will be called rtc-x1205.
252 config RTC_DRV_PCF8563
253 tristate "Philips PCF8563/Epson RTC8564"
255 If you say yes here you get support for the
256 Philips PCF8563 RTC chip. The Epson RTC8564
259 This driver can also be built as a module. If so, the module
260 will be called rtc-pcf8563.
262 config RTC_DRV_PCF8583
263 tristate "Philips PCF8583"
265 If you say yes here you get support for the Philips PCF8583
266 RTC chip found on Acorn RiscPCs. This driver supports the
267 platform specific method of retrieving the current year from
268 the RTC's SRAM. It will work on other platforms with the same
269 chip, but the year will probably have to be tweaked.
271 This driver can also be built as a module. If so, the module
272 will be called rtc-pcf8583.
274 config RTC_DRV_M41T80
275 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
277 If you say Y here you will get support for the ST M41T60
278 and M41T80 RTC chips series. Currently, the following chips are
279 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
280 M41ST85, and M41ST87.
282 This driver can also be built as a module. If so, the module
283 will be called rtc-m41t80.
285 config RTC_DRV_M41T80_WDT
286 bool "ST M41T65/M41T80 series RTC watchdog timer"
287 depends on RTC_DRV_M41T80
289 If you say Y here you will get support for the
290 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
293 tristate "TI BQ32000"
295 If you say Y here you will get support for the TI
296 BQ32000 I2C RTC chip.
298 This driver can also be built as a module. If so, the module
299 will be called rtc-bq32k.
301 config RTC_DRV_DM355EVM
302 tristate "TI DaVinci DM355 EVM RTC"
303 depends on MFD_DM355EVM_MSP
305 Supports the RTC firmware in the MSP430 on the DM355 EVM.
307 config RTC_DRV_TWL92330
308 boolean "TI TWL92330/Menelaus"
311 If you say yes here you get support for the RTC on the
312 TWL92330 "Menelaus" power management chip, used with OMAP2
313 platforms. The support is integrated with the rest of
314 the Menelaus driver; it's not separate module.
316 config RTC_DRV_TWL4030
317 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
318 depends on RTC_CLASS && TWL4030_CORE
320 If you say yes here you get support for the RTC on the
321 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
323 This driver can also be built as a module. If so, the module
324 will be called rtc-twl.
326 config RTC_DRV_S35390A
327 tristate "Seiko Instruments S-35390A"
330 If you say yes here you will get support for the Seiko
331 Instruments S-35390A.
333 This driver can also be built as a module. If so the module
334 will be called rtc-s35390a.
336 config RTC_DRV_FM3130
337 tristate "Ramtron FM3130"
339 If you say Y here you will get support for the
340 Ramtron FM3130 RTC chips.
341 Ramtron FM3130 is a chip with two separate devices inside,
342 RTC clock and FRAM. This driver provides only RTC functionality.
344 This driver can also be built as a module. If so the module
345 will be called rtc-fm3130.
347 config RTC_DRV_RX8581
348 tristate "Epson RX-8581"
350 If you say yes here you will get support for the Epson RX-8581.
352 This driver can also be built as a module. If so the module
353 will be called rtc-rx8581.
355 config RTC_DRV_RX8025
356 tristate "Epson RX-8025SA/NB"
358 If you say yes here you get support for the Epson
359 RX-8025SA/NB RTC chips.
361 This driver can also be built as a module. If so, the module
362 will be called rtc-rx8025.
366 comment "SPI RTC drivers"
370 config RTC_DRV_M41T94
373 If you say yes here you will get support for the
374 ST M41T94 SPI RTC chip.
376 This driver can also be built as a module. If so, the module
377 will be called rtc-m41t94.
379 config RTC_DRV_DS1305
380 tristate "Dallas/Maxim DS1305/DS1306"
382 Select this driver to get support for the Dallas/Maxim DS1305
383 and DS1306 real time clock chips. These support a trickle
384 charger, alarms, and NVRAM in addition to the clock.
386 This driver can also be built as a module. If so, the module
387 will be called rtc-ds1305.
389 config RTC_DRV_DS1390
390 tristate "Dallas/Maxim DS1390/93/94"
392 If you say yes here you get support for the
393 Dallas/Maxim DS1390/93/94 chips.
395 This driver only supports the RTC feature, and not other chip
396 features such as alarms and trickle charging.
398 This driver can also be built as a module. If so, the module
399 will be called rtc-ds1390.
401 config RTC_DRV_MAX6902
402 tristate "Maxim MAX6902"
404 If you say yes here you will get support for the
405 Maxim MAX6902 SPI RTC chip.
407 This driver can also be built as a module. If so, the module
408 will be called rtc-max6902.
411 tristate "Epson RTC-9701JE"
413 If you say yes here you will get support for the
414 Epson RTC-9701JE SPI RTC chip.
416 This driver can also be built as a module. If so, the module
417 will be called rtc-r9701.
419 config RTC_DRV_RS5C348
420 tristate "Ricoh RS5C348A/B"
422 If you say yes here you get support for the
423 Ricoh RS5C348A and RS5C348B RTC chips.
425 This driver can also be built as a module. If so, the module
426 will be called rtc-rs5c348.
428 config RTC_DRV_DS3234
429 tristate "Maxim/Dallas DS3234"
431 If you say yes here you get support for the
432 Maxim/Dallas DS3234 SPI RTC chip.
434 This driver can also be built as a module. If so, the module
435 will be called rtc-ds3234.
437 config RTC_DRV_PCF2123
438 tristate "NXP PCF2123"
440 If you say yes here you get support for the NXP PCF2123
443 This driver can also be built as a module. If so, the module
444 will be called rtc-pcf2123.
448 comment "Platform RTC drivers"
450 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
451 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
452 # global rtc_lock ... it's not yet just another platform_device.
455 tristate "PC-style 'CMOS'"
456 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
459 Say "yes" here to get direct support for the real time clock
460 found in every PC or ACPI-based system, and some other boards.
461 Specifically the original MC146818, compatibles like those in
462 PC south bridges, the DS12887 or M48T86, some multifunction
463 or LPC bus chips, and so on.
465 Your system will need to define the platform device used by
466 this driver, otherwise it won't be accessible. This means
467 you can safely enable this driver if you don't know whether
468 or not your board has this kind of hardware.
470 This driver can also be built as a module. If so, the module
471 will be called rtc-cmos.
474 tristate "Virtual RTC for Moorestown platforms"
476 default y if X86_MRST
479 Say "yes" here to get direct support for the real time clock
480 found on Moorestown platforms. The VRTC is a emulated RTC that
481 derives its clock source from a real RTC in the PMIC. The MC146818
482 style programming interface is mostly conserved, but any
483 updates are done via IPC calls to the system controller FW.
485 config RTC_DRV_DS1216
486 tristate "Dallas DS1216"
489 If you say yes here you get support for the Dallas DS1216 RTC chips.
491 config RTC_DRV_DS1286
492 tristate "Dallas DS1286"
494 If you say yes here you get support for the Dallas DS1286 RTC chips.
496 config RTC_DRV_DS1302
497 tristate "Dallas DS1302"
498 depends on SH_SECUREEDGE5410
500 If you say yes here you get support for the Dallas DS1302 RTC chips.
502 config RTC_DRV_DS1511
503 tristate "Dallas DS1511"
506 If you say yes here you get support for the
507 Dallas DS1511 timekeeping/watchdog chip.
509 This driver can also be built as a module. If so, the module
510 will be called rtc-ds1511.
512 config RTC_DRV_DS1553
513 tristate "Maxim/Dallas DS1553"
515 If you say yes here you get support for the
516 Maxim/Dallas DS1553 timekeeping chip.
518 This driver can also be built as a module. If so, the module
519 will be called rtc-ds1553.
521 config RTC_DRV_DS1742
522 tristate "Maxim/Dallas DS1742/1743"
524 If you say yes here you get support for the
525 Maxim/Dallas DS1742/1743 timekeeping chip.
527 This driver can also be built as a module. If so, the module
528 will be called rtc-ds1742.
534 If you say yes here you will get support for the EFI
537 This driver can also be built as a module. If so, the module
538 will be called rtc-efi.
540 config RTC_DRV_STK17TA8
541 tristate "Simtek STK17TA8"
544 If you say yes here you get support for the
545 Simtek STK17TA8 timekeeping chip.
547 This driver can also be built as a module. If so, the module
548 will be called rtc-stk17ta8.
550 config RTC_DRV_M48T86
551 tristate "ST M48T86/Dallas DS12887"
553 If you say Y here you will get support for the
554 ST M48T86 and Dallas DS12887 RTC chips.
556 This driver can also be built as a module. If so, the module
557 will be called rtc-m48t86.
559 config RTC_DRV_M48T35
562 If you say Y here you will get support for the
565 This driver can also be built as a module, if so, the module
566 will be called "rtc-m48t35".
568 config RTC_DRV_M48T59
569 tristate "ST M48T59/M48T08/M48T02"
571 If you say Y here you will get support for the
572 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
574 These chips are usually found in Sun SPARC and UltraSPARC
577 This driver can also be built as a module, if so, the module
578 will be called "rtc-m48t59".
580 config RTC_DRV_MSM6242
581 tristate "Oki MSM6242"
583 If you say yes here you get support for the Oki MSM6242
584 timekeeping chip. It is used in some Amiga models (e.g. A2000).
586 This driver can also be built as a module. If so, the module
587 will be called rtc-msm6242.
590 tristate "Freescale IMX DryIce Real Time Clock"
594 Support for Freescale IMX DryIce RTC
596 This driver can also be built as a module, if so, the module
597 will be called "rtc-imxdi".
600 tristate "Freescale MXC Real Time Clock"
604 If you say yes here you get support for the Freescale MXC
607 This driver can also be built as a module, if so, the module
608 will be called "rtc-mxc".
610 config RTC_DRV_BQ4802
613 If you say Y here you will get support for the TI
616 This driver can also be built as a module. If so, the module
617 will be called rtc-bq4802.
619 config RTC_DRV_RP5C01
620 tristate "Ricoh RP5C01"
622 If you say yes here you get support for the Ricoh RP5C01
623 timekeeping chip. It is used in some Amiga models (e.g. A3000
626 This driver can also be built as a module. If so, the module
627 will be called rtc-rp5c01.
630 tristate "EM Microelectronic V3020"
632 If you say yes here you will get support for the
633 EM Microelectronic v3020 RTC chip.
635 This driver can also be built as a module. If so, the module
636 will be called rtc-v3020.
638 config RTC_DRV_WM831X
639 tristate "Wolfson Microelectronics WM831x RTC"
640 depends on MFD_WM831X
642 If you say yes here you will get support for the RTC subsystem
643 of the Wolfson Microelectronics WM831X series PMICs.
645 This driver can also be built as a module. If so, the module
646 will be called "rtc-wm831x".
648 config RTC_DRV_WM8350
649 tristate "Wolfson Microelectronics WM8350 RTC"
650 depends on MFD_WM8350
652 If you say yes here you will get support for the RTC subsystem
653 of the Wolfson Microelectronics WM8350.
655 This driver can also be built as a module. If so, the module
656 will be called "rtc-wm8350".
658 config RTC_DRV_PCF50633
659 depends on MFD_PCF50633
660 tristate "NXP PCF50633 RTC"
662 If you say yes here you get support for the RTC subsystem of the
663 NXP PCF50633 used in embedded systems.
665 config RTC_DRV_AB3100
666 tristate "ST-Ericsson AB3100 RTC"
667 depends on AB3100_CORE
668 default y if AB3100_CORE
670 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
671 support. This chip contains a battery- and capacitor-backed RTC.
673 config RTC_DRV_AB8500
674 tristate "ST-Ericsson AB8500 RTC"
675 depends on AB8500_CORE
677 Select this to enable the ST-Ericsson AB8500 power management IC RTC
678 support. This chip contains a battery- and capacitor-backed RTC.
680 config RTC_DRV_NUC900
681 tristate "NUC910/NUC920 RTC driver"
682 depends on RTC_CLASS && ARCH_W90X900
684 If you say yes here you get support for the RTC subsystem of the
685 NUC910/NUC920 used in embedded systems.
687 comment "on-CPU RTC drivers"
689 config RTC_DRV_DAVINCI
690 tristate "TI DaVinci RTC"
691 depends on ARCH_DAVINCI_DM365
693 If you say yes here you get support for the RTC on the
694 DaVinci platforms (DM365).
696 This driver can also be built as a module. If so, the module
697 will be called rtc-davinci.
701 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
703 Say "yes" here to support the real time clock on TI OMAP1 and
704 DA8xx/OMAP-L13x chips. This driver can also be built as a
705 module called rtc-omap.
710 This will include RTC support for Samsung SoCs. If
711 you want to include RTC support for any machine, kindly
712 select this in the respective mach-XXXX/Kconfig file.
715 tristate "Samsung S3C series SoC RTC"
716 depends on ARCH_S3C2410 || ARCH_S3C64XX || HAVE_S3C_RTC
718 RTC (Realtime Clock) driver for the clock inbuilt into the
719 Samsung S3C24XX series of SoCs. This can provide periodic
720 interrupt rates from 1Hz to 64Hz for user programs, and
723 The driver currently supports the common features on all the
724 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
727 This driver can also be build as a module. If so, the module
728 will be called rtc-s3c.
730 config RTC_DRV_EP93XX
731 tristate "Cirrus Logic EP93XX"
732 depends on ARCH_EP93XX
734 If you say yes here you get support for the
735 RTC embedded in the Cirrus Logic EP93XX processors.
737 This driver can also be built as a module. If so, the module
738 will be called rtc-ep93xx.
740 config RTC_DRV_SA1100
741 tristate "SA11x0/PXA2xx"
742 depends on ARCH_SA1100 || ARCH_PXA
744 If you say Y here you will get access to the real time clock
745 built into your SA11x0 or PXA2xx CPU.
747 To compile this driver as a module, choose M here: the
748 module will be called rtc-sa1100.
751 tristate "SuperH On-Chip RTC"
752 depends on RTC_CLASS && SUPERH && HAVE_CLK
754 Say Y here to enable support for the on-chip RTC found in
755 most SuperH processors.
757 To compile this driver as a module, choose M here: the
758 module will be called rtc-sh.
760 config RTC_DRV_VR41XX
761 tristate "NEC VR41XX"
762 depends on CPU_VR41XX
764 If you say Y here you will get access to the real time clock
765 built into your NEC VR41XX CPU.
767 To compile this driver as a module, choose M here: the
768 module will be called rtc-vr41xx.
771 tristate "ARM AMBA PL030 RTC"
774 If you say Y here you will get access to ARM AMBA
775 PrimeCell PL030 RTC found on certain ARM SOCs.
777 To compile this driver as a module, choose M here: the
778 module will be called rtc-pl030.
781 tristate "ARM AMBA PL031 RTC"
784 If you say Y here you will get access to ARM AMBA
785 PrimeCell PL031 RTC found on certain ARM SOCs.
787 To compile this driver as a module, choose M here: the
788 module will be called rtc-pl031.
790 config RTC_DRV_AT32AP700X
791 tristate "AT32AP700X series RTC"
792 depends on PLATFORM_AT32AP
794 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
795 AT32AP700x family processors.
797 config RTC_DRV_AT91RM9200
798 tristate "AT91RM9200 or some AT91SAM9 RTC"
799 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
801 Driver for the internal RTC (Realtime Clock) module found on
802 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
803 this is powered by the backup power supply.
805 config RTC_DRV_AT91SAM9
806 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
807 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
809 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
810 (Real Time Timer). These timers are powered by the backup power
811 supply (such as a small coin cell battery), but do not need to
814 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
815 dedicated RTC module and leave the RTT available for other uses.)
817 config RTC_DRV_AT91SAM9_RTT
821 prompt "RTT module Number" if ARCH_AT91SAM9263
822 depends on RTC_DRV_AT91SAM9
824 More than one RTT module is available. You can choose which
825 one will be used as an RTC. The default of zero is normally
826 OK to use, though some systems use that for non-RTC purposes.
828 config RTC_DRV_AT91SAM9_GPBR
830 range 0 3 if !ARCH_AT91SAM9263
831 range 0 15 if ARCH_AT91SAM9263
833 prompt "Backup Register Number"
834 depends on RTC_DRV_AT91SAM9
836 The RTC driver needs to use one of the General Purpose Backup
837 Registers (GPBRs) as well as the RTT. You can choose which one
838 will be used. The default of zero is normally OK to use, but
839 on some systems other software needs to use that register.
841 config RTC_DRV_AU1XXX
842 tristate "Au1xxx Counter0 RTC support"
843 depends on MIPS_ALCHEMY
845 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
846 counter) to be used as a RTC.
848 This driver can also be built as a module. If so, the module
849 will be called rtc-au1xxx.
852 tristate "Blackfin On-Chip RTC"
853 depends on BLACKFIN && !BF561
855 If you say yes here you will get support for the
856 Blackfin On-Chip Real Time Clock.
858 This driver can also be built as a module. If so, the module
859 will be called rtc-bfin.
861 config RTC_DRV_RS5C313
862 tristate "Ricoh RS5C313"
863 depends on SH_LANDISK
865 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
867 config RTC_DRV_GENERIC
868 tristate "Generic RTC support"
869 # Please consider writing a new RTC driver instead of using the generic
871 depends on PARISC || M68K || PPC || SUPERH32
873 Say Y or M here to enable RTC support on systems using the generic
874 RTC abstraction. If you do not know what you are doing, you should
878 tristate "PXA27x/PXA3xx"
881 If you say Y here you will get access to the real time clock
882 built into your PXA27x or PXA3xx CPU.
884 This RTC driver uses PXA RTC registers available since pxa27x
885 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
889 bool "SUN4V Hypervisor RTC"
892 If you say Y here you will get support for the Hypervisor
893 based RTC on SUN4V systems.
895 config RTC_DRV_STARFIRE
899 If you say Y here you will get support for the RTC found on
902 config RTC_DRV_TX4939
903 tristate "TX4939 SoC"
904 depends on SOC_TX4939
906 Driver for the internal RTC (Realtime Clock) module found on
910 tristate "Marvell SoC RTC"
911 depends on ARCH_KIRKWOOD || ARCH_DOVE
913 If you say yes here you will get support for the in-chip RTC
914 that can be found in some of Marvell's SoC devices, such as
915 the Kirkwood 88F6281 and 88F6192.
917 This driver can also be built as a module. If so, the module
918 will be called rtc-mv.
924 If you say yes here you will get support for the RTC on PS3.
926 This driver can also be built as a module. If so, the module
927 will be called rtc-ps3.
929 config RTC_DRV_COH901331
930 tristate "ST-Ericsson COH 901 331 RTC"
933 If you say Y here you will get access to ST-Ericsson
934 COH 901 331 RTC clock found in some ST-Ericsson Mobile
937 This driver can also be built as a module. If so, the module
938 will be called "rtc-coh901331".
942 tristate "Freescale STMP3xxx RTC"
943 depends on ARCH_STMP3XXX
945 If you say yes here you will get support for the onboard
948 This driver can also be built as a module. If so, the module
949 will be called rtc-stmp3xxx.
955 If you say Y here you will get support for the RTC found on
956 the PCAP2 ASIC used on some Motorola phones.
958 config RTC_DRV_MC13XXX
959 depends on MFD_MC13XXX
960 tristate "Freescale MC13xxx RTC"
962 This enables support for the RTCs found on Freescale's PMICs
965 config RTC_DRV_MPC5121
966 tristate "Freescale MPC5121 built-in RTC"
967 depends on PPC_MPC512x && RTC_CLASS
969 If you say yes here you will get support for the
970 built-in RTC MPC5121.
972 This driver can also be built as a module. If so, the module
973 will be called rtc-mpc5121.
975 config RTC_DRV_JZ4740
976 tristate "Ingenic JZ4740 SoC"
978 depends on MACH_JZ4740
980 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
983 This driver can also be buillt as a module. If so, the module
984 will be called rtc-jz4740.
986 config RTC_DRV_LPC32XX
987 depends on ARCH_LPC32XX
988 tristate "NXP LPC32XX RTC"
990 This enables support for the NXP RTC in the LPC32XX
992 This driver can also be buillt as a module. If so, the module
993 will be called rtc-lpc32xx.
996 tristate "NVIDIA Tegra Internal RTC driver"
997 depends on RTC_CLASS && ARCH_TEGRA
999 If you say yes here you get support for the
1000 Tegra 200 series internal RTC module.
1002 This drive can also be built as a module. If so, the module
1003 will be called rtc-tegra.
1006 tristate "Tilera hypervisor RTC support"
1009 Enable support for the Linux driver side of the Tilera
1010 hypervisor's real-time clock interface.