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