1# 2# RTC class/drivers configuration 3# 4 5config RTC_LIB 6 bool 7 8menuconfig RTC_CLASS 9 bool "Real Time Clock" 10 default n 11 depends on !S390 && !UML 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 18if RTC_CLASS 19 20config RTC_HCTOSYS 21 bool "Set system time from RTC on startup and resume" 22 default y 23 help 24 If you say yes here, the system time (wall clock) will be set using 25 the value read from a specified RTC device. This is useful to avoid 26 unnecessary fsck runs at boot time, and to network better. 27 28config RTC_HCTOSYS_DEVICE 29 string "RTC used to set the system time" 30 depends on RTC_HCTOSYS = y 31 default "rtc0" 32 help 33 The RTC device that will be used to (re)initialize the system 34 clock, usually rtc0. Initialization is done when the system 35 starts up, and when it resumes from a low power state. This 36 device should record time in UTC, since the kernel won't do 37 timezone correction. 38 39 The driver for this RTC device must be loaded before late_initcall 40 functions run, so it must usually be statically linked. 41 42 This clock should be battery-backed, so that it reads the correct 43 time when the system boots from a power-off state. Otherwise, your 44 system will need an external clock source (like an NTP server). 45 46 If the clock you specify here is not battery backed, it may still 47 be useful to reinitialize system time when resuming from system 48 sleep states. Do not specify an RTC here unless it stays powered 49 during all this system's supported sleep states. 50 51config RTC_DEBUG 52 bool "RTC debug support" 53 help 54 Say yes here to enable debugging support in the RTC framework 55 and individual RTC drivers. 56 57comment "RTC interfaces" 58 59config RTC_INTF_SYSFS 60 boolean "/sys/class/rtc/rtcN (sysfs)" 61 depends on SYSFS 62 default RTC_CLASS 63 help 64 Say yes here if you want to use your RTCs using sysfs interfaces, 65 /sys/class/rtc/rtc0 through /sys/.../rtcN. 66 67 If unsure, say Y. 68 69config RTC_INTF_PROC 70 boolean "/proc/driver/rtc (procfs for rtcN)" 71 depends on PROC_FS 72 default RTC_CLASS 73 help 74 Say yes here if you want to use your system clock RTC through 75 the proc interface, /proc/driver/rtc. 76 Other RTCs will not be available through that API. 77 If there is no RTC for the system clock, then the first RTC(rtc0) 78 is used by default. 79 80 If unsure, say Y. 81 82config RTC_INTF_DEV 83 boolean "/dev/rtcN (character devices)" 84 default RTC_CLASS 85 help 86 Say yes here if you want to use your RTCs using the /dev 87 interfaces, which "udev" sets up as /dev/rtc0 through 88 /dev/rtcN. 89 90 You may want to set up a symbolic link so one of these 91 can be accessed as /dev/rtc, which is a name 92 expected by "hwclock" and some other programs. Recent 93 versions of "udev" are known to set up the symlink for you. 94 95 If unsure, say Y. 96 97config RTC_INTF_DEV_UIE_EMUL 98 bool "RTC UIE emulation on dev interface" 99 depends on RTC_INTF_DEV 100 help 101 Provides an emulation for RTC_UIE if the underlying rtc chip 102 driver does not expose RTC_UIE ioctls. Those requests generate 103 once-per-second update interrupts, used for synchronization. 104 105 The emulation code will read the time from the hardware 106 clock several times per second, please enable this option 107 only if you know that you really need it. 108 109config RTC_DRV_TEST 110 tristate "Test driver/device" 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 I2C 125 126if I2C 127 128config RTC_DRV_88PM860X 129 tristate "Marvell 88PM860x" 130 depends on I2C && MFD_88PM860X 131 help 132 If you say yes here you get support for RTC function in Marvell 133 88PM860x chips. 134 135 This driver can also be built as a module. If so, the module 136 will be called rtc-88pm860x. 137 138config RTC_DRV_88PM80X 139 tristate "Marvell 88PM80x" 140 depends on I2C && MFD_88PM800 141 help 142 If you say yes here you get support for RTC function in Marvell 143 88PM80x chips. 144 145 This driver can also be built as a module. If so, the module 146 will be called rtc-88pm80x. 147 148config RTC_DRV_DS1307 149 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025" 150 help 151 If you say yes here you get support for various compatible RTC 152 chips (often with battery backup) connected with I2C. This driver 153 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00, 154 EPSON RX-8025 and probably other chips. In some cases the RTC 155 must already have been initialized (by manufacturing or a 156 bootloader). 157 158 The first seven registers on these chips hold an RTC, and other 159 registers may add features such as NVRAM, a trickle charger for 160 the RTC/NVRAM backup power, and alarms. NVRAM is visible in 161 sysfs, but other chip features may not be available. 162 163 This driver can also be built as a module. If so, the module 164 will be called rtc-ds1307. 165 166config RTC_DRV_DS1374 167 tristate "Dallas/Maxim DS1374" 168 depends on I2C 169 help 170 If you say yes here you get support for Dallas Semiconductor 171 DS1374 real-time clock chips. If an interrupt is associated 172 with the device, the alarm functionality is supported. 173 174 This driver can also be built as a module. If so, the module 175 will be called rtc-ds1374. 176 177config RTC_DRV_DS1672 178 tristate "Dallas/Maxim DS1672" 179 help 180 If you say yes here you get support for the 181 Dallas/Maxim DS1672 timekeeping chip. 182 183 This driver can also be built as a module. If so, the module 184 will be called rtc-ds1672. 185 186config RTC_DRV_DS3232 187 tristate "Dallas/Maxim DS3232" 188 depends on I2C 189 help 190 If you say yes here you get support for Dallas Semiconductor 191 DS3232 real-time clock chips. If an interrupt is associated 192 with the device, the alarm functionality is supported. 193 194 This driver can also be built as a module. If so, the module 195 will be called rtc-ds3232. 196 197config RTC_DRV_MAX6900 198 tristate "Maxim MAX6900" 199 help 200 If you say yes here you will get support for the 201 Maxim MAX6900 I2C RTC chip. 202 203 This driver can also be built as a module. If so, the module 204 will be called rtc-max6900. 205 206config RTC_DRV_MAX8907 207 tristate "Maxim MAX8907" 208 depends on MFD_MAX8907 209 help 210 If you say yes here you will get support for the 211 RTC of Maxim MAX8907 PMIC. 212 213 This driver can also be built as a module. If so, the module 214 will be called rtc-max8907. 215 216config RTC_DRV_MAX8925 217 tristate "Maxim MAX8925" 218 depends on MFD_MAX8925 219 help 220 If you say yes here you will get support for the 221 RTC of Maxim MAX8925 PMIC. 222 223 This driver can also be built as a module. If so, the module 224 will be called rtc-max8925. 225 226config RTC_DRV_MAX8998 227 tristate "Maxim MAX8998" 228 depends on MFD_MAX8998 229 help 230 If you say yes here you will get support for the 231 RTC of Maxim MAX8998 PMIC. 232 233 This driver can also be built as a module. If so, the module 234 will be called rtc-max8998. 235 236config RTC_DRV_RS5C372 237 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A" 238 help 239 If you say yes here you get support for the 240 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. 241 242 This driver can also be built as a module. If so, the module 243 will be called rtc-rs5c372. 244 245config RTC_DRV_ISL1208 246 tristate "Intersil ISL1208" 247 help 248 If you say yes here you get support for the 249 Intersil ISL1208 RTC chip. 250 251 This driver can also be built as a module. If so, the module 252 will be called rtc-isl1208. 253 254config RTC_DRV_ISL12022 255 tristate "Intersil ISL12022" 256 help 257 If you say yes here you get support for the 258 Intersil ISL12022 RTC chip. 259 260 This driver can also be built as a module. If so, the module 261 will be called rtc-isl12022. 262 263config RTC_DRV_X1205 264 tristate "Xicor/Intersil X1205" 265 help 266 If you say yes here you get support for the 267 Xicor/Intersil X1205 RTC chip. 268 269 This driver can also be built as a module. If so, the module 270 will be called rtc-x1205. 271 272config RTC_DRV_PCF8523 273 tristate "NXP PCF8523" 274 help 275 If you say yes here you get support for the NXP PCF8523 RTC 276 chips. 277 278 This driver can also be built as a module. If so, the module 279 will be called rtc-pcf8523. 280 281config RTC_DRV_PCF8563 282 tristate "Philips PCF8563/Epson RTC8564" 283 help 284 If you say yes here you get support for the 285 Philips PCF8563 RTC chip. The Epson RTC8564 286 should work as well. 287 288 This driver can also be built as a module. If so, the module 289 will be called rtc-pcf8563. 290 291config RTC_DRV_PCF8583 292 tristate "Philips PCF8583" 293 help 294 If you say yes here you get support for the Philips PCF8583 295 RTC chip found on Acorn RiscPCs. This driver supports the 296 platform specific method of retrieving the current year from 297 the RTC's SRAM. It will work on other platforms with the same 298 chip, but the year will probably have to be tweaked. 299 300 This driver can also be built as a module. If so, the module 301 will be called rtc-pcf8583. 302 303config RTC_DRV_M41T80 304 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87" 305 help 306 If you say Y here you will get support for the ST M41T60 307 and M41T80 RTC chips series. Currently, the following chips are 308 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84, 309 M41ST85, and M41ST87. 310 311 This driver can also be built as a module. If so, the module 312 will be called rtc-m41t80. 313 314config RTC_DRV_M41T80_WDT 315 bool "ST M41T65/M41T80 series RTC watchdog timer" 316 depends on RTC_DRV_M41T80 317 help 318 If you say Y here you will get support for the 319 watchdog timer in the ST M41T60 and M41T80 RTC chips series. 320 321config RTC_DRV_BQ32K 322 tristate "TI BQ32000" 323 help 324 If you say Y here you will get support for the TI 325 BQ32000 I2C RTC chip. 326 327 This driver can also be built as a module. If so, the module 328 will be called rtc-bq32k. 329 330config RTC_DRV_DM355EVM 331 tristate "TI DaVinci DM355 EVM RTC" 332 depends on MFD_DM355EVM_MSP 333 help 334 Supports the RTC firmware in the MSP430 on the DM355 EVM. 335 336config RTC_DRV_TWL92330 337 boolean "TI TWL92330/Menelaus" 338 depends on MENELAUS 339 help 340 If you say yes here you get support for the RTC on the 341 TWL92330 "Menelaus" power management chip, used with OMAP2 342 platforms. The support is integrated with the rest of 343 the Menelaus driver; it's not separate module. 344 345config RTC_DRV_TWL4030 346 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0" 347 depends on TWL4030_CORE 348 help 349 If you say yes here you get support for the RTC on the 350 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms. 351 352 This driver can also be built as a module. If so, the module 353 will be called rtc-twl. 354 355config RTC_DRV_TPS6586X 356 tristate "TI TPS6586X RTC driver" 357 depends on MFD_TPS6586X 358 help 359 TI Power Managment IC TPS6586X supports RTC functionality 360 along with alarm. This driver supports the RTC driver for 361 the TPS6586X RTC module. 362 363config RTC_DRV_TPS65910 364 tristate "TI TPS65910 RTC driver" 365 depends on RTC_CLASS && MFD_TPS65910 366 help 367 If you say yes here you get support for the RTC on the 368 TPS65910 chips. 369 370 This driver can also be built as a module. If so, the module 371 will be called rtc-tps65910. 372 373config RTC_DRV_RC5T583 374 tristate "RICOH 5T583 RTC driver" 375 depends on MFD_RC5T583 376 help 377 If you say yes here you get support for the RTC on the 378 RICOH 5T583 chips. 379 380 This driver can also be built as a module. If so, the module 381 will be called rtc-rc5t583. 382 383config RTC_DRV_S35390A 384 tristate "Seiko Instruments S-35390A" 385 select BITREVERSE 386 help 387 If you say yes here you will get support for the Seiko 388 Instruments S-35390A. 389 390 This driver can also be built as a module. If so the module 391 will be called rtc-s35390a. 392 393config RTC_DRV_FM3130 394 tristate "Ramtron FM3130" 395 help 396 If you say Y here you will get support for the 397 Ramtron FM3130 RTC chips. 398 Ramtron FM3130 is a chip with two separate devices inside, 399 RTC clock and FRAM. This driver provides only RTC functionality. 400 401 This driver can also be built as a module. If so the module 402 will be called rtc-fm3130. 403 404config RTC_DRV_RX8581 405 tristate "Epson RX-8581" 406 help 407 If you say yes here you will get support for the Epson RX-8581. 408 409 This driver can also be built as a module. If so the module 410 will be called rtc-rx8581. 411 412config RTC_DRV_RX8025 413 tristate "Epson RX-8025SA/NB" 414 help 415 If you say yes here you get support for the Epson 416 RX-8025SA/NB RTC chips. 417 418 This driver can also be built as a module. If so, the module 419 will be called rtc-rx8025. 420 421config RTC_DRV_EM3027 422 tristate "EM Microelectronic EM3027" 423 help 424 If you say yes here you get support for the EM 425 Microelectronic EM3027 RTC chips. 426 427 This driver can also be built as a module. If so, the module 428 will be called rtc-em3027. 429 430config RTC_DRV_RV3029C2 431 tristate "Micro Crystal RTC" 432 help 433 If you say yes here you get support for the Micro Crystal 434 RV3029-C2 RTC chips. 435 436 This driver can also be built as a module. If so, the module 437 will be called rtc-rv3029c2. 438 439endif # I2C 440 441comment "SPI RTC drivers" 442 443if SPI_MASTER 444 445config RTC_DRV_M41T93 446 tristate "ST M41T93" 447 help 448 If you say yes here you will get support for the 449 ST M41T93 SPI RTC chip. 450 451 This driver can also be built as a module. If so, the module 452 will be called rtc-m41t93. 453 454config RTC_DRV_M41T94 455 tristate "ST M41T94" 456 help 457 If you say yes here you will get support for the 458 ST M41T94 SPI RTC chip. 459 460 This driver can also be built as a module. If so, the module 461 will be called rtc-m41t94. 462 463config RTC_DRV_DS1305 464 tristate "Dallas/Maxim DS1305/DS1306" 465 help 466 Select this driver to get support for the Dallas/Maxim DS1305 467 and DS1306 real time clock chips. These support a trickle 468 charger, alarms, and NVRAM in addition to the clock. 469 470 This driver can also be built as a module. If so, the module 471 will be called rtc-ds1305. 472 473config RTC_DRV_DS1390 474 tristate "Dallas/Maxim DS1390/93/94" 475 help 476 If you say yes here you get support for the 477 Dallas/Maxim DS1390/93/94 chips. 478 479 This driver only supports the RTC feature, and not other chip 480 features such as alarms and trickle charging. 481 482 This driver can also be built as a module. If so, the module 483 will be called rtc-ds1390. 484 485config RTC_DRV_MAX6902 486 tristate "Maxim MAX6902" 487 help 488 If you say yes here you will get support for the 489 Maxim MAX6902 SPI RTC chip. 490 491 This driver can also be built as a module. If so, the module 492 will be called rtc-max6902. 493 494config RTC_DRV_R9701 495 tristate "Epson RTC-9701JE" 496 help 497 If you say yes here you will get support for the 498 Epson RTC-9701JE SPI RTC chip. 499 500 This driver can also be built as a module. If so, the module 501 will be called rtc-r9701. 502 503config RTC_DRV_RS5C348 504 tristate "Ricoh RS5C348A/B" 505 help 506 If you say yes here you get support for the 507 Ricoh RS5C348A and RS5C348B RTC chips. 508 509 This driver can also be built as a module. If so, the module 510 will be called rtc-rs5c348. 511 512config RTC_DRV_DS3234 513 tristate "Maxim/Dallas DS3234" 514 help 515 If you say yes here you get support for the 516 Maxim/Dallas DS3234 SPI RTC chip. 517 518 This driver can also be built as a module. If so, the module 519 will be called rtc-ds3234. 520 521config RTC_DRV_PCF2123 522 tristate "NXP PCF2123" 523 help 524 If you say yes here you get support for the NXP PCF2123 525 RTC chip. 526 527 This driver can also be built as a module. If so, the module 528 will be called rtc-pcf2123. 529 530endif # SPI_MASTER 531 532comment "Platform RTC drivers" 533 534# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> 535# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a 536# global rtc_lock ... it's not yet just another platform_device. 537 538config RTC_DRV_CMOS 539 tristate "PC-style 'CMOS'" 540 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64 541 default y if X86 542 help 543 Say "yes" here to get direct support for the real time clock 544 found in every PC or ACPI-based system, and some other boards. 545 Specifically the original MC146818, compatibles like those in 546 PC south bridges, the DS12887 or M48T86, some multifunction 547 or LPC bus chips, and so on. 548 549 Your system will need to define the platform device used by 550 this driver, otherwise it won't be accessible. This means 551 you can safely enable this driver if you don't know whether 552 or not your board has this kind of hardware. 553 554 This driver can also be built as a module. If so, the module 555 will be called rtc-cmos. 556 557config RTC_DRV_VRTC 558 tristate "Virtual RTC for Intel MID platforms" 559 depends on X86_INTEL_MID 560 default y if X86_INTEL_MID 561 562 help 563 Say "yes" here to get direct support for the real time clock 564 found on Moorestown platforms. The VRTC is a emulated RTC that 565 derives its clock source from a real RTC in the PMIC. The MC146818 566 style programming interface is mostly conserved, but any 567 updates are done via IPC calls to the system controller FW. 568 569config RTC_DRV_DS1216 570 tristate "Dallas DS1216" 571 depends on SNI_RM 572 help 573 If you say yes here you get support for the Dallas DS1216 RTC chips. 574 575config RTC_DRV_DS1286 576 tristate "Dallas DS1286" 577 help 578 If you say yes here you get support for the Dallas DS1286 RTC chips. 579 580config RTC_DRV_DS1302 581 tristate "Dallas DS1302" 582 depends on SH_SECUREEDGE5410 583 help 584 If you say yes here you get support for the Dallas DS1302 RTC chips. 585 586config RTC_DRV_DS1511 587 tristate "Dallas DS1511" 588 help 589 If you say yes here you get support for the 590 Dallas DS1511 timekeeping/watchdog chip. 591 592 This driver can also be built as a module. If so, the module 593 will be called rtc-ds1511. 594 595config RTC_DRV_DS1553 596 tristate "Maxim/Dallas DS1553" 597 help 598 If you say yes here you get support for the 599 Maxim/Dallas DS1553 timekeeping chip. 600 601 This driver can also be built as a module. If so, the module 602 will be called rtc-ds1553. 603 604config RTC_DRV_DS1742 605 tristate "Maxim/Dallas DS1742/1743" 606 help 607 If you say yes here you get support for the 608 Maxim/Dallas DS1742/1743 timekeeping chip. 609 610 This driver can also be built as a module. If so, the module 611 will be called rtc-ds1742. 612 613config RTC_DRV_DA9052 614 tristate "Dialog DA9052/DA9053 RTC" 615 depends on PMIC_DA9052 616 help 617 Say y here to support the RTC driver for Dialog Semiconductor 618 DA9052-BC and DA9053-AA/Bx PMICs. 619 620config RTC_DRV_DA9055 621 tristate "Dialog Semiconductor DA9055 RTC" 622 depends on MFD_DA9055 623 help 624 If you say yes here you will get support for the 625 RTC of the Dialog DA9055 PMIC. 626 627 This driver can also be built as a module. If so, the module 628 will be called rtc-da9055 629 630config RTC_DRV_EFI 631 tristate "EFI RTC" 632 depends on IA64 633 help 634 If you say yes here you will get support for the EFI 635 Real Time Clock. 636 637 This driver can also be built as a module. If so, the module 638 will be called rtc-efi. 639 640config RTC_DRV_STK17TA8 641 tristate "Simtek STK17TA8" 642 help 643 If you say yes here you get support for the 644 Simtek STK17TA8 timekeeping chip. 645 646 This driver can also be built as a module. If so, the module 647 will be called rtc-stk17ta8. 648 649config RTC_DRV_M48T86 650 tristate "ST M48T86/Dallas DS12887" 651 help 652 If you say Y here you will get support for the 653 ST M48T86 and Dallas DS12887 RTC chips. 654 655 This driver can also be built as a module. If so, the module 656 will be called rtc-m48t86. 657 658config RTC_DRV_M48T35 659 tristate "ST M48T35" 660 help 661 If you say Y here you will get support for the 662 ST M48T35 RTC chip. 663 664 This driver can also be built as a module, if so, the module 665 will be called "rtc-m48t35". 666 667config RTC_DRV_M48T59 668 tristate "ST M48T59/M48T08/M48T02" 669 help 670 If you say Y here you will get support for the 671 ST M48T59 RTC chip and compatible ST M48T08 and M48T02. 672 673 These chips are usually found in Sun SPARC and UltraSPARC 674 workstations. 675 676 This driver can also be built as a module, if so, the module 677 will be called "rtc-m48t59". 678 679config RTC_DRV_MSM6242 680 tristate "Oki MSM6242" 681 help 682 If you say yes here you get support for the Oki MSM6242 683 timekeeping chip. It is used in some Amiga models (e.g. A2000). 684 685 This driver can also be built as a module. If so, the module 686 will be called rtc-msm6242. 687 688config RTC_DRV_BQ4802 689 tristate "TI BQ4802" 690 help 691 If you say Y here you will get support for the TI 692 BQ4802 RTC chip. 693 694 This driver can also be built as a module. If so, the module 695 will be called rtc-bq4802. 696 697config RTC_DRV_RP5C01 698 tristate "Ricoh RP5C01" 699 help 700 If you say yes here you get support for the Ricoh RP5C01 701 timekeeping chip. It is used in some Amiga models (e.g. A3000 702 and A4000). 703 704 This driver can also be built as a module. If so, the module 705 will be called rtc-rp5c01. 706 707config RTC_DRV_V3020 708 tristate "EM Microelectronic V3020" 709 help 710 If you say yes here you will get support for the 711 EM Microelectronic v3020 RTC chip. 712 713 This driver can also be built as a module. If so, the module 714 will be called rtc-v3020. 715 716config RTC_DRV_DS2404 717 tristate "Dallas DS2404" 718 help 719 If you say yes here you get support for the 720 Dallas DS2404 RTC chip. 721 722 This driver can also be built as a module. If so, the module 723 will be called rtc-ds2404. 724 725config RTC_DRV_WM831X 726 tristate "Wolfson Microelectronics WM831x RTC" 727 depends on MFD_WM831X 728 help 729 If you say yes here you will get support for the RTC subsystem 730 of the Wolfson Microelectronics WM831X series PMICs. 731 732 This driver can also be built as a module. If so, the module 733 will be called "rtc-wm831x". 734 735config RTC_DRV_WM8350 736 tristate "Wolfson Microelectronics WM8350 RTC" 737 depends on MFD_WM8350 738 help 739 If you say yes here you will get support for the RTC subsystem 740 of the Wolfson Microelectronics WM8350. 741 742 This driver can also be built as a module. If so, the module 743 will be called "rtc-wm8350". 744 745config RTC_DRV_SPEAR 746 tristate "SPEAR ST RTC" 747 depends on PLAT_SPEAR 748 default y 749 help 750 If you say Y here you will get support for the RTC found on 751 spear 752 753config RTC_DRV_PCF50633 754 depends on MFD_PCF50633 755 tristate "NXP PCF50633 RTC" 756 help 757 If you say yes here you get support for the RTC subsystem of the 758 NXP PCF50633 used in embedded systems. 759 760config RTC_DRV_AB3100 761 tristate "ST-Ericsson AB3100 RTC" 762 depends on AB3100_CORE 763 default y if AB3100_CORE 764 help 765 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC 766 support. This chip contains a battery- and capacitor-backed RTC. 767 768config RTC_DRV_AB8500 769 tristate "ST-Ericsson AB8500 RTC" 770 depends on AB8500_CORE 771 select RTC_INTF_DEV 772 select RTC_INTF_DEV_UIE_EMUL 773 help 774 Select this to enable the ST-Ericsson AB8500 power management IC RTC 775 support. This chip contains a battery- and capacitor-backed RTC. 776 777config RTC_DRV_NUC900 778 tristate "NUC910/NUC920 RTC driver" 779 depends on ARCH_W90X900 780 help 781 If you say yes here you get support for the RTC subsystem of the 782 NUC910/NUC920 used in embedded systems. 783 784comment "on-CPU RTC drivers" 785 786config RTC_DRV_DAVINCI 787 tristate "TI DaVinci RTC" 788 depends on ARCH_DAVINCI_DM365 789 help 790 If you say yes here you get support for the RTC on the 791 DaVinci platforms (DM365). 792 793 This driver can also be built as a module. If so, the module 794 will be called rtc-davinci. 795 796config RTC_DRV_IMXDI 797 tristate "Freescale IMX DryIce Real Time Clock" 798 depends on ARCH_MXC 799 help 800 Support for Freescale IMX DryIce RTC 801 802 This driver can also be built as a module, if so, the module 803 will be called "rtc-imxdi". 804 805config RTC_DRV_OMAP 806 tristate "TI OMAP1" 807 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX 808 help 809 Say "yes" here to support the on chip real time clock 810 present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x. 811 812 This driver can also be built as a module, if so, module 813 will be called rtc-omap. 814 815config HAVE_S3C_RTC 816 bool 817 help 818 This will include RTC support for Samsung SoCs. If 819 you want to include RTC support for any machine, kindly 820 select this in the respective mach-XXXX/Kconfig file. 821 822config RTC_DRV_S3C 823 tristate "Samsung S3C series SoC RTC" 824 depends on ARCH_S3C64XX || HAVE_S3C_RTC 825 help 826 RTC (Realtime Clock) driver for the clock inbuilt into the 827 Samsung S3C24XX series of SoCs. This can provide periodic 828 interrupt rates from 1Hz to 64Hz for user programs, and 829 wakeup from Alarm. 830 831 The driver currently supports the common features on all the 832 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 833 and S3C2442. 834 835 This driver can also be build as a module. If so, the module 836 will be called rtc-s3c. 837 838config RTC_DRV_EP93XX 839 tristate "Cirrus Logic EP93XX" 840 depends on ARCH_EP93XX 841 help 842 If you say yes here you get support for the 843 RTC embedded in the Cirrus Logic EP93XX processors. 844 845 This driver can also be built as a module. If so, the module 846 will be called rtc-ep93xx. 847 848config RTC_DRV_SA1100 849 tristate "SA11x0/PXA2xx/PXA910" 850 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP 851 help 852 If you say Y here you will get access to the real time clock 853 built into your SA11x0 or PXA2xx CPU. 854 855 To compile this driver as a module, choose M here: the 856 module will be called rtc-sa1100. 857 858config RTC_DRV_SH 859 tristate "SuperH On-Chip RTC" 860 depends on SUPERH && HAVE_CLK 861 help 862 Say Y here to enable support for the on-chip RTC found in 863 most SuperH processors. 864 865 To compile this driver as a module, choose M here: the 866 module will be called rtc-sh. 867 868config RTC_DRV_VR41XX 869 tristate "NEC VR41XX" 870 depends on CPU_VR41XX 871 help 872 If you say Y here you will get access to the real time clock 873 built into your NEC VR41XX CPU. 874 875 To compile this driver as a module, choose M here: the 876 module will be called rtc-vr41xx. 877 878config RTC_DRV_PL030 879 tristate "ARM AMBA PL030 RTC" 880 depends on ARM_AMBA 881 help 882 If you say Y here you will get access to ARM AMBA 883 PrimeCell PL030 RTC found on certain ARM SOCs. 884 885 To compile this driver as a module, choose M here: the 886 module will be called rtc-pl030. 887 888config RTC_DRV_PL031 889 tristate "ARM AMBA PL031 RTC" 890 depends on ARM_AMBA 891 help 892 If you say Y here you will get access to ARM AMBA 893 PrimeCell PL031 RTC found on certain ARM SOCs. 894 895 To compile this driver as a module, choose M here: the 896 module will be called rtc-pl031. 897 898config RTC_DRV_AT32AP700X 899 tristate "AT32AP700X series RTC" 900 depends on PLATFORM_AT32AP 901 help 902 Driver for the internal RTC (Realtime Clock) on Atmel AVR32 903 AT32AP700x family processors. 904 905config RTC_DRV_AT91RM9200 906 tristate "AT91RM9200 or some AT91SAM9 RTC" 907 depends on ARCH_AT91 908 help 909 Driver for the internal RTC (Realtime Clock) module found on 910 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips 911 this is powered by the backup power supply. 912 913config RTC_DRV_AT91SAM9 914 tristate "AT91SAM9x/AT91CAP9 RTT as RTC" 915 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40) 916 help 917 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT 918 (Real Time Timer). These timers are powered by the backup power 919 supply (such as a small coin cell battery), but do not need to 920 be used as RTCs. 921 922 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the 923 dedicated RTC module and leave the RTT available for other uses.) 924 925config RTC_DRV_AT91SAM9_RTT 926 int 927 range 0 1 928 default 0 929 prompt "RTT module Number" if ARCH_AT91SAM9263 930 depends on RTC_DRV_AT91SAM9 931 help 932 More than one RTT module is available. You can choose which 933 one will be used as an RTC. The default of zero is normally 934 OK to use, though some systems use that for non-RTC purposes. 935 936config RTC_DRV_AT91SAM9_GPBR 937 int 938 range 0 3 if !ARCH_AT91SAM9263 939 range 0 15 if ARCH_AT91SAM9263 940 default 0 941 prompt "Backup Register Number" 942 depends on RTC_DRV_AT91SAM9 943 help 944 The RTC driver needs to use one of the General Purpose Backup 945 Registers (GPBRs) as well as the RTT. You can choose which one 946 will be used. The default of zero is normally OK to use, but 947 on some systems other software needs to use that register. 948 949config RTC_DRV_AU1XXX 950 tristate "Au1xxx Counter0 RTC support" 951 depends on MIPS_ALCHEMY 952 help 953 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year 954 counter) to be used as a RTC. 955 956 This driver can also be built as a module. If so, the module 957 will be called rtc-au1xxx. 958 959config RTC_DRV_BFIN 960 tristate "Blackfin On-Chip RTC" 961 depends on BLACKFIN && !BF561 962 help 963 If you say yes here you will get support for the 964 Blackfin On-Chip Real Time Clock. 965 966 This driver can also be built as a module. If so, the module 967 will be called rtc-bfin. 968 969config RTC_DRV_RS5C313 970 tristate "Ricoh RS5C313" 971 depends on SH_LANDISK 972 help 973 If you say yes here you get support for the Ricoh RS5C313 RTC chips. 974 975config RTC_DRV_GENERIC 976 tristate "Generic RTC support" 977 # Please consider writing a new RTC driver instead of using the generic 978 # RTC abstraction 979 depends on PARISC || M68K || PPC || SUPERH32 980 help 981 Say Y or M here to enable RTC support on systems using the generic 982 RTC abstraction. If you do not know what you are doing, you should 983 just say Y. 984 985config RTC_DRV_PXA 986 tristate "PXA27x/PXA3xx" 987 depends on ARCH_PXA 988 help 989 If you say Y here you will get access to the real time clock 990 built into your PXA27x or PXA3xx CPU. 991 992 This RTC driver uses PXA RTC registers available since pxa27x 993 series (RDxR, RYxR) instead of legacy RCNR, RTAR. 994 995config RTC_DRV_VT8500 996 tristate "VIA/WonderMedia 85xx SoC RTC" 997 depends on ARCH_VT8500 998 help 999 If you say Y here you will get access to the real time clock 1000 built into your VIA VT8500 SoC or its relatives. 1001 1002 1003config RTC_DRV_SUN4V 1004 bool "SUN4V Hypervisor RTC" 1005 depends on SPARC64 1006 help 1007 If you say Y here you will get support for the Hypervisor 1008 based RTC on SUN4V systems. 1009 1010config RTC_DRV_STARFIRE 1011 bool "Starfire RTC" 1012 depends on SPARC64 1013 help 1014 If you say Y here you will get support for the RTC found on 1015 Starfire systems. 1016 1017config RTC_DRV_TX4939 1018 tristate "TX4939 SoC" 1019 depends on SOC_TX4939 1020 help 1021 Driver for the internal RTC (Realtime Clock) module found on 1022 Toshiba TX4939 SoC. 1023 1024config RTC_DRV_MV 1025 tristate "Marvell SoC RTC" 1026 depends on ARCH_KIRKWOOD || ARCH_DOVE 1027 help 1028 If you say yes here you will get support for the in-chip RTC 1029 that can be found in some of Marvell's SoC devices, such as 1030 the Kirkwood 88F6281 and 88F6192. 1031 1032 This driver can also be built as a module. If so, the module 1033 will be called rtc-mv. 1034 1035config RTC_DRV_PS3 1036 tristate "PS3 RTC" 1037 depends on PPC_PS3 1038 help 1039 If you say yes here you will get support for the RTC on PS3. 1040 1041 This driver can also be built as a module. If so, the module 1042 will be called rtc-ps3. 1043 1044config RTC_DRV_COH901331 1045 tristate "ST-Ericsson COH 901 331 RTC" 1046 depends on ARCH_U300 1047 help 1048 If you say Y here you will get access to ST-Ericsson 1049 COH 901 331 RTC clock found in some ST-Ericsson Mobile 1050 Platforms. 1051 1052 This driver can also be built as a module. If so, the module 1053 will be called "rtc-coh901331". 1054 1055 1056config RTC_DRV_STMP 1057 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC" 1058 depends on ARCH_MXS 1059 help 1060 If you say yes here you will get support for the onboard 1061 STMP3xxx/i.MX23/i.MX28 RTC. 1062 1063 This driver can also be built as a module. If so, the module 1064 will be called rtc-stmp3xxx. 1065 1066config RTC_DRV_PCAP 1067 tristate "PCAP RTC" 1068 depends on EZX_PCAP 1069 help 1070 If you say Y here you will get support for the RTC found on 1071 the PCAP2 ASIC used on some Motorola phones. 1072 1073config RTC_DRV_MC13XXX 1074 depends on MFD_MC13XXX 1075 tristate "Freescale MC13xxx RTC" 1076 help 1077 This enables support for the RTCs found on Freescale's PMICs 1078 MC13783 and MC13892. 1079 1080config RTC_DRV_MPC5121 1081 tristate "Freescale MPC5121 built-in RTC" 1082 depends on PPC_MPC512x || PPC_MPC52xx 1083 help 1084 If you say yes here you will get support for the 1085 built-in RTC on MPC5121 or on MPC5200. 1086 1087 This driver can also be built as a module. If so, the module 1088 will be called rtc-mpc5121. 1089 1090config RTC_DRV_JZ4740 1091 tristate "Ingenic JZ4740 SoC" 1092 depends on MACH_JZ4740 1093 help 1094 If you say yes here you get support for the Ingenic JZ4740 SoC RTC 1095 controller. 1096 1097 This driver can also be buillt as a module. If so, the module 1098 will be called rtc-jz4740. 1099 1100config RTC_DRV_LPC32XX 1101 depends on ARCH_LPC32XX 1102 tristate "NXP LPC32XX RTC" 1103 help 1104 This enables support for the NXP RTC in the LPC32XX 1105 1106 This driver can also be buillt as a module. If so, the module 1107 will be called rtc-lpc32xx. 1108 1109config RTC_DRV_PM8XXX 1110 tristate "Qualcomm PMIC8XXX RTC" 1111 depends on MFD_PM8XXX 1112 help 1113 If you say yes here you get support for the 1114 Qualcomm PMIC8XXX RTC. 1115 1116 To compile this driver as a module, choose M here: the 1117 module will be called rtc-pm8xxx. 1118 1119config RTC_DRV_TEGRA 1120 tristate "NVIDIA Tegra Internal RTC driver" 1121 depends on ARCH_TEGRA 1122 help 1123 If you say yes here you get support for the 1124 Tegra 200 series internal RTC module. 1125 1126 This drive can also be built as a module. If so, the module 1127 will be called rtc-tegra. 1128 1129config RTC_DRV_TILE 1130 tristate "Tilera hypervisor RTC support" 1131 depends on TILE 1132 help 1133 Enable support for the Linux driver side of the Tilera 1134 hypervisor's real-time clock interface. 1135 1136config RTC_DRV_PUV3 1137 tristate "PKUnity v3 RTC support" 1138 depends on ARCH_PUV3 1139 help 1140 This enables support for the RTC in the PKUnity-v3 SoCs. 1141 1142 This drive can also be built as a module. If so, the module 1143 will be called rtc-puv3. 1144 1145config RTC_DRV_LOONGSON1 1146 tristate "loongson1 RTC support" 1147 depends on MACH_LOONGSON1 1148 help 1149 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year 1150 counter) to be used as a RTC. 1151 1152 This driver can also be built as a module. If so, the module 1153 will be called rtc-ls1x. 1154 1155config RTC_DRV_MXC 1156 tristate "Freescale MXC Real Time Clock" 1157 depends on ARCH_MXC 1158 help 1159 If you say yes here you get support for the Freescale MXC 1160 RTC module. 1161 1162 This driver can also be built as a module, if so, the module 1163 will be called "rtc-mxc". 1164 1165config RTC_DRV_SNVS 1166 tristate "Freescale SNVS RTC support" 1167 depends on HAS_IOMEM 1168 depends on OF 1169 help 1170 If you say yes here you get support for the Freescale SNVS 1171 Low Power (LP) RTC module. 1172 1173 This driver can also be built as a module, if so, the module 1174 will be called "rtc-snvs". 1175 1176endif # RTC_CLASS 1177