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_MAX8997
253 tristate "Maxim MAX8997"
254 depends on MFD_MAX8997
256 If you say yes here you will get support for the
257 RTC of Maxim MAX8997 PMIC.
259 This driver can also be built as a module. If so, the module
260 will be called rtc-max8997.
262 config RTC_DRV_MAX77686
263 tristate "Maxim MAX77686"
264 depends on MFD_MAX77686
266 If you say yes here you will get support for the
267 RTC of Maxim MAX77686 PMIC.
269 This driver can also be built as a module. If so, the module
270 will be called rtc-max77686.
272 config RTC_DRV_RS5C372
273 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
275 If you say yes here you get support for the
276 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
278 This driver can also be built as a module. If so, the module
279 will be called rtc-rs5c372.
281 config RTC_DRV_ISL1208
282 tristate "Intersil ISL1208"
284 If you say yes here you get support for the
285 Intersil ISL1208 RTC chip.
287 This driver can also be built as a module. If so, the module
288 will be called rtc-isl1208.
290 config RTC_DRV_ISL12022
291 tristate "Intersil ISL12022"
293 If you say yes here you get support for the
294 Intersil ISL12022 RTC chip.
296 This driver can also be built as a module. If so, the module
297 will be called rtc-isl12022.
300 tristate "Xicor/Intersil X1205"
302 If you say yes here you get support for the
303 Xicor/Intersil X1205 RTC chip.
305 This driver can also be built as a module. If so, the module
306 will be called rtc-x1205.
308 config RTC_DRV_PCF8523
309 tristate "NXP PCF8523"
311 If you say yes here you get support for the NXP PCF8523 RTC
314 This driver can also be built as a module. If so, the module
315 will be called rtc-pcf8523.
317 config RTC_DRV_PCF8563
318 tristate "Philips PCF8563/Epson RTC8564"
320 If you say yes here you get support for the
321 Philips PCF8563 RTC chip. The Epson RTC8564
324 This driver can also be built as a module. If so, the module
325 will be called rtc-pcf8563.
327 config RTC_DRV_PCF8583
328 tristate "Philips PCF8583"
330 If you say yes here you get support for the Philips PCF8583
331 RTC chip found on Acorn RiscPCs. This driver supports the
332 platform specific method of retrieving the current year from
333 the RTC's SRAM. It will work on other platforms with the same
334 chip, but the year will probably have to be tweaked.
336 This driver can also be built as a module. If so, the module
337 will be called rtc-pcf8583.
339 config RTC_DRV_M41T80
340 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
342 If you say Y here you will get support for the ST M41T60
343 and M41T80 RTC chips series. Currently, the following chips are
344 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
345 M41ST85, and M41ST87.
347 This driver can also be built as a module. If so, the module
348 will be called rtc-m41t80.
350 config RTC_DRV_M41T80_WDT
351 bool "ST M41T65/M41T80 series RTC watchdog timer"
352 depends on RTC_DRV_M41T80
354 If you say Y here you will get support for the
355 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
358 tristate "TI BQ32000"
360 If you say Y here you will get support for the TI
361 BQ32000 I2C RTC chip.
363 This driver can also be built as a module. If so, the module
364 will be called rtc-bq32k.
366 config RTC_DRV_DM355EVM
367 tristate "TI DaVinci DM355 EVM RTC"
368 depends on MFD_DM355EVM_MSP
370 Supports the RTC firmware in the MSP430 on the DM355 EVM.
372 config RTC_DRV_TWL92330
373 boolean "TI TWL92330/Menelaus"
376 If you say yes here you get support for the RTC on the
377 TWL92330 "Menelaus" power management chip, used with OMAP2
378 platforms. The support is integrated with the rest of
379 the Menelaus driver; it's not separate module.
381 config RTC_DRV_TWL4030
382 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
383 depends on TWL4030_CORE
385 If you say yes here you get support for the RTC on the
386 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
388 This driver can also be built as a module. If so, the module
389 will be called rtc-twl.
391 config RTC_DRV_TPS6586X
392 tristate "TI TPS6586X RTC driver"
393 depends on MFD_TPS6586X
395 TI Power Managment IC TPS6586X supports RTC functionality
396 along with alarm. This driver supports the RTC driver for
397 the TPS6586X RTC module.
399 config RTC_DRV_TPS65910
400 tristate "TI TPS65910 RTC driver"
401 depends on RTC_CLASS && MFD_TPS65910
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-tps65910.
409 config RTC_DRV_TPS80031
410 tristate "TI TPS80031/TPS80032 RTC driver"
411 depends on MFD_TPS80031
413 TI Power Managment IC TPS80031 supports RTC functionality
414 along with alarm. This driver supports the RTC driver for
415 the TPS80031 RTC module.
417 config RTC_DRV_RC5T583
418 tristate "RICOH 5T583 RTC driver"
419 depends on MFD_RC5T583
421 If you say yes here you get support for the RTC on the
424 This driver can also be built as a module. If so, the module
425 will be called rtc-rc5t583.
427 config RTC_DRV_S35390A
428 tristate "Seiko Instruments S-35390A"
431 If you say yes here you will get support for the Seiko
432 Instruments S-35390A.
434 This driver can also be built as a module. If so the module
435 will be called rtc-s35390a.
437 config RTC_DRV_FM3130
438 tristate "Ramtron FM3130"
440 If you say Y here you will get support for the
441 Ramtron FM3130 RTC chips.
442 Ramtron FM3130 is a chip with two separate devices inside,
443 RTC clock and FRAM. This driver provides only RTC functionality.
445 This driver can also be built as a module. If so the module
446 will be called rtc-fm3130.
448 config RTC_DRV_RX8581
449 tristate "Epson RX-8581"
451 If you say yes here you will get support for the Epson RX-8581.
453 This driver can also be built as a module. If so the module
454 will be called rtc-rx8581.
456 config RTC_DRV_RX8025
457 tristate "Epson RX-8025SA/NB"
459 If you say yes here you get support for the Epson
460 RX-8025SA/NB RTC chips.
462 This driver can also be built as a module. If so, the module
463 will be called rtc-rx8025.
465 config RTC_DRV_EM3027
466 tristate "EM Microelectronic EM3027"
468 If you say yes here you get support for the EM
469 Microelectronic EM3027 RTC chips.
471 This driver can also be built as a module. If so, the module
472 will be called rtc-em3027.
474 config RTC_DRV_RV3029C2
475 tristate "Micro Crystal RTC"
477 If you say yes here you get support for the Micro Crystal
480 This driver can also be built as a module. If so, the module
481 will be called rtc-rv3029c2.
485 comment "SPI RTC drivers"
489 config RTC_DRV_M41T93
492 If you say yes here you will get support for the
493 ST M41T93 SPI RTC chip.
495 This driver can also be built as a module. If so, the module
496 will be called rtc-m41t93.
498 config RTC_DRV_M41T94
501 If you say yes here you will get support for the
502 ST M41T94 SPI RTC chip.
504 This driver can also be built as a module. If so, the module
505 will be called rtc-m41t94.
507 config RTC_DRV_DS1305
508 tristate "Dallas/Maxim DS1305/DS1306"
510 Select this driver to get support for the Dallas/Maxim DS1305
511 and DS1306 real time clock chips. These support a trickle
512 charger, alarms, and NVRAM in addition to the clock.
514 This driver can also be built as a module. If so, the module
515 will be called rtc-ds1305.
517 config RTC_DRV_DS1390
518 tristate "Dallas/Maxim DS1390/93/94"
520 If you say yes here you get support for the
521 Dallas/Maxim DS1390/93/94 chips.
523 This driver only supports the RTC feature, and not other chip
524 features such as alarms and trickle charging.
526 This driver can also be built as a module. If so, the module
527 will be called rtc-ds1390.
529 config RTC_DRV_MAX6902
530 tristate "Maxim MAX6902"
532 If you say yes here you will get support for the
533 Maxim MAX6902 SPI RTC chip.
535 This driver can also be built as a module. If so, the module
536 will be called rtc-max6902.
539 tristate "Epson RTC-9701JE"
541 If you say yes here you will get support for the
542 Epson RTC-9701JE SPI RTC chip.
544 This driver can also be built as a module. If so, the module
545 will be called rtc-r9701.
547 config RTC_DRV_RS5C348
548 tristate "Ricoh RS5C348A/B"
550 If you say yes here you get support for the
551 Ricoh RS5C348A and RS5C348B RTC chips.
553 This driver can also be built as a module. If so, the module
554 will be called rtc-rs5c348.
556 config RTC_DRV_DS3234
557 tristate "Maxim/Dallas DS3234"
559 If you say yes here you get support for the
560 Maxim/Dallas DS3234 SPI RTC chip.
562 This driver can also be built as a module. If so, the module
563 will be called rtc-ds3234.
565 config RTC_DRV_PCF2123
566 tristate "NXP PCF2123"
568 If you say yes here you get support for the NXP PCF2123
571 This driver can also be built as a module. If so, the module
572 will be called rtc-pcf2123.
574 config RTC_DRV_RX4581
575 tristate "Epson RX-4581"
577 If you say yes here you will get support for the Epson RX-4581.
579 This driver can also be built as a module. If so the module
580 will be called rtc-rx4581.
584 comment "Platform RTC drivers"
586 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
587 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
588 # global rtc_lock ... it's not yet just another platform_device.
591 tristate "PC-style 'CMOS'"
592 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
595 Say "yes" here to get direct support for the real time clock
596 found in every PC or ACPI-based system, and some other boards.
597 Specifically the original MC146818, compatibles like those in
598 PC south bridges, the DS12887 or M48T86, some multifunction
599 or LPC bus chips, and so on.
601 Your system will need to define the platform device used by
602 this driver, otherwise it won't be accessible. This means
603 you can safely enable this driver if you don't know whether
604 or not your board has this kind of hardware.
606 This driver can also be built as a module. If so, the module
607 will be called rtc-cmos.
610 tristate "Virtual RTC for Intel MID platforms"
611 depends on X86_INTEL_MID
612 default y if X86_INTEL_MID
615 Say "yes" here to get direct support for the real time clock
616 found on Moorestown platforms. The VRTC is a emulated RTC that
617 derives its clock source from a real RTC in the PMIC. The MC146818
618 style programming interface is mostly conserved, but any
619 updates are done via IPC calls to the system controller FW.
621 config RTC_DRV_DS1216
622 tristate "Dallas DS1216"
625 If you say yes here you get support for the Dallas DS1216 RTC chips.
627 config RTC_DRV_DS1286
628 tristate "Dallas DS1286"
630 If you say yes here you get support for the Dallas DS1286 RTC chips.
632 config RTC_DRV_DS1302
633 tristate "Dallas DS1302"
634 depends on SH_SECUREEDGE5410
636 If you say yes here you get support for the Dallas DS1302 RTC chips.
638 config RTC_DRV_DS1511
639 tristate "Dallas DS1511"
641 If you say yes here you get support for the
642 Dallas DS1511 timekeeping/watchdog chip.
644 This driver can also be built as a module. If so, the module
645 will be called rtc-ds1511.
647 config RTC_DRV_DS1553
648 tristate "Maxim/Dallas DS1553"
650 If you say yes here you get support for the
651 Maxim/Dallas DS1553 timekeeping chip.
653 This driver can also be built as a module. If so, the module
654 will be called rtc-ds1553.
656 config RTC_DRV_DS1742
657 tristate "Maxim/Dallas DS1742/1743"
659 If you say yes here you get support for the
660 Maxim/Dallas DS1742/1743 timekeeping chip.
662 This driver can also be built as a module. If so, the module
663 will be called rtc-ds1742.
665 config RTC_DRV_DA9052
666 tristate "Dialog DA9052/DA9053 RTC"
667 depends on PMIC_DA9052
669 Say y here to support the RTC driver for Dialog Semiconductor
670 DA9052-BC and DA9053-AA/Bx PMICs.
672 config RTC_DRV_DA9055
673 tristate "Dialog Semiconductor DA9055 RTC"
674 depends on MFD_DA9055
676 If you say yes here you will get support for the
677 RTC of the Dialog DA9055 PMIC.
679 This driver can also be built as a module. If so, the module
680 will be called rtc-da9055
686 If you say yes here you will get support for the EFI
689 This driver can also be built as a module. If so, the module
690 will be called rtc-efi.
692 config RTC_DRV_STK17TA8
693 tristate "Simtek STK17TA8"
695 If you say yes here you get support for the
696 Simtek STK17TA8 timekeeping chip.
698 This driver can also be built as a module. If so, the module
699 will be called rtc-stk17ta8.
701 config RTC_DRV_M48T86
702 tristate "ST M48T86/Dallas DS12887"
704 If you say Y here you will get support for the
705 ST M48T86 and Dallas DS12887 RTC chips.
707 This driver can also be built as a module. If so, the module
708 will be called rtc-m48t86.
710 config RTC_DRV_M48T35
713 If you say Y here you will get support for the
716 This driver can also be built as a module, if so, the module
717 will be called "rtc-m48t35".
719 config RTC_DRV_M48T59
720 tristate "ST M48T59/M48T08/M48T02"
722 If you say Y here you will get support for the
723 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
725 These chips are usually found in Sun SPARC and UltraSPARC
728 This driver can also be built as a module, if so, the module
729 will be called "rtc-m48t59".
731 config RTC_DRV_MSM6242
732 tristate "Oki MSM6242"
734 If you say yes here you get support for the Oki MSM6242
735 timekeeping chip. It is used in some Amiga models (e.g. A2000).
737 This driver can also be built as a module. If so, the module
738 will be called rtc-msm6242.
740 config RTC_DRV_BQ4802
743 If you say Y here you will get support for the TI
746 This driver can also be built as a module. If so, the module
747 will be called rtc-bq4802.
749 config RTC_DRV_RP5C01
750 tristate "Ricoh RP5C01"
752 If you say yes here you get support for the Ricoh RP5C01
753 timekeeping chip. It is used in some Amiga models (e.g. A3000
756 This driver can also be built as a module. If so, the module
757 will be called rtc-rp5c01.
760 tristate "EM Microelectronic V3020"
762 If you say yes here you will get support for the
763 EM Microelectronic v3020 RTC chip.
765 This driver can also be built as a module. If so, the module
766 will be called rtc-v3020.
768 config RTC_DRV_DS2404
769 tristate "Dallas DS2404"
771 If you say yes here you get support for the
772 Dallas DS2404 RTC chip.
774 This driver can also be built as a module. If so, the module
775 will be called rtc-ds2404.
777 config RTC_DRV_WM831X
778 tristate "Wolfson Microelectronics WM831x RTC"
779 depends on MFD_WM831X
781 If you say yes here you will get support for the RTC subsystem
782 of the Wolfson Microelectronics WM831X series PMICs.
784 This driver can also be built as a module. If so, the module
785 will be called "rtc-wm831x".
787 config RTC_DRV_WM8350
788 tristate "Wolfson Microelectronics WM8350 RTC"
789 depends on MFD_WM8350
791 If you say yes here you will get support for the RTC subsystem
792 of the Wolfson Microelectronics WM8350.
794 This driver can also be built as a module. If so, the module
795 will be called "rtc-wm8350".
798 tristate "SPEAR ST RTC"
799 depends on PLAT_SPEAR
802 If you say Y here you will get support for the RTC found on
805 config RTC_DRV_PCF50633
806 depends on MFD_PCF50633
807 tristate "NXP PCF50633 RTC"
809 If you say yes here you get support for the RTC subsystem of the
810 NXP PCF50633 used in embedded systems.
812 config RTC_DRV_AB3100
813 tristate "ST-Ericsson AB3100 RTC"
814 depends on AB3100_CORE
815 default y if AB3100_CORE
817 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
818 support. This chip contains a battery- and capacitor-backed RTC.
820 config RTC_DRV_AB8500
821 tristate "ST-Ericsson AB8500 RTC"
822 depends on AB8500_CORE
824 select RTC_INTF_DEV_UIE_EMUL
826 Select this to enable the ST-Ericsson AB8500 power management IC RTC
827 support. This chip contains a battery- and capacitor-backed RTC.
829 config RTC_DRV_NUC900
830 tristate "NUC910/NUC920 RTC driver"
831 depends on ARCH_W90X900
833 If you say yes here you get support for the RTC subsystem of the
834 NUC910/NUC920 used in embedded systems.
836 comment "on-CPU RTC drivers"
838 config RTC_DRV_DAVINCI
839 tristate "TI DaVinci RTC"
840 depends on ARCH_DAVINCI_DM365
842 If you say yes here you get support for the RTC on the
843 DaVinci platforms (DM365).
845 This driver can also be built as a module. If so, the module
846 will be called rtc-davinci.
849 tristate "Freescale IMX DryIce Real Time Clock"
852 Support for Freescale IMX DryIce RTC
854 This driver can also be built as a module, if so, the module
855 will be called "rtc-imxdi".
859 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
861 Say "yes" here to support the on chip real time clock
862 present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
864 This driver can also be built as a module, if so, module
865 will be called rtc-omap.
870 This will include RTC support for Samsung SoCs. If
871 you want to include RTC support for any machine, kindly
872 select this in the respective mach-XXXX/Kconfig file.
875 tristate "Samsung S3C series SoC RTC"
876 depends on ARCH_S3C64XX || HAVE_S3C_RTC
878 RTC (Realtime Clock) driver for the clock inbuilt into the
879 Samsung S3C24XX series of SoCs. This can provide periodic
880 interrupt rates from 1Hz to 64Hz for user programs, and
883 The driver currently supports the common features on all the
884 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
887 This driver can also be build as a module. If so, the module
888 will be called rtc-s3c.
890 config RTC_DRV_EP93XX
891 tristate "Cirrus Logic EP93XX"
892 depends on ARCH_EP93XX
894 If you say yes here you get support for the
895 RTC embedded in the Cirrus Logic EP93XX processors.
897 This driver can also be built as a module. If so, the module
898 will be called rtc-ep93xx.
900 config RTC_DRV_SA1100
901 tristate "SA11x0/PXA2xx/PXA910"
902 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
904 If you say Y here you will get access to the real time clock
905 built into your SA11x0 or PXA2xx CPU.
907 To compile this driver as a module, choose M here: the
908 module will be called rtc-sa1100.
911 tristate "SuperH On-Chip RTC"
912 depends on SUPERH && HAVE_CLK
914 Say Y here to enable support for the on-chip RTC found in
915 most SuperH processors.
917 To compile this driver as a module, choose M here: the
918 module will be called rtc-sh.
920 config RTC_DRV_VR41XX
921 tristate "NEC VR41XX"
922 depends on CPU_VR41XX
924 If you say Y here you will get access to the real time clock
925 built into your NEC VR41XX CPU.
927 To compile this driver as a module, choose M here: the
928 module will be called rtc-vr41xx.
931 tristate "ARM AMBA PL030 RTC"
934 If you say Y here you will get access to ARM AMBA
935 PrimeCell PL030 RTC found on certain ARM SOCs.
937 To compile this driver as a module, choose M here: the
938 module will be called rtc-pl030.
941 tristate "ARM AMBA PL031 RTC"
944 If you say Y here you will get access to ARM AMBA
945 PrimeCell PL031 RTC found on certain ARM SOCs.
947 To compile this driver as a module, choose M here: the
948 module will be called rtc-pl031.
950 config RTC_DRV_AT32AP700X
951 tristate "AT32AP700X series RTC"
952 depends on PLATFORM_AT32AP
954 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
955 AT32AP700x family processors.
957 config RTC_DRV_AT91RM9200
958 tristate "AT91RM9200 or some AT91SAM9 RTC"
961 Driver for the internal RTC (Realtime Clock) module found on
962 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
963 this is powered by the backup power supply.
965 config RTC_DRV_AT91SAM9
966 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
967 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
969 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
970 (Real Time Timer). These timers are powered by the backup power
971 supply (such as a small coin cell battery), but do not need to
974 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
975 dedicated RTC module and leave the RTT available for other uses.)
977 config RTC_DRV_AT91SAM9_RTT
981 prompt "RTT module Number" if ARCH_AT91SAM9263
982 depends on RTC_DRV_AT91SAM9
984 More than one RTT module is available. You can choose which
985 one will be used as an RTC. The default of zero is normally
986 OK to use, though some systems use that for non-RTC purposes.
988 config RTC_DRV_AT91SAM9_GPBR
990 range 0 3 if !ARCH_AT91SAM9263
991 range 0 15 if ARCH_AT91SAM9263
993 prompt "Backup Register Number"
994 depends on RTC_DRV_AT91SAM9
996 The RTC driver needs to use one of the General Purpose Backup
997 Registers (GPBRs) as well as the RTT. You can choose which one
998 will be used. The default of zero is normally OK to use, but
999 on some systems other software needs to use that register.
1001 config RTC_DRV_AU1XXX
1002 tristate "Au1xxx Counter0 RTC support"
1003 depends on MIPS_ALCHEMY
1005 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1006 counter) to be used as a RTC.
1008 This driver can also be built as a module. If so, the module
1009 will be called rtc-au1xxx.
1012 tristate "Blackfin On-Chip RTC"
1013 depends on BLACKFIN && !BF561
1015 If you say yes here you will get support for the
1016 Blackfin On-Chip Real Time Clock.
1018 This driver can also be built as a module. If so, the module
1019 will be called rtc-bfin.
1021 config RTC_DRV_RS5C313
1022 tristate "Ricoh RS5C313"
1023 depends on SH_LANDISK
1025 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1027 config RTC_DRV_GENERIC
1028 tristate "Generic RTC support"
1029 # Please consider writing a new RTC driver instead of using the generic
1031 depends on PARISC || M68K || PPC || SUPERH32
1033 Say Y or M here to enable RTC support on systems using the generic
1034 RTC abstraction. If you do not know what you are doing, you should
1038 tristate "PXA27x/PXA3xx"
1041 If you say Y here you will get access to the real time clock
1042 built into your PXA27x or PXA3xx CPU.
1044 This RTC driver uses PXA RTC registers available since pxa27x
1045 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1047 config RTC_DRV_VT8500
1048 tristate "VIA/WonderMedia 85xx SoC RTC"
1049 depends on ARCH_VT8500
1051 If you say Y here you will get access to the real time clock
1052 built into your VIA VT8500 SoC or its relatives.
1055 config RTC_DRV_SUN4V
1056 bool "SUN4V Hypervisor RTC"
1059 If you say Y here you will get support for the Hypervisor
1060 based RTC on SUN4V systems.
1062 config RTC_DRV_STARFIRE
1066 If you say Y here you will get support for the RTC found on
1069 config RTC_DRV_TX4939
1070 tristate "TX4939 SoC"
1071 depends on SOC_TX4939
1073 Driver for the internal RTC (Realtime Clock) module found on
1077 tristate "Marvell SoC RTC"
1078 depends on ARCH_KIRKWOOD || ARCH_DOVE || ARCH_MVEBU
1080 If you say yes here you will get support for the in-chip RTC
1081 that can be found in some of Marvell's SoC devices, such as
1082 the Kirkwood 88F6281 and 88F6192.
1084 This driver can also be built as a module. If so, the module
1085 will be called rtc-mv.
1091 If you say yes here you will get support for the RTC on PS3.
1093 This driver can also be built as a module. If so, the module
1094 will be called rtc-ps3.
1096 config RTC_DRV_COH901331
1097 tristate "ST-Ericsson COH 901 331 RTC"
1098 depends on ARCH_U300
1100 If you say Y here you will get access to ST-Ericsson
1101 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1104 This driver can also be built as a module. If so, the module
1105 will be called "rtc-coh901331".
1109 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1112 If you say yes here you will get support for the onboard
1113 STMP3xxx/i.MX23/i.MX28 RTC.
1115 This driver can also be built as a module. If so, the module
1116 will be called rtc-stmp3xxx.
1122 If you say Y here you will get support for the RTC found on
1123 the PCAP2 ASIC used on some Motorola phones.
1125 config RTC_DRV_MC13XXX
1126 depends on MFD_MC13XXX
1127 tristate "Freescale MC13xxx RTC"
1129 This enables support for the RTCs found on Freescale's PMICs
1130 MC13783 and MC13892.
1132 config RTC_DRV_MPC5121
1133 tristate "Freescale MPC5121 built-in RTC"
1134 depends on PPC_MPC512x || PPC_MPC52xx
1136 If you say yes here you will get support for the
1137 built-in RTC on MPC5121 or on MPC5200.
1139 This driver can also be built as a module. If so, the module
1140 will be called rtc-mpc5121.
1142 config RTC_DRV_JZ4740
1143 tristate "Ingenic JZ4740 SoC"
1144 depends on MACH_JZ4740
1146 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1149 This driver can also be buillt as a module. If so, the module
1150 will be called rtc-jz4740.
1152 config RTC_DRV_LPC32XX
1153 depends on ARCH_LPC32XX
1154 tristate "NXP LPC32XX RTC"
1156 This enables support for the NXP RTC in the LPC32XX
1158 This driver can also be buillt as a module. If so, the module
1159 will be called rtc-lpc32xx.
1161 config RTC_DRV_PM8XXX
1162 tristate "Qualcomm PMIC8XXX RTC"
1163 depends on MFD_PM8XXX
1165 If you say yes here you get support for the
1166 Qualcomm PMIC8XXX RTC.
1168 To compile this driver as a module, choose M here: the
1169 module will be called rtc-pm8xxx.
1171 config RTC_DRV_TEGRA
1172 tristate "NVIDIA Tegra Internal RTC driver"
1173 depends on ARCH_TEGRA
1175 If you say yes here you get support for the
1176 Tegra 200 series internal RTC module.
1178 This drive can also be built as a module. If so, the module
1179 will be called rtc-tegra.
1182 tristate "Tilera hypervisor RTC support"
1185 Enable support for the Linux driver side of the Tilera
1186 hypervisor's real-time clock interface.
1189 tristate "PKUnity v3 RTC support"
1190 depends on ARCH_PUV3
1192 This enables support for the RTC in the PKUnity-v3 SoCs.
1194 This drive can also be built as a module. If so, the module
1195 will be called rtc-puv3.
1197 config RTC_DRV_LOONGSON1
1198 tristate "loongson1 RTC support"
1199 depends on MACH_LOONGSON1
1201 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1202 counter) to be used as a RTC.
1204 This driver can also be built as a module. If so, the module
1205 will be called rtc-ls1x.
1208 tristate "Freescale MXC Real Time Clock"
1211 If you say yes here you get support for the Freescale MXC
1214 This driver can also be built as a module, if so, the module
1215 will be called "rtc-mxc".
1218 tristate "Freescale SNVS RTC support"
1219 depends on HAS_IOMEM
1222 If you say yes here you get support for the Freescale SNVS
1223 Low Power (LP) RTC module.
1225 This driver can also be built as a module, if so, the module
1226 will be called "rtc-snvs".
1228 comment "HID Sensor RTC drivers"
1230 config RTC_DRV_HID_SENSOR_TIME
1231 tristate "HID Sensor Time"
1234 select HID_SENSOR_HUB
1235 select HID_SENSOR_IIO_COMMON
1237 Say yes here to build support for the HID Sensors of type Time.
1238 This drivers makes such sensors available as RTCs.
1240 If this driver is compiled as a module, it will be named
1241 rtc-hid-sensor-time.