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         depends on !ALWAYS_USE_PERSISTENT_CLOCK
  24         help
  25           If you say yes here, the system time (wall clock) will be set using
  26           the value read from a specified RTC device. This is useful to avoid
  27           unnecessary fsck runs at boot time, and to network better.
  28
  29 config RTC_SYSTOHC
  30         bool "Set the RTC time based on NTP synchronization"
  31         default y
  32         depends on !ALWAYS_USE_PERSISTENT_CLOCK
  33         help
  34           If you say yes here, the system time (wall clock) will be stored
  35           in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
  36           minutes if userspace reports synchronized NTP status.
  37
  38 config RTC_HCTOSYS_DEVICE
  39         string "RTC used to set the system time"
  40         depends on RTC_HCTOSYS = y || RTC_SYSTOHC = y
  41         default "rtc0"
  42         help
  43           The RTC device that will be used to (re)initialize the system
  44           clock, usually rtc0. Initialization is done when the system
  45           starts up, and when it resumes from a low power state. This
  46           device should record time in UTC, since the kernel won't do
  47           timezone correction.
  48
  49           The driver for this RTC device must be loaded before late_initcall
  50           functions run, so it must usually be statically linked.
  51
  52           This clock should be battery-backed, so that it reads the correct
  53           time when the system boots from a power-off state. Otherwise, your
  54           system will need an external clock source (like an NTP server).
  55
  56           If the clock you specify here is not battery backed, it may still
  57           be useful to reinitialize system time when resuming from system
  58           sleep states. Do not specify an RTC here unless it stays powered
  59           during all this system's supported sleep states.
  60
  61 config RTC_DEBUG
  62         bool "RTC debug support"
  63         help
  64           Say yes here to enable debugging support in the RTC framework
  65           and individual RTC drivers.
  66
  67 comment "RTC interfaces"
  68
  69 config RTC_INTF_SYSFS
  70         boolean "/sys/class/rtc/rtcN (sysfs)"
  71         depends on SYSFS
  72         default RTC_CLASS
  73         help
  74           Say yes here if you want to use your RTCs using sysfs interfaces,
  75           /sys/class/rtc/rtc0 through /sys/.../rtcN.
  76
  77           If unsure, say Y.
  78
  79 config RTC_INTF_PROC
  80         boolean "/proc/driver/rtc (procfs for rtcN)"
  81         depends on PROC_FS
  82         default RTC_CLASS
  83         help
  84           Say yes here if you want to use your system clock RTC through
  85           the proc interface, /proc/driver/rtc.
  86           Other RTCs will not be available through that API.
  87           If there is no RTC for the system clock, then the first RTC(rtc0)
  88           is used by default.
  89
  90           If unsure, say Y.
  91
  92 config RTC_INTF_DEV
  93         boolean "/dev/rtcN (character devices)"
  94         default RTC_CLASS
  95         help
  96           Say yes here if you want to use your RTCs using the /dev
  97           interfaces, which "udev" sets up as /dev/rtc0 through
  98           /dev/rtcN.
  99
 100           You may want to set up a symbolic link so one of these
 101           can be accessed as /dev/rtc, which is a name
 102           expected by "hwclock" and some other programs. Recent
 103           versions of "udev" are known to set up the symlink for you.
 104
 105           If unsure, say Y.
 106
 107 config RTC_INTF_DEV_UIE_EMUL
 108         bool "RTC UIE emulation on dev interface"
 109         depends on RTC_INTF_DEV
 110         help
 111           Provides an emulation for RTC_UIE if the underlying rtc chip
 112           driver does not expose RTC_UIE ioctls. Those requests generate
 113           once-per-second update interrupts, used for synchronization.
 114
 115           The emulation code will read the time from the hardware
 116           clock several times per second, please enable this option
 117           only if you know that you really need it.
 118
 119 config RTC_DRV_TEST
 120         tristate "Test driver/device"
 121         help
 122           If you say yes here you get support for the
 123           RTC test driver. It's a software RTC which can be
 124           used to test the RTC subsystem APIs. It gets
 125           the time from the system clock.
 126           You want this driver only if you are doing development
 127           on the RTC subsystem. Please read the source code
 128           for further details.
 129
 130           This driver can also be built as a module. If so, the module
 131           will be called rtc-test.
 132
 133 comment "I2C RTC drivers"
 134         depends on I2C
 135
 136 if I2C
 137
 138 config RTC_DRV_88PM860X
 139         tristate "Marvell 88PM860x"
 140         depends on I2C && MFD_88PM860X
 141         help
 142           If you say yes here you get support for RTC function in Marvell
 143           88PM860x chips.
 144
 145           This driver can also be built as a module. If so, the module
 146           will be called rtc-88pm860x.
 147
 148 config RTC_DRV_88PM80X
 149         tristate "Marvell 88PM80x"
 150         depends on I2C && MFD_88PM800
 151         help
 152           If you say yes here you get support for RTC function in Marvell
 153           88PM80x chips.
 154
 155           This driver can also be built as a module. If so, the module
 156           will be called rtc-88pm80x.
 157
 158 config RTC_DRV_DS1307
 159         tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
 160         help
 161           If you say yes here you get support for various compatible RTC
 162           chips (often with battery backup) connected with I2C. This driver
 163           should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
 164           EPSON RX-8025 and probably other chips. In some cases the RTC
 165           must already have been initialized (by manufacturing or a
 166           bootloader).
 167
 168           The first seven registers on these chips hold an RTC, and other
 169           registers may add features such as NVRAM, a trickle charger for
 170           the RTC/NVRAM backup power, and alarms. NVRAM is visible in
 171           sysfs, but other chip features may not be available.
 172
 173           This driver can also be built as a module. If so, the module
 174           will be called rtc-ds1307.
 175
 176 config RTC_DRV_DS1374
 177         tristate "Dallas/Maxim DS1374"
 178         depends on I2C
 179         help
 180           If you say yes here you get support for Dallas Semiconductor
 181           DS1374 real-time clock chips. If an interrupt is associated
 182           with the device, the alarm functionality is supported.
 183
 184           This driver can also be built as a module. If so, the module
 185           will be called rtc-ds1374.
 186
 187 config RTC_DRV_DS1672
 188         tristate "Dallas/Maxim DS1672"
 189         help
 190           If you say yes here you get support for the
 191           Dallas/Maxim DS1672 timekeeping chip.
 192
 193           This driver can also be built as a module. If so, the module
 194           will be called rtc-ds1672.
 195
 196 config RTC_DRV_DS3232
 197         tristate "Dallas/Maxim DS3232"
 198         depends on I2C
 199         help
 200           If you say yes here you get support for Dallas Semiconductor
 201           DS3232 real-time clock chips. If an interrupt is associated
 202           with the device, the alarm functionality is supported.
 203
 204           This driver can also be built as a module.  If so, the module
 205           will be called rtc-ds3232.
 206
 207 config RTC_DRV_MAX6900
 208         tristate "Maxim MAX6900"
 209         help
 210           If you say yes here you will get support for the
 211           Maxim MAX6900 I2C RTC chip.
 212
 213           This driver can also be built as a module. If so, the module
 214           will be called rtc-max6900.
 215
 216 config RTC_DRV_MAX8907
 217         tristate "Maxim MAX8907"
 218         depends on MFD_MAX8907
 219         help
 220           If you say yes here you will get support for the
 221           RTC of Maxim MAX8907 PMIC.
 222
 223           This driver can also be built as a module. If so, the module
 224           will be called rtc-max8907.
 225
 226 config RTC_DRV_MAX8925
 227         tristate "Maxim MAX8925"
 228         depends on MFD_MAX8925
 229         help
 230           If you say yes here you will get support for the
 231           RTC of Maxim MAX8925 PMIC.
 232
 233           This driver can also be built as a module. If so, the module
 234           will be called rtc-max8925.
 235
 236 config RTC_DRV_MAX8998
 237         tristate "Maxim MAX8998"
 238         depends on MFD_MAX8998
 239         help
 240           If you say yes here you will get support for the
 241           RTC of Maxim MAX8998 PMIC.
 242
 243           This driver can also be built as a module. If so, the module
 244           will be called rtc-max8998.
 245
 246 config RTC_DRV_MAX77686
 247         tristate "Maxim MAX77686"
 248         depends on MFD_MAX77686
 249         help
 250           If you say yes here you will get support for the
 251           RTC of Maxim MAX77686 PMIC.
 252
 253           This driver can also be built as a module. If so, the module
 254           will be called rtc-max77686.
 255
 256 config RTC_DRV_RS5C372
 257         tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
 258         help
 259           If you say yes here you get support for the
 260           Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
 261
 262           This driver can also be built as a module. If so, the module
 263           will be called rtc-rs5c372.
 264
 265 config RTC_DRV_ISL1208
 266         tristate "Intersil ISL1208"
 267         help
 268           If you say yes here you get support for the
 269           Intersil ISL1208 RTC chip.
 270
 271           This driver can also be built as a module. If so, the module
 272           will be called rtc-isl1208.
 273
 274 config RTC_DRV_ISL12022
 275         tristate "Intersil ISL12022"
 276         help
 277           If you say yes here you get support for the
 278           Intersil ISL12022 RTC chip.
 279
 280           This driver can also be built as a module. If so, the module
 281           will be called rtc-isl12022.
 282
 283 config RTC_DRV_X1205
 284         tristate "Xicor/Intersil X1205"
 285         help
 286           If you say yes here you get support for the
 287           Xicor/Intersil X1205 RTC chip.
 288
 289           This driver can also be built as a module. If so, the module
 290           will be called rtc-x1205.
 291
 292 config RTC_DRV_PCF8523
 293         tristate "NXP PCF8523"
 294         help
 295           If you say yes here you get support for the NXP PCF8523 RTC
 296           chips.
 297
 298           This driver can also be built as a module. If so, the module
 299           will be called rtc-pcf8523.
 300
 301 config RTC_DRV_PCF8563
 302         tristate "Philips PCF8563/Epson RTC8564"
 303         help
 304           If you say yes here you get support for the
 305           Philips PCF8563 RTC chip. The Epson RTC8564
 306           should work as well.
 307
 308           This driver can also be built as a module. If so, the module
 309           will be called rtc-pcf8563.
 310
 311 config RTC_DRV_PCF8583
 312         tristate "Philips PCF8583"
 313         help
 314           If you say yes here you get support for the Philips PCF8583
 315           RTC chip found on Acorn RiscPCs. This driver supports the
 316           platform specific method of retrieving the current year from
 317           the RTC's SRAM. It will work on other platforms with the same
 318           chip, but the year will probably have to be tweaked.
 319
 320           This driver can also be built as a module. If so, the module
 321           will be called rtc-pcf8583.
 322
 323 config RTC_DRV_M41T80
 324         tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
 325         help
 326           If you say Y here you will get support for the ST M41T60
 327           and M41T80 RTC chips series. Currently, the following chips are
 328           supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
 329           M41ST85, and M41ST87.
 330
 331           This driver can also be built as a module. If so, the module
 332           will be called rtc-m41t80.
 333
 334 config RTC_DRV_M41T80_WDT
 335         bool "ST M41T65/M41T80 series RTC watchdog timer"
 336         depends on RTC_DRV_M41T80
 337         help
 338           If you say Y here you will get support for the
 339           watchdog timer in the ST M41T60 and M41T80 RTC chips series.
 340
 341 config RTC_DRV_BQ32K
 342         tristate "TI BQ32000"
 343         help
 344           If you say Y here you will get support for the TI
 345           BQ32000 I2C RTC chip.
 346
 347           This driver can also be built as a module. If so, the module
 348           will be called rtc-bq32k.
 349
 350 config RTC_DRV_DM355EVM
 351         tristate "TI DaVinci DM355 EVM RTC"
 352         depends on MFD_DM355EVM_MSP
 353         help
 354           Supports the RTC firmware in the MSP430 on the DM355 EVM.
 355
 356 config RTC_DRV_TWL92330
 357         boolean "TI TWL92330/Menelaus"
 358         depends on MENELAUS
 359         help
 360           If you say yes here you get support for the RTC on the
 361           TWL92330 "Menelaus" power management chip, used with OMAP2
 362           platforms. The support is integrated with the rest of
 363           the Menelaus driver; it's not separate module.
 364
 365 config RTC_DRV_TWL4030
 366         tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
 367         depends on TWL4030_CORE
 368         help
 369           If you say yes here you get support for the RTC on the
 370           TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
 371
 372           This driver can also be built as a module. If so, the module
 373           will be called rtc-twl.
 374
 375 config RTC_DRV_TPS6586X
 376         tristate "TI TPS6586X RTC driver"
 377         depends on MFD_TPS6586X
 378         help
 379           TI Power Managment IC TPS6586X supports RTC functionality
 380           along with alarm. This driver supports the RTC driver for
 381           the TPS6586X RTC module.
 382
 383 config RTC_DRV_TPS65910
 384         tristate "TI TPS65910 RTC driver"
 385         depends on RTC_CLASS && MFD_TPS65910
 386         help
 387           If you say yes here you get support for the RTC on the
 388           TPS65910 chips.
 389
 390           This driver can also be built as a module. If so, the module
 391           will be called rtc-tps65910.
 392
 393 config RTC_DRV_RC5T583
 394         tristate "RICOH 5T583 RTC driver"
 395         depends on MFD_RC5T583
 396         help
 397           If you say yes here you get support for the RTC on the
 398           RICOH 5T583 chips.
 399
 400           This driver can also be built as a module. If so, the module
 401           will be called rtc-rc5t583.
 402
 403 config RTC_DRV_S35390A
 404         tristate "Seiko Instruments S-35390A"
 405         select BITREVERSE
 406         help
 407           If you say yes here you will get support for the Seiko
 408           Instruments S-35390A.
 409
 410           This driver can also be built as a module. If so the module
 411           will be called rtc-s35390a.
 412
 413 config RTC_DRV_FM3130
 414         tristate "Ramtron FM3130"
 415         help
 416           If you say Y here you will get support for the
 417           Ramtron FM3130 RTC chips.
 418           Ramtron FM3130 is a chip with two separate devices inside,
 419           RTC clock and FRAM. This driver provides only RTC functionality.
 420
 421           This driver can also be built as a module. If so the module
 422           will be called rtc-fm3130.
 423
 424 config RTC_DRV_RX8581
 425         tristate "Epson RX-8581"
 426         help
 427           If you say yes here you will get support for the Epson RX-8581.
 428
 429           This driver can also be built as a module. If so the module
 430           will be called rtc-rx8581.
 431
 432 config RTC_DRV_RX8025
 433         tristate "Epson RX-8025SA/NB"
 434         help
 435           If you say yes here you get support for the Epson
 436           RX-8025SA/NB RTC chips.
 437
 438           This driver can also be built as a module. If so, the module
 439           will be called rtc-rx8025.
 440
 441 config RTC_DRV_EM3027
 442         tristate "EM Microelectronic EM3027"
 443         help
 444           If you say yes here you get support for the EM
 445           Microelectronic EM3027 RTC chips.
 446
 447           This driver can also be built as a module. If so, the module
 448           will be called rtc-em3027.
 449
 450 config RTC_DRV_RV3029C2
 451         tristate "Micro Crystal RTC"
 452         help
 453           If you say yes here you get support for the Micro Crystal
 454           RV3029-C2 RTC chips.
 455
 456           This driver can also be built as a module. If so, the module
 457           will be called rtc-rv3029c2.
 458
 459 endif # I2C
 460
 461 comment "SPI RTC drivers"
 462
 463 if SPI_MASTER
 464
 465 config RTC_DRV_M41T93
 466         tristate "ST M41T93"
 467         help
 468           If you say yes here you will get support for the
 469           ST M41T93 SPI RTC chip.
 470
 471           This driver can also be built as a module. If so, the module
 472           will be called rtc-m41t93.
 473
 474 config RTC_DRV_M41T94
 475         tristate "ST M41T94"
 476         help
 477           If you say yes here you will get support for the
 478           ST M41T94 SPI RTC chip.
 479
 480           This driver can also be built as a module. If so, the module
 481           will be called rtc-m41t94.
 482
 483 config RTC_DRV_DS1305
 484         tristate "Dallas/Maxim DS1305/DS1306"
 485         help
 486           Select this driver to get support for the Dallas/Maxim DS1305
 487           and DS1306 real time clock chips. These support a trickle
 488           charger, alarms, and NVRAM in addition to the clock.
 489
 490           This driver can also be built as a module. If so, the module
 491           will be called rtc-ds1305.
 492
 493 config RTC_DRV_DS1390
 494         tristate "Dallas/Maxim DS1390/93/94"
 495         help
 496           If you say yes here you get support for the
 497           Dallas/Maxim DS1390/93/94 chips.
 498
 499           This driver only supports the RTC feature, and not other chip
 500           features such as alarms and trickle charging.
 501
 502           This driver can also be built as a module. If so, the module
 503           will be called rtc-ds1390.
 504
 505 config RTC_DRV_MAX6902
 506         tristate "Maxim MAX6902"
 507         help
 508           If you say yes here you will get support for the
 509           Maxim MAX6902 SPI RTC chip.
 510
 511           This driver can also be built as a module. If so, the module
 512           will be called rtc-max6902.
 513
 514 config RTC_DRV_R9701
 515         tristate "Epson RTC-9701JE"
 516         help
 517           If you say yes here you will get support for the
 518           Epson RTC-9701JE SPI RTC chip.
 519
 520           This driver can also be built as a module. If so, the module
 521           will be called rtc-r9701.
 522
 523 config RTC_DRV_RS5C348
 524         tristate "Ricoh RS5C348A/B"
 525         help
 526           If you say yes here you get support for the
 527           Ricoh RS5C348A and RS5C348B RTC chips.
 528
 529           This driver can also be built as a module. If so, the module
 530           will be called rtc-rs5c348.
 531
 532 config RTC_DRV_DS3234
 533         tristate "Maxim/Dallas DS3234"
 534         help
 535           If you say yes here you get support for the
 536           Maxim/Dallas DS3234 SPI RTC chip.
 537
 538           This driver can also be built as a module. If so, the module
 539           will be called rtc-ds3234.
 540
 541 config RTC_DRV_PCF2123
 542         tristate "NXP PCF2123"
 543         help
 544           If you say yes here you get support for the NXP PCF2123
 545           RTC chip.
 546
 547           This driver can also be built as a module. If so, the module
 548           will be called rtc-pcf2123.
 549
 550 endif # SPI_MASTER
 551
 552 comment "Platform RTC drivers"
 553
 554 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
 555 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
 556 # global rtc_lock ... it's not yet just another platform_device.
 557
 558 config RTC_DRV_CMOS
 559         tristate "PC-style 'CMOS'"
 560         depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
 561         default y if X86
 562         help
 563           Say "yes" here to get direct support for the real time clock
 564           found in every PC or ACPI-based system, and some other boards.
 565           Specifically the original MC146818, compatibles like those in
 566           PC south bridges, the DS12887 or M48T86, some multifunction
 567           or LPC bus chips, and so on.
 568
 569           Your system will need to define the platform device used by
 570           this driver, otherwise it won't be accessible. This means
 571           you can safely enable this driver if you don't know whether
 572           or not your board has this kind of hardware.
 573
 574           This driver can also be built as a module. If so, the module
 575           will be called rtc-cmos.
 576
 577 config RTC_DRV_VRTC
 578         tristate "Virtual RTC for Intel MID platforms"
 579         depends on X86_INTEL_MID
 580         default y if X86_INTEL_MID
 581
 582         help
 583         Say "yes" here to get direct support for the real time clock
 584         found on Moorestown platforms. The VRTC is a emulated RTC that
 585         derives its clock source from a real RTC in the PMIC. The MC146818
 586         style programming interface is mostly conserved, but any
 587         updates are done via IPC calls to the system controller FW.
 588
 589 config RTC_DRV_DS1216
 590         tristate "Dallas DS1216"
 591         depends on SNI_RM
 592         help
 593           If you say yes here you get support for the Dallas DS1216 RTC chips.
 594
 595 config RTC_DRV_DS1286
 596         tristate "Dallas DS1286"
 597         help
 598           If you say yes here you get support for the Dallas DS1286 RTC chips.
 599
 600 config RTC_DRV_DS1302
 601         tristate "Dallas DS1302"
 602         depends on SH_SECUREEDGE5410
 603         help
 604           If you say yes here you get support for the Dallas DS1302 RTC chips.
 605
 606 config RTC_DRV_DS1511
 607         tristate "Dallas DS1511"
 608         help
 609           If you say yes here you get support for the
 610           Dallas DS1511 timekeeping/watchdog chip.
 611
 612           This driver can also be built as a module. If so, the module
 613           will be called rtc-ds1511.
 614
 615 config RTC_DRV_DS1553
 616         tristate "Maxim/Dallas DS1553"
 617         help
 618           If you say yes here you get support for the
 619           Maxim/Dallas DS1553 timekeeping chip.
 620
 621           This driver can also be built as a module. If so, the module
 622           will be called rtc-ds1553.
 623
 624 config RTC_DRV_DS1742
 625         tristate "Maxim/Dallas DS1742/1743"
 626         help
 627           If you say yes here you get support for the
 628           Maxim/Dallas DS1742/1743 timekeeping chip.
 629
 630           This driver can also be built as a module. If so, the module
 631           will be called rtc-ds1742.
 632
 633 config RTC_DRV_DA9052
 634         tristate "Dialog DA9052/DA9053 RTC"
 635         depends on PMIC_DA9052
 636         help
 637           Say y here to support the RTC driver for Dialog Semiconductor
 638           DA9052-BC and DA9053-AA/Bx PMICs.
 639
 640 config RTC_DRV_DA9055
 641         tristate "Dialog Semiconductor DA9055 RTC"
 642         depends on MFD_DA9055
 643         help
 644           If you say yes here you will get support for the
 645           RTC of the Dialog DA9055 PMIC.
 646
 647           This driver can also be built as a module. If so, the module
 648           will be called rtc-da9055
 649
 650 config RTC_DRV_EFI
 651         tristate "EFI RTC"
 652         depends on IA64
 653         help
 654           If you say yes here you will get support for the EFI
 655           Real Time Clock.
 656
 657           This driver can also be built as a module. If so, the module
 658           will be called rtc-efi.
 659
 660 config RTC_DRV_STK17TA8
 661         tristate "Simtek STK17TA8"
 662         help
 663           If you say yes here you get support for the
 664           Simtek STK17TA8 timekeeping chip.
 665
 666           This driver can also be built as a module. If so, the module
 667           will be called rtc-stk17ta8.
 668
 669 config RTC_DRV_M48T86
 670         tristate "ST M48T86/Dallas DS12887"
 671         help
 672           If you say Y here you will get support for the
 673           ST M48T86 and Dallas DS12887 RTC chips.
 674
 675           This driver can also be built as a module. If so, the module
 676           will be called rtc-m48t86.
 677
 678 config RTC_DRV_M48T35
 679         tristate "ST M48T35"
 680         help
 681           If you say Y here you will get support for the
 682           ST M48T35 RTC chip.
 683
 684           This driver can also be built as a module, if so, the module
 685           will be called "rtc-m48t35".
 686
 687 config RTC_DRV_M48T59
 688         tristate "ST M48T59/M48T08/M48T02"
 689         help
 690           If you say Y here you will get support for the
 691           ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
 692
 693           These chips are usually found in Sun SPARC and UltraSPARC
 694           workstations.
 695
 696           This driver can also be built as a module, if so, the module
 697           will be called "rtc-m48t59".
 698
 699 config RTC_DRV_MSM6242
 700         tristate "Oki MSM6242"
 701         help
 702           If you say yes here you get support for the Oki MSM6242
 703           timekeeping chip. It is used in some Amiga models (e.g. A2000).
 704
 705           This driver can also be built as a module. If so, the module
 706           will be called rtc-msm6242.
 707
 708 config RTC_DRV_BQ4802
 709         tristate "TI BQ4802"
 710         help
 711           If you say Y here you will get support for the TI
 712           BQ4802 RTC chip.
 713
 714           This driver can also be built as a module. If so, the module
 715           will be called rtc-bq4802.
 716
 717 config RTC_DRV_RP5C01
 718         tristate "Ricoh RP5C01"
 719         help
 720           If you say yes here you get support for the Ricoh RP5C01
 721           timekeeping chip. It is used in some Amiga models (e.g. A3000
 722           and A4000).
 723
 724           This driver can also be built as a module. If so, the module
 725           will be called rtc-rp5c01.
 726
 727 config RTC_DRV_V3020
 728         tristate "EM Microelectronic V3020"
 729         help
 730           If you say yes here you will get support for the
 731           EM Microelectronic v3020 RTC chip.
 732
 733           This driver can also be built as a module. If so, the module
 734           will be called rtc-v3020.
 735
 736 config RTC_DRV_DS2404
 737         tristate "Dallas DS2404"
 738         help
 739           If you say yes here you get support for the
 740           Dallas DS2404 RTC chip.
 741
 742           This driver can also be built as a module. If so, the module
 743           will be called rtc-ds2404.
 744
 745 config RTC_DRV_WM831X
 746         tristate "Wolfson Microelectronics WM831x RTC"
 747         depends on MFD_WM831X
 748         help
 749           If you say yes here you will get support for the RTC subsystem
 750           of the Wolfson Microelectronics WM831X series PMICs.
 751
 752           This driver can also be built as a module. If so, the module
 753           will be called "rtc-wm831x".
 754
 755 config RTC_DRV_WM8350
 756         tristate "Wolfson Microelectronics WM8350 RTC"
 757         depends on MFD_WM8350
 758         help
 759           If you say yes here you will get support for the RTC subsystem
 760           of the Wolfson Microelectronics WM8350.
 761
 762           This driver can also be built as a module. If so, the module
 763           will be called "rtc-wm8350".
 764
 765 config RTC_DRV_SPEAR
 766         tristate "SPEAR ST RTC"
 767         depends on PLAT_SPEAR
 768         default y
 769         help
 770          If you say Y here you will get support for the RTC found on
 771          spear
 772
 773 config RTC_DRV_PCF50633
 774         depends on MFD_PCF50633
 775         tristate "NXP PCF50633 RTC"
 776         help
 777           If you say yes here you get support for the RTC subsystem of the
 778           NXP PCF50633 used in embedded systems.
 779
 780 config RTC_DRV_AB3100
 781         tristate "ST-Ericsson AB3100 RTC"
 782         depends on AB3100_CORE
 783         default y if AB3100_CORE
 784         help
 785           Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
 786           support. This chip contains a battery- and capacitor-backed RTC.
 787
 788 config RTC_DRV_AB8500
 789         tristate "ST-Ericsson AB8500 RTC"
 790         depends on AB8500_CORE
 791         select RTC_INTF_DEV
 792         select RTC_INTF_DEV_UIE_EMUL
 793         help
 794           Select this to enable the ST-Ericsson AB8500 power management IC RTC
 795           support. This chip contains a battery- and capacitor-backed RTC.
 796
 797 config RTC_DRV_NUC900
 798         tristate "NUC910/NUC920 RTC driver"
 799         depends on ARCH_W90X900
 800         help
 801           If you say yes here you get support for the RTC subsystem of the
 802           NUC910/NUC920 used in embedded systems.
 803
 804 comment "on-CPU RTC drivers"
 805
 806 config RTC_DRV_DAVINCI
 807         tristate "TI DaVinci RTC"
 808         depends on ARCH_DAVINCI_DM365
 809         help
 810           If you say yes here you get support for the RTC on the
 811           DaVinci platforms (DM365).
 812
 813           This driver can also be built as a module. If so, the module
 814           will be called rtc-davinci.
 815
 816 config RTC_DRV_IMXDI
 817         tristate "Freescale IMX DryIce Real Time Clock"
 818         depends on ARCH_MXC
 819         help
 820            Support for Freescale IMX DryIce RTC
 821
 822            This driver can also be built as a module, if so, the module
 823            will be called "rtc-imxdi".
 824
 825 config RTC_DRV_OMAP
 826         tristate "TI OMAP1"
 827         depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
 828         help
 829           Say "yes" here to support the on chip real time clock
 830           present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
 831
 832           This driver can also be built as a module, if so, module
 833           will be called rtc-omap.
 834
 835 config HAVE_S3C_RTC
 836         bool
 837         help
 838           This will include RTC support for Samsung SoCs. If
 839           you want to include RTC support for any machine, kindly
 840           select this in the respective mach-XXXX/Kconfig file.
 841
 842 config RTC_DRV_S3C
 843         tristate "Samsung S3C series SoC RTC"
 844         depends on ARCH_S3C64XX || HAVE_S3C_RTC
 845         help
 846           RTC (Realtime Clock) driver for the clock inbuilt into the
 847           Samsung S3C24XX series of SoCs. This can provide periodic
 848           interrupt rates from 1Hz to 64Hz for user programs, and
 849           wakeup from Alarm.
 850
 851           The driver currently supports the common features on all the
 852           S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
 853           and S3C2442.
 854
 855           This driver can also be build as a module. If so, the module
 856           will be called rtc-s3c.
 857
 858 config RTC_DRV_EP93XX
 859         tristate "Cirrus Logic EP93XX"
 860         depends on ARCH_EP93XX
 861         help
 862           If you say yes here you get support for the
 863           RTC embedded in the Cirrus Logic EP93XX processors.
 864
 865           This driver can also be built as a module. If so, the module
 866           will be called rtc-ep93xx.
 867
 868 config RTC_DRV_SA1100
 869         tristate "SA11x0/PXA2xx/PXA910"
 870         depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
 871         help
 872           If you say Y here you will get access to the real time clock
 873           built into your SA11x0 or PXA2xx CPU.
 874
 875           To compile this driver as a module, choose M here: the
 876           module will be called rtc-sa1100.
 877
 878 config RTC_DRV_SH
 879         tristate "SuperH On-Chip RTC"
 880         depends on SUPERH && HAVE_CLK
 881         help
 882           Say Y here to enable support for the on-chip RTC found in
 883           most SuperH processors.
 884
 885           To compile this driver as a module, choose M here: the
 886           module will be called rtc-sh.
 887
 888 config RTC_DRV_VR41XX
 889         tristate "NEC VR41XX"
 890         depends on CPU_VR41XX
 891         help
 892           If you say Y here you will get access to the real time clock
 893           built into your NEC VR41XX CPU.
 894
 895           To compile this driver as a module, choose M here: the
 896           module will be called rtc-vr41xx.
 897
 898 config RTC_DRV_PL030
 899         tristate "ARM AMBA PL030 RTC"
 900         depends on ARM_AMBA
 901         help
 902           If you say Y here you will get access to ARM AMBA
 903           PrimeCell PL030 RTC found on certain ARM SOCs.
 904
 905           To compile this driver as a module, choose M here: the
 906           module will be called rtc-pl030.
 907
 908 config RTC_DRV_PL031
 909         tristate "ARM AMBA PL031 RTC"
 910         depends on ARM_AMBA
 911         help
 912           If you say Y here you will get access to ARM AMBA
 913           PrimeCell PL031 RTC found on certain ARM SOCs.
 914
 915           To compile this driver as a module, choose M here: the
 916           module will be called rtc-pl031.
 917
 918 config RTC_DRV_AT32AP700X
 919         tristate "AT32AP700X series RTC"
 920         depends on PLATFORM_AT32AP
 921         help
 922           Driver for the internal RTC (Realtime Clock) on Atmel AVR32
 923           AT32AP700x family processors.
 924
 925 config RTC_DRV_AT91RM9200
 926         tristate "AT91RM9200 or some AT91SAM9 RTC"
 927         depends on ARCH_AT91
 928         help
 929           Driver for the internal RTC (Realtime Clock) module found on
 930           Atmel AT91RM9200's and some  AT91SAM9 chips. On AT91SAM9 chips
 931           this is powered by the backup power supply.
 932
 933 config RTC_DRV_AT91SAM9
 934         tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
 935         depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
 936         help
 937           RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
 938           (Real Time Timer). These timers are powered by the backup power
 939           supply (such as a small coin cell battery), but do not need to
 940           be used as RTCs.
 941
 942           (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
 943           dedicated RTC module and leave the RTT available for other uses.)
 944
 945 config RTC_DRV_AT91SAM9_RTT
 946         int
 947         range 0 1
 948         default 0
 949         prompt "RTT module Number" if ARCH_AT91SAM9263
 950         depends on RTC_DRV_AT91SAM9
 951         help
 952           More than one RTT module is available. You can choose which
 953           one will be used as an RTC. The default of zero is normally
 954           OK to use, though some systems use that for non-RTC purposes.
 955
 956 config RTC_DRV_AT91SAM9_GPBR
 957         int
 958         range 0 3 if !ARCH_AT91SAM9263
 959         range 0 15 if ARCH_AT91SAM9263
 960         default 0
 961         prompt "Backup Register Number"
 962         depends on RTC_DRV_AT91SAM9
 963         help
 964           The RTC driver needs to use one of the General Purpose Backup
 965           Registers (GPBRs) as well as the RTT. You can choose which one
 966           will be used. The default of zero is normally OK to use, but
 967           on some systems other software needs to use that register.
 968
 969 config RTC_DRV_AU1XXX
 970         tristate "Au1xxx Counter0 RTC support"
 971         depends on MIPS_ALCHEMY
 972         help
 973           This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
 974           counter) to be used as a RTC.
 975
 976           This driver can also be built as a module. If so, the module
 977           will be called rtc-au1xxx.
 978
 979 config RTC_DRV_BFIN
 980         tristate "Blackfin On-Chip RTC"
 981         depends on BLACKFIN && !BF561
 982         help
 983           If you say yes here you will get support for the
 984           Blackfin On-Chip Real Time Clock.
 985
 986           This driver can also be built as a module. If so, the module
 987           will be called rtc-bfin.
 988
 989 config RTC_DRV_RS5C313
 990         tristate "Ricoh RS5C313"
 991         depends on SH_LANDISK
 992         help
 993           If you say yes here you get support for the Ricoh RS5C313 RTC chips.
 994
 995 config RTC_DRV_GENERIC
 996         tristate "Generic RTC support"
 997         # Please consider writing a new RTC driver instead of using the generic
 998         # RTC abstraction
 999         depends on PARISC || M68K || PPC || SUPERH32
