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.
112 config RTC_INTF_ALARM
113 bool "Android alarm driver"
117 Provides non-wakeup and rtc backed wakeup alarms based on rtc or
118 elapsed realtime, and a non-wakeup alarm on the monotonic clock.
119 Also provides an interface to set the wall time which must be used
120 for elapsed realtime to work.
122 config RTC_INTF_ALARM_DEV
123 bool "Android alarm device"
124 depends on RTC_INTF_ALARM
127 Exports the alarm interface to user-space.
131 tristate "Test driver/device"
133 If you say yes here you get support for the
134 RTC test driver. It's a software RTC which can be
135 used to test the RTC subsystem APIs. It gets
136 the time from the system clock.
137 You want this driver only if you are doing development
138 on the RTC subsystem. Please read the source code
141 This driver can also be built as a module. If so, the module
142 will be called rtc-test.
144 comment "I2C RTC drivers"
149 config RTC_DRV_DS1307
150 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
152 If you say yes here you get support for various compatible RTC
153 chips (often with battery backup) connected with I2C. This driver
154 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
155 EPSON RX-8025 and probably other chips. In some cases the RTC
156 must already have been initialized (by manufacturing or a
159 The first seven registers on these chips hold an RTC, and other
160 registers may add features such as NVRAM, a trickle charger for
161 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
162 sysfs, but other chip features may not be available.
164 This driver can also be built as a module. If so, the module
165 will be called rtc-ds1307.
167 config RTC_DRV_DS1374
168 tristate "Dallas/Maxim DS1374"
169 depends on RTC_CLASS && I2C
171 If you say yes here you get support for Dallas Semiconductor
172 DS1374 real-time clock chips. If an interrupt is associated
173 with the device, the alarm functionality is supported.
175 This driver can also be built as a module. If so, the module
176 will be called rtc-ds1374.
178 config RTC_DRV_DS1672
179 tristate "Dallas/Maxim DS1672"
181 If you say yes here you get support for the
182 Dallas/Maxim DS1672 timekeeping chip.
184 This driver can also be built as a module. If so, the module
185 will be called rtc-ds1672.
187 config RTC_DRV_DS3232
188 tristate "Dallas/Maxim DS3232"
189 depends on RTC_CLASS && I2C
191 If you say yes here you get support for Dallas Semiconductor
192 DS3232 real-time clock chips.
194 This driver can also be built as a module. If so, the module
195 will be called rtc-ds3232.
197 config RTC_DRV_MAX6900
198 tristate "Maxim MAX6900"
200 If you say yes here you will get support for the
201 Maxim MAX6900 I2C RTC chip.
203 This driver can also be built as a module. If so, the module
204 will be called rtc-max6900.
206 config RTC_DRV_MAX8925
207 tristate "Maxim MAX8925"
208 depends on MFD_MAX8925
210 If you say yes here you will get support for the
211 RTC of Maxim MAX8925 PMIC.
213 This driver can also be built as a module. If so, the module
214 will be called rtc-max8925.
216 config RTC_DRV_RS5C372
217 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
219 If you say yes here you get support for the
220 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
222 This driver can also be built as a module. If so, the module
223 will be called rtc-rs5c372.
225 config RTC_DRV_ISL1208
226 tristate "Intersil ISL1208"
228 If you say yes here you get support for the
229 Intersil ISL1208 RTC chip.
231 This driver can also be built as a module. If so, the module
232 will be called rtc-isl1208.
234 config RTC_DRV_ISL12022
235 tristate "Intersil ISL12022"
237 If you say yes here you get support for the
238 Intersil ISL12022 RTC chip.
240 This driver can also be built as a module. If so, the module
241 will be called rtc-isl12022.
244 tristate "Xicor/Intersil X1205"
246 If you say yes here you get support for the
247 Xicor/Intersil X1205 RTC chip.
249 This driver can also be built as a module. If so, the module
250 will be called rtc-x1205.
252 config RTC_DRV_PCF8563
253 tristate "Philips PCF8563/Epson RTC8564"
255 If you say yes here you get support for the
256 Philips PCF8563 RTC chip. The Epson RTC8564
259 This driver can also be built as a module. If so, the module
260 will be called rtc-pcf8563.
262 config RTC_DRV_PCF8583
263 tristate "Philips PCF8583"
265 If you say yes here you get support for the Philips PCF8583
266 RTC chip found on Acorn RiscPCs. This driver supports the
267 platform specific method of retrieving the current year from
268 the RTC's SRAM. It will work on other platforms with the same
269 chip, but the year will probably have to be tweaked.
271 This driver can also be built as a module. If so, the module
272 will be called rtc-pcf8583.
274 config RTC_DRV_M41T80
275 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
277 If you say Y here you will get support for the ST M41T60
278 and M41T80 RTC chips series. Currently, the following chips are
279 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
280 M41ST85, and M41ST87.
282 This driver can also be built as a module. If so, the module
283 will be called rtc-m41t80.
285 config RTC_DRV_M41T80_WDT
286 bool "ST M41T65/M41T80 series RTC watchdog timer"
287 depends on RTC_DRV_M41T80
289 If you say Y here you will get support for the
290 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
293 tristate "TI BQ32000"
295 If you say Y here you will get support for the TI
296 BQ32000 I2C RTC chip.
298 This driver can also be built as a module. If so, the module
299 will be called rtc-bq32k.
301 config RTC_DRV_DM355EVM
302 tristate "TI DaVinci DM355 EVM RTC"
303 depends on MFD_DM355EVM_MSP
305 Supports the RTC firmware in the MSP430 on the DM355 EVM.
307 config RTC_DRV_TPS6586X
308 tristate "TI TPS6586X RTC"
312 This driver supports TPS6586X RTC
314 config RTC_DRV_TWL92330
315 boolean "TI TWL92330/Menelaus"
318 If you say yes here you get support for the RTC on the
319 TWL92330 "Menelaus" power management chip, used with OMAP2
320 platforms. The support is integrated with the rest of
321 the Menelaus driver; it's not separate module.
323 config RTC_DRV_TWL4030
324 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
325 depends on RTC_CLASS && TWL4030_CORE
327 If you say yes here you get support for the RTC on the
328 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
330 This driver can also be built as a module. If so, the module
331 will be called rtc-twl.
333 config RTC_DRV_S35390A
334 tristate "Seiko Instruments S-35390A"
337 If you say yes here you will get support for the Seiko
338 Instruments S-35390A.
340 This driver can also be built as a module. If so the module
341 will be called rtc-s35390a.
343 config RTC_DRV_FM3130
344 tristate "Ramtron FM3130"
346 If you say Y here you will get support for the
347 Ramtron FM3130 RTC chips.
348 Ramtron FM3130 is a chip with two separate devices inside,
349 RTC clock and FRAM. This driver provides only RTC functionality.
351 This driver can also be built as a module. If so the module
352 will be called rtc-fm3130.
354 config RTC_DRV_RX8581
355 tristate "Epson RX-8581"
357 If you say yes here you will get support for the Epson RX-8581.
359 This driver can also be built as a module. If so the module
360 will be called rtc-rx8581.
362 config RTC_DRV_RX8025
363 tristate "Epson RX-8025SA/NB"
365 If you say yes here you get support for the Epson
366 RX-8025SA/NB RTC chips.
368 This driver can also be built as a module. If so, the module
369 will be called rtc-rx8025.
373 comment "SPI RTC drivers"
377 config RTC_DRV_M41T94
380 If you say yes here you will get support for the
381 ST M41T94 SPI RTC chip.
383 This driver can also be built as a module. If so, the module
384 will be called rtc-m41t94.
386 config RTC_DRV_DS1305
387 tristate "Dallas/Maxim DS1305/DS1306"
389 Select this driver to get support for the Dallas/Maxim DS1305
390 and DS1306 real time clock chips. These support a trickle
391 charger, alarms, and NVRAM in addition to the clock.
393 This driver can also be built as a module. If so, the module
394 will be called rtc-ds1305.
396 config RTC_DRV_DS1390
397 tristate "Dallas/Maxim DS1390/93/94"
399 If you say yes here you get support for the
400 Dallas/Maxim DS1390/93/94 chips.
402 This driver only supports the RTC feature, and not other chip
403 features such as alarms and trickle charging.
405 This driver can also be built as a module. If so, the module
406 will be called rtc-ds1390.
408 config RTC_DRV_MAX6902
409 tristate "Maxim MAX6902"
411 If you say yes here you will get support for the
412 Maxim MAX6902 SPI RTC chip.
414 This driver can also be built as a module. If so, the module
415 will be called rtc-max6902.
418 tristate "Epson RTC-9701JE"
420 If you say yes here you will get support for the
421 Epson RTC-9701JE SPI RTC chip.
423 This driver can also be built as a module. If so, the module
424 will be called rtc-r9701.
426 config RTC_DRV_RS5C348
427 tristate "Ricoh RS5C348A/B"
429 If you say yes here you get support for the
430 Ricoh RS5C348A and RS5C348B RTC chips.
432 This driver can also be built as a module. If so, the module
433 will be called rtc-rs5c348.
435 config RTC_DRV_DS3234
436 tristate "Maxim/Dallas DS3234"
438 If you say yes here you get support for the
439 Maxim/Dallas DS3234 SPI RTC chip.
441 This driver can also be built as a module. If so, the module
442 will be called rtc-ds3234.
444 config RTC_DRV_PCF2123
445 tristate "NXP PCF2123"
447 If you say yes here you get support for the NXP PCF2123
450 This driver can also be built as a module. If so, the module
451 will be called rtc-pcf2123.
455 comment "Platform RTC drivers"
457 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
458 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
459 # global rtc_lock ... it's not yet just another platform_device.
462 tristate "PC-style 'CMOS'"
463 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
466 Say "yes" here to get direct support for the real time clock
467 found in every PC or ACPI-based system, and some other boards.
468 Specifically the original MC146818, compatibles like those in
469 PC south bridges, the DS12887 or M48T86, some multifunction
470 or LPC bus chips, and so on.
472 Your system will need to define the platform device used by
473 this driver, otherwise it won't be accessible. This means
474 you can safely enable this driver if you don't know whether
475 or not your board has this kind of hardware.
477 This driver can also be built as a module. If so, the module
478 will be called rtc-cmos.
480 config RTC_DRV_DS1216
481 tristate "Dallas DS1216"
484 If you say yes here you get support for the Dallas DS1216 RTC chips.
486 config RTC_DRV_DS1286
487 tristate "Dallas DS1286"
489 If you say yes here you get support for the Dallas DS1286 RTC chips.
491 config RTC_DRV_DS1302
492 tristate "Dallas DS1302"
493 depends on SH_SECUREEDGE5410
495 If you say yes here you get support for the Dallas DS1302 RTC chips.
497 config RTC_DRV_DS1511
498 tristate "Dallas DS1511"
501 If you say yes here you get support for the
502 Dallas DS1511 timekeeping/watchdog chip.
504 This driver can also be built as a module. If so, the module
505 will be called rtc-ds1511.
507 config RTC_DRV_DS1553
508 tristate "Maxim/Dallas DS1553"
510 If you say yes here you get support for the
511 Maxim/Dallas DS1553 timekeeping chip.
513 This driver can also be built as a module. If so, the module
514 will be called rtc-ds1553.
516 config RTC_DRV_DS1742
517 tristate "Maxim/Dallas DS1742/1743"
519 If you say yes here you get support for the
520 Maxim/Dallas DS1742/1743 timekeeping chip.
522 This driver can also be built as a module. If so, the module
523 will be called rtc-ds1742.
529 If you say yes here you will get support for the EFI
532 This driver can also be built as a module. If so, the module
533 will be called rtc-efi.
535 config RTC_DRV_STK17TA8
536 tristate "Simtek STK17TA8"
539 If you say yes here you get support for the
540 Simtek STK17TA8 timekeeping chip.
542 This driver can also be built as a module. If so, the module
543 will be called rtc-stk17ta8.
545 config RTC_DRV_M48T86
546 tristate "ST M48T86/Dallas DS12887"
548 If you say Y here you will get support for the
549 ST M48T86 and Dallas DS12887 RTC chips.
551 This driver can also be built as a module. If so, the module
552 will be called rtc-m48t86.
554 config RTC_DRV_M48T35
557 If you say Y here you will get support for the
560 This driver can also be built as a module, if so, the module
561 will be called "rtc-m48t35".
563 config RTC_DRV_M48T59
564 tristate "ST M48T59/M48T08/M48T02"
566 If you say Y here you will get support for the
567 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
569 These chips are usually found in Sun SPARC and UltraSPARC
572 This driver can also be built as a module, if so, the module
573 will be called "rtc-m48t59".
575 config RTC_DRV_MSM6242
576 tristate "Oki MSM6242"
578 If you say yes here you get support for the Oki MSM6242
579 timekeeping chip. It is used in some Amiga models (e.g. A2000).
581 This driver can also be built as a module. If so, the module
582 will be called rtc-msm6242.
585 tristate "Freescale IMX DryIce Real Time Clock"
589 Support for Freescale IMX DryIce RTC
591 This driver can also be built as a module, if so, the module
592 will be called "rtc-imxdi".
595 tristate "Freescale MXC Real Time Clock"
599 If you say yes here you get support for the Freescale MXC
602 This driver can also be built as a module, if so, the module
603 will be called "rtc-mxc".
605 config RTC_DRV_BQ4802
608 If you say Y here you will get support for the TI
611 This driver can also be built as a module. If so, the module
612 will be called rtc-bq4802.
614 config RTC_DRV_RP5C01
615 tristate "Ricoh RP5C01"
617 If you say yes here you get support for the Ricoh RP5C01
618 timekeeping chip. It is used in some Amiga models (e.g. A3000
621 This driver can also be built as a module. If so, the module
622 will be called rtc-rp5c01.
625 tristate "EM Microelectronic V3020"
627 If you say yes here you will get support for the
628 EM Microelectronic v3020 RTC chip.
630 This driver can also be built as a module. If so, the module
631 will be called rtc-v3020.
633 config RTC_DRV_WM831X
634 tristate "Wolfson Microelectronics WM831x RTC"
635 depends on MFD_WM831X
637 If you say yes here you will get support for the RTC subsystem
638 of the Wolfson Microelectronics WM831X series PMICs.
640 This driver can also be built as a module. If so, the module
641 will be called "rtc-wm831x".
643 config RTC_DRV_WM8350
644 tristate "Wolfson Microelectronics WM8350 RTC"
645 depends on MFD_WM8350
647 If you say yes here you will get support for the RTC subsystem
648 of the Wolfson Microelectronics WM8350.
650 This driver can also be built as a module. If so, the module
651 will be called "rtc-wm8350".
653 config RTC_DRV_PCF50633
654 depends on MFD_PCF50633
655 tristate "NXP PCF50633 RTC"
657 If you say yes here you get support for the RTC subsystem of the
658 NXP PCF50633 used in embedded systems.
660 config RTC_DRV_AB3100
661 tristate "ST-Ericsson AB3100 RTC"
662 depends on AB3100_CORE
663 default y if AB3100_CORE
665 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
666 support. This chip contains a battery- and capacitor-backed RTC.
668 config RTC_DRV_AB8500
669 tristate "ST-Ericsson AB8500 RTC"
670 depends on AB8500_CORE
672 Select this to enable the ST-Ericsson AB8500 power management IC RTC
673 support. This chip contains a battery- and capacitor-backed RTC.
675 config RTC_DRV_NUC900
676 tristate "NUC910/NUC920 RTC driver"
677 depends on RTC_CLASS && ARCH_W90X900
679 If you say yes here you get support for the RTC subsystem of the
680 NUC910/NUC920 used in embedded systems.
682 comment "on-CPU RTC drivers"
684 config RTC_DRV_DAVINCI
685 tristate "TI DaVinci RTC"
686 depends on ARCH_DAVINCI_DM365
688 If you say yes here you get support for the RTC on the
689 DaVinci platforms (DM365).
691 This driver can also be built as a module. If so, the module
692 will be called rtc-davinci.
696 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
698 Say "yes" here to support the real time clock on TI OMAP1 and
699 DA8xx/OMAP-L13x chips. This driver can also be built as a
700 module called rtc-omap.
705 This will include RTC support for Samsung SoCs. If
706 you want to include RTC support for any machine, kindly
707 select this in the respective mach-XXXX/Kconfig file.
710 tristate "Samsung S3C series SoC RTC"
711 depends on ARCH_S3C2410 || ARCH_S3C64XX || HAVE_S3C_RTC
713 RTC (Realtime Clock) driver for the clock inbuilt into the
714 Samsung S3C24XX series of SoCs. This can provide periodic
715 interrupt rates from 1Hz to 64Hz for user programs, and
718 The driver currently supports the common features on all the
719 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
722 This driver can also be build as a module. If so, the module
723 will be called rtc-s3c.
725 config RTC_DRV_EP93XX
726 tristate "Cirrus Logic EP93XX"
727 depends on ARCH_EP93XX
729 If you say yes here you get support for the
730 RTC embedded in the Cirrus Logic EP93XX processors.
732 This driver can also be built as a module. If so, the module
733 will be called rtc-ep93xx.
735 config RTC_DRV_SA1100
736 tristate "SA11x0/PXA2xx"
737 depends on ARCH_SA1100 || ARCH_PXA
739 If you say Y here you will get access to the real time clock
740 built into your SA11x0 or PXA2xx CPU.
742 To compile this driver as a module, choose M here: the
743 module will be called rtc-sa1100.
746 tristate "SuperH On-Chip RTC"
747 depends on RTC_CLASS && SUPERH && HAVE_CLK
749 Say Y here to enable support for the on-chip RTC found in
750 most SuperH processors.
752 To compile this driver as a module, choose M here: the
753 module will be called rtc-sh.
755 config RTC_DRV_VR41XX
756 tristate "NEC VR41XX"
757 depends on CPU_VR41XX
759 If you say Y here you will get access to the real time clock
760 built into your NEC VR41XX CPU.
762 To compile this driver as a module, choose M here: the
763 module will be called rtc-vr41xx.
766 tristate "ARM AMBA PL030 RTC"
769 If you say Y here you will get access to ARM AMBA
770 PrimeCell PL030 RTC found on certain ARM SOCs.
772 To compile this driver as a module, choose M here: the
773 module will be called rtc-pl030.
776 tristate "ARM AMBA PL031 RTC"
779 If you say Y here you will get access to ARM AMBA
780 PrimeCell PL031 RTC found on certain ARM SOCs.
782 To compile this driver as a module, choose M here: the
783 module will be called rtc-pl031.
785 config RTC_DRV_AT32AP700X
786 tristate "AT32AP700X series RTC"
787 depends on PLATFORM_AT32AP
789 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
790 AT32AP700x family processors.
792 config RTC_DRV_AT91RM9200
793 tristate "AT91RM9200 or AT91SAM9RL"
794 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
796 Driver for the internal RTC (Realtime Clock) module found on
797 Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips
798 this is powered by the backup power supply.
800 config RTC_DRV_AT91SAM9
801 tristate "AT91SAM9x/AT91CAP9"
802 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
804 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
805 (Real Time Timer). These timers are powered by the backup power
806 supply (such as a small coin cell battery), but do not need to
809 (On AT91SAM9rl chips you probably want to use the dedicated RTC
810 module and leave the RTT available for other uses.)
812 config RTC_DRV_AT91SAM9_RTT
816 prompt "RTT module Number" if ARCH_AT91SAM9263
817 depends on RTC_DRV_AT91SAM9
819 More than one RTT module is available. You can choose which
820 one will be used as an RTC. The default of zero is normally
821 OK to use, though some systems use that for non-RTC purposes.
823 config RTC_DRV_AT91SAM9_GPBR
825 range 0 3 if !ARCH_AT91SAM9263
826 range 0 15 if ARCH_AT91SAM9263
828 prompt "Backup Register Number"
829 depends on RTC_DRV_AT91SAM9
831 The RTC driver needs to use one of the General Purpose Backup
832 Registers (GPBRs) as well as the RTT. You can choose which one
833 will be used. The default of zero is normally OK to use, but
834 on some systems other software needs to use that register.
836 config RTC_DRV_AU1XXX
837 tristate "Au1xxx Counter0 RTC support"
838 depends on MIPS_ALCHEMY
840 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
841 counter) to be used as a RTC.
843 This driver can also be built as a module. If so, the module
844 will be called rtc-au1xxx.
847 tristate "Blackfin On-Chip RTC"
848 depends on BLACKFIN && !BF561
850 If you say yes here you will get support for the
851 Blackfin On-Chip Real Time Clock.
853 This driver can also be built as a module. If so, the module
854 will be called rtc-bfin.
856 config RTC_DRV_RS5C313
857 tristate "Ricoh RS5C313"
858 depends on SH_LANDISK
860 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
862 config RTC_DRV_GENERIC
863 tristate "Generic RTC support"
864 # Please consider writing a new RTC driver instead of using the generic
866 depends on PARISC || M68K || PPC || SUPERH32
868 Say Y or M here to enable RTC support on systems using the generic
869 RTC abstraction. If you do not know what you are doing, you should
873 tristate "PXA27x/PXA3xx"
876 If you say Y here you will get access to the real time clock
877 built into your PXA27x or PXA3xx CPU.
879 This RTC driver uses PXA RTC registers available since pxa27x
880 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
884 bool "SUN4V Hypervisor RTC"
887 If you say Y here you will get support for the Hypervisor
888 based RTC on SUN4V systems.
890 config RTC_DRV_STARFIRE
894 If you say Y here you will get support for the RTC found on
897 config RTC_DRV_TX4939
898 tristate "TX4939 SoC"
899 depends on SOC_TX4939
901 Driver for the internal RTC (Realtime Clock) module found on
905 tristate "Marvell SoC RTC"
906 depends on ARCH_KIRKWOOD || ARCH_DOVE
908 If you say yes here you will get support for the in-chip RTC
909 that can be found in some of Marvell's SoC devices, such as
910 the Kirkwood 88F6281 and 88F6192.
912 This driver can also be built as a module. If so, the module
913 will be called rtc-mv.
919 If you say yes here you will get support for the RTC on PS3.
921 This driver can also be built as a module. If so, the module
922 will be called rtc-ps3.
924 config RTC_DRV_COH901331
925 tristate "ST-Ericsson COH 901 331 RTC"
928 If you say Y here you will get access to ST-Ericsson
929 COH 901 331 RTC clock found in some ST-Ericsson Mobile
932 This driver can also be built as a module. If so, the module
933 will be called "rtc-coh901331".
937 tristate "Freescale STMP3xxx RTC"
938 depends on ARCH_STMP3XXX
940 If you say yes here you will get support for the onboard
943 This driver can also be built as a module. If so, the module
944 will be called rtc-stmp3xxx.
950 If you say Y here you will get support for the RTC found on
951 the PCAP2 ASIC used on some Motorola phones.
953 config RTC_DRV_MC13783
954 depends on MFD_MC13783
955 tristate "Freescale MC13783 RTC"
957 This enables support for the Freescale MC13783 PMIC RTC
959 config RTC_DRV_MPC5121
960 tristate "Freescale MPC5121 built-in RTC"
961 depends on PPC_MPC512x && RTC_CLASS
963 If you say yes here you will get support for the
964 built-in RTC MPC5121.
966 This driver can also be built as a module. If so, the module
967 will be called rtc-mpc5121.
969 config RTC_DRV_JZ4740
970 tristate "Ingenic JZ4740 SoC"
972 depends on MACH_JZ4740
974 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
977 This driver can also be buillt as a module. If so, the module
978 will be called rtc-jz4740.