2 # RTC class/drivers configuration
11 depends on !S390 && !UML
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.
21 bool "Set system time from RTC on startup and resume"
23 depends on !HAS_PERSISTENT_CLOCK
25 If you say yes here, the system time (wall clock) will be set using
26 the value read from a specified RTC device. This is useful to avoid
27 unnecessary fsck runs at boot time, and to network better.
30 bool "Set the RTC time based on NTP synchronization"
32 depends on !HAS_PERSISTENT_CLOCK
34 If you say yes here, the system time (wall clock) will be stored
35 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
36 minutes if userspace reports synchronized NTP status.
38 config RTC_HCTOSYS_DEVICE
39 string "RTC used to set the system time"
40 depends on RTC_HCTOSYS = y || RTC_SYSTOHC = y
43 The RTC device that will be used to (re)initialize the system
44 clock, usually rtc0. Initialization is done when the system
45 starts up, and when it resumes from a low power state. This
46 device should record time in UTC, since the kernel won't do
49 The driver for this RTC device must be loaded before late_initcall
50 functions run, so it must usually be statically linked.
52 This clock should be battery-backed, so that it reads the correct
53 time when the system boots from a power-off state. Otherwise, your
54 system will need an external clock source (like an NTP server).
56 If the clock you specify here is not battery backed, it may still
57 be useful to reinitialize system time when resuming from system
58 sleep states. Do not specify an RTC here unless it stays powered
59 during all this system's supported sleep states.
62 bool "RTC debug support"
64 Say yes here to enable debugging support in the RTC framework
65 and individual RTC drivers.
67 comment "RTC interfaces"
70 boolean "/sys/class/rtc/rtcN (sysfs)"
74 Say yes here if you want to use your RTCs using sysfs interfaces,
75 /sys/class/rtc/rtc0 through /sys/.../rtcN.
80 boolean "/proc/driver/rtc (procfs for rtcN)"
84 Say yes here if you want to use your system clock RTC through
85 the proc interface, /proc/driver/rtc.
86 Other RTCs will not be available through that API.
87 If there is no RTC for the system clock, then the first RTC(rtc0)
93 boolean "/dev/rtcN (character devices)"
96 Say yes here if you want to use your RTCs using the /dev
97 interfaces, which "udev" sets up as /dev/rtc0 through
100 You may want to set up a symbolic link so one of these
101 can be accessed as /dev/rtc, which is a name
102 expected by "hwclock" and some other programs. Recent
103 versions of "udev" are known to set up the symlink for you.
107 config RTC_INTF_DEV_UIE_EMUL
108 bool "RTC UIE emulation on dev interface"
109 depends on RTC_INTF_DEV
111 Provides an emulation for RTC_UIE if the underlying rtc chip
112 driver does not expose RTC_UIE ioctls. Those requests generate
113 once-per-second update interrupts, used for synchronization.
115 The emulation code will read the time from the hardware
116 clock several times per second, please enable this option
117 only if you know that you really need it.
120 tristate "Test driver/device"
122 If you say yes here you get support for the
123 RTC test driver. It's a software RTC which can be
124 used to test the RTC subsystem APIs. It gets
125 the time from the system clock.
126 You want this driver only if you are doing development
127 on the RTC subsystem. Please read the source code
130 This driver can also be built as a module. If so, the module
131 will be called rtc-test.
133 comment "I2C RTC drivers"
138 config RTC_DRV_88PM860X
139 tristate "Marvell 88PM860x"
140 depends on I2C && MFD_88PM860X
142 If you say yes here you get support for RTC function in Marvell
145 This driver can also be built as a module. If so, the module
146 will be called rtc-88pm860x.
148 config RTC_DRV_88PM80X
149 tristate "Marvell 88PM80x"
150 depends on I2C && MFD_88PM800
152 If you say yes here you get support for RTC function in Marvell
155 This driver can also be built as a module. If so, the module
156 will be called rtc-88pm80x.
158 config RTC_DRV_DS1307
159 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
161 If you say yes here you get support for various compatible RTC
162 chips (often with battery backup) connected with I2C. This driver
163 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
164 EPSON RX-8025 and probably other chips. In some cases the RTC
165 must already have been initialized (by manufacturing or a
168 The first seven registers on these chips hold an RTC, and other
169 registers may add features such as NVRAM, a trickle charger for
170 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
171 sysfs, but other chip features may not be available.
173 This driver can also be built as a module. If so, the module
174 will be called rtc-ds1307.
176 config RTC_DRV_DS1374
177 tristate "Dallas/Maxim DS1374"
180 If you say yes here you get support for Dallas Semiconductor
181 DS1374 real-time clock chips. If an interrupt is associated
182 with the device, the alarm functionality is supported.
184 This driver can also be built as a module. If so, the module
185 will be called rtc-ds1374.
187 config RTC_DRV_DS1672
188 tristate "Dallas/Maxim DS1672"
190 If you say yes here you get support for the
191 Dallas/Maxim DS1672 timekeeping chip.
193 This driver can also be built as a module. If so, the module
194 will be called rtc-ds1672.
196 config RTC_DRV_DS3232
197 tristate "Dallas/Maxim DS3232"
200 If you say yes here you get support for Dallas Semiconductor
201 DS3232 real-time clock chips. If an interrupt is associated
202 with the device, the alarm functionality is supported.
204 This driver can also be built as a module. If so, the module
205 will be called rtc-ds3232.
207 config RTC_DRV_MAX6900
208 tristate "Maxim MAX6900"
210 If you say yes here you will get support for the
211 Maxim MAX6900 I2C RTC chip.
213 This driver can also be built as a module. If so, the module
214 will be called rtc-max6900.
216 config RTC_DRV_MAX8907
217 tristate "Maxim MAX8907"
218 depends on MFD_MAX8907
220 If you say yes here you will get support for the
221 RTC of Maxim MAX8907 PMIC.
223 This driver can also be built as a module. If so, the module
224 will be called rtc-max8907.
226 config RTC_DRV_MAX8925
227 tristate "Maxim MAX8925"
228 depends on MFD_MAX8925
230 If you say yes here you will get support for the
231 RTC of Maxim MAX8925 PMIC.
233 This driver can also be built as a module. If so, the module
234 will be called rtc-max8925.
236 config RTC_DRV_MAX8998
237 tristate "Maxim MAX8998"
238 depends on MFD_MAX8998
240 If you say yes here you will get support for the
241 RTC of Maxim MAX8998 PMIC.
243 This driver can also be built as a module. If so, the module
244 will be called rtc-max8998.
246 config RTC_DRV_RS5C372
247 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
249 If you say yes here you get support for the
250 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
252 This driver can also be built as a module. If so, the module
253 will be called rtc-rs5c372.
255 config RTC_DRV_ISL1208
256 tristate "Intersil ISL1208"
258 If you say yes here you get support for the
259 Intersil ISL1208 RTC chip.
261 This driver can also be built as a module. If so, the module
262 will be called rtc-isl1208.
264 config RTC_DRV_ISL12022
265 tristate "Intersil ISL12022"
267 If you say yes here you get support for the
268 Intersil ISL12022 RTC chip.
270 This driver can also be built as a module. If so, the module
271 will be called rtc-isl12022.
274 tristate "Xicor/Intersil X1205"
276 If you say yes here you get support for the
277 Xicor/Intersil X1205 RTC chip.
279 This driver can also be built as a module. If so, the module
280 will be called rtc-x1205.
282 config RTC_DRV_PCF8563
283 tristate "Philips PCF8563/Epson RTC8564"
285 If you say yes here you get support for the
286 Philips PCF8563 RTC chip. The Epson RTC8564
289 This driver can also be built as a module. If so, the module
290 will be called rtc-pcf8563.
292 config RTC_DRV_PCF8583
293 tristate "Philips PCF8583"
295 If you say yes here you get support for the Philips PCF8583
296 RTC chip found on Acorn RiscPCs. This driver supports the
297 platform specific method of retrieving the current year from
298 the RTC's SRAM. It will work on other platforms with the same
299 chip, but the year will probably have to be tweaked.
301 This driver can also be built as a module. If so, the module
302 will be called rtc-pcf8583.
304 config RTC_DRV_M41T80
305 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
307 If you say Y here you will get support for the ST M41T60
308 and M41T80 RTC chips series. Currently, the following chips are
309 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
310 M41ST85, and M41ST87.
312 This driver can also be built as a module. If so, the module
313 will be called rtc-m41t80.
315 config RTC_DRV_M41T80_WDT
316 bool "ST M41T65/M41T80 series RTC watchdog timer"
317 depends on RTC_DRV_M41T80
319 If you say Y here you will get support for the
320 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
323 tristate "TI BQ32000"
325 If you say Y here you will get support for the TI
326 BQ32000 I2C RTC chip.
328 This driver can also be built as a module. If so, the module
329 will be called rtc-bq32k.
331 config RTC_DRV_DM355EVM
332 tristate "TI DaVinci DM355 EVM RTC"
333 depends on MFD_DM355EVM_MSP
335 Supports the RTC firmware in the MSP430 on the DM355 EVM.
337 config RTC_DRV_TWL92330
338 boolean "TI TWL92330/Menelaus"
341 If you say yes here you get support for the RTC on the
342 TWL92330 "Menelaus" power management chip, used with OMAP2
343 platforms. The support is integrated with the rest of
344 the Menelaus driver; it's not separate module.
346 config RTC_DRV_TWL4030
347 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
348 depends on TWL4030_CORE
350 If you say yes here you get support for the RTC on the
351 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
353 This driver can also be built as a module. If so, the module
354 will be called rtc-twl.
356 config RTC_DRV_TPS65910
357 tristate "TI TPS65910 RTC driver"
358 depends on RTC_CLASS && MFD_TPS65910
360 If you say yes here you get support for the RTC on the
363 This driver can also be built as a module. If so, the module
364 will be called rtc-tps65910.
366 config RTC_DRV_RC5T583
367 tristate "RICOH 5T583 RTC driver"
368 depends on MFD_RC5T583
370 If you say yes here you get support for the RTC on the
373 This driver can also be built as a module. If so, the module
374 will be called rtc-rc5t583.
376 config RTC_DRV_S35390A
377 tristate "Seiko Instruments S-35390A"
380 If you say yes here you will get support for the Seiko
381 Instruments S-35390A.
383 This driver can also be built as a module. If so the module
384 will be called rtc-s35390a.
386 config RTC_DRV_FM3130
387 tristate "Ramtron FM3130"
389 If you say Y here you will get support for the
390 Ramtron FM3130 RTC chips.
391 Ramtron FM3130 is a chip with two separate devices inside,
392 RTC clock and FRAM. This driver provides only RTC functionality.
394 This driver can also be built as a module. If so the module
395 will be called rtc-fm3130.
397 config RTC_DRV_RX8581
398 tristate "Epson RX-8581"
400 If you say yes here you will get support for the Epson RX-8581.
402 This driver can also be built as a module. If so the module
403 will be called rtc-rx8581.
405 config RTC_DRV_RX8025
406 tristate "Epson RX-8025SA/NB"
408 If you say yes here you get support for the Epson
409 RX-8025SA/NB RTC chips.
411 This driver can also be built as a module. If so, the module
412 will be called rtc-rx8025.
414 config RTC_DRV_EM3027
415 tristate "EM Microelectronic EM3027"
417 If you say yes here you get support for the EM
418 Microelectronic EM3027 RTC chips.
420 This driver can also be built as a module. If so, the module
421 will be called rtc-em3027.
423 config RTC_DRV_RV3029C2
424 tristate "Micro Crystal RTC"
426 If you say yes here you get support for the Micro Crystal
429 This driver can also be built as a module. If so, the module
430 will be called rtc-rv3029c2.
434 comment "SPI RTC drivers"
438 config RTC_DRV_M41T93
441 If you say yes here you will get support for the
442 ST M41T93 SPI RTC chip.
444 This driver can also be built as a module. If so, the module
445 will be called rtc-m41t93.
447 config RTC_DRV_M41T94
450 If you say yes here you will get support for the
451 ST M41T94 SPI RTC chip.
453 This driver can also be built as a module. If so, the module
454 will be called rtc-m41t94.
456 config RTC_DRV_DS1305
457 tristate "Dallas/Maxim DS1305/DS1306"
459 Select this driver to get support for the Dallas/Maxim DS1305
460 and DS1306 real time clock chips. These support a trickle
461 charger, alarms, and NVRAM in addition to the clock.
463 This driver can also be built as a module. If so, the module
464 will be called rtc-ds1305.
466 config RTC_DRV_DS1390
467 tristate "Dallas/Maxim DS1390/93/94"
469 If you say yes here you get support for the
470 Dallas/Maxim DS1390/93/94 chips.
472 This driver only supports the RTC feature, and not other chip
473 features such as alarms and trickle charging.
475 This driver can also be built as a module. If so, the module
476 will be called rtc-ds1390.
478 config RTC_DRV_MAX6902
479 tristate "Maxim MAX6902"
481 If you say yes here you will get support for the
482 Maxim MAX6902 SPI RTC chip.
484 This driver can also be built as a module. If so, the module
485 will be called rtc-max6902.
488 tristate "Epson RTC-9701JE"
490 If you say yes here you will get support for the
491 Epson RTC-9701JE SPI RTC chip.
493 This driver can also be built as a module. If so, the module
494 will be called rtc-r9701.
496 config RTC_DRV_RS5C348
497 tristate "Ricoh RS5C348A/B"
499 If you say yes here you get support for the
500 Ricoh RS5C348A and RS5C348B RTC chips.
502 This driver can also be built as a module. If so, the module
503 will be called rtc-rs5c348.
505 config RTC_DRV_DS3234
506 tristate "Maxim/Dallas DS3234"
508 If you say yes here you get support for the
509 Maxim/Dallas DS3234 SPI RTC chip.
511 This driver can also be built as a module. If so, the module
512 will be called rtc-ds3234.
514 config RTC_DRV_PCF2123
515 tristate "NXP PCF2123"
517 If you say yes here you get support for the NXP PCF2123
520 This driver can also be built as a module. If so, the module
521 will be called rtc-pcf2123.
525 comment "Platform RTC drivers"
527 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
528 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
529 # global rtc_lock ... it's not yet just another platform_device.
532 tristate "PC-style 'CMOS'"
533 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
536 Say "yes" here to get direct support for the real time clock
537 found in every PC or ACPI-based system, and some other boards.
538 Specifically the original MC146818, compatibles like those in
539 PC south bridges, the DS12887 or M48T86, some multifunction
540 or LPC bus chips, and so on.
542 Your system will need to define the platform device used by
543 this driver, otherwise it won't be accessible. This means
544 you can safely enable this driver if you don't know whether
545 or not your board has this kind of hardware.
547 This driver can also be built as a module. If so, the module
548 will be called rtc-cmos.
551 tristate "Virtual RTC for Intel MID platforms"
552 depends on X86_INTEL_MID
553 default y if X86_INTEL_MID
556 Say "yes" here to get direct support for the real time clock
557 found on Moorestown platforms. The VRTC is a emulated RTC that
558 derives its clock source from a real RTC in the PMIC. The MC146818
559 style programming interface is mostly conserved, but any
560 updates are done via IPC calls to the system controller FW.
562 config RTC_DRV_DS1216
563 tristate "Dallas DS1216"
566 If you say yes here you get support for the Dallas DS1216 RTC chips.
568 config RTC_DRV_DS1286
569 tristate "Dallas DS1286"
571 If you say yes here you get support for the Dallas DS1286 RTC chips.
573 config RTC_DRV_DS1302
574 tristate "Dallas DS1302"
575 depends on SH_SECUREEDGE5410
577 If you say yes here you get support for the Dallas DS1302 RTC chips.
579 config RTC_DRV_DS1511
580 tristate "Dallas DS1511"
582 If you say yes here you get support for the
583 Dallas DS1511 timekeeping/watchdog chip.
585 This driver can also be built as a module. If so, the module
586 will be called rtc-ds1511.
588 config RTC_DRV_DS1553
589 tristate "Maxim/Dallas DS1553"
591 If you say yes here you get support for the
592 Maxim/Dallas DS1553 timekeeping chip.
594 This driver can also be built as a module. If so, the module
595 will be called rtc-ds1553.
597 config RTC_DRV_DS1742
598 tristate "Maxim/Dallas DS1742/1743"
600 If you say yes here you get support for the
601 Maxim/Dallas DS1742/1743 timekeeping chip.
603 This driver can also be built as a module. If so, the module
604 will be called rtc-ds1742.
606 config RTC_DRV_DA9052
607 tristate "Dialog DA9052/DA9053 RTC"
608 depends on PMIC_DA9052
610 Say y here to support the RTC driver for Dialog Semiconductor
611 DA9052-BC and DA9053-AA/Bx PMICs.
617 If you say yes here you will get support for the EFI
620 This driver can also be built as a module. If so, the module
621 will be called rtc-efi.
623 config RTC_DRV_STK17TA8
624 tristate "Simtek STK17TA8"
626 If you say yes here you get support for the
627 Simtek STK17TA8 timekeeping chip.
629 This driver can also be built as a module. If so, the module
630 will be called rtc-stk17ta8.
632 config RTC_DRV_M48T86
633 tristate "ST M48T86/Dallas DS12887"
635 If you say Y here you will get support for the
636 ST M48T86 and Dallas DS12887 RTC chips.
638 This driver can also be built as a module. If so, the module
639 will be called rtc-m48t86.
641 config RTC_DRV_M48T35
644 If you say Y here you will get support for the
647 This driver can also be built as a module, if so, the module
648 will be called "rtc-m48t35".
650 config RTC_DRV_M48T59
651 tristate "ST M48T59/M48T08/M48T02"
653 If you say Y here you will get support for the
654 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
656 These chips are usually found in Sun SPARC and UltraSPARC
659 This driver can also be built as a module, if so, the module
660 will be called "rtc-m48t59".
662 config RTC_DRV_MSM6242
663 tristate "Oki MSM6242"
665 If you say yes here you get support for the Oki MSM6242
666 timekeeping chip. It is used in some Amiga models (e.g. A2000).
668 This driver can also be built as a module. If so, the module
669 will be called rtc-msm6242.
671 config RTC_DRV_BQ4802
674 If you say Y here you will get support for the TI
677 This driver can also be built as a module. If so, the module
678 will be called rtc-bq4802.
680 config RTC_DRV_RP5C01
681 tristate "Ricoh RP5C01"
683 If you say yes here you get support for the Ricoh RP5C01
684 timekeeping chip. It is used in some Amiga models (e.g. A3000
687 This driver can also be built as a module. If so, the module
688 will be called rtc-rp5c01.
691 tristate "EM Microelectronic V3020"
693 If you say yes here you will get support for the
694 EM Microelectronic v3020 RTC chip.
696 This driver can also be built as a module. If so, the module
697 will be called rtc-v3020.
699 config RTC_DRV_DS2404
700 tristate "Dallas DS2404"
702 If you say yes here you get support for the
703 Dallas DS2404 RTC chip.
705 This driver can also be built as a module. If so, the module
706 will be called rtc-ds2404.
708 config RTC_DRV_WM831X
709 tristate "Wolfson Microelectronics WM831x RTC"
710 depends on MFD_WM831X
712 If you say yes here you will get support for the RTC subsystem
713 of the Wolfson Microelectronics WM831X series PMICs.
715 This driver can also be built as a module. If so, the module
716 will be called "rtc-wm831x".
718 config RTC_DRV_WM8350
719 tristate "Wolfson Microelectronics WM8350 RTC"
720 depends on MFD_WM8350
722 If you say yes here you will get support for the RTC subsystem
723 of the Wolfson Microelectronics WM8350.
725 This driver can also be built as a module. If so, the module
726 will be called "rtc-wm8350".
729 tristate "SPEAR ST RTC"
730 depends on PLAT_SPEAR
733 If you say Y here you will get support for the RTC found on
736 config RTC_DRV_PCF50633
737 depends on MFD_PCF50633
738 tristate "NXP PCF50633 RTC"
740 If you say yes here you get support for the RTC subsystem of the
741 NXP PCF50633 used in embedded systems.
743 config RTC_DRV_AB3100
744 tristate "ST-Ericsson AB3100 RTC"
745 depends on AB3100_CORE
746 default y if AB3100_CORE
748 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
749 support. This chip contains a battery- and capacitor-backed RTC.
751 config RTC_DRV_AB8500
752 tristate "ST-Ericsson AB8500 RTC"
753 depends on AB8500_CORE
755 select RTC_INTF_DEV_UIE_EMUL
757 Select this to enable the ST-Ericsson AB8500 power management IC RTC
758 support. This chip contains a battery- and capacitor-backed RTC.
760 config RTC_DRV_NUC900
761 tristate "NUC910/NUC920 RTC driver"
762 depends on ARCH_W90X900
764 If you say yes here you get support for the RTC subsystem of the
765 NUC910/NUC920 used in embedded systems.
767 comment "on-CPU RTC drivers"
769 config RTC_DRV_DAVINCI
770 tristate "TI DaVinci RTC"
771 depends on ARCH_DAVINCI_DM365
773 If you say yes here you get support for the RTC on the
774 DaVinci platforms (DM365).
776 This driver can also be built as a module. If so, the module
777 will be called rtc-davinci.
780 tristate "Freescale IMX DryIce Real Time Clock"
783 Support for Freescale IMX DryIce RTC
785 This driver can also be built as a module, if so, the module
786 will be called "rtc-imxdi".
790 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
792 Say "yes" here to support the real time clock on TI OMAP1 and
793 DA8xx/OMAP-L13x chips. This driver can also be built as a
794 module called rtc-omap.
799 This will include RTC support for Samsung SoCs. If
800 you want to include RTC support for any machine, kindly
801 select this in the respective mach-XXXX/Kconfig file.
804 tristate "Samsung S3C series SoC RTC"
805 depends on ARCH_S3C64XX || HAVE_S3C_RTC
807 RTC (Realtime Clock) driver for the clock inbuilt into the
808 Samsung S3C24XX series of SoCs. This can provide periodic
809 interrupt rates from 1Hz to 64Hz for user programs, and
812 The driver currently supports the common features on all the
813 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
816 This driver can also be build as a module. If so, the module
817 will be called rtc-s3c.
819 config RTC_DRV_EP93XX
820 tristate "Cirrus Logic EP93XX"
821 depends on ARCH_EP93XX
823 If you say yes here you get support for the
824 RTC embedded in the Cirrus Logic EP93XX processors.
826 This driver can also be built as a module. If so, the module
827 will be called rtc-ep93xx.
829 config RTC_DRV_SA1100
830 tristate "SA11x0/PXA2xx/PXA910"
831 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
833 If you say Y here you will get access to the real time clock
834 built into your SA11x0 or PXA2xx CPU.
836 To compile this driver as a module, choose M here: the
837 module will be called rtc-sa1100.
840 tristate "SuperH On-Chip RTC"
841 depends on SUPERH && HAVE_CLK
843 Say Y here to enable support for the on-chip RTC found in
844 most SuperH processors.
846 To compile this driver as a module, choose M here: the
847 module will be called rtc-sh.
849 config RTC_DRV_VR41XX
850 tristate "NEC VR41XX"
851 depends on CPU_VR41XX
853 If you say Y here you will get access to the real time clock
854 built into your NEC VR41XX CPU.
856 To compile this driver as a module, choose M here: the
857 module will be called rtc-vr41xx.
860 tristate "ARM AMBA PL030 RTC"
863 If you say Y here you will get access to ARM AMBA
864 PrimeCell PL030 RTC found on certain ARM SOCs.
866 To compile this driver as a module, choose M here: the
867 module will be called rtc-pl030.
870 tristate "ARM AMBA PL031 RTC"
873 If you say Y here you will get access to ARM AMBA
874 PrimeCell PL031 RTC found on certain ARM SOCs.
876 To compile this driver as a module, choose M here: the
877 module will be called rtc-pl031.
879 config RTC_DRV_AT32AP700X
880 tristate "AT32AP700X series RTC"
881 depends on PLATFORM_AT32AP
883 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
884 AT32AP700x family processors.
886 config RTC_DRV_AT91RM9200
887 tristate "AT91RM9200 or some AT91SAM9 RTC"
890 Driver for the internal RTC (Realtime Clock) module found on
891 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
892 this is powered by the backup power supply.
894 config RTC_DRV_AT91SAM9
895 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
896 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
898 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
899 (Real Time Timer). These timers are powered by the backup power
900 supply (such as a small coin cell battery), but do not need to
903 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
904 dedicated RTC module and leave the RTT available for other uses.)
906 config RTC_DRV_AT91SAM9_RTT
910 prompt "RTT module Number" if ARCH_AT91SAM9263
911 depends on RTC_DRV_AT91SAM9
913 More than one RTT module is available. You can choose which
914 one will be used as an RTC. The default of zero is normally
915 OK to use, though some systems use that for non-RTC purposes.
917 config RTC_DRV_AT91SAM9_GPBR
919 range 0 3 if !ARCH_AT91SAM9263
920 range 0 15 if ARCH_AT91SAM9263
922 prompt "Backup Register Number"
923 depends on RTC_DRV_AT91SAM9
925 The RTC driver needs to use one of the General Purpose Backup
926 Registers (GPBRs) as well as the RTT. You can choose which one
927 will be used. The default of zero is normally OK to use, but
928 on some systems other software needs to use that register.
930 config RTC_DRV_AU1XXX
931 tristate "Au1xxx Counter0 RTC support"
932 depends on MIPS_ALCHEMY
934 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
935 counter) to be used as a RTC.
937 This driver can also be built as a module. If so, the module
938 will be called rtc-au1xxx.
941 tristate "Blackfin On-Chip RTC"
942 depends on BLACKFIN && !BF561
944 If you say yes here you will get support for the
945 Blackfin On-Chip Real Time Clock.
947 This driver can also be built as a module. If so, the module
948 will be called rtc-bfin.
950 config RTC_DRV_RS5C313
951 tristate "Ricoh RS5C313"
952 depends on SH_LANDISK
954 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
956 config RTC_DRV_GENERIC
957 tristate "Generic RTC support"
958 # Please consider writing a new RTC driver instead of using the generic
960 depends on PARISC || M68K || PPC || SUPERH32
962 Say Y or M here to enable RTC support on systems using the generic
963 RTC abstraction. If you do not know what you are doing, you should
967 tristate "PXA27x/PXA3xx"
970 If you say Y here you will get access to the real time clock
971 built into your PXA27x or PXA3xx CPU.
973 This RTC driver uses PXA RTC registers available since pxa27x
974 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
976 config RTC_DRV_VT8500
977 tristate "VIA/WonderMedia 85xx SoC RTC"
978 depends on ARCH_VT8500
980 If you say Y here you will get access to the real time clock
981 built into your VIA VT8500 SoC or its relatives.
985 bool "SUN4V Hypervisor RTC"
988 If you say Y here you will get support for the Hypervisor
989 based RTC on SUN4V systems.
991 config RTC_DRV_STARFIRE
995 If you say Y here you will get support for the RTC found on
998 config RTC_DRV_TX4939
999 tristate "TX4939 SoC"
1000 depends on SOC_TX4939
1002 Driver for the internal RTC (Realtime Clock) module found on
1006 tristate "Marvell SoC RTC"
1007 depends on ARCH_KIRKWOOD || ARCH_DOVE
1009 If you say yes here you will get support for the in-chip RTC
1010 that can be found in some of Marvell's SoC devices, such as
1011 the Kirkwood 88F6281 and 88F6192.
1013 This driver can also be built as a module. If so, the module
1014 will be called rtc-mv.
1020 If you say yes here you will get support for the RTC on PS3.
1022 This driver can also be built as a module. If so, the module
1023 will be called rtc-ps3.
1025 config RTC_DRV_COH901331
1026 tristate "ST-Ericsson COH 901 331 RTC"
1027 depends on ARCH_U300
1029 If you say Y here you will get access to ST-Ericsson
1030 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1033 This driver can also be built as a module. If so, the module
1034 will be called "rtc-coh901331".
1038 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1041 If you say yes here you will get support for the onboard
1042 STMP3xxx/i.MX23/i.MX28 RTC.
1044 This driver can also be built as a module. If so, the module
1045 will be called rtc-stmp3xxx.
1051 If you say Y here you will get support for the RTC found on
1052 the PCAP2 ASIC used on some Motorola phones.
1054 config RTC_DRV_MC13XXX
1055 depends on MFD_MC13XXX
1056 tristate "Freescale MC13xxx RTC"
1058 This enables support for the RTCs found on Freescale's PMICs
1059 MC13783 and MC13892.
1061 config RTC_DRV_MPC5121
1062 tristate "Freescale MPC5121 built-in RTC"
1063 depends on PPC_MPC512x || PPC_MPC52xx
1065 If you say yes here you will get support for the
1066 built-in RTC on MPC5121 or on MPC5200.
1068 This driver can also be built as a module. If so, the module
1069 will be called rtc-mpc5121.
1071 config RTC_DRV_JZ4740
1072 tristate "Ingenic JZ4740 SoC"
1073 depends on MACH_JZ4740
1075 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1078 This driver can also be buillt as a module. If so, the module
1079 will be called rtc-jz4740.
1081 config RTC_DRV_LPC32XX
1082 depends on ARCH_LPC32XX
1083 tristate "NXP LPC32XX RTC"
1085 This enables support for the NXP RTC in the LPC32XX
1087 This driver can also be buillt as a module. If so, the module
1088 will be called rtc-lpc32xx.
1090 config RTC_DRV_PM8XXX
1091 tristate "Qualcomm PMIC8XXX RTC"
1092 depends on MFD_PM8XXX
1094 If you say yes here you get support for the
1095 Qualcomm PMIC8XXX RTC.
1097 To compile this driver as a module, choose M here: the
1098 module will be called rtc-pm8xxx.
1100 config RTC_DRV_TEGRA
1101 tristate "NVIDIA Tegra Internal RTC driver"
1102 depends on ARCH_TEGRA
1104 If you say yes here you get support for the
1105 Tegra 200 series internal RTC module.
1107 This drive can also be built as a module. If so, the module
1108 will be called rtc-tegra.
1111 tristate "Tilera hypervisor RTC support"
1114 Enable support for the Linux driver side of the Tilera
1115 hypervisor's real-time clock interface.
1118 tristate "PKUnity v3 RTC support"
1119 depends on ARCH_PUV3
1121 This enables support for the RTC in the PKUnity-v3 SoCs.
1123 This drive can also be built as a module. If so, the module
1124 will be called rtc-puv3.
1126 config RTC_DRV_LOONGSON1
1127 tristate "loongson1 RTC support"
1128 depends on MACH_LOONGSON1
1130 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1131 counter) to be used as a RTC.
1133 This driver can also be built as a module. If so, the module
1134 will be called rtc-ls1x.
1137 tristate "Freescale MXC Real Time Clock"
1140 If you say yes here you get support for the Freescale MXC
1143 This driver can also be built as a module, if so, the module
1144 will be called "rtc-mxc".
1147 tristate "Freescale SNVS RTC support"
1148 depends on HAS_IOMEM
1151 If you say yes here you get support for the Freescale SNVS
1152 Low Power (LP) RTC module.
1154 This driver can also be built as a module, if so, the module
1155 will be called "rtc-snvs".