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 !ALWAYS_USE_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 !ALWAYS_USE_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_LP8788
208 tristate "TI LP8788 RTC driver"
209 depends on MFD_LP8788
211 Say Y to enable support for the LP8788 RTC/ALARM driver.
213 config RTC_DRV_MAX6900
214 tristate "Maxim MAX6900"
216 If you say yes here you will get support for the
217 Maxim MAX6900 I2C RTC chip.
219 This driver can also be built as a module. If so, the module
220 will be called rtc-max6900.
222 config RTC_DRV_MAX8907
223 tristate "Maxim MAX8907"
224 depends on MFD_MAX8907
226 If you say yes here you will get support for the
227 RTC of Maxim MAX8907 PMIC.
229 This driver can also be built as a module. If so, the module
230 will be called rtc-max8907.
232 config RTC_DRV_MAX8925
233 tristate "Maxim MAX8925"
234 depends on MFD_MAX8925
236 If you say yes here you will get support for the
237 RTC of Maxim MAX8925 PMIC.
239 This driver can also be built as a module. If so, the module
240 will be called rtc-max8925.
242 config RTC_DRV_MAX8998
243 tristate "Maxim MAX8998"
244 depends on MFD_MAX8998
246 If you say yes here you will get support for the
247 RTC of Maxim MAX8998 PMIC.
249 This driver can also be built as a module. If so, the module
250 will be called rtc-max8998.
252 config RTC_DRV_MAX77686
253 tristate "Maxim MAX77686"
254 depends on MFD_MAX77686
256 If you say yes here you will get support for the
257 RTC of Maxim MAX77686 PMIC.
259 This driver can also be built as a module. If so, the module
260 will be called rtc-max77686.
262 config RTC_DRV_RS5C372
263 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
265 If you say yes here you get support for the
266 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
268 This driver can also be built as a module. If so, the module
269 will be called rtc-rs5c372.
271 config RTC_DRV_ISL1208
272 tristate "Intersil ISL1208"
274 If you say yes here you get support for the
275 Intersil ISL1208 RTC chip.
277 This driver can also be built as a module. If so, the module
278 will be called rtc-isl1208.
280 config RTC_DRV_ISL12022
281 tristate "Intersil ISL12022"
283 If you say yes here you get support for the
284 Intersil ISL12022 RTC chip.
286 This driver can also be built as a module. If so, the module
287 will be called rtc-isl12022.
290 tristate "Xicor/Intersil X1205"
292 If you say yes here you get support for the
293 Xicor/Intersil X1205 RTC chip.
295 This driver can also be built as a module. If so, the module
296 will be called rtc-x1205.
298 config RTC_DRV_PCF8523
299 tristate "NXP PCF8523"
301 If you say yes here you get support for the NXP PCF8523 RTC
304 This driver can also be built as a module. If so, the module
305 will be called rtc-pcf8523.
307 config RTC_DRV_PCF8563
308 tristate "Philips PCF8563/Epson RTC8564"
310 If you say yes here you get support for the
311 Philips PCF8563 RTC chip. The Epson RTC8564
314 This driver can also be built as a module. If so, the module
315 will be called rtc-pcf8563.
317 config RTC_DRV_PCF8583
318 tristate "Philips PCF8583"
320 If you say yes here you get support for the Philips PCF8583
321 RTC chip found on Acorn RiscPCs. This driver supports the
322 platform specific method of retrieving the current year from
323 the RTC's SRAM. It will work on other platforms with the same
324 chip, but the year will probably have to be tweaked.
326 This driver can also be built as a module. If so, the module
327 will be called rtc-pcf8583.
329 config RTC_DRV_M41T80
330 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
332 If you say Y here you will get support for the ST M41T60
333 and M41T80 RTC chips series. Currently, the following chips are
334 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
335 M41ST85, and M41ST87.
337 This driver can also be built as a module. If so, the module
338 will be called rtc-m41t80.
340 config RTC_DRV_M41T80_WDT
341 bool "ST M41T65/M41T80 series RTC watchdog timer"
342 depends on RTC_DRV_M41T80
344 If you say Y here you will get support for the
345 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
348 tristate "TI BQ32000"
350 If you say Y here you will get support for the TI
351 BQ32000 I2C RTC chip.
353 This driver can also be built as a module. If so, the module
354 will be called rtc-bq32k.
356 config RTC_DRV_DM355EVM
357 tristate "TI DaVinci DM355 EVM RTC"
358 depends on MFD_DM355EVM_MSP
360 Supports the RTC firmware in the MSP430 on the DM355 EVM.
362 config RTC_DRV_TWL92330
363 boolean "TI TWL92330/Menelaus"
366 If you say yes here you get support for the RTC on the
367 TWL92330 "Menelaus" power management chip, used with OMAP2
368 platforms. The support is integrated with the rest of
369 the Menelaus driver; it's not separate module.
371 config RTC_DRV_TWL4030
372 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
373 depends on TWL4030_CORE
375 If you say yes here you get support for the RTC on the
376 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
378 This driver can also be built as a module. If so, the module
379 will be called rtc-twl.
381 config RTC_DRV_TPS6586X
382 tristate "TI TPS6586X RTC driver"
383 depends on MFD_TPS6586X
385 TI Power Managment IC TPS6586X supports RTC functionality
386 along with alarm. This driver supports the RTC driver for
387 the TPS6586X RTC module.
389 config RTC_DRV_TPS65910
390 tristate "TI TPS65910 RTC driver"
391 depends on RTC_CLASS && MFD_TPS65910
393 If you say yes here you get support for the RTC on the
396 This driver can also be built as a module. If so, the module
397 will be called rtc-tps65910.
399 config RTC_DRV_RC5T583
400 tristate "RICOH 5T583 RTC driver"
401 depends on MFD_RC5T583
403 If you say yes here you get support for the RTC on the
406 This driver can also be built as a module. If so, the module
407 will be called rtc-rc5t583.
409 config RTC_DRV_S35390A
410 tristate "Seiko Instruments S-35390A"
413 If you say yes here you will get support for the Seiko
414 Instruments S-35390A.
416 This driver can also be built as a module. If so the module
417 will be called rtc-s35390a.
419 config RTC_DRV_FM3130
420 tristate "Ramtron FM3130"
422 If you say Y here you will get support for the
423 Ramtron FM3130 RTC chips.
424 Ramtron FM3130 is a chip with two separate devices inside,
425 RTC clock and FRAM. This driver provides only RTC functionality.
427 This driver can also be built as a module. If so the module
428 will be called rtc-fm3130.
430 config RTC_DRV_RX8581
431 tristate "Epson RX-8581"
433 If you say yes here you will get support for the Epson RX-8581.
435 This driver can also be built as a module. If so the module
436 will be called rtc-rx8581.
438 config RTC_DRV_RX8025
439 tristate "Epson RX-8025SA/NB"
441 If you say yes here you get support for the Epson
442 RX-8025SA/NB RTC chips.
444 This driver can also be built as a module. If so, the module
445 will be called rtc-rx8025.
447 config RTC_DRV_EM3027
448 tristate "EM Microelectronic EM3027"
450 If you say yes here you get support for the EM
451 Microelectronic EM3027 RTC chips.
453 This driver can also be built as a module. If so, the module
454 will be called rtc-em3027.
456 config RTC_DRV_RV3029C2
457 tristate "Micro Crystal RTC"
459 If you say yes here you get support for the Micro Crystal
462 This driver can also be built as a module. If so, the module
463 will be called rtc-rv3029c2.
467 comment "SPI RTC drivers"
471 config RTC_DRV_M41T93
474 If you say yes here you will get support for the
475 ST M41T93 SPI RTC chip.
477 This driver can also be built as a module. If so, the module
478 will be called rtc-m41t93.
480 config RTC_DRV_M41T94
483 If you say yes here you will get support for the
484 ST M41T94 SPI RTC chip.
486 This driver can also be built as a module. If so, the module
487 will be called rtc-m41t94.
489 config RTC_DRV_DS1305
490 tristate "Dallas/Maxim DS1305/DS1306"
492 Select this driver to get support for the Dallas/Maxim DS1305
493 and DS1306 real time clock chips. These support a trickle
494 charger, alarms, and NVRAM in addition to the clock.
496 This driver can also be built as a module. If so, the module
497 will be called rtc-ds1305.
499 config RTC_DRV_DS1390
500 tristate "Dallas/Maxim DS1390/93/94"
502 If you say yes here you get support for the
503 Dallas/Maxim DS1390/93/94 chips.
505 This driver only supports the RTC feature, and not other chip
506 features such as alarms and trickle charging.
508 This driver can also be built as a module. If so, the module
509 will be called rtc-ds1390.
511 config RTC_DRV_MAX6902
512 tristate "Maxim MAX6902"
514 If you say yes here you will get support for the
515 Maxim MAX6902 SPI RTC chip.
517 This driver can also be built as a module. If so, the module
518 will be called rtc-max6902.
521 tristate "Epson RTC-9701JE"
523 If you say yes here you will get support for the
524 Epson RTC-9701JE SPI RTC chip.
526 This driver can also be built as a module. If so, the module
527 will be called rtc-r9701.
529 config RTC_DRV_RS5C348
530 tristate "Ricoh RS5C348A/B"
532 If you say yes here you get support for the
533 Ricoh RS5C348A and RS5C348B RTC chips.
535 This driver can also be built as a module. If so, the module
536 will be called rtc-rs5c348.
538 config RTC_DRV_DS3234
539 tristate "Maxim/Dallas DS3234"
541 If you say yes here you get support for the
542 Maxim/Dallas DS3234 SPI RTC chip.
544 This driver can also be built as a module. If so, the module
545 will be called rtc-ds3234.
547 config RTC_DRV_PCF2123
548 tristate "NXP PCF2123"
550 If you say yes here you get support for the NXP PCF2123
553 This driver can also be built as a module. If so, the module
554 will be called rtc-pcf2123.
558 comment "Platform RTC drivers"
560 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
561 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
562 # global rtc_lock ... it's not yet just another platform_device.
565 tristate "PC-style 'CMOS'"
566 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
569 Say "yes" here to get direct support for the real time clock
570 found in every PC or ACPI-based system, and some other boards.
571 Specifically the original MC146818, compatibles like those in
572 PC south bridges, the DS12887 or M48T86, some multifunction
573 or LPC bus chips, and so on.
575 Your system will need to define the platform device used by
576 this driver, otherwise it won't be accessible. This means
577 you can safely enable this driver if you don't know whether
578 or not your board has this kind of hardware.
580 This driver can also be built as a module. If so, the module
581 will be called rtc-cmos.
584 tristate "Virtual RTC for Intel MID platforms"
585 depends on X86_INTEL_MID
586 default y if X86_INTEL_MID
589 Say "yes" here to get direct support for the real time clock
590 found on Moorestown platforms. The VRTC is a emulated RTC that
591 derives its clock source from a real RTC in the PMIC. The MC146818
592 style programming interface is mostly conserved, but any
593 updates are done via IPC calls to the system controller FW.
595 config RTC_DRV_DS1216
596 tristate "Dallas DS1216"
599 If you say yes here you get support for the Dallas DS1216 RTC chips.
601 config RTC_DRV_DS1286
602 tristate "Dallas DS1286"
604 If you say yes here you get support for the Dallas DS1286 RTC chips.
606 config RTC_DRV_DS1302
607 tristate "Dallas DS1302"
608 depends on SH_SECUREEDGE5410
610 If you say yes here you get support for the Dallas DS1302 RTC chips.
612 config RTC_DRV_DS1511
613 tristate "Dallas DS1511"
615 If you say yes here you get support for the
616 Dallas DS1511 timekeeping/watchdog chip.
618 This driver can also be built as a module. If so, the module
619 will be called rtc-ds1511.
621 config RTC_DRV_DS1553
622 tristate "Maxim/Dallas DS1553"
624 If you say yes here you get support for the
625 Maxim/Dallas DS1553 timekeeping chip.
627 This driver can also be built as a module. If so, the module
628 will be called rtc-ds1553.
630 config RTC_DRV_DS1742
631 tristate "Maxim/Dallas DS1742/1743"
633 If you say yes here you get support for the
634 Maxim/Dallas DS1742/1743 timekeeping chip.
636 This driver can also be built as a module. If so, the module
637 will be called rtc-ds1742.
639 config RTC_DRV_DA9052
640 tristate "Dialog DA9052/DA9053 RTC"
641 depends on PMIC_DA9052
643 Say y here to support the RTC driver for Dialog Semiconductor
644 DA9052-BC and DA9053-AA/Bx PMICs.
646 config RTC_DRV_DA9055
647 tristate "Dialog Semiconductor DA9055 RTC"
648 depends on MFD_DA9055
650 If you say yes here you will get support for the
651 RTC of the Dialog DA9055 PMIC.
653 This driver can also be built as a module. If so, the module
654 will be called rtc-da9055
660 If you say yes here you will get support for the EFI
663 This driver can also be built as a module. If so, the module
664 will be called rtc-efi.
666 config RTC_DRV_STK17TA8
667 tristate "Simtek STK17TA8"
669 If you say yes here you get support for the
670 Simtek STK17TA8 timekeeping chip.
672 This driver can also be built as a module. If so, the module
673 will be called rtc-stk17ta8.
675 config RTC_DRV_M48T86
676 tristate "ST M48T86/Dallas DS12887"
678 If you say Y here you will get support for the
679 ST M48T86 and Dallas DS12887 RTC chips.
681 This driver can also be built as a module. If so, the module
682 will be called rtc-m48t86.
684 config RTC_DRV_M48T35
687 If you say Y here you will get support for the
690 This driver can also be built as a module, if so, the module
691 will be called "rtc-m48t35".
693 config RTC_DRV_M48T59
694 tristate "ST M48T59/M48T08/M48T02"
696 If you say Y here you will get support for the
697 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
699 These chips are usually found in Sun SPARC and UltraSPARC
702 This driver can also be built as a module, if so, the module
703 will be called "rtc-m48t59".
705 config RTC_DRV_MSM6242
706 tristate "Oki MSM6242"
708 If you say yes here you get support for the Oki MSM6242
709 timekeeping chip. It is used in some Amiga models (e.g. A2000).
711 This driver can also be built as a module. If so, the module
712 will be called rtc-msm6242.
714 config RTC_DRV_BQ4802
717 If you say Y here you will get support for the TI
720 This driver can also be built as a module. If so, the module
721 will be called rtc-bq4802.
723 config RTC_DRV_RP5C01
724 tristate "Ricoh RP5C01"
726 If you say yes here you get support for the Ricoh RP5C01
727 timekeeping chip. It is used in some Amiga models (e.g. A3000
730 This driver can also be built as a module. If so, the module
731 will be called rtc-rp5c01.
734 tristate "EM Microelectronic V3020"
736 If you say yes here you will get support for the
737 EM Microelectronic v3020 RTC chip.
739 This driver can also be built as a module. If so, the module
740 will be called rtc-v3020.
742 config RTC_DRV_DS2404
743 tristate "Dallas DS2404"
745 If you say yes here you get support for the
746 Dallas DS2404 RTC chip.
748 This driver can also be built as a module. If so, the module
749 will be called rtc-ds2404.
751 config RTC_DRV_WM831X
752 tristate "Wolfson Microelectronics WM831x RTC"
753 depends on MFD_WM831X
755 If you say yes here you will get support for the RTC subsystem
756 of the Wolfson Microelectronics WM831X series PMICs.
758 This driver can also be built as a module. If so, the module
759 will be called "rtc-wm831x".
761 config RTC_DRV_WM8350
762 tristate "Wolfson Microelectronics WM8350 RTC"
763 depends on MFD_WM8350
765 If you say yes here you will get support for the RTC subsystem
766 of the Wolfson Microelectronics WM8350.
768 This driver can also be built as a module. If so, the module
769 will be called "rtc-wm8350".
772 tristate "SPEAR ST RTC"
773 depends on PLAT_SPEAR
776 If you say Y here you will get support for the RTC found on
779 config RTC_DRV_PCF50633
780 depends on MFD_PCF50633
781 tristate "NXP PCF50633 RTC"
783 If you say yes here you get support for the RTC subsystem of the
784 NXP PCF50633 used in embedded systems.
786 config RTC_DRV_AB3100
787 tristate "ST-Ericsson AB3100 RTC"
788 depends on AB3100_CORE
789 default y if AB3100_CORE
791 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
792 support. This chip contains a battery- and capacitor-backed RTC.
794 config RTC_DRV_AB8500
795 tristate "ST-Ericsson AB8500 RTC"
796 depends on AB8500_CORE
798 select RTC_INTF_DEV_UIE_EMUL
800 Select this to enable the ST-Ericsson AB8500 power management IC RTC
801 support. This chip contains a battery- and capacitor-backed RTC.
803 config RTC_DRV_NUC900
804 tristate "NUC910/NUC920 RTC driver"
805 depends on ARCH_W90X900
807 If you say yes here you get support for the RTC subsystem of the
808 NUC910/NUC920 used in embedded systems.
810 comment "on-CPU RTC drivers"
812 config RTC_DRV_DAVINCI
813 tristate "TI DaVinci RTC"
814 depends on ARCH_DAVINCI_DM365
816 If you say yes here you get support for the RTC on the
817 DaVinci platforms (DM365).
819 This driver can also be built as a module. If so, the module
820 will be called rtc-davinci.
823 tristate "Freescale IMX DryIce Real Time Clock"
826 Support for Freescale IMX DryIce RTC
828 This driver can also be built as a module, if so, the module
829 will be called "rtc-imxdi".
833 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
835 Say "yes" here to support the on chip real time clock
836 present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
838 This driver can also be built as a module, if so, module
839 will be called rtc-omap.
844 This will include RTC support for Samsung SoCs. If
845 you want to include RTC support for any machine, kindly
846 select this in the respective mach-XXXX/Kconfig file.
849 tristate "Samsung S3C series SoC RTC"
850 depends on ARCH_S3C64XX || HAVE_S3C_RTC
852 RTC (Realtime Clock) driver for the clock inbuilt into the
853 Samsung S3C24XX series of SoCs. This can provide periodic
854 interrupt rates from 1Hz to 64Hz for user programs, and
857 The driver currently supports the common features on all the
858 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
861 This driver can also be build as a module. If so, the module
862 will be called rtc-s3c.
864 config RTC_DRV_EP93XX
865 tristate "Cirrus Logic EP93XX"
866 depends on ARCH_EP93XX
868 If you say yes here you get support for the
869 RTC embedded in the Cirrus Logic EP93XX processors.
871 This driver can also be built as a module. If so, the module
872 will be called rtc-ep93xx.
874 config RTC_DRV_SA1100
875 tristate "SA11x0/PXA2xx/PXA910"
876 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
878 If you say Y here you will get access to the real time clock
879 built into your SA11x0 or PXA2xx CPU.
881 To compile this driver as a module, choose M here: the
882 module will be called rtc-sa1100.
885 tristate "SuperH On-Chip RTC"
886 depends on SUPERH && HAVE_CLK
888 Say Y here to enable support for the on-chip RTC found in
889 most SuperH processors.
891 To compile this driver as a module, choose M here: the
892 module will be called rtc-sh.
894 config RTC_DRV_VR41XX
895 tristate "NEC VR41XX"
896 depends on CPU_VR41XX
898 If you say Y here you will get access to the real time clock
899 built into your NEC VR41XX CPU.
901 To compile this driver as a module, choose M here: the
902 module will be called rtc-vr41xx.
905 tristate "ARM AMBA PL030 RTC"
908 If you say Y here you will get access to ARM AMBA
909 PrimeCell PL030 RTC found on certain ARM SOCs.
911 To compile this driver as a module, choose M here: the
912 module will be called rtc-pl030.
915 tristate "ARM AMBA PL031 RTC"
918 If you say Y here you will get access to ARM AMBA
919 PrimeCell PL031 RTC found on certain ARM SOCs.
921 To compile this driver as a module, choose M here: the
922 module will be called rtc-pl031.
924 config RTC_DRV_AT32AP700X
925 tristate "AT32AP700X series RTC"
926 depends on PLATFORM_AT32AP
928 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
929 AT32AP700x family processors.
931 config RTC_DRV_AT91RM9200
932 tristate "AT91RM9200 or some AT91SAM9 RTC"
935 Driver for the internal RTC (Realtime Clock) module found on
936 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
937 this is powered by the backup power supply.
939 config RTC_DRV_AT91SAM9
940 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
941 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
943 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
944 (Real Time Timer). These timers are powered by the backup power
945 supply (such as a small coin cell battery), but do not need to
948 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
949 dedicated RTC module and leave the RTT available for other uses.)
951 config RTC_DRV_AT91SAM9_RTT
955 prompt "RTT module Number" if ARCH_AT91SAM9263
956 depends on RTC_DRV_AT91SAM9
958 More than one RTT module is available. You can choose which
959 one will be used as an RTC. The default of zero is normally
960 OK to use, though some systems use that for non-RTC purposes.
962 config RTC_DRV_AT91SAM9_GPBR
964 range 0 3 if !ARCH_AT91SAM9263
965 range 0 15 if ARCH_AT91SAM9263
967 prompt "Backup Register Number"
968 depends on RTC_DRV_AT91SAM9
970 The RTC driver needs to use one of the General Purpose Backup
971 Registers (GPBRs) as well as the RTT. You can choose which one
972 will be used. The default of zero is normally OK to use, but
973 on some systems other software needs to use that register.
975 config RTC_DRV_AU1XXX
976 tristate "Au1xxx Counter0 RTC support"
977 depends on MIPS_ALCHEMY
979 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
980 counter) to be used as a RTC.
982 This driver can also be built as a module. If so, the module
983 will be called rtc-au1xxx.
986 tristate "Blackfin On-Chip RTC"
987 depends on BLACKFIN && !BF561
989 If you say yes here you will get support for the
990 Blackfin On-Chip Real Time Clock.
992 This driver can also be built as a module. If so, the module
993 will be called rtc-bfin.
995 config RTC_DRV_RS5C313
996 tristate "Ricoh RS5C313"
997 depends on SH_LANDISK
999 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1001 config RTC_DRV_GENERIC
1002 tristate "Generic RTC support"
1003 # Please consider writing a new RTC driver instead of using the generic
1005 depends on PARISC || M68K || PPC || SUPERH32
1007 Say Y or M here to enable RTC support on systems using the generic
1008 RTC abstraction. If you do not know what you are doing, you should
1012 tristate "PXA27x/PXA3xx"
1015 If you say Y here you will get access to the real time clock
1016 built into your PXA27x or PXA3xx CPU.
1018 This RTC driver uses PXA RTC registers available since pxa27x
1019 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1021 config RTC_DRV_VT8500
1022 tristate "VIA/WonderMedia 85xx SoC RTC"
1023 depends on ARCH_VT8500
1025 If you say Y here you will get access to the real time clock
1026 built into your VIA VT8500 SoC or its relatives.
1029 config RTC_DRV_SUN4V
1030 bool "SUN4V Hypervisor RTC"
1033 If you say Y here you will get support for the Hypervisor
1034 based RTC on SUN4V systems.
1036 config RTC_DRV_STARFIRE
1040 If you say Y here you will get support for the RTC found on
1043 config RTC_DRV_TX4939
1044 tristate "TX4939 SoC"
1045 depends on SOC_TX4939
1047 Driver for the internal RTC (Realtime Clock) module found on
1051 tristate "Marvell SoC RTC"
1052 depends on ARCH_KIRKWOOD || ARCH_DOVE
1054 If you say yes here you will get support for the in-chip RTC
1055 that can be found in some of Marvell's SoC devices, such as
1056 the Kirkwood 88F6281 and 88F6192.
1058 This driver can also be built as a module. If so, the module
1059 will be called rtc-mv.
1065 If you say yes here you will get support for the RTC on PS3.
1067 This driver can also be built as a module. If so, the module
1068 will be called rtc-ps3.
1070 config RTC_DRV_COH901331
1071 tristate "ST-Ericsson COH 901 331 RTC"
1072 depends on ARCH_U300
1074 If you say Y here you will get access to ST-Ericsson
1075 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1078 This driver can also be built as a module. If so, the module
1079 will be called "rtc-coh901331".
1083 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1086 If you say yes here you will get support for the onboard
1087 STMP3xxx/i.MX23/i.MX28 RTC.
1089 This driver can also be built as a module. If so, the module
1090 will be called rtc-stmp3xxx.
1096 If you say Y here you will get support for the RTC found on
1097 the PCAP2 ASIC used on some Motorola phones.
1099 config RTC_DRV_MC13XXX
1100 depends on MFD_MC13XXX
1101 tristate "Freescale MC13xxx RTC"
1103 This enables support for the RTCs found on Freescale's PMICs
1104 MC13783 and MC13892.
1106 config RTC_DRV_MPC5121
1107 tristate "Freescale MPC5121 built-in RTC"
1108 depends on PPC_MPC512x || PPC_MPC52xx
1110 If you say yes here you will get support for the
1111 built-in RTC on MPC5121 or on MPC5200.
1113 This driver can also be built as a module. If so, the module
1114 will be called rtc-mpc5121.
1116 config RTC_DRV_JZ4740
1117 tristate "Ingenic JZ4740 SoC"
1118 depends on MACH_JZ4740
1120 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1123 This driver can also be buillt as a module. If so, the module
1124 will be called rtc-jz4740.
1126 config RTC_DRV_LPC32XX
1127 depends on ARCH_LPC32XX
1128 tristate "NXP LPC32XX RTC"
1130 This enables support for the NXP RTC in the LPC32XX
1132 This driver can also be buillt as a module. If so, the module
1133 will be called rtc-lpc32xx.
1135 config RTC_DRV_PM8XXX
1136 tristate "Qualcomm PMIC8XXX RTC"
1137 depends on MFD_PM8XXX
1139 If you say yes here you get support for the
1140 Qualcomm PMIC8XXX RTC.
1142 To compile this driver as a module, choose M here: the
1143 module will be called rtc-pm8xxx.
1145 config RTC_DRV_TEGRA
1146 tristate "NVIDIA Tegra Internal RTC driver"
1147 depends on ARCH_TEGRA
1149 If you say yes here you get support for the
1150 Tegra 200 series internal RTC module.
1152 This drive can also be built as a module. If so, the module
1153 will be called rtc-tegra.
1156 tristate "Tilera hypervisor RTC support"
1159 Enable support for the Linux driver side of the Tilera
1160 hypervisor's real-time clock interface.
1163 tristate "PKUnity v3 RTC support"
1164 depends on ARCH_PUV3
1166 This enables support for the RTC in the PKUnity-v3 SoCs.
1168 This drive can also be built as a module. If so, the module
1169 will be called rtc-puv3.
1171 config RTC_DRV_LOONGSON1
1172 tristate "loongson1 RTC support"
1173 depends on MACH_LOONGSON1
1175 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1176 counter) to be used as a RTC.
1178 This driver can also be built as a module. If so, the module
1179 will be called rtc-ls1x.
1182 tristate "Freescale MXC Real Time Clock"
1185 If you say yes here you get support for the Freescale MXC
1188 This driver can also be built as a module, if so, the module
1189 will be called "rtc-mxc".
1192 tristate "Freescale SNVS RTC support"
1193 depends on HAS_IOMEM
1196 If you say yes here you get support for the Freescale SNVS
1197 Low Power (LP) RTC module.
1199 This driver can also be built as a module, if so, the module
1200 will be called "rtc-snvs".