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.
113 tristate "Test driver/device"
115 If you say yes here you get support for the
116 RTC test driver. It's a software RTC which can be
117 used to test the RTC subsystem APIs. It gets
118 the time from the system clock.
119 You want this driver only if you are doing development
120 on the RTC subsystem. Please read the source code
123 This driver can also be built as a module. If so, the module
124 will be called rtc-test.
126 comment "I2C RTC drivers"
131 config RTC_DRV_DS1307
132 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
134 If you say yes here you get support for various compatible RTC
135 chips (often with battery backup) connected with I2C. This driver
136 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
137 EPSON RX-8025 and probably other chips. In some cases the RTC
138 must already have been initialized (by manufacturing or a
141 The first seven registers on these chips hold an RTC, and other
142 registers may add features such as NVRAM, a trickle charger for
143 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
144 sysfs, but other chip features may not be available.
146 This driver can also be built as a module. If so, the module
147 will be called rtc-ds1307.
149 config RTC_DRV_DS1374
150 tristate "Dallas/Maxim DS1374"
151 depends on RTC_CLASS && I2C
153 If you say yes here you get support for Dallas Semiconductor
154 DS1374 real-time clock chips. If an interrupt is associated
155 with the device, the alarm functionality is supported.
157 This driver can also be built as a module. If so, the module
158 will be called rtc-ds1374.
160 config RTC_DRV_DS1672
161 tristate "Dallas/Maxim DS1672"
163 If you say yes here you get support for the
164 Dallas/Maxim DS1672 timekeeping chip.
166 This driver can also be built as a module. If so, the module
167 will be called rtc-ds1672.
169 config RTC_DRV_DS3232
170 tristate "Dallas/Maxim DS3232"
171 depends on RTC_CLASS && I2C
173 If you say yes here you get support for Dallas Semiconductor
174 DS3232 real-time clock chips. If an interrupt is associated
175 with the device, the alarm functionality is supported.
177 This driver can also be built as a module. If so, the module
178 will be called rtc-ds3232.
180 config RTC_DRV_MAX6900
181 tristate "Maxim MAX6900"
183 If you say yes here you will get support for the
184 Maxim MAX6900 I2C RTC chip.
186 This driver can also be built as a module. If so, the module
187 will be called rtc-max6900.
189 config RTC_DRV_MAX8925
190 tristate "Maxim MAX8925"
191 depends on MFD_MAX8925
193 If you say yes here you will get support for the
194 RTC of Maxim MAX8925 PMIC.
196 This driver can also be built as a module. If so, the module
197 will be called rtc-max8925.
199 config RTC_DRV_RS5C372
200 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
202 If you say yes here you get support for the
203 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
205 This driver can also be built as a module. If so, the module
206 will be called rtc-rs5c372.
208 config RTC_DRV_ISL1208
209 tristate "Intersil ISL1208"
211 If you say yes here you get support for the
212 Intersil ISL1208 RTC chip.
214 This driver can also be built as a module. If so, the module
215 will be called rtc-isl1208.
217 config RTC_DRV_ISL12022
218 tristate "Intersil ISL12022"
220 If you say yes here you get support for the
221 Intersil ISL12022 RTC chip.
223 This driver can also be built as a module. If so, the module
224 will be called rtc-isl12022.
227 tristate "Xicor/Intersil X1205"
229 If you say yes here you get support for the
230 Xicor/Intersil X1205 RTC chip.
232 This driver can also be built as a module. If so, the module
233 will be called rtc-x1205.
235 config RTC_DRV_PCF8563
236 tristate "Philips PCF8563/Epson RTC8564"
238 If you say yes here you get support for the
239 Philips PCF8563 RTC chip. The Epson RTC8564
242 This driver can also be built as a module. If so, the module
243 will be called rtc-pcf8563.
245 config RTC_DRV_PCF8583
246 tristate "Philips PCF8583"
248 If you say yes here you get support for the Philips PCF8583
249 RTC chip found on Acorn RiscPCs. This driver supports the
250 platform specific method of retrieving the current year from
251 the RTC's SRAM. It will work on other platforms with the same
252 chip, but the year will probably have to be tweaked.
254 This driver can also be built as a module. If so, the module
255 will be called rtc-pcf8583.
257 config RTC_DRV_M41T80
258 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
260 If you say Y here you will get support for the ST M41T60
261 and M41T80 RTC chips series. Currently, the following chips are
262 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
263 M41ST85, and M41ST87.
265 This driver can also be built as a module. If so, the module
266 will be called rtc-m41t80.
268 config RTC_DRV_M41T80_WDT
269 bool "ST M41T65/M41T80 series RTC watchdog timer"
270 depends on RTC_DRV_M41T80
272 If you say Y here you will get support for the
273 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
276 tristate "TI BQ32000"
278 If you say Y here you will get support for the TI
279 BQ32000 I2C RTC chip.
281 This driver can also be built as a module. If so, the module
282 will be called rtc-bq32k.
284 config RTC_DRV_DM355EVM
285 tristate "TI DaVinci DM355 EVM RTC"
286 depends on MFD_DM355EVM_MSP
288 Supports the RTC firmware in the MSP430 on the DM355 EVM.
290 config RTC_DRV_TWL92330
291 boolean "TI TWL92330/Menelaus"
294 If you say yes here you get support for the RTC on the
295 TWL92330 "Menelaus" power management chip, used with OMAP2
296 platforms. The support is integrated with the rest of
297 the Menelaus driver; it's not separate module.
299 config RTC_DRV_TWL4030
300 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
301 depends on RTC_CLASS && TWL4030_CORE
303 If you say yes here you get support for the RTC on the
304 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
306 This driver can also be built as a module. If so, the module
307 will be called rtc-twl.
309 config RTC_DRV_S35390A
310 tristate "Seiko Instruments S-35390A"
313 If you say yes here you will get support for the Seiko
314 Instruments S-35390A.
316 This driver can also be built as a module. If so the module
317 will be called rtc-s35390a.
319 config RTC_DRV_FM3130
320 tristate "Ramtron FM3130"
322 If you say Y here you will get support for the
323 Ramtron FM3130 RTC chips.
324 Ramtron FM3130 is a chip with two separate devices inside,
325 RTC clock and FRAM. This driver provides only RTC functionality.
327 This driver can also be built as a module. If so the module
328 will be called rtc-fm3130.
330 config RTC_DRV_RX8581
331 tristate "Epson RX-8581"
333 If you say yes here you will get support for the Epson RX-8581.
335 This driver can also be built as a module. If so the module
336 will be called rtc-rx8581.
338 config RTC_DRV_RX8025
339 tristate "Epson RX-8025SA/NB"
341 If you say yes here you get support for the Epson
342 RX-8025SA/NB RTC chips.
344 This driver can also be built as a module. If so, the module
345 will be called rtc-rx8025.
349 comment "SPI RTC drivers"
353 config RTC_DRV_M41T94
356 If you say yes here you will get support for the
357 ST M41T94 SPI RTC chip.
359 This driver can also be built as a module. If so, the module
360 will be called rtc-m41t94.
362 config RTC_DRV_DS1305
363 tristate "Dallas/Maxim DS1305/DS1306"
365 Select this driver to get support for the Dallas/Maxim DS1305
366 and DS1306 real time clock chips. These support a trickle
367 charger, alarms, and NVRAM in addition to the clock.
369 This driver can also be built as a module. If so, the module
370 will be called rtc-ds1305.
372 config RTC_DRV_DS1390
373 tristate "Dallas/Maxim DS1390/93/94"
375 If you say yes here you get support for the
376 Dallas/Maxim DS1390/93/94 chips.
378 This driver only supports the RTC feature, and not other chip
379 features such as alarms and trickle charging.
381 This driver can also be built as a module. If so, the module
382 will be called rtc-ds1390.
384 config RTC_DRV_MAX6902
385 tristate "Maxim MAX6902"
387 If you say yes here you will get support for the
388 Maxim MAX6902 SPI RTC chip.
390 This driver can also be built as a module. If so, the module
391 will be called rtc-max6902.
394 tristate "Epson RTC-9701JE"
396 If you say yes here you will get support for the
397 Epson RTC-9701JE SPI RTC chip.
399 This driver can also be built as a module. If so, the module
400 will be called rtc-r9701.
402 config RTC_DRV_RS5C348
403 tristate "Ricoh RS5C348A/B"
405 If you say yes here you get support for the
406 Ricoh RS5C348A and RS5C348B RTC chips.
408 This driver can also be built as a module. If so, the module
409 will be called rtc-rs5c348.
411 config RTC_DRV_DS3234
412 tristate "Maxim/Dallas DS3234"
414 If you say yes here you get support for the
415 Maxim/Dallas DS3234 SPI RTC chip.
417 This driver can also be built as a module. If so, the module
418 will be called rtc-ds3234.
420 config RTC_DRV_PCF2123
421 tristate "NXP PCF2123"
423 If you say yes here you get support for the NXP PCF2123
426 This driver can also be built as a module. If so, the module
427 will be called rtc-pcf2123.
431 comment "Platform RTC drivers"
433 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
434 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
435 # global rtc_lock ... it's not yet just another platform_device.
438 tristate "PC-style 'CMOS'"
439 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
442 Say "yes" here to get direct support for the real time clock
443 found in every PC or ACPI-based system, and some other boards.
444 Specifically the original MC146818, compatibles like those in
445 PC south bridges, the DS12887 or M48T86, some multifunction
446 or LPC bus chips, and so on.
448 Your system will need to define the platform device used by
449 this driver, otherwise it won't be accessible. This means
450 you can safely enable this driver if you don't know whether
451 or not your board has this kind of hardware.
453 This driver can also be built as a module. If so, the module
454 will be called rtc-cmos.
456 config RTC_DRV_DS1216
457 tristate "Dallas DS1216"
460 If you say yes here you get support for the Dallas DS1216 RTC chips.
462 config RTC_DRV_DS1286
463 tristate "Dallas DS1286"
465 If you say yes here you get support for the Dallas DS1286 RTC chips.
467 config RTC_DRV_DS1302
468 tristate "Dallas DS1302"
469 depends on SH_SECUREEDGE5410
471 If you say yes here you get support for the Dallas DS1302 RTC chips.
473 config RTC_DRV_DS1511
474 tristate "Dallas DS1511"
477 If you say yes here you get support for the
478 Dallas DS1511 timekeeping/watchdog chip.
480 This driver can also be built as a module. If so, the module
481 will be called rtc-ds1511.
483 config RTC_DRV_DS1553
484 tristate "Maxim/Dallas DS1553"
486 If you say yes here you get support for the
487 Maxim/Dallas DS1553 timekeeping chip.
489 This driver can also be built as a module. If so, the module
490 will be called rtc-ds1553.
492 config RTC_DRV_DS1742
493 tristate "Maxim/Dallas DS1742/1743"
495 If you say yes here you get support for the
496 Maxim/Dallas DS1742/1743 timekeeping chip.
498 This driver can also be built as a module. If so, the module
499 will be called rtc-ds1742.
505 If you say yes here you will get support for the EFI
508 This driver can also be built as a module. If so, the module
509 will be called rtc-efi.
511 config RTC_DRV_STK17TA8
512 tristate "Simtek STK17TA8"
515 If you say yes here you get support for the
516 Simtek STK17TA8 timekeeping chip.
518 This driver can also be built as a module. If so, the module
519 will be called rtc-stk17ta8.
521 config RTC_DRV_M48T86
522 tristate "ST M48T86/Dallas DS12887"
524 If you say Y here you will get support for the
525 ST M48T86 and Dallas DS12887 RTC chips.
527 This driver can also be built as a module. If so, the module
528 will be called rtc-m48t86.
530 config RTC_DRV_M48T35
533 If you say Y here you will get support for the
536 This driver can also be built as a module, if so, the module
537 will be called "rtc-m48t35".
539 config RTC_DRV_M48T59
540 tristate "ST M48T59/M48T08/M48T02"
542 If you say Y here you will get support for the
543 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
545 These chips are usually found in Sun SPARC and UltraSPARC
548 This driver can also be built as a module, if so, the module
549 will be called "rtc-m48t59".
551 config RTC_DRV_MSM6242
552 tristate "Oki MSM6242"
554 If you say yes here you get support for the Oki MSM6242
555 timekeeping chip. It is used in some Amiga models (e.g. A2000).
557 This driver can also be built as a module. If so, the module
558 will be called rtc-msm6242.
561 tristate "Freescale IMX DryIce Real Time Clock"
565 Support for Freescale IMX DryIce RTC
567 This driver can also be built as a module, if so, the module
568 will be called "rtc-imxdi".
571 tristate "Freescale MXC Real Time Clock"
575 If you say yes here you get support for the Freescale MXC
578 This driver can also be built as a module, if so, the module
579 will be called "rtc-mxc".
581 config RTC_DRV_BQ4802
584 If you say Y here you will get support for the TI
587 This driver can also be built as a module. If so, the module
588 will be called rtc-bq4802.
590 config RTC_DRV_RP5C01
591 tristate "Ricoh RP5C01"
593 If you say yes here you get support for the Ricoh RP5C01
594 timekeeping chip. It is used in some Amiga models (e.g. A3000
597 This driver can also be built as a module. If so, the module
598 will be called rtc-rp5c01.
601 tristate "EM Microelectronic V3020"
603 If you say yes here you will get support for the
604 EM Microelectronic v3020 RTC chip.
606 This driver can also be built as a module. If so, the module
607 will be called rtc-v3020.
609 config RTC_DRV_WM831X
610 tristate "Wolfson Microelectronics WM831x RTC"
611 depends on MFD_WM831X
613 If you say yes here you will get support for the RTC subsystem
614 of the Wolfson Microelectronics WM831X series PMICs.
616 This driver can also be built as a module. If so, the module
617 will be called "rtc-wm831x".
619 config RTC_DRV_WM8350
620 tristate "Wolfson Microelectronics WM8350 RTC"
621 depends on MFD_WM8350
623 If you say yes here you will get support for the RTC subsystem
624 of the Wolfson Microelectronics WM8350.
626 This driver can also be built as a module. If so, the module
627 will be called "rtc-wm8350".
629 config RTC_DRV_PCF50633
630 depends on MFD_PCF50633
631 tristate "NXP PCF50633 RTC"
633 If you say yes here you get support for the RTC subsystem of the
634 NXP PCF50633 used in embedded systems.
636 config RTC_DRV_AB3100
637 tristate "ST-Ericsson AB3100 RTC"
638 depends on AB3100_CORE
639 default y if AB3100_CORE
641 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
642 support. This chip contains a battery- and capacitor-backed RTC.
644 config RTC_DRV_AB8500
645 tristate "ST-Ericsson AB8500 RTC"
646 depends on AB8500_CORE
648 Select this to enable the ST-Ericsson AB8500 power management IC RTC
649 support. This chip contains a battery- and capacitor-backed RTC.
651 config RTC_DRV_NUC900
652 tristate "NUC910/NUC920 RTC driver"
653 depends on RTC_CLASS && ARCH_W90X900
655 If you say yes here you get support for the RTC subsystem of the
656 NUC910/NUC920 used in embedded systems.
658 comment "on-CPU RTC drivers"
660 config RTC_DRV_DAVINCI
661 tristate "TI DaVinci RTC"
662 depends on ARCH_DAVINCI_DM365
664 If you say yes here you get support for the RTC on the
665 DaVinci platforms (DM365).
667 This driver can also be built as a module. If so, the module
668 will be called rtc-davinci.
672 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
674 Say "yes" here to support the real time clock on TI OMAP1 and
675 DA8xx/OMAP-L13x chips. This driver can also be built as a
676 module called rtc-omap.
681 This will include RTC support for Samsung SoCs. If
682 you want to include RTC support for any machine, kindly
683 select this in the respective mach-XXXX/Kconfig file.
686 tristate "Samsung S3C series SoC RTC"
687 depends on ARCH_S3C2410 || ARCH_S3C64XX || HAVE_S3C_RTC
689 RTC (Realtime Clock) driver for the clock inbuilt into the
690 Samsung S3C24XX series of SoCs. This can provide periodic
691 interrupt rates from 1Hz to 64Hz for user programs, and
694 The driver currently supports the common features on all the
695 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
698 This driver can also be build as a module. If so, the module
699 will be called rtc-s3c.
701 config RTC_DRV_EP93XX
702 tristate "Cirrus Logic EP93XX"
703 depends on ARCH_EP93XX
705 If you say yes here you get support for the
706 RTC embedded in the Cirrus Logic EP93XX processors.
708 This driver can also be built as a module. If so, the module
709 will be called rtc-ep93xx.
711 config RTC_DRV_SA1100
712 tristate "SA11x0/PXA2xx"
713 depends on ARCH_SA1100 || ARCH_PXA
715 If you say Y here you will get access to the real time clock
716 built into your SA11x0 or PXA2xx CPU.
718 To compile this driver as a module, choose M here: the
719 module will be called rtc-sa1100.
722 tristate "SuperH On-Chip RTC"
723 depends on RTC_CLASS && SUPERH && HAVE_CLK
725 Say Y here to enable support for the on-chip RTC found in
726 most SuperH processors.
728 To compile this driver as a module, choose M here: the
729 module will be called rtc-sh.
731 config RTC_DRV_VR41XX
732 tristate "NEC VR41XX"
733 depends on CPU_VR41XX
735 If you say Y here you will get access to the real time clock
736 built into your NEC VR41XX CPU.
738 To compile this driver as a module, choose M here: the
739 module will be called rtc-vr41xx.
742 tristate "ARM AMBA PL030 RTC"
745 If you say Y here you will get access to ARM AMBA
746 PrimeCell PL030 RTC found on certain ARM SOCs.
748 To compile this driver as a module, choose M here: the
749 module will be called rtc-pl030.
752 tristate "ARM AMBA PL031 RTC"
755 If you say Y here you will get access to ARM AMBA
756 PrimeCell PL031 RTC found on certain ARM SOCs.
758 To compile this driver as a module, choose M here: the
759 module will be called rtc-pl031.
761 config RTC_DRV_AT32AP700X
762 tristate "AT32AP700X series RTC"
763 depends on PLATFORM_AT32AP
765 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
766 AT32AP700x family processors.
768 config RTC_DRV_AT91RM9200
769 tristate "AT91RM9200 or some AT91SAM9 RTC"
770 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
772 Driver for the internal RTC (Realtime Clock) module found on
773 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
774 this is powered by the backup power supply.
776 config RTC_DRV_AT91SAM9
777 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
778 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
780 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
781 (Real Time Timer). These timers are powered by the backup power
782 supply (such as a small coin cell battery), but do not need to
785 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
786 dedicated RTC module and leave the RTT available for other uses.)
788 config RTC_DRV_AT91SAM9_RTT
792 prompt "RTT module Number" if ARCH_AT91SAM9263
793 depends on RTC_DRV_AT91SAM9
795 More than one RTT module is available. You can choose which
796 one will be used as an RTC. The default of zero is normally
797 OK to use, though some systems use that for non-RTC purposes.
799 config RTC_DRV_AT91SAM9_GPBR
801 range 0 3 if !ARCH_AT91SAM9263
802 range 0 15 if ARCH_AT91SAM9263
804 prompt "Backup Register Number"
805 depends on RTC_DRV_AT91SAM9
807 The RTC driver needs to use one of the General Purpose Backup
808 Registers (GPBRs) as well as the RTT. You can choose which one
809 will be used. The default of zero is normally OK to use, but
810 on some systems other software needs to use that register.
812 config RTC_DRV_AU1XXX
813 tristate "Au1xxx Counter0 RTC support"
814 depends on MIPS_ALCHEMY
816 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
817 counter) to be used as a RTC.
819 This driver can also be built as a module. If so, the module
820 will be called rtc-au1xxx.
823 tristate "Blackfin On-Chip RTC"
824 depends on BLACKFIN && !BF561
826 If you say yes here you will get support for the
827 Blackfin On-Chip Real Time Clock.
829 This driver can also be built as a module. If so, the module
830 will be called rtc-bfin.
832 config RTC_DRV_RS5C313
833 tristate "Ricoh RS5C313"
834 depends on SH_LANDISK
836 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
838 config RTC_DRV_GENERIC
839 tristate "Generic RTC support"
840 # Please consider writing a new RTC driver instead of using the generic
842 depends on PARISC || M68K || PPC || SUPERH32
844 Say Y or M here to enable RTC support on systems using the generic
845 RTC abstraction. If you do not know what you are doing, you should
849 tristate "PXA27x/PXA3xx"
852 If you say Y here you will get access to the real time clock
853 built into your PXA27x or PXA3xx CPU.
855 This RTC driver uses PXA RTC registers available since pxa27x
856 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
860 bool "SUN4V Hypervisor RTC"
863 If you say Y here you will get support for the Hypervisor
864 based RTC on SUN4V systems.
866 config RTC_DRV_STARFIRE
870 If you say Y here you will get support for the RTC found on
873 config RTC_DRV_TX4939
874 tristate "TX4939 SoC"
875 depends on SOC_TX4939
877 Driver for the internal RTC (Realtime Clock) module found on
881 tristate "Marvell SoC RTC"
882 depends on ARCH_KIRKWOOD || ARCH_DOVE
884 If you say yes here you will get support for the in-chip RTC
885 that can be found in some of Marvell's SoC devices, such as
886 the Kirkwood 88F6281 and 88F6192.
888 This driver can also be built as a module. If so, the module
889 will be called rtc-mv.
895 If you say yes here you will get support for the RTC on PS3.
897 This driver can also be built as a module. If so, the module
898 will be called rtc-ps3.
900 config RTC_DRV_COH901331
901 tristate "ST-Ericsson COH 901 331 RTC"
904 If you say Y here you will get access to ST-Ericsson
905 COH 901 331 RTC clock found in some ST-Ericsson Mobile
908 This driver can also be built as a module. If so, the module
909 will be called "rtc-coh901331".
913 tristate "Freescale STMP3xxx RTC"
914 depends on ARCH_STMP3XXX
916 If you say yes here you will get support for the onboard
919 This driver can also be built as a module. If so, the module
920 will be called rtc-stmp3xxx.
926 If you say Y here you will get support for the RTC found on
927 the PCAP2 ASIC used on some Motorola phones.
929 config RTC_DRV_MC13783
930 depends on MFD_MC13783
931 tristate "Freescale MC13783 RTC"
933 This enables support for the Freescale MC13783 PMIC RTC
935 config RTC_DRV_MPC5121
936 tristate "Freescale MPC5121 built-in RTC"
937 depends on PPC_MPC512x && RTC_CLASS
939 If you say yes here you will get support for the
940 built-in RTC MPC5121.
942 This driver can also be built as a module. If so, the module
943 will be called rtc-mpc5121.
945 config RTC_DRV_JZ4740
946 tristate "Ingenic JZ4740 SoC"
948 depends on MACH_JZ4740
950 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
953 This driver can also be buillt as a module. If so, the module
954 will be called rtc-jz4740.
956 config RTC_DRV_LPC32XX
957 depends on ARCH_LPC32XX
958 tristate "NXP LPC32XX RTC"
960 This enables support for the NXP RTC in the LPC32XX
962 This driver can also be buillt as a module. If so, the module
963 will be called rtc-lpc32xx.