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