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