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         default y
  23         help
  24           If you say yes here, the system time (wall clock) will be set using
  25           the value read from a specified RTC device. This is useful to avoid
  26           unnecessary fsck runs at boot time, and to network better.
  27
  28 config RTC_SYSTOHC
  29         bool "Set the RTC time based on NTP synchronization"
  30         default y
  31         help
  32           If you say yes here, the system time (wall clock) will be stored
  33           in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
  34           minutes if userspace reports synchronized NTP status.
  35
  36 config RTC_HCTOSYS_DEVICE
  37         string "RTC used to set the system time"
  38         depends on RTC_HCTOSYS = y || RTC_SYSTOHC = y
  39         default "rtc0"
  40         help
  41           The RTC device that will be used to (re)initialize the system
  42           clock, usually rtc0. Initialization is done when the system
  43           starts up, and when it resumes from a low power state. This
  44           device should record time in UTC, since the kernel won't do
  45           timezone correction.
  46
  47           The driver for this RTC device must be loaded before late_initcall
  48           functions run, so it must usually be statically linked.
  49
  50           This clock should be battery-backed, so that it reads the correct
  51           time when the system boots from a power-off state. Otherwise, your
  52           system will need an external clock source (like an NTP server).
  53
  54           If the clock you specify here is not battery backed, it may still
  55           be useful to reinitialize system time when resuming from system
  56           sleep states. Do not specify an RTC here unless it stays powered
  57           during all this system's supported sleep states.
  58
  59 config RTC_DEBUG
  60         bool "RTC debug support"
  61         help
  62           Say yes here to enable debugging support in the RTC framework
  63           and individual RTC drivers.
  64
  65 comment "RTC interfaces"
  66
  67 config RTC_INTF_SYSFS
  68         bool "/sys/class/rtc/rtcN (sysfs)"
  69         depends on SYSFS
  70         default RTC_CLASS
  71         help
  72           Say yes here if you want to use your RTCs using sysfs interfaces,
  73           /sys/class/rtc/rtc0 through /sys/.../rtcN.
  74
  75           If unsure, say Y.
  76
  77 config RTC_INTF_PROC
  78         bool "/proc/driver/rtc (procfs for rtcN)"
  79         depends on PROC_FS
  80         default RTC_CLASS
  81         help
  82           Say yes here if you want to use your system clock RTC through
  83           the proc interface, /proc/driver/rtc.
  84           Other RTCs will not be available through that API.
  85           If there is no RTC for the system clock, then the first RTC(rtc0)
  86           is used by default.
  87
  88           If unsure, say Y.
  89
  90 config RTC_INTF_DEV
  91         bool "/dev/rtcN (character devices)"
  92         default RTC_CLASS
  93         help
  94           Say yes here if you want to use your RTCs using the /dev
  95           interfaces, which "udev" sets up as /dev/rtc0 through
  96           /dev/rtcN.
  97
  98           You may want to set up a symbolic link so one of these
  99           can be accessed as /dev/rtc, which is a name
 100           expected by "hwclock" and some other programs. Recent
 101           versions of "udev" are known to set up the symlink for you.
 102
 103           If unsure, say Y.
 104
 105 config RTC_INTF_DEV_UIE_EMUL
 106         bool "RTC UIE emulation on dev interface"
 107         depends on RTC_INTF_DEV
 108         help
 109           Provides an emulation for RTC_UIE if the underlying rtc chip
 110           driver does not expose RTC_UIE ioctls. Those requests generate
 111           once-per-second update interrupts, used for synchronization.
 112
 113           The emulation code will read the time from the hardware
 114           clock several times per second, please enable this option
 115           only if you know that you really need it.
 116
 117 config RTC_DRV_TEST
 118         tristate "Test driver/device"
 119         help
 120           If you say yes here you get support for the
 121           RTC test driver. It's a software RTC which can be
 122           used to test the RTC subsystem APIs. It gets
 123           the time from the system clock.
 124           You want this driver only if you are doing development
 125           on the RTC subsystem. Please read the source code
 126           for further details.
 127
 128           This driver can also be built as a module. If so, the module
 129           will be called rtc-test.
 130
 131 comment "I2C RTC drivers"
 132         depends on I2C
 133
 134 if I2C
 135
 136 config RTC_DRV_88PM860X
 137         tristate "Marvell 88PM860x"
 138         depends on I2C && MFD_88PM860X
 139         help
 140           If you say yes here you get support for RTC function in Marvell
 141           88PM860x chips.
 142
 143           This driver can also be built as a module. If so, the module
 144           will be called rtc-88pm860x.
 145
 146 config RTC_DRV_88PM80X
 147         tristate "Marvell 88PM80x"
 148         depends on I2C && MFD_88PM800
 149         help
 150           If you say yes here you get support for RTC function in Marvell
 151           88PM80x chips.
 152
 153           This driver can also be built as a module. If so, the module
 154           will be called rtc-88pm80x.
 155
 156 config RTC_DRV_ABB5ZES3
 157        depends on I2C
 158        select REGMAP_I2C
 159        tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
 160        help
 161           If you say yes here you get support for the Abracon
 162           AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
 163
 164           This driver can also be built as a module. If so, the module
 165           will be called rtc-ab-b5ze-s3.
 166
 167 config RTC_DRV_AS3722
 168         tristate "ams AS3722 RTC driver"
 169         depends on MFD_AS3722
 170         help
 171           If you say yes here you get support for the RTC of ams AS3722 PMIC
 172           chips.
 173
 174           This driver can also be built as a module. If so, the module
 175           will be called rtc-as3722.
 176
 177 config RTC_DRV_DS1307
 178         tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
 179         help
 180           If you say yes here you get support for various compatible RTC
 181           chips (often with battery backup) connected with I2C. This driver
 182           should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
 183           EPSON RX-8025 and probably other chips. In some cases the RTC
 184           must already have been initialized (by manufacturing or a
 185           bootloader).
 186
 187           The first seven registers on these chips hold an RTC, and other
 188           registers may add features such as NVRAM, a trickle charger for
 189           the RTC/NVRAM backup power, and alarms. NVRAM is visible in
 190           sysfs, but other chip features may not be available.
 191
 192           This driver can also be built as a module. If so, the module
 193           will be called rtc-ds1307.
 194
 195 config RTC_DRV_DS1374
 196         tristate "Dallas/Maxim DS1374"
 197         depends on I2C
 198         help
 199           If you say yes here you get support for Dallas Semiconductor
 200           DS1374 real-time clock chips. If an interrupt is associated
 201           with the device, the alarm functionality is supported.
 202
 203           This driver can also be built as a module. If so, the module
 204           will be called rtc-ds1374.
 205
 206 config RTC_DRV_DS1374_WDT
 207         bool "Dallas/Maxim DS1374 watchdog timer"
 208         depends on RTC_DRV_DS1374
 209         help
 210           If you say Y here you will get support for the
 211           watchdog timer in the Dallas Semiconductor DS1374
 212           real-time clock chips.
 213
 214 config RTC_DRV_DS1672
 215         tristate "Dallas/Maxim DS1672"
 216         help
 217           If you say yes here you get support for the
 218           Dallas/Maxim DS1672 timekeeping chip.
 219
 220           This driver can also be built as a module. If so, the module
 221           will be called rtc-ds1672.
 222
 223 config RTC_DRV_DS3232
 224         tristate "Dallas/Maxim DS3232"
 225         depends on I2C
 226         help
 227           If you say yes here you get support for Dallas Semiconductor
 228           DS3232 real-time clock chips. If an interrupt is associated
 229           with the device, the alarm functionality is supported.
 230
 231           This driver can also be built as a module.  If so, the module
 232           will be called rtc-ds3232.
 233
 234 config RTC_DRV_HYM8563
 235         tristate "Haoyu Microelectronics HYM8563"
 236         depends on I2C && OF
 237         help
 238           Say Y to enable support for the HYM8563 I2C RTC chip. Apart
 239           from the usual rtc functions it provides a clock output of
 240           up to 32kHz.
 241
 242           This driver can also be built as a module. If so, the module
 243           will be called rtc-hym8563.
 244
 245 config RTC_DRV_LP8788
 246         tristate "TI LP8788 RTC driver"
 247         depends on MFD_LP8788
 248         help
 249           Say Y to enable support for the LP8788 RTC/ALARM driver.
 250
 251 config RTC_DRV_MAX6900
 252         tristate "Maxim MAX6900"
 253         help
 254           If you say yes here you will get support for the
 255           Maxim MAX6900 I2C RTC chip.
 256
 257           This driver can also be built as a module. If so, the module
 258           will be called rtc-max6900.
 259
 260 config RTC_DRV_MAX8907
 261         tristate "Maxim MAX8907"
 262         depends on MFD_MAX8907
 263         help
 264           If you say yes here you will get support for the
 265           RTC of Maxim MAX8907 PMIC.
 266
 267           This driver can also be built as a module. If so, the module
 268           will be called rtc-max8907.
 269
 270 config RTC_DRV_MAX8925
 271         tristate "Maxim MAX8925"
 272         depends on MFD_MAX8925
 273         help
 274           If you say yes here you will get support for the
 275           RTC of Maxim MAX8925 PMIC.
 276
 277           This driver can also be built as a module. If so, the module
 278           will be called rtc-max8925.
 279
 280 config RTC_DRV_MAX8998
 281         tristate "Maxim MAX8998"
 282         depends on MFD_MAX8998
 283         help
 284           If you say yes here you will get support for the
 285           RTC of Maxim MAX8998 PMIC.
 286
 287           This driver can also be built as a module. If so, the module
 288           will be called rtc-max8998.
 289
 290 config RTC_DRV_MAX8997
 291         tristate "Maxim MAX8997"
 292         depends on MFD_MAX8997
 293         help
 294           If you say yes here you will get support for the
 295           RTC of Maxim MAX8997 PMIC.
 296
 297           This driver can also be built as a module. If so, the module
 298           will be called rtc-max8997.
 299
 300 config RTC_DRV_MAX77686
 301         tristate "Maxim MAX77686"
 302         depends on MFD_MAX77686
 303         help
 304           If you say yes here you will get support for the
 305           RTC of Maxim MAX77686 PMIC.
 306
 307           This driver can also be built as a module. If so, the module
 308           will be called rtc-max77686.
 309
 310 config RTC_DRV_RK808
 311         tristate "Rockchip RK808 RTC"
 312         depends on MFD_RK808
 313         help
 314           If you say yes here you will get support for the
 315           RTC of RK808 PMIC.
 316
 317           This driver can also be built as a module. If so, the module
 318           will be called rk808-rtc.
 319
 320 config RTC_DRV_MAX77802
 321         tristate "Maxim 77802 RTC"
 322         depends on MFD_MAX77686
 323         help
 324           If you say yes here you will get support for the
 325           RTC of Maxim MAX77802 PMIC.
 326
 327           This driver can also be built as a module. If so, the module
 328           will be called rtc-max77802.
 329
 330 config RTC_DRV_RS5C372
 331         tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
 332         help
 333           If you say yes here you get support for the
 334           Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
 335
 336           This driver can also be built as a module. If so, the module
 337           will be called rtc-rs5c372.
 338
 339 config RTC_DRV_ISL1208
 340         tristate "Intersil ISL1208"
 341         help
 342           If you say yes here you get support for the
 343           Intersil ISL1208 RTC chip.
 344
 345           This driver can also be built as a module. If so, the module
 346           will be called rtc-isl1208.
 347
 348 config RTC_DRV_ISL12022
 349         tristate "Intersil ISL12022"
 350         help
 351           If you say yes here you get support for the
 352           Intersil ISL12022 RTC chip.
 353
 354           This driver can also be built as a module. If so, the module
 355           will be called rtc-isl12022.
 356
 357 config RTC_DRV_ISL12057
 358        depends on I2C
 359        select REGMAP_I2C
 360        tristate "Intersil ISL12057"
 361        help
 362           If you say yes here you get support for the Intersil ISL12057
 363           I2C RTC chip.
 364
 365           This driver can also be built as a module. If so, the module
 366           will be called rtc-isl12057.
 367
 368 config RTC_DRV_X1205
 369         tristate "Xicor/Intersil X1205"
 370         help
 371           If you say yes here you get support for the
 372           Xicor/Intersil X1205 RTC chip.
 373
 374           This driver can also be built as a module. If so, the module
 375           will be called rtc-x1205.
 376
 377 config RTC_DRV_PALMAS
 378         tristate "TI Palmas RTC driver"
 379         depends on MFD_PALMAS
 380         help
 381           If you say yes here you get support for the RTC of TI PALMA series PMIC
 382           chips.
 383
 384           This driver can also be built as a module. If so, the module
 385           will be called rtc-palma.
 386
 387 config RTC_DRV_PCF2127
 388         tristate "NXP PCF2127"
 389         help
 390           If you say yes here you get support for the NXP PCF2127/29 RTC
 391           chips.
 392
 393           This driver can also be built as a module. If so, the module
 394           will be called rtc-pcf2127.
 395
 396 config RTC_DRV_PCF8523
 397         tristate "NXP PCF8523"
 398         help
 399           If you say yes here you get support for the NXP PCF8523 RTC
 400           chips.
 401
 402           This driver can also be built as a module. If so, the module
 403           will be called rtc-pcf8523.
 404
 405 config RTC_DRV_PCF8563
 406         tristate "Philips PCF8563/Epson RTC8564"
 407         help
 408           If you say yes here you get support for the
 409           Philips PCF8563 RTC chip. The Epson RTC8564
 410           should work as well.
 411
 412           This driver can also be built as a module. If so, the module
 413           will be called rtc-pcf8563.
 414
 415 config RTC_DRV_PCF85063
 416         tristate "nxp PCF85063"
 417         help
 418           If you say yes here you get support for the PCF85063 RTC chip
 419
 420           This driver can also be built as a module. If so, the module
 421           will be called rtc-pcf85063.
 422
 423 config RTC_DRV_PCF8583
 424         tristate "Philips PCF8583"
 425         help
 426           If you say yes here you get support for the Philips PCF8583
 427           RTC chip found on Acorn RiscPCs. This driver supports the
 428           platform specific method of retrieving the current year from
 429           the RTC's SRAM. It will work on other platforms with the same
 430           chip, but the year will probably have to be tweaked.
 431
 432           This driver can also be built as a module. If so, the module
 433           will be called rtc-pcf8583.
 434
 435 config RTC_DRV_M41T80
 436         tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
 437         help
 438           If you say Y here you will get support for the ST M41T60
 439           and M41T80 RTC chips series. Currently, the following chips are
 440           supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
 441           M41ST85, M41ST87, and MicroCrystal RV4162.
 442
 443           This driver can also be built as a module. If so, the module
 444           will be called rtc-m41t80.
 445
 446 config RTC_DRV_M41T80_WDT
 447         bool "ST M41T65/M41T80 series RTC watchdog timer"
 448         depends on RTC_DRV_M41T80
 449         help
 450           If you say Y here you will get support for the
 451           watchdog timer in the ST M41T60 and M41T80 RTC chips series.
 452
 453 config RTC_DRV_BQ32K
 454         tristate "TI BQ32000"
 455         help
 456           If you say Y here you will get support for the TI
 457           BQ32000 I2C RTC chip.
 458
 459           This driver can also be built as a module. If so, the module
 460           will be called rtc-bq32k.
 461
 462 config RTC_DRV_DM355EVM
 463         tristate "TI DaVinci DM355 EVM RTC"
 464         depends on MFD_DM355EVM_MSP
 465         help
 466           Supports the RTC firmware in the MSP430 on the DM355 EVM.
 467
 468 config RTC_DRV_TWL92330
 469         bool "TI TWL92330/Menelaus"
 470         depends on MENELAUS
 471         help
 472           If you say yes here you get support for the RTC on the
 473           TWL92330 "Menelaus" power management chip, used with OMAP2
 474           platforms. The support is integrated with the rest of
 475           the Menelaus driver; it's not separate module.
 476
 477 config RTC_DRV_TWL4030
 478         tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
 479         depends on TWL4030_CORE
 480         help
 481           If you say yes here you get support for the RTC on the
 482           TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
 483
 484           This driver can also be built as a module. If so, the module
 485           will be called rtc-twl.
 486
 487 config RTC_DRV_TPS6586X
 488         tristate "TI TPS6586X RTC driver"
 489         depends on MFD_TPS6586X
 490         help
 491           TI Power Management IC TPS6586X supports RTC functionality
 492           along with alarm. This driver supports the RTC driver for
 493           the TPS6586X RTC module.
 494
 495 config RTC_DRV_TPS65910
 496         tristate "TI TPS65910 RTC driver"
 497         depends on RTC_CLASS && MFD_TPS65910
 498         help
 499           If you say yes here you get support for the RTC on the
 500           TPS65910 chips.
 501
 502           This driver can also be built as a module. If so, the module
 503           will be called rtc-tps65910.
 504
 505 config RTC_DRV_TPS80031
 506         tristate "TI TPS80031/TPS80032 RTC driver"
 507         depends on MFD_TPS80031
 508         help
 509           TI Power Management IC TPS80031 supports RTC functionality
 510           along with alarm. This driver supports the RTC driver for
 511           the TPS80031 RTC module.
 512
 513 config RTC_DRV_RC5T583
 514         tristate "RICOH 5T583 RTC driver"
 515         depends on MFD_RC5T583
 516         help
 517           If you say yes here you get support for the RTC on the
 518           RICOH 5T583 chips.
 519
 520           This driver can also be built as a module. If so, the module
 521           will be called rtc-rc5t583.
 522
 523 config RTC_DRV_S35390A
 524         tristate "Seiko Instruments S-35390A"
 525         select BITREVERSE
 526         help
 527           If you say yes here you will get support for the Seiko
 528           Instruments S-35390A.
 529
 530           This driver can also be built as a module. If so the module
 531           will be called rtc-s35390a.
 532
 533 config RTC_DRV_FM3130
 534         tristate "Ramtron FM3130"
 535         help
 536           If you say Y here you will get support for the
 537           Ramtron FM3130 RTC chips.
 538           Ramtron FM3130 is a chip with two separate devices inside,
 539           RTC clock and FRAM. This driver provides only RTC functionality.
 540
 541           This driver can also be built as a module. If so the module
 542           will be called rtc-fm3130.
 543
 544 config RTC_DRV_RX8581
 545         tristate "Epson RX-8581"
 546         help
 547           If you say yes here you will get support for the Epson RX-8581.
 548
 549           This driver can also be built as a module. If so the module
 550           will be called rtc-rx8581.
 551
 552 config RTC_DRV_RX8025
 553         tristate "Epson RX-8025SA/NB"
 554         help
 555           If you say yes here you get support for the Epson
 556           RX-8025SA/NB RTC chips.
 557
 558           This driver can also be built as a module. If so, the module
 559           will be called rtc-rx8025.
 560
 561 config RTC_DRV_EM3027
 562         tristate "EM Microelectronic EM3027"
 563         help
 564           If you say yes here you get support for the EM
 565           Microelectronic EM3027 RTC chips.
 566
 567           This driver can also be built as a module. If so, the module
 568           will be called rtc-em3027.
 569
 570 config RTC_DRV_RV3029C2
 571         tristate "Micro Crystal RTC"
 572         help
 573           If you say yes here you get support for the Micro Crystal
 574           RV3029-C2 RTC chips.
 575
 576           This driver can also be built as a module. If so, the module
 577           will be called rtc-rv3029c2.
 578
 579 config RTC_DRV_S5M
 580         tristate "Samsung S2M/S5M series"
 581         depends on MFD_SEC_CORE
 582         help
 583           If you say yes here you will get support for the
 584           RTC of Samsung S2MPS14 and S5M PMIC series.
 585
 586           This driver can also be built as a module. If so, the module
 587           will be called rtc-s5m.
 588
 589 endif # I2C
 590
 591 comment "SPI RTC drivers"
 592
 593 if SPI_MASTER
 594
 595 config RTC_DRV_M41T93
 596         tristate "ST M41T93"
 597         help
 598           If you say yes here you will get support for the
 599           ST M41T93 SPI RTC chip.
 600
 601           This driver can also be built as a module. If so, the module
 602           will be called rtc-m41t93.
 603
 604 config RTC_DRV_M41T94
 605         tristate "ST M41T94"
 606         help
 607           If you say yes here you will get support for the
 608           ST M41T94 SPI RTC chip.
 609
 610           This driver can also be built as a module. If so, the module
 611           will be called rtc-m41t94.
 612
 613 config RTC_DRV_DS1305
 614         tristate "Dallas/Maxim DS1305/DS1306"
 615         help
 616           Select this driver to get support for the Dallas/Maxim DS1305
 617           and DS1306 real time clock chips. These support a trickle
 618           charger, alarms, and NVRAM in addition to the clock.
 619
 620           This driver can also be built as a module. If so, the module
 621           will be called rtc-ds1305.
 622
 623 config RTC_DRV_DS1343
 624         select REGMAP_SPI
 625         tristate "Dallas/Maxim DS1343/DS1344"
 626         help
 627           If you say yes here you get support for the
 628           Dallas/Maxim DS1343 and DS1344 real time clock chips.
 629           Support for trickle charger, alarm is provided.
 630
 631           This driver can also be built as a module. If so, the module
 632           will be called rtc-ds1343.
 633
 634 config RTC_DRV_DS1347
 635         tristate "Dallas/Maxim DS1347"
 636         help
 637           If you say yes here you get support for the
 638           Dallas/Maxim DS1347 chips.
 639
 640           This driver only supports the RTC feature, and not other chip
 641           features such as alarms.
 642
 643           This driver can also be built as a module. If so, the module
 644           will be called rtc-ds1347.
 645
 646 config RTC_DRV_DS1390
 647         tristate "Dallas/Maxim DS1390/93/94"
 648         help
 649           If you say yes here you get support for the
 650           Dallas/Maxim DS1390/93/94 chips.
 651
 652           This driver only supports the RTC feature, and not other chip
 653           features such as alarms and trickle charging.
 654
 655           This driver can also be built as a module. If so, the module
 656           will be called rtc-ds1390.
 657
 658 config RTC_DRV_MAX6902
 659         tristate "Maxim MAX6902"
 660         help
 661           If you say yes here you will get support for the
 662           Maxim MAX6902 SPI RTC chip.
 663
 664           This driver can also be built as a module. If so, the module
 665           will be called rtc-max6902.
 666
 667 config RTC_DRV_R9701
 668         tristate "Epson RTC-9701JE"
 669         help
 670           If you say yes here you will get support for the
 671           Epson RTC-9701JE SPI RTC chip.
 672
 673           This driver can also be built as a module. If so, the module
 674           will be called rtc-r9701.
 675
 676 config RTC_DRV_RS5C348
 677         tristate "Ricoh RS5C348A/B"
 678         help
 679           If you say yes here you get support for the
 680           Ricoh RS5C348A and RS5C348B RTC chips.
 681
 682           This driver can also be built as a module. If so, the module
 683           will be called rtc-rs5c348.
 684
 685 config RTC_DRV_DS3234
 686         tristate "Maxim/Dallas DS3234"
 687         help
 688           If you say yes here you get support for the
 689           Maxim/Dallas DS3234 SPI RTC chip.
 690
 691           This driver can also be built as a module. If so, the module
 692           will be called rtc-ds3234.
 693
 694 config RTC_DRV_PCF2123
 695         tristate "NXP PCF2123"
 696         help
 697           If you say yes here you get support for the NXP PCF2123
 698           RTC chip.
 699
 700           This driver can also be built as a module. If so, the module
 701           will be called rtc-pcf2123.
 702
 703 config RTC_DRV_RX4581
 704         tristate "Epson RX-4581"
 705         help
 706           If you say yes here you will get support for the Epson RX-4581.
 707
 708           This driver can also be built as a module. If so the module
 709           will be called rtc-rx4581.
 710
 711 config RTC_DRV_MCP795
 712         tristate "Microchip MCP795"
 713         help
 714           If you say yes here you will get support for the Microchip MCP795.
 715
 716           This driver can also be built as a module. If so the module
 717           will be called rtc-mcp795.
 718
 719 endif # SPI_MASTER
 720
 721 comment "Platform RTC drivers"
 722
 723 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
 724 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
 725 # global rtc_lock ... it's not yet just another platform_device.
 726
 727 config RTC_DRV_CMOS
 728         tristate "PC-style 'CMOS'"
 729         depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
 730         default y if X86
 731         help
 732           Say "yes" here to get direct support for the real time clock
 733           found in every PC or ACPI-based system, and some other boards.
 734           Specifically the original MC146818, compatibles like those in
 735           PC south bridges, the DS12887 or M48T86, some multifunction
 736           or LPC bus chips, and so on.
 737
 738           Your system will need to define the platform device used by
 739           this driver, otherwise it won't be accessible. This means
 740           you can safely enable this driver if you don't know whether
 741           or not your board has this kind of hardware.
 742
 743           This driver can also be built as a module. If so, the module
 744           will be called rtc-cmos.
 745
 746 config RTC_DRV_ALPHA
 747         bool "Alpha PC-style CMOS"
 748         depends on ALPHA
 749         default y
 750         help
 751           Direct support for the real-time clock found on every Alpha
 752           system, specifically MC146818 compatibles.  If in doubt, say Y.
 753
 754 config RTC_DRV_VRTC
 755         tristate "Virtual RTC for Intel MID platforms"
 756         depends on X86_INTEL_MID
 757         default y if X86_INTEL_MID
 758
 759         help
 760         Say "yes" here to get direct support for the real time clock
 761         found on Moorestown platforms. The VRTC is a emulated RTC that
 762         derives its clock source from a real RTC in the PMIC. The MC146818
 763         style programming interface is mostly conserved, but any
 764         updates are done via IPC calls to the system controller FW.
 765
 766 config RTC_DRV_DS1216
 767         tristate "Dallas DS1216"
 768         depends on SNI_RM
 769         help
 770           If you say yes here you get support for the Dallas DS1216 RTC chips.
 771
 772 config RTC_DRV_DS1286
 773         tristate "Dallas DS1286"
 774         depends on HAS_IOMEM
 775         help
 776           If you say yes here you get support for the Dallas DS1286 RTC chips.
 777
 778 config RTC_DRV_DS1302
 779         tristate "Dallas DS1302"
 780         depends on SH_SECUREEDGE5410
 781         help
 782           If you say yes here you get support for the Dallas DS1302 RTC chips.
 783
 784 config RTC_DRV_DS1511
 785         tristate "Dallas DS1511"
 786         depends on HAS_IOMEM
 787         help
 788           If you say yes here you get support for the
 789           Dallas DS1511 timekeeping/watchdog chip.
 790
 791           This driver can also be built as a module. If so, the module
 792           will be called rtc-ds1511.
 793
 794 config RTC_DRV_DS1553
 795         tristate "Maxim/Dallas DS1553"
 796         depends on HAS_IOMEM
 797         help
 798           If you say yes here you get support for the
 799           Maxim/Dallas DS1553 timekeeping chip.
 800
 801           This driver can also be built as a module. If so, the module
 802           will be called rtc-ds1553.
 803
 804 config RTC_DRV_DS1685_FAMILY
 805         tristate "Dallas/Maxim DS1685 Family"
 806         help
 807           If you say yes here you get support for the Dallas/Maxim DS1685
 808           family of real time chips.  This family includes the DS1685/DS1687,
 809           DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
 810           DS17885/DS17887 chips.
 811
 812           This driver can also be built as a module. If so, the module
 813           will be called rtc-ds1685.
 814
 815 choice
 816         prompt "Subtype"
 817         depends on RTC_DRV_DS1685_FAMILY
 818         default RTC_DRV_DS1685
 819
 820 config RTC_DRV_DS1685
 821         bool "DS1685/DS1687"
 822         help
 823           This enables support for the Dallas/Maxim DS1685/DS1687 real time
 824           clock chip.
 825
 826           This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
 827           systems, as well as EPPC-405-UC modules by electronic system design
 828           GmbH.
 829
 830 config RTC_DRV_DS1689
 831         bool "DS1689/DS1693"
 832         help
 833           This enables support for the Dallas/Maxim DS1689/DS1693 real time
 834           clock chip.
 835
 836           This is an older RTC chip, supplanted by the DS1685/DS1687 above,
 837           which supports a few minor features such as Vcc, Vbat, and Power
 838           Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
 839
 840           It also works for the even older DS1688/DS1691 RTC chips, which are
 841           virtually the same and carry the same model number.  Both chips
 842           have 114 bytes of user NVRAM.
 843
 844 config RTC_DRV_DS17285
 845         bool "DS17285/DS17287"
 846         help
 847           This enables support for the Dallas/Maxim DS17285/DS17287 real time
 848           clock chip.
 849
 850           This chip features 2kb of extended NV-SRAM.  It may possibly be
 851           found in some SGI O2 systems (rare).
 852
 853 config RTC_DRV_DS17485
 854         bool "DS17485/DS17487"
 855         help
 856           This enables support for the Dallas/Maxim DS17485/DS17487 real time
 857           clock chip.
 858
 859           This chip features 4kb of extended NV-SRAM.
 860
 861 config RTC_DRV_DS17885
 862         bool "DS17885/DS17887"
 863         help
 864           This enables support for the Dallas/Maxim DS17885/DS17887 real time
 865           clock chip.
 866
 867           This chip features 8kb of extended NV-SRAM.
 868
 869 endchoice
 870
 871 config RTC_DS1685_PROC_REGS
 872         bool "Display register values in /proc"
 873         depends on RTC_DRV_DS1685_FAMILY && PROC_FS
 874         help
 875           Enable this to display a readout of all of the RTC registers in
 876           /proc/drivers/rtc.  Keep in mind that this can potentially lead
 877           to lost interrupts, as reading Control Register C will clear
 878           all pending IRQ flags.
 879
 880           Unless you are debugging this driver, choose N.
 881
 882 config RTC_DS1685_SYSFS_REGS
 883         bool "SysFS access to RTC register bits"
 884         depends on RTC_DRV_DS1685_FAMILY && SYSFS
 885         help
 886           Enable this to provide access to the RTC control register bits
 887           in /sys.  Some of the bits are read-write, others are read-only.
 888
 889           Keep in mind that reading Control C's bits automatically clears
 890           all pending IRQ flags - this can cause lost interrupts.
 891
 892           If you know that you need access to these bits, choose Y, Else N.
 893
 894 config RTC_DRV_DS1742
 895         tristate "Maxim/Dallas DS1742/1743"
 896         depends on HAS_IOMEM
 897         help
 898           If you say yes here you get support for the
 899           Maxim/Dallas DS1742/1743 timekeeping chip.
 900
 901           This driver can also be built as a module. If so, the module
 902           will be called rtc-ds1742.
 903
 904 config RTC_DRV_DS2404
 905         tristate "Maxim/Dallas DS2404"
 906         help
 907           If you say yes here you get support for the
 908           Dallas DS2404 RTC chip.
 909
 910           This driver can also be built as a module. If so, the module
 911           will be called rtc-ds2404.
 912
 913 config RTC_DRV_DA9052
 914         tristate "Dialog DA9052/DA9053 RTC"
 915         depends on PMIC_DA9052
 916         help
 917           Say y here to support the RTC driver for Dialog Semiconductor
 918           DA9052-BC and DA9053-AA/Bx PMICs.
 919
 920 config RTC_DRV_DA9055
 921         tristate "Dialog Semiconductor DA9055 RTC"
 922         depends on MFD_DA9055
 923         help
 924           If you say yes here you will get support for the
 925           RTC of the Dialog DA9055 PMIC.
 926
 927           This driver can also be built as a module. If so, the module
 928           will be called rtc-da9055
 929
 930 config RTC_DRV_DA9063
 931         tristate "Dialog Semiconductor DA9063 RTC"
 932         depends on MFD_DA9063
 933         help
 934           If you say yes here you will get support for the RTC subsystem
 935           of the Dialog Semiconductor DA9063.
 936
 937           This driver can also be built as a module. If so, the module
 938           will be called "rtc-da9063".
 939
 940 config RTC_DRV_EFI
 941         tristate "EFI RTC"
 942         depends on EFI && !X86
 943         help
 944           If you say yes here you will get support for the EFI
 945           Real Time Clock.
 946
 947           This driver can also be built as a module. If so, the module
 948           will be called rtc-efi.
 949
 950 config RTC_DRV_STK17TA8
 951         tristate "Simtek STK17TA8"
 952         depends on HAS_IOMEM
 953         help
 954           If you say yes here you get support for the
 955           Simtek STK17TA8 timekeeping chip.
 956
 957           This driver can also be built as a module. If so, the module
 958           will be called rtc-stk17ta8.
 959
 960 config RTC_DRV_M48T86
 961         tristate "ST M48T86/Dallas DS12887"
 962         help
 963           If you say Y here you will get support for the
 964           ST M48T86 and Dallas DS12887 RTC chips.
 965
 966           This driver can also be built as a module. If so, the module
 967           will be called rtc-m48t86.
 968
 969 config RTC_DRV_M48T35
 970         tristate "ST M48T35"
 971         depends on HAS_IOMEM
 972         help
 973           If you say Y here you will get support for the
 974           ST M48T35 RTC chip.
 975
 976           This driver can also be built as a module, if so, the module
 977           will be called "rtc-m48t35".
 978
 979 config RTC_DRV_M48T59
 980         tristate "ST M48T59/M48T08/M48T02"
 981         depends on HAS_IOMEM
 982         help
 983           If you say Y here you will get support for the
 984           ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
 985
 986           These chips are usually found in Sun SPARC and UltraSPARC
 987           workstations.
 988
 989           This driver can also be built as a module, if so, the module
 990           will be called "rtc-m48t59".
 991
 992 config RTC_DRV_MSM6242
 993         tristate "Oki MSM6242"
 994         depends on HAS_IOMEM
 995         help
 996           If you say yes here you get support for the Oki MSM6242
 997           timekeeping chip. It is used in some Amiga models (e.g. A2000).
 998
 999           This driver can also be built as a module. If so, the module
