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