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