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