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