drivers/rtc/Kconfig

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