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