Lines Matching +full:system +full:- +full:on +full:- +full:a +full:- +full:chip
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
30 the value read from a specified RTC device. This is useful to avoid
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
40 starts up, and when it resumes from a low power state. This
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)
128 You may want to set up a symbolic link so one of these
129 can be accessed as /dev/rtc, which is a name
136 bool "RTC UIE emulation on dev interface"
137 depends on RTC_INTF_DEV
139 Provides an emulation for RTC_UIE if the underlying rtc chip
141 once-per-second update interrupts, used for synchronization.
151 RTC test driver. It's a software RTC which can be
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.
257 manufacturing or a bootloader).
259 The first seven registers on these chips hold an RTC, and other
260 registers may add features such as NVRAM, a trickle charger for
262 sysfs, but other chip features may not be available.
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
272 The DS1307 driver suffered from a bug where it was enabling the
276 the time was previously set using a kernel predating this option,
277 reading the date will return a date in the next century.
278 To solve that, you could boot a kernel without this option set, set
279 the RTC date and then boot a kernel with this option set.
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.
304 Dallas/Maxim DS1672 timekeeping chip.
306 This driver can also be built as a module. If so, the module
307 will be called rtc-ds1672.
311 depends on OF
313 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
314 from the usual rtc functions it provides a clock output 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
330 Maxim MAX6900 I2C RTC chip.
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 || 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 MFD_RK808
393 This driver can also be built as a module. If so, the module
394 will be called rk808-rtc.
402 This driver can also be built as a module. If so, the module
403 will be called rtc-rs5c372.
409 Intersil ISL1208 RTC chip.
411 This driver can also be built as a module. If so, the module
412 will be called rtc-isl1208.
418 Intersil ISL12022 RTC chip.
420 This driver can also be built as a module. If so, the module
421 will be called rtc-isl12022.
425 depends on OF || COMPILE_TEST
428 Intersil ISL12026 RTC chip.
430 This driver can also be built as a module. If so, the module
431 will be called rtc-isl12026.
437 Xicor/Intersil X1205 RTC chip.
439 This driver can also be built as a module. If so, the module
440 will be called rtc-x1205.
448 This driver can also be built as a module. If so, the module
449 will be called rtc-pcf8523.
455 If you say yes here you get support for the PCF85063 RTC chip
457 This driver can also be built as a module. If so, the module
458 will be called rtc-pcf85063.
464 If you say yes here you get support for the PCF85363 RTC chip.
466 This driver can also be built as a module. If so, the module
467 will be called rtc-pcf85363.
469 The nvmem interface will be named pcf85363-#, where # is the
470 zero-based instance number.
476 Philips PCF8563 RTC chip. The Epson RTC8564
479 This driver can also be built as a module. If so, the module
480 will be called rtc-pcf8563.
486 RTC chip found on Acorn RiscPCs. This driver supports the
488 the RTC's SRAM. It will work on other platforms with the same
489 chip, but the year will probably have to be tweaked.
491 This driver can also be built as a module. If so, the module
492 will be called rtc-pcf8583.
502 This driver can also be built as a module. If so, the module
503 will be called rtc-m41t80.
507 depends on RTC_DRV_M41T80
514 depends on MFD_ROHM_BD71828
517 block on ROHM BD71815 and BD71828 Power Management IC.
519 This driver can also be built as a module. If so, the module
520 will be called rtc-bd70528.
526 BQ32000 I2C RTC chip.
528 This driver can also be built as a module. If so, the module
529 will be called rtc-bq32k.
533 depends on MFD_DM355EVM_MSP
535 Supports the RTC firmware in the MSP430 on the DM355 EVM.
539 depends on MENELAUS
541 If you say yes here you get support for the RTC on the
542 TWL92330 "Menelaus" power management chip, used with OMAP2
548 depends on TWL4030_CORE
549 depends on OF
551 If you say yes here you get support for the RTC on the
554 This driver can also be built as a module. If so, the module
555 will be called rtc-twl.
559 depends on MFD_PALMAS
564 This driver can also be built as a module. If so, the module
565 will be called rtc-palma.
569 depends on MFD_TPS6586X
577 depends on MFD_TPS65910
579 If you say yes here you get support for the RTC on the
582 This driver can also be built as a module. If so, the module
583 will be called rtc-tps65910.
587 depends on MFD_TPS80031
595 depends on MFD_RC5T583
597 If you say yes here you get support for the RTC on the
600 This driver can also be built as a module. If so, the module
601 will be called rtc-rc5t583.
605 depends on MFD_RN5T618
607 If you say yes here you get support for the RTC on the
610 This driver can also be built as a module. If so, the module
611 will be called rtc-rc5t619.
614 tristate "Seiko Instruments S-35390A"
618 Instruments S-35390A.
620 This driver can also be built as a module. If so the module
621 will be called rtc-s35390a.
628 Ramtron FM3130 is a chip with two separate devices inside,
631 This driver can also be built as a module. If so the module
632 will be called rtc-fm3130.
639 chip.
641 This driver can also be built as a module. If so, the module
642 will be called rtc-rx8010.
645 tristate "Epson RX-8571/RX-8581"
648 If you say yes here you will get support for the Epson RX-8571/
649 RX-8581.
651 This driver can also be built as a module. If so the module
652 will be called rtc-rx8581.
655 tristate "Epson RX-8025SA/NB"
658 RX-8025SA/NB RTC chips.
660 This driver can also be built as a module. If so, the module
661 will be called rtc-rx8025.
669 This driver can also be built as a module. If so, the module
670 will be called rtc-em3027.
679 This driver can also be built as a module. If so, the module
680 will be called rtc-rv3028.
689 This driver can also be built as a module. If so, the module
690 will be called rtc-rv3032.
698 This driver can also be built as a module. If so, the module
699 will be called rtc-rv8803.
703 depends on MFD_SEC_CORE || COMPILE_TEST
710 This driver can also be built as a module. If so, the module
711 will be called rtc-s5m.
720 This driver can also be built as a module. If so, the module
721 will be called rtc-sd3078
733 ST M41T93 SPI RTC chip.
735 This driver can also be built as a module. If so, the module
736 will be called rtc-m41t93.
742 ST M41T94 SPI RTC chip.
744 This driver can also be built as a module. If so, the module
745 will be called rtc-m41t94.
749 depends on SPI
753 This driver can also be built as a module. If so, the module
754 will be called rtc-ds1302.
760 and DS1306 real time clock chips. These support a trickle
763 This driver can also be built as a module. If so, the module
764 will be called rtc-ds1305.
774 This driver can also be built as a module. If so, the module
775 will be called rtc-ds1343.
784 This driver only supports the RTC feature, and not other chip
787 This driver can also be built as a module. If so, the module
788 will be called rtc-ds1347.
797 other chip features such as alarms.
799 This driver can also be built as a module. If so, the module
800 will be called rtc-ds1390.
806 Maxim MAX6916 SPI RTC chip.
808 This driver only supports the RTC feature, and not other chip
811 This driver can also be built as a module. If so, the module
812 will be called rtc-max6916.
815 tristate "Epson RTC-9701JE"
818 Epson RTC-9701JE SPI RTC chip.
820 This driver can also be built as a module. If so, the module
821 will be called rtc-r9701.
824 tristate "Epson RX-4581"
826 If you say yes here you will get support for the Epson RX-4581.
828 This driver can also be built as a module. If so the module
829 will be called rtc-rx4581.
837 This driver can also be built as a module. If so, the module
838 will be called rtc-rs5c348.
844 Maxim MAX6902 SPI RTC chip.
846 This driver can also be built as a module. If so, the module
847 will be called rtc-max6902.
854 RTC chip.
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.
942 tristate "Epson RX-6110"
943 depends on RTC_I2C_AND_SPI
947 If you say yes here you will get support for the Epson RX-6110.
949 This driver can also be built as a module. If so the module
950 will be called rtc-rx6110.
955 # <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
959 tristate "PC-style 'CMOS'"
960 depends on X86 || ARM || PPC || MIPS || SPARC64
965 found in every PC or ACPI-based system, and some other boards.
968 or LPC bus chips, and so on.
970 Your system will need to define the platform device used by
975 This driver can also be built as a module. If so, the module
976 will be called rtc-cmos.
979 bool "Alpha PC-style CMOS"
980 depends on ALPHA
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
1004 Dallas DS1511 timekeeping/watchdog chip.
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
1014 Maxim/Dallas DS1553 timekeeping chip.
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
1040 clock chip.
1042 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
1043 systems, as well as EPPC-405-UC modules by electronic system design
1050 clock chip.
1052 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
1053 which supports a few minor features such as Vcc, Vbat, and Power
1054 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
1064 clock chip.
1066 This chip features 2kb of extended NV-SRAM. It may possibly be
1073 clock chip.
1075 This chip features 4kb of extended NV-SRAM.
1081 clock chip.
1083 This chip features 8kb of extended NV-SRAM.
1089 depends on HAS_IOMEM
1092 Maxim/Dallas DS1742/1743 timekeeping chip.
1094 This driver can also be built as a module. If so, the module
1095 will be called rtc-ds1742.
1101 Dallas DS2404 RTC chip.
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
1148 Simtek STK17TA8 timekeeping chip.
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
1168 ST M48T35 RTC chip.
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
1178 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
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
1191 timekeeping chip. It is used in some Amiga models (e.g. A2000).
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
1201 BQ4802 RTC chip.
1203 This driver can also be built as a module. If so, the module
1204 will be called rtc-bq4802.
1208 depends on HAS_IOMEM
1211 timekeeping chip. It is used in some Amiga models (e.g. A3000
1214 This driver can also be built as a module. If so, the module
1215 will be called rtc-rp5c01.
1221 EM Microelectronic v3020 RTC chip.
1223 This driver can also be built as a module. If so, the module
1224 will be called rtc-v3020.
1228 depends on MFD_WM831X
1233 This driver can also be built as a module. If so, the module
1234 will be called "rtc-wm831x".
1238 depends on MFD_WM8350
1243 This driver can also be built as a module. If so, the module
1244 will be called "rtc-wm8350".
1248 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1254 This driver can also be built as a module. If so, the module
1255 will be called rtc-sc27xx.
1259 depends on PLAT_SPEAR || COMPILE_TEST
1262 If you say Y here you will get support for the RTC found on
1266 depends on MFD_PCF50633
1273 tristate "ST-Ericsson AB8500 RTC"
1274 depends on AB8500_CORE
1278 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1279 support. This chip contains a battery- and capacitor-backed RTC.
1283 depends on PPC_POWERNV
1287 driver based on OPAL interfaces.
1289 This driver can also be built as a module. If so, the module
1290 will be called rtc-opal.
1294 depends on OF && HAS_IOMEM
1296 If you say yes here you get support for the RTC controller found on
1301 depends on CROS_EC
1306 This driver can also be built as a module. If so, the module
1307 will be called rtc-cros-ec.
1311 depends on MFD_NTXEC
1314 embedded controller found in certain e-book readers designed by the
1317 comment "on-CPU RTC drivers"
1321 depends on MACH_ASM9260 || COMPILE_TEST
1323 If you say yes here you get support for the RTC on the
1326 This driver can also be built as a module. If so, the module
1327 will be called rtc-asm9260.
1331 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1333 If you say yes here you get support for the RTC on the
1336 This driver can also be built as a module. If so, the module
1337 will be called rtc-davinci.
1341 depends on ARCH_DIGICOLOR || COMPILE_TEST
1343 If you say yes here you get support for the RTC on Conexant
1346 This driver can also be built as a module. If so, the module
1347 will be called rtc-digicolor.
1351 depends on ARCH_MXC
1352 depends on OF
1356 This driver can also be built as a module, if so, the module
1357 will be called "rtc-imxdi".
1361 depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST
1367 alarm functions for wakeup system from deep sleep.
1369 This driver can also be built as a module, if so, the module
1370 will be called "rtc-fsl-ftm-alarm".
1374 depends on (ARM && ARCH_MESON) || COMPILE_TEST
1377 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1380 This driver can also be built as a module, if so, the module
1381 will be called "rtc-meson".
1385 depends on ARCH_MESON || COMPILE_TEST
1391 This driver can also be built as a module. If so, the module
1392 will be called rtc-meson-vrtc.
1396 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1397 depends on OF
1398 depends on PINCTRL
1401 Say "yes" here to support the on chip real time clock
1402 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1404 This driver can also be built as a module, if so, module
1405 will be called rtc-omap.
1412 select this in the respective mach-XXXX/Kconfig file.
1416 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1423 The driver currently supports the common features on all the
1427 This driver can also be build as a module. If so, the module
1428 will be called rtc-s3c.
1432 depends on ARCH_EP93XX || COMPILE_TEST
1437 This driver can also be built as a module. If so, the module
1438 will be called rtc-ep93xx.
1442 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1447 To compile this driver as a module, choose M here: the
1448 module will be called rtc-sa1100.
1451 tristate "SuperH On-Chip RTC"
1452 depends on SUPERH || ARCH_RENESAS
1454 Say Y here to enable support for the on-chip RTC found in
1455 most SuperH processors. This RTC is also found in RZ/A SoCs.
1457 To compile this driver as a module, choose M here: the
1458 module will be called rtc-sh.
1462 depends on CPU_VR41XX || COMPILE_TEST
1467 To compile this driver as a module, choose M here: the
1468 module will be called rtc-vr41xx.
1472 depends on ARM_AMBA
1475 PrimeCell PL030 RTC found on certain ARM SOCs.
1477 To compile this driver as a module, choose M here: the
1478 module will be called rtc-pl030.
1482 depends on ARM_AMBA
1485 PrimeCell PL031 RTC found on certain ARM SOCs.
1487 To compile this driver as a module, choose M here: the
1488 module will be called rtc-pl031.
1492 depends on ARCH_AT91 || COMPILE_TEST
1493 depends on OF
1495 Driver for the internal RTC (Realtime Clock) module found on
1496 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1501 depends on ARCH_AT91 || COMPILE_TEST
1502 depends on OF && HAS_IOMEM
1506 can be used as an RTC thanks to the backup power supply (e.g. a
1510 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1516 depends on MIPS_ALCHEMY
1518 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1519 counter) to be used as a RTC.
1521 This driver can also be built as a module. If so, the module
1522 will be called rtc-au1xxx.
1526 depends on SH_LANDISK
1532 # Please consider writing a new RTC driver instead of using the generic
1534 depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST
1536 Say Y or M here to enable RTC support on systems using the generic
1542 depends on ARCH_PXA
1554 depends on ARCH_VT8500 || COMPILE_TEST
1562 depends on SPARC64
1565 based RTC on SUN4V systems.
1570 depends on COMMON_CLK
1571 depends on ARCH_SUNXI || COMPILE_TEST
1578 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1580 If you say Y here you will get support for the RTC found on
1585 depends on SPARC64
1587 If you say Y here you will get support for the RTC found on
1592 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1594 If you say yes here you will get support for the in-chip RTC
1598 This driver can also be built as a module. If so, the module
1599 will be called rtc-mv.
1603 depends on ARCH_MVEBU || COMPILE_TEST
1604 depends on OF
1606 If you say yes here you will get support for the in-chip RTC
1609 This driver can also be built as a module. If so, the module
1610 will be called armada38x-rtc.
1614 depends on OF && HAS_IOMEM
1617 found on certain SOCs.
1619 To compile this driver as a module, choose M here: the
1620 module will be called rtc-cadence.
1624 depends on HAS_IOMEM
1628 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1630 This driver can also be built as a module. If so, the module
1631 will be called rtc-ftrtc010.
1635 depends on PPC_PS3
1637 If you say yes here you will get support for the RTC on PS3.
1639 This driver can also be built as a module. If so, the module
1640 will be called rtc-ps3.
1644 depends on ARCH_MXS || COMPILE_TEST
1650 This driver can also be built as a module. If so, the module
1651 will be called rtc-stmp3xxx.
1655 depends on EZX_PCAP
1657 If you say Y here you will get support for the RTC found on
1658 the PCAP2 ASIC used on some Motorola phones.
1661 depends on MFD_MC13XXX
1664 This enables support for the RTCs found on Freescale's PMICs
1668 tristate "Freescale MPC5121 built-in RTC"
1669 depends on PPC_MPC512x || PPC_MPC52xx
1672 built-in RTC on MPC5121 or on MPC5200.
1674 This driver can also be built as a module. If so, the module
1675 will be called rtc-mpc5121.
1679 depends on MIPS || COMPILE_TEST
1680 depends on OF
1685 This driver can also be built as a module. If so, the module
1686 will be called rtc-jz4740.
1690 depends on ARCH_LPC18XX || COMPILE_TEST
1691 depends on OF && HAS_IOMEM
1693 This enables support for the NXP RTC found which can be found on
1697 the hardware RTC. This driver can also be built as a module. If
1698 so, the module will be called rtc-lpc24xx.
1701 depends on ARCH_LPC32XX || COMPILE_TEST
1706 This driver can also be built as a module. If so, the module
1707 will be called rtc-lpc32xx.
1711 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1716 To compile this driver as a module, choose M here: the
1717 module will be called rtc-pm8xxx.
1721 depends on ARCH_TEGRA || COMPILE_TEST
1726 This drive can also be built as a module. If so, the module
1727 will be called rtc-tegra.
1731 depends on MACH_LOONGSON32
1733 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1734 counter) to be used as a RTC.
1736 This driver can also be built as a module. If so, the module
1737 will be called rtc-ls1x.
1741 depends on ARCH_MXC || COMPILE_TEST
1742 depends on HAS_IOMEM
1743 depends on OF
1748 This driver can also be built as a module, if so, the module
1749 will be called "rtc-mxc".
1753 depends on ARCH_MXC || COMPILE_TEST
1754 depends on HAS_IOMEM
1755 depends on OF
1760 This driver can also be built as a module, if so, the module
1761 will be called "rtc-mxc_v2".
1766 depends on ARCH_MXC || COMPILE_TEST
1767 depends on HAS_IOMEM
1768 depends on OF
1773 This driver can also be built as a module, if so, the module
1774 will be called "rtc-snvs".
1777 depends on IMX_SCU
1778 depends on HAVE_ARM_SMCCC
1779 tristate "NXP i.MX System Controller RTC support"
1781 If you say yes here you get support for the NXP i.MX System
1786 depends on ARCH_STI
1787 depends on OF
1792 To compile this driver as a module, choose M here: the
1793 module will be called rtc-st-lpc.
1797 depends on ARCH_MOXART || COMPILE_TEST
1802 This driver can also be built as a module. If so, the module
1803 will be called rtc-moxart
1807 depends on ARCH_MEDIATEK || COMPILE_TEST
1812 This drive can also be built as a module. If so, the module
1813 will be called rtc-mt2712.
1817 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1827 depends on ARCH_MEDIATEK || COMPILE_TEST
1832 This drive can also be built as a module. If so, the module
1833 will be called rtc-mt7622.
1836 tristate "APM X-Gene RTC"
1837 depends on HAS_IOMEM
1838 depends on ARCH_XGENE || COMPILE_TEST
1840 If you say yes here you get support for the APM X-Gene SoC real time
1843 This driver can also be built as a module, if so, the module
1844 will be called "rtc-xgene".
1848 depends on MACH_PIC32
1853 This driver can also be built as a module. If so, the module
1854 will be called rtc-pic32
1857 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1859 depends on OF && HAS_IOMEM
1862 RTC-7301SF/DG chips.
1864 This driver can also be built as a module. If so, the module
1865 will be called rtc-r7301.
1870 depends on ARCH_STM32 || COMPILE_TEST
1872 If you say yes here you get support for the STM32 On-Chip
1875 This driver can also be built as a module, if so, the module
1876 will be called "rtc-stm32".
1879 depends on MFD_CPCAP
1882 Say y here for CPCAP rtc found on some Motorola phones
1887 depends on ARCH_REALTEK || COMPILE_TEST
1895 depends on OF
1896 depends on ARCH_ASPEED || COMPILE_TEST
1901 This driver can also be built as a module, if so, the module
1902 will be called "rtc-aspeed".
1908 depends on USB_HID
1909 depends on HID_SENSOR_HUB && IIO
1915 If this driver is compiled as a module, it will be named
1916 rtc-hid-sensor-time.
1920 depends on HAS_IOMEM
1924 Goldfish is a code name for the virtual platform developed by Google
1929 depends on WILCO_EC
1933 Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook)
1935 This can also be built as a module. If so, the module will