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