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