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