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 | |
44e0451d | 19 | will be called rtc-core. |
0c86edc0 | 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 | 37 | The RTC device that will be used to (re)initialize the system |
ae64d169 AZ |
38 | clock, usually rtc0. Initialization is done when the system |
39 | starts up, and when it resumes from a low power state. This | |
779d2089 DB |
40 | device should record time in UTC, since the kernel won't do |
41 | timezone correction. | |
7ca1d488 | 42 | |
55ff1aba DB |
43 | The driver for this RTC device must be loaded before late_initcall |
44 | functions run, so it must usually be statically linked. | |
45 | ||
7ca1d488 | 46 | This clock should be battery-backed, so that it reads the correct |
ae64d169 | 47 | time when the system boots from a power-off state. Otherwise, your |
7ca1d488 DB |
48 | system will need an external clock source (like an NTP server). |
49 | ||
50 | If the clock you specify here is not battery backed, it may still | |
51 | be useful to reinitialize system time when resuming from system | |
09b6bdb3 | 52 | sleep states. Do not specify an RTC here unless it stays powered |
7ca1d488 | 53 | during all this system's supported sleep states. |
0c86edc0 | 54 | |
9e86ecb6 DB |
55 | config RTC_DEBUG |
56 | bool "RTC debug support" | |
57 | depends on RTC_CLASS = y | |
58 | help | |
59 | Say yes here to enable debugging support in the RTC framework | |
60 | and individual RTC drivers. | |
61 | ||
0c86edc0 | 62 | comment "RTC interfaces" |
0c86edc0 | 63 | |
c5c3e192 | 64 | config RTC_INTF_SYSFS |
e40659c5 | 65 | boolean "/sys/class/rtc/rtcN (sysfs)" |
bb35fb20 | 66 | depends on SYSFS |
c5c3e192 AZ |
67 | default RTC_CLASS |
68 | help | |
9e86ecb6 DB |
69 | Say yes here if you want to use your RTCs using sysfs interfaces, |
70 | /sys/class/rtc/rtc0 through /sys/.../rtcN. | |
c5c3e192 | 71 | |
ae64d169 | 72 | If unsure, say Y. |
c5c3e192 | 73 | |
728a2947 | 74 | config RTC_INTF_PROC |
e40659c5 | 75 | boolean "/proc/driver/rtc (procfs for rtc0)" |
bb35fb20 | 76 | depends on PROC_FS |
728a2947 AZ |
77 | default RTC_CLASS |
78 | help | |
9e86ecb6 | 79 | Say yes here if you want to use your first RTC through the proc |
ae64d169 | 80 | interface, /proc/driver/rtc. Other RTCs will not be available |
9e86ecb6 | 81 | through that API. |
728a2947 | 82 | |
ae64d169 | 83 | If unsure, say Y. |
728a2947 | 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 | |
ae64d169 | 91 | /dev/rtcN. |
e824290e | 92 | |
ae64d169 AZ |
93 | You may want to set up a symbolic link so one of these |
94 | can be accessed as /dev/rtc, which is a name | |
95 | expected by "hwclock" and some other programs. Recent | |
96 | versions of "udev" are known to set up the symlink for you. | |
97 | ||
98 | If unsure, say Y. | |
e824290e | 99 | |
09a21e56 AZ |
100 | config RTC_DRV_TEST |
101 | tristate "Test driver/device" | |
1fec7c66 AZ |
102 | help |
103 | If you say yes here you get support for the | |
09a21e56 AZ |
104 | RTC test driver. It's a software RTC which can be |
105 | used to test the RTC subsystem APIs. It gets | |
106 | the time from the system clock. | |
107 | You want this driver only if you are doing development | |
108 | on the RTC subsystem. Please read the source code | |
109 | for further details. | |
1fec7c66 AZ |
110 | |
111 | This driver can also be built as a module. If so, the module | |
09a21e56 AZ |
112 | will be called rtc-test. |
113 | ||
114 | comment "I2C RTC drivers" | |
bb35fb20 JE |
115 | depends on I2C |
116 | ||
117 | if I2C | |
1fec7c66 | 118 | |
1abb0dc9 | 119 | config RTC_DRV_DS1307 |
a2166858 | 120 | tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025" |
1abb0dc9 DB |
121 | help |
122 | If you say yes here you get support for various compatible RTC | |
ae64d169 | 123 | chips (often with battery backup) connected with I2C. This driver |
1abb0dc9 | 124 | should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00, |
a2166858 MF |
125 | EPSON RX-8025 and probably other chips. In some cases the RTC |
126 | must already have been initialized (by manufacturing or a | |
127 | bootloader). | |
1abb0dc9 DB |
128 | |
129 | The first seven registers on these chips hold an RTC, and other | |
130 | registers may add features such as NVRAM, a trickle charger for | |
ae64d169 | 131 | the RTC/NVRAM backup power, and alarms. NVRAM is visible in |
682d73f6 | 132 | sysfs, but other chip features may not be available. |
1abb0dc9 DB |
133 | |
134 | This driver can also be built as a module. If so, the module | |
135 | will be called rtc-ds1307. | |
136 | ||
bf4994d7 | 137 | config RTC_DRV_DS1374 |
09b6bdb3 | 138 | tristate "Dallas/Maxim DS1374" |
bf4994d7 SW |
139 | depends on RTC_CLASS && I2C |
140 | help | |
141 | If you say yes here you get support for Dallas Semiconductor | |
ae64d169 | 142 | DS1374 real-time clock chips. If an interrupt is associated |
bf4994d7 SW |
143 | with the device, the alarm functionality is supported. |
144 | ||
ae64d169 | 145 | This driver can also be built as a module. If so, the module |
bf4994d7 SW |
146 | will be called rtc-ds1374. |
147 | ||
09a21e56 AZ |
148 | config RTC_DRV_DS1672 |
149 | tristate "Dallas/Maxim DS1672" | |
9bf5b4f5 AN |
150 | help |
151 | If you say yes here you get support for the | |
09a21e56 | 152 | Dallas/Maxim DS1672 timekeeping chip. |
9bf5b4f5 AN |
153 | |
154 | This driver can also be built as a module. If so, the module | |
09a21e56 | 155 | will be called rtc-ds1672. |
9bf5b4f5 | 156 | |
c03675f0 RZ |
157 | config RTC_DRV_DS3232 |
158 | tristate "Dallas/Maxim DS3232" | |
159 | depends on RTC_CLASS && I2C | |
160 | help | |
161 | If you say yes here you get support for Dallas Semiconductor | |
f46418c5 LCB |
162 | DS3232 real-time clock chips. If an interrupt is associated |
163 | with the device, the alarm functionality is supported. | |
c03675f0 RZ |
164 | |
165 | This driver can also be built as a module. If so, the module | |
166 | will be called rtc-ds3232. | |
167 | ||
09a21e56 | 168 | config RTC_DRV_MAX6900 |
09b6bdb3 | 169 | tristate "Maxim MAX6900" |
7e56a7dc | 170 | help |
09a21e56 AZ |
171 | If you say yes here you will get support for the |
172 | Maxim MAX6900 I2C RTC chip. | |
7e56a7dc HVR |
173 | |
174 | This driver can also be built as a module. If so, the module | |
09a21e56 | 175 | will be called rtc-max6900. |
7e56a7dc | 176 | |
a39069f6 HZ |
177 | config RTC_DRV_MAX8925 |
178 | tristate "Maxim MAX8925" | |
179 | depends on MFD_MAX8925 | |
180 | help | |
181 | If you say yes here you will get support for the | |
182 | RTC of Maxim MAX8925 PMIC. | |
183 | ||
184 | This driver can also be built as a module. If so, the module | |
185 | will be called rtc-max8925. | |
186 | ||
9b16c0a4 JS |
187 | config RTC_DRV_MAX8998 |
188 | tristate "Maxim MAX8998" | |
189 | depends on MFD_MAX8998 | |
190 | help | |
191 | If you say yes here you will get support for the | |
192 | RTC of Maxim MAX8998 PMIC. | |
193 | ||
194 | This driver can also be built as a module. If so, the module | |
195 | will be called rtc-max8998. | |
196 | ||
09a21e56 | 197 | config RTC_DRV_RS5C372 |
5d4529be | 198 | tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A" |
edf1aaa3 AZ |
199 | help |
200 | If you say yes here you get support for the | |
5d4529be | 201 | Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. |
edf1aaa3 AZ |
202 | |
203 | This driver can also be built as a module. If so, the module | |
09a21e56 | 204 | will be called rtc-rs5c372. |
edf1aaa3 | 205 | |
09a21e56 | 206 | config RTC_DRV_ISL1208 |
09b6bdb3 | 207 | tristate "Intersil ISL1208" |
5ec3e4b7 AN |
208 | help |
209 | If you say yes here you get support for the | |
09b6bdb3 | 210 | Intersil ISL1208 RTC chip. |
5ec3e4b7 AN |
211 | |
212 | This driver can also be built as a module. If so, the module | |
09a21e56 | 213 | will be called rtc-isl1208. |
5ec3e4b7 | 214 | |
d6c7428f RF |
215 | config RTC_DRV_ISL12022 |
216 | tristate "Intersil ISL12022" | |
217 | help | |
218 | If you say yes here you get support for the | |
219 | Intersil ISL12022 RTC chip. | |
220 | ||
221 | This driver can also be built as a module. If so, the module | |
222 | will be called rtc-isl12022. | |
223 | ||
09a21e56 AZ |
224 | config RTC_DRV_X1205 |
225 | tristate "Xicor/Intersil X1205" | |
db68b189 | 226 | help |
09a21e56 AZ |
227 | If you say yes here you get support for the |
228 | Xicor/Intersil X1205 RTC chip. | |
229 | ||
230 | This driver can also be built as a module. If so, the module | |
231 | will be called rtc-x1205. | |
db68b189 | 232 | |
b5a82d62 AZ |
233 | config RTC_DRV_PCF8563 |
234 | tristate "Philips PCF8563/Epson RTC8564" | |
b5a82d62 AZ |
235 | help |
236 | If you say yes here you get support for the | |
237 | Philips PCF8563 RTC chip. The Epson RTC8564 | |
238 | should work as well. | |
239 | ||
240 | This driver can also be built as a module. If so, the module | |
241 | will be called rtc-pcf8563. | |
242 | ||
9c0c5705 L |
243 | config RTC_DRV_PCF8583 |
244 | tristate "Philips PCF8583" | |
9c0c5705 | 245 | help |
bb71f99f | 246 | If you say yes here you get support for the Philips PCF8583 |
09a21e56 | 247 | RTC chip found on Acorn RiscPCs. This driver supports the |
bb71f99f | 248 | platform specific method of retrieving the current year from |
09a21e56 AZ |
249 | the RTC's SRAM. It will work on other platforms with the same |
250 | chip, but the year will probably have to be tweaked. | |
9c0c5705 L |
251 | |
252 | This driver can also be built as a module. If so, the module | |
253 | will be called rtc-pcf8583. | |
254 | ||
caaff562 | 255 | config RTC_DRV_M41T80 |
f30281f4 | 256 | tristate "ST M41T62/65/M41T80/81/82/83/84/85/87" |
caaff562 | 257 | help |
d3a126fc SF |
258 | If you say Y here you will get support for the ST M41T60 |
259 | and M41T80 RTC chips series. Currently, the following chips are | |
f30281f4 | 260 | supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84, |
d3a126fc | 261 | M41ST85, and M41ST87. |
caaff562 AN |
262 | |
263 | This driver can also be built as a module. If so, the module | |
264 | will be called rtc-m41t80. | |
265 | ||
617780d2 | 266 | config RTC_DRV_M41T80_WDT |
d3a126fc | 267 | bool "ST M41T65/M41T80 series RTC watchdog timer" |
617780d2 AN |
268 | depends on RTC_DRV_M41T80 |
269 | help | |
270 | If you say Y here you will get support for the | |
d3a126fc | 271 | watchdog timer in the ST M41T60 and M41T80 RTC chips series. |
617780d2 | 272 | |
1ce7c83f PZ |
273 | config RTC_DRV_BQ32K |
274 | tristate "TI BQ32000" | |
275 | help | |
276 | If you say Y here you will get support for the TI | |
277 | BQ32000 I2C RTC chip. | |
278 | ||
279 | This driver can also be built as a module. If so, the module | |
280 | will be called rtc-bq32k. | |
281 | ||
afd8d0f9 DB |
282 | config RTC_DRV_DM355EVM |
283 | tristate "TI DaVinci DM355 EVM RTC" | |
284 | depends on MFD_DM355EVM_MSP | |
285 | help | |
286 | Supports the RTC firmware in the MSP430 on the DM355 EVM. | |
287 | ||
0c4a59fe TL |
288 | config RTC_DRV_TWL92330 |
289 | boolean "TI TWL92330/Menelaus" | |
bb35fb20 | 290 | depends on MENELAUS |
0c4a59fe TL |
291 | help |
292 | If you say yes here you get support for the RTC on the | |
01dd2fbf | 293 | TWL92330 "Menelaus" power management chip, used with OMAP2 |
ae64d169 | 294 | platforms. The support is integrated with the rest of |
0c4a59fe TL |
295 | the Menelaus driver; it's not separate module. |
296 | ||
f96411ab | 297 | config RTC_DRV_TWL4030 |
a6b49ffd | 298 | tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0" |
f96411ab DB |
299 | depends on RTC_CLASS && TWL4030_CORE |
300 | help | |
301 | If you say yes here you get support for the RTC on the | |
a6b49ffd | 302 | TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms. |
f96411ab DB |
303 | |
304 | This driver can also be built as a module. If so, the module | |
a6b49ffd | 305 | will be called rtc-twl. |
f96411ab | 306 | |
c46288b0 BB |
307 | config RTC_DRV_S35390A |
308 | tristate "Seiko Instruments S-35390A" | |
d479540d | 309 | select BITREVERSE |
c46288b0 BB |
310 | help |
311 | If you say yes here you will get support for the Seiko | |
312 | Instruments S-35390A. | |
313 | ||
314 | This driver can also be built as a module. If so the module | |
315 | will be called rtc-s35390a. | |
316 | ||
c6d8f400 SL |
317 | config RTC_DRV_FM3130 |
318 | tristate "Ramtron FM3130" | |
319 | help | |
320 | If you say Y here you will get support for the | |
321 | Ramtron FM3130 RTC chips. | |
322 | Ramtron FM3130 is a chip with two separate devices inside, | |
323 | RTC clock and FRAM. This driver provides only RTC functionality. | |
324 | ||
325 | This driver can also be built as a module. If so the module | |
326 | will be called rtc-fm3130. | |
327 | ||
a7fa9851 MW |
328 | config RTC_DRV_RX8581 |
329 | tristate "Epson RX-8581" | |
330 | help | |
331 | If you say yes here you will get support for the Epson RX-8581. | |
332 | ||
333 | This driver can also be built as a module. If so the module | |
334 | will be called rtc-rx8581. | |
335 | ||
3c2b9075 WG |
336 | config RTC_DRV_RX8025 |
337 | tristate "Epson RX-8025SA/NB" | |
338 | help | |
339 | If you say yes here you get support for the Epson | |
340 | RX-8025SA/NB RTC chips. | |
341 | ||
342 | This driver can also be built as a module. If so, the module | |
343 | will be called rtc-rx8025. | |
344 | ||
bb35fb20 JE |
345 | endif # I2C |
346 | ||
09a21e56 | 347 | comment "SPI RTC drivers" |
bb35fb20 JE |
348 | |
349 | if SPI_MASTER | |
09a21e56 | 350 | |
8fc2c767 KH |
351 | config RTC_DRV_M41T94 |
352 | tristate "ST M41T94" | |
353 | help | |
354 | If you say yes here you will get support for the | |
355 | ST M41T94 SPI RTC chip. | |
356 | ||
357 | This driver can also be built as a module. If so, the module | |
358 | will be called rtc-m41t94. | |
359 | ||
53e84b67 DB |
360 | config RTC_DRV_DS1305 |
361 | tristate "Dallas/Maxim DS1305/DS1306" | |
362 | help | |
363 | Select this driver to get support for the Dallas/Maxim DS1305 | |
ae64d169 | 364 | and DS1306 real time clock chips. These support a trickle |
53e84b67 DB |
365 | charger, alarms, and NVRAM in addition to the clock. |
366 | ||
367 | This driver can also be built as a module. If so, the module | |
368 | will be called rtc-ds1305. | |
369 | ||
06de1808 MJ |
370 | config RTC_DRV_DS1390 |
371 | tristate "Dallas/Maxim DS1390/93/94" | |
372 | help | |
7b9b2ef1 AZ |
373 | If you say yes here you get support for the |
374 | Dallas/Maxim DS1390/93/94 chips. | |
06de1808 MJ |
375 | |
376 | This driver only supports the RTC feature, and not other chip | |
377 | features such as alarms and trickle charging. | |
378 | ||
379 | This driver can also be built as a module. If so, the module | |
380 | will be called rtc-ds1390. | |
381 | ||
09b6bdb3 AZ |
382 | config RTC_DRV_MAX6902 |
383 | tristate "Maxim MAX6902" | |
384 | help | |
385 | If you say yes here you will get support for the | |
386 | Maxim MAX6902 SPI RTC chip. | |
387 | ||
388 | This driver can also be built as a module. If so, the module | |
389 | will be called rtc-max6902. | |
390 | ||
2805b969 MD |
391 | config RTC_DRV_R9701 |
392 | tristate "Epson RTC-9701JE" | |
393 | help | |
394 | If you say yes here you will get support for the | |
395 | Epson RTC-9701JE SPI RTC chip. | |
396 | ||
397 | This driver can also be built as a module. If so, the module | |
398 | will be called rtc-r9701. | |
399 | ||
e0ac4761 AN |
400 | config RTC_DRV_RS5C348 |
401 | tristate "Ricoh RS5C348A/B" | |
e0ac4761 AN |
402 | help |
403 | If you say yes here you get support for the | |
404 | Ricoh RS5C348A and RS5C348B RTC chips. | |
405 | ||
406 | This driver can also be built as a module. If so, the module | |
407 | will be called rtc-rs5c348. | |
408 | ||
2f9b75e0 DA |
409 | config RTC_DRV_DS3234 |
410 | tristate "Maxim/Dallas DS3234" | |
411 | help | |
412 | If you say yes here you get support for the | |
413 | Maxim/Dallas DS3234 SPI RTC chip. | |
414 | ||
415 | This driver can also be built as a module. If so, the module | |
416 | will be called rtc-ds3234. | |
417 | ||
7f3923a1 CV |
418 | config RTC_DRV_PCF2123 |
419 | tristate "NXP PCF2123" | |
420 | help | |
421 | If you say yes here you get support for the NXP PCF2123 | |
422 | RTC chip. | |
423 | ||
424 | This driver can also be built as a module. If so, the module | |
425 | will be called rtc-pcf2123. | |
426 | ||
bb35fb20 JE |
427 | endif # SPI_MASTER |
428 | ||
09a21e56 | 429 | comment "Platform RTC drivers" |
09a21e56 AZ |
430 | |
431 | # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> | |
432 | # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a | |
433 | # global rtc_lock ... it's not yet just another platform_device. | |
434 | ||
435 | config RTC_DRV_CMOS | |
436 | tristate "PC-style 'CMOS'" | |
5ec87708 | 437 | depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64 |
c7500900 | 438 | default y if X86 |
09a21e56 AZ |
439 | help |
440 | Say "yes" here to get direct support for the real time clock | |
441 | found in every PC or ACPI-based system, and some other boards. | |
442 | Specifically the original MC146818, compatibles like those in | |
443 | PC south bridges, the DS12887 or M48T86, some multifunction | |
444 | or LPC bus chips, and so on. | |
445 | ||
446 | Your system will need to define the platform device used by | |
ae64d169 | 447 | this driver, otherwise it won't be accessible. This means |
09a21e56 AZ |
448 | you can safely enable this driver if you don't know whether |
449 | or not your board has this kind of hardware. | |
450 | ||
451 | This driver can also be built as a module. If so, the module | |
452 | will be called rtc-cmos. | |
453 | ||
0146f261 FT |
454 | config RTC_DRV_VRTC |
455 | tristate "Virtual RTC for Moorestown platforms" | |
456 | depends on X86_MRST | |
457 | default y if X86_MRST | |
458 | ||
459 | help | |
460 | Say "yes" here to get direct support for the real time clock | |
461 | found on Moorestown platforms. The VRTC is a emulated RTC that | |
462 | derives its clock source from a real RTC in the PMIC. The MC146818 | |
463 | style programming interface is mostly conserved, but any | |
464 | updates are done via IPC calls to the system controller FW. | |
465 | ||
537739de TB |
466 | config RTC_DRV_DS1216 |
467 | tristate "Dallas DS1216" | |
bb35fb20 | 468 | depends on SNI_RM |
537739de TB |
469 | help |
470 | If you say yes here you get support for the Dallas DS1216 RTC chips. | |
471 | ||
5f119f29 TB |
472 | config RTC_DRV_DS1286 |
473 | tristate "Dallas DS1286" | |
474 | help | |
475 | If you say yes here you get support for the Dallas DS1286 RTC chips. | |
476 | ||
739d340d PM |
477 | config RTC_DRV_DS1302 |
478 | tristate "Dallas DS1302" | |
479 | depends on SH_SECUREEDGE5410 | |
480 | help | |
481 | If you say yes here you get support for the Dallas DS1302 RTC chips. | |
482 | ||
8f26795a AS |
483 | config RTC_DRV_DS1511 |
484 | tristate "Dallas DS1511" | |
485 | depends on RTC_CLASS | |
486 | help | |
487 | If you say yes here you get support for the | |
488 | Dallas DS1511 timekeeping/watchdog chip. | |
489 | ||
490 | This driver can also be built as a module. If so, the module | |
491 | will be called rtc-ds1511. | |
492 | ||
09a21e56 | 493 | config RTC_DRV_DS1553 |
09b6bdb3 | 494 | tristate "Maxim/Dallas DS1553" |
7520b94d AZ |
495 | help |
496 | If you say yes here you get support for the | |
09b6bdb3 | 497 | Maxim/Dallas DS1553 timekeeping chip. |
7520b94d AZ |
498 | |
499 | This driver can also be built as a module. If so, the module | |
09a21e56 AZ |
500 | will be called rtc-ds1553. |
501 | ||
09b6bdb3 AZ |
502 | config RTC_DRV_DS1742 |
503 | tristate "Maxim/Dallas DS1742/1743" | |
02964115 TH |
504 | help |
505 | If you say yes here you get support for the | |
09b6bdb3 | 506 | Maxim/Dallas DS1742/1743 timekeeping chip. |
02964115 TH |
507 | |
508 | This driver can also be built as a module. If so, the module | |
09b6bdb3 | 509 | will be called rtc-ds1742. |
02964115 | 510 | |
5e3fd9e5 | 511 | config RTC_DRV_EFI |
512 | tristate "EFI RTC" | |
513 | depends on IA64 | |
514 | help | |
515 | If you say yes here you will get support for the EFI | |
516 | Real Time Clock. | |
517 | ||
518 | This driver can also be built as a module. If so, the module | |
519 | will be called rtc-efi. | |
520 | ||
09b6bdb3 AZ |
521 | config RTC_DRV_STK17TA8 |
522 | tristate "Simtek STK17TA8" | |
523 | depends on RTC_CLASS | |
09a21e56 AZ |
524 | help |
525 | If you say yes here you get support for the | |
09b6bdb3 | 526 | Simtek STK17TA8 timekeeping chip. |
09a21e56 AZ |
527 | |
528 | This driver can also be built as a module. If so, the module | |
09b6bdb3 | 529 | will be called rtc-stk17ta8. |
09a21e56 AZ |
530 | |
531 | config RTC_DRV_M48T86 | |
532 | tristate "ST M48T86/Dallas DS12887" | |
09a21e56 AZ |
533 | help |
534 | If you say Y here you will get support for the | |
535 | ST M48T86 and Dallas DS12887 RTC chips. | |
536 | ||
537 | This driver can also be built as a module. If so, the module | |
538 | will be called rtc-m48t86. | |
539 | ||
d1dbd82e TB |
540 | config RTC_DRV_M48T35 |
541 | tristate "ST M48T35" | |
542 | help | |
543 | If you say Y here you will get support for the | |
544 | ST M48T35 RTC chip. | |
545 | ||
546 | This driver can also be built as a module, if so, the module | |
547 | will be called "rtc-m48t35". | |
548 | ||
2e774c7c | 549 | config RTC_DRV_M48T59 |
94fe7424 | 550 | tristate "ST M48T59/M48T08/M48T02" |
2e774c7c MZ |
551 | help |
552 | If you say Y here you will get support for the | |
94fe7424 KH |
553 | ST M48T59 RTC chip and compatible ST M48T08 and M48T02. |
554 | ||
555 | These chips are usually found in Sun SPARC and UltraSPARC | |
556 | workstations. | |
2e774c7c MZ |
557 | |
558 | This driver can also be built as a module, if so, the module | |
559 | will be called "rtc-m48t59". | |
560 | ||
4f9b9bba GU |
561 | config RTC_DRV_MSM6242 |
562 | tristate "Oki MSM6242" | |
563 | help | |
564 | If you say yes here you get support for the Oki MSM6242 | |
565 | timekeeping chip. It is used in some Amiga models (e.g. A2000). | |
566 | ||
567 | This driver can also be built as a module. If so, the module | |
568 | will be called rtc-msm6242. | |
569 | ||
eba54546 BS |
570 | config RTC_DRV_IMXDI |
571 | tristate "Freescale IMX DryIce Real Time Clock" | |
572 | depends on ARCH_MX25 | |
573 | depends on RTC_CLASS | |
574 | help | |
575 | Support for Freescale IMX DryIce RTC | |
576 | ||
577 | This driver can also be built as a module, if so, the module | |
578 | will be called "rtc-imxdi". | |
579 | ||
d00ed3cf DM |
580 | config RTC_MXC |
581 | tristate "Freescale MXC Real Time Clock" | |
582 | depends on ARCH_MXC | |
583 | depends on RTC_CLASS | |
584 | help | |
585 | If you say yes here you get support for the Freescale MXC | |
586 | RTC module. | |
587 | ||
588 | This driver can also be built as a module, if so, the module | |
589 | will be called "rtc-mxc". | |
590 | ||
cca4c231 DM |
591 | config RTC_DRV_BQ4802 |
592 | tristate "TI BQ4802" | |
593 | help | |
594 | If you say Y here you will get support for the TI | |
595 | BQ4802 RTC chip. | |
596 | ||
597 | This driver can also be built as a module. If so, the module | |
598 | will be called rtc-bq4802. | |
599 | ||
4f672ce2 GU |
600 | config RTC_DRV_RP5C01 |
601 | tristate "Ricoh RP5C01" | |
602 | help | |
603 | If you say yes here you get support for the Ricoh RP5C01 | |
604 | timekeeping chip. It is used in some Amiga models (e.g. A3000 | |
605 | and A4000). | |
606 | ||
607 | This driver can also be built as a module. If so, the module | |
608 | will be called rtc-rp5c01. | |
609 | ||
09a21e56 AZ |
610 | config RTC_DRV_V3020 |
611 | tristate "EM Microelectronic V3020" | |
09a21e56 AZ |
612 | help |
613 | If you say yes here you will get support for the | |
614 | EM Microelectronic v3020 RTC chip. | |
615 | ||
616 | This driver can also be built as a module. If so, the module | |
617 | will be called rtc-v3020. | |
618 | ||
35c86bf6 MB |
619 | config RTC_DRV_WM831X |
620 | tristate "Wolfson Microelectronics WM831x RTC" | |
621 | depends on MFD_WM831X | |
622 | help | |
623 | If you say yes here you will get support for the RTC subsystem | |
624 | of the Wolfson Microelectronics WM831X series PMICs. | |
625 | ||
626 | This driver can also be built as a module. If so, the module | |
627 | will be called "rtc-wm831x". | |
628 | ||
077eaf5b MB |
629 | config RTC_DRV_WM8350 |
630 | tristate "Wolfson Microelectronics WM8350 RTC" | |
631 | depends on MFD_WM8350 | |
632 | help | |
633 | If you say yes here you will get support for the RTC subsystem | |
634 | of the Wolfson Microelectronics WM8350. | |
635 | ||
636 | This driver can also be built as a module. If so, the module | |
637 | will be called "rtc-wm8350". | |
638 | ||
eae854b2 BR |
639 | config RTC_DRV_PCF50633 |
640 | depends on MFD_PCF50633 | |
641 | tristate "NXP PCF50633 RTC" | |
642 | help | |
643 | If you say yes here you get support for the RTC subsystem of the | |
644 | NXP PCF50633 used in embedded systems. | |
645 | ||
bd207cfb LW |
646 | config RTC_DRV_AB3100 |
647 | tristate "ST-Ericsson AB3100 RTC" | |
648 | depends on AB3100_CORE | |
649 | default y if AB3100_CORE | |
650 | help | |
651 | Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC | |
652 | support. This chip contains a battery- and capacitor-backed RTC. | |
653 | ||
0af62f4d VS |
654 | config RTC_DRV_AB8500 |
655 | tristate "ST-Ericsson AB8500 RTC" | |
656 | depends on AB8500_CORE | |
657 | help | |
658 | Select this to enable the ST-Ericsson AB8500 power management IC RTC | |
659 | support. This chip contains a battery- and capacitor-backed RTC. | |
660 | ||
afd49a7e WZ |
661 | config RTC_DRV_NUC900 |
662 | tristate "NUC910/NUC920 RTC driver" | |
663 | depends on RTC_CLASS && ARCH_W90X900 | |
664 | help | |
665 | If you say yes here you get support for the RTC subsystem of the | |
666 | NUC910/NUC920 used in embedded systems. | |
bd207cfb | 667 | |
09a21e56 | 668 | comment "on-CPU RTC drivers" |
09a21e56 | 669 | |
8ecf6c54 MA |
670 | config RTC_DRV_DAVINCI |
671 | tristate "TI DaVinci RTC" | |
672 | depends on ARCH_DAVINCI_DM365 | |
673 | help | |
674 | If you say yes here you get support for the RTC on the | |
675 | DaVinci platforms (DM365). | |
676 | ||
677 | This driver can also be built as a module. If so, the module | |
678 | will be called rtc-davinci. | |
679 | ||
09a21e56 AZ |
680 | config RTC_DRV_OMAP |
681 | tristate "TI OMAP1" | |
8cfde8c1 | 682 | depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX |
09a21e56 | 683 | help |
8cfde8c1 MG |
684 | Say "yes" here to support the real time clock on TI OMAP1 and |
685 | DA8xx/OMAP-L13x chips. This driver can also be built as a | |
686 | module called rtc-omap. | |
7520b94d | 687 | |
16f4efe7 AD |
688 | config HAVE_S3C_RTC |
689 | bool | |
690 | help | |
691 | This will include RTC support for Samsung SoCs. If | |
692 | you want to include RTC support for any machine, kindly | |
693 | select this in the respective mach-XXXX/Kconfig file. | |
694 | ||
1add6781 BD |
695 | config RTC_DRV_S3C |
696 | tristate "Samsung S3C series SoC RTC" | |
16f4efe7 | 697 | depends on ARCH_S3C2410 || ARCH_S3C64XX || HAVE_S3C_RTC |
1add6781 BD |
698 | help |
699 | RTC (Realtime Clock) driver for the clock inbuilt into the | |
700 | Samsung S3C24XX series of SoCs. This can provide periodic | |
701 | interrupt rates from 1Hz to 64Hz for user programs, and | |
702 | wakeup from Alarm. | |
703 | ||
704 | The driver currently supports the common features on all the | |
705 | S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 | |
706 | and S3C2442. | |
707 | ||
708 | This driver can also be build as a module. If so, the module | |
709 | will be called rtc-s3c. | |
710 | ||
fd507e2f AZ |
711 | config RTC_DRV_EP93XX |
712 | tristate "Cirrus Logic EP93XX" | |
bb35fb20 | 713 | depends on ARCH_EP93XX |
fd507e2f AZ |
714 | help |
715 | If you say yes here you get support for the | |
716 | RTC embedded in the Cirrus Logic EP93XX processors. | |
717 | ||
718 | This driver can also be built as a module. If so, the module | |
719 | will be called rtc-ep93xx. | |
720 | ||
e842f1c8 RP |
721 | config RTC_DRV_SA1100 |
722 | tristate "SA11x0/PXA2xx" | |
bb35fb20 | 723 | depends on ARCH_SA1100 || ARCH_PXA |
e842f1c8 RP |
724 | help |
725 | If you say Y here you will get access to the real time clock | |
726 | built into your SA11x0 or PXA2xx CPU. | |
727 | ||
728 | To compile this driver as a module, choose M here: the | |
729 | module will be called rtc-sa1100. | |
fd507e2f | 730 | |
317a6104 PM |
731 | config RTC_DRV_SH |
732 | tristate "SuperH On-Chip RTC" | |
063adc75 | 733 | depends on RTC_CLASS && SUPERH && HAVE_CLK |
317a6104 PM |
734 | help |
735 | Say Y here to enable support for the on-chip RTC found in | |
736 | most SuperH processors. | |
737 | ||
738 | To compile this driver as a module, choose M here: the | |
739 | module will be called rtc-sh. | |
740 | ||
8417eb7a | 741 | config RTC_DRV_VR41XX |
3e16f6af | 742 | tristate "NEC VR41XX" |
bb35fb20 | 743 | depends on CPU_VR41XX |
3e16f6af AZ |
744 | help |
745 | If you say Y here you will get access to the real time clock | |
746 | built into your NEC VR41XX CPU. | |
747 | ||
748 | To compile this driver as a module, choose M here: the | |
749 | module will be called rtc-vr41xx. | |
8417eb7a | 750 | |
a190901c RK |
751 | config RTC_DRV_PL030 |
752 | tristate "ARM AMBA PL030 RTC" | |
753 | depends on ARM_AMBA | |
754 | help | |
755 | If you say Y here you will get access to ARM AMBA | |
756 | PrimeCell PL030 RTC found on certain ARM SOCs. | |
757 | ||
758 | To compile this driver as a module, choose M here: the | |
759 | module will be called rtc-pl030. | |
760 | ||
8ae6e163 DS |
761 | config RTC_DRV_PL031 |
762 | tristate "ARM AMBA PL031 RTC" | |
bb35fb20 | 763 | depends on ARM_AMBA |
8ae6e163 DS |
764 | help |
765 | If you say Y here you will get access to ARM AMBA | |
09a21e56 | 766 | PrimeCell PL031 RTC found on certain ARM SOCs. |
8ae6e163 DS |
767 | |
768 | To compile this driver as a module, choose M here: the | |
769 | module will be called rtc-pl031. | |
770 | ||
fa04e78b HCE |
771 | config RTC_DRV_AT32AP700X |
772 | tristate "AT32AP700X series RTC" | |
bb35fb20 | 773 | depends on PLATFORM_AT32AP |
fa04e78b HCE |
774 | help |
775 | Driver for the internal RTC (Realtime Clock) on Atmel AVR32 | |
776 | AT32AP700x family processors. | |
777 | ||
7fc39f6d | 778 | config RTC_DRV_AT91RM9200 |
24cecc1b NF |
779 | tristate "AT91RM9200 or some AT91SAM9 RTC" |
780 | depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45 | |
4cdf854f DB |
781 | help |
782 | Driver for the internal RTC (Realtime Clock) module found on | |
24cecc1b | 783 | Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips |
4cdf854f DB |
784 | this is powered by the backup power supply. |
785 | ||
786 | config RTC_DRV_AT91SAM9 | |
24cecc1b | 787 | tristate "AT91SAM9x/AT91CAP9 RTT as RTC" |
4cdf854f DB |
788 | depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40) |
789 | help | |
6b71dbf6 SP |
790 | RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT |
791 | (Real Time Timer). These timers are powered by the backup power | |
792 | supply (such as a small coin cell battery), but do not need to | |
793 | be used as RTCs. | |
4cdf854f | 794 | |
24cecc1b NF |
795 | (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the |
796 | dedicated RTC module and leave the RTT available for other uses.) | |
4cdf854f DB |
797 | |
798 | config RTC_DRV_AT91SAM9_RTT | |
799 | int | |
800 | range 0 1 | |
801 | default 0 | |
802 | prompt "RTT module Number" if ARCH_AT91SAM9263 | |
803 | depends on RTC_DRV_AT91SAM9 | |
804 | help | |
ae64d169 AZ |
805 | More than one RTT module is available. You can choose which |
806 | one will be used as an RTC. The default of zero is normally | |
4cdf854f DB |
807 | OK to use, though some systems use that for non-RTC purposes. |
808 | ||
809 | config RTC_DRV_AT91SAM9_GPBR | |
810 | int | |
811 | range 0 3 if !ARCH_AT91SAM9263 | |
812 | range 0 15 if ARCH_AT91SAM9263 | |
813 | default 0 | |
814 | prompt "Backup Register Number" | |
815 | depends on RTC_DRV_AT91SAM9 | |
816 | help | |
817 | The RTC driver needs to use one of the General Purpose Backup | |
ae64d169 AZ |
818 | Registers (GPBRs) as well as the RTT. You can choose which one |
819 | will be used. The default of zero is normally OK to use, but | |
4cdf854f | 820 | on some systems other software needs to use that register. |
788b1fc6 | 821 | |
45fd8a0c ML |
822 | config RTC_DRV_AU1XXX |
823 | tristate "Au1xxx Counter0 RTC support" | |
42a4f17d | 824 | depends on MIPS_ALCHEMY |
45fd8a0c ML |
825 | help |
826 | This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year | |
827 | counter) to be used as a RTC. | |
828 | ||
829 | This driver can also be built as a module. If so, the module | |
830 | will be called rtc-au1xxx. | |
831 | ||
8cc75c9a WB |
832 | config RTC_DRV_BFIN |
833 | tristate "Blackfin On-Chip RTC" | |
7f604599 | 834 | depends on BLACKFIN && !BF561 |
8cc75c9a WB |
835 | help |
836 | If you say yes here you will get support for the | |
837 | Blackfin On-Chip Real Time Clock. | |
838 | ||
839 | This driver can also be built as a module. If so, the module | |
840 | will be called rtc-bfin. | |
841 | ||
e9f2bd81 NI |
842 | config RTC_DRV_RS5C313 |
843 | tristate "Ricoh RS5C313" | |
bb35fb20 | 844 | depends on SH_LANDISK |
e9f2bd81 NI |
845 | help |
846 | If you say yes here you get support for the Ricoh RS5C313 RTC chips. | |
847 | ||
3afe6d04 GU |
848 | config RTC_DRV_GENERIC |
849 | tristate "Generic RTC support" | |
850 | # Please consider writing a new RTC driver instead of using the generic | |
851 | # RTC abstraction | |
47c8a08b | 852 | depends on PARISC || M68K || PPC || SUPERH32 |
9eb16864 | 853 | help |
3afe6d04 GU |
854 | Say Y or M here to enable RTC support on systems using the generic |
855 | RTC abstraction. If you do not know what you are doing, you should | |
9eb16864 KM |
856 | just say Y. |
857 | ||
dc944368 RJ |
858 | config RTC_DRV_PXA |
859 | tristate "PXA27x/PXA3xx" | |
860 | depends on ARCH_PXA | |
861 | help | |
862 | If you say Y here you will get access to the real time clock | |
863 | built into your PXA27x or PXA3xx CPU. | |
864 | ||
865 | This RTC driver uses PXA RTC registers available since pxa27x | |
866 | series (RDxR, RYxR) instead of legacy RCNR, RTAR. | |
867 | ||
868 | ||
7a138ede DM |
869 | config RTC_DRV_SUN4V |
870 | bool "SUN4V Hypervisor RTC" | |
871 | depends on SPARC64 | |
872 | help | |
873 | If you say Y here you will get support for the Hypervisor | |
874 | based RTC on SUN4V systems. | |
875 | ||
de2cf332 DM |
876 | config RTC_DRV_STARFIRE |
877 | bool "Starfire RTC" | |
878 | depends on SPARC64 | |
879 | help | |
880 | If you say Y here you will get support for the RTC found on | |
881 | Starfire systems. | |
882 | ||
0e149233 AN |
883 | config RTC_DRV_TX4939 |
884 | tristate "TX4939 SoC" | |
885 | depends on SOC_TX4939 | |
886 | help | |
887 | Driver for the internal RTC (Realtime Clock) module found on | |
888 | Toshiba TX4939 SoC. | |
889 | ||
defb4514 SB |
890 | config RTC_DRV_MV |
891 | tristate "Marvell SoC RTC" | |
da43243e | 892 | depends on ARCH_KIRKWOOD || ARCH_DOVE |
defb4514 SB |
893 | help |
894 | If you say yes here you will get support for the in-chip RTC | |
895 | that can be found in some of Marvell's SoC devices, such as | |
896 | the Kirkwood 88F6281 and 88F6192. | |
897 | ||
898 | This driver can also be built as a module. If so, the module | |
899 | will be called rtc-mv. | |
900 | ||
0b5f037a GU |
901 | config RTC_DRV_PS3 |
902 | tristate "PS3 RTC" | |
903 | depends on PPC_PS3 | |
904 | help | |
905 | If you say yes here you will get support for the RTC on PS3. | |
906 | ||
907 | This driver can also be built as a module. If so, the module | |
908 | will be called rtc-ps3. | |
909 | ||
aa958f57 LW |
910 | config RTC_DRV_COH901331 |
911 | tristate "ST-Ericsson COH 901 331 RTC" | |
912 | depends on ARCH_U300 | |
913 | help | |
914 | If you say Y here you will get access to ST-Ericsson | |
915 | COH 901 331 RTC clock found in some ST-Ericsson Mobile | |
916 | Platforms. | |
917 | ||
918 | This driver can also be built as a module. If so, the module | |
919 | will be called "rtc-coh901331". | |
920 | ||
921 | ||
df17f631 | 922 | config RTC_DRV_STMP |
923 | tristate "Freescale STMP3xxx RTC" | |
924 | depends on ARCH_STMP3XXX | |
925 | help | |
926 | If you say yes here you will get support for the onboard | |
927 | STMP3xxx RTC. | |
928 | ||
929 | This driver can also be built as a module. If so, the module | |
930 | will be called rtc-stmp3xxx. | |
931 | ||
d3c7a3f7 DR |
932 | config RTC_DRV_PCAP |
933 | tristate "PCAP RTC" | |
934 | depends on EZX_PCAP | |
935 | help | |
936 | If you say Y here you will get support for the RTC found on | |
937 | the PCAP2 ASIC used on some Motorola phones. | |
938 | ||
1c97872b UKK |
939 | config RTC_DRV_MC13XXX |
940 | depends on MFD_MC13XXX | |
941 | tristate "Freescale MC13xxx RTC" | |
43299f28 | 942 | help |
1c97872b UKK |
943 | This enables support for the RTCs found on Freescale's PMICs |
944 | MC13783 and MC13892. | |
43299f28 | 945 | |
50aae724 AG |
946 | config RTC_DRV_MPC5121 |
947 | tristate "Freescale MPC5121 built-in RTC" | |
948 | depends on PPC_MPC512x && RTC_CLASS | |
949 | help | |
950 | If you say yes here you will get support for the | |
951 | built-in RTC MPC5121. | |
952 | ||
953 | This driver can also be built as a module. If so, the module | |
954 | will be called rtc-mpc5121. | |
955 | ||
3bf0eea8 LPC |
956 | config RTC_DRV_JZ4740 |
957 | tristate "Ingenic JZ4740 SoC" | |
958 | depends on RTC_CLASS | |
959 | depends on MACH_JZ4740 | |
960 | help | |
961 | If you say yes here you get support for the Ingenic JZ4740 SoC RTC | |
962 | controller. | |
963 | ||
964 | This driver can also be buillt as a module. If so, the module | |
965 | will be called rtc-jz4740. | |
966 | ||
9aa449be KW |
967 | config RTC_DRV_LPC32XX |
968 | depends on ARCH_LPC32XX | |
969 | tristate "NXP LPC32XX RTC" | |
970 | help | |
971 | This enables support for the NXP RTC in the LPC32XX | |
972 | ||
973 | This driver can also be buillt as a module. If so, the module | |
974 | will be called rtc-lpc32xx. | |
975 | ||
bb35fb20 | 976 | endif # RTC_CLASS |