1# 2# RTC class/drivers configuration 3# 4 5config RTC_LIB 6 tristate 7 8menuconfig RTC_CLASS 9 tristate "Real Time Clock" 10 default n 11 depends on !S390 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 16 probably want to enable one or more of the interfaces below. 17 18 This driver can also be built as a module. If so, the module 19 will be called rtc-core. 20 21if 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. This 40 device should record time in UTC, since the kernel won't do 41 timezone correction. 42 43 The driver for this RTC device must be loaded before late_initcall 44 functions run, so it must usually be statically linked. 45 46 This clock should be battery-backed, so that it reads the correct 47 time when the system boots from a power-off state. Otherwise, your 48 system will need an external clock source (like an NTP server). 49 50 If the clock you specify here is not battery backed, it may still 51 be useful to reinitialize system time when resuming from system 52 sleep states. Do not specify an RTC here unless it stays powered 53 during all this system's supported sleep states. 54 55config RTC_DEBUG 56 bool "RTC debug support" 57 depends on RTC_CLASS = y 58 help 59 Say yes here to enable debugging support in the RTC framework 60 and individual RTC drivers. 61 62comment "RTC interfaces" 63 64config RTC_INTF_SYSFS 65 boolean "/sys/class/rtc/rtcN (sysfs)" 66 depends on SYSFS 67 default RTC_CLASS 68 help 69 Say yes here if you want to use your RTCs using sysfs interfaces, 70 /sys/class/rtc/rtc0 through /sys/.../rtcN. 71 72 This driver can also be built as a module. If so, the module 73 will be called rtc-sysfs. 74 75config RTC_INTF_PROC 76 boolean "/proc/driver/rtc (procfs for rtc0)" 77 depends on PROC_FS 78 default RTC_CLASS 79 help 80 Say yes here if you want to use your first RTC through the proc 81 interface, /proc/driver/rtc. Other RTCs will not be available 82 through that API. 83 84 This driver can also be built as a module. If so, the module 85 will be called rtc-proc. 86 87config RTC_INTF_DEV 88 boolean "/dev/rtcN (character devices)" 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 help 111 If you say yes here you get support for the 112 RTC test driver. It's a software RTC which can be 113 used to test the RTC subsystem APIs. It gets 114 the time from the system clock. 115 You want this driver only if you are doing development 116 on the RTC subsystem. Please read the source code 117 for further details. 118 119 This driver can also be built as a module. If so, the module 120 will be called rtc-test. 121 122comment "I2C RTC drivers" 123 depends on I2C 124 125if I2C 126 127config RTC_DRV_DS1307 128 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00" 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. NVRAM is visible in 139 sysfs, but other chip features may not be available. 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_DS1374 145 tristate "Dallas/Maxim DS1374" 146 depends on RTC_CLASS && I2C 147 help 148 If you say yes here you get support for Dallas Semiconductor 149 DS1374 real-time clock chips. If an interrupt is associated 150 with the device, the alarm functionality is supported. 151 152 This driver can also be built as a module. If so, the module 153 will be called rtc-ds1374. 154 155config RTC_DRV_DS1672 156 tristate "Dallas/Maxim DS1672" 157 help 158 If you say yes here you get support for the 159 Dallas/Maxim DS1672 timekeeping chip. 160 161 This driver can also be built as a module. If so, the module 162 will be called rtc-ds1672. 163 164config RTC_DRV_MAX6900 165 tristate "Maxim MAX6900" 166 help 167 If you say yes here you will get support for the 168 Maxim MAX6900 I2C RTC chip. 169 170 This driver can also be built as a module. If so, the module 171 will be called rtc-max6900. 172 173config RTC_DRV_RS5C372 174 tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A" 175 help 176 If you say yes here you get support for the 177 Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. 178 179 This driver can also be built as a module. If so, the module 180 will be called rtc-rs5c372. 181 182config RTC_DRV_ISL1208 183 tristate "Intersil ISL1208" 184 help 185 If you say yes here you get support for the 186 Intersil ISL1208 RTC chip. 187 188 This driver can also be built as a module. If so, the module 189 will be called rtc-isl1208. 190 191config RTC_DRV_X1205 192 tristate "Xicor/Intersil X1205" 193 help 194 If you say yes here you get support for the 195 Xicor/Intersil X1205 RTC chip. 196 197 This driver can also be built as a module. If so, the module 198 will be called rtc-x1205. 199 200config RTC_DRV_PCF8563 201 tristate "Philips PCF8563/Epson RTC8564" 202 help 203 If you say yes here you get support for the 204 Philips PCF8563 RTC chip. The Epson RTC8564 205 should work as well. 206 207 This driver can also be built as a module. If so, the module 208 will be called rtc-pcf8563. 209 210config RTC_DRV_PCF8583 211 tristate "Philips PCF8583" 212 help 213 If you say yes here you get support for the Philips PCF8583 214 RTC chip found on Acorn RiscPCs. This driver supports the 215 platform specific method of retrieving the current year from 216 the RTC's SRAM. It will work on other platforms with the same 217 chip, but the year will probably have to be tweaked. 218 219 This driver can also be built as a module. If so, the module 220 will be called rtc-pcf8583. 221 222config RTC_DRV_M41T80 223 tristate "ST M41T80/81/82/83/84/85/87" 224 help 225 If you say Y here you will get support for the 226 ST M41T80 RTC chips series. Currently following chips are 227 supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85 228 and M41ST87. 229 230 This driver can also be built as a module. If so, the module 231 will be called rtc-m41t80. 232 233config RTC_DRV_M41T80_WDT 234 bool "ST M41T80 series RTC watchdog timer" 235 depends on RTC_DRV_M41T80 236 help 237 If you say Y here you will get support for the 238 watchdog timer in ST M41T80 RTC chips series. 239 240config RTC_DRV_TWL92330 241 boolean "TI TWL92330/Menelaus" 242 depends on MENELAUS 243 help 244 If you say yes here you get support for the RTC on the 245 TWL92330 "Menelaus" power management chip, used with OMAP2 246 platforms. The support is integrated with the rest of 247 the Menelaus driver; it's not separate module. 248 249config RTC_DRV_S35390A 250 tristate "Seiko Instruments S-35390A" 251 select BITREVERSE 252 help 253 If you say yes here you will get support for the Seiko 254 Instruments S-35390A. 255 256 This driver can also be built as a module. If so the module 257 will be called rtc-s35390a. 258 259endif # I2C 260 261comment "SPI RTC drivers" 262 263if SPI_MASTER 264 265config RTC_DRV_MAX6902 266 tristate "Maxim MAX6902" 267 help 268 If you say yes here you will get support for the 269 Maxim MAX6902 SPI RTC chip. 270 271 This driver can also be built as a module. If so, the module 272 will be called rtc-max6902. 273 274config RTC_DRV_R9701 275 tristate "Epson RTC-9701JE" 276 help 277 If you say yes here you will get support for the 278 Epson RTC-9701JE SPI RTC chip. 279 280 This driver can also be built as a module. If so, the module 281 will be called rtc-r9701. 282 283config RTC_DRV_RS5C348 284 tristate "Ricoh RS5C348A/B" 285 help 286 If you say yes here you get support for the 287 Ricoh RS5C348A and RS5C348B RTC chips. 288 289 This driver can also be built as a module. If so, the module 290 will be called rtc-rs5c348. 291 292endif # SPI_MASTER 293 294comment "Platform RTC drivers" 295 296# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> 297# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a 298# global rtc_lock ... it's not yet just another platform_device. 299 300config RTC_DRV_CMOS 301 tristate "PC-style 'CMOS'" 302 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS 303 default y if X86 304 help 305 Say "yes" here to get direct support for the real time clock 306 found in every PC or ACPI-based system, and some other boards. 307 Specifically the original MC146818, compatibles like those in 308 PC south bridges, the DS12887 or M48T86, some multifunction 309 or LPC bus chips, and so on. 310 311 Your system will need to define the platform device used by 312 this driver, otherwise it won't be accessible. This means 313 you can safely enable this driver if you don't know whether 314 or not your board has this kind of hardware. 315 316 This driver can also be built as a module. If so, the module 317 will be called rtc-cmos. 318 319config RTC_DRV_DS1216 320 tristate "Dallas DS1216" 321 depends on SNI_RM 322 help 323 If you say yes here you get support for the Dallas DS1216 RTC chips. 324 325config RTC_DRV_DS1302 326 tristate "Dallas DS1302" 327 depends on SH_SECUREEDGE5410 328 help 329 If you say yes here you get support for the Dallas DS1302 RTC chips. 330 331config RTC_DRV_DS1511 332 tristate "Dallas DS1511" 333 depends on RTC_CLASS 334 help 335 If you say yes here you get support for the 336 Dallas DS1511 timekeeping/watchdog chip. 337 338 This driver can also be built as a module. If so, the module 339 will be called rtc-ds1511. 340 341config RTC_DRV_DS1553 342 tristate "Maxim/Dallas DS1553" 343 help 344 If you say yes here you get support for the 345 Maxim/Dallas DS1553 timekeeping chip. 346 347 This driver can also be built as a module. If so, the module 348 will be called rtc-ds1553. 349 350config RTC_DRV_DS1742 351 tristate "Maxim/Dallas DS1742/1743" 352 help 353 If you say yes here you get support for the 354 Maxim/Dallas DS1742/1743 timekeeping chip. 355 356 This driver can also be built as a module. If so, the module 357 will be called rtc-ds1742. 358 359config RTC_DRV_STK17TA8 360 tristate "Simtek STK17TA8" 361 depends on RTC_CLASS 362 help 363 If you say yes here you get support for the 364 Simtek STK17TA8 timekeeping chip. 365 366 This driver can also be built as a module. If so, the module 367 will be called rtc-stk17ta8. 368 369config RTC_DRV_M48T86 370 tristate "ST M48T86/Dallas DS12887" 371 help 372 If you say Y here you will get support for the 373 ST M48T86 and Dallas DS12887 RTC chips. 374 375 This driver can also be built as a module. If so, the module 376 will be called rtc-m48t86. 377 378config RTC_DRV_M48T59 379 tristate "ST M48T59" 380 help 381 If you say Y here you will get support for the 382 ST M48T59 RTC chip. 383 384 This driver can also be built as a module, if so, the module 385 will be called "rtc-m48t59". 386 387config RTC_DRV_V3020 388 tristate "EM Microelectronic V3020" 389 help 390 If you say yes here you will get support for the 391 EM Microelectronic v3020 RTC chip. 392 393 This driver can also be built as a module. If so, the module 394 will be called rtc-v3020. 395 396comment "on-CPU RTC drivers" 397 398config RTC_DRV_OMAP 399 tristate "TI OMAP1" 400 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 401 help 402 Say "yes" here to support the real time clock on TI OMAP1 chips. 403 This driver can also be built as a module called rtc-omap. 404 405config RTC_DRV_S3C 406 tristate "Samsung S3C series SoC RTC" 407 depends on ARCH_S3C2410 408 help 409 RTC (Realtime Clock) driver for the clock inbuilt into the 410 Samsung S3C24XX series of SoCs. This can provide periodic 411 interrupt rates from 1Hz to 64Hz for user programs, and 412 wakeup from Alarm. 413 414 The driver currently supports the common features on all the 415 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 416 and S3C2442. 417 418 This driver can also be build as a module. If so, the module 419 will be called rtc-s3c. 420 421config RTC_DRV_EP93XX 422 tristate "Cirrus Logic EP93XX" 423 depends on ARCH_EP93XX 424 help 425 If you say yes here you get support for the 426 RTC embedded in the Cirrus Logic EP93XX processors. 427 428 This driver can also be built as a module. If so, the module 429 will be called rtc-ep93xx. 430 431config RTC_DRV_SA1100 432 tristate "SA11x0/PXA2xx" 433 depends on ARCH_SA1100 || ARCH_PXA 434 help 435 If you say Y here you will get access to the real time clock 436 built into your SA11x0 or PXA2xx CPU. 437 438 To compile this driver as a module, choose M here: the 439 module will be called rtc-sa1100. 440 441config RTC_DRV_SH 442 tristate "SuperH On-Chip RTC" 443 depends on RTC_CLASS && SUPERH 444 help 445 Say Y here to enable support for the on-chip RTC found in 446 most SuperH processors. 447 448 To compile this driver as a module, choose M here: the 449 module will be called rtc-sh. 450 451config RTC_DRV_VR41XX 452 tristate "NEC VR41XX" 453 depends on CPU_VR41XX 454 help 455 If you say Y here you will get access to the real time clock 456 built into your NEC VR41XX CPU. 457 458 To compile this driver as a module, choose M here: the 459 module will be called rtc-vr41xx. 460 461config RTC_DRV_PL031 462 tristate "ARM AMBA PL031 RTC" 463 depends on ARM_AMBA 464 help 465 If you say Y here you will get access to ARM AMBA 466 PrimeCell PL031 RTC found on certain ARM SOCs. 467 468 To compile this driver as a module, choose M here: the 469 module will be called rtc-pl031. 470 471config RTC_DRV_AT32AP700X 472 tristate "AT32AP700X series RTC" 473 depends on PLATFORM_AT32AP 474 help 475 Driver for the internal RTC (Realtime Clock) on Atmel AVR32 476 AT32AP700x family processors. 477 478config RTC_DRV_AT91RM9200 479 tristate "AT91RM9200 or AT91SAM9RL" 480 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL 481 help 482 Driver for the internal RTC (Realtime Clock) module found on 483 Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips 484 this is powered by the backup power supply. 485 486config RTC_DRV_AT91SAM9 487 tristate "AT91SAM9x" 488 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40) 489 help 490 RTC driver for the Atmel AT91SAM9x internal RTT (Real Time Timer). 491 These timers are powered by the backup power supply (such as a 492 small coin cell battery), but do not need to be used as RTCs. 493 494 (On AT91SAM9rl chips you probably want to use the dedicated RTC 495 module and leave the RTT available for other uses.) 496 497config RTC_DRV_AT91SAM9_RTT 498 int 499 range 0 1 500 default 0 501 prompt "RTT module Number" if ARCH_AT91SAM9263 502 depends on RTC_DRV_AT91SAM9 503 help 504 More than one RTT module is available. You can choose which 505 one will be used as an RTC. The default of zero is normally 506 OK to use, though some systems use that for non-RTC purposes. 507 508config RTC_DRV_AT91SAM9_GPBR 509 int 510 range 0 3 if !ARCH_AT91SAM9263 511 range 0 15 if ARCH_AT91SAM9263 512 default 0 513 prompt "Backup Register Number" 514 depends on RTC_DRV_AT91SAM9 515 help 516 The RTC driver needs to use one of the General Purpose Backup 517 Registers (GPBRs) as well as the RTT. You can choose which one 518 will be used. The default of zero is normally OK to use, but 519 on some systems other software needs to use that register. 520 521config RTC_DRV_BFIN 522 tristate "Blackfin On-Chip RTC" 523 depends on BLACKFIN 524 help 525 If you say yes here you will get support for the 526 Blackfin On-Chip Real Time Clock. 527 528 This driver can also be built as a module. If so, the module 529 will be called rtc-bfin. 530 531config RTC_DRV_RS5C313 532 tristate "Ricoh RS5C313" 533 depends on SH_LANDISK 534 help 535 If you say yes here you get support for the Ricoh RS5C313 RTC chips. 536 537config RTC_DRV_PPC 538 tristate "PowerPC machine dependent RTC support" 539 depends on PPC_MERGE 540 help 541 The PowerPC kernel has machine-specific functions for accessing 542 the RTC. This exposes that functionality through the generic RTC 543 class. 544 545endif # RTC_CLASS 546