Lines Matching +full:system +full:- +full:on +full:- +full:module
1 # SPDX-License-Identifier: GPL-2.0-only
16 depends on !S390 && !UML
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
84 backed) storage present on RTCs.
90 depends on SYSFS
100 depends on PROC_FS
103 Say yes here if you want to use your system clock RTC through
106 If there is no RTC for the system clock, then the first RTC(rtc0)
127 bool "RTC UIE emulation on dev interface"
128 depends on RTC_INTF_DEV
132 once-per-second update interrupts, used for synchronization.
144 the time from the system clock.
146 on the RTC subsystem. Please read the source code
149 This driver can also be built as a module. If so, the module
150 will be called rtc-test.
158 depends on MFD_88PM860X
163 This driver can also be built as a module. If so, the module
164 will be called rtc-88pm860x.
168 depends on MFD_88PM800
173 This driver can also be built as a module. If so, the module
174 will be called rtc-88pm80x.
178 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
181 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
183 This driver can also be built as a module. If so, the module
184 will be called rtc-ab-b5ze-s3.
188 tristate "Abracon AB-RTCMC-32.768kHz-EOZ9"
191 AB-RTCMC-32.768kHz-EOA9 I2C RTC chip.
193 This driver can also be built as a module. If so, the module
194 will be called rtc-ab-e0z9.
201 families of ultra-low-power battery- and capacitor-backed real-time
204 This driver can also be built as a module. If so, the module
205 will be called rtc-abx80x.
208 tristate "X-Powers AC100"
209 depends on MFD_AC100
211 If you say yes here you get support for the real-time clock found
212 in X-Powers AC100 family peripheral ICs.
214 This driver can also be built as a module. If so, the module
215 will be called rtc-ac100.
218 tristate "Broadcom STB wake-timer"
219 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
222 If you say yes here you get support for the wake-timer found on
225 This driver can also be built as a module. If so, the module will
226 be called rtc-brcmstb-waketimer.
230 depends on MFD_AS3722
235 This driver can also be built as a module. If so, the module
236 will be called rtc-as3722.
239 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"
246 ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.
250 The first seven registers on these chips hold an RTC, and other
255 This driver can also be built as a module. If so, the module
256 will be called rtc-ds1307.
259 bool "Century bit support for rtc-ds1307"
260 depends on RTC_DRV_DS1307
276 DS1374 real-time clock chips. If an interrupt is associated
279 This driver can also be built as a module. If so, the module
280 will be called rtc-ds1374.
284 depends on RTC_DRV_DS1374 && WATCHDOG
289 real-time clock chips.
297 This driver can also be built as a module. If so, the module
298 will be called rtc-ds1672.
302 depends on OF
308 This driver can also be built as a module. If so, the module
309 will be called rtc-hym8563.
313 depends on MFD_LP8788
323 This driver can also be built as a module. If so, the module
324 will be called rtc-max6900.
328 depends on MFD_MAX8907 || COMPILE_TEST
334 This driver can also be built as a module. If so, the module
335 will be called rtc-max8907.
339 depends on MFD_MAX8925
344 This driver can also be built as a module. If so, the module
345 will be called rtc-max8925.
349 depends on MFD_MAX8998
354 This driver can also be built as a module. If so, the module
355 will be called rtc-max8998.
359 depends on MFD_MAX8997
364 This driver can also be built as a module. If so, the module
365 will be called rtc-max8997.
369 depends on MFD_MAX77686 || MFD_MAX77620 || COMPILE_TEST
374 This driver can also be built as a module. If so, the module
375 will be called rtc-max77686.
379 depends on MFD_RK808
384 This driver can also be built as a module. If so, the module
385 will be called rk808-rtc.
393 This driver can also be built as a module. If so, the module
394 will be called rtc-rs5c372.
402 This driver can also be built as a module. If so, the module
403 will be called rtc-isl1208.
411 This driver can also be built as a module. If so, the module
412 will be called rtc-isl12022.
416 depends on OF || COMPILE_TEST
421 This driver can also be built as a module. If so, the module
422 will be called rtc-isl12026.
430 This driver can also be built as a module. If so, the module
431 will be called rtc-x1205.
439 This driver can also be built as a module. If so, the module
440 will be called rtc-pcf8523.
448 This driver can also be built as a module. If so, the module
449 will be called rtc-pcf85063.
457 This driver can also be built as a module. If so, the module
458 will be called rtc-pcf85363.
460 The nvmem interface will be named pcf85363-#, where # is the
461 zero-based instance number.
470 This driver can also be built as a module. If so, the module
471 will be called rtc-pcf8563.
477 RTC chip found on Acorn RiscPCs. This driver supports the
479 the RTC's SRAM. It will work on other platforms with the same
482 This driver can also be built as a module. If so, the module
483 will be called rtc-pcf8583.
493 This driver can also be built as a module. If so, the module
494 will be called rtc-m41t80.
498 depends on RTC_DRV_M41T80
505 depends on MFD_ROHM_BD70528 && (BD70528_WATCHDOG || !BD70528_WATCHDOG)
508 block on ROHM BD70528 and BD71828 Power Management IC.
510 This driver can also be built as a module. If so, the module
511 will be called rtc-bd70528.
519 This driver can also be built as a module. If so, the module
520 will be called rtc-bq32k.
524 depends on MFD_DM355EVM_MSP
526 Supports the RTC firmware in the MSP430 on the DM355 EVM.
530 depends on MENELAUS
532 If you say yes here you get support for the RTC on the
535 the Menelaus driver; it's not separate module.
539 depends on TWL4030_CORE
540 depends on OF
542 If you say yes here you get support for the RTC on the
545 This driver can also be built as a module. If so, the module
546 will be called rtc-twl.
550 depends on MFD_PALMAS
555 This driver can also be built as a module. If so, the module
556 will be called rtc-palma.
560 depends on MFD_TPS6586X
564 the TPS6586X RTC module.
568 depends on MFD_TPS65910
570 If you say yes here you get support for the RTC on the
573 This driver can also be built as a module. If so, the module
574 will be called rtc-tps65910.
578 depends on MFD_TPS80031
582 the TPS80031 RTC module.
586 depends on MFD_RC5T583
588 If you say yes here you get support for the RTC on the
591 This driver can also be built as a module. If so, the module
592 will be called rtc-rc5t583.
596 depends on MFD_RN5T618
598 If you say yes here you get support for the RTC on the
601 This driver can also be built as a module. If so, the module
602 will be called rtc-rc5t619.
605 tristate "Seiko Instruments S-35390A"
609 Instruments S-35390A.
611 This driver can also be built as a module. If so the module
612 will be called rtc-s35390a.
622 This driver can also be built as a module. If so the module
623 will be called rtc-fm3130.
632 This driver can also be built as a module. If so, the module
633 will be called rtc-rx8010.
636 tristate "Epson RX-8571/RX-8581"
639 If you say yes here you will get support for the Epson RX-8571/
640 RX-8581.
642 This driver can also be built as a module. If so the module
643 will be called rtc-rx8581.
646 tristate "Epson RX-8025SA/NB"
649 RX-8025SA/NB RTC chips.
651 This driver can also be built as a module. If so, the module
652 will be called rtc-rx8025.
660 This driver can also be built as a module. If so, the module
661 will be called rtc-em3027.
670 This driver can also be built as a module. If so, the module
671 will be called rtc-rv3028.
680 This driver can also be built as a module. If so, the module
681 will be called rtc-rv3032.
689 This driver can also be built as a module. If so, the module
690 will be called rtc-rv8803.
694 depends on MFD_SEC_CORE || COMPILE_TEST
701 This driver can also be built as a module. If so, the module
702 will be called rtc-s5m.
711 This driver can also be built as a module. If so, the module
712 will be called rtc-sd3078
726 This driver can also be built as a module. If so, the module
727 will be called rtc-m41t93.
735 This driver can also be built as a module. If so, the module
736 will be called rtc-m41t94.
740 depends on SPI
744 This driver can also be built as a module. If so, the module
745 will be called rtc-ds1302.
754 This driver can also be built as a module. If so, the module
755 will be called rtc-ds1305.
765 This driver can also be built as a module. If so, the module
766 will be called rtc-ds1343.
778 This driver can also be built as a module. If so, the module
779 will be called rtc-ds1347.
790 This driver can also be built as a module. If so, the module
791 will be called rtc-ds1390.
802 This driver can also be built as a module. If so, the module
803 will be called rtc-max6916.
806 tristate "Epson RTC-9701JE"
809 Epson RTC-9701JE SPI RTC chip.
811 This driver can also be built as a module. If so, the module
812 will be called rtc-r9701.
815 tristate "Epson RX-4581"
817 If you say yes here you will get support for the Epson RX-4581.
819 This driver can also be built as a module. If so the module
820 will be called rtc-rx4581.
823 tristate "Epson RX-6110"
826 If you say yes here you will get support for the Epson RX-6610.
828 This driver can also be built as a module. If so the module
829 will be called rtc-rx6110.
837 This driver can also be built as a module. If so, the module
838 will be called rtc-rs5c348.
846 This driver can also be built as a module. If so, the module
847 will be called rtc-max6902.
856 This driver can also be built as a module. If so, the module
857 will be called rtc-pcf2123.
864 This driver can also be built as a module. If so the module
865 will be called rtc-mcp795.
883 depends on RTC_I2C_AND_SPI
888 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
891 This driver can also be built as a module. If so, the module
892 will be called rtc-ds3232.
896 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
899 Say Y here if you want to expose temperature sensor data on
900 rtc-ds3232
904 depends on RTC_I2C_AND_SPI
917 This driver can also be built as a module. If so, the module
918 will be called rtc-pcf2127.
922 depends on RTC_I2C_AND_SPI
929 This driver can also be built as a module. If so, the module
930 will be called rtc-rv3029c2.
934 depends on RTC_DRV_RV3029C2 && HWMON
935 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
938 Say Y here if you want to expose temperature sensor data on
939 rtc-rv3029.
948 tristate "PC-style 'CMOS'"
949 depends on X86 || ARM || PPC || MIPS || SPARC64
954 found in every PC or ACPI-based system, and some other boards.
957 or LPC bus chips, and so on.
959 Your system will need to define the platform device used by
964 This driver can also be built as a module. If so, the module
965 will be called rtc-cmos.
968 bool "Alpha PC-style CMOS"
969 depends on ALPHA
973 Direct support for the real-time clock found on every Alpha
974 system, specifically MC146818 compatibles. If in doubt, say Y.
978 depends on X86_INTEL_MID
983 found on Moorestown platforms. The VRTC is a emulated RTC that
986 updates are done via IPC calls to the system controller FW.
990 depends on SNI_RM
996 depends on HAS_IOMEM
1002 depends on HAS_IOMEM
1007 This driver can also be built as a module. If so, the module
1008 will be called rtc-ds1511.
1012 depends on HAS_IOMEM
1017 This driver can also be built as a module. If so, the module
1018 will be called rtc-ds1553.
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.
1159 This driver can also be built as a module. If so, the module
1160 will be called rtc-m48t86.
1164 depends on HAS_IOMEM
1169 This driver can also be built as a module, if so, the module
1170 will be called "rtc-m48t35".
1174 depends on HAS_IOMEM
1182 This driver can also be built as a module, if so, the module
1183 will be called "rtc-m48t59".
1187 depends on HAS_IOMEM
1192 This driver can also be built as a module. If so, the module
1193 will be called rtc-msm6242.
1197 depends on HAS_IOMEM
1202 This driver can also be built as a module. If so, the module
1203 will be called rtc-bq4802.
1207 depends on HAS_IOMEM
1213 This driver can also be built as a module. If so, the module
1214 will be called rtc-rp5c01.
1222 This driver can also be built as a module. If so, the module
1223 will be called rtc-v3020.
1227 depends on MFD_WM831X
1232 This driver can also be built as a module. If so, the module
1233 will be called "rtc-wm831x".
1237 depends on MFD_WM8350
1242 This driver can also be built as a module. If so, the module
1243 will be called "rtc-wm8350".
1247 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1253 This driver can also be built as a module. If so, the module
1254 will be called rtc-sc27xx.
1258 depends on PLAT_SPEAR || COMPILE_TEST
1261 If you say Y here you will get support for the RTC found on
1265 depends on MFD_PCF50633
1272 tristate "ST-Ericsson AB3100 RTC"
1273 depends on AB3100_CORE
1276 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1277 support. This chip contains a battery- and capacitor-backed RTC.
1280 tristate "ST-Ericsson AB8500 RTC"
1281 depends on AB8500_CORE
1285 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1286 support. This chip contains a battery- and capacitor-backed RTC.
1290 depends on PPC_POWERNV
1294 driver based on OPAL interfaces.
1296 This driver can also be built as a module. If so, the module
1297 will be called rtc-opal.
1301 depends on OF && HAS_IOMEM
1303 If you say yes here you get support for the RTC controller found on
1308 depends on CROS_EC
1313 This driver can also be built as a module. If so, the module
1314 will be called rtc-cros-ec.
1316 comment "on-CPU RTC drivers"
1320 depends on MACH_ASM9260 || COMPILE_TEST
1322 If you say yes here you get support for the RTC on the
1325 This driver can also be built as a module. If so, the module
1326 will be called rtc-asm9260.
1330 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1332 If you say yes here you get support for the RTC on the
1335 This driver can also be built as a module. If so, the module
1336 will be called rtc-davinci.
1340 depends on ARCH_DIGICOLOR || COMPILE_TEST
1342 If you say yes here you get support for the RTC on Conexant
1345 This driver can also be built as a module. If so, the module
1346 will be called rtc-digicolor.
1350 depends on ARCH_MXC
1354 This driver can also be built as a module, if so, the module
1355 will be called "rtc-imxdi".
1359 depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST
1365 alarm functions for wakeup system from deep sleep.
1367 This driver can also be built as a module, if so, the module
1368 will be called "rtc-fsl-ftm-alarm".
1372 depends on (ARM && ARCH_MESON) || COMPILE_TEST
1375 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1378 This driver can also be built as a module, if so, the module
1379 will be called "rtc-meson".
1383 depends on ARCH_MESON || COMPILE_TEST
1389 This driver can also be built as a module. If so, the module
1390 will be called rtc-meson-vrtc.
1394 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1395 depends on OF
1396 depends on PINCTRL
1399 Say "yes" here to support the on chip real time clock
1400 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1402 This driver can also be built as a module, if so, module
1403 will be called rtc-omap.
1410 select this in the respective mach-XXXX/Kconfig file.
1414 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1421 The driver currently supports the common features on all the
1425 This driver can also be build as a module. If so, the module
1426 will be called rtc-s3c.
1430 depends on ARCH_EP93XX || COMPILE_TEST
1435 This driver can also be built as a module. If so, the module
1436 will be called rtc-ep93xx.
1440 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1445 To compile this driver as a module, choose M here: the
1446 module will be called rtc-sa1100.
1449 tristate "SuperH On-Chip RTC"
1450 depends on SUPERH || ARCH_RENESAS
1452 Say Y here to enable support for the on-chip RTC found in
1455 To compile this driver as a module, choose M here: the
1456 module will be called rtc-sh.
1460 depends on CPU_VR41XX || COMPILE_TEST
1465 To compile this driver as a module, choose M here: the
1466 module will be called rtc-vr41xx.
1470 depends on ARM_AMBA
1473 PrimeCell PL030 RTC found on certain ARM SOCs.
1475 To compile this driver as a module, choose M here: the
1476 module will be called rtc-pl030.
1480 depends on ARM_AMBA
1483 PrimeCell PL031 RTC found on certain ARM SOCs.
1485 To compile this driver as a module, choose M here: the
1486 module will be called rtc-pl031.
1490 depends on ARCH_AT91 || COMPILE_TEST
1491 depends on OF
1493 Driver for the internal RTC (Realtime Clock) module found on
1494 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1499 depends on ARCH_AT91 || COMPILE_TEST
1500 depends on OF && HAS_IOMEM
1508 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1514 depends on MIPS_ALCHEMY
1516 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1519 This driver can also be built as a module. If so, the module
1520 will be called rtc-au1xxx.
1524 depends on SH_LANDISK
1532 depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST
1534 Say Y or M here to enable RTC support on systems using the generic
1540 depends on ARCH_PXA
1552 depends on ARCH_VT8500 || COMPILE_TEST
1560 depends on SPARC64
1563 based RTC on SUN4V systems.
1568 depends on COMMON_CLK
1569 depends on ARCH_SUNXI || COMPILE_TEST
1576 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1578 If you say Y here you will get support for the RTC found on
1583 depends on SPARC64
1585 If you say Y here you will get support for the RTC found on
1590 depends on SOC_TX4939 || COMPILE_TEST
1592 Driver for the internal RTC (Realtime Clock) module found on
1597 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1599 If you say yes here you will get support for the in-chip RTC
1603 This driver can also be built as a module. If so, the module
1604 will be called rtc-mv.
1608 depends on ARCH_MVEBU || COMPILE_TEST
1610 If you say yes here you will get support for the in-chip RTC
1613 This driver can also be built as a module. If so, the module
1614 will be called armada38x-rtc.
1618 depends on OF && HAS_IOMEM
1621 found on certain SOCs.
1623 To compile this driver as a module, choose M here: the
1624 module will be called rtc-cadence.
1628 depends on HAS_IOMEM
1632 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1634 This driver can also be built as a module. If so, the module
1635 will be called rtc-ftrtc010.
1639 depends on PPC_PS3
1641 If you say yes here you will get support for the RTC on PS3.
1643 This driver can also be built as a module. If so, the module
1644 will be called rtc-ps3.
1647 tristate "ST-Ericsson COH 901 331 RTC"
1648 depends on ARCH_U300 || COMPILE_TEST
1650 If you say Y here you will get access to ST-Ericsson
1651 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1654 This driver can also be built as a module. If so, the module
1655 will be called "rtc-coh901331".
1660 depends on ARCH_MXS || COMPILE_TEST
1666 This driver can also be built as a module. If so, the module
1667 will be called rtc-stmp3xxx.
1671 depends on EZX_PCAP
1673 If you say Y here you will get support for the RTC found on
1674 the PCAP2 ASIC used on some Motorola phones.
1677 depends on MFD_MC13XXX
1680 This enables support for the RTCs found on Freescale's PMICs
1684 tristate "Freescale MPC5121 built-in RTC"
1685 depends on PPC_MPC512x || PPC_MPC52xx
1688 built-in RTC on MPC5121 or on MPC5200.
1690 This driver can also be built as a module. If so, the module
1691 will be called rtc-mpc5121.
1695 depends on MIPS || COMPILE_TEST
1696 depends on OF
1701 This driver can also be built as a module. If so, the module
1702 will be called rtc-jz4740.
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 MACH_LOONGSON32
1749 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1752 This driver can also be built as a module. If so, the module
1753 will be called rtc-ls1x.
1757 depends on ARCH_MXC
1760 RTC module.
1762 This driver can also be built as a module, if so, the module
1763 will be called "rtc-mxc".
1767 depends on ARCH_MXC
1770 SRTC module in i.MX53 processor.
1772 This driver can also be built as a module, if so, the module
1773 will be called "rtc-mxc_v2".
1778 depends on ARCH_MXC || COMPILE_TEST
1779 depends on HAS_IOMEM
1780 depends on OF
1783 Low Power (LP) RTC module.
1785 This driver can also be built as a module, if so, the module
1786 will be called "rtc-snvs".
1789 depends on IMX_SCU
1790 depends on HAVE_ARM_SMCCC
1791 tristate "NXP i.MX System Controller RTC support"
1793 If you say yes here you get support for the NXP i.MX System
1794 Controller RTC module.
1798 depends on ARCH_SIRF
1800 Say "yes" here to support the real time clock on SiRF SOC chips.
1801 This driver can also be built as a module called rtc-sirfsoc.
1805 depends on ARCH_STI
1806 depends on OF
1811 To compile this driver as a module, choose M here: the
1812 module will be called rtc-st-lpc.
1816 depends on ARCH_MOXART || COMPILE_TEST
1819 RTC module.
1821 This driver can also be built as a module. If so, the module
1822 will be called rtc-moxart
1826 depends on ARCH_MEDIATEK || COMPILE_TEST
1831 This drive can also be built as a module. If so, the module
1832 will be called rtc-mt2712.
1836 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
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".
1927 depends on USB_HID
1928 depends on HID_SENSOR_HUB && IIO
1934 If this driver is compiled as a module, it will be named
1935 rtc-hid-sensor-time.
1939 depends on OF && HAS_IOMEM
1940 depends on GOLDFISH || COMPILE_TEST
1949 depends on WILCO_EC
1953 Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook)
1955 This can also be built as a module. If so, the module will