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