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 I2C
379 depends on COMMON_CLK
380 depends on HWMON || HWMON=n
386 This driver can also be built as a module. If so, the module
387 will be called rtc-max31335.
391 depends on MFD_MAX77686 || MFD_MAX77620 || MFD_MAX77714 || COMPILE_TEST
396 This driver can also be built as a module. If so, the module
397 will be called rtc-max77686.
401 depends on OF
406 This driver can also be built as a module, if so, the module will be
407 called "rtc-nct3018y".
411 depends on MFD_RK8XX
416 This driver can also be built as a module. If so, the module
417 will be called rk808-rtc.
425 This driver can also be built as a module. If so, the module
426 will be called rtc-rs5c372.
434 This driver can also be built as a module. If so, the module
435 will be called rtc-isl1208.
444 This driver can also be built as a module. If so, the module
445 will be called rtc-isl12022.
449 depends on OF
454 This driver can also be built as a module. If so, the module
455 will be called rtc-isl12026.
463 This driver can also be built as a module. If so, the module
464 will be called rtc-x1205.
473 This driver can also be built as a module. If so, the module
474 will be called rtc-pcf8523.
482 This driver can also be built as a module. If so, the module
483 will be called rtc-pcf85063.
491 This driver can also be built as a module. If so, the module
492 will be called rtc-pcf85363.
494 The nvmem interface will be named pcf85363-#, where # is the
495 zero-based instance number.
504 This driver can also be built as a module. If so, the module
505 will be called rtc-pcf8563.
511 RTC chip found on Acorn RiscPCs. This driver supports the
513 the RTC's SRAM. It will work on other platforms with the same
516 This driver can also be built as a module. If so, the module
517 will be called rtc-pcf8583.
527 This driver can also be built as a module. If so, the module
528 will be called rtc-m41t80.
532 depends on RTC_DRV_M41T80
539 depends on MFD_ROHM_BD71828
542 block on ROHM BD71815 and BD71828 Power Management IC.
544 This driver can also be built as a module. If so, the module
545 will be called rtc-bd70528.
553 This driver can also be built as a module. If so, the module
554 will be called rtc-bq32k.
558 depends on MENELAUS
560 If you say yes here you get support for the RTC on the
563 the Menelaus driver; it's not separate module.
567 depends on TWL4030_CORE
568 depends on OF
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-twl.
578 depends on MFD_PALMAS
583 This driver can also be built as a module. If so, the module
584 will be called rtc-palma.
588 depends on MFD_TPS6586X
592 the TPS6586X RTC module.
596 depends on MFD_TPS6594
601 the TPS6594 RTC module.
603 This driver can also be built as a module. If so, the module
604 will be called rtc-tps6594.
608 depends on MFD_TPS65910
610 If you say yes here you get support for the RTC on the
613 This driver can also be built as a module. If so, the module
614 will be called rtc-tps65910.
618 depends on MFD_RC5T583
620 If you say yes here you get support for the RTC on the
623 This driver can also be built as a module. If so, the module
624 will be called rtc-rc5t583.
628 depends on MFD_RN5T618
630 If you say yes here you get support for the RTC on the
633 This driver can also be built as a module. If so, the module
634 will be called rtc-rc5t619.
637 tristate "Seiko Instruments S-35390A"
641 Instruments S-35390A.
643 This driver can also be built as a module. If so the module
644 will be called rtc-s35390a.
654 This driver can also be built as a module. If so the module
655 will be called rtc-fm3130.
664 This driver can also be built as a module. If so, the module
665 will be called rtc-rx8010.
670 depends on I2C
674 This driver can also be built as a module. If so, the module will be
675 called rtc-rx8111.
678 tristate "Epson RX-8571/RX-8581"
681 If you say yes here you will get support for the Epson RX-8571/
682 RX-8581.
684 This driver can also be built as a module. If so the module
685 will be called rtc-rx8581.
688 tristate "Epson RX-8025SA/NB"
691 RX-8025SA/NB RTC chips.
693 This driver can also be built as a module. If so, the module
694 will be called rtc-rx8025.
702 This driver can also be built as a module. If so, the module
703 will be called rtc-em3027.
712 This driver can also be built as a module. If so, the module
713 will be called rtc-rv3028.
722 This driver can also be built as a module. If so, the module
723 will be called rtc-rv3032.
731 This driver can also be built as a module. If so, the module
732 will be called rtc-rv8803.
736 depends on MFD_SEC_CORE || COMPILE_TEST
743 This driver can also be built as a module. If so, the module
744 will be called rtc-s5m.
751 DFRobot SD2405AL I2C RTC Module.
753 This driver can also be built as a module. If so, the module
754 will be called rtc-sd2405al.
763 This driver can also be built as a module. If so, the module
764 will be called rtc-sd3078
778 This driver can also be built as a module. If so, the module
779 will be called rtc-m41t93.
787 This driver can also be built as a module. If so, the module
788 will be called rtc-m41t94.
792 depends on SPI
796 This driver can also be built as a module. If so, the module
797 will be called rtc-ds1302.
806 This driver can also be built as a module. If so, the module
807 will be called rtc-ds1305.
817 This driver can also be built as a module. If so, the module
818 will be called rtc-ds1343.
830 This driver can also be built as a module. If so, the module
831 will be called rtc-ds1347.
842 This driver can also be built as a module. If so, the module
843 will be called rtc-ds1390.
854 This driver can also be built as a module. If so, the module
855 will be called rtc-max6916.
858 tristate "Epson RTC-9701JE"
861 Epson RTC-9701JE SPI RTC chip.
863 This driver can also be built as a module. If so, the module
864 will be called rtc-r9701.
867 tristate "Epson RX-4581"
869 If you say yes here you will get support for the Epson RX-4581.
871 This driver can also be built as a module. If so the module
872 will be called rtc-rx4581.
880 This driver can also be built as a module. If so, the module
881 will be called rtc-rs5c348.
889 This driver can also be built as a module. If so, the module
890 will be called rtc-max6902.
899 This driver can also be built as a module. If so, the module
900 will be called rtc-pcf2123.
907 This driver can also be built as a module. If so the module
908 will be called rtc-mcp795.
926 depends on RTC_I2C_AND_SPI
931 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
934 This driver can also be built as a module. If so, the module
935 will be called rtc-ds3232.
939 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
942 Say Y here if you want to expose temperature sensor data on
943 rtc-ds3232
947 depends on RTC_I2C_AND_SPI
960 This driver can also be built as a module. If so, the module
961 will be called rtc-pcf2127.
965 depends on RTC_I2C_AND_SPI
972 This driver can also be built as a module. If so, the module
973 will be called rtc-rv3029c2.
977 depends on RTC_DRV_RV3029C2 && HWMON
978 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
981 Say Y here if you want to expose temperature sensor data on
982 rtc-rv3029.
985 tristate "Epson RX-6110"
986 depends on RTC_I2C_AND_SPI
990 If you say yes here you will get support for the Epson RX-6110.
992 This driver can also be built as a module. If so the module
993 will be called rtc-rx6110.
1002 tristate "PC-style 'CMOS'"
1003 depends on X86 || ARM || PPC || MIPS || SPARC64
1004 depends on HAS_IOPORT || MACH_DECSTATION
1009 found in every PC or ACPI-based system, and some other boards.
1012 or LPC bus chips, and so on.
1014 Your system will need to define the platform device used by
1019 This driver can also be built as a module. If so, the module
1020 will be called rtc-cmos.
1023 bool "Alpha PC-style CMOS"
1024 depends on ALPHA
1025 depends on HAS_IOPORT
1029 Direct support for the real-time clock found on every Alpha
1030 system, specifically MC146818 compatibles. If in doubt, say Y.
1034 depends on SNI_RM
1040 depends on HAS_IOMEM
1046 depends on HAS_IOMEM
1051 This driver can also be built as a module. If so, the module
1052 will be called rtc-ds1511.
1056 depends on HAS_IOMEM
1061 This driver can also be built as a module. If so, the module
1062 will be called rtc-ds1553.
1066 depends on HAS_IOMEM
1073 This driver can also be built as a module. If so, the module
1074 will be called rtc-ds1685.
1078 depends on RTC_DRV_DS1685_FAMILY
1088 systems, as well as EPPC-405-UC modules by electronic system design
1099 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
1111 This chip features 2kb of extended NV-SRAM. It may possibly be
1120 This chip features 4kb of extended NV-SRAM.
1128 This chip features 8kb of extended NV-SRAM.
1134 depends on HAS_IOMEM
1139 This driver can also be built as a module. If so, the module
1140 will be called rtc-ds1742.
1148 This driver can also be built as a module. If so, the module
1149 will be called rtc-ds2404.
1153 depends on PMIC_DA9052
1156 DA9052-BC and DA9053-AA/Bx PMICs.
1160 depends on MFD_DA9055
1165 This driver can also be built as a module. If so, the module
1166 will be called rtc-da9055
1170 depends on MFD_DA9063 || MFD_DA9062
1175 This driver can also be built as a module. If so, the module
1176 will be called "rtc-da9063".
1180 depends on EFI && !X86
1185 This driver can also be built as a module. If so, the module
1186 will be called rtc-efi.
1190 depends on HAS_IOMEM
1195 This driver can also be built as a module. If so, the module
1196 will be called rtc-stk17ta8.
1200 depends on HAS_IOMEM
1205 This driver can also be built as a module. If so, the module
1206 will be called rtc-m48t86.
1210 depends on HAS_IOMEM
1215 This driver can also be built as a module, if so, the module
1216 will be called "rtc-m48t35".
1220 depends on HAS_IOMEM
1228 This driver can also be built as a module, if so, the module
1229 will be called "rtc-m48t59".
1233 depends on HAS_IOMEM
1238 This driver can also be built as a module. If so, the module
1239 will be called rtc-msm6242.
1243 depends on HAS_IOMEM && HAS_IOPORT
1244 depends on SPARC || COMPILE_TEST
1249 This driver can also be built as a module. If so, the module
1250 will be called rtc-bq4802.
1254 depends on HAS_IOMEM
1260 This driver can also be built as a module. If so, the module
1261 will be called rtc-rp5c01.
1265 depends on GAMECUBE || WII || COMPILE_TEST
1271 This driver can also be built as a module. If so, the module
1272 will be called "rtc-gamecube".
1276 depends on MFD_WM831X
1281 This driver can also be built as a module. If so, the module
1282 will be called "rtc-wm831x".
1286 depends on MFD_WM8350
1291 This driver can also be built as a module. If so, the module
1292 will be called "rtc-wm8350".
1296 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1302 This driver can also be built as a module. If so, the module
1303 will be called rtc-sc27xx.
1307 depends on PLAT_SPEAR || COMPILE_TEST
1310 If you say Y here you will get support for the RTC found on
1314 depends on MFD_PCF50633
1321 tristate "ST-Ericsson AB8500 RTC"
1322 depends on AB8500_CORE
1326 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1327 support. This chip contains a battery- and capacitor-backed RTC.
1331 depends on PPC_POWERNV
1335 driver based on OPAL interfaces.
1337 This driver can also be built as a module. If so, the module
1338 will be called rtc-opal.
1341 tristate "OP-TEE based RTC driver"
1342 depends on OPTEE
1344 Select this to get support for OP-TEE based RTC control on SoCs where
1347 This driver can also be built as a module. If so, the module
1348 will be called rtc-optee.
1352 depends on OF && HAS_IOMEM
1354 If you say yes here you get support for the RTC controller found on
1359 depends on CROS_EC
1364 This driver can also be built as a module. If so, the module
1365 will be called rtc-cros-ec.
1369 depends on MFD_NTXEC
1372 embedded controller found in certain e-book readers designed by the
1375 comment "on-CPU RTC drivers"
1379 depends on MACH_ASM9260 || COMPILE_TEST
1381 If you say yes here you get support for the RTC on the
1384 This driver can also be built as a module. If so, the module
1385 will be called rtc-asm9260.
1389 depends on ARCH_DIGICOLOR || COMPILE_TEST
1391 If you say yes here you get support for the RTC on Conexant
1394 This driver can also be built as a module. If so, the module
1395 will be called rtc-digicolor.
1399 depends on ARCH_MXC || COMPILE_TEST
1400 depends on OF
1404 This driver can also be built as a module, if so, the module
1405 will be called "rtc-imxdi".
1409 depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST
1415 alarm functions for wakeup system from deep sleep.
1417 This driver can also be built as a module, if so, the module
1418 will be called "rtc-fsl-ftm-alarm".
1422 depends on (ARM && ARCH_MESON) || COMPILE_TEST
1425 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1428 This driver can also be built as a module, if so, the module
1429 will be called "rtc-meson".
1433 depends on ARCH_MESON || COMPILE_TEST
1439 This driver can also be built as a module. If so, the module
1440 will be called rtc-meson-vrtc.
1444 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1445 depends on OF
1446 depends on PINCTRL
1449 Say "yes" here to support the on chip real time clock
1450 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1452 This driver can also be built as a module, if so, module
1453 will be called rtc-omap.
1457 depends on ARCH_EXYNOS || ARCH_S3C64XX || ARCH_S5PV210 || \
1465 This driver can also be build as a module. If so, the module
1466 will be called rtc-s3c.
1470 depends on ARCH_EP93XX || COMPILE_TEST
1475 This driver can also be built as a module. If so, the module
1476 will be called rtc-ep93xx.
1480 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1485 To compile this driver as a module, choose M here: the
1486 module will be called rtc-sa1100.
1489 tristate "SuperH On-Chip RTC"
1490 depends on SUPERH || ARCH_RENESAS
1492 Say Y here to enable support for the on-chip RTC found in
1495 To compile this driver as a module, choose M here: the
1496 module will be called rtc-sh.
1500 depends on SOC_SP7021
1502 Say 'yes' to get support for the real-time clock present in
1503 Sunplus SP7021 - a SoC for industrial applications. It provides
1508 This driver can also be built as a module. If so, the module
1509 will be called rtc-sunplus.
1513 depends on ARM_AMBA
1516 PrimeCell PL030 RTC found on certain ARM SOCs.
1518 To compile this driver as a module, choose M here: the
1519 module will be called rtc-pl030.
1523 depends on ARM_AMBA
1526 PrimeCell PL031 RTC found on certain ARM SOCs.
1528 To compile this driver as a module, choose M here: the
1529 module will be called rtc-pl031.
1533 depends on ARCH_AT91 || COMPILE_TEST
1534 depends on OF
1536 Driver for the internal RTC (Realtime Clock) module found on
1537 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1542 depends on ARCH_AT91 || COMPILE_TEST
1543 depends on OF && HAS_IOMEM
1551 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1557 depends on MIPS_ALCHEMY
1559 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1562 This driver can also be built as a module. If so, the module
1563 will be called rtc-au1xxx.
1567 depends on SH_LANDISK
1573 depends on ARCH_RZN1 || COMPILE_TEST
1574 depends on OF && HAS_IOMEM
1582 depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST
1584 Say Y or M here to enable RTC support on systems using the generic
1590 depends on ARCH_PXA
1602 depends on ARCH_VT8500 || COMPILE_TEST
1610 depends on SPARC64
1613 based RTC on SUN4V systems.
1618 depends on COMMON_CLK
1619 depends on ARCH_SUNXI || COMPILE_TEST
1626 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1628 If you say Y here you will get support for the RTC found on
1633 depends on SPARC64
1635 If you say Y here you will get support for the RTC found on
1640 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1642 If you say yes here you will get support for the in-chip RTC
1646 This driver can also be built as a module. If so, the module
1647 will be called rtc-mv.
1651 depends on ARCH_MVEBU || COMPILE_TEST
1652 depends on OF
1654 If you say yes here you will get support for the in-chip RTC
1657 This driver can also be built as a module. If so, the module
1658 will be called armada38x-rtc.
1662 depends on OF && HAS_IOMEM
1665 found on certain SOCs.
1667 To compile this driver as a module, choose M here: the
1668 module will be called rtc-cadence.
1672 depends on HAS_IOMEM
1676 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1678 This driver can also be built as a module. If so, the module
1679 will be called rtc-ftrtc010.
1683 depends on PPC_PS3
1685 If you say yes here you will get support for the RTC on PS3.
1687 This driver can also be built as a module. If so, the module
1688 will be called rtc-ps3.
1692 depends on ARCH_MXS || COMPILE_TEST
1698 This driver can also be built as a module. If so, the module
1699 will be called rtc-stmp3xxx.
1703 depends on EZX_PCAP
1705 If you say Y here you will get support for the RTC found on
1706 the PCAP2 ASIC used on some Motorola phones.
1709 depends on MFD_MC13XXX
1712 This enables support for the RTCs found on Freescale's PMICs
1716 tristate "Freescale MPC5121 built-in RTC"
1717 depends on PPC_MPC512x || PPC_MPC52xx
1720 built-in RTC on MPC5121 or on MPC5200.
1722 This driver can also be built as a module. If so, the module
1723 will be called rtc-mpc5121.
1727 depends on MIPS || COMPILE_TEST
1728 depends on OF && COMMON_CLK
1733 This driver can also be built as a module. If so, the module
1734 will be called rtc-jz4740.
1737 tristate "Loongson On-chip RTC"
1738 depends on MACH_LOONGSON32 || MACH_LOONGSON64 || COMPILE_TEST
1741 This is a driver for the Loongson on-chip Counter0 (Time-Of-Year
1743 It can be found on Loongson-1 series cpu, Loongson-2K series cpu
1746 This driver can also be built as a module. If so, the module
1747 will be called rtc-loongson.
1751 depends on ARCH_LPC18XX || COMPILE_TEST
1752 depends on OF && HAS_IOMEM
1753 depends on COMMON_CLK
1755 This enables support for the NXP RTC found which can be found on
1759 the hardware RTC. This driver can also be built as a module. If
1760 so, the module will be called rtc-lpc24xx.
1763 depends on ARCH_LPC32XX || COMPILE_TEST
1768 This driver can also be built as a module. If so, the module
1769 will be called rtc-lpc32xx.
1773 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1778 To compile this driver as a module, choose M here: the
1779 module will be called rtc-pm8xxx.
1783 depends on ARCH_TEGRA || COMPILE_TEST
1786 Tegra 200 series internal RTC module.
1788 This drive can also be built as a module. If so, the module
1789 will be called rtc-tegra.
1793 depends on ARCH_MXC || COMPILE_TEST
1794 depends on HAS_IOMEM
1795 depends on OF
1798 RTC module.
1800 This driver can also be built as a module, if so, the module
1801 will be called "rtc-mxc".
1805 depends on ARCH_MXC || COMPILE_TEST
1806 depends on HAS_IOMEM
1807 depends on OF
1810 SRTC module in i.MX53 processor.
1812 This driver can also be built as a module, if so, the module
1813 will be called "rtc-mxc_v2".
1818 depends on ARCH_MXC || COMPILE_TEST
1819 depends on HAS_IOMEM
1820 depends on OF
1823 Low Power (LP) RTC module.
1825 This driver can also be built as a module, if so, the module
1826 will be called "rtc-snvs".
1831 depends on ARCH_MXC || COMPILE_TEST
1832 depends on HAS_IOMEM
1833 depends on OF
1835 If you say yes here you get support for the NXP BBNSM RTC module.
1837 This driver can also be built as a module, if so, the module
1838 will be called "rtc-bbnsm".
1841 depends on IMX_SCMI_BBM_EXT || COMPILE_TEST
1846 RTC module.
1848 To compile this driver as a module, choose M here: the
1849 module will be called rtc-imx-sm-bbm.
1852 depends on IMX_SCU
1853 depends on HAVE_ARM_SMCCC
1854 tristate "NXP i.MX System Controller RTC support"
1856 If you say yes here you get support for the NXP i.MX System
1857 Controller RTC module.
1861 depends on ARCH_STI
1862 depends on OF
1867 To compile this driver as a module, choose M here: the
1868 module will be called rtc-st-lpc.
1872 depends on ARCH_MOXART || COMPILE_TEST
1875 RTC module.
1877 This driver can also be built as a module. If so, the module
1878 will be called rtc-moxart
1882 depends on ARCH_MEDIATEK || COMPILE_TEST
1887 This drive can also be built as a module. If so, the module
1888 will be called rtc-mt2712.
1892 depends on MFD_MT6397 || COMPILE_TEST
1903 depends on ARCH_MEDIATEK || COMPILE_TEST
1908 This drive can also be built as a module. If so, the module
1909 will be called rtc-mt7622.
1912 tristate "APM X-Gene RTC"
1913 depends on HAS_IOMEM
1914 depends on ARCH_XGENE || COMPILE_TEST
1916 If you say yes here you get support for the APM X-Gene SoC real time
1919 This driver can also be built as a module, if so, the module
1920 will be called "rtc-xgene".
1924 depends on MACH_PIC32
1927 If you say yes here you get support for the PIC32 RTC module.
1929 This driver can also be built as a module. If so, the module
1930 will be called rtc-pic32
1933 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1935 depends on OF && HAS_IOMEM
1938 RTC-7301SF/DG chips.
1940 This driver can also be built as a module. If so, the module
1941 will be called rtc-r7301.
1946 depends on ARCH_STM32 || COMPILE_TEST
1947 depends on OF
1948 depends on PINCTRL
1952 depends on COMMON_CLK
1954 If you say yes here you get support for the STM32 On-Chip
1957 This driver can also be built as a module, if so, the module
1958 will be called "rtc-stm32".
1961 depends on MFD_CPCAP
1964 Say y here for CPCAP rtc found on some Motorola phones
1969 depends on ARCH_REALTEK || COMPILE_TEST
1977 depends on OF
1978 depends on ARCH_ASPEED || COMPILE_TEST
1983 This driver can also be built as a module, if so, the module
1984 will be called "rtc-aspeed".
1988 depends on ARCH_K3 || COMPILE_TEST
1994 This driver can also be built as a module, if so, the module
1995 will be called "rtc-ti-k3".
1999 depends on ARCH_MA35 || COMPILE_TEST
2003 On-Chip Real Time Clock.
2005 This driver can also be built as a module, if so, the module
2006 will be called "rtc-ma35d1".
2012 depends on USB_HID
2013 depends on HID_SENSOR_HUB && IIO
2019 If this driver is compiled as a module, it will be named
2020 rtc-hid-sensor-time.
2024 depends on HAS_IOMEM
2033 depends on WILCO_EC
2037 Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook)
2039 This can also be built as a module. If so, the module will
2044 depends on ARCH_MSTARV7 || COMPILE_TEST
2046 If you say yes here you get support for the Mstar MSC313e On-Chip
2049 This driver can also be built as a module, if so, the module
2050 will be called "rtc-msc313".
2053 tristate "Microchip PolarFire SoC built-in RTC"
2054 depends on ARCH_MICROCHIP_POLARFIRE
2057 built-in RTC on Polarfire SoC.
2059 This driver can also be built as a module, if so, the module
2060 will be called "rtc-mpfs".
2064 depends on ARCH_MSTARV7 || COMPILE_TEST
2067 If you say yes here you get support for the SigmaStar SSD202D On-Chip
2070 This driver can also be built as a module, if so, the module
2071 will be called "rtc-ssd20xd".