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