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