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