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