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 && !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
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
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)
119 You may want to set up a symbolic link so one of these
120 can be accessed as /dev/rtc, which is a name
127 bool "RTC UIE emulation on dev interface"
128 depends on RTC_INTF_DEV
130 Provides an emulation for RTC_UIE if the underlying rtc chip
132 once-per-second update interrupts, used for synchronization.
142 RTC test driver. It's a software RTC which can be
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.
248 manufacturing or a bootloader).
250 The first seven registers on these chips hold an RTC, and other
251 registers may add features such as NVRAM, a trickle charger for
253 sysfs, but other chip features may not be available.
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
263 The DS1307 driver suffered from a bug where it was enabling the
267 the time was previously set using a kernel predating this option,
268 reading the date will return a date in the next century.
269 To solve that, you could boot a kernel without this option set, set
270 the RTC date and then boot a kernel with this option set.
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.
295 Dallas/Maxim DS1672 timekeeping chip.
297 This driver can also be built as a module. If so, the module
298 will be called rtc-ds1672.
302 depends on OF
304 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
305 from the usual rtc functions it provides a clock output 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
321 Maxim MAX6900 I2C RTC chip.
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.
389 depends on ARCH_ROCKCHIP
394 This driver can also be built as a module. If so, the module
395 will be called rtc-rockchip.
403 This driver can also be built as a module. If so, the module
404 will be called rtc-rs5c372.
410 Intersil ISL1208 RTC chip.
412 This driver can also be built as a module. If so, the module
413 will be called rtc-isl1208.
419 Intersil ISL12022 RTC chip.
421 This driver can also be built as a module. If so, the module
422 will be called rtc-isl12022.
426 depends on OF || COMPILE_TEST
429 Intersil ISL12026 RTC chip.
431 This driver can also be built as a module. If so, the module
432 will be called rtc-isl12026.
438 Xicor/Intersil X1205 RTC chip.
440 This driver can also be built as a module. If so, the module
441 will be called rtc-x1205.
449 This driver can also be built as a module. If so, the module
450 will be called rtc-pcf8523.
456 If you say yes here you get support for the PCF85063 RTC chip
458 This driver can also be built as a module. If so, the module
459 will be called rtc-pcf85063.
465 If you say yes here you get support for the PCF85363 RTC chip.
467 This driver can also be built as a module. If so, the module
468 will be called rtc-pcf85363.
470 The nvmem interface will be named pcf85363-#, where # is the
471 zero-based instance number.
477 Philips PCF8563 RTC chip. The Epson RTC8564
480 This driver can also be built as a module. If so, the module
481 will be called rtc-pcf8563.
487 RTC chip found on Acorn RiscPCs. This driver supports the
489 the RTC's SRAM. It will work on other platforms with the same
490 chip, but the year will probably have to be tweaked.
492 This driver can also be built as a module. If so, the module
493 will be called rtc-pcf8583.
503 This driver can also be built as a module. If so, the module
504 will be called rtc-m41t80.
508 depends on RTC_DRV_M41T80
515 depends on MFD_ROHM_BD70528 && (BD70528_WATCHDOG || !BD70528_WATCHDOG)
518 block on ROHM BD70528 and BD71828 Power Management IC.
520 This driver can also be built as a module. If so, the module
521 will be called rtc-bd70528.
527 BQ32000 I2C RTC chip.
529 This driver can also be built as a module. If so, the module
530 will be called rtc-bq32k.
534 depends on MFD_DM355EVM_MSP
536 Supports the RTC firmware in the MSP430 on the DM355 EVM.
540 depends on MENELAUS
542 If you say yes here you get support for the RTC on the
543 TWL92330 "Menelaus" power management chip, used with OMAP2
549 depends on TWL4030_CORE
550 depends on OF
552 If you say yes here you get support for the RTC on the
555 This driver can also be built as a module. If so, the module
556 will be called rtc-twl.
560 depends on MFD_PALMAS
565 This driver can also be built as a module. If so, the module
566 will be called rtc-palma.
570 depends on MFD_TPS6586X
578 depends on MFD_TPS65910
580 If you say yes here you get support for the RTC on the
583 This driver can also be built as a module. If so, the module
584 will be called rtc-tps65910.
588 depends on MFD_TPS80031
596 depends on MFD_RC5T583
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-rc5t583.
606 depends on MFD_RN5T618
608 If you say yes here you get support for the RTC on the
611 This driver can also be built as a module. If so, the module
612 will be called rtc-rc5t619.
615 tristate "Seiko Instruments S-35390A"
619 Instruments S-35390A.
621 This driver can also be built as a module. If so the module
622 will be called rtc-s35390a.
629 Ramtron FM3130 is a chip with two separate devices inside,
632 This driver can also be built as a module. If so the module
633 will be called rtc-fm3130.
640 chip.
642 This driver can also be built as a module. If so, the module
643 will be called rtc-rx8010.
646 tristate "Epson RX-8571/RX-8581"
649 If you say yes here you will get support for the Epson RX-8571/
650 RX-8581.
652 This driver can also be built as a module. If so the module
653 will be called rtc-rx8581.
656 tristate "Epson RX-8025SA/NB"
659 RX-8025SA/NB RTC chips.
661 This driver can also be built as a module. If so, the module
662 will be called rtc-rx8025.
670 This driver can also be built as a module. If so, the module
671 will be called rtc-em3027.
680 This driver can also be built as a module. If so, the module
681 will be called rtc-rv3028.
690 This driver can also be built as a module. If so, the module
691 will be called rtc-rv3032.
699 This driver can also be built as a module. If so, the module
700 will be called rtc-rv8803.
704 depends on MFD_SEC_CORE || COMPILE_TEST
711 This driver can also be built as a module. If so, the module
712 will be called rtc-s5m.
721 This driver can also be built as a module. If so, the module
722 will be called rtc-sd3078
734 ST M41T93 SPI RTC chip.
736 This driver can also be built as a module. If so, the module
737 will be called rtc-m41t93.
743 ST M41T94 SPI RTC chip.
745 This driver can also be built as a module. If so, the module
746 will be called rtc-m41t94.
750 depends on SPI
754 This driver can also be built as a module. If so, the module
755 will be called rtc-ds1302.
761 and DS1306 real time clock chips. These support a trickle
764 This driver can also be built as a module. If so, the module
765 will be called rtc-ds1305.
775 This driver can also be built as a module. If so, the module
776 will be called rtc-ds1343.
785 This driver only supports the RTC feature, and not other chip
788 This driver can also be built as a module. If so, the module
789 will be called rtc-ds1347.
798 other chip features such as alarms.
800 This driver can also be built as a module. If so, the module
801 will be called rtc-ds1390.
807 Maxim MAX6916 SPI RTC chip.
809 This driver only supports the RTC feature, and not other chip
812 This driver can also be built as a module. If so, the module
813 will be called rtc-max6916.
816 tristate "Epson RTC-9701JE"
819 Epson RTC-9701JE SPI RTC chip.
821 This driver can also be built as a module. If so, the module
822 will be called rtc-r9701.
825 tristate "Epson RX-4581"
827 If you say yes here you will get support for the Epson RX-4581.
829 This driver can also be built as a module. If so the module
830 will be called rtc-rx4581.
833 tristate "Epson RX-6110"
836 If you say yes here you will get support for the Epson RX-6610.
838 This driver can also be built as a module. If so the module
839 will be called rtc-rx6110.
847 This driver can also be built as a module. If so, the module
848 will be called rtc-rs5c348.
854 Maxim MAX6902 SPI RTC chip.
856 This driver can also be built as a module. If so, the module
857 will be called rtc-max6902.
864 RTC chip.
866 This driver can also be built as a module. If so, the module
867 will be called rtc-pcf2123.
874 This driver can also be built as a module. If so the module
875 will be called rtc-mcp795.
893 depends on RTC_I2C_AND_SPI
898 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
901 This driver can also be built as a module. If so, the module
902 will be called rtc-ds3232.
906 depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
909 Say Y here if you want to expose temperature sensor data on
910 rtc-ds3232
914 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-pcf2127.
932 depends on RTC_I2C_AND_SPI
939 This driver can also be built as a module. If so, the module
940 will be called rtc-rv3029c2.
944 depends on RTC_DRV_RV3029C2 && HWMON
945 depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
948 Say Y here if you want to expose temperature sensor data on
949 rtc-rv3029.
954 # <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
958 tristate "PC-style 'CMOS'"
959 depends on X86 || ARM || PPC || MIPS || SPARC64
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
983 Direct support for the real-time clock found on every Alpha
984 system, specifically MC146818 compatibles. If in doubt, say Y.
988 depends on X86_INTEL_MID
993 found on Moorestown platforms. The VRTC is a emulated RTC that
994 derives its clock source from a real RTC in the PMIC. The MC146818
996 updates are done via IPC calls to the system controller FW.
1000 depends on SNI_RM
1006 depends on HAS_IOMEM
1012 depends on HAS_IOMEM
1015 Dallas DS1511 timekeeping/watchdog chip.
1017 This driver can also be built as a module. If so, the module
1018 will be called rtc-ds1511.
1022 depends on HAS_IOMEM
1025 Maxim/Dallas DS1553 timekeeping chip.
1027 This driver can also be built as a module. If so, the module
1028 will be called rtc-ds1553.
1038 This driver can also be built as a module. If so, the module
1039 will be called rtc-ds1685.
1043 depends on RTC_DRV_DS1685_FAMILY
1050 clock chip.
1052 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
1053 systems, as well as EPPC-405-UC modules by electronic system design
1060 clock chip.
1062 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
1063 which supports a few minor features such as Vcc, Vbat, and Power
1064 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
1074 clock chip.
1076 This chip features 2kb of extended NV-SRAM. It may possibly be
1083 clock chip.
1085 This chip features 4kb of extended NV-SRAM.
1091 clock chip.
1093 This chip features 8kb of extended NV-SRAM.
1099 depends on HAS_IOMEM
1102 Maxim/Dallas DS1742/1743 timekeeping chip.
1104 This driver can also be built as a module. If so, the module
1105 will be called rtc-ds1742.
1111 Dallas DS2404 RTC chip.
1113 This driver can also be built as a module. If so, the module
1114 will be called rtc-ds2404.
1118 depends on PMIC_DA9052
1121 DA9052-BC and DA9053-AA/Bx PMICs.
1125 depends on MFD_DA9055
1130 This driver can also be built as a module. If so, the module
1131 will be called rtc-da9055
1135 depends on MFD_DA9063 || MFD_DA9062
1140 This driver can also be built as a module. If so, the module
1141 will be called "rtc-da9063".
1145 depends on EFI && !X86
1150 This driver can also be built as a module. If so, the module
1151 will be called rtc-efi.
1155 depends on HAS_IOMEM
1158 Simtek STK17TA8 timekeeping chip.
1160 This driver can also be built as a module. If so, the module
1161 will be called rtc-stk17ta8.
1169 This driver can also be built as a module. If so, the module
1170 will be called rtc-m48t86.
1174 depends on HAS_IOMEM
1177 ST M48T35 RTC chip.
1179 This driver can also be built as a module, if so, the module
1180 will be called "rtc-m48t35".
1184 depends on HAS_IOMEM
1187 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1192 This driver can also be built as a module, if so, the module
1193 will be called "rtc-m48t59".
1197 depends on HAS_IOMEM
1200 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1202 This driver can also be built as a module. If so, the module
1203 will be called rtc-msm6242.
1207 depends on HAS_IOMEM
1210 BQ4802 RTC chip.
1212 This driver can also be built as a module. If so, the module
1213 will be called rtc-bq4802.
1217 depends on HAS_IOMEM
1220 timekeeping chip. It is used in some Amiga models (e.g. A3000
1223 This driver can also be built as a module. If so, the module
1224 will be called rtc-rp5c01.
1230 EM Microelectronic v3020 RTC chip.
1232 This driver can also be built as a module. If so, the module
1233 will be called rtc-v3020.
1237 depends on MFD_WM831X
1242 This driver can also be built as a module. If so, the module
1243 will be called "rtc-wm831x".
1247 depends on MFD_WM8350
1252 This driver can also be built as a module. If so, the module
1253 will be called "rtc-wm8350".
1257 depends on MFD_SC27XX_PMIC || COMPILE_TEST
1263 This driver can also be built as a module. If so, the module
1264 will be called rtc-sc27xx.
1268 depends on PLAT_SPEAR || COMPILE_TEST
1271 If you say Y here you will get support for the RTC found on
1275 depends on MFD_PCF50633
1282 tristate "ST-Ericsson AB3100 RTC"
1283 depends on AB3100_CORE
1286 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1287 support. This chip contains a battery- and capacitor-backed RTC.
1290 tristate "ST-Ericsson AB8500 RTC"
1291 depends on AB8500_CORE
1295 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1296 support. This chip contains a battery- and capacitor-backed RTC.
1300 depends on PPC_POWERNV
1304 driver based on OPAL interfaces.
1306 This driver can also be built as a module. If so, the module
1307 will be called rtc-opal.
1311 depends on OF && HAS_IOMEM
1313 If you say yes here you get support for the RTC controller found on
1318 depends on CROS_EC
1323 This driver can also be built as a module. If so, the module
1324 will be called rtc-cros-ec.
1326 comment "on-CPU RTC drivers"
1330 depends on MACH_ASM9260 || 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-asm9260.
1340 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1342 If you say yes here you get support for the RTC on the
1345 This driver can also be built as a module. If so, the module
1346 will be called rtc-davinci.
1350 depends on ARCH_DIGICOLOR || COMPILE_TEST
1352 If you say yes here you get support for the RTC on Conexant
1355 This driver can also be built as a module. If so, the module
1356 will be called rtc-digicolor.
1360 depends on ARCH_MXC
1364 This driver can also be built as a module, if so, the module
1365 will be called "rtc-imxdi".
1369 depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST
1375 alarm functions for wakeup system from deep sleep.
1377 This driver can also be built as a module, if so, the module
1378 will be called "rtc-fsl-ftm-alarm".
1382 depends on (ARM && ARCH_MESON) || COMPILE_TEST
1385 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1388 This driver can also be built as a module, if so, the module
1389 will be called "rtc-meson".
1393 depends on ARCH_MESON || COMPILE_TEST
1399 This driver can also be built as a module. If so, the module
1400 will be called rtc-meson-vrtc.
1404 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1405 depends on OF
1406 depends on PINCTRL
1409 Say "yes" here to support the on chip real time clock
1410 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1412 This driver can also be built as a module, if so, module
1413 will be called rtc-omap.
1420 select this in the respective mach-XXXX/Kconfig file.
1424 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
1431 The driver currently supports the common features on all the
1435 This driver can also be build as a module. If so, the module
1436 will be called rtc-s3c.
1440 depends on ARCH_EP93XX || COMPILE_TEST
1445 This driver can also be built as a module. If so, the module
1446 will be called rtc-ep93xx.
1450 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1455 To compile this driver as a module, choose M here: the
1456 module will be called rtc-sa1100.
1459 tristate "SuperH On-Chip RTC"
1460 depends on SUPERH || ARCH_RENESAS
1462 Say Y here to enable support for the on-chip RTC found in
1463 most SuperH processors. This RTC is also found in RZ/A SoCs.
1465 To compile this driver as a module, choose M here: the
1466 module will be called rtc-sh.
1470 depends on CPU_VR41XX || COMPILE_TEST
1475 To compile this driver as a module, choose M here: the
1476 module will be called rtc-vr41xx.
1480 depends on ARM_AMBA
1483 PrimeCell PL030 RTC found on certain ARM SOCs.
1485 To compile this driver as a module, choose M here: the
1486 module will be called rtc-pl030.
1490 depends on ARM_AMBA
1493 PrimeCell PL031 RTC found on certain ARM SOCs.
1495 To compile this driver as a module, choose M here: the
1496 module will be called rtc-pl031.
1500 depends on ARCH_AT91 || COMPILE_TEST
1501 depends on OF
1503 Driver for the internal RTC (Realtime Clock) module found on
1504 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
1509 depends on ARCH_AT91 || COMPILE_TEST
1510 depends on OF && HAS_IOMEM
1514 can be used as an RTC thanks to the backup power supply (e.g. a
1518 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1524 depends on MIPS_ALCHEMY
1526 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1527 counter) to be used as a RTC.
1529 This driver can also be built as a module. If so, the module
1530 will be called rtc-au1xxx.
1534 depends on SH_LANDISK
1540 # Please consider writing a new RTC driver instead of using the generic
1542 depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST
1544 Say Y or M here to enable RTC support on systems using the generic
1550 depends on ARCH_PXA
1562 depends on ARCH_VT8500 || COMPILE_TEST
1570 depends on SPARC64
1573 based RTC on SUN4V systems.
1578 depends on COMMON_CLK
1579 depends on ARCH_SUNXI || COMPILE_TEST
1586 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1588 If you say Y here you will get support for the RTC found on
1593 depends on SPARC64
1595 If you say Y here you will get support for the RTC found on
1600 depends on SOC_TX4939 || COMPILE_TEST
1602 Driver for the internal RTC (Realtime Clock) module found on
1607 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1609 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 rtc-mv.
1618 depends on ARCH_MVEBU || COMPILE_TEST
1620 If you say yes here you will get support for the in-chip RTC
1623 This driver can also be built as a module. If so, the module
1624 will be called armada38x-rtc.
1628 depends on OF && HAS_IOMEM
1631 found on certain SOCs.
1633 To compile this driver as a module, choose M here: the
1634 module will be called rtc-cadence.
1638 depends on HAS_IOMEM
1642 Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1644 This driver can also be built as a module. If so, the module
1645 will be called rtc-ftrtc010.
1649 depends on PPC_PS3
1651 If you say yes here you will get support for the RTC on PS3.
1653 This driver can also be built as a module. If so, the module
1654 will be called rtc-ps3.
1657 tristate "ST-Ericsson COH 901 331 RTC"
1658 depends on ARCH_U300 || COMPILE_TEST
1660 If you say Y here you will get access to ST-Ericsson
1661 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1664 This driver can also be built as a module. If so, the module
1665 will be called "rtc-coh901331".
1670 depends on ARCH_MXS || COMPILE_TEST
1676 This driver can also be built as a module. If so, the module
1677 will be called rtc-stmp3xxx.
1681 depends on EZX_PCAP
1683 If you say Y here you will get support for the RTC found on
1684 the PCAP2 ASIC used on some Motorola phones.
1687 depends on MFD_MC13XXX
1690 This enables support for the RTCs found on Freescale's PMICs
1694 tristate "Freescale MPC5121 built-in RTC"
1695 depends on PPC_MPC512x || PPC_MPC52xx
1698 built-in RTC on MPC5121 or on MPC5200.
1700 This driver can also be built as a module. If so, the module
1701 will be called rtc-mpc5121.
1705 depends on MIPS || COMPILE_TEST
1706 depends on OF
1711 This driver can also be built as a module. If so, the module
1712 will be called rtc-jz4740.
1716 depends on ARCH_LPC18XX || COMPILE_TEST
1717 depends on OF && HAS_IOMEM
1719 This enables support for the NXP RTC found which can be found on
1723 the hardware RTC. This driver can also be built as a module. If
1724 so, the module will be called rtc-lpc24xx.
1727 depends on ARCH_LPC32XX || COMPILE_TEST
1732 This driver can also be built as a module. If so, the module
1733 will be called rtc-lpc32xx.
1737 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1742 To compile this driver as a module, choose M here: the
1743 module will be called rtc-pm8xxx.
1747 depends on ARCH_TEGRA || COMPILE_TEST
1752 This drive can also be built as a module. If so, the module
1753 will be called rtc-tegra.
1757 depends on MACH_LOONGSON32
1759 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1760 counter) to be used as a RTC.
1762 This driver can also be built as a module. If so, the module
1763 will be called rtc-ls1x.
1767 depends on ARCH_MXC
1772 This driver can also be built as a module, if so, the module
1773 will be called "rtc-mxc".
1777 depends on ARCH_MXC
1782 This driver can also be built as a module, if so, the module
1783 will be called "rtc-mxc_v2".
1788 depends on ARCH_MXC || COMPILE_TEST
1789 depends on HAS_IOMEM
1790 depends on OF
1795 This driver can also be built as a module, if so, the module
1796 will be called "rtc-snvs".
1799 depends on IMX_SCU
1800 depends on HAVE_ARM_SMCCC
1801 tristate "NXP i.MX System Controller RTC support"
1803 If you say yes here you get support for the NXP i.MX System
1808 depends on ARCH_SIRF
1810 Say "yes" here to support the real time clock on SiRF SOC chips.
1811 This driver can also be built as a module called rtc-sirfsoc.
1815 depends on ARCH_STI
1816 depends on OF
1821 To compile this driver as a module, choose M here: the
1822 module will be called rtc-st-lpc.
1826 depends on ARCH_MOXART || COMPILE_TEST
1831 This driver can also be built as a module. If so, the module
1832 will be called rtc-moxart
1836 depends on ARCH_MEDIATEK || COMPILE_TEST
1841 This drive can also be built as a module. If so, the module
1842 will be called rtc-mt2712.
1846 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1856 depends on ARCH_MEDIATEK || COMPILE_TEST
1861 This drive can also be built as a module. If so, the module
1862 will be called rtc-mt7622.
1865 tristate "APM X-Gene RTC"
1866 depends on HAS_IOMEM
1867 depends on ARCH_XGENE || COMPILE_TEST
1869 If you say yes here you get support for the APM X-Gene SoC real time
1872 This driver can also be built as a module, if so, the module
1873 will be called "rtc-xgene".
1877 depends on MACH_PIC32
1882 This driver can also be built as a module. If so, the module
1883 will be called rtc-pic32
1886 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1888 depends on OF && HAS_IOMEM
1891 RTC-7301SF/DG chips.
1893 This driver can also be built as a module. If so, the module
1894 will be called rtc-r7301.
1899 depends on ARCH_STM32 || COMPILE_TEST
1901 If you say yes here you get support for the STM32 On-Chip
1904 This driver can also be built as a module, if so, the module
1905 will be called "rtc-stm32".
1908 depends on MFD_CPCAP
1911 Say y here for CPCAP rtc found on some Motorola phones
1916 depends on ARCH_REALTEK || COMPILE_TEST
1924 depends on OF
1925 depends on ARCH_ASPEED || COMPILE_TEST
1930 This driver can also be built as a module, if so, the module
1931 will be called "rtc-aspeed".
1937 depends on USB_HID
1938 depends on HID_SENSOR_HUB && IIO
1944 If this driver is compiled as a module, it will be named
1945 rtc-hid-sensor-time.
1949 depends on OF && HAS_IOMEM
1950 depends on GOLDFISH || COMPILE_TEST
1954 Goldfish is a code name for the virtual platform developed by Google
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