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.
191 tristate "X-Powers AC100"
194 If you say yes here you get support for the real-time clock found
195 in X-Powers AC100 family peripheral ICs.
197 This driver can also be built as a module. If so, the module
198 will be called rtc-ac100.
200 config RTC_DRV_AS3722
201 tristate "ams AS3722 RTC driver"
202 depends on MFD_AS3722
204 If you say yes here you get support for the RTC of ams AS3722 PMIC
207 This driver can also be built as a module. If so, the module
208 will be called rtc-as3722.
210 config RTC_DRV_DS1307
211 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025, ISL12057"
213 If you say yes here you get support for various compatible RTC
214 chips (often with battery backup) connected with I2C. This driver
215 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
216 EPSON RX-8025, Intersil ISL12057 and probably other chips. In some
217 cases the RTC must already have been initialized (by manufacturing or
220 The first seven registers on these chips hold an RTC, and other
221 registers may add features such as NVRAM, a trickle charger for
222 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
223 sysfs, but other chip features may not be available.
225 This driver can also be built as a module. If so, the module
226 will be called rtc-ds1307.
228 config RTC_DRV_DS1307_HWMON
229 bool "HWMON support for rtc-ds1307"
230 depends on RTC_DRV_DS1307 && HWMON
231 depends on !(RTC_DRV_DS1307=y && HWMON=m)
234 Say Y here if you want to expose temperature sensor data on
235 rtc-ds1307 (only DS3231)
237 config RTC_DRV_DS1307_CENTURY
238 bool "Century bit support for rtc-ds1307"
239 depends on RTC_DRV_DS1307
242 The DS1307 driver suffered from a bug where it was enabling the
243 century bit inconditionnally but never used it when reading the time.
244 It made the driver unable to support dates beyond 2099.
245 Setting this option will add proper support for the century bit but if
246 the time was previously set using a kernel predating this option,
247 reading the date will return a date in the next century.
248 To solve that, you could boot a kernel without this option set, set
249 the RTC date and then boot a kernel with this option set.
251 config RTC_DRV_DS1374
252 tristate "Dallas/Maxim DS1374"
254 If you say yes here you get support for Dallas Semiconductor
255 DS1374 real-time clock chips. If an interrupt is associated
256 with the device, the alarm functionality is supported.
258 This driver can also be built as a module. If so, the module
259 will be called rtc-ds1374.
261 config RTC_DRV_DS1374_WDT
262 bool "Dallas/Maxim DS1374 watchdog timer"
263 depends on RTC_DRV_DS1374
265 If you say Y here you will get support for the
266 watchdog timer in the Dallas Semiconductor DS1374
267 real-time clock chips.
269 config RTC_DRV_DS1672
270 tristate "Dallas/Maxim DS1672"
272 If you say yes here you get support for the
273 Dallas/Maxim DS1672 timekeeping chip.
275 This driver can also be built as a module. If so, the module
276 will be called rtc-ds1672.
278 config RTC_DRV_HYM8563
279 tristate "Haoyu Microelectronics HYM8563"
282 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
283 from the usual rtc functions it provides a clock output of
286 This driver can also be built as a module. If so, the module
287 will be called rtc-hym8563.
289 config RTC_DRV_LP8788
290 tristate "TI LP8788 RTC driver"
291 depends on MFD_LP8788
293 Say Y to enable support for the LP8788 RTC/ALARM driver.
295 config RTC_DRV_MAX6900
296 tristate "Maxim MAX6900"
298 If you say yes here you will get support for the
299 Maxim MAX6900 I2C RTC chip.
301 This driver can also be built as a module. If so, the module
302 will be called rtc-max6900.
304 config RTC_DRV_MAX8907
305 tristate "Maxim MAX8907"
306 depends on MFD_MAX8907
309 If you say yes here you will get support for the
310 RTC of Maxim MAX8907 PMIC.
312 This driver can also be built as a module. If so, the module
313 will be called rtc-max8907.
315 config RTC_DRV_MAX8925
316 tristate "Maxim MAX8925"
317 depends on MFD_MAX8925
319 If you say yes here you will get support for the
320 RTC of Maxim MAX8925 PMIC.
322 This driver can also be built as a module. If so, the module
323 will be called rtc-max8925.
325 config RTC_DRV_MAX8998
326 tristate "Maxim MAX8998"
327 depends on MFD_MAX8998
329 If you say yes here you will get support for the
330 RTC of Maxim MAX8998 PMIC.
332 This driver can also be built as a module. If so, the module
333 will be called rtc-max8998.
335 config RTC_DRV_MAX8997
336 tristate "Maxim MAX8997"
337 depends on MFD_MAX8997
339 If you say yes here you will get support for the
340 RTC of Maxim MAX8997 PMIC.
342 This driver can also be built as a module. If so, the module
343 will be called rtc-max8997.
345 config RTC_DRV_MAX77686
346 tristate "Maxim MAX77686"
347 depends on MFD_MAX77686 || MFD_MAX77620
349 If you say yes here you will get support for the
350 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
352 This driver can also be built as a module. If so, the module
353 will be called rtc-max77686.
356 tristate "Rockchip RK808/RK818 RTC"
359 If you say yes here you will get support for the
360 RTC of RK808 and RK818 PMIC.
362 This driver can also be built as a module. If so, the module
363 will be called rk808-rtc.
365 config RTC_DRV_RS5C372
366 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
368 If you say yes here you get support for the
369 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
371 This driver can also be built as a module. If so, the module
372 will be called rtc-rs5c372.
374 config RTC_DRV_ISL1208
375 tristate "Intersil ISL1208"
377 If you say yes here you get support for the
378 Intersil ISL1208 RTC chip.
380 This driver can also be built as a module. If so, the module
381 will be called rtc-isl1208.
383 config RTC_DRV_ISL12022
384 tristate "Intersil ISL12022"
386 If you say yes here you get support for the
387 Intersil ISL12022 RTC chip.
389 This driver can also be built as a module. If so, the module
390 will be called rtc-isl12022.
393 tristate "Xicor/Intersil X1205"
395 If you say yes here you get support for the
396 Xicor/Intersil X1205 RTC chip.
398 This driver can also be built as a module. If so, the module
399 will be called rtc-x1205.
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_RV8803
596 tristate "Micro Crystal RV8803, Epson RX8900"
598 If you say yes here you get support for the Micro Crystal RV8803 and
599 Epson RX8900 RTC chips.
601 This driver can also be built as a module. If so, the module
602 will be called rtc-rv8803.
605 tristate "Samsung S2M/S5M series"
606 depends on MFD_SEC_CORE
608 If you say yes here you will get support for the
609 RTC of Samsung S2MPS14 and S5M PMIC series.
611 This driver can also be built as a module. If so, the module
612 will be called rtc-s5m.
616 comment "SPI RTC drivers"
620 config RTC_DRV_M41T93
623 If you say yes here you will get support for the
624 ST M41T93 SPI RTC chip.
626 This driver can also be built as a module. If so, the module
627 will be called rtc-m41t93.
629 config RTC_DRV_M41T94
632 If you say yes here you will get support for the
633 ST M41T94 SPI RTC chip.
635 This driver can also be built as a module. If so, the module
636 will be called rtc-m41t94.
638 config RTC_DRV_DS1302
639 tristate "Dallas/Maxim DS1302"
642 If you say yes here you get support for the Dallas DS1302 RTC chips.
644 This driver can also be built as a module. If so, the module
645 will be called rtc-ds1302.
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
670 tristate "Dallas/Maxim DS1347"
672 If you say yes here you get support for the
673 Dallas/Maxim DS1347 chips.
675 This driver only supports the RTC feature, and not other chip
676 features such as alarms.
678 This driver can also be built as a module. If so, the module
679 will be called rtc-ds1347.
681 config RTC_DRV_DS1390
682 tristate "Dallas/Maxim DS1390/93/94"
684 If you say yes here you get support for the
685 Dallas/Maxim DS1390/93/94 chips.
687 This driver supports the RTC feature and trickle charging but not
688 other chip features such as alarms.
690 This driver can also be built as a module. If so, the module
691 will be called rtc-ds1390.
693 config RTC_DRV_MAX6916
694 tristate "Maxim MAX6916"
696 If you say yes here you will get support for the
697 Maxim MAX6916 SPI RTC chip.
699 This driver only supports the RTC feature, and not other chip
700 features such as alarms.
702 This driver can also be built as a module. If so, the module
703 will be called rtc-max6916.
706 tristate "Epson RTC-9701JE"
708 If you say yes here you will get support for the
709 Epson RTC-9701JE SPI RTC chip.
711 This driver can also be built as a module. If so, the module
712 will be called rtc-r9701.
714 config RTC_DRV_RX4581
715 tristate "Epson RX-4581"
717 If you say yes here you will get support for the Epson RX-4581.
719 This driver can also be built as a module. If so the module
720 will be called rtc-rx4581.
722 config RTC_DRV_RX6110
723 tristate "Epson RX-6110"
726 If you say yes here you will get support for the Epson RX-6610.
728 This driver can also be built as a module. If so the module
729 will be called rtc-rx6110.
731 config RTC_DRV_RS5C348
732 tristate "Ricoh RS5C348A/B"
734 If you say yes here you get support for the
735 Ricoh RS5C348A and RS5C348B RTC chips.
737 This driver can also be built as a module. If so, the module
738 will be called rtc-rs5c348.
740 config RTC_DRV_MAX6902
741 tristate "Maxim MAX6902"
743 If you say yes here you will get support for the
744 Maxim MAX6902 SPI RTC chip.
746 This driver can also be built as a module. If so, the module
747 will be called rtc-max6902.
749 config RTC_DRV_PCF2123
750 tristate "NXP PCF2123"
752 If you say yes here you get support for the NXP PCF2123
755 This driver can also be built as a module. If so, the module
756 will be called rtc-pcf2123.
758 config RTC_DRV_MCP795
759 tristate "Microchip MCP795"
761 If you say yes here you will get support for the Microchip MCP795.
763 This driver can also be built as a module. If so the module
764 will be called rtc-mcp795.
769 # Helper to resolve issues with configs that have SPI enabled but I2C
770 # modular. See SND_SOC_I2C_AND_SPI for more information
772 config RTC_I2C_AND_SPI
776 default y if SPI_MASTER=y
777 select REGMAP_I2C if I2C
778 select REGMAP_SPI if SPI_MASTER
780 comment "SPI and I2C RTC drivers"
782 config RTC_DRV_DS3232
783 tristate "Dallas/Maxim DS3232/DS3234"
784 depends on RTC_I2C_AND_SPI
786 If you say yes here you get support for Dallas Semiconductor
787 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
788 with the device, the alarm functionality is supported.
790 This driver can also be built as a module. If so, the module
791 will be called rtc-ds3232.
793 config RTC_DRV_PCF2127
794 tristate "NXP PCF2127"
795 depends on RTC_I2C_AND_SPI
797 If you say yes here you get support for the NXP PCF2127/29 RTC
800 This driver can also be built as a module. If so, the module
801 will be called rtc-pcf2127.
803 config RTC_DRV_RV3029C2
804 tristate "Micro Crystal RV3029/3049"
805 depends on RTC_I2C_AND_SPI
807 If you say yes here you get support for the Micro Crystal
808 RV3029 and RV3049 RTC chips.
810 This driver can also be built as a module. If so, the module
811 will be called rtc-rv3029c2.
813 config RTC_DRV_RV3029_HWMON
814 bool "HWMON support for RV3029/3049"
815 depends on RTC_DRV_RV3029C2 && HWMON
816 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
819 Say Y here if you want to expose temperature sensor data on
822 comment "Platform RTC drivers"
824 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
825 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
826 # global rtc_lock ... it's not yet just another platform_device.
829 tristate "PC-style 'CMOS'"
830 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64 || MN10300
832 select RTC_MC146818_LIB
834 Say "yes" here to get direct support for the real time clock
835 found in every PC or ACPI-based system, and some other boards.
836 Specifically the original MC146818, compatibles like those in
837 PC south bridges, the DS12887 or M48T86, some multifunction
838 or LPC bus chips, and so on.
840 Your system will need to define the platform device used by
841 this driver, otherwise it won't be accessible. This means
842 you can safely enable this driver if you don't know whether
843 or not your board has this kind of hardware.
845 This driver can also be built as a module. If so, the module
846 will be called rtc-cmos.
849 bool "Alpha PC-style CMOS"
851 select RTC_MC146818_LIB
854 Direct support for the real-time clock found on every Alpha
855 system, specifically MC146818 compatibles. If in doubt, say Y.
858 tristate "Virtual RTC for Intel MID platforms"
859 depends on X86_INTEL_MID
860 default y if X86_INTEL_MID
863 Say "yes" here to get direct support for the real time clock
864 found on Moorestown platforms. The VRTC is a emulated RTC that
865 derives its clock source from a real RTC in the PMIC. The MC146818
866 style programming interface is mostly conserved, but any
867 updates are done via IPC calls to the system controller FW.
869 config RTC_DRV_DS1216
870 tristate "Dallas DS1216"
873 If you say yes here you get support for the Dallas DS1216 RTC chips.
875 config RTC_DRV_DS1286
876 tristate "Dallas DS1286"
879 If you say yes here you get support for the Dallas DS1286 RTC chips.
881 config RTC_DRV_DS1511
882 tristate "Dallas DS1511"
885 If you say yes here you get support for the
886 Dallas DS1511 timekeeping/watchdog chip.
888 This driver can also be built as a module. If so, the module
889 will be called rtc-ds1511.
891 config RTC_DRV_DS1553
892 tristate "Maxim/Dallas DS1553"
895 If you say yes here you get support for the
896 Maxim/Dallas DS1553 timekeeping chip.
898 This driver can also be built as a module. If so, the module
899 will be called rtc-ds1553.
901 config RTC_DRV_DS1685_FAMILY
902 tristate "Dallas/Maxim DS1685 Family"
904 If you say yes here you get support for the Dallas/Maxim DS1685
905 family of real time chips. This family includes the DS1685/DS1687,
906 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
907 DS17885/DS17887 chips.
909 This driver can also be built as a module. If so, the module
910 will be called rtc-ds1685.
914 depends on RTC_DRV_DS1685_FAMILY
915 default RTC_DRV_DS1685
917 config RTC_DRV_DS1685
920 This enables support for the Dallas/Maxim DS1685/DS1687 real time
923 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
924 systems, as well as EPPC-405-UC modules by electronic system design
927 config RTC_DRV_DS1689
930 This enables support for the Dallas/Maxim DS1689/DS1693 real time
933 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
934 which supports a few minor features such as Vcc, Vbat, and Power
935 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
937 It also works for the even older DS1688/DS1691 RTC chips, which are
938 virtually the same and carry the same model number. Both chips
939 have 114 bytes of user NVRAM.
941 config RTC_DRV_DS17285
942 bool "DS17285/DS17287"
944 This enables support for the Dallas/Maxim DS17285/DS17287 real time
947 This chip features 2kb of extended NV-SRAM. It may possibly be
948 found in some SGI O2 systems (rare).
950 config RTC_DRV_DS17485
951 bool "DS17485/DS17487"
953 This enables support for the Dallas/Maxim DS17485/DS17487 real time
956 This chip features 4kb of extended NV-SRAM.
958 config RTC_DRV_DS17885
959 bool "DS17885/DS17887"
961 This enables support for the Dallas/Maxim DS17885/DS17887 real time
964 This chip features 8kb of extended NV-SRAM.
968 config RTC_DS1685_PROC_REGS
969 bool "Display register values in /proc"
970 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
972 Enable this to display a readout of all of the RTC registers in
973 /proc/drivers/rtc. Keep in mind that this can potentially lead
974 to lost interrupts, as reading Control Register C will clear
975 all pending IRQ flags.
977 Unless you are debugging this driver, choose N.
979 config RTC_DS1685_SYSFS_REGS
980 bool "SysFS access to RTC register bits"
981 depends on RTC_DRV_DS1685_FAMILY && SYSFS
983 Enable this to provide access to the RTC control register bits
984 in /sys. Some of the bits are read-write, others are read-only.
986 Keep in mind that reading Control C's bits automatically clears
987 all pending IRQ flags - this can cause lost interrupts.
989 If you know that you need access to these bits, choose Y, Else N.
991 config RTC_DRV_DS1742
992 tristate "Maxim/Dallas DS1742/1743"
995 If you say yes here you get support for the
996 Maxim/Dallas DS1742/1743 timekeeping chip.
998 This driver can also be built as a module. If so, the module
999 will be called rtc-ds1742.
1001 config RTC_DRV_DS2404
1002 tristate "Maxim/Dallas DS2404"
1004 If you say yes here you get support for the
1005 Dallas DS2404 RTC chip.
1007 This driver can also be built as a module. If so, the module
1008 will be called rtc-ds2404.
1010 config RTC_DRV_DA9052
1011 tristate "Dialog DA9052/DA9053 RTC"
1012 depends on PMIC_DA9052
1014 Say y here to support the RTC driver for Dialog Semiconductor
1015 DA9052-BC and DA9053-AA/Bx PMICs.
1017 config RTC_DRV_DA9055
1018 tristate "Dialog Semiconductor DA9055 RTC"
1019 depends on MFD_DA9055
1021 If you say yes here you will get support for the
1022 RTC of the Dialog DA9055 PMIC.
1024 This driver can also be built as a module. If so, the module
1025 will be called rtc-da9055
1027 config RTC_DRV_DA9063
1028 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1029 depends on MFD_DA9063 || MFD_DA9062
1031 If you say yes here you will get support for the RTC subsystem
1032 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1034 This driver can also be built as a module. If so, the module
1035 will be called "rtc-da9063".
1039 depends on EFI && !X86
1041 If you say yes here you will get support for the EFI
1044 This driver can also be built as a module. If so, the module
1045 will be called rtc-efi.
1047 config RTC_DRV_STK17TA8
1048 tristate "Simtek STK17TA8"
1049 depends on HAS_IOMEM
1051 If you say yes here you get support for the
1052 Simtek STK17TA8 timekeeping chip.
1054 This driver can also be built as a module. If so, the module
1055 will be called rtc-stk17ta8.
1057 config RTC_DRV_M48T86
1058 tristate "ST M48T86/Dallas DS12887"
1060 If you say Y here you will get support for the
1061 ST M48T86 and Dallas DS12887 RTC chips.
1063 This driver can also be built as a module. If so, the module
1064 will be called rtc-m48t86.
1066 config RTC_DRV_M48T35
1067 tristate "ST M48T35"
1068 depends on HAS_IOMEM
1070 If you say Y here you will get support for the
1073 This driver can also be built as a module, if so, the module
1074 will be called "rtc-m48t35".
1076 config RTC_DRV_M48T59
1077 tristate "ST M48T59/M48T08/M48T02"
1078 depends on HAS_IOMEM
1080 If you say Y here you will get support for the
1081 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1083 These chips are usually found in Sun SPARC and UltraSPARC
1086 This driver can also be built as a module, if so, the module
1087 will be called "rtc-m48t59".
1089 config RTC_DRV_MSM6242
1090 tristate "Oki MSM6242"
1091 depends on HAS_IOMEM
1093 If you say yes here you get support for the Oki MSM6242
1094 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1096 This driver can also be built as a module. If so, the module
1097 will be called rtc-msm6242.
1099 config RTC_DRV_BQ4802
1100 tristate "TI BQ4802"
1101 depends on HAS_IOMEM
1103 If you say Y here you will get support for the TI
1106 This driver can also be built as a module. If so, the module
1107 will be called rtc-bq4802.
1109 config RTC_DRV_RP5C01
1110 tristate "Ricoh RP5C01"
1111 depends on HAS_IOMEM
1113 If you say yes here you get support for the Ricoh RP5C01
1114 timekeeping chip. It is used in some Amiga models (e.g. A3000
1117 This driver can also be built as a module. If so, the module
1118 will be called rtc-rp5c01.
1120 config RTC_DRV_V3020
1121 tristate "EM Microelectronic V3020"
1123 If you say yes here you will get support for the
1124 EM Microelectronic v3020 RTC chip.
1126 This driver can also be built as a module. If so, the module
1127 will be called rtc-v3020.
1129 config RTC_DRV_WM831X
1130 tristate "Wolfson Microelectronics WM831x RTC"
1131 depends on MFD_WM831X
1133 If you say yes here you will get support for the RTC subsystem
1134 of the Wolfson Microelectronics WM831X series PMICs.
1136 This driver can also be built as a module. If so, the module
1137 will be called "rtc-wm831x".
1139 config RTC_DRV_WM8350
1140 tristate "Wolfson Microelectronics WM8350 RTC"
1141 depends on MFD_WM8350
1143 If you say yes here you will get support for the RTC subsystem
1144 of the Wolfson Microelectronics WM8350.
1146 This driver can also be built as a module. If so, the module
1147 will be called "rtc-wm8350".
1149 config RTC_DRV_SPEAR
1150 tristate "SPEAR ST RTC"
1151 depends on PLAT_SPEAR || COMPILE_TEST
1154 If you say Y here you will get support for the RTC found on
1157 config RTC_DRV_PCF50633
1158 depends on MFD_PCF50633
1159 tristate "NXP PCF50633 RTC"
1161 If you say yes here you get support for the RTC subsystem of the
1162 NXP PCF50633 used in embedded systems.
1164 config RTC_DRV_AB3100
1165 tristate "ST-Ericsson AB3100 RTC"
1166 depends on AB3100_CORE
1167 default y if AB3100_CORE
1169 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1170 support. This chip contains a battery- and capacitor-backed RTC.
1172 config RTC_DRV_AB8500
1173 tristate "ST-Ericsson AB8500 RTC"
1174 depends on AB8500_CORE
1176 select RTC_INTF_DEV_UIE_EMUL
1178 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1179 support. This chip contains a battery- and capacitor-backed RTC.
1181 config RTC_DRV_NUC900
1182 tristate "NUC910/NUC920 RTC driver"
1183 depends on ARCH_W90X900 || COMPILE_TEST
1185 If you say yes here you get support for the RTC subsystem of the
1186 NUC910/NUC920 used in embedded systems.
1189 tristate "IBM OPAL RTC driver"
1190 depends on PPC_POWERNV
1193 If you say yes here you get support for the PowerNV platform RTC
1194 driver based on OPAL interfaces.
1196 This driver can also be built as a module. If so, the module
1197 will be called rtc-opal.
1199 config RTC_DRV_ZYNQMP
1200 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1203 If you say yes here you get support for the RTC controller found on
1204 Xilinx Zynq Ultrascale+ MPSoC.
1206 comment "on-CPU RTC drivers"
1208 config RTC_DRV_ASM9260
1209 tristate "Alphascale asm9260 RTC"
1210 depends on MACH_ASM9260 || COMPILE_TEST
1212 If you say yes here you get support for the RTC on the
1213 Alphascale asm9260 SoC.
1215 This driver can also be built as a module. If so, the module
1216 will be called rtc-asm9260.
1218 config RTC_DRV_DAVINCI
1219 tristate "TI DaVinci RTC"
1220 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1222 If you say yes here you get support for the RTC on the
1223 DaVinci platforms (DM365).
1225 This driver can also be built as a module. If so, the module
1226 will be called rtc-davinci.
1228 config RTC_DRV_DIGICOLOR
1229 tristate "Conexant Digicolor RTC"
1230 depends on ARCH_DIGICOLOR || COMPILE_TEST
1232 If you say yes here you get support for the RTC on Conexant
1233 Digicolor platforms. This currently includes the CX92755 SoC.
1235 This driver can also be built as a module. If so, the module
1236 will be called rtc-digicolor.
1238 config RTC_DRV_IMXDI
1239 tristate "Freescale IMX DryIce Real Time Clock"
1242 Support for Freescale IMX DryIce RTC
1244 This driver can also be built as a module, if so, the module
1245 will be called "rtc-imxdi".
1248 tristate "TI OMAP Real Time Clock"
1249 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1252 select GENERIC_PINCONF
1254 Say "yes" here to support the on chip real time clock
1255 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1257 This driver can also be built as a module, if so, module
1258 will be called rtc-omap.
1263 This will include RTC support for Samsung SoCs. If
1264 you want to include RTC support for any machine, kindly
1265 select this in the respective mach-XXXX/Kconfig file.
1268 tristate "Samsung S3C series SoC RTC"
1269 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1271 RTC (Realtime Clock) driver for the clock inbuilt into the
1272 Samsung S3C24XX series of SoCs. This can provide periodic
1273 interrupt rates from 1Hz to 64Hz for user programs, and
1276 The driver currently supports the common features on all the
1277 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1280 This driver can also be build as a module. If so, the module
1281 will be called rtc-s3c.
1283 config RTC_DRV_EP93XX
1284 tristate "Cirrus Logic EP93XX"
1285 depends on ARCH_EP93XX || COMPILE_TEST
1287 If you say yes here you get support for the
1288 RTC embedded in the Cirrus Logic EP93XX processors.
1290 This driver can also be built as a module. If so, the module
1291 will be called rtc-ep93xx.
1293 config RTC_DRV_SA1100
1294 tristate "SA11x0/PXA2xx/PXA910"
1295 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1297 If you say Y here you will get access to the real time clock
1298 built into your SA11x0 or PXA2xx CPU.
1300 To compile this driver as a module, choose M here: the
1301 module will be called rtc-sa1100.
1304 tristate "SuperH On-Chip RTC"
1305 depends on SUPERH && HAVE_CLK
1307 Say Y here to enable support for the on-chip RTC found in
1308 most SuperH processors.
1310 To compile this driver as a module, choose M here: the
1311 module will be called rtc-sh.
1313 config RTC_DRV_VR41XX
1314 tristate "NEC VR41XX"
1315 depends on CPU_VR41XX || COMPILE_TEST
1317 If you say Y here you will get access to the real time clock
1318 built into your NEC VR41XX CPU.
1320 To compile this driver as a module, choose M here: the
1321 module will be called rtc-vr41xx.
1323 config RTC_DRV_PL030
1324 tristate "ARM AMBA PL030 RTC"
1327 If you say Y here you will get access to ARM AMBA
1328 PrimeCell PL030 RTC found on certain ARM SOCs.
1330 To compile this driver as a module, choose M here: the
1331 module will be called rtc-pl030.
1333 config RTC_DRV_PL031
1334 tristate "ARM AMBA PL031 RTC"
1337 If you say Y here you will get access to ARM AMBA
1338 PrimeCell PL031 RTC found on certain ARM SOCs.
1340 To compile this driver as a module, choose M here: the
1341 module will be called rtc-pl031.
1343 config RTC_DRV_AT32AP700X
1344 tristate "AT32AP700X series RTC"
1345 depends on PLATFORM_AT32AP || COMPILE_TEST
1347 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1348 AT32AP700x family processors.
1350 config RTC_DRV_AT91RM9200
1351 tristate "AT91RM9200 or some AT91SAM9 RTC"
1352 depends on ARCH_AT91 || COMPILE_TEST
1354 Driver for the internal RTC (Realtime Clock) module found on
1355 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1356 this is powered by the backup power supply.
1358 config RTC_DRV_AT91SAM9
1359 tristate "AT91SAM9 RTT as RTC"
1360 depends on ARCH_AT91 || COMPILE_TEST
1363 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1364 can be used as an RTC thanks to the backup power supply (e.g. a
1365 small coin cell battery) which keeps this block and the GPBR
1366 (General Purpose Backup Registers) block powered when the device
1368 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1369 probably want to use the real RTC block instead of the "RTT as an
1372 config RTC_DRV_AU1XXX
1373 tristate "Au1xxx Counter0 RTC support"
1374 depends on MIPS_ALCHEMY
1376 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1377 counter) to be used as a RTC.
1379 This driver can also be built as a module. If so, the module
1380 will be called rtc-au1xxx.
1383 tristate "Blackfin On-Chip RTC"
1384 depends on BLACKFIN && !BF561
1386 If you say yes here you will get support for the
1387 Blackfin On-Chip Real Time Clock.
1389 This driver can also be built as a module. If so, the module
1390 will be called rtc-bfin.
1392 config RTC_DRV_RS5C313
1393 tristate "Ricoh RS5C313"
1394 depends on SH_LANDISK
1396 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1398 config RTC_DRV_GENERIC
1399 tristate "Generic RTC support"
1400 # Please consider writing a new RTC driver instead of using the generic
1402 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
1404 Say Y or M here to enable RTC support on systems using the generic
1405 RTC abstraction. If you do not know what you are doing, you should
1409 tristate "PXA27x/PXA3xx"
1411 select RTC_DRV_SA1100
1413 If you say Y here you will get access to the real time clock
1414 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1415 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1417 This RTC driver uses PXA RTC registers available since pxa27x
1418 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1420 config RTC_DRV_VT8500
1421 tristate "VIA/WonderMedia 85xx SoC RTC"
1422 depends on ARCH_VT8500 || COMPILE_TEST
1424 If you say Y here you will get access to the real time clock
1425 built into your VIA VT8500 SoC or its relatives.
1428 config RTC_DRV_SUN4V
1429 bool "SUN4V Hypervisor RTC"
1432 If you say Y here you will get support for the Hypervisor
1433 based RTC on SUN4V systems.
1435 config RTC_DRV_SUN6I
1436 bool "Allwinner A31 RTC"
1437 default MACH_SUN6I || MACH_SUN8I || COMPILE_TEST
1438 depends on ARCH_SUNXI
1440 If you say Y here you will get support for the RTC found in
1441 some Allwinner SoCs like the A31 or the A64.
1443 config RTC_DRV_SUNXI
1444 tristate "Allwinner sun4i/sun7i RTC"
1445 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1447 If you say Y here you will get support for the RTC found on
1450 config RTC_DRV_STARFIRE
1454 If you say Y here you will get support for the RTC found on
1457 config RTC_DRV_TX4939
1458 tristate "TX4939 SoC"
1459 depends on SOC_TX4939
1461 Driver for the internal RTC (Realtime Clock) module found on
1465 tristate "Marvell SoC RTC"
1466 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1468 If you say yes here you will get support for the in-chip RTC
1469 that can be found in some of Marvell's SoC devices, such as
1470 the Kirkwood 88F6281 and 88F6192.
1472 This driver can also be built as a module. If so, the module
1473 will be called rtc-mv.
1475 config RTC_DRV_ARMADA38X
1476 tristate "Armada 38x Marvell SoC RTC"
1477 depends on ARCH_MVEBU || COMPILE_TEST
1479 If you say yes here you will get support for the in-chip RTC
1480 that can be found in the Armada 38x Marvell's SoC device
1482 This driver can also be built as a module. If so, the module
1483 will be called armada38x-rtc.
1485 config RTC_DRV_GEMINI
1486 tristate "Gemini SoC RTC"
1487 depends on ARCH_GEMINI || COMPILE_TEST
1488 depends on HAS_IOMEM
1490 If you say Y here you will get support for the
1491 RTC found on Gemini SoC's.
1493 This driver can also be built as a module. If so, the module
1494 will be called rtc-gemini.
1500 If you say yes here you will get support for the RTC on PS3.
1502 This driver can also be built as a module. If so, the module
1503 will be called rtc-ps3.
1505 config RTC_DRV_COH901331
1506 tristate "ST-Ericsson COH 901 331 RTC"
1507 depends on ARCH_U300 || COMPILE_TEST
1509 If you say Y here you will get access to ST-Ericsson
1510 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1513 This driver can also be built as a module. If so, the module
1514 will be called "rtc-coh901331".
1518 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1519 depends on ARCH_MXS || COMPILE_TEST
1522 If you say yes here you will get support for the onboard
1523 STMP3xxx/i.MX23/i.MX28 RTC.
1525 This driver can also be built as a module. If so, the module
1526 will be called rtc-stmp3xxx.
1532 If you say Y here you will get support for the RTC found on
1533 the PCAP2 ASIC used on some Motorola phones.
1535 config RTC_DRV_MC13XXX
1536 depends on MFD_MC13XXX
1537 tristate "Freescale MC13xxx RTC"
1539 This enables support for the RTCs found on Freescale's PMICs
1540 MC13783 and MC13892.
1542 config RTC_DRV_MPC5121
1543 tristate "Freescale MPC5121 built-in RTC"
1544 depends on PPC_MPC512x || PPC_MPC52xx
1546 If you say yes here you will get support for the
1547 built-in RTC on MPC5121 or on MPC5200.
1549 This driver can also be built as a module. If so, the module
1550 will be called rtc-mpc5121.
1552 config RTC_DRV_JZ4740
1553 tristate "Ingenic JZ4740 SoC"
1554 depends on MACH_JZ4740 || COMPILE_TEST
1556 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1559 This driver can also be buillt as a module. If so, the module
1560 will be called rtc-jz4740.
1562 config RTC_DRV_LPC24XX
1563 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1564 depends on ARCH_LPC18XX || COMPILE_TEST
1565 depends on OF && HAS_IOMEM
1567 This enables support for the NXP RTC found which can be found on
1568 NXP LPC178x/18xx/408x/43xx devices.
1570 If you have one of the devices above enable this driver to use
1571 the hardware RTC. This driver can also be buillt as a module. If
1572 so, the module will be called rtc-lpc24xx.
1574 config RTC_DRV_LPC32XX
1575 depends on ARCH_LPC32XX || COMPILE_TEST
1576 tristate "NXP LPC32XX RTC"
1578 This enables support for the NXP RTC in the LPC32XX
1580 This driver can also be buillt as a module. If so, the module
1581 will be called rtc-lpc32xx.
1583 config RTC_DRV_PM8XXX
1584 tristate "Qualcomm PMIC8XXX RTC"
1585 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1587 If you say yes here you get support for the
1588 Qualcomm PMIC8XXX RTC.
1590 To compile this driver as a module, choose M here: the
1591 module will be called rtc-pm8xxx.
1593 config RTC_DRV_TEGRA
1594 tristate "NVIDIA Tegra Internal RTC driver"
1595 depends on ARCH_TEGRA || COMPILE_TEST
1597 If you say yes here you get support for the
1598 Tegra 200 series internal RTC module.
1600 This drive can also be built as a module. If so, the module
1601 will be called rtc-tegra.
1604 tristate "Tilera hypervisor RTC support"
1607 Enable support for the Linux driver side of the Tilera
1608 hypervisor's real-time clock interface.
1611 tristate "PKUnity v3 RTC support"
1612 depends on ARCH_PUV3
1614 This enables support for the RTC in the PKUnity-v3 SoCs.
1616 This drive can also be built as a module. If so, the module
1617 will be called rtc-puv3.
1619 config RTC_DRV_LOONGSON1
1620 tristate "loongson1 RTC support"
1621 depends on MACH_LOONGSON32
1623 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1624 counter) to be used as a RTC.
1626 This driver can also be built as a module. If so, the module
1627 will be called rtc-ls1x.
1630 tristate "Freescale MXC Real Time Clock"
1633 If you say yes here you get support for the Freescale MXC
1636 This driver can also be built as a module, if so, the module
1637 will be called "rtc-mxc".
1640 tristate "Freescale SNVS RTC support"
1642 depends on HAS_IOMEM
1645 If you say yes here you get support for the Freescale SNVS
1646 Low Power (LP) RTC module.
1648 This driver can also be built as a module, if so, the module
1649 will be called "rtc-snvs".
1651 config RTC_DRV_SIRFSOC
1652 tristate "SiRFSOC RTC"
1653 depends on ARCH_SIRF
1655 Say "yes" here to support the real time clock on SiRF SOC chips.
1656 This driver can also be built as a module called rtc-sirfsoc.
1658 config RTC_DRV_ST_LPC
1659 tristate "STMicroelectronics LPC RTC"
1663 Say Y here to include STMicroelectronics Low Power Controller
1664 (LPC) based RTC support.
1666 To compile this driver as a module, choose M here: the
1667 module will be called rtc-st-lpc.
1669 config RTC_DRV_MOXART
1670 tristate "MOXA ART RTC"
1671 depends on ARCH_MOXART || COMPILE_TEST
1673 If you say yes here you get support for the MOXA ART
1676 This driver can also be built as a module. If so, the module
1677 will be called rtc-moxart
1679 config RTC_DRV_MT6397
1680 tristate "Mediatek Real Time Clock driver"
1681 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1683 This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
1684 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1685 Mediatek(R) RTC driver.
1687 If you want to use Mediatek(R) RTC interface, select Y or M here.
1689 config RTC_DRV_XGENE
1690 tristate "APM X-Gene RTC"
1691 depends on HAS_IOMEM
1692 depends on ARCH_XGENE || COMPILE_TEST
1694 If you say yes here you get support for the APM X-Gene SoC real time
1697 This driver can also be built as a module, if so, the module
1698 will be called "rtc-xgene".
1700 config RTC_DRV_PIC32
1701 tristate "Microchip PIC32 RTC"
1702 depends on MACH_PIC32
1705 If you say yes here you get support for the PIC32 RTC module.
1707 This driver can also be built as a module. If so, the module
1708 will be called rtc-pic32
1710 comment "HID Sensor RTC drivers"
1712 config RTC_DRV_HID_SENSOR_TIME
1713 tristate "HID Sensor Time"
1716 select HID_SENSOR_HUB
1717 select HID_SENSOR_IIO_COMMON
1719 Say yes here to build support for the HID Sensors of type Time.
1720 This drivers makes such sensors available as RTCs.
1722 If this driver is compiled as a module, it will be named
1723 rtc-hid-sensor-time.