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