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_DS1307
157 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
159 If you say yes here you get support for various compatible RTC
160 chips (often with battery backup) connected with I2C. This driver
161 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
162 EPSON RX-8025 and probably other chips. In some cases the RTC
163 must already have been initialized (by manufacturing or a
166 The first seven registers on these chips hold an RTC, and other
167 registers may add features such as NVRAM, a trickle charger for
168 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
169 sysfs, but other chip features may not be available.
171 This driver can also be built as a module. If so, the module
172 will be called rtc-ds1307.
174 config RTC_DRV_DS1374
175 tristate "Dallas/Maxim DS1374"
178 If you say yes here you get support for Dallas Semiconductor
179 DS1374 real-time clock chips. If an interrupt is associated
180 with the device, the alarm functionality is supported.
182 This driver can also be built as a module. If so, the module
183 will be called rtc-ds1374.
185 config RTC_DRV_DS1672
186 tristate "Dallas/Maxim DS1672"
188 If you say yes here you get support for the
189 Dallas/Maxim DS1672 timekeeping chip.
191 This driver can also be built as a module. If so, the module
192 will be called rtc-ds1672.
194 config RTC_DRV_DS3232
195 tristate "Dallas/Maxim DS3232"
198 If you say yes here you get support for Dallas Semiconductor
199 DS3232 real-time clock chips. If an interrupt is associated
200 with the device, the alarm functionality is supported.
202 This driver can also be built as a module. If so, the module
203 will be called rtc-ds3232.
205 config RTC_DRV_LP8788
206 tristate "TI LP8788 RTC driver"
207 depends on MFD_LP8788
209 Say Y to enable support for the LP8788 RTC/ALARM driver.
211 config RTC_DRV_MAX6900
212 tristate "Maxim MAX6900"
214 If you say yes here you will get support for the
215 Maxim MAX6900 I2C RTC chip.
217 This driver can also be built as a module. If so, the module
218 will be called rtc-max6900.
220 config RTC_DRV_MAX8907
221 tristate "Maxim MAX8907"
222 depends on MFD_MAX8907
224 If you say yes here you will get support for the
225 RTC of Maxim MAX8907 PMIC.
227 This driver can also be built as a module. If so, the module
228 will be called rtc-max8907.
230 config RTC_DRV_MAX8925
231 tristate "Maxim MAX8925"
232 depends on MFD_MAX8925
234 If you say yes here you will get support for the
235 RTC of Maxim MAX8925 PMIC.
237 This driver can also be built as a module. If so, the module
238 will be called rtc-max8925.
240 config RTC_DRV_MAX8998
241 tristate "Maxim MAX8998"
242 depends on MFD_MAX8998
244 If you say yes here you will get support for the
245 RTC of Maxim MAX8998 PMIC.
247 This driver can also be built as a module. If so, the module
248 will be called rtc-max8998.
250 config RTC_DRV_MAX8997
251 tristate "Maxim MAX8997"
252 depends on MFD_MAX8997
254 If you say yes here you will get support for the
255 RTC of Maxim MAX8997 PMIC.
257 This driver can also be built as a module. If so, the module
258 will be called rtc-max8997.
260 config RTC_DRV_MAX77686
261 tristate "Maxim MAX77686"
262 depends on MFD_MAX77686
264 If you say yes here you will get support for the
265 RTC of Maxim MAX77686 PMIC.
267 This driver can also be built as a module. If so, the module
268 will be called rtc-max77686.
270 config RTC_DRV_RS5C372
271 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
273 If you say yes here you get support for the
274 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
276 This driver can also be built as a module. If so, the module
277 will be called rtc-rs5c372.
279 config RTC_DRV_ISL1208
280 tristate "Intersil ISL1208"
282 If you say yes here you get support for the
283 Intersil ISL1208 RTC chip.
285 This driver can also be built as a module. If so, the module
286 will be called rtc-isl1208.
288 config RTC_DRV_ISL12022
289 tristate "Intersil ISL12022"
291 If you say yes here you get support for the
292 Intersil ISL12022 RTC chip.
294 This driver can also be built as a module. If so, the module
295 will be called rtc-isl12022.
298 tristate "Xicor/Intersil X1205"
300 If you say yes here you get support for the
301 Xicor/Intersil X1205 RTC chip.
303 This driver can also be built as a module. If so, the module
304 will be called rtc-x1205.
306 config RTC_DRV_PALMAS
307 tristate "TI Palmas RTC driver"
308 depends on MFD_PALMAS
310 If you say yes here you get support for the RTC of TI PALMA series PMIC
313 This driver can also be built as a module. If so, the module
314 will be called rtc-palma.
316 config RTC_DRV_PCF8523
317 tristate "NXP PCF8523"
319 If you say yes here you get support for the NXP PCF8523 RTC
322 This driver can also be built as a module. If so, the module
323 will be called rtc-pcf8523.
325 config RTC_DRV_PCF8563
326 tristate "Philips PCF8563/Epson RTC8564"
328 If you say yes here you get support for the
329 Philips PCF8563 RTC chip. The Epson RTC8564
332 This driver can also be built as a module. If so, the module
333 will be called rtc-pcf8563.
336 tristate "rtc of HYM8563"
338 If you say yes here you get support for the
339 HYM8563 RTC chip. The HYM8564 should work as well.
341 This driver can also be built as a module. If so, the module
342 will be called rtc-HYM8563.
344 config RTC_DRV_PCF8583
345 tristate "Philips PCF8583"
347 If you say yes here you get support for the Philips PCF8583
348 RTC chip found on Acorn RiscPCs. This driver supports the
349 platform specific method of retrieving the current year from
350 the RTC's SRAM. It will work on other platforms with the same
351 chip, but the year will probably have to be tweaked.
353 This driver can also be built as a module. If so, the module
354 will be called rtc-pcf8583.
356 config RTC_DRV_M41T80
357 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
359 If you say Y here you will get support for the ST M41T60
360 and M41T80 RTC chips series. Currently, the following chips are
361 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
362 M41ST85, and M41ST87.
364 This driver can also be built as a module. If so, the module
365 will be called rtc-m41t80.
367 config RTC_DRV_M41T80_WDT
368 bool "ST M41T65/M41T80 series RTC watchdog timer"
369 depends on RTC_DRV_M41T80
371 If you say Y here you will get support for the
372 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
375 tristate "TI BQ32000"
377 If you say Y here you will get support for the TI
378 BQ32000 I2C RTC chip.
380 This driver can also be built as a module. If so, the module
381 will be called rtc-bq32k.
383 config RTC_DRV_DM355EVM
384 tristate "TI DaVinci DM355 EVM RTC"
385 depends on MFD_DM355EVM_MSP
387 Supports the RTC firmware in the MSP430 on the DM355 EVM.
389 config RTC_DRV_TWL92330
390 boolean "TI TWL92330/Menelaus"
393 If you say yes here you get support for the RTC on the
394 TWL92330 "Menelaus" power management chip, used with OMAP2
395 platforms. The support is integrated with the rest of
396 the Menelaus driver; it's not separate module.
398 config RTC_DRV_TWL4030
399 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
400 depends on TWL4030_CORE
402 If you say yes here you get support for the RTC on the
403 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
405 This driver can also be built as a module. If so, the module
406 will be called rtc-twl.
408 config RTC_DRV_TPS6586X
409 tristate "TI TPS6586X RTC driver"
410 depends on MFD_TPS6586X
412 TI Power Management IC TPS6586X supports RTC functionality
413 along with alarm. This driver supports the RTC driver for
414 the TPS6586X RTC module.
416 config RTC_DRV_TPS65910
417 tristate "TI TPS65910 RTC driver"
418 depends on RTC_CLASS && MFD_TPS65910
420 If you say yes here you get support for the RTC on the
423 This driver can also be built as a module. If so, the module
424 will be called rtc-tps65910.
427 tristate "rk808 rtc for rk"
430 enable rk808 rtc for system
433 tristate "rk818 rtc for rk"
436 enable rk818 rtc for system
439 bool "RT5036 RTC driver support"
440 depends on MFD_RT5036
443 Say Y here if you want to support Richtek RT5036 RTC.
445 config RTC_DRV_TPS80031
446 tristate "TI TPS80031/TPS80032 RTC driver"
447 depends on MFD_TPS80031
449 TI Power Management IC TPS80031 supports RTC functionality
450 along with alarm. This driver supports the RTC driver for
451 the TPS80031 RTC module.
453 config RTC_DRV_RC5T583
454 tristate "RICOH 5T583 RTC driver"
455 depends on MFD_RC5T583
457 If you say yes here you get support for the RTC on the
460 This driver can also be built as a module. If so, the module
461 will be called rtc-rc5t583.
463 config RTC_DRV_S35390A
464 tristate "Seiko Instruments S-35390A"
467 If you say yes here you will get support for the Seiko
468 Instruments S-35390A.
470 This driver can also be built as a module. If so the module
471 will be called rtc-s35390a.
473 config RTC_DRV_FM3130
474 tristate "Ramtron FM3130"
476 If you say Y here you will get support for the
477 Ramtron FM3130 RTC chips.
478 Ramtron FM3130 is a chip with two separate devices inside,
479 RTC clock and FRAM. This driver provides only RTC functionality.
481 This driver can also be built as a module. If so the module
482 will be called rtc-fm3130.
484 config RTC_DRV_RX8581
485 tristate "Epson RX-8581"
487 If you say yes here you will get support for the Epson RX-8581.
489 This driver can also be built as a module. If so the module
490 will be called rtc-rx8581.
492 config RTC_DRV_RX8025
493 tristate "Epson RX-8025SA/NB"
495 If you say yes here you get support for the Epson
496 RX-8025SA/NB RTC chips.
498 This driver can also be built as a module. If so, the module
499 will be called rtc-rx8025.
501 config RTC_DRV_EM3027
502 tristate "EM Microelectronic EM3027"
504 If you say yes here you get support for the EM
505 Microelectronic EM3027 RTC chips.
507 This driver can also be built as a module. If so, the module
508 will be called rtc-em3027.
510 config RTC_DRV_RV3029C2
511 tristate "Micro Crystal RTC"
513 If you say yes here you get support for the Micro Crystal
516 This driver can also be built as a module. If so, the module
517 will be called rtc-rv3029c2.
521 comment "SPI RTC drivers"
525 config RTC_DRV_M41T93
528 If you say yes here you will get support for the
529 ST M41T93 SPI RTC chip.
531 This driver can also be built as a module. If so, the module
532 will be called rtc-m41t93.
534 config RTC_DRV_M41T94
537 If you say yes here you will get support for the
538 ST M41T94 SPI RTC chip.
540 This driver can also be built as a module. If so, the module
541 will be called rtc-m41t94.
543 config RTC_DRV_DS1305
544 tristate "Dallas/Maxim DS1305/DS1306"
546 Select this driver to get support for the Dallas/Maxim DS1305
547 and DS1306 real time clock chips. These support a trickle
548 charger, alarms, and NVRAM in addition to the clock.
550 This driver can also be built as a module. If so, the module
551 will be called rtc-ds1305.
553 config RTC_DRV_DS1390
554 tristate "Dallas/Maxim DS1390/93/94"
556 If you say yes here you get support for the
557 Dallas/Maxim DS1390/93/94 chips.
559 This driver only supports the RTC feature, and not other chip
560 features such as alarms and trickle charging.
562 This driver can also be built as a module. If so, the module
563 will be called rtc-ds1390.
565 config RTC_DRV_MAX6902
566 tristate "Maxim MAX6902"
568 If you say yes here you will get support for the
569 Maxim MAX6902 SPI RTC chip.
571 This driver can also be built as a module. If so, the module
572 will be called rtc-max6902.
575 tristate "Epson RTC-9701JE"
577 If you say yes here you will get support for the
578 Epson RTC-9701JE SPI RTC chip.
580 This driver can also be built as a module. If so, the module
581 will be called rtc-r9701.
583 config RTC_DRV_RS5C348
584 tristate "Ricoh RS5C348A/B"
586 If you say yes here you get support for the
587 Ricoh RS5C348A and RS5C348B RTC chips.
589 This driver can also be built as a module. If so, the module
590 will be called rtc-rs5c348.
592 config RTC_DRV_DS3234
593 tristate "Maxim/Dallas DS3234"
595 If you say yes here you get support for the
596 Maxim/Dallas DS3234 SPI RTC chip.
598 This driver can also be built as a module. If so, the module
599 will be called rtc-ds3234.
601 config RTC_DRV_PCF2123
602 tristate "NXP PCF2123"
604 If you say yes here you get support for the NXP PCF2123
607 This driver can also be built as a module. If so, the module
608 will be called rtc-pcf2123.
610 config RTC_DRV_RX4581
611 tristate "Epson RX-4581"
613 If you say yes here you will get support for the Epson RX-4581.
615 This driver can also be built as a module. If so the module
616 will be called rtc-rx4581.
620 comment "Platform RTC drivers"
622 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
623 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
624 # global rtc_lock ... it's not yet just another platform_device.
627 tristate "PC-style 'CMOS'"
628 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
631 Say "yes" here to get direct support for the real time clock
632 found in every PC or ACPI-based system, and some other boards.
633 Specifically the original MC146818, compatibles like those in
634 PC south bridges, the DS12887 or M48T86, some multifunction
635 or LPC bus chips, and so on.
637 Your system will need to define the platform device used by
638 this driver, otherwise it won't be accessible. This means
639 you can safely enable this driver if you don't know whether
640 or not your board has this kind of hardware.
642 This driver can also be built as a module. If so, the module
643 will be called rtc-cmos.
646 tristate "Virtual RTC for Intel MID platforms"
647 depends on X86_INTEL_MID
648 default y if X86_INTEL_MID
651 Say "yes" here to get direct support for the real time clock
652 found on Moorestown platforms. The VRTC is a emulated RTC that
653 derives its clock source from a real RTC in the PMIC. The MC146818
654 style programming interface is mostly conserved, but any
655 updates are done via IPC calls to the system controller FW.
657 config RTC_DRV_DS1216
658 tristate "Dallas DS1216"
661 If you say yes here you get support for the Dallas DS1216 RTC chips.
663 config RTC_DRV_DS1286
664 tristate "Dallas DS1286"
666 If you say yes here you get support for the Dallas DS1286 RTC chips.
668 config RTC_DRV_DS1302
669 tristate "Dallas DS1302"
670 depends on SH_SECUREEDGE5410
672 If you say yes here you get support for the Dallas DS1302 RTC chips.
674 config RTC_DRV_DS1511
675 tristate "Dallas DS1511"
677 If you say yes here you get support for the
678 Dallas DS1511 timekeeping/watchdog chip.
680 This driver can also be built as a module. If so, the module
681 will be called rtc-ds1511.
683 config RTC_DRV_DS1553
684 tristate "Maxim/Dallas DS1553"
686 If you say yes here you get support for the
687 Maxim/Dallas DS1553 timekeeping chip.
689 This driver can also be built as a module. If so, the module
690 will be called rtc-ds1553.
692 config RTC_DRV_DS1742
693 tristate "Maxim/Dallas DS1742/1743"
695 If you say yes here you get support for the
696 Maxim/Dallas DS1742/1743 timekeeping chip.
698 This driver can also be built as a module. If so, the module
699 will be called rtc-ds1742.
701 config RTC_DRV_DA9052
702 tristate "Dialog DA9052/DA9053 RTC"
703 depends on PMIC_DA9052
705 Say y here to support the RTC driver for Dialog Semiconductor
706 DA9052-BC and DA9053-AA/Bx PMICs.
708 config RTC_DRV_DA9055
709 tristate "Dialog Semiconductor DA9055 RTC"
710 depends on MFD_DA9055
712 If you say yes here you will get support for the
713 RTC of the Dialog DA9055 PMIC.
715 This driver can also be built as a module. If so, the module
716 will be called rtc-da9055
722 If you say yes here you will get support for the EFI
725 This driver can also be built as a module. If so, the module
726 will be called rtc-efi.
728 config RTC_DRV_STK17TA8
729 tristate "Simtek STK17TA8"
731 If you say yes here you get support for the
732 Simtek STK17TA8 timekeeping chip.
734 This driver can also be built as a module. If so, the module
735 will be called rtc-stk17ta8.
737 config RTC_DRV_M48T86
738 tristate "ST M48T86/Dallas DS12887"
740 If you say Y here you will get support for the
741 ST M48T86 and Dallas DS12887 RTC chips.
743 This driver can also be built as a module. If so, the module
744 will be called rtc-m48t86.
746 config RTC_DRV_M48T35
749 If you say Y here you will get support for the
752 This driver can also be built as a module, if so, the module
753 will be called "rtc-m48t35".
755 config RTC_DRV_M48T59
756 tristate "ST M48T59/M48T08/M48T02"
758 If you say Y here you will get support for the
759 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
761 These chips are usually found in Sun SPARC and UltraSPARC
764 This driver can also be built as a module, if so, the module
765 will be called "rtc-m48t59".
767 config RTC_DRV_MSM6242
768 tristate "Oki MSM6242"
770 If you say yes here you get support for the Oki MSM6242
771 timekeeping chip. It is used in some Amiga models (e.g. A2000).
773 This driver can also be built as a module. If so, the module
774 will be called rtc-msm6242.
776 config RTC_DRV_BQ4802
779 If you say Y here you will get support for the TI
782 This driver can also be built as a module. If so, the module
783 will be called rtc-bq4802.
785 config RTC_DRV_RP5C01
786 tristate "Ricoh RP5C01"
788 If you say yes here you get support for the Ricoh RP5C01
789 timekeeping chip. It is used in some Amiga models (e.g. A3000
792 This driver can also be built as a module. If so, the module
793 will be called rtc-rp5c01.
796 tristate "EM Microelectronic V3020"
798 If you say yes here you will get support for the
799 EM Microelectronic v3020 RTC chip.
801 This driver can also be built as a module. If so, the module
802 will be called rtc-v3020.
804 config RTC_DRV_DS2404
805 tristate "Dallas DS2404"
807 If you say yes here you get support for the
808 Dallas DS2404 RTC chip.
810 This driver can also be built as a module. If so, the module
811 will be called rtc-ds2404.
813 config RTC_DRV_WM831X
814 tristate "Wolfson Microelectronics WM831x RTC"
815 depends on MFD_WM831X
817 If you say yes here you will get support for the RTC subsystem
818 of the Wolfson Microelectronics WM831X series PMICs.
820 This driver can also be built as a module. If so, the module
821 will be called "rtc-wm831x".
823 config RTC_DRV_WM8350
824 tristate "Wolfson Microelectronics WM8350 RTC"
825 depends on MFD_WM8350
827 If you say yes here you will get support for the RTC subsystem
828 of the Wolfson Microelectronics WM8350.
830 This driver can also be built as a module. If so, the module
831 will be called "rtc-wm8350".
834 tristate "SPEAR ST RTC"
835 depends on PLAT_SPEAR
838 If you say Y here you will get support for the RTC found on
841 config RTC_DRV_PCF50633
842 depends on MFD_PCF50633
843 tristate "NXP PCF50633 RTC"
845 If you say yes here you get support for the RTC subsystem of the
846 NXP PCF50633 used in embedded systems.
848 config RTC_DRV_AB3100
849 tristate "ST-Ericsson AB3100 RTC"
850 depends on AB3100_CORE
851 default y if AB3100_CORE
853 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
854 support. This chip contains a battery- and capacitor-backed RTC.
856 config RTC_DRV_AB8500
857 tristate "ST-Ericsson AB8500 RTC"
858 depends on AB8500_CORE
860 select RTC_INTF_DEV_UIE_EMUL
862 Select this to enable the ST-Ericsson AB8500 power management IC RTC
863 support. This chip contains a battery- and capacitor-backed RTC.
865 config RTC_DRV_NUC900
866 tristate "NUC910/NUC920 RTC driver"
867 depends on ARCH_W90X900
869 If you say yes here you get support for the RTC subsystem of the
870 NUC910/NUC920 used in embedded systems.
872 comment "on-CPU RTC drivers"
874 config RTC_DRV_DAVINCI
875 tristate "TI DaVinci RTC"
876 depends on ARCH_DAVINCI_DM365
878 If you say yes here you get support for the RTC on the
879 DaVinci platforms (DM365).
881 This driver can also be built as a module. If so, the module
882 will be called rtc-davinci.
885 tristate "Freescale IMX DryIce Real Time Clock"
888 Support for Freescale IMX DryIce RTC
890 This driver can also be built as a module, if so, the module
891 will be called "rtc-imxdi".
895 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
897 Say "yes" here to support the on chip real time clock
898 present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
900 This driver can also be built as a module, if so, module
901 will be called rtc-omap.
906 This will include RTC support for Samsung SoCs. If
907 you want to include RTC support for any machine, kindly
908 select this in the respective mach-XXXX/Kconfig file.
911 tristate "Samsung S3C series SoC RTC"
912 depends on ARCH_S3C64XX || HAVE_S3C_RTC
914 RTC (Realtime Clock) driver for the clock inbuilt into the
915 Samsung S3C24XX series of SoCs. This can provide periodic
916 interrupt rates from 1Hz to 64Hz for user programs, and
919 The driver currently supports the common features on all the
920 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
923 This driver can also be build as a module. If so, the module
924 will be called rtc-s3c.
926 config RTC_DRV_EP93XX
927 tristate "Cirrus Logic EP93XX"
928 depends on ARCH_EP93XX
930 If you say yes here you get support for the
931 RTC embedded in the Cirrus Logic EP93XX processors.
933 This driver can also be built as a module. If so, the module
934 will be called rtc-ep93xx.
936 config RTC_DRV_SA1100
937 tristate "SA11x0/PXA2xx/PXA910"
938 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
940 If you say Y here you will get access to the real time clock
941 built into your SA11x0 or PXA2xx CPU.
943 To compile this driver as a module, choose M here: the
944 module will be called rtc-sa1100.
947 tristate "SuperH On-Chip RTC"
948 depends on SUPERH && HAVE_CLK
950 Say Y here to enable support for the on-chip RTC found in
951 most SuperH processors.
953 To compile this driver as a module, choose M here: the
954 module will be called rtc-sh.
956 config RTC_DRV_VR41XX
957 tristate "NEC VR41XX"
958 depends on CPU_VR41XX
960 If you say Y here you will get access to the real time clock
961 built into your NEC VR41XX CPU.
963 To compile this driver as a module, choose M here: the
964 module will be called rtc-vr41xx.
967 tristate "ARM AMBA PL030 RTC"
970 If you say Y here you will get access to ARM AMBA
971 PrimeCell PL030 RTC found on certain ARM SOCs.
973 To compile this driver as a module, choose M here: the
974 module will be called rtc-pl030.
977 tristate "ARM AMBA PL031 RTC"
980 If you say Y here you will get access to ARM AMBA
981 PrimeCell PL031 RTC found on certain ARM SOCs.
983 To compile this driver as a module, choose M here: the
984 module will be called rtc-pl031.
986 config RTC_DRV_AT32AP700X
987 tristate "AT32AP700X series RTC"
988 depends on PLATFORM_AT32AP
990 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
991 AT32AP700x family processors.
993 config RTC_DRV_AT91RM9200
994 tristate "AT91RM9200 or some AT91SAM9 RTC"
997 Driver for the internal RTC (Realtime Clock) module found on
998 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
999 this is powered by the backup power supply.
1001 config RTC_DRV_AT91SAM9
1002 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
1003 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
1005 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
1006 (Real Time Timer). These timers are powered by the backup power
1007 supply (such as a small coin cell battery), but do not need to
1010 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
1011 dedicated RTC module and leave the RTT available for other uses.)
1013 config RTC_DRV_AT91SAM9_RTT
1017 prompt "RTT module Number" if ARCH_AT91SAM9263
1018 depends on RTC_DRV_AT91SAM9
1020 More than one RTT module is available. You can choose which
1021 one will be used as an RTC. The default of zero is normally
1022 OK to use, though some systems use that for non-RTC purposes.
1024 config RTC_DRV_AT91SAM9_GPBR
1026 range 0 3 if !ARCH_AT91SAM9263
1027 range 0 15 if ARCH_AT91SAM9263
1029 prompt "Backup Register Number"
1030 depends on RTC_DRV_AT91SAM9
1032 The RTC driver needs to use one of the General Purpose Backup
1033 Registers (GPBRs) as well as the RTT. You can choose which one
1034 will be used. The default of zero is normally OK to use, but
1035 on some systems other software needs to use that register.
1037 config RTC_DRV_AU1XXX
1038 tristate "Au1xxx Counter0 RTC support"
1039 depends on MIPS_ALCHEMY
1041 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1042 counter) to be used as a RTC.
1044 This driver can also be built as a module. If so, the module
1045 will be called rtc-au1xxx.
1048 tristate "Blackfin On-Chip RTC"
1049 depends on BLACKFIN && !BF561
1051 If you say yes here you will get support for the
1052 Blackfin On-Chip Real Time Clock.
1054 This driver can also be built as a module. If so, the module
1055 will be called rtc-bfin.
1057 config RTC_DRV_RS5C313
1058 tristate "Ricoh RS5C313"
1059 depends on SH_LANDISK
1061 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1063 config RTC_DRV_GENERIC
1064 tristate "Generic RTC support"
1065 # Please consider writing a new RTC driver instead of using the generic
1067 depends on PARISC || M68K || PPC || SUPERH32
1069 Say Y or M here to enable RTC support on systems using the generic
1070 RTC abstraction. If you do not know what you are doing, you should
1074 tristate "PXA27x/PXA3xx"
1077 If you say Y here you will get access to the real time clock
1078 built into your PXA27x or PXA3xx CPU.
1080 This RTC driver uses PXA RTC registers available since pxa27x
1081 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1083 config RTC_DRV_VT8500
1084 tristate "VIA/WonderMedia 85xx SoC RTC"
1085 depends on ARCH_VT8500
1087 If you say Y here you will get access to the real time clock
1088 built into your VIA VT8500 SoC or its relatives.
1091 config RTC_DRV_SUN4V
1092 bool "SUN4V Hypervisor RTC"
1095 If you say Y here you will get support for the Hypervisor
1096 based RTC on SUN4V systems.
1098 config RTC_DRV_STARFIRE
1102 If you say Y here you will get support for the RTC found on
1105 config RTC_DRV_TX4939
1106 tristate "TX4939 SoC"
1107 depends on SOC_TX4939
1109 Driver for the internal RTC (Realtime Clock) module found on
1113 tristate "Marvell SoC RTC"
1114 depends on ARCH_KIRKWOOD || ARCH_DOVE || ARCH_MVEBU
1116 If you say yes here you will get support for the in-chip RTC
1117 that can be found in some of Marvell's SoC devices, such as
1118 the Kirkwood 88F6281 and 88F6192.
1120 This driver can also be built as a module. If so, the module
1121 will be called rtc-mv.
1127 If you say yes here you will get support for the RTC on PS3.
1129 This driver can also be built as a module. If so, the module
1130 will be called rtc-ps3.
1132 config RTC_DRV_COH901331
1133 tristate "ST-Ericsson COH 901 331 RTC"
1134 depends on ARCH_U300
1136 If you say Y here you will get access to ST-Ericsson
1137 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1140 This driver can also be built as a module. If so, the module
1141 will be called "rtc-coh901331".
1145 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1148 If you say yes here you will get support for the onboard
1149 STMP3xxx/i.MX23/i.MX28 RTC.
1151 This driver can also be built as a module. If so, the module
1152 will be called rtc-stmp3xxx.
1158 If you say Y here you will get support for the RTC found on
1159 the PCAP2 ASIC used on some Motorola phones.
1161 config RTC_DRV_MC13XXX
1162 depends on MFD_MC13XXX
1163 tristate "Freescale MC13xxx RTC"
1165 This enables support for the RTCs found on Freescale's PMICs
1166 MC13783 and MC13892.
1168 config RTC_DRV_MPC5121
1169 tristate "Freescale MPC5121 built-in RTC"
1170 depends on PPC_MPC512x || PPC_MPC52xx
1172 If you say yes here you will get support for the
1173 built-in RTC on MPC5121 or on MPC5200.
1175 This driver can also be built as a module. If so, the module
1176 will be called rtc-mpc5121.
1178 config RTC_DRV_JZ4740
1179 tristate "Ingenic JZ4740 SoC"
1180 depends on MACH_JZ4740
1182 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1185 This driver can also be buillt as a module. If so, the module
1186 will be called rtc-jz4740.
1188 config RTC_DRV_LPC32XX
1189 depends on ARCH_LPC32XX
1190 tristate "NXP LPC32XX RTC"
1192 This enables support for the NXP RTC in the LPC32XX
1194 This driver can also be buillt as a module. If so, the module
1195 will be called rtc-lpc32xx.
1197 config RTC_DRV_PM8XXX
1198 tristate "Qualcomm PMIC8XXX RTC"
1199 depends on MFD_PM8XXX
1201 If you say yes here you get support for the
1202 Qualcomm PMIC8XXX RTC.
1204 To compile this driver as a module, choose M here: the
1205 module will be called rtc-pm8xxx.
1207 config RTC_DRV_TEGRA
1208 tristate "NVIDIA Tegra Internal RTC driver"
1209 depends on ARCH_TEGRA
1211 If you say yes here you get support for the
1212 Tegra 200 series internal RTC module.
1214 This drive can also be built as a module. If so, the module
1215 will be called rtc-tegra.
1218 tristate "Tilera hypervisor RTC support"
1221 Enable support for the Linux driver side of the Tilera
1222 hypervisor's real-time clock interface.
1225 tristate "PKUnity v3 RTC support"
1226 depends on ARCH_PUV3
1228 This enables support for the RTC in the PKUnity-v3 SoCs.
1230 This drive can also be built as a module. If so, the module
1231 will be called rtc-puv3.
1233 config RTC_DRV_LOONGSON1
1234 tristate "loongson1 RTC support"
1235 depends on MACH_LOONGSON1
1237 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1238 counter) to be used as a RTC.
1240 This driver can also be built as a module. If so, the module
1241 will be called rtc-ls1x.
1244 tristate "Freescale MXC Real Time Clock"
1247 If you say yes here you get support for the Freescale MXC
1250 This driver can also be built as a module, if so, the module
1251 will be called "rtc-mxc".
1254 tristate "Freescale SNVS RTC support"
1255 depends on HAS_IOMEM
1258 If you say yes here you get support for the Freescale SNVS
1259 Low Power (LP) RTC module.
1261 This driver can also be built as a module, if so, the module
1262 will be called "rtc-snvs".
1264 comment "HID Sensor RTC drivers"
1266 config RTC_DRV_HID_SENSOR_TIME
1267 tristate "HID Sensor Time"
1270 select HID_SENSOR_HUB
1271 select HID_SENSOR_IIO_COMMON
1273 Say yes here to build support for the HID Sensors of type Time.
1274 This drivers makes such sensors available as RTCs.
1276 If this driver is compiled as a module, it will be named
1277 rtc-hid-sensor-time.
1279 config RTC_DRV_RC5T619
1280 tristate "RICOH RC5T619 PMU RTC driver"
1281 depends on MFD_RICOH619
1284 If you say yes here you get support for the RICOH RC5T619 RTC module.
1286 This driver can also be built as a module. If so, the module
1287 will be called rtc-rc5t619.