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