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_TPS80031
400 tristate "TI TPS80031/TPS80032 RTC driver"
401 depends on MFD_TPS80031
403 TI Power Managment IC TPS80031 supports RTC functionality
404 along with alarm. This driver supports the RTC driver for
405 the TPS80031 RTC module.
407 config RTC_DRV_RC5T583
408 tristate "RICOH 5T583 RTC driver"
409 depends on MFD_RC5T583
411 If you say yes here you get support for the RTC on the
414 This driver can also be built as a module. If so, the module
415 will be called rtc-rc5t583.
417 config RTC_DRV_S35390A
418 tristate "Seiko Instruments S-35390A"
421 If you say yes here you will get support for the Seiko
422 Instruments S-35390A.
424 This driver can also be built as a module. If so the module
425 will be called rtc-s35390a.
427 config RTC_DRV_FM3130
428 tristate "Ramtron FM3130"
430 If you say Y here you will get support for the
431 Ramtron FM3130 RTC chips.
432 Ramtron FM3130 is a chip with two separate devices inside,
433 RTC clock and FRAM. This driver provides only RTC functionality.
435 This driver can also be built as a module. If so the module
436 will be called rtc-fm3130.
438 config RTC_DRV_RX8581
439 tristate "Epson RX-8581"
441 If you say yes here you will get support for the Epson RX-8581.
443 This driver can also be built as a module. If so the module
444 will be called rtc-rx8581.
446 config RTC_DRV_RX8025
447 tristate "Epson RX-8025SA/NB"
449 If you say yes here you get support for the Epson
450 RX-8025SA/NB RTC chips.
452 This driver can also be built as a module. If so, the module
453 will be called rtc-rx8025.
455 config RTC_DRV_EM3027
456 tristate "EM Microelectronic EM3027"
458 If you say yes here you get support for the EM
459 Microelectronic EM3027 RTC chips.
461 This driver can also be built as a module. If so, the module
462 will be called rtc-em3027.
464 config RTC_DRV_RV3029C2
465 tristate "Micro Crystal RTC"
467 If you say yes here you get support for the Micro Crystal
470 This driver can also be built as a module. If so, the module
471 will be called rtc-rv3029c2.
475 comment "SPI RTC drivers"
479 config RTC_DRV_M41T93
482 If you say yes here you will get support for the
483 ST M41T93 SPI RTC chip.
485 This driver can also be built as a module. If so, the module
486 will be called rtc-m41t93.
488 config RTC_DRV_M41T94
491 If you say yes here you will get support for the
492 ST M41T94 SPI RTC chip.
494 This driver can also be built as a module. If so, the module
495 will be called rtc-m41t94.
497 config RTC_DRV_DS1305
498 tristate "Dallas/Maxim DS1305/DS1306"
500 Select this driver to get support for the Dallas/Maxim DS1305
501 and DS1306 real time clock chips. These support a trickle
502 charger, alarms, and NVRAM in addition to the clock.
504 This driver can also be built as a module. If so, the module
505 will be called rtc-ds1305.
507 config RTC_DRV_DS1390
508 tristate "Dallas/Maxim DS1390/93/94"
510 If you say yes here you get support for the
511 Dallas/Maxim DS1390/93/94 chips.
513 This driver only supports the RTC feature, and not other chip
514 features such as alarms and trickle charging.
516 This driver can also be built as a module. If so, the module
517 will be called rtc-ds1390.
519 config RTC_DRV_MAX6902
520 tristate "Maxim MAX6902"
522 If you say yes here you will get support for the
523 Maxim MAX6902 SPI RTC chip.
525 This driver can also be built as a module. If so, the module
526 will be called rtc-max6902.
529 tristate "Epson RTC-9701JE"
531 If you say yes here you will get support for the
532 Epson RTC-9701JE SPI RTC chip.
534 This driver can also be built as a module. If so, the module
535 will be called rtc-r9701.
537 config RTC_DRV_RS5C348
538 tristate "Ricoh RS5C348A/B"
540 If you say yes here you get support for the
541 Ricoh RS5C348A and RS5C348B RTC chips.
543 This driver can also be built as a module. If so, the module
544 will be called rtc-rs5c348.
546 config RTC_DRV_DS3234
547 tristate "Maxim/Dallas DS3234"
549 If you say yes here you get support for the
550 Maxim/Dallas DS3234 SPI RTC chip.
552 This driver can also be built as a module. If so, the module
553 will be called rtc-ds3234.
555 config RTC_DRV_PCF2123
556 tristate "NXP PCF2123"
558 If you say yes here you get support for the NXP PCF2123
561 This driver can also be built as a module. If so, the module
562 will be called rtc-pcf2123.
566 comment "Platform RTC drivers"
568 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
569 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
570 # global rtc_lock ... it's not yet just another platform_device.
573 tristate "PC-style 'CMOS'"
574 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
577 Say "yes" here to get direct support for the real time clock
578 found in every PC or ACPI-based system, and some other boards.
579 Specifically the original MC146818, compatibles like those in
580 PC south bridges, the DS12887 or M48T86, some multifunction
581 or LPC bus chips, and so on.
583 Your system will need to define the platform device used by
584 this driver, otherwise it won't be accessible. This means
585 you can safely enable this driver if you don't know whether
586 or not your board has this kind of hardware.
588 This driver can also be built as a module. If so, the module
589 will be called rtc-cmos.
592 tristate "Virtual RTC for Intel MID platforms"
593 depends on X86_INTEL_MID
594 default y if X86_INTEL_MID
597 Say "yes" here to get direct support for the real time clock
598 found on Moorestown platforms. The VRTC is a emulated RTC that
599 derives its clock source from a real RTC in the PMIC. The MC146818
600 style programming interface is mostly conserved, but any
601 updates are done via IPC calls to the system controller FW.
603 config RTC_DRV_DS1216
604 tristate "Dallas DS1216"
607 If you say yes here you get support for the Dallas DS1216 RTC chips.
609 config RTC_DRV_DS1286
610 tristate "Dallas DS1286"
612 If you say yes here you get support for the Dallas DS1286 RTC chips.
614 config RTC_DRV_DS1302
615 tristate "Dallas DS1302"
616 depends on SH_SECUREEDGE5410
618 If you say yes here you get support for the Dallas DS1302 RTC chips.
620 config RTC_DRV_DS1511
621 tristate "Dallas DS1511"
623 If you say yes here you get support for the
624 Dallas DS1511 timekeeping/watchdog chip.
626 This driver can also be built as a module. If so, the module
627 will be called rtc-ds1511.
629 config RTC_DRV_DS1553
630 tristate "Maxim/Dallas DS1553"
632 If you say yes here you get support for the
633 Maxim/Dallas DS1553 timekeeping chip.
635 This driver can also be built as a module. If so, the module
636 will be called rtc-ds1553.
638 config RTC_DRV_DS1742
639 tristate "Maxim/Dallas DS1742/1743"
641 If you say yes here you get support for the
642 Maxim/Dallas DS1742/1743 timekeeping chip.
644 This driver can also be built as a module. If so, the module
645 will be called rtc-ds1742.
647 config RTC_DRV_DA9052
648 tristate "Dialog DA9052/DA9053 RTC"
649 depends on PMIC_DA9052
651 Say y here to support the RTC driver for Dialog Semiconductor
652 DA9052-BC and DA9053-AA/Bx PMICs.
654 config RTC_DRV_DA9055
655 tristate "Dialog Semiconductor DA9055 RTC"
656 depends on MFD_DA9055
658 If you say yes here you will get support for the
659 RTC of the Dialog DA9055 PMIC.
661 This driver can also be built as a module. If so, the module
662 will be called rtc-da9055
668 If you say yes here you will get support for the EFI
671 This driver can also be built as a module. If so, the module
672 will be called rtc-efi.
674 config RTC_DRV_STK17TA8
675 tristate "Simtek STK17TA8"
677 If you say yes here you get support for the
678 Simtek STK17TA8 timekeeping chip.
680 This driver can also be built as a module. If so, the module
681 will be called rtc-stk17ta8.
683 config RTC_DRV_M48T86
684 tristate "ST M48T86/Dallas DS12887"
686 If you say Y here you will get support for the
687 ST M48T86 and Dallas DS12887 RTC chips.
689 This driver can also be built as a module. If so, the module
690 will be called rtc-m48t86.
692 config RTC_DRV_M48T35
695 If you say Y here you will get support for the
698 This driver can also be built as a module, if so, the module
699 will be called "rtc-m48t35".
701 config RTC_DRV_M48T59
702 tristate "ST M48T59/M48T08/M48T02"
704 If you say Y here you will get support for the
705 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
707 These chips are usually found in Sun SPARC and UltraSPARC
710 This driver can also be built as a module, if so, the module
711 will be called "rtc-m48t59".
713 config RTC_DRV_MSM6242
714 tristate "Oki MSM6242"
716 If you say yes here you get support for the Oki MSM6242
717 timekeeping chip. It is used in some Amiga models (e.g. A2000).
719 This driver can also be built as a module. If so, the module
720 will be called rtc-msm6242.
722 config RTC_DRV_BQ4802
725 If you say Y here you will get support for the TI
728 This driver can also be built as a module. If so, the module
729 will be called rtc-bq4802.
731 config RTC_DRV_RP5C01
732 tristate "Ricoh RP5C01"
734 If you say yes here you get support for the Ricoh RP5C01
735 timekeeping chip. It is used in some Amiga models (e.g. A3000
738 This driver can also be built as a module. If so, the module
739 will be called rtc-rp5c01.
742 tristate "EM Microelectronic V3020"
744 If you say yes here you will get support for the
745 EM Microelectronic v3020 RTC chip.
747 This driver can also be built as a module. If so, the module
748 will be called rtc-v3020.
750 config RTC_DRV_DS2404
751 tristate "Dallas DS2404"
753 If you say yes here you get support for the
754 Dallas DS2404 RTC chip.
756 This driver can also be built as a module. If so, the module
757 will be called rtc-ds2404.
759 config RTC_DRV_WM831X
760 tristate "Wolfson Microelectronics WM831x RTC"
761 depends on MFD_WM831X
763 If you say yes here you will get support for the RTC subsystem
764 of the Wolfson Microelectronics WM831X series PMICs.
766 This driver can also be built as a module. If so, the module
767 will be called "rtc-wm831x".
769 config RTC_DRV_WM8350
770 tristate "Wolfson Microelectronics WM8350 RTC"
771 depends on MFD_WM8350
773 If you say yes here you will get support for the RTC subsystem
774 of the Wolfson Microelectronics WM8350.
776 This driver can also be built as a module. If so, the module
777 will be called "rtc-wm8350".
780 tristate "SPEAR ST RTC"
781 depends on PLAT_SPEAR
784 If you say Y here you will get support for the RTC found on
787 config RTC_DRV_PCF50633
788 depends on MFD_PCF50633
789 tristate "NXP PCF50633 RTC"
791 If you say yes here you get support for the RTC subsystem of the
792 NXP PCF50633 used in embedded systems.
794 config RTC_DRV_AB3100
795 tristate "ST-Ericsson AB3100 RTC"
796 depends on AB3100_CORE
797 default y if AB3100_CORE
799 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
800 support. This chip contains a battery- and capacitor-backed RTC.
802 config RTC_DRV_AB8500
803 tristate "ST-Ericsson AB8500 RTC"
804 depends on AB8500_CORE
806 select RTC_INTF_DEV_UIE_EMUL
808 Select this to enable the ST-Ericsson AB8500 power management IC RTC
809 support. This chip contains a battery- and capacitor-backed RTC.
811 config RTC_DRV_NUC900
812 tristate "NUC910/NUC920 RTC driver"
813 depends on ARCH_W90X900
815 If you say yes here you get support for the RTC subsystem of the
816 NUC910/NUC920 used in embedded systems.
818 comment "on-CPU RTC drivers"
820 config RTC_DRV_DAVINCI
821 tristate "TI DaVinci RTC"
822 depends on ARCH_DAVINCI_DM365
824 If you say yes here you get support for the RTC on the
825 DaVinci platforms (DM365).
827 This driver can also be built as a module. If so, the module
828 will be called rtc-davinci.
831 tristate "Freescale IMX DryIce Real Time Clock"
834 Support for Freescale IMX DryIce RTC
836 This driver can also be built as a module, if so, the module
837 will be called "rtc-imxdi".
841 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
843 Say "yes" here to support the on chip real time clock
844 present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
846 This driver can also be built as a module, if so, module
847 will be called rtc-omap.
852 This will include RTC support for Samsung SoCs. If
853 you want to include RTC support for any machine, kindly
854 select this in the respective mach-XXXX/Kconfig file.
857 tristate "Samsung S3C series SoC RTC"
858 depends on ARCH_S3C64XX || HAVE_S3C_RTC
860 RTC (Realtime Clock) driver for the clock inbuilt into the
861 Samsung S3C24XX series of SoCs. This can provide periodic
862 interrupt rates from 1Hz to 64Hz for user programs, and
865 The driver currently supports the common features on all the
866 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
869 This driver can also be build as a module. If so, the module
870 will be called rtc-s3c.
872 config RTC_DRV_EP93XX
873 tristate "Cirrus Logic EP93XX"
874 depends on ARCH_EP93XX
876 If you say yes here you get support for the
877 RTC embedded in the Cirrus Logic EP93XX processors.
879 This driver can also be built as a module. If so, the module
880 will be called rtc-ep93xx.
882 config RTC_DRV_SA1100
883 tristate "SA11x0/PXA2xx/PXA910"
884 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
886 If you say Y here you will get access to the real time clock
887 built into your SA11x0 or PXA2xx CPU.
889 To compile this driver as a module, choose M here: the
890 module will be called rtc-sa1100.
893 tristate "SuperH On-Chip RTC"
894 depends on SUPERH && HAVE_CLK
896 Say Y here to enable support for the on-chip RTC found in
897 most SuperH processors.
899 To compile this driver as a module, choose M here: the
900 module will be called rtc-sh.
902 config RTC_DRV_VR41XX
903 tristate "NEC VR41XX"
904 depends on CPU_VR41XX
906 If you say Y here you will get access to the real time clock
907 built into your NEC VR41XX CPU.
909 To compile this driver as a module, choose M here: the
910 module will be called rtc-vr41xx.
913 tristate "ARM AMBA PL030 RTC"
916 If you say Y here you will get access to ARM AMBA
917 PrimeCell PL030 RTC found on certain ARM SOCs.
919 To compile this driver as a module, choose M here: the
920 module will be called rtc-pl030.
923 tristate "ARM AMBA PL031 RTC"
926 If you say Y here you will get access to ARM AMBA
927 PrimeCell PL031 RTC found on certain ARM SOCs.
929 To compile this driver as a module, choose M here: the
930 module will be called rtc-pl031.
932 config RTC_DRV_AT32AP700X
933 tristate "AT32AP700X series RTC"
934 depends on PLATFORM_AT32AP
936 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
937 AT32AP700x family processors.
939 config RTC_DRV_AT91RM9200
940 tristate "AT91RM9200 or some AT91SAM9 RTC"
943 Driver for the internal RTC (Realtime Clock) module found on
944 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
945 this is powered by the backup power supply.
947 config RTC_DRV_AT91SAM9
948 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
949 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
951 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
952 (Real Time Timer). These timers are powered by the backup power
953 supply (such as a small coin cell battery), but do not need to
956 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
957 dedicated RTC module and leave the RTT available for other uses.)
959 config RTC_DRV_AT91SAM9_RTT
963 prompt "RTT module Number" if ARCH_AT91SAM9263
964 depends on RTC_DRV_AT91SAM9
966 More than one RTT module is available. You can choose which
967 one will be used as an RTC. The default of zero is normally
968 OK to use, though some systems use that for non-RTC purposes.
970 config RTC_DRV_AT91SAM9_GPBR
972 range 0 3 if !ARCH_AT91SAM9263
973 range 0 15 if ARCH_AT91SAM9263
975 prompt "Backup Register Number"
976 depends on RTC_DRV_AT91SAM9
978 The RTC driver needs to use one of the General Purpose Backup
979 Registers (GPBRs) as well as the RTT. You can choose which one
980 will be used. The default of zero is normally OK to use, but
981 on some systems other software needs to use that register.
983 config RTC_DRV_AU1XXX
984 tristate "Au1xxx Counter0 RTC support"
985 depends on MIPS_ALCHEMY
987 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
988 counter) to be used as a RTC.
990 This driver can also be built as a module. If so, the module
991 will be called rtc-au1xxx.
994 tristate "Blackfin On-Chip RTC"
995 depends on BLACKFIN && !BF561
997 If you say yes here you will get support for the
998 Blackfin On-Chip Real Time Clock.
1000 This driver can also be built as a module. If so, the module
1001 will be called rtc-bfin.
1003 config RTC_DRV_RS5C313
1004 tristate "Ricoh RS5C313"
1005 depends on SH_LANDISK
1007 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1009 config RTC_DRV_GENERIC
1010 tristate "Generic RTC support"
1011 # Please consider writing a new RTC driver instead of using the generic
1013 depends on PARISC || M68K || PPC || SUPERH32
1015 Say Y or M here to enable RTC support on systems using the generic
1016 RTC abstraction. If you do not know what you are doing, you should
1020 tristate "PXA27x/PXA3xx"
1023 If you say Y here you will get access to the real time clock
1024 built into your PXA27x or PXA3xx CPU.
1026 This RTC driver uses PXA RTC registers available since pxa27x
1027 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1029 config RTC_DRV_VT8500
1030 tristate "VIA/WonderMedia 85xx SoC RTC"
1031 depends on ARCH_VT8500
1033 If you say Y here you will get access to the real time clock
1034 built into your VIA VT8500 SoC or its relatives.
1037 config RTC_DRV_SUN4V
1038 bool "SUN4V Hypervisor RTC"
1041 If you say Y here you will get support for the Hypervisor
1042 based RTC on SUN4V systems.
1044 config RTC_DRV_STARFIRE
1048 If you say Y here you will get support for the RTC found on
1051 config RTC_DRV_TX4939
1052 tristate "TX4939 SoC"
1053 depends on SOC_TX4939
1055 Driver for the internal RTC (Realtime Clock) module found on
1059 tristate "Marvell SoC RTC"
1060 depends on ARCH_KIRKWOOD || ARCH_DOVE
1062 If you say yes here you will get support for the in-chip RTC
1063 that can be found in some of Marvell's SoC devices, such as
1064 the Kirkwood 88F6281 and 88F6192.
1066 This driver can also be built as a module. If so, the module
1067 will be called rtc-mv.
1073 If you say yes here you will get support for the RTC on PS3.
1075 This driver can also be built as a module. If so, the module
1076 will be called rtc-ps3.
1078 config RTC_DRV_COH901331
1079 tristate "ST-Ericsson COH 901 331 RTC"
1080 depends on ARCH_U300
1082 If you say Y here you will get access to ST-Ericsson
1083 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1086 This driver can also be built as a module. If so, the module
1087 will be called "rtc-coh901331".
1091 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1094 If you say yes here you will get support for the onboard
1095 STMP3xxx/i.MX23/i.MX28 RTC.
1097 This driver can also be built as a module. If so, the module
1098 will be called rtc-stmp3xxx.
1104 If you say Y here you will get support for the RTC found on
1105 the PCAP2 ASIC used on some Motorola phones.
1107 config RTC_DRV_MC13XXX
1108 depends on MFD_MC13XXX
1109 tristate "Freescale MC13xxx RTC"
1111 This enables support for the RTCs found on Freescale's PMICs
1112 MC13783 and MC13892.
1114 config RTC_DRV_MPC5121
1115 tristate "Freescale MPC5121 built-in RTC"
1116 depends on PPC_MPC512x || PPC_MPC52xx
1118 If you say yes here you will get support for the
1119 built-in RTC on MPC5121 or on MPC5200.
1121 This driver can also be built as a module. If so, the module
1122 will be called rtc-mpc5121.
1124 config RTC_DRV_JZ4740
1125 tristate "Ingenic JZ4740 SoC"
1126 depends on MACH_JZ4740
1128 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1131 This driver can also be buillt as a module. If so, the module
1132 will be called rtc-jz4740.
1134 config RTC_DRV_LPC32XX
1135 depends on ARCH_LPC32XX
1136 tristate "NXP LPC32XX RTC"
1138 This enables support for the NXP RTC in the LPC32XX
1140 This driver can also be buillt as a module. If so, the module
1141 will be called rtc-lpc32xx.
1143 config RTC_DRV_PM8XXX
1144 tristate "Qualcomm PMIC8XXX RTC"
1145 depends on MFD_PM8XXX
1147 If you say yes here you get support for the
1148 Qualcomm PMIC8XXX RTC.
1150 To compile this driver as a module, choose M here: the
1151 module will be called rtc-pm8xxx.
1153 config RTC_DRV_TEGRA
1154 tristate "NVIDIA Tegra Internal RTC driver"
1155 depends on ARCH_TEGRA
1157 If you say yes here you get support for the
1158 Tegra 200 series internal RTC module.
1160 This drive can also be built as a module. If so, the module
1161 will be called rtc-tegra.
1164 tristate "Tilera hypervisor RTC support"
1167 Enable support for the Linux driver side of the Tilera
1168 hypervisor's real-time clock interface.
1171 tristate "PKUnity v3 RTC support"
1172 depends on ARCH_PUV3
1174 This enables support for the RTC in the PKUnity-v3 SoCs.
1176 This drive can also be built as a module. If so, the module
1177 will be called rtc-puv3.
1179 config RTC_DRV_LOONGSON1
1180 tristate "loongson1 RTC support"
1181 depends on MACH_LOONGSON1
1183 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1184 counter) to be used as a RTC.
1186 This driver can also be built as a module. If so, the module
1187 will be called rtc-ls1x.
1190 tristate "Freescale MXC Real Time Clock"
1193 If you say yes here you get support for the Freescale MXC
1196 This driver can also be built as a module, if so, the module
1197 will be called "rtc-mxc".
1200 tristate "Freescale SNVS RTC support"
1201 depends on HAS_IOMEM
1204 If you say yes here you get support for the Freescale SNVS
1205 Low Power (LP) RTC module.
1207 This driver can also be built as a module, if so, the module
1208 will be called "rtc-snvs".