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