Lines Matching +full:system +full:- +full:on +full:- +full:module
1 # SPDX-License-Identifier: GPL-2.0-only
16 depends on !S390
20 be allowed to plug one or more RTCs to your system. You will
26 bool "Set system time from RTC on startup and resume"
29 If you say yes here, the system time (wall clock) will be set using
34 string "RTC used to set the system time"
35 depends on RTC_HCTOSYS
38 The RTC device that will be used to (re)initialize the system
39 clock, usually rtc0. Initialization is done when the system
44 This clock should be battery-backed, so that it reads the correct
45 time when the system boots from a power-off state. Otherwise, your
46 system will need an external clock source (like an NTP server).
49 be useful to reinitialize system time when resuming from system
51 during all this system's supported sleep states.
54 bool "Set the RTC time based on NTP synchronization"
57 If you say yes here, the system time (wall clock) will be stored
63 depends on RTC_SYSTOHC
80 depends on KUNIT
93 backed) storage present on RTCs.
99 depends on SYSFS
109 depends on PROC_FS
112 Say yes here if you want to use your system clock RTC through
115 If there is no RTC for the system clock, then the first RTC(rtc0)
136 bool "RTC UIE emulation on dev interface"
137 depends on RTC_INTF_DEV
141 once-per-second update interrupts, used for synchronization.
153 the time from the system clock.
155 on the RTC subsystem. Please read the source code
158 This driver can also be built as a module. If so, the module
159 will be called rtc-test.
167 depends on MFD_88PM860X
172 This driver can also be built as a module. If so, the module
173 will be called rtc-88pm860x.
177 depends on MFD_88PM800
182 This driver can also be built as a module. If so, the module
183 will be called rtc-88pm80x.
187 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
190 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
192 This driver can also be built as a module. If so, the module
193 will be called rtc-ab-b5ze-s3.
197 tristate "Abracon AB-RTCMC-32.768kHz-EOZ9"
200 AB-RTCMC-32.768kHz-EOA9 I2C RTC chip.
202 This driver can also be built as a module. If so, the module
203 will be called rtc-ab-e0z9.
210 families of ultra-low-power battery- and capacitor-backed real-time
213 This driver can also be built as a module. If so, the module
214 will be called rtc-abx80x.
217 tristate "X-Powers AC100"
218 depends on MFD_AC100
220 If you say yes here you get support for the real-time clock found
221 in X-Powers AC100 family peripheral ICs.
223 This driver can also be built as a module. If so, the module
224 will be called rtc-ac100.
227 tristate "Broadcom STB wake-timer"
228 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
231 If you say yes here you get support for the wake-timer found on
234 This driver can also be built as a module. If so, the module will
235 be called rtc-brcmstb-waketimer.
239 depends on MFD_AS3722
244 This driver can also be built as a module. If so, the module
245 will be called rtc-as3722.
248 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"
255 ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.
259 The first seven registers on these chips hold an RTC, and other
264 This driver can also be built as a module. If so, the module
265 will be called rtc-ds1307.
268 bool "Century bit support for rtc-ds1307"
269 depends on RTC_DRV_DS1307
285 DS1374 real-time clock chips. If an interrupt is associated
288 This driver can also be built as a module. If so, the module
289 will be called rtc-ds1374.
293 depends on RTC_DRV_DS1374 && WATCHDOG
298 real-time clock chips.
306 This driver can also be built as a module. If so, the module
307 will be called rtc-ds1672.
311 depends on OF
317 This driver can also be built as a module. If so, the module
318 will be called rtc-hym8563.
322 depends on MFD_LP8788
332 This driver can also be built as a module. If so, the module
333 will be called rtc-max6900.
337 depends on MFD_MAX8907 || COMPILE_TEST
343 This driver can also be built as a module. If so, the module
344 will be called rtc-max8907.
348 depends on MFD_MAX8925
353 This driver can also be built as a module. If so, the module
354 will be called rtc-max8925.
358 depends on MFD_MAX8998
363 This driver can also be built as a module. If so, the module
364 will be called rtc-max8998.
368 depends on MFD_MAX8997
373 This driver can also be built as a module. If so, the module
374 will be called rtc-max8997.
378 depends on MFD_MAX77686 || MFD_MAX77620 || MFD_MAX77714 || COMPILE_TEST
383 This driver can also be built as a module. If so, the module
384 will be called rtc-max77686.
388 depends on OF
393 This driver can also be built as a module, if so, the module will be
394 called "rtc-nct3018y".
398 depends on MFD_RK8XX
403 This driver can also be built as a module. If so, the module
404 will be called rk808-rtc.
412 This driver can also be built as a module. If so, the module
413 will be called rtc-rs5c372.
421 This driver can also be built as a module. If so, the module
422 will be called rtc-isl1208.
431 This driver can also be built as a module. If so, the module
432 will be called rtc-isl12022.
436 depends on OF
441 This driver can also be built as a module. If so, the module
442 will be called rtc-isl12026.
450 This driver can also be built as a module. If so, the module
451 will be called rtc-x1205.
460 This driver can also be built as a module. If so, the module
461 will be called rtc-pcf8523.
469 This driver can also be built as a module. If so, the module
470 will be called rtc-pcf85063.
478 This driver can also be built as a module. If so, the module
479 will be called rtc-pcf85363.
481 The nvmem interface will be named pcf85363-#, where # is the
482 zero-based instance number.
491 This driver can also be built as a module. If so, the module
492 will be called rtc-pcf8563.
498 RTC chip found on Acorn RiscPCs. This driver supports the
500 the RTC's SRAM. It will work on other platforms with the same
503 This driver can also be built as a module. If so, the module
504 will be called rtc-pcf8583.
514 This driver can also be built as a module. If so, the module
515 will be called rtc-m41t80.
519 depends on RTC_DRV_M41T80
526 depends on MFD_ROHM_BD71828
529 block on ROHM BD71815 and BD71828 Power Management IC.
531 This driver can also be built as a module. If so, the module
532 will be called rtc-bd70528.
540 This driver can also be built as a module. If so, the module
541 will be called rtc-bq32k.
545 depends on MENELAUS
547 If you say yes here you get support for the RTC on the
550 the Menelaus driver; it's not separate module.
554 depends on TWL4030_CORE
555 depends on OF
557 If you say yes here you get support for the RTC on the
560 This driver can also be built as a module. If so, the module
561 will be called rtc-twl.
565 depends on MFD_PALMAS
570 This driver can also be built as a module. If so, the module
571 will be called rtc-palma.
575 depends on MFD_TPS6586X
579 the TPS6586X RTC module.
583 depends on MFD_TPS65910
585 If you say yes here you get support for the RTC on the
588 This driver can also be built as a module. If so, the module
589 will be called rtc-tps65910.
593 depends on MFD_RC5T583
595 If you say yes here you get support for the RTC on the
598 This driver can also be built as a module. If so, the module
599 will be called rtc-rc5t583.
603 depends on MFD_RN5T618
605 If you say yes here you get support for the RTC on the
608 This driver can also be built as a module. If so, the module
609 will be called rtc-rc5t619.
612 tristate "Seiko Instruments S-35390A"
616 Instruments S-35390A.
618 This driver can also be built as a module. If so the module
619 will be called rtc-s35390a.
629 This driver can also be built as a module. If so the module
630 will be called rtc-fm3130.
639 This driver can also be built as a module. If so, the module
640 will be called rtc-rx8010.
643 tristate "Epson RX-8571/RX-8581"
646 If you say yes here you will get support for the Epson RX-8571/
647 RX-8581.
649 This driver can also be built as a module. If so the module
650 will be called rtc-rx8581.
653 tristate "Epson RX-8025SA/NB"
656 RX-8025SA/NB RTC chips.
658 This driver can also be built as a module. If so, the module
659 will be called rtc-rx8025.
667 This driver can also be built as a module. If so, the module
668 will be called rtc-em3027.
677 This driver can also be built as a module. If so, the module
678 will be called rtc-rv3028.
687 This driver can also be built as a module. If so, the module
688 will be called rtc-rv3032.
696 This driver can also be built as a module. If so, the module
697 will be called rtc-rv8803.
701 depends on MFD_SEC_CORE || COMPILE_TEST
708 This driver can also be built as a module. If so, the module
709 will be called rtc-s5m.
718 This driver can also be built as a module. If so, the module
719 will be called rtc-sd3078
733 This driver can also be built as a module. If so, the module
734 will be called rtc-m41t93.
742 This driver can also be built as a module. If so, the module
743 will be called rtc-m41t94.
747 depends on SPI
751 This driver can also be built as a module. If so, the module
752 will be called rtc-ds1302.
761 This driver can also be built as a module. If so, the module
762 will be called rtc-ds1305.
772 This driver can also be built as a module. If so, the module
773 will be called rtc-ds1343.
785 This driver can also be built as a module. If so, the module
786 will be called rtc-ds1347.
797 This driver can also be built as a module. If so, the module
798 will be called rtc-ds1390.
809 This driver can also be built as a module. If so, the module
810 will be called rtc-max6916.
813 tristate "Epson RTC-9701JE"
816 Epson RTC-9701JE SPI RTC chip.
818 This driver can also be built as a module. If so, the module
819 will be called rtc-r9701.
822 tristate "Epson RX-4581"
824 If you say yes here you will get support for the Epson RX-4581.
826 This driver can also be built as a module. If so the module
827 will be called rtc-rx4581.
835 This driver can also be built as a module. If so, the module
836 will be called rtc-rs5c348.
844 This driver can also be built as a module. If so, the module
845 will be called rtc-max6902.
854 This driver can also be built as a module. If so, the module
855 will be called rtc-pcf2123.
862 This driver can also be built as a module. If so the module
863 will be called rtc-mcp795.
881 depends on RTC_I2C_AND_SPI
886 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
889 This driver can also be built as a module. If so, the module
890 will be called rtc-ds3232.
894 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
897 Say Y here if you want to expose temperature sensor data on
898 rtc-ds3232
902 depends on RTC_I2C_AND_SPI
915 This driver can also be built as a module. If so, the module
916 will be called rtc-pcf2127.
920 depends on RTC_I2C_AND_SPI
927 This driver can also be built as a module. If so, the module
928 will be called rtc-rv3029c2.
932 depends on RTC_DRV_RV3029C2 && HWMON
933 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
936 Say Y here if you want to expose temperature sensor data on
937 rtc-rv3029.
940 tristate "Epson RX-6110"
941 depends on RTC_I2C_AND_SPI
945 If you say yes here you will get support for the Epson RX-6110.
947 This driver can also be built as a module. If so the module
948 will be called rtc-rx6110.
957 tristate "PC-style 'CMOS'"
958 depends on X86 || ARM || PPC || MIPS || SPARC64
959 depends on HAS_IOPORT || MACH_DECSTATION
964 found in every PC or ACPI-based system, and some other boards.
967 or LPC bus chips, and so on.
969 Your system will need to define the platform device used by
974 This driver can also be built as a module. If so, the module
975 will be called rtc-cmos.
978 bool "Alpha PC-style CMOS"
979 depends on ALPHA
980 depends on HAS_IOPORT
984 Direct support for the real-time clock found on every Alpha
985 system, specifically MC146818 compatibles. If in doubt, say Y.
989 depends on SNI_RM
995 depends on HAS_IOMEM
1001 depends on HAS_IOMEM
1006 This driver can also be built as a module. If so, the module
1007 will be called rtc-ds1511.
1011 depends on HAS_IOMEM
1016 This driver can also be built as a module. If so, the module
1017 will be called rtc-ds1553.
1021 depends on HAS_IOMEM
1028 This driver can also be built as a module. If so, the module
1029 will be called rtc-ds1685.
1033 depends on RTC_DRV_DS1685_FAMILY
1043 systems, as well as EPPC-405-UC modules by electronic system design
1054 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
1066 This chip features 2kb of extended NV-SRAM. It may possibly be
1075 This chip features 4kb of extended NV-SRAM.
1083 This chip features 8kb of extended NV-SRAM.
1089 depends on HAS_IOMEM
1094 This driver can also be built as a module. If so, the module
1095 will be called rtc-ds1742.
1103 This driver can also be built as a module. If so, the module
1104 will be called rtc-ds2404.
1108 depends on PMIC_DA9052
1111 DA9052-BC and DA9053-AA/Bx PMICs.
1115 depends on MFD_DA9055
1120 This driver can also be built as a module. If so, the module
1121 will be called rtc-da9055
1125 depends on MFD_DA9063 || MFD_DA9062
1130 This driver can also be built as a module. If so, the module
1131 will be called "rtc-da9063".
1135 depends on EFI && !X86
1140 This driver can also be built as a module. If so, the module
1141 will be called rtc-efi.
1145 depends on HAS_IOMEM
1150 This driver can also be built as a module. If so, the module
1151 will be called rtc-stk17ta8.
1155 depends on HAS_IOMEM
1160 This driver can also be built as a module. If so, the module
1161 will be called rtc-m48t86.
1165 depends on HAS_IOMEM
1170 This driver can also be built as a module, if so, the module
1171 will be called "rtc-m48t35".
1175 depends on HAS_IOMEM
1183 This driver can also be built as a module, if so, the module
1184 will be called "rtc-m48t59".
1188 depends on HAS_IOMEM
1193 This driver can also be built as a module. If so, the module
1194 will be called rtc-msm6242.
1198 depends on HAS_IOMEM && HAS_IOPORT
1199 depends on SPARC || COMPILE_TEST
1204 This driver can also be built as a module. If so, the module
1205 will be called rtc-bq4802.
1209 depends on HAS_IOMEM
1215 This driver can also be built as a module. If so, the module
1216 will be called rtc-rp5c01.
1220 depends on GAMECUBE || WII || COMPILE_TEST
1226 This driver can also be built as a module. If so, the module
1227 will be called "rtc-gamecube".
1231 depends on MFD_WM831X
1236 This driver can also be built as a module. If so, the module
1237 will be called "rtc-wm831x".
1241 depends on MFD_WM8350
1246 This driver can also be built as a module. If so, the module
1247 will be called "rtc-wm8350".
1251 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1257 This driver can also be built as a module. If so, the module
1258 will be called rtc-sc27xx.
1262 depends on PLAT_SPEAR || COMPILE_TEST
1265 If you say Y here you will get support for the RTC found on
1269 depends on MFD_PCF50633
1276 tristate "ST-Ericsson AB8500 RTC"
1277 depends on AB8500_CORE
1281 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1282 support. This chip contains a battery- and capacitor-backed RTC.
1286 depends on PPC_POWERNV
1290 driver based on OPAL interfaces.
1292 This driver can also be built as a module. If so, the module
1293 will be called rtc-opal.
1296 tristate "OP-TEE based RTC driver"
1297 depends on OPTEE
1299 Select this to get support for OP-TEE based RTC control on SoCs where
1302 This driver can also be built as a module. If so, the module
1303 will be called rtc-optee.
1307 depends on OF && HAS_IOMEM
1309 If you say yes here you get support for the RTC controller found on
1314 depends on CROS_EC
1319 This driver can also be built as a module. If so, the module
1320 will be called rtc-cros-ec.
1324 depends on MFD_NTXEC
1327 embedded controller found in certain e-book readers designed by the
1330 comment "on-CPU RTC drivers"
1334 depends on MACH_ASM9260 || COMPILE_TEST
1336 If you say yes here you get support for the RTC on the
1339 This driver can also be built as a module. If so, the module
1340 will be called rtc-asm9260.
1344 depends on ARCH_DIGICOLOR || COMPILE_TEST
1346 If you say yes here you get support for the RTC on Conexant
1349 This driver can also be built as a module. If so, the module
1350 will be called rtc-digicolor.
1354 depends on ARCH_MXC
1355 depends on OF
1359 This driver can also be built as a module, if so, the module
1360 will be called "rtc-imxdi".
1364 depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST
1370 alarm functions for wakeup system from deep sleep.
1372 This driver can also be built as a module, if so, the module
1373 will be called "rtc-fsl-ftm-alarm".
1377 depends on (ARM && ARCH_MESON) || COMPILE_TEST
1380 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1383 This driver can also be built as a module, if so, the module
1384 will be called "rtc-meson".
1388 depends on ARCH_MESON || COMPILE_TEST
1394 This driver can also be built as a module. If so, the module
1395 will be called rtc-meson-vrtc.
1399 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1400 depends on OF
1401 depends on PINCTRL
1404 Say "yes" here to support the on chip real time clock
1405 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1407 This driver can also be built as a module, if so, module
1408 will be called rtc-omap.
1412 depends on ARCH_EXYNOS || ARCH_S3C64XX || ARCH_S5PV210 || \
1420 This driver can also be build as a module. If so, the module
1421 will be called rtc-s3c.
1425 depends on ARCH_EP93XX || COMPILE_TEST
1430 This driver can also be built as a module. If so, the module
1431 will be called rtc-ep93xx.
1435 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1440 To compile this driver as a module, choose M here: the
1441 module will be called rtc-sa1100.
1444 tristate "SuperH On-Chip RTC"
1445 depends on SUPERH || ARCH_RENESAS
1447 Say Y here to enable support for the on-chip RTC found in
1450 To compile this driver as a module, choose M here: the
1451 module will be called rtc-sh.
1455 depends on SOC_SP7021
1457 Say 'yes' to get support for the real-time clock present in
1458 Sunplus SP7021 - a SoC for industrial applications. It provides
1463 This driver can also be built as a module. If so, the module
1464 will be called rtc-sunplus.
1468 depends on ARM_AMBA
1471 PrimeCell PL030 RTC found on certain ARM SOCs.
1473 To compile this driver as a module, choose M here: the
1474 module will be called rtc-pl030.
1478 depends on ARM_AMBA
1481 PrimeCell PL031 RTC found on certain ARM SOCs.
1483 To compile this driver as a module, choose M here: the
1484 module will be called rtc-pl031.
1488 depends on ARCH_AT91 || COMPILE_TEST
1489 depends on OF
1491 Driver for the internal RTC (Realtime Clock) module found on
1492 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1497 depends on ARCH_AT91 || COMPILE_TEST
1498 depends on OF && HAS_IOMEM
1506 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1512 depends on MIPS_ALCHEMY
1514 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1517 This driver can also be built as a module. If so, the module
1518 will be called rtc-au1xxx.
1522 depends on SH_LANDISK
1528 depends on ARCH_RZN1 || COMPILE_TEST
1529 depends on OF && HAS_IOMEM
1537 depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST
1539 Say Y or M here to enable RTC support on systems using the generic
1545 depends on ARCH_PXA
1557 depends on ARCH_VT8500 || COMPILE_TEST
1565 depends on SPARC64
1568 based RTC on SUN4V systems.
1573 depends on COMMON_CLK
1574 depends on ARCH_SUNXI || COMPILE_TEST
1581 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1583 If you say Y here you will get support for the RTC found on
1588 depends on SPARC64
1590 If you say Y here you will get support for the RTC found on
1595 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1597 If you say yes here you will get support for the in-chip RTC
1601 This driver can also be built as a module. If so, the module
1602 will be called rtc-mv.
1606 depends on ARCH_MVEBU || COMPILE_TEST
1607 depends on OF
1609 If you say yes here you will get support for the in-chip RTC
1612 This driver can also be built as a module. If so, the module
1613 will be called armada38x-rtc.
1617 depends on OF && HAS_IOMEM
1620 found on certain SOCs.
1622 To compile this driver as a module, choose M here: the
1623 module will be called rtc-cadence.
1627 depends on HAS_IOMEM
1631 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1633 This driver can also be built as a module. If so, the module
1634 will be called rtc-ftrtc010.
1638 depends on PPC_PS3
1640 If you say yes here you will get support for the RTC on PS3.
1642 This driver can also be built as a module. If so, the module
1643 will be called rtc-ps3.
1647 depends on ARCH_MXS || COMPILE_TEST
1653 This driver can also be built as a module. If so, the module
1654 will be called rtc-stmp3xxx.
1658 depends on EZX_PCAP
1660 If you say Y here you will get support for the RTC found on
1661 the PCAP2 ASIC used on some Motorola phones.
1664 depends on MFD_MC13XXX
1667 This enables support for the RTCs found on Freescale's PMICs
1671 tristate "Freescale MPC5121 built-in RTC"
1672 depends on PPC_MPC512x || PPC_MPC52xx
1675 built-in RTC on MPC5121 or on MPC5200.
1677 This driver can also be built as a module. If so, the module
1678 will be called rtc-mpc5121.
1682 depends on MIPS || COMPILE_TEST
1683 depends on OF && COMMON_CLK
1688 This driver can also be built as a module. If so, the module
1689 will be called rtc-jz4740.
1692 tristate "Loongson On-chip RTC"
1693 depends on MACH_LOONGSON32 || MACH_LOONGSON64 || COMPILE_TEST
1696 This is a driver for the Loongson on-chip Counter0 (Time-Of-Year
1698 It can be found on Loongson-1 series cpu, Loongson-2K series cpu
1701 This driver can also be built as a module. If so, the module
1702 will be called rtc-loongson.
1706 depends on ARCH_LPC18XX || COMPILE_TEST
1707 depends on OF && HAS_IOMEM
1709 This enables support for the NXP RTC found which can be found on
1713 the hardware RTC. This driver can also be built as a module. If
1714 so, the module will be called rtc-lpc24xx.
1717 depends on ARCH_LPC32XX || COMPILE_TEST
1722 This driver can also be built as a module. If so, the module
1723 will be called rtc-lpc32xx.
1727 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1732 To compile this driver as a module, choose M here: the
1733 module will be called rtc-pm8xxx.
1737 depends on ARCH_TEGRA || COMPILE_TEST
1740 Tegra 200 series internal RTC module.
1742 This drive can also be built as a module. If so, the module
1743 will be called rtc-tegra.
1747 depends on ARCH_MXC || COMPILE_TEST
1748 depends on HAS_IOMEM
1749 depends on OF
1752 RTC module.
1754 This driver can also be built as a module, if so, the module
1755 will be called "rtc-mxc".
1759 depends on ARCH_MXC || COMPILE_TEST
1760 depends on HAS_IOMEM
1761 depends on OF
1764 SRTC module in i.MX53 processor.
1766 This driver can also be built as a module, if so, the module
1767 will be called "rtc-mxc_v2".
1772 depends on ARCH_MXC || COMPILE_TEST
1773 depends on HAS_IOMEM
1774 depends on OF
1777 Low Power (LP) RTC module.
1779 This driver can also be built as a module, if so, the module
1780 will be called "rtc-snvs".
1785 depends on ARCH_MXC || COMPILE_TEST
1786 depends on HAS_IOMEM
1787 depends on OF
1789 If you say yes here you get support for the NXP BBNSM RTC module.
1791 This driver can also be built as a module, if so, the module
1792 will be called "rtc-bbnsm".
1795 depends on IMX_SCU
1796 depends on HAVE_ARM_SMCCC
1797 tristate "NXP i.MX System Controller RTC support"
1799 If you say yes here you get support for the NXP i.MX System
1800 Controller RTC module.
1804 depends on ARCH_STI
1805 depends on OF
1810 To compile this driver as a module, choose M here: the
1811 module will be called rtc-st-lpc.
1815 depends on ARCH_MOXART || COMPILE_TEST
1818 RTC module.
1820 This driver can also be built as a module. If so, the module
1821 will be called rtc-moxart
1825 depends on ARCH_MEDIATEK || COMPILE_TEST
1830 This drive can also be built as a module. If so, the module
1831 will be called rtc-mt2712.
1835 depends on MFD_MT6397 || COMPILE_TEST
1846 depends on ARCH_MEDIATEK || COMPILE_TEST
1851 This drive can also be built as a module. If so, the module
1852 will be called rtc-mt7622.
1855 tristate "APM X-Gene RTC"
1856 depends on HAS_IOMEM
1857 depends on ARCH_XGENE || COMPILE_TEST
1859 If you say yes here you get support for the APM X-Gene SoC real time
1862 This driver can also be built as a module, if so, the module
1863 will be called "rtc-xgene".
1867 depends on MACH_PIC32
1870 If you say yes here you get support for the PIC32 RTC module.
1872 This driver can also be built as a module. If so, the module
1873 will be called rtc-pic32
1876 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1878 depends on OF && HAS_IOMEM
1881 RTC-7301SF/DG chips.
1883 This driver can also be built as a module. If so, the module
1884 will be called rtc-r7301.
1889 depends on ARCH_STM32 || COMPILE_TEST
1891 If you say yes here you get support for the STM32 On-Chip
1894 This driver can also be built as a module, if so, the module
1895 will be called "rtc-stm32".
1898 depends on MFD_CPCAP
1901 Say y here for CPCAP rtc found on some Motorola phones
1906 depends on ARCH_REALTEK || COMPILE_TEST
1914 depends on OF
1915 depends on ARCH_ASPEED || COMPILE_TEST
1920 This driver can also be built as a module, if so, the module
1921 will be called "rtc-aspeed".
1925 depends on ARCH_K3 || COMPILE_TEST
1931 This driver can also be built as a module, if so, the module
1932 will be called "rtc-ti-k3".
1938 depends on USB_HID
1939 depends on HID_SENSOR_HUB && IIO
1945 If this driver is compiled as a module, it will be named
1946 rtc-hid-sensor-time.
1950 depends on HAS_IOMEM
1959 depends on WILCO_EC
1963 Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook)
1965 This can also be built as a module. If so, the module will
1970 depends on ARCH_MSTARV7 || COMPILE_TEST
1972 If you say yes here you get support for the Mstar MSC313e On-Chip
1975 This driver can also be built as a module, if so, the module
1976 will be called "rtc-msc313".
1979 tristate "Microchip PolarFire SoC built-in RTC"
1980 depends on ARCH_MICROCHIP_POLARFIRE
1983 built-in RTC on Polarfire SoC.
1985 This driver can also be built as a module, if so, the module
1986 will be called "rtc-mpfs".