]>
Commit | Line | Data |
---|---|---|
7be2c7c9 | 1 | # |
c58411e9 AZ |
2 | # RTC class/drivers configuration |
3 | # | |
4 | ||
5 | config RTC_LIB | |
0c86edc0 AZ |
6 | tristate |
7 | ||
bb35fb20 JE |
8 | menuconfig RTC_CLASS |
9 | tristate "Real Time Clock" | |
0c86edc0 | 10 | default n |
bb35fb20 | 11 | depends on !S390 |
0c86edc0 AZ |
12 | select RTC_LIB |
13 | help | |
14 | Generic RTC class support. If you say yes here, you will | |
15 | be allowed to plug one or more RTCs to your system. You will | |
27ae4104 | 16 | probably want to enable one or more of the interfaces below. |
0c86edc0 AZ |
17 | |
18 | This driver can also be built as a module. If so, the module | |
19 | will be called rtc-class. | |
20 | ||
bb35fb20 JE |
21 | if RTC_CLASS |
22 | ||
09b6bdb3 AZ |
23 | if GEN_RTC || RTC |
24 | comment "Conflicting RTC option has been selected, check GEN_RTC and RTC" | |
25 | endif | |
26 | ||
0c86edc0 | 27 | config RTC_HCTOSYS |
7ca1d488 | 28 | bool "Set system time from RTC on startup and resume" |
0c86edc0 AZ |
29 | depends on RTC_CLASS = y |
30 | default y | |
31 | help | |
7ca1d488 DB |
32 | If you say yes here, the system time (wall clock) will be set using |
33 | the value read from a specified RTC device. This is useful to avoid | |
34 | unnecessary fsck runs at boot time, and to network better. | |
0c86edc0 AZ |
35 | |
36 | config RTC_HCTOSYS_DEVICE | |
7ca1d488 | 37 | string "RTC used to set the system time" |
0c86edc0 AZ |
38 | depends on RTC_HCTOSYS = y |
39 | default "rtc0" | |
40 | help | |
7ca1d488 DB |
41 | The RTC device that will be used to (re)initialize the system |
42 | clock, usually rtc0. Initialization is done when the system | |
779d2089 DB |
43 | starts up, and when it resumes from a low power state. This |
44 | device should record time in UTC, since the kernel won't do | |
45 | timezone correction. | |
7ca1d488 | 46 | |
55ff1aba DB |
47 | The driver for this RTC device must be loaded before late_initcall |
48 | functions run, so it must usually be statically linked. | |
49 | ||
7ca1d488 DB |
50 | This clock should be battery-backed, so that it reads the correct |
51 | time when the system boots from a power-off state. Otherwise, your | |
52 | system will need an external clock source (like an NTP server). | |
53 | ||
54 | If the clock you specify here is not battery backed, it may still | |
55 | be useful to reinitialize system time when resuming from system | |
09b6bdb3 | 56 | sleep states. Do not specify an RTC here unless it stays powered |
7ca1d488 | 57 | during all this system's supported sleep states. |
0c86edc0 | 58 | |
9e86ecb6 DB |
59 | config RTC_DEBUG |
60 | bool "RTC debug support" | |
61 | depends on RTC_CLASS = y | |
62 | help | |
63 | Say yes here to enable debugging support in the RTC framework | |
64 | and individual RTC drivers. | |
65 | ||
0c86edc0 | 66 | comment "RTC interfaces" |
0c86edc0 | 67 | |
c5c3e192 | 68 | config RTC_INTF_SYSFS |
e40659c5 | 69 | boolean "/sys/class/rtc/rtcN (sysfs)" |
bb35fb20 | 70 | depends on SYSFS |
c5c3e192 AZ |
71 | default RTC_CLASS |
72 | help | |
9e86ecb6 DB |
73 | Say yes here if you want to use your RTCs using sysfs interfaces, |
74 | /sys/class/rtc/rtc0 through /sys/.../rtcN. | |
c5c3e192 AZ |
75 | |
76 | This driver can also be built as a module. If so, the module | |
77 | will be called rtc-sysfs. | |
78 | ||
728a2947 | 79 | config RTC_INTF_PROC |
e40659c5 | 80 | boolean "/proc/driver/rtc (procfs for rtc0)" |
bb35fb20 | 81 | depends on PROC_FS |
728a2947 AZ |
82 | default RTC_CLASS |
83 | help | |
9e86ecb6 DB |
84 | Say yes here if you want to use your first RTC through the proc |
85 | interface, /proc/driver/rtc. Other RTCs will not be available | |
86 | through that API. | |
728a2947 AZ |
87 | |
88 | This driver can also be built as a module. If so, the module | |
89 | will be called rtc-proc. | |
90 | ||
e824290e | 91 | config RTC_INTF_DEV |
e40659c5 | 92 | boolean "/dev/rtcN (character devices)" |
e824290e AZ |
93 | default RTC_CLASS |
94 | help | |
9e86ecb6 DB |
95 | Say yes here if you want to use your RTCs using the /dev |
96 | interfaces, which "udev" sets up as /dev/rtc0 through | |
97 | /dev/rtcN. You may want to set up a symbolic link so one | |
98 | of these can be accessed as /dev/rtc, which is a name | |
99 | expected by "hwclock" and some other programs. | |
e824290e AZ |
100 | |
101 | This driver can also be built as a module. If so, the module | |
102 | will be called rtc-dev. | |
103 | ||
655066c3 AN |
104 | config RTC_INTF_DEV_UIE_EMUL |
105 | bool "RTC UIE emulation on dev interface" | |
106 | depends on RTC_INTF_DEV | |
107 | help | |
3dde6ad8 | 108 | Provides an emulation for RTC_UIE if the underlying rtc chip |
9e86ecb6 DB |
109 | driver does not expose RTC_UIE ioctls. Those requests generate |
110 | once-per-second update interrupts, used for synchronization. | |
655066c3 | 111 | |
09a21e56 AZ |
112 | config RTC_DRV_TEST |
113 | tristate "Test driver/device" | |
1fec7c66 AZ |
114 | help |
115 | If you say yes here you get support for the | |
09a21e56 AZ |
116 | RTC test driver. It's a software RTC which can be |
117 | used to test the RTC subsystem APIs. It gets | |
118 | the time from the system clock. | |
119 | You want this driver only if you are doing development | |
120 | on the RTC subsystem. Please read the source code | |
121 | for further details. | |
1fec7c66 AZ |
122 | |
123 | This driver can also be built as a module. If so, the module | |
09a21e56 AZ |
124 | will be called rtc-test. |
125 | ||
126 | comment "I2C RTC drivers" | |
bb35fb20 JE |
127 | depends on I2C |
128 | ||
129 | if I2C | |
1fec7c66 | 130 | |
1abb0dc9 | 131 | config RTC_DRV_DS1307 |
09a21e56 | 132 | tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00" |
1abb0dc9 DB |
133 | help |
134 | If you say yes here you get support for various compatible RTC | |
135 | chips (often with battery backup) connected with I2C. This driver | |
136 | should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00, | |
137 | and probably other chips. In some cases the RTC must already | |
138 | have been initialized (by manufacturing or a bootloader). | |
139 | ||
140 | The first seven registers on these chips hold an RTC, and other | |
141 | registers may add features such as NVRAM, a trickle charger for | |
682d73f6 DB |
142 | the RTC/NVRAM backup power, and alarms. NVRAM is visible in |
143 | sysfs, but other chip features may not be available. | |
1abb0dc9 DB |
144 | |
145 | This driver can also be built as a module. If so, the module | |
146 | will be called rtc-ds1307. | |
147 | ||
bf4994d7 | 148 | config RTC_DRV_DS1374 |
09b6bdb3 | 149 | tristate "Dallas/Maxim DS1374" |
bf4994d7 SW |
150 | depends on RTC_CLASS && I2C |
151 | help | |
152 | If you say yes here you get support for Dallas Semiconductor | |
153 | DS1374 real-time clock chips. If an interrupt is associated | |
154 | with the device, the alarm functionality is supported. | |
155 | ||
156 | This driver can also be built as a module. If so, the module | |
157 | will be called rtc-ds1374. | |
158 | ||
09a21e56 AZ |
159 | config RTC_DRV_DS1672 |
160 | tristate "Dallas/Maxim DS1672" | |
9bf5b4f5 AN |
161 | help |
162 | If you say yes here you get support for the | |
09a21e56 | 163 | Dallas/Maxim DS1672 timekeeping chip. |
9bf5b4f5 AN |
164 | |
165 | This driver can also be built as a module. If so, the module | |
09a21e56 | 166 | will be called rtc-ds1672. |
9bf5b4f5 | 167 | |
09a21e56 | 168 | config RTC_DRV_MAX6900 |
09b6bdb3 | 169 | tristate "Maxim MAX6900" |
7e56a7dc | 170 | help |
09a21e56 AZ |
171 | If you say yes here you will get support for the |
172 | Maxim MAX6900 I2C RTC chip. | |
7e56a7dc HVR |
173 | |
174 | This driver can also be built as a module. If so, the module | |
09a21e56 | 175 | will be called rtc-max6900. |
7e56a7dc | 176 | |
09a21e56 | 177 | config RTC_DRV_RS5C372 |
d815461c | 178 | tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A" |
edf1aaa3 AZ |
179 | help |
180 | If you say yes here you get support for the | |
d815461c | 181 | Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. |
edf1aaa3 AZ |
182 | |
183 | This driver can also be built as a module. If so, the module | |
09a21e56 | 184 | will be called rtc-rs5c372. |
edf1aaa3 | 185 | |
09a21e56 | 186 | config RTC_DRV_ISL1208 |
09b6bdb3 | 187 | tristate "Intersil ISL1208" |
5ec3e4b7 AN |
188 | help |
189 | If you say yes here you get support for the | |
09b6bdb3 | 190 | Intersil ISL1208 RTC chip. |
5ec3e4b7 AN |
191 | |
192 | This driver can also be built as a module. If so, the module | |
09a21e56 | 193 | will be called rtc-isl1208. |
5ec3e4b7 | 194 | |
09a21e56 AZ |
195 | config RTC_DRV_X1205 |
196 | tristate "Xicor/Intersil X1205" | |
db68b189 | 197 | help |
09a21e56 AZ |
198 | If you say yes here you get support for the |
199 | Xicor/Intersil X1205 RTC chip. | |
200 | ||
201 | This driver can also be built as a module. If so, the module | |
202 | will be called rtc-x1205. | |
db68b189 | 203 | |
b5a82d62 AZ |
204 | config RTC_DRV_PCF8563 |
205 | tristate "Philips PCF8563/Epson RTC8564" | |
b5a82d62 AZ |
206 | help |
207 | If you say yes here you get support for the | |
208 | Philips PCF8563 RTC chip. The Epson RTC8564 | |
209 | should work as well. | |
210 | ||
211 | This driver can also be built as a module. If so, the module | |
212 | will be called rtc-pcf8563. | |
213 | ||
9c0c5705 L |
214 | config RTC_DRV_PCF8583 |
215 | tristate "Philips PCF8583" | |
9c0c5705 | 216 | help |
bb71f99f | 217 | If you say yes here you get support for the Philips PCF8583 |
09a21e56 | 218 | RTC chip found on Acorn RiscPCs. This driver supports the |
bb71f99f | 219 | platform specific method of retrieving the current year from |
09a21e56 AZ |
220 | the RTC's SRAM. It will work on other platforms with the same |
221 | chip, but the year will probably have to be tweaked. | |
9c0c5705 L |
222 | |
223 | This driver can also be built as a module. If so, the module | |
224 | will be called rtc-pcf8583. | |
225 | ||
caaff562 | 226 | config RTC_DRV_M41T80 |
09b6bdb3 | 227 | tristate "ST M41T80/81/82/83/84/85/87" |
caaff562 AN |
228 | help |
229 | If you say Y here you will get support for the | |
230 | ST M41T80 RTC chips series. Currently following chips are | |
231 | supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85 | |
232 | and M41ST87. | |
233 | ||
234 | This driver can also be built as a module. If so, the module | |
235 | will be called rtc-m41t80. | |
236 | ||
617780d2 AN |
237 | config RTC_DRV_M41T80_WDT |
238 | bool "ST M41T80 series RTC watchdog timer" | |
239 | depends on RTC_DRV_M41T80 | |
240 | help | |
241 | If you say Y here you will get support for the | |
242 | watchdog timer in ST M41T80 RTC chips series. | |
243 | ||
0c4a59fe TL |
244 | config RTC_DRV_TWL92330 |
245 | boolean "TI TWL92330/Menelaus" | |
bb35fb20 | 246 | depends on MENELAUS |
0c4a59fe TL |
247 | help |
248 | If you say yes here you get support for the RTC on the | |
01dd2fbf | 249 | TWL92330 "Menelaus" power management chip, used with OMAP2 |
0c4a59fe TL |
250 | platforms. The support is integrated with the rest of |
251 | the Menelaus driver; it's not separate module. | |
252 | ||
bb35fb20 JE |
253 | endif # I2C |
254 | ||
09a21e56 | 255 | comment "SPI RTC drivers" |
bb35fb20 JE |
256 | |
257 | if SPI_MASTER | |
09a21e56 | 258 | |
09b6bdb3 AZ |
259 | config RTC_DRV_MAX6902 |
260 | tristate "Maxim MAX6902" | |
261 | help | |
262 | If you say yes here you will get support for the | |
263 | Maxim MAX6902 SPI RTC chip. | |
264 | ||
265 | This driver can also be built as a module. If so, the module | |
266 | will be called rtc-max6902. | |
267 | ||
e0ac4761 AN |
268 | config RTC_DRV_RS5C348 |
269 | tristate "Ricoh RS5C348A/B" | |
e0ac4761 AN |
270 | help |
271 | If you say yes here you get support for the | |
272 | Ricoh RS5C348A and RS5C348B RTC chips. | |
273 | ||
274 | This driver can also be built as a module. If so, the module | |
275 | will be called rtc-rs5c348. | |
276 | ||
bb35fb20 JE |
277 | endif # SPI_MASTER |
278 | ||
09a21e56 | 279 | comment "Platform RTC drivers" |
09a21e56 AZ |
280 | |
281 | # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> | |
282 | # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a | |
283 | # global rtc_lock ... it's not yet just another platform_device. | |
284 | ||
285 | config RTC_DRV_CMOS | |
286 | tristate "PC-style 'CMOS'" | |
bb35fb20 | 287 | depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS |
09a21e56 AZ |
288 | help |
289 | Say "yes" here to get direct support for the real time clock | |
290 | found in every PC or ACPI-based system, and some other boards. | |
291 | Specifically the original MC146818, compatibles like those in | |
292 | PC south bridges, the DS12887 or M48T86, some multifunction | |
293 | or LPC bus chips, and so on. | |
294 | ||
295 | Your system will need to define the platform device used by | |
296 | this driver, otherwise it won't be accessible. This means | |
297 | you can safely enable this driver if you don't know whether | |
298 | or not your board has this kind of hardware. | |
299 | ||
300 | This driver can also be built as a module. If so, the module | |
301 | will be called rtc-cmos. | |
302 | ||
537739de TB |
303 | config RTC_DRV_DS1216 |
304 | tristate "Dallas DS1216" | |
bb35fb20 | 305 | depends on SNI_RM |
537739de TB |
306 | help |
307 | If you say yes here you get support for the Dallas DS1216 RTC chips. | |
308 | ||
739d340d PM |
309 | config RTC_DRV_DS1302 |
310 | tristate "Dallas DS1302" | |
311 | depends on SH_SECUREEDGE5410 | |
312 | help | |
313 | If you say yes here you get support for the Dallas DS1302 RTC chips. | |
314 | ||
09a21e56 | 315 | config RTC_DRV_DS1553 |
09b6bdb3 | 316 | tristate "Maxim/Dallas DS1553" |
7520b94d AZ |
317 | help |
318 | If you say yes here you get support for the | |
09b6bdb3 | 319 | Maxim/Dallas DS1553 timekeeping chip. |
7520b94d AZ |
320 | |
321 | This driver can also be built as a module. If so, the module | |
09a21e56 AZ |
322 | will be called rtc-ds1553. |
323 | ||
09b6bdb3 AZ |
324 | config RTC_DRV_DS1742 |
325 | tristate "Maxim/Dallas DS1742/1743" | |
02964115 TH |
326 | help |
327 | If you say yes here you get support for the | |
09b6bdb3 | 328 | Maxim/Dallas DS1742/1743 timekeeping chip. |
02964115 TH |
329 | |
330 | This driver can also be built as a module. If so, the module | |
09b6bdb3 | 331 | will be called rtc-ds1742. |
02964115 | 332 | |
09b6bdb3 AZ |
333 | config RTC_DRV_STK17TA8 |
334 | tristate "Simtek STK17TA8" | |
335 | depends on RTC_CLASS | |
09a21e56 AZ |
336 | help |
337 | If you say yes here you get support for the | |
09b6bdb3 | 338 | Simtek STK17TA8 timekeeping chip. |
09a21e56 AZ |
339 | |
340 | This driver can also be built as a module. If so, the module | |
09b6bdb3 | 341 | will be called rtc-stk17ta8. |
09a21e56 AZ |
342 | |
343 | config RTC_DRV_M48T86 | |
344 | tristate "ST M48T86/Dallas DS12887" | |
09a21e56 AZ |
345 | help |
346 | If you say Y here you will get support for the | |
347 | ST M48T86 and Dallas DS12887 RTC chips. | |
348 | ||
349 | This driver can also be built as a module. If so, the module | |
350 | will be called rtc-m48t86. | |
351 | ||
2e774c7c MZ |
352 | config RTC_DRV_M48T59 |
353 | tristate "ST M48T59" | |
2e774c7c MZ |
354 | help |
355 | If you say Y here you will get support for the | |
356 | ST M48T59 RTC chip. | |
357 | ||
358 | This driver can also be built as a module, if so, the module | |
359 | will be called "rtc-m48t59". | |
360 | ||
09a21e56 AZ |
361 | config RTC_DRV_V3020 |
362 | tristate "EM Microelectronic V3020" | |
09a21e56 AZ |
363 | help |
364 | If you say yes here you will get support for the | |
365 | EM Microelectronic v3020 RTC chip. | |
366 | ||
367 | This driver can also be built as a module. If so, the module | |
368 | will be called rtc-v3020. | |
369 | ||
370 | comment "on-CPU RTC drivers" | |
09a21e56 AZ |
371 | |
372 | config RTC_DRV_OMAP | |
373 | tristate "TI OMAP1" | |
bb35fb20 | 374 | depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 |
09a21e56 AZ |
375 | help |
376 | Say "yes" here to support the real time clock on TI OMAP1 chips. | |
377 | This driver can also be built as a module called rtc-omap. | |
7520b94d | 378 | |
1add6781 BD |
379 | config RTC_DRV_S3C |
380 | tristate "Samsung S3C series SoC RTC" | |
bb35fb20 | 381 | depends on ARCH_S3C2410 |
1add6781 BD |
382 | help |
383 | RTC (Realtime Clock) driver for the clock inbuilt into the | |
384 | Samsung S3C24XX series of SoCs. This can provide periodic | |
385 | interrupt rates from 1Hz to 64Hz for user programs, and | |
386 | wakeup from Alarm. | |
387 | ||
388 | The driver currently supports the common features on all the | |
389 | S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 | |
390 | and S3C2442. | |
391 | ||
392 | This driver can also be build as a module. If so, the module | |
393 | will be called rtc-s3c. | |
394 | ||
fd507e2f AZ |
395 | config RTC_DRV_EP93XX |
396 | tristate "Cirrus Logic EP93XX" | |
bb35fb20 | 397 | depends on ARCH_EP93XX |
fd507e2f AZ |
398 | help |
399 | If you say yes here you get support for the | |
400 | RTC embedded in the Cirrus Logic EP93XX processors. | |
401 | ||
402 | This driver can also be built as a module. If so, the module | |
403 | will be called rtc-ep93xx. | |
404 | ||
e842f1c8 RP |
405 | config RTC_DRV_SA1100 |
406 | tristate "SA11x0/PXA2xx" | |
bb35fb20 | 407 | depends on ARCH_SA1100 || ARCH_PXA |
e842f1c8 RP |
408 | help |
409 | If you say Y here you will get access to the real time clock | |
410 | built into your SA11x0 or PXA2xx CPU. | |
411 | ||
412 | To compile this driver as a module, choose M here: the | |
413 | module will be called rtc-sa1100. | |
fd507e2f | 414 | |
317a6104 PM |
415 | config RTC_DRV_SH |
416 | tristate "SuperH On-Chip RTC" | |
ff1b7506 | 417 | depends on RTC_CLASS && SUPERH |
317a6104 PM |
418 | help |
419 | Say Y here to enable support for the on-chip RTC found in | |
420 | most SuperH processors. | |
421 | ||
422 | To compile this driver as a module, choose M here: the | |
423 | module will be called rtc-sh. | |
424 | ||
8417eb7a | 425 | config RTC_DRV_VR41XX |
3e16f6af | 426 | tristate "NEC VR41XX" |
bb35fb20 | 427 | depends on CPU_VR41XX |
3e16f6af AZ |
428 | help |
429 | If you say Y here you will get access to the real time clock | |
430 | built into your NEC VR41XX CPU. | |
431 | ||
432 | To compile this driver as a module, choose M here: the | |
433 | module will be called rtc-vr41xx. | |
8417eb7a | 434 | |
8ae6e163 DS |
435 | config RTC_DRV_PL031 |
436 | tristate "ARM AMBA PL031 RTC" | |
bb35fb20 | 437 | depends on ARM_AMBA |
8ae6e163 DS |
438 | help |
439 | If you say Y here you will get access to ARM AMBA | |
09a21e56 | 440 | PrimeCell PL031 RTC found on certain ARM SOCs. |
8ae6e163 DS |
441 | |
442 | To compile this driver as a module, choose M here: the | |
443 | module will be called rtc-pl031. | |
444 | ||
fa04e78b HCE |
445 | config RTC_DRV_AT32AP700X |
446 | tristate "AT32AP700X series RTC" | |
bb35fb20 | 447 | depends on PLATFORM_AT32AP |
fa04e78b HCE |
448 | help |
449 | Driver for the internal RTC (Realtime Clock) on Atmel AVR32 | |
450 | AT32AP700x family processors. | |
451 | ||
7fc39f6d | 452 | config RTC_DRV_AT91RM9200 |
788b1fc6 | 453 | tristate "AT91RM9200" |
bb35fb20 | 454 | depends on ARCH_AT91RM9200 |
788b1fc6 AV |
455 | help |
456 | Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock). | |
457 | ||
8cc75c9a WB |
458 | config RTC_DRV_BFIN |
459 | tristate "Blackfin On-Chip RTC" | |
529a73fb | 460 | depends on BLACKFIN |
8cc75c9a WB |
461 | help |
462 | If you say yes here you will get support for the | |
463 | Blackfin On-Chip Real Time Clock. | |
464 | ||
465 | This driver can also be built as a module. If so, the module | |
466 | will be called rtc-bfin. | |
467 | ||
e9f2bd81 NI |
468 | config RTC_DRV_RS5C313 |
469 | tristate "Ricoh RS5C313" | |
bb35fb20 | 470 | depends on SH_LANDISK |
e9f2bd81 NI |
471 | help |
472 | If you say yes here you get support for the Ricoh RS5C313 RTC chips. | |
473 | ||
bb35fb20 | 474 | endif # RTC_CLASS |