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