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_NCT3018Y 410 tristate "Nuvoton NCT3018Y" 411 depends on OF 412 help 413 If you say yes here you get support for the Nuvoton NCT3018Y I2C RTC 414 chip. 415 416 This driver can also be built as a module, if so, the module will be 417 called "rtc-nct3018y". 418 419config RTC_DRV_NCT6694 420 tristate "Nuvoton NCT6694 RTC support" 421 depends on MFD_NCT6694 422 help 423 If you say yes to this option, support will be included for Nuvoton 424 NCT6694, a USB device to RTC. 425 426 This driver can also be built as a module. If so, the module will 427 be called rtc-nct6694. 428 429config RTC_DRV_RK808 430 tristate "Rockchip RK805/RK808/RK809/RK817/RK818 RTC" 431 depends on MFD_RK8XX 432 help 433 If you say yes here you will get support for the 434 RTC of RK805, RK809 and RK817, RK808 and RK818 PMIC. 435 436 This driver can also be built as a module. If so, the module 437 will be called rk808-rtc. 438 439config RTC_DRV_RS5C372 440 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A" 441 help 442 If you say yes here you get support for the 443 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. 444 445 This driver can also be built as a module. If so, the module 446 will be called rtc-rs5c372. 447 448config RTC_DRV_ISL1208 449 tristate "Intersil ISL1208" 450 help 451 If you say yes here you get support for the 452 Intersil ISL1208 RTC chip. 453 454 This driver can also be built as a module. If so, the module 455 will be called rtc-isl1208. 456 457config RTC_DRV_ISL12022 458 tristate "Intersil ISL12022" 459 select REGMAP_I2C 460 help 461 If you say yes here you get support for the 462 Intersil ISL12022 RTC chip. 463 464 This driver can also be built as a module. If so, the module 465 will be called rtc-isl12022. 466 467config RTC_DRV_ISL12026 468 tristate "Intersil ISL12026" 469 depends on OF 470 help 471 If you say yes here you get support for the 472 Intersil ISL12026 RTC chip. 473 474 This driver can also be built as a module. If so, the module 475 will be called rtc-isl12026. 476 477config RTC_DRV_X1205 478 tristate "Xicor/Intersil X1205" 479 help 480 If you say yes here you get support for the 481 Xicor/Intersil X1205 RTC chip. 482 483 This driver can also be built as a module. If so, the module 484 will be called rtc-x1205. 485 486config RTC_DRV_PCF8523 487 tristate "NXP PCF8523" 488 select REGMAP_I2C 489 help 490 If you say yes here you get support for the NXP PCF8523 RTC 491 chips. 492 493 This driver can also be built as a module. If so, the module 494 will be called rtc-pcf8523. 495 496config RTC_DRV_PCF85363 497 tristate "NXP PCF85363" 498 select REGMAP_I2C 499 help 500 If you say yes here you get support for the PCF85363 RTC chip. 501 502 This driver can also be built as a module. If so, the module 503 will be called rtc-pcf85363. 504 505 The nvmem interface will be named pcf85363-#, where # is the 506 zero-based instance number. 507 508config RTC_DRV_PCF8563 509 tristate "Philips PCF8563/Epson RTC8564" 510 select REGMAP_I2C 511 help 512 If you say yes here you get support for the 513 Philips PCF8563 RTC chip. The Epson RTC8564 514 should work as well. 515 516 This driver can also be built as a module. If so, the module 517 will be called rtc-pcf8563. 518 519config RTC_DRV_PCF8583 520 tristate "Philips PCF8583" 521 help 522 If you say yes here you get support for the Philips PCF8583 523 RTC chip found on Acorn RiscPCs. This driver supports the 524 platform specific method of retrieving the current year from 525 the RTC's SRAM. It will work on other platforms with the same 526 chip, but the year will probably have to be tweaked. 527 528 This driver can also be built as a module. If so, the module 529 will be called rtc-pcf8583. 530 531config RTC_DRV_M41T80 532 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible" 533 help 534 If you say Y here you will get support for the ST M41T60 535 and M41T80 RTC chips series. Currently, the following chips are 536 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84, 537 M41ST85, M41ST87, and MicroCrystal RV4162. 538 539 This driver can also be built as a module. If so, the module 540 will be called rtc-m41t80. 541 542config RTC_DRV_M41T80_WDT 543 bool "ST M41T65/M41T80 series RTC watchdog timer" 544 depends on RTC_DRV_M41T80 545 help 546 If you say Y here you will get support for the 547 watchdog timer in the ST M41T60 and M41T80 RTC chips series. 548 549config RTC_DRV_BD70528 550 tristate "ROHM BD71815 and BD71828 PMIC RTC" 551 depends on MFD_ROHM_BD71828 552 help 553 If you say Y here you will get support for the RTC 554 block on ROHM BD71815 and BD71828 Power Management IC. 555 556 This driver can also be built as a module. If so, the module 557 will be called rtc-bd70528. 558 559config RTC_DRV_BQ32K 560 tristate "TI BQ32000" 561 help 562 If you say Y here you will get support for the TI 563 BQ32000 I2C RTC chip. 564 565 This driver can also be built as a module. If so, the module 566 will be called rtc-bq32k. 567 568config RTC_DRV_TWL92330 569 bool "TI TWL92330/Menelaus" 570 depends on MENELAUS 571 help 572 If you say yes here you get support for the RTC on the 573 TWL92330 "Menelaus" power management chip, used with OMAP2 574 platforms. The support is integrated with the rest of 575 the Menelaus driver; it's not separate module. 576 577config RTC_DRV_TWL4030 578 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0" 579 depends on TWL4030_CORE 580 depends on OF 581 help 582 If you say yes here you get support for the RTC on the 583 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms. 584 585 This driver can also be built as a module. If so, the module 586 will be called rtc-twl. 587 588config RTC_DRV_PALMAS 589 tristate "TI Palmas RTC driver" 590 depends on MFD_PALMAS 591 help 592 If you say yes here you get support for the RTC of TI PALMA series PMIC 593 chips. 594 595 This driver can also be built as a module. If so, the module 596 will be called rtc-palma. 597 598config RTC_DRV_TPS6586X 599 tristate "TI TPS6586X RTC driver" 600 depends on MFD_TPS6586X 601 help 602 TI Power Management IC TPS6586X supports RTC functionality 603 along with alarm. This driver supports the RTC driver for 604 the TPS6586X RTC module. 605 606config RTC_DRV_TPS6594 607 tristate "TI TPS6594 RTC driver" 608 depends on MFD_TPS6594 609 default MFD_TPS6594 610 help 611 TI Power Management IC TPS6594 supports RTC functionality 612 along with alarm. This driver supports the RTC driver for 613 the TPS6594 RTC module. 614 615 This driver can also be built as a module. If so, the module 616 will be called rtc-tps6594. 617 618config RTC_DRV_TPS65910 619 tristate "TI TPS65910 RTC driver" 620 depends on MFD_TPS65910 621 help 622 If you say yes here you get support for the RTC on the 623 TPS65910 chips. 624 625 This driver can also be built as a module. If so, the module 626 will be called rtc-tps65910. 627 628config RTC_DRV_RC5T583 629 tristate "RICOH 5T583 RTC driver" 630 depends on MFD_RC5T583 631 help 632 If you say yes here you get support for the RTC on the 633 RICOH 5T583 chips. 634 635 This driver can also be built as a module. If so, the module 636 will be called rtc-rc5t583. 637 638config RTC_DRV_RC5T619 639 tristate "RICOH RC5T619 RTC driver" 640 depends on MFD_RN5T618 641 help 642 If you say yes here you get support for the RTC on the 643 RICOH RC5T619 chips. 644 645 This driver can also be built as a module. If so, the module 646 will be called rtc-rc5t619. 647 648config RTC_DRV_S35390A 649 tristate "Seiko Instruments S-35390A" 650 select BITREVERSE 651 help 652 If you say yes here you will get support for the Seiko 653 Instruments S-35390A. 654 655 This driver can also be built as a module. If so the module 656 will be called rtc-s35390a. 657 658config RTC_DRV_FM3130 659 tristate "Ramtron FM3130" 660 help 661 If you say Y here you will get support for the 662 Ramtron FM3130 RTC chips. 663 Ramtron FM3130 is a chip with two separate devices inside, 664 RTC clock and FRAM. This driver provides only RTC functionality. 665 666 This driver can also be built as a module. If so the module 667 will be called rtc-fm3130. 668 669config RTC_DRV_RX8010 670 tristate "Epson RX8010SJ" 671 select REGMAP_I2C 672 help 673 If you say yes here you get support for the Epson RX8010SJ RTC 674 chip. 675 676 This driver can also be built as a module. If so, the module 677 will be called rtc-rx8010. 678 679config RTC_DRV_RX8111 680 tristate "Epson RX8111" 681 select REGMAP_I2C 682 depends on I2C 683 help 684 If you say yes here you will get support for the Epson RX8111 RTC. 685 686 This driver can also be built as a module. If so, the module will be 687 called rtc-rx8111. 688 689config RTC_DRV_RX8581 690 tristate "Epson RX-8571/RX-8581" 691 select REGMAP_I2C 692 help 693 If you say yes here you will get support for the Epson RX-8571/ 694 RX-8581. 695 696 This driver can also be built as a module. If so the module 697 will be called rtc-rx8581. 698 699config RTC_DRV_RX8025 700 tristate "Epson RX-8025SA/NB" 701 help 702 If you say yes here you get support for the Epson 703 RX-8025SA/NB RTC chips. 704 705 This driver can also be built as a module. If so, the module 706 will be called rtc-rx8025. 707 708config RTC_DRV_EM3027 709 tristate "EM Microelectronic EM3027" 710 help 711 If you say yes here you get support for the EM 712 Microelectronic EM3027 RTC chips. 713 714 This driver can also be built as a module. If so, the module 715 will be called rtc-em3027. 716 717config RTC_DRV_RV3028 718 tristate "Micro Crystal RV3028" 719 select REGMAP_I2C 720 help 721 If you say yes here you get support for the Micro Crystal 722 RV3028. 723 724 This driver can also be built as a module. If so, the module 725 will be called rtc-rv3028. 726 727config RTC_DRV_RV3032 728 tristate "Micro Crystal RV3032" 729 select REGMAP_I2C 730 help 731 If you say yes here you get support for the Micro Crystal 732 RV3032. 733 734 This driver can also be built as a module. If so, the module 735 will be called rtc-rv3032. 736 737config RTC_DRV_RV8803 738 tristate "Micro Crystal RV8803, Epson RX8900" 739 help 740 If you say yes here you get support for the Micro Crystal RV8803 and 741 Epson RX8900 RTC chips. 742 743 This driver can also be built as a module. If so, the module 744 will be called rtc-rv8803. 745 746config RTC_DRV_S5M 747 tristate "Samsung S2M/S5M series" 748 depends on MFD_SEC_CORE || COMPILE_TEST 749 select REGMAP_IRQ 750 select REGMAP_I2C 751 help 752 If you say yes here you will get support for the 753 RTC of Samsung S2MPS14 and S5M PMIC series. 754 755 This driver can also be built as a module. If so, the module 756 will be called rtc-s5m. 757 758config RTC_DRV_SD2405AL 759 tristate "DFRobot SD2405AL" 760 select REGMAP_I2C 761 help 762 If you say yes here you will get support for the 763 DFRobot SD2405AL I2C RTC Module. 764 765 This driver can also be built as a module. If so, the module 766 will be called rtc-sd2405al. 767 768config RTC_DRV_SD3078 769 tristate "ZXW Shenzhen whwave SD3078" 770 select REGMAP_I2C 771 help 772 If you say yes here you get support for the ZXW Shenzhen whwave 773 SD3078 RTC chips. 774 775 This driver can also be built as a module. If so, the module 776 will be called rtc-sd3078 777 778endif # I2C 779 780comment "SPI RTC drivers" 781 782if SPI_MASTER 783 784config RTC_DRV_M41T93 785 tristate "ST M41T93" 786 help 787 If you say yes here you will get support for the 788 ST M41T93 SPI RTC chip. 789 790 This driver can also be built as a module. If so, the module 791 will be called rtc-m41t93. 792 793config RTC_DRV_M41T94 794 tristate "ST M41T94" 795 help 796 If you say yes here you will get support for the 797 ST M41T94 SPI RTC chip. 798 799 This driver can also be built as a module. If so, the module 800 will be called rtc-m41t94. 801 802config RTC_DRV_DS1302 803 tristate "Dallas/Maxim DS1302" 804 depends on SPI 805 help 806 If you say yes here you get support for the Dallas DS1302 RTC chips. 807 808 This driver can also be built as a module. If so, the module 809 will be called rtc-ds1302. 810 811config RTC_DRV_DS1305 812 tristate "Dallas/Maxim DS1305/DS1306" 813 help 814 Select this driver to get support for the Dallas/Maxim DS1305 815 and DS1306 real time clock chips. These support a trickle 816 charger, alarms, and NVRAM in addition to the clock. 817 818 This driver can also be built as a module. If so, the module 819 will be called rtc-ds1305. 820 821config RTC_DRV_DS1343 822 select REGMAP_SPI 823 tristate "Dallas/Maxim DS1343/DS1344" 824 help 825 If you say yes here you get support for the 826 Dallas/Maxim DS1343 and DS1344 real time clock chips. 827 Support for trickle charger, alarm is provided. 828 829 This driver can also be built as a module. If so, the module 830 will be called rtc-ds1343. 831 832config RTC_DRV_DS1347 833 select REGMAP_SPI 834 tristate "Dallas/Maxim DS1347" 835 help 836 If you say yes here you get support for the 837 Dallas/Maxim DS1347 chips. 838 839 This driver only supports the RTC feature, and not other chip 840 features such as alarms. 841 842 This driver can also be built as a module. If so, the module 843 will be called rtc-ds1347. 844 845config RTC_DRV_DS1390 846 tristate "Dallas/Maxim DS1390/93/94" 847 help 848 If you say yes here you get support for the 849 Dallas/Maxim DS1390/93/94 chips. 850 851 This driver supports the RTC feature and trickle charging but not 852 other chip features such as alarms. 853 854 This driver can also be built as a module. If so, the module 855 will be called rtc-ds1390. 856 857config RTC_DRV_MAX6916 858 tristate "Maxim MAX6916" 859 help 860 If you say yes here you will get support for the 861 Maxim MAX6916 SPI RTC chip. 862 863 This driver only supports the RTC feature, and not other chip 864 features such as alarms. 865 866 This driver can also be built as a module. If so, the module 867 will be called rtc-max6916. 868 869config RTC_DRV_R9701 870 tristate "Epson RTC-9701JE" 871 help 872 If you say yes here you will get support for the 873 Epson RTC-9701JE SPI RTC chip. 874 875 This driver can also be built as a module. If so, the module 876 will be called rtc-r9701. 877 878config RTC_DRV_RX4581 879 tristate "Epson RX-4581" 880 help 881 If you say yes here you will get support for the Epson RX-4581. 882 883 This driver can also be built as a module. If so the module 884 will be called rtc-rx4581. 885 886config RTC_DRV_RS5C348 887 tristate "Ricoh RS5C348A/B" 888 help 889 If you say yes here you get support for the 890 Ricoh RS5C348A and RS5C348B RTC chips. 891 892 This driver can also be built as a module. If so, the module 893 will be called rtc-rs5c348. 894 895config RTC_DRV_MAX6902 896 tristate "Maxim MAX6902" 897 help 898 If you say yes here you will get support for the 899 Maxim MAX6902 SPI RTC chip. 900 901 This driver can also be built as a module. If so, the module 902 will be called rtc-max6902. 903 904config RTC_DRV_PCF2123 905 tristate "NXP PCF2123" 906 select REGMAP_SPI 907 help 908 If you say yes here you get support for the NXP PCF2123 909 RTC chip. 910 911 This driver can also be built as a module. If so, the module 912 will be called rtc-pcf2123. 913 914config RTC_DRV_MCP795 915 tristate "Microchip MCP795" 916 help 917 If you say yes here you will get support for the Microchip MCP795. 918 919 This driver can also be built as a module. If so the module 920 will be called rtc-mcp795. 921 922endif # SPI_MASTER 923 924# 925# Helper to resolve issues with configs that have SPI enabled but I2C 926# modular. See SND_SOC_I2C_AND_SPI for more information 927# 928config RTC_I2C_AND_SPI 929 tristate 930 default m if I2C=m 931 default y if I2C=y 932 default y if SPI_MASTER=y 933 934comment "SPI and I2C RTC drivers" 935 936config RTC_DRV_DS3232 937 tristate "Dallas/Maxim DS3232/DS3234" 938 depends on RTC_I2C_AND_SPI 939 select REGMAP_I2C if I2C 940 select REGMAP_SPI if SPI_MASTER 941 help 942 If you say yes here you get support for Dallas Semiconductor 943 DS3232 and DS3234 real-time clock chips. If an interrupt is associated 944 with the device, the alarm functionality is supported. 945 946 This driver can also be built as a module. If so, the module 947 will be called rtc-ds3232. 948 949config RTC_DRV_DS3232_HWMON 950 bool "HWMON support for Dallas/Maxim DS3232/DS3234" 951 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m) 952 default y 953 help 954 Say Y here if you want to expose temperature sensor data on 955 rtc-ds3232 956 957config RTC_DRV_PCF2127 958 tristate "NXP PCF2127" 959 depends on RTC_I2C_AND_SPI 960 select REGMAP_I2C if I2C 961 select REGMAP_SPI if SPI_MASTER 962 select WATCHDOG_CORE if WATCHDOG 963 help 964 If you say yes here you get support for the NXP PCF2127/29/31 RTC 965 chips with integrated quartz crystal for industrial applications. 966 These chips also have watchdog timer and tamper switch detection 967 features. 968 969 PCF2127 has an additional feature of 512 bytes battery backed 970 memory that's accessible using nvmem interface. 971 972 This driver can also be built as a module. If so, the module 973 will be called rtc-pcf2127. 974 975config RTC_DRV_PCF85063 976 tristate "NXP PCF85063" 977 depends on RTC_I2C_AND_SPI 978 select REGMAP_I2C if I2C 979 select REGMAP_SPI if SPI_MASTER 980 help 981 If you say yes here you get support for the PCF85063 and RV8063 982 RTC chips. 983 984 This driver can also be built as a module. If so, the module 985 will be called rtc-pcf85063. 986 987config RTC_DRV_RV3029C2 988 tristate "Micro Crystal RV3029/3049" 989 depends on RTC_I2C_AND_SPI 990 select REGMAP_I2C if I2C 991 select REGMAP_SPI if SPI_MASTER 992 help 993 If you say yes here you get support for the Micro Crystal 994 RV3029 and RV3049 RTC chips. 995 996 This driver can also be built as a module. If so, the module 997 will be called rtc-rv3029c2. 998 999config RTC_DRV_RV3029_HWMON 1000 bool "HWMON support for RV3029/3049" 1001 depends on RTC_DRV_RV3029C2 && HWMON 1002 depends on !(RTC_DRV_RV3029C2=y && HWMON=m) 1003 default y 1004 help 1005 Say Y here if you want to expose temperature sensor data on 1006 rtc-rv3029. 1007 1008config RTC_DRV_RX6110 1009 tristate "Epson RX-6110" 1010 depends on RTC_I2C_AND_SPI 1011 select REGMAP_SPI if SPI_MASTER 1012 select REGMAP_I2C if I2C 1013 help 1014 If you say yes here you will get support for the Epson RX-6110. 1015 1016 This driver can also be built as a module. If so the module 1017 will be called rtc-rx6110. 1018 1019comment "Platform RTC drivers" 1020 1021# this 'CMOS' RTC driver is arch dependent because it requires 1022# <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a 1023# global rtc_lock ... it's not yet just another platform_device. 1024 1025config RTC_DRV_CMOS 1026 tristate "PC-style 'CMOS'" 1027 depends on X86 || ARM || PPC || MIPS || SPARC64 1028 depends on HAS_IOPORT || MACH_DECSTATION 1029 default y if X86 1030 select RTC_MC146818_LIB 1031 help 1032 Say "yes" here to get direct support for the real time clock 1033 found in every PC or ACPI-based system, and some other boards. 1034 Specifically the original MC146818, compatibles like those in 1035 PC south bridges, the DS12887 or M48T86, some multifunction 1036 or LPC bus chips, and so on. 1037 1038 Your system will need to define the platform device used by 1039 this driver, otherwise it won't be accessible. This means 1040 you can safely enable this driver if you don't know whether 1041 or not your board has this kind of hardware. 1042 1043 This driver can also be built as a module. If so, the module 1044 will be called rtc-cmos. 1045 1046config RTC_DRV_ALPHA 1047 bool "Alpha PC-style CMOS" 1048 depends on ALPHA 1049 depends on HAS_IOPORT 1050 select RTC_MC146818_LIB 1051 default y 1052 help 1053 Direct support for the real-time clock found on every Alpha 1054 system, specifically MC146818 compatibles. If in doubt, say Y. 1055 1056config RTC_DRV_DS1216 1057 tristate "Dallas DS1216" 1058 depends on SNI_RM 1059 help 1060 If you say yes here you get support for the Dallas DS1216 RTC chips. 1061 1062config RTC_DRV_DS1286 1063 tristate "Dallas DS1286" 1064 depends on HAS_IOMEM 1065 help 1066 If you say yes here you get support for the Dallas DS1286 RTC chips. 1067 1068config RTC_DRV_DS1511 1069 tristate "Dallas DS1511" 1070 depends on HAS_IOMEM 1071 help 1072 If you say yes here you get support for the 1073 Dallas DS1511 timekeeping/watchdog chip. 1074 1075 This driver can also be built as a module. If so, the module 1076 will be called rtc-ds1511. 1077 1078config RTC_DRV_DS1553 1079 tristate "Maxim/Dallas DS1553" 1080 depends on HAS_IOMEM 1081 help 1082 If you say yes here you get support for the 1083 Maxim/Dallas DS1553 timekeeping chip. 1084 1085 This driver can also be built as a module. If so, the module 1086 will be called rtc-ds1553. 1087 1088config RTC_DRV_DS1685_FAMILY 1089 tristate "Dallas/Maxim DS1685 Family" 1090 depends on HAS_IOMEM 1091 help 1092 If you say yes here you get support for the Dallas/Maxim DS1685 1093 family of real time chips. This family includes the DS1685/DS1687, 1094 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and 1095 DS17885/DS17887 chips. 1096 1097 This driver can also be built as a module. If so, the module 1098 will be called rtc-ds1685. 1099 1100choice 1101 prompt "Subtype" 1102 depends on RTC_DRV_DS1685_FAMILY 1103 default RTC_DRV_DS1685 1104 1105config RTC_DRV_DS1685 1106 bool "DS1685/DS1687" 1107 help 1108 This enables support for the Dallas/Maxim DS1685/DS1687 real time 1109 clock chip. 1110 1111 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30) 1112 systems, as well as EPPC-405-UC modules by electronic system design 1113 GmbH. 1114 1115config RTC_DRV_DS1689 1116 bool "DS1689/DS1693" 1117 help 1118 This enables support for the Dallas/Maxim DS1689/DS1693 real time 1119 clock chip. 1120 1121 This is an older RTC chip, supplanted by the DS1685/DS1687 above, 1122 which supports a few minor features such as Vcc, Vbat, and Power 1123 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number. 1124 1125 It also works for the even older DS1688/DS1691 RTC chips, which are 1126 virtually the same and carry the same model number. Both chips 1127 have 114 bytes of user NVRAM. 1128 1129config RTC_DRV_DS17285 1130 bool "DS17285/DS17287" 1131 help 1132 This enables support for the Dallas/Maxim DS17285/DS17287 real time 1133 clock chip. 1134 1135 This chip features 2kb of extended NV-SRAM. It may possibly be 1136 found in some SGI O2 systems (rare). 1137 1138config RTC_DRV_DS17485 1139 bool "DS17485/DS17487" 1140 help 1141 This enables support for the Dallas/Maxim DS17485/DS17487 real time 1142 clock chip. 1143 1144 This chip features 4kb of extended NV-SRAM. 1145 1146config RTC_DRV_DS17885 1147 bool "DS17885/DS17887" 1148 help 1149 This enables support for the Dallas/Maxim DS17885/DS17887 real time 1150 clock chip. 1151 1152 This chip features 8kb of extended NV-SRAM. 1153 1154endchoice 1155 1156config RTC_DRV_DS1742 1157 tristate "Maxim/Dallas DS1742/1743" 1158 depends on HAS_IOMEM 1159 help 1160 If you say yes here you get support for the 1161 Maxim/Dallas DS1742/1743 timekeeping chip. 1162 1163 This driver can also be built as a module. If so, the module 1164 will be called rtc-ds1742. 1165 1166config RTC_DRV_DS2404 1167 tristate "Maxim/Dallas DS2404" 1168 help 1169 If you say yes here you get support for the 1170 Dallas DS2404 RTC chip. 1171 1172 This driver can also be built as a module. If so, the module 1173 will be called rtc-ds2404. 1174 1175config RTC_DRV_DA9052 1176 tristate "Dialog DA9052/DA9053 RTC" 1177 depends on PMIC_DA9052 1178 help 1179 Say y here to support the RTC driver for Dialog Semiconductor 1180 DA9052-BC and DA9053-AA/Bx PMICs. 1181 1182config RTC_DRV_DA9055 1183 tristate "Dialog Semiconductor DA9055 RTC" 1184 depends on MFD_DA9055 1185 help 1186 If you say yes here you will get support for the 1187 RTC of the Dialog DA9055 PMIC. 1188 1189 This driver can also be built as a module. If so, the module 1190 will be called rtc-da9055 1191 1192config RTC_DRV_DA9063 1193 tristate "Dialog Semiconductor DA9063/DA9062 RTC" 1194 depends on MFD_DA9063 || MFD_DA9062 1195 help 1196 If you say yes here you will get support for the RTC subsystem 1197 for the Dialog Semiconductor PMIC chips DA9063 and DA9062. 1198 1199 This driver can also be built as a module. If so, the module 1200 will be called "rtc-da9063". 1201 1202config RTC_DRV_EFI 1203 tristate "EFI RTC" 1204 depends on EFI && !X86 1205 help 1206 If you say yes here you will get support for the EFI 1207 Real Time Clock. 1208 1209 This driver can also be built as a module. If so, the module 1210 will be called rtc-efi. 1211 1212config RTC_DRV_STK17TA8 1213 tristate "Simtek STK17TA8" 1214 depends on HAS_IOMEM 1215 help 1216 If you say yes here you get support for the 1217 Simtek STK17TA8 timekeeping chip. 1218 1219 This driver can also be built as a module. If so, the module 1220 will be called rtc-stk17ta8. 1221 1222config RTC_DRV_M48T86 1223 tristate "ST M48T86/Dallas DS12887" 1224 depends on HAS_IOMEM 1225 help 1226 If you say Y here you will get support for the 1227 ST M48T86 and Dallas DS12887 RTC chips. 1228 1229 This driver can also be built as a module. If so, the module 1230 will be called rtc-m48t86. 1231 1232config RTC_DRV_M48T35 1233 tristate "ST M48T35" 1234 depends on HAS_IOMEM 1235 help 1236 If you say Y here you will get support for the 1237 ST M48T35 RTC chip. 1238 1239 This driver can also be built as a module, if so, the module 1240 will be called "rtc-m48t35". 1241 1242config RTC_DRV_M48T59 1243 tristate "ST M48T59/M48T08/M48T02" 1244 depends on HAS_IOMEM 1245 help 1246 If you say Y here you will get support for the 1247 ST M48T59 RTC chip and compatible ST M48T08 and M48T02. 1248 1249 These chips are usually found in Sun SPARC and UltraSPARC 1250 workstations. 1251 1252 This driver can also be built as a module, if so, the module 1253 will be called "rtc-m48t59". 1254 1255config RTC_DRV_MSM6242 1256 tristate "Oki MSM6242" 1257 depends on HAS_IOMEM 1258 help 1259 If you say yes here you get support for the Oki MSM6242 1260 timekeeping chip. It is used in some Amiga models (e.g. A2000). 1261 1262 This driver can also be built as a module. If so, the module 1263 will be called rtc-msm6242. 1264 1265config RTC_DRV_BQ4802 1266 tristate "TI BQ4802" 1267 depends on HAS_IOMEM && HAS_IOPORT 1268 depends on SPARC || COMPILE_TEST 1269 help 1270 If you say Y here you will get support for the TI 1271 BQ4802 RTC chip. 1272 1273 This driver can also be built as a module. If so, the module 1274 will be called rtc-bq4802. 1275 1276config RTC_DRV_RP5C01 1277 tristate "Ricoh RP5C01" 1278 depends on HAS_IOMEM 1279 help 1280 If you say yes here you get support for the Ricoh RP5C01 1281 timekeeping chip. It is used in some Amiga models (e.g. A3000 1282 and A4000). 1283 1284 This driver can also be built as a module. If so, the module 1285 will be called rtc-rp5c01. 1286 1287config RTC_DRV_GAMECUBE 1288 tristate "Nintendo GameCube, Wii and Wii U RTC" 1289 depends on GAMECUBE || WII || COMPILE_TEST 1290 select REGMAP 1291 help 1292 If you say yes here you will get support for the RTC subsystem 1293 of the Nintendo GameCube, Wii and Wii U. 1294 1295 This driver can also be built as a module. If so, the module 1296 will be called "rtc-gamecube". 1297 1298config RTC_DRV_WM831X 1299 tristate "Wolfson Microelectronics WM831x RTC" 1300 depends on MFD_WM831X 1301 help 1302 If you say yes here you will get support for the RTC subsystem 1303 of the Wolfson Microelectronics WM831X series PMICs. 1304 1305 This driver can also be built as a module. If so, the module 1306 will be called "rtc-wm831x". 1307 1308config RTC_DRV_WM8350 1309 tristate "Wolfson Microelectronics WM8350 RTC" 1310 depends on MFD_WM8350 1311 help 1312 If you say yes here you will get support for the RTC subsystem 1313 of the Wolfson Microelectronics WM8350. 1314 1315 This driver can also be built as a module. If so, the module 1316 will be called "rtc-wm8350". 1317 1318config RTC_DRV_SC27XX 1319 tristate "Spreadtrum SC27xx RTC" 1320 depends on MFD_SC27XX_PMIC || COMPILE_TEST 1321 help 1322 If you say Y here you will get support for the RTC subsystem 1323 of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs 1324 includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips. 1325 1326 This driver can also be built as a module. If so, the module 1327 will be called rtc-sc27xx. 1328 1329config RTC_DRV_SPEAR 1330 tristate "SPEAR ST RTC" 1331 depends on PLAT_SPEAR || COMPILE_TEST 1332 default PLAT_SPEAR 1333 help 1334 If you say Y here you will get support for the RTC found on 1335 spear 1336 1337config RTC_DRV_AB8500 1338 tristate "ST-Ericsson AB8500 RTC" 1339 depends on AB8500_CORE 1340 select RTC_INTF_DEV 1341 select RTC_INTF_DEV_UIE_EMUL 1342 help 1343 Select this to enable the ST-Ericsson AB8500 power management IC RTC 1344 support. This chip contains a battery- and capacitor-backed RTC. 1345 1346config RTC_DRV_OPAL 1347 tristate "IBM OPAL RTC driver" 1348 depends on PPC_POWERNV 1349 default y 1350 help 1351 If you say yes here you get support for the PowerNV platform RTC 1352 driver based on OPAL interfaces. 1353 1354 This driver can also be built as a module. If so, the module 1355 will be called rtc-opal. 1356 1357config RTC_DRV_OPTEE 1358 tristate "OP-TEE based RTC driver" 1359 depends on OPTEE 1360 help 1361 Select this to get support for OP-TEE based RTC control on SoCs where 1362 RTC are not accessible to the normal world (Linux). 1363 1364 This driver can also be built as a module. If so, the module 1365 will be called rtc-optee. 1366 1367config RTC_DRV_ZYNQMP 1368 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC" 1369 depends on OF && HAS_IOMEM 1370 help 1371 If you say yes here you get support for the RTC controller found on 1372 Xilinx Zynq Ultrascale+ MPSoC. 1373 1374config RTC_DRV_CROS_EC 1375 tristate "Chrome OS EC RTC driver" 1376 depends on CROS_EC 1377 help 1378 If you say yes here you will get support for the 1379 Chrome OS Embedded Controller's RTC. 1380 1381 This driver can also be built as a module. If so, the module 1382 will be called rtc-cros-ec. 1383 1384config RTC_DRV_NTXEC 1385 tristate "Netronix embedded controller RTC" 1386 depends on MFD_NTXEC 1387 help 1388 Say yes here if you want to support the RTC functionality of the 1389 embedded controller found in certain e-book readers designed by the 1390 original design manufacturer Netronix. 1391 1392comment "on-CPU RTC drivers" 1393 1394config RTC_DRV_ASM9260 1395 tristate "Alphascale asm9260 RTC" 1396 depends on MACH_ASM9260 || COMPILE_TEST 1397 help 1398 If you say yes here you get support for the RTC on the 1399 Alphascale asm9260 SoC. 1400 1401 This driver can also be built as a module. If so, the module 1402 will be called rtc-asm9260. 1403 1404config RTC_DRV_CV1800 1405 tristate "Sophgo CV1800 RTC" 1406 depends on SOPHGO_CV1800_RTCSYS || COMPILE_TEST 1407 select MFD_SYSCON 1408 select REGMAP 1409 help 1410 If you say yes here you get support the RTC driver for Sophgo CV1800 1411 series SoC. 1412 1413 This driver can also be built as a module. If so, the module will be 1414 called rtc-cv1800. 1415 1416config RTC_DRV_DIGICOLOR 1417 tristate "Conexant Digicolor RTC" 1418 depends on ARCH_DIGICOLOR || COMPILE_TEST 1419 help 1420 If you say yes here you get support for the RTC on Conexant 1421 Digicolor platforms. This currently includes the CX92755 SoC. 1422 1423 This driver can also be built as a module. If so, the module 1424 will be called rtc-digicolor. 1425 1426config RTC_DRV_IMXDI 1427 tristate "Freescale IMX DryIce Real Time Clock" 1428 depends on ARCH_MXC || COMPILE_TEST 1429 depends on OF 1430 help 1431 Support for Freescale IMX DryIce RTC 1432 1433 This driver can also be built as a module, if so, the module 1434 will be called "rtc-imxdi". 1435 1436config RTC_DRV_FSL_FTM_ALARM 1437 tristate "Freescale FlexTimer alarm timer" 1438 depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST 1439 help 1440 For the FlexTimer in LS1012A, LS1021A, LS1028A, LS1043A, LS1046A, 1441 LS1088A, LS208xA, we can use FTM as the wakeup source. 1442 1443 Say y here to enable FTM alarm support. The FTM alarm provides 1444 alarm functions for wakeup system from deep sleep. 1445 1446 This driver can also be built as a module, if so, the module 1447 will be called "rtc-fsl-ftm-alarm". 1448 1449config RTC_DRV_MESON 1450 tristate "Amlogic Meson RTC" 1451 depends on (ARM && ARCH_MESON) || COMPILE_TEST 1452 select REGMAP_MMIO 1453 help 1454 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b 1455 and Meson8m2 SoCs. 1456 1457 This driver can also be built as a module, if so, the module 1458 will be called "rtc-meson". 1459 1460config RTC_DRV_MESON_VRTC 1461 tristate "Amlogic Meson Virtual RTC" 1462 depends on ARCH_MESON || COMPILE_TEST 1463 default m if ARCH_MESON 1464 help 1465 If you say yes here you will get support for the 1466 Virtual RTC of Amlogic SoCs. 1467 1468 This driver can also be built as a module. If so, the module 1469 will be called rtc-meson-vrtc. 1470 1471config RTC_DRV_OMAP 1472 tristate "TI OMAP Real Time Clock" 1473 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST 1474 depends on OF 1475 depends on PINCTRL 1476 select GENERIC_PINCONF 1477 help 1478 Say "yes" here to support the on chip real time clock 1479 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx. 1480 1481 This driver can also be built as a module, if so, module 1482 will be called rtc-omap. 1483 1484config RTC_DRV_S3C 1485 tristate "Samsung S3C series SoC RTC" 1486 depends on ARCH_EXYNOS || ARCH_S3C64XX || ARCH_S5PV210 || \ 1487 COMPILE_TEST 1488 help 1489 RTC (Realtime Clock) driver for the clock inbuilt into the 1490 Samsung S3C64XX series of SoCs. This can provide periodic 1491 interrupt rates from 1Hz to 64Hz for user programs, and 1492 wakeup from Alarm. 1493 1494 This driver can also be build as a module. If so, the module 1495 will be called rtc-s3c. 1496 1497config RTC_DRV_EP93XX 1498 tristate "Cirrus Logic EP93XX" 1499 depends on ARCH_EP93XX || COMPILE_TEST 1500 help 1501 If you say yes here you get support for the 1502 RTC embedded in the Cirrus Logic EP93XX processors. 1503 1504 This driver can also be built as a module. If so, the module 1505 will be called rtc-ep93xx. 1506 1507config RTC_DRV_SA1100 1508 tristate "SA11x0/PXA2xx/PXA910" 1509 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP 1510 help 1511 If you say Y here you will get access to the real time clock 1512 built into your SA11x0 or PXA2xx CPU. 1513 1514 To compile this driver as a module, choose M here: the 1515 module will be called rtc-sa1100. 1516 1517config RTC_DRV_SH 1518 tristate "SuperH On-Chip RTC" 1519 depends on SUPERH || ARCH_RENESAS 1520 help 1521 Say Y here to enable support for the on-chip RTC found in 1522 most SuperH processors. This RTC is also found in RZ/A SoCs. 1523 1524 To compile this driver as a module, choose M here: the 1525 module will be called rtc-sh. 1526 1527config RTC_DRV_SUNPLUS 1528 tristate "Sunplus SP7021 RTC" 1529 depends on SOC_SP7021 1530 help 1531 Say 'yes' to get support for the real-time clock present in 1532 Sunplus SP7021 - a SoC for industrial applications. It provides 1533 RTC status check, timer/alarm functionalities, user data 1534 reservation with the battery over 2.5V, RTC power status check 1535 and battery charge. 1536 1537 This driver can also be built as a module. If so, the module 1538 will be called rtc-sunplus. 1539 1540config RTC_DRV_PL030 1541 tristate "ARM AMBA PL030 RTC" 1542 depends on ARM_AMBA 1543 help 1544 If you say Y here you will get access to ARM AMBA 1545 PrimeCell PL030 RTC found on certain ARM SOCs. 1546 1547 To compile this driver as a module, choose M here: the 1548 module will be called rtc-pl030. 1549 1550config RTC_DRV_PL031 1551 tristate "ARM AMBA PL031 RTC" 1552 depends on ARM_AMBA 1553 help 1554 If you say Y here you will get access to ARM AMBA 1555 PrimeCell PL031 RTC found on certain ARM SOCs. 1556 1557 To compile this driver as a module, choose M here: the 1558 module will be called rtc-pl031. 1559 1560config RTC_DRV_AT91RM9200 1561 tristate "AT91RM9200 or some AT91SAM9 RTC" 1562 depends on ARCH_AT91 || COMPILE_TEST 1563 depends on OF 1564 help 1565 Driver for the internal RTC (Realtime Clock) module found on 1566 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips 1567 this is powered by the backup power supply. 1568 1569config RTC_DRV_AT91SAM9 1570 tristate "AT91SAM9 RTT as RTC" 1571 depends on ARCH_AT91 || COMPILE_TEST 1572 depends on OF && HAS_IOMEM 1573 select MFD_SYSCON 1574 help 1575 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which 1576 can be used as an RTC thanks to the backup power supply (e.g. a 1577 small coin cell battery) which keeps this block and the GPBR 1578 (General Purpose Backup Registers) block powered when the device 1579 is shutdown. 1580 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd 1581 probably want to use the real RTC block instead of the "RTT as an 1582 RTC" driver. 1583 1584config RTC_DRV_AU1XXX 1585 tristate "Au1xxx Counter0 RTC support" 1586 depends on MIPS_ALCHEMY 1587 help 1588 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year 1589 counter) to be used as a RTC. 1590 1591 This driver can also be built as a module. If so, the module 1592 will be called rtc-au1xxx. 1593 1594config RTC_DRV_RS5C313 1595 tristate "Ricoh RS5C313" 1596 depends on SH_LANDISK 1597 help 1598 If you say yes here you get support for the Ricoh RS5C313 RTC chips. 1599 1600config RTC_DRV_RZN1 1601 tristate "Renesas RZ/N1 RTC" 1602 depends on ARCH_RZN1 || COMPILE_TEST 1603 depends on OF && HAS_IOMEM 1604 help 1605 If you say yes here you get support for the Renesas RZ/N1 RTC. 1606 1607config RTC_DRV_GENERIC 1608 tristate "Generic RTC support" 1609 # Please consider writing a new RTC driver instead of using the generic 1610 # RTC abstraction 1611 depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST 1612 help 1613 Say Y or M here to enable RTC support on systems using the generic 1614 RTC abstraction. If you do not know what you are doing, you should 1615 just say Y. 1616 1617config RTC_DRV_PXA 1618 tristate "PXA27x/PXA3xx" 1619 depends on ARCH_PXA 1620 select RTC_DRV_SA1100 1621 help 1622 If you say Y here you will get access to the real time clock 1623 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs 1624 consisting of an SA1100 compatible RTC and the extended PXA RTC. 1625 1626 This RTC driver uses PXA RTC registers available since pxa27x 1627 series (RDxR, RYxR) instead of legacy RCNR, RTAR. 1628 1629config RTC_DRV_VT8500 1630 tristate "VIA/WonderMedia 85xx SoC RTC" 1631 depends on ARCH_VT8500 || COMPILE_TEST 1632 help 1633 If you say Y here you will get access to the real time clock 1634 built into your VIA VT8500 SoC or its relatives. 1635 1636 1637config RTC_DRV_SUN4V 1638 bool "SUN4V Hypervisor RTC" 1639 depends on SPARC64 1640 help 1641 If you say Y here you will get support for the Hypervisor 1642 based RTC on SUN4V systems. 1643 1644config RTC_DRV_SUN6I 1645 bool "Allwinner A31 RTC" 1646 default MACH_SUN6I || MACH_SUN8I 1647 depends on COMMON_CLK 1648 depends on ARCH_SUNXI || COMPILE_TEST 1649 help 1650 If you say Y here you will get support for the RTC found in 1651 some Allwinner SoCs like the A31 or the A64. 1652 1653config RTC_DRV_SUNXI 1654 tristate "Allwinner sun4i/sun7i RTC" 1655 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST 1656 help 1657 If you say Y here you will get support for the RTC found on 1658 Allwinner A10/A20. 1659 1660config RTC_DRV_STARFIRE 1661 bool "Starfire RTC" 1662 depends on SPARC64 1663 help 1664 If you say Y here you will get support for the RTC found on 1665 Starfire systems. 1666 1667config RTC_DRV_MV 1668 tristate "Marvell SoC RTC" 1669 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST 1670 help 1671 If you say yes here you will get support for the in-chip RTC 1672 that can be found in some of Marvell's SoC devices, such as 1673 the Kirkwood 88F6281 and 88F6192. 1674 1675 This driver can also be built as a module. If so, the module 1676 will be called rtc-mv. 1677 1678config RTC_DRV_ARMADA38X 1679 tristate "Armada 38x Marvell SoC RTC" 1680 depends on ARCH_MVEBU || COMPILE_TEST 1681 depends on OF 1682 help 1683 If you say yes here you will get support for the in-chip RTC 1684 that can be found in the Armada 38x Marvell's SoC device 1685 1686 This driver can also be built as a module. If so, the module 1687 will be called armada38x-rtc. 1688 1689config RTC_DRV_CADENCE 1690 tristate "Cadence RTC driver" 1691 depends on OF && HAS_IOMEM 1692 help 1693 If you say Y here you will get access to Cadence RTC IP 1694 found on certain SOCs. 1695 1696 To compile this driver as a module, choose M here: the 1697 module will be called rtc-cadence. 1698 1699config RTC_DRV_FTRTC010 1700 tristate "Faraday Technology FTRTC010 RTC" 1701 depends on HAS_IOMEM 1702 default ARCH_GEMINI 1703 help 1704 If you say Y here you will get support for the 1705 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's. 1706 1707 This driver can also be built as a module. If so, the module 1708 will be called rtc-ftrtc010. 1709 1710config RTC_DRV_PS3 1711 tristate "PS3 RTC" 1712 depends on PPC_PS3 1713 help 1714 If you say yes here you will get support for the RTC on PS3. 1715 1716 This driver can also be built as a module. If so, the module 1717 will be called rtc-ps3. 1718 1719config RTC_DRV_STMP 1720 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC" 1721 depends on ARCH_MXS || COMPILE_TEST 1722 select STMP_DEVICE 1723 help 1724 If you say yes here you will get support for the onboard 1725 STMP3xxx/i.MX23/i.MX28 RTC. 1726 1727 This driver can also be built as a module. If so, the module 1728 will be called rtc-stmp3xxx. 1729 1730config RTC_DRV_PCAP 1731 tristate "PCAP RTC" 1732 depends on EZX_PCAP 1733 help 1734 If you say Y here you will get support for the RTC found on 1735 the PCAP2 ASIC used on some Motorola phones. 1736 1737config RTC_DRV_MC13XXX 1738 depends on MFD_MC13XXX 1739 tristate "Freescale MC13xxx RTC" 1740 help 1741 This enables support for the RTCs found on Freescale's PMICs 1742 MC13783 and MC13892. 1743 1744config RTC_DRV_MPC5121 1745 tristate "Freescale MPC5121 built-in RTC" 1746 depends on PPC_MPC512x || PPC_MPC52xx 1747 help 1748 If you say yes here you will get support for the 1749 built-in RTC on MPC5121 or on MPC5200. 1750 1751 This driver can also be built as a module. If so, the module 1752 will be called rtc-mpc5121. 1753 1754config RTC_DRV_JZ4740 1755 tristate "Ingenic JZ4740 SoC" 1756 depends on MIPS || COMPILE_TEST 1757 depends on OF && COMMON_CLK 1758 help 1759 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC 1760 controllers. 1761 1762 This driver can also be built as a module. If so, the module 1763 will be called rtc-jz4740. 1764 1765config RTC_DRV_LOONGSON 1766 tristate "Loongson On-chip RTC" 1767 depends on MACH_LOONGSON32 || MACH_LOONGSON64 || COMPILE_TEST 1768 select REGMAP_MMIO 1769 help 1770 This is a driver for the Loongson on-chip Counter0 (Time-Of-Year 1771 counter) to be used as a RTC. 1772 It can be found on Loongson-1 series cpu, Loongson-2K series cpu 1773 and Loongson LS7A bridge chips. 1774 1775 This driver can also be built as a module. If so, the module 1776 will be called rtc-loongson. 1777 1778config RTC_DRV_LPC24XX 1779 tristate "NXP RTC for LPC178x/18xx/408x/43xx" 1780 depends on ARCH_LPC18XX || COMPILE_TEST 1781 depends on OF && HAS_IOMEM 1782 depends on COMMON_CLK 1783 help 1784 This enables support for the NXP RTC found which can be found on 1785 NXP LPC178x/18xx/408x/43xx devices. 1786 1787 If you have one of the devices above enable this driver to use 1788 the hardware RTC. This driver can also be built as a module. If 1789 so, the module will be called rtc-lpc24xx. 1790 1791config RTC_DRV_LPC32XX 1792 depends on ARCH_LPC32XX || COMPILE_TEST 1793 tristate "NXP LPC32XX RTC" 1794 help 1795 This enables support for the NXP RTC in the LPC32XX 1796 1797 This driver can also be built as a module. If so, the module 1798 will be called rtc-lpc32xx. 1799 1800config RTC_DRV_PM8XXX 1801 tristate "Qualcomm PMIC8XXX RTC" 1802 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST 1803 help 1804 If you say yes here you get support for the 1805 Qualcomm PMIC8XXX RTC. 1806 1807 To compile this driver as a module, choose M here: the 1808 module will be called rtc-pm8xxx. 1809 1810config RTC_DRV_TEGRA 1811 tristate "NVIDIA Tegra Internal RTC driver" 1812 depends on ARCH_TEGRA || COMPILE_TEST 1813 help 1814 If you say yes here you get support for the 1815 Tegra 200 series internal RTC module. 1816 1817 This drive can also be built as a module. If so, the module 1818 will be called rtc-tegra. 1819 1820config RTC_DRV_MXC 1821 tristate "Freescale MXC Real Time Clock" 1822 depends on ARCH_MXC || COMPILE_TEST 1823 depends on HAS_IOMEM 1824 depends on OF 1825 help 1826 If you say yes here you get support for the Freescale MXC 1827 RTC module. 1828 1829 This driver can also be built as a module, if so, the module 1830 will be called "rtc-mxc". 1831 1832config RTC_DRV_MXC_V2 1833 tristate "Freescale MXC Real Time Clock for i.MX53" 1834 depends on ARCH_MXC || COMPILE_TEST 1835 depends on HAS_IOMEM 1836 depends on OF 1837 help 1838 If you say yes here you get support for the Freescale MXC 1839 SRTC module in i.MX53 processor. 1840 1841 This driver can also be built as a module, if so, the module 1842 will be called "rtc-mxc_v2". 1843 1844config RTC_DRV_SNVS 1845 tristate "Freescale SNVS RTC support" 1846 select REGMAP_MMIO 1847 depends on ARCH_MXC || COMPILE_TEST 1848 depends on HAS_IOMEM 1849 depends on OF 1850 help 1851 If you say yes here you get support for the Freescale SNVS 1852 Low Power (LP) RTC module. 1853 1854 This driver can also be built as a module, if so, the module 1855 will be called "rtc-snvs". 1856 1857config RTC_DRV_BBNSM 1858 tristate "NXP BBNSM RTC support" 1859 select REGMAP_MMIO 1860 depends on ARCH_MXC || COMPILE_TEST 1861 depends on HAS_IOMEM 1862 depends on OF 1863 help 1864 If you say yes here you get support for the NXP BBNSM RTC module. 1865 1866 This driver can also be built as a module, if so, the module 1867 will be called "rtc-bbnsm". 1868 1869config RTC_DRV_IMX_BBM_SCMI 1870 depends on IMX_SCMI_BBM_EXT || COMPILE_TEST 1871 default y if ARCH_MXC 1872 tristate "NXP i.MX BBM SCMI RTC support" 1873 help 1874 If you say yes here you get support for the NXP i.MX BBSM SCMI 1875 RTC module. 1876 1877 To compile this driver as a module, choose M here: the 1878 module will be called rtc-imx-sm-bbm. 1879 1880config RTC_DRV_IMX_SC 1881 depends on IMX_SCU 1882 depends on HAVE_ARM_SMCCC 1883 tristate "NXP i.MX System Controller RTC support" 1884 help 1885 If you say yes here you get support for the NXP i.MX System 1886 Controller RTC module. 1887 1888config RTC_DRV_ST_LPC 1889 tristate "STMicroelectronics LPC RTC" 1890 depends on ARCH_STI 1891 depends on OF 1892 help 1893 Say Y here to include STMicroelectronics Low Power Controller 1894 (LPC) based RTC support. 1895 1896 To compile this driver as a module, choose M here: the 1897 module will be called rtc-st-lpc. 1898 1899config RTC_DRV_MOXART 1900 tristate "MOXA ART RTC" 1901 depends on ARCH_MOXART || COMPILE_TEST 1902 help 1903 If you say yes here you get support for the MOXA ART 1904 RTC module. 1905 1906 This driver can also be built as a module. If so, the module 1907 will be called rtc-moxart 1908 1909config RTC_DRV_MT2712 1910 tristate "MediaTek MT2712 SoC based RTC" 1911 depends on ARCH_MEDIATEK || COMPILE_TEST 1912 help 1913 This enables support for the real time clock built in the MediaTek 1914 SoCs for MT2712. 1915 1916 This drive can also be built as a module. If so, the module 1917 will be called rtc-mt2712. 1918 1919config RTC_DRV_MT6397 1920 tristate "MediaTek PMIC based RTC" 1921 depends on MFD_MT6397 || COMPILE_TEST 1922 select IRQ_DOMAIN 1923 help 1924 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek 1925 MT6397 PMIC. You should enable MT6397 PMIC MFD before select 1926 MediaTek(R) RTC driver. 1927 1928 If you want to use MediaTek(R) RTC interface, select Y or M here. 1929 1930config RTC_DRV_MT7622 1931 tristate "MediaTek SoC based RTC" 1932 depends on ARCH_MEDIATEK || COMPILE_TEST 1933 help 1934 This enables support for the real time clock built in the MediaTek 1935 SoCs. 1936 1937 This drive can also be built as a module. If so, the module 1938 will be called rtc-mt7622. 1939 1940config RTC_DRV_XGENE 1941 tristate "APM X-Gene RTC" 1942 depends on HAS_IOMEM 1943 depends on ARCH_XGENE || COMPILE_TEST 1944 help 1945 If you say yes here you get support for the APM X-Gene SoC real time 1946 clock. 1947 1948 This driver can also be built as a module, if so, the module 1949 will be called "rtc-xgene". 1950 1951config RTC_DRV_PIC32 1952 tristate "Microchip PIC32 RTC" 1953 depends on MACH_PIC32 1954 default y 1955 help 1956 If you say yes here you get support for the PIC32 RTC module. 1957 1958 This driver can also be built as a module. If so, the module 1959 will be called rtc-pic32 1960 1961config RTC_DRV_R7301 1962 tristate "EPSON TOYOCOM RTC-7301SF/DG" 1963 select REGMAP_MMIO 1964 depends on OF && HAS_IOMEM 1965 help 1966 If you say yes here you get support for the EPSON TOYOCOM 1967 RTC-7301SF/DG chips. 1968 1969 This driver can also be built as a module. If so, the module 1970 will be called rtc-r7301. 1971 1972config RTC_DRV_STM32 1973 tristate "STM32 RTC" 1974 select REGMAP_MMIO 1975 depends on ARCH_STM32 || COMPILE_TEST 1976 depends on OF 1977 depends on PINCTRL 1978 select PINMUX 1979 select PINCONF 1980 select GENERIC_PINCONF 1981 depends on COMMON_CLK 1982 help 1983 If you say yes here you get support for the STM32 On-Chip 1984 Real Time Clock. 1985 1986 This driver can also be built as a module, if so, the module 1987 will be called "rtc-stm32". 1988 1989config RTC_DRV_CPCAP 1990 depends on MFD_CPCAP 1991 tristate "Motorola CPCAP RTC" 1992 help 1993 Say y here for CPCAP rtc found on some Motorola phones 1994 and tablets such as Droid 4. 1995 1996config RTC_DRV_RTD119X 1997 bool "Realtek RTD129x RTC" 1998 depends on ARCH_REALTEK || COMPILE_TEST 1999 default ARCH_REALTEK 2000 help 2001 If you say yes here, you get support for the RTD1295 SoC 2002 Real Time Clock. 2003 2004config RTC_DRV_ASPEED 2005 tristate "ASPEED RTC" 2006 depends on OF 2007 depends on ARCH_ASPEED || COMPILE_TEST 2008 help 2009 If you say yes here you get support for the ASPEED BMC SoC real time 2010 clocks. 2011 2012 This driver can also be built as a module, if so, the module 2013 will be called "rtc-aspeed". 2014 2015config RTC_DRV_TI_K3 2016 tristate "TI K3 RTC" 2017 depends on ARCH_K3 || COMPILE_TEST 2018 select REGMAP_MMIO 2019 help 2020 If you say yes here you get support for the Texas Instruments's 2021 Real Time Clock for K3 architecture. 2022 2023 This driver can also be built as a module, if so, the module 2024 will be called "rtc-ti-k3". 2025 2026config RTC_DRV_MA35D1 2027 tristate "Nuvoton MA35D1 RTC" 2028 depends on ARCH_MA35 || COMPILE_TEST 2029 select REGMAP_MMIO 2030 help 2031 If you say yes here you get support for the Nuvoton MA35D1 2032 On-Chip Real Time Clock. 2033 2034 This driver can also be built as a module, if so, the module 2035 will be called "rtc-ma35d1". 2036 2037config RTC_DRV_RENESAS_RTCA3 2038 tristate "Renesas RTCA-3 RTC" 2039 depends on ARCH_RENESAS 2040 help 2041 If you say yes here you get support for the Renesas RTCA-3 RTC 2042 available on the Renesas RZ/G3S SoC. 2043 2044 This driver can also be built as a module, if so, the module 2045 will be called "rtc-rtca3". 2046 2047comment "HID Sensor RTC drivers" 2048 2049config RTC_DRV_HID_SENSOR_TIME 2050 tristate "HID Sensor Time" 2051 depends on USB_HID 2052 depends on HID_SENSOR_HUB && IIO 2053 select HID_SENSOR_IIO_COMMON 2054 help 2055 Say yes here to build support for the HID Sensors of type Time. 2056 This drivers makes such sensors available as RTCs. 2057 2058 If this driver is compiled as a module, it will be named 2059 rtc-hid-sensor-time. 2060 2061config RTC_DRV_GOLDFISH 2062 tristate "Goldfish Real Time Clock" 2063 depends on HAS_IOMEM 2064 help 2065 Say yes to enable RTC driver for the Goldfish based virtual platform. 2066 2067 Goldfish is a code name for the virtual platform developed by Google 2068 for Android emulation. 2069 2070config RTC_DRV_WILCO_EC 2071 tristate "Wilco EC RTC" 2072 depends on WILCO_EC 2073 default m 2074 help 2075 If you say yes here, you get read/write support for the Real Time 2076 Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook) 2077 2078 This can also be built as a module. If so, the module will 2079 be named "rtc_wilco_ec". 2080 2081config RTC_DRV_MSC313 2082 tristate "MStar MSC313 RTC" 2083 depends on ARCH_MSTARV7 || COMPILE_TEST 2084 help 2085 If you say yes here you get support for the Mstar MSC313e On-Chip 2086 Real Time Clock. 2087 2088 This driver can also be built as a module, if so, the module 2089 will be called "rtc-msc313". 2090 2091config RTC_DRV_POLARFIRE_SOC 2092 tristate "Microchip PolarFire SoC built-in RTC" 2093 depends on ARCH_MICROCHIP_POLARFIRE 2094 help 2095 If you say yes here you will get support for the 2096 built-in RTC on Polarfire SoC. 2097 2098 This driver can also be built as a module, if so, the module 2099 will be called "rtc-mpfs". 2100 2101config RTC_DRV_SSD202D 2102 tristate "SigmaStar SSD202D RTC" 2103 depends on ARCH_MSTARV7 || COMPILE_TEST 2104 default ARCH_MSTARV7 2105 help 2106 If you say yes here you get support for the SigmaStar SSD202D On-Chip 2107 Real Time Clock. 2108 2109 This driver can also be built as a module, if so, the module 2110 will be called "rtc-ssd20xd". 2111 2112config RTC_DRV_AMLOGIC_A4 2113 tristate "Amlogic RTC" 2114 depends on ARCH_MESON || COMPILE_TEST 2115 select REGMAP_MMIO 2116 default ARCH_MESON 2117 help 2118 If you say yes here you get support for the RTC block on the 2119 Amlogic A113L2(A4) and A113X2(A5) SoCs. 2120 2121 This driver can also be built as a module. If so, the module 2122 will be called "rtc-amlogic-a4". 2123 2124config RTC_DRV_S32G 2125 tristate "RTC driver for S32G2/S32G3 SoCs" 2126 depends on ARCH_S32 || COMPILE_TEST 2127 depends on COMMON_CLK 2128 help 2129 Say yes to enable RTC driver for platforms based on the 2130 S32G2/S32G3 SoC family. 2131 2132 This RTC module can be used as a wakeup source. 2133 Please note that it is not battery-powered. 2134 2135endif # RTC_CLASS 2136