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