diff options
-rw-r--r-- | drivers/rtc/Kconfig | 250 |
1 files changed, 130 insertions, 120 deletions
diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig index a53ef4d670cc..5e439836db2d 100644 --- a/drivers/rtc/Kconfig +++ b/drivers/rtc/Kconfig | |||
@@ -102,44 +102,26 @@ config RTC_INTF_DEV_UIE_EMUL | |||
102 | driver does not expose RTC_UIE ioctls. Those requests generate | 102 | driver does not expose RTC_UIE ioctls. Those requests generate |
103 | once-per-second update interrupts, used for synchronization. | 103 | once-per-second update interrupts, used for synchronization. |
104 | 104 | ||
105 | comment "RTC drivers" | 105 | config RTC_DRV_TEST |
106 | tristate "Test driver/device" | ||
106 | depends on RTC_CLASS | 107 | depends on RTC_CLASS |
107 | |||
108 | # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> | ||
109 | # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a | ||
110 | # global rtc_lock ... it's not yet just another platform_device. | ||
111 | |||
112 | config RTC_DRV_CMOS | ||
113 | tristate "PC-style 'CMOS' real time clock" | ||
114 | depends on RTC_CLASS && (X86 || ALPHA || ARM26 || ARM \ | ||
115 | || M32R || ATARI || POWERPC) | ||
116 | help | ||
117 | Say "yes" here to get direct support for the real time clock | ||
118 | found in every PC or ACPI-based system, and some other boards. | ||
119 | Specifically the original MC146818, compatibles like those in | ||
120 | PC south bridges, the DS12887 or M48T86, some multifunction | ||
121 | or LPC bus chips, and so on. | ||
122 | |||
123 | Your system will need to define the platform device used by | ||
124 | this driver, otherwise it won't be accessible. This means | ||
125 | you can safely enable this driver if you don't know whether | ||
126 | or not your board has this kind of hardware. | ||
127 | |||
128 | This driver can also be built as a module. If so, the module | ||
129 | will be called rtc-cmos. | ||
130 | |||
131 | config RTC_DRV_X1205 | ||
132 | tristate "Xicor/Intersil X1205" | ||
133 | depends on RTC_CLASS && I2C | ||
134 | help | 108 | help |
135 | If you say yes here you get support for the | 109 | If you say yes here you get support for the |
136 | Xicor/Intersil X1205 RTC chip. | 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. | ||
137 | 116 | ||
138 | This driver can also be built as a module. If so, the module | 117 | This driver can also be built as a module. If so, the module |
139 | will be called rtc-x1205. | 118 | will be called rtc-test. |
119 | |||
120 | comment "I2C RTC drivers" | ||
121 | depends on RTC_CLASS | ||
140 | 122 | ||
141 | config RTC_DRV_DS1307 | 123 | config RTC_DRV_DS1307 |
142 | tristate "Dallas/Maxim DS1307 and similar I2C RTC chips" | 124 | tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00" |
143 | depends on RTC_CLASS && I2C | 125 | depends on RTC_CLASS && I2C |
144 | help | 126 | help |
145 | If you say yes here you get support for various compatible RTC | 127 | If you say yes here you get support for various compatible RTC |
@@ -156,53 +138,55 @@ config RTC_DRV_DS1307 | |||
156 | This driver can also be built as a module. If so, the module | 138 | This driver can also be built as a module. If so, the module |
157 | will be called rtc-ds1307. | 139 | will be called rtc-ds1307. |
158 | 140 | ||
159 | config RTC_DRV_DS1553 | 141 | config RTC_DRV_DS1672 |
160 | tristate "Dallas DS1553" | 142 | tristate "Dallas/Maxim DS1672" |
161 | depends on RTC_CLASS | 143 | depends on RTC_CLASS && I2C |
162 | help | 144 | help |
163 | If you say yes here you get support for the | 145 | If you say yes here you get support for the |
164 | Dallas DS1553 timekeeping chip. | 146 | Dallas/Maxim DS1672 timekeeping chip. |
165 | 147 | ||
166 | This driver can also be built as a module. If so, the module | 148 | This driver can also be built as a module. If so, the module |
167 | will be called rtc-ds1553. | 149 | will be called rtc-ds1672. |
168 | 150 | ||
169 | config RTC_DRV_ISL1208 | 151 | config RTC_DRV_MAX6900 |
170 | tristate "Intersil 1208" | 152 | tristate "Maxim 6900" |
171 | depends on RTC_CLASS && I2C | 153 | depends on RTC_CLASS && I2C |
172 | help | 154 | help |
173 | If you say yes here you get support for the | 155 | If you say yes here you will get support for the |
174 | Intersil 1208 RTC chip. | 156 | Maxim MAX6900 I2C RTC chip. |
175 | 157 | ||
176 | This driver can also be built as a module. If so, the module | 158 | This driver can also be built as a module. If so, the module |
177 | will be called rtc-isl1208. | 159 | will be called rtc-max6900. |
178 | 160 | ||
179 | config RTC_DRV_DS1672 | 161 | config RTC_DRV_RS5C372 |
180 | tristate "Dallas/Maxim DS1672" | 162 | tristate "Ricoh RS5C372A/B" |
181 | depends on RTC_CLASS && I2C | 163 | depends on RTC_CLASS && I2C |
182 | help | 164 | help |
183 | If you say yes here you get support for the | 165 | If you say yes here you get support for the |
184 | Dallas/Maxim DS1672 timekeeping chip. | 166 | Ricoh RS5C372A and RS5C372B RTC chips. |
185 | 167 | ||
186 | This driver can also be built as a module. If so, the module | 168 | This driver can also be built as a module. If so, the module |
187 | will be called rtc-ds1672. | 169 | will be called rtc-rs5c372. |
188 | 170 | ||
189 | config RTC_DRV_DS1742 | 171 | config RTC_DRV_ISL1208 |
190 | tristate "Dallas DS1742/1743" | 172 | tristate "Intersil 1208" |
191 | depends on RTC_CLASS | 173 | depends on RTC_CLASS && I2C |
192 | help | 174 | help |
193 | If you say yes here you get support for the | 175 | If you say yes here you get support for the |
194 | Dallas DS1742/1743 timekeeping chip. | 176 | Intersil 1208 RTC chip. |
195 | 177 | ||
196 | This driver can also be built as a module. If so, the module | 178 | This driver can also be built as a module. If so, the module |
197 | will be called rtc-ds1742. | 179 | will be called rtc-isl1208. |
198 | 180 | ||
199 | config RTC_DRV_OMAP | 181 | config RTC_DRV_X1205 |
200 | tristate "TI OMAP1" | 182 | tristate "Xicor/Intersil X1205" |
201 | depends on RTC_CLASS && ( \ | 183 | depends on RTC_CLASS && I2C |
202 | ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 ) | ||
203 | help | 184 | help |
204 | Say "yes" here to support the real time clock on TI OMAP1 chips. | 185 | If you say yes here you get support for the |
205 | This driver can also be built as a module called rtc-omap. | 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. | ||
206 | 190 | ||
207 | config RTC_DRV_PCF8563 | 191 | config RTC_DRV_PCF8563 |
208 | tristate "Philips PCF8563/Epson RTC8564" | 192 | tristate "Philips PCF8563/Epson RTC8564" |
@@ -217,16 +201,20 @@ config RTC_DRV_PCF8563 | |||
217 | 201 | ||
218 | config RTC_DRV_PCF8583 | 202 | config RTC_DRV_PCF8583 |
219 | tristate "Philips PCF8583" | 203 | tristate "Philips PCF8583" |
220 | depends on RTC_CLASS && I2C && ARCH_RPC | 204 | depends on RTC_CLASS && I2C |
221 | help | 205 | help |
222 | If you say yes here you get support for the Philips PCF8583 | 206 | If you say yes here you get support for the Philips PCF8583 |
223 | RTC chip found on Acorn RiscPCs. This driver supports the | 207 | RTC chip found on Acorn RiscPCs. This driver supports the |
224 | platform specific method of retrieving the current year from | 208 | platform specific method of retrieving the current year from |
225 | the RTC's SRAM. | 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. | ||
226 | 211 | ||
227 | This driver can also be built as a module. If so, the module | 212 | This driver can also be built as a module. If so, the module |
228 | will be called rtc-pcf8583. | 213 | will be called rtc-pcf8583. |
229 | 214 | ||
215 | comment "SPI RTC drivers" | ||
216 | depends on RTC_CLASS | ||
217 | |||
230 | config RTC_DRV_RS5C348 | 218 | config RTC_DRV_RS5C348 |
231 | tristate "Ricoh RS5C348A/B" | 219 | tristate "Ricoh RS5C348A/B" |
232 | depends on RTC_CLASS && SPI | 220 | depends on RTC_CLASS && SPI |
@@ -237,15 +225,92 @@ config RTC_DRV_RS5C348 | |||
237 | This driver can also be built as a module. If so, the module | 225 | This driver can also be built as a module. If so, the module |
238 | will be called rtc-rs5c348. | 226 | will be called rtc-rs5c348. |
239 | 227 | ||
240 | config RTC_DRV_RS5C372 | 228 | config RTC_DRV_MAX6902 |
241 | tristate "Ricoh RS5C372A/B" | 229 | tristate "Maxim 6902" |
242 | depends on RTC_CLASS && I2C | 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 | ||
243 | help | 267 | help |
244 | If you say yes here you get support for the | 268 | If you say yes here you get support for the |
245 | Ricoh RS5C372A and RS5C372B RTC chips. | 269 | Dallas DS1553 timekeeping chip. |
246 | 270 | ||
247 | This driver can also be built as a module. If so, the module | 271 | This driver can also be built as a module. If so, the module |
248 | will be called rtc-rs5c372. | 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. | ||
249 | 314 | ||
250 | config RTC_DRV_S3C | 315 | config RTC_DRV_S3C |
251 | tristate "Samsung S3C series SoC RTC" | 316 | tristate "Samsung S3C series SoC RTC" |
@@ -263,16 +328,6 @@ config RTC_DRV_S3C | |||
263 | This driver can also be build as a module. If so, the module | 328 | This driver can also be build as a module. If so, the module |
264 | will be called rtc-s3c. | 329 | will be called rtc-s3c. |
265 | 330 | ||
266 | config RTC_DRV_M48T86 | ||
267 | tristate "ST M48T86/Dallas DS12887" | ||
268 | depends on RTC_CLASS | ||
269 | help | ||
270 | If you say Y here you will get support for the | ||
271 | ST M48T86 and Dallas DS12887 RTC chips. | ||
272 | |||
273 | This driver can also be built as a module. If so, the module | ||
274 | will be called rtc-m48t86. | ||
275 | |||
276 | config RTC_DRV_EP93XX | 331 | config RTC_DRV_EP93XX |
277 | tristate "Cirrus Logic EP93XX" | 332 | tristate "Cirrus Logic EP93XX" |
278 | depends on RTC_CLASS && ARCH_EP93XX | 333 | depends on RTC_CLASS && ARCH_EP93XX |
@@ -318,7 +373,7 @@ config RTC_DRV_PL031 | |||
318 | depends on RTC_CLASS && ARM_AMBA | 373 | depends on RTC_CLASS && ARM_AMBA |
319 | help | 374 | help |
320 | If you say Y here you will get access to ARM AMBA | 375 | If you say Y here you will get access to ARM AMBA |
321 | PrimeCell PL031 UART found on certain ARM SOCs. | 376 | PrimeCell PL031 RTC found on certain ARM SOCs. |
322 | 377 | ||
323 | To compile this driver as a module, choose M here: the | 378 | To compile this driver as a module, choose M here: the |
324 | module will be called rtc-pl031. | 379 | module will be called rtc-pl031. |
@@ -329,51 +384,6 @@ config RTC_DRV_AT91RM9200 | |||
329 | help | 384 | help |
330 | Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock). | 385 | Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock). |
331 | 386 | ||
332 | config RTC_DRV_TEST | ||
333 | tristate "Test driver/device" | ||
334 | depends on RTC_CLASS | ||
335 | help | ||
336 | If you say yes here you get support for the | ||
337 | RTC test driver. It's a software RTC which can be | ||
338 | used to test the RTC subsystem APIs. It gets | ||
339 | the time from the system clock. | ||
340 | You want this driver only if you are doing development | ||
341 | on the RTC subsystem. Please read the source code | ||
342 | for further details. | ||
343 | |||
344 | This driver can also be built as a module. If so, the module | ||
345 | will be called rtc-test. | ||
346 | |||
347 | config RTC_DRV_MAX6900 | ||
348 | tristate "Maxim 6900" | ||
349 | depends on RTC_CLASS && I2C | ||
350 | help | ||
351 | If you say yes here you will get support for the | ||
352 | Maxim MAX6900 I2C RTC chip. | ||
353 | |||
354 | This driver can also be built as a module. If so, the module | ||
355 | will be called rtc-max6900. | ||
356 | |||
357 | config RTC_DRV_MAX6902 | ||
358 | tristate "Maxim 6902" | ||
359 | depends on RTC_CLASS && SPI | ||
360 | help | ||
361 | If you say yes here you will get support for the | ||
362 | Maxim MAX6902 spi RTC chip. | ||
363 | |||
364 | This driver can also be built as a module. If so, the module | ||
365 | will be called rtc-max6902. | ||
366 | |||
367 | config RTC_DRV_V3020 | ||
368 | tristate "EM Microelectronic V3020" | ||
369 | depends on RTC_CLASS | ||
370 | help | ||
371 | If you say yes here you will get support for the | ||
372 | EM Microelectronic v3020 RTC chip. | ||
373 | |||
374 | This driver can also be built as a module. If so, the module | ||
375 | will be called rtc-v3020. | ||
376 | |||
377 | config RTC_DRV_BFIN | 387 | config RTC_DRV_BFIN |
378 | tristate "Blackfin On-Chip RTC" | 388 | tristate "Blackfin On-Chip RTC" |
379 | depends on RTC_CLASS && BFIN | 389 | depends on RTC_CLASS && BFIN |