| .. | .. |
|---|
| 1 | +# SPDX-License-Identifier: GPL-2.0-only |
|---|
| 1 | 2 | # |
|---|
| 2 | 3 | # RTC class/drivers configuration |
|---|
| 3 | 4 | # |
|---|
| .. | .. |
|---|
| 39 | 40 | starts up, and when it resumes from a low power state. This |
|---|
| 40 | 41 | device should record time in UTC, since the kernel won't do |
|---|
| 41 | 42 | 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 | 43 | |
|---|
| 46 | 44 | This clock should be battery-backed, so that it reads the correct |
|---|
| 47 | 45 | time when the system boots from a power-off state. Otherwise, your |
|---|
| .. | .. |
|---|
| 185 | 183 | This driver can also be built as a module. If so, the module |
|---|
| 186 | 184 | will be called rtc-ab-b5ze-s3. |
|---|
| 187 | 185 | |
|---|
| 186 | +config RTC_DRV_ABEOZ9 |
|---|
| 187 | + select REGMAP_I2C |
|---|
| 188 | + tristate "Abracon AB-RTCMC-32.768kHz-EOZ9" |
|---|
| 189 | + help |
|---|
| 190 | + If you say yes here you get support for the Abracon |
|---|
| 191 | + AB-RTCMC-32.768kHz-EOA9 I2C RTC chip. |
|---|
| 192 | + |
|---|
| 193 | + This driver can also be built as a module. If so, the module |
|---|
| 194 | + will be called rtc-ab-e0z9. |
|---|
| 195 | + |
|---|
| 188 | 196 | config RTC_DRV_ABX80X |
|---|
| 189 | 197 | tristate "Abracon ABx80x" |
|---|
| 198 | + select WATCHDOG_CORE if WATCHDOG |
|---|
| 190 | 199 | help |
|---|
| 191 | 200 | If you say yes here you get support for Abracon AB080X and AB180X |
|---|
| 192 | 201 | families of ultra-low-power battery- and capacitor-backed real-time |
|---|
| .. | .. |
|---|
| 228 | 237 | |
|---|
| 229 | 238 | config RTC_DRV_DS1307 |
|---|
| 230 | 239 | tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057" |
|---|
| 240 | + select REGMAP_I2C |
|---|
| 241 | + select WATCHDOG_CORE if WATCHDOG |
|---|
| 231 | 242 | help |
|---|
| 232 | 243 | If you say yes here you get support for various compatible RTC |
|---|
| 233 | 244 | chips (often with battery backup) connected with I2C. This driver |
|---|
| .. | .. |
|---|
| 270 | 281 | |
|---|
| 271 | 282 | config RTC_DRV_DS1374_WDT |
|---|
| 272 | 283 | bool "Dallas/Maxim DS1374 watchdog timer" |
|---|
| 273 | | - depends on RTC_DRV_DS1374 |
|---|
| 284 | + depends on RTC_DRV_DS1374 && WATCHDOG |
|---|
| 285 | + select WATCHDOG_CORE |
|---|
| 274 | 286 | help |
|---|
| 275 | 287 | If you say Y here you will get support for the |
|---|
| 276 | 288 | watchdog timer in the Dallas Semiconductor DS1374 |
|---|
| .. | .. |
|---|
| 284 | 296 | |
|---|
| 285 | 297 | This driver can also be built as a module. If so, the module |
|---|
| 286 | 298 | will be called rtc-ds1672. |
|---|
| 287 | | - |
|---|
| 288 | | -config RTC_DRV_FAKE |
|---|
| 289 | | - tristate "FAKE RTC" |
|---|
| 290 | | - help |
|---|
| 291 | | - This driver as a virtual rtc module, if so, the module |
|---|
| 292 | | - will be called "rtc-fake". |
|---|
| 293 | 299 | |
|---|
| 294 | 300 | config RTC_DRV_HYM8563 |
|---|
| 295 | 301 | tristate "Haoyu Microelectronics HYM8563" |
|---|
| .. | .. |
|---|
| 383 | 389 | depends on MFD_RK808 |
|---|
| 384 | 390 | help |
|---|
| 385 | 391 | If you say yes here you will get support for the |
|---|
| 386 | | - RTC of RK805, RK808 , RK809, RK816, RK817 and RK818 PMIC. |
|---|
| 392 | + RTC of RK805, RK809 and RK817, RK808, RK816 and RK818 PMIC. |
|---|
| 387 | 393 | |
|---|
| 388 | 394 | This driver can also be built as a module. If so, the module |
|---|
| 389 | 395 | will be called rk808-rtc. |
|---|
| 390 | 396 | |
|---|
| 391 | | -config RTC_DRV_RK_TIMER |
|---|
| 392 | | - tristate "Rockchip timer RTC" |
|---|
| 393 | | - depends on OF |
|---|
| 397 | +config RTC_DRV_ROCKCHIP |
|---|
| 398 | + tristate "Rockchip RTC" |
|---|
| 399 | + depends on ARCH_ROCKCHIP |
|---|
| 394 | 400 | help |
|---|
| 395 | 401 | If you say yes here you will get support for the |
|---|
| 396 | | - RTC of Rockchip timer. |
|---|
| 402 | + RTC of Rockchip. |
|---|
| 397 | 403 | |
|---|
| 398 | 404 | This driver can also be built as a module. If so, the module |
|---|
| 399 | | - will be called rtc-rk-timer. |
|---|
| 405 | + will be called rtc-rockchip. |
|---|
| 400 | 406 | |
|---|
| 401 | 407 | config RTC_DRV_RS5C372 |
|---|
| 402 | 408 | tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A" |
|---|
| .. | .. |
|---|
| 455 | 461 | |
|---|
| 456 | 462 | config RTC_DRV_PCF85063 |
|---|
| 457 | 463 | tristate "NXP PCF85063" |
|---|
| 464 | + select REGMAP_I2C |
|---|
| 458 | 465 | help |
|---|
| 459 | 466 | If you say yes here you get support for the PCF85063 RTC chip |
|---|
| 460 | 467 | |
|---|
| .. | .. |
|---|
| 463 | 470 | |
|---|
| 464 | 471 | config RTC_DRV_PCF85363 |
|---|
| 465 | 472 | tristate "NXP PCF85363" |
|---|
| 466 | | - depends on I2C |
|---|
| 467 | 473 | select REGMAP_I2C |
|---|
| 468 | 474 | help |
|---|
| 469 | 475 | If you say yes here you get support for the PCF85363 RTC chip. |
|---|
| .. | .. |
|---|
| 513 | 519 | help |
|---|
| 514 | 520 | If you say Y here you will get support for the |
|---|
| 515 | 521 | watchdog timer in the ST M41T60 and M41T80 RTC chips series. |
|---|
| 522 | + |
|---|
| 523 | +config RTC_DRV_BD70528 |
|---|
| 524 | + tristate "ROHM BD70528 PMIC RTC" |
|---|
| 525 | + depends on MFD_ROHM_BD70528 && (BD70528_WATCHDOG || !BD70528_WATCHDOG) |
|---|
| 526 | + help |
|---|
| 527 | + If you say Y here you will get support for the RTC |
|---|
| 528 | + block on ROHM BD70528 and BD71828 Power Management IC. |
|---|
| 529 | + |
|---|
| 530 | + This driver can also be built as a module. If so, the module |
|---|
| 531 | + will be called rtc-bd70528. |
|---|
| 516 | 532 | |
|---|
| 517 | 533 | config RTC_DRV_BQ32K |
|---|
| 518 | 534 | tristate "TI BQ32000" |
|---|
| .. | .. |
|---|
| 569 | 585 | |
|---|
| 570 | 586 | config RTC_DRV_TPS65910 |
|---|
| 571 | 587 | tristate "TI TPS65910 RTC driver" |
|---|
| 572 | | - depends on RTC_CLASS && MFD_TPS65910 |
|---|
| 588 | + depends on MFD_TPS65910 |
|---|
| 573 | 589 | help |
|---|
| 574 | 590 | If you say yes here you get support for the RTC on the |
|---|
| 575 | 591 | TPS65910 chips. |
|---|
| .. | .. |
|---|
| 595 | 611 | This driver can also be built as a module. If so, the module |
|---|
| 596 | 612 | will be called rtc-rc5t583. |
|---|
| 597 | 613 | |
|---|
| 614 | +config RTC_DRV_RC5T619 |
|---|
| 615 | + tristate "RICOH RC5T619 RTC driver" |
|---|
| 616 | + depends on MFD_RN5T618 |
|---|
| 617 | + help |
|---|
| 618 | + If you say yes here you get support for the RTC on the |
|---|
| 619 | + RICOH RC5T619 chips. |
|---|
| 620 | + |
|---|
| 621 | + This driver can also be built as a module. If so, the module |
|---|
| 622 | + will be called rtc-rc5t619. |
|---|
| 623 | + |
|---|
| 598 | 624 | config RTC_DRV_S35390A |
|---|
| 599 | 625 | tristate "Seiko Instruments S-35390A" |
|---|
| 600 | 626 | select BITREVERSE |
|---|
| .. | .. |
|---|
| 618 | 644 | |
|---|
| 619 | 645 | config RTC_DRV_RX8010 |
|---|
| 620 | 646 | tristate "Epson RX8010SJ" |
|---|
| 621 | | - depends on I2C |
|---|
| 647 | + select REGMAP_I2C |
|---|
| 622 | 648 | help |
|---|
| 623 | 649 | If you say yes here you get support for the Epson RX8010SJ RTC |
|---|
| 624 | 650 | chip. |
|---|
| .. | .. |
|---|
| 627 | 653 | will be called rtc-rx8010. |
|---|
| 628 | 654 | |
|---|
| 629 | 655 | config RTC_DRV_RX8581 |
|---|
| 630 | | - tristate "Epson RX-8581" |
|---|
| 656 | + tristate "Epson RX-8571/RX-8581" |
|---|
| 657 | + select REGMAP_I2C |
|---|
| 631 | 658 | help |
|---|
| 632 | | - If you say yes here you will get support for the Epson RX-8581. |
|---|
| 659 | + If you say yes here you will get support for the Epson RX-8571/ |
|---|
| 660 | + RX-8581. |
|---|
| 633 | 661 | |
|---|
| 634 | 662 | This driver can also be built as a module. If so the module |
|---|
| 635 | 663 | will be called rtc-rx8581. |
|---|
| .. | .. |
|---|
| 652 | 680 | This driver can also be built as a module. If so, the module |
|---|
| 653 | 681 | will be called rtc-em3027. |
|---|
| 654 | 682 | |
|---|
| 683 | +config RTC_DRV_RV3028 |
|---|
| 684 | + tristate "Micro Crystal RV3028" |
|---|
| 685 | + select REGMAP_I2C |
|---|
| 686 | + help |
|---|
| 687 | + If you say yes here you get support for the Micro Crystal |
|---|
| 688 | + RV3028. |
|---|
| 689 | + |
|---|
| 690 | + This driver can also be built as a module. If so, the module |
|---|
| 691 | + will be called rtc-rv3028. |
|---|
| 692 | + |
|---|
| 693 | +config RTC_DRV_RV3032 |
|---|
| 694 | + tristate "Micro Crystal RV3032" |
|---|
| 695 | + select REGMAP_I2C |
|---|
| 696 | + help |
|---|
| 697 | + If you say yes here you get support for the Micro Crystal |
|---|
| 698 | + RV3032. |
|---|
| 699 | + |
|---|
| 700 | + This driver can also be built as a module. If so, the module |
|---|
| 701 | + will be called rtc-rv3032. |
|---|
| 702 | + |
|---|
| 655 | 703 | config RTC_DRV_RV8803 |
|---|
| 656 | 704 | tristate "Micro Crystal RV8803, Epson RX8900" |
|---|
| 657 | 705 | help |
|---|
| .. | .. |
|---|
| 672 | 720 | |
|---|
| 673 | 721 | This driver can also be built as a module. If so, the module |
|---|
| 674 | 722 | will be called rtc-s5m. |
|---|
| 723 | + |
|---|
| 724 | +config RTC_DRV_SD3078 |
|---|
| 725 | + tristate "ZXW Shenzhen whwave SD3078" |
|---|
| 726 | + select REGMAP_I2C |
|---|
| 727 | + help |
|---|
| 728 | + If you say yes here you get support for the ZXW Shenzhen whwave |
|---|
| 729 | + SD3078 RTC chips. |
|---|
| 730 | + |
|---|
| 731 | + This driver can also be built as a module. If so, the module |
|---|
| 732 | + will be called rtc-sd3078 |
|---|
| 675 | 733 | |
|---|
| 676 | 734 | endif # I2C |
|---|
| 677 | 735 | |
|---|
| .. | .. |
|---|
| 810 | 868 | |
|---|
| 811 | 869 | config RTC_DRV_PCF2123 |
|---|
| 812 | 870 | tristate "NXP PCF2123" |
|---|
| 871 | + select REGMAP_SPI |
|---|
| 813 | 872 | help |
|---|
| 814 | 873 | If you say yes here you get support for the NXP PCF2123 |
|---|
| 815 | 874 | RTC chip. |
|---|
| .. | .. |
|---|
| 836 | 895 | default m if I2C=m |
|---|
| 837 | 896 | default y if I2C=y |
|---|
| 838 | 897 | default y if SPI_MASTER=y |
|---|
| 839 | | - select REGMAP_I2C if I2C |
|---|
| 840 | | - select REGMAP_SPI if SPI_MASTER |
|---|
| 841 | 898 | |
|---|
| 842 | 899 | comment "SPI and I2C RTC drivers" |
|---|
| 843 | 900 | |
|---|
| 844 | 901 | config RTC_DRV_DS3232 |
|---|
| 845 | 902 | tristate "Dallas/Maxim DS3232/DS3234" |
|---|
| 846 | 903 | depends on RTC_I2C_AND_SPI |
|---|
| 904 | + select REGMAP_I2C if I2C |
|---|
| 905 | + select REGMAP_SPI if SPI_MASTER |
|---|
| 847 | 906 | help |
|---|
| 848 | 907 | If you say yes here you get support for Dallas Semiconductor |
|---|
| 849 | 908 | DS3232 and DS3234 real-time clock chips. If an interrupt is associated |
|---|
| .. | .. |
|---|
| 863 | 922 | config RTC_DRV_PCF2127 |
|---|
| 864 | 923 | tristate "NXP PCF2127" |
|---|
| 865 | 924 | depends on RTC_I2C_AND_SPI |
|---|
| 925 | + select REGMAP_I2C if I2C |
|---|
| 926 | + select REGMAP_SPI if SPI_MASTER |
|---|
| 927 | + select WATCHDOG_CORE if WATCHDOG |
|---|
| 866 | 928 | help |
|---|
| 867 | 929 | If you say yes here you get support for the NXP PCF2127/29 RTC |
|---|
| 868 | | - chips. |
|---|
| 930 | + chips with integrated quartz crystal for industrial applications. |
|---|
| 931 | + Both chips also have watchdog timer and tamper switch detection |
|---|
| 932 | + features. |
|---|
| 933 | + |
|---|
| 934 | + PCF2127 has an additional feature of 512 bytes battery backed |
|---|
| 935 | + memory that's accessible using nvmem interface. |
|---|
| 869 | 936 | |
|---|
| 870 | 937 | This driver can also be built as a module. If so, the module |
|---|
| 871 | 938 | will be called rtc-pcf2127. |
|---|
| .. | .. |
|---|
| 873 | 940 | config RTC_DRV_RV3029C2 |
|---|
| 874 | 941 | tristate "Micro Crystal RV3029/3049" |
|---|
| 875 | 942 | depends on RTC_I2C_AND_SPI |
|---|
| 943 | + select REGMAP_I2C if I2C |
|---|
| 944 | + select REGMAP_SPI if SPI_MASTER |
|---|
| 876 | 945 | help |
|---|
| 877 | 946 | If you say yes here you get support for the Micro Crystal |
|---|
| 878 | 947 | RV3029 and RV3049 RTC chips. |
|---|
| .. | .. |
|---|
| 1034 | 1103 | This chip features 8kb of extended NV-SRAM. |
|---|
| 1035 | 1104 | |
|---|
| 1036 | 1105 | endchoice |
|---|
| 1037 | | - |
|---|
| 1038 | | -config RTC_DS1685_PROC_REGS |
|---|
| 1039 | | - bool "Display register values in /proc" |
|---|
| 1040 | | - depends on RTC_DRV_DS1685_FAMILY && PROC_FS |
|---|
| 1041 | | - help |
|---|
| 1042 | | - Enable this to display a readout of all of the RTC registers in |
|---|
| 1043 | | - /proc/drivers/rtc. Keep in mind that this can potentially lead |
|---|
| 1044 | | - to lost interrupts, as reading Control Register C will clear |
|---|
| 1045 | | - all pending IRQ flags. |
|---|
| 1046 | | - |
|---|
| 1047 | | - Unless you are debugging this driver, choose N. |
|---|
| 1048 | 1106 | |
|---|
| 1049 | 1107 | config RTC_DRV_DS1742 |
|---|
| 1050 | 1108 | tristate "Maxim/Dallas DS1742/1743" |
|---|
| .. | .. |
|---|
| 1247 | 1305 | Select this to enable the ST-Ericsson AB8500 power management IC RTC |
|---|
| 1248 | 1306 | support. This chip contains a battery- and capacitor-backed RTC. |
|---|
| 1249 | 1307 | |
|---|
| 1250 | | -config RTC_DRV_NUC900 |
|---|
| 1251 | | - tristate "NUC910/NUC920 RTC driver" |
|---|
| 1252 | | - depends on ARCH_W90X900 || COMPILE_TEST |
|---|
| 1253 | | - help |
|---|
| 1254 | | - If you say yes here you get support for the RTC subsystem of the |
|---|
| 1255 | | - NUC910/NUC920 used in embedded systems. |
|---|
| 1256 | | - |
|---|
| 1257 | 1308 | config RTC_DRV_OPAL |
|---|
| 1258 | 1309 | tristate "IBM OPAL RTC driver" |
|---|
| 1259 | 1310 | depends on PPC_POWERNV |
|---|
| .. | .. |
|---|
| 1267 | 1318 | |
|---|
| 1268 | 1319 | config RTC_DRV_ZYNQMP |
|---|
| 1269 | 1320 | tristate "Xilinx Zynq Ultrascale+ MPSoC RTC" |
|---|
| 1270 | | - depends on OF |
|---|
| 1321 | + depends on OF && HAS_IOMEM |
|---|
| 1271 | 1322 | help |
|---|
| 1272 | 1323 | If you say yes here you get support for the RTC controller found on |
|---|
| 1273 | 1324 | Xilinx Zynq Ultrascale+ MPSoC. |
|---|
| 1274 | 1325 | |
|---|
| 1275 | 1326 | config RTC_DRV_CROS_EC |
|---|
| 1276 | 1327 | tristate "Chrome OS EC RTC driver" |
|---|
| 1277 | | - depends on MFD_CROS_EC |
|---|
| 1328 | + depends on CROS_EC |
|---|
| 1278 | 1329 | help |
|---|
| 1279 | 1330 | If you say yes here you will get support for the |
|---|
| 1280 | 1331 | Chrome OS Embedded Controller's RTC. |
|---|
| .. | .. |
|---|
| 1322 | 1373 | |
|---|
| 1323 | 1374 | This driver can also be built as a module, if so, the module |
|---|
| 1324 | 1375 | will be called "rtc-imxdi". |
|---|
| 1376 | + |
|---|
| 1377 | +config RTC_DRV_FSL_FTM_ALARM |
|---|
| 1378 | + tristate "Freescale FlexTimer alarm timer" |
|---|
| 1379 | + depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST |
|---|
| 1380 | + help |
|---|
| 1381 | + For the FlexTimer in LS1012A, LS1021A, LS1028A, LS1043A, LS1046A, |
|---|
| 1382 | + LS1088A, LS208xA, we can use FTM as the wakeup source. |
|---|
| 1383 | + |
|---|
| 1384 | + Say y here to enable FTM alarm support. The FTM alarm provides |
|---|
| 1385 | + alarm functions for wakeup system from deep sleep. |
|---|
| 1386 | + |
|---|
| 1387 | + This driver can also be built as a module, if so, the module |
|---|
| 1388 | + will be called "rtc-fsl-ftm-alarm". |
|---|
| 1389 | + |
|---|
| 1390 | +config RTC_DRV_MESON |
|---|
| 1391 | + tristate "Amlogic Meson RTC" |
|---|
| 1392 | + depends on (ARM && ARCH_MESON) || COMPILE_TEST |
|---|
| 1393 | + select REGMAP_MMIO |
|---|
| 1394 | + help |
|---|
| 1395 | + Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b |
|---|
| 1396 | + and Meson8m2 SoCs. |
|---|
| 1397 | + |
|---|
| 1398 | + This driver can also be built as a module, if so, the module |
|---|
| 1399 | + will be called "rtc-meson". |
|---|
| 1400 | + |
|---|
| 1401 | +config RTC_DRV_MESON_VRTC |
|---|
| 1402 | + tristate "Amlogic Meson Virtual RTC" |
|---|
| 1403 | + depends on ARCH_MESON || COMPILE_TEST |
|---|
| 1404 | + default m if ARCH_MESON |
|---|
| 1405 | + help |
|---|
| 1406 | + If you say yes here you will get support for the |
|---|
| 1407 | + Virtual RTC of Amlogic SoCs. |
|---|
| 1408 | + |
|---|
| 1409 | + This driver can also be built as a module. If so, the module |
|---|
| 1410 | + will be called rtc-meson-vrtc. |
|---|
| 1325 | 1411 | |
|---|
| 1326 | 1412 | config RTC_DRV_OMAP |
|---|
| 1327 | 1413 | tristate "TI OMAP Real Time Clock" |
|---|
| .. | .. |
|---|
| 1422 | 1508 | config RTC_DRV_AT91RM9200 |
|---|
| 1423 | 1509 | tristate "AT91RM9200 or some AT91SAM9 RTC" |
|---|
| 1424 | 1510 | depends on ARCH_AT91 || COMPILE_TEST |
|---|
| 1511 | + depends on OF |
|---|
| 1425 | 1512 | help |
|---|
| 1426 | 1513 | Driver for the internal RTC (Realtime Clock) module found on |
|---|
| 1427 | 1514 | Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips |
|---|
| .. | .. |
|---|
| 1430 | 1517 | config RTC_DRV_AT91SAM9 |
|---|
| 1431 | 1518 | tristate "AT91SAM9 RTT as RTC" |
|---|
| 1432 | 1519 | depends on ARCH_AT91 || COMPILE_TEST |
|---|
| 1433 | | - depends on HAS_IOMEM |
|---|
| 1520 | + depends on OF && HAS_IOMEM |
|---|
| 1434 | 1521 | select MFD_SYSCON |
|---|
| 1435 | 1522 | help |
|---|
| 1436 | 1523 | Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which |
|---|
| .. | .. |
|---|
| 1462 | 1549 | tristate "Generic RTC support" |
|---|
| 1463 | 1550 | # Please consider writing a new RTC driver instead of using the generic |
|---|
| 1464 | 1551 | # RTC abstraction |
|---|
| 1465 | | - depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST |
|---|
| 1552 | + depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST |
|---|
| 1466 | 1553 | help |
|---|
| 1467 | 1554 | Say Y or M here to enable RTC support on systems using the generic |
|---|
| 1468 | 1555 | RTC abstraction. If you do not know what you are doing, you should |
|---|
| .. | .. |
|---|
| 1473 | 1560 | depends on ARCH_PXA |
|---|
| 1474 | 1561 | select RTC_DRV_SA1100 |
|---|
| 1475 | 1562 | help |
|---|
| 1476 | | - If you say Y here you will get access to the real time clock |
|---|
| 1477 | | - built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs |
|---|
| 1478 | | - consisting of an SA1100 compatible RTC and the extended PXA RTC. |
|---|
| 1563 | + If you say Y here you will get access to the real time clock |
|---|
| 1564 | + built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs |
|---|
| 1565 | + consisting of an SA1100 compatible RTC and the extended PXA RTC. |
|---|
| 1479 | 1566 | |
|---|
| 1480 | 1567 | This RTC driver uses PXA RTC registers available since pxa27x |
|---|
| 1481 | 1568 | series (RDxR, RYxR) instead of legacy RCNR, RTAR. |
|---|
| .. | .. |
|---|
| 1546 | 1633 | This driver can also be built as a module. If so, the module |
|---|
| 1547 | 1634 | will be called armada38x-rtc. |
|---|
| 1548 | 1635 | |
|---|
| 1636 | +config RTC_DRV_CADENCE |
|---|
| 1637 | + tristate "Cadence RTC driver" |
|---|
| 1638 | + depends on OF && HAS_IOMEM |
|---|
| 1639 | + help |
|---|
| 1640 | + If you say Y here you will get access to Cadence RTC IP |
|---|
| 1641 | + found on certain SOCs. |
|---|
| 1642 | + |
|---|
| 1643 | + To compile this driver as a module, choose M here: the |
|---|
| 1644 | + module will be called rtc-cadence. |
|---|
| 1645 | + |
|---|
| 1549 | 1646 | config RTC_DRV_FTRTC010 |
|---|
| 1550 | 1647 | tristate "Faraday Technology FTRTC010 RTC" |
|---|
| 1551 | 1648 | depends on HAS_IOMEM |
|---|
| .. | .. |
|---|
| 1615 | 1712 | |
|---|
| 1616 | 1713 | config RTC_DRV_JZ4740 |
|---|
| 1617 | 1714 | tristate "Ingenic JZ4740 SoC" |
|---|
| 1618 | | - depends on MACH_INGENIC || COMPILE_TEST |
|---|
| 1715 | + depends on MIPS || COMPILE_TEST |
|---|
| 1716 | + depends on OF |
|---|
| 1619 | 1717 | help |
|---|
| 1620 | 1718 | If you say yes here you get support for the Ingenic JZ47xx SoCs RTC |
|---|
| 1621 | 1719 | controllers. |
|---|
| .. | .. |
|---|
| 1664 | 1762 | This drive can also be built as a module. If so, the module |
|---|
| 1665 | 1763 | will be called rtc-tegra. |
|---|
| 1666 | 1764 | |
|---|
| 1667 | | -config RTC_DRV_PUV3 |
|---|
| 1668 | | - tristate "PKUnity v3 RTC support" |
|---|
| 1669 | | - depends on ARCH_PUV3 |
|---|
| 1670 | | - help |
|---|
| 1671 | | - This enables support for the RTC in the PKUnity-v3 SoCs. |
|---|
| 1672 | | - |
|---|
| 1673 | | - This drive can also be built as a module. If so, the module |
|---|
| 1674 | | - will be called rtc-puv3. |
|---|
| 1675 | | - |
|---|
| 1676 | 1765 | config RTC_DRV_LOONGSON1 |
|---|
| 1677 | 1766 | tristate "loongson1 RTC support" |
|---|
| 1678 | 1767 | depends on MACH_LOONGSON32 |
|---|
| .. | .. |
|---|
| 1706 | 1795 | config RTC_DRV_SNVS |
|---|
| 1707 | 1796 | tristate "Freescale SNVS RTC support" |
|---|
| 1708 | 1797 | select REGMAP_MMIO |
|---|
| 1798 | + depends on ARCH_MXC || COMPILE_TEST |
|---|
| 1709 | 1799 | depends on HAS_IOMEM |
|---|
| 1710 | 1800 | depends on OF |
|---|
| 1711 | 1801 | help |
|---|
| .. | .. |
|---|
| 1714 | 1804 | |
|---|
| 1715 | 1805 | This driver can also be built as a module, if so, the module |
|---|
| 1716 | 1806 | will be called "rtc-snvs". |
|---|
| 1807 | + |
|---|
| 1808 | +config RTC_DRV_IMX_SC |
|---|
| 1809 | + depends on IMX_SCU |
|---|
| 1810 | + depends on HAVE_ARM_SMCCC |
|---|
| 1811 | + tristate "NXP i.MX System Controller RTC support" |
|---|
| 1812 | + help |
|---|
| 1813 | + If you say yes here you get support for the NXP i.MX System |
|---|
| 1814 | + Controller RTC module. |
|---|
| 1717 | 1815 | |
|---|
| 1718 | 1816 | config RTC_DRV_SIRFSOC |
|---|
| 1719 | 1817 | tristate "SiRFSOC RTC" |
|---|
| .. | .. |
|---|
| 1742 | 1840 | |
|---|
| 1743 | 1841 | This driver can also be built as a module. If so, the module |
|---|
| 1744 | 1842 | will be called rtc-moxart |
|---|
| 1843 | + |
|---|
| 1844 | +config RTC_DRV_MT2712 |
|---|
| 1845 | + tristate "MediaTek MT2712 SoC based RTC" |
|---|
| 1846 | + depends on ARCH_MEDIATEK || COMPILE_TEST |
|---|
| 1847 | + help |
|---|
| 1848 | + This enables support for the real time clock built in the MediaTek |
|---|
| 1849 | + SoCs for MT2712. |
|---|
| 1850 | + |
|---|
| 1851 | + This drive can also be built as a module. If so, the module |
|---|
| 1852 | + will be called rtc-mt2712. |
|---|
| 1745 | 1853 | |
|---|
| 1746 | 1854 | config RTC_DRV_MT6397 |
|---|
| 1747 | 1855 | tristate "MediaTek PMIC based RTC" |
|---|
| .. | .. |
|---|
| 1821 | 1929 | If you say yes here, you get support for the RTD1295 SoC |
|---|
| 1822 | 1930 | Real Time Clock. |
|---|
| 1823 | 1931 | |
|---|
| 1932 | +config RTC_DRV_ASPEED |
|---|
| 1933 | + tristate "ASPEED RTC" |
|---|
| 1934 | + depends on OF |
|---|
| 1935 | + depends on ARCH_ASPEED || COMPILE_TEST |
|---|
| 1936 | + help |
|---|
| 1937 | + If you say yes here you get support for the ASPEED BMC SoC real time |
|---|
| 1938 | + clocks. |
|---|
| 1939 | + |
|---|
| 1940 | + This driver can also be built as a module, if so, the module |
|---|
| 1941 | + will be called "rtc-aspeed". |
|---|
| 1942 | + |
|---|
| 1824 | 1943 | comment "HID Sensor RTC drivers" |
|---|
| 1825 | 1944 | |
|---|
| 1826 | 1945 | config RTC_DRV_HID_SENSOR_TIME |
|---|
| 1827 | 1946 | tristate "HID Sensor Time" |
|---|
| 1828 | 1947 | depends on USB_HID |
|---|
| 1829 | | - select IIO |
|---|
| 1830 | | - select HID_SENSOR_HUB |
|---|
| 1948 | + depends on HID_SENSOR_HUB && IIO |
|---|
| 1831 | 1949 | select HID_SENSOR_IIO_COMMON |
|---|
| 1832 | 1950 | help |
|---|
| 1833 | 1951 | Say yes here to build support for the HID Sensors of type Time. |
|---|
| .. | .. |
|---|
| 1838 | 1956 | |
|---|
| 1839 | 1957 | config RTC_DRV_GOLDFISH |
|---|
| 1840 | 1958 | tristate "Goldfish Real Time Clock" |
|---|
| 1841 | | - depends on MIPS && (GOLDFISH || COMPILE_TEST) |
|---|
| 1959 | + depends on OF && HAS_IOMEM |
|---|
| 1960 | + depends on GOLDFISH || COMPILE_TEST |
|---|
| 1842 | 1961 | help |
|---|
| 1843 | 1962 | Say yes to enable RTC driver for the Goldfish based virtual platform. |
|---|
| 1844 | 1963 | |
|---|
| 1845 | 1964 | Goldfish is a code name for the virtual platform developed by Google |
|---|
| 1846 | 1965 | for Android emulation. |
|---|
| 1847 | 1966 | |
|---|
| 1967 | +config RTC_DRV_WILCO_EC |
|---|
| 1968 | + tristate "Wilco EC RTC" |
|---|
| 1969 | + depends on WILCO_EC |
|---|
| 1970 | + default m |
|---|
| 1971 | + help |
|---|
| 1972 | + If you say yes here, you get read/write support for the Real Time |
|---|
| 1973 | + Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook) |
|---|
| 1974 | + |
|---|
| 1975 | + This can also be built as a module. If so, the module will |
|---|
| 1976 | + be named "rtc_wilco_ec". |
|---|
| 1977 | + |
|---|
| 1848 | 1978 | endif # RTC_CLASS |
|---|