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