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