blob: 5e439836db2d534da615ff0114d9358ad9c7b5fd [file] [log] [blame]
David Brownell7be2c7c2007-02-10 01:46:02 -08001#
Alessandro Zummoc58411e2006-03-27 01:16:34 -08002# RTC class/drivers configuration
3#
4
Alessandro Zummo0c86edc2006-03-27 01:16:37 -08005menu "Real Time Clock"
6
Alessandro Zummoc58411e2006-03-27 01:16:34 -08007config RTC_LIB
Alessandro Zummo0c86edc2006-03-27 01:16:37 -08008 tristate
9
10config RTC_CLASS
11 tristate "RTC class"
12 depends on EXPERIMENTAL
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
Adrian Bunk27ae4102006-06-30 18:18:41 +020018 probably want to enable one or more of the interfaces below.
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080019
20 This driver can also be built as a module. If so, the module
21 will be called rtc-class.
22
23config RTC_HCTOSYS
David Brownell7ca1d482007-05-08 00:33:42 -070024 bool "Set system time from RTC on startup and resume"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080025 depends on RTC_CLASS = y
26 default y
27 help
David Brownell7ca1d482007-05-08 00:33:42 -070028 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.
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080031
32config RTC_HCTOSYS_DEVICE
David Brownell7ca1d482007-05-08 00:33:42 -070033 string "RTC used to set the system time"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080034 depends on RTC_HCTOSYS = y
35 default "rtc0"
36 help
David Brownell7ca1d482007-05-08 00:33:42 -070037 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.
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080049
David Brownell9e86ecb2006-09-30 23:28:14 -070050config 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
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080057comment "RTC interfaces"
58 depends on RTC_CLASS
59
Alessandro Zummoc5c3e192006-03-27 01:16:39 -080060config RTC_INTF_SYSFS
David Brownell446ecbd2007-05-08 00:33:33 -070061 boolean "sysfs"
Alessandro Zummoc5c3e192006-03-27 01:16:39 -080062 depends on RTC_CLASS && SYSFS
63 default RTC_CLASS
64 help
David Brownell9e86ecb2006-09-30 23:28:14 -070065 Say yes here if you want to use your RTCs using sysfs interfaces,
66 /sys/class/rtc/rtc0 through /sys/.../rtcN.
Alessandro Zummoc5c3e192006-03-27 01:16:39 -080067
68 This driver can also be built as a module. If so, the module
69 will be called rtc-sysfs.
70
Alessandro Zummo728a2942006-03-27 01:16:40 -080071config RTC_INTF_PROC
David Brownell7d9f99e2007-05-08 00:33:38 -070072 boolean "proc"
Alessandro Zummo728a2942006-03-27 01:16:40 -080073 depends on RTC_CLASS && PROC_FS
74 default RTC_CLASS
75 help
David Brownell9e86ecb2006-09-30 23:28:14 -070076 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.
Alessandro Zummo728a2942006-03-27 01:16:40 -080079
80 This driver can also be built as a module. If so, the module
81 will be called rtc-proc.
82
Alessandro Zummoe8242902006-03-27 01:16:41 -080083config RTC_INTF_DEV
David Brownell5726fb22007-05-08 00:33:27 -070084 boolean "dev"
Alessandro Zummoe8242902006-03-27 01:16:41 -080085 depends on RTC_CLASS
86 default RTC_CLASS
87 help
David Brownell9e86ecb2006-09-30 23:28:14 -070088 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.
Alessandro Zummoe8242902006-03-27 01:16:41 -080093
94 This driver can also be built as a module. If so, the module
95 will be called rtc-dev.
96
Atsushi Nemoto655066c2006-06-25 05:48:17 -070097config 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 underlaying rtc chip
David Brownell9e86ecb2006-09-30 23:28:14 -0700102 driver does not expose RTC_UIE ioctls. Those requests generate
103 once-per-second update interrupts, used for synchronization.
Atsushi Nemoto655066c2006-06-25 05:48:17 -0700104
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700105config 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
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"
163 depends on RTC_CLASS && I2C
164 help
165 If you say yes here you get support for the
166 Ricoh RS5C372A and RS5C372B 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
215comment "SPI RTC drivers"
216 depends on RTC_CLASS
217
218config RTC_DRV_RS5C348
219 tristate "Ricoh RS5C348A/B"
220 depends on RTC_CLASS && SPI
221 help
222 If you say yes here you get support for the
223 Ricoh RS5C348A and RS5C348B RTC chips.
224
225 This driver can also be built as a module. If so, the module
226 will be called rtc-rs5c348.
227
228config RTC_DRV_MAX6902
229 tristate "Maxim 6902"
230 depends on RTC_CLASS && SPI
231 help
232 If you say yes here you will get support for the
233 Maxim MAX6902 SPI RTC chip.
234
235 This driver can also be built as a module. If so, the module
236 will be called rtc-max6902.
237
238comment "Platform RTC drivers"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -0800239 depends on RTC_CLASS
240
David Brownell7be2c7c2007-02-10 01:46:02 -0800241# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
242# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
243# global rtc_lock ... it's not yet just another platform_device.
244
245config RTC_DRV_CMOS
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700246 tristate "PC-style 'CMOS'"
Dave Jonesc0663322007-02-20 13:58:07 -0800247 depends on RTC_CLASS && (X86 || ALPHA || ARM26 || ARM \
David Brownell7be2c7c2007-02-10 01:46:02 -0800248 || M32R || ATARI || POWERPC)
249 help
250 Say "yes" here to get direct support for the real time clock
251 found in every PC or ACPI-based system, and some other boards.
252 Specifically the original MC146818, compatibles like those in
253 PC south bridges, the DS12887 or M48T86, some multifunction
254 or LPC bus chips, and so on.
255
256 Your system will need to define the platform device used by
257 this driver, otherwise it won't be accessible. This means
258 you can safely enable this driver if you don't know whether
259 or not your board has this kind of hardware.
260
261 This driver can also be built as a module. If so, the module
262 will be called rtc-cmos.
263
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700264config RTC_DRV_DS1553
265 tristate "Dallas DS1553"
266 depends on RTC_CLASS
267 help
268 If you say yes here you get support for the
269 Dallas DS1553 timekeeping chip.
270
271 This driver can also be built as a module. If so, the module
272 will be called rtc-ds1553.
273
Atsushi Nemoto5ec3e4b2006-06-25 05:48:29 -0700274config RTC_DRV_DS1742
Torsten Ertbjerg Rasmussenf9231a02006-12-06 20:39:41 -0800275 tristate "Dallas DS1742/1743"
Atsushi Nemoto5ec3e4b2006-06-25 05:48:29 -0700276 depends on RTC_CLASS
277 help
278 If you say yes here you get support for the
Torsten Ertbjerg Rasmussenf9231a02006-12-06 20:39:41 -0800279 Dallas DS1742/1743 timekeeping chip.
Atsushi Nemoto5ec3e4b2006-06-25 05:48:29 -0700280
281 This driver can also be built as a module. If so, the module
282 will be called rtc-ds1742.
283
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700284config RTC_DRV_M48T86
285 tristate "ST M48T86/Dallas DS12887"
286 depends on RTC_CLASS
287 help
288 If you say Y here you will get support for the
289 ST M48T86 and Dallas DS12887 RTC chips.
290
291 This driver can also be built as a module. If so, the module
292 will be called rtc-m48t86.
293
294config RTC_DRV_V3020
295 tristate "EM Microelectronic V3020"
296 depends on RTC_CLASS
297 help
298 If you say yes here you will get support for the
299 EM Microelectronic v3020 RTC chip.
300
301 This driver can also be built as a module. If so, the module
302 will be called rtc-v3020.
303
304comment "on-CPU RTC drivers"
305 depends on RTC_CLASS
306
David Brownelldb68b182006-12-06 20:38:36 -0800307config RTC_DRV_OMAP
308 tristate "TI OMAP1"
309 depends on RTC_CLASS && ( \
310 ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 )
311 help
312 Say "yes" here to support the real time clock on TI OMAP1 chips.
313 This driver can also be built as a module called rtc-omap.
314
Ben Dooks1add6782006-07-01 04:36:26 -0700315config RTC_DRV_S3C
316 tristate "Samsung S3C series SoC RTC"
317 depends on RTC_CLASS && ARCH_S3C2410
318 help
319 RTC (Realtime Clock) driver for the clock inbuilt into the
320 Samsung S3C24XX series of SoCs. This can provide periodic
321 interrupt rates from 1Hz to 64Hz for user programs, and
322 wakeup from Alarm.
323
324 The driver currently supports the common features on all the
325 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
326 and S3C2442.
327
328 This driver can also be build as a module. If so, the module
329 will be called rtc-s3c.
330
Alessandro Zummofd507e22006-03-27 01:16:45 -0800331config RTC_DRV_EP93XX
332 tristate "Cirrus Logic EP93XX"
333 depends on RTC_CLASS && ARCH_EP93XX
334 help
335 If you say yes here you get support for the
336 RTC embedded in the Cirrus Logic EP93XX processors.
337
338 This driver can also be built as a module. If so, the module
339 will be called rtc-ep93xx.
340
Richard Purdiee842f1c2006-03-27 01:16:46 -0800341config RTC_DRV_SA1100
342 tristate "SA11x0/PXA2xx"
343 depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA)
344 help
345 If you say Y here you will get access to the real time clock
346 built into your SA11x0 or PXA2xx CPU.
347
348 To compile this driver as a module, choose M here: the
349 module will be called rtc-sa1100.
Alessandro Zummofd507e22006-03-27 01:16:45 -0800350
Paul Mundt317a6102006-09-27 17:13:19 +0900351config RTC_DRV_SH
352 tristate "SuperH On-Chip RTC"
353 depends on RTC_CLASS && SUPERH
354 help
355 Say Y here to enable support for the on-chip RTC found in
356 most SuperH processors.
357
358 To compile this driver as a module, choose M here: the
359 module will be called rtc-sh.
360
Yoichi Yuasa8417eb72006-04-10 22:54:47 -0700361config RTC_DRV_VR41XX
Alessandro Zummo3e16f6a2006-04-10 22:54:48 -0700362 tristate "NEC VR41XX"
Yoichi Yuasa8417eb72006-04-10 22:54:47 -0700363 depends on RTC_CLASS && CPU_VR41XX
Alessandro Zummo3e16f6a2006-04-10 22:54:48 -0700364 help
365 If you say Y here you will get access to the real time clock
366 built into your NEC VR41XX CPU.
367
368 To compile this driver as a module, choose M here: the
369 module will be called rtc-vr41xx.
Yoichi Yuasa8417eb72006-04-10 22:54:47 -0700370
Deepak Saxena8ae6e162006-06-25 05:47:38 -0700371config RTC_DRV_PL031
372 tristate "ARM AMBA PL031 RTC"
373 depends on RTC_CLASS && ARM_AMBA
374 help
375 If you say Y here you will get access to ARM AMBA
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700376 PrimeCell PL031 RTC found on certain ARM SOCs.
Deepak Saxena8ae6e162006-06-25 05:47:38 -0700377
378 To compile this driver as a module, choose M here: the
379 module will be called rtc-pl031.
380
Andrew Victor7fc39f62006-12-10 02:19:03 -0800381config RTC_DRV_AT91RM9200
Andrew Victor788b1fc2006-06-25 05:48:27 -0700382 tristate "AT91RM9200"
383 depends on RTC_CLASS && ARCH_AT91RM9200
384 help
385 Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).
386
Wu, Bryan8cc75c92007-05-06 14:50:32 -0700387config RTC_DRV_BFIN
388 tristate "Blackfin On-Chip RTC"
389 depends on RTC_CLASS && BFIN
390 help
391 If you say yes here you will get support for the
392 Blackfin On-Chip Real Time Clock.
393
394 This driver can also be built as a module. If so, the module
395 will be called rtc-bfin.
396
Nobuhiro Iwamatsue9f2bd82007-05-08 00:26:37 -0700397config RTC_DRV_RS5C313
398 tristate "Ricoh RS5C313"
399 depends on RTC_CLASS && BROKEN
400 help
401 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
402
Alessandro Zummo0c86edc2006-03-27 01:16:37 -0800403endmenu