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.
28 config RTC_HCTOSYS_DEVICE
29 string "RTC used to set the system time"
30 depends on RTC_HCTOSYS
33 The RTC device that will be used to (re)initialize the system
34 clock, usually rtc0. Initialization is done when the system
35 starts up, and when it resumes from a low power state. This
36 device should record time in UTC, since the kernel won't do
39 The driver for this RTC device must be loaded before late_initcall
40 functions run, so it must usually be statically linked.
42 This clock should be battery-backed, so that it reads the correct
43 time when the system boots from a power-off state. Otherwise, your
44 system will need an external clock source (like an NTP server).
46 If the clock you specify here is not battery backed, it may still
47 be useful to reinitialize system time when resuming from system
48 sleep states. Do not specify an RTC here unless it stays powered
49 during all this system's supported sleep states.
52 bool "Set the RTC time based on NTP synchronization"
55 If you say yes here, the system time (wall clock) will be stored
56 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
57 minutes if userspace reports synchronized NTP status.
59 config RTC_SYSTOHC_DEVICE
60 string "RTC used to synchronize NTP adjustment"
61 depends on RTC_SYSTOHC
62 default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS
65 The RTC device used for NTP synchronization. The main difference
66 between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this
67 one can sleep when setting time, because it runs in the workqueue
71 bool "RTC debug support"
73 Say yes here to enable debugging support in the RTC framework
74 and individual RTC drivers.
76 comment "RTC interfaces"
79 bool "/sys/class/rtc/rtcN (sysfs)"
83 Say yes here if you want to use your RTCs using sysfs interfaces,
84 /sys/class/rtc/rtc0 through /sys/.../rtcN.
89 bool "/proc/driver/rtc (procfs for rtcN)"
93 Say yes here if you want to use your system clock RTC through
94 the proc interface, /proc/driver/rtc.
95 Other RTCs will not be available through that API.
96 If there is no RTC for the system clock, then the first RTC(rtc0)
102 bool "/dev/rtcN (character devices)"
105 Say yes here if you want to use your RTCs using the /dev
106 interfaces, which "udev" sets up as /dev/rtc0 through
109 You may want to set up a symbolic link so one of these
110 can be accessed as /dev/rtc, which is a name
111 expected by "hwclock" and some other programs. Recent
112 versions of "udev" are known to set up the symlink for you.
116 config RTC_INTF_DEV_UIE_EMUL
117 bool "RTC UIE emulation on dev interface"
118 depends on RTC_INTF_DEV
120 Provides an emulation for RTC_UIE if the underlying rtc chip
121 driver does not expose RTC_UIE ioctls. Those requests generate
122 once-per-second update interrupts, used for synchronization.
124 The emulation code will read the time from the hardware
125 clock several times per second, please enable this option
126 only if you know that you really need it.
129 tristate "Test driver/device"
131 If you say yes here you get support for the
132 RTC test driver. It's a software RTC which can be
133 used to test the RTC subsystem APIs. It gets
134 the time from the system clock.
135 You want this driver only if you are doing development
136 on the RTC subsystem. Please read the source code
139 This driver can also be built as a module. If so, the module
140 will be called rtc-test.
142 comment "I2C RTC drivers"
146 config RTC_DRV_88PM860X
147 tristate "Marvell 88PM860x"
148 depends on MFD_88PM860X
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-88pm860x.
156 config RTC_DRV_88PM80X
157 tristate "Marvell 88PM80x"
158 depends on MFD_88PM800
160 If you say yes here you get support for RTC function in Marvell
163 This driver can also be built as a module. If so, the module
164 will be called rtc-88pm80x.
166 config RTC_DRV_ABB5ZES3
168 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
170 If you say yes here you get support for the Abracon
171 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
173 This driver can also be built as a module. If so, the module
174 will be called rtc-ab-b5ze-s3.
176 config RTC_DRV_ABX80X
177 tristate "Abracon ABx80x"
179 If you say yes here you get support for Abracon AB080X and AB180X
180 families of ultra-low-power battery- and capacitor-backed real-time
183 This driver can also be built as a module. If so, the module
184 will be called rtc-abx80x.
186 config RTC_DRV_AS3722
187 tristate "ams AS3722 RTC driver"
188 depends on MFD_AS3722
190 If you say yes here you get support for the RTC of ams AS3722 PMIC
193 This driver can also be built as a module. If so, the module
194 will be called rtc-as3722.
196 config RTC_DRV_DS1307
197 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
199 If you say yes here you get support for various compatible RTC
200 chips (often with battery backup) connected with I2C. This driver
201 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
202 EPSON RX-8025 and probably other chips. In some cases the RTC
203 must already have been initialized (by manufacturing or a
206 The first seven registers on these chips hold an RTC, and other
207 registers may add features such as NVRAM, a trickle charger for
208 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
209 sysfs, but other chip features may not be available.
211 This driver can also be built as a module. If so, the module
212 will be called rtc-ds1307.
214 config RTC_DRV_DS1307_HWMON
215 bool "HWMON support for rtc-ds1307"
216 depends on RTC_DRV_DS1307 && HWMON
217 depends on !(RTC_DRV_DS1307=y && HWMON=m)
220 Say Y here if you want to expose temperature sensor data on
221 rtc-ds1307 (only DS3231)
223 config RTC_DRV_DS1374
224 tristate "Dallas/Maxim DS1374"
226 If you say yes here you get support for Dallas Semiconductor
227 DS1374 real-time clock chips. If an interrupt is associated
228 with the device, the alarm functionality is supported.
230 This driver can also be built as a module. If so, the module
231 will be called rtc-ds1374.
233 config RTC_DRV_DS1374_WDT
234 bool "Dallas/Maxim DS1374 watchdog timer"
235 depends on RTC_DRV_DS1374
237 If you say Y here you will get support for the
238 watchdog timer in the Dallas Semiconductor DS1374
239 real-time clock chips.
241 config RTC_DRV_DS1672
242 tristate "Dallas/Maxim DS1672"
244 If you say yes here you get support for the
245 Dallas/Maxim DS1672 timekeeping chip.
247 This driver can also be built as a module. If so, the module
248 will be called rtc-ds1672.
250 config RTC_DRV_DS3232
251 tristate "Dallas/Maxim DS3232"
253 If you say yes here you get support for Dallas Semiconductor
254 DS3232 real-time clock chips. If an interrupt is associated
255 with the device, the alarm functionality is supported.
257 This driver can also be built as a module. If so, the module
258 will be called rtc-ds3232.
260 config RTC_DRV_HYM8563
261 tristate "Haoyu Microelectronics HYM8563"
264 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
265 from the usual rtc functions it provides a clock output of
268 This driver can also be built as a module. If so, the module
269 will be called rtc-hym8563.
271 config RTC_DRV_LP8788
272 tristate "TI LP8788 RTC driver"
273 depends on MFD_LP8788
275 Say Y to enable support for the LP8788 RTC/ALARM driver.
277 config RTC_DRV_MAX6900
278 tristate "Maxim MAX6900"
280 If you say yes here you will get support for the
281 Maxim MAX6900 I2C RTC chip.
283 This driver can also be built as a module. If so, the module
284 will be called rtc-max6900.
286 config RTC_DRV_MAX8907
287 tristate "Maxim MAX8907"
288 depends on MFD_MAX8907
290 If you say yes here you will get support for the
291 RTC of Maxim MAX8907 PMIC.
293 This driver can also be built as a module. If so, the module
294 will be called rtc-max8907.
296 config RTC_DRV_MAX8925
297 tristate "Maxim MAX8925"
298 depends on MFD_MAX8925
300 If you say yes here you will get support for the
301 RTC of Maxim MAX8925 PMIC.
303 This driver can also be built as a module. If so, the module
304 will be called rtc-max8925.
306 config RTC_DRV_MAX8998
307 tristate "Maxim MAX8998"
308 depends on MFD_MAX8998
310 If you say yes here you will get support for the
311 RTC of Maxim MAX8998 PMIC.
313 This driver can also be built as a module. If so, the module
314 will be called rtc-max8998.
316 config RTC_DRV_MAX8997
317 tristate "Maxim MAX8997"
318 depends on MFD_MAX8997
320 If you say yes here you will get support for the
321 RTC of Maxim MAX8997 PMIC.
323 This driver can also be built as a module. If so, the module
324 will be called rtc-max8997.
326 config RTC_DRV_MAX77686
327 tristate "Maxim MAX77686"
328 depends on MFD_MAX77686 || MFD_MAX77620
330 If you say yes here you will get support for the
331 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
333 This driver can also be built as a module. If so, the module
334 will be called rtc-max77686.
337 tristate "Rockchip RK808 RTC"
340 If you say yes here you will get support for the
343 This driver can also be built as a module. If so, the module
344 will be called rk808-rtc.
346 config RTC_DRV_RS5C372
347 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
349 If you say yes here you get support for the
350 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
352 This driver can also be built as a module. If so, the module
353 will be called rtc-rs5c372.
355 config RTC_DRV_ISL1208
356 tristate "Intersil ISL1208"
358 If you say yes here you get support for the
359 Intersil ISL1208 RTC chip.
361 This driver can also be built as a module. If so, the module
362 will be called rtc-isl1208.
364 config RTC_DRV_ISL12022
365 tristate "Intersil ISL12022"
367 If you say yes here you get support for the
368 Intersil ISL12022 RTC chip.
370 This driver can also be built as a module. If so, the module
371 will be called rtc-isl12022.
373 config RTC_DRV_ISL12057
375 tristate "Intersil ISL12057"
377 If you say yes here you get support for the Intersil ISL12057
380 This driver can also be built as a module. If so, the module
381 will be called rtc-isl12057.
384 tristate "Xicor/Intersil X1205"
386 If you say yes here you get support for the
387 Xicor/Intersil X1205 RTC chip.
389 This driver can also be built as a module. If so, the module
390 will be called rtc-x1205.
392 config RTC_DRV_PCF2127
393 tristate "NXP PCF2127"
395 If you say yes here you get support for the NXP PCF2127/29 RTC
398 This driver can also be built as a module. If so, the module
399 will be called rtc-pcf2127.
401 config RTC_DRV_PCF8523
402 tristate "NXP PCF8523"
404 If you say yes here you get support for the NXP PCF8523 RTC
407 This driver can also be built as a module. If so, the module
408 will be called rtc-pcf8523.
410 config RTC_DRV_PCF85063
411 tristate "NXP PCF85063"
413 If you say yes here you get support for the PCF85063 RTC chip
415 This driver can also be built as a module. If so, the module
416 will be called rtc-pcf85063.
418 config RTC_DRV_PCF8563
419 tristate "Philips PCF8563/Epson RTC8564"
421 If you say yes here you get support for the
422 Philips PCF8563 RTC chip. The Epson RTC8564
425 This driver can also be built as a module. If so, the module
426 will be called rtc-pcf8563.
428 config RTC_DRV_PCF8583
429 tristate "Philips PCF8583"
431 If you say yes here you get support for the Philips PCF8583
432 RTC chip found on Acorn RiscPCs. This driver supports the
433 platform specific method of retrieving the current year from
434 the RTC's SRAM. It will work on other platforms with the same
435 chip, but the year will probably have to be tweaked.
437 This driver can also be built as a module. If so, the module
438 will be called rtc-pcf8583.
440 config RTC_DRV_M41T80
441 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
443 If you say Y here you will get support for the ST M41T60
444 and M41T80 RTC chips series. Currently, the following chips are
445 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
446 M41ST85, M41ST87, and MicroCrystal RV4162.
448 This driver can also be built as a module. If so, the module
449 will be called rtc-m41t80.
451 config RTC_DRV_M41T80_WDT
452 bool "ST M41T65/M41T80 series RTC watchdog timer"
453 depends on RTC_DRV_M41T80
455 If you say Y here you will get support for the
456 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
459 tristate "TI BQ32000"
461 If you say Y here you will get support for the TI
462 BQ32000 I2C RTC chip.
464 This driver can also be built as a module. If so, the module
465 will be called rtc-bq32k.
467 config RTC_DRV_DM355EVM
468 tristate "TI DaVinci DM355 EVM RTC"
469 depends on MFD_DM355EVM_MSP
471 Supports the RTC firmware in the MSP430 on the DM355 EVM.
473 config RTC_DRV_TWL92330
474 bool "TI TWL92330/Menelaus"
477 If you say yes here you get support for the RTC on the
478 TWL92330 "Menelaus" power management chip, used with OMAP2
479 platforms. The support is integrated with the rest of
480 the Menelaus driver; it's not separate module.
482 config RTC_DRV_TWL4030
483 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
484 depends on TWL4030_CORE
486 If you say yes here you get support for the RTC on the
487 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
489 This driver can also be built as a module. If so, the module
490 will be called rtc-twl.
492 config RTC_DRV_PALMAS
493 tristate "TI Palmas RTC driver"
494 depends on MFD_PALMAS
496 If you say yes here you get support for the RTC of TI PALMA series PMIC
499 This driver can also be built as a module. If so, the module
500 will be called rtc-palma.
502 config RTC_DRV_TPS6586X
503 tristate "TI TPS6586X RTC driver"
504 depends on MFD_TPS6586X
506 TI Power Management IC TPS6586X supports RTC functionality
507 along with alarm. This driver supports the RTC driver for
508 the TPS6586X RTC module.
510 config RTC_DRV_TPS65910
511 tristate "TI TPS65910 RTC driver"
512 depends on RTC_CLASS && MFD_TPS65910
514 If you say yes here you get support for the RTC on the
517 This driver can also be built as a module. If so, the module
518 will be called rtc-tps65910.
520 config RTC_DRV_TPS80031
521 tristate "TI TPS80031/TPS80032 RTC driver"
522 depends on MFD_TPS80031
524 TI Power Management IC TPS80031 supports RTC functionality
525 along with alarm. This driver supports the RTC driver for
526 the TPS80031 RTC module.
528 config RTC_DRV_RC5T583
529 tristate "RICOH 5T583 RTC driver"
530 depends on MFD_RC5T583
532 If you say yes here you get support for the RTC on the
535 This driver can also be built as a module. If so, the module
536 will be called rtc-rc5t583.
538 config RTC_DRV_S35390A
539 tristate "Seiko Instruments S-35390A"
542 If you say yes here you will get support for the Seiko
543 Instruments S-35390A.
545 This driver can also be built as a module. If so the module
546 will be called rtc-s35390a.
548 config RTC_DRV_FM3130
549 tristate "Ramtron FM3130"
551 If you say Y here you will get support for the
552 Ramtron FM3130 RTC chips.
553 Ramtron FM3130 is a chip with two separate devices inside,
554 RTC clock and FRAM. This driver provides only RTC functionality.
556 This driver can also be built as a module. If so the module
557 will be called rtc-fm3130.
559 config RTC_DRV_RX8010
560 tristate "Epson RX8010SJ"
563 If you say yes here you get support for the Epson RX8010SJ RTC
566 This driver can also be built as a module. If so, the module
567 will be called rtc-rx8010.
569 config RTC_DRV_RX8581
570 tristate "Epson RX-8581"
572 If you say yes here you will get support for the Epson RX-8581.
574 This driver can also be built as a module. If so the module
575 will be called rtc-rx8581.
577 config RTC_DRV_RX8025
578 tristate "Epson RX-8025SA/NB"
580 If you say yes here you get support for the Epson
581 RX-8025SA/NB RTC chips.
583 This driver can also be built as a module. If so, the module
584 will be called rtc-rx8025.
586 config RTC_DRV_EM3027
587 tristate "EM Microelectronic EM3027"
589 If you say yes here you get support for the EM
590 Microelectronic EM3027 RTC chips.
592 This driver can also be built as a module. If so, the module
593 will be called rtc-em3027.
595 config RTC_DRV_RV3029C2
596 tristate "Micro Crystal RV3029"
598 If you say yes here you get support for the Micro Crystal
601 This driver can also be built as a module. If so, the module
602 will be called rtc-rv3029c2.
604 config RTC_DRV_RV8803
605 tristate "Micro Crystal RV8803"
607 If you say yes here you get support for the Micro Crystal
610 This driver can also be built as a module. If so, the module
611 will be called rtc-rv8803.
614 tristate "Samsung S2M/S5M series"
615 depends on MFD_SEC_CORE
617 If you say yes here you will get support for the
618 RTC of Samsung S2MPS14 and S5M PMIC series.
620 This driver can also be built as a module. If so, the module
621 will be called rtc-s5m.
625 comment "SPI RTC drivers"
629 config RTC_DRV_M41T93
632 If you say yes here you will get support for the
633 ST M41T93 SPI RTC chip.
635 This driver can also be built as a module. If so, the module
636 will be called rtc-m41t93.
638 config RTC_DRV_M41T94
641 If you say yes here you will get support for the
642 ST M41T94 SPI RTC chip.
644 This driver can also be built as a module. If so, the module
645 will be called rtc-m41t94.
647 config RTC_DRV_DS1305
648 tristate "Dallas/Maxim DS1305/DS1306"
650 Select this driver to get support for the Dallas/Maxim DS1305
651 and DS1306 real time clock chips. These support a trickle
652 charger, alarms, and NVRAM in addition to the clock.
654 This driver can also be built as a module. If so, the module
655 will be called rtc-ds1305.
657 config RTC_DRV_DS1343
659 tristate "Dallas/Maxim DS1343/DS1344"
661 If you say yes here you get support for the
662 Dallas/Maxim DS1343 and DS1344 real time clock chips.
663 Support for trickle charger, alarm is provided.
665 This driver can also be built as a module. If so, the module
666 will be called rtc-ds1343.
668 config RTC_DRV_DS1347
669 tristate "Dallas/Maxim DS1347"
671 If you say yes here you get support for the
672 Dallas/Maxim DS1347 chips.
674 This driver only supports the RTC feature, and not other chip
675 features such as alarms.
677 This driver can also be built as a module. If so, the module
678 will be called rtc-ds1347.
680 config RTC_DRV_DS1390
681 tristate "Dallas/Maxim DS1390/93/94"
683 If you say yes here you get support for the
684 Dallas/Maxim DS1390/93/94 chips.
686 This driver supports the RTC feature and trickle charging but not
687 other chip features such as alarms.
689 This driver can also be built as a module. If so, the module
690 will be called rtc-ds1390.
693 tristate "Epson RTC-9701JE"
695 If you say yes here you will get support for the
696 Epson RTC-9701JE SPI RTC chip.
698 This driver can also be built as a module. If so, the module
699 will be called rtc-r9701.
701 config RTC_DRV_RX4581
702 tristate "Epson RX-4581"
704 If you say yes here you will get support for the Epson RX-4581.
706 This driver can also be built as a module. If so the module
707 will be called rtc-rx4581.
709 config RTC_DRV_RX6110
710 tristate "Epson RX-6110"
713 If you say yes here you will get support for the Epson RX-6610.
715 This driver can also be built as a module. If so the module
716 will be called rtc-rx6110.
718 config RTC_DRV_RS5C348
719 tristate "Ricoh RS5C348A/B"
721 If you say yes here you get support for the
722 Ricoh RS5C348A and RS5C348B RTC chips.
724 This driver can also be built as a module. If so, the module
725 will be called rtc-rs5c348.
727 config RTC_DRV_MAX6902
728 tristate "Maxim MAX6902"
730 If you say yes here you will get support for the
731 Maxim MAX6902 SPI RTC chip.
733 This driver can also be built as a module. If so, the module
734 will be called rtc-max6902.
736 config RTC_DRV_DS3234
737 tristate "Maxim/Dallas DS3234"
739 If you say yes here you get support for the
740 Maxim/Dallas DS3234 SPI RTC chip.
742 This driver can also be built as a module. If so, the module
743 will be called rtc-ds3234.
745 config RTC_DRV_PCF2123
746 tristate "NXP PCF2123"
748 If you say yes here you get support for the NXP PCF2123
751 This driver can also be built as a module. If so, the module
752 will be called rtc-pcf2123.
754 config RTC_DRV_MCP795
755 tristate "Microchip MCP795"
757 If you say yes here you will get support for the Microchip MCP795.
759 This driver can also be built as a module. If so the module
760 will be called rtc-mcp795.
764 comment "Platform RTC drivers"
766 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
767 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
768 # global rtc_lock ... it's not yet just another platform_device.
771 tristate "PC-style 'CMOS'"
772 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
775 Say "yes" here to get direct support for the real time clock
776 found in every PC or ACPI-based system, and some other boards.
777 Specifically the original MC146818, compatibles like those in
778 PC south bridges, the DS12887 or M48T86, some multifunction
779 or LPC bus chips, and so on.
781 Your system will need to define the platform device used by
782 this driver, otherwise it won't be accessible. This means
783 you can safely enable this driver if you don't know whether
784 or not your board has this kind of hardware.
786 This driver can also be built as a module. If so, the module
787 will be called rtc-cmos.
790 bool "Alpha PC-style CMOS"
794 Direct support for the real-time clock found on every Alpha
795 system, specifically MC146818 compatibles. If in doubt, say Y.
798 tristate "Virtual RTC for Intel MID platforms"
799 depends on X86_INTEL_MID
800 default y if X86_INTEL_MID
803 Say "yes" here to get direct support for the real time clock
804 found on Moorestown platforms. The VRTC is a emulated RTC that
805 derives its clock source from a real RTC in the PMIC. The MC146818
806 style programming interface is mostly conserved, but any
807 updates are done via IPC calls to the system controller FW.
809 config RTC_DRV_DS1216
810 tristate "Dallas DS1216"
813 If you say yes here you get support for the Dallas DS1216 RTC chips.
815 config RTC_DRV_DS1286
816 tristate "Dallas DS1286"
819 If you say yes here you get support for the Dallas DS1286 RTC chips.
821 config RTC_DRV_DS1302
822 tristate "Dallas DS1302"
823 depends on SH_SECUREEDGE5410
825 If you say yes here you get support for the Dallas DS1302 RTC chips.
827 config RTC_DRV_DS1511
828 tristate "Dallas DS1511"
831 If you say yes here you get support for the
832 Dallas DS1511 timekeeping/watchdog chip.
834 This driver can also be built as a module. If so, the module
835 will be called rtc-ds1511.
837 config RTC_DRV_DS1553
838 tristate "Maxim/Dallas DS1553"
841 If you say yes here you get support for the
842 Maxim/Dallas DS1553 timekeeping chip.
844 This driver can also be built as a module. If so, the module
845 will be called rtc-ds1553.
847 config RTC_DRV_DS1685_FAMILY
848 tristate "Dallas/Maxim DS1685 Family"
850 If you say yes here you get support for the Dallas/Maxim DS1685
851 family of real time chips. This family includes the DS1685/DS1687,
852 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
853 DS17885/DS17887 chips.
855 This driver can also be built as a module. If so, the module
856 will be called rtc-ds1685.
860 depends on RTC_DRV_DS1685_FAMILY
861 default RTC_DRV_DS1685
863 config RTC_DRV_DS1685
866 This enables support for the Dallas/Maxim DS1685/DS1687 real time
869 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
870 systems, as well as EPPC-405-UC modules by electronic system design
873 config RTC_DRV_DS1689
876 This enables support for the Dallas/Maxim DS1689/DS1693 real time
879 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
880 which supports a few minor features such as Vcc, Vbat, and Power
881 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
883 It also works for the even older DS1688/DS1691 RTC chips, which are
884 virtually the same and carry the same model number. Both chips
885 have 114 bytes of user NVRAM.
887 config RTC_DRV_DS17285
888 bool "DS17285/DS17287"
890 This enables support for the Dallas/Maxim DS17285/DS17287 real time
893 This chip features 2kb of extended NV-SRAM. It may possibly be
894 found in some SGI O2 systems (rare).
896 config RTC_DRV_DS17485
897 bool "DS17485/DS17487"
899 This enables support for the Dallas/Maxim DS17485/DS17487 real time
902 This chip features 4kb of extended NV-SRAM.
904 config RTC_DRV_DS17885
905 bool "DS17885/DS17887"
907 This enables support for the Dallas/Maxim DS17885/DS17887 real time
910 This chip features 8kb of extended NV-SRAM.
914 config RTC_DS1685_PROC_REGS
915 bool "Display register values in /proc"
916 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
918 Enable this to display a readout of all of the RTC registers in
919 /proc/drivers/rtc. Keep in mind that this can potentially lead
920 to lost interrupts, as reading Control Register C will clear
921 all pending IRQ flags.
923 Unless you are debugging this driver, choose N.
925 config RTC_DS1685_SYSFS_REGS
926 bool "SysFS access to RTC register bits"
927 depends on RTC_DRV_DS1685_FAMILY && SYSFS
929 Enable this to provide access to the RTC control register bits
930 in /sys. Some of the bits are read-write, others are read-only.
932 Keep in mind that reading Control C's bits automatically clears
933 all pending IRQ flags - this can cause lost interrupts.
935 If you know that you need access to these bits, choose Y, Else N.
937 config RTC_DRV_DS1742
938 tristate "Maxim/Dallas DS1742/1743"
941 If you say yes here you get support for the
942 Maxim/Dallas DS1742/1743 timekeeping chip.
944 This driver can also be built as a module. If so, the module
945 will be called rtc-ds1742.
947 config RTC_DRV_DS2404
948 tristate "Maxim/Dallas DS2404"
950 If you say yes here you get support for the
951 Dallas DS2404 RTC chip.
953 This driver can also be built as a module. If so, the module
954 will be called rtc-ds2404.
956 config RTC_DRV_DA9052
957 tristate "Dialog DA9052/DA9053 RTC"
958 depends on PMIC_DA9052
960 Say y here to support the RTC driver for Dialog Semiconductor
961 DA9052-BC and DA9053-AA/Bx PMICs.
963 config RTC_DRV_DA9055
964 tristate "Dialog Semiconductor DA9055 RTC"
965 depends on MFD_DA9055
967 If you say yes here you will get support for the
968 RTC of the Dialog DA9055 PMIC.
970 This driver can also be built as a module. If so, the module
971 will be called rtc-da9055
973 config RTC_DRV_DA9063
974 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
975 depends on MFD_DA9063 || MFD_DA9062
977 If you say yes here you will get support for the RTC subsystem
978 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
980 This driver can also be built as a module. If so, the module
981 will be called "rtc-da9063".
985 depends on EFI && !X86
987 If you say yes here you will get support for the EFI
990 This driver can also be built as a module. If so, the module
991 will be called rtc-efi.
993 config RTC_DRV_STK17TA8
994 tristate "Simtek STK17TA8"
997 If you say yes here you get support for the
998 Simtek STK17TA8 timekeeping chip.
1000 This driver can also be built as a module. If so, the module
1001 will be called rtc-stk17ta8.
1003 config RTC_DRV_M48T86
1004 tristate "ST M48T86/Dallas DS12887"
1006 If you say Y here you will get support for the
1007 ST M48T86 and Dallas DS12887 RTC chips.
1009 This driver can also be built as a module. If so, the module
1010 will be called rtc-m48t86.
1012 config RTC_DRV_M48T35
1013 tristate "ST M48T35"
1014 depends on HAS_IOMEM
1016 If you say Y here you will get support for the
1019 This driver can also be built as a module, if so, the module
1020 will be called "rtc-m48t35".
1022 config RTC_DRV_M48T59
1023 tristate "ST M48T59/M48T08/M48T02"
1024 depends on HAS_IOMEM
1026 If you say Y here you will get support for the
1027 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1029 These chips are usually found in Sun SPARC and UltraSPARC
1032 This driver can also be built as a module, if so, the module
1033 will be called "rtc-m48t59".
1035 config RTC_DRV_MSM6242
1036 tristate "Oki MSM6242"
1037 depends on HAS_IOMEM
1039 If you say yes here you get support for the Oki MSM6242
1040 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1042 This driver can also be built as a module. If so, the module
1043 will be called rtc-msm6242.
1045 config RTC_DRV_BQ4802
1046 tristate "TI BQ4802"
1047 depends on HAS_IOMEM
1049 If you say Y here you will get support for the TI
1052 This driver can also be built as a module. If so, the module
1053 will be called rtc-bq4802.
1055 config RTC_DRV_RP5C01
1056 tristate "Ricoh RP5C01"
1057 depends on HAS_IOMEM
1059 If you say yes here you get support for the Ricoh RP5C01
1060 timekeeping chip. It is used in some Amiga models (e.g. A3000
1063 This driver can also be built as a module. If so, the module
1064 will be called rtc-rp5c01.
1066 config RTC_DRV_V3020
1067 tristate "EM Microelectronic V3020"
1069 If you say yes here you will get support for the
1070 EM Microelectronic v3020 RTC chip.
1072 This driver can also be built as a module. If so, the module
1073 will be called rtc-v3020.
1075 config RTC_DRV_WM831X
1076 tristate "Wolfson Microelectronics WM831x RTC"
1077 depends on MFD_WM831X
1079 If you say yes here you will get support for the RTC subsystem
1080 of the Wolfson Microelectronics WM831X series PMICs.
1082 This driver can also be built as a module. If so, the module
1083 will be called "rtc-wm831x".
1085 config RTC_DRV_WM8350
1086 tristate "Wolfson Microelectronics WM8350 RTC"
1087 depends on MFD_WM8350
1089 If you say yes here you will get support for the RTC subsystem
1090 of the Wolfson Microelectronics WM8350.
1092 This driver can also be built as a module. If so, the module
1093 will be called "rtc-wm8350".
1095 config RTC_DRV_SPEAR
1096 tristate "SPEAR ST RTC"
1097 depends on PLAT_SPEAR || COMPILE_TEST
1100 If you say Y here you will get support for the RTC found on
1103 config RTC_DRV_PCF50633
1104 depends on MFD_PCF50633
1105 tristate "NXP PCF50633 RTC"
1107 If you say yes here you get support for the RTC subsystem of the
1108 NXP PCF50633 used in embedded systems.
1110 config RTC_DRV_AB3100
1111 tristate "ST-Ericsson AB3100 RTC"
1112 depends on AB3100_CORE
1113 default y if AB3100_CORE
1115 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1116 support. This chip contains a battery- and capacitor-backed RTC.
1118 config RTC_DRV_AB8500
1119 tristate "ST-Ericsson AB8500 RTC"
1120 depends on AB8500_CORE
1122 select RTC_INTF_DEV_UIE_EMUL
1124 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1125 support. This chip contains a battery- and capacitor-backed RTC.
1127 config RTC_DRV_NUC900
1128 tristate "NUC910/NUC920 RTC driver"
1129 depends on ARCH_W90X900 || COMPILE_TEST
1131 If you say yes here you get support for the RTC subsystem of the
1132 NUC910/NUC920 used in embedded systems.
1135 tristate "IBM OPAL RTC driver"
1136 depends on PPC_POWERNV
1139 If you say yes here you get support for the PowerNV platform RTC
1140 driver based on OPAL interfaces.
1142 This driver can also be built as a module. If so, the module
1143 will be called rtc-opal.
1145 config RTC_DRV_ZYNQMP
1146 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1149 If you say yes here you get support for the RTC controller found on
1150 Xilinx Zynq Ultrascale+ MPSoC.
1152 comment "on-CPU RTC drivers"
1154 config RTC_DRV_ASM9260
1155 tristate "Alphascale asm9260 RTC"
1156 depends on MACH_ASM9260
1158 If you say yes here you get support for the RTC on the
1159 Alphascale asm9260 SoC.
1161 This driver can also be built as a module. If so, the module
1162 will be called rtc-asm9260.
1164 config RTC_DRV_DAVINCI
1165 tristate "TI DaVinci RTC"
1166 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1168 If you say yes here you get support for the RTC on the
1169 DaVinci platforms (DM365).
1171 This driver can also be built as a module. If so, the module
1172 will be called rtc-davinci.
1174 config RTC_DRV_DIGICOLOR
1175 tristate "Conexant Digicolor RTC"
1176 depends on ARCH_DIGICOLOR || COMPILE_TEST
1178 If you say yes here you get support for the RTC on Conexant
1179 Digicolor platforms. This currently includes the CX92755 SoC.
1181 This driver can also be built as a module. If so, the module
1182 will be called rtc-digicolor.
1184 config RTC_DRV_IMXDI
1185 tristate "Freescale IMX DryIce Real Time Clock"
1188 Support for Freescale IMX DryIce RTC
1190 This driver can also be built as a module, if so, the module
1191 will be called "rtc-imxdi".
1194 tristate "TI OMAP Real Time Clock"
1195 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1197 Say "yes" here to support the on chip real time clock
1198 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1200 This driver can also be built as a module, if so, module
1201 will be called rtc-omap.
1206 This will include RTC support for Samsung SoCs. If
1207 you want to include RTC support for any machine, kindly
1208 select this in the respective mach-XXXX/Kconfig file.
1211 tristate "Samsung S3C series SoC RTC"
1212 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1214 RTC (Realtime Clock) driver for the clock inbuilt into the
1215 Samsung S3C24XX series of SoCs. This can provide periodic
1216 interrupt rates from 1Hz to 64Hz for user programs, and
1219 The driver currently supports the common features on all the
1220 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1223 This driver can also be build as a module. If so, the module
1224 will be called rtc-s3c.
1226 config RTC_DRV_EP93XX
1227 tristate "Cirrus Logic EP93XX"
1228 depends on ARCH_EP93XX || COMPILE_TEST
1230 If you say yes here you get support for the
1231 RTC embedded in the Cirrus Logic EP93XX processors.
1233 This driver can also be built as a module. If so, the module
1234 will be called rtc-ep93xx.
1236 config RTC_DRV_SA1100
1237 tristate "SA11x0/PXA2xx/PXA910"
1238 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1240 If you say Y here you will get access to the real time clock
1241 built into your SA11x0 or PXA2xx CPU.
1243 To compile this driver as a module, choose M here: the
1244 module will be called rtc-sa1100.
1247 tristate "SuperH On-Chip RTC"
1248 depends on SUPERH && HAVE_CLK
1250 Say Y here to enable support for the on-chip RTC found in
1251 most SuperH processors.
1253 To compile this driver as a module, choose M here: the
1254 module will be called rtc-sh.
1256 config RTC_DRV_VR41XX
1257 tristate "NEC VR41XX"
1258 depends on CPU_VR41XX || COMPILE_TEST
1260 If you say Y here you will get access to the real time clock
1261 built into your NEC VR41XX CPU.
1263 To compile this driver as a module, choose M here: the
1264 module will be called rtc-vr41xx.
1266 config RTC_DRV_PL030
1267 tristate "ARM AMBA PL030 RTC"
1270 If you say Y here you will get access to ARM AMBA
1271 PrimeCell PL030 RTC found on certain ARM SOCs.
1273 To compile this driver as a module, choose M here: the
1274 module will be called rtc-pl030.
1276 config RTC_DRV_PL031
1277 tristate "ARM AMBA PL031 RTC"
1280 If you say Y here you will get access to ARM AMBA
1281 PrimeCell PL031 RTC found on certain ARM SOCs.
1283 To compile this driver as a module, choose M here: the
1284 module will be called rtc-pl031.
1286 config RTC_DRV_AT32AP700X
1287 tristate "AT32AP700X series RTC"
1288 depends on PLATFORM_AT32AP || COMPILE_TEST
1290 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1291 AT32AP700x family processors.
1293 config RTC_DRV_AT91RM9200
1294 tristate "AT91RM9200 or some AT91SAM9 RTC"
1295 depends on ARCH_AT91 || COMPILE_TEST
1297 Driver for the internal RTC (Realtime Clock) module found on
1298 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1299 this is powered by the backup power supply.
1301 config RTC_DRV_AT91SAM9
1302 tristate "AT91SAM9 RTT as RTC"
1303 depends on ARCH_AT91 || COMPILE_TEST
1306 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1307 can be used as an RTC thanks to the backup power supply (e.g. a
1308 small coin cell battery) which keeps this block and the GPBR
1309 (General Purpose Backup Registers) block powered when the device
1311 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1312 probably want to use the real RTC block instead of the "RTT as an
1315 config RTC_DRV_AU1XXX
1316 tristate "Au1xxx Counter0 RTC support"
1317 depends on MIPS_ALCHEMY
1319 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1320 counter) to be used as a RTC.
1322 This driver can also be built as a module. If so, the module
1323 will be called rtc-au1xxx.
1326 tristate "Blackfin On-Chip RTC"
1327 depends on BLACKFIN && !BF561
1329 If you say yes here you will get support for the
1330 Blackfin On-Chip Real Time Clock.
1332 This driver can also be built as a module. If so, the module
1333 will be called rtc-bfin.
1335 config RTC_DRV_RS5C313
1336 tristate "Ricoh RS5C313"
1337 depends on SH_LANDISK
1339 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1341 config RTC_DRV_GENERIC
1342 tristate "Generic RTC support"
1343 # Please consider writing a new RTC driver instead of using the generic
1345 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
1347 Say Y or M here to enable RTC support on systems using the generic
1348 RTC abstraction. If you do not know what you are doing, you should
1352 tristate "PXA27x/PXA3xx"
1354 select RTC_DRV_SA1100
1356 If you say Y here you will get access to the real time clock
1357 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1358 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1360 This RTC driver uses PXA RTC registers available since pxa27x
1361 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1363 config RTC_DRV_VT8500
1364 tristate "VIA/WonderMedia 85xx SoC RTC"
1365 depends on ARCH_VT8500 || COMPILE_TEST
1367 If you say Y here you will get access to the real time clock
1368 built into your VIA VT8500 SoC or its relatives.
1371 config RTC_DRV_SUN4V
1372 bool "SUN4V Hypervisor RTC"
1375 If you say Y here you will get support for the Hypervisor
1376 based RTC on SUN4V systems.
1378 config RTC_DRV_SUN6I
1379 tristate "Allwinner A31 RTC"
1380 default MACH_SUN6I || MACH_SUN8I || COMPILE_TEST
1381 depends on ARCH_SUNXI
1383 If you say Y here you will get support for the RTC found in
1384 some Allwinner SoCs like the A31 or the A64.
1386 config RTC_DRV_SUNXI
1387 tristate "Allwinner sun4i/sun7i RTC"
1388 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1390 If you say Y here you will get support for the RTC found on
1393 config RTC_DRV_STARFIRE
1397 If you say Y here you will get support for the RTC found on
1400 config RTC_DRV_TX4939
1401 tristate "TX4939 SoC"
1402 depends on SOC_TX4939
1404 Driver for the internal RTC (Realtime Clock) module found on
1408 tristate "Marvell SoC RTC"
1409 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1411 If you say yes here you will get support for the in-chip RTC
1412 that can be found in some of Marvell's SoC devices, such as
1413 the Kirkwood 88F6281 and 88F6192.
1415 This driver can also be built as a module. If so, the module
1416 will be called rtc-mv.
1418 config RTC_DRV_ARMADA38X
1419 tristate "Armada 38x Marvell SoC RTC"
1420 depends on ARCH_MVEBU || COMPILE_TEST
1422 If you say yes here you will get support for the in-chip RTC
1423 that can be found in the Armada 38x Marvell's SoC device
1425 This driver can also be built as a module. If so, the module
1426 will be called armada38x-rtc.
1428 config RTC_DRV_GEMINI
1429 tristate "Gemini SoC RTC"
1430 depends on ARCH_GEMINI || COMPILE_TEST
1431 depends on HAS_IOMEM
1433 If you say Y here you will get support for the
1434 RTC found on Gemini SoC's.
1436 This driver can also be built as a module. If so, the module
1437 will be called rtc-gemini.
1443 If you say yes here you will get support for the RTC on PS3.
1445 This driver can also be built as a module. If so, the module
1446 will be called rtc-ps3.
1448 config RTC_DRV_COH901331
1449 tristate "ST-Ericsson COH 901 331 RTC"
1450 depends on ARCH_U300 || COMPILE_TEST
1452 If you say Y here you will get access to ST-Ericsson
1453 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1456 This driver can also be built as a module. If so, the module
1457 will be called "rtc-coh901331".
1461 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1462 depends on ARCH_MXS || COMPILE_TEST
1465 If you say yes here you will get support for the onboard
1466 STMP3xxx/i.MX23/i.MX28 RTC.
1468 This driver can also be built as a module. If so, the module
1469 will be called rtc-stmp3xxx.
1475 If you say Y here you will get support for the RTC found on
1476 the PCAP2 ASIC used on some Motorola phones.
1478 config RTC_DRV_MC13XXX
1479 depends on MFD_MC13XXX
1480 tristate "Freescale MC13xxx RTC"
1482 This enables support for the RTCs found on Freescale's PMICs
1483 MC13783 and MC13892.
1485 config RTC_DRV_MPC5121
1486 tristate "Freescale MPC5121 built-in RTC"
1487 depends on PPC_MPC512x || PPC_MPC52xx
1489 If you say yes here you will get support for the
1490 built-in RTC on MPC5121 or on MPC5200.
1492 This driver can also be built as a module. If so, the module
1493 will be called rtc-mpc5121.
1495 config RTC_DRV_JZ4740
1496 tristate "Ingenic JZ4740 SoC"
1497 depends on MACH_JZ4740 || COMPILE_TEST
1499 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1502 This driver can also be buillt as a module. If so, the module
1503 will be called rtc-jz4740.
1505 config RTC_DRV_LPC24XX
1506 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1507 depends on ARCH_LPC18XX || COMPILE_TEST
1508 depends on OF && HAS_IOMEM
1510 This enables support for the NXP RTC found which can be found on
1511 NXP LPC178x/18xx/408x/43xx devices.
1513 If you have one of the devices above enable this driver to use
1514 the hardware RTC. This driver can also be buillt as a module. If
1515 so, the module will be called rtc-lpc24xx.
1517 config RTC_DRV_LPC32XX
1518 depends on ARCH_LPC32XX || COMPILE_TEST
1519 tristate "NXP LPC32XX RTC"
1521 This enables support for the NXP RTC in the LPC32XX
1523 This driver can also be buillt as a module. If so, the module
1524 will be called rtc-lpc32xx.
1526 config RTC_DRV_PM8XXX
1527 tristate "Qualcomm PMIC8XXX RTC"
1528 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1530 If you say yes here you get support for the
1531 Qualcomm PMIC8XXX RTC.
1533 To compile this driver as a module, choose M here: the
1534 module will be called rtc-pm8xxx.
1536 config RTC_DRV_TEGRA
1537 tristate "NVIDIA Tegra Internal RTC driver"
1538 depends on ARCH_TEGRA || COMPILE_TEST
1540 If you say yes here you get support for the
1541 Tegra 200 series internal RTC module.
1543 This drive can also be built as a module. If so, the module
1544 will be called rtc-tegra.
1547 tristate "Tilera hypervisor RTC support"
1550 Enable support for the Linux driver side of the Tilera
1551 hypervisor's real-time clock interface.
1554 tristate "PKUnity v3 RTC support"
1555 depends on ARCH_PUV3
1557 This enables support for the RTC in the PKUnity-v3 SoCs.
1559 This drive can also be built as a module. If so, the module
1560 will be called rtc-puv3.
1562 config RTC_DRV_LOONGSON1
1563 tristate "loongson1 RTC support"
1564 depends on MACH_LOONGSON32
1566 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1567 counter) to be used as a RTC.
1569 This driver can also be built as a module. If so, the module
1570 will be called rtc-ls1x.
1573 tristate "Freescale MXC Real Time Clock"
1576 If you say yes here you get support for the Freescale MXC
1579 This driver can also be built as a module, if so, the module
1580 will be called "rtc-mxc".
1583 tristate "Freescale SNVS RTC support"
1585 depends on HAS_IOMEM
1588 If you say yes here you get support for the Freescale SNVS
1589 Low Power (LP) RTC module.
1591 This driver can also be built as a module, if so, the module
1592 will be called "rtc-snvs".
1594 config RTC_DRV_SIRFSOC
1595 tristate "SiRFSOC RTC"
1596 depends on ARCH_SIRF
1598 Say "yes" here to support the real time clock on SiRF SOC chips.
1599 This driver can also be built as a module called rtc-sirfsoc.
1601 config RTC_DRV_ST_LPC
1602 tristate "STMicroelectronics LPC RTC"
1606 Say Y here to include STMicroelectronics Low Power Controller
1607 (LPC) based RTC support.
1609 To compile this driver as a module, choose M here: the
1610 module will be called rtc-st-lpc.
1612 config RTC_DRV_MOXART
1613 tristate "MOXA ART RTC"
1614 depends on ARCH_MOXART || COMPILE_TEST
1616 If you say yes here you get support for the MOXA ART
1619 This driver can also be built as a module. If so, the module
1620 will be called rtc-moxart
1622 config RTC_DRV_MT6397
1623 tristate "Mediatek Real Time Clock driver"
1624 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1626 This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
1627 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1628 Mediatek(R) RTC driver.
1630 If you want to use Mediatek(R) RTC interface, select Y or M here.
1632 config RTC_DRV_XGENE
1633 tristate "APM X-Gene RTC"
1634 depends on HAS_IOMEM
1635 depends on ARCH_XGENE || COMPILE_TEST
1637 If you say yes here you get support for the APM X-Gene SoC real time
1640 This driver can also be built as a module, if so, the module
1641 will be called "rtc-xgene".
1643 config RTC_DRV_PIC32
1644 tristate "Microchip PIC32 RTC"
1645 depends on MACH_PIC32
1648 If you say yes here you get support for the PIC32 RTC module.
1650 This driver can also be built as a module. If so, the module
1651 will be called rtc-pic32
1653 comment "HID Sensor RTC drivers"
1655 config RTC_DRV_HID_SENSOR_TIME
1656 tristate "HID Sensor Time"
1659 select HID_SENSOR_HUB
1660 select HID_SENSOR_IIO_COMMON
1662 Say yes here to build support for the HID Sensors of type Time.
1663 This drivers makes such sensors available as RTCs.
1665 If this driver is compiled as a module, it will be named
1666 rtc-hid-sensor-time.