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