Lines Matching +full:snvs +full:- +full:rtc +full:- +full:lp
1 # SPDX-License-Identifier: GPL-2.0-only
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
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
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
141 once-per-second update interrupts, used for synchronization.
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.
197 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
200 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
203 will be called rtc-ab-b5ze-s3.
207 tristate "Abracon AB-RTCMC-32.768kHz-EOZ9"
210 AB-RTCMC-32.768kHz-EOA9 I2C RTC chip.
213 will be called rtc-ab-e0z9.
220 families of ultra-low-power battery- and capacitor-backed real-time
224 will be called rtc-abx80x.
227 tristate "X-Powers AC100"
230 If you say yes here you get support for the real-time clock found
231 in X-Powers AC100 family peripheral ICs.
234 will be called rtc-ac100.
237 tristate "Broadcom STB wake-timer"
241 If you say yes here you get support for the wake-timer found on
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.
258 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"
262 If you say yes here you get support for various compatible RTC
265 ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.
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.
295 DS1374 real-time clock chips. If an interrupt is associated
299 will be called rtc-ds1374.
308 real-time clock chips.
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.
413 If you say yes here you get support for the Nuvoton NCT3018Y I2C RTC
417 called "rtc-nct3018y".
420 tristate "Rockchip RK805/RK808/RK809/RK817/RK818 RTC"
424 RTC of RK805, RK809 and RK817, RK808 and RK818 PMIC.
427 will be called rk808-rtc.
433 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
436 will be called rtc-rs5c372.
442 Intersil ISL1208 RTC chip.
445 will be called rtc-isl1208.
452 Intersil ISL12022 RTC chip.
455 will be called rtc-isl12022.
462 Intersil ISL12026 RTC chip.
465 will be called rtc-isl12026.
471 Xicor/Intersil X1205 RTC chip.
474 will be called rtc-x1205.
480 If you say yes here you get support for the NXP PCF8523 RTC
484 will be called rtc-pcf8523.
490 If you say yes here you get support for the PCF85363 RTC chip.
493 will be called rtc-pcf85363.
495 The nvmem interface will be named pcf85363-#, where # is the
496 zero-based instance number.
503 Philips PCF8563 RTC chip. The Epson RTC8564
507 will be called rtc-pcf8563.
513 RTC chip found on Acorn RiscPCs. This driver supports the
515 the RTC's SRAM. It will work on other platforms with the same
519 will be called rtc-pcf8583.
525 and M41T80 RTC chips series. Currently, the following chips are
530 will be called rtc-m41t80.
533 bool "ST M41T65/M41T80 series RTC watchdog timer"
537 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
540 tristate "ROHM BD71815 and BD71828 PMIC RTC"
543 If you say Y here you will get support for the RTC
547 will be called rtc-bd70528.
553 BQ32000 I2C RTC chip.
556 will be called rtc-bq32k.
562 If you say yes here you get support for the RTC on the
572 If you say yes here you get support for the RTC on the
576 will be called rtc-twl.
579 tristate "TI Palmas RTC driver"
582 If you say yes here you get support for the RTC of TI PALMA series PMIC
586 will be called rtc-palma.
589 tristate "TI TPS6586X RTC driver"
592 TI Power Management IC TPS6586X supports RTC functionality
593 along with alarm. This driver supports the RTC driver for
594 the TPS6586X RTC module.
597 tristate "TI TPS6594 RTC driver"
601 TI Power Management IC TPS6594 supports RTC functionality
602 along with alarm. This driver supports the RTC driver for
603 the TPS6594 RTC module.
606 will be called rtc-tps6594.
609 tristate "TI TPS65910 RTC driver"
612 If you say yes here you get support for the RTC on the
616 will be called rtc-tps65910.
619 tristate "RICOH 5T583 RTC driver"
622 If you say yes here you get support for the RTC on the
626 will be called rtc-rc5t583.
629 tristate "RICOH RC5T619 RTC driver"
632 If you say yes here you get support for the RTC on the
636 will be called rtc-rc5t619.
639 tristate "Seiko Instruments S-35390A"
643 Instruments S-35390A.
646 will be called rtc-s35390a.
652 Ramtron FM3130 RTC chips.
654 RTC clock and FRAM. This driver provides only RTC functionality.
657 will be called rtc-fm3130.
663 If you say yes here you get support for the Epson RX8010SJ RTC
667 will be called rtc-rx8010.
674 If you say yes here you will get support for the Epson RX8111 RTC.
677 called rtc-rx8111.
680 tristate "Epson RX-8571/RX-8581"
683 If you say yes here you will get support for the Epson RX-8571/
684 RX-8581.
687 will be called rtc-rx8581.
690 tristate "Epson RX-8025SA/NB"
693 RX-8025SA/NB RTC chips.
696 will be called rtc-rx8025.
702 Microelectronic EM3027 RTC chips.
705 will be called rtc-em3027.
715 will be called rtc-rv3028.
725 will be called rtc-rv3032.
731 Epson RX8900 RTC chips.
734 will be called rtc-rv8803.
743 RTC of Samsung S2MPS14 and S5M PMIC series.
746 will be called rtc-s5m.
753 DFRobot SD2405AL I2C RTC Module.
756 will be called rtc-sd2405al.
763 SD3078 RTC chips.
766 will be called rtc-sd3078
770 comment "SPI RTC drivers"
778 ST M41T93 SPI RTC chip.
781 will be called rtc-m41t93.
787 ST M41T94 SPI RTC chip.
790 will be called rtc-m41t94.
796 If you say yes here you get support for the Dallas DS1302 RTC chips.
799 will be called rtc-ds1302.
809 will be called rtc-ds1305.
820 will be called rtc-ds1343.
829 This driver only supports the RTC feature, and not other chip
833 will be called rtc-ds1347.
841 This driver supports the RTC feature and trickle charging but not
845 will be called rtc-ds1390.
851 Maxim MAX6916 SPI RTC chip.
853 This driver only supports the RTC feature, and not other chip
857 will be called rtc-max6916.
860 tristate "Epson RTC-9701JE"
863 Epson RTC-9701JE SPI RTC chip.
866 will be called rtc-r9701.
869 tristate "Epson RX-4581"
871 If you say yes here you will get support for the Epson RX-4581.
874 will be called rtc-rx4581.
880 Ricoh RS5C348A and RS5C348B RTC chips.
883 will be called rtc-rs5c348.
889 Maxim MAX6902 SPI RTC chip.
892 will be called rtc-max6902.
899 RTC chip.
902 will be called rtc-pcf2123.
910 will be called rtc-mcp795.
924 comment "SPI and I2C RTC drivers"
933 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
937 will be called rtc-ds3232.
945 rtc-ds3232
954 If you say yes here you get support for the NXP PCF2127/29/31 RTC
963 will be called rtc-pcf2127.
972 RTC chips.
975 will be called rtc-pcf85063.
984 RV3029 and RV3049 RTC chips.
987 will be called rtc-rv3029c2.
996 rtc-rv3029.
999 tristate "Epson RX-6110"
1004 If you say yes here you will get support for the Epson RX-6110.
1007 will be called rtc-rx6110.
1009 comment "Platform RTC drivers"
1011 # this 'CMOS' RTC driver is arch dependent because it requires
1016 tristate "PC-style 'CMOS'"
1023 found in every PC or ACPI-based system, and some other boards.
1034 will be called rtc-cmos.
1037 bool "Alpha PC-style CMOS"
1043 Direct support for the real-time clock found on every Alpha
1050 If you say yes here you get support for the Dallas DS1216 RTC chips.
1056 If you say yes here you get support for the Dallas DS1286 RTC chips.
1066 will be called rtc-ds1511.
1076 will be called rtc-ds1553.
1088 will be called rtc-ds1685.
1102 systems, as well as EPPC-405-UC modules by electronic system design
1111 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
1113 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
1115 It also works for the even older DS1688/DS1691 RTC chips, which are
1125 This chip features 2kb of extended NV-SRAM. It may possibly be
1134 This chip features 4kb of extended NV-SRAM.
1142 This chip features 8kb of extended NV-SRAM.
1154 will be called rtc-ds1742.
1160 Dallas DS2404 RTC chip.
1163 will be called rtc-ds2404.
1166 tristate "Dialog DA9052/DA9053 RTC"
1169 Say y here to support the RTC driver for Dialog Semiconductor
1170 DA9052-BC and DA9053-AA/Bx PMICs.
1173 tristate "Dialog Semiconductor DA9055 RTC"
1177 RTC of the Dialog DA9055 PMIC.
1180 will be called rtc-da9055
1183 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1186 If you say yes here you will get support for the RTC subsystem
1190 will be called "rtc-da9063".
1193 tristate "EFI RTC"
1200 will be called rtc-efi.
1210 will be called rtc-stk17ta8.
1217 ST M48T86 and Dallas DS12887 RTC chips.
1220 will be called rtc-m48t86.
1227 ST M48T35 RTC chip.
1230 will be called "rtc-m48t35".
1237 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1243 will be called "rtc-m48t59".
1253 will be called rtc-msm6242.
1261 BQ4802 RTC chip.
1264 will be called rtc-bq4802.
1275 will be called rtc-rp5c01.
1278 tristate "Nintendo GameCube, Wii and Wii U RTC"
1282 If you say yes here you will get support for the RTC subsystem
1286 will be called "rtc-gamecube".
1289 tristate "Wolfson Microelectronics WM831x RTC"
1292 If you say yes here you will get support for the RTC subsystem
1296 will be called "rtc-wm831x".
1299 tristate "Wolfson Microelectronics WM8350 RTC"
1302 If you say yes here you will get support for the RTC subsystem
1306 will be called "rtc-wm8350".
1309 tristate "Spreadtrum SC27xx RTC"
1312 If you say Y here you will get support for the RTC subsystem
1317 will be called rtc-sc27xx.
1320 tristate "SPEAR ST RTC"
1324 If you say Y here you will get support for the RTC found on
1328 tristate "ST-Ericsson AB8500 RTC"
1333 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1334 support. This chip contains a battery- and capacitor-backed RTC.
1337 tristate "IBM OPAL RTC driver"
1341 If you say yes here you get support for the PowerNV platform RTC
1345 will be called rtc-opal.
1348 tristate "OP-TEE based RTC driver"
1351 Select this to get support for OP-TEE based RTC control on SoCs where
1352 RTC are not accessible to the normal world (Linux).
1355 will be called rtc-optee.
1358 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1361 If you say yes here you get support for the RTC controller found on
1365 tristate "Chrome OS EC RTC driver"
1369 Chrome OS Embedded Controller's RTC.
1372 will be called rtc-cros-ec.
1375 tristate "Netronix embedded controller RTC"
1378 Say yes here if you want to support the RTC functionality of the
1379 embedded controller found in certain e-book readers designed by the
1382 comment "on-CPU RTC drivers"
1385 tristate "Alphascale asm9260 RTC"
1388 If you say yes here you get support for the RTC on the
1392 will be called rtc-asm9260.
1395 tristate "Sophgo CV1800 RTC"
1400 If you say yes here you get support the RTC driver for Sophgo CV1800
1404 called rtc-cv1800.
1407 tristate "Conexant Digicolor RTC"
1410 If you say yes here you get support for the RTC on Conexant
1414 will be called rtc-digicolor.
1421 Support for Freescale IMX DryIce RTC
1424 will be called "rtc-imxdi".
1437 will be called "rtc-fsl-ftm-alarm".
1440 tristate "Amlogic Meson RTC"
1444 Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1448 will be called "rtc-meson".
1451 tristate "Amlogic Meson Virtual RTC"
1456 Virtual RTC of Amlogic SoCs.
1459 will be called rtc-meson-vrtc.
1469 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1472 will be called rtc-omap.
1475 tristate "Samsung S3C series SoC RTC"
1479 RTC (Realtime Clock) driver for the clock inbuilt into the
1485 will be called rtc-s3c.
1492 RTC embedded in the Cirrus Logic EP93XX processors.
1495 will be called rtc-ep93xx.
1505 module will be called rtc-sa1100.
1508 tristate "SuperH On-Chip RTC"
1511 Say Y here to enable support for the on-chip RTC found in
1512 most SuperH processors. This RTC is also found in RZ/A SoCs.
1515 module will be called rtc-sh.
1518 tristate "Sunplus SP7021 RTC"
1521 Say 'yes' to get support for the real-time clock present in
1522 Sunplus SP7021 - a SoC for industrial applications. It provides
1523 RTC status check, timer/alarm functionalities, user data
1524 reservation with the battery over 2.5V, RTC power status check
1528 will be called rtc-sunplus.
1531 tristate "ARM AMBA PL030 RTC"
1535 PrimeCell PL030 RTC found on certain ARM SOCs.
1538 module will be called rtc-pl030.
1541 tristate "ARM AMBA PL031 RTC"
1545 PrimeCell PL031 RTC found on certain ARM SOCs.
1548 module will be called rtc-pl031.
1551 tristate "AT91RM9200 or some AT91SAM9 RTC"
1555 Driver for the internal RTC (Realtime Clock) module found on
1560 tristate "AT91SAM9 RTT as RTC"
1566 can be used as an RTC thanks to the backup power supply (e.g. a
1570 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1571 probably want to use the real RTC block instead of the "RTT as an
1572 RTC" driver.
1575 tristate "Au1xxx Counter0 RTC support"
1578 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1579 counter) to be used as a RTC.
1582 will be called rtc-au1xxx.
1588 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1591 tristate "Renesas RZ/N1 RTC"
1595 If you say yes here you get support for the Renesas RZ/N1 RTC.
1598 tristate "Generic RTC support"
1599 # Please consider writing a new RTC driver instead of using the generic
1600 # RTC abstraction
1603 Say Y or M here to enable RTC support on systems using the generic
1604 RTC abstraction. If you do not know what you are doing, you should
1613 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1614 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1616 This RTC driver uses PXA RTC registers available since pxa27x
1620 tristate "VIA/WonderMedia 85xx SoC RTC"
1628 bool "SUN4V Hypervisor RTC"
1632 based RTC on SUN4V systems.
1635 bool "Allwinner A31 RTC"
1640 If you say Y here you will get support for the RTC found in
1644 tristate "Allwinner sun4i/sun7i RTC"
1647 If you say Y here you will get support for the RTC found on
1651 bool "Starfire RTC"
1654 If you say Y here you will get support for the RTC found on
1658 tristate "Marvell SoC RTC"
1661 If you say yes here you will get support for the in-chip RTC
1666 will be called rtc-mv.
1669 tristate "Armada 38x Marvell SoC RTC"
1673 If you say yes here you will get support for the in-chip RTC
1677 will be called armada38x-rtc.
1680 tristate "Cadence RTC driver"
1683 If you say Y here you will get access to Cadence RTC IP
1687 module will be called rtc-cadence.
1690 tristate "Faraday Technology FTRTC010 RTC"
1698 will be called rtc-ftrtc010.
1701 tristate "PS3 RTC"
1704 If you say yes here you will get support for the RTC on PS3.
1707 will be called rtc-ps3.
1710 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1715 STMP3xxx/i.MX23/i.MX28 RTC.
1718 will be called rtc-stmp3xxx.
1721 tristate "PCAP RTC"
1724 If you say Y here you will get support for the RTC found on
1729 tristate "Freescale MC13xxx RTC"
1735 tristate "Freescale MPC5121 built-in RTC"
1739 built-in RTC on MPC5121 or on MPC5200.
1742 will be called rtc-mpc5121.
1749 If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1753 will be called rtc-jz4740.
1756 tristate "Loongson On-chip RTC"
1760 This is a driver for the Loongson on-chip Counter0 (Time-Of-Year
1761 counter) to be used as a RTC.
1762 It can be found on Loongson-1 series cpu, Loongson-2K series cpu
1766 will be called rtc-loongson.
1769 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1774 This enables support for the NXP RTC found which can be found on
1778 the hardware RTC. This driver can also be built as a module. If
1779 so, the module will be called rtc-lpc24xx.
1783 tristate "NXP LPC32XX RTC"
1785 This enables support for the NXP RTC in the LPC32XX
1788 will be called rtc-lpc32xx.
1791 tristate "Qualcomm PMIC8XXX RTC"
1795 Qualcomm PMIC8XXX RTC.
1798 module will be called rtc-pm8xxx.
1801 tristate "NVIDIA Tegra Internal RTC driver"
1805 Tegra 200 series internal RTC module.
1808 will be called rtc-tegra.
1817 RTC module.
1820 will be called "rtc-mxc".
1832 will be called "rtc-mxc_v2".
1835 tristate "Freescale SNVS RTC support"
1841 If you say yes here you get support for the Freescale SNVS
1842 Low Power (LP) RTC module.
1845 will be called "rtc-snvs".
1848 tristate "NXP BBNSM RTC support"
1854 If you say yes here you get support for the NXP BBNSM RTC module.
1857 will be called "rtc-bbnsm".
1862 tristate "NXP i.MX BBM SCMI RTC support"
1865 RTC module.
1868 module will be called rtc-imx-sm-bbm.
1873 tristate "NXP i.MX System Controller RTC support"
1876 Controller RTC module.
1879 tristate "STMicroelectronics LPC RTC"
1884 (LPC) based RTC support.
1887 module will be called rtc-st-lpc.
1890 tristate "MOXA ART RTC"
1894 RTC module.
1897 will be called rtc-moxart
1900 tristate "MediaTek MT2712 SoC based RTC"
1907 will be called rtc-mt2712.
1910 tristate "MediaTek PMIC based RTC"
1914 This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1916 MediaTek(R) RTC driver.
1918 If you want to use MediaTek(R) RTC interface, select Y or M here.
1921 tristate "MediaTek SoC based RTC"
1928 will be called rtc-mt7622.
1931 tristate "APM X-Gene RTC"
1935 If you say yes here you get support for the APM X-Gene SoC real time
1939 will be called "rtc-xgene".
1942 tristate "Microchip PIC32 RTC"
1946 If you say yes here you get support for the PIC32 RTC module.
1949 will be called rtc-pic32
1952 tristate "EPSON TOYOCOM RTC-7301SF/DG"
1957 RTC-7301SF/DG chips.
1960 will be called rtc-r7301.
1963 tristate "STM32 RTC"
1973 If you say yes here you get support for the STM32 On-Chip
1977 will be called "rtc-stm32".
1981 tristate "Motorola CPCAP RTC"
1983 Say y here for CPCAP rtc found on some Motorola phones
1987 bool "Realtek RTD129x RTC"
1995 tristate "ASPEED RTC"
2003 will be called "rtc-aspeed".
2006 tristate "TI K3 RTC"
2014 will be called "rtc-ti-k3".
2017 tristate "Nuvoton MA35D1 RTC"
2022 On-Chip Real Time Clock.
2025 will be called "rtc-ma35d1".
2028 tristate "Renesas RTCA-3 RTC"
2031 If you say yes here you get support for the Renesas RTCA-3 RTC
2035 will be called "rtc-rtca3".
2037 comment "HID Sensor RTC drivers"
2049 rtc-hid-sensor-time.
2055 Say yes to enable RTC driver for the Goldfish based virtual platform.
2061 tristate "Wilco EC RTC"
2072 tristate "MStar MSC313 RTC"
2075 If you say yes here you get support for the Mstar MSC313e On-Chip
2079 will be called "rtc-msc313".
2082 tristate "Microchip PolarFire SoC built-in RTC"
2086 built-in RTC on Polarfire SoC.
2089 will be called "rtc-mpfs".
2092 tristate "SigmaStar SSD202D RTC"
2096 If you say yes here you get support for the SigmaStar SSD202D On-Chip
2100 will be called "rtc-ssd20xd".
2103 tristate "Amlogic RTC"
2108 If you say yes here you get support for the RTC block on the
2112 will be called "rtc-amlogic-a4".
2115 tristate "RTC driver for S32G2/S32G3 SoCs"
2119 Say yes to enable RTC driver for platforms based on the
2122 This RTC module can be used as a wakeup source.
2123 Please note that it is not battery-powered.