1000           will be called rtc-msm6242.
1001
1002 config RTC_DRV_BQ4802
1003         tristate "TI BQ4802"
1004         depends on HAS_IOMEM
1005         help
1006           If you say Y here you will get support for the TI
1007           BQ4802 RTC chip.
1008
1009           This driver can also be built as a module. If so, the module
1010           will be called rtc-bq4802.
1011
1012 config RTC_DRV_RP5C01
1013         tristate "Ricoh RP5C01"
1014         depends on HAS_IOMEM
1015         help
1016           If you say yes here you get support for the Ricoh RP5C01
1017           timekeeping chip. It is used in some Amiga models (e.g. A3000
1018           and A4000).
1019
1020           This driver can also be built as a module. If so, the module
1021           will be called rtc-rp5c01.
1022
1023 config RTC_DRV_V3020
1024         tristate "EM Microelectronic V3020"
1025         help
1026           If you say yes here you will get support for the
1027           EM Microelectronic v3020 RTC chip.
1028
1029           This driver can also be built as a module. If so, the module
1030           will be called rtc-v3020.
1031
1032 config RTC_DRV_WM831X
1033         tristate "Wolfson Microelectronics WM831x RTC"
1034         depends on MFD_WM831X
1035         help
1036           If you say yes here you will get support for the RTC subsystem
1037           of the Wolfson Microelectronics WM831X series PMICs.
1038
1039           This driver can also be built as a module. If so, the module
1040           will be called "rtc-wm831x".
1041
1042 config RTC_DRV_WM8350
1043         tristate "Wolfson Microelectronics WM8350 RTC"
1044         depends on MFD_WM8350
1045         help
1046           If you say yes here you will get support for the RTC subsystem
1047           of the Wolfson Microelectronics WM8350.
1048
1049           This driver can also be built as a module. If so, the module
1050           will be called "rtc-wm8350".
1051
1052 config RTC_DRV_SPEAR
1053         tristate "SPEAR ST RTC"
1054         depends on PLAT_SPEAR
1055         default y
1056         help
1057          If you say Y here you will get support for the RTC found on
1058          spear
1059
1060 config RTC_DRV_PCF50633
1061         depends on MFD_PCF50633
1062         tristate "NXP PCF50633 RTC"
1063         help
1064           If you say yes here you get support for the RTC subsystem of the
1065           NXP PCF50633 used in embedded systems.
1066
1067 config RTC_DRV_AB3100
1068         tristate "ST-Ericsson AB3100 RTC"
1069         depends on AB3100_CORE
1070         default y if AB3100_CORE
1071         help
1072           Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1073           support. This chip contains a battery- and capacitor-backed RTC.
1074
1075 config RTC_DRV_AB8500
1076         tristate "ST-Ericsson AB8500 RTC"
1077         depends on AB8500_CORE
1078         select RTC_INTF_DEV
1079         select RTC_INTF_DEV_UIE_EMUL
1080         help
1081           Select this to enable the ST-Ericsson AB8500 power management IC RTC
1082           support. This chip contains a battery- and capacitor-backed RTC.
1083
1084 config RTC_DRV_NUC900
1085         tristate "NUC910/NUC920 RTC driver"
1086         depends on ARCH_W90X900
1087         help
1088           If you say yes here you get support for the RTC subsystem of the
1089           NUC910/NUC920 used in embedded systems.
1090
1091 config RTC_DRV_OPAL
1092         tristate "IBM OPAL RTC driver"
1093         depends on PPC_POWERNV
1094         default y
1095         help
1096           If you say yes here you get support for the PowerNV platform RTC
1097           driver based on OPAL interfaces.
1098
1099           This driver can also be built as a module. If so, the module
1100           will be called rtc-opal.
1101
1102 comment "on-CPU RTC drivers"
1103
1104 config RTC_DRV_DAVINCI
1105         tristate "TI DaVinci RTC"
1106         depends on ARCH_DAVINCI_DM365
1107         help
1108           If you say yes here you get support for the RTC on the
1109           DaVinci platforms (DM365).
1110
1111           This driver can also be built as a module. If so, the module
1112           will be called rtc-davinci.
1113
1114 config RTC_DRV_DIGICOLOR
1115         tristate "Conexant Digicolor RTC"
1116         depends on ARCH_DIGICOLOR
1117         help
1118           If you say yes here you get support for the RTC on Conexant
1119           Digicolor platforms. This currently includes the CX92755 SoC.
1120
1121           This driver can also be built as a module. If so, the module
1122           will be called rtc-digicolor.
1123
1124 config RTC_DRV_IMXDI
1125         tristate "Freescale IMX DryIce Real Time Clock"
1126         depends on ARCH_MXC
1127         help
1128            Support for Freescale IMX DryIce RTC
1129
1130            This driver can also be built as a module, if so, the module
1131            will be called "rtc-imxdi".
1132
1133 config RTC_DRV_OMAP
1134         tristate "TI OMAP Real Time Clock"
1135         depends on ARCH_OMAP || ARCH_DAVINCI
1136         help
1137           Say "yes" here to support the on chip real time clock
1138           present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1139
1140           This driver can also be built as a module, if so, module
1141           will be called rtc-omap.
1142
1143 config HAVE_S3C_RTC
1144         bool
1145         help
1146           This will include RTC support for Samsung SoCs. If
1147           you want to include RTC support for any machine, kindly
1148           select this in the respective mach-XXXX/Kconfig file.
1149
1150 config RTC_DRV_S3C
1151         tristate "Samsung S3C series SoC RTC"
1152         depends on ARCH_S3C64XX || HAVE_S3C_RTC
1153         help
1154           RTC (Realtime Clock) driver for the clock inbuilt into the
1155           Samsung S3C24XX series of SoCs. This can provide periodic
1156           interrupt rates from 1Hz to 64Hz for user programs, and
1157           wakeup from Alarm.
1158
1159           The driver currently supports the common features on all the
1160           S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1161           and S3C2442.
1162
1163           This driver can also be build as a module. If so, the module
1164           will be called rtc-s3c.
1165
1166 config RTC_DRV_EP93XX
1167         tristate "Cirrus Logic EP93XX"
1168         depends on ARCH_EP93XX
1169         help
1170           If you say yes here you get support for the
1171           RTC embedded in the Cirrus Logic EP93XX processors.
1172
1173           This driver can also be built as a module. If so, the module
1174           will be called rtc-ep93xx.
1175
1176 config RTC_DRV_SA1100
1177         tristate "SA11x0/PXA2xx/PXA910"
1178         depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1179         help
1180           If you say Y here you will get access to the real time clock
1181           built into your SA11x0 or PXA2xx CPU.
1182
1183           To compile this driver as a module, choose M here: the
1184           module will be called rtc-sa1100.
1185
1186 config RTC_DRV_SH
1187         tristate "SuperH On-Chip RTC"
1188         depends on SUPERH && HAVE_CLK
1189         help
1190           Say Y here to enable support for the on-chip RTC found in
1191           most SuperH processors.
1192
1193           To compile this driver as a module, choose M here: the
1194           module will be called rtc-sh.
1195
1196 config RTC_DRV_VR41XX
1197         tristate "NEC VR41XX"
1198         depends on CPU_VR41XX
1199         help
1200           If you say Y here you will get access to the real time clock
1201           built into your NEC VR41XX CPU.
1202
1203           To compile this driver as a module, choose M here: the
1204           module will be called rtc-vr41xx.
1205
1206 config RTC_DRV_PL030
1207         tristate "ARM AMBA PL030 RTC"
1208         depends on ARM_AMBA
1209         help
1210           If you say Y here you will get access to ARM AMBA
1211           PrimeCell PL030 RTC found on certain ARM SOCs.
1212
1213           To compile this driver as a module, choose M here: the
1214           module will be called rtc-pl030.
1215
1216 config RTC_DRV_PL031
1217         tristate "ARM AMBA PL031 RTC"
1218         depends on ARM_AMBA
1219         help
1220           If you say Y here you will get access to ARM AMBA
1221           PrimeCell PL031 RTC found on certain ARM SOCs.
1222
1223           To compile this driver as a module, choose M here: the
1224           module will be called rtc-pl031.
1225
1226 config RTC_DRV_AT32AP700X
1227         tristate "AT32AP700X series RTC"
1228         depends on PLATFORM_AT32AP
1229         help
1230           Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1231           AT32AP700x family processors.
1232
1233 config RTC_DRV_AT91RM9200
1234         tristate "AT91RM9200 or some AT91SAM9 RTC"
1235         depends on ARCH_AT91
1236         help
1237           Driver for the internal RTC (Realtime Clock) module found on
1238           Atmel AT91RM9200's and some  AT91SAM9 chips. On AT91SAM9 chips
1239           this is powered by the backup power supply.
1240
1241 config RTC_DRV_AT91SAM9
1242         tristate "AT91SAM9 RTT as RTC"
1243         depends on ARCH_AT91
1244         select MFD_SYSCON
1245         help
1246           Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1247           can be used as an RTC thanks to the backup power supply (e.g. a
1248           small coin cell battery) which keeps this block and the GPBR
1249           (General Purpose Backup Registers) block powered when the device
1250           is shutdown.
1251           Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1252           probably want to use the real RTC block instead of the "RTT as an
1253           RTC" driver.
1254
1255 config RTC_DRV_AU1XXX
1256         tristate "Au1xxx Counter0 RTC support"
1257         depends on MIPS_ALCHEMY
1258         help
1259           This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1260           counter) to be used as a RTC.
1261
1262           This driver can also be built as a module. If so, the module
1263           will be called rtc-au1xxx.
1264
1265 config RTC_DRV_BFIN
1266         tristate "Blackfin On-Chip RTC"
1267         depends on BLACKFIN && !BF561
1268         help
1269           If you say yes here you will get support for the
1270           Blackfin On-Chip Real Time Clock.
1271
1272           This driver can also be built as a module. If so, the module
1273           will be called rtc-bfin.
1274
1275 config RTC_DRV_RS5C313
1276         tristate "Ricoh RS5C313"
1277         depends on SH_LANDISK
1278         help
1279           If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1280
1281 config RTC_DRV_GENERIC
1282         tristate "Generic RTC support"
1283         # Please consider writing a new RTC driver instead of using the generic
1284         # RTC abstraction
1285         depends on PARISC || M68K || PPC || SUPERH32
1286         help
1287           Say Y or M here to enable RTC support on systems using the generic
1288           RTC abstraction. If you do not know what you are doing, you should
1289           just say Y.
1290
1291 config RTC_DRV_PXA
1292        tristate "PXA27x/PXA3xx"
1293        depends on ARCH_PXA
1294        help
1295          If you say Y here you will get access to the real time clock
1296          built into your PXA27x or PXA3xx CPU.
1297
1298          This RTC driver uses PXA RTC registers available since pxa27x
1299          series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1300
1301 config RTC_DRV_VT8500
1302         tristate "VIA/WonderMedia 85xx SoC RTC"
1303         depends on ARCH_VT8500
1304         help
1305           If you say Y here you will get access to the real time clock
1306           built into your VIA VT8500 SoC or its relatives.
1307
1308
1309 config RTC_DRV_SUN4V
1310         bool "SUN4V Hypervisor RTC"
1311         depends on SPARC64
1312         help
1313           If you say Y here you will get support for the Hypervisor
1314           based RTC on SUN4V systems.
1315
1316 config RTC_DRV_SUN6I
1317         tristate "Allwinner A31 RTC"
1318         depends on MACH_SUN6I || MACH_SUN8I
1319         help
1320           If you say Y here you will get support for the RTC found on
1321           Allwinner A31.
1322
1323 config RTC_DRV_SUNXI
1324         tristate "Allwinner sun4i/sun7i RTC"
1325         depends on MACH_SUN4I || MACH_SUN7I
1326         help
1327           If you say Y here you will get support for the RTC found on
1328           Allwinner A10/A20.
1329
1330 config RTC_DRV_STARFIRE
1331         bool "Starfire RTC"
1332         depends on SPARC64
1333         help
1334           If you say Y here you will get support for the RTC found on
1335           Starfire systems.
1336
1337 config RTC_DRV_TX4939
1338         tristate "TX4939 SoC"
1339         depends on SOC_TX4939
1340         help
1341           Driver for the internal RTC (Realtime Clock) module found on
1342           Toshiba TX4939 SoC.
1343
1344 config RTC_DRV_MV
1345         tristate "Marvell SoC RTC"
1346         depends on ARCH_DOVE || ARCH_MVEBU
1347         help
1348           If you say yes here you will get support for the in-chip RTC
1349           that can be found in some of Marvell's SoC devices, such as
1350           the Kirkwood 88F6281 and 88F6192.
1351
1352           This driver can also be built as a module. If so, the module
1353           will be called rtc-mv.
1354
1355 config RTC_DRV_ARMADA38X
1356         tristate "Armada 38x Marvell SoC RTC"
1357         depends on ARCH_MVEBU
1358         help
1359           If you say yes here you will get support for the in-chip RTC
1360           that can be found in the Armada 38x Marvell's SoC device
1361
1362           This driver can also be built as a module. If so, the module
1363           will be called armada38x-rtc.
1364
1365 config RTC_DRV_PS3
1366         tristate "PS3 RTC"
1367         depends on PPC_PS3
1368         help
1369           If you say yes here you will get support for the RTC on PS3.
1370
1371           This driver can also be built as a module. If so, the module
1372           will be called rtc-ps3.
1373
1374 config RTC_DRV_COH901331
1375         tristate "ST-Ericsson COH 901 331 RTC"
1376         depends on ARCH_U300
1377         help
1378           If you say Y here you will get access to ST-Ericsson
1379           COH 901 331 RTC clock found in some ST-Ericsson Mobile
1380           Platforms.
1381
1382           This driver can also be built as a module. If so, the module
1383           will be called "rtc-coh901331".
1384
1385
1386 config RTC_DRV_STMP
1387         tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1388         depends on ARCH_MXS
1389         help
1390           If you say yes here you will get support for the onboard
1391           STMP3xxx/i.MX23/i.MX28 RTC.
1392
1393           This driver can also be built as a module. If so, the module
1394           will be called rtc-stmp3xxx.
1395
1396 config RTC_DRV_PCAP
1397         tristate "PCAP RTC"
1398         depends on EZX_PCAP
1399         help
1400           If you say Y here you will get support for the RTC found on
1401           the PCAP2 ASIC used on some Motorola phones.
1402
1403 config RTC_DRV_MC13XXX
1404         depends on MFD_MC13XXX
1405         tristate "Freescale MC13xxx RTC"
1406         help
1407           This enables support for the RTCs found on Freescale's PMICs
1408           MC13783 and MC13892.
1409
1410 config RTC_DRV_MPC5121
1411         tristate "Freescale MPC5121 built-in RTC"
1412         depends on PPC_MPC512x || PPC_MPC52xx
1413         help
1414           If you say yes here you will get support for the
1415           built-in RTC on MPC5121 or on MPC5200.
1416
1417           This driver can also be built as a module. If so, the module
1418           will be called rtc-mpc5121.
1419
1420 config RTC_DRV_JZ4740
1421         tristate "Ingenic JZ4740 SoC"
1422         depends on MACH_JZ4740
1423         help
1424           If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1425           controller.
1426
1427           This driver can also be buillt as a module. If so, the module
1428           will be called rtc-jz4740.
1429
1430 config RTC_DRV_LPC32XX
1431         depends on ARCH_LPC32XX
1432         tristate "NXP LPC32XX RTC"
1433         help
1434           This enables support for the NXP RTC in the LPC32XX
1435
1436           This driver can also be buillt as a module. If so, the module
1437           will be called rtc-lpc32xx.
1438
1439 config RTC_DRV_PM8XXX
1440         tristate "Qualcomm PMIC8XXX RTC"
1441         depends on MFD_PM8XXX || MFD_SPMI_PMIC
1442         help
1443           If you say yes here you get support for the
1444           Qualcomm PMIC8XXX RTC.
1445
1446           To compile this driver as a module, choose M here: the
1447           module will be called rtc-pm8xxx.
1448
1449 config RTC_DRV_TEGRA
1450         tristate "NVIDIA Tegra Internal RTC driver"
1451         depends on ARCH_TEGRA
1452         help
1453           If you say yes here you get support for the
1454           Tegra 200 series internal RTC module.
1455
1456           This drive can also be built as a module. If so, the module
1457           will be called rtc-tegra.
1458
1459 config RTC_DRV_TILE
1460         tristate "Tilera hypervisor RTC support"
1461         depends on TILE
1462         help
1463           Enable support for the Linux driver side of the Tilera
1464           hypervisor's real-time clock interface.
1465
1466 config RTC_DRV_PUV3
1467         tristate "PKUnity v3 RTC support"
1468         depends on ARCH_PUV3
1469         help
1470           This enables support for the RTC in the PKUnity-v3 SoCs.
1471
1472           This drive can also be built as a module. If so, the module
1473           will be called rtc-puv3.
1474
1475 config RTC_DRV_LOONGSON1
1476         tristate "loongson1 RTC support"
1477         depends on MACH_LOONGSON1
1478         help
1479           This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1480           counter) to be used as a RTC.
1481
1482           This driver can also be built as a module. If so, the module
1483           will be called rtc-ls1x.
1484
1485 config RTC_DRV_MXC
1486         tristate "Freescale MXC Real Time Clock"
1487         depends on ARCH_MXC
1488         help
1489            If you say yes here you get support for the Freescale MXC
1490            RTC module.
1491
1492            This driver can also be built as a module, if so, the module
1493            will be called "rtc-mxc".
1494
1495 config RTC_DRV_SNVS
1496         tristate "Freescale SNVS RTC support"
1497         depends on HAS_IOMEM
1498         depends on OF
1499         help
1500            If you say yes here you get support for the Freescale SNVS
1501            Low Power (LP) RTC module.
1502
1503            This driver can also be built as a module, if so, the module
1504            will be called "rtc-snvs".
1505
1506 config RTC_DRV_SIRFSOC
1507         tristate "SiRFSOC RTC"
1508         depends on ARCH_SIRF
1509         help
1510           Say "yes" here to support the real time clock on SiRF SOC chips.
1511           This driver can also be built as a module called rtc-sirfsoc.
1512
1513 config RTC_DRV_MOXART
1514         tristate "MOXA ART RTC"
1515         depends on ARCH_MOXART || COMPILE_TEST
1516         help
1517            If you say yes here you get support for the MOXA ART
1518            RTC module.
1519
1520            This driver can also be built as a module. If so, the module
1521            will be called rtc-moxart
1522
1523 config RTC_DRV_XGENE
1524         tristate "APM X-Gene RTC"
1525         depends on HAS_IOMEM
1526         help
1527           If you say yes here you get support for the APM X-Gene SoC real time
1528           clock.
1529
1530           This driver can also be built as a module, if so, the module
1531           will be called "rtc-xgene".
1532
1533 comment "HID Sensor RTC drivers"
1534
1535 config RTC_DRV_HID_SENSOR_TIME
1536         tristate "HID Sensor Time"
1537         depends on USB_HID
1538         select IIO
1539         select HID_SENSOR_HUB
1540         select HID_SENSOR_IIO_COMMON
1541         help
1542           Say yes here to build support for the HID Sensors of type Time.
1543           This drivers makes such sensors available as RTCs.
1544
1545           If this driver is compiled as a module, it will be named
1546           rtc-hid-sensor-time.
1547
1548
1549 endif # RTC_CLASS