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