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.
176 This driver can also be built as a module. If so, the module
177 will be called rtc-ds3232.
179 config RTC_DRV_MAX6900
180 tristate "Maxim MAX6900"
182 If you say yes here you will get support for the
183 Maxim MAX6900 I2C RTC chip.
185 This driver can also be built as a module. If so, the module
186 will be called rtc-max6900.
188 config RTC_DRV_MAX8925
189 tristate "Maxim MAX8925"
190 depends on MFD_MAX8925
192 If you say yes here you will get support for the
193 RTC of Maxim MAX8925 PMIC.
195 This driver can also be built as a module. If so, the module
196 will be called rtc-max8925.
198 config RTC_DRV_RS5C372
199 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
201 If you say yes here you get support for the
202 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
204 This driver can also be built as a module. If so, the module
205 will be called rtc-rs5c372.
207 config RTC_DRV_ISL1208
208 tristate "Intersil ISL1208"
210 If you say yes here you get support for the
211 Intersil ISL1208 RTC chip.
213 This driver can also be built as a module. If so, the module
214 will be called rtc-isl1208.
216 config RTC_DRV_ISL12022
217 tristate "Intersil ISL12022"
219 If you say yes here you get support for the
220 Intersil ISL12022 RTC chip.
222 This driver can also be built as a module. If so, the module
223 will be called rtc-isl12022.
226 tristate "Xicor/Intersil X1205"
228 If you say yes here you get support for the
229 Xicor/Intersil X1205 RTC chip.
231 This driver can also be built as a module. If so, the module
232 will be called rtc-x1205.
234 config RTC_DRV_PCF8563
235 tristate "Philips PCF8563/Epson RTC8564"
237 If you say yes here you get support for the
238 Philips PCF8563 RTC chip. The Epson RTC8564
241 This driver can also be built as a module. If so, the module
242 will be called rtc-pcf8563.
244 config RTC_DRV_PCF8583
245 tristate "Philips PCF8583"
247 If you say yes here you get support for the Philips PCF8583
248 RTC chip found on Acorn RiscPCs. This driver supports the
249 platform specific method of retrieving the current year from
250 the RTC's SRAM. It will work on other platforms with the same
251 chip, but the year will probably have to be tweaked.
253 This driver can also be built as a module. If so, the module
254 will be called rtc-pcf8583.
256 config RTC_DRV_M41T80
257 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
259 If you say Y here you will get support for the ST M41T60
260 and M41T80 RTC chips series. Currently, the following chips are
261 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
262 M41ST85, and M41ST87.
264 This driver can also be built as a module. If so, the module
265 will be called rtc-m41t80.
267 config RTC_DRV_M41T80_WDT
268 bool "ST M41T65/M41T80 series RTC watchdog timer"
269 depends on RTC_DRV_M41T80
271 If you say Y here you will get support for the
272 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
275 tristate "TI BQ32000"
277 If you say Y here you will get support for the TI
278 BQ32000 I2C RTC chip.
280 This driver can also be built as a module. If so, the module
281 will be called rtc-bq32k.
283 config RTC_DRV_DM355EVM
284 tristate "TI DaVinci DM355 EVM RTC"
285 depends on MFD_DM355EVM_MSP
287 Supports the RTC firmware in the MSP430 on the DM355 EVM.
289 config RTC_DRV_TWL92330
290 boolean "TI TWL92330/Menelaus"
293 If you say yes here you get support for the RTC on the
294 TWL92330 "Menelaus" power management chip, used with OMAP2
295 platforms. The support is integrated with the rest of
296 the Menelaus driver; it's not separate module.
298 config RTC_DRV_TWL4030
299 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
300 depends on RTC_CLASS && TWL4030_CORE
302 If you say yes here you get support for the RTC on the
303 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
305 This driver can also be built as a module. If so, the module
306 will be called rtc-twl.
308 config RTC_DRV_S35390A
309 tristate "Seiko Instruments S-35390A"
312 If you say yes here you will get support for the Seiko
313 Instruments S-35390A.
315 This driver can also be built as a module. If so the module
316 will be called rtc-s35390a.
318 config RTC_DRV_FM3130
319 tristate "Ramtron FM3130"
321 If you say Y here you will get support for the
322 Ramtron FM3130 RTC chips.
323 Ramtron FM3130 is a chip with two separate devices inside,
324 RTC clock and FRAM. This driver provides only RTC functionality.
326 This driver can also be built as a module. If so the module
327 will be called rtc-fm3130.
329 config RTC_DRV_RX8581
330 tristate "Epson RX-8581"
332 If you say yes here you will get support for the Epson RX-8581.
334 This driver can also be built as a module. If so the module
335 will be called rtc-rx8581.
337 config RTC_DRV_RX8025
338 tristate "Epson RX-8025SA/NB"
340 If you say yes here you get support for the Epson
341 RX-8025SA/NB RTC chips.
343 This driver can also be built as a module. If so, the module
344 will be called rtc-rx8025.
348 comment "SPI RTC drivers"
352 config RTC_DRV_M41T94
355 If you say yes here you will get support for the
356 ST M41T94 SPI RTC chip.
358 This driver can also be built as a module. If so, the module
359 will be called rtc-m41t94.
361 config RTC_DRV_DS1305
362 tristate "Dallas/Maxim DS1305/DS1306"
364 Select this driver to get support for the Dallas/Maxim DS1305
365 and DS1306 real time clock chips. These support a trickle
366 charger, alarms, and NVRAM in addition to the clock.
368 This driver can also be built as a module. If so, the module
369 will be called rtc-ds1305.
371 config RTC_DRV_DS1390
372 tristate "Dallas/Maxim DS1390/93/94"
374 If you say yes here you get support for the
375 Dallas/Maxim DS1390/93/94 chips.
377 This driver only supports the RTC feature, and not other chip
378 features such as alarms and trickle charging.
380 This driver can also be built as a module. If so, the module
381 will be called rtc-ds1390.
383 config RTC_DRV_MAX6902
384 tristate "Maxim MAX6902"
386 If you say yes here you will get support for the
387 Maxim MAX6902 SPI RTC chip.
389 This driver can also be built as a module. If so, the module
390 will be called rtc-max6902.
393 tristate "Epson RTC-9701JE"
395 If you say yes here you will get support for the
396 Epson RTC-9701JE SPI RTC chip.
398 This driver can also be built as a module. If so, the module
399 will be called rtc-r9701.
401 config RTC_DRV_RS5C348
402 tristate "Ricoh RS5C348A/B"
404 If you say yes here you get support for the
405 Ricoh RS5C348A and RS5C348B RTC chips.
407 This driver can also be built as a module. If so, the module
408 will be called rtc-rs5c348.
410 config RTC_DRV_DS3234
411 tristate "Maxim/Dallas DS3234"
413 If you say yes here you get support for the
414 Maxim/Dallas DS3234 SPI RTC chip.
416 This driver can also be built as a module. If so, the module
417 will be called rtc-ds3234.
419 config RTC_DRV_PCF2123
420 tristate "NXP PCF2123"
422 If you say yes here you get support for the NXP PCF2123
425 This driver can also be built as a module. If so, the module
426 will be called rtc-pcf2123.
430 comment "Platform RTC drivers"
432 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
433 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
434 # global rtc_lock ... it's not yet just another platform_device.
437 tristate "PC-style 'CMOS'"
438 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
441 Say "yes" here to get direct support for the real time clock
442 found in every PC or ACPI-based system, and some other boards.
443 Specifically the original MC146818, compatibles like those in
444 PC south bridges, the DS12887 or M48T86, some multifunction
445 or LPC bus chips, and so on.
447 Your system will need to define the platform device used by
448 this driver, otherwise it won't be accessible. This means
449 you can safely enable this driver if you don't know whether
450 or not your board has this kind of hardware.
452 This driver can also be built as a module. If so, the module
453 will be called rtc-cmos.
455 config RTC_DRV_DS1216
456 tristate "Dallas DS1216"
459 If you say yes here you get support for the Dallas DS1216 RTC chips.
461 config RTC_DRV_DS1286
462 tristate "Dallas DS1286"
464 If you say yes here you get support for the Dallas DS1286 RTC chips.
466 config RTC_DRV_DS1302
467 tristate "Dallas DS1302"
468 depends on SH_SECUREEDGE5410
470 If you say yes here you get support for the Dallas DS1302 RTC chips.
472 config RTC_DRV_DS1511
473 tristate "Dallas DS1511"
476 If you say yes here you get support for the
477 Dallas DS1511 timekeeping/watchdog chip.
479 This driver can also be built as a module. If so, the module
480 will be called rtc-ds1511.
482 config RTC_DRV_DS1553
483 tristate "Maxim/Dallas DS1553"
485 If you say yes here you get support for the
486 Maxim/Dallas DS1553 timekeeping chip.
488 This driver can also be built as a module. If so, the module
489 will be called rtc-ds1553.
491 config RTC_DRV_DS1742
492 tristate "Maxim/Dallas DS1742/1743"
494 If you say yes here you get support for the
495 Maxim/Dallas DS1742/1743 timekeeping chip.
497 This driver can also be built as a module. If so, the module
498 will be called rtc-ds1742.
504 If you say yes here you will get support for the EFI
507 This driver can also be built as a module. If so, the module
508 will be called rtc-efi.
510 config RTC_DRV_STK17TA8
511 tristate "Simtek STK17TA8"
514 If you say yes here you get support for the
515 Simtek STK17TA8 timekeeping chip.
517 This driver can also be built as a module. If so, the module
518 will be called rtc-stk17ta8.
520 config RTC_DRV_M48T86
521 tristate "ST M48T86/Dallas DS12887"
523 If you say Y here you will get support for the
524 ST M48T86 and Dallas DS12887 RTC chips.
526 This driver can also be built as a module. If so, the module
527 will be called rtc-m48t86.
529 config RTC_DRV_M48T35
532 If you say Y here you will get support for the
535 This driver can also be built as a module, if so, the module
536 will be called "rtc-m48t35".
538 config RTC_DRV_M48T59
539 tristate "ST M48T59/M48T08/M48T02"
541 If you say Y here you will get support for the
542 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
544 These chips are usually found in Sun SPARC and UltraSPARC
547 This driver can also be built as a module, if so, the module
548 will be called "rtc-m48t59".
550 config RTC_DRV_MSM6242
551 tristate "Oki MSM6242"
553 If you say yes here you get support for the Oki MSM6242
554 timekeeping chip. It is used in some Amiga models (e.g. A2000).
556 This driver can also be built as a module. If so, the module
557 will be called rtc-msm6242.
560 tristate "Freescale IMX DryIce Real Time Clock"
564 Support for Freescale IMX DryIce RTC
566 This driver can also be built as a module, if so, the module
567 will be called "rtc-imxdi".
570 tristate "Freescale MXC Real Time Clock"
574 If you say yes here you get support for the Freescale MXC
577 This driver can also be built as a module, if so, the module
578 will be called "rtc-mxc".
580 config RTC_DRV_BQ4802
583 If you say Y here you will get support for the TI
586 This driver can also be built as a module. If so, the module
587 will be called rtc-bq4802.
589 config RTC_DRV_RP5C01
590 tristate "Ricoh RP5C01"
592 If you say yes here you get support for the Ricoh RP5C01
593 timekeeping chip. It is used in some Amiga models (e.g. A3000
596 This driver can also be built as a module. If so, the module
597 will be called rtc-rp5c01.
600 tristate "EM Microelectronic V3020"
602 If you say yes here you will get support for the
603 EM Microelectronic v3020 RTC chip.
605 This driver can also be built as a module. If so, the module
606 will be called rtc-v3020.
608 config RTC_DRV_WM831X
609 tristate "Wolfson Microelectronics WM831x RTC"
610 depends on MFD_WM831X
612 If you say yes here you will get support for the RTC subsystem
613 of the Wolfson Microelectronics WM831X series PMICs.
615 This driver can also be built as a module. If so, the module
616 will be called "rtc-wm831x".
618 config RTC_DRV_WM8350
619 tristate "Wolfson Microelectronics WM8350 RTC"
620 depends on MFD_WM8350
622 If you say yes here you will get support for the RTC subsystem
623 of the Wolfson Microelectronics WM8350.
625 This driver can also be built as a module. If so, the module
626 will be called "rtc-wm8350".
628 config RTC_DRV_PCF50633
629 depends on MFD_PCF50633
630 tristate "NXP PCF50633 RTC"
632 If you say yes here you get support for the RTC subsystem of the
633 NXP PCF50633 used in embedded systems.
635 config RTC_DRV_AB3100
636 tristate "ST-Ericsson AB3100 RTC"
637 depends on AB3100_CORE
638 default y if AB3100_CORE
640 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
641 support. This chip contains a battery- and capacitor-backed RTC.
643 config RTC_DRV_AB8500
644 tristate "ST-Ericsson AB8500 RTC"
645 depends on AB8500_CORE
647 Select this to enable the ST-Ericsson AB8500 power management IC RTC
648 support. This chip contains a battery- and capacitor-backed RTC.
650 config RTC_DRV_NUC900
651 tristate "NUC910/NUC920 RTC driver"
652 depends on RTC_CLASS && ARCH_W90X900
654 If you say yes here you get support for the RTC subsystem of the
655 NUC910/NUC920 used in embedded systems.
657 comment "on-CPU RTC drivers"
659 config RTC_DRV_DAVINCI
660 tristate "TI DaVinci RTC"
661 depends on ARCH_DAVINCI_DM365
663 If you say yes here you get support for the RTC on the
664 DaVinci platforms (DM365).
666 This driver can also be built as a module. If so, the module
667 will be called rtc-davinci.
671 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
673 Say "yes" here to support the real time clock on TI OMAP1 and
674 DA8xx/OMAP-L13x chips. This driver can also be built as a
675 module called rtc-omap.
678 tristate "Samsung S3C series SoC RTC"
679 depends on ARCH_S3C2410 || ARCH_S3C64XX
681 RTC (Realtime Clock) driver for the clock inbuilt into the
682 Samsung S3C24XX series of SoCs. This can provide periodic
683 interrupt rates from 1Hz to 64Hz for user programs, and
686 The driver currently supports the common features on all the
687 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
690 This driver can also be build as a module. If so, the module
691 will be called rtc-s3c.
693 config RTC_DRV_EP93XX
694 tristate "Cirrus Logic EP93XX"
695 depends on ARCH_EP93XX
697 If you say yes here you get support for the
698 RTC embedded in the Cirrus Logic EP93XX processors.
700 This driver can also be built as a module. If so, the module
701 will be called rtc-ep93xx.
703 config RTC_DRV_SA1100
704 tristate "SA11x0/PXA2xx"
705 depends on ARCH_SA1100 || ARCH_PXA
707 If you say Y here you will get access to the real time clock
708 built into your SA11x0 or PXA2xx CPU.
710 To compile this driver as a module, choose M here: the
711 module will be called rtc-sa1100.
714 tristate "SuperH On-Chip RTC"
715 depends on RTC_CLASS && SUPERH && HAVE_CLK
717 Say Y here to enable support for the on-chip RTC found in
718 most SuperH processors.
720 To compile this driver as a module, choose M here: the
721 module will be called rtc-sh.
723 config RTC_DRV_VR41XX
724 tristate "NEC VR41XX"
725 depends on CPU_VR41XX
727 If you say Y here you will get access to the real time clock
728 built into your NEC VR41XX CPU.
730 To compile this driver as a module, choose M here: the
731 module will be called rtc-vr41xx.
734 tristate "ARM AMBA PL030 RTC"
737 If you say Y here you will get access to ARM AMBA
738 PrimeCell PL030 RTC found on certain ARM SOCs.
740 To compile this driver as a module, choose M here: the
741 module will be called rtc-pl030.
744 tristate "ARM AMBA PL031 RTC"
747 If you say Y here you will get access to ARM AMBA
748 PrimeCell PL031 RTC found on certain ARM SOCs.
750 To compile this driver as a module, choose M here: the
751 module will be called rtc-pl031.
753 config RTC_DRV_AT32AP700X
754 tristate "AT32AP700X series RTC"
755 depends on PLATFORM_AT32AP
757 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
758 AT32AP700x family processors.
760 config RTC_DRV_AT91RM9200
761 tristate "AT91RM9200 or AT91SAM9RL"
762 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
764 Driver for the internal RTC (Realtime Clock) module found on
765 Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips
766 this is powered by the backup power supply.
768 config RTC_DRV_AT91SAM9
769 tristate "AT91SAM9x/AT91CAP9"
770 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
772 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
773 (Real Time Timer). These timers are powered by the backup power
774 supply (such as a small coin cell battery), but do not need to
777 (On AT91SAM9rl chips you probably want to use the dedicated RTC
778 module and leave the RTT available for other uses.)
780 config RTC_DRV_AT91SAM9_RTT
784 prompt "RTT module Number" if ARCH_AT91SAM9263
785 depends on RTC_DRV_AT91SAM9
787 More than one RTT module is available. You can choose which
788 one will be used as an RTC. The default of zero is normally
789 OK to use, though some systems use that for non-RTC purposes.
791 config RTC_DRV_AT91SAM9_GPBR
793 range 0 3 if !ARCH_AT91SAM9263
794 range 0 15 if ARCH_AT91SAM9263
796 prompt "Backup Register Number"
797 depends on RTC_DRV_AT91SAM9
799 The RTC driver needs to use one of the General Purpose Backup
800 Registers (GPBRs) as well as the RTT. You can choose which one
801 will be used. The default of zero is normally OK to use, but
802 on some systems other software needs to use that register.
804 config RTC_DRV_AU1XXX
805 tristate "Au1xxx Counter0 RTC support"
806 depends on MIPS_ALCHEMY
808 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
809 counter) to be used as a RTC.
811 This driver can also be built as a module. If so, the module
812 will be called rtc-au1xxx.
815 tristate "Blackfin On-Chip RTC"
816 depends on BLACKFIN && !BF561
818 If you say yes here you will get support for the
819 Blackfin On-Chip Real Time Clock.
821 This driver can also be built as a module. If so, the module
822 will be called rtc-bfin.
824 config RTC_DRV_RS5C313
825 tristate "Ricoh RS5C313"
826 depends on SH_LANDISK
828 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
830 config RTC_DRV_GENERIC
831 tristate "Generic RTC support"
832 # Please consider writing a new RTC driver instead of using the generic
834 depends on PARISC || M68K || PPC || SUPERH32
836 Say Y or M here to enable RTC support on systems using the generic
837 RTC abstraction. If you do not know what you are doing, you should
841 tristate "PXA27x/PXA3xx"
844 If you say Y here you will get access to the real time clock
845 built into your PXA27x or PXA3xx CPU.
847 This RTC driver uses PXA RTC registers available since pxa27x
848 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
852 bool "SUN4V Hypervisor RTC"
855 If you say Y here you will get support for the Hypervisor
856 based RTC on SUN4V systems.
858 config RTC_DRV_STARFIRE
862 If you say Y here you will get support for the RTC found on
865 config RTC_DRV_TX4939
866 tristate "TX4939 SoC"
867 depends on SOC_TX4939
869 Driver for the internal RTC (Realtime Clock) module found on
873 tristate "Marvell SoC RTC"
874 depends on ARCH_KIRKWOOD || ARCH_DOVE
876 If you say yes here you will get support for the in-chip RTC
877 that can be found in some of Marvell's SoC devices, such as
878 the Kirkwood 88F6281 and 88F6192.
880 This driver can also be built as a module. If so, the module
881 will be called rtc-mv.
887 If you say yes here you will get support for the RTC on PS3.
889 This driver can also be built as a module. If so, the module
890 will be called rtc-ps3.
892 config RTC_DRV_COH901331
893 tristate "ST-Ericsson COH 901 331 RTC"
896 If you say Y here you will get access to ST-Ericsson
897 COH 901 331 RTC clock found in some ST-Ericsson Mobile
900 This driver can also be built as a module. If so, the module
901 will be called "rtc-coh901331".
905 tristate "Freescale STMP3xxx RTC"
906 depends on ARCH_STMP3XXX
908 If you say yes here you will get support for the onboard
911 This driver can also be built as a module. If so, the module
912 will be called rtc-stmp3xxx.
918 If you say Y here you will get support for the RTC found on
919 the PCAP2 ASIC used on some Motorola phones.
921 config RTC_DRV_MC13783
922 depends on MFD_MC13783
923 tristate "Freescale MC13783 RTC"
925 This enables support for the Freescale MC13783 PMIC RTC
927 config RTC_DRV_MPC5121
928 tristate "Freescale MPC5121 built-in RTC"
929 depends on PPC_MPC512x && RTC_CLASS
931 If you say yes here you will get support for the
932 built-in RTC MPC5121.
934 This driver can also be built as a module. If so, the module
935 will be called rtc-mpc5121.
937 config RTC_DRV_JZ4740
938 tristate "Ingenic JZ4740 SoC"
940 depends on MACH_JZ4740
942 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
945 This driver can also be buillt as a module. If so, the module
946 will be called rtc-jz4740.