^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) # SPDX-License-Identifier: GPL-2.0-only
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) # RTC class/drivers configuration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) config RTC_LIB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) config RTC_MC146818_LIB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) select RTC_LIB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) menuconfig RTC_CLASS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) bool "Real Time Clock"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) default n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) depends on !S390 && !UML
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) select RTC_LIB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) Generic RTC class support. If you say yes here, you will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) be allowed to plug one or more RTCs to your system. You will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) probably want to enable one or more of the interfaces below.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) if RTC_CLASS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) config RTC_HCTOSYS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) bool "Set system time from RTC on startup and resume"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) If you say yes here, the system time (wall clock) will be set using
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) the value read from a specified RTC device. This is useful to avoid
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) unnecessary fsck runs at boot time, and to network better.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) config RTC_HCTOSYS_DEVICE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) string "RTC used to set the system time"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) depends on RTC_HCTOSYS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) default "rtc0"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) The RTC device that will be used to (re)initialize the system
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) clock, usually rtc0. Initialization is done when the system
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) starts up, and when it resumes from a low power state. This
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) device should record time in UTC, since the kernel won't do
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) timezone correction.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) This clock should be battery-backed, so that it reads the correct
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) time when the system boots from a power-off state. Otherwise, your
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) system will need an external clock source (like an NTP server).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) If the clock you specify here is not battery backed, it may still
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49) be useful to reinitialize system time when resuming from system
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) sleep states. Do not specify an RTC here unless it stays powered
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) during all this system's supported sleep states.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53) config RTC_SYSTOHC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) bool "Set the RTC time based on NTP synchronization"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) If you say yes here, the system time (wall clock) will be stored
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) minutes if userspace reports synchronized NTP status.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) config RTC_SYSTOHC_DEVICE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) string "RTC used to synchronize NTP adjustment"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63) depends on RTC_SYSTOHC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) default "rtc0"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67) The RTC device used for NTP synchronization. The main difference
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) one can sleep when setting time, because it runs in the workqueue
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70) context.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) config RTC_DEBUG
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) bool "RTC debug support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) Say yes here to enable debugging support in the RTC framework
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76) and individual RTC drivers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78) config RTC_NVMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79) bool "RTC non volatile storage support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80) select NVMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) default RTC_CLASS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) Say yes here to add support for the non volatile (often battery
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) backed) storage present on RTCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) comment "RTC interfaces"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) config RTC_INTF_SYSFS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89) bool "/sys/class/rtc/rtcN (sysfs)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90) depends on SYSFS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91) default RTC_CLASS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93) Say yes here if you want to use your RTCs using sysfs interfaces,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94) /sys/class/rtc/rtc0 through /sys/.../rtcN.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96) If unsure, say Y.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) config RTC_INTF_PROC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99) bool "/proc/driver/rtc (procfs for rtcN)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) depends on PROC_FS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) default RTC_CLASS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) Say yes here if you want to use your system clock RTC through
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) the proc interface, /proc/driver/rtc.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) Other RTCs will not be available through that API.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) If there is no RTC for the system clock, then the first RTC(rtc0)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) is used by default.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) If unsure, say Y.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) config RTC_INTF_DEV
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) bool "/dev/rtcN (character devices)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) default RTC_CLASS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) Say yes here if you want to use your RTCs using the /dev
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) interfaces, which "udev" sets up as /dev/rtc0 through
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) /dev/rtcN.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) You may want to set up a symbolic link so one of these
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) can be accessed as /dev/rtc, which is a name
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) expected by "hwclock" and some other programs. Recent
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) versions of "udev" are known to set up the symlink for you.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) If unsure, say Y.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) config RTC_INTF_DEV_UIE_EMUL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) bool "RTC UIE emulation on dev interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) depends on RTC_INTF_DEV
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) Provides an emulation for RTC_UIE if the underlying rtc chip
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131) driver does not expose RTC_UIE ioctls. Those requests generate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) once-per-second update interrupts, used for synchronization.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) The emulation code will read the time from the hardware
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) clock several times per second, please enable this option
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) only if you know that you really need it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) config RTC_DRV_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139) tristate "Test driver/device"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) RTC test driver. It's a software RTC which can be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) used to test the RTC subsystem APIs. It gets
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144) the time from the system clock.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) You want this driver only if you are doing development
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) on the RTC subsystem. Please read the source code
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) for further details.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) will be called rtc-test.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) comment "I2C RTC drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) if I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) config RTC_DRV_88PM860X
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) tristate "Marvell 88PM860x"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) depends on MFD_88PM860X
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) If you say yes here you get support for RTC function in Marvell
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) 88PM860x chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) will be called rtc-88pm860x.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) config RTC_DRV_88PM80X
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) tristate "Marvell 88PM80x"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) depends on MFD_88PM800
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) If you say yes here you get support for RTC function in Marvell
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) 88PM80x chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174) will be called rtc-88pm80x.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) config RTC_DRV_ABB5ZES3
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) select REGMAP_I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) If you say yes here you get support for the Abracon
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) will be called rtc-ab-b5ze-s3.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) config RTC_DRV_ABEOZ9
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) select REGMAP_I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) tristate "Abracon AB-RTCMC-32.768kHz-EOZ9"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) If you say yes here you get support for the Abracon
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) AB-RTCMC-32.768kHz-EOA9 I2C RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) will be called rtc-ab-e0z9.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) config RTC_DRV_ABX80X
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) tristate "Abracon ABx80x"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) select WATCHDOG_CORE if WATCHDOG
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200) If you say yes here you get support for Abracon AB080X and AB180X
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) families of ultra-low-power battery- and capacitor-backed real-time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202) clock chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205) will be called rtc-abx80x.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) config RTC_DRV_AC100
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208) tristate "X-Powers AC100"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) depends on MFD_AC100
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) If you say yes here you get support for the real-time clock found
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) in X-Powers AC100 family peripheral ICs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) will be called rtc-ac100.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) config RTC_DRV_BRCMSTB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) tristate "Broadcom STB wake-timer"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219) depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) default ARCH_BRCMSTB || BMIPS_GENERIC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222) If you say yes here you get support for the wake-timer found on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) Broadcom STB SoCs (BCM7xxx).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) This driver can also be built as a module. If so, the module will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226) be called rtc-brcmstb-waketimer.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228) config RTC_DRV_AS3722
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) tristate "ams AS3722 RTC driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230) depends on MFD_AS3722
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232) If you say yes here you get support for the RTC of ams AS3722 PMIC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233) chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) will be called rtc-as3722.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) config RTC_DRV_DS1307
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239) tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) select REGMAP_I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241) select WATCHDOG_CORE if WATCHDOG
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243) If you say yes here you get support for various compatible RTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244) chips (often with battery backup) connected with I2C. This driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245) should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246) ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247) In some cases the RTC must already have been initialized (by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248) manufacturing or a bootloader).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250) The first seven registers on these chips hold an RTC, and other
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 251) registers may add features such as NVRAM, a trickle charger for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 252) the RTC/NVRAM backup power, and alarms. NVRAM is visible in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 253) sysfs, but other chip features may not be available.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 254)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 255) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 256) will be called rtc-ds1307.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 257)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 258) config RTC_DRV_DS1307_CENTURY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 259) bool "Century bit support for rtc-ds1307"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 260) depends on RTC_DRV_DS1307
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 261) default n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 262) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 263) The DS1307 driver suffered from a bug where it was enabling the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 264) century bit inconditionnally but never used it when reading the time.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 265) It made the driver unable to support dates beyond 2099.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 266) Setting this option will add proper support for the century bit but if
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 267) the time was previously set using a kernel predating this option,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 268) reading the date will return a date in the next century.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 269) To solve that, you could boot a kernel without this option set, set
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 270) the RTC date and then boot a kernel with this option set.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 271)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 272) config RTC_DRV_DS1374
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 273) tristate "Dallas/Maxim DS1374"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 274) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 275) If you say yes here you get support for Dallas Semiconductor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 276) DS1374 real-time clock chips. If an interrupt is associated
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 277) with the device, the alarm functionality is supported.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 278)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 279) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 280) will be called rtc-ds1374.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 281)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 282) config RTC_DRV_DS1374_WDT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 283) bool "Dallas/Maxim DS1374 watchdog timer"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 284) depends on RTC_DRV_DS1374 && WATCHDOG
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 285) select WATCHDOG_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 286) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 287) If you say Y here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 288) watchdog timer in the Dallas Semiconductor DS1374
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 289) real-time clock chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 290)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 291) config RTC_DRV_DS1672
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 292) tristate "Dallas/Maxim DS1672"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 293) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 294) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 295) Dallas/Maxim DS1672 timekeeping chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 296)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 297) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 298) will be called rtc-ds1672.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 299)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 300) config RTC_DRV_HYM8563
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 301) tristate "Haoyu Microelectronics HYM8563"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 302) depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 303) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 304) Say Y to enable support for the HYM8563 I2C RTC chip. Apart
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 305) from the usual rtc functions it provides a clock output of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 306) up to 32kHz.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 307)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 308) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 309) will be called rtc-hym8563.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 310)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 311) config RTC_DRV_LP8788
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 312) tristate "TI LP8788 RTC driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 313) depends on MFD_LP8788
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 314) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 315) Say Y to enable support for the LP8788 RTC/ALARM driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 316)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 317) config RTC_DRV_MAX6900
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 318) tristate "Maxim MAX6900"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 319) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 320) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 321) Maxim MAX6900 I2C RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 322)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 323) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 324) will be called rtc-max6900.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 325)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 326) config RTC_DRV_MAX8907
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 327) tristate "Maxim MAX8907"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 328) depends on MFD_MAX8907 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 329) select REGMAP_IRQ
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 330) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 331) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 332) RTC of Maxim MAX8907 PMIC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 333)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 334) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 335) will be called rtc-max8907.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 336)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 337) config RTC_DRV_MAX8925
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 338) tristate "Maxim MAX8925"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 339) depends on MFD_MAX8925
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 340) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 341) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 342) RTC of Maxim MAX8925 PMIC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 343)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 344) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 345) will be called rtc-max8925.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 346)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 347) config RTC_DRV_MAX8998
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 348) tristate "Maxim MAX8998"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 349) depends on MFD_MAX8998
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 350) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 351) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 352) RTC of Maxim MAX8998 PMIC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 353)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 354) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 355) will be called rtc-max8998.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 356)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 357) config RTC_DRV_MAX8997
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 358) tristate "Maxim MAX8997"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 359) depends on MFD_MAX8997
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 360) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 361) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 362) RTC of Maxim MAX8997 PMIC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 363)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 364) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 365) will be called rtc-max8997.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 366)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 367) config RTC_DRV_MAX77686
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 368) tristate "Maxim MAX77686"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 369) depends on MFD_MAX77686 || MFD_MAX77620 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 370) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 371) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 372) RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 373)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 374) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 375) will be called rtc-max77686.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 376)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 377) config RTC_DRV_RK808
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 378) tristate "Rockchip RK805/RK808/RK809/RK816/RK817/RK818 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 379) depends on MFD_RK808
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 380) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 381) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 382) RTC of RK805, RK809 and RK817, RK808, RK816 and RK818 PMIC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 383)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 384) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 385) will be called rk808-rtc.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 386)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 387) config RTC_DRV_ROCKCHIP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 388) tristate "Rockchip RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 389) depends on ARCH_ROCKCHIP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 390) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 391) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 392) RTC of Rockchip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 393)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 394) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 395) will be called rtc-rockchip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 396)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 397) config RTC_DRV_RS5C372
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 398) tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 399) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 400) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 401) Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 402)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 403) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 404) will be called rtc-rs5c372.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 405)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 406) config RTC_DRV_ISL1208
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 407) tristate "Intersil ISL1208"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 408) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 409) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 410) Intersil ISL1208 RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 411)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 412) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 413) will be called rtc-isl1208.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 414)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 415) config RTC_DRV_ISL12022
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 416) tristate "Intersil ISL12022"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 417) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 418) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 419) Intersil ISL12022 RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 420)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 421) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 422) will be called rtc-isl12022.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 423)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 424) config RTC_DRV_ISL12026
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 425) tristate "Intersil ISL12026"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 426) depends on OF || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 427) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 428) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 429) Intersil ISL12026 RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 430)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 431) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 432) will be called rtc-isl12026.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 433)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 434) config RTC_DRV_X1205
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 435) tristate "Xicor/Intersil X1205"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 436) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 437) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 438) Xicor/Intersil X1205 RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 439)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 440) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 441) will be called rtc-x1205.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 442)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 443) config RTC_DRV_PCF8523
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 444) tristate "NXP PCF8523"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 445) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 446) If you say yes here you get support for the NXP PCF8523 RTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 447) chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 448)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 449) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 450) will be called rtc-pcf8523.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 451)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 452) config RTC_DRV_PCF85063
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 453) tristate "NXP PCF85063"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 454) select REGMAP_I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 455) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 456) If you say yes here you get support for the PCF85063 RTC chip
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 457)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 458) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 459) will be called rtc-pcf85063.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 460)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 461) config RTC_DRV_PCF85363
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 462) tristate "NXP PCF85363"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 463) select REGMAP_I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 464) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 465) If you say yes here you get support for the PCF85363 RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 466)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 467) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 468) will be called rtc-pcf85363.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 469)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 470) The nvmem interface will be named pcf85363-#, where # is the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 471) zero-based instance number.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 472)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 473) config RTC_DRV_PCF8563
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 474) tristate "Philips PCF8563/Epson RTC8564"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 475) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 476) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 477) Philips PCF8563 RTC chip. The Epson RTC8564
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 478) should work as well.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 479)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 480) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 481) will be called rtc-pcf8563.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 482)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 483) config RTC_DRV_PCF8583
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 484) tristate "Philips PCF8583"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 485) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 486) If you say yes here you get support for the Philips PCF8583
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 487) RTC chip found on Acorn RiscPCs. This driver supports the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 488) platform specific method of retrieving the current year from
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 489) the RTC's SRAM. It will work on other platforms with the same
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 490) chip, but the year will probably have to be tweaked.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 491)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 492) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 493) will be called rtc-pcf8583.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 494)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 495) config RTC_DRV_M41T80
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 496) tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 497) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 498) If you say Y here you will get support for the ST M41T60
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 499) and M41T80 RTC chips series. Currently, the following chips are
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 500) supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 501) M41ST85, M41ST87, and MicroCrystal RV4162.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 502)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 503) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 504) will be called rtc-m41t80.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 505)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 506) config RTC_DRV_M41T80_WDT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 507) bool "ST M41T65/M41T80 series RTC watchdog timer"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 508) depends on RTC_DRV_M41T80
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 509) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 510) If you say Y here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 511) watchdog timer in the ST M41T60 and M41T80 RTC chips series.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 512)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 513) config RTC_DRV_BD70528
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 514) tristate "ROHM BD70528 PMIC RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 515) depends on MFD_ROHM_BD70528 && (BD70528_WATCHDOG || !BD70528_WATCHDOG)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 516) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 517) If you say Y here you will get support for the RTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 518) block on ROHM BD70528 and BD71828 Power Management IC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 519)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 520) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 521) will be called rtc-bd70528.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 522)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 523) config RTC_DRV_BQ32K
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 524) tristate "TI BQ32000"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 525) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 526) If you say Y here you will get support for the TI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 527) BQ32000 I2C RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 528)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 529) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 530) will be called rtc-bq32k.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 531)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 532) config RTC_DRV_DM355EVM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 533) tristate "TI DaVinci DM355 EVM RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 534) depends on MFD_DM355EVM_MSP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 535) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 536) Supports the RTC firmware in the MSP430 on the DM355 EVM.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 537)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 538) config RTC_DRV_TWL92330
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 539) bool "TI TWL92330/Menelaus"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 540) depends on MENELAUS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 541) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 542) If you say yes here you get support for the RTC on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 543) TWL92330 "Menelaus" power management chip, used with OMAP2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 544) platforms. The support is integrated with the rest of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 545) the Menelaus driver; it's not separate module.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 546)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 547) config RTC_DRV_TWL4030
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 548) tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 549) depends on TWL4030_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 550) depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 551) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 552) If you say yes here you get support for the RTC on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 553) TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 554)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 555) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 556) will be called rtc-twl.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 557)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 558) config RTC_DRV_PALMAS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 559) tristate "TI Palmas RTC driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 560) depends on MFD_PALMAS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 561) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 562) If you say yes here you get support for the RTC of TI PALMA series PMIC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 563) chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 564)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 565) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 566) will be called rtc-palma.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 567)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 568) config RTC_DRV_TPS6586X
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 569) tristate "TI TPS6586X RTC driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 570) depends on MFD_TPS6586X
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 571) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 572) TI Power Management IC TPS6586X supports RTC functionality
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 573) along with alarm. This driver supports the RTC driver for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 574) the TPS6586X RTC module.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 575)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 576) config RTC_DRV_TPS65910
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 577) tristate "TI TPS65910 RTC driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 578) depends on MFD_TPS65910
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 579) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 580) If you say yes here you get support for the RTC on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 581) TPS65910 chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 582)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 583) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 584) will be called rtc-tps65910.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 585)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 586) config RTC_DRV_TPS80031
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 587) tristate "TI TPS80031/TPS80032 RTC driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 588) depends on MFD_TPS80031
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 589) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 590) TI Power Management IC TPS80031 supports RTC functionality
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 591) along with alarm. This driver supports the RTC driver for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 592) the TPS80031 RTC module.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 593)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 594) config RTC_DRV_RC5T583
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 595) tristate "RICOH 5T583 RTC driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 596) depends on MFD_RC5T583
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 597) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 598) If you say yes here you get support for the RTC on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 599) RICOH 5T583 chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 600)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 601) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 602) will be called rtc-rc5t583.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 603)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 604) config RTC_DRV_RC5T619
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 605) tristate "RICOH RC5T619 RTC driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 606) depends on MFD_RN5T618
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 607) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 608) If you say yes here you get support for the RTC on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 609) RICOH RC5T619 chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 610)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 611) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 612) will be called rtc-rc5t619.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 613)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 614) config RTC_DRV_S35390A
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 615) tristate "Seiko Instruments S-35390A"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 616) select BITREVERSE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 617) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 618) If you say yes here you will get support for the Seiko
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 619) Instruments S-35390A.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 620)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 621) This driver can also be built as a module. If so the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 622) will be called rtc-s35390a.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 623)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 624) config RTC_DRV_FM3130
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 625) tristate "Ramtron FM3130"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 626) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 627) If you say Y here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 628) Ramtron FM3130 RTC chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 629) Ramtron FM3130 is a chip with two separate devices inside,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 630) RTC clock and FRAM. This driver provides only RTC functionality.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 631)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 632) This driver can also be built as a module. If so the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 633) will be called rtc-fm3130.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 634)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 635) config RTC_DRV_RX8010
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 636) tristate "Epson RX8010SJ"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 637) select REGMAP_I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 638) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 639) If you say yes here you get support for the Epson RX8010SJ RTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 640) chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 641)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 642) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 643) will be called rtc-rx8010.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 644)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 645) config RTC_DRV_RX8581
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 646) tristate "Epson RX-8571/RX-8581"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 647) select REGMAP_I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 648) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 649) If you say yes here you will get support for the Epson RX-8571/
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 650) RX-8581.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 651)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 652) This driver can also be built as a module. If so the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 653) will be called rtc-rx8581.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 654)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 655) config RTC_DRV_RX8025
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 656) tristate "Epson RX-8025SA/NB"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 657) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 658) If you say yes here you get support for the Epson
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 659) RX-8025SA/NB RTC chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 660)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 661) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 662) will be called rtc-rx8025.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 663)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 664) config RTC_DRV_EM3027
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 665) tristate "EM Microelectronic EM3027"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 666) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 667) If you say yes here you get support for the EM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 668) Microelectronic EM3027 RTC chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 669)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 670) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 671) will be called rtc-em3027.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 672)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 673) config RTC_DRV_RV3028
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 674) tristate "Micro Crystal RV3028"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 675) select REGMAP_I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 676) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 677) If you say yes here you get support for the Micro Crystal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 678) RV3028.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 679)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 680) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 681) will be called rtc-rv3028.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 682)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 683) config RTC_DRV_RV3032
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 684) tristate "Micro Crystal RV3032"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 685) select REGMAP_I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 686) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 687) If you say yes here you get support for the Micro Crystal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 688) RV3032.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 689)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 690) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 691) will be called rtc-rv3032.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 692)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 693) config RTC_DRV_RV8803
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 694) tristate "Micro Crystal RV8803, Epson RX8900"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 695) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 696) If you say yes here you get support for the Micro Crystal RV8803 and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 697) Epson RX8900 RTC chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 698)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 699) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 700) will be called rtc-rv8803.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 701)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 702) config RTC_DRV_S5M
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 703) tristate "Samsung S2M/S5M series"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 704) depends on MFD_SEC_CORE || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 705) select REGMAP_IRQ
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 706) select REGMAP_I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 707) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 708) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 709) RTC of Samsung S2MPS14 and S5M PMIC series.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 710)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 711) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 712) will be called rtc-s5m.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 713)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 714) config RTC_DRV_SD3078
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 715) tristate "ZXW Shenzhen whwave SD3078"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 716) select REGMAP_I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 717) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 718) If you say yes here you get support for the ZXW Shenzhen whwave
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 719) SD3078 RTC chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 720)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 721) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 722) will be called rtc-sd3078
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 723)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 724) endif # I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 725)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 726) comment "SPI RTC drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 727)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 728) if SPI_MASTER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 729)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 730) config RTC_DRV_M41T93
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 731) tristate "ST M41T93"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 732) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 733) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 734) ST M41T93 SPI RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 735)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 736) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 737) will be called rtc-m41t93.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 738)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 739) config RTC_DRV_M41T94
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 740) tristate "ST M41T94"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 741) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 742) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 743) ST M41T94 SPI RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 744)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 745) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 746) will be called rtc-m41t94.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 747)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 748) config RTC_DRV_DS1302
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 749) tristate "Dallas/Maxim DS1302"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 750) depends on SPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 751) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 752) If you say yes here you get support for the Dallas DS1302 RTC chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 753)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 754) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 755) will be called rtc-ds1302.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 756)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 757) config RTC_DRV_DS1305
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 758) tristate "Dallas/Maxim DS1305/DS1306"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 759) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 760) Select this driver to get support for the Dallas/Maxim DS1305
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 761) and DS1306 real time clock chips. These support a trickle
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 762) charger, alarms, and NVRAM in addition to the clock.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 763)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 764) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 765) will be called rtc-ds1305.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 766)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 767) config RTC_DRV_DS1343
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 768) select REGMAP_SPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 769) tristate "Dallas/Maxim DS1343/DS1344"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 770) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 771) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 772) Dallas/Maxim DS1343 and DS1344 real time clock chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 773) Support for trickle charger, alarm is provided.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 774)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 775) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 776) will be called rtc-ds1343.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 777)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 778) config RTC_DRV_DS1347
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 779) select REGMAP_SPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 780) tristate "Dallas/Maxim DS1347"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 781) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 782) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 783) Dallas/Maxim DS1347 chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 784)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 785) This driver only supports the RTC feature, and not other chip
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 786) features such as alarms.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 787)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 788) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 789) will be called rtc-ds1347.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 790)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 791) config RTC_DRV_DS1390
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 792) tristate "Dallas/Maxim DS1390/93/94"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 793) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 794) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 795) Dallas/Maxim DS1390/93/94 chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 796)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 797) This driver supports the RTC feature and trickle charging but not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 798) other chip features such as alarms.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 799)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 800) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 801) will be called rtc-ds1390.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 802)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 803) config RTC_DRV_MAX6916
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 804) tristate "Maxim MAX6916"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 805) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 806) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 807) Maxim MAX6916 SPI RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 808)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 809) This driver only supports the RTC feature, and not other chip
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 810) features such as alarms.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 811)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 812) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 813) will be called rtc-max6916.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 814)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 815) config RTC_DRV_R9701
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 816) tristate "Epson RTC-9701JE"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 817) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 818) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 819) Epson RTC-9701JE SPI RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 820)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 821) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 822) will be called rtc-r9701.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 823)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 824) config RTC_DRV_RX4581
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 825) tristate "Epson RX-4581"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 826) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 827) If you say yes here you will get support for the Epson RX-4581.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 828)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 829) This driver can also be built as a module. If so the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 830) will be called rtc-rx4581.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 831)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 832) config RTC_DRV_RX6110
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 833) tristate "Epson RX-6110"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 834) select REGMAP_SPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 835) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 836) If you say yes here you will get support for the Epson RX-6610.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 837)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 838) This driver can also be built as a module. If so the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 839) will be called rtc-rx6110.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 840)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 841) config RTC_DRV_RS5C348
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 842) tristate "Ricoh RS5C348A/B"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 843) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 844) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 845) Ricoh RS5C348A and RS5C348B RTC chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 846)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 847) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 848) will be called rtc-rs5c348.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 849)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 850) config RTC_DRV_MAX6902
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 851) tristate "Maxim MAX6902"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 852) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 853) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 854) Maxim MAX6902 SPI RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 855)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 856) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 857) will be called rtc-max6902.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 858)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 859) config RTC_DRV_PCF2123
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 860) tristate "NXP PCF2123"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 861) select REGMAP_SPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 862) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 863) If you say yes here you get support for the NXP PCF2123
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 864) RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 865)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 866) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 867) will be called rtc-pcf2123.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 868)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 869) config RTC_DRV_MCP795
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 870) tristate "Microchip MCP795"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 871) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 872) If you say yes here you will get support for the Microchip MCP795.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 873)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 874) This driver can also be built as a module. If so the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 875) will be called rtc-mcp795.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 876)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 877) endif # SPI_MASTER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 878)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 879) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 880) # Helper to resolve issues with configs that have SPI enabled but I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 881) # modular. See SND_SOC_I2C_AND_SPI for more information
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 882) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 883) config RTC_I2C_AND_SPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 884) tristate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 885) default m if I2C=m
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 886) default y if I2C=y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 887) default y if SPI_MASTER=y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 888)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 889) comment "SPI and I2C RTC drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 890)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 891) config RTC_DRV_DS3232
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 892) tristate "Dallas/Maxim DS3232/DS3234"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 893) depends on RTC_I2C_AND_SPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 894) select REGMAP_I2C if I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 895) select REGMAP_SPI if SPI_MASTER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 896) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 897) If you say yes here you get support for Dallas Semiconductor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 898) DS3232 and DS3234 real-time clock chips. If an interrupt is associated
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 899) with the device, the alarm functionality is supported.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 900)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 901) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 902) will be called rtc-ds3232.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 903)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 904) config RTC_DRV_DS3232_HWMON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 905) bool "HWMON support for Dallas/Maxim DS3232/DS3234"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 906) depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 907) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 908) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 909) Say Y here if you want to expose temperature sensor data on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 910) rtc-ds3232
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 911)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 912) config RTC_DRV_PCF2127
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 913) tristate "NXP PCF2127"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 914) depends on RTC_I2C_AND_SPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 915) select REGMAP_I2C if I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 916) select REGMAP_SPI if SPI_MASTER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 917) select WATCHDOG_CORE if WATCHDOG
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 918) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 919) If you say yes here you get support for the NXP PCF2127/29 RTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 920) chips with integrated quartz crystal for industrial applications.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 921) Both chips also have watchdog timer and tamper switch detection
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 922) features.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 923)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 924) PCF2127 has an additional feature of 512 bytes battery backed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 925) memory that's accessible using nvmem interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 926)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 927) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 928) will be called rtc-pcf2127.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 929)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 930) config RTC_DRV_RV3029C2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 931) tristate "Micro Crystal RV3029/3049"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 932) depends on RTC_I2C_AND_SPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 933) select REGMAP_I2C if I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 934) select REGMAP_SPI if SPI_MASTER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 935) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 936) If you say yes here you get support for the Micro Crystal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 937) RV3029 and RV3049 RTC chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 938)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 939) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 940) will be called rtc-rv3029c2.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 941)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 942) config RTC_DRV_RV3029_HWMON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 943) bool "HWMON support for RV3029/3049"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 944) depends on RTC_DRV_RV3029C2 && HWMON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 945) depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 946) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 947) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 948) Say Y here if you want to expose temperature sensor data on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 949) rtc-rv3029.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 950)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 951) comment "Platform RTC drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 952)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 953) # this 'CMOS' RTC driver is arch dependent because it requires
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 954) # <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 955) # global rtc_lock ... it's not yet just another platform_device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 956)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 957) config RTC_DRV_CMOS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 958) tristate "PC-style 'CMOS'"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 959) depends on X86 || ARM || PPC || MIPS || SPARC64
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 960) default y if X86
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 961) select RTC_MC146818_LIB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 962) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 963) Say "yes" here to get direct support for the real time clock
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 964) found in every PC or ACPI-based system, and some other boards.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 965) Specifically the original MC146818, compatibles like those in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 966) PC south bridges, the DS12887 or M48T86, some multifunction
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 967) or LPC bus chips, and so on.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 968)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 969) Your system will need to define the platform device used by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 970) this driver, otherwise it won't be accessible. This means
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 971) you can safely enable this driver if you don't know whether
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 972) or not your board has this kind of hardware.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 973)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 974) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 975) will be called rtc-cmos.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 976)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 977) config RTC_DRV_ALPHA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 978) bool "Alpha PC-style CMOS"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 979) depends on ALPHA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 980) select RTC_MC146818_LIB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 981) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 982) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 983) Direct support for the real-time clock found on every Alpha
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 984) system, specifically MC146818 compatibles. If in doubt, say Y.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 985)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 986) config RTC_DRV_VRTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 987) tristate "Virtual RTC for Intel MID platforms"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 988) depends on X86_INTEL_MID
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 989) default y if X86_INTEL_MID
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 990)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 991) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 992) Say "yes" here to get direct support for the real time clock
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 993) found on Moorestown platforms. The VRTC is a emulated RTC that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 994) derives its clock source from a real RTC in the PMIC. The MC146818
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 995) style programming interface is mostly conserved, but any
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 996) updates are done via IPC calls to the system controller FW.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 997)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 998) config RTC_DRV_DS1216
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 999) tristate "Dallas DS1216"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1000) depends on SNI_RM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1001) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1002) If you say yes here you get support for the Dallas DS1216 RTC chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1003)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1004) config RTC_DRV_DS1286
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1005) tristate "Dallas DS1286"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1006) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1007) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1008) If you say yes here you get support for the Dallas DS1286 RTC chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1009)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1010) config RTC_DRV_DS1511
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1011) tristate "Dallas DS1511"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1012) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1013) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1014) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1015) Dallas DS1511 timekeeping/watchdog chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1016)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1017) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1018) will be called rtc-ds1511.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1019)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1020) config RTC_DRV_DS1553
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1021) tristate "Maxim/Dallas DS1553"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1022) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1023) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1024) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1025) Maxim/Dallas DS1553 timekeeping chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1026)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1027) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1028) will be called rtc-ds1553.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1029)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1030) config RTC_DRV_DS1685_FAMILY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1031) tristate "Dallas/Maxim DS1685 Family"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1032) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1033) If you say yes here you get support for the Dallas/Maxim DS1685
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1034) family of real time chips. This family includes the DS1685/DS1687,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1035) DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1036) DS17885/DS17887 chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1037)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1038) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1039) will be called rtc-ds1685.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1040)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1041) choice
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1042) prompt "Subtype"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1043) depends on RTC_DRV_DS1685_FAMILY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1044) default RTC_DRV_DS1685
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1045)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1046) config RTC_DRV_DS1685
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1047) bool "DS1685/DS1687"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1048) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1049) This enables support for the Dallas/Maxim DS1685/DS1687 real time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1050) clock chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1051)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1052) This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1053) systems, as well as EPPC-405-UC modules by electronic system design
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1054) GmbH.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1055)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1056) config RTC_DRV_DS1689
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1057) bool "DS1689/DS1693"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1058) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1059) This enables support for the Dallas/Maxim DS1689/DS1693 real time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1060) clock chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1061)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1062) This is an older RTC chip, supplanted by the DS1685/DS1687 above,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1063) which supports a few minor features such as Vcc, Vbat, and Power
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1064) Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1065)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1066) It also works for the even older DS1688/DS1691 RTC chips, which are
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1067) virtually the same and carry the same model number. Both chips
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1068) have 114 bytes of user NVRAM.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1069)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1070) config RTC_DRV_DS17285
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1071) bool "DS17285/DS17287"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1072) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1073) This enables support for the Dallas/Maxim DS17285/DS17287 real time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1074) clock chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1075)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1076) This chip features 2kb of extended NV-SRAM. It may possibly be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1077) found in some SGI O2 systems (rare).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1078)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1079) config RTC_DRV_DS17485
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1080) bool "DS17485/DS17487"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1081) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1082) This enables support for the Dallas/Maxim DS17485/DS17487 real time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1083) clock chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1084)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1085) This chip features 4kb of extended NV-SRAM.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1086)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1087) config RTC_DRV_DS17885
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1088) bool "DS17885/DS17887"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1089) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1090) This enables support for the Dallas/Maxim DS17885/DS17887 real time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1091) clock chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1092)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1093) This chip features 8kb of extended NV-SRAM.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1094)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1095) endchoice
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1096)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1097) config RTC_DRV_DS1742
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1098) tristate "Maxim/Dallas DS1742/1743"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1099) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1100) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1101) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1102) Maxim/Dallas DS1742/1743 timekeeping chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1103)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1104) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1105) will be called rtc-ds1742.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1106)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1107) config RTC_DRV_DS2404
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1108) tristate "Maxim/Dallas DS2404"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1109) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1110) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1111) Dallas DS2404 RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1112)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1113) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1114) will be called rtc-ds2404.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1115)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1116) config RTC_DRV_DA9052
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1117) tristate "Dialog DA9052/DA9053 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1118) depends on PMIC_DA9052
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1119) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1120) Say y here to support the RTC driver for Dialog Semiconductor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1121) DA9052-BC and DA9053-AA/Bx PMICs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1122)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1123) config RTC_DRV_DA9055
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1124) tristate "Dialog Semiconductor DA9055 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1125) depends on MFD_DA9055
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1126) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1127) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1128) RTC of the Dialog DA9055 PMIC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1129)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1130) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1131) will be called rtc-da9055
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1132)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1133) config RTC_DRV_DA9063
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1134) tristate "Dialog Semiconductor DA9063/DA9062 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1135) depends on MFD_DA9063 || MFD_DA9062
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1136) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1137) If you say yes here you will get support for the RTC subsystem
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1138) for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1139)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1140) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1141) will be called "rtc-da9063".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1142)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1143) config RTC_DRV_EFI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1144) tristate "EFI RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1145) depends on EFI && !X86
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1146) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1147) If you say yes here you will get support for the EFI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1148) Real Time Clock.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1149)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1150) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1151) will be called rtc-efi.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1152)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1153) config RTC_DRV_STK17TA8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1154) tristate "Simtek STK17TA8"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1155) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1156) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1157) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1158) Simtek STK17TA8 timekeeping chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1159)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1160) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1161) will be called rtc-stk17ta8.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1162)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1163) config RTC_DRV_M48T86
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1164) tristate "ST M48T86/Dallas DS12887"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1165) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1166) If you say Y here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1167) ST M48T86 and Dallas DS12887 RTC chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1168)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1169) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1170) will be called rtc-m48t86.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1171)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1172) config RTC_DRV_M48T35
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1173) tristate "ST M48T35"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1174) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1175) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1176) If you say Y here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1177) ST M48T35 RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1178)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1179) This driver can also be built as a module, if so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1180) will be called "rtc-m48t35".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1181)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1182) config RTC_DRV_M48T59
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1183) tristate "ST M48T59/M48T08/M48T02"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1184) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1185) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1186) If you say Y here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1187) ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1188)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1189) These chips are usually found in Sun SPARC and UltraSPARC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1190) workstations.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1191)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1192) This driver can also be built as a module, if so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1193) will be called "rtc-m48t59".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1194)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1195) config RTC_DRV_MSM6242
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1196) tristate "Oki MSM6242"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1197) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1198) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1199) If you say yes here you get support for the Oki MSM6242
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1200) timekeeping chip. It is used in some Amiga models (e.g. A2000).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1201)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1202) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1203) will be called rtc-msm6242.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1204)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1205) config RTC_DRV_BQ4802
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1206) tristate "TI BQ4802"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1207) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1208) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1209) If you say Y here you will get support for the TI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1210) BQ4802 RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1211)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1212) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1213) will be called rtc-bq4802.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1214)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1215) config RTC_DRV_RP5C01
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1216) tristate "Ricoh RP5C01"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1217) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1218) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1219) If you say yes here you get support for the Ricoh RP5C01
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1220) timekeeping chip. It is used in some Amiga models (e.g. A3000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1221) and A4000).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1222)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1223) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1224) will be called rtc-rp5c01.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1225)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1226) config RTC_DRV_V3020
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1227) tristate "EM Microelectronic V3020"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1228) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1229) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1230) EM Microelectronic v3020 RTC chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1231)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1232) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1233) will be called rtc-v3020.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1234)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1235) config RTC_DRV_WM831X
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1236) tristate "Wolfson Microelectronics WM831x RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1237) depends on MFD_WM831X
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1238) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1239) If you say yes here you will get support for the RTC subsystem
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1240) of the Wolfson Microelectronics WM831X series PMICs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1241)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1242) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1243) will be called "rtc-wm831x".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1244)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1245) config RTC_DRV_WM8350
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1246) tristate "Wolfson Microelectronics WM8350 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1247) depends on MFD_WM8350
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1248) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1249) If you say yes here you will get support for the RTC subsystem
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1250) of the Wolfson Microelectronics WM8350.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1251)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1252) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1253) will be called "rtc-wm8350".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1254)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1255) config RTC_DRV_SC27XX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1256) tristate "Spreadtrum SC27xx RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1257) depends on MFD_SC27XX_PMIC || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1258) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1259) If you say Y here you will get support for the RTC subsystem
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1260) of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1261) includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1262)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1263) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1264) will be called rtc-sc27xx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1265)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1266) config RTC_DRV_SPEAR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1267) tristate "SPEAR ST RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1268) depends on PLAT_SPEAR || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1269) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1270) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1271) If you say Y here you will get support for the RTC found on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1272) spear
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1273)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1274) config RTC_DRV_PCF50633
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1275) depends on MFD_PCF50633
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1276) tristate "NXP PCF50633 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1277) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1278) If you say yes here you get support for the RTC subsystem of the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1279) NXP PCF50633 used in embedded systems.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1280)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1281) config RTC_DRV_AB3100
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1282) tristate "ST-Ericsson AB3100 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1283) depends on AB3100_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1284) default y if AB3100_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1285) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1286) Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1287) support. This chip contains a battery- and capacitor-backed RTC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1288)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1289) config RTC_DRV_AB8500
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1290) tristate "ST-Ericsson AB8500 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1291) depends on AB8500_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1292) select RTC_INTF_DEV
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1293) select RTC_INTF_DEV_UIE_EMUL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1294) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1295) Select this to enable the ST-Ericsson AB8500 power management IC RTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1296) support. This chip contains a battery- and capacitor-backed RTC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1297)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1298) config RTC_DRV_OPAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1299) tristate "IBM OPAL RTC driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1300) depends on PPC_POWERNV
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1301) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1302) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1303) If you say yes here you get support for the PowerNV platform RTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1304) driver based on OPAL interfaces.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1305)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1306) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1307) will be called rtc-opal.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1308)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1309) config RTC_DRV_ZYNQMP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1310) tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1311) depends on OF && HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1312) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1313) If you say yes here you get support for the RTC controller found on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1314) Xilinx Zynq Ultrascale+ MPSoC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1315)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1316) config RTC_DRV_CROS_EC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1317) tristate "Chrome OS EC RTC driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1318) depends on CROS_EC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1319) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1320) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1321) Chrome OS Embedded Controller's RTC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1322)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1323) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1324) will be called rtc-cros-ec.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1325)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1326) comment "on-CPU RTC drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1327)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1328) config RTC_DRV_ASM9260
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1329) tristate "Alphascale asm9260 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1330) depends on MACH_ASM9260 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1331) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1332) If you say yes here you get support for the RTC on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1333) Alphascale asm9260 SoC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1334)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1335) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1336) will be called rtc-asm9260.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1337)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1338) config RTC_DRV_DAVINCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1339) tristate "TI DaVinci RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1340) depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1341) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1342) If you say yes here you get support for the RTC on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1343) DaVinci platforms (DM365).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1344)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1345) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1346) will be called rtc-davinci.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1347)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1348) config RTC_DRV_DIGICOLOR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1349) tristate "Conexant Digicolor RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1350) depends on ARCH_DIGICOLOR || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1351) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1352) If you say yes here you get support for the RTC on Conexant
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1353) Digicolor platforms. This currently includes the CX92755 SoC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1354)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1355) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1356) will be called rtc-digicolor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1357)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1358) config RTC_DRV_IMXDI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1359) tristate "Freescale IMX DryIce Real Time Clock"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1360) depends on ARCH_MXC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1361) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1362) Support for Freescale IMX DryIce RTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1363)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1364) This driver can also be built as a module, if so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1365) will be called "rtc-imxdi".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1366)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1367) config RTC_DRV_FSL_FTM_ALARM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1368) tristate "Freescale FlexTimer alarm timer"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1369) depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1370) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1371) For the FlexTimer in LS1012A, LS1021A, LS1028A, LS1043A, LS1046A,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1372) LS1088A, LS208xA, we can use FTM as the wakeup source.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1373)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1374) Say y here to enable FTM alarm support. The FTM alarm provides
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1375) alarm functions for wakeup system from deep sleep.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1376)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1377) This driver can also be built as a module, if so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1378) will be called "rtc-fsl-ftm-alarm".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1379)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1380) config RTC_DRV_MESON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1381) tristate "Amlogic Meson RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1382) depends on (ARM && ARCH_MESON) || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1383) select REGMAP_MMIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1384) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1385) Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1386) and Meson8m2 SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1387)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1388) This driver can also be built as a module, if so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1389) will be called "rtc-meson".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1390)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1391) config RTC_DRV_MESON_VRTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1392) tristate "Amlogic Meson Virtual RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1393) depends on ARCH_MESON || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1394) default m if ARCH_MESON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1395) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1396) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1397) Virtual RTC of Amlogic SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1398)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1399) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1400) will be called rtc-meson-vrtc.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1401)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1402) config RTC_DRV_OMAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1403) tristate "TI OMAP Real Time Clock"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1404) depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1405) depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1406) depends on PINCTRL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1407) select GENERIC_PINCONF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1408) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1409) Say "yes" here to support the on chip real time clock
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1410) present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1411)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1412) This driver can also be built as a module, if so, module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1413) will be called rtc-omap.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1414)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1415) config HAVE_S3C_RTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1416) bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1417) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1418) This will include RTC support for Samsung SoCs. If
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1419) you want to include RTC support for any machine, kindly
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1420) select this in the respective mach-XXXX/Kconfig file.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1421)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1422) config RTC_DRV_S3C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1423) tristate "Samsung S3C series SoC RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1424) depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1425) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1426) RTC (Realtime Clock) driver for the clock inbuilt into the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1427) Samsung S3C24XX series of SoCs. This can provide periodic
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1428) interrupt rates from 1Hz to 64Hz for user programs, and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1429) wakeup from Alarm.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1430)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1431) The driver currently supports the common features on all the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1432) S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1433) and S3C2442.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1434)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1435) This driver can also be build as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1436) will be called rtc-s3c.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1437)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1438) config RTC_DRV_EP93XX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1439) tristate "Cirrus Logic EP93XX"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1440) depends on ARCH_EP93XX || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1441) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1442) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1443) RTC embedded in the Cirrus Logic EP93XX processors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1444)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1445) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1446) will be called rtc-ep93xx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1447)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1448) config RTC_DRV_SA1100
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1449) tristate "SA11x0/PXA2xx/PXA910"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1450) depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1451) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1452) If you say Y here you will get access to the real time clock
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1453) built into your SA11x0 or PXA2xx CPU.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1454)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1455) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1456) module will be called rtc-sa1100.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1457)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1458) config RTC_DRV_SH
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1459) tristate "SuperH On-Chip RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1460) depends on SUPERH || ARCH_RENESAS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1461) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1462) Say Y here to enable support for the on-chip RTC found in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1463) most SuperH processors. This RTC is also found in RZ/A SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1464)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1465) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1466) module will be called rtc-sh.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1467)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1468) config RTC_DRV_VR41XX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1469) tristate "NEC VR41XX"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1470) depends on CPU_VR41XX || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1471) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1472) If you say Y here you will get access to the real time clock
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1473) built into your NEC VR41XX CPU.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1474)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1475) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1476) module will be called rtc-vr41xx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1477)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1478) config RTC_DRV_PL030
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1479) tristate "ARM AMBA PL030 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1480) depends on ARM_AMBA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1481) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1482) If you say Y here you will get access to ARM AMBA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1483) PrimeCell PL030 RTC found on certain ARM SOCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1484)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1485) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1486) module will be called rtc-pl030.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1487)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1488) config RTC_DRV_PL031
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1489) tristate "ARM AMBA PL031 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1490) depends on ARM_AMBA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1491) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1492) If you say Y here you will get access to ARM AMBA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1493) PrimeCell PL031 RTC found on certain ARM SOCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1494)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1495) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1496) module will be called rtc-pl031.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1497)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1498) config RTC_DRV_AT91RM9200
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1499) tristate "AT91RM9200 or some AT91SAM9 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1500) depends on ARCH_AT91 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1501) depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1502) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1503) Driver for the internal RTC (Realtime Clock) module found on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1504) Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1505) this is powered by the backup power supply.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1506)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1507) config RTC_DRV_AT91SAM9
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1508) tristate "AT91SAM9 RTT as RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1509) depends on ARCH_AT91 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1510) depends on OF && HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1511) select MFD_SYSCON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1512) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1513) Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1514) can be used as an RTC thanks to the backup power supply (e.g. a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1515) small coin cell battery) which keeps this block and the GPBR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1516) (General Purpose Backup Registers) block powered when the device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1517) is shutdown.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1518) Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1519) probably want to use the real RTC block instead of the "RTT as an
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1520) RTC" driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1521)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1522) config RTC_DRV_AU1XXX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1523) tristate "Au1xxx Counter0 RTC support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1524) depends on MIPS_ALCHEMY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1525) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1526) This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1527) counter) to be used as a RTC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1528)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1529) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1530) will be called rtc-au1xxx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1531)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1532) config RTC_DRV_RS5C313
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1533) tristate "Ricoh RS5C313"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1534) depends on SH_LANDISK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1535) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1536) If you say yes here you get support for the Ricoh RS5C313 RTC chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1537)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1538) config RTC_DRV_GENERIC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1539) tristate "Generic RTC support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1540) # Please consider writing a new RTC driver instead of using the generic
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1541) # RTC abstraction
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1542) depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1543) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1544) Say Y or M here to enable RTC support on systems using the generic
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1545) RTC abstraction. If you do not know what you are doing, you should
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1546) just say Y.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1547)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1548) config RTC_DRV_PXA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1549) tristate "PXA27x/PXA3xx"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1550) depends on ARCH_PXA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1551) select RTC_DRV_SA1100
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1552) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1553) If you say Y here you will get access to the real time clock
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1554) built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1555) consisting of an SA1100 compatible RTC and the extended PXA RTC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1556)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1557) This RTC driver uses PXA RTC registers available since pxa27x
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1558) series (RDxR, RYxR) instead of legacy RCNR, RTAR.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1559)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1560) config RTC_DRV_VT8500
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1561) tristate "VIA/WonderMedia 85xx SoC RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1562) depends on ARCH_VT8500 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1563) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1564) If you say Y here you will get access to the real time clock
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1565) built into your VIA VT8500 SoC or its relatives.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1566)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1567)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1568) config RTC_DRV_SUN4V
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1569) bool "SUN4V Hypervisor RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1570) depends on SPARC64
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1571) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1572) If you say Y here you will get support for the Hypervisor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1573) based RTC on SUN4V systems.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1574)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1575) config RTC_DRV_SUN6I
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1576) bool "Allwinner A31 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1577) default MACH_SUN6I || MACH_SUN8I
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1578) depends on COMMON_CLK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1579) depends on ARCH_SUNXI || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1580) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1581) If you say Y here you will get support for the RTC found in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1582) some Allwinner SoCs like the A31 or the A64.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1583)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1584) config RTC_DRV_SUNXI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1585) tristate "Allwinner sun4i/sun7i RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1586) depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1587) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1588) If you say Y here you will get support for the RTC found on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1589) Allwinner A10/A20.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1590)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1591) config RTC_DRV_STARFIRE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1592) bool "Starfire RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1593) depends on SPARC64
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1594) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1595) If you say Y here you will get support for the RTC found on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1596) Starfire systems.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1597)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1598) config RTC_DRV_TX4939
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1599) tristate "TX4939 SoC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1600) depends on SOC_TX4939 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1601) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1602) Driver for the internal RTC (Realtime Clock) module found on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1603) Toshiba TX4939 SoC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1604)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1605) config RTC_DRV_MV
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1606) tristate "Marvell SoC RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1607) depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1608) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1609) If you say yes here you will get support for the in-chip RTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1610) that can be found in some of Marvell's SoC devices, such as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1611) the Kirkwood 88F6281 and 88F6192.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1612)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1613) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1614) will be called rtc-mv.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1615)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1616) config RTC_DRV_ARMADA38X
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1617) tristate "Armada 38x Marvell SoC RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1618) depends on ARCH_MVEBU || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1619) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1620) If you say yes here you will get support for the in-chip RTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1621) that can be found in the Armada 38x Marvell's SoC device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1622)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1623) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1624) will be called armada38x-rtc.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1625)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1626) config RTC_DRV_CADENCE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1627) tristate "Cadence RTC driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1628) depends on OF && HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1629) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1630) If you say Y here you will get access to Cadence RTC IP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1631) found on certain SOCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1632)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1633) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1634) module will be called rtc-cadence.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1635)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1636) config RTC_DRV_FTRTC010
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1637) tristate "Faraday Technology FTRTC010 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1638) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1639) default ARCH_GEMINI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1640) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1641) If you say Y here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1642) Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1643)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1644) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1645) will be called rtc-ftrtc010.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1646)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1647) config RTC_DRV_PS3
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1648) tristate "PS3 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1649) depends on PPC_PS3
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1650) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1651) If you say yes here you will get support for the RTC on PS3.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1652)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1653) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1654) will be called rtc-ps3.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1655)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1656) config RTC_DRV_COH901331
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1657) tristate "ST-Ericsson COH 901 331 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1658) depends on ARCH_U300 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1659) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1660) If you say Y here you will get access to ST-Ericsson
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1661) COH 901 331 RTC clock found in some ST-Ericsson Mobile
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1662) Platforms.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1663)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1664) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1665) will be called "rtc-coh901331".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1666)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1667)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1668) config RTC_DRV_STMP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1669) tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1670) depends on ARCH_MXS || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1671) select STMP_DEVICE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1672) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1673) If you say yes here you will get support for the onboard
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1674) STMP3xxx/i.MX23/i.MX28 RTC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1675)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1676) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1677) will be called rtc-stmp3xxx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1678)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1679) config RTC_DRV_PCAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1680) tristate "PCAP RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1681) depends on EZX_PCAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1682) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1683) If you say Y here you will get support for the RTC found on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1684) the PCAP2 ASIC used on some Motorola phones.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1685)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1686) config RTC_DRV_MC13XXX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1687) depends on MFD_MC13XXX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1688) tristate "Freescale MC13xxx RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1689) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1690) This enables support for the RTCs found on Freescale's PMICs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1691) MC13783 and MC13892.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1692)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1693) config RTC_DRV_MPC5121
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1694) tristate "Freescale MPC5121 built-in RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1695) depends on PPC_MPC512x || PPC_MPC52xx
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1696) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1697) If you say yes here you will get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1698) built-in RTC on MPC5121 or on MPC5200.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1699)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1700) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1701) will be called rtc-mpc5121.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1702)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1703) config RTC_DRV_JZ4740
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1704) tristate "Ingenic JZ4740 SoC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1705) depends on MIPS || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1706) depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1707) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1708) If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1709) controllers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1710)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1711) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1712) will be called rtc-jz4740.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1713)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1714) config RTC_DRV_LPC24XX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1715) tristate "NXP RTC for LPC178x/18xx/408x/43xx"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1716) depends on ARCH_LPC18XX || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1717) depends on OF && HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1718) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1719) This enables support for the NXP RTC found which can be found on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1720) NXP LPC178x/18xx/408x/43xx devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1721)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1722) If you have one of the devices above enable this driver to use
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1723) the hardware RTC. This driver can also be built as a module. If
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1724) so, the module will be called rtc-lpc24xx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1725)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1726) config RTC_DRV_LPC32XX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1727) depends on ARCH_LPC32XX || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1728) tristate "NXP LPC32XX RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1729) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1730) This enables support for the NXP RTC in the LPC32XX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1731)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1732) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1733) will be called rtc-lpc32xx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1734)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1735) config RTC_DRV_PM8XXX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1736) tristate "Qualcomm PMIC8XXX RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1737) depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1738) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1739) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1740) Qualcomm PMIC8XXX RTC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1741)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1742) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1743) module will be called rtc-pm8xxx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1744)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1745) config RTC_DRV_TEGRA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1746) tristate "NVIDIA Tegra Internal RTC driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1747) depends on ARCH_TEGRA || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1748) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1749) If you say yes here you get support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1750) Tegra 200 series internal RTC module.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1751)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1752) This drive can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1753) will be called rtc-tegra.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1754)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1755) config RTC_DRV_LOONGSON1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1756) tristate "loongson1 RTC support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1757) depends on MACH_LOONGSON32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1758) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1759) This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1760) counter) to be used as a RTC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1761)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1762) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1763) will be called rtc-ls1x.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1764)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1765) config RTC_DRV_MXC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1766) tristate "Freescale MXC Real Time Clock"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1767) depends on ARCH_MXC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1768) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1769) If you say yes here you get support for the Freescale MXC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1770) RTC module.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1771)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1772) This driver can also be built as a module, if so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1773) will be called "rtc-mxc".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1774)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1775) config RTC_DRV_MXC_V2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1776) tristate "Freescale MXC Real Time Clock for i.MX53"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1777) depends on ARCH_MXC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1778) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1779) If you say yes here you get support for the Freescale MXC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1780) SRTC module in i.MX53 processor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1781)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1782) This driver can also be built as a module, if so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1783) will be called "rtc-mxc_v2".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1784)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1785) config RTC_DRV_SNVS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1786) tristate "Freescale SNVS RTC support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1787) select REGMAP_MMIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1788) depends on ARCH_MXC || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1789) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1790) depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1791) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1792) If you say yes here you get support for the Freescale SNVS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1793) Low Power (LP) RTC module.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1794)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1795) This driver can also be built as a module, if so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1796) will be called "rtc-snvs".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1797)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1798) config RTC_DRV_IMX_SC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1799) depends on IMX_SCU
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1800) depends on HAVE_ARM_SMCCC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1801) tristate "NXP i.MX System Controller RTC support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1802) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1803) If you say yes here you get support for the NXP i.MX System
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1804) Controller RTC module.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1805)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1806) config RTC_DRV_SIRFSOC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1807) tristate "SiRFSOC RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1808) depends on ARCH_SIRF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1809) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1810) Say "yes" here to support the real time clock on SiRF SOC chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1811) This driver can also be built as a module called rtc-sirfsoc.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1812)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1813) config RTC_DRV_ST_LPC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1814) tristate "STMicroelectronics LPC RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1815) depends on ARCH_STI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1816) depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1817) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1818) Say Y here to include STMicroelectronics Low Power Controller
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1819) (LPC) based RTC support.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1820)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1821) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1822) module will be called rtc-st-lpc.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1823)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1824) config RTC_DRV_MOXART
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1825) tristate "MOXA ART RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1826) depends on ARCH_MOXART || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1827) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1828) If you say yes here you get support for the MOXA ART
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1829) RTC module.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1830)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1831) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1832) will be called rtc-moxart
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1833)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1834) config RTC_DRV_MT2712
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1835) tristate "MediaTek MT2712 SoC based RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1836) depends on ARCH_MEDIATEK || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1837) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1838) This enables support for the real time clock built in the MediaTek
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1839) SoCs for MT2712.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1840)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1841) This drive can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1842) will be called rtc-mt2712.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1843)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1844) config RTC_DRV_MT6397
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1845) tristate "MediaTek PMIC based RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1846) depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1847) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1848) This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1849) MT6397 PMIC. You should enable MT6397 PMIC MFD before select
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1850) MediaTek(R) RTC driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1851)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1852) If you want to use MediaTek(R) RTC interface, select Y or M here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1853)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1854) config RTC_DRV_MT7622
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1855) tristate "MediaTek SoC based RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1856) depends on ARCH_MEDIATEK || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1857) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1858) This enables support for the real time clock built in the MediaTek
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1859) SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1860)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1861) This drive can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1862) will be called rtc-mt7622.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1863)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1864) config RTC_DRV_XGENE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1865) tristate "APM X-Gene RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1866) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1867) depends on ARCH_XGENE || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1868) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1869) If you say yes here you get support for the APM X-Gene SoC real time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1870) clock.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1871)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1872) This driver can also be built as a module, if so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1873) will be called "rtc-xgene".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1874)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1875) config RTC_DRV_PIC32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1876) tristate "Microchip PIC32 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1877) depends on MACH_PIC32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1878) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1879) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1880) If you say yes here you get support for the PIC32 RTC module.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1881)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1882) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1883) will be called rtc-pic32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1884)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1885) config RTC_DRV_R7301
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1886) tristate "EPSON TOYOCOM RTC-7301SF/DG"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1887) select REGMAP_MMIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1888) depends on OF && HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1889) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1890) If you say yes here you get support for the EPSON TOYOCOM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1891) RTC-7301SF/DG chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1892)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1893) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1894) will be called rtc-r7301.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1895)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1896) config RTC_DRV_STM32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1897) tristate "STM32 RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1898) select REGMAP_MMIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1899) depends on ARCH_STM32 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1900) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1901) If you say yes here you get support for the STM32 On-Chip
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1902) Real Time Clock.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1903)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1904) This driver can also be built as a module, if so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1905) will be called "rtc-stm32".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1906)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1907) config RTC_DRV_CPCAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1908) depends on MFD_CPCAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1909) tristate "Motorola CPCAP RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1910) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1911) Say y here for CPCAP rtc found on some Motorola phones
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1912) and tablets such as Droid 4.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1913)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1914) config RTC_DRV_RTD119X
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1915) bool "Realtek RTD129x RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1916) depends on ARCH_REALTEK || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1917) default ARCH_REALTEK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1918) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1919) If you say yes here, you get support for the RTD1295 SoC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1920) Real Time Clock.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1921)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1922) config RTC_DRV_ASPEED
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1923) tristate "ASPEED RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1924) depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1925) depends on ARCH_ASPEED || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1926) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1927) If you say yes here you get support for the ASPEED BMC SoC real time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1928) clocks.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1929)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1930) This driver can also be built as a module, if so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1931) will be called "rtc-aspeed".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1932)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1933) comment "HID Sensor RTC drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1934)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1935) config RTC_DRV_HID_SENSOR_TIME
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1936) tristate "HID Sensor Time"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1937) depends on USB_HID
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1938) depends on HID_SENSOR_HUB && IIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1939) select HID_SENSOR_IIO_COMMON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1940) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1941) Say yes here to build support for the HID Sensors of type Time.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1942) This drivers makes such sensors available as RTCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1943)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1944) If this driver is compiled as a module, it will be named
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1945) rtc-hid-sensor-time.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1946)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1947) config RTC_DRV_GOLDFISH
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1948) tristate "Goldfish Real Time Clock"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1949) depends on OF && HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1950) depends on GOLDFISH || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1951) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1952) Say yes to enable RTC driver for the Goldfish based virtual platform.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1953)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1954) Goldfish is a code name for the virtual platform developed by Google
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1955) for Android emulation.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1956)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1957) config RTC_DRV_WILCO_EC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1958) tristate "Wilco EC RTC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1959) depends on WILCO_EC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1960) default m
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1961) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1962) If you say yes here, you get read/write support for the Real Time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1963) Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1964)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1965) This can also be built as a module. If so, the module will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1966) be named "rtc_wilco_ec".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1967)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1968) endif # RTC_CLASS
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags