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 | |
09a21e56 | 169 | config RTC_DRV_MAX6900 |
09b6bdb3 | 170 | tristate "Maxim MAX6900" |
7e56a7dc | 171 | help |
09a21e56 AZ |
172 | If you say yes here you will get support for the |
173 | Maxim MAX6900 I2C RTC chip. | |
7e56a7dc HVR |
174 | |
175 | This driver can also be built as a module. If so, the module | |
09a21e56 | 176 | will be called rtc-max6900. |
7e56a7dc | 177 | |
09a21e56 | 178 | config RTC_DRV_RS5C372 |
5d4529be | 179 | tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A" |
edf1aaa3 AZ |
180 | help |
181 | If you say yes here you get support for the | |
5d4529be | 182 | Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. |
edf1aaa3 AZ |
183 | |
184 | This driver can also be built as a module. If so, the module | |
09a21e56 | 185 | will be called rtc-rs5c372. |
edf1aaa3 | 186 | |
09a21e56 | 187 | config RTC_DRV_ISL1208 |
09b6bdb3 | 188 | tristate "Intersil ISL1208" |
5ec3e4b7 AN |
189 | help |
190 | If you say yes here you get support for the | |
09b6bdb3 | 191 | Intersil ISL1208 RTC chip. |
5ec3e4b7 AN |
192 | |
193 | This driver can also be built as a module. If so, the module | |
09a21e56 | 194 | will be called rtc-isl1208. |
5ec3e4b7 | 195 | |
09a21e56 AZ |
196 | config RTC_DRV_X1205 |
197 | tristate "Xicor/Intersil X1205" | |
db68b189 | 198 | help |
09a21e56 AZ |
199 | If you say yes here you get support for the |
200 | Xicor/Intersil X1205 RTC chip. | |
201 | ||
202 | This driver can also be built as a module. If so, the module | |
203 | will be called rtc-x1205. | |
db68b189 | 204 | |
b5a82d62 AZ |
205 | config RTC_DRV_PCF8563 |
206 | tristate "Philips PCF8563/Epson RTC8564" | |
b5a82d62 AZ |
207 | help |
208 | If you say yes here you get support for the | |
209 | Philips PCF8563 RTC chip. The Epson RTC8564 | |
210 | should work as well. | |
211 | ||
212 | This driver can also be built as a module. If so, the module | |
213 | will be called rtc-pcf8563. | |
214 | ||
9c0c5705 L |
215 | config RTC_DRV_PCF8583 |
216 | tristate "Philips PCF8583" | |
9c0c5705 | 217 | help |
bb71f99f | 218 | If you say yes here you get support for the Philips PCF8583 |
09a21e56 | 219 | RTC chip found on Acorn RiscPCs. This driver supports the |
bb71f99f | 220 | platform specific method of retrieving the current year from |
09a21e56 AZ |
221 | the RTC's SRAM. It will work on other platforms with the same |
222 | chip, but the year will probably have to be tweaked. | |
9c0c5705 L |
223 | |
224 | This driver can also be built as a module. If so, the module | |
225 | will be called rtc-pcf8583. | |
226 | ||
caaff562 | 227 | config RTC_DRV_M41T80 |
f30281f4 | 228 | tristate "ST M41T62/65/M41T80/81/82/83/84/85/87" |
caaff562 | 229 | help |
d3a126fc SF |
230 | If you say Y here you will get support for the ST M41T60 |
231 | and M41T80 RTC chips series. Currently, the following chips are | |
f30281f4 | 232 | supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84, |
d3a126fc | 233 | M41ST85, and M41ST87. |
caaff562 AN |
234 | |
235 | This driver can also be built as a module. If so, the module | |
236 | will be called rtc-m41t80. | |
237 | ||
617780d2 | 238 | config RTC_DRV_M41T80_WDT |
d3a126fc | 239 | bool "ST M41T65/M41T80 series RTC watchdog timer" |
617780d2 AN |
240 | depends on RTC_DRV_M41T80 |
241 | help | |
242 | If you say Y here you will get support for the | |
d3a126fc | 243 | watchdog timer in the ST M41T60 and M41T80 RTC chips series. |
617780d2 | 244 | |
afd8d0f9 DB |
245 | config RTC_DRV_DM355EVM |
246 | tristate "TI DaVinci DM355 EVM RTC" | |
247 | depends on MFD_DM355EVM_MSP | |
248 | help | |
249 | Supports the RTC firmware in the MSP430 on the DM355 EVM. | |
250 | ||
0c4a59fe TL |
251 | config RTC_DRV_TWL92330 |
252 | boolean "TI TWL92330/Menelaus" | |
bb35fb20 | 253 | depends on MENELAUS |
0c4a59fe TL |
254 | help |
255 | If you say yes here you get support for the RTC on the | |
01dd2fbf | 256 | TWL92330 "Menelaus" power management chip, used with OMAP2 |
ae64d169 | 257 | platforms. The support is integrated with the rest of |
0c4a59fe TL |
258 | the Menelaus driver; it's not separate module. |
259 | ||
f96411ab DB |
260 | config RTC_DRV_TWL4030 |
261 | tristate "TI TWL4030/TWL5030/TPS659x0" | |
262 | depends on RTC_CLASS && TWL4030_CORE | |
263 | help | |
264 | If you say yes here you get support for the RTC on the | |
265 | TWL4030 family chips, used mostly with OMAP3 platforms. | |
266 | ||
267 | This driver can also be built as a module. If so, the module | |
268 | will be called rtc-twl4030. | |
269 | ||
c46288b0 BB |
270 | config RTC_DRV_S35390A |
271 | tristate "Seiko Instruments S-35390A" | |
d479540d | 272 | select BITREVERSE |
c46288b0 BB |
273 | help |
274 | If you say yes here you will get support for the Seiko | |
275 | Instruments S-35390A. | |
276 | ||
277 | This driver can also be built as a module. If so the module | |
278 | will be called rtc-s35390a. | |
279 | ||
c6d8f400 SL |
280 | config RTC_DRV_FM3130 |
281 | tristate "Ramtron FM3130" | |
282 | help | |
283 | If you say Y here you will get support for the | |
284 | Ramtron FM3130 RTC chips. | |
285 | Ramtron FM3130 is a chip with two separate devices inside, | |
286 | RTC clock and FRAM. This driver provides only RTC functionality. | |
287 | ||
288 | This driver can also be built as a module. If so the module | |
289 | will be called rtc-fm3130. | |
290 | ||
a7fa9851 MW |
291 | config RTC_DRV_RX8581 |
292 | tristate "Epson RX-8581" | |
293 | help | |
294 | If you say yes here you will get support for the Epson RX-8581. | |
295 | ||
296 | This driver can also be built as a module. If so the module | |
297 | will be called rtc-rx8581. | |
298 | ||
3c2b9075 WG |
299 | config RTC_DRV_RX8025 |
300 | tristate "Epson RX-8025SA/NB" | |
301 | help | |
302 | If you say yes here you get support for the Epson | |
303 | RX-8025SA/NB RTC chips. | |
304 | ||
305 | This driver can also be built as a module. If so, the module | |
306 | will be called rtc-rx8025. | |
307 | ||
bb35fb20 JE |
308 | endif # I2C |
309 | ||
09a21e56 | 310 | comment "SPI RTC drivers" |
bb35fb20 JE |
311 | |
312 | if SPI_MASTER | |
09a21e56 | 313 | |
8fc2c767 KH |
314 | config RTC_DRV_M41T94 |
315 | tristate "ST M41T94" | |
316 | help | |
317 | If you say yes here you will get support for the | |
318 | ST M41T94 SPI RTC chip. | |
319 | ||
320 | This driver can also be built as a module. If so, the module | |
321 | will be called rtc-m41t94. | |
322 | ||
53e84b67 DB |
323 | config RTC_DRV_DS1305 |
324 | tristate "Dallas/Maxim DS1305/DS1306" | |
325 | help | |
326 | Select this driver to get support for the Dallas/Maxim DS1305 | |
ae64d169 | 327 | and DS1306 real time clock chips. These support a trickle |
53e84b67 DB |
328 | charger, alarms, and NVRAM in addition to the clock. |
329 | ||
330 | This driver can also be built as a module. If so, the module | |
331 | will be called rtc-ds1305. | |
332 | ||
06de1808 MJ |
333 | config RTC_DRV_DS1390 |
334 | tristate "Dallas/Maxim DS1390/93/94" | |
335 | help | |
7b9b2ef1 AZ |
336 | If you say yes here you get support for the |
337 | Dallas/Maxim DS1390/93/94 chips. | |
06de1808 MJ |
338 | |
339 | This driver only supports the RTC feature, and not other chip | |
340 | features such as alarms and trickle charging. | |
341 | ||
342 | This driver can also be built as a module. If so, the module | |
343 | will be called rtc-ds1390. | |
344 | ||
09b6bdb3 AZ |
345 | config RTC_DRV_MAX6902 |
346 | tristate "Maxim MAX6902" | |
347 | help | |
348 | If you say yes here you will get support for the | |
349 | Maxim MAX6902 SPI RTC chip. | |
350 | ||
351 | This driver can also be built as a module. If so, the module | |
352 | will be called rtc-max6902. | |
353 | ||
2805b969 MD |
354 | config RTC_DRV_R9701 |
355 | tristate "Epson RTC-9701JE" | |
356 | help | |
357 | If you say yes here you will get support for the | |
358 | Epson RTC-9701JE SPI RTC chip. | |
359 | ||
360 | This driver can also be built as a module. If so, the module | |
361 | will be called rtc-r9701. | |
362 | ||
e0ac4761 AN |
363 | config RTC_DRV_RS5C348 |
364 | tristate "Ricoh RS5C348A/B" | |
e0ac4761 AN |
365 | help |
366 | If you say yes here you get support for the | |
367 | Ricoh RS5C348A and RS5C348B RTC chips. | |
368 | ||
369 | This driver can also be built as a module. If so, the module | |
370 | will be called rtc-rs5c348. | |
371 | ||
2f9b75e0 DA |
372 | config RTC_DRV_DS3234 |
373 | tristate "Maxim/Dallas DS3234" | |
374 | help | |
375 | If you say yes here you get support for the | |
376 | Maxim/Dallas DS3234 SPI RTC chip. | |
377 | ||
378 | This driver can also be built as a module. If so, the module | |
379 | will be called rtc-ds3234. | |
380 | ||
bb35fb20 JE |
381 | endif # SPI_MASTER |
382 | ||
09a21e56 | 383 | comment "Platform RTC drivers" |
09a21e56 AZ |
384 | |
385 | # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> | |
386 | # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a | |
387 | # global rtc_lock ... it's not yet just another platform_device. | |
388 | ||
389 | config RTC_DRV_CMOS | |
390 | tristate "PC-style 'CMOS'" | |
5ec87708 | 391 | depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64 |
c7500900 | 392 | default y if X86 |
09a21e56 AZ |
393 | help |
394 | Say "yes" here to get direct support for the real time clock | |
395 | found in every PC or ACPI-based system, and some other boards. | |
396 | Specifically the original MC146818, compatibles like those in | |
397 | PC south bridges, the DS12887 or M48T86, some multifunction | |
398 | or LPC bus chips, and so on. | |
399 | ||
400 | Your system will need to define the platform device used by | |
ae64d169 | 401 | this driver, otherwise it won't be accessible. This means |
09a21e56 AZ |
402 | you can safely enable this driver if you don't know whether |
403 | or not your board has this kind of hardware. | |
404 | ||
405 | This driver can also be built as a module. If so, the module | |
406 | will be called rtc-cmos. | |
407 | ||
537739de TB |
408 | config RTC_DRV_DS1216 |
409 | tristate "Dallas DS1216" | |
bb35fb20 | 410 | depends on SNI_RM |
537739de TB |
411 | help |
412 | If you say yes here you get support for the Dallas DS1216 RTC chips. | |
413 | ||
5f119f29 TB |
414 | config RTC_DRV_DS1286 |
415 | tristate "Dallas DS1286" | |
416 | help | |
417 | If you say yes here you get support for the Dallas DS1286 RTC chips. | |
418 | ||
739d340d PM |
419 | config RTC_DRV_DS1302 |
420 | tristate "Dallas DS1302" | |
421 | depends on SH_SECUREEDGE5410 | |
422 | help | |
423 | If you say yes here you get support for the Dallas DS1302 RTC chips. | |
424 | ||
8f26795a AS |
425 | config RTC_DRV_DS1511 |
426 | tristate "Dallas DS1511" | |
427 | depends on RTC_CLASS | |
428 | help | |
429 | If you say yes here you get support for the | |
430 | Dallas DS1511 timekeeping/watchdog chip. | |
431 | ||
432 | This driver can also be built as a module. If so, the module | |
433 | will be called rtc-ds1511. | |
434 | ||
09a21e56 | 435 | config RTC_DRV_DS1553 |
09b6bdb3 | 436 | tristate "Maxim/Dallas DS1553" |
7520b94d AZ |
437 | help |
438 | If you say yes here you get support for the | |
09b6bdb3 | 439 | Maxim/Dallas DS1553 timekeeping chip. |
7520b94d AZ |
440 | |
441 | This driver can also be built as a module. If so, the module | |
09a21e56 AZ |
442 | will be called rtc-ds1553. |
443 | ||
09b6bdb3 AZ |
444 | config RTC_DRV_DS1742 |
445 | tristate "Maxim/Dallas DS1742/1743" | |
02964115 TH |
446 | help |
447 | If you say yes here you get support for the | |
09b6bdb3 | 448 | Maxim/Dallas DS1742/1743 timekeeping chip. |
02964115 TH |
449 | |
450 | This driver can also be built as a module. If so, the module | |
09b6bdb3 | 451 | will be called rtc-ds1742. |
02964115 | 452 | |
5e3fd9e5 | 453 | config RTC_DRV_EFI |
454 | tristate "EFI RTC" | |
455 | depends on IA64 | |
456 | help | |
457 | If you say yes here you will get support for the EFI | |
458 | Real Time Clock. | |
459 | ||
460 | This driver can also be built as a module. If so, the module | |
461 | will be called rtc-efi. | |
462 | ||
09b6bdb3 AZ |
463 | config RTC_DRV_STK17TA8 |
464 | tristate "Simtek STK17TA8" | |
465 | depends on RTC_CLASS | |
09a21e56 AZ |
466 | help |
467 | If you say yes here you get support for the | |
09b6bdb3 | 468 | Simtek STK17TA8 timekeeping chip. |
09a21e56 AZ |
469 | |
470 | This driver can also be built as a module. If so, the module | |
09b6bdb3 | 471 | will be called rtc-stk17ta8. |
09a21e56 AZ |
472 | |
473 | config RTC_DRV_M48T86 | |
474 | tristate "ST M48T86/Dallas DS12887" | |
09a21e56 AZ |
475 | help |
476 | If you say Y here you will get support for the | |
477 | ST M48T86 and Dallas DS12887 RTC chips. | |
478 | ||
479 | This driver can also be built as a module. If so, the module | |
480 | will be called rtc-m48t86. | |
481 | ||
d1dbd82e TB |
482 | config RTC_DRV_M48T35 |
483 | tristate "ST M48T35" | |
484 | help | |
485 | If you say Y here you will get support for the | |
486 | ST M48T35 RTC chip. | |
487 | ||
488 | This driver can also be built as a module, if so, the module | |
489 | will be called "rtc-m48t35". | |
490 | ||
2e774c7c | 491 | config RTC_DRV_M48T59 |
94fe7424 | 492 | tristate "ST M48T59/M48T08/M48T02" |
2e774c7c MZ |
493 | help |
494 | If you say Y here you will get support for the | |
94fe7424 KH |
495 | ST M48T59 RTC chip and compatible ST M48T08 and M48T02. |
496 | ||
497 | These chips are usually found in Sun SPARC and UltraSPARC | |
498 | workstations. | |
2e774c7c MZ |
499 | |
500 | This driver can also be built as a module, if so, the module | |
501 | will be called "rtc-m48t59". | |
502 | ||
cca4c231 DM |
503 | config RTC_DRV_BQ4802 |
504 | tristate "TI BQ4802" | |
505 | help | |
506 | If you say Y here you will get support for the TI | |
507 | BQ4802 RTC chip. | |
508 | ||
509 | This driver can also be built as a module. If so, the module | |
510 | will be called rtc-bq4802. | |
511 | ||
09a21e56 AZ |
512 | config RTC_DRV_V3020 |
513 | tristate "EM Microelectronic V3020" | |
09a21e56 AZ |
514 | help |
515 | If you say yes here you will get support for the | |
516 | EM Microelectronic v3020 RTC chip. | |
517 | ||
518 | This driver can also be built as a module. If so, the module | |
519 | will be called rtc-v3020. | |
520 | ||
077eaf5b MB |
521 | config RTC_DRV_WM8350 |
522 | tristate "Wolfson Microelectronics WM8350 RTC" | |
523 | depends on MFD_WM8350 | |
524 | help | |
525 | If you say yes here you will get support for the RTC subsystem | |
526 | of the Wolfson Microelectronics WM8350. | |
527 | ||
528 | This driver can also be built as a module. If so, the module | |
529 | will be called "rtc-wm8350". | |
530 | ||
eae854b2 BR |
531 | config RTC_DRV_PCF50633 |
532 | depends on MFD_PCF50633 | |
533 | tristate "NXP PCF50633 RTC" | |
534 | help | |
535 | If you say yes here you get support for the RTC subsystem of the | |
536 | NXP PCF50633 used in embedded systems. | |
537 | ||
09a21e56 | 538 | comment "on-CPU RTC drivers" |
09a21e56 AZ |
539 | |
540 | config RTC_DRV_OMAP | |
541 | tristate "TI OMAP1" | |
bb35fb20 | 542 | depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 |
09a21e56 AZ |
543 | help |
544 | Say "yes" here to support the real time clock on TI OMAP1 chips. | |
545 | This driver can also be built as a module called rtc-omap. | |
7520b94d | 546 | |
1add6781 BD |
547 | config RTC_DRV_S3C |
548 | tristate "Samsung S3C series SoC RTC" | |
bb35fb20 | 549 | depends on ARCH_S3C2410 |
1add6781 BD |
550 | help |
551 | RTC (Realtime Clock) driver for the clock inbuilt into the | |
552 | Samsung S3C24XX series of SoCs. This can provide periodic | |
553 | interrupt rates from 1Hz to 64Hz for user programs, and | |
554 | wakeup from Alarm. | |
555 | ||
556 | The driver currently supports the common features on all the | |
557 | S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 | |
558 | and S3C2442. | |
559 | ||
560 | This driver can also be build as a module. If so, the module | |
561 | will be called rtc-s3c. | |
562 | ||
fd507e2f AZ |
563 | config RTC_DRV_EP93XX |
564 | tristate "Cirrus Logic EP93XX" | |
bb35fb20 | 565 | depends on ARCH_EP93XX |
fd507e2f AZ |
566 | help |
567 | If you say yes here you get support for the | |
568 | RTC embedded in the Cirrus Logic EP93XX processors. | |
569 | ||
570 | This driver can also be built as a module. If so, the module | |
571 | will be called rtc-ep93xx. | |
572 | ||
e842f1c8 RP |
573 | config RTC_DRV_SA1100 |
574 | tristate "SA11x0/PXA2xx" | |
bb35fb20 | 575 | depends on ARCH_SA1100 || ARCH_PXA |
e842f1c8 RP |
576 | help |
577 | If you say Y here you will get access to the real time clock | |
578 | built into your SA11x0 or PXA2xx CPU. | |
579 | ||
580 | To compile this driver as a module, choose M here: the | |
581 | module will be called rtc-sa1100. | |
fd507e2f | 582 | |
317a6104 PM |
583 | config RTC_DRV_SH |
584 | tristate "SuperH On-Chip RTC" | |
063adc75 | 585 | depends on RTC_CLASS && SUPERH && HAVE_CLK |
317a6104 PM |
586 | help |
587 | Say Y here to enable support for the on-chip RTC found in | |
588 | most SuperH processors. | |
589 | ||
590 | To compile this driver as a module, choose M here: the | |
591 | module will be called rtc-sh. | |
592 | ||
8417eb7a | 593 | config RTC_DRV_VR41XX |
3e16f6af | 594 | tristate "NEC VR41XX" |
bb35fb20 | 595 | depends on CPU_VR41XX |
3e16f6af AZ |
596 | help |
597 | If you say Y here you will get access to the real time clock | |
598 | built into your NEC VR41XX CPU. | |
599 | ||
600 | To compile this driver as a module, choose M here: the | |
601 | module will be called rtc-vr41xx. | |
8417eb7a | 602 | |
a190901c RK |
603 | config RTC_DRV_PL030 |
604 | tristate "ARM AMBA PL030 RTC" | |
605 | depends on ARM_AMBA | |
606 | help | |
607 | If you say Y here you will get access to ARM AMBA | |
608 | PrimeCell PL030 RTC found on certain ARM SOCs. | |
609 | ||
610 | To compile this driver as a module, choose M here: the | |
611 | module will be called rtc-pl030. | |
612 | ||
8ae6e163 DS |
613 | config RTC_DRV_PL031 |
614 | tristate "ARM AMBA PL031 RTC" | |
bb35fb20 | 615 | depends on ARM_AMBA |
8ae6e163 DS |
616 | help |
617 | If you say Y here you will get access to ARM AMBA | |
09a21e56 | 618 | PrimeCell PL031 RTC found on certain ARM SOCs. |
8ae6e163 DS |
619 | |
620 | To compile this driver as a module, choose M here: the | |
621 | module will be called rtc-pl031. | |
622 | ||
fa04e78b HCE |
623 | config RTC_DRV_AT32AP700X |
624 | tristate "AT32AP700X series RTC" | |
bb35fb20 | 625 | depends on PLATFORM_AT32AP |
fa04e78b HCE |
626 | help |
627 | Driver for the internal RTC (Realtime Clock) on Atmel AVR32 | |
628 | AT32AP700x family processors. | |
629 | ||
7fc39f6d | 630 | config RTC_DRV_AT91RM9200 |
4cdf854f DB |
631 | tristate "AT91RM9200 or AT91SAM9RL" |
632 | depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL | |
633 | help | |
634 | Driver for the internal RTC (Realtime Clock) module found on | |
ae64d169 | 635 | Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips |
4cdf854f DB |
636 | this is powered by the backup power supply. |
637 | ||
638 | config RTC_DRV_AT91SAM9 | |
6b71dbf6 | 639 | tristate "AT91SAM9x/AT91CAP9" |
4cdf854f DB |
640 | depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40) |
641 | help | |
6b71dbf6 SP |
642 | RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT |
643 | (Real Time Timer). These timers are powered by the backup power | |
644 | supply (such as a small coin cell battery), but do not need to | |
645 | be used as RTCs. | |
4cdf854f DB |
646 | |
647 | (On AT91SAM9rl chips you probably want to use the dedicated RTC | |
648 | module and leave the RTT available for other uses.) | |
649 | ||
650 | config RTC_DRV_AT91SAM9_RTT | |
651 | int | |
652 | range 0 1 | |
653 | default 0 | |
654 | prompt "RTT module Number" if ARCH_AT91SAM9263 | |
655 | depends on RTC_DRV_AT91SAM9 | |
656 | help | |
ae64d169 AZ |
657 | More than one RTT module is available. You can choose which |
658 | one will be used as an RTC. The default of zero is normally | |
4cdf854f DB |
659 | OK to use, though some systems use that for non-RTC purposes. |
660 | ||
661 | config RTC_DRV_AT91SAM9_GPBR | |
662 | int | |
663 | range 0 3 if !ARCH_AT91SAM9263 | |
664 | range 0 15 if ARCH_AT91SAM9263 | |
665 | default 0 | |
666 | prompt "Backup Register Number" | |
667 | depends on RTC_DRV_AT91SAM9 | |
668 | help | |
669 | The RTC driver needs to use one of the General Purpose Backup | |
ae64d169 AZ |
670 | Registers (GPBRs) as well as the RTT. You can choose which one |
671 | will be used. The default of zero is normally OK to use, but | |
4cdf854f | 672 | on some systems other software needs to use that register. |
788b1fc6 | 673 | |
45fd8a0c ML |
674 | config RTC_DRV_AU1XXX |
675 | tristate "Au1xxx Counter0 RTC support" | |
676 | depends on SOC_AU1X00 | |
677 | help | |
678 | This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year | |
679 | counter) to be used as a RTC. | |
680 | ||
681 | This driver can also be built as a module. If so, the module | |
682 | will be called rtc-au1xxx. | |
683 | ||
8cc75c9a WB |
684 | config RTC_DRV_BFIN |
685 | tristate "Blackfin On-Chip RTC" | |
7f604599 | 686 | depends on BLACKFIN && !BF561 |
8cc75c9a WB |
687 | help |
688 | If you say yes here you will get support for the | |
689 | Blackfin On-Chip Real Time Clock. | |
690 | ||
691 | This driver can also be built as a module. If so, the module | |
692 | will be called rtc-bfin. | |
693 | ||
e9f2bd81 NI |
694 | config RTC_DRV_RS5C313 |
695 | tristate "Ricoh RS5C313" | |
bb35fb20 | 696 | depends on SH_LANDISK |
e9f2bd81 NI |
697 | help |
698 | If you say yes here you get support for the Ricoh RS5C313 RTC chips. | |
699 | ||
3afe6d04 GU |
700 | config RTC_DRV_GENERIC |
701 | tristate "Generic RTC support" | |
702 | # Please consider writing a new RTC driver instead of using the generic | |
703 | # RTC abstraction | |
47c8a08b | 704 | depends on PARISC || M68K || PPC || SUPERH32 |
9eb16864 | 705 | help |
3afe6d04 GU |
706 | Say Y or M here to enable RTC support on systems using the generic |
707 | RTC abstraction. If you do not know what you are doing, you should | |
9eb16864 KM |
708 | just say Y. |
709 | ||
dc944368 RJ |
710 | config RTC_DRV_PXA |
711 | tristate "PXA27x/PXA3xx" | |
712 | depends on ARCH_PXA | |
713 | help | |
714 | If you say Y here you will get access to the real time clock | |
715 | built into your PXA27x or PXA3xx CPU. | |
716 | ||
717 | This RTC driver uses PXA RTC registers available since pxa27x | |
718 | series (RDxR, RYxR) instead of legacy RCNR, RTAR. | |
719 | ||
720 | ||
7a138ede DM |
721 | config RTC_DRV_SUN4V |
722 | bool "SUN4V Hypervisor RTC" | |
723 | depends on SPARC64 | |
724 | help | |
725 | If you say Y here you will get support for the Hypervisor | |
726 | based RTC on SUN4V systems. | |
727 | ||
de2cf332 DM |
728 | config RTC_DRV_STARFIRE |
729 | bool "Starfire RTC" | |
730 | depends on SPARC64 | |
731 | help | |
732 | If you say Y here you will get support for the RTC found on | |
733 | Starfire systems. | |
734 | ||
0e149233 AN |
735 | config RTC_DRV_TX4939 |
736 | tristate "TX4939 SoC" | |
737 | depends on SOC_TX4939 | |
738 | help | |
739 | Driver for the internal RTC (Realtime Clock) module found on | |
740 | Toshiba TX4939 SoC. | |
741 | ||
defb4514 SB |
742 | config RTC_DRV_MV |
743 | tristate "Marvell SoC RTC" | |
744 | depends on ARCH_KIRKWOOD | |
745 | help | |
746 | If you say yes here you will get support for the in-chip RTC | |
747 | that can be found in some of Marvell's SoC devices, such as | |
748 | the Kirkwood 88F6281 and 88F6192. | |
749 | ||
750 | This driver can also be built as a module. If so, the module | |
751 | will be called rtc-mv. | |
752 | ||
0b5f037a GU |
753 | config RTC_DRV_PS3 |
754 | tristate "PS3 RTC" | |
755 | depends on PPC_PS3 | |
756 | help | |
757 | If you say yes here you will get support for the RTC on PS3. | |
758 | ||
759 | This driver can also be built as a module. If so, the module | |
760 | will be called rtc-ps3. | |
761 | ||
bb35fb20 | 762 | endif # RTC_CLASS |