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_PCF8563 273 tristate "Philips PCF8563/Epson RTC8564" 274 help 275 If you say yes here you get support for the 276 Philips PCF8563 RTC chip. The Epson RTC8564 277 should work as well. 278 279 This driver can also be built as a module. If so, the module 280 will be called rtc-pcf8563. 281 282config RTC_DRV_PCF8583 283 tristate "Philips PCF8583" 284 help 285 If you say yes here you get support for the Philips PCF8583 286 RTC chip found on Acorn RiscPCs. This driver supports the 287 platform specific method of retrieving the current year from 288 the RTC's SRAM. It will work on other platforms with the same 289 chip, but the year will probably have to be tweaked. 290 291 This driver can also be built as a module. If so, the module 292 will be called rtc-pcf8583. 293 294config RTC_DRV_M41T80 295 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87" 296 help 297 If you say Y here you will get support for the ST M41T60 298 and M41T80 RTC chips series. Currently, the following chips are 299 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84, 300 M41ST85, and M41ST87. 301 302 This driver can also be built as a module. If so, the module 303 will be called rtc-m41t80. 304 305config RTC_DRV_M41T80_WDT 306 bool "ST M41T65/M41T80 series RTC watchdog timer" 307 depends on RTC_DRV_M41T80 308 help 309 If you say Y here you will get support for the 310 watchdog timer in the ST M41T60 and M41T80 RTC chips series. 311 312config RTC_DRV_BQ32K 313 tristate "TI BQ32000" 314 help 315 If you say Y here you will get support for the TI 316 BQ32000 I2C RTC chip. 317 318 This driver can also be built as a module. If so, the module 319 will be called rtc-bq32k. 320 321config RTC_DRV_DM355EVM 322 tristate "TI DaVinci DM355 EVM RTC" 323 depends on MFD_DM355EVM_MSP 324 help 325 Supports the RTC firmware in the MSP430 on the DM355 EVM. 326 327config RTC_DRV_TWL92330 328 boolean "TI TWL92330/Menelaus" 329 depends on MENELAUS 330 help 331 If you say yes here you get support for the RTC on the 332 TWL92330 "Menelaus" power management chip, used with OMAP2 333 platforms. The support is integrated with the rest of 334 the Menelaus driver; it's not separate module. 335 336config RTC_DRV_TWL4030 337 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0" 338 depends on TWL4030_CORE 339 help 340 If you say yes here you get support for the RTC on the 341 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms. 342 343 This driver can also be built as a module. If so, the module 344 will be called rtc-twl. 345 346config RTC_DRV_TPS65910 347 tristate "TI TPS65910 RTC driver" 348 depends on RTC_CLASS && MFD_TPS65910 349 help 350 If you say yes here you get support for the RTC on the 351 TPS65910 chips. 352 353 This driver can also be built as a module. If so, the module 354 will be called rtc-tps65910. 355 356config RTC_DRV_RC5T583 357 tristate "RICOH 5T583 RTC driver" 358 depends on MFD_RC5T583 359 help 360 If you say yes here you get support for the RTC on the 361 RICOH 5T583 chips. 362 363 This driver can also be built as a module. If so, the module 364 will be called rtc-rc5t583. 365 366config RTC_DRV_S35390A 367 tristate "Seiko Instruments S-35390A" 368 select BITREVERSE 369 help 370 If you say yes here you will get support for the Seiko 371 Instruments S-35390A. 372 373 This driver can also be built as a module. If so the module 374 will be called rtc-s35390a. 375 376config RTC_DRV_FM3130 377 tristate "Ramtron FM3130" 378 help 379 If you say Y here you will get support for the 380 Ramtron FM3130 RTC chips. 381 Ramtron FM3130 is a chip with two separate devices inside, 382 RTC clock and FRAM. This driver provides only RTC functionality. 383 384 This driver can also be built as a module. If so the module 385 will be called rtc-fm3130. 386 387config RTC_DRV_RX8581 388 tristate "Epson RX-8581" 389 help 390 If you say yes here you will get support for the Epson RX-8581. 391 392 This driver can also be built as a module. If so the module 393 will be called rtc-rx8581. 394 395config RTC_DRV_RX8025 396 tristate "Epson RX-8025SA/NB" 397 help 398 If you say yes here you get support for the Epson 399 RX-8025SA/NB RTC chips. 400 401 This driver can also be built as a module. If so, the module 402 will be called rtc-rx8025. 403 404config RTC_DRV_EM3027 405 tristate "EM Microelectronic EM3027" 406 help 407 If you say yes here you get support for the EM 408 Microelectronic EM3027 RTC chips. 409 410 This driver can also be built as a module. If so, the module 411 will be called rtc-em3027. 412 413config RTC_DRV_RV3029C2 414 tristate "Micro Crystal RTC" 415 help 416 If you say yes here you get support for the Micro Crystal 417 RV3029-C2 RTC chips. 418 419 This driver can also be built as a module. If so, the module 420 will be called rtc-rv3029c2. 421 422endif # I2C 423 424comment "SPI RTC drivers" 425 426if SPI_MASTER 427 428config RTC_DRV_M41T93 429 tristate "ST M41T93" 430 help 431 If you say yes here you will get support for the 432 ST M41T93 SPI RTC chip. 433 434 This driver can also be built as a module. If so, the module 435 will be called rtc-m41t93. 436 437config RTC_DRV_M41T94 438 tristate "ST M41T94" 439 help 440 If you say yes here you will get support for the 441 ST M41T94 SPI RTC chip. 442 443 This driver can also be built as a module. If so, the module 444 will be called rtc-m41t94. 445 446config RTC_DRV_DS1305 447 tristate "Dallas/Maxim DS1305/DS1306" 448 help 449 Select this driver to get support for the Dallas/Maxim DS1305 450 and DS1306 real time clock chips. These support a trickle 451 charger, alarms, and NVRAM in addition to the clock. 452 453 This driver can also be built as a module. If so, the module 454 will be called rtc-ds1305. 455 456config RTC_DRV_DS1390 457 tristate "Dallas/Maxim DS1390/93/94" 458 help 459 If you say yes here you get support for the 460 Dallas/Maxim DS1390/93/94 chips. 461 462 This driver only supports the RTC feature, and not other chip 463 features such as alarms and trickle charging. 464 465 This driver can also be built as a module. If so, the module 466 will be called rtc-ds1390. 467 468config RTC_DRV_MAX6902 469 tristate "Maxim MAX6902" 470 help 471 If you say yes here you will get support for the 472 Maxim MAX6902 SPI RTC chip. 473 474 This driver can also be built as a module. If so, the module 475 will be called rtc-max6902. 476 477config RTC_DRV_R9701 478 tristate "Epson RTC-9701JE" 479 help 480 If you say yes here you will get support for the 481 Epson RTC-9701JE SPI RTC chip. 482 483 This driver can also be built as a module. If so, the module 484 will be called rtc-r9701. 485 486config RTC_DRV_RS5C348 487 tristate "Ricoh RS5C348A/B" 488 help 489 If you say yes here you get support for the 490 Ricoh RS5C348A and RS5C348B RTC chips. 491 492 This driver can also be built as a module. If so, the module 493 will be called rtc-rs5c348. 494 495config RTC_DRV_DS3234 496 tristate "Maxim/Dallas DS3234" 497 help 498 If you say yes here you get support for the 499 Maxim/Dallas DS3234 SPI RTC chip. 500 501 This driver can also be built as a module. If so, the module 502 will be called rtc-ds3234. 503 504config RTC_DRV_PCF2123 505 tristate "NXP PCF2123" 506 help 507 If you say yes here you get support for the NXP PCF2123 508 RTC chip. 509 510 This driver can also be built as a module. If so, the module 511 will be called rtc-pcf2123. 512 513endif # SPI_MASTER 514 515comment "Platform RTC drivers" 516 517# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> 518# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a 519# global rtc_lock ... it's not yet just another platform_device. 520 521config RTC_DRV_CMOS 522 tristate "PC-style 'CMOS'" 523 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64 524 default y if X86 525 help 526 Say "yes" here to get direct support for the real time clock 527 found in every PC or ACPI-based system, and some other boards. 528 Specifically the original MC146818, compatibles like those in 529 PC south bridges, the DS12887 or M48T86, some multifunction 530 or LPC bus chips, and so on. 531 532 Your system will need to define the platform device used by 533 this driver, otherwise it won't be accessible. This means 534 you can safely enable this driver if you don't know whether 535 or not your board has this kind of hardware. 536 537 This driver can also be built as a module. If so, the module 538 will be called rtc-cmos. 539 540config RTC_DRV_VRTC 541 tristate "Virtual RTC for Intel MID platforms" 542 depends on X86_INTEL_MID 543 default y if X86_INTEL_MID 544 545 help 546 Say "yes" here to get direct support for the real time clock 547 found on Moorestown platforms. The VRTC is a emulated RTC that 548 derives its clock source from a real RTC in the PMIC. The MC146818 549 style programming interface is mostly conserved, but any 550 updates are done via IPC calls to the system controller FW. 551 552config RTC_DRV_DS1216 553 tristate "Dallas DS1216" 554 depends on SNI_RM 555 help 556 If you say yes here you get support for the Dallas DS1216 RTC chips. 557 558config RTC_DRV_DS1286 559 tristate "Dallas DS1286" 560 help 561 If you say yes here you get support for the Dallas DS1286 RTC chips. 562 563config RTC_DRV_DS1302 564 tristate "Dallas DS1302" 565 depends on SH_SECUREEDGE5410 566 help 567 If you say yes here you get support for the Dallas DS1302 RTC chips. 568 569config RTC_DRV_DS1511 570 tristate "Dallas DS1511" 571 help 572 If you say yes here you get support for the 573 Dallas DS1511 timekeeping/watchdog chip. 574 575 This driver can also be built as a module. If so, the module 576 will be called rtc-ds1511. 577 578config RTC_DRV_DS1553 579 tristate "Maxim/Dallas DS1553" 580 help 581 If you say yes here you get support for the 582 Maxim/Dallas DS1553 timekeeping chip. 583 584 This driver can also be built as a module. If so, the module 585 will be called rtc-ds1553. 586 587config RTC_DRV_DS1742 588 tristate "Maxim/Dallas DS1742/1743" 589 help 590 If you say yes here you get support for the 591 Maxim/Dallas DS1742/1743 timekeeping chip. 592 593 This driver can also be built as a module. If so, the module 594 will be called rtc-ds1742. 595 596config RTC_DRV_DA9052 597 tristate "Dialog DA9052/DA9053 RTC" 598 depends on PMIC_DA9052 599 help 600 Say y here to support the RTC driver for Dialog Semiconductor 601 DA9052-BC and DA9053-AA/Bx PMICs. 602 603config RTC_DRV_EFI 604 tristate "EFI RTC" 605 depends on IA64 606 help 607 If you say yes here you will get support for the EFI 608 Real Time Clock. 609 610 This driver can also be built as a module. If so, the module 611 will be called rtc-efi. 612 613config RTC_DRV_STK17TA8 614 tristate "Simtek STK17TA8" 615 help 616 If you say yes here you get support for the 617 Simtek STK17TA8 timekeeping chip. 618 619 This driver can also be built as a module. If so, the module 620 will be called rtc-stk17ta8. 621 622config RTC_DRV_M48T86 623 tristate "ST M48T86/Dallas DS12887" 624 help 625 If you say Y here you will get support for the 626 ST M48T86 and Dallas DS12887 RTC chips. 627 628 This driver can also be built as a module. If so, the module 629 will be called rtc-m48t86. 630 631config RTC_DRV_M48T35 632 tristate "ST M48T35" 633 help 634 If you say Y here you will get support for the 635 ST M48T35 RTC chip. 636 637 This driver can also be built as a module, if so, the module 638 will be called "rtc-m48t35". 639 640config RTC_DRV_M48T59 641 tristate "ST M48T59/M48T08/M48T02" 642 help 643 If you say Y here you will get support for the 644 ST M48T59 RTC chip and compatible ST M48T08 and M48T02. 645 646 These chips are usually found in Sun SPARC and UltraSPARC 647 workstations. 648 649 This driver can also be built as a module, if so, the module 650 will be called "rtc-m48t59". 651 652config RTC_DRV_MSM6242 653 tristate "Oki MSM6242" 654 help 655 If you say yes here you get support for the Oki MSM6242 656 timekeeping chip. It is used in some Amiga models (e.g. A2000). 657 658 This driver can also be built as a module. If so, the module 659 will be called rtc-msm6242. 660 661config RTC_DRV_BQ4802 662 tristate "TI BQ4802" 663 help 664 If you say Y here you will get support for the TI 665 BQ4802 RTC chip. 666 667 This driver can also be built as a module. If so, the module 668 will be called rtc-bq4802. 669 670config RTC_DRV_RP5C01 671 tristate "Ricoh RP5C01" 672 help 673 If you say yes here you get support for the Ricoh RP5C01 674 timekeeping chip. It is used in some Amiga models (e.g. A3000 675 and A4000). 676 677 This driver can also be built as a module. If so, the module 678 will be called rtc-rp5c01. 679 680config RTC_DRV_V3020 681 tristate "EM Microelectronic V3020" 682 help 683 If you say yes here you will get support for the 684 EM Microelectronic v3020 RTC chip. 685 686 This driver can also be built as a module. If so, the module 687 will be called rtc-v3020. 688 689config RTC_DRV_DS2404 690 tristate "Dallas DS2404" 691 help 692 If you say yes here you get support for the 693 Dallas DS2404 RTC chip. 694 695 This driver can also be built as a module. If so, the module 696 will be called rtc-ds2404. 697 698config RTC_DRV_WM831X 699 tristate "Wolfson Microelectronics WM831x RTC" 700 depends on MFD_WM831X 701 help 702 If you say yes here you will get support for the RTC subsystem 703 of the Wolfson Microelectronics WM831X series PMICs. 704 705 This driver can also be built as a module. If so, the module 706 will be called "rtc-wm831x". 707 708config RTC_DRV_WM8350 709 tristate "Wolfson Microelectronics WM8350 RTC" 710 depends on MFD_WM8350 711 help 712 If you say yes here you will get support for the RTC subsystem 713 of the Wolfson Microelectronics WM8350. 714 715 This driver can also be built as a module. If so, the module 716 will be called "rtc-wm8350". 717 718config RTC_DRV_SPEAR 719 tristate "SPEAR ST RTC" 720 depends on PLAT_SPEAR 721 default y 722 help 723 If you say Y here you will get support for the RTC found on 724 spear 725 726config RTC_DRV_PCF50633 727 depends on MFD_PCF50633 728 tristate "NXP PCF50633 RTC" 729 help 730 If you say yes here you get support for the RTC subsystem of the 731 NXP PCF50633 used in embedded systems. 732 733config RTC_DRV_AB3100 734 tristate "ST-Ericsson AB3100 RTC" 735 depends on AB3100_CORE 736 default y if AB3100_CORE 737 help 738 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC 739 support. This chip contains a battery- and capacitor-backed RTC. 740 741config RTC_DRV_AB8500 742 tristate "ST-Ericsson AB8500 RTC" 743 depends on AB8500_CORE 744 select RTC_INTF_DEV 745 select RTC_INTF_DEV_UIE_EMUL 746 help 747 Select this to enable the ST-Ericsson AB8500 power management IC RTC 748 support. This chip contains a battery- and capacitor-backed RTC. 749 750config RTC_DRV_NUC900 751 tristate "NUC910/NUC920 RTC driver" 752 depends on ARCH_W90X900 753 help 754 If you say yes here you get support for the RTC subsystem of the 755 NUC910/NUC920 used in embedded systems. 756 757comment "on-CPU RTC drivers" 758 759config RTC_DRV_DAVINCI 760 tristate "TI DaVinci RTC" 761 depends on ARCH_DAVINCI_DM365 762 help 763 If you say yes here you get support for the RTC on the 764 DaVinci platforms (DM365). 765 766 This driver can also be built as a module. If so, the module 767 will be called rtc-davinci. 768 769config RTC_DRV_IMXDI 770 tristate "Freescale IMX DryIce Real Time Clock" 771 depends on SOC_IMX25 772 help 773 Support for Freescale IMX DryIce RTC 774 775 This driver can also be built as a module, if so, the module 776 will be called "rtc-imxdi". 777 778config RTC_DRV_OMAP 779 tristate "TI OMAP1" 780 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX 781 help 782 Say "yes" here to support the real time clock on TI OMAP1 and 783 DA8xx/OMAP-L13x chips. This driver can also be built as a 784 module called rtc-omap. 785 786config HAVE_S3C_RTC 787 bool 788 help 789 This will include RTC support for Samsung SoCs. If 790 you want to include RTC support for any machine, kindly 791 select this in the respective mach-XXXX/Kconfig file. 792 793config RTC_DRV_S3C 794 tristate "Samsung S3C series SoC RTC" 795 depends on ARCH_S3C64XX || HAVE_S3C_RTC 796 help 797 RTC (Realtime Clock) driver for the clock inbuilt into the 798 Samsung S3C24XX series of SoCs. This can provide periodic 799 interrupt rates from 1Hz to 64Hz for user programs, and 800 wakeup from Alarm. 801 802 The driver currently supports the common features on all the 803 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 804 and S3C2442. 805 806 This driver can also be build as a module. If so, the module 807 will be called rtc-s3c. 808 809config RTC_DRV_EP93XX 810 tristate "Cirrus Logic EP93XX" 811 depends on ARCH_EP93XX 812 help 813 If you say yes here you get support for the 814 RTC embedded in the Cirrus Logic EP93XX processors. 815 816 This driver can also be built as a module. If so, the module 817 will be called rtc-ep93xx. 818 819config RTC_DRV_SA1100 820 tristate "SA11x0/PXA2xx/PXA910" 821 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP 822 help 823 If you say Y here you will get access to the real time clock 824 built into your SA11x0 or PXA2xx CPU. 825 826 To compile this driver as a module, choose M here: the 827 module will be called rtc-sa1100. 828 829config RTC_DRV_SH 830 tristate "SuperH On-Chip RTC" 831 depends on SUPERH && HAVE_CLK 832 help 833 Say Y here to enable support for the on-chip RTC found in 834 most SuperH processors. 835 836 To compile this driver as a module, choose M here: the 837 module will be called rtc-sh. 838 839config RTC_DRV_VR41XX 840 tristate "NEC VR41XX" 841 depends on CPU_VR41XX 842 help 843 If you say Y here you will get access to the real time clock 844 built into your NEC VR41XX CPU. 845 846 To compile this driver as a module, choose M here: the 847 module will be called rtc-vr41xx. 848 849config RTC_DRV_PL030 850 tristate "ARM AMBA PL030 RTC" 851 depends on ARM_AMBA 852 help 853 If you say Y here you will get access to ARM AMBA 854 PrimeCell PL030 RTC found on certain ARM SOCs. 855 856 To compile this driver as a module, choose M here: the 857 module will be called rtc-pl030. 858 859config RTC_DRV_PL031 860 tristate "ARM AMBA PL031 RTC" 861 depends on ARM_AMBA 862 help 863 If you say Y here you will get access to ARM AMBA 864 PrimeCell PL031 RTC found on certain ARM SOCs. 865 866 To compile this driver as a module, choose M here: the 867 module will be called rtc-pl031. 868 869config RTC_DRV_AT32AP700X 870 tristate "AT32AP700X series RTC" 871 depends on PLATFORM_AT32AP 872 help 873 Driver for the internal RTC (Realtime Clock) on Atmel AVR32 874 AT32AP700x family processors. 875 876config RTC_DRV_AT91RM9200 877 tristate "AT91RM9200 or some AT91SAM9 RTC" 878 depends on ARCH_AT91 879 help 880 Driver for the internal RTC (Realtime Clock) module found on 881 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips 882 this is powered by the backup power supply. 883 884config RTC_DRV_AT91SAM9 885 tristate "AT91SAM9x/AT91CAP9 RTT as RTC" 886 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40) 887 help 888 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT 889 (Real Time Timer). These timers are powered by the backup power 890 supply (such as a small coin cell battery), but do not need to 891 be used as RTCs. 892 893 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the 894 dedicated RTC module and leave the RTT available for other uses.) 895 896config RTC_DRV_AT91SAM9_RTT 897 int 898 range 0 1 899 default 0 900 prompt "RTT module Number" if ARCH_AT91SAM9263 901 depends on RTC_DRV_AT91SAM9 902 help 903 More than one RTT module is available. You can choose which 904 one will be used as an RTC. The default of zero is normally 905 OK to use, though some systems use that for non-RTC purposes. 906 907config RTC_DRV_AT91SAM9_GPBR 908 int 909 range 0 3 if !ARCH_AT91SAM9263 910 range 0 15 if ARCH_AT91SAM9263 911 default 0 912 prompt "Backup Register Number" 913 depends on RTC_DRV_AT91SAM9 914 help 915 The RTC driver needs to use one of the General Purpose Backup 916 Registers (GPBRs) as well as the RTT. You can choose which one 917 will be used. The default of zero is normally OK to use, but 918 on some systems other software needs to use that register. 919 920config RTC_DRV_AU1XXX 921 tristate "Au1xxx Counter0 RTC support" 922 depends on MIPS_ALCHEMY 923 help 924 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year 925 counter) to be used as a RTC. 926 927 This driver can also be built as a module. If so, the module 928 will be called rtc-au1xxx. 929 930config RTC_DRV_BFIN 931 tristate "Blackfin On-Chip RTC" 932 depends on BLACKFIN && !BF561 933 help 934 If you say yes here you will get support for the 935 Blackfin On-Chip Real Time Clock. 936 937 This driver can also be built as a module. If so, the module 938 will be called rtc-bfin. 939 940config RTC_DRV_RS5C313 941 tristate "Ricoh RS5C313" 942 depends on SH_LANDISK 943 help 944 If you say yes here you get support for the Ricoh RS5C313 RTC chips. 945 946config RTC_DRV_GENERIC 947 tristate "Generic RTC support" 948 # Please consider writing a new RTC driver instead of using the generic 949 # RTC abstraction 950 depends on PARISC || M68K || PPC || SUPERH32 951 help 952 Say Y or M here to enable RTC support on systems using the generic 953 RTC abstraction. If you do not know what you are doing, you should 954 just say Y. 955 956config RTC_DRV_PXA 957 tristate "PXA27x/PXA3xx" 958 depends on ARCH_PXA 959 help 960 If you say Y here you will get access to the real time clock 961 built into your PXA27x or PXA3xx CPU. 962 963 This RTC driver uses PXA RTC registers available since pxa27x 964 series (RDxR, RYxR) instead of legacy RCNR, RTAR. 965 966config RTC_DRV_VT8500 967 tristate "VIA/WonderMedia 85xx SoC RTC" 968 depends on ARCH_VT8500 969 help 970 If you say Y here you will get access to the real time clock 971 built into your VIA VT8500 SoC or its relatives. 972 973 974config RTC_DRV_SUN4V 975 bool "SUN4V Hypervisor RTC" 976 depends on SPARC64 977 help 978 If you say Y here you will get support for the Hypervisor 979 based RTC on SUN4V systems. 980 981config RTC_DRV_STARFIRE 982 bool "Starfire RTC" 983 depends on SPARC64 984 help 985 If you say Y here you will get support for the RTC found on 986 Starfire systems. 987 988config RTC_DRV_TX4939 989 tristate "TX4939 SoC" 990 depends on SOC_TX4939 991 help 992 Driver for the internal RTC (Realtime Clock) module found on 993 Toshiba TX4939 SoC. 994 995config RTC_DRV_MV 996 tristate "Marvell SoC RTC" 997 depends on ARCH_KIRKWOOD || ARCH_DOVE 998 help 999 If you say yes here you will get support for the in-chip RTC 1000 that can be found in some of Marvell's SoC devices, such as 1001 the Kirkwood 88F6281 and 88F6192. 1002 1003 This driver can also be built as a module. If so, the module 1004 will be called rtc-mv. 1005 1006config RTC_DRV_PS3 1007 tristate "PS3 RTC" 1008 depends on PPC_PS3 1009 help 1010 If you say yes here you will get support for the RTC on PS3. 1011 1012 This driver can also be built as a module. If so, the module 1013 will be called rtc-ps3. 1014 1015config RTC_DRV_COH901331 1016 tristate "ST-Ericsson COH 901 331 RTC" 1017 depends on ARCH_U300 1018 help 1019 If you say Y here you will get access to ST-Ericsson 1020 COH 901 331 RTC clock found in some ST-Ericsson Mobile 1021 Platforms. 1022 1023 This driver can also be built as a module. If so, the module 1024 will be called "rtc-coh901331". 1025 1026 1027config RTC_DRV_STMP 1028 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC" 1029 depends on ARCH_MXS 1030 help 1031 If you say yes here you will get support for the onboard 1032 STMP3xxx/i.MX23/i.MX28 RTC. 1033 1034 This driver can also be built as a module. If so, the module 1035 will be called rtc-stmp3xxx. 1036 1037config RTC_DRV_PCAP 1038 tristate "PCAP RTC" 1039 depends on EZX_PCAP 1040 help 1041 If you say Y here you will get support for the RTC found on 1042 the PCAP2 ASIC used on some Motorola phones. 1043 1044config RTC_DRV_MC13XXX 1045 depends on MFD_MC13XXX 1046 tristate "Freescale MC13xxx RTC" 1047 help 1048 This enables support for the RTCs found on Freescale's PMICs 1049 MC13783 and MC13892. 1050 1051config RTC_DRV_MPC5121 1052 tristate "Freescale MPC5121 built-in RTC" 1053 depends on PPC_MPC512x || PPC_MPC52xx 1054 help 1055 If you say yes here you will get support for the 1056 built-in RTC on MPC5121 or on MPC5200. 1057 1058 This driver can also be built as a module. If so, the module 1059 will be called rtc-mpc5121. 1060 1061config RTC_DRV_JZ4740 1062 tristate "Ingenic JZ4740 SoC" 1063 depends on MACH_JZ4740 1064 help 1065 If you say yes here you get support for the Ingenic JZ4740 SoC RTC 1066 controller. 1067 1068 This driver can also be buillt as a module. If so, the module 1069 will be called rtc-jz4740. 1070 1071config RTC_DRV_LPC32XX 1072 depends on ARCH_LPC32XX 1073 tristate "NXP LPC32XX RTC" 1074 help 1075 This enables support for the NXP RTC in the LPC32XX 1076 1077 This driver can also be buillt as a module. If so, the module 1078 will be called rtc-lpc32xx. 1079 1080config RTC_DRV_PM8XXX 1081 tristate "Qualcomm PMIC8XXX RTC" 1082 depends on MFD_PM8XXX 1083 help 1084 If you say yes here you get support for the 1085 Qualcomm PMIC8XXX RTC. 1086 1087 To compile this driver as a module, choose M here: the 1088 module will be called rtc-pm8xxx. 1089 1090config RTC_DRV_TEGRA 1091 tristate "NVIDIA Tegra Internal RTC driver" 1092 depends on ARCH_TEGRA 1093 help 1094 If you say yes here you get support for the 1095 Tegra 200 series internal RTC module. 1096 1097 This drive can also be built as a module. If so, the module 1098 will be called rtc-tegra. 1099 1100config RTC_DRV_TILE 1101 tristate "Tilera hypervisor RTC support" 1102 depends on TILE 1103 help 1104 Enable support for the Linux driver side of the Tilera 1105 hypervisor's real-time clock interface. 1106 1107config RTC_DRV_PUV3 1108 tristate "PKUnity v3 RTC support" 1109 depends on ARCH_PUV3 1110 help 1111 This enables support for the RTC in the PKUnity-v3 SoCs. 1112 1113 This drive can also be built as a module. If so, the module 1114 will be called rtc-puv3. 1115 1116config RTC_DRV_LOONGSON1 1117 tristate "loongson1 RTC support" 1118 depends on MACH_LOONGSON1 1119 help 1120 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year 1121 counter) to be used as a RTC. 1122 1123 This driver can also be built as a module. If so, the module 1124 will be called rtc-ls1x. 1125 1126config RTC_DRV_MXC 1127 tristate "Freescale MXC Real Time Clock" 1128 depends on ARCH_MXC 1129 help 1130 If you say yes here you get support for the Freescale MXC 1131 RTC module. 1132 1133 This driver can also be built as a module, if so, the module 1134 will be called "rtc-mxc". 1135 1136config RTC_DRV_SNVS 1137 tristate "Freescale SNVS RTC support" 1138 depends on HAS_IOMEM 1139 depends on OF 1140 help 1141 If you say yes here you get support for the Freescale SNVS 1142 Low Power (LP) RTC module. 1143 1144 This driver can also be built as a module, if so, the module 1145 will be called "rtc-snvs". 1146 1147endif # RTC_CLASS 1148