linux/drivers/rtc/Kconfig
<<
>>
Prefs
   1#
   2# RTC class/drivers configuration
   3#
   4
   5config RTC_LIB
   6        bool
   7
   8menuconfig 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
  18if RTC_CLASS
  19
  20config 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
  28config 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
  36config 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
  59config 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
  65comment "RTC interfaces"
  66
  67config 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
  77config 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
  90config 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
 105config 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
 117config 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
 131comment "I2C RTC drivers"
 132        depends on I2C
 133
 134if I2C
 135
 136config 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
 146config 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
 156config 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
 174config 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
 185config 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
 194config 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
 205config 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
 211config 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
 220config 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
 230config 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
 240config 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
 250config 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
 260config 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
 270config 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
 279config 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
 288config 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
 297config 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
 306config 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
 316config RTC_DRV_PCF8523
 317        tristate "NXP PCF8523"
 318        help
 319          If you say yes here you get support for the NXP PCF8523 RTC
 320          chips.
 321
 322          This driver can also be built as a module. If so, the module
 323          will be called rtc-pcf8523.
 324
 325config RTC_DRV_PCF8563
 326        tristate "Philips PCF8563/Epson RTC8564"
 327        help
 328          If you say yes here you get support for the
 329          Philips PCF8563 RTC chip. The Epson RTC8564
 330          should work as well.
 331
 332          This driver can also be built as a module. If so, the module
 333          will be called rtc-pcf8563.
 334
 335config RTC_DRV_PCF8583
 336        tristate "Philips PCF8583"
 337        help
 338          If you say yes here you get support for the Philips PCF8583
 339          RTC chip found on Acorn RiscPCs. This driver supports the
 340          platform specific method of retrieving the current year from
 341          the RTC's SRAM. It will work on other platforms with the same
 342          chip, but the year will probably have to be tweaked.
 343
 344          This driver can also be built as a module. If so, the module
 345          will be called rtc-pcf8583.
 346
 347config RTC_DRV_M41T80
 348        tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
 349        help
 350          If you say Y here you will get support for the ST M41T60
 351          and M41T80 RTC chips series. Currently, the following chips are
 352          supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
 353          M41ST85, and M41ST87.
 354
 355          This driver can also be built as a module. If so, the module
 356          will be called rtc-m41t80.
 357
 358config RTC_DRV_M41T80_WDT
 359        bool "ST M41T65/M41T80 series RTC watchdog timer"
 360        depends on RTC_DRV_M41T80
 361        help
 362          If you say Y here you will get support for the
 363          watchdog timer in the ST M41T60 and M41T80 RTC chips series.
 364
 365config RTC_DRV_BQ32K
 366        tristate "TI BQ32000"
 367        help
 368          If you say Y here you will get support for the TI
 369          BQ32000 I2C RTC chip.
 370
 371          This driver can also be built as a module. If so, the module
 372          will be called rtc-bq32k.
 373
 374config RTC_DRV_DM355EVM
 375        tristate "TI DaVinci DM355 EVM RTC"
 376        depends on MFD_DM355EVM_MSP
 377        help
 378          Supports the RTC firmware in the MSP430 on the DM355 EVM.
 379
 380config RTC_DRV_TWL92330
 381        boolean "TI TWL92330/Menelaus"
 382        depends on MENELAUS
 383        help
 384          If you say yes here you get support for the RTC on the
 385          TWL92330 "Menelaus" power management chip, used with OMAP2
 386          platforms. The support is integrated with the rest of
 387          the Menelaus driver; it's not separate module.
 388
 389config RTC_DRV_TWL4030
 390        tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
 391        depends on TWL4030_CORE
 392        help
 393          If you say yes here you get support for the RTC on the
 394          TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
 395
 396          This driver can also be built as a module. If so, the module
 397          will be called rtc-twl.
 398
 399config RTC_DRV_TPS6586X
 400        tristate "TI TPS6586X RTC driver"
 401        depends on MFD_TPS6586X
 402        help
 403          TI Power Managment IC TPS6586X supports RTC functionality
 404          along with alarm. This driver supports the RTC driver for
 405          the TPS6586X RTC module.
 406
 407config RTC_DRV_TPS65910
 408        tristate "TI TPS65910 RTC driver"
 409        depends on RTC_CLASS && MFD_TPS65910
 410        help
 411          If you say yes here you get support for the RTC on the
 412          TPS65910 chips.
 413
 414          This driver can also be built as a module. If so, the module
 415          will be called rtc-tps65910.
 416
 417config RTC_DRV_TPS80031
 418        tristate "TI TPS80031/TPS80032 RTC driver"
 419        depends on MFD_TPS80031
 420        help
 421          TI Power Managment IC TPS80031 supports RTC functionality
 422          along with alarm. This driver supports the RTC driver for
 423          the TPS80031 RTC module.
 424
 425config RTC_DRV_RC5T583
 426        tristate "RICOH 5T583 RTC driver"
 427        depends on MFD_RC5T583
 428        help
 429          If you say yes here you get support for the RTC on the
 430          RICOH 5T583 chips.
 431
 432          This driver can also be built as a module. If so, the module
 433          will be called rtc-rc5t583.
 434
 435config RTC_DRV_S35390A
 436        tristate "Seiko Instruments S-35390A"
 437        select BITREVERSE
 438        help
 439          If you say yes here you will get support for the Seiko
 440          Instruments S-35390A.
 441
 442          This driver can also be built as a module. If so the module
 443          will be called rtc-s35390a.
 444
 445config RTC_DRV_FM3130
 446        tristate "Ramtron FM3130"
 447        help
 448          If you say Y here you will get support for the
 449          Ramtron FM3130 RTC chips.
 450          Ramtron FM3130 is a chip with two separate devices inside,
 451          RTC clock and FRAM. This driver provides only RTC functionality.
 452
 453          This driver can also be built as a module. If so the module
 454          will be called rtc-fm3130.
 455
 456config RTC_DRV_RX8581
 457        tristate "Epson RX-8581"
 458        help
 459          If you say yes here you will get support for the Epson RX-8581.
 460
 461          This driver can also be built as a module. If so the module
 462          will be called rtc-rx8581.
 463
 464config RTC_DRV_RX8025
 465        tristate "Epson RX-8025SA/NB"
 466        help
 467          If you say yes here you get support for the Epson
 468          RX-8025SA/NB RTC chips.
 469
 470          This driver can also be built as a module. If so, the module
 471          will be called rtc-rx8025.
 472
 473config RTC_DRV_EM3027
 474        tristate "EM Microelectronic EM3027"
 475        help
 476          If you say yes here you get support for the EM
 477          Microelectronic EM3027 RTC chips.
 478
 479          This driver can also be built as a module. If so, the module
 480          will be called rtc-em3027.
 481
 482config RTC_DRV_RV3029C2
 483        tristate "Micro Crystal RTC"
 484        help
 485          If you say yes here you get support for the Micro Crystal
 486          RV3029-C2 RTC chips.
 487
 488          This driver can also be built as a module. If so, the module
 489          will be called rtc-rv3029c2.
 490
 491endif # I2C
 492
 493comment "SPI RTC drivers"
 494
 495if SPI_MASTER
 496
 497config RTC_DRV_M41T93
 498        tristate "ST M41T93"
 499        help
 500          If you say yes here you will get support for the
 501          ST M41T93 SPI RTC chip.
 502
 503          This driver can also be built as a module. If so, the module
 504          will be called rtc-m41t93.
 505
 506config RTC_DRV_M41T94
 507        tristate "ST M41T94"
 508        help
 509          If you say yes here you will get support for the
 510          ST M41T94 SPI RTC chip.
 511
 512          This driver can also be built as a module. If so, the module
 513          will be called rtc-m41t94.
 514
 515config RTC_DRV_DS1305
 516        tristate "Dallas/Maxim DS1305/DS1306"
 517        help
 518          Select this driver to get support for the Dallas/Maxim DS1305
 519          and DS1306 real time clock chips. These support a trickle
 520          charger, alarms, and NVRAM in addition to the clock.
 521
 522          This driver can also be built as a module. If so, the module
 523          will be called rtc-ds1305.
 524
 525config RTC_DRV_DS1390
 526        tristate "Dallas/Maxim DS1390/93/94"
 527        help
 528          If you say yes here you get support for the
 529          Dallas/Maxim DS1390/93/94 chips.
 530
 531          This driver only supports the RTC feature, and not other chip
 532          features such as alarms and trickle charging.
 533
 534          This driver can also be built as a module. If so, the module
 535          will be called rtc-ds1390.
 536
 537config RTC_DRV_MAX6902
 538        tristate "Maxim MAX6902"
 539        help
 540          If you say yes here you will get support for the
 541          Maxim MAX6902 SPI RTC chip.
 542
 543          This driver can also be built as a module. If so, the module
 544          will be called rtc-max6902.
 545
 546config RTC_DRV_R9701
 547        tristate "Epson RTC-9701JE"
 548        help
 549          If you say yes here you will get support for the
 550          Epson RTC-9701JE SPI RTC chip.
 551
 552          This driver can also be built as a module. If so, the module
 553          will be called rtc-r9701.
 554
 555config RTC_DRV_RS5C348
 556        tristate "Ricoh RS5C348A/B"
 557        help
 558          If you say yes here you get support for the
 559          Ricoh RS5C348A and RS5C348B RTC chips.
 560
 561          This driver can also be built as a module. If so, the module
 562          will be called rtc-rs5c348.
 563
 564config RTC_DRV_DS3234
 565        tristate "Maxim/Dallas DS3234"
 566        help
 567          If you say yes here you get support for the
 568          Maxim/Dallas DS3234 SPI RTC chip.
 569
 570          This driver can also be built as a module. If so, the module
 571          will be called rtc-ds3234.
 572
 573config RTC_DRV_PCF2123
 574        tristate "NXP PCF2123"
 575        help
 576          If you say yes here you get support for the NXP PCF2123
 577          RTC chip.
 578
 579          This driver can also be built as a module. If so, the module
 580          will be called rtc-pcf2123.
 581
 582config RTC_DRV_RX4581
 583        tristate "Epson RX-4581"
 584        help
 585          If you say yes here you will get support for the Epson RX-4581.
 586
 587          This driver can also be built as a module. If so the module
 588          will be called rtc-rx4581.
 589
 590endif # SPI_MASTER
 591
 592comment "Platform RTC drivers"
 593
 594# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
 595# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
 596# global rtc_lock ... it's not yet just another platform_device.
 597
 598config RTC_DRV_CMOS
 599        tristate "PC-style 'CMOS'"
 600        depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
 601        default y if X86
 602        help
 603          Say "yes" here to get direct support for the real time clock
 604          found in every PC or ACPI-based system, and some other boards.
 605          Specifically the original MC146818, compatibles like those in
 606          PC south bridges, the DS12887 or M48T86, some multifunction
 607          or LPC bus chips, and so on.
 608
 609          Your system will need to define the platform device used by
 610          this driver, otherwise it won't be accessible. This means
 611          you can safely enable this driver if you don't know whether
 612          or not your board has this kind of hardware.
 613
 614          This driver can also be built as a module. If so, the module
 615          will be called rtc-cmos.
 616
 617config RTC_DRV_VRTC
 618        tristate "Virtual RTC for Intel MID platforms"
 619        depends on X86_INTEL_MID
 620        default y if X86_INTEL_MID
 621
 622        help
 623        Say "yes" here to get direct support for the real time clock
 624        found on Moorestown platforms. The VRTC is a emulated RTC that
 625        derives its clock source from a real RTC in the PMIC. The MC146818
 626        style programming interface is mostly conserved, but any
 627        updates are done via IPC calls to the system controller FW.
 628
 629config RTC_DRV_DS1216
 630        tristate "Dallas DS1216"
 631        depends on SNI_RM
 632        help
 633          If you say yes here you get support for the Dallas DS1216 RTC chips.
 634
 635config RTC_DRV_DS1286
 636        tristate "Dallas DS1286"
 637        help
 638          If you say yes here you get support for the Dallas DS1286 RTC chips.
 639
 640config RTC_DRV_DS1302
 641        tristate "Dallas DS1302"
 642        depends on SH_SECUREEDGE5410
 643        help
 644          If you say yes here you get support for the Dallas DS1302 RTC chips.
 645
 646config RTC_DRV_DS1511
 647        tristate "Dallas DS1511"
 648        help
 649          If you say yes here you get support for the
 650          Dallas DS1511 timekeeping/watchdog chip.
 651
 652          This driver can also be built as a module. If so, the module
 653          will be called rtc-ds1511.
 654
 655config RTC_DRV_DS1553
 656        tristate "Maxim/Dallas DS1553"
 657        help
 658          If you say yes here you get support for the
 659          Maxim/Dallas DS1553 timekeeping chip.
 660
 661          This driver can also be built as a module. If so, the module
 662          will be called rtc-ds1553.
 663
 664config RTC_DRV_DS1742
 665        tristate "Maxim/Dallas DS1742/1743"
 666        help
 667          If you say yes here you get support for the
 668          Maxim/Dallas DS1742/1743 timekeeping chip.
 669
 670          This driver can also be built as a module. If so, the module
 671          will be called rtc-ds1742.
 672
 673config RTC_DRV_DA9052
 674        tristate "Dialog DA9052/DA9053 RTC"
 675        depends on PMIC_DA9052
 676        help
 677          Say y here to support the RTC driver for Dialog Semiconductor
 678          DA9052-BC and DA9053-AA/Bx PMICs.
 679
 680config RTC_DRV_DA9055
 681        tristate "Dialog Semiconductor DA9055 RTC"
 682        depends on MFD_DA9055
 683        help
 684          If you say yes here you will get support for the
 685          RTC of the Dialog DA9055 PMIC.
 686
 687          This driver can also be built as a module. If so, the module
 688          will be called rtc-da9055
 689
 690config RTC_DRV_EFI
 691        tristate "EFI RTC"
 692        depends on IA64
 693        help
 694          If you say yes here you will get support for the EFI
 695          Real Time Clock.
 696
 697          This driver can also be built as a module. If so, the module
 698          will be called rtc-efi.
 699
 700config RTC_DRV_STK17TA8
 701        tristate "Simtek STK17TA8"
 702        help
 703          If you say yes here you get support for the
 704          Simtek STK17TA8 timekeeping chip.
 705
 706          This driver can also be built as a module. If so, the module
 707          will be called rtc-stk17ta8.
 708
 709config RTC_DRV_M48T86
 710        tristate "ST M48T86/Dallas DS12887"
 711        help
 712          If you say Y here you will get support for the
 713          ST M48T86 and Dallas DS12887 RTC chips.
 714
 715          This driver can also be built as a module. If so, the module
 716          will be called rtc-m48t86.
 717
 718config RTC_DRV_M48T35
 719        tristate "ST M48T35"
 720        help
 721          If you say Y here you will get support for the
 722          ST M48T35 RTC chip.
 723
 724          This driver can also be built as a module, if so, the module
 725          will be called "rtc-m48t35".
 726
 727config RTC_DRV_M48T59
 728        tristate "ST M48T59/M48T08/M48T02"
 729        help
 730          If you say Y here you will get support for the
 731          ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
 732
 733          These chips are usually found in Sun SPARC and UltraSPARC
 734          workstations.
 735
 736          This driver can also be built as a module, if so, the module
 737          will be called "rtc-m48t59".
 738
 739config RTC_DRV_MSM6242
 740        tristate "Oki MSM6242"
 741        help
 742          If you say yes here you get support for the Oki MSM6242
 743          timekeeping chip. It is used in some Amiga models (e.g. A2000).
 744
 745          This driver can also be built as a module. If so, the module
 746          will be called rtc-msm6242.
 747
 748config RTC_DRV_BQ4802
 749        tristate "TI BQ4802"
 750        help
 751          If you say Y here you will get support for the TI
 752          BQ4802 RTC chip.
 753
 754          This driver can also be built as a module. If so, the module
 755          will be called rtc-bq4802.
 756
 757config RTC_DRV_RP5C01
 758        tristate "Ricoh RP5C01"
 759        help
 760          If you say yes here you get support for the Ricoh RP5C01
 761          timekeeping chip. It is used in some Amiga models (e.g. A3000
 762          and A4000).
 763
 764          This driver can also be built as a module. If so, the module
 765          will be called rtc-rp5c01.
 766
 767config RTC_DRV_V3020
 768        tristate "EM Microelectronic V3020"
 769        help
 770          If you say yes here you will get support for the
 771          EM Microelectronic v3020 RTC chip.
 772
 773          This driver can also be built as a module. If so, the module
 774          will be called rtc-v3020.
 775
 776config RTC_DRV_DS2404
 777        tristate "Dallas DS2404"
 778        help
 779          If you say yes here you get support for the
 780          Dallas DS2404 RTC chip.
 781
 782          This driver can also be built as a module. If so, the module
 783          will be called rtc-ds2404.
 784
 785config RTC_DRV_WM831X
 786        tristate "Wolfson Microelectronics WM831x RTC"
 787        depends on MFD_WM831X
 788        help
 789          If you say yes here you will get support for the RTC subsystem
 790          of the Wolfson Microelectronics WM831X series PMICs.
 791
 792          This driver can also be built as a module. If so, the module
 793          will be called "rtc-wm831x".
 794
 795config RTC_DRV_WM8350
 796        tristate "Wolfson Microelectronics WM8350 RTC"
 797        depends on MFD_WM8350
 798        help
 799          If you say yes here you will get support for the RTC subsystem
 800          of the Wolfson Microelectronics WM8350.
 801
 802          This driver can also be built as a module. If so, the module
 803          will be called "rtc-wm8350".
 804
 805config RTC_DRV_SPEAR
 806        tristate "SPEAR ST RTC"
 807        depends on PLAT_SPEAR
 808        default y
 809        help
 810         If you say Y here you will get support for the RTC found on
 811         spear
 812
 813config RTC_DRV_PCF50633
 814        depends on MFD_PCF50633
 815        tristate "NXP PCF50633 RTC"
 816        help
 817          If you say yes here you get support for the RTC subsystem of the
 818          NXP PCF50633 used in embedded systems.
 819
 820config RTC_DRV_AB3100
 821        tristate "ST-Ericsson AB3100 RTC"
 822        depends on AB3100_CORE
 823        default y if AB3100_CORE
 824        help
 825          Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
 826          support. This chip contains a battery- and capacitor-backed RTC.
 827
 828config RTC_DRV_AB8500
 829        tristate "ST-Ericsson AB8500 RTC"
 830        depends on AB8500_CORE
 831        select RTC_INTF_DEV
 832        select RTC_INTF_DEV_UIE_EMUL
 833        help
 834          Select this to enable the ST-Ericsson AB8500 power management IC RTC
 835          support. This chip contains a battery- and capacitor-backed RTC.
 836
 837config RTC_DRV_NUC900
 838        tristate "NUC910/NUC920 RTC driver"
 839        depends on ARCH_W90X900
 840        help
 841          If you say yes here you get support for the RTC subsystem of the
 842          NUC910/NUC920 used in embedded systems.
 843
 844comment "on-CPU RTC drivers"
 845
 846config RTC_DRV_DAVINCI
 847        tristate "TI DaVinci RTC"
 848        depends on ARCH_DAVINCI_DM365
 849        help
 850          If you say yes here you get support for the RTC on the
 851          DaVinci platforms (DM365).
 852
 853          This driver can also be built as a module. If so, the module
 854          will be called rtc-davinci.
 855
 856config RTC_DRV_IMXDI
 857        tristate "Freescale IMX DryIce Real Time Clock"
 858        depends on ARCH_MXC
 859        help
 860           Support for Freescale IMX DryIce RTC
 861
 862           This driver can also be built as a module, if so, the module
 863           will be called "rtc-imxdi".
 864
 865config RTC_DRV_OMAP
 866        tristate "TI OMAP1"
 867        depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
 868        help
 869          Say "yes" here to support the on chip real time clock
 870          present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
 871
 872          This driver can also be built as a module, if so, module
 873          will be called rtc-omap.
 874
 875config HAVE_S3C_RTC
 876        bool
 877        help
 878          This will include RTC support for Samsung SoCs. If
 879          you want to include RTC support for any machine, kindly
 880          select this in the respective mach-XXXX/Kconfig file.
 881
 882config RTC_DRV_S3C
 883        tristate "Samsung S3C series SoC RTC"
 884        depends on ARCH_S3C64XX || HAVE_S3C_RTC
 885        help
 886          RTC (Realtime Clock) driver for the clock inbuilt into the
 887          Samsung S3C24XX series of SoCs. This can provide periodic
 888          interrupt rates from 1Hz to 64Hz for user programs, and
 889          wakeup from Alarm.
 890
 891          The driver currently supports the common features on all the
 892          S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
 893          and S3C2442.
 894
 895          This driver can also be build as a module. If so, the module
 896          will be called rtc-s3c.
 897
 898config RTC_DRV_EP93XX
 899        tristate "Cirrus Logic EP93XX"
 900        depends on ARCH_EP93XX
 901        help
 902          If you say yes here you get support for the
 903          RTC embedded in the Cirrus Logic EP93XX processors.
 904
 905          This driver can also be built as a module. If so, the module
 906          will be called rtc-ep93xx.
 907
 908config RTC_DRV_SA1100
 909        tristate "SA11x0/PXA2xx/PXA910"
 910        depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
 911        help
 912          If you say Y here you will get access to the real time clock
 913          built into your SA11x0 or PXA2xx CPU.
 914
 915          To compile this driver as a module, choose M here: the
 916          module will be called rtc-sa1100.
 917
 918config RTC_DRV_SH
 919        tristate "SuperH On-Chip RTC"
 920        depends on SUPERH && HAVE_CLK
 921        help
 922          Say Y here to enable support for the on-chip RTC found in
 923          most SuperH processors.
 924
 925          To compile this driver as a module, choose M here: the
 926          module will be called rtc-sh.
 927
 928config RTC_DRV_VR41XX
 929        tristate "NEC VR41XX"
 930        depends on CPU_VR41XX
 931        help
 932          If you say Y here you will get access to the real time clock
 933          built into your NEC VR41XX CPU.
 934
 935          To compile this driver as a module, choose M here: the
 936          module will be called rtc-vr41xx.
 937
 938config RTC_DRV_PL030
 939        tristate "ARM AMBA PL030 RTC"
 940        depends on ARM_AMBA
 941        help
 942          If you say Y here you will get access to ARM AMBA
 943          PrimeCell PL030 RTC found on certain ARM SOCs.
 944
 945          To compile this driver as a module, choose M here: the
 946          module will be called rtc-pl030.
 947
 948config RTC_DRV_PL031
 949        tristate "ARM AMBA PL031 RTC"
 950        depends on ARM_AMBA
 951        help
 952          If you say Y here you will get access to ARM AMBA
 953          PrimeCell PL031 RTC found on certain ARM SOCs.
 954
 955          To compile this driver as a module, choose M here: the
 956          module will be called rtc-pl031.
 957
 958config RTC_DRV_AT32AP700X
 959        tristate "AT32AP700X series RTC"
 960        depends on PLATFORM_AT32AP
 961        help
 962          Driver for the internal RTC (Realtime Clock) on Atmel AVR32
 963          AT32AP700x family processors.
 964
 965config RTC_DRV_AT91RM9200
 966        tristate "AT91RM9200 or some AT91SAM9 RTC"
 967        depends on ARCH_AT91
 968        help
 969          Driver for the internal RTC (Realtime Clock) module found on
 970          Atmel AT91RM9200's and some  AT91SAM9 chips. On AT91SAM9 chips
 971          this is powered by the backup power supply.
 972
 973config RTC_DRV_AT91SAM9
 974        tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
 975        depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
 976        help
 977          RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
 978          (Real Time Timer). These timers are powered by the backup power
 979          supply (such as a small coin cell battery), but do not need to
 980          be used as RTCs.
 981
 982          (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
 983          dedicated RTC module and leave the RTT available for other uses.)
 984
 985config RTC_DRV_AT91SAM9_RTT
 986        int
 987        range 0 1
 988        default 0
 989        prompt "RTT module Number" if ARCH_AT91SAM9263
 990        depends on RTC_DRV_AT91SAM9
 991        help
 992          More than one RTT module is available. You can choose which
 993          one will be used as an RTC. The default of zero is normally
 994          OK to use, though some systems use that for non-RTC purposes.
 995
 996config RTC_DRV_AT91SAM9_GPBR
 997        int
 998        range 0 3 if !ARCH_AT91SAM9263
 999        range 0 15 if ARCH_AT91SAM9263
