2074 lines · plain
1# SPDX-License-Identifier: GPL-2.0-only2#3# RTC class/drivers configuration4#5 6config RTC_LIB7 bool8 9config RTC_MC146818_LIB10 bool11 select RTC_LIB12 13menuconfig RTC_CLASS14 bool "Real Time Clock"15 default n16 depends on !S39017 select RTC_LIB18 help19 Generic RTC class support. If you say yes here, you will20 be allowed to plug one or more RTCs to your system. You will21 probably want to enable one or more of the interfaces below.22 23if RTC_CLASS24 25config RTC_HCTOSYS26 bool "Set system time from RTC on startup and resume"27 default y28 help29 If you say yes here, the system time (wall clock) will be set using30 the value read from a specified RTC device. This is useful to avoid31 unnecessary fsck runs at boot time, and to network better.32 33config RTC_HCTOSYS_DEVICE34 string "RTC used to set the system time"35 depends on RTC_HCTOSYS36 default "rtc0"37 help38 The RTC device that will be used to (re)initialize the system39 clock, usually rtc0. Initialization is done when the system40 starts up, and when it resumes from a low power state. This41 device should record time in UTC, since the kernel won't do42 timezone correction.43 44 This clock should be battery-backed, so that it reads the correct45 time when the system boots from a power-off state. Otherwise, your46 system will need an external clock source (like an NTP server).47 48 If the clock you specify here is not battery backed, it may still49 be useful to reinitialize system time when resuming from system50 sleep states. Do not specify an RTC here unless it stays powered51 during all this system's supported sleep states.52 53config RTC_SYSTOHC54 bool "Set the RTC time based on NTP synchronization"55 default y56 help57 If you say yes here, the system time (wall clock) will be stored58 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 1159 minutes if userspace reports synchronized NTP status.60 61config RTC_SYSTOHC_DEVICE62 string "RTC used to synchronize NTP adjustment"63 depends on RTC_SYSTOHC64 default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS65 default "rtc0"66 help67 The RTC device used for NTP synchronization. The main difference68 between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this69 one can sleep when setting time, because it runs in the workqueue70 context.71 72config RTC_DEBUG73 bool "RTC debug support"74 help75 Say yes here to enable debugging support in the RTC framework76 and individual RTC drivers.77 78config RTC_LIB_KUNIT_TEST79 tristate "KUnit test for RTC lib functions" if !KUNIT_ALL_TESTS80 depends on KUNIT81 default KUNIT_ALL_TESTS82 help83 Enable this option to test RTC library functions.84 85 If unsure, say N.86 87config RTC_NVMEM88 bool "RTC non volatile storage support"89 select NVMEM90 default RTC_CLASS91 help92 Say yes here to add support for the non volatile (often battery93 backed) storage present on RTCs.94 95comment "RTC interfaces"96 97config RTC_INTF_SYSFS98 bool "/sys/class/rtc/rtcN (sysfs)"99 depends on SYSFS100 default RTC_CLASS101 help102 Say yes here if you want to use your RTCs using sysfs interfaces,103 /sys/class/rtc/rtc0 through /sys/.../rtcN.104 105 If unsure, say Y.106 107config RTC_INTF_PROC108 bool "/proc/driver/rtc (procfs for rtcN)"109 depends on PROC_FS110 default RTC_CLASS111 help112 Say yes here if you want to use your system clock RTC through113 the proc interface, /proc/driver/rtc.114 Other RTCs will not be available through that API.115 If there is no RTC for the system clock, then the first RTC(rtc0)116 is used by default.117 118 If unsure, say Y.119 120config RTC_INTF_DEV121 bool "/dev/rtcN (character devices)"122 default RTC_CLASS123 help124 Say yes here if you want to use your RTCs using the /dev125 interfaces, which "udev" sets up as /dev/rtc0 through126 /dev/rtcN.127 128 You may want to set up a symbolic link so one of these129 can be accessed as /dev/rtc, which is a name130 expected by "hwclock" and some other programs. Recent131 versions of "udev" are known to set up the symlink for you.132 133 If unsure, say Y.134 135config RTC_INTF_DEV_UIE_EMUL136 bool "RTC UIE emulation on dev interface"137 depends on RTC_INTF_DEV138 help139 Provides an emulation for RTC_UIE if the underlying rtc chip140 driver does not expose RTC_UIE ioctls. Those requests generate141 once-per-second update interrupts, used for synchronization.142 143 The emulation code will read the time from the hardware144 clock several times per second, please enable this option145 only if you know that you really need it.146 147config RTC_DRV_TEST148 tristate "Test driver/device"149 help150 If you say yes here you get support for the151 RTC test driver. It's a software RTC which can be152 used to test the RTC subsystem APIs. It gets153 the time from the system clock.154 You want this driver only if you are doing development155 on the RTC subsystem. Please read the source code156 for further details.157 158 This driver can also be built as a module. If so, the module159 will be called rtc-test.160 161comment "I2C RTC drivers"162 163if I2C164 165config RTC_DRV_88PM860X166 tristate "Marvell 88PM860x"167 depends on MFD_88PM860X168 help169 If you say yes here you get support for RTC function in Marvell170 88PM860x chips.171 172 This driver can also be built as a module. If so, the module173 will be called rtc-88pm860x.174 175config RTC_DRV_88PM80X176 tristate "Marvell 88PM80x"177 depends on MFD_88PM800178 help179 If you say yes here you get support for RTC function in Marvell180 88PM80x chips.181 182 This driver can also be built as a module. If so, the module183 will be called rtc-88pm80x.184 185config RTC_DRV_ABB5ZES3186 select REGMAP_I2C187 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"188 help189 If you say yes here you get support for the Abracon190 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.191 192 This driver can also be built as a module. If so, the module193 will be called rtc-ab-b5ze-s3.194 195config RTC_DRV_ABEOZ9196 select REGMAP_I2C197 tristate "Abracon AB-RTCMC-32.768kHz-EOZ9"198 help199 If you say yes here you get support for the Abracon200 AB-RTCMC-32.768kHz-EOA9 I2C RTC chip.201 202 This driver can also be built as a module. If so, the module203 will be called rtc-ab-e0z9.204 205config RTC_DRV_ABX80X206 tristate "Abracon ABx80x"207 select WATCHDOG_CORE if WATCHDOG208 help209 If you say yes here you get support for Abracon AB080X and AB180X210 families of ultra-low-power battery- and capacitor-backed real-time211 clock chips.212 213 This driver can also be built as a module. If so, the module214 will be called rtc-abx80x.215 216config RTC_DRV_AC100217 tristate "X-Powers AC100"218 depends on MFD_AC100219 help220 If you say yes here you get support for the real-time clock found221 in X-Powers AC100 family peripheral ICs.222 223 This driver can also be built as a module. If so, the module224 will be called rtc-ac100.225 226config RTC_DRV_BRCMSTB227 tristate "Broadcom STB wake-timer"228 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST229 default ARCH_BRCMSTB || BMIPS_GENERIC230 help231 If you say yes here you get support for the wake-timer found on232 Broadcom STB SoCs (BCM7xxx).233 234 This driver can also be built as a module. If so, the module will235 be called rtc-brcmstb-waketimer.236 237config RTC_DRV_AS3722238 tristate "ams AS3722 RTC driver"239 depends on MFD_AS3722240 help241 If you say yes here you get support for the RTC of ams AS3722 PMIC242 chips.243 244 This driver can also be built as a module. If so, the module245 will be called rtc-as3722.246 247config RTC_DRV_DS1307248 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"249 select REGMAP_I2C250 select WATCHDOG_CORE if WATCHDOG251 help252 If you say yes here you get support for various compatible RTC253 chips (often with battery backup) connected with I2C. This driver254 should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341,255 ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.256 In some cases the RTC must already have been initialized (by257 manufacturing or a bootloader).258 259 The first seven registers on these chips hold an RTC, and other260 registers may add features such as NVRAM, a trickle charger for261 the RTC/NVRAM backup power, and alarms. NVRAM is visible in262 sysfs, but other chip features may not be available.263 264 This driver can also be built as a module. If so, the module265 will be called rtc-ds1307.266 267config RTC_DRV_DS1307_CENTURY268 bool "Century bit support for rtc-ds1307"269 depends on RTC_DRV_DS1307270 default n271 help272 The DS1307 driver suffered from a bug where it was enabling the273 century bit inconditionnally but never used it when reading the time.274 It made the driver unable to support dates beyond 2099.275 Setting this option will add proper support for the century bit but if276 the time was previously set using a kernel predating this option,277 reading the date will return a date in the next century.278 To solve that, you could boot a kernel without this option set, set279 the RTC date and then boot a kernel with this option set.280 281config RTC_DRV_DS1374282 tristate "Dallas/Maxim DS1374"283 help284 If you say yes here you get support for Dallas Semiconductor285 DS1374 real-time clock chips. If an interrupt is associated286 with the device, the alarm functionality is supported.287 288 This driver can also be built as a module. If so, the module289 will be called rtc-ds1374.290 291config RTC_DRV_DS1374_WDT292 bool "Dallas/Maxim DS1374 watchdog timer"293 depends on RTC_DRV_DS1374 && WATCHDOG294 select WATCHDOG_CORE295 help296 If you say Y here you will get support for the297 watchdog timer in the Dallas Semiconductor DS1374298 real-time clock chips.299 300config RTC_DRV_DS1672301 tristate "Dallas/Maxim DS1672"302 help303 If you say yes here you get support for the304 Dallas/Maxim DS1672 timekeeping chip.305 306 This driver can also be built as a module. If so, the module307 will be called rtc-ds1672.308 309config RTC_DRV_HYM8563310 tristate "Haoyu Microelectronics HYM8563"311 depends on OF312 help313 Say Y to enable support for the HYM8563 I2C RTC chip. Apart314 from the usual rtc functions it provides a clock output of315 up to 32kHz.316 317 This driver can also be built as a module. If so, the module318 will be called rtc-hym8563.319 320config RTC_DRV_LP8788321 tristate "TI LP8788 RTC driver"322 depends on MFD_LP8788323 help324 Say Y to enable support for the LP8788 RTC/ALARM driver.325 326config RTC_DRV_MAX6900327 tristate "Maxim MAX6900"328 help329 If you say yes here you will get support for the330 Maxim MAX6900 I2C RTC chip.331 332 This driver can also be built as a module. If so, the module333 will be called rtc-max6900.334 335config RTC_DRV_MAX8907336 tristate "Maxim MAX8907"337 depends on MFD_MAX8907 || COMPILE_TEST338 select REGMAP_IRQ339 help340 If you say yes here you will get support for the341 RTC of Maxim MAX8907 PMIC.342 343 This driver can also be built as a module. If so, the module344 will be called rtc-max8907.345 346config RTC_DRV_MAX8925347 tristate "Maxim MAX8925"348 depends on MFD_MAX8925349 help350 If you say yes here you will get support for the351 RTC of Maxim MAX8925 PMIC.352 353 This driver can also be built as a module. If so, the module354 will be called rtc-max8925.355 356config RTC_DRV_MAX8998357 tristate "Maxim MAX8998"358 depends on MFD_MAX8998359 help360 If you say yes here you will get support for the361 RTC of Maxim MAX8998 PMIC.362 363 This driver can also be built as a module. If so, the module364 will be called rtc-max8998.365 366config RTC_DRV_MAX8997367 tristate "Maxim MAX8997"368 depends on MFD_MAX8997369 help370 If you say yes here you will get support for the371 RTC of Maxim MAX8997 PMIC.372 373 This driver can also be built as a module. If so, the module374 will be called rtc-max8997.375 376config RTC_DRV_MAX31335377 tristate "Analog Devices MAX31335"378 depends on I2C379 depends on COMMON_CLK380 depends on HWMON || HWMON=n381 select REGMAP_I2C382 help383 If you say yes here you get support for the Analog Devices384 MAX31335.385 386 This driver can also be built as a module. If so, the module387 will be called rtc-max31335.388 389config RTC_DRV_MAX77686390 tristate "Maxim MAX77686"391 depends on MFD_MAX77686 || MFD_MAX77620 || MFD_MAX77714 || COMPILE_TEST392 help393 If you say yes here you will get support for the394 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.395 396 This driver can also be built as a module. If so, the module397 will be called rtc-max77686.398 399config RTC_DRV_NCT3018Y400 tristate "Nuvoton NCT3018Y"401 depends on OF402 help403 If you say yes here you get support for the Nuvoton NCT3018Y I2C RTC404 chip.405 406 This driver can also be built as a module, if so, the module will be407 called "rtc-nct3018y".408 409config RTC_DRV_RK808410 tristate "Rockchip RK805/RK808/RK809/RK817/RK818 RTC"411 depends on MFD_RK8XX412 help413 If you say yes here you will get support for the414 RTC of RK805, RK809 and RK817, RK808 and RK818 PMIC.415 416 This driver can also be built as a module. If so, the module417 will be called rk808-rtc.418 419config RTC_DRV_RS5C372420 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"421 help422 If you say yes here you get support for the423 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.424 425 This driver can also be built as a module. If so, the module426 will be called rtc-rs5c372.427 428config RTC_DRV_ISL1208429 tristate "Intersil ISL1208"430 help431 If you say yes here you get support for the432 Intersil ISL1208 RTC chip.433 434 This driver can also be built as a module. If so, the module435 will be called rtc-isl1208.436 437config RTC_DRV_ISL12022438 tristate "Intersil ISL12022"439 select REGMAP_I2C440 help441 If you say yes here you get support for the442 Intersil ISL12022 RTC chip.443 444 This driver can also be built as a module. If so, the module445 will be called rtc-isl12022.446 447config RTC_DRV_ISL12026448 tristate "Intersil ISL12026"449 depends on OF450 help451 If you say yes here you get support for the452 Intersil ISL12026 RTC chip.453 454 This driver can also be built as a module. If so, the module455 will be called rtc-isl12026.456 457config RTC_DRV_X1205458 tristate "Xicor/Intersil X1205"459 help460 If you say yes here you get support for the461 Xicor/Intersil X1205 RTC chip.462 463 This driver can also be built as a module. If so, the module464 will be called rtc-x1205.465 466config RTC_DRV_PCF8523467 tristate "NXP PCF8523"468 select REGMAP_I2C469 help470 If you say yes here you get support for the NXP PCF8523 RTC471 chips.472 473 This driver can also be built as a module. If so, the module474 will be called rtc-pcf8523.475 476config RTC_DRV_PCF85063477 tristate "NXP PCF85063"478 select REGMAP_I2C479 help480 If you say yes here you get support for the PCF85063 RTC chip481 482 This driver can also be built as a module. If so, the module483 will be called rtc-pcf85063.484 485config RTC_DRV_PCF85363486 tristate "NXP PCF85363"487 select REGMAP_I2C488 help489 If you say yes here you get support for the PCF85363 RTC chip.490 491 This driver can also be built as a module. If so, the module492 will be called rtc-pcf85363.493 494 The nvmem interface will be named pcf85363-#, where # is the495 zero-based instance number.496 497config RTC_DRV_PCF8563498 tristate "Philips PCF8563/Epson RTC8564"499 help500 If you say yes here you get support for the501 Philips PCF8563 RTC chip. The Epson RTC8564502 should work as well.503 504 This driver can also be built as a module. If so, the module505 will be called rtc-pcf8563.506 507config RTC_DRV_PCF8583508 tristate "Philips PCF8583"509 help510 If you say yes here you get support for the Philips PCF8583511 RTC chip found on Acorn RiscPCs. This driver supports the512 platform specific method of retrieving the current year from513 the RTC's SRAM. It will work on other platforms with the same514 chip, but the year will probably have to be tweaked.515 516 This driver can also be built as a module. If so, the module517 will be called rtc-pcf8583.518 519config RTC_DRV_M41T80520 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"521 help522 If you say Y here you will get support for the ST M41T60523 and M41T80 RTC chips series. Currently, the following chips are524 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,525 M41ST85, M41ST87, and MicroCrystal RV4162.526 527 This driver can also be built as a module. If so, the module528 will be called rtc-m41t80.529 530config RTC_DRV_M41T80_WDT531 bool "ST M41T65/M41T80 series RTC watchdog timer"532 depends on RTC_DRV_M41T80533 help534 If you say Y here you will get support for the535 watchdog timer in the ST M41T60 and M41T80 RTC chips series.536 537config RTC_DRV_BD70528538 tristate "ROHM BD71815 and BD71828 PMIC RTC"539 depends on MFD_ROHM_BD71828540 help541 If you say Y here you will get support for the RTC542 block on ROHM BD71815 and BD71828 Power Management IC.543 544 This driver can also be built as a module. If so, the module545 will be called rtc-bd70528.546 547config RTC_DRV_BQ32K548 tristate "TI BQ32000"549 help550 If you say Y here you will get support for the TI551 BQ32000 I2C RTC chip.552 553 This driver can also be built as a module. If so, the module554 will be called rtc-bq32k.555 556config RTC_DRV_TWL92330557 bool "TI TWL92330/Menelaus"558 depends on MENELAUS559 help560 If you say yes here you get support for the RTC on the561 TWL92330 "Menelaus" power management chip, used with OMAP2562 platforms. The support is integrated with the rest of563 the Menelaus driver; it's not separate module.564 565config RTC_DRV_TWL4030566 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"567 depends on TWL4030_CORE568 depends on OF569 help570 If you say yes here you get support for the RTC on the571 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.572 573 This driver can also be built as a module. If so, the module574 will be called rtc-twl.575 576config RTC_DRV_PALMAS577 tristate "TI Palmas RTC driver"578 depends on MFD_PALMAS579 help580 If you say yes here you get support for the RTC of TI PALMA series PMIC581 chips.582 583 This driver can also be built as a module. If so, the module584 will be called rtc-palma.585 586config RTC_DRV_TPS6586X587 tristate "TI TPS6586X RTC driver"588 depends on MFD_TPS6586X589 help590 TI Power Management IC TPS6586X supports RTC functionality591 along with alarm. This driver supports the RTC driver for592 the TPS6586X RTC module.593 594config RTC_DRV_TPS6594595 tristate "TI TPS6594 RTC driver"596 depends on MFD_TPS6594597 default MFD_TPS6594598 help599 TI Power Management IC TPS6594 supports RTC functionality600 along with alarm. This driver supports the RTC driver for601 the TPS6594 RTC module.602 603 This driver can also be built as a module. If so, the module604 will be called rtc-tps6594.605 606config RTC_DRV_TPS65910607 tristate "TI TPS65910 RTC driver"608 depends on MFD_TPS65910609 help610 If you say yes here you get support for the RTC on the611 TPS65910 chips.612 613 This driver can also be built as a module. If so, the module614 will be called rtc-tps65910.615 616config RTC_DRV_RC5T583617 tristate "RICOH 5T583 RTC driver"618 depends on MFD_RC5T583619 help620 If you say yes here you get support for the RTC on the621 RICOH 5T583 chips.622 623 This driver can also be built as a module. If so, the module624 will be called rtc-rc5t583.625 626config RTC_DRV_RC5T619627 tristate "RICOH RC5T619 RTC driver"628 depends on MFD_RN5T618629 help630 If you say yes here you get support for the RTC on the631 RICOH RC5T619 chips.632 633 This driver can also be built as a module. If so, the module634 will be called rtc-rc5t619.635 636config RTC_DRV_S35390A637 tristate "Seiko Instruments S-35390A"638 select BITREVERSE639 help640 If you say yes here you will get support for the Seiko641 Instruments S-35390A.642 643 This driver can also be built as a module. If so the module644 will be called rtc-s35390a.645 646config RTC_DRV_FM3130647 tristate "Ramtron FM3130"648 help649 If you say Y here you will get support for the650 Ramtron FM3130 RTC chips.651 Ramtron FM3130 is a chip with two separate devices inside,652 RTC clock and FRAM. This driver provides only RTC functionality.653 654 This driver can also be built as a module. If so the module655 will be called rtc-fm3130.656 657config RTC_DRV_RX8010658 tristate "Epson RX8010SJ"659 select REGMAP_I2C660 help661 If you say yes here you get support for the Epson RX8010SJ RTC662 chip.663 664 This driver can also be built as a module. If so, the module665 will be called rtc-rx8010.666 667config RTC_DRV_RX8111668 tristate "Epson RX8111"669 select REGMAP_I2C670 depends on I2C671 help672 If you say yes here you will get support for the Epson RX8111 RTC.673 674 This driver can also be built as a module. If so, the module will be675 called rtc-rx8111.676 677config RTC_DRV_RX8581678 tristate "Epson RX-8571/RX-8581"679 select REGMAP_I2C680 help681 If you say yes here you will get support for the Epson RX-8571/682 RX-8581.683 684 This driver can also be built as a module. If so the module685 will be called rtc-rx8581.686 687config RTC_DRV_RX8025688 tristate "Epson RX-8025SA/NB"689 help690 If you say yes here you get support for the Epson691 RX-8025SA/NB RTC chips.692 693 This driver can also be built as a module. If so, the module694 will be called rtc-rx8025.695 696config RTC_DRV_EM3027697 tristate "EM Microelectronic EM3027"698 help699 If you say yes here you get support for the EM700 Microelectronic EM3027 RTC chips.701 702 This driver can also be built as a module. If so, the module703 will be called rtc-em3027.704 705config RTC_DRV_RV3028706 tristate "Micro Crystal RV3028"707 select REGMAP_I2C708 help709 If you say yes here you get support for the Micro Crystal710 RV3028.711 712 This driver can also be built as a module. If so, the module713 will be called rtc-rv3028.714 715config RTC_DRV_RV3032716 tristate "Micro Crystal RV3032"717 select REGMAP_I2C718 help719 If you say yes here you get support for the Micro Crystal720 RV3032.721 722 This driver can also be built as a module. If so, the module723 will be called rtc-rv3032.724 725config RTC_DRV_RV8803726 tristate "Micro Crystal RV8803, Epson RX8900"727 help728 If you say yes here you get support for the Micro Crystal RV8803 and729 Epson RX8900 RTC chips.730 731 This driver can also be built as a module. If so, the module732 will be called rtc-rv8803.733 734config RTC_DRV_S5M735 tristate "Samsung S2M/S5M series"736 depends on MFD_SEC_CORE || COMPILE_TEST737 select REGMAP_IRQ738 select REGMAP_I2C739 help740 If you say yes here you will get support for the741 RTC of Samsung S2MPS14 and S5M PMIC series.742 743 This driver can also be built as a module. If so, the module744 will be called rtc-s5m.745 746config RTC_DRV_SD2405AL747 tristate "DFRobot SD2405AL"748 select REGMAP_I2C749 help750 If you say yes here you will get support for the751 DFRobot SD2405AL I2C RTC Module.752 753 This driver can also be built as a module. If so, the module754 will be called rtc-sd2405al.755 756config RTC_DRV_SD3078757 tristate "ZXW Shenzhen whwave SD3078"758 select REGMAP_I2C759 help760 If you say yes here you get support for the ZXW Shenzhen whwave761 SD3078 RTC chips.762 763 This driver can also be built as a module. If so, the module764 will be called rtc-sd3078765 766endif # I2C767 768comment "SPI RTC drivers"769 770if SPI_MASTER771 772config RTC_DRV_M41T93773 tristate "ST M41T93"774 help775 If you say yes here you will get support for the776 ST M41T93 SPI RTC chip.777 778 This driver can also be built as a module. If so, the module779 will be called rtc-m41t93.780 781config RTC_DRV_M41T94782 tristate "ST M41T94"783 help784 If you say yes here you will get support for the785 ST M41T94 SPI RTC chip.786 787 This driver can also be built as a module. If so, the module788 will be called rtc-m41t94.789 790config RTC_DRV_DS1302791 tristate "Dallas/Maxim DS1302"792 depends on SPI793 help794 If you say yes here you get support for the Dallas DS1302 RTC chips.795 796 This driver can also be built as a module. If so, the module797 will be called rtc-ds1302.798 799config RTC_DRV_DS1305800 tristate "Dallas/Maxim DS1305/DS1306"801 help802 Select this driver to get support for the Dallas/Maxim DS1305803 and DS1306 real time clock chips. These support a trickle804 charger, alarms, and NVRAM in addition to the clock.805 806 This driver can also be built as a module. If so, the module807 will be called rtc-ds1305.808 809config RTC_DRV_DS1343810 select REGMAP_SPI811 tristate "Dallas/Maxim DS1343/DS1344"812 help813 If you say yes here you get support for the814 Dallas/Maxim DS1343 and DS1344 real time clock chips.815 Support for trickle charger, alarm is provided.816 817 This driver can also be built as a module. If so, the module818 will be called rtc-ds1343.819 820config RTC_DRV_DS1347821 select REGMAP_SPI822 tristate "Dallas/Maxim DS1347"823 help824 If you say yes here you get support for the825 Dallas/Maxim DS1347 chips.826 827 This driver only supports the RTC feature, and not other chip828 features such as alarms.829 830 This driver can also be built as a module. If so, the module831 will be called rtc-ds1347.832 833config RTC_DRV_DS1390834 tristate "Dallas/Maxim DS1390/93/94"835 help836 If you say yes here you get support for the837 Dallas/Maxim DS1390/93/94 chips.838 839 This driver supports the RTC feature and trickle charging but not840 other chip features such as alarms.841 842 This driver can also be built as a module. If so, the module843 will be called rtc-ds1390.844 845config RTC_DRV_MAX6916846 tristate "Maxim MAX6916"847 help848 If you say yes here you will get support for the849 Maxim MAX6916 SPI RTC chip.850 851 This driver only supports the RTC feature, and not other chip852 features such as alarms.853 854 This driver can also be built as a module. If so, the module855 will be called rtc-max6916.856 857config RTC_DRV_R9701858 tristate "Epson RTC-9701JE"859 help860 If you say yes here you will get support for the861 Epson RTC-9701JE SPI RTC chip.862 863 This driver can also be built as a module. If so, the module864 will be called rtc-r9701.865 866config RTC_DRV_RX4581867 tristate "Epson RX-4581"868 help869 If you say yes here you will get support for the Epson RX-4581.870 871 This driver can also be built as a module. If so the module872 will be called rtc-rx4581.873 874config RTC_DRV_RS5C348875 tristate "Ricoh RS5C348A/B"876 help877 If you say yes here you get support for the878 Ricoh RS5C348A and RS5C348B RTC chips.879 880 This driver can also be built as a module. If so, the module881 will be called rtc-rs5c348.882 883config RTC_DRV_MAX6902884 tristate "Maxim MAX6902"885 help886 If you say yes here you will get support for the887 Maxim MAX6902 SPI RTC chip.888 889 This driver can also be built as a module. If so, the module890 will be called rtc-max6902.891 892config RTC_DRV_PCF2123893 tristate "NXP PCF2123"894 select REGMAP_SPI895 help896 If you say yes here you get support for the NXP PCF2123897 RTC chip.898 899 This driver can also be built as a module. If so, the module900 will be called rtc-pcf2123.901 902config RTC_DRV_MCP795903 tristate "Microchip MCP795"904 help905 If you say yes here you will get support for the Microchip MCP795.906 907 This driver can also be built as a module. If so the module908 will be called rtc-mcp795.909 910endif # SPI_MASTER911 912#913# Helper to resolve issues with configs that have SPI enabled but I2C914# modular. See SND_SOC_I2C_AND_SPI for more information915#916config RTC_I2C_AND_SPI917 tristate918 default m if I2C=m919 default y if I2C=y920 default y if SPI_MASTER=y921 922comment "SPI and I2C RTC drivers"923 924config RTC_DRV_DS3232925 tristate "Dallas/Maxim DS3232/DS3234"926 depends on RTC_I2C_AND_SPI927 select REGMAP_I2C if I2C928 select REGMAP_SPI if SPI_MASTER929 help930 If you say yes here you get support for Dallas Semiconductor931 DS3232 and DS3234 real-time clock chips. If an interrupt is associated932 with the device, the alarm functionality is supported.933 934 This driver can also be built as a module. If so, the module935 will be called rtc-ds3232.936 937config RTC_DRV_DS3232_HWMON938 bool "HWMON support for Dallas/Maxim DS3232/DS3234"939 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)940 default y941 help942 Say Y here if you want to expose temperature sensor data on943 rtc-ds3232944 945config RTC_DRV_PCF2127946 tristate "NXP PCF2127"947 depends on RTC_I2C_AND_SPI948 select REGMAP_I2C if I2C949 select REGMAP_SPI if SPI_MASTER950 select WATCHDOG_CORE if WATCHDOG951 help952 If you say yes here you get support for the NXP PCF2127/29/31 RTC953 chips with integrated quartz crystal for industrial applications.954 These chips also have watchdog timer and tamper switch detection955 features.956 957 PCF2127 has an additional feature of 512 bytes battery backed958 memory that's accessible using nvmem interface.959 960 This driver can also be built as a module. If so, the module961 will be called rtc-pcf2127.962 963config RTC_DRV_RV3029C2964 tristate "Micro Crystal RV3029/3049"965 depends on RTC_I2C_AND_SPI966 select REGMAP_I2C if I2C967 select REGMAP_SPI if SPI_MASTER968 help969 If you say yes here you get support for the Micro Crystal970 RV3029 and RV3049 RTC chips.971 972 This driver can also be built as a module. If so, the module973 will be called rtc-rv3029c2.974 975config RTC_DRV_RV3029_HWMON976 bool "HWMON support for RV3029/3049"977 depends on RTC_DRV_RV3029C2 && HWMON978 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)979 default y980 help981 Say Y here if you want to expose temperature sensor data on982 rtc-rv3029.983 984config RTC_DRV_RX6110985 tristate "Epson RX-6110"986 depends on RTC_I2C_AND_SPI987 select REGMAP_SPI if SPI_MASTER988 select REGMAP_I2C if I2C989 help990 If you say yes here you will get support for the Epson RX-6110.991 992 This driver can also be built as a module. If so the module993 will be called rtc-rx6110.994 995comment "Platform RTC drivers"996 997# this 'CMOS' RTC driver is arch dependent because it requires998# <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a999# global rtc_lock ... it's not yet just another platform_device.1000 1001config RTC_DRV_CMOS1002 tristate "PC-style 'CMOS'"1003 depends on X86 || ARM || PPC || MIPS || SPARC641004 depends on HAS_IOPORT || MACH_DECSTATION1005 default y if X861006 select RTC_MC146818_LIB1007 help1008 Say "yes" here to get direct support for the real time clock1009 found in every PC or ACPI-based system, and some other boards.1010 Specifically the original MC146818, compatibles like those in1011 PC south bridges, the DS12887 or M48T86, some multifunction1012 or LPC bus chips, and so on.1013 1014 Your system will need to define the platform device used by1015 this driver, otherwise it won't be accessible. This means1016 you can safely enable this driver if you don't know whether1017 or not your board has this kind of hardware.1018 1019 This driver can also be built as a module. If so, the module1020 will be called rtc-cmos.1021 1022config RTC_DRV_ALPHA1023 bool "Alpha PC-style CMOS"1024 depends on ALPHA1025 depends on HAS_IOPORT1026 select RTC_MC146818_LIB1027 default y1028 help1029 Direct support for the real-time clock found on every Alpha1030 system, specifically MC146818 compatibles. If in doubt, say Y.1031 1032config RTC_DRV_DS12161033 tristate "Dallas DS1216"1034 depends on SNI_RM1035 help1036 If you say yes here you get support for the Dallas DS1216 RTC chips.1037 1038config RTC_DRV_DS12861039 tristate "Dallas DS1286"1040 depends on HAS_IOMEM1041 help1042 If you say yes here you get support for the Dallas DS1286 RTC chips.1043 1044config RTC_DRV_DS15111045 tristate "Dallas DS1511"1046 depends on HAS_IOMEM1047 help1048 If you say yes here you get support for the1049 Dallas DS1511 timekeeping/watchdog chip.1050 1051 This driver can also be built as a module. If so, the module1052 will be called rtc-ds1511.1053 1054config RTC_DRV_DS15531055 tristate "Maxim/Dallas DS1553"1056 depends on HAS_IOMEM1057 help1058 If you say yes here you get support for the1059 Maxim/Dallas DS1553 timekeeping chip.1060 1061 This driver can also be built as a module. If so, the module1062 will be called rtc-ds1553.1063 1064config RTC_DRV_DS1685_FAMILY1065 tristate "Dallas/Maxim DS1685 Family"1066 depends on HAS_IOMEM1067 help1068 If you say yes here you get support for the Dallas/Maxim DS16851069 family of real time chips. This family includes the DS1685/DS1687,1070 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and1071 DS17885/DS17887 chips.1072 1073 This driver can also be built as a module. If so, the module1074 will be called rtc-ds1685.1075 1076choice1077 prompt "Subtype"1078 depends on RTC_DRV_DS1685_FAMILY1079 default RTC_DRV_DS16851080 1081config RTC_DRV_DS16851082 bool "DS1685/DS1687"1083 help1084 This enables support for the Dallas/Maxim DS1685/DS1687 real time1085 clock chip.1086 1087 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)1088 systems, as well as EPPC-405-UC modules by electronic system design1089 GmbH.1090 1091config RTC_DRV_DS16891092 bool "DS1689/DS1693"1093 help1094 This enables support for the Dallas/Maxim DS1689/DS1693 real time1095 clock chip.1096 1097 This is an older RTC chip, supplanted by the DS1685/DS1687 above,1098 which supports a few minor features such as Vcc, Vbat, and Power1099 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.1100 1101 It also works for the even older DS1688/DS1691 RTC chips, which are1102 virtually the same and carry the same model number. Both chips1103 have 114 bytes of user NVRAM.1104 1105config RTC_DRV_DS172851106 bool "DS17285/DS17287"1107 help1108 This enables support for the Dallas/Maxim DS17285/DS17287 real time1109 clock chip.1110 1111 This chip features 2kb of extended NV-SRAM. It may possibly be1112 found in some SGI O2 systems (rare).1113 1114config RTC_DRV_DS174851115 bool "DS17485/DS17487"1116 help1117 This enables support for the Dallas/Maxim DS17485/DS17487 real time1118 clock chip.1119 1120 This chip features 4kb of extended NV-SRAM.1121 1122config RTC_DRV_DS178851123 bool "DS17885/DS17887"1124 help1125 This enables support for the Dallas/Maxim DS17885/DS17887 real time1126 clock chip.1127 1128 This chip features 8kb of extended NV-SRAM.1129 1130endchoice1131 1132config RTC_DRV_DS17421133 tristate "Maxim/Dallas DS1742/1743"1134 depends on HAS_IOMEM1135 help1136 If you say yes here you get support for the1137 Maxim/Dallas DS1742/1743 timekeeping chip.1138 1139 This driver can also be built as a module. If so, the module1140 will be called rtc-ds1742.1141 1142config RTC_DRV_DS24041143 tristate "Maxim/Dallas DS2404"1144 help1145 If you say yes here you get support for the1146 Dallas DS2404 RTC chip.1147 1148 This driver can also be built as a module. If so, the module1149 will be called rtc-ds2404.1150 1151config RTC_DRV_DA90521152 tristate "Dialog DA9052/DA9053 RTC"1153 depends on PMIC_DA90521154 help1155 Say y here to support the RTC driver for Dialog Semiconductor1156 DA9052-BC and DA9053-AA/Bx PMICs.1157 1158config RTC_DRV_DA90551159 tristate "Dialog Semiconductor DA9055 RTC"1160 depends on MFD_DA90551161 help1162 If you say yes here you will get support for the1163 RTC of the Dialog DA9055 PMIC.1164 1165 This driver can also be built as a module. If so, the module1166 will be called rtc-da90551167 1168config RTC_DRV_DA90631169 tristate "Dialog Semiconductor DA9063/DA9062 RTC"1170 depends on MFD_DA9063 || MFD_DA90621171 help1172 If you say yes here you will get support for the RTC subsystem1173 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.1174 1175 This driver can also be built as a module. If so, the module1176 will be called "rtc-da9063".1177 1178config RTC_DRV_EFI1179 tristate "EFI RTC"1180 depends on EFI && !X861181 help1182 If you say yes here you will get support for the EFI1183 Real Time Clock.1184 1185 This driver can also be built as a module. If so, the module1186 will be called rtc-efi.1187 1188config RTC_DRV_STK17TA81189 tristate "Simtek STK17TA8"1190 depends on HAS_IOMEM1191 help1192 If you say yes here you get support for the1193 Simtek STK17TA8 timekeeping chip.1194 1195 This driver can also be built as a module. If so, the module1196 will be called rtc-stk17ta8.1197 1198config RTC_DRV_M48T861199 tristate "ST M48T86/Dallas DS12887"1200 depends on HAS_IOMEM1201 help1202 If you say Y here you will get support for the1203 ST M48T86 and Dallas DS12887 RTC chips.1204 1205 This driver can also be built as a module. If so, the module1206 will be called rtc-m48t86.1207 1208config RTC_DRV_M48T351209 tristate "ST M48T35"1210 depends on HAS_IOMEM1211 help1212 If you say Y here you will get support for the1213 ST M48T35 RTC chip.1214 1215 This driver can also be built as a module, if so, the module1216 will be called "rtc-m48t35".1217 1218config RTC_DRV_M48T591219 tristate "ST M48T59/M48T08/M48T02"1220 depends on HAS_IOMEM1221 help1222 If you say Y here you will get support for the1223 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.1224 1225 These chips are usually found in Sun SPARC and UltraSPARC1226 workstations.1227 1228 This driver can also be built as a module, if so, the module1229 will be called "rtc-m48t59".1230 1231config RTC_DRV_MSM62421232 tristate "Oki MSM6242"1233 depends on HAS_IOMEM1234 help1235 If you say yes here you get support for the Oki MSM62421236 timekeeping chip. It is used in some Amiga models (e.g. A2000).1237 1238 This driver can also be built as a module. If so, the module1239 will be called rtc-msm6242.1240 1241config RTC_DRV_BQ48021242 tristate "TI BQ4802"1243 depends on HAS_IOMEM && HAS_IOPORT1244 depends on SPARC || COMPILE_TEST1245 help1246 If you say Y here you will get support for the TI1247 BQ4802 RTC chip.1248 1249 This driver can also be built as a module. If so, the module1250 will be called rtc-bq4802.1251 1252config RTC_DRV_RP5C011253 tristate "Ricoh RP5C01"1254 depends on HAS_IOMEM1255 help1256 If you say yes here you get support for the Ricoh RP5C011257 timekeeping chip. It is used in some Amiga models (e.g. A30001258 and A4000).1259 1260 This driver can also be built as a module. If so, the module1261 will be called rtc-rp5c01.1262 1263config RTC_DRV_GAMECUBE1264 tristate "Nintendo GameCube, Wii and Wii U RTC"1265 depends on GAMECUBE || WII || COMPILE_TEST1266 select REGMAP1267 help1268 If you say yes here you will get support for the RTC subsystem1269 of the Nintendo GameCube, Wii and Wii U.1270 1271 This driver can also be built as a module. If so, the module1272 will be called "rtc-gamecube".1273 1274config RTC_DRV_WM831X1275 tristate "Wolfson Microelectronics WM831x RTC"1276 depends on MFD_WM831X1277 help1278 If you say yes here you will get support for the RTC subsystem1279 of the Wolfson Microelectronics WM831X series PMICs.1280 1281 This driver can also be built as a module. If so, the module1282 will be called "rtc-wm831x".1283 1284config RTC_DRV_WM83501285 tristate "Wolfson Microelectronics WM8350 RTC"1286 depends on MFD_WM83501287 help1288 If you say yes here you will get support for the RTC subsystem1289 of the Wolfson Microelectronics WM8350.1290 1291 This driver can also be built as a module. If so, the module1292 will be called "rtc-wm8350".1293 1294config RTC_DRV_SC27XX1295 tristate "Spreadtrum SC27xx RTC"1296 depends on MFD_SC27XX_PMIC || COMPILE_TEST1297 help1298 If you say Y here you will get support for the RTC subsystem1299 of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs1300 includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips.1301 1302 This driver can also be built as a module. If so, the module1303 will be called rtc-sc27xx.1304 1305config RTC_DRV_SPEAR1306 tristate "SPEAR ST RTC"1307 depends on PLAT_SPEAR || COMPILE_TEST1308 default y1309 help1310 If you say Y here you will get support for the RTC found on1311 spear1312 1313config RTC_DRV_PCF506331314 depends on MFD_PCF506331315 tristate "NXP PCF50633 RTC"1316 help1317 If you say yes here you get support for the RTC subsystem of the1318 NXP PCF50633 used in embedded systems.1319 1320config RTC_DRV_AB85001321 tristate "ST-Ericsson AB8500 RTC"1322 depends on AB8500_CORE1323 select RTC_INTF_DEV1324 select RTC_INTF_DEV_UIE_EMUL1325 help1326 Select this to enable the ST-Ericsson AB8500 power management IC RTC1327 support. This chip contains a battery- and capacitor-backed RTC.1328 1329config RTC_DRV_OPAL1330 tristate "IBM OPAL RTC driver"1331 depends on PPC_POWERNV1332 default y1333 help1334 If you say yes here you get support for the PowerNV platform RTC1335 driver based on OPAL interfaces.1336 1337 This driver can also be built as a module. If so, the module1338 will be called rtc-opal.1339 1340config RTC_DRV_OPTEE1341 tristate "OP-TEE based RTC driver"1342 depends on OPTEE1343 help1344 Select this to get support for OP-TEE based RTC control on SoCs where1345 RTC are not accessible to the normal world (Linux).1346 1347 This driver can also be built as a module. If so, the module1348 will be called rtc-optee.1349 1350config RTC_DRV_ZYNQMP1351 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"1352 depends on OF && HAS_IOMEM1353 help1354 If you say yes here you get support for the RTC controller found on1355 Xilinx Zynq Ultrascale+ MPSoC.1356 1357config RTC_DRV_CROS_EC1358 tristate "Chrome OS EC RTC driver"1359 depends on CROS_EC1360 help1361 If you say yes here you will get support for the1362 Chrome OS Embedded Controller's RTC.1363 1364 This driver can also be built as a module. If so, the module1365 will be called rtc-cros-ec.1366 1367config RTC_DRV_NTXEC1368 tristate "Netronix embedded controller RTC"1369 depends on MFD_NTXEC1370 help1371 Say yes here if you want to support the RTC functionality of the1372 embedded controller found in certain e-book readers designed by the1373 original design manufacturer Netronix.1374 1375comment "on-CPU RTC drivers"1376 1377config RTC_DRV_ASM92601378 tristate "Alphascale asm9260 RTC"1379 depends on MACH_ASM9260 || COMPILE_TEST1380 help1381 If you say yes here you get support for the RTC on the1382 Alphascale asm9260 SoC.1383 1384 This driver can also be built as a module. If so, the module1385 will be called rtc-asm9260.1386 1387config RTC_DRV_DIGICOLOR1388 tristate "Conexant Digicolor RTC"1389 depends on ARCH_DIGICOLOR || COMPILE_TEST1390 help1391 If you say yes here you get support for the RTC on Conexant1392 Digicolor platforms. This currently includes the CX92755 SoC.1393 1394 This driver can also be built as a module. If so, the module1395 will be called rtc-digicolor.1396 1397config RTC_DRV_IMXDI1398 tristate "Freescale IMX DryIce Real Time Clock"1399 depends on ARCH_MXC || COMPILE_TEST1400 depends on OF1401 help1402 Support for Freescale IMX DryIce RTC1403 1404 This driver can also be built as a module, if so, the module1405 will be called "rtc-imxdi".1406 1407config RTC_DRV_FSL_FTM_ALARM1408 tristate "Freescale FlexTimer alarm timer"1409 depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST1410 help1411 For the FlexTimer in LS1012A, LS1021A, LS1028A, LS1043A, LS1046A,1412 LS1088A, LS208xA, we can use FTM as the wakeup source.1413 1414 Say y here to enable FTM alarm support. The FTM alarm provides1415 alarm functions for wakeup system from deep sleep.1416 1417 This driver can also be built as a module, if so, the module1418 will be called "rtc-fsl-ftm-alarm".1419 1420config RTC_DRV_MESON1421 tristate "Amlogic Meson RTC"1422 depends on (ARM && ARCH_MESON) || COMPILE_TEST1423 select REGMAP_MMIO1424 help1425 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b1426 and Meson8m2 SoCs.1427 1428 This driver can also be built as a module, if so, the module1429 will be called "rtc-meson".1430 1431config RTC_DRV_MESON_VRTC1432 tristate "Amlogic Meson Virtual RTC"1433 depends on ARCH_MESON || COMPILE_TEST1434 default m if ARCH_MESON1435 help1436 If you say yes here you will get support for the1437 Virtual RTC of Amlogic SoCs.1438 1439 This driver can also be built as a module. If so, the module1440 will be called rtc-meson-vrtc.1441 1442config RTC_DRV_OMAP1443 tristate "TI OMAP Real Time Clock"1444 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST1445 depends on OF1446 depends on PINCTRL1447 select GENERIC_PINCONF1448 help1449 Say "yes" here to support the on chip real time clock1450 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.1451 1452 This driver can also be built as a module, if so, module1453 will be called rtc-omap.1454 1455config RTC_DRV_S3C1456 tristate "Samsung S3C series SoC RTC"1457 depends on ARCH_EXYNOS || ARCH_S3C64XX || ARCH_S5PV210 || \1458 COMPILE_TEST1459 help1460 RTC (Realtime Clock) driver for the clock inbuilt into the1461 Samsung S3C64XX series of SoCs. This can provide periodic1462 interrupt rates from 1Hz to 64Hz for user programs, and1463 wakeup from Alarm.1464 1465 This driver can also be build as a module. If so, the module1466 will be called rtc-s3c.1467 1468config RTC_DRV_EP93XX1469 tristate "Cirrus Logic EP93XX"1470 depends on ARCH_EP93XX || COMPILE_TEST1471 help1472 If you say yes here you get support for the1473 RTC embedded in the Cirrus Logic EP93XX processors.1474 1475 This driver can also be built as a module. If so, the module1476 will be called rtc-ep93xx.1477 1478config RTC_DRV_SA11001479 tristate "SA11x0/PXA2xx/PXA910"1480 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP1481 help1482 If you say Y here you will get access to the real time clock1483 built into your SA11x0 or PXA2xx CPU.1484 1485 To compile this driver as a module, choose M here: the1486 module will be called rtc-sa1100.1487 1488config RTC_DRV_SH1489 tristate "SuperH On-Chip RTC"1490 depends on SUPERH || ARCH_RENESAS1491 help1492 Say Y here to enable support for the on-chip RTC found in1493 most SuperH processors. This RTC is also found in RZ/A SoCs.1494 1495 To compile this driver as a module, choose M here: the1496 module will be called rtc-sh.1497 1498config RTC_DRV_SUNPLUS1499 tristate "Sunplus SP7021 RTC"1500 depends on SOC_SP70211501 help1502 Say 'yes' to get support for the real-time clock present in1503 Sunplus SP7021 - a SoC for industrial applications. It provides1504 RTC status check, timer/alarm functionalities, user data1505 reservation with the battery over 2.5V, RTC power status check1506 and battery charge.1507 1508 This driver can also be built as a module. If so, the module1509 will be called rtc-sunplus.1510 1511config RTC_DRV_PL0301512 tristate "ARM AMBA PL030 RTC"1513 depends on ARM_AMBA1514 help1515 If you say Y here you will get access to ARM AMBA1516 PrimeCell PL030 RTC found on certain ARM SOCs.1517 1518 To compile this driver as a module, choose M here: the1519 module will be called rtc-pl030.1520 1521config RTC_DRV_PL0311522 tristate "ARM AMBA PL031 RTC"1523 depends on ARM_AMBA1524 help1525 If you say Y here you will get access to ARM AMBA1526 PrimeCell PL031 RTC found on certain ARM SOCs.1527 1528 To compile this driver as a module, choose M here: the1529 module will be called rtc-pl031.1530 1531config RTC_DRV_AT91RM92001532 tristate "AT91RM9200 or some AT91SAM9 RTC"1533 depends on ARCH_AT91 || COMPILE_TEST1534 depends on OF1535 help1536 Driver for the internal RTC (Realtime Clock) module found on1537 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips1538 this is powered by the backup power supply.1539 1540config RTC_DRV_AT91SAM91541 tristate "AT91SAM9 RTT as RTC"1542 depends on ARCH_AT91 || COMPILE_TEST1543 depends on OF && HAS_IOMEM1544 select MFD_SYSCON1545 help1546 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which1547 can be used as an RTC thanks to the backup power supply (e.g. a1548 small coin cell battery) which keeps this block and the GPBR1549 (General Purpose Backup Registers) block powered when the device1550 is shutdown.1551 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd1552 probably want to use the real RTC block instead of the "RTT as an1553 RTC" driver.1554 1555config RTC_DRV_AU1XXX1556 tristate "Au1xxx Counter0 RTC support"1557 depends on MIPS_ALCHEMY1558 help1559 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year1560 counter) to be used as a RTC.1561 1562 This driver can also be built as a module. If so, the module1563 will be called rtc-au1xxx.1564 1565config RTC_DRV_RS5C3131566 tristate "Ricoh RS5C313"1567 depends on SH_LANDISK1568 help1569 If you say yes here you get support for the Ricoh RS5C313 RTC chips.1570 1571config RTC_DRV_RZN11572 tristate "Renesas RZ/N1 RTC"1573 depends on ARCH_RZN1 || COMPILE_TEST1574 depends on OF && HAS_IOMEM1575 help1576 If you say yes here you get support for the Renesas RZ/N1 RTC.1577 1578config RTC_DRV_GENERIC1579 tristate "Generic RTC support"1580 # Please consider writing a new RTC driver instead of using the generic1581 # RTC abstraction1582 depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST1583 help1584 Say Y or M here to enable RTC support on systems using the generic1585 RTC abstraction. If you do not know what you are doing, you should1586 just say Y.1587 1588config RTC_DRV_PXA1589 tristate "PXA27x/PXA3xx"1590 depends on ARCH_PXA1591 select RTC_DRV_SA11001592 help1593 If you say Y here you will get access to the real time clock1594 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs1595 consisting of an SA1100 compatible RTC and the extended PXA RTC.1596 1597 This RTC driver uses PXA RTC registers available since pxa27x1598 series (RDxR, RYxR) instead of legacy RCNR, RTAR.1599 1600config RTC_DRV_VT85001601 tristate "VIA/WonderMedia 85xx SoC RTC"1602 depends on ARCH_VT8500 || COMPILE_TEST1603 help1604 If you say Y here you will get access to the real time clock1605 built into your VIA VT8500 SoC or its relatives.1606 1607 1608config RTC_DRV_SUN4V1609 bool "SUN4V Hypervisor RTC"1610 depends on SPARC641611 help1612 If you say Y here you will get support for the Hypervisor1613 based RTC on SUN4V systems.1614 1615config RTC_DRV_SUN6I1616 bool "Allwinner A31 RTC"1617 default MACH_SUN6I || MACH_SUN8I1618 depends on COMMON_CLK1619 depends on ARCH_SUNXI || COMPILE_TEST1620 help1621 If you say Y here you will get support for the RTC found in1622 some Allwinner SoCs like the A31 or the A64.1623 1624config RTC_DRV_SUNXI1625 tristate "Allwinner sun4i/sun7i RTC"1626 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST1627 help1628 If you say Y here you will get support for the RTC found on1629 Allwinner A10/A20.1630 1631config RTC_DRV_STARFIRE1632 bool "Starfire RTC"1633 depends on SPARC641634 help1635 If you say Y here you will get support for the RTC found on1636 Starfire systems.1637 1638config RTC_DRV_MV1639 tristate "Marvell SoC RTC"1640 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST1641 help1642 If you say yes here you will get support for the in-chip RTC1643 that can be found in some of Marvell's SoC devices, such as1644 the Kirkwood 88F6281 and 88F6192.1645 1646 This driver can also be built as a module. If so, the module1647 will be called rtc-mv.1648 1649config RTC_DRV_ARMADA38X1650 tristate "Armada 38x Marvell SoC RTC"1651 depends on ARCH_MVEBU || COMPILE_TEST1652 depends on OF1653 help1654 If you say yes here you will get support for the in-chip RTC1655 that can be found in the Armada 38x Marvell's SoC device1656 1657 This driver can also be built as a module. If so, the module1658 will be called armada38x-rtc.1659 1660config RTC_DRV_CADENCE1661 tristate "Cadence RTC driver"1662 depends on OF && HAS_IOMEM1663 help1664 If you say Y here you will get access to Cadence RTC IP1665 found on certain SOCs.1666 1667 To compile this driver as a module, choose M here: the1668 module will be called rtc-cadence.1669 1670config RTC_DRV_FTRTC0101671 tristate "Faraday Technology FTRTC010 RTC"1672 depends on HAS_IOMEM1673 default ARCH_GEMINI1674 help1675 If you say Y here you will get support for the1676 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.1677 1678 This driver can also be built as a module. If so, the module1679 will be called rtc-ftrtc010.1680 1681config RTC_DRV_PS31682 tristate "PS3 RTC"1683 depends on PPC_PS31684 help1685 If you say yes here you will get support for the RTC on PS3.1686 1687 This driver can also be built as a module. If so, the module1688 will be called rtc-ps3.1689 1690config RTC_DRV_STMP1691 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"1692 depends on ARCH_MXS || COMPILE_TEST1693 select STMP_DEVICE1694 help1695 If you say yes here you will get support for the onboard1696 STMP3xxx/i.MX23/i.MX28 RTC.1697 1698 This driver can also be built as a module. If so, the module1699 will be called rtc-stmp3xxx.1700 1701config RTC_DRV_PCAP1702 tristate "PCAP RTC"1703 depends on EZX_PCAP1704 help1705 If you say Y here you will get support for the RTC found on1706 the PCAP2 ASIC used on some Motorola phones.1707 1708config RTC_DRV_MC13XXX1709 depends on MFD_MC13XXX1710 tristate "Freescale MC13xxx RTC"1711 help1712 This enables support for the RTCs found on Freescale's PMICs1713 MC13783 and MC13892.1714 1715config RTC_DRV_MPC51211716 tristate "Freescale MPC5121 built-in RTC"1717 depends on PPC_MPC512x || PPC_MPC52xx1718 help1719 If you say yes here you will get support for the1720 built-in RTC on MPC5121 or on MPC5200.1721 1722 This driver can also be built as a module. If so, the module1723 will be called rtc-mpc5121.1724 1725config RTC_DRV_JZ47401726 tristate "Ingenic JZ4740 SoC"1727 depends on MIPS || COMPILE_TEST1728 depends on OF && COMMON_CLK1729 help1730 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC1731 controllers.1732 1733 This driver can also be built as a module. If so, the module1734 will be called rtc-jz4740.1735 1736config RTC_DRV_LOONGSON1737 tristate "Loongson On-chip RTC"1738 depends on MACH_LOONGSON32 || MACH_LOONGSON64 || COMPILE_TEST1739 select REGMAP_MMIO1740 help1741 This is a driver for the Loongson on-chip Counter0 (Time-Of-Year1742 counter) to be used as a RTC.1743 It can be found on Loongson-1 series cpu, Loongson-2K series cpu1744 and Loongson LS7A bridge chips.1745 1746 This driver can also be built as a module. If so, the module1747 will be called rtc-loongson.1748 1749config RTC_DRV_LPC24XX1750 tristate "NXP RTC for LPC178x/18xx/408x/43xx"1751 depends on ARCH_LPC18XX || COMPILE_TEST1752 depends on OF && HAS_IOMEM1753 depends on COMMON_CLK1754 help1755 This enables support for the NXP RTC found which can be found on1756 NXP LPC178x/18xx/408x/43xx devices.1757 1758 If you have one of the devices above enable this driver to use1759 the hardware RTC. This driver can also be built as a module. If1760 so, the module will be called rtc-lpc24xx.1761 1762config RTC_DRV_LPC32XX1763 depends on ARCH_LPC32XX || COMPILE_TEST1764 tristate "NXP LPC32XX RTC"1765 help1766 This enables support for the NXP RTC in the LPC32XX1767 1768 This driver can also be built as a module. If so, the module1769 will be called rtc-lpc32xx.1770 1771config RTC_DRV_PM8XXX1772 tristate "Qualcomm PMIC8XXX RTC"1773 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST1774 help1775 If you say yes here you get support for the1776 Qualcomm PMIC8XXX RTC.1777 1778 To compile this driver as a module, choose M here: the1779 module will be called rtc-pm8xxx.1780 1781config RTC_DRV_TEGRA1782 tristate "NVIDIA Tegra Internal RTC driver"1783 depends on ARCH_TEGRA || COMPILE_TEST1784 help1785 If you say yes here you get support for the1786 Tegra 200 series internal RTC module.1787 1788 This drive can also be built as a module. If so, the module1789 will be called rtc-tegra.1790 1791config RTC_DRV_MXC1792 tristate "Freescale MXC Real Time Clock"1793 depends on ARCH_MXC || COMPILE_TEST1794 depends on HAS_IOMEM1795 depends on OF1796 help1797 If you say yes here you get support for the Freescale MXC1798 RTC module.1799 1800 This driver can also be built as a module, if so, the module1801 will be called "rtc-mxc".1802 1803config RTC_DRV_MXC_V21804 tristate "Freescale MXC Real Time Clock for i.MX53"1805 depends on ARCH_MXC || COMPILE_TEST1806 depends on HAS_IOMEM1807 depends on OF1808 help1809 If you say yes here you get support for the Freescale MXC1810 SRTC module in i.MX53 processor.1811 1812 This driver can also be built as a module, if so, the module1813 will be called "rtc-mxc_v2".1814 1815config RTC_DRV_SNVS1816 tristate "Freescale SNVS RTC support"1817 select REGMAP_MMIO1818 depends on ARCH_MXC || COMPILE_TEST1819 depends on HAS_IOMEM1820 depends on OF1821 help1822 If you say yes here you get support for the Freescale SNVS1823 Low Power (LP) RTC module.1824 1825 This driver can also be built as a module, if so, the module1826 will be called "rtc-snvs".1827 1828config RTC_DRV_BBNSM1829 tristate "NXP BBNSM RTC support"1830 select REGMAP_MMIO1831 depends on ARCH_MXC || COMPILE_TEST1832 depends on HAS_IOMEM1833 depends on OF1834 help1835 If you say yes here you get support for the NXP BBNSM RTC module.1836 1837 This driver can also be built as a module, if so, the module1838 will be called "rtc-bbnsm".1839 1840config RTC_DRV_IMX_BBM_SCMI1841 depends on IMX_SCMI_BBM_EXT || COMPILE_TEST1842 default y if ARCH_MXC1843 tristate "NXP i.MX BBM SCMI RTC support"1844 help1845 If you say yes here you get support for the NXP i.MX BBSM SCMI1846 RTC module.1847 1848 To compile this driver as a module, choose M here: the1849 module will be called rtc-imx-sm-bbm.1850 1851config RTC_DRV_IMX_SC1852 depends on IMX_SCU1853 depends on HAVE_ARM_SMCCC1854 tristate "NXP i.MX System Controller RTC support"1855 help1856 If you say yes here you get support for the NXP i.MX System1857 Controller RTC module.1858 1859config RTC_DRV_ST_LPC1860 tristate "STMicroelectronics LPC RTC"1861 depends on ARCH_STI1862 depends on OF1863 help1864 Say Y here to include STMicroelectronics Low Power Controller1865 (LPC) based RTC support.1866 1867 To compile this driver as a module, choose M here: the1868 module will be called rtc-st-lpc.1869 1870config RTC_DRV_MOXART1871 tristate "MOXA ART RTC"1872 depends on ARCH_MOXART || COMPILE_TEST1873 help1874 If you say yes here you get support for the MOXA ART1875 RTC module.1876 1877 This driver can also be built as a module. If so, the module1878 will be called rtc-moxart1879 1880config RTC_DRV_MT27121881 tristate "MediaTek MT2712 SoC based RTC"1882 depends on ARCH_MEDIATEK || COMPILE_TEST1883 help1884 This enables support for the real time clock built in the MediaTek1885 SoCs for MT2712.1886 1887 This drive can also be built as a module. If so, the module1888 will be called rtc-mt2712.1889 1890config RTC_DRV_MT63971891 tristate "MediaTek PMIC based RTC"1892 depends on MFD_MT6397 || COMPILE_TEST1893 select IRQ_DOMAIN1894 help1895 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek1896 MT6397 PMIC. You should enable MT6397 PMIC MFD before select1897 MediaTek(R) RTC driver.1898 1899 If you want to use MediaTek(R) RTC interface, select Y or M here.1900 1901config RTC_DRV_MT76221902 tristate "MediaTek SoC based RTC"1903 depends on ARCH_MEDIATEK || COMPILE_TEST1904 help1905 This enables support for the real time clock built in the MediaTek1906 SoCs.1907 1908 This drive can also be built as a module. If so, the module1909 will be called rtc-mt7622.1910 1911config RTC_DRV_XGENE1912 tristate "APM X-Gene RTC"1913 depends on HAS_IOMEM1914 depends on ARCH_XGENE || COMPILE_TEST1915 help1916 If you say yes here you get support for the APM X-Gene SoC real time1917 clock.1918 1919 This driver can also be built as a module, if so, the module1920 will be called "rtc-xgene".1921 1922config RTC_DRV_PIC321923 tristate "Microchip PIC32 RTC"1924 depends on MACH_PIC321925 default y1926 help1927 If you say yes here you get support for the PIC32 RTC module.1928 1929 This driver can also be built as a module. If so, the module1930 will be called rtc-pic321931 1932config RTC_DRV_R73011933 tristate "EPSON TOYOCOM RTC-7301SF/DG"1934 select REGMAP_MMIO1935 depends on OF && HAS_IOMEM1936 help1937 If you say yes here you get support for the EPSON TOYOCOM1938 RTC-7301SF/DG chips.1939 1940 This driver can also be built as a module. If so, the module1941 will be called rtc-r7301.1942 1943config RTC_DRV_STM321944 tristate "STM32 RTC"1945 select REGMAP_MMIO1946 depends on ARCH_STM32 || COMPILE_TEST1947 depends on OF1948 depends on PINCTRL1949 select PINMUX1950 select PINCONF1951 select GENERIC_PINCONF1952 depends on COMMON_CLK1953 help1954 If you say yes here you get support for the STM32 On-Chip1955 Real Time Clock.1956 1957 This driver can also be built as a module, if so, the module1958 will be called "rtc-stm32".1959 1960config RTC_DRV_CPCAP1961 depends on MFD_CPCAP1962 tristate "Motorola CPCAP RTC"1963 help1964 Say y here for CPCAP rtc found on some Motorola phones1965 and tablets such as Droid 4.1966 1967config RTC_DRV_RTD119X1968 bool "Realtek RTD129x RTC"1969 depends on ARCH_REALTEK || COMPILE_TEST1970 default ARCH_REALTEK1971 help1972 If you say yes here, you get support for the RTD1295 SoC1973 Real Time Clock.1974 1975config RTC_DRV_ASPEED1976 tristate "ASPEED RTC"1977 depends on OF1978 depends on ARCH_ASPEED || COMPILE_TEST1979 help1980 If you say yes here you get support for the ASPEED BMC SoC real time1981 clocks.1982 1983 This driver can also be built as a module, if so, the module1984 will be called "rtc-aspeed".1985 1986config RTC_DRV_TI_K31987 tristate "TI K3 RTC"1988 depends on ARCH_K3 || COMPILE_TEST1989 select REGMAP_MMIO1990 help1991 If you say yes here you get support for the Texas Instruments's1992 Real Time Clock for K3 architecture.1993 1994 This driver can also be built as a module, if so, the module1995 will be called "rtc-ti-k3".1996 1997config RTC_DRV_MA35D11998 tristate "Nuvoton MA35D1 RTC"1999 depends on ARCH_MA35 || COMPILE_TEST2000 select REGMAP_MMIO2001 help2002 If you say yes here you get support for the Nuvoton MA35D12003 On-Chip Real Time Clock.2004 2005 This driver can also be built as a module, if so, the module2006 will be called "rtc-ma35d1".2007 2008comment "HID Sensor RTC drivers"2009 2010config RTC_DRV_HID_SENSOR_TIME2011 tristate "HID Sensor Time"2012 depends on USB_HID2013 depends on HID_SENSOR_HUB && IIO2014 select HID_SENSOR_IIO_COMMON2015 help2016 Say yes here to build support for the HID Sensors of type Time.2017 This drivers makes such sensors available as RTCs.2018 2019 If this driver is compiled as a module, it will be named2020 rtc-hid-sensor-time.2021 2022config RTC_DRV_GOLDFISH2023 tristate "Goldfish Real Time Clock"2024 depends on HAS_IOMEM2025 help2026 Say yes to enable RTC driver for the Goldfish based virtual platform.2027 2028 Goldfish is a code name for the virtual platform developed by Google2029 for Android emulation.2030 2031config RTC_DRV_WILCO_EC2032 tristate "Wilco EC RTC"2033 depends on WILCO_EC2034 default m2035 help2036 If you say yes here, you get read/write support for the Real Time2037 Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook)2038 2039 This can also be built as a module. If so, the module will2040 be named "rtc_wilco_ec".2041 2042config RTC_DRV_MSC3132043 tristate "MStar MSC313 RTC"2044 depends on ARCH_MSTARV7 || COMPILE_TEST2045 help2046 If you say yes here you get support for the Mstar MSC313e On-Chip2047 Real Time Clock.2048 2049 This driver can also be built as a module, if so, the module2050 will be called "rtc-msc313".2051 2052config RTC_DRV_POLARFIRE_SOC2053 tristate "Microchip PolarFire SoC built-in RTC"2054 depends on ARCH_MICROCHIP_POLARFIRE2055 help2056 If you say yes here you will get support for the2057 built-in RTC on Polarfire SoC.2058 2059 This driver can also be built as a module, if so, the module2060 will be called "rtc-mpfs".2061 2062config RTC_DRV_SSD202D2063 tristate "SigmaStar SSD202D RTC"2064 depends on ARCH_MSTARV7 || COMPILE_TEST2065 default ARCH_MSTARV72066 help2067 If you say yes here you get support for the SigmaStar SSD202D On-Chip2068 Real Time Clock.2069 2070 This driver can also be built as a module, if so, the module2071 will be called "rtc-ssd20xd".2072 2073endif # RTC_CLASS2074