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