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"
24 If you say yes here, the system time (wall clock) will be set using
25 the value read from a specified RTC device. This is useful to avoid
26 unnecessary fsck runs at boot time, and to network better.
29 bool "Set the RTC time based on NTP synchronization"
32 If you say yes here, the system time (wall clock) will be stored
33 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
34 minutes if userspace reports synchronized NTP status.
36 config RTC_HCTOSYS_DEVICE
37 string "RTC used to set the system time"
38 depends on RTC_HCTOSYS = y || RTC_SYSTOHC = y
41 The RTC device that will be used to (re)initialize the system
42 clock, usually rtc0. Initialization is done when the system
43 starts up, and when it resumes from a low power state. This
44 device should record time in UTC, since the kernel won't do
47 The driver for this RTC device must be loaded before late_initcall
48 functions run, so it must usually be statically linked.
50 This clock should be battery-backed, so that it reads the correct
51 time when the system boots from a power-off state. Otherwise, your
52 system will need an external clock source (like an NTP server).
54 If the clock you specify here is not battery backed, it may still
55 be useful to reinitialize system time when resuming from system
56 sleep states. Do not specify an RTC here unless it stays powered
57 during all this system's supported sleep states.
60 bool "RTC debug support"
62 Say yes here to enable debugging support in the RTC framework
63 and individual RTC drivers.
65 comment "RTC interfaces"
68 boolean "/sys/class/rtc/rtcN (sysfs)"
72 Say yes here if you want to use your RTCs using sysfs interfaces,
73 /sys/class/rtc/rtc0 through /sys/.../rtcN.
78 boolean "/proc/driver/rtc (procfs for rtcN)"
82 Say yes here if you want to use your system clock RTC through
83 the proc interface, /proc/driver/rtc.
84 Other RTCs will not be available through that API.
85 If there is no RTC for the system clock, then the first RTC(rtc0)
91 boolean "/dev/rtcN (character devices)"
94 Say yes here if you want to use your RTCs using the /dev
95 interfaces, which "udev" sets up as /dev/rtc0 through
98 You may want to set up a symbolic link so one of these
99 can be accessed as /dev/rtc, which is a name
100 expected by "hwclock" and some other programs. Recent
101 versions of "udev" are known to set up the symlink for you.
105 config RTC_INTF_DEV_UIE_EMUL
106 bool "RTC UIE emulation on dev interface"
107 depends on RTC_INTF_DEV
109 Provides an emulation for RTC_UIE if the underlying rtc chip
110 driver does not expose RTC_UIE ioctls. Those requests generate
111 once-per-second update interrupts, used for synchronization.
113 The emulation code will read the time from the hardware
114 clock several times per second, please enable this option
115 only if you know that you really need it.
118 tristate "Test driver/device"
120 If you say yes here you get support for the
121 RTC test driver. It's a software RTC which can be
122 used to test the RTC subsystem APIs. It gets
123 the time from the system clock.
124 You want this driver only if you are doing development
125 on the RTC subsystem. Please read the source code
128 This driver can also be built as a module. If so, the module
129 will be called rtc-test.
131 comment "I2C RTC drivers"
136 config RTC_DRV_88PM860X
137 tristate "Marvell 88PM860x"
138 depends on I2C && MFD_88PM860X
140 If you say yes here you get support for RTC function in Marvell
143 This driver can also be built as a module. If so, the module
144 will be called rtc-88pm860x.
146 config RTC_DRV_88PM80X
147 tristate "Marvell 88PM80x"
148 depends on I2C && MFD_88PM800
150 If you say yes here you get support for RTC function in Marvell
153 This driver can also be built as a module. If so, the module
154 will be called rtc-88pm80x.
156 config RTC_DRV_AS3722
157 tristate "ams AS3722 RTC driver"
158 depends on MFD_AS3722
160 If you say yes here you get support for the RTC of ams AS3722 PMIC
163 This driver can also be built as a module. If so, the module
164 will be called rtc-as3722.
166 config RTC_DRV_DS1307
167 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
169 If you say yes here you get support for various compatible RTC
170 chips (often with battery backup) connected with I2C. This driver
171 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
172 EPSON RX-8025 and probably other chips. In some cases the RTC
173 must already have been initialized (by manufacturing or a
176 The first seven registers on these chips hold an RTC, and other
177 registers may add features such as NVRAM, a trickle charger for
178 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
179 sysfs, but other chip features may not be available.
181 This driver can also be built as a module. If so, the module
182 will be called rtc-ds1307.
184 config RTC_DRV_DS1374
185 tristate "Dallas/Maxim DS1374"
188 If you say yes here you get support for Dallas Semiconductor
189 DS1374 real-time clock chips. If an interrupt is associated
190 with the device, the alarm functionality is supported.
192 This driver can also be built as a module. If so, the module
193 will be called rtc-ds1374.
195 config RTC_DRV_DS1672
196 tristate "Dallas/Maxim DS1672"
198 If you say yes here you get support for the
199 Dallas/Maxim DS1672 timekeeping chip.
201 This driver can also be built as a module. If so, the module
202 will be called rtc-ds1672.
204 config RTC_DRV_DS3232
205 tristate "Dallas/Maxim DS3232"
208 If you say yes here you get support for Dallas Semiconductor
209 DS3232 real-time clock chips. If an interrupt is associated
210 with the device, the alarm functionality is supported.
212 This driver can also be built as a module. If so, the module
213 will be called rtc-ds3232.
215 config RTC_DRV_LP8788
216 tristate "TI LP8788 RTC driver"
217 depends on MFD_LP8788
219 Say Y to enable support for the LP8788 RTC/ALARM driver.
221 config RTC_DRV_MAX6900
222 tristate "Maxim MAX6900"
224 If you say yes here you will get support for the
225 Maxim MAX6900 I2C RTC chip.
227 This driver can also be built as a module. If so, the module
228 will be called rtc-max6900.
230 config RTC_DRV_MAX8907
231 tristate "Maxim MAX8907"
232 depends on MFD_MAX8907
234 If you say yes here you will get support for the
235 RTC of Maxim MAX8907 PMIC.
237 This driver can also be built as a module. If so, the module
238 will be called rtc-max8907.
240 config RTC_DRV_MAX8925
241 tristate "Maxim MAX8925"
242 depends on MFD_MAX8925
244 If you say yes here you will get support for the
245 RTC of Maxim MAX8925 PMIC.
247 This driver can also be built as a module. If so, the module
248 will be called rtc-max8925.
250 config RTC_DRV_MAX8998
251 tristate "Maxim MAX8998"
252 depends on MFD_MAX8998
254 If you say yes here you will get support for the
255 RTC of Maxim MAX8998 PMIC.
257 This driver can also be built as a module. If so, the module
258 will be called rtc-max8998.
260 config RTC_DRV_MAX8997
261 tristate "Maxim MAX8997"
262 depends on MFD_MAX8997
264 If you say yes here you will get support for the
265 RTC of Maxim MAX8997 PMIC.
267 This driver can also be built as a module. If so, the module
268 will be called rtc-max8997.
270 config RTC_DRV_MAX77686
271 tristate "Maxim MAX77686"
272 depends on MFD_MAX77686
274 If you say yes here you will get support for the
275 RTC of Maxim MAX77686 PMIC.
277 This driver can also be built as a module. If so, the module
278 will be called rtc-max77686.
280 config RTC_DRV_RS5C372
281 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
283 If you say yes here you get support for the
284 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
286 This driver can also be built as a module. If so, the module
287 will be called rtc-rs5c372.
289 config RTC_DRV_ISL1208
290 tristate "Intersil ISL1208"
292 If you say yes here you get support for the
293 Intersil ISL1208 RTC chip.
295 This driver can also be built as a module. If so, the module
296 will be called rtc-isl1208.
298 config RTC_DRV_ISL12022
299 tristate "Intersil ISL12022"
301 If you say yes here you get support for the
302 Intersil ISL12022 RTC chip.
304 This driver can also be built as a module. If so, the module
305 will be called rtc-isl12022.
308 tristate "Xicor/Intersil X1205"
310 If you say yes here you get support for the
311 Xicor/Intersil X1205 RTC chip.
313 This driver can also be built as a module. If so, the module
314 will be called rtc-x1205.
316 config RTC_DRV_PALMAS
317 tristate "TI Palmas RTC driver"
318 depends on MFD_PALMAS
320 If you say yes here you get support for the RTC of TI PALMA series PMIC
323 This driver can also be built as a module. If so, the module
324 will be called rtc-palma.
326 config RTC_DRV_PCF2127
327 tristate "NXP PCF2127"
329 If you say yes here you get support for the NXP PCF2127/29 RTC
332 This driver can also be built as a module. If so, the module
333 will be called rtc-pcf2127.
335 config RTC_DRV_PCF8523
336 tristate "NXP PCF8523"
338 If you say yes here you get support for the NXP PCF8523 RTC
341 This driver can also be built as a module. If so, the module
342 will be called rtc-pcf8523.
344 config RTC_DRV_PCF8563
345 tristate "Philips PCF8563/Epson RTC8564"
347 If you say yes here you get support for the
348 Philips PCF8563 RTC chip. The Epson RTC8564
351 This driver can also be built as a module. If so, the module
352 will be called rtc-pcf8563.
354 config RTC_DRV_PCF8583
355 tristate "Philips PCF8583"
357 If you say yes here you get support for the Philips PCF8583
358 RTC chip found on Acorn RiscPCs. This driver supports the
359 platform specific method of retrieving the current year from
360 the RTC's SRAM. It will work on other platforms with the same
361 chip, but the year will probably have to be tweaked.
363 This driver can also be built as a module. If so, the module
364 will be called rtc-pcf8583.
366 config RTC_DRV_M41T80
367 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
369 If you say Y here you will get support for the ST M41T60
370 and M41T80 RTC chips series. Currently, the following chips are
371 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
372 M41ST85, and M41ST87.
374 This driver can also be built as a module. If so, the module
375 will be called rtc-m41t80.
377 config RTC_DRV_M41T80_WDT
378 bool "ST M41T65/M41T80 series RTC watchdog timer"
379 depends on RTC_DRV_M41T80
381 If you say Y here you will get support for the
382 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
385 tristate "TI BQ32000"
387 If you say Y here you will get support for the TI
388 BQ32000 I2C RTC chip.
390 This driver can also be built as a module. If so, the module
391 will be called rtc-bq32k.
393 config RTC_DRV_DM355EVM
394 tristate "TI DaVinci DM355 EVM RTC"
395 depends on MFD_DM355EVM_MSP
397 Supports the RTC firmware in the MSP430 on the DM355 EVM.
399 config RTC_DRV_TWL92330
400 boolean "TI TWL92330/Menelaus"
403 If you say yes here you get support for the RTC on the
404 TWL92330 "Menelaus" power management chip, used with OMAP2
405 platforms. The support is integrated with the rest of
406 the Menelaus driver; it's not separate module.
408 config RTC_DRV_TWL4030
409 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
410 depends on TWL4030_CORE
412 If you say yes here you get support for the RTC on the
413 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
415 This driver can also be built as a module. If so, the module
416 will be called rtc-twl.
418 config RTC_DRV_TPS6586X
419 tristate "TI TPS6586X RTC driver"
420 depends on MFD_TPS6586X
422 TI Power Management IC TPS6586X supports RTC functionality
423 along with alarm. This driver supports the RTC driver for
424 the TPS6586X RTC module.
426 config RTC_DRV_TPS65910
427 tristate "TI TPS65910 RTC driver"
428 depends on RTC_CLASS && MFD_TPS65910
430 If you say yes here you get support for the RTC on the
433 This driver can also be built as a module. If so, the module
434 will be called rtc-tps65910.
436 config RTC_DRV_TPS80031
437 tristate "TI TPS80031/TPS80032 RTC driver"
438 depends on MFD_TPS80031
440 TI Power Management IC TPS80031 supports RTC functionality
441 along with alarm. This driver supports the RTC driver for
442 the TPS80031 RTC module.
444 config RTC_DRV_RC5T583
445 tristate "RICOH 5T583 RTC driver"
446 depends on MFD_RC5T583
448 If you say yes here you get support for the RTC on the
451 This driver can also be built as a module. If so, the module
452 will be called rtc-rc5t583.
454 config RTC_DRV_S35390A
455 tristate "Seiko Instruments S-35390A"
458 If you say yes here you will get support for the Seiko
459 Instruments S-35390A.
461 This driver can also be built as a module. If so the module
462 will be called rtc-s35390a.
464 config RTC_DRV_FM3130
465 tristate "Ramtron FM3130"
467 If you say Y here you will get support for the
468 Ramtron FM3130 RTC chips.
469 Ramtron FM3130 is a chip with two separate devices inside,
470 RTC clock and FRAM. This driver provides only RTC functionality.
472 This driver can also be built as a module. If so the module
473 will be called rtc-fm3130.
475 config RTC_DRV_RX8581
476 tristate "Epson RX-8581"
478 If you say yes here you will get support for the Epson RX-8581.
480 This driver can also be built as a module. If so the module
481 will be called rtc-rx8581.
483 config RTC_DRV_RX8025
484 tristate "Epson RX-8025SA/NB"
486 If you say yes here you get support for the Epson
487 RX-8025SA/NB RTC chips.
489 This driver can also be built as a module. If so, the module
490 will be called rtc-rx8025.
492 config RTC_DRV_EM3027
493 tristate "EM Microelectronic EM3027"
495 If you say yes here you get support for the EM
496 Microelectronic EM3027 RTC chips.
498 This driver can also be built as a module. If so, the module
499 will be called rtc-em3027.
501 config RTC_DRV_RV3029C2
502 tristate "Micro Crystal RTC"
504 If you say yes here you get support for the Micro Crystal
507 This driver can also be built as a module. If so, the module
508 will be called rtc-rv3029c2.
511 tristate "Samsung S5M series"
512 depends on MFD_SEC_CORE
514 If you say yes here you will get support for the
515 RTC of Samsung S5M PMIC series.
517 This driver can also be built as a module. If so, the module
518 will be called rtc-s5m.
522 comment "SPI RTC drivers"
526 config RTC_DRV_M41T93
529 If you say yes here you will get support for the
530 ST M41T93 SPI RTC chip.
532 This driver can also be built as a module. If so, the module
533 will be called rtc-m41t93.
535 config RTC_DRV_M41T94
538 If you say yes here you will get support for the
539 ST M41T94 SPI RTC chip.
541 This driver can also be built as a module. If so, the module
542 will be called rtc-m41t94.
544 config RTC_DRV_DS1305
545 tristate "Dallas/Maxim DS1305/DS1306"
547 Select this driver to get support for the Dallas/Maxim DS1305
548 and DS1306 real time clock chips. These support a trickle
549 charger, alarms, and NVRAM in addition to the clock.
551 This driver can also be built as a module. If so, the module
552 will be called rtc-ds1305.
554 config RTC_DRV_DS1390
555 tristate "Dallas/Maxim DS1390/93/94"
557 If you say yes here you get support for the
558 Dallas/Maxim DS1390/93/94 chips.
560 This driver only supports the RTC feature, and not other chip
561 features such as alarms and trickle charging.
563 This driver can also be built as a module. If so, the module
564 will be called rtc-ds1390.
566 config RTC_DRV_MAX6902
567 tristate "Maxim MAX6902"
569 If you say yes here you will get support for the
570 Maxim MAX6902 SPI RTC chip.
572 This driver can also be built as a module. If so, the module
573 will be called rtc-max6902.
576 tristate "Epson RTC-9701JE"
578 If you say yes here you will get support for the
579 Epson RTC-9701JE SPI RTC chip.
581 This driver can also be built as a module. If so, the module
582 will be called rtc-r9701.
584 config RTC_DRV_RS5C348
585 tristate "Ricoh RS5C348A/B"
587 If you say yes here you get support for the
588 Ricoh RS5C348A and RS5C348B RTC chips.
590 This driver can also be built as a module. If so, the module
591 will be called rtc-rs5c348.
593 config RTC_DRV_DS3234
594 tristate "Maxim/Dallas DS3234"
596 If you say yes here you get support for the
597 Maxim/Dallas DS3234 SPI RTC chip.
599 This driver can also be built as a module. If so, the module
600 will be called rtc-ds3234.
602 config RTC_DRV_PCF2123
603 tristate "NXP PCF2123"
605 If you say yes here you get support for the NXP PCF2123
608 This driver can also be built as a module. If so, the module
609 will be called rtc-pcf2123.
611 config RTC_DRV_RX4581
612 tristate "Epson RX-4581"
614 If you say yes here you will get support for the Epson RX-4581.
616 This driver can also be built as a module. If so the module
617 will be called rtc-rx4581.
621 comment "Platform RTC drivers"
623 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
624 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
625 # global rtc_lock ... it's not yet just another platform_device.
628 tristate "PC-style 'CMOS'"
629 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
632 Say "yes" here to get direct support for the real time clock
633 found in every PC or ACPI-based system, and some other boards.
634 Specifically the original MC146818, compatibles like those in
635 PC south bridges, the DS12887 or M48T86, some multifunction
636 or LPC bus chips, and so on.
638 Your system will need to define the platform device used by
639 this driver, otherwise it won't be accessible. This means
640 you can safely enable this driver if you don't know whether
641 or not your board has this kind of hardware.
643 This driver can also be built as a module. If so, the module
644 will be called rtc-cmos.
647 tristate "Virtual RTC for Intel MID platforms"
648 depends on X86_INTEL_MID
649 default y if X86_INTEL_MID
652 Say "yes" here to get direct support for the real time clock
653 found on Moorestown platforms. The VRTC is a emulated RTC that
654 derives its clock source from a real RTC in the PMIC. The MC146818
655 style programming interface is mostly conserved, but any
656 updates are done via IPC calls to the system controller FW.
658 config RTC_DRV_DS1216
659 tristate "Dallas DS1216"
662 If you say yes here you get support for the Dallas DS1216 RTC chips.
664 config RTC_DRV_DS1286
665 tristate "Dallas DS1286"
667 If you say yes here you get support for the Dallas DS1286 RTC chips.
669 config RTC_DRV_DS1302
670 tristate "Dallas DS1302"
671 depends on SH_SECUREEDGE5410
673 If you say yes here you get support for the Dallas DS1302 RTC chips.
675 config RTC_DRV_DS1511
676 tristate "Dallas DS1511"
678 If you say yes here you get support for the
679 Dallas DS1511 timekeeping/watchdog chip.
681 This driver can also be built as a module. If so, the module
682 will be called rtc-ds1511.
684 config RTC_DRV_DS1553
685 tristate "Maxim/Dallas DS1553"
687 If you say yes here you get support for the
688 Maxim/Dallas DS1553 timekeeping chip.
690 This driver can also be built as a module. If so, the module
691 will be called rtc-ds1553.
693 config RTC_DRV_DS1742
694 tristate "Maxim/Dallas DS1742/1743"
696 If you say yes here you get support for the
697 Maxim/Dallas DS1742/1743 timekeeping chip.
699 This driver can also be built as a module. If so, the module
700 will be called rtc-ds1742.
702 config RTC_DRV_DA9052
703 tristate "Dialog DA9052/DA9053 RTC"
704 depends on PMIC_DA9052
706 Say y here to support the RTC driver for Dialog Semiconductor
707 DA9052-BC and DA9053-AA/Bx PMICs.
709 config RTC_DRV_DA9055
710 tristate "Dialog Semiconductor DA9055 RTC"
711 depends on MFD_DA9055
713 If you say yes here you will get support for the
714 RTC of the Dialog DA9055 PMIC.
716 This driver can also be built as a module. If so, the module
717 will be called rtc-da9055
723 If you say yes here you will get support for the EFI
726 This driver can also be built as a module. If so, the module
727 will be called rtc-efi.
729 config RTC_DRV_STK17TA8
730 tristate "Simtek STK17TA8"
732 If you say yes here you get support for the
733 Simtek STK17TA8 timekeeping chip.
735 This driver can also be built as a module. If so, the module
736 will be called rtc-stk17ta8.
738 config RTC_DRV_M48T86
739 tristate "ST M48T86/Dallas DS12887"
741 If you say Y here you will get support for the
742 ST M48T86 and Dallas DS12887 RTC chips.
744 This driver can also be built as a module. If so, the module
745 will be called rtc-m48t86.
747 config RTC_DRV_M48T35
750 If you say Y here you will get support for the
753 This driver can also be built as a module, if so, the module
754 will be called "rtc-m48t35".
756 config RTC_DRV_M48T59
757 tristate "ST M48T59/M48T08/M48T02"
759 If you say Y here you will get support for the
760 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
762 These chips are usually found in Sun SPARC and UltraSPARC
765 This driver can also be built as a module, if so, the module
766 will be called "rtc-m48t59".
768 config RTC_DRV_MSM6242
769 tristate "Oki MSM6242"
771 If you say yes here you get support for the Oki MSM6242
772 timekeeping chip. It is used in some Amiga models (e.g. A2000).
774 This driver can also be built as a module. If so, the module
775 will be called rtc-msm6242.
777 config RTC_DRV_BQ4802
780 If you say Y here you will get support for the TI
783 This driver can also be built as a module. If so, the module
784 will be called rtc-bq4802.
786 config RTC_DRV_RP5C01
787 tristate "Ricoh RP5C01"
789 If you say yes here you get support for the Ricoh RP5C01
790 timekeeping chip. It is used in some Amiga models (e.g. A3000
793 This driver can also be built as a module. If so, the module
794 will be called rtc-rp5c01.
797 tristate "EM Microelectronic V3020"
799 If you say yes here you will get support for the
800 EM Microelectronic v3020 RTC chip.
802 This driver can also be built as a module. If so, the module
803 will be called rtc-v3020.
805 config RTC_DRV_DS2404
806 tristate "Dallas DS2404"
808 If you say yes here you get support for the
809 Dallas DS2404 RTC chip.
811 This driver can also be built as a module. If so, the module
812 will be called rtc-ds2404.
814 config RTC_DRV_WM831X
815 tristate "Wolfson Microelectronics WM831x RTC"
816 depends on MFD_WM831X
818 If you say yes here you will get support for the RTC subsystem
819 of the Wolfson Microelectronics WM831X series PMICs.
821 This driver can also be built as a module. If so, the module
822 will be called "rtc-wm831x".
824 config RTC_DRV_WM8350
825 tristate "Wolfson Microelectronics WM8350 RTC"
826 depends on MFD_WM8350
828 If you say yes here you will get support for the RTC subsystem
829 of the Wolfson Microelectronics WM8350.
831 This driver can also be built as a module. If so, the module
832 will be called "rtc-wm8350".
835 tristate "SPEAR ST RTC"
836 depends on PLAT_SPEAR
839 If you say Y here you will get support for the RTC found on
842 config RTC_DRV_PCF50633
843 depends on MFD_PCF50633
844 tristate "NXP PCF50633 RTC"
846 If you say yes here you get support for the RTC subsystem of the
847 NXP PCF50633 used in embedded systems.
849 config RTC_DRV_AB3100
850 tristate "ST-Ericsson AB3100 RTC"
851 depends on AB3100_CORE
852 default y if AB3100_CORE
854 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
855 support. This chip contains a battery- and capacitor-backed RTC.
857 config RTC_DRV_AB8500
858 tristate "ST-Ericsson AB8500 RTC"
859 depends on AB8500_CORE
861 select RTC_INTF_DEV_UIE_EMUL
863 Select this to enable the ST-Ericsson AB8500 power management IC RTC
864 support. This chip contains a battery- and capacitor-backed RTC.
866 config RTC_DRV_NUC900
867 tristate "NUC910/NUC920 RTC driver"
868 depends on ARCH_W90X900
870 If you say yes here you get support for the RTC subsystem of the
871 NUC910/NUC920 used in embedded systems.
873 comment "on-CPU RTC drivers"
875 config RTC_DRV_DAVINCI
876 tristate "TI DaVinci RTC"
877 depends on ARCH_DAVINCI_DM365
879 If you say yes here you get support for the RTC on the
880 DaVinci platforms (DM365).
882 This driver can also be built as a module. If so, the module
883 will be called rtc-davinci.
886 tristate "Freescale IMX DryIce Real Time Clock"
889 Support for Freescale IMX DryIce RTC
891 This driver can also be built as a module, if so, the module
892 will be called "rtc-imxdi".
896 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
898 Say "yes" here to support the on chip real time clock
899 present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
901 This driver can also be built as a module, if so, module
902 will be called rtc-omap.
907 This will include RTC support for Samsung SoCs. If
908 you want to include RTC support for any machine, kindly
909 select this in the respective mach-XXXX/Kconfig file.
912 tristate "Samsung S3C series SoC RTC"
913 depends on ARCH_S3C64XX || HAVE_S3C_RTC
915 RTC (Realtime Clock) driver for the clock inbuilt into the
916 Samsung S3C24XX series of SoCs. This can provide periodic
917 interrupt rates from 1Hz to 64Hz for user programs, and
920 The driver currently supports the common features on all the
921 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
924 This driver can also be build as a module. If so, the module
925 will be called rtc-s3c.
927 config RTC_DRV_EP93XX
928 tristate "Cirrus Logic EP93XX"
929 depends on ARCH_EP93XX
931 If you say yes here you get support for the
932 RTC embedded in the Cirrus Logic EP93XX processors.
934 This driver can also be built as a module. If so, the module
935 will be called rtc-ep93xx.
937 config RTC_DRV_SA1100
938 tristate "SA11x0/PXA2xx/PXA910"
939 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
941 If you say Y here you will get access to the real time clock
942 built into your SA11x0 or PXA2xx CPU.
944 To compile this driver as a module, choose M here: the
945 module will be called rtc-sa1100.
948 tristate "SuperH On-Chip RTC"
949 depends on SUPERH && HAVE_CLK
951 Say Y here to enable support for the on-chip RTC found in
952 most SuperH processors.
954 To compile this driver as a module, choose M here: the
955 module will be called rtc-sh.
957 config RTC_DRV_VR41XX
958 tristate "NEC VR41XX"
959 depends on CPU_VR41XX
961 If you say Y here you will get access to the real time clock
962 built into your NEC VR41XX CPU.
964 To compile this driver as a module, choose M here: the
965 module will be called rtc-vr41xx.
968 tristate "ARM AMBA PL030 RTC"
971 If you say Y here you will get access to ARM AMBA
972 PrimeCell PL030 RTC found on certain ARM SOCs.
974 To compile this driver as a module, choose M here: the
975 module will be called rtc-pl030.
978 tristate "ARM AMBA PL031 RTC"
981 If you say Y here you will get access to ARM AMBA
982 PrimeCell PL031 RTC found on certain ARM SOCs.
984 To compile this driver as a module, choose M here: the
985 module will be called rtc-pl031.
987 config RTC_DRV_AT32AP700X
988 tristate "AT32AP700X series RTC"
989 depends on PLATFORM_AT32AP
991 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
992 AT32AP700x family processors.
994 config RTC_DRV_AT91RM9200
995 tristate "AT91RM9200 or some AT91SAM9 RTC"
998 Driver for the internal RTC (Realtime Clock) module found on
999 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1000 this is powered by the backup power supply.
1002 config RTC_DRV_AT91SAM9
1003 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
1004 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
1006 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
1007 (Real Time Timer). These timers are powered by the backup power
1008 supply (such as a small coin cell battery), but do not need to
1011 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
1012 dedicated RTC module and leave the RTT available for other uses.)
1014 config RTC_DRV_AT91SAM9_RTT
1018 prompt "RTT module Number" if ARCH_AT91SAM9263
1019 depends on RTC_DRV_AT91SAM9
1021 More than one RTT module is available. You can choose which
1022 one will be used as an RTC. The default of zero is normally
1023 OK to use, though some systems use that for non-RTC purposes.
1025 config RTC_DRV_AT91SAM9_GPBR
1027 range 0 3 if !ARCH_AT91SAM9263
1028 range 0 15 if ARCH_AT91SAM9263
1030 prompt "Backup Register Number"
1031 depends on RTC_DRV_AT91SAM9
1033 The RTC driver needs to use one of the General Purpose Backup
1034 Registers (GPBRs) as well as the RTT. You can choose which one
1035 will be used. The default of zero is normally OK to use, but
1036 on some systems other software needs to use that register.
1038 config RTC_DRV_AU1XXX
1039 tristate "Au1xxx Counter0 RTC support"
1040 depends on MIPS_ALCHEMY
1042 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1043 counter) to be used as a RTC.
1045 This driver can also be built as a module. If so, the module
1046 will be called rtc-au1xxx.
1049 tristate "Blackfin On-Chip RTC"
1050 depends on BLACKFIN && !BF561
1052 If you say yes here you will get support for the
1053 Blackfin On-Chip Real Time Clock.
1055 This driver can also be built as a module. If so, the module
1056 will be called rtc-bfin.
1058 config RTC_DRV_RS5C313
1059 tristate "Ricoh RS5C313"
1060 depends on SH_LANDISK
1062 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1064 config RTC_DRV_GENERIC
1065 tristate "Generic RTC support"
1066 # Please consider writing a new RTC driver instead of using the generic
1068 depends on PARISC || M68K || PPC || SUPERH32
1070 Say Y or M here to enable RTC support on systems using the generic
1071 RTC abstraction. If you do not know what you are doing, you should
1075 tristate "PXA27x/PXA3xx"
1078 If you say Y here you will get access to the real time clock
1079 built into your PXA27x or PXA3xx CPU.
1081 This RTC driver uses PXA RTC registers available since pxa27x
1082 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1084 config RTC_DRV_VT8500
1085 tristate "VIA/WonderMedia 85xx SoC RTC"
1086 depends on ARCH_VT8500
1088 If you say Y here you will get access to the real time clock
1089 built into your VIA VT8500 SoC or its relatives.
1092 config RTC_DRV_SUN4V
1093 bool "SUN4V Hypervisor RTC"
1096 If you say Y here you will get support for the Hypervisor
1097 based RTC on SUN4V systems.
1099 config RTC_DRV_STARFIRE
1103 If you say Y here you will get support for the RTC found on
1106 config RTC_DRV_TX4939
1107 tristate "TX4939 SoC"
1108 depends on SOC_TX4939
1110 Driver for the internal RTC (Realtime Clock) module found on
1114 tristate "Marvell SoC RTC"
1115 depends on ARCH_KIRKWOOD || ARCH_DOVE || ARCH_MVEBU
1117 If you say yes here you will get support for the in-chip RTC
1118 that can be found in some of Marvell's SoC devices, such as
1119 the Kirkwood 88F6281 and 88F6192.
1121 This driver can also be built as a module. If so, the module
1122 will be called rtc-mv.
1128 If you say yes here you will get support for the RTC on PS3.
1130 This driver can also be built as a module. If so, the module
1131 will be called rtc-ps3.
1133 config RTC_DRV_COH901331
1134 tristate "ST-Ericsson COH 901 331 RTC"
1135 depends on ARCH_U300
1137 If you say Y here you will get access to ST-Ericsson
1138 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1141 This driver can also be built as a module. If so, the module
1142 will be called "rtc-coh901331".
1146 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1149 If you say yes here you will get support for the onboard
1150 STMP3xxx/i.MX23/i.MX28 RTC.
1152 This driver can also be built as a module. If so, the module
1153 will be called rtc-stmp3xxx.
1159 If you say Y here you will get support for the RTC found on
1160 the PCAP2 ASIC used on some Motorola phones.
1162 config RTC_DRV_MC13XXX
1163 depends on MFD_MC13XXX
1164 tristate "Freescale MC13xxx RTC"
1166 This enables support for the RTCs found on Freescale's PMICs
1167 MC13783 and MC13892.
1169 config RTC_DRV_MPC5121
1170 tristate "Freescale MPC5121 built-in RTC"
1171 depends on PPC_MPC512x || PPC_MPC52xx
1173 If you say yes here you will get support for the
1174 built-in RTC on MPC5121 or on MPC5200.
1176 This driver can also be built as a module. If so, the module
1177 will be called rtc-mpc5121.
1179 config RTC_DRV_JZ4740
1180 tristate "Ingenic JZ4740 SoC"
1181 depends on MACH_JZ4740
1183 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1186 This driver can also be buillt as a module. If so, the module
1187 will be called rtc-jz4740.
1189 config RTC_DRV_LPC32XX
1190 depends on ARCH_LPC32XX
1191 tristate "NXP LPC32XX RTC"
1193 This enables support for the NXP RTC in the LPC32XX
1195 This driver can also be buillt as a module. If so, the module
1196 will be called rtc-lpc32xx.
1198 config RTC_DRV_PM8XXX
1199 tristate "Qualcomm PMIC8XXX RTC"
1200 depends on MFD_PM8XXX
1202 If you say yes here you get support for the
1203 Qualcomm PMIC8XXX RTC.
1205 To compile this driver as a module, choose M here: the
1206 module will be called rtc-pm8xxx.
1208 config RTC_DRV_TEGRA
1209 tristate "NVIDIA Tegra Internal RTC driver"
1210 depends on ARCH_TEGRA
1212 If you say yes here you get support for the
1213 Tegra 200 series internal RTC module.
1215 This drive can also be built as a module. If so, the module
1216 will be called rtc-tegra.
1219 tristate "Tilera hypervisor RTC support"
1222 Enable support for the Linux driver side of the Tilera
1223 hypervisor's real-time clock interface.
1226 tristate "PKUnity v3 RTC support"
1227 depends on ARCH_PUV3
1229 This enables support for the RTC in the PKUnity-v3 SoCs.
1231 This drive can also be built as a module. If so, the module
1232 will be called rtc-puv3.
1234 config RTC_DRV_LOONGSON1
1235 tristate "loongson1 RTC support"
1236 depends on MACH_LOONGSON1
1238 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1239 counter) to be used as a RTC.
1241 This driver can also be built as a module. If so, the module
1242 will be called rtc-ls1x.
1245 tristate "Freescale MXC Real Time Clock"
1248 If you say yes here you get support for the Freescale MXC
1251 This driver can also be built as a module, if so, the module
1252 will be called "rtc-mxc".
1255 tristate "Freescale SNVS RTC support"
1256 depends on HAS_IOMEM
1259 If you say yes here you get support for the Freescale SNVS
1260 Low Power (LP) RTC module.
1262 This driver can also be built as a module, if so, the module
1263 will be called "rtc-snvs".
1265 config RTC_DRV_SIRFSOC
1266 tristate "SiRFSOC RTC"
1267 depends on ARCH_SIRF
1269 Say "yes" here to support the real time clock on SiRF SOC chips.
1270 This driver can also be built as a module called rtc-sirfsoc.
1272 config RTC_DRV_MOXART
1273 tristate "MOXA ART RTC"
1275 If you say yes here you get support for the MOXA ART
1278 This driver can also be built as a module. If so, the module
1279 will be called rtc-moxart
1281 comment "HID Sensor RTC drivers"
1283 config RTC_DRV_HID_SENSOR_TIME
1284 tristate "HID Sensor Time"
1287 select HID_SENSOR_HUB
1288 select HID_SENSOR_IIO_COMMON
1290 Say yes here to build support for the HID Sensors of type Time.
1291 This drivers makes such sensors available as RTCs.
1293 If this driver is compiled as a module, it will be named
1294 rtc-hid-sensor-time.