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