]>
Commit | Line | Data |
---|---|---|
7be2c7c9 | 1 | # |
c58411e9 AZ |
2 | # RTC class/drivers configuration |
3 | # | |
4 | ||
5 | config RTC_LIB | |
0c86edc0 AZ |
6 | tristate |
7 | ||
bb35fb20 JE |
8 | menuconfig 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 |
21 | if RTC_CLASS |
22 | ||
0c86edc0 | 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 | ||
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 |
53 | config 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 | 60 | comment "RTC interfaces" |
0c86edc0 | 61 | |
c5c3e192 | 62 | config 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 | 73 | config 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 | 85 | config 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 |
98 | config 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 |
106 | config 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 | ||
120 | comment "I2C RTC drivers" | |
bb35fb20 JE |
121 | depends on I2C |
122 | ||
123 | if I2C | |
1fec7c66 | 124 | |
1abb0dc9 | 125 | config 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 | ||
09a21e56 AZ |
142 | config RTC_DRV_DS1672 |
143 | tristate "Dallas/Maxim DS1672" | |
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 | 153 | help |
09a21e56 AZ |
154 | If you say yes here you will get support for the |
155 | Maxim MAX6900 I2C RTC chip. | |
7e56a7dc HVR |
156 | |
157 | This driver can also be built as a module. If so, the module | |
09a21e56 | 158 | will be called rtc-max6900. |
7e56a7dc | 159 | |
09a21e56 | 160 | config RTC_DRV_RS5C372 |
d815461c | 161 | tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A" |
edf1aaa3 AZ |
162 | help |
163 | If you say yes here you get support for the | |
d815461c | 164 | Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. |
edf1aaa3 AZ |
165 | |
166 | This driver can also be built as a module. If so, the module | |
09a21e56 | 167 | will be called rtc-rs5c372. |
edf1aaa3 | 168 | |
09a21e56 AZ |
169 | config RTC_DRV_ISL1208 |
170 | tristate "Intersil 1208" | |
5ec3e4b7 AN |
171 | help |
172 | If you say yes here you get support for the | |
09a21e56 | 173 | Intersil 1208 RTC chip. |
5ec3e4b7 AN |
174 | |
175 | This driver can also be built as a module. If so, the module | |
09a21e56 | 176 | will be called rtc-isl1208. |
5ec3e4b7 | 177 | |
09a21e56 AZ |
178 | config RTC_DRV_X1205 |
179 | tristate "Xicor/Intersil X1205" | |
db68b189 | 180 | help |
09a21e56 AZ |
181 | If you say yes here you get support for the |
182 | Xicor/Intersil X1205 RTC chip. | |
183 | ||
184 | This driver can also be built as a module. If so, the module | |
185 | will be called rtc-x1205. | |
db68b189 | 186 | |
b5a82d62 AZ |
187 | config RTC_DRV_PCF8563 |
188 | tristate "Philips PCF8563/Epson RTC8564" | |
b5a82d62 AZ |
189 | help |
190 | If you say yes here you get support for the | |
191 | Philips PCF8563 RTC chip. The Epson RTC8564 | |
192 | should work as well. | |
193 | ||
194 | This driver can also be built as a module. If so, the module | |
195 | will be called rtc-pcf8563. | |
196 | ||
9c0c5705 L |
197 | config RTC_DRV_PCF8583 |
198 | tristate "Philips PCF8583" | |
9c0c5705 | 199 | help |
bb71f99f | 200 | If you say yes here you get support for the Philips PCF8583 |
09a21e56 | 201 | RTC chip found on Acorn RiscPCs. This driver supports the |
bb71f99f | 202 | platform specific method of retrieving the current year from |
09a21e56 AZ |
203 | the RTC's SRAM. It will work on other platforms with the same |
204 | chip, but the year will probably have to be tweaked. | |
9c0c5705 L |
205 | |
206 | This driver can also be built as a module. If so, the module | |
207 | will be called rtc-pcf8583. | |
208 | ||
caaff562 AN |
209 | config RTC_DRV_M41T80 |
210 | tristate "ST M41T80 series RTC" | |
caaff562 AN |
211 | help |
212 | If you say Y here you will get support for the | |
213 | ST M41T80 RTC chips series. Currently following chips are | |
214 | supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85 | |
215 | and M41ST87. | |
216 | ||
217 | This driver can also be built as a module. If so, the module | |
218 | will be called rtc-m41t80. | |
219 | ||
617780d2 AN |
220 | config RTC_DRV_M41T80_WDT |
221 | bool "ST M41T80 series RTC watchdog timer" | |
222 | depends on RTC_DRV_M41T80 | |
223 | help | |
224 | If you say Y here you will get support for the | |
225 | watchdog timer in ST M41T80 RTC chips series. | |
226 | ||
0c4a59fe TL |
227 | config RTC_DRV_TWL92330 |
228 | boolean "TI TWL92330/Menelaus" | |
bb35fb20 | 229 | depends on MENELAUS |
0c4a59fe TL |
230 | help |
231 | If you say yes here you get support for the RTC on the | |
232 | TWL92330 "Menelaus" power mangement chip, used with OMAP2 | |
233 | platforms. The support is integrated with the rest of | |
234 | the Menelaus driver; it's not separate module. | |
235 | ||
bb35fb20 JE |
236 | endif # I2C |
237 | ||
09a21e56 | 238 | comment "SPI RTC drivers" |
bb35fb20 JE |
239 | |
240 | if SPI_MASTER | |
09a21e56 | 241 | |
e0ac4761 AN |
242 | config RTC_DRV_RS5C348 |
243 | tristate "Ricoh RS5C348A/B" | |
e0ac4761 AN |
244 | help |
245 | If you say yes here you get support for the | |
246 | Ricoh RS5C348A and RS5C348B RTC chips. | |
247 | ||
248 | This driver can also be built as a module. If so, the module | |
249 | will be called rtc-rs5c348. | |
250 | ||
09a21e56 AZ |
251 | config RTC_DRV_MAX6902 |
252 | tristate "Maxim 6902" | |
09a21e56 AZ |
253 | help |
254 | If you say yes here you will get support for the | |
255 | Maxim MAX6902 SPI RTC chip. | |
256 | ||
257 | This driver can also be built as a module. If so, the module | |
258 | will be called rtc-max6902. | |
259 | ||
bb35fb20 JE |
260 | endif # SPI_MASTER |
261 | ||
09a21e56 | 262 | comment "Platform RTC drivers" |
09a21e56 AZ |
263 | |
264 | # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> | |
265 | # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a | |
266 | # global rtc_lock ... it's not yet just another platform_device. | |
267 | ||
268 | config RTC_DRV_CMOS | |
269 | tristate "PC-style 'CMOS'" | |
bb35fb20 | 270 | depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS |
09a21e56 AZ |
271 | help |
272 | Say "yes" here to get direct support for the real time clock | |
273 | found in every PC or ACPI-based system, and some other boards. | |
274 | Specifically the original MC146818, compatibles like those in | |
275 | PC south bridges, the DS12887 or M48T86, some multifunction | |
276 | or LPC bus chips, and so on. | |
277 | ||
278 | Your system will need to define the platform device used by | |
279 | this driver, otherwise it won't be accessible. This means | |
280 | you can safely enable this driver if you don't know whether | |
281 | or not your board has this kind of hardware. | |
282 | ||
283 | This driver can also be built as a module. If so, the module | |
284 | will be called rtc-cmos. | |
285 | ||
537739de TB |
286 | config RTC_DRV_DS1216 |
287 | tristate "Dallas DS1216" | |
bb35fb20 | 288 | depends on SNI_RM |
537739de TB |
289 | help |
290 | If you say yes here you get support for the Dallas DS1216 RTC chips. | |
291 | ||
09a21e56 AZ |
292 | config RTC_DRV_DS1553 |
293 | tristate "Dallas DS1553" | |
7520b94d AZ |
294 | help |
295 | If you say yes here you get support for the | |
09a21e56 | 296 | Dallas DS1553 timekeeping chip. |
7520b94d AZ |
297 | |
298 | This driver can also be built as a module. If so, the module | |
09a21e56 AZ |
299 | will be called rtc-ds1553. |
300 | ||
02964115 TH |
301 | config RTC_DRV_STK17TA8 |
302 | tristate "Simtek STK17TA8" | |
303 | depends on RTC_CLASS | |
304 | help | |
305 | If you say yes here you get support for the | |
306 | Simtek STK17TA8 timekeeping chip. | |
307 | ||
308 | This driver can also be built as a module. If so, the module | |
309 | will be called rtc-stk17ta8. | |
310 | ||
09a21e56 AZ |
311 | config RTC_DRV_DS1742 |
312 | tristate "Dallas DS1742/1743" | |
09a21e56 AZ |
313 | help |
314 | If you say yes here you get support for the | |
315 | Dallas DS1742/1743 timekeeping chip. | |
316 | ||
317 | This driver can also be built as a module. If so, the module | |
318 | will be called rtc-ds1742. | |
319 | ||
320 | config RTC_DRV_M48T86 | |
321 | tristate "ST M48T86/Dallas DS12887" | |
09a21e56 AZ |
322 | help |
323 | If you say Y here you will get support for the | |
324 | ST M48T86 and Dallas DS12887 RTC chips. | |
325 | ||
326 | This driver can also be built as a module. If so, the module | |
327 | will be called rtc-m48t86. | |
328 | ||
2e774c7c MZ |
329 | config RTC_DRV_M48T59 |
330 | tristate "ST M48T59" | |
2e774c7c MZ |
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 | ||
09a21e56 AZ |
338 | config RTC_DRV_V3020 |
339 | tristate "EM Microelectronic V3020" | |
09a21e56 AZ |
340 | help |
341 | If you say yes here you will get support for the | |
342 | EM Microelectronic v3020 RTC chip. | |
343 | ||
344 | This driver can also be built as a module. If so, the module | |
345 | will be called rtc-v3020. | |
346 | ||
347 | comment "on-CPU RTC drivers" | |
09a21e56 AZ |
348 | |
349 | config RTC_DRV_OMAP | |
350 | tristate "TI OMAP1" | |
bb35fb20 | 351 | depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 |
09a21e56 AZ |
352 | help |
353 | Say "yes" here to support the real time clock on TI OMAP1 chips. | |
354 | This driver can also be built as a module called rtc-omap. | |
7520b94d | 355 | |
1add6781 BD |
356 | config RTC_DRV_S3C |
357 | tristate "Samsung S3C series SoC RTC" | |
bb35fb20 | 358 | depends on ARCH_S3C2410 |
1add6781 BD |
359 | help |
360 | RTC (Realtime Clock) driver for the clock inbuilt into the | |
361 | Samsung S3C24XX series of SoCs. This can provide periodic | |
362 | interrupt rates from 1Hz to 64Hz for user programs, and | |
363 | wakeup from Alarm. | |
364 | ||
365 | The driver currently supports the common features on all the | |
366 | S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 | |
367 | and S3C2442. | |
368 | ||
369 | This driver can also be build as a module. If so, the module | |
370 | will be called rtc-s3c. | |
371 | ||
fd507e2f AZ |
372 | config RTC_DRV_EP93XX |
373 | tristate "Cirrus Logic EP93XX" | |
bb35fb20 | 374 | depends on ARCH_EP93XX |
fd507e2f AZ |
375 | help |
376 | If you say yes here you get support for the | |
377 | RTC embedded in the Cirrus Logic EP93XX processors. | |
378 | ||
379 | This driver can also be built as a module. If so, the module | |
380 | will be called rtc-ep93xx. | |
381 | ||
e842f1c8 RP |
382 | config RTC_DRV_SA1100 |
383 | tristate "SA11x0/PXA2xx" | |
bb35fb20 | 384 | depends on ARCH_SA1100 || ARCH_PXA |
e842f1c8 RP |
385 | help |
386 | If you say Y here you will get access to the real time clock | |
387 | built into your SA11x0 or PXA2xx CPU. | |
388 | ||
389 | To compile this driver as a module, choose M here: the | |
390 | module will be called rtc-sa1100. | |
fd507e2f | 391 | |
317a6104 PM |
392 | config RTC_DRV_SH |
393 | tristate "SuperH On-Chip RTC" | |
bb35fb20 | 394 | depends on RTC_CLASS && (CPU_SH3 || CPU_SH4) |
317a6104 PM |
395 | help |
396 | Say Y here to enable support for the on-chip RTC found in | |
397 | most SuperH processors. | |
398 | ||
399 | To compile this driver as a module, choose M here: the | |
400 | module will be called rtc-sh. | |
401 | ||
8417eb7a | 402 | config RTC_DRV_VR41XX |
3e16f6af | 403 | tristate "NEC VR41XX" |
bb35fb20 | 404 | depends on CPU_VR41XX |
3e16f6af AZ |
405 | help |
406 | If you say Y here you will get access to the real time clock | |
407 | built into your NEC VR41XX CPU. | |
408 | ||
409 | To compile this driver as a module, choose M here: the | |
410 | module will be called rtc-vr41xx. | |
8417eb7a | 411 | |
8ae6e163 DS |
412 | config RTC_DRV_PL031 |
413 | tristate "ARM AMBA PL031 RTC" | |
bb35fb20 | 414 | depends on ARM_AMBA |
8ae6e163 DS |
415 | help |
416 | If you say Y here you will get access to ARM AMBA | |
09a21e56 | 417 | PrimeCell PL031 RTC found on certain ARM SOCs. |
8ae6e163 DS |
418 | |
419 | To compile this driver as a module, choose M here: the | |
420 | module will be called rtc-pl031. | |
421 | ||
fa04e78b HCE |
422 | config RTC_DRV_AT32AP700X |
423 | tristate "AT32AP700X series RTC" | |
bb35fb20 | 424 | depends on PLATFORM_AT32AP |
fa04e78b HCE |
425 | help |
426 | Driver for the internal RTC (Realtime Clock) on Atmel AVR32 | |
427 | AT32AP700x family processors. | |
428 | ||
7fc39f6d | 429 | config RTC_DRV_AT91RM9200 |
788b1fc6 | 430 | tristate "AT91RM9200" |
bb35fb20 | 431 | depends on ARCH_AT91RM9200 |
788b1fc6 AV |
432 | help |
433 | Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock). | |
434 | ||
8cc75c9a WB |
435 | config RTC_DRV_BFIN |
436 | tristate "Blackfin On-Chip RTC" | |
bb35fb20 | 437 | depends on BFIN |
8cc75c9a WB |
438 | help |
439 | If you say yes here you will get support for the | |
440 | Blackfin On-Chip Real Time Clock. | |
441 | ||
442 | This driver can also be built as a module. If so, the module | |
443 | will be called rtc-bfin. | |
444 | ||
e9f2bd81 NI |
445 | config RTC_DRV_RS5C313 |
446 | tristate "Ricoh RS5C313" | |
bb35fb20 | 447 | depends on SH_LANDISK |
e9f2bd81 NI |
448 | help |
449 | If you say yes here you get support for the Ricoh RS5C313 RTC chips. | |
450 | ||
bb35fb20 | 451 | endif # RTC_CLASS |