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.
190 	  AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
193 	  will be called rtc-ab-b5ze-s3.
200 	  AB-RTCMC-32.768kHz-EOA9 I2C RTC chip.
203 	  will be called rtc-ab-e0z9.
214 	  will be called rtc-abx80x.
224 	  will be called rtc-ac100.
235 	  be called rtc-brcmstb-waketimer.
238 	tristate "ams AS3722 RTC driver"
241 	  If you say yes here you get support for the RTC of ams AS3722 PMIC
245 	  will be called rtc-as3722.
252 	  If you say yes here you get support for various compatible RTC
256 	  In some cases the RTC must already have been initialized (by
259 	  The first seven registers on these chips hold an RTC, and other
261 	  the RTC/NVRAM backup power, and alarms. NVRAM is visible in
265 	  will be called rtc-ds1307.
268 	bool "Century bit support for rtc-ds1307"
279 	  the RTC date and then boot a kernel with this option set.
289 	  will be called rtc-ds1374.
307 	  will be called rtc-ds1672.
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
318 	  will be called rtc-hym8563.
321 	tristate "TI LP8788 RTC driver"
324 	  Say Y to enable support for the LP8788 RTC/ALARM driver.
330 	  Maxim MAX6900 I2C RTC chip.
333 	  will be called rtc-max6900.
341 	  RTC of Maxim MAX8907 PMIC.
344 	  will be called rtc-max8907.
351 	  RTC of Maxim MAX8925 PMIC.
354 	  will be called rtc-max8925.
361 	  RTC of Maxim MAX8998 PMIC.
364 	  will be called rtc-max8998.
371 	  RTC of Maxim MAX8997 PMIC.
374 	  will be called rtc-max8997.
387 	  will be called rtc-max31335.
394 	  RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
397 	  will be called rtc-max77686.
403 	   If you say yes here you get support for the Nuvoton NCT3018Y I2C RTC
407 	   called "rtc-nct3018y".
410 	tristate "Rockchip RK805/RK808/RK809/RK817/RK818 RTC"
414 	  RTC of RK805, RK809 and RK817, RK808 and RK818 PMIC.
417 	  will be called rk808-rtc.
423 	  Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
426 	  will be called rtc-rs5c372.
432 	  Intersil ISL1208 RTC chip.
435 	  will be called rtc-isl1208.
442 	  Intersil ISL12022 RTC chip.
445 	  will be called rtc-isl12022.
452 	  Intersil ISL12026 RTC chip.
455 	  will be called rtc-isl12026.
461 	  Xicor/Intersil X1205 RTC chip.
464 	  will be called rtc-x1205.
470 	  If you say yes here you get support for the NXP PCF8523 RTC
474 	  will be called rtc-pcf8523.
480 	  If you say yes here you get support for the PCF85063 RTC chip
483 	  will be called rtc-pcf85063.
489 	  If you say yes here you get support for the PCF85363 RTC chip.
492 	  will be called rtc-pcf85363.
501 	  Philips PCF8563 RTC chip. The Epson RTC8564
505 	  will be called rtc-pcf8563.
511 	  RTC chip found on Acorn RiscPCs. This driver supports the
513 	  the RTC's SRAM. It will work on other platforms with the same
517 	  will be called rtc-pcf8583.
523 	  and M41T80 RTC chips series. Currently, the following chips are
528 	  will be called rtc-m41t80.
531 	bool "ST M41T65/M41T80 series RTC watchdog timer"
535 	  watchdog timer in the ST M41T60 and M41T80 RTC chips series.
538 	tristate "ROHM BD71815 and BD71828 PMIC RTC"
541 	  If you say Y here you will get support for the RTC
545 	  will be called rtc-bd70528.
551 	  BQ32000 I2C RTC chip.
554 	  will be called rtc-bq32k.
560 	  If you say yes here you get support for the RTC on the
570 	  If you say yes here you get support for the RTC on the
574 	  will be called rtc-twl.
577 	tristate "TI Palmas RTC driver"
580 	  If you say yes here you get support for the RTC of TI PALMA series PMIC
584 	  will be called rtc-palma.
587 	tristate "TI TPS6586X RTC driver"
590 	  TI Power Management IC TPS6586X supports RTC functionality
591 	  along with alarm. This driver supports the RTC driver for
592 	  the TPS6586X RTC module.
595 	tristate "TI TPS6594 RTC driver"
599 	  TI Power Management IC TPS6594 supports RTC functionality
600 	  along with alarm. This driver supports the RTC driver for
601 	  the TPS6594 RTC module.
604 	  will be called rtc-tps6594.
607 	tristate "TI TPS65910 RTC driver"
610 	  If you say yes here you get support for the RTC on the
614 	  will be called rtc-tps65910.
617 	tristate "RICOH 5T583 RTC driver"
620 	  If you say yes here you get support for the RTC on the
624 	  will be called rtc-rc5t583.
627 	tristate "RICOH RC5T619 RTC driver"
630 	  If you say yes here you get support for the RTC on the
634 	  will be called rtc-rc5t619.
644 	  will be called rtc-s35390a.
650 	  Ramtron FM3130 RTC chips.
652 	  RTC clock and FRAM. This driver provides only RTC functionality.
655 	  will be called rtc-fm3130.
661 	  If you say yes here you get support for the Epson RX8010SJ RTC
665 	  will be called rtc-rx8010.
672 	  If you say yes here you will get support for the Epson RX8111 RTC.
675 	  called rtc-rx8111.
685 	  will be called rtc-rx8581.
691 	  RX-8025SA/NB RTC chips.
694 	  will be called rtc-rx8025.
700 	  Microelectronic EM3027 RTC chips.
703 	  will be called rtc-em3027.
713 	  will be called rtc-rv3028.
723 	  will be called rtc-rv3032.
729 	  Epson RX8900 RTC chips.
732 	  will be called rtc-rv8803.
741 	  RTC of Samsung S2MPS14 and S5M PMIC series.
744 	  will be called rtc-s5m.
751 	  DFRobot SD2405AL I2C RTC Module.
754 	  will be called rtc-sd2405al.
761 	  SD3078 RTC chips.
764 	  will be called rtc-sd3078
768 comment "SPI RTC drivers"
776 	  ST M41T93 SPI RTC chip.
779 	  will be called rtc-m41t93.
785 	  ST M41T94 SPI RTC chip.
788 	  will be called rtc-m41t94.
794 	  If you say yes here you get support for the Dallas DS1302 RTC chips.
797 	  will be called rtc-ds1302.
807 	  will be called rtc-ds1305.
818 	  will be called rtc-ds1343.
827 	  This driver only supports the RTC feature, and not other chip
831 	  will be called rtc-ds1347.
839 	  This driver supports the RTC feature and trickle charging but not
843 	  will be called rtc-ds1390.
849 	  Maxim MAX6916 SPI RTC chip.
851 	  This driver only supports the RTC feature, and not other chip
855 	  will be called rtc-max6916.
858 	tristate "Epson RTC-9701JE"
861 	  Epson RTC-9701JE SPI RTC chip.
864 	  will be called rtc-r9701.
872 	  will be called rtc-rx4581.
878 	  Ricoh RS5C348A and RS5C348B RTC chips.
881 	  will be called rtc-rs5c348.
887 	  Maxim MAX6902 SPI RTC chip.
890 	  will be called rtc-max6902.
897 	  RTC chip.
900 	  will be called rtc-pcf2123.
908 	  will be called rtc-mcp795.
922 comment "SPI and I2C RTC drivers"
935 	  will be called rtc-ds3232.
943 	  rtc-ds3232
952 	  If you say yes here you get support for the NXP PCF2127/29/31 RTC
961 	  will be called rtc-pcf2127.
970 	  RV3029 and RV3049 RTC chips.
973 	  will be called rtc-rv3029c2.
982 	  rtc-rv3029.
993 	  will be called rtc-rx6110.
995 comment "Platform RTC drivers"
997 # this 'CMOS' RTC driver is arch dependent because it requires
1020 	  will be called rtc-cmos.
1036 	  If you say yes here you get support for the Dallas DS1216 RTC chips.
1042 	  If you say yes here you get support for the Dallas DS1286 RTC chips.
1052 	  will be called rtc-ds1511.
1062 	  will be called rtc-ds1553.
1074 	  will be called rtc-ds1685.
1097 	  This is an older RTC chip, supplanted by the DS1685/DS1687 above,
1101 	  It also works for the even older DS1688/DS1691 RTC chips, which are
1140 	  will be called rtc-ds1742.
1146 	  Dallas DS2404 RTC chip.
1149 	  will be called rtc-ds2404.
1152 	tristate "Dialog DA9052/DA9053 RTC"
1155 	  Say y here to support the RTC driver for Dialog Semiconductor
1159 	tristate "Dialog Semiconductor DA9055 RTC"
1163 	  RTC of the Dialog DA9055 PMIC.
1166 	  will be called rtc-da9055
1169 	tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1172 	  If you say yes here you will get support for the RTC subsystem
1176 	  will be called "rtc-da9063".
1179 	tristate "EFI RTC"
1186 	  will be called rtc-efi.
1196 	  will be called rtc-stk17ta8.
1203 	  ST M48T86 and Dallas DS12887 RTC chips.
1206 	  will be called rtc-m48t86.
1213 	  ST M48T35 RTC chip.
1216 	  will be called "rtc-m48t35".
1223 	  ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1229 	  will be called "rtc-m48t59".
1239 	  will be called rtc-msm6242.
1247 	  BQ4802 RTC chip.
1250 	  will be called rtc-bq4802.
1261 	  will be called rtc-rp5c01.
1264 	tristate "Nintendo GameCube, Wii and Wii U RTC"
1268 	  If you say yes here you will get support for the RTC subsystem
1272 	  will be called "rtc-gamecube".
1275 	tristate "Wolfson Microelectronics WM831x RTC"
1278 	  If you say yes here you will get support for the RTC subsystem
1282 	  will be called "rtc-wm831x".
1285 	tristate "Wolfson Microelectronics WM8350 RTC"
1288 	  If you say yes here you will get support for the RTC subsystem
1292 	  will be called "rtc-wm8350".
1295 	tristate "Spreadtrum SC27xx RTC"
1298 	  If you say Y here you will get support for the RTC subsystem
1303 	  will be called rtc-sc27xx.
1306 	tristate "SPEAR ST RTC"
1310 	 If you say Y here you will get support for the RTC found on
1315 	tristate "NXP PCF50633 RTC"
1317 	  If you say yes here you get support for the RTC subsystem of the
1321 	tristate "ST-Ericsson AB8500 RTC"
1326 	  Select this to enable the ST-Ericsson AB8500 power management IC RTC
1327 	  support. This chip contains a battery- and capacitor-backed RTC.
1330 	tristate "IBM OPAL RTC driver"
1334 	  If you say yes here you get support for the PowerNV platform RTC
1338 	  will be called rtc-opal.
1341 	tristate "OP-TEE based RTC driver"
1344 	  Select this to get support for OP-TEE based RTC control on SoCs where
1345 	  RTC are not accessible to the normal world (Linux).
1348 	  will be called rtc-optee.
1351 	tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1354 	  If you say yes here you get support for the RTC controller found on
1358 	tristate "Chrome OS EC RTC driver"
1362 	  Chrome OS Embedded Controller's RTC.
1365 	  will be called rtc-cros-ec.
1368 	tristate "Netronix embedded controller RTC"
1371 	  Say yes here if you want to support the RTC functionality of the
1375 comment "on-CPU RTC drivers"
1378 	tristate "Alphascale asm9260 RTC"
1381 	  If you say yes here you get support for the RTC on the
1385 	  will be called rtc-asm9260.
1388 	tristate "Conexant Digicolor RTC"
1391 	  If you say yes here you get support for the RTC on Conexant
1395 	  will be called rtc-digicolor.
1402 	   Support for Freescale IMX DryIce RTC
1405 	   will be called "rtc-imxdi".
1418 	   will be called "rtc-fsl-ftm-alarm".
1421 	tristate "Amlogic Meson RTC"
1425 	   Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1429 	   will be called "rtc-meson".
1432 	tristate "Amlogic Meson Virtual RTC"
1437 	  Virtual RTC of Amlogic SoCs.
1440 	  will be called rtc-meson-vrtc.
1453 	  will be called rtc-omap.
1456 	tristate "Samsung S3C series SoC RTC"
1460 	  RTC (Realtime Clock) driver for the clock inbuilt into the
1466 	  will be called rtc-s3c.
1473 	  RTC embedded in the Cirrus Logic EP93XX processors.
1476 	  will be called rtc-ep93xx.
1486 	  module will be called rtc-sa1100.
1489 	tristate "SuperH On-Chip RTC"
1492 	  Say Y here to enable support for the on-chip RTC found in
1493 	  most SuperH processors. This RTC is also found in RZ/A SoCs.
1496 	  module will be called rtc-sh.
1499 	tristate "Sunplus SP7021 RTC"
1504 	  RTC status check, timer/alarm functionalities, user data
1505 	  reservation with the battery over 2.5V, RTC power status check
1509 	  will be called rtc-sunplus.
1512 	tristate "ARM AMBA PL030 RTC"
1516 	  PrimeCell PL030 RTC found on certain ARM SOCs.
1519 	  module will be called rtc-pl030.
1522 	tristate "ARM AMBA PL031 RTC"
1526 	  PrimeCell PL031 RTC found on certain ARM SOCs.
1529 	  module will be called rtc-pl031.
1532 	tristate "AT91RM9200 or some AT91SAM9 RTC"
1536 	  Driver for the internal RTC (Realtime Clock) module found on
1541 	tristate "AT91SAM9 RTT as RTC"
1547 	  can be used as an RTC thanks to the backup power supply (e.g. a
1551 	  Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1552 	  probably want to use the real RTC block instead of the "RTT as an
1553 	  RTC" driver.
1556 	tristate "Au1xxx Counter0 RTC support"
1560 	  counter) to be used as a RTC.
1563 	  will be called rtc-au1xxx.
1569 	  If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1572 	tristate "Renesas RZ/N1 RTC"
1576 	  If you say yes here you get support for the Renesas RZ/N1 RTC.
1579 	tristate "Generic RTC support"
1580 	# Please consider writing a new RTC driver instead of using the generic
1581 	# RTC abstraction
1584 	  Say Y or M here to enable RTC support on systems using the generic
1585 	  RTC abstraction. If you do not know what you are doing, you should
1594 	 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1595 	 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1597 	 This RTC driver uses PXA RTC registers available since pxa27x
1601 	tristate "VIA/WonderMedia 85xx SoC RTC"
1609 	bool "SUN4V Hypervisor RTC"
1613 	  based RTC on SUN4V systems.
1616 	bool "Allwinner A31 RTC"
1621 	  If you say Y here you will get support for the RTC found in
1625 	tristate "Allwinner sun4i/sun7i RTC"
1628 	  If you say Y here you will get support for the RTC found on
1632 	bool "Starfire RTC"
1635 	  If you say Y here you will get support for the RTC found on
1639 	tristate "Marvell SoC RTC"
1642 	  If you say yes here you will get support for the in-chip RTC
1647 	  will be called rtc-mv.
1650 	tristate "Armada 38x Marvell SoC RTC"
1654 	  If you say yes here you will get support for the in-chip RTC
1658 	  will be called armada38x-rtc.
1661 	tristate "Cadence RTC driver"
1664 	  If you say Y here you will get access to Cadence RTC IP
1668 	  module will be called rtc-cadence.
1671 	tristate "Faraday Technology FTRTC010 RTC"
1679 	  will be called rtc-ftrtc010.
1682 	tristate "PS3 RTC"
1685 	  If you say yes here you will get support for the RTC on PS3.
1688 	  will be called rtc-ps3.
1691 	tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1696 	  STMP3xxx/i.MX23/i.MX28 RTC.
1699 	  will be called rtc-stmp3xxx.
1702 	tristate "PCAP RTC"
1705 	  If you say Y here you will get support for the RTC found on
1710 	tristate "Freescale MC13xxx RTC"
1716 	tristate "Freescale MPC5121 built-in RTC"
1720 	  built-in RTC on MPC5121 or on MPC5200.
1723 	  will be called rtc-mpc5121.
1730 	  If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1734 	  will be called rtc-jz4740.
1737 	tristate "Loongson On-chip RTC"
1742 	  counter) to be used as a RTC.
1747 	  will be called rtc-loongson.
1750 	tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1755 	  This enables support for the NXP RTC found which can be found on
1759 	  the hardware RTC. This driver can also be built as a module. If
1760 	  so, the module will be called rtc-lpc24xx.
1764 	tristate "NXP LPC32XX RTC"
1766 	  This enables support for the NXP RTC in the LPC32XX
1769 	  will be called rtc-lpc32xx.
1772 	tristate "Qualcomm PMIC8XXX RTC"
1776 	  Qualcomm PMIC8XXX RTC.
1779 	  module will be called rtc-pm8xxx.
1782 	tristate "NVIDIA Tegra Internal RTC driver"
1786 	  Tegra 200 series internal RTC module.
1789 	  will be called rtc-tegra.
1798 	   RTC module.
1801 	   will be called "rtc-mxc".
1813 	   will be called "rtc-mxc_v2".
1816 	tristate "Freescale SNVS RTC support"
1823 	   Low Power (LP) RTC module.
1826 	   will be called "rtc-snvs".
1829 	tristate "NXP BBNSM RTC support"
1835 	   If you say yes here you get support for the NXP BBNSM RTC module.
1838 	   will be called "rtc-bbnsm".
1843 	tristate "NXP i.MX BBM SCMI RTC support"
1846 	  RTC module.
1849 	  module will be called rtc-imx-sm-bbm.
1854 	tristate "NXP i.MX System Controller RTC support"
1857 	   Controller RTC module.
1860 	tristate "STMicroelectronics LPC RTC"
1865 	  (LPC) based RTC support.
1868 	  module will be called rtc-st-lpc.
1871 	tristate "MOXA ART RTC"
1875 	   RTC module.
1878 	   will be called rtc-moxart
1881 	tristate "MediaTek MT2712 SoC based RTC"
1888 	  will be called rtc-mt2712.
1891 	tristate "MediaTek PMIC based RTC"
1895 	  This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1897 	  MediaTek(R) RTC driver.
1899 	  If you want to use MediaTek(R) RTC interface, select Y or M here.
1902 	tristate "MediaTek SoC based RTC"
1909 	  will be called rtc-mt7622.
1912 	tristate "APM X-Gene RTC"
1920 	  will be called "rtc-xgene".
1923 	tristate "Microchip PIC32 RTC"
1927 	   If you say yes here you get support for the PIC32 RTC module.
1930 	   will be called rtc-pic32
1933 	tristate "EPSON TOYOCOM RTC-7301SF/DG"
1938 	   RTC-7301SF/DG chips.
1941 	   will be called rtc-r7301.
1944 	tristate "STM32 RTC"
1958 	   will be called "rtc-stm32".
1962 	tristate "Motorola CPCAP RTC"
1964 	   Say y here for CPCAP rtc found on some Motorola phones
1968 	bool "Realtek RTD129x RTC"
1976 	tristate "ASPEED RTC"
1984 	  will be called "rtc-aspeed".
1987 	tristate "TI K3 RTC"
1995 	  will be called "rtc-ti-k3".
1998 	tristate "Nuvoton MA35D1 RTC"
2006 	   will be called "rtc-ma35d1".
2008 comment "HID Sensor RTC drivers"
2020 	  rtc-hid-sensor-time.
2026 	  Say yes to enable RTC driver for the Goldfish based virtual platform.
2032 	tristate "Wilco EC RTC"
2043 	tristate "MStar MSC313 RTC"
2050 	  will be called "rtc-msc313".
2053 	tristate "Microchip PolarFire SoC built-in RTC"
2057 	  built-in RTC on Polarfire SoC.
2060 	  will be called "rtc-mpfs".
2063 	tristate "SigmaStar SSD202D RTC"
2071 	  will be called "rtc-ssd20xd".