xref: /linux/drivers/rtc/Kconfig (revision 8b4a40809e5330c9da5d20107d693d92d73b31dc)
1#
2# RTC class/drivers configuration
3#
4
5menu "Real Time Clock"
6	depends on !S390
7
8config RTC_LIB
9	tristate
10
11config RTC_CLASS
12	tristate "RTC class"
13	default n
14	select RTC_LIB
15	help
16	  Generic RTC class support. If you say yes here, you will
17 	  be allowed to plug one or more RTCs to your system. You will
18	  probably want to enable one or more of the interfaces below.
19
20	  This driver can also be built as a module. If so, the module
21	  will be called rtc-class.
22
23config RTC_HCTOSYS
24	bool "Set system time from RTC on startup and resume"
25	depends on RTC_CLASS = y
26	default y
27	help
28	  If you say yes here, the system time (wall clock) will be set using
29	  the value read from a specified RTC device. This is useful to avoid
30	  unnecessary fsck runs at boot time, and to network better.
31
32config RTC_HCTOSYS_DEVICE
33	string "RTC used to set the system time"
34	depends on RTC_HCTOSYS = y
35	default "rtc0"
36	help
37	  The RTC device that will be used to (re)initialize the system
38	  clock, usually rtc0.  Initialization is done when the system
39	  starts up, and when it resumes from a low power state.
40
41	  This clock should be battery-backed, so that it reads the correct
42	  time when the system boots from a power-off state.  Otherwise, your
43	  system will need an external clock source (like an NTP server).
44
45	  If the clock you specify here is not battery backed, it may still
46	  be useful to reinitialize system time when resuming from system
47	  sleep states.  Do not specify an RTC here unless it stays powered
48	  during all this system's supported sleep states.
49
50config RTC_DEBUG
51	bool "RTC debug support"
52	depends on RTC_CLASS = y
53	help
54	  Say yes here to enable debugging support in the RTC framework
55	  and individual RTC drivers.
56
57comment "RTC interfaces"
58	depends on RTC_CLASS
59
60config RTC_INTF_SYSFS
61	boolean "/sys/class/rtc/rtcN (sysfs)"
62	depends on RTC_CLASS && SYSFS
63	default RTC_CLASS
64	help
65	  Say yes here if you want to use your RTCs using sysfs interfaces,
66	  /sys/class/rtc/rtc0 through /sys/.../rtcN.
67
68	  This driver can also be built as a module. If so, the module
69	  will be called rtc-sysfs.
70
71config RTC_INTF_PROC
72	boolean "/proc/driver/rtc (procfs for rtc0)"
73	depends on RTC_CLASS && PROC_FS
74	default RTC_CLASS
75	help
76	  Say yes here if you want to use your first RTC through the proc
77	  interface, /proc/driver/rtc.  Other RTCs will not be available
78	  through that API.
79
80	  This driver can also be built as a module. If so, the module
81	  will be called rtc-proc.
82
83config RTC_INTF_DEV
84	boolean "/dev/rtcN (character devices)"
85	depends on RTC_CLASS
86	default RTC_CLASS
87	help
88	  Say yes here if you want to use your RTCs using the /dev
89	  interfaces, which "udev" sets up as /dev/rtc0 through
90	  /dev/rtcN.  You may want to set up a symbolic link so one
91	  of these can be accessed as /dev/rtc, which is a name
92	  expected by "hwclock" and some other programs.
93
94	  This driver can also be built as a module. If so, the module
95	  will be called rtc-dev.
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
105config RTC_DRV_TEST
106	tristate "Test driver/device"
107	depends on RTC_CLASS
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 RTC_CLASS && I2C
122
123config RTC_DRV_DS1307
124	tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00"
125	depends on RTC_CLASS && I2C
126	help
127	  If you say yes here you get support for various compatible RTC
128	  chips (often with battery backup) connected with I2C.  This driver
129	  should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
130	  and probably other chips.  In some cases the RTC must already
131	  have been initialized (by manufacturing or a bootloader).
132
133	  The first seven registers on these chips hold an RTC, and other
134	  registers may add features such as NVRAM, a trickle charger for
135	  the RTC/NVRAM backup power, and alarms.  This driver may not
136	  expose all those available chip features.
137
138	  This driver can also be built as a module. If so, the module
139	  will be called rtc-ds1307.
140
141config RTC_DRV_DS1672
142	tristate "Dallas/Maxim DS1672"
143	depends on RTC_CLASS && I2C
144	help
145	  If you say yes here you get support for the
146	  Dallas/Maxim DS1672 timekeeping chip.
147
148	  This driver can also be built as a module. If so, the module
149	  will be called rtc-ds1672.
150
151config RTC_DRV_MAX6900
152	tristate "Maxim 6900"
153	depends on RTC_CLASS && I2C
154	help
155	  If you say yes here you will get support for the
156	  Maxim MAX6900 I2C RTC chip.
157
158	  This driver can also be built as a module. If so, the module
159	  will be called rtc-max6900.
160
161config RTC_DRV_RS5C372
162	tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A"
163	depends on RTC_CLASS && I2C
164	help
165	  If you say yes here you get support for the
166	  Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
167
168	  This driver can also be built as a module. If so, the module
169	  will be called rtc-rs5c372.
170
171config RTC_DRV_ISL1208
172	tristate "Intersil 1208"
173	depends on RTC_CLASS && I2C
174	help
175	  If you say yes here you get support for the
176	  Intersil 1208 RTC chip.
177
178	  This driver can also be built as a module. If so, the module
179	  will be called rtc-isl1208.
180
181config RTC_DRV_X1205
182	tristate "Xicor/Intersil X1205"
183	depends on RTC_CLASS && I2C
184	help
185	  If you say yes here you get support for the
186	  Xicor/Intersil X1205 RTC chip.
187
188	  This driver can also be built as a module. If so, the module
189	  will be called rtc-x1205.
190
191config RTC_DRV_PCF8563
192	tristate "Philips PCF8563/Epson RTC8564"
193	depends on RTC_CLASS && I2C
194	help
195	  If you say yes here you get support for the
196	  Philips PCF8563 RTC chip. The Epson RTC8564
197	  should work as well.
198
199	  This driver can also be built as a module. If so, the module
200	  will be called rtc-pcf8563.
201
202config RTC_DRV_PCF8583
203	tristate "Philips PCF8583"
204	depends on RTC_CLASS && I2C
205	help
206	  If you say yes here you get support for the Philips PCF8583
207	  RTC chip found on Acorn RiscPCs. This driver supports the
208	  platform specific method of retrieving the current year from
209	  the RTC's SRAM. It will work on other platforms with the same
210	  chip, but the year will probably have to be tweaked.
211
212	  This driver can also be built as a module. If so, the module
213	  will be called rtc-pcf8583.
214
215config RTC_DRV_M41T80
216	tristate "ST M41T80 series RTC"
217	depends on RTC_CLASS && I2C
218	help
219	  If you say Y here you will get support for the
220	  ST M41T80 RTC chips series. Currently following chips are
221	  supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85
222	  and M41ST87.
223
224	  This driver can also be built as a module. If so, the module
225	  will be called rtc-m41t80.
226
227config RTC_DRV_M41T80_WDT
228	bool "ST M41T80 series RTC watchdog timer"
229	depends on RTC_DRV_M41T80
230	help
231	  If you say Y here you will get support for the
232	  watchdog timer in ST M41T80 RTC chips series.
233
234config RTC_DRV_TWL92330
235	boolean "TI TWL92330/Menelaus"
236	depends on RTC_CLASS && I2C && MENELAUS
237	help
238	  If you say yes here you get support for the RTC on the
239	  TWL92330 "Menelaus" power mangement chip, used with OMAP2
240	  platforms.  The support is integrated with the rest of
241	  the Menelaus driver; it's not separate module.
242
243comment "SPI RTC drivers"
244	depends on RTC_CLASS && SPI_MASTER
245
246config RTC_DRV_RS5C348
247	tristate "Ricoh RS5C348A/B"
248	depends on RTC_CLASS && SPI_MASTER
249	help
250	  If you say yes here you get support for the
251	  Ricoh RS5C348A and RS5C348B RTC chips.
252
253	  This driver can also be built as a module. If so, the module
254	  will be called rtc-rs5c348.
255
256config RTC_DRV_MAX6902
257	tristate "Maxim 6902"
258	depends on RTC_CLASS && SPI_MASTER
259	help
260	  If you say yes here you will get support for the
261	  Maxim MAX6902 SPI RTC chip.
262
263	  This driver can also be built as a module. If so, the module
264	  will be called rtc-max6902.
265
266comment "Platform RTC drivers"
267	depends on RTC_CLASS
268
269# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
270# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
271# global rtc_lock ... it's not yet just another platform_device.
272
273config RTC_DRV_CMOS
274	tristate "PC-style 'CMOS'"
275	depends on RTC_CLASS && (X86 || ALPHA || ARM26 || ARM \
276		|| M32R || ATARI || PPC || MIPS)
277	help
278	  Say "yes" here to get direct support for the real time clock
279	  found in every PC or ACPI-based system, and some other boards.
280	  Specifically the original MC146818, compatibles like those in
281	  PC south bridges, the DS12887 or M48T86, some multifunction
282	  or LPC bus chips, and so on.
283
284	  Your system will need to define the platform device used by
285	  this driver, otherwise it won't be accessible.  This means
286	  you can safely enable this driver if you don't know whether
287	  or not your board has this kind of hardware.
288
289	  This driver can also be built as a module. If so, the module
290	  will be called rtc-cmos.
291
292config RTC_DRV_DS1216
293	tristate "Dallas DS1216"
294	depends on RTC_CLASS && SNI_RM
295	help
296	  If you say yes here you get support for the Dallas DS1216 RTC chips.
297
298config RTC_DRV_DS1553
299	tristate "Dallas DS1553"
300	depends on RTC_CLASS
301	help
302	  If you say yes here you get support for the
303	  Dallas DS1553 timekeeping chip.
304
305	  This driver can also be built as a module. If so, the module
306	  will be called rtc-ds1553.
307
308config RTC_DRV_DS1742
309	tristate "Dallas DS1742/1743"
310	depends on RTC_CLASS
311	help
312	  If you say yes here you get support for the
313	  Dallas DS1742/1743 timekeeping chip.
314
315	  This driver can also be built as a module. If so, the module
316	  will be called rtc-ds1742.
317
318config RTC_DRV_M48T86
319	tristate "ST M48T86/Dallas DS12887"
320	depends on RTC_CLASS
321	help
322	  If you say Y here you will get support for the
323	  ST M48T86 and Dallas DS12887 RTC chips.
324
325	  This driver can also be built as a module. If so, the module
326	  will be called rtc-m48t86.
327
328config RTC_DRV_M48T59
329	tristate "ST M48T59"
330	depends on RTC_CLASS
331	help
332	  If you say Y here you will get support for the
333	  ST M48T59 RTC chip.
334
335	  This driver can also be built as a module, if so, the module
336	  will be called "rtc-m48t59".
337
338config RTC_DRV_V3020
339	tristate "EM Microelectronic V3020"
340	depends on RTC_CLASS
341	help
342	  If you say yes here you will get support for the
343	  EM Microelectronic v3020 RTC chip.
344
345	  This driver can also be built as a module. If so, the module
346	  will be called rtc-v3020.
347
348comment "on-CPU RTC drivers"
349	depends on RTC_CLASS
350
351config RTC_DRV_OMAP
352	tristate "TI OMAP1"
353	depends on RTC_CLASS && ( \
354		ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 )
355	help
356	  Say "yes" here to support the real time clock on TI OMAP1 chips.
357	  This driver can also be built as a module called rtc-omap.
358
359config RTC_DRV_S3C
360	tristate "Samsung S3C series SoC RTC"
361	depends on RTC_CLASS && ARCH_S3C2410
362	help
363	  RTC (Realtime Clock) driver for the clock inbuilt into the
364	  Samsung S3C24XX series of SoCs. This can provide periodic
365	  interrupt rates from 1Hz to 64Hz for user programs, and
366	  wakeup from Alarm.
367
368	  The driver currently supports the common features on all the
369	  S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
370	  and S3C2442.
371
372	  This driver can also be build as a module. If so, the module
373	  will be called rtc-s3c.
374
375config RTC_DRV_EP93XX
376	tristate "Cirrus Logic EP93XX"
377	depends on RTC_CLASS && ARCH_EP93XX
378	help
379	  If you say yes here you get support for the
380	  RTC embedded in the Cirrus Logic EP93XX processors.
381
382	  This driver can also be built as a module. If so, the module
383	  will be called rtc-ep93xx.
384
385config RTC_DRV_SA1100
386	tristate "SA11x0/PXA2xx"
387	depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA)
388	help
389	  If you say Y here you will get access to the real time clock
390	  built into your SA11x0 or PXA2xx CPU.
391
392	  To compile this driver as a module, choose M here: the
393	  module will be called rtc-sa1100.
394
395config RTC_DRV_SH
396	tristate "SuperH On-Chip RTC"
397	depends on RTC_CLASS && SUPERH
398	help
399	  Say Y here to enable support for the on-chip RTC found in
400	  most SuperH processors.
401
402 	  To compile this driver as a module, choose M here: the
403	  module will be called rtc-sh.
404
405config RTC_DRV_VR41XX
406	tristate "NEC VR41XX"
407	depends on RTC_CLASS && CPU_VR41XX
408	help
409	  If you say Y here you will get access to the real time clock
410	  built into your NEC VR41XX CPU.
411
412	  To compile this driver as a module, choose M here: the
413	  module will be called rtc-vr41xx.
414
415config RTC_DRV_PL031
416	tristate "ARM AMBA PL031 RTC"
417	depends on RTC_CLASS && ARM_AMBA
418	help
419	  If you say Y here you will get access to ARM AMBA
420	  PrimeCell PL031 RTC found on certain ARM SOCs.
421
422	  To compile this driver as a module, choose M here: the
423	  module will be called rtc-pl031.
424
425config RTC_DRV_AT32AP700X
426	tristate "AT32AP700X series RTC"
427	depends on RTC_CLASS && PLATFORM_AT32AP
428	help
429	  Driver for the internal RTC (Realtime Clock) on Atmel AVR32
430	  AT32AP700x family processors.
431
432config RTC_DRV_AT91RM9200
433	tristate "AT91RM9200"
434	depends on RTC_CLASS && ARCH_AT91RM9200
435	help
436	  Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).
437
438config RTC_DRV_BFIN
439	tristate "Blackfin On-Chip RTC"
440	depends on RTC_CLASS && BFIN
441	help
442	  If you say yes here you will get support for the
443	  Blackfin On-Chip Real Time Clock.
444
445	  This driver can also be built as a module. If so, the module
446	  will be called rtc-bfin.
447
448config RTC_DRV_RS5C313
449	tristate "Ricoh RS5C313"
450	depends on RTC_CLASS && SH_LANDISK
451	help
452	  If you say yes here you get support for the Ricoh RS5C313 RTC chips.
453
454endmenu
455