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