Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
1# SPDX-License-Identifier: GPL-2.0-only
2#
3# RTC class/drivers configuration
4#
5
6config RTC_LIB
7 bool
8
9config RTC_MC146818_LIB
10 bool
11 select RTC_LIB
12
13menuconfig RTC_CLASS
14 bool "Real Time Clock"
15 default n
16 depends on !S390
17 select RTC_LIB
18 help
19 Generic RTC class support. If you say yes here, you will
20 be allowed to plug one or more RTCs to your system. You will
21 probably want to enable one or more of the interfaces below.
22
23if RTC_CLASS
24
25config RTC_HCTOSYS
26 bool "Set system time from RTC on startup and resume"
27 default y
28 help
29 If you say yes here, the system time (wall clock) will be set using
30 the value read from a specified RTC device. This is useful to avoid
31 unnecessary fsck runs at boot time, and to network better.
32
33config RTC_HCTOSYS_DEVICE
34 string "RTC used to set the system time"
35 depends on RTC_HCTOSYS
36 default "rtc0"
37 help
38 The RTC device that will be used to (re)initialize the system
39 clock, usually rtc0. Initialization is done when the system
40 starts up, and when it resumes from a low power state. This
41 device should record time in UTC, since the kernel won't do
42 timezone correction.
43
44 This clock should be battery-backed, so that it reads the correct
45 time when the system boots from a power-off state. Otherwise, your
46 system will need an external clock source (like an NTP server).
47
48 If the clock you specify here is not battery backed, it may still
49 be useful to reinitialize system time when resuming from system
50 sleep states. Do not specify an RTC here unless it stays powered
51 during all this system's supported sleep states.
52
53config RTC_SYSTOHC
54 bool "Set the RTC time based on NTP synchronization"
55 default y
56 help
57 If you say yes here, the system time (wall clock) will be stored
58 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
59 minutes if userspace reports synchronized NTP status.
60
61config RTC_SYSTOHC_DEVICE
62 string "RTC used to synchronize NTP adjustment"
63 depends on RTC_SYSTOHC
64 default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS
65 default "rtc0"
66 help
67 The RTC device used for NTP synchronization. The main difference
68 between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this
69 one can sleep when setting time, because it runs in the workqueue
70 context.
71
72config RTC_DEBUG
73 bool "RTC debug support"
74 help
75 Say yes here to enable debugging support in the RTC framework
76 and individual RTC drivers.
77
78config RTC_LIB_KUNIT_TEST
79 tristate "KUnit test for RTC lib functions" if !KUNIT_ALL_TESTS
80 depends on KUNIT
81 default KUNIT_ALL_TESTS
82 help
83 Enable this option to test RTC library functions.
84
85 If unsure, say N.
86
87config RTC_NVMEM
88 bool "RTC non volatile storage support"
89 select NVMEM
90 default RTC_CLASS
91 help
92 Say yes here to add support for the non volatile (often battery
93 backed) storage present on RTCs.
94
95comment "RTC interfaces"
96
97config RTC_INTF_SYSFS
98 bool "/sys/class/rtc/rtcN (sysfs)"
99 depends on SYSFS
100 default RTC_CLASS
101 help
102 Say yes here if you want to use your RTCs using sysfs interfaces,
103 /sys/class/rtc/rtc0 through /sys/.../rtcN.
104
105 If unsure, say Y.
106
107config RTC_INTF_PROC
108 bool "/proc/driver/rtc (procfs for rtcN)"
109 depends on PROC_FS
110 default RTC_CLASS
111 help
112 Say yes here if you want to use your system clock RTC through
113 the proc interface, /proc/driver/rtc.
114 Other RTCs will not be available through that API.
115 If there is no RTC for the system clock, then the first RTC(rtc0)
116 is used by default.
117
118 If unsure, say Y.
119
120config RTC_INTF_DEV
121 bool "/dev/rtcN (character devices)"
122 default RTC_CLASS
123 help
124 Say yes here if you want to use your RTCs using the /dev
125 interfaces, which "udev" sets up as /dev/rtc0 through
126 /dev/rtcN.
127
128 You may want to set up a symbolic link so one of these
129 can be accessed as /dev/rtc, which is a name
130 expected by "hwclock" and some other programs. Recent
131 versions of "udev" are known to set up the symlink for you.
132
133 If unsure, say Y.
134
135config RTC_INTF_DEV_UIE_EMUL
136 bool "RTC UIE emulation on dev interface"
137 depends on RTC_INTF_DEV
138 help
139 Provides an emulation for RTC_UIE if the underlying rtc chip
140 driver does not expose RTC_UIE ioctls. Those requests generate
141 once-per-second update interrupts, used for synchronization.
142
143 The emulation code will read the time from the hardware
144 clock several times per second, please enable this option
145 only if you know that you really need it.
146
147config RTC_DRV_TEST
148 tristate "Test driver/device"
149 help
150 If you say yes here you get support for the
151 RTC test driver. It's a software RTC which can be
152 used to test the RTC subsystem APIs. It gets
153 the time from the system clock.
154 You want this driver only if you are doing development
155 on the RTC subsystem. Please read the source code
156 for further details.
157
158 This driver can also be built as a module. If so, the module
159 will be called rtc-test.
160
161comment "I2C RTC drivers"
162
163if I2C
164
165config RTC_DRV_88PM860X
166 tristate "Marvell 88PM860x"
167 depends on MFD_88PM860X
168 help
169 If you say yes here you get support for RTC function in Marvell
170 88PM860x chips.
171
172 This driver can also be built as a module. If so, the module
173 will be called rtc-88pm860x.
174
175config RTC_DRV_88PM80X
176 tristate "Marvell 88PM80x"
177 depends on MFD_88PM800
178 help
179 If you say yes here you get support for RTC function in Marvell
180 88PM80x chips.
181
182 This driver can also be built as a module. If so, the module
183 will be called rtc-88pm80x.
184
185config RTC_DRV_ABB5ZES3
186 select REGMAP_I2C
187 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
188 help
189 If you say yes here you get support for the Abracon
190 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
191
192 This driver can also be built as a module. If so, the module
193 will be called rtc-ab-b5ze-s3.
194
195config RTC_DRV_ABEOZ9
196 select REGMAP_I2C
197 tristate "Abracon AB-RTCMC-32.768kHz-EOZ9"
198 help
199 If you say yes here you get support for the Abracon
200 AB-RTCMC-32.768kHz-EOA9 I2C RTC chip.
201
202 This driver can also be built as a module. If so, the module
203 will be called rtc-ab-e0z9.
204
205config RTC_DRV_ABX80X
206 tristate "Abracon ABx80x"
207 select WATCHDOG_CORE if WATCHDOG
208 help
209 If you say yes here you get support for Abracon AB080X and AB180X
210 families of ultra-low-power battery- and capacitor-backed real-time
211 clock chips.
212
213 This driver can also be built as a module. If so, the module
214 will be called rtc-abx80x.
215
216config RTC_DRV_AC100
217 tristate "X-Powers AC100"
218 depends on MFD_AC100
219 help
220 If you say yes here you get support for the real-time clock found
221 in X-Powers AC100 family peripheral ICs.
222
223 This driver can also be built as a module. If so, the module
224 will be called rtc-ac100.
225
226config RTC_DRV_BRCMSTB
227 tristate "Broadcom STB wake-timer"
228 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
229 default ARCH_BRCMSTB || BMIPS_GENERIC
230 help
231 If you say yes here you get support for the wake-timer found on
232 Broadcom STB SoCs (BCM7xxx).
233
234 This driver can also be built as a module. If so, the module will
235 be called rtc-brcmstb-waketimer.
236
237config RTC_DRV_AS3722
238 tristate "ams AS3722 RTC driver"
239 depends on MFD_AS3722
240 help
241 If you say yes here you get support for the RTC of ams AS3722 PMIC
242 chips.
243
244 This driver can also be built as a module. If so, the module
245 will be called rtc-as3722.
246
247config RTC_DRV_DS1307
248 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"
249 select REGMAP_I2C
250 select WATCHDOG_CORE if WATCHDOG
251 help
252 If you say yes here you get support for various compatible RTC
253 chips (often with battery backup) connected with I2C. This driver
254 should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341,
255 ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.
256 In some cases the RTC must already have been initialized (by
257 manufacturing or a bootloader).
258
259 The first seven registers on these chips hold an RTC, and other
260 registers may add features such as NVRAM, a trickle charger for
261 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
262 sysfs, but other chip features may not be available.
263
264 This driver can also be built as a module. If so, the module
265 will be called rtc-ds1307.
266
267config RTC_DRV_DS1307_CENTURY
268 bool "Century bit support for rtc-ds1307"
269 depends on RTC_DRV_DS1307
270 default n
271 help
272 The DS1307 driver suffered from a bug where it was enabling the
273 century bit inconditionnally but never used it when reading the time.
274 It made the driver unable to support dates beyond 2099.
275 Setting this option will add proper support for the century bit but if
276 the time was previously set using a kernel predating this option,
277 reading the date will return a date in the next century.
278 To solve that, you could boot a kernel without this option set, set
279 the RTC date and then boot a kernel with this option set.
280
281config RTC_DRV_DS1374
282 tristate "Dallas/Maxim DS1374"
283 help
284 If you say yes here you get support for Dallas Semiconductor
285 DS1374 real-time clock chips. If an interrupt is associated
286 with the device, the alarm functionality is supported.
287
288 This driver can also be built as a module. If so, the module
289 will be called rtc-ds1374.
290
291config RTC_DRV_DS1374_WDT
292 bool "Dallas/Maxim DS1374 watchdog timer"
293 depends on RTC_DRV_DS1374 && WATCHDOG
294 select WATCHDOG_CORE
295 help
296 If you say Y here you will get support for the
297 watchdog timer in the Dallas Semiconductor DS1374
298 real-time clock chips.
299
300config RTC_DRV_DS1672
301 tristate "Dallas/Maxim DS1672"
302 help
303 If you say yes here you get support for the
304 Dallas/Maxim DS1672 timekeeping chip.
305
306 This driver can also be built as a module. If so, the module
307 will be called rtc-ds1672.
308
309config RTC_DRV_HYM8563
310 tristate "Haoyu Microelectronics HYM8563"
311 depends on OF
312 help
313 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
314 from the usual rtc functions it provides a clock output of
315 up to 32kHz.
316
317 This driver can also be built as a module. If so, the module
318 will be called rtc-hym8563.
319
320config RTC_DRV_LP8788
321 tristate "TI LP8788 RTC driver"
322 depends on MFD_LP8788
323 help
324 Say Y to enable support for the LP8788 RTC/ALARM driver.
325
326config RTC_DRV_MAX6900
327 tristate "Maxim MAX6900"
328 help
329 If you say yes here you will get support for the
330 Maxim MAX6900 I2C RTC chip.
331
332 This driver can also be built as a module. If so, the module
333 will be called rtc-max6900.
334
335config RTC_DRV_MAX8907
336 tristate "Maxim MAX8907"
337 depends on MFD_MAX8907 || COMPILE_TEST
338 select REGMAP_IRQ
339 help
340 If you say yes here you will get support for the
341 RTC of Maxim MAX8907 PMIC.
342
343 This driver can also be built as a module. If so, the module
344 will be called rtc-max8907.
345
346config RTC_DRV_MAX8925
347 tristate "Maxim MAX8925"
348 depends on MFD_MAX8925
349 help
350 If you say yes here you will get support for the
351 RTC of Maxim MAX8925 PMIC.
352
353 This driver can also be built as a module. If so, the module
354 will be called rtc-max8925.
355
356config RTC_DRV_MAX8998
357 tristate "Maxim MAX8998"
358 depends on MFD_MAX8998
359 help
360 If you say yes here you will get support for the
361 RTC of Maxim MAX8998 PMIC.
362
363 This driver can also be built as a module. If so, the module
364 will be called rtc-max8998.
365
366config RTC_DRV_MAX8997
367 tristate "Maxim MAX8997"
368 depends on MFD_MAX8997
369 help
370 If you say yes here you will get support for the
371 RTC of Maxim MAX8997 PMIC.
372
373 This driver can also be built as a module. If so, the module
374 will be called rtc-max8997.
375
376config RTC_DRV_MAX77686
377 tristate "Maxim MAX77686"
378 depends on MFD_MAX77686 || MFD_MAX77620 || MFD_MAX77714 || COMPILE_TEST
379 help
380 If you say yes here you will get support for the
381 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
382
383 This driver can also be built as a module. If so, the module
384 will be called rtc-max77686.
385
386config RTC_DRV_NCT3018Y
387 tristate "Nuvoton NCT3018Y"
388 depends on OF
389 help
390 If you say yes here you get support for the Nuvoton NCT3018Y I2C RTC
391 chip.
392
393 This driver can also be built as a module, if so, the module will be
394 called "rtc-nct3018y".
395
396config RTC_DRV_RK808
397 tristate "Rockchip RK805/RK808/RK809/RK817/RK818 RTC"
398 depends on MFD_RK808
399 help
400 If you say yes here you will get support for the
401 RTC of RK805, RK809 and RK817, RK808 and RK818 PMIC.
402
403 This driver can also be built as a module. If so, the module
404 will be called rk808-rtc.
405
406config RTC_DRV_RS5C372
407 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
408 help
409 If you say yes here you get support for the
410 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
411
412 This driver can also be built as a module. If so, the module
413 will be called rtc-rs5c372.
414
415config RTC_DRV_ISL1208
416 tristate "Intersil ISL1208"
417 help
418 If you say yes here you get support for the
419 Intersil ISL1208 RTC chip.
420
421 This driver can also be built as a module. If so, the module
422 will be called rtc-isl1208.
423
424config RTC_DRV_ISL12022
425 tristate "Intersil ISL12022"
426 select REGMAP_I2C
427 help
428 If you say yes here you get support for the
429 Intersil ISL12022 RTC chip.
430
431 This driver can also be built as a module. If so, the module
432 will be called rtc-isl12022.
433
434config RTC_DRV_ISL12026
435 tristate "Intersil ISL12026"
436 depends on OF
437 help
438 If you say yes here you get support for the
439 Intersil ISL12026 RTC chip.
440
441 This driver can also be built as a module. If so, the module
442 will be called rtc-isl12026.
443
444config RTC_DRV_X1205
445 tristate "Xicor/Intersil X1205"
446 help
447 If you say yes here you get support for the
448 Xicor/Intersil X1205 RTC chip.
449
450 This driver can also be built as a module. If so, the module
451 will be called rtc-x1205.
452
453config RTC_DRV_PCF8523
454 tristate "NXP PCF8523"
455 select REGMAP_I2C
456 help
457 If you say yes here you get support for the NXP PCF8523 RTC
458 chips.
459
460 This driver can also be built as a module. If so, the module
461 will be called rtc-pcf8523.
462
463config RTC_DRV_PCF85063
464 tristate "NXP PCF85063"
465 select REGMAP_I2C
466 help
467 If you say yes here you get support for the PCF85063 RTC chip
468
469 This driver can also be built as a module. If so, the module
470 will be called rtc-pcf85063.
471
472config RTC_DRV_PCF85363
473 tristate "NXP PCF85363"
474 select REGMAP_I2C
475 help
476 If you say yes here you get support for the PCF85363 RTC chip.
477
478 This driver can also be built as a module. If so, the module
479 will be called rtc-pcf85363.
480
481 The nvmem interface will be named pcf85363-#, where # is the
482 zero-based instance number.
483
484config RTC_DRV_PCF8563
485 tristate "Philips PCF8563/Epson RTC8564"
486 help
487 If you say yes here you get support for the
488 Philips PCF8563 RTC chip. The Epson RTC8564
489 should work as well.
490
491 This driver can also be built as a module. If so, the module
492 will be called rtc-pcf8563.
493
494config RTC_DRV_PCF8583
495 tristate "Philips PCF8583"
496 help
497 If you say yes here you get support for the Philips PCF8583
498 RTC chip found on Acorn RiscPCs. This driver supports the
499 platform specific method of retrieving the current year from
500 the RTC's SRAM. It will work on other platforms with the same
501 chip, but the year will probably have to be tweaked.
502
503 This driver can also be built as a module. If so, the module
504 will be called rtc-pcf8583.
505
506config RTC_DRV_M41T80
507 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
508 help
509 If you say Y here you will get support for the ST M41T60
510 and M41T80 RTC chips series. Currently, the following chips are
511 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
512 M41ST85, M41ST87, and MicroCrystal RV4162.
513
514 This driver can also be built as a module. If so, the module
515 will be called rtc-m41t80.
516
517config RTC_DRV_M41T80_WDT
518 bool "ST M41T65/M41T80 series RTC watchdog timer"
519 depends on RTC_DRV_M41T80
520 help
521 If you say Y here you will get support for the
522 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
523
524config RTC_DRV_BD70528
525 tristate "ROHM BD71815 and BD71828 PMIC RTC"
526 depends on MFD_ROHM_BD71828
527 help
528 If you say Y here you will get support for the RTC
529 block on ROHM BD71815 and BD71828 Power Management IC.
530
531 This driver can also be built as a module. If so, the module
532 will be called rtc-bd70528.
533
534config RTC_DRV_BQ32K
535 tristate "TI BQ32000"
536 help
537 If you say Y here you will get support for the TI
538 BQ32000 I2C RTC chip.
539
540 This driver can also be built as a module. If so, the module
541 will be called rtc-bq32k.
542
543config RTC_DRV_TWL92330
544 bool "TI TWL92330/Menelaus"
545 depends on MENELAUS
546 help
547 If you say yes here you get support for the RTC on the
548 TWL92330 "Menelaus" power management chip, used with OMAP2
549 platforms. The support is integrated with the rest of
550 the Menelaus driver; it's not separate module.
551
552config RTC_DRV_TWL4030
553 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
554 depends on TWL4030_CORE
555 depends on OF
556 help
557 If you say yes here you get support for the RTC on the
558 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
559
560 This driver can also be built as a module. If so, the module
561 will be called rtc-twl.
562
563config RTC_DRV_PALMAS
564 tristate "TI Palmas RTC driver"
565 depends on MFD_PALMAS
566 help
567 If you say yes here you get support for the RTC of TI PALMA series PMIC
568 chips.
569
570 This driver can also be built as a module. If so, the module
571 will be called rtc-palma.
572
573config RTC_DRV_TPS6586X
574 tristate "TI TPS6586X RTC driver"
575 depends on MFD_TPS6586X
576 help
577 TI Power Management IC TPS6586X supports RTC functionality
578 along with alarm. This driver supports the RTC driver for
579 the TPS6586X RTC module.
580
581config RTC_DRV_TPS65910
582 tristate "TI TPS65910 RTC driver"
583 depends on MFD_TPS65910
584 help
585 If you say yes here you get support for the RTC on the
586 TPS65910 chips.
587
588 This driver can also be built as a module. If so, the module
589 will be called rtc-tps65910.
590
591config RTC_DRV_RC5T583
592 tristate "RICOH 5T583 RTC driver"
593 depends on MFD_RC5T583
594 help
595 If you say yes here you get support for the RTC on the
596 RICOH 5T583 chips.
597
598 This driver can also be built as a module. If so, the module
599 will be called rtc-rc5t583.
600
601config RTC_DRV_RC5T619
602 tristate "RICOH RC5T619 RTC driver"
603 depends on MFD_RN5T618
604 help
605 If you say yes here you get support for the RTC on the
606 RICOH RC5T619 chips.
607
608 This driver can also be built as a module. If so, the module
609 will be called rtc-rc5t619.
610
611config RTC_DRV_S35390A
612 tristate "Seiko Instruments S-35390A"
613 select BITREVERSE
614 help
615 If you say yes here you will get support for the Seiko
616 Instruments S-35390A.
617
618 This driver can also be built as a module. If so the module
619 will be called rtc-s35390a.
620
621config RTC_DRV_FM3130
622 tristate "Ramtron FM3130"
623 help
624 If you say Y here you will get support for the
625 Ramtron FM3130 RTC chips.
626 Ramtron FM3130 is a chip with two separate devices inside,
627 RTC clock and FRAM. This driver provides only RTC functionality.
628
629 This driver can also be built as a module. If so the module
630 will be called rtc-fm3130.
631
632config RTC_DRV_RX8010
633 tristate "Epson RX8010SJ"
634 select REGMAP_I2C
635 help
636 If you say yes here you get support for the Epson RX8010SJ RTC
637 chip.
638
639 This driver can also be built as a module. If so, the module
640 will be called rtc-rx8010.
641
642config RTC_DRV_RX8581
643 tristate "Epson RX-8571/RX-8581"
644 select REGMAP_I2C
645 help
646 If you say yes here you will get support for the Epson RX-8571/
647 RX-8581.
648
649 This driver can also be built as a module. If so the module
650 will be called rtc-rx8581.
651
652config RTC_DRV_RX8025
653 tristate "Epson RX-8025SA/NB"
654 help
655 If you say yes here you get support for the Epson
656 RX-8025SA/NB RTC chips.
657
658 This driver can also be built as a module. If so, the module
659 will be called rtc-rx8025.
660
661config RTC_DRV_EM3027
662 tristate "EM Microelectronic EM3027"
663 help
664 If you say yes here you get support for the EM
665 Microelectronic EM3027 RTC chips.
666
667 This driver can also be built as a module. If so, the module
668 will be called rtc-em3027.
669
670config RTC_DRV_RV3028
671 tristate "Micro Crystal RV3028"
672 select REGMAP_I2C
673 help
674 If you say yes here you get support for the Micro Crystal
675 RV3028.
676
677 This driver can also be built as a module. If so, the module
678 will be called rtc-rv3028.
679
680config RTC_DRV_RV3032
681 tristate "Micro Crystal RV3032"
682 select REGMAP_I2C
683 help
684 If you say yes here you get support for the Micro Crystal
685 RV3032.
686
687 This driver can also be built as a module. If so, the module
688 will be called rtc-rv3032.
689
690config RTC_DRV_RV8803
691 tristate "Micro Crystal RV8803, Epson RX8900"
692 help
693 If you say yes here you get support for the Micro Crystal RV8803 and
694 Epson RX8900 RTC chips.
695
696 This driver can also be built as a module. If so, the module
697 will be called rtc-rv8803.
698
699config RTC_DRV_S5M
700 tristate "Samsung S2M/S5M series"
701 depends on MFD_SEC_CORE || COMPILE_TEST
702 select REGMAP_IRQ
703 select REGMAP_I2C
704 help
705 If you say yes here you will get support for the
706 RTC of Samsung S2MPS14 and S5M PMIC series.
707
708 This driver can also be built as a module. If so, the module
709 will be called rtc-s5m.
710
711config RTC_DRV_SD3078
712 tristate "ZXW Shenzhen whwave SD3078"
713 select REGMAP_I2C
714 help
715 If you say yes here you get support for the ZXW Shenzhen whwave
716 SD3078 RTC chips.
717
718 This driver can also be built as a module. If so, the module
719 will be called rtc-sd3078
720
721endif # I2C
722
723comment "SPI RTC drivers"
724
725if SPI_MASTER
726
727config RTC_DRV_M41T93
728 tristate "ST M41T93"
729 help
730 If you say yes here you will get support for the
731 ST M41T93 SPI RTC chip.
732
733 This driver can also be built as a module. If so, the module
734 will be called rtc-m41t93.
735
736config RTC_DRV_M41T94
737 tristate "ST M41T94"
738 help
739 If you say yes here you will get support for the
740 ST M41T94 SPI RTC chip.
741
742 This driver can also be built as a module. If so, the module
743 will be called rtc-m41t94.
744
745config RTC_DRV_DS1302
746 tristate "Dallas/Maxim DS1302"
747 depends on SPI
748 help
749 If you say yes here you get support for the Dallas DS1302 RTC chips.
750
751 This driver can also be built as a module. If so, the module
752 will be called rtc-ds1302.
753
754config RTC_DRV_DS1305
755 tristate "Dallas/Maxim DS1305/DS1306"
756 help
757 Select this driver to get support for the Dallas/Maxim DS1305
758 and DS1306 real time clock chips. These support a trickle
759 charger, alarms, and NVRAM in addition to the clock.
760
761 This driver can also be built as a module. If so, the module
762 will be called rtc-ds1305.
763
764config RTC_DRV_DS1343
765 select REGMAP_SPI
766 tristate "Dallas/Maxim DS1343/DS1344"
767 help
768 If you say yes here you get support for the
769 Dallas/Maxim DS1343 and DS1344 real time clock chips.
770 Support for trickle charger, alarm is provided.
771
772 This driver can also be built as a module. If so, the module
773 will be called rtc-ds1343.
774
775config RTC_DRV_DS1347
776 select REGMAP_SPI
777 tristate "Dallas/Maxim DS1347"
778 help
779 If you say yes here you get support for the
780 Dallas/Maxim DS1347 chips.
781
782 This driver only supports the RTC feature, and not other chip
783 features such as alarms.
784
785 This driver can also be built as a module. If so, the module
786 will be called rtc-ds1347.
787
788config RTC_DRV_DS1390
789 tristate "Dallas/Maxim DS1390/93/94"
790 help
791 If you say yes here you get support for the
792 Dallas/Maxim DS1390/93/94 chips.
793
794 This driver supports the RTC feature and trickle charging but not
795 other chip features such as alarms.
796
797 This driver can also be built as a module. If so, the module
798 will be called rtc-ds1390.
799
800config RTC_DRV_MAX6916
801 tristate "Maxim MAX6916"
802 help
803 If you say yes here you will get support for the
804 Maxim MAX6916 SPI RTC chip.
805
806 This driver only supports the RTC feature, and not other chip
807 features such as alarms.
808
809 This driver can also be built as a module. If so, the module
810 will be called rtc-max6916.
811
812config RTC_DRV_R9701
813 tristate "Epson RTC-9701JE"
814 help
815 If you say yes here you will get support for the
816 Epson RTC-9701JE SPI RTC chip.
817
818 This driver can also be built as a module. If so, the module
819 will be called rtc-r9701.
820
821config RTC_DRV_RX4581
822 tristate "Epson RX-4581"
823 help
824 If you say yes here you will get support for the Epson RX-4581.
825
826 This driver can also be built as a module. If so the module
827 will be called rtc-rx4581.
828
829config RTC_DRV_RS5C348
830 tristate "Ricoh RS5C348A/B"
831 help
832 If you say yes here you get support for the
833 Ricoh RS5C348A and RS5C348B RTC chips.
834
835 This driver can also be built as a module. If so, the module
836 will be called rtc-rs5c348.
837
838config RTC_DRV_MAX6902
839 tristate "Maxim MAX6902"
840 help
841 If you say yes here you will get support for the
842 Maxim MAX6902 SPI RTC chip.
843
844 This driver can also be built as a module. If so, the module
845 will be called rtc-max6902.
846
847config RTC_DRV_PCF2123
848 tristate "NXP PCF2123"
849 select REGMAP_SPI
850 help
851 If you say yes here you get support for the NXP PCF2123
852 RTC chip.
853
854 This driver can also be built as a module. If so, the module
855 will be called rtc-pcf2123.
856
857config RTC_DRV_MCP795
858 tristate "Microchip MCP795"
859 help
860 If you say yes here you will get support for the Microchip MCP795.
861
862 This driver can also be built as a module. If so the module
863 will be called rtc-mcp795.
864
865endif # SPI_MASTER
866
867#
868# Helper to resolve issues with configs that have SPI enabled but I2C
869# modular. See SND_SOC_I2C_AND_SPI for more information
870#
871config RTC_I2C_AND_SPI
872 tristate
873 default m if I2C=m
874 default y if I2C=y
875 default y if SPI_MASTER=y
876
877comment "SPI and I2C RTC drivers"
878
879config RTC_DRV_DS3232
880 tristate "Dallas/Maxim DS3232/DS3234"
881 depends on RTC_I2C_AND_SPI
882 select REGMAP_I2C if I2C
883 select REGMAP_SPI if SPI_MASTER
884 help
885 If you say yes here you get support for Dallas Semiconductor
886 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
887 with the device, the alarm functionality is supported.
888
889 This driver can also be built as a module. If so, the module
890 will be called rtc-ds3232.
891
892config RTC_DRV_DS3232_HWMON
893 bool "HWMON support for Dallas/Maxim DS3232/DS3234"
894 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
895 default y
896 help
897 Say Y here if you want to expose temperature sensor data on
898 rtc-ds3232
899
900config RTC_DRV_PCF2127
901 tristate "NXP PCF2127"
902 depends on RTC_I2C_AND_SPI
903 select REGMAP_I2C if I2C
904 select REGMAP_SPI if SPI_MASTER
905 select WATCHDOG_CORE if WATCHDOG
906 help
907 If you say yes here you get support for the NXP PCF2127/29 RTC
908 chips with integrated quartz crystal for industrial applications.
909 Both chips also have watchdog timer and tamper switch detection
910 features.
911
912 PCF2127 has an additional feature of 512 bytes battery backed
913 memory that's accessible using nvmem interface.
914
915 This driver can also be built as a module. If so, the module
916 will be called rtc-pcf2127.
917
918config RTC_DRV_RV3029C2
919 tristate "Micro Crystal RV3029/3049"
920 depends on RTC_I2C_AND_SPI
921 select REGMAP_I2C if I2C
922 select REGMAP_SPI if SPI_MASTER
923 help
924 If you say yes here you get support for the Micro Crystal
925 RV3029 and RV3049 RTC chips.
926
927 This driver can also be built as a module. If so, the module
928 will be called rtc-rv3029c2.
929
930config RTC_DRV_RV3029_HWMON
931 bool "HWMON support for RV3029/3049"
932 depends on RTC_DRV_RV3029C2 && HWMON
933 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
934 default y
935 help
936 Say Y here if you want to expose temperature sensor data on
937 rtc-rv3029.
938
939config RTC_DRV_RX6110
940 tristate "Epson RX-6110"
941 depends on RTC_I2C_AND_SPI
942 select REGMAP_SPI if SPI_MASTER
943 select REGMAP_I2C if I2C
944 help
945 If you say yes here you will get support for the Epson RX-6110.
946
947 This driver can also be built as a module. If so the module
948 will be called rtc-rx6110.
949
950comment "Platform RTC drivers"
951
952# this 'CMOS' RTC driver is arch dependent because it requires
953# <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
954# global rtc_lock ... it's not yet just another platform_device.
955
956config RTC_DRV_CMOS
957 tristate "PC-style 'CMOS'"
958 depends on X86 || ARM || PPC || MIPS || SPARC64
959 default y if X86
960 select RTC_MC146818_LIB
961 help
962 Say "yes" here to get direct support for the real time clock
963 found in every PC or ACPI-based system, and some other boards.
964 Specifically the original MC146818, compatibles like those in
965 PC south bridges, the DS12887 or M48T86, some multifunction
966 or LPC bus chips, and so on.
967
968 Your system will need to define the platform device used by
969 this driver, otherwise it won't be accessible. This means
970 you can safely enable this driver if you don't know whether
971 or not your board has this kind of hardware.
972
973 This driver can also be built as a module. If so, the module
974 will be called rtc-cmos.
975
976config RTC_DRV_ALPHA
977 bool "Alpha PC-style CMOS"
978 depends on ALPHA
979 select RTC_MC146818_LIB
980 default y
981 help
982 Direct support for the real-time clock found on every Alpha
983 system, specifically MC146818 compatibles. If in doubt, say Y.
984
985config RTC_DRV_DS1216
986 tristate "Dallas DS1216"
987 depends on SNI_RM
988 help
989 If you say yes here you get support for the Dallas DS1216 RTC chips.
990
991config RTC_DRV_DS1286
992 tristate "Dallas DS1286"
993 depends on HAS_IOMEM
994 help
995 If you say yes here you get support for the Dallas DS1286 RTC chips.
996
997config RTC_DRV_DS1511
998 tristate "Dallas DS1511"
999 depends on HAS_IOMEM
1000 help
1001 If you say yes here you get support for the
1002 Dallas DS1511 timekeeping/watchdog chip.
1003
1004 This driver can also be built as a module. If so, the module
1005 will be called rtc-ds1511.
1006
1007config RTC_DRV_DS1553
1008 tristate "Maxim/Dallas DS1553"
1009 depends on HAS_IOMEM
1010 help
1011 If you say yes here you get support for the
1012 Maxim/Dallas DS1553 timekeeping chip.
1013
1014 This driver can also be built as a module. If so, the module
1015 will be called rtc-ds1553.
1016
1017config RTC_DRV_DS1685_FAMILY
1018 tristate "Dallas/Maxim DS1685 Family"
1019 depends on HAS_IOMEM
1020 help
1021 If you say yes here you get support for the Dallas/Maxim DS1685
1022 family of real time chips. This family includes the DS1685/DS1687,
1023 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
1024 DS17885/DS17887 chips.
1025
1026 This driver can also be built as a module. If so, the module
1027 will be called rtc-ds1685.
1028
1029choice
1030 prompt "Subtype"
1031 depends on RTC_DRV_DS1685_FAMILY
1032 default RTC_DRV_DS1685
1033
1034config RTC_DRV_DS1685
1035 bool "DS1685/DS1687"
1036 help
1037 This enables support for the Dallas/Maxim DS1685/DS1687 real time
1038 clock chip.
1039
1040 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
1041 systems, as well as EPPC-405-UC modules by electronic system design
1042 GmbH.
1043
1044config RTC_DRV_DS1689
1045 bool "DS1689/DS1693"
1046 help
1047 This enables support for the Dallas/Maxim DS1689/DS1693 real time
1048 clock chip.
1049
1050 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
1051 which supports a few minor features such as Vcc, Vbat, and Power
1052 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
1053
1054 It also works for the even older DS1688/DS1691 RTC chips, which are
1055 virtually the same and carry the same model number. Both chips
1056 have 114 bytes of user NVRAM.
1057
1058config RTC_DRV_DS17285
1059 bool "DS17285/DS17287"
1060 help
1061 This enables support for the Dallas/Maxim DS17285/DS17287 real time
1062 clock chip.
1063
1064 This chip features 2kb of extended NV-SRAM. It may possibly be
1065 found in some SGI O2 systems (rare).
1066
1067config RTC_DRV_DS17485
1068 bool "DS17485/DS17487"
1069 help
1070 This enables support for the Dallas/Maxim DS17485/DS17487 real time
1071 clock chip.
1072
1073 This chip features 4kb of extended NV-SRAM.
1074
1075config RTC_DRV_DS17885
1076 bool "DS17885/DS17887"
1077 help
1078 This enables support for the Dallas/Maxim DS17885/DS17887 real time
1079 clock chip.
1080
1081 This chip features 8kb of extended NV-SRAM.
1082
1083endchoice
1084
1085config RTC_DRV_DS1742
1086 tristate "Maxim/Dallas DS1742/1743"
1087 depends on HAS_IOMEM
1088 help
1089 If you say yes here you get support for the
1090 Maxim/Dallas DS1742/1743 timekeeping chip.
1091
1092 This driver can also be built as a module. If so, the module
1093 will be called rtc-ds1742.
1094
1095config RTC_DRV_DS2404
1096 tristate "Maxim/Dallas DS2404"
1097 help
1098 If you say yes here you get support for the
1099 Dallas DS2404 RTC chip.
1100
1101 This driver can also be built as a module. If so, the module
1102 will be called rtc-ds2404.
1103
1104config RTC_DRV_DA9052
1105 tristate "Dialog DA9052/DA9053 RTC"
1106 depends on PMIC_DA9052
1107 help
1108 Say y here to support the RTC driver for Dialog Semiconductor
1109 DA9052-BC and DA9053-AA/Bx PMICs.
1110
1111config RTC_DRV_DA9055
1112 tristate "Dialog Semiconductor DA9055 RTC"
1113 depends on MFD_DA9055
1114 help
1115 If you say yes here you will get support for the
1116 RTC of the Dialog DA9055 PMIC.
1117
1118 This driver can also be built as a module. If so, the module
1119 will be called rtc-da9055
1120
1121config RTC_DRV_DA9063
1122 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1123 depends on MFD_DA9063 || MFD_DA9062
1124 help
1125 If you say yes here you will get support for the RTC subsystem
1126 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1127
1128 This driver can also be built as a module. If so, the module
1129 will be called "rtc-da9063".
1130
1131config RTC_DRV_EFI
1132 tristate "EFI RTC"
1133 depends on EFI && !X86
1134 help
1135 If you say yes here you will get support for the EFI
1136 Real Time Clock.
1137
1138 This driver can also be built as a module. If so, the module
1139 will be called rtc-efi.
1140
1141config RTC_DRV_STK17TA8
1142 tristate "Simtek STK17TA8"
1143 depends on HAS_IOMEM
1144 help
1145 If you say yes here you get support for the
1146 Simtek STK17TA8 timekeeping chip.
1147
1148 This driver can also be built as a module. If so, the module
1149 will be called rtc-stk17ta8.
1150
1151config RTC_DRV_M48T86
1152 tristate "ST M48T86/Dallas DS12887"
1153 depends on HAS_IOMEM
1154 help
1155 If you say Y here you will get support for the
1156 ST M48T86 and Dallas DS12887 RTC chips.
1157
1158 This driver can also be built as a module. If so, the module
1159 will be called rtc-m48t86.
1160
1161config RTC_DRV_M48T35
1162 tristate "ST M48T35"
1163 depends on HAS_IOMEM
1164 help
1165 If you say Y here you will get support for the
1166 ST M48T35 RTC chip.
1167
1168 This driver can also be built as a module, if so, the module
1169 will be called "rtc-m48t35".
1170
1171config RTC_DRV_M48T59
1172 tristate "ST M48T59/M48T08/M48T02"
1173 depends on HAS_IOMEM
1174 help
1175 If you say Y here you will get support for the
1176 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1177
1178 These chips are usually found in Sun SPARC and UltraSPARC
1179 workstations.
1180
1181 This driver can also be built as a module, if so, the module
1182 will be called "rtc-m48t59".
1183
1184config RTC_DRV_MSM6242
1185 tristate "Oki MSM6242"
1186 depends on HAS_IOMEM
1187 help
1188 If you say yes here you get support for the Oki MSM6242
1189 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1190
1191 This driver can also be built as a module. If so, the module
1192 will be called rtc-msm6242.
1193
1194config RTC_DRV_BQ4802
1195 tristate "TI BQ4802"
1196 depends on HAS_IOMEM
1197 help
1198 If you say Y here you will get support for the TI
1199 BQ4802 RTC chip.
1200
1201 This driver can also be built as a module. If so, the module
1202 will be called rtc-bq4802.
1203
1204config RTC_DRV_RP5C01
1205 tristate "Ricoh RP5C01"
1206 depends on HAS_IOMEM
1207 help
1208 If you say yes here you get support for the Ricoh RP5C01
1209 timekeeping chip. It is used in some Amiga models (e.g. A3000
1210 and A4000).
1211
1212 This driver can also be built as a module. If so, the module
1213 will be called rtc-rp5c01.
1214
1215config RTC_DRV_GAMECUBE
1216 tristate "Nintendo GameCube, Wii and Wii U RTC"
1217 depends on GAMECUBE || WII || COMPILE_TEST
1218 select REGMAP
1219 help
1220 If you say yes here you will get support for the RTC subsystem
1221 of the Nintendo GameCube, Wii and Wii U.
1222
1223 This driver can also be built as a module. If so, the module
1224 will be called "rtc-gamecube".
1225
1226config RTC_DRV_WM831X
1227 tristate "Wolfson Microelectronics WM831x RTC"
1228 depends on MFD_WM831X
1229 help
1230 If you say yes here you will get support for the RTC subsystem
1231 of the Wolfson Microelectronics WM831X series PMICs.
1232
1233 This driver can also be built as a module. If so, the module
1234 will be called "rtc-wm831x".
1235
1236config RTC_DRV_WM8350
1237 tristate "Wolfson Microelectronics WM8350 RTC"
1238 depends on MFD_WM8350
1239 help
1240 If you say yes here you will get support for the RTC subsystem
1241 of the Wolfson Microelectronics WM8350.
1242
1243 This driver can also be built as a module. If so, the module
1244 will be called "rtc-wm8350".
1245
1246config RTC_DRV_SC27XX
1247 tristate "Spreadtrum SC27xx RTC"
1248 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1249 help
1250 If you say Y here you will get support for the RTC subsystem
1251 of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs
1252 includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips.
1253
1254 This driver can also be built as a module. If so, the module
1255 will be called rtc-sc27xx.
1256
1257config RTC_DRV_SPEAR
1258 tristate "SPEAR ST RTC"
1259 depends on PLAT_SPEAR || COMPILE_TEST
1260 default y
1261 help
1262 If you say Y here you will get support for the RTC found on
1263 spear
1264
1265config RTC_DRV_PCF50633
1266 depends on MFD_PCF50633
1267 tristate "NXP PCF50633 RTC"
1268 help
1269 If you say yes here you get support for the RTC subsystem of the
1270 NXP PCF50633 used in embedded systems.
1271
1272config RTC_DRV_AB8500
1273 tristate "ST-Ericsson AB8500 RTC"
1274 depends on AB8500_CORE
1275 select RTC_INTF_DEV
1276 select RTC_INTF_DEV_UIE_EMUL
1277 help
1278 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1279 support. This chip contains a battery- and capacitor-backed RTC.
1280
1281config RTC_DRV_OPAL
1282 tristate "IBM OPAL RTC driver"
1283 depends on PPC_POWERNV
1284 default y
1285 help
1286 If you say yes here you get support for the PowerNV platform RTC
1287 driver based on OPAL interfaces.
1288
1289 This driver can also be built as a module. If so, the module
1290 will be called rtc-opal.
1291
1292config RTC_DRV_OPTEE
1293 tristate "OP-TEE based RTC driver"
1294 depends on OPTEE
1295 help
1296 Select this to get support for OP-TEE based RTC control on SoCs where
1297 RTC are not accessible to the normal world (Linux).
1298
1299 This driver can also be built as a module. If so, the module
1300 will be called rtc-optee.
1301
1302config RTC_DRV_ZYNQMP
1303 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1304 depends on OF && HAS_IOMEM
1305 help
1306 If you say yes here you get support for the RTC controller found on
1307 Xilinx Zynq Ultrascale+ MPSoC.
1308
1309config RTC_DRV_CROS_EC
1310 tristate "Chrome OS EC RTC driver"
1311 depends on CROS_EC
1312 help
1313 If you say yes here you will get support for the
1314 Chrome OS Embedded Controller's RTC.
1315
1316 This driver can also be built as a module. If so, the module
1317 will be called rtc-cros-ec.
1318
1319config RTC_DRV_NTXEC
1320 tristate "Netronix embedded controller RTC"
1321 depends on MFD_NTXEC
1322 help
1323 Say yes here if you want to support the RTC functionality of the
1324 embedded controller found in certain e-book readers designed by the
1325 original design manufacturer Netronix.
1326
1327comment "on-CPU RTC drivers"
1328
1329config RTC_DRV_ASM9260
1330 tristate "Alphascale asm9260 RTC"
1331 depends on MACH_ASM9260 || COMPILE_TEST
1332 help
1333 If you say yes here you get support for the RTC on the
1334 Alphascale asm9260 SoC.
1335
1336 This driver can also be built as a module. If so, the module
1337 will be called rtc-asm9260.
1338
1339config RTC_DRV_DIGICOLOR
1340 tristate "Conexant Digicolor RTC"
1341 depends on ARCH_DIGICOLOR || COMPILE_TEST
1342 help
1343 If you say yes here you get support for the RTC on Conexant
1344 Digicolor platforms. This currently includes the CX92755 SoC.
1345
1346 This driver can also be built as a module. If so, the module
1347 will be called rtc-digicolor.
1348
1349config RTC_DRV_IMXDI
1350 tristate "Freescale IMX DryIce Real Time Clock"
1351 depends on ARCH_MXC
1352 depends on OF
1353 help
1354 Support for Freescale IMX DryIce RTC
1355
1356 This driver can also be built as a module, if so, the module
1357 will be called "rtc-imxdi".
1358
1359config RTC_DRV_FSL_FTM_ALARM
1360 tristate "Freescale FlexTimer alarm timer"
1361 depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST
1362 help
1363 For the FlexTimer in LS1012A, LS1021A, LS1028A, LS1043A, LS1046A,
1364 LS1088A, LS208xA, we can use FTM as the wakeup source.
1365
1366 Say y here to enable FTM alarm support. The FTM alarm provides
1367 alarm functions for wakeup system from deep sleep.
1368
1369 This driver can also be built as a module, if so, the module
1370 will be called "rtc-fsl-ftm-alarm".
1371
1372config RTC_DRV_MESON
1373 tristate "Amlogic Meson RTC"
1374 depends on (ARM && ARCH_MESON) || COMPILE_TEST
1375 select REGMAP_MMIO
1376 help
1377 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1378 and Meson8m2 SoCs.
1379
1380 This driver can also be built as a module, if so, the module
1381 will be called "rtc-meson".
1382
1383config RTC_DRV_MESON_VRTC
1384 tristate "Amlogic Meson Virtual RTC"
1385 depends on ARCH_MESON || COMPILE_TEST
1386 default m if ARCH_MESON
1387 help
1388 If you say yes here you will get support for the
1389 Virtual RTC of Amlogic SoCs.
1390
1391 This driver can also be built as a module. If so, the module
1392 will be called rtc-meson-vrtc.
1393
1394config RTC_DRV_OMAP
1395 tristate "TI OMAP Real Time Clock"
1396 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1397 depends on OF
1398 depends on PINCTRL
1399 select GENERIC_PINCONF
1400 help
1401 Say "yes" here to support the on chip real time clock
1402 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1403
1404 This driver can also be built as a module, if so, module
1405 will be called rtc-omap.
1406
1407config RTC_DRV_S3C
1408 tristate "Samsung S3C series SoC RTC"
1409 depends on ARCH_EXYNOS || ARCH_S3C64XX || ARCH_S5PV210 || \
1410 COMPILE_TEST
1411 help
1412 RTC (Realtime Clock) driver for the clock inbuilt into the
1413 Samsung S3C64XX series of SoCs. This can provide periodic
1414 interrupt rates from 1Hz to 64Hz for user programs, and
1415 wakeup from Alarm.
1416
1417 This driver can also be build as a module. If so, the module
1418 will be called rtc-s3c.
1419
1420config RTC_DRV_EP93XX
1421 tristate "Cirrus Logic EP93XX"
1422 depends on ARCH_EP93XX || COMPILE_TEST
1423 help
1424 If you say yes here you get support for the
1425 RTC embedded in the Cirrus Logic EP93XX processors.
1426
1427 This driver can also be built as a module. If so, the module
1428 will be called rtc-ep93xx.
1429
1430config RTC_DRV_SA1100
1431 tristate "SA11x0/PXA2xx/PXA910"
1432 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1433 help
1434 If you say Y here you will get access to the real time clock
1435 built into your SA11x0 or PXA2xx CPU.
1436
1437 To compile this driver as a module, choose M here: the
1438 module will be called rtc-sa1100.
1439
1440config RTC_DRV_SH
1441 tristate "SuperH On-Chip RTC"
1442 depends on SUPERH || ARCH_RENESAS
1443 help
1444 Say Y here to enable support for the on-chip RTC found in
1445 most SuperH processors. This RTC is also found in RZ/A SoCs.
1446
1447 To compile this driver as a module, choose M here: the
1448 module will be called rtc-sh.
1449
1450config RTC_DRV_SUNPLUS
1451 tristate "Sunplus SP7021 RTC"
1452 depends on SOC_SP7021
1453 help
1454 Say 'yes' to get support for the real-time clock present in
1455 Sunplus SP7021 - a SoC for industrial applications. It provides
1456 RTC status check, timer/alarm functionalities, user data
1457 reservation with the battery over 2.5V, RTC power status check
1458 and battery charge.
1459
1460 This driver can also be built as a module. If so, the module
1461 will be called rtc-sunplus.
1462
1463config RTC_DRV_PL030
1464 tristate "ARM AMBA PL030 RTC"
1465 depends on ARM_AMBA
1466 help
1467 If you say Y here you will get access to ARM AMBA
1468 PrimeCell PL030 RTC found on certain ARM SOCs.
1469
1470 To compile this driver as a module, choose M here: the
1471 module will be called rtc-pl030.
1472
1473config RTC_DRV_PL031
1474 tristate "ARM AMBA PL031 RTC"
1475 depends on ARM_AMBA
1476 help
1477 If you say Y here you will get access to ARM AMBA
1478 PrimeCell PL031 RTC found on certain ARM SOCs.
1479
1480 To compile this driver as a module, choose M here: the
1481 module will be called rtc-pl031.
1482
1483config RTC_DRV_AT91RM9200
1484 tristate "AT91RM9200 or some AT91SAM9 RTC"
1485 depends on ARCH_AT91 || COMPILE_TEST
1486 depends on OF
1487 help
1488 Driver for the internal RTC (Realtime Clock) module found on
1489 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1490 this is powered by the backup power supply.
1491
1492config RTC_DRV_AT91SAM9
1493 tristate "AT91SAM9 RTT as RTC"
1494 depends on ARCH_AT91 || COMPILE_TEST
1495 depends on OF && HAS_IOMEM
1496 select MFD_SYSCON
1497 help
1498 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1499 can be used as an RTC thanks to the backup power supply (e.g. a
1500 small coin cell battery) which keeps this block and the GPBR
1501 (General Purpose Backup Registers) block powered when the device
1502 is shutdown.
1503 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1504 probably want to use the real RTC block instead of the "RTT as an
1505 RTC" driver.
1506
1507config RTC_DRV_AU1XXX
1508 tristate "Au1xxx Counter0 RTC support"
1509 depends on MIPS_ALCHEMY
1510 help
1511 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1512 counter) to be used as a RTC.
1513
1514 This driver can also be built as a module. If so, the module
1515 will be called rtc-au1xxx.
1516
1517config RTC_DRV_RS5C313
1518 tristate "Ricoh RS5C313"
1519 depends on SH_LANDISK
1520 help
1521 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1522
1523config RTC_DRV_RZN1
1524 tristate "Renesas RZ/N1 RTC"
1525 depends on ARCH_RZN1 || COMPILE_TEST
1526 depends on OF && HAS_IOMEM
1527 help
1528 If you say yes here you get support for the Renesas RZ/N1 RTC.
1529
1530config RTC_DRV_GENERIC
1531 tristate "Generic RTC support"
1532 # Please consider writing a new RTC driver instead of using the generic
1533 # RTC abstraction
1534 depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST
1535 help
1536 Say Y or M here to enable RTC support on systems using the generic
1537 RTC abstraction. If you do not know what you are doing, you should
1538 just say Y.
1539
1540config RTC_DRV_PXA
1541 tristate "PXA27x/PXA3xx"
1542 depends on ARCH_PXA
1543 select RTC_DRV_SA1100
1544 help
1545 If you say Y here you will get access to the real time clock
1546 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1547 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1548
1549 This RTC driver uses PXA RTC registers available since pxa27x
1550 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1551
1552config RTC_DRV_VT8500
1553 tristate "VIA/WonderMedia 85xx SoC RTC"
1554 depends on ARCH_VT8500 || COMPILE_TEST
1555 help
1556 If you say Y here you will get access to the real time clock
1557 built into your VIA VT8500 SoC or its relatives.
1558
1559
1560config RTC_DRV_SUN4V
1561 bool "SUN4V Hypervisor RTC"
1562 depends on SPARC64
1563 help
1564 If you say Y here you will get support for the Hypervisor
1565 based RTC on SUN4V systems.
1566
1567config RTC_DRV_SUN6I
1568 bool "Allwinner A31 RTC"
1569 default MACH_SUN6I || MACH_SUN8I
1570 depends on COMMON_CLK
1571 depends on ARCH_SUNXI || COMPILE_TEST
1572 help
1573 If you say Y here you will get support for the RTC found in
1574 some Allwinner SoCs like the A31 or the A64.
1575
1576config RTC_DRV_SUNXI
1577 tristate "Allwinner sun4i/sun7i RTC"
1578 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1579 help
1580 If you say Y here you will get support for the RTC found on
1581 Allwinner A10/A20.
1582
1583config RTC_DRV_STARFIRE
1584 bool "Starfire RTC"
1585 depends on SPARC64
1586 help
1587 If you say Y here you will get support for the RTC found on
1588 Starfire systems.
1589
1590config RTC_DRV_MV
1591 tristate "Marvell SoC RTC"
1592 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1593 help
1594 If you say yes here you will get support for the in-chip RTC
1595 that can be found in some of Marvell's SoC devices, such as
1596 the Kirkwood 88F6281 and 88F6192.
1597
1598 This driver can also be built as a module. If so, the module
1599 will be called rtc-mv.
1600
1601config RTC_DRV_ARMADA38X
1602 tristate "Armada 38x Marvell SoC RTC"
1603 depends on ARCH_MVEBU || COMPILE_TEST
1604 depends on OF
1605 help
1606 If you say yes here you will get support for the in-chip RTC
1607 that can be found in the Armada 38x Marvell's SoC device
1608
1609 This driver can also be built as a module. If so, the module
1610 will be called armada38x-rtc.
1611
1612config RTC_DRV_CADENCE
1613 tristate "Cadence RTC driver"
1614 depends on OF && HAS_IOMEM
1615 help
1616 If you say Y here you will get access to Cadence RTC IP
1617 found on certain SOCs.
1618
1619 To compile this driver as a module, choose M here: the
1620 module will be called rtc-cadence.
1621
1622config RTC_DRV_FTRTC010
1623 tristate "Faraday Technology FTRTC010 RTC"
1624 depends on HAS_IOMEM
1625 default ARCH_GEMINI
1626 help
1627 If you say Y here you will get support for the
1628 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1629
1630 This driver can also be built as a module. If so, the module
1631 will be called rtc-ftrtc010.
1632
1633config RTC_DRV_PS3
1634 tristate "PS3 RTC"
1635 depends on PPC_PS3
1636 help
1637 If you say yes here you will get support for the RTC on PS3.
1638
1639 This driver can also be built as a module. If so, the module
1640 will be called rtc-ps3.
1641
1642config RTC_DRV_STMP
1643 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1644 depends on ARCH_MXS || COMPILE_TEST
1645 select STMP_DEVICE
1646 help
1647 If you say yes here you will get support for the onboard
1648 STMP3xxx/i.MX23/i.MX28 RTC.
1649
1650 This driver can also be built as a module. If so, the module
1651 will be called rtc-stmp3xxx.
1652
1653config RTC_DRV_PCAP
1654 tristate "PCAP RTC"
1655 depends on EZX_PCAP
1656 help
1657 If you say Y here you will get support for the RTC found on
1658 the PCAP2 ASIC used on some Motorola phones.
1659
1660config RTC_DRV_MC13XXX
1661 depends on MFD_MC13XXX
1662 tristate "Freescale MC13xxx RTC"
1663 help
1664 This enables support for the RTCs found on Freescale's PMICs
1665 MC13783 and MC13892.
1666
1667config RTC_DRV_MPC5121
1668 tristate "Freescale MPC5121 built-in RTC"
1669 depends on PPC_MPC512x || PPC_MPC52xx
1670 help
1671 If you say yes here you will get support for the
1672 built-in RTC on MPC5121 or on MPC5200.
1673
1674 This driver can also be built as a module. If so, the module
1675 will be called rtc-mpc5121.
1676
1677config RTC_DRV_JZ4740
1678 tristate "Ingenic JZ4740 SoC"
1679 depends on MIPS || COMPILE_TEST
1680 depends on OF && COMMON_CLK
1681 help
1682 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1683 controllers.
1684
1685 This driver can also be built as a module. If so, the module
1686 will be called rtc-jz4740.
1687
1688config RTC_DRV_LPC24XX
1689 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1690 depends on ARCH_LPC18XX || COMPILE_TEST
1691 depends on OF && HAS_IOMEM
1692 help
1693 This enables support for the NXP RTC found which can be found on
1694 NXP LPC178x/18xx/408x/43xx devices.
1695
1696 If you have one of the devices above enable this driver to use
1697 the hardware RTC. This driver can also be built as a module. If
1698 so, the module will be called rtc-lpc24xx.
1699
1700config RTC_DRV_LPC32XX
1701 depends on ARCH_LPC32XX || COMPILE_TEST
1702 tristate "NXP LPC32XX RTC"
1703 help
1704 This enables support for the NXP RTC in the LPC32XX
1705
1706 This driver can also be built as a module. If so, the module
1707 will be called rtc-lpc32xx.
1708
1709config RTC_DRV_PM8XXX
1710 tristate "Qualcomm PMIC8XXX RTC"
1711 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1712 help
1713 If you say yes here you get support for the
1714 Qualcomm PMIC8XXX RTC.
1715
1716 To compile this driver as a module, choose M here: the
1717 module will be called rtc-pm8xxx.
1718
1719config RTC_DRV_TEGRA
1720 tristate "NVIDIA Tegra Internal RTC driver"
1721 depends on ARCH_TEGRA || COMPILE_TEST
1722 help
1723 If you say yes here you get support for the
1724 Tegra 200 series internal RTC module.
1725
1726 This drive can also be built as a module. If so, the module
1727 will be called rtc-tegra.
1728
1729config RTC_DRV_LOONGSON1
1730 tristate "loongson1 RTC support"
1731 depends on MACH_LOONGSON32
1732 help
1733 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1734 counter) to be used as a RTC.
1735
1736 This driver can also be built as a module. If so, the module
1737 will be called rtc-ls1x.
1738
1739config RTC_DRV_MXC
1740 tristate "Freescale MXC Real Time Clock"
1741 depends on ARCH_MXC || COMPILE_TEST
1742 depends on HAS_IOMEM
1743 depends on OF
1744 help
1745 If you say yes here you get support for the Freescale MXC
1746 RTC module.
1747
1748 This driver can also be built as a module, if so, the module
1749 will be called "rtc-mxc".
1750
1751config RTC_DRV_MXC_V2
1752 tristate "Freescale MXC Real Time Clock for i.MX53"
1753 depends on ARCH_MXC || COMPILE_TEST
1754 depends on HAS_IOMEM
1755 depends on OF
1756 help
1757 If you say yes here you get support for the Freescale MXC
1758 SRTC module in i.MX53 processor.
1759
1760 This driver can also be built as a module, if so, the module
1761 will be called "rtc-mxc_v2".
1762
1763config RTC_DRV_SNVS
1764 tristate "Freescale SNVS RTC support"
1765 select REGMAP_MMIO
1766 depends on ARCH_MXC || COMPILE_TEST
1767 depends on HAS_IOMEM
1768 depends on OF
1769 help
1770 If you say yes here you get support for the Freescale SNVS
1771 Low Power (LP) RTC module.
1772
1773 This driver can also be built as a module, if so, the module
1774 will be called "rtc-snvs".
1775
1776config RTC_DRV_BBNSM
1777 tristate "NXP BBNSM RTC support"
1778 select REGMAP_MMIO
1779 depends on ARCH_MXC || COMPILE_TEST
1780 depends on HAS_IOMEM
1781 depends on OF
1782 help
1783 If you say yes here you get support for the NXP BBNSM RTC module.
1784
1785 This driver can also be built as a module, if so, the module
1786 will be called "rtc-bbnsm".
1787
1788config RTC_DRV_IMX_SC
1789 depends on IMX_SCU
1790 depends on HAVE_ARM_SMCCC
1791 tristate "NXP i.MX System Controller RTC support"
1792 help
1793 If you say yes here you get support for the NXP i.MX System
1794 Controller RTC module.
1795
1796config RTC_DRV_ST_LPC
1797 tristate "STMicroelectronics LPC RTC"
1798 depends on ARCH_STI
1799 depends on OF
1800 help
1801 Say Y here to include STMicroelectronics Low Power Controller
1802 (LPC) based RTC support.
1803
1804 To compile this driver as a module, choose M here: the
1805 module will be called rtc-st-lpc.
1806
1807config RTC_DRV_MOXART
1808 tristate "MOXA ART RTC"
1809 depends on ARCH_MOXART || COMPILE_TEST
1810 help
1811 If you say yes here you get support for the MOXA ART
1812 RTC module.
1813
1814 This driver can also be built as a module. If so, the module
1815 will be called rtc-moxart
1816
1817config RTC_DRV_MT2712
1818 tristate "MediaTek MT2712 SoC based RTC"
1819 depends on ARCH_MEDIATEK || COMPILE_TEST
1820 help
1821 This enables support for the real time clock built in the MediaTek
1822 SoCs for MT2712.
1823
1824 This drive can also be built as a module. If so, the module
1825 will be called rtc-mt2712.
1826
1827config RTC_DRV_MT6397
1828 tristate "MediaTek PMIC based RTC"
1829 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1830 help
1831 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1832 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1833 MediaTek(R) RTC driver.
1834
1835 If you want to use MediaTek(R) RTC interface, select Y or M here.
1836
1837config RTC_DRV_MT7622
1838 tristate "MediaTek SoC based RTC"
1839 depends on ARCH_MEDIATEK || COMPILE_TEST
1840 help
1841 This enables support for the real time clock built in the MediaTek
1842 SoCs.
1843
1844 This drive can also be built as a module. If so, the module
1845 will be called rtc-mt7622.
1846
1847config RTC_DRV_XGENE
1848 tristate "APM X-Gene RTC"
1849 depends on HAS_IOMEM
1850 depends on ARCH_XGENE || COMPILE_TEST
1851 help
1852 If you say yes here you get support for the APM X-Gene SoC real time
1853 clock.
1854
1855 This driver can also be built as a module, if so, the module
1856 will be called "rtc-xgene".
1857
1858config RTC_DRV_PIC32
1859 tristate "Microchip PIC32 RTC"
1860 depends on MACH_PIC32
1861 default y
1862 help
1863 If you say yes here you get support for the PIC32 RTC module.
1864
1865 This driver can also be built as a module. If so, the module
1866 will be called rtc-pic32
1867
1868config RTC_DRV_R7301
1869 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1870 select REGMAP_MMIO
1871 depends on OF && HAS_IOMEM
1872 help
1873 If you say yes here you get support for the EPSON TOYOCOM
1874 RTC-7301SF/DG chips.
1875
1876 This driver can also be built as a module. If so, the module
1877 will be called rtc-r7301.
1878
1879config RTC_DRV_STM32
1880 tristate "STM32 RTC"
1881 select REGMAP_MMIO
1882 depends on ARCH_STM32 || COMPILE_TEST
1883 help
1884 If you say yes here you get support for the STM32 On-Chip
1885 Real Time Clock.
1886
1887 This driver can also be built as a module, if so, the module
1888 will be called "rtc-stm32".
1889
1890config RTC_DRV_CPCAP
1891 depends on MFD_CPCAP
1892 tristate "Motorola CPCAP RTC"
1893 help
1894 Say y here for CPCAP rtc found on some Motorola phones
1895 and tablets such as Droid 4.
1896
1897config RTC_DRV_RTD119X
1898 bool "Realtek RTD129x RTC"
1899 depends on ARCH_REALTEK || COMPILE_TEST
1900 default ARCH_REALTEK
1901 help
1902 If you say yes here, you get support for the RTD1295 SoC
1903 Real Time Clock.
1904
1905config RTC_DRV_ASPEED
1906 tristate "ASPEED RTC"
1907 depends on OF
1908 depends on ARCH_ASPEED || COMPILE_TEST
1909 help
1910 If you say yes here you get support for the ASPEED BMC SoC real time
1911 clocks.
1912
1913 This driver can also be built as a module, if so, the module
1914 will be called "rtc-aspeed".
1915
1916config RTC_DRV_TI_K3
1917 tristate "TI K3 RTC"
1918 depends on ARCH_K3 || COMPILE_TEST
1919 select REGMAP_MMIO
1920 help
1921 If you say yes here you get support for the Texas Instruments's
1922 Real Time Clock for K3 architecture.
1923
1924 This driver can also be built as a module, if so, the module
1925 will be called "rtc-ti-k3".
1926
1927comment "HID Sensor RTC drivers"
1928
1929config RTC_DRV_HID_SENSOR_TIME
1930 tristate "HID Sensor Time"
1931 depends on USB_HID
1932 depends on HID_SENSOR_HUB && IIO
1933 select HID_SENSOR_IIO_COMMON
1934 help
1935 Say yes here to build support for the HID Sensors of type Time.
1936 This drivers makes such sensors available as RTCs.
1937
1938 If this driver is compiled as a module, it will be named
1939 rtc-hid-sensor-time.
1940
1941config RTC_DRV_GOLDFISH
1942 tristate "Goldfish Real Time Clock"
1943 depends on HAS_IOMEM
1944 help
1945 Say yes to enable RTC driver for the Goldfish based virtual platform.
1946
1947 Goldfish is a code name for the virtual platform developed by Google
1948 for Android emulation.
1949
1950config RTC_DRV_WILCO_EC
1951 tristate "Wilco EC RTC"
1952 depends on WILCO_EC
1953 default m
1954 help
1955 If you say yes here, you get read/write support for the Real Time
1956 Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook)
1957
1958 This can also be built as a module. If so, the module will
1959 be named "rtc_wilco_ec".
1960
1961config RTC_DRV_MSC313
1962 tristate "MStar MSC313 RTC"
1963 depends on ARCH_MSTARV7 || COMPILE_TEST
1964 help
1965 If you say yes here you get support for the Mstar MSC313e On-Chip
1966 Real Time Clock.
1967
1968 This driver can also be built as a module, if so, the module
1969 will be called "rtc-msc313".
1970
1971config RTC_DRV_POLARFIRE_SOC
1972 tristate "Microchip PolarFire SoC built-in RTC"
1973 depends on ARCH_MICROCHIP_POLARFIRE
1974 help
1975 If you say yes here you will get support for the
1976 built-in RTC on Polarfire SoC.
1977
1978 This driver can also be built as a module, if so, the module
1979 will be called "rtc-mpfs".
1980
1981endif # RTC_CLASS