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