Commit | Line | Data |
---|---|---|
7be2c7c9 | 1 | # |
c58411e9 AZ |
2 | # RTC class/drivers configuration |
3 | # | |
4 | ||
0c86edc0 | 5 | menu "Real Time Clock" |
9556fb73 | 6 | depends on !S390 |
0c86edc0 | 7 | |
c58411e9 | 8 | config RTC_LIB |
0c86edc0 AZ |
9 | tristate |
10 | ||
11 | config RTC_CLASS | |
12 | tristate "RTC class" | |
0c86edc0 AZ |
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 | |
27ae4104 | 18 | probably want to enable one or more of the interfaces below. |
0c86edc0 AZ |
19 | |
20 | This driver can also be built as a module. If so, the module | |
21 | will be called rtc-class. | |
22 | ||
23 | config 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 | |
32 | config 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 | ||
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. | |
0c86edc0 | 49 | |
9e86ecb6 DB |
50 | config 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 | ||
0c86edc0 AZ |
57 | comment "RTC interfaces" |
58 | depends on RTC_CLASS | |
59 | ||
c5c3e192 | 60 | config RTC_INTF_SYSFS |
e40659c5 | 61 | boolean "/sys/class/rtc/rtcN (sysfs)" |
c5c3e192 AZ |
62 | depends on RTC_CLASS && SYSFS |
63 | default RTC_CLASS | |
64 | help | |
9e86ecb6 DB |
65 | Say yes here if you want to use your RTCs using sysfs interfaces, |
66 | /sys/class/rtc/rtc0 through /sys/.../rtcN. | |
c5c3e192 AZ |
67 | |
68 | This driver can also be built as a module. If so, the module | |
69 | will be called rtc-sysfs. | |
70 | ||
728a2947 | 71 | config RTC_INTF_PROC |
e40659c5 | 72 | boolean "/proc/driver/rtc (procfs for rtc0)" |
728a2947 AZ |
73 | depends on RTC_CLASS && PROC_FS |
74 | default RTC_CLASS | |
75 | help | |
9e86ecb6 DB |
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. | |
728a2947 AZ |
79 | |
80 | This driver can also be built as a module. If so, the module | |
81 | will be called rtc-proc. | |
82 | ||
e824290e | 83 | config RTC_INTF_DEV |
e40659c5 | 84 | boolean "/dev/rtcN (character devices)" |
e824290e AZ |
85 | depends on RTC_CLASS |
86 | default RTC_CLASS | |
87 | help | |
9e86ecb6 DB |
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. | |
e824290e AZ |
93 | |
94 | This driver can also be built as a module. If so, the module | |
95 | will be called rtc-dev. | |
96 | ||
655066c3 AN |
97 | config RTC_INTF_DEV_UIE_EMUL |
98 | bool "RTC UIE emulation on dev interface" | |
99 | depends on RTC_INTF_DEV | |
100 | help | |
3dde6ad8 | 101 | Provides an emulation for RTC_UIE if the underlying rtc chip |
9e86ecb6 DB |
102 | driver does not expose RTC_UIE ioctls. Those requests generate |
103 | once-per-second update interrupts, used for synchronization. | |
655066c3 | 104 | |
09a21e56 AZ |
105 | config RTC_DRV_TEST |
106 | tristate "Test driver/device" | |
0c86edc0 | 107 | depends on RTC_CLASS |
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 | ||
120 | comment "I2C RTC drivers" | |
5663c14b | 121 | depends on RTC_CLASS && I2C |
1fec7c66 | 122 | |
1abb0dc9 | 123 | config RTC_DRV_DS1307 |
09a21e56 | 124 | tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00" |
1abb0dc9 DB |
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 | ||
09a21e56 AZ |
141 | config RTC_DRV_DS1672 |
142 | tristate "Dallas/Maxim DS1672" | |
143 | depends on RTC_CLASS && I2C | |
9bf5b4f5 AN |
144 | help |
145 | If you say yes here you get support for the | |
09a21e56 | 146 | Dallas/Maxim DS1672 timekeeping chip. |
9bf5b4f5 AN |
147 | |
148 | This driver can also be built as a module. If so, the module | |
09a21e56 | 149 | will be called rtc-ds1672. |
9bf5b4f5 | 150 | |
09a21e56 AZ |
151 | config RTC_DRV_MAX6900 |
152 | tristate "Maxim 6900" | |
7e56a7dc HVR |
153 | depends on RTC_CLASS && I2C |
154 | help | |
09a21e56 AZ |
155 | If you say yes here you will get support for the |
156 | Maxim MAX6900 I2C RTC chip. | |
7e56a7dc HVR |
157 | |
158 | This driver can also be built as a module. If so, the module | |
09a21e56 | 159 | will be called rtc-max6900. |
7e56a7dc | 160 | |
09a21e56 | 161 | config RTC_DRV_RS5C372 |
d815461c | 162 | tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A" |
edf1aaa3 AZ |
163 | depends on RTC_CLASS && I2C |
164 | help | |
165 | If you say yes here you get support for the | |
d815461c | 166 | Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. |
edf1aaa3 AZ |
167 | |
168 | This driver can also be built as a module. If so, the module | |
09a21e56 | 169 | will be called rtc-rs5c372. |
edf1aaa3 | 170 | |
09a21e56 AZ |
171 | config RTC_DRV_ISL1208 |
172 | tristate "Intersil 1208" | |
173 | depends on RTC_CLASS && I2C | |
5ec3e4b7 AN |
174 | help |
175 | If you say yes here you get support for the | |
09a21e56 | 176 | Intersil 1208 RTC chip. |
5ec3e4b7 AN |
177 | |
178 | This driver can also be built as a module. If so, the module | |
09a21e56 | 179 | will be called rtc-isl1208. |
5ec3e4b7 | 180 | |
09a21e56 AZ |
181 | config RTC_DRV_X1205 |
182 | tristate "Xicor/Intersil X1205" | |
183 | depends on RTC_CLASS && I2C | |
db68b189 | 184 | help |
09a21e56 AZ |
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. | |
db68b189 | 190 | |
b5a82d62 AZ |
191 | config 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 | ||
9c0c5705 L |
202 | config RTC_DRV_PCF8583 |
203 | tristate "Philips PCF8583" | |
09a21e56 | 204 | depends on RTC_CLASS && I2C |
9c0c5705 | 205 | help |
bb71f99f | 206 | If you say yes here you get support for the Philips PCF8583 |
09a21e56 | 207 | RTC chip found on Acorn RiscPCs. This driver supports the |
bb71f99f | 208 | platform specific method of retrieving the current year from |
09a21e56 AZ |
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. | |
9c0c5705 L |
211 | |
212 | This driver can also be built as a module. If so, the module | |
213 | will be called rtc-pcf8583. | |
214 | ||
caaff562 AN |
215 | config 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 | ||
617780d2 AN |
227 | config 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 | ||
09a21e56 | 234 | comment "SPI RTC drivers" |
5663c14b | 235 | depends on RTC_CLASS && SPI_MASTER |
09a21e56 | 236 | |
e0ac4761 AN |
237 | config RTC_DRV_RS5C348 |
238 | tristate "Ricoh RS5C348A/B" | |
5663c14b | 239 | depends on RTC_CLASS && SPI_MASTER |
e0ac4761 AN |
240 | help |
241 | If you say yes here you get support for the | |
242 | Ricoh RS5C348A and RS5C348B RTC chips. | |
243 | ||
244 | This driver can also be built as a module. If so, the module | |
245 | will be called rtc-rs5c348. | |
246 | ||
09a21e56 AZ |
247 | config RTC_DRV_MAX6902 |
248 | tristate "Maxim 6902" | |
5663c14b | 249 | depends on RTC_CLASS && SPI_MASTER |
09a21e56 AZ |
250 | help |
251 | If you say yes here you will get support for the | |
252 | Maxim MAX6902 SPI RTC chip. | |
253 | ||
254 | This driver can also be built as a module. If so, the module | |
255 | will be called rtc-max6902. | |
256 | ||
257 | comment "Platform RTC drivers" | |
258 | depends on RTC_CLASS | |
259 | ||
260 | # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> | |
261 | # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a | |
262 | # global rtc_lock ... it's not yet just another platform_device. | |
263 | ||
264 | config RTC_DRV_CMOS | |
265 | tristate "PC-style 'CMOS'" | |
266 | depends on RTC_CLASS && (X86 || ALPHA || ARM26 || ARM \ | |
57cc705f | 267 | || M32R || ATARI || PPC || MIPS) |
09a21e56 AZ |
268 | help |
269 | Say "yes" here to get direct support for the real time clock | |
270 | found in every PC or ACPI-based system, and some other boards. | |
271 | Specifically the original MC146818, compatibles like those in | |
272 | PC south bridges, the DS12887 or M48T86, some multifunction | |
273 | or LPC bus chips, and so on. | |
274 | ||
275 | Your system will need to define the platform device used by | |
276 | this driver, otherwise it won't be accessible. This means | |
277 | you can safely enable this driver if you don't know whether | |
278 | or not your board has this kind of hardware. | |
279 | ||
280 | This driver can also be built as a module. If so, the module | |
281 | will be called rtc-cmos. | |
282 | ||
283 | config RTC_DRV_DS1553 | |
284 | tristate "Dallas DS1553" | |
285 | depends on RTC_CLASS | |
7520b94d AZ |
286 | help |
287 | If you say yes here you get support for the | |
09a21e56 | 288 | Dallas DS1553 timekeeping chip. |
7520b94d AZ |
289 | |
290 | This driver can also be built as a module. If so, the module | |
09a21e56 AZ |
291 | will be called rtc-ds1553. |
292 | ||
293 | config RTC_DRV_DS1742 | |
294 | tristate "Dallas DS1742/1743" | |
295 | depends on RTC_CLASS | |
296 | help | |
297 | If you say yes here you get support for the | |
298 | Dallas DS1742/1743 timekeeping chip. | |
299 | ||
300 | This driver can also be built as a module. If so, the module | |
301 | will be called rtc-ds1742. | |
302 | ||
303 | config RTC_DRV_M48T86 | |
304 | tristate "ST M48T86/Dallas DS12887" | |
305 | depends on RTC_CLASS | |
306 | help | |
307 | If you say Y here you will get support for the | |
308 | ST M48T86 and Dallas DS12887 RTC chips. | |
309 | ||
310 | This driver can also be built as a module. If so, the module | |
311 | will be called rtc-m48t86. | |
312 | ||
2e774c7c MZ |
313 | config RTC_DRV_M48T59 |
314 | tristate "ST M48T59" | |
315 | depends on RTC_CLASS | |
316 | help | |
317 | If you say Y here you will get support for the | |
318 | ST M48T59 RTC chip. | |
319 | ||
320 | This driver can also be built as a module, if so, the module | |
321 | will be called "rtc-m48t59". | |
322 | ||
09a21e56 AZ |
323 | config RTC_DRV_V3020 |
324 | tristate "EM Microelectronic V3020" | |
325 | depends on RTC_CLASS | |
326 | help | |
327 | If you say yes here you will get support for the | |
328 | EM Microelectronic v3020 RTC chip. | |
329 | ||
330 | This driver can also be built as a module. If so, the module | |
331 | will be called rtc-v3020. | |
332 | ||
333 | comment "on-CPU RTC drivers" | |
334 | depends on RTC_CLASS | |
335 | ||
336 | config RTC_DRV_OMAP | |
337 | tristate "TI OMAP1" | |
338 | depends on RTC_CLASS && ( \ | |
339 | ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 ) | |
340 | help | |
341 | Say "yes" here to support the real time clock on TI OMAP1 chips. | |
342 | This driver can also be built as a module called rtc-omap. | |
7520b94d | 343 | |
1add6781 BD |
344 | config RTC_DRV_S3C |
345 | tristate "Samsung S3C series SoC RTC" | |
346 | depends on RTC_CLASS && ARCH_S3C2410 | |
347 | help | |
348 | RTC (Realtime Clock) driver for the clock inbuilt into the | |
349 | Samsung S3C24XX series of SoCs. This can provide periodic | |
350 | interrupt rates from 1Hz to 64Hz for user programs, and | |
351 | wakeup from Alarm. | |
352 | ||
353 | The driver currently supports the common features on all the | |
354 | S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 | |
355 | and S3C2442. | |
356 | ||
357 | This driver can also be build as a module. If so, the module | |
358 | will be called rtc-s3c. | |
359 | ||
fd507e2f AZ |
360 | config RTC_DRV_EP93XX |
361 | tristate "Cirrus Logic EP93XX" | |
362 | depends on RTC_CLASS && ARCH_EP93XX | |
363 | help | |
364 | If you say yes here you get support for the | |
365 | RTC embedded in the Cirrus Logic EP93XX processors. | |
366 | ||
367 | This driver can also be built as a module. If so, the module | |
368 | will be called rtc-ep93xx. | |
369 | ||
e842f1c8 RP |
370 | config RTC_DRV_SA1100 |
371 | tristate "SA11x0/PXA2xx" | |
372 | depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA) | |
373 | help | |
374 | If you say Y here you will get access to the real time clock | |
375 | built into your SA11x0 or PXA2xx CPU. | |
376 | ||
377 | To compile this driver as a module, choose M here: the | |
378 | module will be called rtc-sa1100. | |
fd507e2f | 379 | |
317a6104 PM |
380 | config RTC_DRV_SH |
381 | tristate "SuperH On-Chip RTC" | |
382 | depends on RTC_CLASS && SUPERH | |
383 | help | |
384 | Say Y here to enable support for the on-chip RTC found in | |
385 | most SuperH processors. | |
386 | ||
387 | To compile this driver as a module, choose M here: the | |
388 | module will be called rtc-sh. | |
389 | ||
8417eb7a | 390 | config RTC_DRV_VR41XX |
3e16f6af | 391 | tristate "NEC VR41XX" |
8417eb7a | 392 | depends on RTC_CLASS && CPU_VR41XX |
3e16f6af AZ |
393 | help |
394 | If you say Y here you will get access to the real time clock | |
395 | built into your NEC VR41XX CPU. | |
396 | ||
397 | To compile this driver as a module, choose M here: the | |
398 | module will be called rtc-vr41xx. | |
8417eb7a | 399 | |
8ae6e163 DS |
400 | config RTC_DRV_PL031 |
401 | tristate "ARM AMBA PL031 RTC" | |
402 | depends on RTC_CLASS && ARM_AMBA | |
403 | help | |
404 | If you say Y here you will get access to ARM AMBA | |
09a21e56 | 405 | PrimeCell PL031 RTC found on certain ARM SOCs. |
8ae6e163 DS |
406 | |
407 | To compile this driver as a module, choose M here: the | |
408 | module will be called rtc-pl031. | |
409 | ||
fa04e78b HCE |
410 | config RTC_DRV_AT32AP700X |
411 | tristate "AT32AP700X series RTC" | |
412 | depends on RTC_CLASS && PLATFORM_AT32AP | |
413 | help | |
414 | Driver for the internal RTC (Realtime Clock) on Atmel AVR32 | |
415 | AT32AP700x family processors. | |
416 | ||
7fc39f6d | 417 | config RTC_DRV_AT91RM9200 |
788b1fc6 AV |
418 | tristate "AT91RM9200" |
419 | depends on RTC_CLASS && ARCH_AT91RM9200 | |
420 | help | |
421 | Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock). | |
422 | ||
8cc75c9a WB |
423 | config RTC_DRV_BFIN |
424 | tristate "Blackfin On-Chip RTC" | |
425 | depends on RTC_CLASS && BFIN | |
426 | help | |
427 | If you say yes here you will get support for the | |
428 | Blackfin On-Chip Real Time Clock. | |
429 | ||
430 | This driver can also be built as a module. If so, the module | |
431 | will be called rtc-bfin. | |
432 | ||
e9f2bd81 NI |
433 | config RTC_DRV_RS5C313 |
434 | tristate "Ricoh RS5C313" | |
9a3f1d53 | 435 | depends on RTC_CLASS && SH_LANDISK |
e9f2bd81 NI |
436 | help |
437 | If you say yes here you get support for the Ricoh RS5C313 RTC chips. | |
438 | ||
0c86edc0 | 439 | endmenu |