1000         help
1001           Say Y or M here to enable RTC support on systems using the generic
1002           RTC abstraction. If you do not know what you are doing, you should
1003           just say Y.
1004
1005 config RTC_DRV_PXA
1006        tristate "PXA27x/PXA3xx"
1007        depends on ARCH_PXA
1008        help
1009          If you say Y here you will get access to the real time clock
1010          built into your PXA27x or PXA3xx CPU.
1011
1012          This RTC driver uses PXA RTC registers available since pxa27x
1013          series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1014
1015 config RTC_DRV_VT8500
1016         tristate "VIA/WonderMedia 85xx SoC RTC"
1017         depends on ARCH_VT8500
1018         help
1019           If you say Y here you will get access to the real time clock
1020           built into your VIA VT8500 SoC or its relatives.
1021
1022
1023 config RTC_DRV_SUN4V
1024         bool "SUN4V Hypervisor RTC"
1025         depends on SPARC64
1026         help
1027           If you say Y here you will get support for the Hypervisor
1028           based RTC on SUN4V systems.
1029
1030 config RTC_DRV_STARFIRE
1031         bool "Starfire RTC"
1032         depends on SPARC64
1033         help
1034           If you say Y here you will get support for the RTC found on
1035           Starfire systems.
1036
1037 config RTC_DRV_TX4939
1038         tristate "TX4939 SoC"
1039         depends on SOC_TX4939
1040         help
1041           Driver for the internal RTC (Realtime Clock) module found on
1042           Toshiba TX4939 SoC.
1043
1044 config RTC_DRV_MV
1045         tristate "Marvell SoC RTC"
1046         depends on ARCH_KIRKWOOD || ARCH_DOVE
1047         help
1048           If you say yes here you will get support for the in-chip RTC
1049           that can be found in some of Marvell's SoC devices, such as
1050           the Kirkwood 88F6281 and 88F6192.
1051
1052           This driver can also be built as a module. If so, the module
1053           will be called rtc-mv.
1054
1055 config RTC_DRV_PS3
1056         tristate "PS3 RTC"
1057         depends on PPC_PS3
1058         help
1059           If you say yes here you will get support for the RTC on PS3.
1060
1061           This driver can also be built as a module. If so, the module
1062           will be called rtc-ps3.
1063
1064 config RTC_DRV_COH901331
1065         tristate "ST-Ericsson COH 901 331 RTC"
1066         depends on ARCH_U300
1067         help
1068           If you say Y here you will get access to ST-Ericsson
1069           COH 901 331 RTC clock found in some ST-Ericsson Mobile
1070           Platforms.
1071
1072           This driver can also be built as a module. If so, the module
1073           will be called "rtc-coh901331".
1074
1075
1076 config RTC_DRV_STMP
1077         tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1078         depends on ARCH_MXS
1079         help
1080           If you say yes here you will get support for the onboard
1081           STMP3xxx/i.MX23/i.MX28 RTC.
1082
1083           This driver can also be built as a module. If so, the module
1084           will be called rtc-stmp3xxx.
1085
1086 config RTC_DRV_PCAP
1087         tristate "PCAP RTC"
1088         depends on EZX_PCAP
1089         help
1090           If you say Y here you will get support for the RTC found on
1091           the PCAP2 ASIC used on some Motorola phones.
1092
1093 config RTC_DRV_MC13XXX
1094         depends on MFD_MC13XXX
1095         tristate "Freescale MC13xxx RTC"
1096         help
1097           This enables support for the RTCs found on Freescale's PMICs
1098           MC13783 and MC13892.
1099
1100 config RTC_DRV_MPC5121
1101         tristate "Freescale MPC5121 built-in RTC"
1102         depends on PPC_MPC512x || PPC_MPC52xx
1103         help
1104           If you say yes here you will get support for the
1105           built-in RTC on MPC5121 or on MPC5200.
1106
1107           This driver can also be built as a module. If so, the module
1108           will be called rtc-mpc5121.
1109
1110 config RTC_DRV_JZ4740
1111         tristate "Ingenic JZ4740 SoC"
1112         depends on MACH_JZ4740
1113         help
1114           If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1115           controller.
1116
1117           This driver can also be buillt as a module. If so, the module
1118           will be called rtc-jz4740.
1119
1120 config RTC_DRV_LPC32XX
1121         depends on ARCH_LPC32XX
1122         tristate "NXP LPC32XX RTC"
1123         help
1124           This enables support for the NXP RTC in the LPC32XX
1125
1126           This driver can also be buillt as a module. If so, the module
1127           will be called rtc-lpc32xx.
1128
1129 config RTC_DRV_PM8XXX
1130         tristate "Qualcomm PMIC8XXX RTC"
1131         depends on MFD_PM8XXX
1132         help
1133           If you say yes here you get support for the
1134           Qualcomm PMIC8XXX RTC.
1135
1136           To compile this driver as a module, choose M here: the
1137           module will be called rtc-pm8xxx.
1138
1139 config RTC_DRV_TEGRA
1140         tristate "NVIDIA Tegra Internal RTC driver"
1141         depends on ARCH_TEGRA
1142         help
1143           If you say yes here you get support for the
1144           Tegra 200 series internal RTC module.
1145
1146           This drive can also be built as a module. If so, the module
1147           will be called rtc-tegra.
1148
1149 config RTC_DRV_TILE
1150         tristate "Tilera hypervisor RTC support"
1151         depends on TILE
1152         help
1153           Enable support for the Linux driver side of the Tilera
1154           hypervisor's real-time clock interface.
1155
1156 config RTC_DRV_PUV3
1157         tristate "PKUnity v3 RTC support"
1158         depends on ARCH_PUV3
1159         help
1160           This enables support for the RTC in the PKUnity-v3 SoCs.
1161
1162           This drive can also be built as a module. If so, the module
1163           will be called rtc-puv3.
1164
1165 config RTC_DRV_LOONGSON1
1166         tristate "loongson1 RTC support"
1167         depends on MACH_LOONGSON1
1168         help
1169           This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1170           counter) to be used as a RTC.
1171
1172           This driver can also be built as a module. If so, the module
1173           will be called rtc-ls1x.
1174
1175 config RTC_DRV_MXC
1176         tristate "Freescale MXC Real Time Clock"
1177         depends on ARCH_MXC
1178         help
1179            If you say yes here you get support for the Freescale MXC
1180            RTC module.
1181
1182            This driver can also be built as a module, if so, the module
1183            will be called "rtc-mxc".
1184
1185 config RTC_DRV_SNVS
1186         tristate "Freescale SNVS RTC support"
1187         depends on HAS_IOMEM
1188         depends on OF
1189         help
1190            If you say yes here you get support for the Freescale SNVS
1191            Low Power (LP) RTC module.
1192
1193            This driver can also be built as a module, if so, the module
1194            will be called "rtc-snvs".
1195
1196 endif # RTC_CLASS