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