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