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