Lines Matching full:rtc

3 # RTC class/drivers configuration
19 	  Generic RTC class support. If you say yes here, you will
26 	bool "Set system time from RTC on startup and resume"
30 	  the value read from a specified RTC device. This is useful to avoid
34 	string "RTC used to set the system time"
38 	  The RTC device that will be used to (re)initialize the system
50 	  sleep states. Do not specify an RTC here unless it stays powered
54 	bool "Set the RTC time based on NTP synchronization"
58 	  in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
62 	string "RTC used to synchronize NTP adjustment"
67 	  The RTC device used for NTP synchronization. The main difference
73 	bool "RTC debug support"
75 	  Say yes here to enable debugging support in the RTC framework
76 	  and individual RTC drivers.
79 	tristate "KUnit test for RTC lib functions" if !KUNIT_ALL_TESTS
83 	  Enable this option to test RTC library functions.
88 	bool "RTC non volatile storage support"
95 comment "RTC interfaces"
98 	bool "/sys/class/rtc/rtcN (sysfs)"
103 	  /sys/class/rtc/rtc0 through /sys/.../rtcN.
108 	bool "/proc/driver/rtc (procfs for rtcN)"
112 	  Say yes here if you want to use your system clock RTC through
113 	  the proc interface, /proc/driver/rtc.
115 	  If there is no RTC for the system clock, then the first RTC(rtc0)
129 	  can be accessed as /dev/rtc, which is a name
136 	bool "RTC UIE emulation on dev interface"
139 	  Provides an emulation for RTC_UIE if the underlying rtc chip
151 	  RTC test driver. It's a software RTC which can be
152 	  used to test the RTC subsystem APIs. It gets
155 	  on the RTC subsystem. Please read the source code
159 	  will be called rtc-test.
161 comment "I2C RTC drivers"
169 	  If you say yes here you get support for RTC function in Marvell
173 	  will be called rtc-88pm860x.
179 	  If you say yes here you get support for RTC function in Marvell
183 	  will be called rtc-88pm80x.
186 	tristate "Marvell 88PM886 RTC driver"
189 	  If you say yes here you will get support for the RTC function in the
193 	  will be called rtc-88pm886.
200 	  AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
203 	  will be called rtc-ab-b5ze-s3.
210 	  AB-RTCMC-32.768kHz-EOA9 I2C RTC chip.
213 	  will be called rtc-ab-e0z9.
224 	  will be called rtc-abx80x.
234 	  will be called rtc-ac100.
245 	  be called rtc-brcmstb-waketimer.
248 	tristate "ams AS3722 RTC driver"
251 	  If you say yes here you get support for the RTC of ams AS3722 PMIC
255 	  will be called rtc-as3722.
262 	  If you say yes here you get support for various compatible RTC
266 	  In some cases the RTC must already have been initialized (by
269 	  The first seven registers on these chips hold an RTC, and other
271 	  the RTC/NVRAM backup power, and alarms. NVRAM is visible in
275 	  will be called rtc-ds1307.
278 	bool "Century bit support for rtc-ds1307"
289 	  the RTC date and then boot a kernel with this option set.
299 	  will be called rtc-ds1374.
317 	  will be called rtc-ds1672.
323 	  Say Y to enable support for the HYM8563 I2C RTC chip. Apart
324 	  from the usual rtc functions it provides a clock output of
328 	  will be called rtc-hym8563.
331 	tristate "TI LP8788 RTC driver"
334 	  Say Y to enable support for the LP8788 RTC/ALARM driver.
340 	  Maxim MAX6900 I2C RTC chip.
343 	  will be called rtc-max6900.
351 	  RTC of Maxim MAX8907 PMIC.
354 	  will be called rtc-max8907.
361 	  RTC of Maxim MAX8925 PMIC.
364 	  will be called rtc-max8925.
371 	  RTC of Maxim MAX8998 PMIC.
374 	  will be called rtc-max8998.
381 	  RTC of Maxim MAX8997 PMIC.
384 	  will be called rtc-max8997.
397 	  will be called rtc-max31335.
404 	  RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
407 	  will be called rtc-max77686.
410 	tristate "SpacemiT P1 RTC"
415 	  Enable support for the RTC function in the SpacemiT P1 PMIC.
417 	  "spacemit-p1-rtc".
423 	   If you say yes here you get support for the Nuvoton NCT3018Y I2C RTC
427 	   called "rtc-nct3018y".
430 	tristate "Nuvoton NCT6694 RTC support"
434 	  NCT6694, a USB device to RTC.
437 	  be called rtc-nct6694.
440 	tristate "Rockchip RK805/RK808/RK809/RK817/RK818 RTC"
444 	  RTC of RK805, RK809 and RK817, RK808 and RK818 PMIC.
447 	  will be called rk808-rtc.
453 	  Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
456 	  will be called rtc-rs5c372.
462 	  Intersil ISL1208 RTC chip.
465 	  will be called rtc-isl1208.
472 	  Intersil ISL12022 RTC chip.
475 	  will be called rtc-isl12022.
482 	  Intersil ISL12026 RTC chip.
485 	  will be called rtc-isl12026.
491 	  Xicor/Intersil X1205 RTC chip.
494 	  will be called rtc-x1205.
500 	  If you say yes here you get support for the NXP PCF8523 RTC
504 	  will be called rtc-pcf8523.
510 	  If you say yes here you get support for the PCF85363 RTC chip.
513 	  will be called rtc-pcf85363.
523 	  Philips PCF8563 RTC chip. The Epson RTC8564
527 	  will be called rtc-pcf8563.
533 	  RTC chip found on Acorn RiscPCs. This driver supports the
535 	  the RTC's SRAM. It will work on other platforms with the same
539 	  will be called rtc-pcf8583.
545 	  and M41T80 RTC chips series. Currently, the following chips are
550 	  will be called rtc-m41t80.
553 	bool "ST M41T65/M41T80 series RTC watchdog timer"
557 	  watchdog timer in the ST M41T60 and M41T80 RTC chips series.
560 	tristate "ROHM BD71815 and BD71828 PMIC RTC"
563 	  If you say Y here you will get support for the RTC
567 	  will be called rtc-bd70528.
573 	  BQ32000 I2C RTC chip.
576 	  will be called rtc-bq32k.
582 	  If you say yes here you get support for the RTC on the
592 	  If you say yes here you get support for the RTC on the
596 	  will be called rtc-twl.
599 	tristate "TI Palmas RTC driver"
602 	  If you say yes here you get support for the RTC of TI PALMA series PMIC
606 	  will be called rtc-palma.
609 	tristate "TI TPS6586X RTC driver"
612 	  TI Power Management IC TPS6586X supports RTC functionality
613 	  along with alarm. This driver supports the RTC driver for
614 	  the TPS6586X RTC module.
617 	tristate "TI TPS6594 RTC driver"
621 	  TI Power Management IC TPS6594 supports RTC functionality
622 	  along with alarm. This driver supports the RTC driver for
623 	  the TPS6594 RTC module.
626 	  will be called rtc-tps6594.
629 	tristate "TI TPS65910 RTC driver"
632 	  If you say yes here you get support for the RTC on the
636 	  will be called rtc-tps65910.
639 	tristate "RICOH 5T583 RTC driver"
642 	  If you say yes here you get support for the RTC on the
646 	  will be called rtc-rc5t583.
649 	tristate "RICOH RC5T619 RTC driver"
652 	  If you say yes here you get support for the RTC on the
656 	  will be called rtc-rc5t619.
666 	  will be called rtc-s35390a.
672 	  Ramtron FM3130 RTC chips.
674 	  RTC clock and FRAM. This driver provides only RTC functionality.
677 	  will be called rtc-fm3130.
683 	  If you say yes here you get support for the Epson RX8010SJ RTC
687 	  will be called rtc-rx8010.
694 	  If you say yes here you will get support for the Epson RX8111 RTC.
697 	  called rtc-rx8111.
707 	  will be called rtc-rx8581.
713 	  RX-8025SA/NB RTC chips.
716 	  will be called rtc-rx8025.
722 	  Microelectronic EM3027 RTC chips.
725 	  will be called rtc-em3027.
735 	  will be called rtc-rv3028.
745 	  will be called rtc-rv3032.
751 	  Epson RX8900 RTC chips.
754 	  will be called rtc-rv8803.
763 	  RTC of Samsung S2MPS14 and S5M PMIC series.
766 	  will be called rtc-s5m.
773 	  DFRobot SD2405AL I2C RTC Module.
776 	  will be called rtc-sd2405al.
783 	  SD3078 RTC chips.
786 	  will be called rtc-sd3078
790 comment "SPI RTC drivers"
798 	  ST M41T93 SPI RTC chip.
801 	  will be called rtc-m41t93.
807 	  ST M41T94 SPI RTC chip.
810 	  will be called rtc-m41t94.
816 	  If you say yes here you get support for the Dallas DS1302 RTC chips.
819 	  will be called rtc-ds1302.
829 	  will be called rtc-ds1305.
840 	  will be called rtc-ds1343.
849 	  This driver only supports the RTC feature, and not other chip
853 	  will be called rtc-ds1347.
861 	  This driver supports the RTC feature and trickle charging but not
865 	  will be called rtc-ds1390.
871 	  Maxim MAX6916 SPI RTC chip.
873 	  This driver only supports the RTC feature, and not other chip
877 	  will be called rtc-max6916.
880 	tristate "Epson RTC-9701JE"
883 	  Epson RTC-9701JE SPI RTC chip.
886 	  will be called rtc-r9701.
894 	  will be called rtc-rx4581.
900 	  Ricoh RS5C348A and RS5C348B RTC chips.
903 	  will be called rtc-rs5c348.
909 	  Maxim MAX6902 SPI RTC chip.
912 	  will be called rtc-max6902.
919 	  RTC chip.
922 	  will be called rtc-pcf2123.
930 	  will be called rtc-mcp795.
944 comment "SPI and I2C RTC drivers"
957 	  will be called rtc-ds3232.
965 	  rtc-ds3232
974 	  If you say yes here you get support for the NXP PCF2127/29/31 RTC
983 	  will be called rtc-pcf2127.
992 	  RTC chips.
995 	  will be called rtc-pcf85063.
1004 	  RV3029 and RV3049 RTC chips.
1007 	  will be called rtc-rv3029c2.
1016 	  rtc-rv3029.
1027 	  will be called rtc-rx6110.
1029 comment "Platform RTC drivers"
1031 # this 'CMOS' RTC driver is arch dependent because it requires
1054 	  will be called rtc-cmos.
1070 	  If you say yes here you get support for the Dallas DS1216 RTC chips.
1076 	  If you say yes here you get support for the Dallas DS1286 RTC chips.
1086 	  will be called rtc-ds1511.
1096 	  will be called rtc-ds1553.
1108 	  will be called rtc-ds1685.
1131 	  This is an older RTC chip, supplanted by the DS1685/DS1687 above,
1135 	  It also works for the even older DS1688/DS1691 RTC chips, which are
1174 	  will be called rtc-ds1742.
1180 	  Dallas DS2404 RTC chip.
1183 	  will be called rtc-ds2404.
1186 	tristate "Dialog DA9052/DA9053 RTC"
1189 	  Say y here to support the RTC driver for Dialog Semiconductor
1193 	tristate "Dialog Semiconductor DA9055 RTC"
1197 	  RTC of the Dialog DA9055 PMIC.
1200 	  will be called rtc-da9055
1203 	tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1206 	  If you say yes here you will get support for the RTC subsystem
1210 	  will be called "rtc-da9063".
1213 	tristate "EFI RTC"
1220 	  will be called rtc-efi.
1230 	  will be called rtc-stk17ta8.
1237 	  ST M48T86 and Dallas DS12887 RTC chips.
1240 	  will be called rtc-m48t86.
1247 	  ST M48T35 RTC chip.
1250 	  will be called "rtc-m48t35".
1257 	  ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1263 	  will be called "rtc-m48t59".
1273 	  will be called rtc-msm6242.
1281 	  BQ4802 RTC chip.
1284 	  will be called rtc-bq4802.
1295 	  will be called rtc-rp5c01.
1298 	tristate "Nintendo GameCube, Wii and Wii U RTC"
1302 	  If you say yes here you will get support for the RTC subsystem
1306 	  will be called "rtc-gamecube".
1309 	tristate "Wolfson Microelectronics WM831x RTC"
1312 	  If you say yes here you will get support for the RTC subsystem
1316 	  will be called "rtc-wm831x".
1319 	tristate "Wolfson Microelectronics WM8350 RTC"
1322 	  If you say yes here you will get support for the RTC subsystem
1326 	  will be called "rtc-wm8350".
1329 	tristate "Spreadtrum SC27xx RTC"
1332 	  If you say Y here you will get support for the RTC subsystem
1337 	  will be called rtc-sc27xx.
1340 	tristate "SPEAR ST RTC"
1344 	 If you say Y here you will get support for the RTC found on
1348 	tristate "ST-Ericsson AB8500 RTC"
1353 	  Select this to enable the ST-Ericsson AB8500 power management IC RTC
1354 	  support. This chip contains a battery- and capacitor-backed RTC.
1357 	tristate "IBM OPAL RTC driver"
1361 	  If you say yes here you get support for the PowerNV platform RTC
1365 	  will be called rtc-opal.
1368 	tristate "OP-TEE based RTC driver"
1371 	  Select this to get support for OP-TEE based RTC control on SoCs where
1372 	  RTC are not accessible to the normal world (Linux).
1375 	  will be called rtc-optee.
1378 	tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1381 	  If you say yes here you get support for the RTC controller found on
1385 	tristate "Chrome OS EC RTC driver"
1389 	  Chrome OS Embedded Controller's RTC.
1392 	  will be called rtc-cros-ec.
1395 	tristate "Netronix embedded controller RTC"
1398 	  Say yes here if you want to support the RTC functionality of the
1402 comment "on-CPU RTC drivers"
1405 	tristate "Alphascale asm9260 RTC"
1408 	  If you say yes here you get support for the RTC on the
1412 	  will be called rtc-asm9260.
1415 	tristate "Sophgo CV1800 RTC"
1420 	  If you say yes here you get support the RTC driver for Sophgo CV1800
1424 	  called rtc-cv1800.
1427 	tristate "Conexant Digicolor RTC"
1430 	  If you say yes here you get support for the RTC on Conexant
1434 	  will be called rtc-digicolor.
1441 	   Support for Freescale IMX DryIce RTC
1444 	   will be called "rtc-imxdi".
1457 	   will be called "rtc-fsl-ftm-alarm".
1460 	tristate "Amlogic Meson RTC"
1464 	   Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1468 	   will be called "rtc-meson".
1471 	tristate "Amlogic Meson Virtual RTC"
1476 	  Virtual RTC of Amlogic SoCs.
1479 	  will be called rtc-meson-vrtc.
1492 	  will be called rtc-omap.
1495 	tristate "Samsung S3C series SoC RTC"
1499 	  RTC (Realtime Clock) driver for the clock inbuilt into the
1505 	  will be called rtc-s3c.
1512 	  RTC embedded in the Cirrus Logic EP93XX processors.
1515 	  will be called rtc-ep93xx.
1525 	  module will be called rtc-sa1100.
1528 	tristate "SuperH On-Chip RTC"
1531 	  Say Y here to enable support for the on-chip RTC found in
1532 	  most SuperH processors. This RTC is also found in RZ/A SoCs.
1535 	  module will be called rtc-sh.
1538 	tristate "Sunplus SP7021 RTC"
1543 	  RTC status check, timer/alarm functionalities, user data
1544 	  reservation with the battery over 2.5V, RTC power status check
1548 	  will be called rtc-sunplus.
1551 	tristate "ARM AMBA PL030 RTC"
1555 	  PrimeCell PL030 RTC found on certain ARM SOCs.
1558 	  module will be called rtc-pl030.
1561 	tristate "ARM AMBA PL031 RTC"
1565 	  PrimeCell PL031 RTC found on certain ARM SOCs.
1568 	  module will be called rtc-pl031.
1571 	tristate "AT91RM9200 or some AT91SAM9 RTC"
1575 	  Driver for the internal RTC (Realtime Clock) module found on
1580 	tristate "AT91SAM9 RTT as RTC"
1586 	  can be used as an RTC thanks to the backup power supply (e.g. a
1590 	  Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1591 	  probably want to use the real RTC block instead of the "RTT as an
1592 	  RTC" driver.
1595 	tristate "Au1xxx Counter0 RTC support"
1599 	  counter) to be used as a RTC.
1602 	  will be called rtc-au1xxx.
1608 	  If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1611 	tristate "Renesas RZ/N1 RTC"
1615 	  If you say yes here you get support for the Renesas RZ/N1 RTC.
1618 	tristate "Generic RTC support"
1619 	# Please consider writing a new RTC driver instead of using the generic
1620 	# RTC abstraction
1623 	  Say Y or M here to enable RTC support on systems using the generic
1624 	  RTC abstraction. If you do not know what you are doing, you should
1633 	 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1634 	 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1636 	 This RTC driver uses PXA RTC registers available since pxa27x
1640 	tristate "VIA/WonderMedia 85xx SoC RTC"
1648 	bool "SUN4V Hypervisor RTC"
1652 	  based RTC on SUN4V systems.
1655 	bool "Allwinner A31 RTC"
1660 	  If you say Y here you will get support for the RTC found in
1664 	tristate "Allwinner sun4i/sun7i RTC"
1667 	  If you say Y here you will get support for the RTC found on
1671 	bool "Starfire RTC"
1674 	  If you say Y here you will get support for the RTC found on
1678 	tristate "Marvell SoC RTC"
1681 	  If you say yes here you will get support for the in-chip RTC
1686 	  will be called rtc-mv.
1689 	tristate "Armada 38x Marvell SoC RTC"
1693 	  If you say yes here you will get support for the in-chip RTC
1697 	  will be called armada38x-rtc.
1700 	tristate "Cadence RTC driver"
1703 	  If you say Y here you will get access to Cadence RTC IP
1707 	  module will be called rtc-cadence.
1710 	tristate "Faraday Technology FTRTC010 RTC"
1718 	  will be called rtc-ftrtc010.
1721 	tristate "PS3 RTC"
1724 	  If you say yes here you will get support for the RTC on PS3.
1727 	  will be called rtc-ps3.
1730 	tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1735 	  STMP3xxx/i.MX23/i.MX28 RTC.
1738 	  will be called rtc-stmp3xxx.
1741 	tristate "PCAP RTC"
1744 	  If you say Y here you will get support for the RTC found on
1749 	tristate "Freescale MC13xxx RTC"
1755 	tristate "Freescale MPC5121 built-in RTC"
1759 	  built-in RTC on MPC5121 or on MPC5200.
1762 	  will be called rtc-mpc5121.
1769 	  If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1773 	  will be called rtc-jz4740.
1776 	tristate "Loongson On-chip RTC"
1781 	  counter) to be used as a RTC.
1786 	  will be called rtc-loongson.
1789 	tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1794 	  This enables support for the NXP RTC found which can be found on
1798 	  the hardware RTC. This driver can also be built as a module. If
1799 	  so, the module will be called rtc-lpc24xx.
1803 	tristate "NXP LPC32XX RTC"
1805 	  This enables support for the NXP RTC in the LPC32XX
1808 	  will be called rtc-lpc32xx.
1811 	tristate "Qualcomm PMIC8XXX RTC"
1815 	  Qualcomm PMIC8XXX RTC.
1818 	  module will be called rtc-pm8xxx.
1821 	tristate "NVIDIA Tegra Internal RTC driver"
1825 	  Tegra 200 series internal RTC module.
1828 	  will be called rtc-tegra.
1837 	   RTC module.
1840 	   will be called "rtc-mxc".
1852 	   will be called "rtc-mxc_v2".
1855 	tristate "Freescale SNVS RTC support"
1862 	   Low Power (LP) RTC module.
1865 	   will be called "rtc-snvs".
1868 	tristate "NXP BBNSM RTC support"
1874 	   If you say yes here you get support for the NXP BBNSM RTC module.
1877 	   will be called "rtc-bbnsm".
1882 	tristate "NXP i.MX BBM SCMI RTC support"
1885 	  RTC module.
1888 	  module will be called rtc-imx-sm-bbm.
1893 	tristate "NXP i.MX System Controller RTC support"
1896 	   Controller RTC module.
1899 	tristate "STMicroelectronics LPC RTC"
1904 	  (LPC) based RTC support.
1907 	  module will be called rtc-st-lpc.
1910 	tristate "MOXA ART RTC"
1914 	   RTC module.
1917 	   will be called rtc-moxart
1920 	tristate "MediaTek MT2712 SoC based RTC"
1927 	  will be called rtc-mt2712.
1930 	tristate "MediaTek PMIC based RTC"
1934 	  This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1936 	  MediaTek(R) RTC driver.
1938 	  If you want to use MediaTek(R) RTC interface, select Y or M here.
1941 	tristate "MediaTek SoC based RTC"
1948 	  will be called rtc-mt7622.
1951 	tristate "APM X-Gene RTC"
1959 	  will be called "rtc-xgene".
1962 	tristate "Microchip PIC32 RTC"
1966 	   If you say yes here you get support for the PIC32 RTC module.
1969 	   will be called rtc-pic32
1972 	tristate "EPSON TOYOCOM RTC-7301SF/DG"
1977 	   RTC-7301SF/DG chips.
1980 	   will be called rtc-r7301.
1983 	tristate "STM32 RTC"
1997 	   will be called "rtc-stm32".
2001 	tristate "Motorola CPCAP RTC"
2003 	   Say y here for CPCAP rtc found on some Motorola phones
2007 	bool "Realtek RTD129x RTC"
2015 	tristate "ASPEED RTC"
2023 	  will be called "rtc-aspeed".
2026 	tristate "TI K3 RTC"
2034 	  will be called "rtc-ti-k3".
2037 	tristate "Nuvoton MA35D1 RTC"
2045 	   will be called "rtc-ma35d1".
2048 	tristate "Renesas RTCA-3 RTC"
2051 	  If you say yes here you get support for the Renesas RTCA-3 RTC
2055 	  will be called "rtc-rtca3".
2061 	  Say yes to enable RTC driver for the Goldfish based virtual platform.
2067 	tristate "Wilco EC RTC"
2078 	tristate "MStar MSC313 RTC"
2085 	  will be called "rtc-msc313".
2088 	tristate "Microchip PolarFire SoC built-in RTC"
2092 	  built-in RTC on Polarfire SoC.
2095 	  will be called "rtc-mpfs".
2098 	tristate "SigmaStar SSD202D RTC"
2106 	  will be called "rtc-ssd20xd".
2109 	tristate "Amlogic RTC"
2114 	  If you say yes here you get support for the RTC block on the
2118 	  will be called "rtc-amlogic-a4".
2121 	tristate "RTC driver for S32G2/S32G3 SoCs"
2125 	  Say yes to enable RTC driver for platforms based on the
2128 	  This RTC module can be used as a wakeup source.
2131 comment "HID Sensor RTC drivers"
2143 	  rtc-hid-sensor-time.