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