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