drivers/rtc/Kconfig

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