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.
207 tristate "Xicor/Intersil X1205"
209 If you say yes here you get support for the
210 Xicor/Intersil X1205 RTC chip.
212 This driver can also be built as a module. If so, the module
213 will be called rtc-x1205.
215 config RTC_DRV_PCF8563
216 tristate "Philips PCF8563/Epson RTC8564"
218 If you say yes here you get support for the
219 Philips PCF8563 RTC chip. The Epson RTC8564
222 This driver can also be built as a module. If so, the module
223 will be called rtc-pcf8563.
225 config RTC_DRV_PCF8583
226 tristate "Philips PCF8583"
228 If you say yes here you get support for the Philips PCF8583
229 RTC chip found on Acorn RiscPCs. This driver supports the
230 platform specific method of retrieving the current year from
231 the RTC's SRAM. It will work on other platforms with the same
232 chip, but the year will probably have to be tweaked.
234 This driver can also be built as a module. If so, the module
235 will be called rtc-pcf8583.
237 config RTC_DRV_M41T80
238 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
240 If you say Y here you will get support for the ST M41T60
241 and M41T80 RTC chips series. Currently, the following chips are
242 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
243 M41ST85, and M41ST87.
245 This driver can also be built as a module. If so, the module
246 will be called rtc-m41t80.
248 config RTC_DRV_M41T80_WDT
249 bool "ST M41T65/M41T80 series RTC watchdog timer"
250 depends on RTC_DRV_M41T80
252 If you say Y here you will get support for the
253 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
256 tristate "TI BQ32000"
258 If you say Y here you will get support for the TI
259 BQ32000 I2C RTC chip.
261 This driver can also be built as a module. If so, the module
262 will be called rtc-bq32k.
264 config RTC_DRV_DM355EVM
265 tristate "TI DaVinci DM355 EVM RTC"
266 depends on MFD_DM355EVM_MSP
268 Supports the RTC firmware in the MSP430 on the DM355 EVM.
270 config RTC_DRV_TWL92330
271 boolean "TI TWL92330/Menelaus"
274 If you say yes here you get support for the RTC on the
275 TWL92330 "Menelaus" power management chip, used with OMAP2
276 platforms. The support is integrated with the rest of
277 the Menelaus driver; it's not separate module.
279 config RTC_DRV_TWL4030
280 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
281 depends on RTC_CLASS && TWL4030_CORE
283 If you say yes here you get support for the RTC on the
284 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
286 This driver can also be built as a module. If so, the module
287 will be called rtc-twl.
289 config RTC_DRV_S35390A
290 tristate "Seiko Instruments S-35390A"
293 If you say yes here you will get support for the Seiko
294 Instruments S-35390A.
296 This driver can also be built as a module. If so the module
297 will be called rtc-s35390a.
299 config RTC_DRV_FM3130
300 tristate "Ramtron FM3130"
302 If you say Y here you will get support for the
303 Ramtron FM3130 RTC chips.
304 Ramtron FM3130 is a chip with two separate devices inside,
305 RTC clock and FRAM. This driver provides only RTC functionality.
307 This driver can also be built as a module. If so the module
308 will be called rtc-fm3130.
310 config RTC_DRV_RX8581
311 tristate "Epson RX-8581"
313 If you say yes here you will get support for the Epson RX-8581.
315 This driver can also be built as a module. If so the module
316 will be called rtc-rx8581.
318 config RTC_DRV_RX8025
319 tristate "Epson RX-8025SA/NB"
321 If you say yes here you get support for the Epson
322 RX-8025SA/NB RTC chips.
324 This driver can also be built as a module. If so, the module
325 will be called rtc-rx8025.
329 comment "SPI RTC drivers"
333 config RTC_DRV_M41T94
336 If you say yes here you will get support for the
337 ST M41T94 SPI RTC chip.
339 This driver can also be built as a module. If so, the module
340 will be called rtc-m41t94.
342 config RTC_DRV_DS1305
343 tristate "Dallas/Maxim DS1305/DS1306"
345 Select this driver to get support for the Dallas/Maxim DS1305
346 and DS1306 real time clock chips. These support a trickle
347 charger, alarms, and NVRAM in addition to the clock.
349 This driver can also be built as a module. If so, the module
350 will be called rtc-ds1305.
352 config RTC_DRV_DS1390
353 tristate "Dallas/Maxim DS1390/93/94"
355 If you say yes here you get support for the
356 Dallas/Maxim DS1390/93/94 chips.
358 This driver only supports the RTC feature, and not other chip
359 features such as alarms and trickle charging.
361 This driver can also be built as a module. If so, the module
362 will be called rtc-ds1390.
364 config RTC_DRV_MAX6902
365 tristate "Maxim MAX6902"
367 If you say yes here you will get support for the
368 Maxim MAX6902 SPI RTC chip.
370 This driver can also be built as a module. If so, the module
371 will be called rtc-max6902.
374 tristate "Epson RTC-9701JE"
376 If you say yes here you will get support for the
377 Epson RTC-9701JE SPI RTC chip.
379 This driver can also be built as a module. If so, the module
380 will be called rtc-r9701.
382 config RTC_DRV_RS5C348
383 tristate "Ricoh RS5C348A/B"
385 If you say yes here you get support for the
386 Ricoh RS5C348A and RS5C348B RTC chips.
388 This driver can also be built as a module. If so, the module
389 will be called rtc-rs5c348.
391 config RTC_DRV_DS3234
392 tristate "Maxim/Dallas DS3234"
394 If you say yes here you get support for the
395 Maxim/Dallas DS3234 SPI RTC chip.
397 This driver can also be built as a module. If so, the module
398 will be called rtc-ds3234.
400 config RTC_DRV_PCF2123
401 tristate "NXP PCF2123"
403 If you say yes here you get support for the NXP PCF2123
406 This driver can also be built as a module. If so, the module
407 will be called rtc-pcf2123.
411 comment "Platform RTC drivers"
413 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
414 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
415 # global rtc_lock ... it's not yet just another platform_device.
418 tristate "PC-style 'CMOS'"
419 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
422 Say "yes" here to get direct support for the real time clock
423 found in every PC or ACPI-based system, and some other boards.
424 Specifically the original MC146818, compatibles like those in
425 PC south bridges, the DS12887 or M48T86, some multifunction
426 or LPC bus chips, and so on.
428 Your system will need to define the platform device used by
429 this driver, otherwise it won't be accessible. This means
430 you can safely enable this driver if you don't know whether
431 or not your board has this kind of hardware.
433 This driver can also be built as a module. If so, the module
434 will be called rtc-cmos.
436 config RTC_DRV_DS1216
437 tristate "Dallas DS1216"
440 If you say yes here you get support for the Dallas DS1216 RTC chips.
442 config RTC_DRV_DS1286
443 tristate "Dallas DS1286"
445 If you say yes here you get support for the Dallas DS1286 RTC chips.
447 config RTC_DRV_DS1302
448 tristate "Dallas DS1302"
449 depends on SH_SECUREEDGE5410
451 If you say yes here you get support for the Dallas DS1302 RTC chips.
453 config RTC_DRV_DS1511
454 tristate "Dallas DS1511"
457 If you say yes here you get support for the
458 Dallas DS1511 timekeeping/watchdog chip.
460 This driver can also be built as a module. If so, the module
461 will be called rtc-ds1511.
463 config RTC_DRV_DS1553
464 tristate "Maxim/Dallas DS1553"
466 If you say yes here you get support for the
467 Maxim/Dallas DS1553 timekeeping chip.
469 This driver can also be built as a module. If so, the module
470 will be called rtc-ds1553.
472 config RTC_DRV_DS1742
473 tristate "Maxim/Dallas DS1742/1743"
475 If you say yes here you get support for the
476 Maxim/Dallas DS1742/1743 timekeeping chip.
478 This driver can also be built as a module. If so, the module
479 will be called rtc-ds1742.
485 If you say yes here you will get support for the EFI
488 This driver can also be built as a module. If so, the module
489 will be called rtc-efi.
491 config RTC_DRV_STK17TA8
492 tristate "Simtek STK17TA8"
495 If you say yes here you get support for the
496 Simtek STK17TA8 timekeeping chip.
498 This driver can also be built as a module. If so, the module
499 will be called rtc-stk17ta8.
501 config RTC_DRV_M48T86
502 tristate "ST M48T86/Dallas DS12887"
504 If you say Y here you will get support for the
505 ST M48T86 and Dallas DS12887 RTC chips.
507 This driver can also be built as a module. If so, the module
508 will be called rtc-m48t86.
510 config RTC_DRV_M48T35
513 If you say Y here you will get support for the
516 This driver can also be built as a module, if so, the module
517 will be called "rtc-m48t35".
519 config RTC_DRV_M48T59
520 tristate "ST M48T59/M48T08/M48T02"
522 If you say Y here you will get support for the
523 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
525 These chips are usually found in Sun SPARC and UltraSPARC
528 This driver can also be built as a module, if so, the module
529 will be called "rtc-m48t59".
531 config RTC_DRV_MSM6242
532 tristate "Oki MSM6242"
534 If you say yes here you get support for the Oki MSM6242
535 timekeeping chip. It is used in some Amiga models (e.g. A2000).
537 This driver can also be built as a module. If so, the module
538 will be called rtc-msm6242.
541 tristate "Freescale IMX DryIce Real Time Clock"
545 Support for Freescale IMX DryIce RTC
547 This driver can also be built as a module, if so, the module
548 will be called "rtc-imxdi".
551 tristate "Freescale MXC Real Time Clock"
555 If you say yes here you get support for the Freescale MXC
558 This driver can also be built as a module, if so, the module
559 will be called "rtc-mxc".
561 config RTC_DRV_BQ4802
564 If you say Y here you will get support for the TI
567 This driver can also be built as a module. If so, the module
568 will be called rtc-bq4802.
570 config RTC_DRV_RP5C01
571 tristate "Ricoh RP5C01"
573 If you say yes here you get support for the Ricoh RP5C01
574 timekeeping chip. It is used in some Amiga models (e.g. A3000
577 This driver can also be built as a module. If so, the module
578 will be called rtc-rp5c01.
581 tristate "EM Microelectronic V3020"
583 If you say yes here you will get support for the
584 EM Microelectronic v3020 RTC chip.
586 This driver can also be built as a module. If so, the module
587 will be called rtc-v3020.
589 config RTC_DRV_WM831X
590 tristate "Wolfson Microelectronics WM831x RTC"
591 depends on MFD_WM831X
593 If you say yes here you will get support for the RTC subsystem
594 of the Wolfson Microelectronics WM831X series PMICs.
596 This driver can also be built as a module. If so, the module
597 will be called "rtc-wm831x".
599 config RTC_DRV_WM8350
600 tristate "Wolfson Microelectronics WM8350 RTC"
601 depends on MFD_WM8350
603 If you say yes here you will get support for the RTC subsystem
604 of the Wolfson Microelectronics WM8350.
606 This driver can also be built as a module. If so, the module
607 will be called "rtc-wm8350".
609 config RTC_DRV_PCF50633
610 depends on MFD_PCF50633
611 tristate "NXP PCF50633 RTC"
613 If you say yes here you get support for the RTC subsystem of the
614 NXP PCF50633 used in embedded systems.
616 config RTC_DRV_AB3100
617 tristate "ST-Ericsson AB3100 RTC"
618 depends on AB3100_CORE
619 default y if AB3100_CORE
621 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
622 support. This chip contains a battery- and capacitor-backed RTC.
624 config RTC_DRV_AB8500
625 tristate "ST-Ericsson AB8500 RTC"
626 depends on AB8500_CORE
628 Select this to enable the ST-Ericsson AB8500 power management IC RTC
629 support. This chip contains a battery- and capacitor-backed RTC.
631 config RTC_DRV_NUC900
632 tristate "NUC910/NUC920 RTC driver"
633 depends on RTC_CLASS && ARCH_W90X900
635 If you say yes here you get support for the RTC subsystem of the
636 NUC910/NUC920 used in embedded systems.
638 comment "on-CPU RTC drivers"
640 config RTC_DRV_DAVINCI
641 tristate "TI DaVinci RTC"
642 depends on ARCH_DAVINCI_DM365
644 If you say yes here you get support for the RTC on the
645 DaVinci platforms (DM365).
647 This driver can also be built as a module. If so, the module
648 will be called rtc-davinci.
652 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
654 Say "yes" here to support the real time clock on TI OMAP1 and
655 DA8xx/OMAP-L13x chips. This driver can also be built as a
656 module called rtc-omap.
659 tristate "Samsung S3C series SoC RTC"
660 depends on ARCH_S3C2410 || ARCH_S3C64XX
662 RTC (Realtime Clock) driver for the clock inbuilt into the
663 Samsung S3C24XX series of SoCs. This can provide periodic
664 interrupt rates from 1Hz to 64Hz for user programs, and
667 The driver currently supports the common features on all the
668 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
671 This driver can also be build as a module. If so, the module
672 will be called rtc-s3c.
674 config RTC_DRV_EP93XX
675 tristate "Cirrus Logic EP93XX"
676 depends on ARCH_EP93XX
678 If you say yes here you get support for the
679 RTC embedded in the Cirrus Logic EP93XX processors.
681 This driver can also be built as a module. If so, the module
682 will be called rtc-ep93xx.
684 config RTC_DRV_SA1100
685 tristate "SA11x0/PXA2xx"
686 depends on ARCH_SA1100 || ARCH_PXA
688 If you say Y here you will get access to the real time clock
689 built into your SA11x0 or PXA2xx CPU.
691 To compile this driver as a module, choose M here: the
692 module will be called rtc-sa1100.
695 tristate "SuperH On-Chip RTC"
696 depends on RTC_CLASS && SUPERH && HAVE_CLK
698 Say Y here to enable support for the on-chip RTC found in
699 most SuperH processors.
701 To compile this driver as a module, choose M here: the
702 module will be called rtc-sh.
704 config RTC_DRV_VR41XX
705 tristate "NEC VR41XX"
706 depends on CPU_VR41XX
708 If you say Y here you will get access to the real time clock
709 built into your NEC VR41XX CPU.
711 To compile this driver as a module, choose M here: the
712 module will be called rtc-vr41xx.
715 tristate "ARM AMBA PL030 RTC"
718 If you say Y here you will get access to ARM AMBA
719 PrimeCell PL030 RTC found on certain ARM SOCs.
721 To compile this driver as a module, choose M here: the
722 module will be called rtc-pl030.
725 tristate "ARM AMBA PL031 RTC"
728 If you say Y here you will get access to ARM AMBA
729 PrimeCell PL031 RTC found on certain ARM SOCs.
731 To compile this driver as a module, choose M here: the
732 module will be called rtc-pl031.
734 config RTC_DRV_AT32AP700X
735 tristate "AT32AP700X series RTC"
736 depends on PLATFORM_AT32AP
738 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
739 AT32AP700x family processors.
741 config RTC_DRV_AT91RM9200
742 tristate "AT91RM9200 or AT91SAM9RL"
743 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
745 Driver for the internal RTC (Realtime Clock) module found on
746 Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips
747 this is powered by the backup power supply.
749 config RTC_DRV_AT91SAM9
750 tristate "AT91SAM9x/AT91CAP9"
751 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
753 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
754 (Real Time Timer). These timers are powered by the backup power
755 supply (such as a small coin cell battery), but do not need to
758 (On AT91SAM9rl chips you probably want to use the dedicated RTC
759 module and leave the RTT available for other uses.)
761 config RTC_DRV_AT91SAM9_RTT
765 prompt "RTT module Number" if ARCH_AT91SAM9263
766 depends on RTC_DRV_AT91SAM9
768 More than one RTT module is available. You can choose which
769 one will be used as an RTC. The default of zero is normally
770 OK to use, though some systems use that for non-RTC purposes.
772 config RTC_DRV_AT91SAM9_GPBR
774 range 0 3 if !ARCH_AT91SAM9263
775 range 0 15 if ARCH_AT91SAM9263
777 prompt "Backup Register Number"
778 depends on RTC_DRV_AT91SAM9
780 The RTC driver needs to use one of the General Purpose Backup
781 Registers (GPBRs) as well as the RTT. You can choose which one
782 will be used. The default of zero is normally OK to use, but
783 on some systems other software needs to use that register.
785 config RTC_DRV_AU1XXX
786 tristate "Au1xxx Counter0 RTC support"
787 depends on MIPS_ALCHEMY
789 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
790 counter) to be used as a RTC.
792 This driver can also be built as a module. If so, the module
793 will be called rtc-au1xxx.
796 tristate "Blackfin On-Chip RTC"
797 depends on BLACKFIN && !BF561
799 If you say yes here you will get support for the
800 Blackfin On-Chip Real Time Clock.
802 This driver can also be built as a module. If so, the module
803 will be called rtc-bfin.
805 config RTC_DRV_RS5C313
806 tristate "Ricoh RS5C313"
807 depends on SH_LANDISK
809 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
811 config RTC_DRV_GENERIC
812 tristate "Generic RTC support"
813 # Please consider writing a new RTC driver instead of using the generic
815 depends on PARISC || M68K || PPC || SUPERH32
817 Say Y or M here to enable RTC support on systems using the generic
818 RTC abstraction. If you do not know what you are doing, you should
822 tristate "PXA27x/PXA3xx"
825 If you say Y here you will get access to the real time clock
826 built into your PXA27x or PXA3xx CPU.
828 This RTC driver uses PXA RTC registers available since pxa27x
829 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
833 bool "SUN4V Hypervisor RTC"
836 If you say Y here you will get support for the Hypervisor
837 based RTC on SUN4V systems.
839 config RTC_DRV_STARFIRE
843 If you say Y here you will get support for the RTC found on
846 config RTC_DRV_TX4939
847 tristate "TX4939 SoC"
848 depends on SOC_TX4939
850 Driver for the internal RTC (Realtime Clock) module found on
854 tristate "Marvell SoC RTC"
855 depends on ARCH_KIRKWOOD || ARCH_DOVE
857 If you say yes here you will get support for the in-chip RTC
858 that can be found in some of Marvell's SoC devices, such as
859 the Kirkwood 88F6281 and 88F6192.
861 This driver can also be built as a module. If so, the module
862 will be called rtc-mv.
868 If you say yes here you will get support for the RTC on PS3.
870 This driver can also be built as a module. If so, the module
871 will be called rtc-ps3.
873 config RTC_DRV_COH901331
874 tristate "ST-Ericsson COH 901 331 RTC"
877 If you say Y here you will get access to ST-Ericsson
878 COH 901 331 RTC clock found in some ST-Ericsson Mobile
881 This driver can also be built as a module. If so, the module
882 will be called "rtc-coh901331".
886 tristate "Freescale STMP3xxx RTC"
887 depends on ARCH_STMP3XXX
889 If you say yes here you will get support for the onboard
892 This driver can also be built as a module. If so, the module
893 will be called rtc-stmp3xxx.
899 If you say Y here you will get support for the RTC found on
900 the PCAP2 ASIC used on some Motorola phones.
902 config RTC_DRV_MC13783
903 depends on MFD_MC13783
904 tristate "Freescale MC13783 RTC"
906 This enables support for the Freescale MC13783 PMIC RTC
908 config RTC_DRV_MPC5121
909 tristate "Freescale MPC5121 built-in RTC"
910 depends on PPC_MPC512x && RTC_CLASS
912 If you say yes here you will get support for the
913 built-in RTC MPC5121.
915 This driver can also be built as a module. If so, the module
916 will be called rtc-mpc5121.
918 config RTC_DRV_JZ4740
919 tristate "Ingenic JZ4740 SoC"
921 depends on MACH_JZ4740
923 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
926 This driver can also be buillt as a module. If so, the module
927 will be called rtc-jz4740.