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