# SPDX-License-Identifier: GPL-2.0-only## RTC class/drivers configuration# config RTC_LIB bool config RTC_MC146818_LIB bool select RTC_LIB menuconfig RTC_CLASS bool "Real Time Clock" default n depends on !S390 select RTC_LIB help Generic RTC class support. If you say yes here, you will be allowed to plug one or more RTCs to your system. You will probably want to enable one or more of the interfaces below. if RTC_CLASS config RTC_HCTOSYS bool "Set system time from RTC on startup and resume" default y help If you say yes here, the system time (wall clock) will be set using the value read from a specified RTC device. This is useful to avoid unnecessary fsck runs at boot time, and to network better. config RTC_HCTOSYS_DEVICE string "RTC used to set the system time" depends on RTC_HCTOSYS default "rtc0" help The RTC device that will be used to (re)initialize the system clock, usually rtc0. Initialization is done when the system starts up, and when it resumes from a low power state. This device should record time in UTC, since the kernel won't do timezone correction. This clock should be battery-backed, so that it reads the correct time when the system boots from a power-off state. Otherwise, your system will need an external clock source (like an NTP server). If the clock you specify here is not battery backed, it may still be useful to reinitialize system time when resuming from system sleep states. Do not specify an RTC here unless it stays powered during all this system's supported sleep states. config RTC_SYSTOHC bool "Set the RTC time based on NTP synchronization" default y help If you say yes here, the system time (wall clock) will be stored in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11 minutes if userspace reports synchronized NTP status. config RTC_SYSTOHC_DEVICE string "RTC used to synchronize NTP adjustment" depends on RTC_SYSTOHC default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS default "rtc0" help The RTC device used for NTP synchronization. The main difference between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this one can sleep when setting time, because it runs in the workqueue context. config RTC_DEBUG bool "RTC debug support" help Say yes here to enable debugging support in the RTC framework and individual RTC drivers. config RTC_LIB_KUNIT_TEST tristate "KUnit test for RTC lib functions" if !KUNIT_ALL_TESTS depends on KUNIT default KUNIT_ALL_TESTS help Enable this option to test RTC library functions. If unsure, say N. config RTC_NVMEM bool "RTC non volatile storage support" select NVMEM default RTC_CLASS help Say yes here to add support for the non volatile (often battery backed) storage present on RTCs. comment "RTC interfaces" config RTC_INTF_SYSFS bool "/sys/class/rtc/rtcN (sysfs)" depends on SYSFS default RTC_CLASS help Say yes here if you want to use your RTCs using sysfs interfaces, /sys/class/rtc/rtc0 through /sys/.../rtcN. If unsure, say Y. config RTC_INTF_PROC bool "/proc/driver/rtc (procfs for rtcN)" depends on PROC_FS default RTC_CLASS help Say yes here if you want to use your system clock RTC through the proc interface, /proc/driver/rtc. Other RTCs will not be available through that API. If there is no RTC for the system clock, then the first RTC(rtc0) is used by default. If unsure, say Y. config RTC_INTF_DEV bool "/dev/rtcN (character devices)" default RTC_CLASS help Say yes here if you want to use your RTCs using the /dev interfaces, which "udev" sets up as /dev/rtc0 through /dev/rtcN. You may want to set up a symbolic link so one of these can be accessed as /dev/rtc, which is a name expected by "hwclock" and some other programs. Recent versions of "udev" are known to set up the symlink for you. If unsure, say Y. config RTC_INTF_DEV_UIE_EMUL bool "RTC UIE emulation on dev interface" depends on RTC_INTF_DEV help Provides an emulation for RTC_UIE if the underlying rtc chip driver does not expose RTC_UIE ioctls. Those requests generate once-per-second update interrupts, used for synchronization. The emulation code will read the time from the hardware clock several times per second, please enable this option only if you know that you really need it. config RTC_DRV_TEST tristate "Test driver/device" help If you say yes here you get support for the RTC test driver. It's a software RTC which can be used to test the RTC subsystem APIs. It gets the time from the system clock. You want this driver only if you are doing development on the RTC subsystem. Please read the source code for further details. This driver can also be built as a module. If so, the module will be called rtc-test. comment "I2C RTC drivers" if I2C config RTC_DRV_88PM860X tristate "Marvell 88PM860x" depends on MFD_88PM860X help If you say yes here you get support for RTC function in Marvell 88PM860x chips. This driver can also be built as a module. If so, the module will be called rtc-88pm860x. config RTC_DRV_88PM80X tristate "Marvell 88PM80x" depends on MFD_88PM800 help If you say yes here you get support for RTC function in Marvell 88PM80x chips. This driver can also be built as a module. If so, the module will be called rtc-88pm80x. config RTC_DRV_88PM886 tristate "Marvell 88PM886 RTC driver" depends on MFD_88PM886_PMIC help If you say yes here you will get support for the RTC function in the Marvell 88PM886 chip. This driver can also be built as a module. If so, the module will be called rtc-88pm886. config RTC_DRV_ABB5ZES3 select REGMAP_I2C tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3" help If you say yes here you get support for the Abracon AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip. This driver can also be built as a module. If so, the module will be called rtc-ab-b5ze-s3. config RTC_DRV_ABEOZ9 select REGMAP_I2C tristate "Abracon AB-RTCMC-32.768kHz-EOZ9" help If you say yes here you get support for the Abracon AB-RTCMC-32.768kHz-EOA9 I2C RTC chip. This driver can also be built as a module. If so, the module will be called rtc-ab-e0z9. config RTC_DRV_ABX80X tristate "Abracon ABx80x" select WATCHDOG_CORE if WATCHDOG help If you say yes here you get support for Abracon AB080X and AB180X families of ultra-low-power battery- and capacitor-backed real-time clock chips. This driver can also be built as a module. If so, the module will be called rtc-abx80x. config RTC_DRV_AC100 tristate "X-Powers AC100" depends on MFD_AC100 help If you say yes here you get support for the real-time clock found in X-Powers AC100 family peripheral ICs. This driver can also be built as a module. If so, the module will be called rtc-ac100. config RTC_DRV_BRCMSTB tristate "Broadcom STB wake-timer" depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST default ARCH_BRCMSTB || BMIPS_GENERIC help If you say yes here you get support for the wake-timer found on Broadcom STB SoCs (BCM7xxx). This driver can also be built as a module. If so, the module will be called rtc-brcmstb-waketimer. config RTC_DRV_AS3722 tristate "ams AS3722 RTC driver" depends on MFD_AS3722 help If you say yes here you get support for the RTC of ams AS3722 PMIC chips. This driver can also be built as a module. If so, the module will be called rtc-as3722. config RTC_DRV_DS1307 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057" select REGMAP_I2C select WATCHDOG_CORE if WATCHDOG help If you say yes here you get support for various compatible RTC chips (often with battery backup) connected with I2C. This driver should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341, ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips. In some cases the RTC must already have been initialized (by manufacturing or a bootloader). The first seven registers on these chips hold an RTC, and other registers may add features such as NVRAM, a trickle charger for the RTC/NVRAM backup power, and alarms. NVRAM is visible in sysfs, but other chip features may not be available. This driver can also be built as a module. If so, the module will be called rtc-ds1307. config RTC_DRV_DS1307_CENTURY bool "Century bit support for rtc-ds1307" depends on RTC_DRV_DS1307 default n help The DS1307 driver suffered from a bug where it was enabling the century bit inconditionnally but never used it when reading the time. It made the driver unable to support dates beyond 2099. Setting this option will add proper support for the century bit but if the time was previously set using a kernel predating this option, reading the date will return a date in the next century. To solve that, you could boot a kernel without this option set, set the RTC date and then boot a kernel with this option set. config RTC_DRV_DS1374 tristate "Dallas/Maxim DS1374" help If you say yes here you get support for Dallas Semiconductor DS1374 real-time clock chips. If an interrupt is associated with the device, the alarm functionality is supported. This driver can also be built as a module. If so, the module will be called rtc-ds1374. config RTC_DRV_DS1374_WDT bool "Dallas/Maxim DS1374 watchdog timer" depends on RTC_DRV_DS1374 && WATCHDOG select WATCHDOG_CORE help If you say Y here you will get support for the watchdog timer in the Dallas Semiconductor DS1374 real-time clock chips. config RTC_DRV_DS1672 tristate "Dallas/Maxim DS1672" help If you say yes here you get support for the Dallas/Maxim DS1672 timekeeping chip. This driver can also be built as a module. If so, the module will be called rtc-ds1672. config RTC_DRV_HYM8563 tristate "Haoyu Microelectronics HYM8563" depends on OF help Say Y to enable support for the HYM8563 I2C RTC chip. Apart from the usual rtc functions it provides a clock output of up to 32kHz. This driver can also be built as a module. If so, the module will be called rtc-hym8563. config RTC_DRV_LP8788 tristate "TI LP8788 RTC driver" depends on MFD_LP8788 help Say Y to enable support for the LP8788 RTC/ALARM driver. config RTC_DRV_MAX6900 tristate "Maxim MAX6900" help If you say yes here you will get support for the Maxim MAX6900 I2C RTC chip. This driver can also be built as a module. If so, the module will be called rtc-max6900. config RTC_DRV_MAX8907 tristate "Maxim MAX8907" depends on MFD_MAX8907 || COMPILE_TEST select REGMAP_IRQ help If you say yes here you will get support for the RTC of Maxim MAX8907 PMIC. This driver can also be built as a module. If so, the module will be called rtc-max8907. config RTC_DRV_MAX8925 tristate "Maxim MAX8925" depends on MFD_MAX8925 help If you say yes here you will get support for the RTC of Maxim MAX8925 PMIC. This driver can also be built as a module. If so, the module will be called rtc-max8925. config RTC_DRV_MAX8998 tristate "Maxim MAX8998" depends on MFD_MAX8998 help If you say yes here you will get support for the RTC of Maxim MAX8998 PMIC. This driver can also be built as a module. If so, the module will be called rtc-max8998. config RTC_DRV_MAX8997 tristate "Maxim MAX8997" depends on MFD_MAX8997 help If you say yes here you will get support for the RTC of Maxim MAX8997 PMIC. This driver can also be built as a module. If so, the module will be called rtc-max8997. config RTC_DRV_MAX31335 tristate "Analog Devices MAX31335" depends on I2C depends on COMMON_CLK depends on HWMON || HWMON=n select REGMAP_I2C help If you say yes here you get support for the Analog Devices MAX31335. This driver can also be built as a module. If so, the module will be called rtc-max31335. config RTC_DRV_MAX77686 tristate "Maxim MAX77686" depends on MFD_MAX77686 || MFD_MAX77620 || MFD_MAX77714 || COMPILE_TEST help If you say yes here you will get support for the RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC. This driver can also be built as a module. If so, the module will be called rtc-max77686. config RTC_DRV_SPACEMIT_P1 tristate "SpacemiT P1 RTC" depends on ARCH_SPACEMIT || COMPILE_TEST depends on MFD_SPACEMIT_P1 default MFD_SPACEMIT_P1 help Enable support for the RTC function in the SpacemiT P1 PMIC. This driver can also be built as a module, which will be called "spacemit-p1-rtc". config RTC_DRV_NVIDIA_VRS10 tristate "NVIDIA VRS10 RTC device" depends on ARCH_TEGRA || COMPILE_TEST help If you say yes here you will get support for the battery backed RTC device of NVIDIA VRS (Voltage Regulator Specification). The RTC is connected via I2C interface and supports alarm functionality. This driver can also be built as a module. If so, the module will be called rtc-nvidia-vrs10. config RTC_DRV_NCT3018Y tristate "Nuvoton NCT3018Y" depends on OF help If you say yes here you get support for the Nuvoton NCT3018Y I2C RTC chip. This driver can also be built as a module, if so, the module will be called "rtc-nct3018y". config RTC_DRV_NCT6694 tristate "Nuvoton NCT6694 RTC support" depends on MFD_NCT6694 help If you say yes to this option, support will be included for Nuvoton NCT6694, a USB device to RTC. This driver can also be built as a module. If so, the module will be called rtc-nct6694. config RTC_DRV_RK808 tristate "Rockchip RK805/RK808/RK809/RK817/RK818 RTC" depends on MFD_RK8XX help If you say yes here you will get support for the RTC of RK805, RK809 and RK817, RK808 and RK818 PMIC. This driver can also be built as a module. If so, the module will be called rk808-rtc. config RTC_DRV_RS5C372 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A" help If you say yes here you get support for the Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. This driver can also be built as a module. If so, the module will be called rtc-rs5c372. config RTC_DRV_ISL1208 tristate "Intersil ISL1208" help If you say yes here you get support for the Intersil ISL1208 RTC chip. This driver can also be built as a module. If so, the module will be called rtc-isl1208. config RTC_DRV_ISL12022 tristate "Intersil ISL12022" select REGMAP_I2C help If you say yes here you get support for the Intersil ISL12022 RTC chip. This driver can also be built as a module. If so, the module will be called rtc-isl12022. config RTC_DRV_ISL12026 tristate "Intersil ISL12026" depends on OF help If you say yes here you get support for the Intersil ISL12026 RTC chip. This driver can also be built as a module. If so, the module will be called rtc-isl12026. config RTC_DRV_X1205 tristate "Xicor/Intersil X1205" help If you say yes here you get support for theLines 1–500 of 2177. Load more
# SPDX-License-Identifier: GPL-2.0-only # # RTC class/drivers configuration # config RTC_LIB bool config RTC_MC146818_LIB bool select RTC_LIB menuconfig RTC_CLASS bool "Real Time Clock" default n depends on !S390 select RTC_LIB help Generic RTC class support. If you say yes here, you will be allowed to plug one or more RTCs to your system. You will probably want to enable one or more of the interfaces below. if RTC_CLASS config RTC_HCTOSYS bool "Set system time from RTC on startup and resume" default y help If you say yes here, the system time (wall clock) will be set using the value read from a specified RTC device. This is useful to avoid unnecessary fsck runs at boot time, and to network better. config RTC_HCTOSYS_DEVICE string "RTC used to set the system time" depends on RTC_HCTOSYS default "rtc0" help The RTC device that will be used to (re)initialize the system clock, usually rtc0. Initialization is done when the system starts up, and when it resumes from a low power state. This device should record time in UTC, since the kernel won't do timezone correction. This clock should be battery-backed, so that it reads the correct time when the system boots from a power-off state. Otherwise, your system will need an external clock source (like an NTP server). If the clock you specify here is not battery backed, it may still be useful to reinitialize system time when resuming from system sleep states. Do not specify an RTC here unless it stays powered during all this system's supported sleep states. config RTC_SYSTOHC bool "Set the RTC time based on NTP synchronization" default y help If you say yes here, the system time (wall clock) will be stored in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11 minutes if userspace reports synchronized NTP status. config RTC_SYSTOHC_DEVICE string "RTC used to synchronize NTP adjustment" depends on RTC_SYSTOHC default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS default "rtc0" help The RTC device used for NTP synchronization. The main difference between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this one can sleep when setting time, because it runs in the workqueue context. config RTC_DEBUG bool "RTC debug support" help Say yes here to enable debugging support in the RTC framework and individual RTC drivers. config RTC_LIB_KUNIT_TEST tristate "KUnit test for RTC lib functions" if !KUNIT_ALL_TESTS depends on KUNIT default KUNIT_ALL_TESTS help Enable this option to test RTC library functions. If unsure, say N. config RTC_NVMEM bool "RTC non volatile storage support" select NVMEM default RTC_CLASS help Say yes here to add support for the non volatile (often battery backed) storage present on RTCs. comment "RTC interfaces" config RTC_INTF_SYSFS bool "/sys/class/rtc/rtcN (sysfs)" depends on SYSFS default RTC_CLASS help Say yes here if you want to use your RTCs using sysfs interfaces, /sys/class/rtc/rtc0 through /sys/.../rtcN. If unsure, say Y. config RTC_INTF_PROC bool "/proc/driver/rtc (procfs for rtcN)" depends on PROC_FS default RTC_CLASS help Say yes here if you want to use your system clock RTC through the proc interface, /proc/driver/rtc. Other RTCs will not be available through that API. If there is no RTC for the system clock, then the first RTC(rtc0) is used by default. If unsure, say Y. config RTC_INTF_DEV bool "/dev/rtcN (character devices)" default RTC_CLASS help Say yes here if you want to use your RTCs using the /dev interfaces, which "udev" sets up as /dev/rtc0 through /dev/rtcN. You may want to set up a symbolic link so one of these can be accessed as /dev/rtc, which is a name expected by "hwclock" and some other programs. Recent versions of "udev" are known to set up the symlink for you. If unsure, say Y. config RTC_INTF_DEV_UIE_EMUL bool "RTC UIE emulation on dev interface" depends on RTC_INTF_DEV help Provides an emulation for RTC_UIE if the underlying rtc chip driver does not expose RTC_UIE ioctls. Those requests generate once-per-second update interrupts, used for synchronization. The emulation code will read the time from the hardware clock several times per second, please enable this option only if you know that you really need it. config RTC_DRV_TEST tristate "Test driver/device" help If you say yes here you get support for the RTC test driver. It's a software RTC which can be used to test the RTC subsystem APIs. It gets the time from the system clock. You want this driver only if you are doing development on the RTC subsystem. Please read the source code for further details. This driver can also be built as a module. If so, the module will be called rtc-test. comment "I2C RTC drivers" if I2C config RTC_DRV_88PM860X tristate "Marvell 88PM860x" depends on MFD_88PM860X help If you say yes here you get support for RTC function in Marvell 88PM860x chips. This driver can also be built as a module. If so, the module will be called rtc-88pm860x. config RTC_DRV_88PM80X tristate "Marvell 88PM80x" depends on MFD_88PM800 help If you say yes here you get support for RTC function in Marvell 88PM80x chips. This driver can also be built as a module. If so, the module will be called rtc-88pm80x. config RTC_DRV_88PM886 tristate "Marvell 88PM886 RTC driver" depends on MFD_88PM886_PMIC help If you say yes here you will get support for the RTC function in the Marvell 88PM886 chip. This driver can also be built as a module. If so, the module will be called rtc-88pm886. config RTC_DRV_ABB5ZES3 select REGMAP_I2C tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3" help If you say yes here you get support for the Abracon AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip. This driver can also be built as a module. If so, the module will be called rtc-ab-b5ze-s3. config RTC_DRV_ABEOZ9 select REGMAP_I2C tristate "Abracon AB-RTCMC-32.768kHz-EOZ9" help If you say yes here you get support for the Abracon AB-RTCMC-32.768kHz-EOA9 I2C RTC chip. This driver can also be built as a module. If so, the module will be called rtc-ab-e0z9. config RTC_DRV_ABX80X tristate "Abracon ABx80x" select WATCHDOG_CORE if WATCHDOG help If you say yes here you get support for Abracon AB080X and AB180X families of ultra-low-power battery- and capacitor-backed real-time clock chips. This driver can also be built as a module. If so, the module will be called rtc-abx80x. config RTC_DRV_AC100 tristate "X-Powers AC100" depends on MFD_AC100 help If you say yes here you get support for the real-time clock found in X-Powers AC100 family peripheral ICs. This driver can also be built as a module. If so, the module will be called rtc-ac100. config RTC_DRV_BRCMSTB tristate "Broadcom STB wake-timer" depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST default ARCH_BRCMSTB || BMIPS_GENERIC help If you say yes here you get support for the wake-timer found on Broadcom STB SoCs (BCM7xxx). This driver can also be built as a module. If so, the module will be called rtc-brcmstb-waketimer. config RTC_DRV_AS3722 tristate "ams AS3722 RTC driver" depends on MFD_AS3722 help If you say yes here you get support for the RTC of ams AS3722 PMIC chips. This driver can also be built as a module. If so, the module will be called rtc-as3722. config RTC_DRV_DS1307 tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057" select REGMAP_I2C select WATCHDOG_CORE if WATCHDOG help If you say yes here you get support for various compatible RTC chips (often with battery backup) connected with I2C. This driver should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341, ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips. In some cases the RTC must already have been initialized (by manufacturing or a bootloader). The first seven registers on these chips hold an RTC, and other registers may add features such as NVRAM, a trickle charger for the RTC/NVRAM backup power, and alarms. NVRAM is visible in sysfs, but other chip features may not be available. This driver can also be built as a module. If so, the module will be called rtc-ds1307. config RTC_DRV_DS1307_CENTURY bool "Century bit support for rtc-ds1307" depends on RTC_DRV_DS1307 default n help The DS1307 driver suffered from a bug where it was enabling the century bit inconditionnally but never used it when reading the time. It made the driver unable to support dates beyond 2099. Setting this option will add proper support for the century bit but if the time was previously set using a kernel predating this option, reading the date will return a date in the next century. To solve that, you could boot a kernel without this option set, set the RTC date and then boot a kernel with this option set. config RTC_DRV_DS1374 tristate "Dallas/Maxim DS1374" help If you say yes here you get support for Dallas Semiconductor DS1374 real-time clock chips. If an interrupt is associated with the device, the alarm functionality is supported. This driver can also be built as a module. If so, the module will be called rtc-ds1374. config RTC_DRV_DS1374_WDT bool "Dallas/Maxim DS1374 watchdog timer" depends on RTC_DRV_DS1374 && WATCHDOG select WATCHDOG_CORE help If you say Y here you will get support for the watchdog timer in the Dallas Semiconductor DS1374 real-time clock chips. config RTC_DRV_DS1672 tristate "Dallas/Maxim DS1672" help If you say yes here you get support for the Dallas/Maxim DS1672 timekeeping chip. This driver can also be built as a module. If so, the module will be called rtc-ds1672. config RTC_DRV_HYM8563 tristate "Haoyu Microelectronics HYM8563" depends on OF help Say Y to enable support for the HYM8563 I2C RTC chip. Apart from the usual rtc functions it provides a clock output of up to 32kHz. This driver can also be built as a module. If so, the module will be called rtc-hym8563. config RTC_DRV_LP8788 tristate "TI LP8788 RTC driver" depends on MFD_LP8788 help Say Y to enable support for the LP8788 RTC/ALARM driver. config RTC_DRV_MAX6900 tristate "Maxim MAX6900" help If you say yes here you will get support for the Maxim MAX6900 I2C RTC chip. This driver can also be built as a module. If so, the module will be called rtc-max6900. config RTC_DRV_MAX8907 tristate "Maxim MAX8907" depends on MFD_MAX8907 || COMPILE_TEST select REGMAP_IRQ help If you say yes here you will get support for the RTC of Maxim MAX8907 PMIC. This driver can also be built as a module. If so, the module will be called rtc-max8907. config RTC_DRV_MAX8925 tristate "Maxim MAX8925" depends on MFD_MAX8925 help If you say yes here you will get support for the RTC of Maxim MAX8925 PMIC. This driver can also be built as a module. If so, the module will be called rtc-max8925. config RTC_DRV_MAX8998 tristate "Maxim MAX8998" depends on MFD_MAX8998 help If you say yes here you will get support for the RTC of Maxim MAX8998 PMIC. This driver can also be built as a module. If so, the module will be called rtc-max8998. config RTC_DRV_MAX8997 tristate "Maxim MAX8997" depends on MFD_MAX8997 help If you say yes here you will get support for the RTC of Maxim MAX8997 PMIC. This driver can also be built as a module. If so, the module will be called rtc-max8997. config RTC_DRV_MAX31335 tristate "Analog Devices MAX31335" depends on I2C depends on COMMON_CLK depends on HWMON || HWMON=n select REGMAP_I2C help If you say yes here you get support for the Analog Devices MAX31335. This driver can also be built as a module. If so, the module will be called rtc-max31335. config RTC_DRV_MAX77686 tristate "Maxim MAX77686" depends on MFD_MAX77686 || MFD_MAX77620 || MFD_MAX77714 || COMPILE_TEST help If you say yes here you will get support for the RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC. This driver can also be built as a module. If so, the module will be called rtc-max77686. config RTC_DRV_SPACEMIT_P1 tristate "SpacemiT P1 RTC" depends on ARCH_SPACEMIT || COMPILE_TEST depends on MFD_SPACEMIT_P1 default MFD_SPACEMIT_P1 help Enable support for the RTC function in the SpacemiT P1 PMIC. This driver can also be built as a module, which will be called "spacemit-p1-rtc". config RTC_DRV_NVIDIA_VRS10 tristate "NVIDIA VRS10 RTC device" depends on ARCH_TEGRA || COMPILE_TEST help If you say yes here you will get support for the battery backed RTC device of NVIDIA VRS (Voltage Regulator Specification). The RTC is connected via I2C interface and supports alarm functionality. This driver can also be built as a module. If so, the module will be called rtc-nvidia-vrs10. config RTC_DRV_NCT3018Y tristate "Nuvoton NCT3018Y" depends on OF help If you say yes here you get support for the Nuvoton NCT3018Y I2C RTC chip. This driver can also be built as a module, if so, the module will be called "rtc-nct3018y". config RTC_DRV_NCT6694 tristate "Nuvoton NCT6694 RTC support" depends on MFD_NCT6694 help If you say yes to this option, support will be included for Nuvoton NCT6694, a USB device to RTC. This driver can also be built as a module. If so, the module will be called rtc-nct6694. config RTC_DRV_RK808 tristate "Rockchip RK805/RK808/RK809/RK817/RK818 RTC" depends on MFD_RK8XX help If you say yes here you will get support for the RTC of RK805, RK809 and RK817, RK808 and RK818 PMIC. This driver can also be built as a module. If so, the module will be called rk808-rtc. config RTC_DRV_RS5C372 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A" help If you say yes here you get support for the Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. This driver can also be built as a module. If so, the module will be called rtc-rs5c372. config RTC_DRV_ISL1208 tristate "Intersil ISL1208" help If you say yes here you get support for the Intersil ISL1208 RTC chip. This driver can also be built as a module. If so, the module will be called rtc-isl1208. config RTC_DRV_ISL12022 tristate "Intersil ISL12022" select REGMAP_I2C help If you say yes here you get support for the Intersil ISL12022 RTC chip. This driver can also be built as a module. If so, the module will be called rtc-isl12022. config RTC_DRV_ISL12026 tristate "Intersil ISL12026" depends on OF help If you say yes here you get support for the Intersil ISL12026 RTC chip. This driver can also be built as a module. If so, the module will be called rtc-isl12026. config RTC_DRV_X1205 tristate "Xicor/Intersil X1205" help If you say yes here you get support for the