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