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