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