1000        default 0
1001        prompt "Backup Register Number"
1002        depends on RTC_DRV_AT91SAM9
1003        help
1004          The RTC driver needs to use one of the General Purpose Backup
1005          Registers (GPBRs) as well as the RTT. You can choose which one
1006          will be used. The default of zero is normally OK to use, but
1007          on some systems other software needs to use that register.
1008
1009config RTC_DRV_AU1XXX
1010        tristate "Au1xxx Counter0 RTC support"
1011        depends on MIPS_ALCHEMY
1012        help
1013          This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1014          counter) to be used as a RTC.
1015
1016          This driver can also be built as a module. If so, the module
1017          will be called rtc-au1xxx.
1018
1019config RTC_DRV_BFIN
1020        tristate "Blackfin On-Chip RTC"
1021        depends on BLACKFIN && !BF561
1022        help
1023          If you say yes here you will get support for the
1024          Blackfin On-Chip Real Time Clock.
1025
1026          This driver can also be built as a module. If so, the module
1027          will be called rtc-bfin.
1028
1029config RTC_DRV_RS5C313
1030        tristate "Ricoh RS5C313"
1031        depends on SH_LANDISK
1032        help
1033          If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1034
1035config RTC_DRV_GENERIC
1036        tristate "Generic RTC support"
1037        # Please consider writing a new RTC driver instead of using the generic
1038        # RTC abstraction
1039        depends on PARISC || M68K || PPC || SUPERH32
1040        help
1041          Say Y or M here to enable RTC support on systems using the generic
1042          RTC abstraction. If you do not know what you are doing, you should
1043          just say Y.
1044
1045config RTC_DRV_PXA
1046       tristate "PXA27x/PXA3xx"
1047       depends on ARCH_PXA
1048       help
1049         If you say Y here you will get access to the real time clock
1050         built into your PXA27x or PXA3xx CPU.
1051
1052         This RTC driver uses PXA RTC registers available since pxa27x
1053         series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1054
1055config RTC_DRV_VT8500
1056        tristate "VIA/WonderMedia 85xx SoC RTC"
1057        depends on ARCH_VT8500
1058        help
1059          If you say Y here you will get access to the real time clock
1060          built into your VIA VT8500 SoC or its relatives.
1061
1062
1063config RTC_DRV_SUN4V
1064        bool "SUN4V Hypervisor RTC"
1065        depends on SPARC64
1066        help
1067          If you say Y here you will get support for the Hypervisor
1068          based RTC on SUN4V systems.
1069
1070config RTC_DRV_STARFIRE
1071        bool "Starfire RTC"
1072        depends on SPARC64
1073        help
1074          If you say Y here you will get support for the RTC found on
1075          Starfire systems.
1076
1077config RTC_DRV_TX4939
1078        tristate "TX4939 SoC"
1079        depends on SOC_TX4939
1080        help
1081          Driver for the internal RTC (Realtime Clock) module found on
1082          Toshiba TX4939 SoC.
1083
1084config RTC_DRV_MV
1085        tristate "Marvell SoC RTC"
1086        depends on ARCH_KIRKWOOD || ARCH_DOVE || ARCH_MVEBU
1087        help
1088          If you say yes here you will get support for the in-chip RTC
1089          that can be found in some of Marvell's SoC devices, such as
1090          the Kirkwood 88F6281 and 88F6192.
1091
1092          This driver can also be built as a module. If so, the module
1093          will be called rtc-mv.
1094
1095config RTC_DRV_PS3
1096        tristate "PS3 RTC"
1097        depends on PPC_PS3
1098        help
1099          If you say yes here you will get support for the RTC on PS3.
1100
1101          This driver can also be built as a module. If so, the module
1102          will be called rtc-ps3.
1103
1104config RTC_DRV_COH901331
1105        tristate "ST-Ericsson COH 901 331 RTC"
1106        depends on ARCH_U300
1107        help
1108          If you say Y here you will get access to ST-Ericsson
1109          COH 901 331 RTC clock found in some ST-Ericsson Mobile
1110          Platforms.
1111
1112          This driver can also be built as a module. If so, the module
1113          will be called "rtc-coh901331".
1114
1115
1116config RTC_DRV_STMP
1117        tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1118        depends on ARCH_MXS
1119        help
1120          If you say yes here you will get support for the onboard
1121          STMP3xxx/i.MX23/i.MX28 RTC.
1122
1123          This driver can also be built as a module. If so, the module
1124          will be called rtc-stmp3xxx.
1125
1126config RTC_DRV_PCAP
1127        tristate "PCAP RTC"
1128        depends on EZX_PCAP
1129        help
1130          If you say Y here you will get support for the RTC found on
1131          the PCAP2 ASIC used on some Motorola phones.
1132
1133config RTC_DRV_MC13XXX
1134        depends on MFD_MC13XXX
1135        tristate "Freescale MC13xxx RTC"
1136        help
1137          This enables support for the RTCs found on Freescale's PMICs
1138          MC13783 and MC13892.
1139
1140config RTC_DRV_MPC5121
1141        tristate "Freescale MPC5121 built-in RTC"
1142        depends on PPC_MPC512x || PPC_MPC52xx
1143        help
1144          If you say yes here you will get support for the
1145          built-in RTC on MPC5121 or on MPC5200.
1146
1147          This driver can also be built as a module. If so, the module
1148          will be called rtc-mpc5121.
1149
1150config RTC_DRV_JZ4740
1151        tristate "Ingenic JZ4740 SoC"
1152        depends on MACH_JZ4740
1153        help
1154          If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1155          controller.
1156
1157          This driver can also be buillt as a module. If so, the module
1158          will be called rtc-jz4740.
1159
1160config RTC_DRV_LPC32XX
1161        depends on ARCH_LPC32XX
1162        tristate "NXP LPC32XX RTC"
1163        help
1164          This enables support for the NXP RTC in the LPC32XX
1165
1166          This driver can also be buillt as a module. If so, the module
1167          will be called rtc-lpc32xx.
1168
1169config RTC_DRV_PM8XXX
1170        tristate "Qualcomm PMIC8XXX RTC"
1171        depends on MFD_PM8XXX
1172        help
1173          If you say yes here you get support for the
1174          Qualcomm PMIC8XXX RTC.
1175
1176          To compile this driver as a module, choose M here: the
1177          module will be called rtc-pm8xxx.
1178
1179config RTC_DRV_TEGRA
1180        tristate "NVIDIA Tegra Internal RTC driver"
1181        depends on ARCH_TEGRA
1182        help
1183          If you say yes here you get support for the
1184          Tegra 200 series internal RTC module.
1185
1186          This drive can also be built as a module. If so, the module
1187          will be called rtc-tegra.
1188
1189config RTC_DRV_TILE
1190        tristate "Tilera hypervisor RTC support"
1191        depends on TILE
1192        help
1193          Enable support for the Linux driver side of the Tilera
1194          hypervisor's real-time clock interface.
1195
1196config RTC_DRV_PUV3
1197        tristate "PKUnity v3 RTC support"
1198        depends on ARCH_PUV3
1199        help
1200          This enables support for the RTC in the PKUnity-v3 SoCs.
1201
1202          This drive can also be built as a module. If so, the module
1203          will be called rtc-puv3.
1204
1205config RTC_DRV_LOONGSON1
1206        tristate "loongson1 RTC support"
1207        depends on MACH_LOONGSON1
1208        help
1209          This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1210          counter) to be used as a RTC.
1211
1212          This driver can also be built as a module. If so, the module
1213          will be called rtc-ls1x.
1214
1215config RTC_DRV_MXC
1216        tristate "Freescale MXC Real Time Clock"
1217        depends on ARCH_MXC
1218        help
1219           If you say yes here you get support for the Freescale MXC
1220           RTC module.
1221
1222           This driver can also be built as a module, if so, the module
1223           will be called "rtc-mxc".
1224
1225config RTC_DRV_SNVS
1226        tristate "Freescale SNVS RTC support"
1227        depends on HAS_IOMEM
1228        depends on OF
1229        help
1230           If you say yes here you get support for the Freescale SNVS
1231           Low Power (LP) RTC module.
1232
1233           This driver can also be built as a module, if so, the module
1234           will be called "rtc-snvs".
1235
1236comment "HID Sensor RTC drivers"
1237
1238config RTC_DRV_HID_SENSOR_TIME
1239        tristate "HID Sensor Time"
1240        depends on USB_HID
1241        select IIO
1242        select HID_SENSOR_HUB
1243        select HID_SENSOR_IIO_COMMON
1244        help
1245          Say yes here to build support for the HID Sensors of type Time.
1246          This drivers makes such sensors available as RTCs.
1247
1248          If this driver is compiled as a module, it will be named
1249          rtc-hid-sensor-time.
1250
1251
1252endif # RTC_CLASS
1253
lxr.linux.no kindly hosted by Redpill Linpro AS, provider of Linux consulting and operations services since 1995.