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