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.
81 bool "RTC non volatile storage support"
85 Say yes here to add support for the non volatile (often battery
86 backed) storage present on RTCs.
88 comment "RTC interfaces"
91 bool "/sys/class/rtc/rtcN (sysfs)"
95 Say yes here if you want to use your RTCs using sysfs interfaces,
96 /sys/class/rtc/rtc0 through /sys/.../rtcN.
101 bool "/proc/driver/rtc (procfs for rtcN)"
105 Say yes here if you want to use your system clock RTC through
106 the proc interface, /proc/driver/rtc.
107 Other RTCs will not be available through that API.
108 If there is no RTC for the system clock, then the first RTC(rtc0)
114 bool "/dev/rtcN (character devices)"
117 Say yes here if you want to use your RTCs using the /dev
118 interfaces, which "udev" sets up as /dev/rtc0 through
121 You may want to set up a symbolic link so one of these
122 can be accessed as /dev/rtc, which is a name
123 expected by "hwclock" and some other programs. Recent
124 versions of "udev" are known to set up the symlink for you.
128 config RTC_INTF_DEV_UIE_EMUL
129 bool "RTC UIE emulation on dev interface"
130 depends on RTC_INTF_DEV
132 Provides an emulation for RTC_UIE if the underlying rtc chip
133 driver does not expose RTC_UIE ioctls. Those requests generate
134 once-per-second update interrupts, used for synchronization.
136 The emulation code will read the time from the hardware
137 clock several times per second, please enable this option
138 only if you know that you really need it.
141 tristate "Test driver/device"
143 If you say yes here you get support for the
144 RTC test driver. It's a software RTC which can be
145 used to test the RTC subsystem APIs. It gets
146 the time from the system clock.
147 You want this driver only if you are doing development
148 on the RTC subsystem. Please read the source code
151 This driver can also be built as a module. If so, the module
152 will be called rtc-test.
154 comment "I2C RTC drivers"
158 config RTC_DRV_88PM860X
159 tristate "Marvell 88PM860x"
160 depends on MFD_88PM860X
162 If you say yes here you get support for RTC function in Marvell
165 This driver can also be built as a module. If so, the module
166 will be called rtc-88pm860x.
168 config RTC_DRV_88PM80X
169 tristate "Marvell 88PM80x"
170 depends on MFD_88PM800
172 If you say yes here you get support for RTC function in Marvell
175 This driver can also be built as a module. If so, the module
176 will be called rtc-88pm80x.
178 config RTC_DRV_ABB5ZES3
180 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
182 If you say yes here you get support for the Abracon
183 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
185 This driver can also be built as a module. If so, the module
186 will be called rtc-ab-b5ze-s3.
188 config RTC_DRV_ABX80X
189 tristate "Abracon ABx80x"
191 If you say yes here you get support for Abracon AB080X and AB180X
192 families of ultra-low-power battery- and capacitor-backed real-time
195 This driver can also be built as a module. If so, the module
196 will be called rtc-abx80x.
199 tristate "X-Powers AC100"
202 If you say yes here you get support for the real-time clock found
203 in X-Powers AC100 family peripheral ICs.
205 This driver can also be built as a module. If so, the module
206 will be called rtc-ac100.
208 config RTC_DRV_BRCMSTB
209 tristate "Broadcom STB wake-timer"
210 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
211 default ARCH_BRCMSTB || BMIPS_GENERIC
213 If you say yes here you get support for the wake-timer found on
214 Broadcom STB SoCs (BCM7xxx).
216 This driver can also be built as a module. If so, the module will
217 be called rtc-brcmstb-waketimer.
219 config RTC_DRV_AS3722
220 tristate "ams AS3722 RTC driver"
221 depends on MFD_AS3722
223 If you say yes here you get support for the RTC of ams AS3722 PMIC
226 This driver can also be built as a module. If so, the module
227 will be called rtc-as3722.
229 config RTC_DRV_DS1307
230 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"
232 If you say yes here you get support for various compatible RTC
233 chips (often with battery backup) connected with I2C. This driver
234 should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341,
235 ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.
236 In some cases the RTC must already have been initialized (by
237 manufacturing or a bootloader).
239 The first seven registers on these chips hold an RTC, and other
240 registers may add features such as NVRAM, a trickle charger for
241 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
242 sysfs, but other chip features may not be available.
244 This driver can also be built as a module. If so, the module
245 will be called rtc-ds1307.
247 config RTC_DRV_DS1307_HWMON
248 bool "HWMON support for rtc-ds1307"
249 depends on RTC_DRV_DS1307 && HWMON
250 depends on !(RTC_DRV_DS1307=y && HWMON=m)
253 Say Y here if you want to expose temperature sensor data on
254 rtc-ds1307 (only DS3231)
256 config RTC_DRV_DS1307_CENTURY
257 bool "Century bit support for rtc-ds1307"
258 depends on RTC_DRV_DS1307
261 The DS1307 driver suffered from a bug where it was enabling the
262 century bit inconditionnally but never used it when reading the time.
263 It made the driver unable to support dates beyond 2099.
264 Setting this option will add proper support for the century bit but if
265 the time was previously set using a kernel predating this option,
266 reading the date will return a date in the next century.
267 To solve that, you could boot a kernel without this option set, set
268 the RTC date and then boot a kernel with this option set.
270 config RTC_DRV_DS1374
271 tristate "Dallas/Maxim DS1374"
273 If you say yes here you get support for Dallas Semiconductor
274 DS1374 real-time clock chips. If an interrupt is associated
275 with the device, the alarm functionality is supported.
277 This driver can also be built as a module. If so, the module
278 will be called rtc-ds1374.
280 config RTC_DRV_DS1374_WDT
281 bool "Dallas/Maxim DS1374 watchdog timer"
282 depends on RTC_DRV_DS1374
284 If you say Y here you will get support for the
285 watchdog timer in the Dallas Semiconductor DS1374
286 real-time clock chips.
288 config RTC_DRV_DS1672
289 tristate "Dallas/Maxim DS1672"
291 If you say yes here you get support for the
292 Dallas/Maxim DS1672 timekeeping chip.
294 This driver can also be built as a module. If so, the module
295 will be called rtc-ds1672.
297 config RTC_DRV_HYM8563
298 tristate "Haoyu Microelectronics HYM8563"
301 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
302 from the usual rtc functions it provides a clock output of
305 This driver can also be built as a module. If so, the module
306 will be called rtc-hym8563.
308 config RTC_DRV_LP8788
309 tristate "TI LP8788 RTC driver"
310 depends on MFD_LP8788
312 Say Y to enable support for the LP8788 RTC/ALARM driver.
314 config RTC_DRV_MAX6900
315 tristate "Maxim MAX6900"
317 If you say yes here you will get support for the
318 Maxim MAX6900 I2C RTC chip.
320 This driver can also be built as a module. If so, the module
321 will be called rtc-max6900.
323 config RTC_DRV_MAX8907
324 tristate "Maxim MAX8907"
325 depends on MFD_MAX8907 || COMPILE_TEST
327 If you say yes here you will get support for the
328 RTC of Maxim MAX8907 PMIC.
330 This driver can also be built as a module. If so, the module
331 will be called rtc-max8907.
333 config RTC_DRV_MAX8925
334 tristate "Maxim MAX8925"
335 depends on MFD_MAX8925
337 If you say yes here you will get support for the
338 RTC of Maxim MAX8925 PMIC.
340 This driver can also be built as a module. If so, the module
341 will be called rtc-max8925.
343 config RTC_DRV_MAX8998
344 tristate "Maxim MAX8998"
345 depends on MFD_MAX8998
347 If you say yes here you will get support for the
348 RTC of Maxim MAX8998 PMIC.
350 This driver can also be built as a module. If so, the module
351 will be called rtc-max8998.
353 config RTC_DRV_MAX8997
354 tristate "Maxim MAX8997"
355 depends on MFD_MAX8997
357 If you say yes here you will get support for the
358 RTC of Maxim MAX8997 PMIC.
360 This driver can also be built as a module. If so, the module
361 will be called rtc-max8997.
363 config RTC_DRV_MAX77686
364 tristate "Maxim MAX77686"
365 depends on MFD_MAX77686 || MFD_MAX77620 || COMPILE_TEST
367 If you say yes here you will get support for the
368 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
370 This driver can also be built as a module. If so, the module
371 will be called rtc-max77686.
374 tristate "Rockchip RK805/RK808/RK818 RTC"
377 If you say yes here you will get support for the
378 RTC of RK805, RK808 and RK818 PMIC.
380 This driver can also be built as a module. If so, the module
381 will be called rk808-rtc.
383 config RTC_DRV_RS5C372
384 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
386 If you say yes here you get support for the
387 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
389 This driver can also be built as a module. If so, the module
390 will be called rtc-rs5c372.
392 config RTC_DRV_ISL1208
393 tristate "Intersil ISL1208"
395 If you say yes here you get support for the
396 Intersil ISL1208 RTC chip.
398 This driver can also be built as a module. If so, the module
399 will be called rtc-isl1208.
401 config RTC_DRV_ISL12022
402 tristate "Intersil ISL12022"
404 If you say yes here you get support for the
405 Intersil ISL12022 RTC chip.
407 This driver can also be built as a module. If so, the module
408 will be called rtc-isl12022.
411 tristate "Xicor/Intersil X1205"
413 If you say yes here you get support for the
414 Xicor/Intersil X1205 RTC chip.
416 This driver can also be built as a module. If so, the module
417 will be called rtc-x1205.
419 config RTC_DRV_PCF8523
420 tristate "NXP PCF8523"
422 If you say yes here you get support for the NXP PCF8523 RTC
425 This driver can also be built as a module. If so, the module
426 will be called rtc-pcf8523.
428 config RTC_DRV_PCF85063
429 tristate "NXP PCF85063"
431 If you say yes here you get support for the PCF85063 RTC chip
433 This driver can also be built as a module. If so, the module
434 will be called rtc-pcf85063.
436 config RTC_DRV_PCF8563
437 tristate "Philips PCF8563/Epson RTC8564"
439 If you say yes here you get support for the
440 Philips PCF8563 RTC chip. The Epson RTC8564
443 This driver can also be built as a module. If so, the module
444 will be called rtc-pcf8563.
446 config RTC_DRV_PCF8583
447 tristate "Philips PCF8583"
449 If you say yes here you get support for the Philips PCF8583
450 RTC chip found on Acorn RiscPCs. This driver supports the
451 platform specific method of retrieving the current year from
452 the RTC's SRAM. It will work on other platforms with the same
453 chip, but the year will probably have to be tweaked.
455 This driver can also be built as a module. If so, the module
456 will be called rtc-pcf8583.
458 config RTC_DRV_M41T80
459 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
461 If you say Y here you will get support for the ST M41T60
462 and M41T80 RTC chips series. Currently, the following chips are
463 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
464 M41ST85, M41ST87, and MicroCrystal RV4162.
466 This driver can also be built as a module. If so, the module
467 will be called rtc-m41t80.
469 config RTC_DRV_M41T80_WDT
470 bool "ST M41T65/M41T80 series RTC watchdog timer"
471 depends on RTC_DRV_M41T80
473 If you say Y here you will get support for the
474 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
477 tristate "TI BQ32000"
479 If you say Y here you will get support for the TI
480 BQ32000 I2C RTC chip.
482 This driver can also be built as a module. If so, the module
483 will be called rtc-bq32k.
485 config RTC_DRV_DM355EVM
486 tristate "TI DaVinci DM355 EVM RTC"
487 depends on MFD_DM355EVM_MSP
489 Supports the RTC firmware in the MSP430 on the DM355 EVM.
491 config RTC_DRV_TWL92330
492 bool "TI TWL92330/Menelaus"
495 If you say yes here you get support for the RTC on the
496 TWL92330 "Menelaus" power management chip, used with OMAP2
497 platforms. The support is integrated with the rest of
498 the Menelaus driver; it's not separate module.
500 config RTC_DRV_TWL4030
501 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
502 depends on TWL4030_CORE
505 If you say yes here you get support for the RTC on the
506 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
508 This driver can also be built as a module. If so, the module
509 will be called rtc-twl.
511 config RTC_DRV_PALMAS
512 tristate "TI Palmas RTC driver"
513 depends on MFD_PALMAS
515 If you say yes here you get support for the RTC of TI PALMA series PMIC
518 This driver can also be built as a module. If so, the module
519 will be called rtc-palma.
521 config RTC_DRV_TPS6586X
522 tristate "TI TPS6586X RTC driver"
523 depends on MFD_TPS6586X
525 TI Power Management IC TPS6586X supports RTC functionality
526 along with alarm. This driver supports the RTC driver for
527 the TPS6586X RTC module.
529 config RTC_DRV_TPS65910
530 tristate "TI TPS65910 RTC driver"
531 depends on RTC_CLASS && MFD_TPS65910
533 If you say yes here you get support for the RTC on the
536 This driver can also be built as a module. If so, the module
537 will be called rtc-tps65910.
539 config RTC_DRV_TPS80031
540 tristate "TI TPS80031/TPS80032 RTC driver"
541 depends on MFD_TPS80031
543 TI Power Management IC TPS80031 supports RTC functionality
544 along with alarm. This driver supports the RTC driver for
545 the TPS80031 RTC module.
547 config RTC_DRV_RC5T583
548 tristate "RICOH 5T583 RTC driver"
549 depends on MFD_RC5T583
551 If you say yes here you get support for the RTC on the
554 This driver can also be built as a module. If so, the module
555 will be called rtc-rc5t583.
557 config RTC_DRV_S35390A
558 tristate "Seiko Instruments S-35390A"
561 If you say yes here you will get support for the Seiko
562 Instruments S-35390A.
564 This driver can also be built as a module. If so the module
565 will be called rtc-s35390a.
567 config RTC_DRV_FM3130
568 tristate "Ramtron FM3130"
570 If you say Y here you will get support for the
571 Ramtron FM3130 RTC chips.
572 Ramtron FM3130 is a chip with two separate devices inside,
573 RTC clock and FRAM. This driver provides only RTC functionality.
575 This driver can also be built as a module. If so the module
576 will be called rtc-fm3130.
578 config RTC_DRV_RX8010
579 tristate "Epson RX8010SJ"
582 If you say yes here you get support for the Epson RX8010SJ RTC
585 This driver can also be built as a module. If so, the module
586 will be called rtc-rx8010.
588 config RTC_DRV_RX8581
589 tristate "Epson RX-8581"
591 If you say yes here you will get support for the Epson RX-8581.
593 This driver can also be built as a module. If so the module
594 will be called rtc-rx8581.
596 config RTC_DRV_RX8025
597 tristate "Epson RX-8025SA/NB"
599 If you say yes here you get support for the Epson
600 RX-8025SA/NB RTC chips.
602 This driver can also be built as a module. If so, the module
603 will be called rtc-rx8025.
605 config RTC_DRV_EM3027
606 tristate "EM Microelectronic EM3027"
608 If you say yes here you get support for the EM
609 Microelectronic EM3027 RTC chips.
611 This driver can also be built as a module. If so, the module
612 will be called rtc-em3027.
614 config RTC_DRV_RV8803
615 tristate "Micro Crystal RV8803, Epson RX8900"
617 If you say yes here you get support for the Micro Crystal RV8803 and
618 Epson RX8900 RTC chips.
620 This driver can also be built as a module. If so, the module
621 will be called rtc-rv8803.
624 tristate "Samsung S2M/S5M series"
625 depends on MFD_SEC_CORE || COMPILE_TEST
628 If you say yes here you will get support for the
629 RTC of Samsung S2MPS14 and S5M PMIC series.
631 This driver can also be built as a module. If so, the module
632 will be called rtc-s5m.
636 comment "SPI RTC drivers"
640 config RTC_DRV_M41T93
643 If you say yes here you will get support for the
644 ST M41T93 SPI RTC chip.
646 This driver can also be built as a module. If so, the module
647 will be called rtc-m41t93.
649 config RTC_DRV_M41T94
652 If you say yes here you will get support for the
653 ST M41T94 SPI RTC chip.
655 This driver can also be built as a module. If so, the module
656 will be called rtc-m41t94.
658 config RTC_DRV_DS1302
659 tristate "Dallas/Maxim DS1302"
662 If you say yes here you get support for the Dallas DS1302 RTC chips.
664 This driver can also be built as a module. If so, the module
665 will be called rtc-ds1302.
667 config RTC_DRV_DS1305
668 tristate "Dallas/Maxim DS1305/DS1306"
670 Select this driver to get support for the Dallas/Maxim DS1305
671 and DS1306 real time clock chips. These support a trickle
672 charger, alarms, and NVRAM in addition to the clock.
674 This driver can also be built as a module. If so, the module
675 will be called rtc-ds1305.
677 config RTC_DRV_DS1343
679 tristate "Dallas/Maxim DS1343/DS1344"
681 If you say yes here you get support for the
682 Dallas/Maxim DS1343 and DS1344 real time clock chips.
683 Support for trickle charger, alarm is provided.
685 This driver can also be built as a module. If so, the module
686 will be called rtc-ds1343.
688 config RTC_DRV_DS1347
690 tristate "Dallas/Maxim DS1347"
692 If you say yes here you get support for the
693 Dallas/Maxim DS1347 chips.
695 This driver only supports the RTC feature, and not other chip
696 features such as alarms.
698 This driver can also be built as a module. If so, the module
699 will be called rtc-ds1347.
701 config RTC_DRV_DS1390
702 tristate "Dallas/Maxim DS1390/93/94"
704 If you say yes here you get support for the
705 Dallas/Maxim DS1390/93/94 chips.
707 This driver supports the RTC feature and trickle charging but not
708 other chip features such as alarms.
710 This driver can also be built as a module. If so, the module
711 will be called rtc-ds1390.
713 config RTC_DRV_MAX6916
714 tristate "Maxim MAX6916"
716 If you say yes here you will get support for the
717 Maxim MAX6916 SPI RTC chip.
719 This driver only supports the RTC feature, and not other chip
720 features such as alarms.
722 This driver can also be built as a module. If so, the module
723 will be called rtc-max6916.
726 tristate "Epson RTC-9701JE"
728 If you say yes here you will get support for the
729 Epson RTC-9701JE SPI RTC chip.
731 This driver can also be built as a module. If so, the module
732 will be called rtc-r9701.
734 config RTC_DRV_RX4581
735 tristate "Epson RX-4581"
737 If you say yes here you will get support for the Epson RX-4581.
739 This driver can also be built as a module. If so the module
740 will be called rtc-rx4581.
742 config RTC_DRV_RX6110
743 tristate "Epson RX-6110"
746 If you say yes here you will get support for the Epson RX-6610.
748 This driver can also be built as a module. If so the module
749 will be called rtc-rx6110.
751 config RTC_DRV_RS5C348
752 tristate "Ricoh RS5C348A/B"
754 If you say yes here you get support for the
755 Ricoh RS5C348A and RS5C348B RTC chips.
757 This driver can also be built as a module. If so, the module
758 will be called rtc-rs5c348.
760 config RTC_DRV_MAX6902
761 tristate "Maxim MAX6902"
763 If you say yes here you will get support for the
764 Maxim MAX6902 SPI RTC chip.
766 This driver can also be built as a module. If so, the module
767 will be called rtc-max6902.
769 config RTC_DRV_PCF2123
770 tristate "NXP PCF2123"
772 If you say yes here you get support for the NXP PCF2123
775 This driver can also be built as a module. If so, the module
776 will be called rtc-pcf2123.
778 config RTC_DRV_MCP795
779 tristate "Microchip MCP795"
781 If you say yes here you will get support for the Microchip MCP795.
783 This driver can also be built as a module. If so the module
784 will be called rtc-mcp795.
789 # Helper to resolve issues with configs that have SPI enabled but I2C
790 # modular. See SND_SOC_I2C_AND_SPI for more information
792 config RTC_I2C_AND_SPI
796 default y if SPI_MASTER=y
797 select REGMAP_I2C if I2C
798 select REGMAP_SPI if SPI_MASTER
800 comment "SPI and I2C RTC drivers"
802 config RTC_DRV_DS3232
803 tristate "Dallas/Maxim DS3232/DS3234"
804 depends on RTC_I2C_AND_SPI
806 If you say yes here you get support for Dallas Semiconductor
807 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
808 with the device, the alarm functionality is supported.
810 This driver can also be built as a module. If so, the module
811 will be called rtc-ds3232.
813 config RTC_DRV_DS3232_HWMON
814 bool "HWMON support for Dallas/Maxim DS3232/DS3234"
815 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
818 Say Y here if you want to expose temperature sensor data on
821 config RTC_DRV_PCF2127
822 tristate "NXP PCF2127"
823 depends on RTC_I2C_AND_SPI
825 If you say yes here you get support for the NXP PCF2127/29 RTC
828 This driver can also be built as a module. If so, the module
829 will be called rtc-pcf2127.
831 config RTC_DRV_RV3029C2
832 tristate "Micro Crystal RV3029/3049"
833 depends on RTC_I2C_AND_SPI
835 If you say yes here you get support for the Micro Crystal
836 RV3029 and RV3049 RTC chips.
838 This driver can also be built as a module. If so, the module
839 will be called rtc-rv3029c2.
841 config RTC_DRV_RV3029_HWMON
842 bool "HWMON support for RV3029/3049"
843 depends on RTC_DRV_RV3029C2 && HWMON
844 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
847 Say Y here if you want to expose temperature sensor data on
850 comment "Platform RTC drivers"
852 # this 'CMOS' RTC driver is arch dependent because it requires
853 # <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
854 # global rtc_lock ... it's not yet just another platform_device.
857 tristate "PC-style 'CMOS'"
858 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64 || MN10300
860 select RTC_MC146818_LIB
862 Say "yes" here to get direct support for the real time clock
863 found in every PC or ACPI-based system, and some other boards.
864 Specifically the original MC146818, compatibles like those in
865 PC south bridges, the DS12887 or M48T86, some multifunction
866 or LPC bus chips, and so on.
868 Your system will need to define the platform device used by
869 this driver, otherwise it won't be accessible. This means
870 you can safely enable this driver if you don't know whether
871 or not your board has this kind of hardware.
873 This driver can also be built as a module. If so, the module
874 will be called rtc-cmos.
877 bool "Alpha PC-style CMOS"
879 select RTC_MC146818_LIB
882 Direct support for the real-time clock found on every Alpha
883 system, specifically MC146818 compatibles. If in doubt, say Y.
886 tristate "Virtual RTC for Intel MID platforms"
887 depends on X86_INTEL_MID
888 default y if X86_INTEL_MID
891 Say "yes" here to get direct support for the real time clock
892 found on Moorestown platforms. The VRTC is a emulated RTC that
893 derives its clock source from a real RTC in the PMIC. The MC146818
894 style programming interface is mostly conserved, but any
895 updates are done via IPC calls to the system controller FW.
897 config RTC_DRV_DS1216
898 tristate "Dallas DS1216"
901 If you say yes here you get support for the Dallas DS1216 RTC chips.
903 config RTC_DRV_DS1286
904 tristate "Dallas DS1286"
907 If you say yes here you get support for the Dallas DS1286 RTC chips.
909 config RTC_DRV_DS1511
910 tristate "Dallas DS1511"
913 If you say yes here you get support for the
914 Dallas DS1511 timekeeping/watchdog chip.
916 This driver can also be built as a module. If so, the module
917 will be called rtc-ds1511.
919 config RTC_DRV_DS1553
920 tristate "Maxim/Dallas DS1553"
923 If you say yes here you get support for the
924 Maxim/Dallas DS1553 timekeeping chip.
926 This driver can also be built as a module. If so, the module
927 will be called rtc-ds1553.
929 config RTC_DRV_DS1685_FAMILY
930 tristate "Dallas/Maxim DS1685 Family"
932 If you say yes here you get support for the Dallas/Maxim DS1685
933 family of real time chips. This family includes the DS1685/DS1687,
934 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
935 DS17885/DS17887 chips.
937 This driver can also be built as a module. If so, the module
938 will be called rtc-ds1685.
942 depends on RTC_DRV_DS1685_FAMILY
943 default RTC_DRV_DS1685
945 config RTC_DRV_DS1685
948 This enables support for the Dallas/Maxim DS1685/DS1687 real time
951 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
952 systems, as well as EPPC-405-UC modules by electronic system design
955 config RTC_DRV_DS1689
958 This enables support for the Dallas/Maxim DS1689/DS1693 real time
961 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
962 which supports a few minor features such as Vcc, Vbat, and Power
963 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
965 It also works for the even older DS1688/DS1691 RTC chips, which are
966 virtually the same and carry the same model number. Both chips
967 have 114 bytes of user NVRAM.
969 config RTC_DRV_DS17285
970 bool "DS17285/DS17287"
972 This enables support for the Dallas/Maxim DS17285/DS17287 real time
975 This chip features 2kb of extended NV-SRAM. It may possibly be
976 found in some SGI O2 systems (rare).
978 config RTC_DRV_DS17485
979 bool "DS17485/DS17487"
981 This enables support for the Dallas/Maxim DS17485/DS17487 real time
984 This chip features 4kb of extended NV-SRAM.
986 config RTC_DRV_DS17885
987 bool "DS17885/DS17887"
989 This enables support for the Dallas/Maxim DS17885/DS17887 real time
992 This chip features 8kb of extended NV-SRAM.
996 config RTC_DS1685_PROC_REGS
997 bool "Display register values in /proc"
998 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
1000 Enable this to display a readout of all of the RTC registers in
1001 /proc/drivers/rtc. Keep in mind that this can potentially lead
1002 to lost interrupts, as reading Control Register C will clear
1003 all pending IRQ flags.
1005 Unless you are debugging this driver, choose N.
1007 config RTC_DS1685_SYSFS_REGS
1008 bool "SysFS access to RTC register bits"
1009 depends on RTC_DRV_DS1685_FAMILY && SYSFS
1011 Enable this to provide access to the RTC control register bits
1012 in /sys. Some of the bits are read-write, others are read-only.
1014 Keep in mind that reading Control C's bits automatically clears
1015 all pending IRQ flags - this can cause lost interrupts.
1017 If you know that you need access to these bits, choose Y, Else N.
1019 config RTC_DRV_DS1742
1020 tristate "Maxim/Dallas DS1742/1743"
1021 depends on HAS_IOMEM
1023 If you say yes here you get support for the
1024 Maxim/Dallas DS1742/1743 timekeeping chip.
1026 This driver can also be built as a module. If so, the module
1027 will be called rtc-ds1742.
1029 config RTC_DRV_DS2404
1030 tristate "Maxim/Dallas DS2404"
1032 If you say yes here you get support for the
1033 Dallas DS2404 RTC chip.
1035 This driver can also be built as a module. If so, the module
1036 will be called rtc-ds2404.
1038 config RTC_DRV_DA9052
1039 tristate "Dialog DA9052/DA9053 RTC"
1040 depends on PMIC_DA9052
1042 Say y here to support the RTC driver for Dialog Semiconductor
1043 DA9052-BC and DA9053-AA/Bx PMICs.
1045 config RTC_DRV_DA9055
1046 tristate "Dialog Semiconductor DA9055 RTC"
1047 depends on MFD_DA9055
1049 If you say yes here you will get support for the
1050 RTC of the Dialog DA9055 PMIC.
1052 This driver can also be built as a module. If so, the module
1053 will be called rtc-da9055
1055 config RTC_DRV_DA9063
1056 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1057 depends on MFD_DA9063 || MFD_DA9062
1059 If you say yes here you will get support for the RTC subsystem
1060 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1062 This driver can also be built as a module. If so, the module
1063 will be called "rtc-da9063".
1067 depends on EFI && !X86
1069 If you say yes here you will get support for the EFI
1072 This driver can also be built as a module. If so, the module
1073 will be called rtc-efi.
1075 config RTC_DRV_STK17TA8
1076 tristate "Simtek STK17TA8"
1077 depends on HAS_IOMEM
1079 If you say yes here you get support for the
1080 Simtek STK17TA8 timekeeping chip.
1082 This driver can also be built as a module. If so, the module
1083 will be called rtc-stk17ta8.
1085 config RTC_DRV_M48T86
1086 tristate "ST M48T86/Dallas DS12887"
1088 If you say Y here you will get support for the
1089 ST M48T86 and Dallas DS12887 RTC chips.
1091 This driver can also be built as a module. If so, the module
1092 will be called rtc-m48t86.
1094 config RTC_DRV_M48T35
1095 tristate "ST M48T35"
1096 depends on HAS_IOMEM
1098 If you say Y here you will get support for the
1101 This driver can also be built as a module, if so, the module
1102 will be called "rtc-m48t35".
1104 config RTC_DRV_M48T59
1105 tristate "ST M48T59/M48T08/M48T02"
1106 depends on HAS_IOMEM
1108 If you say Y here you will get support for the
1109 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1111 These chips are usually found in Sun SPARC and UltraSPARC
1114 This driver can also be built as a module, if so, the module
1115 will be called "rtc-m48t59".
1117 config RTC_DRV_MSM6242
1118 tristate "Oki MSM6242"
1119 depends on HAS_IOMEM
1121 If you say yes here you get support for the Oki MSM6242
1122 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1124 This driver can also be built as a module. If so, the module
1125 will be called rtc-msm6242.
1127 config RTC_DRV_BQ4802
1128 tristate "TI BQ4802"
1129 depends on HAS_IOMEM
1131 If you say Y here you will get support for the TI
1134 This driver can also be built as a module. If so, the module
1135 will be called rtc-bq4802.
1137 config RTC_DRV_RP5C01
1138 tristate "Ricoh RP5C01"
1139 depends on HAS_IOMEM
1141 If you say yes here you get support for the Ricoh RP5C01
1142 timekeeping chip. It is used in some Amiga models (e.g. A3000
1145 This driver can also be built as a module. If so, the module
1146 will be called rtc-rp5c01.
1148 config RTC_DRV_V3020
1149 tristate "EM Microelectronic V3020"
1151 If you say yes here you will get support for the
1152 EM Microelectronic v3020 RTC chip.
1154 This driver can also be built as a module. If so, the module
1155 will be called rtc-v3020.
1157 config RTC_DRV_WM831X
1158 tristate "Wolfson Microelectronics WM831x RTC"
1159 depends on MFD_WM831X
1161 If you say yes here you will get support for the RTC subsystem
1162 of the Wolfson Microelectronics WM831X series PMICs.
1164 This driver can also be built as a module. If so, the module
1165 will be called "rtc-wm831x".
1167 config RTC_DRV_WM8350
1168 tristate "Wolfson Microelectronics WM8350 RTC"
1169 depends on MFD_WM8350
1171 If you say yes here you will get support for the RTC subsystem
1172 of the Wolfson Microelectronics WM8350.
1174 This driver can also be built as a module. If so, the module
1175 will be called "rtc-wm8350".
1177 config RTC_DRV_SPEAR
1178 tristate "SPEAR ST RTC"
1179 depends on PLAT_SPEAR || COMPILE_TEST
1182 If you say Y here you will get support for the RTC found on
1185 config RTC_DRV_PCF50633
1186 depends on MFD_PCF50633
1187 tristate "NXP PCF50633 RTC"
1189 If you say yes here you get support for the RTC subsystem of the
1190 NXP PCF50633 used in embedded systems.
1192 config RTC_DRV_AB3100
1193 tristate "ST-Ericsson AB3100 RTC"
1194 depends on AB3100_CORE
1195 default y if AB3100_CORE
1197 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1198 support. This chip contains a battery- and capacitor-backed RTC.
1200 config RTC_DRV_AB8500
1201 tristate "ST-Ericsson AB8500 RTC"
1202 depends on AB8500_CORE
1204 select RTC_INTF_DEV_UIE_EMUL
1206 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1207 support. This chip contains a battery- and capacitor-backed RTC.
1209 config RTC_DRV_NUC900
1210 tristate "NUC910/NUC920 RTC driver"
1211 depends on ARCH_W90X900 || COMPILE_TEST
1213 If you say yes here you get support for the RTC subsystem of the
1214 NUC910/NUC920 used in embedded systems.
1217 tristate "IBM OPAL RTC driver"
1218 depends on PPC_POWERNV
1221 If you say yes here you get support for the PowerNV platform RTC
1222 driver based on OPAL interfaces.
1224 This driver can also be built as a module. If so, the module
1225 will be called rtc-opal.
1227 config RTC_DRV_ZYNQMP
1228 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1231 If you say yes here you get support for the RTC controller found on
1232 Xilinx Zynq Ultrascale+ MPSoC.
1234 comment "on-CPU RTC drivers"
1236 config RTC_DRV_ASM9260
1237 tristate "Alphascale asm9260 RTC"
1238 depends on MACH_ASM9260 || COMPILE_TEST
1240 If you say yes here you get support for the RTC on the
1241 Alphascale asm9260 SoC.
1243 This driver can also be built as a module. If so, the module
1244 will be called rtc-asm9260.
1246 config RTC_DRV_DAVINCI
1247 tristate "TI DaVinci RTC"
1248 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1250 If you say yes here you get support for the RTC on the
1251 DaVinci platforms (DM365).
1253 This driver can also be built as a module. If so, the module
1254 will be called rtc-davinci.
1256 config RTC_DRV_DIGICOLOR
1257 tristate "Conexant Digicolor RTC"
1258 depends on ARCH_DIGICOLOR || COMPILE_TEST
1260 If you say yes here you get support for the RTC on Conexant
1261 Digicolor platforms. This currently includes the CX92755 SoC.
1263 This driver can also be built as a module. If so, the module
1264 will be called rtc-digicolor.
1266 config RTC_DRV_IMXDI
1267 tristate "Freescale IMX DryIce Real Time Clock"
1270 Support for Freescale IMX DryIce RTC
1272 This driver can also be built as a module, if so, the module
1273 will be called "rtc-imxdi".
1276 tristate "TI OMAP Real Time Clock"
1277 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1280 select GENERIC_PINCONF
1282 Say "yes" here to support the on chip real time clock
1283 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1285 This driver can also be built as a module, if so, module
1286 will be called rtc-omap.
1291 This will include RTC support for Samsung SoCs. If
1292 you want to include RTC support for any machine, kindly
1293 select this in the respective mach-XXXX/Kconfig file.
1296 tristate "Samsung S3C series SoC RTC"
1297 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1299 RTC (Realtime Clock) driver for the clock inbuilt into the
1300 Samsung S3C24XX series of SoCs. This can provide periodic
1301 interrupt rates from 1Hz to 64Hz for user programs, and
1304 The driver currently supports the common features on all the
1305 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1308 This driver can also be build as a module. If so, the module
1309 will be called rtc-s3c.
1311 config RTC_DRV_EP93XX
1312 tristate "Cirrus Logic EP93XX"
1313 depends on ARCH_EP93XX || COMPILE_TEST
1315 If you say yes here you get support for the
1316 RTC embedded in the Cirrus Logic EP93XX processors.
1318 This driver can also be built as a module. If so, the module
1319 will be called rtc-ep93xx.
1321 config RTC_DRV_SA1100
1322 tristate "SA11x0/PXA2xx/PXA910"
1323 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1325 If you say Y here you will get access to the real time clock
1326 built into your SA11x0 or PXA2xx CPU.
1328 To compile this driver as a module, choose M here: the
1329 module will be called rtc-sa1100.
1332 tristate "SuperH On-Chip RTC"
1333 depends on SUPERH || ARCH_RENESAS
1335 Say Y here to enable support for the on-chip RTC found in
1336 most SuperH processors. This RTC is also found in RZ/A SoCs.
1338 To compile this driver as a module, choose M here: the
1339 module will be called rtc-sh.
1341 config RTC_DRV_VR41XX
1342 tristate "NEC VR41XX"
1343 depends on CPU_VR41XX || COMPILE_TEST
1345 If you say Y here you will get access to the real time clock
1346 built into your NEC VR41XX CPU.
1348 To compile this driver as a module, choose M here: the
1349 module will be called rtc-vr41xx.
1351 config RTC_DRV_PL030
1352 tristate "ARM AMBA PL030 RTC"
1355 If you say Y here you will get access to ARM AMBA
1356 PrimeCell PL030 RTC found on certain ARM SOCs.
1358 To compile this driver as a module, choose M here: the
1359 module will be called rtc-pl030.
1361 config RTC_DRV_PL031
1362 tristate "ARM AMBA PL031 RTC"
1365 If you say Y here you will get access to ARM AMBA
1366 PrimeCell PL031 RTC found on certain ARM SOCs.
1368 To compile this driver as a module, choose M here: the
1369 module will be called rtc-pl031.
1371 config RTC_DRV_AT32AP700X
1372 tristate "AT32AP700X series RTC"
1373 depends on PLATFORM_AT32AP || COMPILE_TEST
1375 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1376 AT32AP700x family processors.
1378 config RTC_DRV_AT91RM9200
1379 tristate "AT91RM9200 or some AT91SAM9 RTC"
1380 depends on ARCH_AT91 || COMPILE_TEST
1382 Driver for the internal RTC (Realtime Clock) module found on
1383 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1384 this is powered by the backup power supply.
1386 config RTC_DRV_AT91SAM9
1387 tristate "AT91SAM9 RTT as RTC"
1388 depends on ARCH_AT91 || COMPILE_TEST
1391 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1392 can be used as an RTC thanks to the backup power supply (e.g. a
1393 small coin cell battery) which keeps this block and the GPBR
1394 (General Purpose Backup Registers) block powered when the device
1396 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1397 probably want to use the real RTC block instead of the "RTT as an
1400 config RTC_DRV_AU1XXX
1401 tristate "Au1xxx Counter0 RTC support"
1402 depends on MIPS_ALCHEMY
1404 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1405 counter) to be used as a RTC.
1407 This driver can also be built as a module. If so, the module
1408 will be called rtc-au1xxx.
1411 tristate "Blackfin On-Chip RTC"
1412 depends on BLACKFIN && !BF561
1414 If you say yes here you will get support for the
1415 Blackfin On-Chip Real Time Clock.
1417 This driver can also be built as a module. If so, the module
1418 will be called rtc-bfin.
1420 config RTC_DRV_RS5C313
1421 tristate "Ricoh RS5C313"
1422 depends on SH_LANDISK
1424 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1426 config RTC_DRV_GENERIC
1427 tristate "Generic RTC support"
1428 # Please consider writing a new RTC driver instead of using the generic
1430 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
1432 Say Y or M here to enable RTC support on systems using the generic
1433 RTC abstraction. If you do not know what you are doing, you should
1437 tristate "PXA27x/PXA3xx"
1439 select RTC_DRV_SA1100
1441 If you say Y here you will get access to the real time clock
1442 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1443 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1445 This RTC driver uses PXA RTC registers available since pxa27x
1446 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1448 config RTC_DRV_VT8500
1449 tristate "VIA/WonderMedia 85xx SoC RTC"
1450 depends on ARCH_VT8500 || COMPILE_TEST
1452 If you say Y here you will get access to the real time clock
1453 built into your VIA VT8500 SoC or its relatives.
1456 config RTC_DRV_SUN4V
1457 bool "SUN4V Hypervisor RTC"
1460 If you say Y here you will get support for the Hypervisor
1461 based RTC on SUN4V systems.
1463 config RTC_DRV_SUN6I
1464 bool "Allwinner A31 RTC"
1465 default MACH_SUN6I || MACH_SUN8I
1466 depends on COMMON_CLK
1467 depends on ARCH_SUNXI || COMPILE_TEST
1469 If you say Y here you will get support for the RTC found in
1470 some Allwinner SoCs like the A31 or the A64.
1472 config RTC_DRV_SUNXI
1473 tristate "Allwinner sun4i/sun7i RTC"
1474 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1476 If you say Y here you will get support for the RTC found on
1479 config RTC_DRV_STARFIRE
1483 If you say Y here you will get support for the RTC found on
1486 config RTC_DRV_TX4939
1487 tristate "TX4939 SoC"
1488 depends on SOC_TX4939
1490 Driver for the internal RTC (Realtime Clock) module found on
1494 tristate "Marvell SoC RTC"
1495 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1497 If you say yes here you will get support for the in-chip RTC
1498 that can be found in some of Marvell's SoC devices, such as
1499 the Kirkwood 88F6281 and 88F6192.
1501 This driver can also be built as a module. If so, the module
1502 will be called rtc-mv.
1504 config RTC_DRV_ARMADA38X
1505 tristate "Armada 38x Marvell SoC RTC"
1506 depends on ARCH_MVEBU || COMPILE_TEST
1508 If you say yes here you will get support for the in-chip RTC
1509 that can be found in the Armada 38x Marvell's SoC device
1511 This driver can also be built as a module. If so, the module
1512 will be called armada38x-rtc.
1514 config RTC_DRV_FTRTC010
1515 tristate "Faraday Technology FTRTC010 RTC"
1516 depends on HAS_IOMEM
1519 If you say Y here you will get support for the
1520 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1522 This driver can also be built as a module. If so, the module
1523 will be called rtc-ftrtc010.
1529 If you say yes here you will get support for the RTC on PS3.
1531 This driver can also be built as a module. If so, the module
1532 will be called rtc-ps3.
1534 config RTC_DRV_COH901331
1535 tristate "ST-Ericsson COH 901 331 RTC"
1536 depends on ARCH_U300 || COMPILE_TEST
1538 If you say Y here you will get access to ST-Ericsson
1539 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1542 This driver can also be built as a module. If so, the module
1543 will be called "rtc-coh901331".
1547 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1548 depends on ARCH_MXS || COMPILE_TEST
1551 If you say yes here you will get support for the onboard
1552 STMP3xxx/i.MX23/i.MX28 RTC.
1554 This driver can also be built as a module. If so, the module
1555 will be called rtc-stmp3xxx.
1561 If you say Y here you will get support for the RTC found on
1562 the PCAP2 ASIC used on some Motorola phones.
1564 config RTC_DRV_MC13XXX
1565 depends on MFD_MC13XXX
1566 tristate "Freescale MC13xxx RTC"
1568 This enables support for the RTCs found on Freescale's PMICs
1569 MC13783 and MC13892.
1571 config RTC_DRV_MPC5121
1572 tristate "Freescale MPC5121 built-in RTC"
1573 depends on PPC_MPC512x || PPC_MPC52xx
1575 If you say yes here you will get support for the
1576 built-in RTC on MPC5121 or on MPC5200.
1578 This driver can also be built as a module. If so, the module
1579 will be called rtc-mpc5121.
1581 config RTC_DRV_JZ4740
1582 tristate "Ingenic JZ4740 SoC"
1583 depends on MACH_INGENIC || COMPILE_TEST
1585 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1588 This driver can also be buillt as a module. If so, the module
1589 will be called rtc-jz4740.
1591 config RTC_DRV_LPC24XX
1592 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1593 depends on ARCH_LPC18XX || COMPILE_TEST
1594 depends on OF && HAS_IOMEM
1596 This enables support for the NXP RTC found which can be found on
1597 NXP LPC178x/18xx/408x/43xx devices.
1599 If you have one of the devices above enable this driver to use
1600 the hardware RTC. This driver can also be built as a module. If
1601 so, the module will be called rtc-lpc24xx.
1603 config RTC_DRV_LPC32XX
1604 depends on ARCH_LPC32XX || COMPILE_TEST
1605 tristate "NXP LPC32XX RTC"
1607 This enables support for the NXP RTC in the LPC32XX
1609 This driver can also be built as a module. If so, the module
1610 will be called rtc-lpc32xx.
1612 config RTC_DRV_PM8XXX
1613 tristate "Qualcomm PMIC8XXX RTC"
1614 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1616 If you say yes here you get support for the
1617 Qualcomm PMIC8XXX RTC.
1619 To compile this driver as a module, choose M here: the
1620 module will be called rtc-pm8xxx.
1622 config RTC_DRV_TEGRA
1623 tristate "NVIDIA Tegra Internal RTC driver"
1624 depends on ARCH_TEGRA || COMPILE_TEST
1626 If you say yes here you get support for the
1627 Tegra 200 series internal RTC module.
1629 This drive can also be built as a module. If so, the module
1630 will be called rtc-tegra.
1633 tristate "Tilera hypervisor RTC support"
1636 Enable support for the Linux driver side of the Tilera
1637 hypervisor's real-time clock interface.
1640 tristate "PKUnity v3 RTC support"
1641 depends on ARCH_PUV3
1643 This enables support for the RTC in the PKUnity-v3 SoCs.
1645 This drive can also be built as a module. If so, the module
1646 will be called rtc-puv3.
1648 config RTC_DRV_LOONGSON1
1649 tristate "loongson1 RTC support"
1650 depends on MACH_LOONGSON32
1652 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1653 counter) to be used as a RTC.
1655 This driver can also be built as a module. If so, the module
1656 will be called rtc-ls1x.
1659 tristate "Freescale MXC Real Time Clock"
1662 If you say yes here you get support for the Freescale MXC
1665 This driver can also be built as a module, if so, the module
1666 will be called "rtc-mxc".
1669 tristate "Freescale SNVS RTC support"
1671 depends on HAS_IOMEM
1674 If you say yes here you get support for the Freescale SNVS
1675 Low Power (LP) RTC module.
1677 This driver can also be built as a module, if so, the module
1678 will be called "rtc-snvs".
1680 config RTC_DRV_SIRFSOC
1681 tristate "SiRFSOC RTC"
1682 depends on ARCH_SIRF
1684 Say "yes" here to support the real time clock on SiRF SOC chips.
1685 This driver can also be built as a module called rtc-sirfsoc.
1687 config RTC_DRV_ST_LPC
1688 tristate "STMicroelectronics LPC RTC"
1692 Say Y here to include STMicroelectronics Low Power Controller
1693 (LPC) based RTC support.
1695 To compile this driver as a module, choose M here: the
1696 module will be called rtc-st-lpc.
1698 config RTC_DRV_MOXART
1699 tristate "MOXA ART RTC"
1700 depends on ARCH_MOXART || COMPILE_TEST
1702 If you say yes here you get support for the MOXA ART
1705 This driver can also be built as a module. If so, the module
1706 will be called rtc-moxart
1708 config RTC_DRV_MT6397
1709 tristate "Mediatek Real Time Clock driver"
1710 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1712 This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
1713 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1714 Mediatek(R) RTC driver.
1716 If you want to use Mediatek(R) RTC interface, select Y or M here.
1718 config RTC_DRV_XGENE
1719 tristate "APM X-Gene RTC"
1720 depends on HAS_IOMEM
1721 depends on ARCH_XGENE || COMPILE_TEST
1723 If you say yes here you get support for the APM X-Gene SoC real time
1726 This driver can also be built as a module, if so, the module
1727 will be called "rtc-xgene".
1729 config RTC_DRV_PIC32
1730 tristate "Microchip PIC32 RTC"
1731 depends on MACH_PIC32
1734 If you say yes here you get support for the PIC32 RTC module.
1736 This driver can also be built as a module. If so, the module
1737 will be called rtc-pic32
1739 config RTC_DRV_R7301
1740 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1742 depends on OF && HAS_IOMEM
1744 If you say yes here you get support for the EPSON TOYOCOM
1745 RTC-7301SF/DG chips.
1747 This driver can also be built as a module. If so, the module
1748 will be called rtc-r7301.
1750 config RTC_DRV_STM32
1751 tristate "STM32 RTC"
1753 depends on ARCH_STM32 || COMPILE_TEST
1755 If you say yes here you get support for the STM32 On-Chip
1758 This driver can also be built as a module, if so, the module
1759 will be called "rtc-stm32".
1761 config RTC_DRV_CPCAP
1762 depends on MFD_CPCAP
1763 tristate "Motorola CPCAP RTC"
1765 Say y here for CPCAP rtc found on some Motorola phones
1766 and tablets such as Droid 4.
1768 config RTC_DRV_RTD119X
1769 bool "Realtek RTD129x RTC"
1770 depends on ARCH_REALTEK || COMPILE_TEST
1771 default ARCH_REALTEK
1773 If you say yes here, you get support for the RTD1295 SoC
1776 comment "HID Sensor RTC drivers"
1778 config RTC_DRV_HID_SENSOR_TIME
1779 tristate "HID Sensor Time"
1782 select HID_SENSOR_HUB
1783 select HID_SENSOR_IIO_COMMON
1785 Say yes here to build support for the HID Sensors of type Time.
1786 This drivers makes such sensors available as RTCs.
1788 If this driver is compiled as a module, it will be named
1789 rtc-hid-sensor-time.
1791 config RTC_DRV_GOLDFISH
1792 tristate "Goldfish Real Time Clock"
1793 depends on MIPS && (GOLDFISH || COMPILE_TEST)
1795 Say yes to enable RTC driver for the Goldfish based virtual platform.
1797 Goldfish is a code name for the virtual platform developed by Google
1798 for Android emulation.