2 # RTC class/drivers configuration
8 config RTC_MC146818_LIB
13 bool "Real Time Clock"
15 depends on !S390 && !UML
18 Generic RTC class support. If you say yes here, you will
19 be allowed to plug one or more RTCs to your system. You will
20 probably want to enable one or more of the interfaces below.
25 bool "Set system time from RTC on startup and resume"
28 If you say yes here, the system time (wall clock) will be set using
29 the value read from a specified RTC device. This is useful to avoid
30 unnecessary fsck runs at boot time, and to network better.
32 config RTC_HCTOSYS_DEVICE
33 string "RTC used to set the system time"
34 depends on RTC_HCTOSYS
37 The RTC device that will be used to (re)initialize the system
38 clock, usually rtc0. Initialization is done when the system
39 starts up, and when it resumes from a low power state. This
40 device should record time in UTC, since the kernel won't do
43 The driver for this RTC device must be loaded before late_initcall
44 functions run, so it must usually be statically linked.
46 This clock should be battery-backed, so that it reads the correct
47 time when the system boots from a power-off state. Otherwise, your
48 system will need an external clock source (like an NTP server).
50 If the clock you specify here is not battery backed, it may still
51 be useful to reinitialize system time when resuming from system
52 sleep states. Do not specify an RTC here unless it stays powered
53 during all this system's supported sleep states.
56 bool "Set the RTC time based on NTP synchronization"
59 If you say yes here, the system time (wall clock) will be stored
60 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
61 minutes if userspace reports synchronized NTP status.
63 config RTC_SYSTOHC_DEVICE
64 string "RTC used to synchronize NTP adjustment"
65 depends on RTC_SYSTOHC
66 default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS
69 The RTC device used for NTP synchronization. The main difference
70 between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this
71 one can sleep when setting time, because it runs in the workqueue
75 bool "RTC debug support"
77 Say yes here to enable debugging support in the RTC framework
78 and individual RTC drivers.
80 comment "RTC interfaces"
83 bool "/sys/class/rtc/rtcN (sysfs)"
87 Say yes here if you want to use your RTCs using sysfs interfaces,
88 /sys/class/rtc/rtc0 through /sys/.../rtcN.
93 bool "/proc/driver/rtc (procfs for rtcN)"
97 Say yes here if you want to use your system clock RTC through
98 the proc interface, /proc/driver/rtc.
99 Other RTCs will not be available through that API.
100 If there is no RTC for the system clock, then the first RTC(rtc0)
106 bool "/dev/rtcN (character devices)"
109 Say yes here if you want to use your RTCs using the /dev
110 interfaces, which "udev" sets up as /dev/rtc0 through
113 You may want to set up a symbolic link so one of these
114 can be accessed as /dev/rtc, which is a name
115 expected by "hwclock" and some other programs. Recent
116 versions of "udev" are known to set up the symlink for you.
120 config RTC_INTF_DEV_UIE_EMUL
121 bool "RTC UIE emulation on dev interface"
122 depends on RTC_INTF_DEV
124 Provides an emulation for RTC_UIE if the underlying rtc chip
125 driver does not expose RTC_UIE ioctls. Those requests generate
126 once-per-second update interrupts, used for synchronization.
128 The emulation code will read the time from the hardware
129 clock several times per second, please enable this option
130 only if you know that you really need it.
133 tristate "Test driver/device"
135 If you say yes here you get support for the
136 RTC test driver. It's a software RTC which can be
137 used to test the RTC subsystem APIs. It gets
138 the time from the system clock.
139 You want this driver only if you are doing development
140 on the RTC subsystem. Please read the source code
143 This driver can also be built as a module. If so, the module
144 will be called rtc-test.
146 comment "I2C RTC drivers"
150 config RTC_DRV_88PM860X
151 tristate "Marvell 88PM860x"
152 depends on MFD_88PM860X
154 If you say yes here you get support for RTC function in Marvell
157 This driver can also be built as a module. If so, the module
158 will be called rtc-88pm860x.
160 config RTC_DRV_88PM80X
161 tristate "Marvell 88PM80x"
162 depends on MFD_88PM800
164 If you say yes here you get support for RTC function in Marvell
167 This driver can also be built as a module. If so, the module
168 will be called rtc-88pm80x.
170 config RTC_DRV_ABB5ZES3
172 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
174 If you say yes here you get support for the Abracon
175 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
177 This driver can also be built as a module. If so, the module
178 will be called rtc-ab-b5ze-s3.
180 config RTC_DRV_ABX80X
181 tristate "Abracon ABx80x"
183 If you say yes here you get support for Abracon AB080X and AB180X
184 families of ultra-low-power battery- and capacitor-backed real-time
187 This driver can also be built as a module. If so, the module
188 will be called rtc-abx80x.
190 config RTC_DRV_AS3722
191 tristate "ams AS3722 RTC driver"
192 depends on MFD_AS3722
194 If you say yes here you get support for the RTC of ams AS3722 PMIC
197 This driver can also be built as a module. If so, the module
198 will be called rtc-as3722.
200 config RTC_DRV_DS1307
201 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
203 If you say yes here you get support for various compatible RTC
204 chips (often with battery backup) connected with I2C. This driver
205 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
206 EPSON RX-8025 and probably other chips. In some cases the RTC
207 must already have been initialized (by manufacturing or a
210 The first seven registers on these chips hold an RTC, and other
211 registers may add features such as NVRAM, a trickle charger for
212 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
213 sysfs, but other chip features may not be available.
215 This driver can also be built as a module. If so, the module
216 will be called rtc-ds1307.
218 config RTC_DRV_DS1307_HWMON
219 bool "HWMON support for rtc-ds1307"
220 depends on RTC_DRV_DS1307 && HWMON
221 depends on !(RTC_DRV_DS1307=y && HWMON=m)
224 Say Y here if you want to expose temperature sensor data on
225 rtc-ds1307 (only DS3231)
227 config RTC_DRV_DS1374
228 tristate "Dallas/Maxim DS1374"
230 If you say yes here you get support for Dallas Semiconductor
231 DS1374 real-time clock chips. If an interrupt is associated
232 with the device, the alarm functionality is supported.
234 This driver can also be built as a module. If so, the module
235 will be called rtc-ds1374.
237 config RTC_DRV_DS1374_WDT
238 bool "Dallas/Maxim DS1374 watchdog timer"
239 depends on RTC_DRV_DS1374
241 If you say Y here you will get support for the
242 watchdog timer in the Dallas Semiconductor DS1374
243 real-time clock chips.
245 config RTC_DRV_DS1672
246 tristate "Dallas/Maxim DS1672"
248 If you say yes here you get support for the
249 Dallas/Maxim DS1672 timekeeping chip.
251 This driver can also be built as a module. If so, the module
252 will be called rtc-ds1672.
254 config RTC_DRV_HYM8563
255 tristate "Haoyu Microelectronics HYM8563"
258 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
259 from the usual rtc functions it provides a clock output of
262 This driver can also be built as a module. If so, the module
263 will be called rtc-hym8563.
265 config RTC_DRV_LP8788
266 tristate "TI LP8788 RTC driver"
267 depends on MFD_LP8788
269 Say Y to enable support for the LP8788 RTC/ALARM driver.
271 config RTC_DRV_MAX6900
272 tristate "Maxim MAX6900"
274 If you say yes here you will get support for the
275 Maxim MAX6900 I2C RTC chip.
277 This driver can also be built as a module. If so, the module
278 will be called rtc-max6900.
280 config RTC_DRV_MAX8907
281 tristate "Maxim MAX8907"
282 depends on MFD_MAX8907
284 If you say yes here you will get support for the
285 RTC of Maxim MAX8907 PMIC.
287 This driver can also be built as a module. If so, the module
288 will be called rtc-max8907.
290 config RTC_DRV_MAX8925
291 tristate "Maxim MAX8925"
292 depends on MFD_MAX8925
294 If you say yes here you will get support for the
295 RTC of Maxim MAX8925 PMIC.
297 This driver can also be built as a module. If so, the module
298 will be called rtc-max8925.
300 config RTC_DRV_MAX8998
301 tristate "Maxim MAX8998"
302 depends on MFD_MAX8998
304 If you say yes here you will get support for the
305 RTC of Maxim MAX8998 PMIC.
307 This driver can also be built as a module. If so, the module
308 will be called rtc-max8998.
310 config RTC_DRV_MAX8997
311 tristate "Maxim MAX8997"
312 depends on MFD_MAX8997
314 If you say yes here you will get support for the
315 RTC of Maxim MAX8997 PMIC.
317 This driver can also be built as a module. If so, the module
318 will be called rtc-max8997.
320 config RTC_DRV_MAX77686
321 tristate "Maxim MAX77686"
322 depends on MFD_MAX77686 || MFD_MAX77620
324 If you say yes here you will get support for the
325 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
327 This driver can also be built as a module. If so, the module
328 will be called rtc-max77686.
331 tristate "Rockchip RK808 RTC"
334 If you say yes here you will get support for the
337 This driver can also be built as a module. If so, the module
338 will be called rk808-rtc.
340 config RTC_DRV_RS5C372
341 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
343 If you say yes here you get support for the
344 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
346 This driver can also be built as a module. If so, the module
347 will be called rtc-rs5c372.
349 config RTC_DRV_ISL1208
350 tristate "Intersil ISL1208"
352 If you say yes here you get support for the
353 Intersil ISL1208 RTC chip.
355 This driver can also be built as a module. If so, the module
356 will be called rtc-isl1208.
358 config RTC_DRV_ISL12022
359 tristate "Intersil ISL12022"
361 If you say yes here you get support for the
362 Intersil ISL12022 RTC chip.
364 This driver can also be built as a module. If so, the module
365 will be called rtc-isl12022.
367 config RTC_DRV_ISL12057
369 tristate "Intersil ISL12057"
371 If you say yes here you get support for the Intersil ISL12057
374 This driver can also be built as a module. If so, the module
375 will be called rtc-isl12057.
378 tristate "Xicor/Intersil X1205"
380 If you say yes here you get support for the
381 Xicor/Intersil X1205 RTC chip.
383 This driver can also be built as a module. If so, the module
384 will be called rtc-x1205.
386 config RTC_DRV_PCF8523
387 tristate "NXP PCF8523"
389 If you say yes here you get support for the NXP PCF8523 RTC
392 This driver can also be built as a module. If so, the module
393 will be called rtc-pcf8523.
395 config RTC_DRV_PCF85063
396 tristate "NXP PCF85063"
398 If you say yes here you get support for the PCF85063 RTC chip
400 This driver can also be built as a module. If so, the module
401 will be called rtc-pcf85063.
403 config RTC_DRV_PCF8563
404 tristate "Philips PCF8563/Epson RTC8564"
406 If you say yes here you get support for the
407 Philips PCF8563 RTC chip. The Epson RTC8564
410 This driver can also be built as a module. If so, the module
411 will be called rtc-pcf8563.
413 config RTC_DRV_PCF8583
414 tristate "Philips PCF8583"
416 If you say yes here you get support for the Philips PCF8583
417 RTC chip found on Acorn RiscPCs. This driver supports the
418 platform specific method of retrieving the current year from
419 the RTC's SRAM. It will work on other platforms with the same
420 chip, but the year will probably have to be tweaked.
422 This driver can also be built as a module. If so, the module
423 will be called rtc-pcf8583.
425 config RTC_DRV_M41T80
426 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
428 If you say Y here you will get support for the ST M41T60
429 and M41T80 RTC chips series. Currently, the following chips are
430 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
431 M41ST85, M41ST87, and MicroCrystal RV4162.
433 This driver can also be built as a module. If so, the module
434 will be called rtc-m41t80.
436 config RTC_DRV_M41T80_WDT
437 bool "ST M41T65/M41T80 series RTC watchdog timer"
438 depends on RTC_DRV_M41T80
440 If you say Y here you will get support for the
441 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
444 tristate "TI BQ32000"
446 If you say Y here you will get support for the TI
447 BQ32000 I2C RTC chip.
449 This driver can also be built as a module. If so, the module
450 will be called rtc-bq32k.
452 config RTC_DRV_DM355EVM
453 tristate "TI DaVinci DM355 EVM RTC"
454 depends on MFD_DM355EVM_MSP
456 Supports the RTC firmware in the MSP430 on the DM355 EVM.
458 config RTC_DRV_TWL92330
459 bool "TI TWL92330/Menelaus"
462 If you say yes here you get support for the RTC on the
463 TWL92330 "Menelaus" power management chip, used with OMAP2
464 platforms. The support is integrated with the rest of
465 the Menelaus driver; it's not separate module.
467 config RTC_DRV_TWL4030
468 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
469 depends on TWL4030_CORE
471 If you say yes here you get support for the RTC on the
472 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
474 This driver can also be built as a module. If so, the module
475 will be called rtc-twl.
477 config RTC_DRV_PALMAS
478 tristate "TI Palmas RTC driver"
479 depends on MFD_PALMAS
481 If you say yes here you get support for the RTC of TI PALMA series PMIC
484 This driver can also be built as a module. If so, the module
485 will be called rtc-palma.
487 config RTC_DRV_TPS6586X
488 tristate "TI TPS6586X RTC driver"
489 depends on MFD_TPS6586X
491 TI Power Management IC TPS6586X supports RTC functionality
492 along with alarm. This driver supports the RTC driver for
493 the TPS6586X RTC module.
495 config RTC_DRV_TPS65910
496 tristate "TI TPS65910 RTC driver"
497 depends on RTC_CLASS && MFD_TPS65910
499 If you say yes here you get support for the RTC on the
502 This driver can also be built as a module. If so, the module
503 will be called rtc-tps65910.
505 config RTC_DRV_TPS80031
506 tristate "TI TPS80031/TPS80032 RTC driver"
507 depends on MFD_TPS80031
509 TI Power Management IC TPS80031 supports RTC functionality
510 along with alarm. This driver supports the RTC driver for
511 the TPS80031 RTC module.
513 config RTC_DRV_RC5T583
514 tristate "RICOH 5T583 RTC driver"
515 depends on MFD_RC5T583
517 If you say yes here you get support for the RTC on the
520 This driver can also be built as a module. If so, the module
521 will be called rtc-rc5t583.
523 config RTC_DRV_S35390A
524 tristate "Seiko Instruments S-35390A"
527 If you say yes here you will get support for the Seiko
528 Instruments S-35390A.
530 This driver can also be built as a module. If so the module
531 will be called rtc-s35390a.
533 config RTC_DRV_FM3130
534 tristate "Ramtron FM3130"
536 If you say Y here you will get support for the
537 Ramtron FM3130 RTC chips.
538 Ramtron FM3130 is a chip with two separate devices inside,
539 RTC clock and FRAM. This driver provides only RTC functionality.
541 This driver can also be built as a module. If so the module
542 will be called rtc-fm3130.
544 config RTC_DRV_RX8010
545 tristate "Epson RX8010SJ"
548 If you say yes here you get support for the Epson RX8010SJ RTC
551 This driver can also be built as a module. If so, the module
552 will be called rtc-rx8010.
554 config RTC_DRV_RX8581
555 tristate "Epson RX-8581"
557 If you say yes here you will get support for the Epson RX-8581.
559 This driver can also be built as a module. If so the module
560 will be called rtc-rx8581.
562 config RTC_DRV_RX8025
563 tristate "Epson RX-8025SA/NB"
565 If you say yes here you get support for the Epson
566 RX-8025SA/NB RTC chips.
568 This driver can also be built as a module. If so, the module
569 will be called rtc-rx8025.
571 config RTC_DRV_EM3027
572 tristate "EM Microelectronic EM3027"
574 If you say yes here you get support for the EM
575 Microelectronic EM3027 RTC chips.
577 This driver can also be built as a module. If so, the module
578 will be called rtc-em3027.
580 config RTC_DRV_RV8803
581 tristate "Micro Crystal RV8803"
583 If you say yes here you get support for the Micro Crystal
586 This driver can also be built as a module. If so, the module
587 will be called rtc-rv8803.
590 tristate "Samsung S2M/S5M series"
591 depends on MFD_SEC_CORE
593 If you say yes here you will get support for the
594 RTC of Samsung S2MPS14 and S5M PMIC series.
596 This driver can also be built as a module. If so, the module
597 will be called rtc-s5m.
601 comment "SPI RTC drivers"
605 config RTC_DRV_M41T93
608 If you say yes here you will get support for the
609 ST M41T93 SPI RTC chip.
611 This driver can also be built as a module. If so, the module
612 will be called rtc-m41t93.
614 config RTC_DRV_M41T94
617 If you say yes here you will get support for the
618 ST M41T94 SPI RTC chip.
620 This driver can also be built as a module. If so, the module
621 will be called rtc-m41t94.
623 config RTC_DRV_DS1302
624 tristate "Dallas/Maxim DS1302"
627 If you say yes here you get support for the Dallas DS1302 RTC chips.
629 This driver can also be built as a module. If so, the module
630 will be called rtc-ds1302.
632 config RTC_DRV_DS1305
633 tristate "Dallas/Maxim DS1305/DS1306"
635 Select this driver to get support for the Dallas/Maxim DS1305
636 and DS1306 real time clock chips. These support a trickle
637 charger, alarms, and NVRAM in addition to the clock.
639 This driver can also be built as a module. If so, the module
640 will be called rtc-ds1305.
642 config RTC_DRV_DS1343
644 tristate "Dallas/Maxim DS1343/DS1344"
646 If you say yes here you get support for the
647 Dallas/Maxim DS1343 and DS1344 real time clock chips.
648 Support for trickle charger, alarm is provided.
650 This driver can also be built as a module. If so, the module
651 will be called rtc-ds1343.
653 config RTC_DRV_DS1347
654 tristate "Dallas/Maxim DS1347"
656 If you say yes here you get support for the
657 Dallas/Maxim DS1347 chips.
659 This driver only supports the RTC feature, and not other chip
660 features such as alarms.
662 This driver can also be built as a module. If so, the module
663 will be called rtc-ds1347.
665 config RTC_DRV_DS1390
666 tristate "Dallas/Maxim DS1390/93/94"
668 If you say yes here you get support for the
669 Dallas/Maxim DS1390/93/94 chips.
671 This driver supports the RTC feature and trickle charging but not
672 other chip features such as alarms.
674 This driver can also be built as a module. If so, the module
675 will be called rtc-ds1390.
677 config RTC_DRV_MAX6916
678 tristate "Maxim MAX6916"
680 If you say yes here you will get support for the
681 Maxim MAX6916 SPI RTC chip.
683 This driver only supports the RTC feature, and not other chip
684 features such as alarms.
686 This driver can also be built as a module. If so, the module
687 will be called rtc-max6916.
690 tristate "Epson RTC-9701JE"
692 If you say yes here you will get support for the
693 Epson RTC-9701JE SPI RTC chip.
695 This driver can also be built as a module. If so, the module
696 will be called rtc-r9701.
698 config RTC_DRV_RX4581
699 tristate "Epson RX-4581"
701 If you say yes here you will get support for the Epson RX-4581.
703 This driver can also be built as a module. If so the module
704 will be called rtc-rx4581.
706 config RTC_DRV_RX6110
707 tristate "Epson RX-6110"
710 If you say yes here you will get support for the Epson RX-6610.
712 This driver can also be built as a module. If so the module
713 will be called rtc-rx6110.
715 config RTC_DRV_RS5C348
716 tristate "Ricoh RS5C348A/B"
718 If you say yes here you get support for the
719 Ricoh RS5C348A and RS5C348B RTC chips.
721 This driver can also be built as a module. If so, the module
722 will be called rtc-rs5c348.
724 config RTC_DRV_MAX6902
725 tristate "Maxim MAX6902"
727 If you say yes here you will get support for the
728 Maxim MAX6902 SPI RTC chip.
730 This driver can also be built as a module. If so, the module
731 will be called rtc-max6902.
733 config RTC_DRV_PCF2123
734 tristate "NXP PCF2123"
736 If you say yes here you get support for the NXP PCF2123
739 This driver can also be built as a module. If so, the module
740 will be called rtc-pcf2123.
742 config RTC_DRV_MCP795
743 tristate "Microchip MCP795"
745 If you say yes here you will get support for the Microchip MCP795.
747 This driver can also be built as a module. If so the module
748 will be called rtc-mcp795.
753 # Helper to resolve issues with configs that have SPI enabled but I2C
754 # modular. See SND_SOC_I2C_AND_SPI for more information
756 config RTC_I2C_AND_SPI
760 default y if SPI_MASTER=y
761 select REGMAP_I2C if I2C
762 select REGMAP_SPI if SPI_MASTER
764 comment "SPI and I2C RTC drivers"
766 config RTC_DRV_DS3232
767 tristate "Dallas/Maxim DS3232/DS3234"
768 depends on RTC_I2C_AND_SPI
770 If you say yes here you get support for Dallas Semiconductor
771 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
772 with the device, the alarm functionality is supported.
774 This driver can also be built as a module. If so, the module
775 will be called rtc-ds3232.
777 config RTC_DRV_PCF2127
778 tristate "NXP PCF2127"
779 depends on RTC_I2C_AND_SPI
781 If you say yes here you get support for the NXP PCF2127/29 RTC
784 This driver can also be built as a module. If so, the module
785 will be called rtc-pcf2127.
787 config RTC_DRV_RV3029C2
788 tristate "Micro Crystal RV3029/3049"
789 depends on RTC_I2C_AND_SPI
791 If you say yes here you get support for the Micro Crystal
792 RV3029 and RV3049 RTC chips.
794 This driver can also be built as a module. If so, the module
795 will be called rtc-rv3029c2.
797 config RTC_DRV_RV3029_HWMON
798 bool "HWMON support for RV3029/3049"
799 depends on RTC_DRV_RV3029C2 && HWMON
800 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
803 Say Y here if you want to expose temperature sensor data on
806 comment "Platform RTC drivers"
808 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
809 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
810 # global rtc_lock ... it's not yet just another platform_device.
813 tristate "PC-style 'CMOS'"
814 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64 || MN10300
816 select RTC_MC146818_LIB
818 Say "yes" here to get direct support for the real time clock
819 found in every PC or ACPI-based system, and some other boards.
820 Specifically the original MC146818, compatibles like those in
821 PC south bridges, the DS12887 or M48T86, some multifunction
822 or LPC bus chips, and so on.
824 Your system will need to define the platform device used by
825 this driver, otherwise it won't be accessible. This means
826 you can safely enable this driver if you don't know whether
827 or not your board has this kind of hardware.
829 This driver can also be built as a module. If so, the module
830 will be called rtc-cmos.
833 bool "Alpha PC-style CMOS"
835 select RTC_MC146818_LIB
838 Direct support for the real-time clock found on every Alpha
839 system, specifically MC146818 compatibles. If in doubt, say Y.
842 tristate "Virtual RTC for Intel MID platforms"
843 depends on X86_INTEL_MID
844 default y if X86_INTEL_MID
847 Say "yes" here to get direct support for the real time clock
848 found on Moorestown platforms. The VRTC is a emulated RTC that
849 derives its clock source from a real RTC in the PMIC. The MC146818
850 style programming interface is mostly conserved, but any
851 updates are done via IPC calls to the system controller FW.
853 config RTC_DRV_DS1216
854 tristate "Dallas DS1216"
857 If you say yes here you get support for the Dallas DS1216 RTC chips.
859 config RTC_DRV_DS1286
860 tristate "Dallas DS1286"
863 If you say yes here you get support for the Dallas DS1286 RTC chips.
865 config RTC_DRV_DS1511
866 tristate "Dallas DS1511"
869 If you say yes here you get support for the
870 Dallas DS1511 timekeeping/watchdog chip.
872 This driver can also be built as a module. If so, the module
873 will be called rtc-ds1511.
875 config RTC_DRV_DS1553
876 tristate "Maxim/Dallas DS1553"
879 If you say yes here you get support for the
880 Maxim/Dallas DS1553 timekeeping chip.
882 This driver can also be built as a module. If so, the module
883 will be called rtc-ds1553.
885 config RTC_DRV_DS1685_FAMILY
886 tristate "Dallas/Maxim DS1685 Family"
888 If you say yes here you get support for the Dallas/Maxim DS1685
889 family of real time chips. This family includes the DS1685/DS1687,
890 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
891 DS17885/DS17887 chips.
893 This driver can also be built as a module. If so, the module
894 will be called rtc-ds1685.
898 depends on RTC_DRV_DS1685_FAMILY
899 default RTC_DRV_DS1685
901 config RTC_DRV_DS1685
904 This enables support for the Dallas/Maxim DS1685/DS1687 real time
907 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
908 systems, as well as EPPC-405-UC modules by electronic system design
911 config RTC_DRV_DS1689
914 This enables support for the Dallas/Maxim DS1689/DS1693 real time
917 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
918 which supports a few minor features such as Vcc, Vbat, and Power
919 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
921 It also works for the even older DS1688/DS1691 RTC chips, which are
922 virtually the same and carry the same model number. Both chips
923 have 114 bytes of user NVRAM.
925 config RTC_DRV_DS17285
926 bool "DS17285/DS17287"
928 This enables support for the Dallas/Maxim DS17285/DS17287 real time
931 This chip features 2kb of extended NV-SRAM. It may possibly be
932 found in some SGI O2 systems (rare).
934 config RTC_DRV_DS17485
935 bool "DS17485/DS17487"
937 This enables support for the Dallas/Maxim DS17485/DS17487 real time
940 This chip features 4kb of extended NV-SRAM.
942 config RTC_DRV_DS17885
943 bool "DS17885/DS17887"
945 This enables support for the Dallas/Maxim DS17885/DS17887 real time
948 This chip features 8kb of extended NV-SRAM.
952 config RTC_DS1685_PROC_REGS
953 bool "Display register values in /proc"
954 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
956 Enable this to display a readout of all of the RTC registers in
957 /proc/drivers/rtc. Keep in mind that this can potentially lead
958 to lost interrupts, as reading Control Register C will clear
959 all pending IRQ flags.
961 Unless you are debugging this driver, choose N.
963 config RTC_DS1685_SYSFS_REGS
964 bool "SysFS access to RTC register bits"
965 depends on RTC_DRV_DS1685_FAMILY && SYSFS
967 Enable this to provide access to the RTC control register bits
968 in /sys. Some of the bits are read-write, others are read-only.
970 Keep in mind that reading Control C's bits automatically clears
971 all pending IRQ flags - this can cause lost interrupts.
973 If you know that you need access to these bits, choose Y, Else N.
975 config RTC_DRV_DS1742
976 tristate "Maxim/Dallas DS1742/1743"
979 If you say yes here you get support for the
980 Maxim/Dallas DS1742/1743 timekeeping chip.
982 This driver can also be built as a module. If so, the module
983 will be called rtc-ds1742.
985 config RTC_DRV_DS2404
986 tristate "Maxim/Dallas DS2404"
988 If you say yes here you get support for the
989 Dallas DS2404 RTC chip.
991 This driver can also be built as a module. If so, the module
992 will be called rtc-ds2404.
994 config RTC_DRV_DA9052
995 tristate "Dialog DA9052/DA9053 RTC"
996 depends on PMIC_DA9052
998 Say y here to support the RTC driver for Dialog Semiconductor
999 DA9052-BC and DA9053-AA/Bx PMICs.
1001 config RTC_DRV_DA9055
1002 tristate "Dialog Semiconductor DA9055 RTC"
1003 depends on MFD_DA9055
1005 If you say yes here you will get support for the
1006 RTC of the Dialog DA9055 PMIC.
1008 This driver can also be built as a module. If so, the module
1009 will be called rtc-da9055
1011 config RTC_DRV_DA9063
1012 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1013 depends on MFD_DA9063 || MFD_DA9062
1015 If you say yes here you will get support for the RTC subsystem
1016 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1018 This driver can also be built as a module. If so, the module
1019 will be called "rtc-da9063".
1023 depends on EFI && !X86
1025 If you say yes here you will get support for the EFI
1028 This driver can also be built as a module. If so, the module
1029 will be called rtc-efi.
1031 config RTC_DRV_STK17TA8
1032 tristate "Simtek STK17TA8"
1033 depends on HAS_IOMEM
1035 If you say yes here you get support for the
1036 Simtek STK17TA8 timekeeping chip.
1038 This driver can also be built as a module. If so, the module
1039 will be called rtc-stk17ta8.
1041 config RTC_DRV_M48T86
1042 tristate "ST M48T86/Dallas DS12887"
1044 If you say Y here you will get support for the
1045 ST M48T86 and Dallas DS12887 RTC chips.
1047 This driver can also be built as a module. If so, the module
1048 will be called rtc-m48t86.
1050 config RTC_DRV_M48T35
1051 tristate "ST M48T35"
1052 depends on HAS_IOMEM
1054 If you say Y here you will get support for the
1057 This driver can also be built as a module, if so, the module
1058 will be called "rtc-m48t35".
1060 config RTC_DRV_M48T59
1061 tristate "ST M48T59/M48T08/M48T02"
1062 depends on HAS_IOMEM
1064 If you say Y here you will get support for the
1065 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1067 These chips are usually found in Sun SPARC and UltraSPARC
1070 This driver can also be built as a module, if so, the module
1071 will be called "rtc-m48t59".
1073 config RTC_DRV_MSM6242
1074 tristate "Oki MSM6242"
1075 depends on HAS_IOMEM
1077 If you say yes here you get support for the Oki MSM6242
1078 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1080 This driver can also be built as a module. If so, the module
1081 will be called rtc-msm6242.
1083 config RTC_DRV_BQ4802
1084 tristate "TI BQ4802"
1085 depends on HAS_IOMEM
1087 If you say Y here you will get support for the TI
1090 This driver can also be built as a module. If so, the module
1091 will be called rtc-bq4802.
1093 config RTC_DRV_RP5C01
1094 tristate "Ricoh RP5C01"
1095 depends on HAS_IOMEM
1097 If you say yes here you get support for the Ricoh RP5C01
1098 timekeeping chip. It is used in some Amiga models (e.g. A3000
1101 This driver can also be built as a module. If so, the module
1102 will be called rtc-rp5c01.
1104 config RTC_DRV_V3020
1105 tristate "EM Microelectronic V3020"
1107 If you say yes here you will get support for the
1108 EM Microelectronic v3020 RTC chip.
1110 This driver can also be built as a module. If so, the module
1111 will be called rtc-v3020.
1113 config RTC_DRV_WM831X
1114 tristate "Wolfson Microelectronics WM831x RTC"
1115 depends on MFD_WM831X
1117 If you say yes here you will get support for the RTC subsystem
1118 of the Wolfson Microelectronics WM831X series PMICs.
1120 This driver can also be built as a module. If so, the module
1121 will be called "rtc-wm831x".
1123 config RTC_DRV_WM8350
1124 tristate "Wolfson Microelectronics WM8350 RTC"
1125 depends on MFD_WM8350
1127 If you say yes here you will get support for the RTC subsystem
1128 of the Wolfson Microelectronics WM8350.
1130 This driver can also be built as a module. If so, the module
1131 will be called "rtc-wm8350".
1133 config RTC_DRV_SPEAR
1134 tristate "SPEAR ST RTC"
1135 depends on PLAT_SPEAR || COMPILE_TEST
1138 If you say Y here you will get support for the RTC found on
1141 config RTC_DRV_PCF50633
1142 depends on MFD_PCF50633
1143 tristate "NXP PCF50633 RTC"
1145 If you say yes here you get support for the RTC subsystem of the
1146 NXP PCF50633 used in embedded systems.
1148 config RTC_DRV_AB3100
1149 tristate "ST-Ericsson AB3100 RTC"
1150 depends on AB3100_CORE
1151 default y if AB3100_CORE
1153 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1154 support. This chip contains a battery- and capacitor-backed RTC.
1156 config RTC_DRV_AB8500
1157 tristate "ST-Ericsson AB8500 RTC"
1158 depends on AB8500_CORE
1160 select RTC_INTF_DEV_UIE_EMUL
1162 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1163 support. This chip contains a battery- and capacitor-backed RTC.
1165 config RTC_DRV_NUC900
1166 tristate "NUC910/NUC920 RTC driver"
1167 depends on ARCH_W90X900 || COMPILE_TEST
1169 If you say yes here you get support for the RTC subsystem of the
1170 NUC910/NUC920 used in embedded systems.
1173 tristate "IBM OPAL RTC driver"
1174 depends on PPC_POWERNV
1177 If you say yes here you get support for the PowerNV platform RTC
1178 driver based on OPAL interfaces.
1180 This driver can also be built as a module. If so, the module
1181 will be called rtc-opal.
1183 config RTC_DRV_ZYNQMP
1184 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1187 If you say yes here you get support for the RTC controller found on
1188 Xilinx Zynq Ultrascale+ MPSoC.
1190 comment "on-CPU RTC drivers"
1192 config RTC_DRV_ASM9260
1193 tristate "Alphascale asm9260 RTC"
1194 depends on MACH_ASM9260
1196 If you say yes here you get support for the RTC on the
1197 Alphascale asm9260 SoC.
1199 This driver can also be built as a module. If so, the module
1200 will be called rtc-asm9260.
1202 config RTC_DRV_DAVINCI
1203 tristate "TI DaVinci RTC"
1204 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1206 If you say yes here you get support for the RTC on the
1207 DaVinci platforms (DM365).
1209 This driver can also be built as a module. If so, the module
1210 will be called rtc-davinci.
1212 config RTC_DRV_DIGICOLOR
1213 tristate "Conexant Digicolor RTC"
1214 depends on ARCH_DIGICOLOR || COMPILE_TEST
1216 If you say yes here you get support for the RTC on Conexant
1217 Digicolor platforms. This currently includes the CX92755 SoC.
1219 This driver can also be built as a module. If so, the module
1220 will be called rtc-digicolor.
1222 config RTC_DRV_IMXDI
1223 tristate "Freescale IMX DryIce Real Time Clock"
1226 Support for Freescale IMX DryIce RTC
1228 This driver can also be built as a module, if so, the module
1229 will be called "rtc-imxdi".
1232 tristate "TI OMAP Real Time Clock"
1233 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1235 Say "yes" here to support the on chip real time clock
1236 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1238 This driver can also be built as a module, if so, module
1239 will be called rtc-omap.
1244 This will include RTC support for Samsung SoCs. If
1245 you want to include RTC support for any machine, kindly
1246 select this in the respective mach-XXXX/Kconfig file.
1249 tristate "Samsung S3C series SoC RTC"
1250 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1252 RTC (Realtime Clock) driver for the clock inbuilt into the
1253 Samsung S3C24XX series of SoCs. This can provide periodic
1254 interrupt rates from 1Hz to 64Hz for user programs, and
1257 The driver currently supports the common features on all the
1258 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1261 This driver can also be build as a module. If so, the module
1262 will be called rtc-s3c.
1264 config RTC_DRV_EP93XX
1265 tristate "Cirrus Logic EP93XX"
1266 depends on ARCH_EP93XX || COMPILE_TEST
1268 If you say yes here you get support for the
1269 RTC embedded in the Cirrus Logic EP93XX processors.
1271 This driver can also be built as a module. If so, the module
1272 will be called rtc-ep93xx.
1274 config RTC_DRV_SA1100
1275 tristate "SA11x0/PXA2xx/PXA910"
1276 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1278 If you say Y here you will get access to the real time clock
1279 built into your SA11x0 or PXA2xx CPU.
1281 To compile this driver as a module, choose M here: the
1282 module will be called rtc-sa1100.
1285 tristate "SuperH On-Chip RTC"
1286 depends on SUPERH && HAVE_CLK
1288 Say Y here to enable support for the on-chip RTC found in
1289 most SuperH processors.
1291 To compile this driver as a module, choose M here: the
1292 module will be called rtc-sh.
1294 config RTC_DRV_VR41XX
1295 tristate "NEC VR41XX"
1296 depends on CPU_VR41XX || COMPILE_TEST
1298 If you say Y here you will get access to the real time clock
1299 built into your NEC VR41XX CPU.
1301 To compile this driver as a module, choose M here: the
1302 module will be called rtc-vr41xx.
1304 config RTC_DRV_PL030
1305 tristate "ARM AMBA PL030 RTC"
1308 If you say Y here you will get access to ARM AMBA
1309 PrimeCell PL030 RTC found on certain ARM SOCs.
1311 To compile this driver as a module, choose M here: the
1312 module will be called rtc-pl030.
1314 config RTC_DRV_PL031
1315 tristate "ARM AMBA PL031 RTC"
1318 If you say Y here you will get access to ARM AMBA
1319 PrimeCell PL031 RTC found on certain ARM SOCs.
1321 To compile this driver as a module, choose M here: the
1322 module will be called rtc-pl031.
1324 config RTC_DRV_AT32AP700X
1325 tristate "AT32AP700X series RTC"
1326 depends on PLATFORM_AT32AP || COMPILE_TEST
1328 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1329 AT32AP700x family processors.
1331 config RTC_DRV_AT91RM9200
1332 tristate "AT91RM9200 or some AT91SAM9 RTC"
1333 depends on ARCH_AT91 || COMPILE_TEST
1335 Driver for the internal RTC (Realtime Clock) module found on
1336 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1337 this is powered by the backup power supply.
1339 config RTC_DRV_AT91SAM9
1340 tristate "AT91SAM9 RTT as RTC"
1341 depends on ARCH_AT91 || COMPILE_TEST
1344 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1345 can be used as an RTC thanks to the backup power supply (e.g. a
1346 small coin cell battery) which keeps this block and the GPBR
1347 (General Purpose Backup Registers) block powered when the device
1349 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1350 probably want to use the real RTC block instead of the "RTT as an
1353 config RTC_DRV_AU1XXX
1354 tristate "Au1xxx Counter0 RTC support"
1355 depends on MIPS_ALCHEMY
1357 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1358 counter) to be used as a RTC.
1360 This driver can also be built as a module. If so, the module
1361 will be called rtc-au1xxx.
1364 tristate "Blackfin On-Chip RTC"
1365 depends on BLACKFIN && !BF561
1367 If you say yes here you will get support for the
1368 Blackfin On-Chip Real Time Clock.
1370 This driver can also be built as a module. If so, the module
1371 will be called rtc-bfin.
1373 config RTC_DRV_RS5C313
1374 tristate "Ricoh RS5C313"
1375 depends on SH_LANDISK
1377 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1379 config RTC_DRV_GENERIC
1380 tristate "Generic RTC support"
1381 # Please consider writing a new RTC driver instead of using the generic
1383 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
1385 Say Y or M here to enable RTC support on systems using the generic
1386 RTC abstraction. If you do not know what you are doing, you should
1390 tristate "PXA27x/PXA3xx"
1392 select RTC_DRV_SA1100
1394 If you say Y here you will get access to the real time clock
1395 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1396 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1398 This RTC driver uses PXA RTC registers available since pxa27x
1399 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1401 config RTC_DRV_VT8500
1402 tristate "VIA/WonderMedia 85xx SoC RTC"
1403 depends on ARCH_VT8500 || COMPILE_TEST
1405 If you say Y here you will get access to the real time clock
1406 built into your VIA VT8500 SoC or its relatives.
1409 config RTC_DRV_SUN4V
1410 bool "SUN4V Hypervisor RTC"
1413 If you say Y here you will get support for the Hypervisor
1414 based RTC on SUN4V systems.
1416 config RTC_DRV_SUN6I
1417 tristate "Allwinner A31 RTC"
1418 default MACH_SUN6I || MACH_SUN8I || COMPILE_TEST
1419 depends on ARCH_SUNXI
1421 If you say Y here you will get support for the RTC found in
1422 some Allwinner SoCs like the A31 or the A64.
1424 config RTC_DRV_SUNXI
1425 tristate "Allwinner sun4i/sun7i RTC"
1426 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1428 If you say Y here you will get support for the RTC found on
1431 config RTC_DRV_STARFIRE
1435 If you say Y here you will get support for the RTC found on
1438 config RTC_DRV_TX4939
1439 tristate "TX4939 SoC"
1440 depends on SOC_TX4939
1442 Driver for the internal RTC (Realtime Clock) module found on
1446 tristate "Marvell SoC RTC"
1447 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1449 If you say yes here you will get support for the in-chip RTC
1450 that can be found in some of Marvell's SoC devices, such as
1451 the Kirkwood 88F6281 and 88F6192.
1453 This driver can also be built as a module. If so, the module
1454 will be called rtc-mv.
1456 config RTC_DRV_ARMADA38X
1457 tristate "Armada 38x Marvell SoC RTC"
1458 depends on ARCH_MVEBU || COMPILE_TEST
1460 If you say yes here you will get support for the in-chip RTC
1461 that can be found in the Armada 38x Marvell's SoC device
1463 This driver can also be built as a module. If so, the module
1464 will be called armada38x-rtc.
1466 config RTC_DRV_GEMINI
1467 tristate "Gemini SoC RTC"
1468 depends on ARCH_GEMINI || COMPILE_TEST
1469 depends on HAS_IOMEM
1471 If you say Y here you will get support for the
1472 RTC found on Gemini SoC's.
1474 This driver can also be built as a module. If so, the module
1475 will be called rtc-gemini.
1481 If you say yes here you will get support for the RTC on PS3.
1483 This driver can also be built as a module. If so, the module
1484 will be called rtc-ps3.
1486 config RTC_DRV_COH901331
1487 tristate "ST-Ericsson COH 901 331 RTC"
1488 depends on ARCH_U300 || COMPILE_TEST
1490 If you say Y here you will get access to ST-Ericsson
1491 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1494 This driver can also be built as a module. If so, the module
1495 will be called "rtc-coh901331".
1499 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1500 depends on ARCH_MXS || COMPILE_TEST
1503 If you say yes here you will get support for the onboard
1504 STMP3xxx/i.MX23/i.MX28 RTC.
1506 This driver can also be built as a module. If so, the module
1507 will be called rtc-stmp3xxx.
1513 If you say Y here you will get support for the RTC found on
1514 the PCAP2 ASIC used on some Motorola phones.
1516 config RTC_DRV_MC13XXX
1517 depends on MFD_MC13XXX
1518 tristate "Freescale MC13xxx RTC"
1520 This enables support for the RTCs found on Freescale's PMICs
1521 MC13783 and MC13892.
1523 config RTC_DRV_MPC5121
1524 tristate "Freescale MPC5121 built-in RTC"
1525 depends on PPC_MPC512x || PPC_MPC52xx
1527 If you say yes here you will get support for the
1528 built-in RTC on MPC5121 or on MPC5200.
1530 This driver can also be built as a module. If so, the module
1531 will be called rtc-mpc5121.
1533 config RTC_DRV_JZ4740
1534 tristate "Ingenic JZ4740 SoC"
1535 depends on MACH_JZ4740 || COMPILE_TEST
1537 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1540 This driver can also be buillt as a module. If so, the module
1541 will be called rtc-jz4740.
1543 config RTC_DRV_LPC24XX
1544 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1545 depends on ARCH_LPC18XX || COMPILE_TEST
1546 depends on OF && HAS_IOMEM
1548 This enables support for the NXP RTC found which can be found on
1549 NXP LPC178x/18xx/408x/43xx devices.
1551 If you have one of the devices above enable this driver to use
1552 the hardware RTC. This driver can also be buillt as a module. If
1553 so, the module will be called rtc-lpc24xx.
1555 config RTC_DRV_LPC32XX
1556 depends on ARCH_LPC32XX || COMPILE_TEST
1557 tristate "NXP LPC32XX RTC"
1559 This enables support for the NXP RTC in the LPC32XX
1561 This driver can also be buillt as a module. If so, the module
1562 will be called rtc-lpc32xx.
1564 config RTC_DRV_PM8XXX
1565 tristate "Qualcomm PMIC8XXX RTC"
1566 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1568 If you say yes here you get support for the
1569 Qualcomm PMIC8XXX RTC.
1571 To compile this driver as a module, choose M here: the
1572 module will be called rtc-pm8xxx.
1574 config RTC_DRV_TEGRA
1575 tristate "NVIDIA Tegra Internal RTC driver"
1576 depends on ARCH_TEGRA || COMPILE_TEST
1578 If you say yes here you get support for the
1579 Tegra 200 series internal RTC module.
1581 This drive can also be built as a module. If so, the module
1582 will be called rtc-tegra.
1585 tristate "Tilera hypervisor RTC support"
1588 Enable support for the Linux driver side of the Tilera
1589 hypervisor's real-time clock interface.
1592 tristate "PKUnity v3 RTC support"
1593 depends on ARCH_PUV3
1595 This enables support for the RTC in the PKUnity-v3 SoCs.
1597 This drive can also be built as a module. If so, the module
1598 will be called rtc-puv3.
1600 config RTC_DRV_LOONGSON1
1601 tristate "loongson1 RTC support"
1602 depends on MACH_LOONGSON32
1604 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1605 counter) to be used as a RTC.
1607 This driver can also be built as a module. If so, the module
1608 will be called rtc-ls1x.
1611 tristate "Freescale MXC Real Time Clock"
1614 If you say yes here you get support for the Freescale MXC
1617 This driver can also be built as a module, if so, the module
1618 will be called "rtc-mxc".
1621 tristate "Freescale SNVS RTC support"
1623 depends on HAS_IOMEM
1626 If you say yes here you get support for the Freescale SNVS
1627 Low Power (LP) RTC module.
1629 This driver can also be built as a module, if so, the module
1630 will be called "rtc-snvs".
1632 config RTC_DRV_SIRFSOC
1633 tristate "SiRFSOC RTC"
1634 depends on ARCH_SIRF
1636 Say "yes" here to support the real time clock on SiRF SOC chips.
1637 This driver can also be built as a module called rtc-sirfsoc.
1639 config RTC_DRV_ST_LPC
1640 tristate "STMicroelectronics LPC RTC"
1644 Say Y here to include STMicroelectronics Low Power Controller
1645 (LPC) based RTC support.
1647 To compile this driver as a module, choose M here: the
1648 module will be called rtc-st-lpc.
1650 config RTC_DRV_MOXART
1651 tristate "MOXA ART RTC"
1652 depends on ARCH_MOXART || COMPILE_TEST
1654 If you say yes here you get support for the MOXA ART
1657 This driver can also be built as a module. If so, the module
1658 will be called rtc-moxart
1660 config RTC_DRV_MT6397
1661 tristate "Mediatek Real Time Clock driver"
1662 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1664 This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
1665 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1666 Mediatek(R) RTC driver.
1668 If you want to use Mediatek(R) RTC interface, select Y or M here.
1670 config RTC_DRV_XGENE
1671 tristate "APM X-Gene RTC"
1672 depends on HAS_IOMEM
1673 depends on ARCH_XGENE || COMPILE_TEST
1675 If you say yes here you get support for the APM X-Gene SoC real time
1678 This driver can also be built as a module, if so, the module
1679 will be called "rtc-xgene".
1681 config RTC_DRV_PIC32
1682 tristate "Microchip PIC32 RTC"
1683 depends on MACH_PIC32
1686 If you say yes here you get support for the PIC32 RTC module.
1688 This driver can also be built as a module. If so, the module
1689 will be called rtc-pic32
1691 comment "HID Sensor RTC drivers"
1693 config RTC_DRV_HID_SENSOR_TIME
1694 tristate "HID Sensor Time"
1697 select HID_SENSOR_HUB
1698 select HID_SENSOR_IIO_COMMON
1700 Say yes here to build support for the HID Sensors of type Time.
1701 This drivers makes such sensors available as RTCs.
1703 If this driver is compiled as a module, it will be named
1704 rtc-hid-sensor-time.