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