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.
675 will be called rtc-rx8581.
681 RX-8025SA/NB RTC chips.
684 will be called rtc-rx8025.
690 Microelectronic EM3027 RTC chips.
693 will be called rtc-em3027.
703 will be called rtc-rv3028.
713 will be called rtc-rv3032.
719 Epson RX8900 RTC chips.
722 will be called rtc-rv8803.
731 RTC of Samsung S2MPS14 and S5M PMIC series.
734 will be called rtc-s5m.
741 SD3078 RTC chips.
744 will be called rtc-sd3078
748 comment "SPI RTC drivers"
756 ST M41T93 SPI RTC chip.
759 will be called rtc-m41t93.
765 ST M41T94 SPI RTC chip.
768 will be called rtc-m41t94.
774 If you say yes here you get support for the Dallas DS1302 RTC chips.
777 will be called rtc-ds1302.
787 will be called rtc-ds1305.
798 will be called rtc-ds1343.
807 This driver only supports the RTC feature, and not other chip
811 will be called rtc-ds1347.
819 This driver supports the RTC feature and trickle charging but not
823 will be called rtc-ds1390.
829 Maxim MAX6916 SPI RTC chip.
831 This driver only supports the RTC feature, and not other chip
835 will be called rtc-max6916.
838 tristate "Epson RTC-9701JE"
841 Epson RTC-9701JE SPI RTC chip.
844 will be called rtc-r9701.
852 will be called rtc-rx4581.
858 Ricoh RS5C348A and RS5C348B RTC chips.
861 will be called rtc-rs5c348.
867 Maxim MAX6902 SPI RTC chip.
870 will be called rtc-max6902.
877 RTC chip.
880 will be called rtc-pcf2123.
888 will be called rtc-mcp795.
902 comment "SPI and I2C RTC drivers"
915 will be called rtc-ds3232.
923 rtc-ds3232
932 If you say yes here you get support for the NXP PCF2127/29/31 RTC
941 will be called rtc-pcf2127.
950 RV3029 and RV3049 RTC chips.
953 will be called rtc-rv3029c2.
962 rtc-rv3029.
973 will be called rtc-rx6110.
975 comment "Platform RTC drivers"
977 # this 'CMOS' RTC driver is arch dependent because it requires
1000 will be called rtc-cmos.
1016 If you say yes here you get support for the Dallas DS1216 RTC chips.
1022 If you say yes here you get support for the Dallas DS1286 RTC chips.
1032 will be called rtc-ds1511.
1042 will be called rtc-ds1553.
1054 will be called rtc-ds1685.
1077 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
1081 It also works for the even older DS1688/DS1691 RTC chips, which are
1120 will be called rtc-ds1742.
1126 Dallas DS2404 RTC chip.
1129 will be called rtc-ds2404.
1132 tristate "Dialog DA9052/DA9053 RTC"
1135 Say y here to support the RTC driver for Dialog Semiconductor
1139 tristate "Dialog Semiconductor DA9055 RTC"
1143 RTC of the Dialog DA9055 PMIC.
1146 will be called rtc-da9055
1149 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1152 If you say yes here you will get support for the RTC subsystem
1156 will be called "rtc-da9063".
1159 tristate "EFI RTC"
1166 will be called rtc-efi.
1176 will be called rtc-stk17ta8.
1183 ST M48T86 and Dallas DS12887 RTC chips.
1186 will be called rtc-m48t86.
1193 ST M48T35 RTC chip.
1196 will be called "rtc-m48t35".
1203 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1209 will be called "rtc-m48t59".
1219 will be called rtc-msm6242.
1227 BQ4802 RTC chip.
1230 will be called rtc-bq4802.
1241 will be called rtc-rp5c01.
1244 tristate "Nintendo GameCube, Wii and Wii U RTC"
1248 If you say yes here you will get support for the RTC subsystem
1252 will be called "rtc-gamecube".
1255 tristate "Wolfson Microelectronics WM831x RTC"
1258 If you say yes here you will get support for the RTC subsystem
1262 will be called "rtc-wm831x".
1265 tristate "Wolfson Microelectronics WM8350 RTC"
1268 If you say yes here you will get support for the RTC subsystem
1272 will be called "rtc-wm8350".
1275 tristate "Spreadtrum SC27xx RTC"
1278 If you say Y here you will get support for the RTC subsystem
1283 will be called rtc-sc27xx.
1286 tristate "SPEAR ST RTC"
1290 If you say Y here you will get support for the RTC found on
1295 tristate "NXP PCF50633 RTC"
1297 If you say yes here you get support for the RTC subsystem of the
1301 tristate "ST-Ericsson AB8500 RTC"
1306 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1307 support. This chip contains a battery- and capacitor-backed RTC.
1310 tristate "IBM OPAL RTC driver"
1314 If you say yes here you get support for the PowerNV platform RTC
1318 will be called rtc-opal.
1321 tristate "OP-TEE based RTC driver"
1324 Select this to get support for OP-TEE based RTC control on SoCs where
1325 RTC are not accessible to the normal world (Linux).
1328 will be called rtc-optee.
1331 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1334 If you say yes here you get support for the RTC controller found on
1338 tristate "Chrome OS EC RTC driver"
1342 Chrome OS Embedded Controller's RTC.
1345 will be called rtc-cros-ec.
1348 tristate "Netronix embedded controller RTC"
1351 Say yes here if you want to support the RTC functionality of the
1355 comment "on-CPU RTC drivers"
1358 tristate "Alphascale asm9260 RTC"
1361 If you say yes here you get support for the RTC on the
1365 will be called rtc-asm9260.
1368 tristate "Conexant Digicolor RTC"
1371 If you say yes here you get support for the RTC on Conexant
1375 will be called rtc-digicolor.
1382 Support for Freescale IMX DryIce RTC
1385 will be called "rtc-imxdi".
1398 will be called "rtc-fsl-ftm-alarm".
1401 tristate "Amlogic Meson RTC"
1405 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1409 will be called "rtc-meson".
1412 tristate "Amlogic Meson Virtual RTC"
1417 Virtual RTC of Amlogic SoCs.
1420 will be called rtc-meson-vrtc.
1433 will be called rtc-omap.
1436 tristate "Samsung S3C series SoC RTC"
1440 RTC (Realtime Clock) driver for the clock inbuilt into the
1446 will be called rtc-s3c.
1453 RTC embedded in the Cirrus Logic EP93XX processors.
1456 will be called rtc-ep93xx.
1466 module will be called rtc-sa1100.
1469 tristate "SuperH On-Chip RTC"
1472 Say Y here to enable support for the on-chip RTC found in
1473 most SuperH processors. This RTC is also found in RZ/A SoCs.
1476 module will be called rtc-sh.
1479 tristate "Sunplus SP7021 RTC"
1484 RTC status check, timer/alarm functionalities, user data
1485 reservation with the battery over 2.5V, RTC power status check
1489 will be called rtc-sunplus.
1492 tristate "ARM AMBA PL030 RTC"
1496 PrimeCell PL030 RTC found on certain ARM SOCs.
1499 module will be called rtc-pl030.
1502 tristate "ARM AMBA PL031 RTC"
1506 PrimeCell PL031 RTC found on certain ARM SOCs.
1509 module will be called rtc-pl031.
1512 tristate "AT91RM9200 or some AT91SAM9 RTC"
1516 Driver for the internal RTC (Realtime Clock) module found on
1521 tristate "AT91SAM9 RTT as RTC"
1527 can be used as an RTC thanks to the backup power supply (e.g. a
1531 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1532 probably want to use the real RTC block instead of the "RTT as an
1533 RTC" driver.
1536 tristate "Au1xxx Counter0 RTC support"
1540 counter) to be used as a RTC.
1543 will be called rtc-au1xxx.
1549 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1552 tristate "Renesas RZ/N1 RTC"
1556 If you say yes here you get support for the Renesas RZ/N1 RTC.
1559 tristate "Generic RTC support"
1560 # Please consider writing a new RTC driver instead of using the generic
1561 # RTC abstraction
1564 Say Y or M here to enable RTC support on systems using the generic
1565 RTC abstraction. If you do not know what you are doing, you should
1574 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1575 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1577 This RTC driver uses PXA RTC registers available since pxa27x
1581 tristate "VIA/WonderMedia 85xx SoC RTC"
1589 bool "SUN4V Hypervisor RTC"
1593 based RTC on SUN4V systems.
1596 bool "Allwinner A31 RTC"
1601 If you say Y here you will get support for the RTC found in
1605 tristate "Allwinner sun4i/sun7i RTC"
1608 If you say Y here you will get support for the RTC found on
1612 bool "Starfire RTC"
1615 If you say Y here you will get support for the RTC found on
1619 tristate "Marvell SoC RTC"
1622 If you say yes here you will get support for the in-chip RTC
1627 will be called rtc-mv.
1630 tristate "Armada 38x Marvell SoC RTC"
1634 If you say yes here you will get support for the in-chip RTC
1638 will be called armada38x-rtc.
1641 tristate "Cadence RTC driver"
1644 If you say Y here you will get access to Cadence RTC IP
1648 module will be called rtc-cadence.
1651 tristate "Faraday Technology FTRTC010 RTC"
1659 will be called rtc-ftrtc010.
1662 tristate "PS3 RTC"
1665 If you say yes here you will get support for the RTC on PS3.
1668 will be called rtc-ps3.
1671 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1676 STMP3xxx/i.MX23/i.MX28 RTC.
1679 will be called rtc-stmp3xxx.
1682 tristate "PCAP RTC"
1685 If you say Y here you will get support for the RTC found on
1690 tristate "Freescale MC13xxx RTC"
1696 tristate "Freescale MPC5121 built-in RTC"
1700 built-in RTC on MPC5121 or on MPC5200.
1703 will be called rtc-mpc5121.
1710 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1714 will be called rtc-jz4740.
1717 tristate "Loongson On-chip RTC"
1722 counter) to be used as a RTC.
1727 will be called rtc-loongson.
1730 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1735 This enables support for the NXP RTC found which can be found on
1739 the hardware RTC. This driver can also be built as a module. If
1740 so, the module will be called rtc-lpc24xx.
1744 tristate "NXP LPC32XX RTC"
1746 This enables support for the NXP RTC in the LPC32XX
1749 will be called rtc-lpc32xx.
1752 tristate "Qualcomm PMIC8XXX RTC"
1756 Qualcomm PMIC8XXX RTC.
1759 module will be called rtc-pm8xxx.
1762 tristate "NVIDIA Tegra Internal RTC driver"
1766 Tegra 200 series internal RTC module.
1769 will be called rtc-tegra.
1778 RTC module.
1781 will be called "rtc-mxc".
1793 will be called "rtc-mxc_v2".
1796 tristate "Freescale SNVS RTC support"
1803 Low Power (LP) RTC module.
1806 will be called "rtc-snvs".
1809 tristate "NXP BBNSM RTC support"
1815 If you say yes here you get support for the NXP BBNSM RTC module.
1818 will be called "rtc-bbnsm".
1823 tristate "NXP i.MX System Controller RTC support"
1826 Controller RTC module.
1829 tristate "STMicroelectronics LPC RTC"
1834 (LPC) based RTC support.
1837 module will be called rtc-st-lpc.
1840 tristate "MOXA ART RTC"
1844 RTC module.
1847 will be called rtc-moxart
1850 tristate "MediaTek MT2712 SoC based RTC"
1857 will be called rtc-mt2712.
1860 tristate "MediaTek PMIC based RTC"
1863 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1865 MediaTek(R) RTC driver.
1867 If you want to use MediaTek(R) RTC interface, select Y or M here.
1870 tristate "MediaTek SoC based RTC"
1877 will be called rtc-mt7622.
1880 tristate "APM X-Gene RTC"
1888 will be called "rtc-xgene".
1891 tristate "Microchip PIC32 RTC"
1895 If you say yes here you get support for the PIC32 RTC module.
1898 will be called rtc-pic32
1901 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1906 RTC-7301SF/DG chips.
1909 will be called rtc-r7301.
1912 tristate "STM32 RTC"
1920 will be called "rtc-stm32".
1924 tristate "Motorola CPCAP RTC"
1926 Say y here for CPCAP rtc found on some Motorola phones
1930 bool "Realtek RTD129x RTC"
1938 tristate "ASPEED RTC"
1946 will be called "rtc-aspeed".
1949 tristate "TI K3 RTC"
1957 will be called "rtc-ti-k3".
1960 tristate "Nuvoton MA35D1 RTC"
1968 will be called "rtc-ma35d1".
1970 comment "HID Sensor RTC drivers"
1982 rtc-hid-sensor-time.
1988 Say yes to enable RTC driver for the Goldfish based virtual platform.
1994 tristate "Wilco EC RTC"
2005 tristate "MStar MSC313 RTC"
2012 will be called "rtc-msc313".
2015 tristate "Microchip PolarFire SoC built-in RTC"
2019 built-in RTC on Polarfire SoC.
2022 will be called "rtc-mpfs".
2025 tristate "SigmaStar SSD202D RTC"
2033 will be called "rtc-ssd20xd".