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