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 help 191 If you say yes here you get support for Abracon AB080X and AB180X 192 families of ultra-low-power battery- and capacitor-backed real-time 193 clock chips. 194 195 This driver can also be built as a module. If so, the module 196 will be called rtc-abx80x. 197 198config RTC_DRV_AC100 199 tristate "X-Powers AC100" 200 depends on MFD_AC100 201 help 202 If you say yes here you get support for the real-time clock found 203 in X-Powers AC100 family peripheral ICs. 204 205 This driver can also be built as a module. If so, the module 206 will be called rtc-ac100. 207 208config RTC_DRV_BRCMSTB 209 tristate "Broadcom STB wake-timer" 210 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST 211 default ARCH_BRCMSTB || BMIPS_GENERIC 212 help 213 If you say yes here you get support for the wake-timer found on 214 Broadcom STB SoCs (BCM7xxx). 215 216 This driver can also be built as a module. If so, the module will 217 be called rtc-brcmstb-waketimer. 218 219config RTC_DRV_AS3722 220 tristate "ams AS3722 RTC driver" 221 depends on MFD_AS3722 222 help 223 If you say yes here you get support for the RTC of ams AS3722 PMIC 224 chips. 225 226 This driver can also be built as a module. If so, the module 227 will be called rtc-as3722. 228 229config RTC_DRV_DS1307 230 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057" 231 help 232 If you say yes here you get support for various compatible RTC 233 chips (often with battery backup) connected with I2C. This driver 234 should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341, 235 ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips. 236 In some cases the RTC must already have been initialized (by 237 manufacturing or a bootloader). 238 239 The first seven registers on these chips hold an RTC, and other 240 registers may add features such as NVRAM, a trickle charger for 241 the RTC/NVRAM backup power, and alarms. NVRAM is visible in 242 sysfs, but other chip features may not be available. 243 244 This driver can also be built as a module. If so, the module 245 will be called rtc-ds1307. 246 247config RTC_DRV_DS1307_CENTURY 248 bool "Century bit support for rtc-ds1307" 249 depends on RTC_DRV_DS1307 250 default n 251 help 252 The DS1307 driver suffered from a bug where it was enabling the 253 century bit inconditionnally but never used it when reading the time. 254 It made the driver unable to support dates beyond 2099. 255 Setting this option will add proper support for the century bit but if 256 the time was previously set using a kernel predating this option, 257 reading the date will return a date in the next century. 258 To solve that, you could boot a kernel without this option set, set 259 the RTC date and then boot a kernel with this option set. 260 261config RTC_DRV_DS1374 262 tristate "Dallas/Maxim DS1374" 263 help 264 If you say yes here you get support for Dallas Semiconductor 265 DS1374 real-time clock chips. If an interrupt is associated 266 with the device, the alarm functionality is supported. 267 268 This driver can also be built as a module. If so, the module 269 will be called rtc-ds1374. 270 271config RTC_DRV_DS1374_WDT 272 bool "Dallas/Maxim DS1374 watchdog timer" 273 depends on RTC_DRV_DS1374 274 help 275 If you say Y here you will get support for the 276 watchdog timer in the Dallas Semiconductor DS1374 277 real-time clock chips. 278 279config RTC_DRV_DS1672 280 tristate "Dallas/Maxim DS1672" 281 help 282 If you say yes here you get support for the 283 Dallas/Maxim DS1672 timekeeping chip. 284 285 This driver can also be built as a module. If so, the module 286 will be called rtc-ds1672. 287 288config RTC_DRV_HYM8563 289 tristate "Haoyu Microelectronics HYM8563" 290 depends on OF 291 help 292 Say Y to enable support for the HYM8563 I2C RTC chip. Apart 293 from the usual rtc functions it provides a clock output of 294 up to 32kHz. 295 296 This driver can also be built as a module. If so, the module 297 will be called rtc-hym8563. 298 299config RTC_DRV_LP8788 300 tristate "TI LP8788 RTC driver" 301 depends on MFD_LP8788 302 help 303 Say Y to enable support for the LP8788 RTC/ALARM driver. 304 305config RTC_DRV_MAX6900 306 tristate "Maxim MAX6900" 307 help 308 If you say yes here you will get support for the 309 Maxim MAX6900 I2C RTC chip. 310 311 This driver can also be built as a module. If so, the module 312 will be called rtc-max6900. 313 314config RTC_DRV_MAX8907 315 tristate "Maxim MAX8907" 316 depends on MFD_MAX8907 || COMPILE_TEST 317 select REGMAP_IRQ 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 select REGMAP_I2C 643 help 644 If you say yes here you will get support for the 645 RTC of Samsung S2MPS14 and S5M PMIC series. 646 647 This driver can also be built as a module. If so, the module 648 will be called rtc-s5m. 649 650endif # I2C 651 652comment "SPI RTC drivers" 653 654if SPI_MASTER 655 656config RTC_DRV_M41T93 657 tristate "ST M41T93" 658 help 659 If you say yes here you will get support for the 660 ST M41T93 SPI RTC chip. 661 662 This driver can also be built as a module. If so, the module 663 will be called rtc-m41t93. 664 665config RTC_DRV_M41T94 666 tristate "ST M41T94" 667 help 668 If you say yes here you will get support for the 669 ST M41T94 SPI RTC chip. 670 671 This driver can also be built as a module. If so, the module 672 will be called rtc-m41t94. 673 674config RTC_DRV_DS1302 675 tristate "Dallas/Maxim DS1302" 676 depends on SPI 677 help 678 If you say yes here you get support for the Dallas DS1302 RTC chips. 679 680 This driver can also be built as a module. If so, the module 681 will be called rtc-ds1302. 682 683config RTC_DRV_DS1305 684 tristate "Dallas/Maxim DS1305/DS1306" 685 help 686 Select this driver to get support for the Dallas/Maxim DS1305 687 and DS1306 real time clock chips. These support a trickle 688 charger, alarms, and NVRAM in addition to the clock. 689 690 This driver can also be built as a module. If so, the module 691 will be called rtc-ds1305. 692 693config RTC_DRV_DS1343 694 select REGMAP_SPI 695 tristate "Dallas/Maxim DS1343/DS1344" 696 help 697 If you say yes here you get support for the 698 Dallas/Maxim DS1343 and DS1344 real time clock chips. 699 Support for trickle charger, alarm is provided. 700 701 This driver can also be built as a module. If so, the module 702 will be called rtc-ds1343. 703 704config RTC_DRV_DS1347 705 select REGMAP_SPI 706 tristate "Dallas/Maxim DS1347" 707 help 708 If you say yes here you get support for the 709 Dallas/Maxim DS1347 chips. 710 711 This driver only supports the RTC feature, and not other chip 712 features such as alarms. 713 714 This driver can also be built as a module. If so, the module 715 will be called rtc-ds1347. 716 717config RTC_DRV_DS1390 718 tristate "Dallas/Maxim DS1390/93/94" 719 help 720 If you say yes here you get support for the 721 Dallas/Maxim DS1390/93/94 chips. 722 723 This driver supports the RTC feature and trickle charging but not 724 other chip features such as alarms. 725 726 This driver can also be built as a module. If so, the module 727 will be called rtc-ds1390. 728 729config RTC_DRV_MAX6916 730 tristate "Maxim MAX6916" 731 help 732 If you say yes here you will get support for the 733 Maxim MAX6916 SPI RTC chip. 734 735 This driver only supports the RTC feature, and not other chip 736 features such as alarms. 737 738 This driver can also be built as a module. If so, the module 739 will be called rtc-max6916. 740 741config RTC_DRV_R9701 742 tristate "Epson RTC-9701JE" 743 help 744 If you say yes here you will get support for the 745 Epson RTC-9701JE SPI RTC chip. 746 747 This driver can also be built as a module. If so, the module 748 will be called rtc-r9701. 749 750config RTC_DRV_RX4581 751 tristate "Epson RX-4581" 752 help 753 If you say yes here you will get support for the Epson RX-4581. 754 755 This driver can also be built as a module. If so the module 756 will be called rtc-rx4581. 757 758config RTC_DRV_RX6110 759 tristate "Epson RX-6110" 760 select REGMAP_SPI 761 help 762 If you say yes here you will get support for the Epson RX-6610. 763 764 This driver can also be built as a module. If so the module 765 will be called rtc-rx6110. 766 767config RTC_DRV_RS5C348 768 tristate "Ricoh RS5C348A/B" 769 help 770 If you say yes here you get support for the 771 Ricoh RS5C348A and RS5C348B RTC chips. 772 773 This driver can also be built as a module. If so, the module 774 will be called rtc-rs5c348. 775 776config RTC_DRV_MAX6902 777 tristate "Maxim MAX6902" 778 help 779 If you say yes here you will get support for the 780 Maxim MAX6902 SPI RTC chip. 781 782 This driver can also be built as a module. If so, the module 783 will be called rtc-max6902. 784 785config RTC_DRV_PCF2123 786 tristate "NXP PCF2123" 787 help 788 If you say yes here you get support for the NXP PCF2123 789 RTC chip. 790 791 This driver can also be built as a module. If so, the module 792 will be called rtc-pcf2123. 793 794config RTC_DRV_MCP795 795 tristate "Microchip MCP795" 796 help 797 If you say yes here you will get support for the Microchip MCP795. 798 799 This driver can also be built as a module. If so the module 800 will be called rtc-mcp795. 801 802endif # SPI_MASTER 803 804# 805# Helper to resolve issues with configs that have SPI enabled but I2C 806# modular. See SND_SOC_I2C_AND_SPI for more information 807# 808config RTC_I2C_AND_SPI 809 tristate 810 default m if I2C=m 811 default y if I2C=y 812 default y if SPI_MASTER=y 813 select REGMAP_I2C if I2C 814 select REGMAP_SPI if SPI_MASTER 815 816comment "SPI and I2C RTC drivers" 817 818config RTC_DRV_DS3232 819 tristate "Dallas/Maxim DS3232/DS3234" 820 depends on RTC_I2C_AND_SPI 821 help 822 If you say yes here you get support for Dallas Semiconductor 823 DS3232 and DS3234 real-time clock chips. If an interrupt is associated 824 with the device, the alarm functionality is supported. 825 826 This driver can also be built as a module. If so, the module 827 will be called rtc-ds3232. 828 829config RTC_DRV_DS3232_HWMON 830 bool "HWMON support for Dallas/Maxim DS3232/DS3234" 831 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m) 832 default y 833 help 834 Say Y here if you want to expose temperature sensor data on 835 rtc-ds3232 836 837config RTC_DRV_PCF2127 838 tristate "NXP PCF2127" 839 depends on RTC_I2C_AND_SPI 840 help 841 If you say yes here you get support for the NXP PCF2127/29 RTC 842 chips. 843 844 This driver can also be built as a module. If so, the module 845 will be called rtc-pcf2127. 846 847config RTC_DRV_RV3029C2 848 tristate "Micro Crystal RV3029/3049" 849 depends on RTC_I2C_AND_SPI 850 help 851 If you say yes here you get support for the Micro Crystal 852 RV3029 and RV3049 RTC chips. 853 854 This driver can also be built as a module. If so, the module 855 will be called rtc-rv3029c2. 856 857config RTC_DRV_RV3029_HWMON 858 bool "HWMON support for RV3029/3049" 859 depends on RTC_DRV_RV3029C2 && HWMON 860 depends on !(RTC_DRV_RV3029C2=y && HWMON=m) 861 default y 862 help 863 Say Y here if you want to expose temperature sensor data on 864 rtc-rv3029. 865 866comment "Platform RTC drivers" 867 868# this 'CMOS' RTC driver is arch dependent because it requires 869# <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a 870# global rtc_lock ... it's not yet just another platform_device. 871 872config RTC_DRV_CMOS 873 tristate "PC-style 'CMOS'" 874 depends on X86 || ARM || PPC || MIPS || SPARC64 875 default y if X86 876 select RTC_MC146818_LIB 877 help 878 Say "yes" here to get direct support for the real time clock 879 found in every PC or ACPI-based system, and some other boards. 880 Specifically the original MC146818, compatibles like those in 881 PC south bridges, the DS12887 or M48T86, some multifunction 882 or LPC bus chips, and so on. 883 884 Your system will need to define the platform device used by 885 this driver, otherwise it won't be accessible. This means 886 you can safely enable this driver if you don't know whether 887 or not your board has this kind of hardware. 888 889 This driver can also be built as a module. If so, the module 890 will be called rtc-cmos. 891 892config RTC_DRV_ALPHA 893 bool "Alpha PC-style CMOS" 894 depends on ALPHA 895 select RTC_MC146818_LIB 896 default y 897 help 898 Direct support for the real-time clock found on every Alpha 899 system, specifically MC146818 compatibles. If in doubt, say Y. 900 901config RTC_DRV_VRTC 902 tristate "Virtual RTC for Intel MID platforms" 903 depends on X86_INTEL_MID 904 default y if X86_INTEL_MID 905 906 help 907 Say "yes" here to get direct support for the real time clock 908 found on Moorestown platforms. The VRTC is a emulated RTC that 909 derives its clock source from a real RTC in the PMIC. The MC146818 910 style programming interface is mostly conserved, but any 911 updates are done via IPC calls to the system controller FW. 912 913config RTC_DRV_DS1216 914 tristate "Dallas DS1216" 915 depends on SNI_RM 916 help 917 If you say yes here you get support for the Dallas DS1216 RTC chips. 918 919config RTC_DRV_DS1286 920 tristate "Dallas DS1286" 921 depends on HAS_IOMEM 922 help 923 If you say yes here you get support for the Dallas DS1286 RTC chips. 924 925config RTC_DRV_DS1511 926 tristate "Dallas DS1511" 927 depends on HAS_IOMEM 928 help 929 If you say yes here you get support for the 930 Dallas DS1511 timekeeping/watchdog chip. 931 932 This driver can also be built as a module. If so, the module 933 will be called rtc-ds1511. 934 935config RTC_DRV_DS1553 936 tristate "Maxim/Dallas DS1553" 937 depends on HAS_IOMEM 938 help 939 If you say yes here you get support for the 940 Maxim/Dallas DS1553 timekeeping chip. 941 942 This driver can also be built as a module. If so, the module 943 will be called rtc-ds1553. 944 945config RTC_DRV_DS1685_FAMILY 946 tristate "Dallas/Maxim DS1685 Family" 947 help 948 If you say yes here you get support for the Dallas/Maxim DS1685 949 family of real time chips. This family includes the DS1685/DS1687, 950 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and 951 DS17885/DS17887 chips. 952 953 This driver can also be built as a module. If so, the module 954 will be called rtc-ds1685. 955 956choice 957 prompt "Subtype" 958 depends on RTC_DRV_DS1685_FAMILY 959 default RTC_DRV_DS1685 960 961config RTC_DRV_DS1685 962 bool "DS1685/DS1687" 963 help 964 This enables support for the Dallas/Maxim DS1685/DS1687 real time 965 clock chip. 966 967 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30) 968 systems, as well as EPPC-405-UC modules by electronic system design 969 GmbH. 970 971config RTC_DRV_DS1689 972 bool "DS1689/DS1693" 973 help 974 This enables support for the Dallas/Maxim DS1689/DS1693 real time 975 clock chip. 976 977 This is an older RTC chip, supplanted by the DS1685/DS1687 above, 978 which supports a few minor features such as Vcc, Vbat, and Power 979 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number. 980 981 It also works for the even older DS1688/DS1691 RTC chips, which are 982 virtually the same and carry the same model number. Both chips 983 have 114 bytes of user NVRAM. 984 985config RTC_DRV_DS17285 986 bool "DS17285/DS17287" 987 help 988 This enables support for the Dallas/Maxim DS17285/DS17287 real time 989 clock chip. 990 991 This chip features 2kb of extended NV-SRAM. It may possibly be 992 found in some SGI O2 systems (rare). 993 994config RTC_DRV_DS17485 995 bool "DS17485/DS17487" 996 help 997 This enables support for the Dallas/Maxim DS17485/DS17487 real time 998 clock chip. 999 1000 This chip features 4kb of extended NV-SRAM. 1001 1002config RTC_DRV_DS17885 1003 bool "DS17885/DS17887" 1004 help 1005 This enables support for the Dallas/Maxim DS17885/DS17887 real time 1006 clock chip. 1007 1008 This chip features 8kb of extended NV-SRAM. 1009 1010endchoice 1011 1012config RTC_DS1685_PROC_REGS 1013 bool "Display register values in /proc" 1014 depends on RTC_DRV_DS1685_FAMILY && PROC_FS 1015 help 1016 Enable this to display a readout of all of the RTC registers in 1017 /proc/drivers/rtc. Keep in mind that this can potentially lead 1018 to lost interrupts, as reading Control Register C will clear 1019 all pending IRQ flags. 1020 1021 Unless you are debugging this driver, choose N. 1022 1023config RTC_DRV_DS1742 1024 tristate "Maxim/Dallas DS1742/1743" 1025 depends on HAS_IOMEM 1026 help 1027 If you say yes here you get support for the 1028 Maxim/Dallas DS1742/1743 timekeeping chip. 1029 1030 This driver can also be built as a module. If so, the module 1031 will be called rtc-ds1742. 1032 1033config RTC_DRV_DS2404 1034 tristate "Maxim/Dallas DS2404" 1035 help 1036 If you say yes here you get support for the 1037 Dallas DS2404 RTC chip. 1038 1039 This driver can also be built as a module. If so, the module 1040 will be called rtc-ds2404. 1041 1042config RTC_DRV_DA9052 1043 tristate "Dialog DA9052/DA9053 RTC" 1044 depends on PMIC_DA9052 1045 help 1046 Say y here to support the RTC driver for Dialog Semiconductor 1047 DA9052-BC and DA9053-AA/Bx PMICs. 1048 1049config RTC_DRV_DA9055 1050 tristate "Dialog Semiconductor DA9055 RTC" 1051 depends on MFD_DA9055 1052 help 1053 If you say yes here you will get support for the 1054 RTC of the Dialog DA9055 PMIC. 1055 1056 This driver can also be built as a module. If so, the module 1057 will be called rtc-da9055 1058 1059config RTC_DRV_DA9063 1060 tristate "Dialog Semiconductor DA9063/DA9062 RTC" 1061 depends on MFD_DA9063 || MFD_DA9062 1062 help 1063 If you say yes here you will get support for the RTC subsystem 1064 for the Dialog Semiconductor PMIC chips DA9063 and DA9062. 1065 1066 This driver can also be built as a module. If so, the module 1067 will be called "rtc-da9063". 1068 1069config RTC_DRV_EFI 1070 tristate "EFI RTC" 1071 depends on EFI && !X86 1072 help 1073 If you say yes here you will get support for the EFI 1074 Real Time Clock. 1075 1076 This driver can also be built as a module. If so, the module 1077 will be called rtc-efi. 1078 1079config RTC_DRV_STK17TA8 1080 tristate "Simtek STK17TA8" 1081 depends on HAS_IOMEM 1082 help 1083 If you say yes here you get support for the 1084 Simtek STK17TA8 timekeeping chip. 1085 1086 This driver can also be built as a module. If so, the module 1087 will be called rtc-stk17ta8. 1088 1089config RTC_DRV_M48T86 1090 tristate "ST M48T86/Dallas DS12887" 1091 help 1092 If you say Y here you will get support for the 1093 ST M48T86 and Dallas DS12887 RTC chips. 1094 1095 This driver can also be built as a module. If so, the module 1096 will be called rtc-m48t86. 1097 1098config RTC_DRV_M48T35 1099 tristate "ST M48T35" 1100 depends on HAS_IOMEM 1101 help 1102 If you say Y here you will get support for the 1103 ST M48T35 RTC chip. 1104 1105 This driver can also be built as a module, if so, the module 1106 will be called "rtc-m48t35". 1107 1108config RTC_DRV_M48T59 1109 tristate "ST M48T59/M48T08/M48T02" 1110 depends on HAS_IOMEM 1111 help 1112 If you say Y here you will get support for the 1113 ST M48T59 RTC chip and compatible ST M48T08 and M48T02. 1114 1115 These chips are usually found in Sun SPARC and UltraSPARC 1116 workstations. 1117 1118 This driver can also be built as a module, if so, the module 1119 will be called "rtc-m48t59". 1120 1121config RTC_DRV_MSM6242 1122 tristate "Oki MSM6242" 1123 depends on HAS_IOMEM 1124 help 1125 If you say yes here you get support for the Oki MSM6242 1126 timekeeping chip. It is used in some Amiga models (e.g. A2000). 1127 1128 This driver can also be built as a module. If so, the module 1129 will be called rtc-msm6242. 1130 1131config RTC_DRV_BQ4802 1132 tristate "TI BQ4802" 1133 depends on HAS_IOMEM 1134 help 1135 If you say Y here you will get support for the TI 1136 BQ4802 RTC chip. 1137 1138 This driver can also be built as a module. If so, the module 1139 will be called rtc-bq4802. 1140 1141config RTC_DRV_RP5C01 1142 tristate "Ricoh RP5C01" 1143 depends on HAS_IOMEM 1144 help 1145 If you say yes here you get support for the Ricoh RP5C01 1146 timekeeping chip. It is used in some Amiga models (e.g. A3000 1147 and A4000). 1148 1149 This driver can also be built as a module. If so, the module 1150 will be called rtc-rp5c01. 1151 1152config RTC_DRV_V3020 1153 tristate "EM Microelectronic V3020" 1154 help 1155 If you say yes here you will get support for the 1156 EM Microelectronic v3020 RTC chip. 1157 1158 This driver can also be built as a module. If so, the module 1159 will be called rtc-v3020. 1160 1161config RTC_DRV_WM831X 1162 tristate "Wolfson Microelectronics WM831x RTC" 1163 depends on MFD_WM831X 1164 help 1165 If you say yes here you will get support for the RTC subsystem 1166 of the Wolfson Microelectronics WM831X series PMICs. 1167 1168 This driver can also be built as a module. If so, the module 1169 will be called "rtc-wm831x". 1170 1171config RTC_DRV_WM8350 1172 tristate "Wolfson Microelectronics WM8350 RTC" 1173 depends on MFD_WM8350 1174 help 1175 If you say yes here you will get support for the RTC subsystem 1176 of the Wolfson Microelectronics WM8350. 1177 1178 This driver can also be built as a module. If so, the module 1179 will be called "rtc-wm8350". 1180 1181config RTC_DRV_SC27XX 1182 tristate "Spreadtrum SC27xx RTC" 1183 depends on MFD_SC27XX_PMIC || COMPILE_TEST 1184 help 1185 If you say Y here you will get support for the RTC subsystem 1186 of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs 1187 includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips. 1188 1189 This driver can also be built as a module. If so, the module 1190 will be called rtc-sc27xx. 1191 1192config RTC_DRV_SPEAR 1193 tristate "SPEAR ST RTC" 1194 depends on PLAT_SPEAR || COMPILE_TEST 1195 default y 1196 help 1197 If you say Y here you will get support for the RTC found on 1198 spear 1199 1200config RTC_DRV_PCF50633 1201 depends on MFD_PCF50633 1202 tristate "NXP PCF50633 RTC" 1203 help 1204 If you say yes here you get support for the RTC subsystem of the 1205 NXP PCF50633 used in embedded systems. 1206 1207config RTC_DRV_AB3100 1208 tristate "ST-Ericsson AB3100 RTC" 1209 depends on AB3100_CORE 1210 default y if AB3100_CORE 1211 help 1212 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC 1213 support. This chip contains a battery- and capacitor-backed RTC. 1214 1215config RTC_DRV_AB8500 1216 tristate "ST-Ericsson AB8500 RTC" 1217 depends on AB8500_CORE 1218 select RTC_INTF_DEV 1219 select RTC_INTF_DEV_UIE_EMUL 1220 help 1221 Select this to enable the ST-Ericsson AB8500 power management IC RTC 1222 support. This chip contains a battery- and capacitor-backed RTC. 1223 1224config RTC_DRV_NUC900 1225 tristate "NUC910/NUC920 RTC driver" 1226 depends on ARCH_W90X900 || COMPILE_TEST 1227 help 1228 If you say yes here you get support for the RTC subsystem of the 1229 NUC910/NUC920 used in embedded systems. 1230 1231config RTC_DRV_OPAL 1232 tristate "IBM OPAL RTC driver" 1233 depends on PPC_POWERNV 1234 default y 1235 help 1236 If you say yes here you get support for the PowerNV platform RTC 1237 driver based on OPAL interfaces. 1238 1239 This driver can also be built as a module. If so, the module 1240 will be called rtc-opal. 1241 1242config RTC_DRV_ZYNQMP 1243 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC" 1244 depends on OF 1245 help 1246 If you say yes here you get support for the RTC controller found on 1247 Xilinx Zynq Ultrascale+ MPSoC. 1248 1249config RTC_DRV_CROS_EC 1250 tristate "Chrome OS EC RTC driver" 1251 depends on MFD_CROS_EC 1252 help 1253 If you say yes here you will get support for the 1254 Chrome OS Embedded Controller's RTC. 1255 1256 This driver can also be built as a module. If so, the module 1257 will be called rtc-cros-ec. 1258 1259comment "on-CPU RTC drivers" 1260 1261config RTC_DRV_ASM9260 1262 tristate "Alphascale asm9260 RTC" 1263 depends on MACH_ASM9260 || COMPILE_TEST 1264 help 1265 If you say yes here you get support for the RTC on the 1266 Alphascale asm9260 SoC. 1267 1268 This driver can also be built as a module. If so, the module 1269 will be called rtc-asm9260. 1270 1271config RTC_DRV_DAVINCI 1272 tristate "TI DaVinci RTC" 1273 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST 1274 help 1275 If you say yes here you get support for the RTC on the 1276 DaVinci platforms (DM365). 1277 1278 This driver can also be built as a module. If so, the module 1279 will be called rtc-davinci. 1280 1281config RTC_DRV_DIGICOLOR 1282 tristate "Conexant Digicolor RTC" 1283 depends on ARCH_DIGICOLOR || COMPILE_TEST 1284 help 1285 If you say yes here you get support for the RTC on Conexant 1286 Digicolor platforms. This currently includes the CX92755 SoC. 1287 1288 This driver can also be built as a module. If so, the module 1289 will be called rtc-digicolor. 1290 1291config RTC_DRV_IMXDI 1292 tristate "Freescale IMX DryIce Real Time Clock" 1293 depends on ARCH_MXC 1294 help 1295 Support for Freescale IMX DryIce RTC 1296 1297 This driver can also be built as a module, if so, the module 1298 will be called "rtc-imxdi". 1299 1300config RTC_DRV_OMAP 1301 tristate "TI OMAP Real Time Clock" 1302 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST 1303 depends on OF 1304 depends on PINCTRL 1305 select GENERIC_PINCONF 1306 help 1307 Say "yes" here to support the on chip real time clock 1308 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx. 1309 1310 This driver can also be built as a module, if so, module 1311 will be called rtc-omap. 1312 1313config HAVE_S3C_RTC 1314 bool 1315 help 1316 This will include RTC support for Samsung SoCs. If 1317 you want to include RTC support for any machine, kindly 1318 select this in the respective mach-XXXX/Kconfig file. 1319 1320config RTC_DRV_S3C 1321 tristate "Samsung S3C series SoC RTC" 1322 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST 1323 help 1324 RTC (Realtime Clock) driver for the clock inbuilt into the 1325 Samsung S3C24XX series of SoCs. This can provide periodic 1326 interrupt rates from 1Hz to 64Hz for user programs, and 1327 wakeup from Alarm. 1328 1329 The driver currently supports the common features on all the 1330 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 1331 and S3C2442. 1332 1333 This driver can also be build as a module. If so, the module 1334 will be called rtc-s3c. 1335 1336config RTC_DRV_EP93XX 1337 tristate "Cirrus Logic EP93XX" 1338 depends on ARCH_EP93XX || COMPILE_TEST 1339 help 1340 If you say yes here you get support for the 1341 RTC embedded in the Cirrus Logic EP93XX processors. 1342 1343 This driver can also be built as a module. If so, the module 1344 will be called rtc-ep93xx. 1345 1346config RTC_DRV_SA1100 1347 tristate "SA11x0/PXA2xx/PXA910" 1348 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP 1349 help 1350 If you say Y here you will get access to the real time clock 1351 built into your SA11x0 or PXA2xx CPU. 1352 1353 To compile this driver as a module, choose M here: the 1354 module will be called rtc-sa1100. 1355 1356config RTC_DRV_SH 1357 tristate "SuperH On-Chip RTC" 1358 depends on SUPERH || ARCH_RENESAS 1359 help 1360 Say Y here to enable support for the on-chip RTC found in 1361 most SuperH processors. This RTC is also found in RZ/A SoCs. 1362 1363 To compile this driver as a module, choose M here: the 1364 module will be called rtc-sh. 1365 1366config RTC_DRV_VR41XX 1367 tristate "NEC VR41XX" 1368 depends on CPU_VR41XX || COMPILE_TEST 1369 help 1370 If you say Y here you will get access to the real time clock 1371 built into your NEC VR41XX CPU. 1372 1373 To compile this driver as a module, choose M here: the 1374 module will be called rtc-vr41xx. 1375 1376config RTC_DRV_PL030 1377 tristate "ARM AMBA PL030 RTC" 1378 depends on ARM_AMBA 1379 help 1380 If you say Y here you will get access to ARM AMBA 1381 PrimeCell PL030 RTC found on certain ARM SOCs. 1382 1383 To compile this driver as a module, choose M here: the 1384 module will be called rtc-pl030. 1385 1386config RTC_DRV_PL031 1387 tristate "ARM AMBA PL031 RTC" 1388 depends on ARM_AMBA 1389 help 1390 If you say Y here you will get access to ARM AMBA 1391 PrimeCell PL031 RTC found on certain ARM SOCs. 1392 1393 To compile this driver as a module, choose M here: the 1394 module will be called rtc-pl031. 1395 1396config RTC_DRV_AT91RM9200 1397 tristate "AT91RM9200 or some AT91SAM9 RTC" 1398 depends on ARCH_AT91 || COMPILE_TEST 1399 help 1400 Driver for the internal RTC (Realtime Clock) module found on 1401 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips 1402 this is powered by the backup power supply. 1403 1404config RTC_DRV_AT91SAM9 1405 tristate "AT91SAM9 RTT as RTC" 1406 depends on ARCH_AT91 || COMPILE_TEST 1407 depends on HAS_IOMEM 1408 select MFD_SYSCON 1409 help 1410 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which 1411 can be used as an RTC thanks to the backup power supply (e.g. a 1412 small coin cell battery) which keeps this block and the GPBR 1413 (General Purpose Backup Registers) block powered when the device 1414 is shutdown. 1415 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd 1416 probably want to use the real RTC block instead of the "RTT as an 1417 RTC" driver. 1418 1419config RTC_DRV_AU1XXX 1420 tristate "Au1xxx Counter0 RTC support" 1421 depends on MIPS_ALCHEMY 1422 help 1423 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year 1424 counter) to be used as a RTC. 1425 1426 This driver can also be built as a module. If so, the module 1427 will be called rtc-au1xxx. 1428 1429config RTC_DRV_RS5C313 1430 tristate "Ricoh RS5C313" 1431 depends on SH_LANDISK 1432 help 1433 If you say yes here you get support for the Ricoh RS5C313 RTC chips. 1434 1435config RTC_DRV_GENERIC 1436 tristate "Generic RTC support" 1437 # Please consider writing a new RTC driver instead of using the generic 1438 # RTC abstraction 1439 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST 1440 help 1441 Say Y or M here to enable RTC support on systems using the generic 1442 RTC abstraction. If you do not know what you are doing, you should 1443 just say Y. 1444 1445config RTC_DRV_PXA 1446 tristate "PXA27x/PXA3xx" 1447 depends on ARCH_PXA 1448 select RTC_DRV_SA1100 1449 help 1450 If you say Y here you will get access to the real time clock 1451 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs 1452 consisting of an SA1100 compatible RTC and the extended PXA RTC. 1453 1454 This RTC driver uses PXA RTC registers available since pxa27x 1455 series (RDxR, RYxR) instead of legacy RCNR, RTAR. 1456 1457config RTC_DRV_VT8500 1458 tristate "VIA/WonderMedia 85xx SoC RTC" 1459 depends on ARCH_VT8500 || COMPILE_TEST 1460 help 1461 If you say Y here you will get access to the real time clock 1462 built into your VIA VT8500 SoC or its relatives. 1463 1464 1465config RTC_DRV_SUN4V 1466 bool "SUN4V Hypervisor RTC" 1467 depends on SPARC64 1468 help 1469 If you say Y here you will get support for the Hypervisor 1470 based RTC on SUN4V systems. 1471 1472config RTC_DRV_SUN6I 1473 bool "Allwinner A31 RTC" 1474 default MACH_SUN6I || MACH_SUN8I 1475 depends on COMMON_CLK 1476 depends on ARCH_SUNXI || COMPILE_TEST 1477 help 1478 If you say Y here you will get support for the RTC found in 1479 some Allwinner SoCs like the A31 or the A64. 1480 1481config RTC_DRV_SUNXI 1482 tristate "Allwinner sun4i/sun7i RTC" 1483 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST 1484 help 1485 If you say Y here you will get support for the RTC found on 1486 Allwinner A10/A20. 1487 1488config RTC_DRV_STARFIRE 1489 bool "Starfire RTC" 1490 depends on SPARC64 1491 help 1492 If you say Y here you will get support for the RTC found on 1493 Starfire systems. 1494 1495config RTC_DRV_TX4939 1496 tristate "TX4939 SoC" 1497 depends on SOC_TX4939 || COMPILE_TEST 1498 help 1499 Driver for the internal RTC (Realtime Clock) module found on 1500 Toshiba TX4939 SoC. 1501 1502config RTC_DRV_MV 1503 tristate "Marvell SoC RTC" 1504 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST 1505 help 1506 If you say yes here you will get support for the in-chip RTC 1507 that can be found in some of Marvell's SoC devices, such as 1508 the Kirkwood 88F6281 and 88F6192. 1509 1510 This driver can also be built as a module. If so, the module 1511 will be called rtc-mv. 1512 1513config RTC_DRV_ARMADA38X 1514 tristate "Armada 38x Marvell SoC RTC" 1515 depends on ARCH_MVEBU || COMPILE_TEST 1516 help 1517 If you say yes here you will get support for the in-chip RTC 1518 that can be found in the Armada 38x Marvell's SoC device 1519 1520 This driver can also be built as a module. If so, the module 1521 will be called armada38x-rtc. 1522 1523config RTC_DRV_FTRTC010 1524 tristate "Faraday Technology FTRTC010 RTC" 1525 depends on HAS_IOMEM 1526 default ARCH_GEMINI 1527 help 1528 If you say Y here you will get support for the 1529 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's. 1530 1531 This driver can also be built as a module. If so, the module 1532 will be called rtc-ftrtc010. 1533 1534config RTC_DRV_PS3 1535 tristate "PS3 RTC" 1536 depends on PPC_PS3 1537 help 1538 If you say yes here you will get support for the RTC on PS3. 1539 1540 This driver can also be built as a module. If so, the module 1541 will be called rtc-ps3. 1542 1543config RTC_DRV_COH901331 1544 tristate "ST-Ericsson COH 901 331 RTC" 1545 depends on ARCH_U300 || COMPILE_TEST 1546 help 1547 If you say Y here you will get access to ST-Ericsson 1548 COH 901 331 RTC clock found in some ST-Ericsson Mobile 1549 Platforms. 1550 1551 This driver can also be built as a module. If so, the module 1552 will be called "rtc-coh901331". 1553 1554 1555config RTC_DRV_STMP 1556 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC" 1557 depends on ARCH_MXS || COMPILE_TEST 1558 select STMP_DEVICE 1559 help 1560 If you say yes here you will get support for the onboard 1561 STMP3xxx/i.MX23/i.MX28 RTC. 1562 1563 This driver can also be built as a module. If so, the module 1564 will be called rtc-stmp3xxx. 1565 1566config RTC_DRV_PCAP 1567 tristate "PCAP RTC" 1568 depends on EZX_PCAP 1569 help 1570 If you say Y here you will get support for the RTC found on 1571 the PCAP2 ASIC used on some Motorola phones. 1572 1573config RTC_DRV_MC13XXX 1574 depends on MFD_MC13XXX 1575 tristate "Freescale MC13xxx RTC" 1576 help 1577 This enables support for the RTCs found on Freescale's PMICs 1578 MC13783 and MC13892. 1579 1580config RTC_DRV_MPC5121 1581 tristate "Freescale MPC5121 built-in RTC" 1582 depends on PPC_MPC512x || PPC_MPC52xx 1583 help 1584 If you say yes here you will get support for the 1585 built-in RTC on MPC5121 or on MPC5200. 1586 1587 This driver can also be built as a module. If so, the module 1588 will be called rtc-mpc5121. 1589 1590config RTC_DRV_JZ4740 1591 tristate "Ingenic JZ4740 SoC" 1592 depends on MACH_INGENIC || COMPILE_TEST 1593 help 1594 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC 1595 controllers. 1596 1597 This driver can also be built as a module. If so, the module 1598 will be called rtc-jz4740. 1599 1600config RTC_DRV_LPC24XX 1601 tristate "NXP RTC for LPC178x/18xx/408x/43xx" 1602 depends on ARCH_LPC18XX || COMPILE_TEST 1603 depends on OF && HAS_IOMEM 1604 help 1605 This enables support for the NXP RTC found which can be found on 1606 NXP LPC178x/18xx/408x/43xx devices. 1607 1608 If you have one of the devices above enable this driver to use 1609 the hardware RTC. This driver can also be built as a module. If 1610 so, the module will be called rtc-lpc24xx. 1611 1612config RTC_DRV_LPC32XX 1613 depends on ARCH_LPC32XX || COMPILE_TEST 1614 tristate "NXP LPC32XX RTC" 1615 help 1616 This enables support for the NXP RTC in the LPC32XX 1617 1618 This driver can also be built as a module. If so, the module 1619 will be called rtc-lpc32xx. 1620 1621config RTC_DRV_PM8XXX 1622 tristate "Qualcomm PMIC8XXX RTC" 1623 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST 1624 help 1625 If you say yes here you get support for the 1626 Qualcomm PMIC8XXX RTC. 1627 1628 To compile this driver as a module, choose M here: the 1629 module will be called rtc-pm8xxx. 1630 1631config RTC_DRV_TEGRA 1632 tristate "NVIDIA Tegra Internal RTC driver" 1633 depends on ARCH_TEGRA || COMPILE_TEST 1634 help 1635 If you say yes here you get support for the 1636 Tegra 200 series internal RTC module. 1637 1638 This drive can also be built as a module. If so, the module 1639 will be called rtc-tegra. 1640 1641config RTC_DRV_PUV3 1642 tristate "PKUnity v3 RTC support" 1643 depends on ARCH_PUV3 1644 help 1645 This enables support for the RTC in the PKUnity-v3 SoCs. 1646 1647 This drive can also be built as a module. If so, the module 1648 will be called rtc-puv3. 1649 1650config RTC_DRV_LOONGSON1 1651 tristate "loongson1 RTC support" 1652 depends on MACH_LOONGSON32 1653 help 1654 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year 1655 counter) to be used as a RTC. 1656 1657 This driver can also be built as a module. If so, the module 1658 will be called rtc-ls1x. 1659 1660config RTC_DRV_MXC 1661 tristate "Freescale MXC Real Time Clock" 1662 depends on ARCH_MXC 1663 help 1664 If you say yes here you get support for the Freescale MXC 1665 RTC module. 1666 1667 This driver can also be built as a module, if so, the module 1668 will be called "rtc-mxc". 1669 1670config RTC_DRV_MXC_V2 1671 tristate "Freescale MXC Real Time Clock for i.MX53" 1672 depends on ARCH_MXC 1673 help 1674 If you say yes here you get support for the Freescale MXC 1675 SRTC module in i.MX53 processor. 1676 1677 This driver can also be built as a module, if so, the module 1678 will be called "rtc-mxc_v2". 1679 1680config RTC_DRV_SNVS 1681 tristate "Freescale SNVS RTC support" 1682 select REGMAP_MMIO 1683 depends on HAS_IOMEM 1684 depends on OF 1685 help 1686 If you say yes here you get support for the Freescale SNVS 1687 Low Power (LP) RTC module. 1688 1689 This driver can also be built as a module, if so, the module 1690 will be called "rtc-snvs". 1691 1692config RTC_DRV_SIRFSOC 1693 tristate "SiRFSOC RTC" 1694 depends on ARCH_SIRF 1695 help 1696 Say "yes" here to support the real time clock on SiRF SOC chips. 1697 This driver can also be built as a module called rtc-sirfsoc. 1698 1699config RTC_DRV_ST_LPC 1700 tristate "STMicroelectronics LPC RTC" 1701 depends on ARCH_STI 1702 depends on OF 1703 help 1704 Say Y here to include STMicroelectronics Low Power Controller 1705 (LPC) based RTC support. 1706 1707 To compile this driver as a module, choose M here: the 1708 module will be called rtc-st-lpc. 1709 1710config RTC_DRV_MOXART 1711 tristate "MOXA ART RTC" 1712 depends on ARCH_MOXART || COMPILE_TEST 1713 help 1714 If you say yes here you get support for the MOXA ART 1715 RTC module. 1716 1717 This driver can also be built as a module. If so, the module 1718 will be called rtc-moxart 1719 1720config RTC_DRV_MT6397 1721 tristate "MediaTek PMIC based RTC" 1722 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN) 1723 help 1724 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek 1725 MT6397 PMIC. You should enable MT6397 PMIC MFD before select 1726 MediaTek(R) RTC driver. 1727 1728 If you want to use MediaTek(R) RTC interface, select Y or M here. 1729 1730config RTC_DRV_MT7622 1731 tristate "MediaTek SoC based RTC" 1732 depends on ARCH_MEDIATEK || COMPILE_TEST 1733 help 1734 This enables support for the real time clock built in the MediaTek 1735 SoCs. 1736 1737 This drive can also be built as a module. If so, the module 1738 will be called rtc-mt7622. 1739 1740config RTC_DRV_XGENE 1741 tristate "APM X-Gene RTC" 1742 depends on HAS_IOMEM 1743 depends on ARCH_XGENE || COMPILE_TEST 1744 help 1745 If you say yes here you get support for the APM X-Gene SoC real time 1746 clock. 1747 1748 This driver can also be built as a module, if so, the module 1749 will be called "rtc-xgene". 1750 1751config RTC_DRV_PIC32 1752 tristate "Microchip PIC32 RTC" 1753 depends on MACH_PIC32 1754 default y 1755 help 1756 If you say yes here you get support for the PIC32 RTC module. 1757 1758 This driver can also be built as a module. If so, the module 1759 will be called rtc-pic32 1760 1761config RTC_DRV_R7301 1762 tristate "EPSON TOYOCOM RTC-7301SF/DG" 1763 select REGMAP_MMIO 1764 depends on OF && HAS_IOMEM 1765 help 1766 If you say yes here you get support for the EPSON TOYOCOM 1767 RTC-7301SF/DG chips. 1768 1769 This driver can also be built as a module. If so, the module 1770 will be called rtc-r7301. 1771 1772config RTC_DRV_STM32 1773 tristate "STM32 RTC" 1774 select REGMAP_MMIO 1775 depends on ARCH_STM32 || COMPILE_TEST 1776 help 1777 If you say yes here you get support for the STM32 On-Chip 1778 Real Time Clock. 1779 1780 This driver can also be built as a module, if so, the module 1781 will be called "rtc-stm32". 1782 1783config RTC_DRV_CPCAP 1784 depends on MFD_CPCAP 1785 tristate "Motorola CPCAP RTC" 1786 help 1787 Say y here for CPCAP rtc found on some Motorola phones 1788 and tablets such as Droid 4. 1789 1790config RTC_DRV_RTD119X 1791 bool "Realtek RTD129x RTC" 1792 depends on ARCH_REALTEK || COMPILE_TEST 1793 default ARCH_REALTEK 1794 help 1795 If you say yes here, you get support for the RTD1295 SoC 1796 Real Time Clock. 1797 1798comment "HID Sensor RTC drivers" 1799 1800config RTC_DRV_HID_SENSOR_TIME 1801 tristate "HID Sensor Time" 1802 depends on USB_HID 1803 select IIO 1804 select HID_SENSOR_HUB 1805 select HID_SENSOR_IIO_COMMON 1806 help 1807 Say yes here to build support for the HID Sensors of type Time. 1808 This drivers makes such sensors available as RTCs. 1809 1810 If this driver is compiled as a module, it will be named 1811 rtc-hid-sensor-time. 1812 1813config RTC_DRV_GOLDFISH 1814 tristate "Goldfish Real Time Clock" 1815 depends on MIPS && (GOLDFISH || COMPILE_TEST) 1816 help 1817 Say yes to enable RTC driver for the Goldfish based virtual platform. 1818 1819 Goldfish is a code name for the virtual platform developed by Google 1820 for Android emulation. 1821 1822endif # RTC_CLASS 1823