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