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