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