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 AZ |
27 | |
28 | config RTC_HCTOSYS_DEVICE | |
7ca1d488 | 29 | string "RTC used to set the system time" |
9c5150b3 | 30 | depends on RTC_HCTOSYS |
0c86edc0 AZ |
31 | default "rtc0" |
32 | help | |
7ca1d488 | 33 | The RTC device that will be used to (re)initialize the system |
ae64d169 AZ |
34 | clock, usually rtc0. Initialization is done when the system |
35 | starts up, and when it resumes from a low power state. This | |
779d2089 DB |
36 | device should record time in UTC, since the kernel won't do |
37 | timezone correction. | |
7ca1d488 | 38 | |
55ff1aba DB |
39 | The driver for this RTC device must be loaded before late_initcall |
40 | functions run, so it must usually be statically linked. | |
41 | ||
7ca1d488 | 42 | This clock should be battery-backed, so that it reads the correct |
ae64d169 | 43 | time when the system boots from a power-off state. Otherwise, your |
7ca1d488 DB |
44 | system will need an external clock source (like an NTP server). |
45 | ||
46 | If the clock you specify here is not battery backed, it may still | |
47 | be useful to reinitialize system time when resuming from system | |
09b6bdb3 | 48 | sleep states. Do not specify an RTC here unless it stays powered |
7ca1d488 | 49 | during all this system's supported sleep states. |
0c86edc0 | 50 | |
9c5150b3 XP |
51 | config RTC_SYSTOHC |
52 | bool "Set the RTC time based on NTP synchronization" | |
53 | default y | |
54 | help | |
55 | If you say yes here, the system time (wall clock) will be stored | |
56 | in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11 | |
57 | minutes if userspace reports synchronized NTP status. | |
58 | ||
59 | config RTC_SYSTOHC_DEVICE | |
60 | string "RTC used to synchronize NTP adjustment" | |
61 | depends on RTC_SYSTOHC | |
62 | default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS | |
63 | default "rtc0" | |
64 | help | |
65 | The RTC device used for NTP synchronization. The main difference | |
66 | between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this | |
67 | one can sleep when setting time, because it runs in the workqueue | |
68 | context. | |
69 | ||
9e86ecb6 DB |
70 | config RTC_DEBUG |
71 | bool "RTC debug support" | |
9e86ecb6 DB |
72 | help |
73 | Say yes here to enable debugging support in the RTC framework | |
74 | and individual RTC drivers. | |
75 | ||
0c86edc0 | 76 | comment "RTC interfaces" |
0c86edc0 | 77 | |
c5c3e192 | 78 | config RTC_INTF_SYSFS |
6341e62b | 79 | bool "/sys/class/rtc/rtcN (sysfs)" |
bb35fb20 | 80 | depends on SYSFS |
8dc08395 | 81 | default RTC_CLASS |
c5c3e192 | 82 | help |
9e86ecb6 DB |
83 | Say yes here if you want to use your RTCs using sysfs interfaces, |
84 | /sys/class/rtc/rtc0 through /sys/.../rtcN. | |
c5c3e192 | 85 | |
ae64d169 | 86 | If unsure, say Y. |
c5c3e192 | 87 | |
728a2947 | 88 | config RTC_INTF_PROC |
6341e62b | 89 | bool "/proc/driver/rtc (procfs for rtcN)" |
bb35fb20 | 90 | depends on PROC_FS |
8dc08395 | 91 | default RTC_CLASS |
728a2947 | 92 | help |
92589c98 KM |
93 | Say yes here if you want to use your system clock RTC through |
94 | the proc interface, /proc/driver/rtc. | |
95 | Other RTCs will not be available through that API. | |
96 | If there is no RTC for the system clock, then the first RTC(rtc0) | |
97 | is used by default. | |
728a2947 | 98 | |
ae64d169 | 99 | If unsure, say Y. |
728a2947 | 100 | |
e824290e | 101 | config RTC_INTF_DEV |
6341e62b | 102 | bool "/dev/rtcN (character devices)" |
8dc08395 | 103 | default RTC_CLASS |
e824290e | 104 | help |
9e86ecb6 DB |
105 | Say yes here if you want to use your RTCs using the /dev |
106 | interfaces, which "udev" sets up as /dev/rtc0 through | |
ae64d169 | 107 | /dev/rtcN. |
e824290e | 108 | |
ae64d169 AZ |
109 | You may want to set up a symbolic link so one of these |
110 | can be accessed as /dev/rtc, which is a name | |
111 | expected by "hwclock" and some other programs. Recent | |
112 | versions of "udev" are known to set up the symlink for you. | |
113 | ||
114 | If unsure, say Y. | |
e824290e | 115 | |
6e57b1d6 JS |
116 | config RTC_INTF_DEV_UIE_EMUL |
117 | bool "RTC UIE emulation on dev interface" | |
118 | depends on RTC_INTF_DEV | |
119 | help | |
120 | Provides an emulation for RTC_UIE if the underlying rtc chip | |
121 | driver does not expose RTC_UIE ioctls. Those requests generate | |
122 | once-per-second update interrupts, used for synchronization. | |
123 | ||
124 | The emulation code will read the time from the hardware | |
125 | clock several times per second, please enable this option | |
126 | only if you know that you really need it. | |
127 | ||
09a21e56 AZ |
128 | config RTC_DRV_TEST |
129 | tristate "Test driver/device" | |
1fec7c66 AZ |
130 | help |
131 | If you say yes here you get support for the | |
09a21e56 AZ |
132 | RTC test driver. It's a software RTC which can be |
133 | used to test the RTC subsystem APIs. It gets | |
134 | the time from the system clock. | |
135 | You want this driver only if you are doing development | |
136 | on the RTC subsystem. Please read the source code | |
137 | for further details. | |
1fec7c66 AZ |
138 | |
139 | This driver can also be built as a module. If so, the module | |
09a21e56 AZ |
140 | will be called rtc-test. |
141 | ||
142 | comment "I2C RTC drivers" | |
bb35fb20 JE |
143 | depends on I2C |
144 | ||
145 | if I2C | |
1fec7c66 | 146 | |
008b3040 HZ |
147 | config RTC_DRV_88PM860X |
148 | tristate "Marvell 88PM860x" | |
6b8029fa | 149 | depends on I2C && MFD_88PM860X |
008b3040 HZ |
150 | help |
151 | If you say yes here you get support for RTC function in Marvell | |
152 | 88PM860x chips. | |
153 | ||
154 | This driver can also be built as a module. If so, the module | |
155 | will be called rtc-88pm860x. | |
156 | ||
2985c29c QZ |
157 | config RTC_DRV_88PM80X |
158 | tristate "Marvell 88PM80x" | |
6b8029fa | 159 | depends on I2C && MFD_88PM800 |
2985c29c QZ |
160 | help |
161 | If you say yes here you get support for RTC function in Marvell | |
162 | 88PM80x chips. | |
163 | ||
164 | This driver can also be built as a module. If so, the module | |
165 | will be called rtc-88pm80x. | |
166 | ||
0b2f6228 AE |
167 | config RTC_DRV_ABB5ZES3 |
168 | depends on I2C | |
169 | select REGMAP_I2C | |
170 | tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3" | |
171 | help | |
172 | If you say yes here you get support for the Abracon | |
173 | AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip. | |
174 | ||
175 | This driver can also be built as a module. If so, the module | |
176 | will be called rtc-ab-b5ze-s3. | |
177 | ||
4d61ff6b PDM |
178 | config RTC_DRV_ABX80X |
179 | tristate "Abracon ABx80x" | |
180 | help | |
181 | If you say yes here you get support for Abracon AB080X and AB180X | |
182 | families of ultra-low-power battery- and capacitor-backed real-time | |
183 | clock chips. | |
184 | ||
185 | This driver can also be built as a module. If so, the module | |
186 | will be called rtc-abx80x. | |
187 | ||
b4506261 LD |
188 | config RTC_DRV_AS3722 |
189 | tristate "ams AS3722 RTC driver" | |
190 | depends on MFD_AS3722 | |
191 | help | |
192 | If you say yes here you get support for the RTC of ams AS3722 PMIC | |
193 | chips. | |
194 | ||
195 | This driver can also be built as a module. If so, the module | |
196 | will be called rtc-as3722. | |
197 | ||
1abb0dc9 | 198 | config RTC_DRV_DS1307 |
a2166858 | 199 | tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025" |
1abb0dc9 DB |
200 | help |
201 | If you say yes here you get support for various compatible RTC | |
ae64d169 | 202 | chips (often with battery backup) connected with I2C. This driver |
1abb0dc9 | 203 | should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00, |
a2166858 MF |
204 | EPSON RX-8025 and probably other chips. In some cases the RTC |
205 | must already have been initialized (by manufacturing or a | |
206 | bootloader). | |
1abb0dc9 DB |
207 | |
208 | The first seven registers on these chips hold an RTC, and other | |
209 | registers may add features such as NVRAM, a trickle charger for | |
ae64d169 | 210 | the RTC/NVRAM backup power, and alarms. NVRAM is visible in |
682d73f6 | 211 | sysfs, but other chip features may not be available. |
1abb0dc9 DB |
212 | |
213 | This driver can also be built as a module. If so, the module | |
214 | will be called rtc-ds1307. | |
215 | ||
bf4994d7 | 216 | config RTC_DRV_DS1374 |
09b6bdb3 | 217 | tristate "Dallas/Maxim DS1374" |
6b8029fa | 218 | depends on I2C |
bf4994d7 SW |
219 | help |
220 | If you say yes here you get support for Dallas Semiconductor | |
ae64d169 | 221 | DS1374 real-time clock chips. If an interrupt is associated |
bf4994d7 SW |
222 | with the device, the alarm functionality is supported. |
223 | ||
ae64d169 | 224 | This driver can also be built as a module. If so, the module |
bf4994d7 SW |
225 | will be called rtc-ds1374. |
226 | ||
920f91e5 SA |
227 | config RTC_DRV_DS1374_WDT |
228 | bool "Dallas/Maxim DS1374 watchdog timer" | |
229 | depends on RTC_DRV_DS1374 | |
230 | help | |
231 | If you say Y here you will get support for the | |
232 | watchdog timer in the Dallas Semiconductor DS1374 | |
233 | real-time clock chips. | |
234 | ||
09a21e56 AZ |
235 | config RTC_DRV_DS1672 |
236 | tristate "Dallas/Maxim DS1672" | |
9bf5b4f5 AN |
237 | help |
238 | If you say yes here you get support for the | |
09a21e56 | 239 | Dallas/Maxim DS1672 timekeeping chip. |
9bf5b4f5 AN |
240 | |
241 | This driver can also be built as a module. If so, the module | |
09a21e56 | 242 | will be called rtc-ds1672. |
9bf5b4f5 | 243 | |
c03675f0 RZ |
244 | config RTC_DRV_DS3232 |
245 | tristate "Dallas/Maxim DS3232" | |
6b8029fa | 246 | depends on I2C |
c03675f0 RZ |
247 | help |
248 | If you say yes here you get support for Dallas Semiconductor | |
f46418c5 LCB |
249 | DS3232 real-time clock chips. If an interrupt is associated |
250 | with the device, the alarm functionality is supported. | |
c03675f0 RZ |
251 | |
252 | This driver can also be built as a module. If so, the module | |
253 | will be called rtc-ds3232. | |
254 | ||
dcaf0384 HS |
255 | config RTC_DRV_HYM8563 |
256 | tristate "Haoyu Microelectronics HYM8563" | |
257 | depends on I2C && OF | |
258 | help | |
259 | Say Y to enable support for the HYM8563 I2C RTC chip. Apart | |
260 | from the usual rtc functions it provides a clock output of | |
261 | up to 32kHz. | |
262 | ||
263 | This driver can also be built as a module. If so, the module | |
264 | will be called rtc-hym8563. | |
265 | ||
38ae176e KM |
266 | config RTC_DRV_LP8788 |
267 | tristate "TI LP8788 RTC driver" | |
268 | depends on MFD_LP8788 | |
269 | help | |
270 | Say Y to enable support for the LP8788 RTC/ALARM driver. | |
271 | ||
09a21e56 | 272 | config RTC_DRV_MAX6900 |
09b6bdb3 | 273 | tristate "Maxim MAX6900" |
7e56a7dc | 274 | help |
09a21e56 AZ |
275 | If you say yes here you will get support for the |
276 | Maxim MAX6900 I2C RTC chip. | |
7e56a7dc HVR |
277 | |
278 | This driver can also be built as a module. If so, the module | |
09a21e56 | 279 | will be called rtc-max6900. |
7e56a7dc | 280 | |
94c01ab6 SW |
281 | config RTC_DRV_MAX8907 |
282 | tristate "Maxim MAX8907" | |
283 | depends on MFD_MAX8907 | |
284 | help | |
285 | If you say yes here you will get support for the | |
286 | RTC of Maxim MAX8907 PMIC. | |
287 | ||
288 | This driver can also be built as a module. If so, the module | |
289 | will be called rtc-max8907. | |
290 | ||
a39069f6 HZ |
291 | config RTC_DRV_MAX8925 |
292 | tristate "Maxim MAX8925" | |
293 | depends on MFD_MAX8925 | |
294 | help | |
295 | If you say yes here you will get support for the | |
296 | RTC of Maxim MAX8925 PMIC. | |
297 | ||
298 | This driver can also be built as a module. If so, the module | |
299 | will be called rtc-max8925. | |
300 | ||
9b16c0a4 JS |
301 | config RTC_DRV_MAX8998 |
302 | tristate "Maxim MAX8998" | |
303 | depends on MFD_MAX8998 | |
304 | help | |
305 | If you say yes here you will get support for the | |
306 | RTC of Maxim MAX8998 PMIC. | |
307 | ||
308 | This driver can also be built as a module. If so, the module | |
309 | will be called rtc-max8998. | |
310 | ||
5e0b2704 JL |
311 | config RTC_DRV_MAX8997 |
312 | tristate "Maxim MAX8997" | |
313 | depends on MFD_MAX8997 | |
314 | help | |
315 | If you say yes here you will get support for the | |
316 | RTC of Maxim MAX8997 PMIC. | |
317 | ||
318 | This driver can also be built as a module. If so, the module | |
319 | will be called rtc-max8997. | |
320 | ||
fca1dd03 JL |
321 | config RTC_DRV_MAX77686 |
322 | tristate "Maxim MAX77686" | |
323 | depends on MFD_MAX77686 | |
324 | help | |
325 | If you say yes here you will get support for the | |
326 | RTC of Maxim MAX77686 PMIC. | |
327 | ||
328 | This driver can also be built as a module. If so, the module | |
329 | will be called rtc-max77686. | |
330 | ||
3ca1e326 CZ |
331 | config RTC_DRV_RK808 |
332 | tristate "Rockchip RK808 RTC" | |
333 | depends on MFD_RK808 | |
334 | help | |
335 | If you say yes here you will get support for the | |
336 | RTC of RK808 PMIC. | |
337 | ||
338 | This driver can also be built as a module. If so, the module | |
339 | will be called rk808-rtc. | |
340 | ||
a4d4121b JMC |
341 | config RTC_DRV_MAX77802 |
342 | tristate "Maxim 77802 RTC" | |
343 | depends on MFD_MAX77686 | |
344 | help | |
345 | If you say yes here you will get support for the | |
346 | RTC of Maxim MAX77802 PMIC. | |
347 | ||
348 | This driver can also be built as a module. If so, the module | |
349 | will be called rtc-max77802. | |
350 | ||
09a21e56 | 351 | config RTC_DRV_RS5C372 |
5d4529be | 352 | tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A" |
edf1aaa3 AZ |
353 | help |
354 | If you say yes here you get support for the | |
5d4529be | 355 | Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. |
edf1aaa3 AZ |
356 | |
357 | This driver can also be built as a module. If so, the module | |
09a21e56 | 358 | will be called rtc-rs5c372. |
edf1aaa3 | 359 | |
09a21e56 | 360 | config RTC_DRV_ISL1208 |
09b6bdb3 | 361 | tristate "Intersil ISL1208" |
5ec3e4b7 AN |
362 | help |
363 | If you say yes here you get support for the | |
09b6bdb3 | 364 | Intersil ISL1208 RTC chip. |
5ec3e4b7 AN |
365 | |
366 | This driver can also be built as a module. If so, the module | |
09a21e56 | 367 | will be called rtc-isl1208. |
5ec3e4b7 | 368 | |
d6c7428f RF |
369 | config RTC_DRV_ISL12022 |
370 | tristate "Intersil ISL12022" | |
371 | help | |
372 | If you say yes here you get support for the | |
373 | Intersil ISL12022 RTC chip. | |
374 | ||
375 | This driver can also be built as a module. If so, the module | |
376 | will be called rtc-isl12022. | |
377 | ||
70e12337 AE |
378 | config RTC_DRV_ISL12057 |
379 | depends on I2C | |
380 | select REGMAP_I2C | |
381 | tristate "Intersil ISL12057" | |
382 | help | |
383 | If you say yes here you get support for the Intersil ISL12057 | |
384 | I2C RTC chip. | |
385 | ||
386 | This driver can also be built as a module. If so, the module | |
387 | will be called rtc-isl12057. | |
388 | ||
09a21e56 AZ |
389 | config RTC_DRV_X1205 |
390 | tristate "Xicor/Intersil X1205" | |
db68b189 | 391 | help |
09a21e56 AZ |
392 | If you say yes here you get support for the |
393 | Xicor/Intersil X1205 RTC chip. | |
394 | ||
395 | This driver can also be built as a module. If so, the module | |
396 | will be called rtc-x1205. | |
db68b189 | 397 | |
0101e53c LD |
398 | config RTC_DRV_PALMAS |
399 | tristate "TI Palmas RTC driver" | |
400 | depends on MFD_PALMAS | |
401 | help | |
402 | If you say yes here you get support for the RTC of TI PALMA series PMIC | |
403 | chips. | |
404 | ||
405 | This driver can also be built as a module. If so, the module | |
406 | will be called rtc-palma. | |
407 | ||
18cb6368 RC |
408 | config RTC_DRV_PCF2127 |
409 | tristate "NXP PCF2127" | |
410 | help | |
411 | If you say yes here you get support for the NXP PCF2127/29 RTC | |
412 | chips. | |
413 | ||
414 | This driver can also be built as a module. If so, the module | |
415 | will be called rtc-pcf2127. | |
416 | ||
f803f0d0 TR |
417 | config RTC_DRV_PCF8523 |
418 | tristate "NXP PCF8523" | |
419 | help | |
420 | If you say yes here you get support for the NXP PCF8523 RTC | |
421 | chips. | |
422 | ||
423 | This driver can also be built as a module. If so, the module | |
424 | will be called rtc-pcf8523. | |
425 | ||
b5a82d62 AZ |
426 | config RTC_DRV_PCF8563 |
427 | tristate "Philips PCF8563/Epson RTC8564" | |
b5a82d62 AZ |
428 | help |
429 | If you say yes here you get support for the | |
430 | Philips PCF8563 RTC chip. The Epson RTC8564 | |
431 | should work as well. | |
432 | ||
433 | This driver can also be built as a module. If so, the module | |
434 | will be called rtc-pcf8563. | |
435 | ||
796b7abb SA |
436 | config RTC_DRV_PCF85063 |
437 | tristate "nxp PCF85063" | |
438 | help | |
439 | If you say yes here you get support for the PCF85063 RTC chip | |
440 | ||
441 | This driver can also be built as a module. If so, the module | |
442 | will be called rtc-pcf85063. | |
443 | ||
9c0c5705 L |
444 | config RTC_DRV_PCF8583 |
445 | tristate "Philips PCF8583" | |
9c0c5705 | 446 | help |
bb71f99f | 447 | If you say yes here you get support for the Philips PCF8583 |
09a21e56 | 448 | RTC chip found on Acorn RiscPCs. This driver supports the |
bb71f99f | 449 | platform specific method of retrieving the current year from |
09a21e56 AZ |
450 | the RTC's SRAM. It will work on other platforms with the same |
451 | chip, but the year will probably have to be tweaked. | |
9c0c5705 L |
452 | |
453 | This driver can also be built as a module. If so, the module | |
454 | will be called rtc-pcf8583. | |
455 | ||
caaff562 | 456 | config RTC_DRV_M41T80 |
6b1a5235 | 457 | tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible" |
caaff562 | 458 | help |
d3a126fc SF |
459 | If you say Y here you will get support for the ST M41T60 |
460 | and M41T80 RTC chips series. Currently, the following chips are | |
f30281f4 | 461 | supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84, |
6b1a5235 | 462 | M41ST85, M41ST87, and MicroCrystal RV4162. |
caaff562 AN |
463 | |
464 | This driver can also be built as a module. If so, the module | |
465 | will be called rtc-m41t80. | |
466 | ||
617780d2 | 467 | config RTC_DRV_M41T80_WDT |
d3a126fc | 468 | bool "ST M41T65/M41T80 series RTC watchdog timer" |
617780d2 AN |
469 | depends on RTC_DRV_M41T80 |
470 | help | |
471 | If you say Y here you will get support for the | |
d3a126fc | 472 | watchdog timer in the ST M41T60 and M41T80 RTC chips series. |
617780d2 | 473 | |
1ce7c83f PZ |
474 | config RTC_DRV_BQ32K |
475 | tristate "TI BQ32000" | |
476 | help | |
477 | If you say Y here you will get support for the TI | |
478 | BQ32000 I2C RTC chip. | |
479 | ||
480 | This driver can also be built as a module. If so, the module | |
481 | will be called rtc-bq32k. | |
482 | ||
afd8d0f9 DB |
483 | config RTC_DRV_DM355EVM |
484 | tristate "TI DaVinci DM355 EVM RTC" | |
485 | depends on MFD_DM355EVM_MSP | |
486 | help | |
487 | Supports the RTC firmware in the MSP430 on the DM355 EVM. | |
488 | ||
0c4a59fe | 489 | config RTC_DRV_TWL92330 |
6341e62b | 490 | bool "TI TWL92330/Menelaus" |
bb35fb20 | 491 | depends on MENELAUS |
0c4a59fe TL |
492 | help |
493 | If you say yes here you get support for the RTC on the | |
01dd2fbf | 494 | TWL92330 "Menelaus" power management chip, used with OMAP2 |
ae64d169 | 495 | platforms. The support is integrated with the rest of |
0c4a59fe TL |
496 | the Menelaus driver; it's not separate module. |
497 | ||
f96411ab | 498 | config RTC_DRV_TWL4030 |
a6b49ffd | 499 | tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0" |
6b8029fa | 500 | depends on TWL4030_CORE |
f96411ab DB |
501 | help |
502 | If you say yes here you get support for the RTC on the | |
a6b49ffd | 503 | TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms. |
f96411ab DB |
504 | |
505 | This driver can also be built as a module. If so, the module | |
a6b49ffd | 506 | will be called rtc-twl. |
f96411ab | 507 | |
dc59ed38 LD |
508 | config RTC_DRV_TPS6586X |
509 | tristate "TI TPS6586X RTC driver" | |
510 | depends on MFD_TPS6586X | |
511 | help | |
a895d57d | 512 | TI Power Management IC TPS6586X supports RTC functionality |
dc59ed38 LD |
513 | along with alarm. This driver supports the RTC driver for |
514 | the TPS6586X RTC module. | |
515 | ||
0e783980 VB |
516 | config RTC_DRV_TPS65910 |
517 | tristate "TI TPS65910 RTC driver" | |
518 | depends on RTC_CLASS && MFD_TPS65910 | |
519 | help | |
520 | If you say yes here you get support for the RTC on the | |
521 | TPS65910 chips. | |
522 | ||
523 | This driver can also be built as a module. If so, the module | |
524 | will be called rtc-tps65910. | |
525 | ||
36d61824 LD |
526 | config RTC_DRV_TPS80031 |
527 | tristate "TI TPS80031/TPS80032 RTC driver" | |
528 | depends on MFD_TPS80031 | |
529 | help | |
a895d57d | 530 | TI Power Management IC TPS80031 supports RTC functionality |
36d61824 LD |
531 | along with alarm. This driver supports the RTC driver for |
532 | the TPS80031 RTC module. | |
533 | ||
90829c08 VB |
534 | config RTC_DRV_RC5T583 |
535 | tristate "RICOH 5T583 RTC driver" | |
536 | depends on MFD_RC5T583 | |
537 | help | |
538 | If you say yes here you get support for the RTC on the | |
539 | RICOH 5T583 chips. | |
540 | ||
541 | This driver can also be built as a module. If so, the module | |
542 | will be called rtc-rc5t583. | |
543 | ||
c46288b0 BB |
544 | config RTC_DRV_S35390A |
545 | tristate "Seiko Instruments S-35390A" | |
d479540d | 546 | select BITREVERSE |
c46288b0 BB |
547 | help |
548 | If you say yes here you will get support for the Seiko | |
549 | Instruments S-35390A. | |
550 | ||
551 | This driver can also be built as a module. If so the module | |
552 | will be called rtc-s35390a. | |
553 | ||
c6d8f400 SL |
554 | config RTC_DRV_FM3130 |
555 | tristate "Ramtron FM3130" | |
556 | help | |
557 | If you say Y here you will get support for the | |
558 | Ramtron FM3130 RTC chips. | |
559 | Ramtron FM3130 is a chip with two separate devices inside, | |
560 | RTC clock and FRAM. This driver provides only RTC functionality. | |
561 | ||
562 | This driver can also be built as a module. If so the module | |
563 | will be called rtc-fm3130. | |
564 | ||
a7fa9851 MW |
565 | config RTC_DRV_RX8581 |
566 | tristate "Epson RX-8581" | |
567 | help | |
568 | If you say yes here you will get support for the Epson RX-8581. | |
569 | ||
570 | This driver can also be built as a module. If so the module | |
571 | will be called rtc-rx8581. | |
572 | ||
3c2b9075 WG |
573 | config RTC_DRV_RX8025 |
574 | tristate "Epson RX-8025SA/NB" | |
575 | help | |
576 | If you say yes here you get support for the Epson | |
577 | RX-8025SA/NB RTC chips. | |
578 | ||
579 | This driver can also be built as a module. If so, the module | |
580 | will be called rtc-rx8025. | |
581 | ||
ae3551f9 MR |
582 | config RTC_DRV_EM3027 |
583 | tristate "EM Microelectronic EM3027" | |
584 | help | |
585 | If you say yes here you get support for the EM | |
586 | Microelectronic EM3027 RTC chips. | |
587 | ||
588 | This driver can also be built as a module. If so, the module | |
589 | will be called rtc-em3027. | |
590 | ||
52365230 HS |
591 | config RTC_DRV_RV3029C2 |
592 | tristate "Micro Crystal RTC" | |
593 | help | |
594 | If you say yes here you get support for the Micro Crystal | |
595 | RV3029-C2 RTC chips. | |
596 | ||
597 | This driver can also be built as a module. If so, the module | |
598 | will be called rtc-rv3029c2. | |
599 | ||
5bccae6e | 600 | config RTC_DRV_S5M |
0c5deb1e | 601 | tristate "Samsung S2M/S5M series" |
5bccae6e SK |
602 | depends on MFD_SEC_CORE |
603 | help | |
604 | If you say yes here you will get support for the | |
0c5deb1e | 605 | RTC of Samsung S2MPS14 and S5M PMIC series. |
5bccae6e SK |
606 | |
607 | This driver can also be built as a module. If so, the module | |
608 | will be called rtc-s5m. | |
609 | ||
bb35fb20 JE |
610 | endif # I2C |
611 | ||
09a21e56 | 612 | comment "SPI RTC drivers" |
bb35fb20 JE |
613 | |
614 | if SPI_MASTER | |
09a21e56 | 615 | |
74d34d4b VN |
616 | config RTC_DRV_M41T93 |
617 | tristate "ST M41T93" | |
618 | help | |
619 | If you say yes here you will get support for the | |
620 | ST M41T93 SPI RTC chip. | |
621 | ||
622 | This driver can also be built as a module. If so, the module | |
623 | will be called rtc-m41t93. | |
624 | ||
8fc2c767 KH |
625 | config RTC_DRV_M41T94 |
626 | tristate "ST M41T94" | |
627 | help | |
628 | If you say yes here you will get support for the | |
629 | ST M41T94 SPI RTC chip. | |
630 | ||
631 | This driver can also be built as a module. If so, the module | |
632 | will be called rtc-m41t94. | |
633 | ||
53e84b67 DB |
634 | config RTC_DRV_DS1305 |
635 | tristate "Dallas/Maxim DS1305/DS1306" | |
636 | help | |
637 | Select this driver to get support for the Dallas/Maxim DS1305 | |
ae64d169 | 638 | and DS1306 real time clock chips. These support a trickle |
53e84b67 DB |
639 | charger, alarms, and NVRAM in addition to the clock. |
640 | ||
641 | This driver can also be built as a module. If so, the module | |
642 | will be called rtc-ds1305. | |
643 | ||
1d6316f5 | 644 | config RTC_DRV_DS1343 |
0dd449b1 | 645 | select REGMAP_SPI |
1d6316f5 RG |
646 | tristate "Dallas/Maxim DS1343/DS1344" |
647 | help | |
648 | If you say yes here you get support for the | |
649 | Dallas/Maxim DS1343 and DS1344 real time clock chips. | |
650 | Support for trickle charger, alarm is provided. | |
651 | ||
652 | This driver can also be built as a module. If so, the module | |
653 | will be called rtc-ds1343. | |
654 | ||
617b26a0 RG |
655 | config RTC_DRV_DS1347 |
656 | tristate "Dallas/Maxim DS1347" | |
657 | help | |
658 | If you say yes here you get support for the | |
659 | Dallas/Maxim DS1347 chips. | |
660 | ||
661 | This driver only supports the RTC feature, and not other chip | |
662 | features such as alarms. | |
663 | ||
664 | This driver can also be built as a module. If so, the module | |
665 | will be called rtc-ds1347. | |
666 | ||
06de1808 MJ |
667 | config RTC_DRV_DS1390 |
668 | tristate "Dallas/Maxim DS1390/93/94" | |
669 | help | |
7b9b2ef1 AZ |
670 | If you say yes here you get support for the |
671 | Dallas/Maxim DS1390/93/94 chips. | |
06de1808 MJ |
672 | |
673 | This driver only supports the RTC feature, and not other chip | |
674 | features such as alarms and trickle charging. | |
675 | ||
676 | This driver can also be built as a module. If so, the module | |
677 | will be called rtc-ds1390. | |
678 | ||
09b6bdb3 AZ |
679 | config RTC_DRV_MAX6902 |
680 | tristate "Maxim MAX6902" | |
681 | help | |
682 | If you say yes here you will get support for the | |
683 | Maxim MAX6902 SPI RTC chip. | |
684 | ||
685 | This driver can also be built as a module. If so, the module | |
686 | will be called rtc-max6902. | |
687 | ||
2805b969 MD |
688 | config RTC_DRV_R9701 |
689 | tristate "Epson RTC-9701JE" | |
690 | help | |
691 | If you say yes here you will get support for the | |
692 | Epson RTC-9701JE SPI RTC chip. | |
693 | ||
694 | This driver can also be built as a module. If so, the module | |
695 | will be called rtc-r9701. | |
696 | ||
e0ac4761 AN |
697 | config RTC_DRV_RS5C348 |
698 | tristate "Ricoh RS5C348A/B" | |
e0ac4761 AN |
699 | help |
700 | If you say yes here you get support for the | |
701 | Ricoh RS5C348A and RS5C348B RTC chips. | |
702 | ||
703 | This driver can also be built as a module. If so, the module | |
704 | will be called rtc-rs5c348. | |
705 | ||
2f9b75e0 DA |
706 | config RTC_DRV_DS3234 |
707 | tristate "Maxim/Dallas DS3234" | |
708 | help | |
709 | If you say yes here you get support for the | |
710 | Maxim/Dallas DS3234 SPI RTC chip. | |
711 | ||
712 | This driver can also be built as a module. If so, the module | |
713 | will be called rtc-ds3234. | |
714 | ||
7f3923a1 CV |
715 | config RTC_DRV_PCF2123 |
716 | tristate "NXP PCF2123" | |
717 | help | |
718 | If you say yes here you get support for the NXP PCF2123 | |
719 | RTC chip. | |
720 | ||
721 | This driver can also be built as a module. If so, the module | |
722 | will be called rtc-pcf2123. | |
723 | ||
cce2da9a TH |
724 | config RTC_DRV_RX4581 |
725 | tristate "Epson RX-4581" | |
726 | help | |
727 | If you say yes here you will get support for the Epson RX-4581. | |
728 | ||
729 | This driver can also be built as a module. If so the module | |
730 | will be called rtc-rx4581. | |
731 | ||
1fcbe42c JG |
732 | config RTC_DRV_MCP795 |
733 | tristate "Microchip MCP795" | |
734 | help | |
735 | If you say yes here you will get support for the Microchip MCP795. | |
736 | ||
737 | This driver can also be built as a module. If so the module | |
738 | will be called rtc-mcp795. | |
739 | ||
bb35fb20 JE |
740 | endif # SPI_MASTER |
741 | ||
09a21e56 | 742 | comment "Platform RTC drivers" |
09a21e56 AZ |
743 | |
744 | # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> | |
745 | # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a | |
746 | # global rtc_lock ... it's not yet just another platform_device. | |
747 | ||
748 | config RTC_DRV_CMOS | |
749 | tristate "PC-style 'CMOS'" | |
41c9dbf4 | 750 | depends on X86 || ARM || M32R || PPC || MIPS || SPARC64 |
c7500900 | 751 | default y if X86 |
09a21e56 AZ |
752 | help |
753 | Say "yes" here to get direct support for the real time clock | |
754 | found in every PC or ACPI-based system, and some other boards. | |
755 | Specifically the original MC146818, compatibles like those in | |
756 | PC south bridges, the DS12887 or M48T86, some multifunction | |
757 | or LPC bus chips, and so on. | |
758 | ||
759 | Your system will need to define the platform device used by | |
ae64d169 | 760 | this driver, otherwise it won't be accessible. This means |
09a21e56 AZ |
761 | you can safely enable this driver if you don't know whether |
762 | or not your board has this kind of hardware. | |
763 | ||
764 | This driver can also be built as a module. If so, the module | |
765 | will be called rtc-cmos. | |
766 | ||
85d0b3a5 RH |
767 | config RTC_DRV_ALPHA |
768 | bool "Alpha PC-style CMOS" | |
769 | depends on ALPHA | |
770 | default y | |
771 | help | |
772 | Direct support for the real-time clock found on every Alpha | |
773 | system, specifically MC146818 compatibles. If in doubt, say Y. | |
774 | ||
0146f261 | 775 | config RTC_DRV_VRTC |
933b9463 AC |
776 | tristate "Virtual RTC for Intel MID platforms" |
777 | depends on X86_INTEL_MID | |
778 | default y if X86_INTEL_MID | |
0146f261 FT |
779 | |
780 | help | |
781 | Say "yes" here to get direct support for the real time clock | |
782 | found on Moorestown platforms. The VRTC is a emulated RTC that | |
783 | derives its clock source from a real RTC in the PMIC. The MC146818 | |
784 | style programming interface is mostly conserved, but any | |
785 | updates are done via IPC calls to the system controller FW. | |
786 | ||
537739de TB |
787 | config RTC_DRV_DS1216 |
788 | tristate "Dallas DS1216" | |
bb35fb20 | 789 | depends on SNI_RM |
537739de TB |
790 | help |
791 | If you say yes here you get support for the Dallas DS1216 RTC chips. | |
792 | ||
5f119f29 TB |
793 | config RTC_DRV_DS1286 |
794 | tristate "Dallas DS1286" | |
706b632d | 795 | depends on HAS_IOMEM |
5f119f29 TB |
796 | help |
797 | If you say yes here you get support for the Dallas DS1286 RTC chips. | |
798 | ||
739d340d PM |
799 | config RTC_DRV_DS1302 |
800 | tristate "Dallas DS1302" | |
801 | depends on SH_SECUREEDGE5410 | |
802 | help | |
803 | If you say yes here you get support for the Dallas DS1302 RTC chips. | |
804 | ||
8f26795a AS |
805 | config RTC_DRV_DS1511 |
806 | tristate "Dallas DS1511" | |
706b632d | 807 | depends on HAS_IOMEM |
8f26795a AS |
808 | help |
809 | If you say yes here you get support for the | |
810 | Dallas DS1511 timekeeping/watchdog chip. | |
811 | ||
812 | This driver can also be built as a module. If so, the module | |
813 | will be called rtc-ds1511. | |
814 | ||
09a21e56 | 815 | config RTC_DRV_DS1553 |
09b6bdb3 | 816 | tristate "Maxim/Dallas DS1553" |
706b632d | 817 | depends on HAS_IOMEM |
7520b94d AZ |
818 | help |
819 | If you say yes here you get support for the | |
09b6bdb3 | 820 | Maxim/Dallas DS1553 timekeeping chip. |
7520b94d AZ |
821 | |
822 | This driver can also be built as a module. If so, the module | |
09a21e56 AZ |
823 | will be called rtc-ds1553. |
824 | ||
aaaf5fbf JK |
825 | config RTC_DRV_DS1685_FAMILY |
826 | tristate "Dallas/Maxim DS1685 Family" | |
827 | help | |
828 | If you say yes here you get support for the Dallas/Maxim DS1685 | |
829 | family of real time chips. This family includes the DS1685/DS1687, | |
830 | DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and | |
831 | DS17885/DS17887 chips. | |
832 | ||
833 | This driver can also be built as a module. If so, the module | |
834 | will be called rtc-ds1685. | |
835 | ||
836 | choice | |
837 | prompt "Subtype" | |
838 | depends on RTC_DRV_DS1685_FAMILY | |
839 | default RTC_DRV_DS1685 | |
840 | ||
841 | config RTC_DRV_DS1685 | |
842 | bool "DS1685/DS1687" | |
843 | help | |
844 | This enables support for the Dallas/Maxim DS1685/DS1687 real time | |
845 | clock chip. | |
846 | ||
847 | This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30) | |
848 | systems, as well as EPPC-405-UC modules by electronic system design | |
849 | GmbH. | |
850 | ||
851 | config RTC_DRV_DS1689 | |
852 | bool "DS1689/DS1693" | |
853 | help | |
854 | This enables support for the Dallas/Maxim DS1689/DS1693 real time | |
855 | clock chip. | |
856 | ||
857 | This is an older RTC chip, supplanted by the DS1685/DS1687 above, | |
858 | which supports a few minor features such as Vcc, Vbat, and Power | |
859 | Cycle counters, plus a customer-specific, 8-byte ROM/Serial number. | |
860 | ||
861 | It also works for the even older DS1688/DS1691 RTC chips, which are | |
862 | virtually the same and carry the same model number. Both chips | |
863 | have 114 bytes of user NVRAM. | |
864 | ||
865 | config RTC_DRV_DS17285 | |
866 | bool "DS17285/DS17287" | |
867 | help | |
868 | This enables support for the Dallas/Maxim DS17285/DS17287 real time | |
869 | clock chip. | |
870 | ||
871 | This chip features 2kb of extended NV-SRAM. It may possibly be | |
872 | found in some SGI O2 systems (rare). | |
873 | ||
874 | config RTC_DRV_DS17485 | |
875 | bool "DS17485/DS17487" | |
876 | help | |
877 | This enables support for the Dallas/Maxim DS17485/DS17487 real time | |
878 | clock chip. | |
879 | ||
880 | This chip features 4kb of extended NV-SRAM. | |
881 | ||
882 | config RTC_DRV_DS17885 | |
883 | bool "DS17885/DS17887" | |
884 | help | |
885 | This enables support for the Dallas/Maxim DS17885/DS17887 real time | |
886 | clock chip. | |
887 | ||
888 | This chip features 8kb of extended NV-SRAM. | |
889 | ||
890 | endchoice | |
891 | ||
892 | config RTC_DS1685_PROC_REGS | |
893 | bool "Display register values in /proc" | |
894 | depends on RTC_DRV_DS1685_FAMILY && PROC_FS | |
895 | help | |
896 | Enable this to display a readout of all of the RTC registers in | |
897 | /proc/drivers/rtc. Keep in mind that this can potentially lead | |
898 | to lost interrupts, as reading Control Register C will clear | |
899 | all pending IRQ flags. | |
900 | ||
901 | Unless you are debugging this driver, choose N. | |
902 | ||
903 | config RTC_DS1685_SYSFS_REGS | |
904 | bool "SysFS access to RTC register bits" | |
905 | depends on RTC_DRV_DS1685_FAMILY && SYSFS | |
906 | help | |
907 | Enable this to provide access to the RTC control register bits | |
908 | in /sys. Some of the bits are read-write, others are read-only. | |
909 | ||
910 | Keep in mind that reading Control C's bits automatically clears | |
911 | all pending IRQ flags - this can cause lost interrupts. | |
912 | ||
913 | If you know that you need access to these bits, choose Y, Else N. | |
914 | ||
09b6bdb3 AZ |
915 | config RTC_DRV_DS1742 |
916 | tristate "Maxim/Dallas DS1742/1743" | |
706b632d | 917 | depends on HAS_IOMEM |
02964115 TH |
918 | help |
919 | If you say yes here you get support for the | |
09b6bdb3 | 920 | Maxim/Dallas DS1742/1743 timekeeping chip. |
02964115 TH |
921 | |
922 | This driver can also be built as a module. If so, the module | |
09b6bdb3 | 923 | will be called rtc-ds1742. |
02964115 | 924 | |
ad0200f7 JD |
925 | config RTC_DRV_DS2404 |
926 | tristate "Maxim/Dallas DS2404" | |
927 | help | |
928 | If you say yes here you get support for the | |
929 | Dallas DS2404 RTC chip. | |
930 | ||
931 | This driver can also be built as a module. If so, the module | |
932 | will be called rtc-ds2404. | |
933 | ||
fef931ff AJ |
934 | config RTC_DRV_DA9052 |
935 | tristate "Dialog DA9052/DA9053 RTC" | |
936 | depends on PMIC_DA9052 | |
937 | help | |
938 | Say y here to support the RTC driver for Dialog Semiconductor | |
939 | DA9052-BC and DA9053-AA/Bx PMICs. | |
940 | ||
6920d996 AJ |
941 | config RTC_DRV_DA9055 |
942 | tristate "Dialog Semiconductor DA9055 RTC" | |
943 | depends on MFD_DA9055 | |
944 | help | |
945 | If you say yes here you will get support for the | |
946 | RTC of the Dialog DA9055 PMIC. | |
947 | ||
948 | This driver can also be built as a module. If so, the module | |
949 | will be called rtc-da9055 | |
950 | ||
c2a57550 OST |
951 | config RTC_DRV_DA9063 |
952 | tristate "Dialog Semiconductor DA9063 RTC" | |
953 | depends on MFD_DA9063 | |
954 | help | |
955 | If you say yes here you will get support for the RTC subsystem | |
956 | of the Dialog Semiconductor DA9063. | |
957 | ||
958 | This driver can also be built as a module. If so, the module | |
959 | will be called "rtc-da9063". | |
960 | ||
5e3fd9e5 | 961 | config RTC_DRV_EFI |
962 | tristate "EFI RTC" | |
7efe6659 | 963 | depends on EFI && !X86 |
5e3fd9e5 | 964 | help |
965 | If you say yes here you will get support for the EFI | |
966 | Real Time Clock. | |
967 | ||
968 | This driver can also be built as a module. If so, the module | |
969 | will be called rtc-efi. | |
970 | ||
09b6bdb3 AZ |
971 | config RTC_DRV_STK17TA8 |
972 | tristate "Simtek STK17TA8" | |
706b632d | 973 | depends on HAS_IOMEM |
09a21e56 AZ |
974 | help |
975 | If you say yes here you get support for the | |
09b6bdb3 | 976 | Simtek STK17TA8 timekeeping chip. |
09a21e56 AZ |
977 | |
978 | This driver can also be built as a module. If so, the module | |
09b6bdb3 | 979 | will be called rtc-stk17ta8. |
09a21e56 AZ |
980 | |
981 | config RTC_DRV_M48T86 | |
982 | tristate "ST M48T86/Dallas DS12887" | |
09a21e56 AZ |
983 | help |
984 | If you say Y here you will get support for the | |
985 | ST M48T86 and Dallas DS12887 RTC chips. | |
986 | ||
987 | This driver can also be built as a module. If so, the module | |
988 | will be called rtc-m48t86. | |
989 | ||
d1dbd82e TB |
990 | config RTC_DRV_M48T35 |
991 | tristate "ST M48T35" | |
706b632d | 992 | depends on HAS_IOMEM |
d1dbd82e TB |
993 | help |
994 | If you say Y here you will get support for the | |
995 | ST M48T35 RTC chip. | |
996 | ||
997 | This driver can also be built as a module, if so, the module | |
998 | will be called "rtc-m48t35". | |
999 | ||
2e774c7c | 1000 | config RTC_DRV_M48T59 |
94fe7424 | 1001 | tristate "ST M48T59/M48T08/M48T02" |
706b632d | 1002 | depends on HAS_IOMEM |
2e774c7c MZ |
1003 | help |
1004 | If you say Y here you will get support for the | |
94fe7424 KH |
1005 | ST M48T59 RTC chip and compatible ST M48T08 and M48T02. |
1006 | ||
1007 | These chips are usually found in Sun SPARC and UltraSPARC | |
1008 | workstations. | |
2e774c7c MZ |
1009 | |
1010 | This driver can also be built as a module, if so, the module | |
1011 | will be called "rtc-m48t59". | |
1012 | ||
4f9b9bba GU |
1013 | config RTC_DRV_MSM6242 |
1014 | tristate "Oki MSM6242" | |
706b632d | 1015 | depends on HAS_IOMEM |
4f9b9bba GU |
1016 | help |
1017 | If you say yes here you get support for the Oki MSM6242 | |
1018 | timekeeping chip. It is used in some Amiga models (e.g. A2000). | |
1019 | ||
1020 | This driver can also be built as a module. If so, the module | |
1021 | will be called rtc-msm6242. | |
1022 | ||
cca4c231 DM |
1023 | config RTC_DRV_BQ4802 |
1024 | tristate "TI BQ4802" | |
706b632d | 1025 | depends on HAS_IOMEM |
cca4c231 DM |
1026 | help |
1027 | If you say Y here you will get support for the TI | |
1028 | BQ4802 RTC chip. | |
1029 | ||
1030 | This driver can also be built as a module. If so, the module | |
1031 | will be called rtc-bq4802. | |
1032 | ||
4f672ce2 GU |
1033 | config RTC_DRV_RP5C01 |
1034 | tristate "Ricoh RP5C01" | |
706b632d | 1035 | depends on HAS_IOMEM |
4f672ce2 GU |
1036 | help |
1037 | If you say yes here you get support for the Ricoh RP5C01 | |
1038 | timekeeping chip. It is used in some Amiga models (e.g. A3000 | |
1039 | and A4000). | |
1040 | ||
1041 | This driver can also be built as a module. If so, the module | |
1042 | will be called rtc-rp5c01. | |
1043 | ||
09a21e56 AZ |
1044 | config RTC_DRV_V3020 |
1045 | tristate "EM Microelectronic V3020" | |
09a21e56 AZ |
1046 | help |
1047 | If you say yes here you will get support for the | |
1048 | EM Microelectronic v3020 RTC chip. | |
1049 | ||
1050 | This driver can also be built as a module. If so, the module | |
1051 | will be called rtc-v3020. | |
1052 | ||
35c86bf6 MB |
1053 | config RTC_DRV_WM831X |
1054 | tristate "Wolfson Microelectronics WM831x RTC" | |
1055 | depends on MFD_WM831X | |
1056 | help | |
1057 | If you say yes here you will get support for the RTC subsystem | |
1058 | of the Wolfson Microelectronics WM831X series PMICs. | |
1059 | ||
1060 | This driver can also be built as a module. If so, the module | |
1061 | will be called "rtc-wm831x". | |
1062 | ||
077eaf5b MB |
1063 | config RTC_DRV_WM8350 |
1064 | tristate "Wolfson Microelectronics WM8350 RTC" | |
1065 | depends on MFD_WM8350 | |
1066 | help | |
1067 | If you say yes here you will get support for the RTC subsystem | |
1068 | of the Wolfson Microelectronics WM8350. | |
1069 | ||
1070 | This driver can also be built as a module. If so, the module | |
1071 | will be called "rtc-wm8350". | |
1072 | ||
0942a71e RK |
1073 | config RTC_DRV_SPEAR |
1074 | tristate "SPEAR ST RTC" | |
1075 | depends on PLAT_SPEAR | |
1076 | default y | |
1077 | help | |
1078 | If you say Y here you will get support for the RTC found on | |
1079 | spear | |
1080 | ||
eae854b2 BR |
1081 | config RTC_DRV_PCF50633 |
1082 | depends on MFD_PCF50633 | |
1083 | tristate "NXP PCF50633 RTC" | |
1084 | help | |
1085 | If you say yes here you get support for the RTC subsystem of the | |
1086 | NXP PCF50633 used in embedded systems. | |
1087 | ||
bd207cfb LW |
1088 | config RTC_DRV_AB3100 |
1089 | tristate "ST-Ericsson AB3100 RTC" | |
1090 | depends on AB3100_CORE | |
1091 | default y if AB3100_CORE | |
1092 | help | |
1093 | Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC | |
1094 | support. This chip contains a battery- and capacitor-backed RTC. | |
1095 | ||
0af62f4d VS |
1096 | config RTC_DRV_AB8500 |
1097 | tristate "ST-Ericsson AB8500 RTC" | |
1098 | depends on AB8500_CORE | |
651fb480 | 1099 | select RTC_INTF_DEV |
dc43d4a2 | 1100 | select RTC_INTF_DEV_UIE_EMUL |
0af62f4d VS |
1101 | help |
1102 | Select this to enable the ST-Ericsson AB8500 power management IC RTC | |
1103 | support. This chip contains a battery- and capacitor-backed RTC. | |
1104 | ||
afd49a7e WZ |
1105 | config RTC_DRV_NUC900 |
1106 | tristate "NUC910/NUC920 RTC driver" | |
6b8029fa | 1107 | depends on ARCH_W90X900 |
afd49a7e WZ |
1108 | help |
1109 | If you say yes here you get support for the RTC subsystem of the | |
1110 | NUC910/NUC920 used in embedded systems. | |
bd207cfb | 1111 | |
16b1d26e NG |
1112 | config RTC_DRV_OPAL |
1113 | tristate "IBM OPAL RTC driver" | |
1114 | depends on PPC_POWERNV | |
1115 | default y | |
1116 | help | |
1117 | If you say yes here you get support for the PowerNV platform RTC | |
1118 | driver based on OPAL interfaces. | |
1119 | ||
1120 | This driver can also be built as a module. If so, the module | |
1121 | will be called rtc-opal. | |
1122 | ||
09a21e56 | 1123 | comment "on-CPU RTC drivers" |
09a21e56 | 1124 | |
8ecf6c54 MA |
1125 | config RTC_DRV_DAVINCI |
1126 | tristate "TI DaVinci RTC" | |
1127 | depends on ARCH_DAVINCI_DM365 | |
1128 | help | |
1129 | If you say yes here you get support for the RTC on the | |
1130 | DaVinci platforms (DM365). | |
1131 | ||
1132 | This driver can also be built as a module. If so, the module | |
1133 | will be called rtc-davinci. | |
1134 | ||
ba172208 BS |
1135 | config RTC_DRV_DIGICOLOR |
1136 | tristate "Conexant Digicolor RTC" | |
1137 | depends on ARCH_DIGICOLOR | |
1138 | help | |
1139 | If you say yes here you get support for the RTC on Conexant | |
1140 | Digicolor platforms. This currently includes the CX92755 SoC. | |
1141 | ||
1142 | This driver can also be built as a module. If so, the module | |
1143 | will be called rtc-digicolor. | |
1144 | ||
b224b9ac FE |
1145 | config RTC_DRV_IMXDI |
1146 | tristate "Freescale IMX DryIce Real Time Clock" | |
ef216ad0 | 1147 | depends on ARCH_MXC |
b224b9ac FE |
1148 | help |
1149 | Support for Freescale IMX DryIce RTC | |
1150 | ||
1151 | This driver can also be built as a module, if so, the module | |
1152 | will be called "rtc-imxdi". | |
1153 | ||
09a21e56 | 1154 | config RTC_DRV_OMAP |
8608976e LV |
1155 | tristate "TI OMAP Real Time Clock" |
1156 | depends on ARCH_OMAP || ARCH_DAVINCI | |
09a21e56 | 1157 | help |
427af9a6 | 1158 | Say "yes" here to support the on chip real time clock |
8608976e | 1159 | present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx. |
427af9a6 AM |
1160 | |
1161 | This driver can also be built as a module, if so, module | |
1162 | will be called rtc-omap. | |
7520b94d | 1163 | |
16f4efe7 AD |
1164 | config HAVE_S3C_RTC |
1165 | bool | |
1166 | help | |
1167 | This will include RTC support for Samsung SoCs. If | |
1168 | you want to include RTC support for any machine, kindly | |
1169 | select this in the respective mach-XXXX/Kconfig file. | |
1170 | ||
1add6781 BD |
1171 | config RTC_DRV_S3C |
1172 | tristate "Samsung S3C series SoC RTC" | |
b130d5c2 | 1173 | depends on ARCH_S3C64XX || HAVE_S3C_RTC |
1add6781 BD |
1174 | help |
1175 | RTC (Realtime Clock) driver for the clock inbuilt into the | |
1176 | Samsung S3C24XX series of SoCs. This can provide periodic | |
1177 | interrupt rates from 1Hz to 64Hz for user programs, and | |
1178 | wakeup from Alarm. | |
1179 | ||
1180 | The driver currently supports the common features on all the | |
1181 | S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 | |
1182 | and S3C2442. | |
1183 | ||
1184 | This driver can also be build as a module. If so, the module | |
1185 | will be called rtc-s3c. | |
1186 | ||
fd507e2f AZ |
1187 | config RTC_DRV_EP93XX |
1188 | tristate "Cirrus Logic EP93XX" | |
bb35fb20 | 1189 | depends on ARCH_EP93XX |
fd507e2f AZ |
1190 | help |
1191 | If you say yes here you get support for the | |
1192 | RTC embedded in the Cirrus Logic EP93XX processors. | |
1193 | ||
1194 | This driver can also be built as a module. If so, the module | |
1195 | will be called rtc-ep93xx. | |
1196 | ||
e842f1c8 | 1197 | config RTC_DRV_SA1100 |
3888c090 HZ |
1198 | tristate "SA11x0/PXA2xx/PXA910" |
1199 | depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP | |
e842f1c8 RP |
1200 | help |
1201 | If you say Y here you will get access to the real time clock | |
1202 | built into your SA11x0 or PXA2xx CPU. | |
1203 | ||
1204 | To compile this driver as a module, choose M here: the | |
1205 | module will be called rtc-sa1100. | |
fd507e2f | 1206 | |
317a6104 PM |
1207 | config RTC_DRV_SH |
1208 | tristate "SuperH On-Chip RTC" | |
6b8029fa | 1209 | depends on SUPERH && HAVE_CLK |
317a6104 PM |
1210 | help |
1211 | Say Y here to enable support for the on-chip RTC found in | |
1212 | most SuperH processors. | |
1213 | ||
1214 | To compile this driver as a module, choose M here: the | |
1215 | module will be called rtc-sh. | |
1216 | ||
8417eb7a | 1217 | config RTC_DRV_VR41XX |
3e16f6af | 1218 | tristate "NEC VR41XX" |
bb35fb20 | 1219 | depends on CPU_VR41XX |
3e16f6af AZ |
1220 | help |
1221 | If you say Y here you will get access to the real time clock | |
1222 | built into your NEC VR41XX CPU. | |
1223 | ||
1224 | To compile this driver as a module, choose M here: the | |
1225 | module will be called rtc-vr41xx. | |
8417eb7a | 1226 | |
a190901c RK |
1227 | config RTC_DRV_PL030 |
1228 | tristate "ARM AMBA PL030 RTC" | |
1229 | depends on ARM_AMBA | |
1230 | help | |
1231 | If you say Y here you will get access to ARM AMBA | |
1232 | PrimeCell PL030 RTC found on certain ARM SOCs. | |
1233 | ||
1234 | To compile this driver as a module, choose M here: the | |
1235 | module will be called rtc-pl030. | |
1236 | ||
8ae6e163 DS |
1237 | config RTC_DRV_PL031 |
1238 | tristate "ARM AMBA PL031 RTC" | |
bb35fb20 | 1239 | depends on ARM_AMBA |
8ae6e163 DS |
1240 | help |
1241 | If you say Y here you will get access to ARM AMBA | |
09a21e56 | 1242 | PrimeCell PL031 RTC found on certain ARM SOCs. |
8ae6e163 DS |
1243 | |
1244 | To compile this driver as a module, choose M here: the | |
1245 | module will be called rtc-pl031. | |
1246 | ||
fa04e78b HCE |
1247 | config RTC_DRV_AT32AP700X |
1248 | tristate "AT32AP700X series RTC" | |
bb35fb20 | 1249 | depends on PLATFORM_AT32AP |
fa04e78b HCE |
1250 | help |
1251 | Driver for the internal RTC (Realtime Clock) on Atmel AVR32 | |
1252 | AT32AP700x family processors. | |
1253 | ||
7fc39f6d | 1254 | config RTC_DRV_AT91RM9200 |
24cecc1b | 1255 | tristate "AT91RM9200 or some AT91SAM9 RTC" |
938f970e | 1256 | depends on ARCH_AT91 |
4cdf854f DB |
1257 | help |
1258 | Driver for the internal RTC (Realtime Clock) module found on | |
24cecc1b | 1259 | Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips |
4cdf854f DB |
1260 | this is powered by the backup power supply. |
1261 | ||
1262 | config RTC_DRV_AT91SAM9 | |
3969eb48 | 1263 | tristate "AT91SAM9 RTT as RTC" |
ee72f18b | 1264 | depends on ARCH_AT91 |
43e112bb | 1265 | select MFD_SYSCON |
4cdf854f | 1266 | help |
3969eb48 BB |
1267 | Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which |
1268 | can be used as an RTC thanks to the backup power supply (e.g. a | |
1269 | small coin cell battery) which keeps this block and the GPBR | |
1270 | (General Purpose Backup Registers) block powered when the device | |
1271 | is shutdown. | |
1272 | Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd | |
1273 | probably want to use the real RTC block instead of the "RTT as an | |
1274 | RTC" driver. | |
4cdf854f | 1275 | |
45fd8a0c ML |
1276 | config RTC_DRV_AU1XXX |
1277 | tristate "Au1xxx Counter0 RTC support" | |
42a4f17d | 1278 | depends on MIPS_ALCHEMY |
45fd8a0c ML |
1279 | help |
1280 | This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year | |
1281 | counter) to be used as a RTC. | |
1282 | ||
1283 | This driver can also be built as a module. If so, the module | |
1284 | will be called rtc-au1xxx. | |
1285 | ||
8cc75c9a WB |
1286 | config RTC_DRV_BFIN |
1287 | tristate "Blackfin On-Chip RTC" | |
7f604599 | 1288 | depends on BLACKFIN && !BF561 |
8cc75c9a WB |
1289 | help |
1290 | If you say yes here you will get support for the | |
1291 | Blackfin On-Chip Real Time Clock. | |
1292 | ||
1293 | This driver can also be built as a module. If so, the module | |
1294 | will be called rtc-bfin. | |
1295 | ||
e9f2bd81 NI |
1296 | config RTC_DRV_RS5C313 |
1297 | tristate "Ricoh RS5C313" | |
bb35fb20 | 1298 | depends on SH_LANDISK |
e9f2bd81 NI |
1299 | help |
1300 | If you say yes here you get support for the Ricoh RS5C313 RTC chips. | |
1301 | ||
3afe6d04 GU |
1302 | config RTC_DRV_GENERIC |
1303 | tristate "Generic RTC support" | |
1304 | # Please consider writing a new RTC driver instead of using the generic | |
1305 | # RTC abstraction | |
47c8a08b | 1306 | depends on PARISC || M68K || PPC || SUPERH32 |
9eb16864 | 1307 | help |
3afe6d04 GU |
1308 | Say Y or M here to enable RTC support on systems using the generic |
1309 | RTC abstraction. If you do not know what you are doing, you should | |
9eb16864 KM |
1310 | just say Y. |
1311 | ||
dc944368 RJ |
1312 | config RTC_DRV_PXA |
1313 | tristate "PXA27x/PXA3xx" | |
1314 | depends on ARCH_PXA | |
1315 | help | |
1316 | If you say Y here you will get access to the real time clock | |
1317 | built into your PXA27x or PXA3xx CPU. | |
1318 | ||
1319 | This RTC driver uses PXA RTC registers available since pxa27x | |
1320 | series (RDxR, RYxR) instead of legacy RCNR, RTAR. | |
1321 | ||
f77fbdf9 AC |
1322 | config RTC_DRV_VT8500 |
1323 | tristate "VIA/WonderMedia 85xx SoC RTC" | |
1324 | depends on ARCH_VT8500 | |
1325 | help | |
1326 | If you say Y here you will get access to the real time clock | |
1327 | built into your VIA VT8500 SoC or its relatives. | |
1328 | ||
dc944368 | 1329 | |
7a138ede DM |
1330 | config RTC_DRV_SUN4V |
1331 | bool "SUN4V Hypervisor RTC" | |
1332 | depends on SPARC64 | |
1333 | help | |
1334 | If you say Y here you will get support for the Hypervisor | |
1335 | based RTC on SUN4V systems. | |
1336 | ||
9765d2d9 CYT |
1337 | config RTC_DRV_SUN6I |
1338 | tristate "Allwinner A31 RTC" | |
1339 | depends on MACH_SUN6I || MACH_SUN8I | |
1340 | help | |
1341 | If you say Y here you will get support for the RTC found on | |
1342 | Allwinner A31. | |
1343 | ||
594c6fb9 CC |
1344 | config RTC_DRV_SUNXI |
1345 | tristate "Allwinner sun4i/sun7i RTC" | |
64a1925c | 1346 | depends on MACH_SUN4I || MACH_SUN7I |
594c6fb9 CC |
1347 | help |
1348 | If you say Y here you will get support for the RTC found on | |
1349 | Allwinner A10/A20. | |
1350 | ||
de2cf332 DM |
1351 | config RTC_DRV_STARFIRE |
1352 | bool "Starfire RTC" | |
1353 | depends on SPARC64 | |
1354 | help | |
1355 | If you say Y here you will get support for the RTC found on | |
1356 | Starfire systems. | |
1357 | ||
0e149233 AN |
1358 | config RTC_DRV_TX4939 |
1359 | tristate "TX4939 SoC" | |
1360 | depends on SOC_TX4939 | |
1361 | help | |
1362 | Driver for the internal RTC (Realtime Clock) module found on | |
1363 | Toshiba TX4939 SoC. | |
1364 | ||
defb4514 SB |
1365 | config RTC_DRV_MV |
1366 | tristate "Marvell SoC RTC" | |
ace2c020 | 1367 | depends on ARCH_DOVE || ARCH_MVEBU |
defb4514 SB |
1368 | help |
1369 | If you say yes here you will get support for the in-chip RTC | |
1370 | that can be found in some of Marvell's SoC devices, such as | |
1371 | the Kirkwood 88F6281 and 88F6192. | |
1372 | ||
1373 | This driver can also be built as a module. If so, the module | |
1374 | will be called rtc-mv. | |
1375 | ||
a3a42806 GC |
1376 | config RTC_DRV_ARMADA38X |
1377 | tristate "Armada 38x Marvell SoC RTC" | |
1378 | depends on ARCH_MVEBU | |
1379 | help | |
1380 | If you say yes here you will get support for the in-chip RTC | |
1381 | that can be found in the Armada 38x Marvell's SoC device | |
1382 | ||
1383 | This driver can also be built as a module. If so, the module | |
1384 | will be called armada38x-rtc. | |
1385 | ||
98a9bb5b HUK |
1386 | config RTC_DRV_GEMINI |
1387 | tristate "Gemini SoC RTC" | |
1388 | depends on ARCH_GEMINI || COMPILE_TEST | |
1389 | depends on HAS_IOMEM | |
1390 | help | |
1391 | If you say Y here you will get support for the | |
1392 | RTC found on Gemini SoC's. | |
1393 | ||
1394 | This driver can also be built as a module. If so, the module | |
1395 | will be called rtc-gemini. | |
1396 | ||
0b5f037a GU |
1397 | config RTC_DRV_PS3 |
1398 | tristate "PS3 RTC" | |
1399 | depends on PPC_PS3 | |
1400 | help | |
1401 | If you say yes here you will get support for the RTC on PS3. | |
1402 | ||
1403 | This driver can also be built as a module. If so, the module | |
1404 | will be called rtc-ps3. | |
1405 | ||
aa958f57 LW |
1406 | config RTC_DRV_COH901331 |
1407 | tristate "ST-Ericsson COH 901 331 RTC" | |
1408 | depends on ARCH_U300 | |
1409 | help | |
1410 | If you say Y here you will get access to ST-Ericsson | |
1411 | COH 901 331 RTC clock found in some ST-Ericsson Mobile | |
1412 | Platforms. | |
1413 | ||
1414 | This driver can also be built as a module. If so, the module | |
1415 | will be called "rtc-coh901331". | |
1416 | ||
1417 | ||
df17f631 | 1418 | config RTC_DRV_STMP |
46b21218 WS |
1419 | tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC" |
1420 | depends on ARCH_MXS | |
20d048ac | 1421 | select STMP_DEVICE |
df17f631 | 1422 | help |
1423 | If you say yes here you will get support for the onboard | |
46b21218 | 1424 | STMP3xxx/i.MX23/i.MX28 RTC. |
df17f631 | 1425 | |
1426 | This driver can also be built as a module. If so, the module | |
1427 | will be called rtc-stmp3xxx. | |
1428 | ||
d3c7a3f7 DR |
1429 | config RTC_DRV_PCAP |
1430 | tristate "PCAP RTC" | |
1431 | depends on EZX_PCAP | |
1432 | help | |
1433 | If you say Y here you will get support for the RTC found on | |
1434 | the PCAP2 ASIC used on some Motorola phones. | |
1435 | ||
1c97872b UKK |
1436 | config RTC_DRV_MC13XXX |
1437 | depends on MFD_MC13XXX | |
1438 | tristate "Freescale MC13xxx RTC" | |
43299f28 | 1439 | help |
1c97872b UKK |
1440 | This enables support for the RTCs found on Freescale's PMICs |
1441 | MC13783 and MC13892. | |
43299f28 | 1442 | |
50aae724 AG |
1443 | config RTC_DRV_MPC5121 |
1444 | tristate "Freescale MPC5121 built-in RTC" | |
955dbea3 | 1445 | depends on PPC_MPC512x || PPC_MPC52xx |
50aae724 AG |
1446 | help |
1447 | If you say yes here you will get support for the | |
955dbea3 | 1448 | built-in RTC on MPC5121 or on MPC5200. |
50aae724 AG |
1449 | |
1450 | This driver can also be built as a module. If so, the module | |
1451 | will be called rtc-mpc5121. | |
1452 | ||
3bf0eea8 LPC |
1453 | config RTC_DRV_JZ4740 |
1454 | tristate "Ingenic JZ4740 SoC" | |
3bf0eea8 LPC |
1455 | depends on MACH_JZ4740 |
1456 | help | |
1457 | If you say yes here you get support for the Ingenic JZ4740 SoC RTC | |
1458 | controller. | |
1459 | ||
1460 | This driver can also be buillt as a module. If so, the module | |
1461 | will be called rtc-jz4740. | |
1462 | ||
9aa449be KW |
1463 | config RTC_DRV_LPC32XX |
1464 | depends on ARCH_LPC32XX | |
1465 | tristate "NXP LPC32XX RTC" | |
1466 | help | |
1467 | This enables support for the NXP RTC in the LPC32XX | |
1468 | ||
1469 | This driver can also be buillt as a module. If so, the module | |
1470 | will be called rtc-lpc32xx. | |
1471 | ||
9a9a54ad AG |
1472 | config RTC_DRV_PM8XXX |
1473 | tristate "Qualcomm PMIC8XXX RTC" | |
c8d523a4 | 1474 | depends on MFD_PM8XXX || MFD_SPMI_PMIC |
9a9a54ad AG |
1475 | help |
1476 | If you say yes here you get support for the | |
1477 | Qualcomm PMIC8XXX RTC. | |
1478 | ||
1479 | To compile this driver as a module, choose M here: the | |
1480 | module will be called rtc-pm8xxx. | |
1481 | ||
ff859ba6 AC |
1482 | config RTC_DRV_TEGRA |
1483 | tristate "NVIDIA Tegra Internal RTC driver" | |
6b8029fa | 1484 | depends on ARCH_TEGRA |
ff859ba6 AC |
1485 | help |
1486 | If you say yes here you get support for the | |
1487 | Tegra 200 series internal RTC module. | |
1488 | ||
1489 | This drive can also be built as a module. If so, the module | |
1490 | will be called rtc-tegra. | |
1491 | ||
dd196a2b CM |
1492 | config RTC_DRV_TILE |
1493 | tristate "Tilera hypervisor RTC support" | |
1494 | depends on TILE | |
1495 | help | |
1496 | Enable support for the Linux driver side of the Tilera | |
1497 | hypervisor's real-time clock interface. | |
1498 | ||
2809e80b GX |
1499 | config RTC_DRV_PUV3 |
1500 | tristate "PKUnity v3 RTC support" | |
1501 | depends on ARCH_PUV3 | |
1502 | help | |
1503 | This enables support for the RTC in the PKUnity-v3 SoCs. | |
1504 | ||
1505 | This drive can also be built as a module. If so, the module | |
1506 | will be called rtc-puv3. | |
1507 | ||
b4f0b880 | 1508 | config RTC_DRV_LOONGSON1 |
1509 | tristate "loongson1 RTC support" | |
1510 | depends on MACH_LOONGSON1 | |
1511 | help | |
1512 | This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year | |
1513 | counter) to be used as a RTC. | |
1514 | ||
1515 | This driver can also be built as a module. If so, the module | |
1516 | will be called rtc-ls1x. | |
1517 | ||
79811595 | 1518 | config RTC_DRV_MXC |
b224b9ac FE |
1519 | tristate "Freescale MXC Real Time Clock" |
1520 | depends on ARCH_MXC | |
b224b9ac FE |
1521 | help |
1522 | If you say yes here you get support for the Freescale MXC | |
1523 | RTC module. | |
1524 | ||
1525 | This driver can also be built as a module, if so, the module | |
1526 | will be called "rtc-mxc". | |
1527 | ||
179a502f SG |
1528 | config RTC_DRV_SNVS |
1529 | tristate "Freescale SNVS RTC support" | |
1530 | depends on HAS_IOMEM | |
1531 | depends on OF | |
1532 | help | |
1533 | If you say yes here you get support for the Freescale SNVS | |
1534 | Low Power (LP) RTC module. | |
1535 | ||
1536 | This driver can also be built as a module, if so, the module | |
1537 | will be called "rtc-snvs". | |
1538 | ||
e88b815e XD |
1539 | config RTC_DRV_SIRFSOC |
1540 | tristate "SiRFSOC RTC" | |
1541 | depends on ARCH_SIRF | |
1542 | help | |
1543 | Say "yes" here to support the real time clock on SiRF SOC chips. | |
1544 | This driver can also be built as a module called rtc-sirfsoc. | |
1545 | ||
453b4c6d JJ |
1546 | config RTC_DRV_MOXART |
1547 | tristate "MOXA ART RTC" | |
441fb768 | 1548 | depends on ARCH_MOXART || COMPILE_TEST |
453b4c6d JJ |
1549 | help |
1550 | If you say yes here you get support for the MOXA ART | |
1551 | RTC module. | |
1552 | ||
1553 | This driver can also be built as a module. If so, the module | |
1554 | will be called rtc-moxart | |
1555 | ||
fc297911 TF |
1556 | config RTC_DRV_MT6397 |
1557 | tristate "Mediatek Real Time Clock driver" | |
1558 | depends on MFD_MT6397 || COMPILE_TEST | |
1559 | help | |
1560 | This selects the Mediatek(R) RTC driver. RTC is part of Mediatek | |
1561 | MT6397 PMIC. You should enable MT6397 PMIC MFD before select | |
1562 | Mediatek(R) RTC driver. | |
1563 | ||
1564 | If you want to use Mediatek(R) RTC interface, select Y or M here. | |
1565 | ||
f12d8695 LH |
1566 | config RTC_DRV_XGENE |
1567 | tristate "APM X-Gene RTC" | |
706b632d | 1568 | depends on HAS_IOMEM |
fdf8afa1 | 1569 | depends on ARCH_XGENE || COMPILE_TEST |
f12d8695 LH |
1570 | help |
1571 | If you say yes here you get support for the APM X-Gene SoC real time | |
1572 | clock. | |
1573 | ||
1574 | This driver can also be built as a module, if so, the module | |
1575 | will be called "rtc-xgene". | |
1576 | ||
62e00cb9 AH |
1577 | comment "HID Sensor RTC drivers" |
1578 | ||
1579 | config RTC_DRV_HID_SENSOR_TIME | |
1580 | tristate "HID Sensor Time" | |
1581 | depends on USB_HID | |
1582 | select IIO | |
1583 | select HID_SENSOR_HUB | |
1584 | select HID_SENSOR_IIO_COMMON | |
1585 | help | |
1586 | Say yes here to build support for the HID Sensors of type Time. | |
1587 | This drivers makes such sensors available as RTCs. | |
1588 | ||
1589 | If this driver is compiled as a module, it will be named | |
1590 | rtc-hid-sensor-time. | |
1591 | ||
1592 | ||
bb35fb20 | 1593 | endif # RTC_CLASS |