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