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_MAX6900
170 tristate "Maxim MAX6900"
172 If you say yes here you will get support for the
173 Maxim MAX6900 I2C RTC chip.
175 This driver can also be built as a module. If so, the module
176 will be called rtc-max6900.
178 config RTC_DRV_MAX8925
179 tristate "Maxim MAX8925"
180 depends on MFD_MAX8925
182 If you say yes here you will get support for the
183 RTC of Maxim MAX8925 PMIC.
185 This driver can also be built as a module. If so, the module
186 will be called rtc-max8925.
188 config RTC_DRV_RS5C372
189 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
191 If you say yes here you get support for the
192 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
194 This driver can also be built as a module. If so, the module
195 will be called rtc-rs5c372.
197 config RTC_DRV_ISL1208
198 tristate "Intersil ISL1208"
200 If you say yes here you get support for the
201 Intersil ISL1208 RTC chip.
203 This driver can also be built as a module. If so, the module
204 will be called rtc-isl1208.
206 config RTC_DRV_ISL12022
207 tristate "Intersil ISL12022"
209 If you say yes here you get support for the
210 Intersil ISL12022 RTC chip.
212 This driver can also be built as a module. If so, the module
213 will be called rtc-isl12022.
216 tristate "Xicor/Intersil X1205"
218 If you say yes here you get support for the
219 Xicor/Intersil X1205 RTC chip.
221 This driver can also be built as a module. If so, the module
222 will be called rtc-x1205.
224 config RTC_DRV_PCF8563
225 tristate "Philips PCF8563/Epson RTC8564"
227 If you say yes here you get support for the
228 Philips PCF8563 RTC chip. The Epson RTC8564
231 This driver can also be built as a module. If so, the module
232 will be called rtc-pcf8563.
234 config RTC_DRV_PCF8583
235 tristate "Philips PCF8583"
237 If you say yes here you get support for the Philips PCF8583
238 RTC chip found on Acorn RiscPCs. This driver supports the
239 platform specific method of retrieving the current year from
240 the RTC's SRAM. It will work on other platforms with the same
241 chip, but the year will probably have to be tweaked.
243 This driver can also be built as a module. If so, the module
244 will be called rtc-pcf8583.
246 config RTC_DRV_M41T80
247 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
249 If you say Y here you will get support for the ST M41T60
250 and M41T80 RTC chips series. Currently, the following chips are
251 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
252 M41ST85, and M41ST87.
254 This driver can also be built as a module. If so, the module
255 will be called rtc-m41t80.
257 config RTC_DRV_M41T80_WDT
258 bool "ST M41T65/M41T80 series RTC watchdog timer"
259 depends on RTC_DRV_M41T80
261 If you say Y here you will get support for the
262 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
265 tristate "TI BQ32000"
267 If you say Y here you will get support for the TI
268 BQ32000 I2C RTC chip.
270 This driver can also be built as a module. If so, the module
271 will be called rtc-bq32k.
273 config RTC_DRV_DM355EVM
274 tristate "TI DaVinci DM355 EVM RTC"
275 depends on MFD_DM355EVM_MSP
277 Supports the RTC firmware in the MSP430 on the DM355 EVM.
279 config RTC_DRV_TWL92330
280 boolean "TI TWL92330/Menelaus"
283 If you say yes here you get support for the RTC on the
284 TWL92330 "Menelaus" power management chip, used with OMAP2
285 platforms. The support is integrated with the rest of
286 the Menelaus driver; it's not separate module.
288 config RTC_DRV_TWL4030
289 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
290 depends on RTC_CLASS && TWL4030_CORE
292 If you say yes here you get support for the RTC on the
293 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
295 This driver can also be built as a module. If so, the module
296 will be called rtc-twl.
298 config RTC_DRV_S35390A
299 tristate "Seiko Instruments S-35390A"
302 If you say yes here you will get support for the Seiko
303 Instruments S-35390A.
305 This driver can also be built as a module. If so the module
306 will be called rtc-s35390a.
308 config RTC_DRV_FM3130
309 tristate "Ramtron FM3130"
311 If you say Y here you will get support for the
312 Ramtron FM3130 RTC chips.
313 Ramtron FM3130 is a chip with two separate devices inside,
314 RTC clock and FRAM. This driver provides only RTC functionality.
316 This driver can also be built as a module. If so the module
317 will be called rtc-fm3130.
319 config RTC_DRV_RX8581
320 tristate "Epson RX-8581"
322 If you say yes here you will get support for the Epson RX-8581.
324 This driver can also be built as a module. If so the module
325 will be called rtc-rx8581.
327 config RTC_DRV_RX8025
328 tristate "Epson RX-8025SA/NB"
330 If you say yes here you get support for the Epson
331 RX-8025SA/NB RTC chips.
333 This driver can also be built as a module. If so, the module
334 will be called rtc-rx8025.
338 comment "SPI RTC drivers"
342 config RTC_DRV_M41T94
345 If you say yes here you will get support for the
346 ST M41T94 SPI RTC chip.
348 This driver can also be built as a module. If so, the module
349 will be called rtc-m41t94.
351 config RTC_DRV_DS1305
352 tristate "Dallas/Maxim DS1305/DS1306"
354 Select this driver to get support for the Dallas/Maxim DS1305
355 and DS1306 real time clock chips. These support a trickle
356 charger, alarms, and NVRAM in addition to the clock.
358 This driver can also be built as a module. If so, the module
359 will be called rtc-ds1305.
361 config RTC_DRV_DS1390
362 tristate "Dallas/Maxim DS1390/93/94"
364 If you say yes here you get support for the
365 Dallas/Maxim DS1390/93/94 chips.
367 This driver only supports the RTC feature, and not other chip
368 features such as alarms and trickle charging.
370 This driver can also be built as a module. If so, the module
371 will be called rtc-ds1390.
373 config RTC_DRV_MAX6902
374 tristate "Maxim MAX6902"
376 If you say yes here you will get support for the
377 Maxim MAX6902 SPI RTC chip.
379 This driver can also be built as a module. If so, the module
380 will be called rtc-max6902.
383 tristate "Epson RTC-9701JE"
385 If you say yes here you will get support for the
386 Epson RTC-9701JE SPI RTC chip.
388 This driver can also be built as a module. If so, the module
389 will be called rtc-r9701.
391 config RTC_DRV_RS5C348
392 tristate "Ricoh RS5C348A/B"
394 If you say yes here you get support for the
395 Ricoh RS5C348A and RS5C348B RTC chips.
397 This driver can also be built as a module. If so, the module
398 will be called rtc-rs5c348.
400 config RTC_DRV_DS3234
401 tristate "Maxim/Dallas DS3234"
403 If you say yes here you get support for the
404 Maxim/Dallas DS3234 SPI RTC chip.
406 This driver can also be built as a module. If so, the module
407 will be called rtc-ds3234.
409 config RTC_DRV_PCF2123
410 tristate "NXP PCF2123"
412 If you say yes here you get support for the NXP PCF2123
415 This driver can also be built as a module. If so, the module
416 will be called rtc-pcf2123.
420 comment "Platform RTC drivers"
422 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
423 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
424 # global rtc_lock ... it's not yet just another platform_device.
427 tristate "PC-style 'CMOS'"
428 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
431 Say "yes" here to get direct support for the real time clock
432 found in every PC or ACPI-based system, and some other boards.
433 Specifically the original MC146818, compatibles like those in
434 PC south bridges, the DS12887 or M48T86, some multifunction
435 or LPC bus chips, and so on.
437 Your system will need to define the platform device used by
438 this driver, otherwise it won't be accessible. This means
439 you can safely enable this driver if you don't know whether
440 or not your board has this kind of hardware.
442 This driver can also be built as a module. If so, the module
443 will be called rtc-cmos.
445 config RTC_DRV_DS1216
446 tristate "Dallas DS1216"
449 If you say yes here you get support for the Dallas DS1216 RTC chips.
451 config RTC_DRV_DS1286
452 tristate "Dallas DS1286"
454 If you say yes here you get support for the Dallas DS1286 RTC chips.
456 config RTC_DRV_DS1302
457 tristate "Dallas DS1302"
458 depends on SH_SECUREEDGE5410
460 If you say yes here you get support for the Dallas DS1302 RTC chips.
462 config RTC_DRV_DS1511
463 tristate "Dallas DS1511"
466 If you say yes here you get support for the
467 Dallas DS1511 timekeeping/watchdog chip.
469 This driver can also be built as a module. If so, the module
470 will be called rtc-ds1511.
472 config RTC_DRV_DS1553
473 tristate "Maxim/Dallas DS1553"
475 If you say yes here you get support for the
476 Maxim/Dallas DS1553 timekeeping chip.
478 This driver can also be built as a module. If so, the module
479 will be called rtc-ds1553.
481 config RTC_DRV_DS1742
482 tristate "Maxim/Dallas DS1742/1743"
484 If you say yes here you get support for the
485 Maxim/Dallas DS1742/1743 timekeeping chip.
487 This driver can also be built as a module. If so, the module
488 will be called rtc-ds1742.
494 If you say yes here you will get support for the EFI
497 This driver can also be built as a module. If so, the module
498 will be called rtc-efi.
500 config RTC_DRV_STK17TA8
501 tristate "Simtek STK17TA8"
504 If you say yes here you get support for the
505 Simtek STK17TA8 timekeeping chip.
507 This driver can also be built as a module. If so, the module
508 will be called rtc-stk17ta8.
510 config RTC_DRV_M48T86
511 tristate "ST M48T86/Dallas DS12887"
513 If you say Y here you will get support for the
514 ST M48T86 and Dallas DS12887 RTC chips.
516 This driver can also be built as a module. If so, the module
517 will be called rtc-m48t86.
519 config RTC_DRV_M48T35
522 If you say Y here you will get support for the
525 This driver can also be built as a module, if so, the module
526 will be called "rtc-m48t35".
528 config RTC_DRV_M48T59
529 tristate "ST M48T59/M48T08/M48T02"
531 If you say Y here you will get support for the
532 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
534 These chips are usually found in Sun SPARC and UltraSPARC
537 This driver can also be built as a module, if so, the module
538 will be called "rtc-m48t59".
540 config RTC_DRV_MSM6242
541 tristate "Oki MSM6242"
543 If you say yes here you get support for the Oki MSM6242
544 timekeeping chip. It is used in some Amiga models (e.g. A2000).
546 This driver can also be built as a module. If so, the module
547 will be called rtc-msm6242.
550 tristate "Freescale IMX DryIce Real Time Clock"
554 Support for Freescale IMX DryIce RTC
556 This driver can also be built as a module, if so, the module
557 will be called "rtc-imxdi".
560 tristate "Freescale MXC Real Time Clock"
564 If you say yes here you get support for the Freescale MXC
567 This driver can also be built as a module, if so, the module
568 will be called "rtc-mxc".
570 config RTC_DRV_BQ4802
573 If you say Y here you will get support for the TI
576 This driver can also be built as a module. If so, the module
577 will be called rtc-bq4802.
579 config RTC_DRV_RP5C01
580 tristate "Ricoh RP5C01"
582 If you say yes here you get support for the Ricoh RP5C01
583 timekeeping chip. It is used in some Amiga models (e.g. A3000
586 This driver can also be built as a module. If so, the module
587 will be called rtc-rp5c01.
590 tristate "EM Microelectronic V3020"
592 If you say yes here you will get support for the
593 EM Microelectronic v3020 RTC chip.
595 This driver can also be built as a module. If so, the module
596 will be called rtc-v3020.
598 config RTC_DRV_WM831X
599 tristate "Wolfson Microelectronics WM831x RTC"
600 depends on MFD_WM831X
602 If you say yes here you will get support for the RTC subsystem
603 of the Wolfson Microelectronics WM831X series PMICs.
605 This driver can also be built as a module. If so, the module
606 will be called "rtc-wm831x".
608 config RTC_DRV_WM8350
609 tristate "Wolfson Microelectronics WM8350 RTC"
610 depends on MFD_WM8350
612 If you say yes here you will get support for the RTC subsystem
613 of the Wolfson Microelectronics WM8350.
615 This driver can also be built as a module. If so, the module
616 will be called "rtc-wm8350".
618 config RTC_DRV_PCF50633
619 depends on MFD_PCF50633
620 tristate "NXP PCF50633 RTC"
622 If you say yes here you get support for the RTC subsystem of the
623 NXP PCF50633 used in embedded systems.
625 config RTC_DRV_AB3100
626 tristate "ST-Ericsson AB3100 RTC"
627 depends on AB3100_CORE
628 default y if AB3100_CORE
630 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
631 support. This chip contains a battery- and capacitor-backed RTC.
633 config RTC_DRV_AB8500
634 tristate "ST-Ericsson AB8500 RTC"
635 depends on AB8500_CORE
637 Select this to enable the ST-Ericsson AB8500 power management IC RTC
638 support. This chip contains a battery- and capacitor-backed RTC.
640 config RTC_DRV_NUC900
641 tristate "NUC910/NUC920 RTC driver"
642 depends on RTC_CLASS && ARCH_W90X900
644 If you say yes here you get support for the RTC subsystem of the
645 NUC910/NUC920 used in embedded systems.
647 comment "on-CPU RTC drivers"
649 config RTC_DRV_DAVINCI
650 tristate "TI DaVinci RTC"
651 depends on ARCH_DAVINCI_DM365
653 If you say yes here you get support for the RTC on the
654 DaVinci platforms (DM365).
656 This driver can also be built as a module. If so, the module
657 will be called rtc-davinci.
661 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
663 Say "yes" here to support the real time clock on TI OMAP1 and
664 DA8xx/OMAP-L13x chips. This driver can also be built as a
665 module called rtc-omap.
668 tristate "Samsung S3C series SoC RTC"
669 depends on ARCH_S3C2410 || ARCH_S3C64XX
671 RTC (Realtime Clock) driver for the clock inbuilt into the
672 Samsung S3C24XX series of SoCs. This can provide periodic
673 interrupt rates from 1Hz to 64Hz for user programs, and
676 The driver currently supports the common features on all the
677 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
680 This driver can also be build as a module. If so, the module
681 will be called rtc-s3c.
683 config RTC_DRV_EP93XX
684 tristate "Cirrus Logic EP93XX"
685 depends on ARCH_EP93XX
687 If you say yes here you get support for the
688 RTC embedded in the Cirrus Logic EP93XX processors.
690 This driver can also be built as a module. If so, the module
691 will be called rtc-ep93xx.
693 config RTC_DRV_SA1100
694 tristate "SA11x0/PXA2xx"
695 depends on ARCH_SA1100 || ARCH_PXA
697 If you say Y here you will get access to the real time clock
698 built into your SA11x0 or PXA2xx CPU.
700 To compile this driver as a module, choose M here: the
701 module will be called rtc-sa1100.
704 tristate "SuperH On-Chip RTC"
705 depends on RTC_CLASS && SUPERH && HAVE_CLK
707 Say Y here to enable support for the on-chip RTC found in
708 most SuperH processors.
710 To compile this driver as a module, choose M here: the
711 module will be called rtc-sh.
713 config RTC_DRV_VR41XX
714 tristate "NEC VR41XX"
715 depends on CPU_VR41XX
717 If you say Y here you will get access to the real time clock
718 built into your NEC VR41XX CPU.
720 To compile this driver as a module, choose M here: the
721 module will be called rtc-vr41xx.
724 tristate "ARM AMBA PL030 RTC"
727 If you say Y here you will get access to ARM AMBA
728 PrimeCell PL030 RTC found on certain ARM SOCs.
730 To compile this driver as a module, choose M here: the
731 module will be called rtc-pl030.
734 tristate "ARM AMBA PL031 RTC"
737 If you say Y here you will get access to ARM AMBA
738 PrimeCell PL031 RTC found on certain ARM SOCs.
740 To compile this driver as a module, choose M here: the
741 module will be called rtc-pl031.
743 config RTC_DRV_AT32AP700X
744 tristate "AT32AP700X series RTC"
745 depends on PLATFORM_AT32AP
747 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
748 AT32AP700x family processors.
750 config RTC_DRV_AT91RM9200
751 tristate "AT91RM9200 or AT91SAM9RL"
752 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
754 Driver for the internal RTC (Realtime Clock) module found on
755 Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips
756 this is powered by the backup power supply.
758 config RTC_DRV_AT91SAM9
759 tristate "AT91SAM9x/AT91CAP9"
760 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
762 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
763 (Real Time Timer). These timers are powered by the backup power
764 supply (such as a small coin cell battery), but do not need to
767 (On AT91SAM9rl chips you probably want to use the dedicated RTC
768 module and leave the RTT available for other uses.)
770 config RTC_DRV_AT91SAM9_RTT
774 prompt "RTT module Number" if ARCH_AT91SAM9263
775 depends on RTC_DRV_AT91SAM9
777 More than one RTT module is available. You can choose which
778 one will be used as an RTC. The default of zero is normally
779 OK to use, though some systems use that for non-RTC purposes.
781 config RTC_DRV_AT91SAM9_GPBR
783 range 0 3 if !ARCH_AT91SAM9263
784 range 0 15 if ARCH_AT91SAM9263
786 prompt "Backup Register Number"
787 depends on RTC_DRV_AT91SAM9
789 The RTC driver needs to use one of the General Purpose Backup
790 Registers (GPBRs) as well as the RTT. You can choose which one
791 will be used. The default of zero is normally OK to use, but
792 on some systems other software needs to use that register.
794 config RTC_DRV_AU1XXX
795 tristate "Au1xxx Counter0 RTC support"
796 depends on MIPS_ALCHEMY
798 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
799 counter) to be used as a RTC.
801 This driver can also be built as a module. If so, the module
802 will be called rtc-au1xxx.
805 tristate "Blackfin On-Chip RTC"
806 depends on BLACKFIN && !BF561
808 If you say yes here you will get support for the
809 Blackfin On-Chip Real Time Clock.
811 This driver can also be built as a module. If so, the module
812 will be called rtc-bfin.
814 config RTC_DRV_RS5C313
815 tristate "Ricoh RS5C313"
816 depends on SH_LANDISK
818 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
820 config RTC_DRV_GENERIC
821 tristate "Generic RTC support"
822 # Please consider writing a new RTC driver instead of using the generic
824 depends on PARISC || M68K || PPC || SUPERH32
826 Say Y or M here to enable RTC support on systems using the generic
827 RTC abstraction. If you do not know what you are doing, you should
831 tristate "PXA27x/PXA3xx"
834 If you say Y here you will get access to the real time clock
835 built into your PXA27x or PXA3xx CPU.
837 This RTC driver uses PXA RTC registers available since pxa27x
838 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
842 bool "SUN4V Hypervisor RTC"
845 If you say Y here you will get support for the Hypervisor
846 based RTC on SUN4V systems.
848 config RTC_DRV_STARFIRE
852 If you say Y here you will get support for the RTC found on
855 config RTC_DRV_TX4939
856 tristate "TX4939 SoC"
857 depends on SOC_TX4939
859 Driver for the internal RTC (Realtime Clock) module found on
863 tristate "Marvell SoC RTC"
864 depends on ARCH_KIRKWOOD || ARCH_DOVE
866 If you say yes here you will get support for the in-chip RTC
867 that can be found in some of Marvell's SoC devices, such as
868 the Kirkwood 88F6281 and 88F6192.
870 This driver can also be built as a module. If so, the module
871 will be called rtc-mv.
877 If you say yes here you will get support for the RTC on PS3.
879 This driver can also be built as a module. If so, the module
880 will be called rtc-ps3.
882 config RTC_DRV_COH901331
883 tristate "ST-Ericsson COH 901 331 RTC"
886 If you say Y here you will get access to ST-Ericsson
887 COH 901 331 RTC clock found in some ST-Ericsson Mobile
890 This driver can also be built as a module. If so, the module
891 will be called "rtc-coh901331".
895 tristate "Freescale STMP3xxx RTC"
896 depends on ARCH_STMP3XXX
898 If you say yes here you will get support for the onboard
901 This driver can also be built as a module. If so, the module
902 will be called rtc-stmp3xxx.
908 If you say Y here you will get support for the RTC found on
909 the PCAP2 ASIC used on some Motorola phones.
911 config RTC_DRV_MC13783
912 depends on MFD_MC13783
913 tristate "Freescale MC13783 RTC"
915 This enables support for the Freescale MC13783 PMIC RTC
917 config RTC_DRV_MPC5121
918 tristate "Freescale MPC5121 built-in RTC"
919 depends on PPC_MPC512x && RTC_CLASS
921 If you say yes here you will get support for the
922 built-in RTC MPC5121.
924 This driver can also be built as a module. If so, the module
925 will be called rtc-mpc5121.
927 config RTC_DRV_JZ4740
928 tristate "Ingenic JZ4740 SoC"
930 depends on MACH_JZ4740
932 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
935 This driver can also be buillt as a module. If so, the module
936 will be called rtc-jz4740.