drivers/rtc/Kconfig

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