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".
420 	tristate "NVIDIA VRS10 RTC device"
423 	  If you say yes here you will get support for the battery backed RTC device
424 	  of NVIDIA VRS (Voltage Regulator Specification). The RTC is connected via
427 	  rtc-nvidia-vrs10.
433 	   If you say yes here you get support for the Nuvoton NCT3018Y I2C RTC
437 	   called "rtc-nct3018y".
440 	tristate "Nuvoton NCT6694 RTC support"
444 	  NCT6694, a USB device to RTC.
447 	  be called rtc-nct6694.
450 	tristate "Rockchip RK805/RK808/RK809/RK817/RK818 RTC"
454 	  RTC of RK805, RK809 and RK817, RK808 and RK818 PMIC.
457 	  will be called rk808-rtc.
463 	  Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
466 	  will be called rtc-rs5c372.
472 	  Intersil ISL1208 RTC chip.
475 	  will be called rtc-isl1208.
482 	  Intersil ISL12022 RTC chip.
485 	  will be called rtc-isl12022.
492 	  Intersil ISL12026 RTC chip.
495 	  will be called rtc-isl12026.
501 	  Xicor/Intersil X1205 RTC chip.
504 	  will be called rtc-x1205.
510 	  If you say yes here you get support for the NXP PCF8523 RTC
514 	  will be called rtc-pcf8523.
520 	  If you say yes here you get support for the PCF85363 RTC chip.
523 	  will be called rtc-pcf85363.
533 	  Philips PCF8563 RTC chip. The Epson RTC8564
537 	  will be called rtc-pcf8563.
543 	  RTC chip found on Acorn RiscPCs. This driver supports the
545 	  the RTC's SRAM. It will work on other platforms with the same
549 	  will be called rtc-pcf8583.
555 	  and M41T80 RTC chips series. Currently, the following chips are
560 	  will be called rtc-m41t80.
563 	bool "ST M41T65/M41T80 series RTC watchdog timer"
567 	  watchdog timer in the ST M41T60 and M41T80 RTC chips series.
570 	tristate "ROHM BD71815 and BD71828 PMIC RTC"
573 	  If you say Y here you will get support for the RTC
578 	  will be called rtc-bd70528.
584 	  BQ32000 I2C RTC chip.
587 	  will be called rtc-bq32k.
593 	  If you say yes here you get support for the RTC on the
603 	  If you say yes here you get support for the RTC on the
607 	  will be called rtc-twl.
610 	tristate "TI Palmas RTC driver"
613 	  If you say yes here you get support for the RTC of TI PALMA series PMIC
617 	  will be called rtc-palma.
620 	tristate "TI TPS6586X RTC driver"
623 	  TI Power Management IC TPS6586X supports RTC functionality
624 	  along with alarm. This driver supports the RTC driver for
625 	  the TPS6586X RTC module.
628 	tristate "TI TPS6594 RTC driver"
632 	  TI Power Management IC TPS6594 supports RTC functionality
633 	  along with alarm. This driver supports the RTC driver for
634 	  the TPS6594 RTC module.
637 	  will be called rtc-tps6594.
640 	tristate "TI TPS65910 RTC driver"
643 	  If you say yes here you get support for the RTC on the
647 	  will be called rtc-tps65910.
650 	tristate "RICOH 5T583 RTC driver"
653 	  If you say yes here you get support for the RTC on the
657 	  will be called rtc-rc5t583.
660 	tristate "RICOH RC5T619 RTC driver"
663 	  If you say yes here you get support for the RTC on the
667 	  will be called rtc-rc5t619.
677 	  will be called rtc-s35390a.
683 	  Ramtron FM3130 RTC chips.
685 	  RTC clock and FRAM. This driver provides only RTC functionality.
688 	  will be called rtc-fm3130.
694 	  If you say yes here you get support for the Epson RX8010SJ RTC
698 	  will be called rtc-rx8010.
705 	  If you say yes here you will get support for the Epson RX8111 RTC.
708 	  called rtc-rx8111.
718 	  will be called rtc-rx8581.
724 	  RX-8025SA/NB RTC chips.
727 	  will be called rtc-rx8025.
733 	  Microelectronic EM3027 RTC chips.
736 	  will be called rtc-em3027.
746 	  will be called rtc-rv3028.
756 	  will be called rtc-rv3032.
762 	  Epson RX8900 RTC chips.
765 	  will be called rtc-rv8803.
774 	  RTC of Samsung S2MPS14 and S5M PMIC series.
777 	  will be called rtc-s5m.
784 	  DFRobot SD2405AL I2C RTC Module.
787 	  will be called rtc-sd2405al.
794 	  SD3078 RTC chips.
797 	  will be called rtc-sd3078
801 comment "SPI RTC drivers"
809 	  ST M41T93 SPI RTC chip.
812 	  will be called rtc-m41t93.
818 	  ST M41T94 SPI RTC chip.
821 	  will be called rtc-m41t94.
827 	  If you say yes here you get support for the Dallas DS1302 RTC chips.
830 	  will be called rtc-ds1302.
840 	  will be called rtc-ds1305.
851 	  will be called rtc-ds1343.
860 	  This driver only supports the RTC feature, and not other chip
864 	  will be called rtc-ds1347.
872 	  This driver supports the RTC feature and trickle charging but not
876 	  will be called rtc-ds1390.
882 	  Maxim MAX6916 SPI RTC chip.
884 	  This driver only supports the RTC feature, and not other chip
888 	  will be called rtc-max6916.
891 	tristate "Epson RTC-9701JE"
894 	  Epson RTC-9701JE SPI RTC chip.
897 	  will be called rtc-r9701.
905 	  will be called rtc-rx4581.
911 	  Ricoh RS5C348A and RS5C348B RTC chips.
914 	  will be called rtc-rs5c348.
920 	  Maxim MAX6902 SPI RTC chip.
923 	  will be called rtc-max6902.
930 	  RTC chip.
933 	  will be called rtc-pcf2123.
941 	  will be called rtc-mcp795.
955 comment "SPI and I2C RTC drivers"
968 	  will be called rtc-ds3232.
976 	  rtc-ds3232
985 	  If you say yes here you get support for the NXP PCF2127/29/31 RTC
994 	  will be called rtc-pcf2127.
1003 	  RTC chips.
1006 	  will be called rtc-pcf85063.
1015 	  RV3029 and RV3049 RTC chips.
1018 	  will be called rtc-rv3029c2.
1027 	  rtc-rv3029.
1038 	  will be called rtc-rx6110.
1040 comment "Platform RTC drivers"
1042 # this 'CMOS' RTC driver is arch dependent because it requires
1065 	  will be called rtc-cmos.
1083 	  RTC driver.
1090 	  be called rtc-atcrtc100.
1096 	  If you say yes here you get support for the Dallas DS1216 RTC chips.
1102 	  If you say yes here you get support for the Dallas DS1286 RTC chips.
1112 	  will be called rtc-ds1511.
1122 	  will be called rtc-ds1553.
1134 	  will be called rtc-ds1685.
1157 	  This is an older RTC chip, supplanted by the DS1685/DS1687 above,
1161 	  It also works for the even older DS1688/DS1691 RTC chips, which are
1200 	  will be called rtc-ds1742.
1206 	  Dallas DS2404 RTC chip.
1209 	  will be called rtc-ds2404.
1212 	tristate "Dialog DA9052/DA9053 RTC"
1215 	  Say y here to support the RTC driver for Dialog Semiconductor
1219 	tristate "Dialog Semiconductor DA9055 RTC"
1223 	  RTC of the Dialog DA9055 PMIC.
1226 	  will be called rtc-da9055
1229 	tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1232 	  If you say yes here you will get support for the RTC subsystem
1236 	  will be called "rtc-da9063".
1239 	tristate "EFI RTC"
1246 	  will be called rtc-efi.
1256 	  will be called rtc-stk17ta8.
1263 	  ST M48T86 and Dallas DS12887 RTC chips.
1266 	  will be called rtc-m48t86.
1273 	  ST M48T35 RTC chip.
1276 	  will be called "rtc-m48t35".
1283 	  ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1289 	  will be called "rtc-m48t59".
1299 	  will be called rtc-msm6242.
1307 	  BQ4802 RTC chip.
1310 	  will be called rtc-bq4802.
1321 	  will be called rtc-rp5c01.
1324 	tristate "Nintendo GameCube, Wii and Wii U RTC"
1328 	  If you say yes here you will get support for the RTC subsystem
1332 	  will be called "rtc-gamecube".
1335 	tristate "Wolfson Microelectronics WM831x RTC"
1338 	  If you say yes here you will get support for the RTC subsystem
1342 	  will be called "rtc-wm831x".
1345 	tristate "Wolfson Microelectronics WM8350 RTC"
1348 	  If you say yes here you will get support for the RTC subsystem
1352 	  will be called "rtc-wm8350".
1355 	tristate "Spreadtrum SC27xx RTC"
1358 	  If you say Y here you will get support for the RTC subsystem
1363 	  will be called rtc-sc27xx.
1366 	tristate "SPEAR ST RTC"
1370 	 If you say Y here you will get support for the RTC found on
1374 	tristate "ST-Ericsson AB8500 RTC"
1379 	  Select this to enable the ST-Ericsson AB8500 power management IC RTC
1380 	  support. This chip contains a battery- and capacitor-backed RTC.
1383 	tristate "IBM OPAL RTC driver"
1387 	  If you say yes here you get support for the PowerNV platform RTC
1391 	  will be called rtc-opal.
1394 	tristate "OP-TEE based RTC driver"
1397 	  Select this to get support for OP-TEE based RTC control on SoCs where
1398 	  RTC are not accessible to the normal world (Linux).
1401 	  will be called rtc-optee.
1404 	tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1407 	  If you say yes here you get support for the RTC controller found on
1411 	tristate "Chrome OS EC RTC driver"
1415 	  Chrome OS Embedded Controller's RTC.
1418 	  will be called rtc-cros-ec.
1421 	tristate "Netronix embedded controller RTC"
1424 	  Say yes here if you want to support the RTC functionality of the
1428 comment "on-CPU RTC drivers"
1431 	tristate "Alphascale asm9260 RTC"
1434 	  If you say yes here you get support for the RTC on the
1438 	  will be called rtc-asm9260.
1441 	tristate "Sophgo CV1800 RTC"
1446 	  If you say yes here you get support the RTC driver for Sophgo CV1800
1450 	  called rtc-cv1800.
1453 	tristate "Conexant Digicolor RTC"
1456 	  If you say yes here you get support for the RTC on Conexant
1460 	  will be called rtc-digicolor.
1467 	   Support for Freescale IMX DryIce RTC
1470 	   will be called "rtc-imxdi".
1483 	   will be called "rtc-fsl-ftm-alarm".
1486 	tristate "Amlogic Meson RTC"
1490 	   Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1494 	   will be called "rtc-meson".
1497 	tristate "Amlogic Meson Virtual RTC"
1502 	  Virtual RTC of Amlogic SoCs.
1505 	  will be called rtc-meson-vrtc.
1518 	  will be called rtc-omap.
1521 	tristate "Samsung S3C series SoC RTC"
1525 	  RTC (Realtime Clock) driver for the clock inbuilt into the
1531 	  will be called rtc-s3c.
1538 	  RTC embedded in the Cirrus Logic EP93XX processors.
1541 	  will be called rtc-ep93xx.
1551 	  module will be called rtc-sa1100.
1554 	tristate "SuperH On-Chip RTC"
1557 	  Say Y here to enable support for the on-chip RTC found in
1558 	  most SuperH processors. This RTC is also found in RZ/A SoCs.
1561 	  module will be called rtc-sh.
1564 	tristate "Sunplus SP7021 RTC"
1569 	  RTC status check, timer/alarm functionalities, user data
1570 	  reservation with the battery over 2.5V, RTC power status check
1574 	  will be called rtc-sunplus.
1577 	tristate "ARM AMBA PL030 RTC"
1581 	  PrimeCell PL030 RTC found on certain ARM SOCs.
1584 	  module will be called rtc-pl030.
1587 	tristate "ARM AMBA PL031 RTC"
1591 	  PrimeCell PL031 RTC found on certain ARM SOCs.
1594 	  module will be called rtc-pl031.
1597 	tristate "AT91RM9200 or some AT91SAM9 RTC"
1601 	  Driver for the internal RTC (Realtime Clock) module found on
1606 	tristate "AT91SAM9 RTT as RTC"
1612 	  can be used as an RTC thanks to the backup power supply (e.g. a
1616 	  Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1617 	  probably want to use the real RTC block instead of the "RTT as an
1618 	  RTC" driver.
1621 	tristate "Au1xxx Counter0 RTC support"
1625 	  counter) to be used as a RTC.
1628 	  will be called rtc-au1xxx.
1634 	  If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1637 	tristate "Renesas RZ/N1 RTC"
1641 	  If you say yes here you get support for the RTC initially found on
1645 	tristate "Generic RTC support"
1646 	# Please consider writing a new RTC driver instead of using the generic
1647 	# RTC abstraction
1650 	  Say Y or M here to enable RTC support on systems using the generic
1651 	  RTC abstraction. If you do not know what you are doing, you should
1660 	 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1661 	 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1663 	 This RTC driver uses PXA RTC registers available since pxa27x
1667 	tristate "VIA/WonderMedia 85xx SoC RTC"
1675 	bool "SUN4V Hypervisor RTC"
1679 	  based RTC on SUN4V systems.
1682 	bool "Allwinner A31 RTC"
1687 	  If you say Y here you will get support for the RTC found in
1691 	tristate "Allwinner sun4i/sun7i RTC"
1694 	  If you say Y here you will get support for the RTC found on
1698 	bool "Starfire RTC"
1701 	  If you say Y here you will get support for the RTC found on
1705 	tristate "Marvell SoC RTC"
1708 	  If you say yes here you will get support for the in-chip RTC
1713 	  will be called rtc-mv.
1716 	tristate "Armada 38x Marvell SoC RTC"
1720 	  If you say yes here you will get support for the in-chip RTC
1724 	  will be called armada38x-rtc.
1727 	tristate "Cadence RTC driver"
1730 	  If you say Y here you will get access to Cadence RTC IP
1734 	  module will be called rtc-cadence.
1737 	tristate "Faraday Technology FTRTC010 RTC"
1745 	  will be called rtc-ftrtc010.
1748 	tristate "PS3 RTC"
1751 	  If you say yes here you will get support for the RTC on PS3.
1754 	  will be called rtc-ps3.
1757 	tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1762 	  STMP3xxx/i.MX23/i.MX28 RTC.
1765 	  will be called rtc-stmp3xxx.
1769 	tristate "Freescale MC13xxx RTC"
1775 	tristate "Freescale MPC5121 built-in RTC"
1779 	  built-in RTC on MPC5121 or on MPC5200.
1782 	  will be called rtc-mpc5121.
1789 	  If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1793 	  will be called rtc-jz4740.
1796 	tristate "Loongson On-chip RTC"
1801 	  counter) to be used as a RTC.
1806 	  will be called rtc-loongson.
1809 	tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1814 	  This enables support for the NXP RTC found which can be found on
1818 	  the hardware RTC. This driver can also be built as a module. If
1819 	  so, the module will be called rtc-lpc24xx.
1823 	tristate "NXP LPC32XX RTC"
1825 	  This enables support for the NXP RTC in the LPC32XX
1828 	  will be called rtc-lpc32xx.
1831 	tristate "Qualcomm PMIC8XXX RTC"
1835 	  Qualcomm PMIC8XXX RTC.
1838 	  module will be called rtc-pm8xxx.
1841 	tristate "NVIDIA Tegra Internal RTC driver"
1845 	  Tegra 200 series internal RTC module.
1848 	  will be called rtc-tegra.
1857 	   RTC module.
1860 	   will be called "rtc-mxc".
1872 	   will be called "rtc-mxc_v2".
1875 	tristate "Freescale SNVS RTC support"
1882 	   Low Power (LP) RTC module.
1885 	   will be called "rtc-snvs".
1888 	tristate "NXP BBNSM RTC support"
1894 	   If you say yes here you get support for the NXP BBNSM RTC module.
1897 	   will be called "rtc-bbnsm".
1902 	tristate "NXP i.MX BBM SCMI RTC support"
1905 	  RTC module.
1908 	  module will be called rtc-imx-sm-bbm.
1913 	tristate "NXP i.MX System Controller RTC support"
1916 	   Controller RTC module.
1919 	tristate "STMicroelectronics LPC RTC"
1924 	  (LPC) based RTC support.
1927 	  module will be called rtc-st-lpc.
1930 	tristate "MOXA ART RTC"
1934 	   RTC module.
1937 	   will be called rtc-moxart
1940 	tristate "MediaTek MT2712 SoC based RTC"
1947 	  will be called rtc-mt2712.
1950 	tristate "MediaTek PMIC based RTC"
1954 	  This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1956 	  MediaTek(R) RTC driver.
1958 	  If you want to use MediaTek(R) RTC interface, select Y or M here.
1961 	tristate "MediaTek SoC based RTC"
1968 	  will be called rtc-mt7622.
1971 	tristate "APM X-Gene RTC"
1979 	  will be called "rtc-xgene".
1982 	tristate "Microchip PIC32 RTC"
1986 	   If you say yes here you get support for the PIC32 RTC module.
1989 	   will be called rtc-pic32
1992 	tristate "EPSON TOYOCOM RTC-7301SF/DG"
1997 	   RTC-7301SF/DG chips.
2000 	   will be called rtc-r7301.
2003 	tristate "STM32 RTC"
2017 	   will be called "rtc-stm32".
2021 	tristate "Motorola CPCAP RTC"
2023 	   Say y here for CPCAP rtc found on some Motorola phones
2027 	bool "Realtek RTD129x RTC"
2035 	tristate "ASPEED RTC"
2043 	  will be called "rtc-aspeed".
2046 	tristate "TI K3 RTC"
2054 	  will be called "rtc-ti-k3".
2057 	tristate "Nuvoton MA35D1 RTC"
2065 	   will be called "rtc-ma35d1".
2068 	tristate "Renesas RTCA-3 RTC"
2071 	  If you say yes here you get support for the Renesas RTCA-3 RTC
2075 	  will be called "rtc-rtca3".
2081 	  Say yes to enable RTC driver for the Goldfish based virtual platform.
2087 	tristate "Wilco EC RTC"
2098 	tristate "Apple Mac System Management Controller RTC"
2101 	  If you say yes here you get support for RTC functions
2106 	  module will be called rtc-macsmc.
2109 	tristate "MStar MSC313 RTC"
2117 	  will be called "rtc-msc313".
2120 	tristate "Microchip PolarFire SoC built-in RTC"
2124 	  built-in RTC on Polarfire SoC.
2127 	  will be called "rtc-mpfs".
2130 	tristate "SigmaStar SSD202D RTC"
2138 	  will be called "rtc-ssd20xd".
2141 	tristate "Amlogic RTC"
2146 	  If you say yes here you get support for the RTC block on the
2150 	  will be called "rtc-amlogic-a4".
2153 	tristate "RTC driver for S32G2/S32G3 SoCs"
2157 	  Say yes to enable RTC driver for platforms based on the
2160 	  This RTC module can be used as a wakeup source.
2163 comment "HID Sensor RTC drivers"
2175 	  rtc-hid-sensor-time.