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