David Brownell | 7be2c7c | 2007-02-10 01:46:02 -0800 | [diff] [blame] | 1 | # |
Alessandro Zummo | c58411e | 2006-03-27 01:16:34 -0800 | [diff] [blame] | 2 | # RTC class/drivers configuration |
| 3 | # |
| 4 | |
| 5 | config RTC_LIB |
John Stultz | b4d246b | 2011-04-29 15:03:11 -0700 | [diff] [blame] | 6 | bool |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 7 | |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 8 | menuconfig RTC_CLASS |
John Stultz | b4d246b | 2011-04-29 15:03:11 -0700 | [diff] [blame] | 9 | bool "Real Time Clock" |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 10 | default n |
Al Viro | 3369465 | 2011-08-18 20:11:59 +0100 | [diff] [blame] | 11 | depends on !S390 && !UML |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 12 | select RTC_LIB |
| 13 | help |
| 14 | Generic RTC class support. If you say yes here, you will |
| 15 | be allowed to plug one or more RTCs to your system. You will |
Adrian Bunk | 27ae410 | 2006-06-30 18:18:41 +0200 | [diff] [blame] | 16 | probably want to enable one or more of the interfaces below. |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 17 | |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 18 | if RTC_CLASS |
| 19 | |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 20 | config RTC_HCTOSYS |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 21 | bool "Set system time from RTC on startup and resume" |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 22 | depends on RTC_CLASS = y |
| 23 | default y |
| 24 | help |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 25 | If you say yes here, the system time (wall clock) will be set using |
| 26 | the value read from a specified RTC device. This is useful to avoid |
| 27 | unnecessary fsck runs at boot time, and to network better. |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 28 | |
| 29 | config RTC_HCTOSYS_DEVICE |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 30 | string "RTC used to set the system time" |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 31 | depends on RTC_HCTOSYS = y |
| 32 | default "rtc0" |
| 33 | help |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 34 | The RTC device that will be used to (re)initialize the system |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 35 | clock, usually rtc0. Initialization is done when the system |
| 36 | starts up, and when it resumes from a low power state. This |
David Brownell | 779d208 | 2007-11-14 16:58:29 -0800 | [diff] [blame] | 37 | device should record time in UTC, since the kernel won't do |
| 38 | timezone correction. |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 39 | |
David Brownell | 55ff1ab | 2007-07-21 04:37:56 -0700 | [diff] [blame] | 40 | The driver for this RTC device must be loaded before late_initcall |
| 41 | functions run, so it must usually be statically linked. |
| 42 | |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 43 | This clock should be battery-backed, so that it reads the correct |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 44 | time when the system boots from a power-off state. Otherwise, your |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 45 | system will need an external clock source (like an NTP server). |
| 46 | |
| 47 | If the clock you specify here is not battery backed, it may still |
| 48 | be useful to reinitialize system time when resuming from system |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 49 | sleep states. Do not specify an RTC here unless it stays powered |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 50 | during all this system's supported sleep states. |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 51 | |
David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 52 | config RTC_DEBUG |
| 53 | bool "RTC debug support" |
| 54 | depends on RTC_CLASS = y |
| 55 | help |
| 56 | Say yes here to enable debugging support in the RTC framework |
| 57 | and individual RTC drivers. |
| 58 | |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 59 | comment "RTC interfaces" |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 60 | |
Alessandro Zummo | c5c3e19 | 2006-03-27 01:16:39 -0800 | [diff] [blame] | 61 | config RTC_INTF_SYSFS |
David Brownell | e40659c | 2007-05-16 22:11:15 -0700 | [diff] [blame] | 62 | boolean "/sys/class/rtc/rtcN (sysfs)" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 63 | depends on SYSFS |
Alessandro Zummo | c5c3e19 | 2006-03-27 01:16:39 -0800 | [diff] [blame] | 64 | default RTC_CLASS |
| 65 | help |
David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 66 | Say yes here if you want to use your RTCs using sysfs interfaces, |
| 67 | /sys/class/rtc/rtc0 through /sys/.../rtcN. |
Alessandro Zummo | c5c3e19 | 2006-03-27 01:16:39 -0800 | [diff] [blame] | 68 | |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 69 | If unsure, say Y. |
Alessandro Zummo | c5c3e19 | 2006-03-27 01:16:39 -0800 | [diff] [blame] | 70 | |
Alessandro Zummo | 728a294 | 2006-03-27 01:16:40 -0800 | [diff] [blame] | 71 | config RTC_INTF_PROC |
David Brownell | e40659c | 2007-05-16 22:11:15 -0700 | [diff] [blame] | 72 | boolean "/proc/driver/rtc (procfs for rtc0)" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 73 | depends on PROC_FS |
Alessandro Zummo | 728a294 | 2006-03-27 01:16:40 -0800 | [diff] [blame] | 74 | default RTC_CLASS |
| 75 | help |
David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 76 | Say yes here if you want to use your first RTC through the proc |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 77 | interface, /proc/driver/rtc. Other RTCs will not be available |
David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 78 | through that API. |
Alessandro Zummo | 728a294 | 2006-03-27 01:16:40 -0800 | [diff] [blame] | 79 | |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 80 | If unsure, say Y. |
Alessandro Zummo | 728a294 | 2006-03-27 01:16:40 -0800 | [diff] [blame] | 81 | |
Alessandro Zummo | e824290 | 2006-03-27 01:16:41 -0800 | [diff] [blame] | 82 | config RTC_INTF_DEV |
David Brownell | e40659c | 2007-05-16 22:11:15 -0700 | [diff] [blame] | 83 | boolean "/dev/rtcN (character devices)" |
Alessandro Zummo | e824290 | 2006-03-27 01:16:41 -0800 | [diff] [blame] | 84 | default RTC_CLASS |
| 85 | help |
David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 86 | Say yes here if you want to use your RTCs using the /dev |
| 87 | interfaces, which "udev" sets up as /dev/rtc0 through |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 88 | /dev/rtcN. |
Alessandro Zummo | e824290 | 2006-03-27 01:16:41 -0800 | [diff] [blame] | 89 | |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 90 | You may want to set up a symbolic link so one of these |
| 91 | can be accessed as /dev/rtc, which is a name |
| 92 | expected by "hwclock" and some other programs. Recent |
| 93 | versions of "udev" are known to set up the symlink for you. |
| 94 | |
| 95 | If unsure, say Y. |
Alessandro Zummo | e824290 | 2006-03-27 01:16:41 -0800 | [diff] [blame] | 96 | |
John Stultz | 6e57b1d | 2011-02-11 17:45:40 -0800 | [diff] [blame] | 97 | config RTC_INTF_DEV_UIE_EMUL |
| 98 | bool "RTC UIE emulation on dev interface" |
| 99 | depends on RTC_INTF_DEV |
| 100 | help |
| 101 | Provides an emulation for RTC_UIE if the underlying rtc chip |
| 102 | driver does not expose RTC_UIE ioctls. Those requests generate |
| 103 | once-per-second update interrupts, used for synchronization. |
| 104 | |
| 105 | The emulation code will read the time from the hardware |
| 106 | clock several times per second, please enable this option |
| 107 | only if you know that you really need it. |
| 108 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 109 | config RTC_DRV_TEST |
| 110 | tristate "Test driver/device" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 111 | help |
| 112 | If you say yes here you get support for the |
| 113 | RTC test driver. It's a software RTC which can be |
| 114 | used to test the RTC subsystem APIs. It gets |
| 115 | the time from the system clock. |
| 116 | You want this driver only if you are doing development |
| 117 | on the RTC subsystem. Please read the source code |
| 118 | for further details. |
| 119 | |
| 120 | This driver can also be built as a module. If so, the module |
| 121 | will be called rtc-test. |
| 122 | |
| 123 | comment "I2C RTC drivers" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 124 | depends on I2C |
| 125 | |
| 126 | if I2C |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 127 | |
Haojian Zhuang | 008b304 | 2011-05-06 17:21:20 +0800 | [diff] [blame] | 128 | config RTC_DRV_88PM860X |
| 129 | tristate "Marvell 88PM860x" |
| 130 | depends on RTC_CLASS && I2C && MFD_88PM860X |
| 131 | help |
| 132 | If you say yes here you get support for RTC function in Marvell |
| 133 | 88PM860x chips. |
| 134 | |
| 135 | This driver can also be built as a module. If so, the module |
| 136 | will be called rtc-88pm860x. |
| 137 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 138 | config RTC_DRV_DS1307 |
Matthias Fuchs | a216685 | 2009-03-31 15:24:58 -0700 | [diff] [blame] | 139 | tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 140 | help |
| 141 | If you say yes here you get support for various compatible RTC |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 142 | chips (often with battery backup) connected with I2C. This driver |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 143 | should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00, |
Matthias Fuchs | a216685 | 2009-03-31 15:24:58 -0700 | [diff] [blame] | 144 | EPSON RX-8025 and probably other chips. In some cases the RTC |
| 145 | must already have been initialized (by manufacturing or a |
| 146 | bootloader). |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 147 | |
| 148 | The first seven registers on these chips hold an RTC, and other |
| 149 | registers may add features such as NVRAM, a trickle charger for |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 150 | the RTC/NVRAM backup power, and alarms. NVRAM is visible in |
David Brownell | 682d73f | 2007-11-14 16:58:32 -0800 | [diff] [blame] | 151 | sysfs, but other chip features may not be available. |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 152 | |
| 153 | This driver can also be built as a module. If so, the module |
| 154 | will be called rtc-ds1307. |
| 155 | |
Scott Wood | bf4994d | 2007-10-16 01:28:19 -0700 | [diff] [blame] | 156 | config RTC_DRV_DS1374 |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 157 | tristate "Dallas/Maxim DS1374" |
Scott Wood | bf4994d | 2007-10-16 01:28:19 -0700 | [diff] [blame] | 158 | depends on RTC_CLASS && I2C |
| 159 | help |
| 160 | If you say yes here you get support for Dallas Semiconductor |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 161 | DS1374 real-time clock chips. If an interrupt is associated |
Scott Wood | bf4994d | 2007-10-16 01:28:19 -0700 | [diff] [blame] | 162 | with the device, the alarm functionality is supported. |
| 163 | |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 164 | This driver can also be built as a module. If so, the module |
Scott Wood | bf4994d | 2007-10-16 01:28:19 -0700 | [diff] [blame] | 165 | will be called rtc-ds1374. |
| 166 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 167 | config RTC_DRV_DS1672 |
| 168 | tristate "Dallas/Maxim DS1672" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 169 | help |
| 170 | If you say yes here you get support for the |
| 171 | Dallas/Maxim DS1672 timekeeping chip. |
| 172 | |
| 173 | This driver can also be built as a module. If so, the module |
| 174 | will be called rtc-ds1672. |
| 175 | |
Roy Zang | c03675f | 2010-08-10 18:02:20 -0700 | [diff] [blame] | 176 | config RTC_DRV_DS3232 |
| 177 | tristate "Dallas/Maxim DS3232" |
| 178 | depends on RTC_CLASS && I2C |
| 179 | help |
| 180 | If you say yes here you get support for Dallas Semiconductor |
Lan Chunhe-B25806 | f46418c | 2010-10-27 15:33:12 -0700 | [diff] [blame] | 181 | DS3232 real-time clock chips. If an interrupt is associated |
| 182 | with the device, the alarm functionality is supported. |
Roy Zang | c03675f | 2010-08-10 18:02:20 -0700 | [diff] [blame] | 183 | |
| 184 | This driver can also be built as a module. If so, the module |
| 185 | will be called rtc-ds3232. |
| 186 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 187 | config RTC_DRV_MAX6900 |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 188 | tristate "Maxim MAX6900" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 189 | help |
| 190 | If you say yes here you will get support for the |
| 191 | Maxim MAX6900 I2C RTC chip. |
| 192 | |
| 193 | This driver can also be built as a module. If so, the module |
| 194 | will be called rtc-max6900. |
| 195 | |
Haojian Zhuang | a39069f | 2010-01-25 06:30:29 -0500 | [diff] [blame] | 196 | config RTC_DRV_MAX8925 |
| 197 | tristate "Maxim MAX8925" |
| 198 | depends on MFD_MAX8925 |
| 199 | help |
| 200 | If you say yes here you will get support for the |
| 201 | RTC of Maxim MAX8925 PMIC. |
| 202 | |
| 203 | This driver can also be built as a module. If so, the module |
| 204 | will be called rtc-max8925. |
| 205 | |
Joonyoung Shim | 9b16c0a | 2010-08-06 11:28:08 +0900 | [diff] [blame] | 206 | config RTC_DRV_MAX8998 |
| 207 | tristate "Maxim MAX8998" |
| 208 | depends on MFD_MAX8998 |
| 209 | help |
| 210 | If you say yes here you will get support for the |
| 211 | RTC of Maxim MAX8998 PMIC. |
| 212 | |
| 213 | This driver can also be built as a module. If so, the module |
| 214 | will be called rtc-max8998. |
| 215 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 216 | config RTC_DRV_RS5C372 |
Paul Mundt | 5d4529b | 2008-10-21 20:12:59 +0900 | [diff] [blame] | 217 | tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 218 | help |
| 219 | If you say yes here you get support for the |
Paul Mundt | 5d4529b | 2008-10-21 20:12:59 +0900 | [diff] [blame] | 220 | Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 221 | |
| 222 | This driver can also be built as a module. If so, the module |
| 223 | will be called rtc-rs5c372. |
| 224 | |
| 225 | config RTC_DRV_ISL1208 |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 226 | tristate "Intersil ISL1208" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 227 | help |
| 228 | If you say yes here you get support for the |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 229 | Intersil ISL1208 RTC chip. |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 230 | |
| 231 | This driver can also be built as a module. If so, the module |
| 232 | will be called rtc-isl1208. |
| 233 | |
Roman Fietze | d6c7428 | 2010-08-10 18:02:14 -0700 | [diff] [blame] | 234 | config RTC_DRV_ISL12022 |
| 235 | tristate "Intersil ISL12022" |
| 236 | help |
| 237 | If you say yes here you get support for the |
| 238 | Intersil ISL12022 RTC chip. |
| 239 | |
| 240 | This driver can also be built as a module. If so, the module |
| 241 | will be called rtc-isl12022. |
| 242 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 243 | config RTC_DRV_X1205 |
| 244 | tristate "Xicor/Intersil X1205" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 245 | help |
| 246 | If you say yes here you get support for the |
| 247 | Xicor/Intersil X1205 RTC chip. |
| 248 | |
| 249 | This driver can also be built as a module. If so, the module |
| 250 | will be called rtc-x1205. |
| 251 | |
| 252 | config RTC_DRV_PCF8563 |
| 253 | tristate "Philips PCF8563/Epson RTC8564" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 254 | help |
| 255 | If you say yes here you get support for the |
| 256 | Philips PCF8563 RTC chip. The Epson RTC8564 |
| 257 | should work as well. |
| 258 | |
| 259 | This driver can also be built as a module. If so, the module |
| 260 | will be called rtc-pcf8563. |
| 261 | |
| 262 | config RTC_DRV_PCF8583 |
| 263 | tristate "Philips PCF8583" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 264 | help |
| 265 | If you say yes here you get support for the Philips PCF8583 |
| 266 | RTC chip found on Acorn RiscPCs. This driver supports the |
| 267 | platform specific method of retrieving the current year from |
| 268 | the RTC's SRAM. It will work on other platforms with the same |
| 269 | chip, but the year will probably have to be tweaked. |
| 270 | |
| 271 | This driver can also be built as a module. If so, the module |
| 272 | will be called rtc-pcf8583. |
| 273 | |
Atsushi Nemoto | caaff56 | 2007-07-17 04:05:02 -0700 | [diff] [blame] | 274 | config RTC_DRV_M41T80 |
Daniel Glockner | f30281f | 2009-04-02 16:57:03 -0700 | [diff] [blame] | 275 | tristate "ST M41T62/65/M41T80/81/82/83/84/85/87" |
Atsushi Nemoto | caaff56 | 2007-07-17 04:05:02 -0700 | [diff] [blame] | 276 | help |
Steven A. Falco | d3a126f | 2008-10-15 22:03:07 -0700 | [diff] [blame] | 277 | If you say Y here you will get support for the ST M41T60 |
| 278 | and M41T80 RTC chips series. Currently, the following chips are |
Daniel Glockner | f30281f | 2009-04-02 16:57:03 -0700 | [diff] [blame] | 279 | supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84, |
Steven A. Falco | d3a126f | 2008-10-15 22:03:07 -0700 | [diff] [blame] | 280 | M41ST85, and M41ST87. |
Atsushi Nemoto | caaff56 | 2007-07-17 04:05:02 -0700 | [diff] [blame] | 281 | |
| 282 | This driver can also be built as a module. If so, the module |
| 283 | will be called rtc-m41t80. |
| 284 | |
Atsushi Nemoto | 617780d | 2007-07-17 04:05:04 -0700 | [diff] [blame] | 285 | config RTC_DRV_M41T80_WDT |
Steven A. Falco | d3a126f | 2008-10-15 22:03:07 -0700 | [diff] [blame] | 286 | bool "ST M41T65/M41T80 series RTC watchdog timer" |
Atsushi Nemoto | 617780d | 2007-07-17 04:05:04 -0700 | [diff] [blame] | 287 | depends on RTC_DRV_M41T80 |
| 288 | help |
| 289 | If you say Y here you will get support for the |
Steven A. Falco | d3a126f | 2008-10-15 22:03:07 -0700 | [diff] [blame] | 290 | watchdog timer in the ST M41T60 and M41T80 RTC chips series. |
Atsushi Nemoto | 617780d | 2007-07-17 04:05:04 -0700 | [diff] [blame] | 291 | |
Piotr Ziecik | 1ce7c83 | 2009-12-15 16:46:12 -0800 | [diff] [blame] | 292 | config RTC_DRV_BQ32K |
| 293 | tristate "TI BQ32000" |
| 294 | help |
| 295 | If you say Y here you will get support for the TI |
| 296 | BQ32000 I2C RTC chip. |
| 297 | |
| 298 | This driver can also be built as a module. If so, the module |
| 299 | will be called rtc-bq32k. |
| 300 | |
David Brownell | afd8d0f | 2009-02-04 15:12:01 -0800 | [diff] [blame] | 301 | config RTC_DRV_DM355EVM |
| 302 | tristate "TI DaVinci DM355 EVM RTC" |
| 303 | depends on MFD_DM355EVM_MSP |
| 304 | help |
| 305 | Supports the RTC firmware in the MSP430 on the DM355 EVM. |
| 306 | |
Tony Lindgren | 0c4a59f | 2007-07-17 04:06:09 -0700 | [diff] [blame] | 307 | config RTC_DRV_TWL92330 |
| 308 | boolean "TI TWL92330/Menelaus" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 309 | depends on MENELAUS |
Tony Lindgren | 0c4a59f | 2007-07-17 04:06:09 -0700 | [diff] [blame] | 310 | help |
| 311 | If you say yes here you get support for the RTC on the |
Matt LaPlante | 01dd2fb | 2007-10-20 01:34:40 +0200 | [diff] [blame] | 312 | TWL92330 "Menelaus" power management chip, used with OMAP2 |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 313 | platforms. The support is integrated with the rest of |
Tony Lindgren | 0c4a59f | 2007-07-17 04:06:09 -0700 | [diff] [blame] | 314 | the Menelaus driver; it's not separate module. |
| 315 | |
David Brownell | f96411a | 2008-10-20 23:50:05 +0200 | [diff] [blame] | 316 | config RTC_DRV_TWL4030 |
Balaji T K | a6b49ff | 2009-12-13 22:16:31 +0100 | [diff] [blame] | 317 | tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0" |
David Brownell | f96411a | 2008-10-20 23:50:05 +0200 | [diff] [blame] | 318 | depends on RTC_CLASS && TWL4030_CORE |
| 319 | help |
| 320 | If you say yes here you get support for the RTC on the |
Balaji T K | a6b49ff | 2009-12-13 22:16:31 +0100 | [diff] [blame] | 321 | TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms. |
David Brownell | f96411a | 2008-10-20 23:50:05 +0200 | [diff] [blame] | 322 | |
| 323 | This driver can also be built as a module. If so, the module |
Balaji T K | a6b49ff | 2009-12-13 22:16:31 +0100 | [diff] [blame] | 324 | will be called rtc-twl. |
David Brownell | f96411a | 2008-10-20 23:50:05 +0200 | [diff] [blame] | 325 | |
Byron Bradley | c46288b | 2008-03-04 14:28:25 -0800 | [diff] [blame] | 326 | config RTC_DRV_S35390A |
| 327 | tristate "Seiko Instruments S-35390A" |
Randy Dunlap | d479540 | 2008-04-10 21:29:18 -0700 | [diff] [blame] | 328 | select BITREVERSE |
Byron Bradley | c46288b | 2008-03-04 14:28:25 -0800 | [diff] [blame] | 329 | help |
| 330 | If you say yes here you will get support for the Seiko |
| 331 | Instruments S-35390A. |
| 332 | |
| 333 | This driver can also be built as a module. If so the module |
| 334 | will be called rtc-s35390a. |
| 335 | |
Sergey Lapin | c6d8f40 | 2008-06-12 15:21:55 -0700 | [diff] [blame] | 336 | config RTC_DRV_FM3130 |
| 337 | tristate "Ramtron FM3130" |
| 338 | help |
| 339 | If you say Y here you will get support for the |
| 340 | Ramtron FM3130 RTC chips. |
| 341 | Ramtron FM3130 is a chip with two separate devices inside, |
| 342 | RTC clock and FRAM. This driver provides only RTC functionality. |
| 343 | |
| 344 | This driver can also be built as a module. If so the module |
| 345 | will be called rtc-fm3130. |
| 346 | |
Martyn Welch | a7fa985 | 2008-11-12 13:27:06 -0800 | [diff] [blame] | 347 | config RTC_DRV_RX8581 |
| 348 | tristate "Epson RX-8581" |
| 349 | help |
| 350 | If you say yes here you will get support for the Epson RX-8581. |
| 351 | |
| 352 | This driver can also be built as a module. If so the module |
| 353 | will be called rtc-rx8581. |
| 354 | |
Wolfgang Grandegger | 3c2b907 | 2009-06-17 16:26:11 -0700 | [diff] [blame] | 355 | config RTC_DRV_RX8025 |
| 356 | tristate "Epson RX-8025SA/NB" |
| 357 | help |
| 358 | If you say yes here you get support for the Epson |
| 359 | RX-8025SA/NB RTC chips. |
| 360 | |
| 361 | This driver can also be built as a module. If so, the module |
| 362 | will be called rtc-rx8025. |
| 363 | |
Mike Rapoport | ae3551f | 2011-05-26 16:25:04 -0700 | [diff] [blame] | 364 | config RTC_DRV_EM3027 |
| 365 | tristate "EM Microelectronic EM3027" |
| 366 | help |
| 367 | If you say yes here you get support for the EM |
| 368 | Microelectronic EM3027 RTC chips. |
| 369 | |
| 370 | This driver can also be built as a module. If so, the module |
| 371 | will be called rtc-em3027. |
| 372 | |
Heiko Schocher | 5236523 | 2011-05-26 16:25:05 -0700 | [diff] [blame] | 373 | config RTC_DRV_RV3029C2 |
| 374 | tristate "Micro Crystal RTC" |
| 375 | help |
| 376 | If you say yes here you get support for the Micro Crystal |
| 377 | RV3029-C2 RTC chips. |
| 378 | |
| 379 | This driver can also be built as a module. If so, the module |
| 380 | will be called rtc-rv3029c2. |
| 381 | |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 382 | endif # I2C |
| 383 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 384 | comment "SPI RTC drivers" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 385 | |
| 386 | if SPI_MASTER |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 387 | |
Voss, Nikolaus | 74d34d4 | 2011-05-26 16:25:07 -0700 | [diff] [blame] | 388 | config RTC_DRV_M41T93 |
| 389 | tristate "ST M41T93" |
| 390 | help |
| 391 | If you say yes here you will get support for the |
| 392 | ST M41T93 SPI RTC chip. |
| 393 | |
| 394 | This driver can also be built as a module. If so, the module |
| 395 | will be called rtc-m41t93. |
| 396 | |
Kim B. Heino | 8fc2c76 | 2008-07-23 21:30:34 -0700 | [diff] [blame] | 397 | config RTC_DRV_M41T94 |
| 398 | tristate "ST M41T94" |
| 399 | help |
| 400 | If you say yes here you will get support for the |
| 401 | ST M41T94 SPI RTC chip. |
| 402 | |
| 403 | This driver can also be built as a module. If so, the module |
| 404 | will be called rtc-m41t94. |
| 405 | |
David Brownell | 53e84b6 | 2008-07-23 21:30:36 -0700 | [diff] [blame] | 406 | config RTC_DRV_DS1305 |
| 407 | tristate "Dallas/Maxim DS1305/DS1306" |
| 408 | help |
| 409 | Select this driver to get support for the Dallas/Maxim DS1305 |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 410 | and DS1306 real time clock chips. These support a trickle |
David Brownell | 53e84b6 | 2008-07-23 21:30:36 -0700 | [diff] [blame] | 411 | charger, alarms, and NVRAM in addition to the clock. |
| 412 | |
| 413 | This driver can also be built as a module. If so, the module |
| 414 | will be called rtc-ds1305. |
| 415 | |
Mark Jackson | 06de180 | 2008-11-12 13:27:07 -0800 | [diff] [blame] | 416 | config RTC_DRV_DS1390 |
| 417 | tristate "Dallas/Maxim DS1390/93/94" |
| 418 | help |
Alessandro Zummo | 7b9b2ef | 2009-01-06 14:42:16 -0800 | [diff] [blame] | 419 | If you say yes here you get support for the |
| 420 | Dallas/Maxim DS1390/93/94 chips. |
Mark Jackson | 06de180 | 2008-11-12 13:27:07 -0800 | [diff] [blame] | 421 | |
| 422 | This driver only supports the RTC feature, and not other chip |
| 423 | features such as alarms and trickle charging. |
| 424 | |
| 425 | This driver can also be built as a module. If so, the module |
| 426 | will be called rtc-ds1390. |
| 427 | |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 428 | config RTC_DRV_MAX6902 |
| 429 | tristate "Maxim MAX6902" |
| 430 | help |
| 431 | If you say yes here you will get support for the |
| 432 | Maxim MAX6902 SPI RTC chip. |
| 433 | |
| 434 | This driver can also be built as a module. If so, the module |
| 435 | will be called rtc-max6902. |
| 436 | |
Magnus Damm | 2805b96 | 2008-02-06 01:38:53 -0800 | [diff] [blame] | 437 | config RTC_DRV_R9701 |
| 438 | tristate "Epson RTC-9701JE" |
| 439 | help |
| 440 | If you say yes here you will get support for the |
| 441 | Epson RTC-9701JE SPI RTC chip. |
| 442 | |
| 443 | This driver can also be built as a module. If so, the module |
| 444 | will be called rtc-r9701. |
| 445 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 446 | config RTC_DRV_RS5C348 |
| 447 | tristate "Ricoh RS5C348A/B" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 448 | help |
| 449 | If you say yes here you get support for the |
| 450 | Ricoh RS5C348A and RS5C348B RTC chips. |
| 451 | |
| 452 | This driver can also be built as a module. If so, the module |
| 453 | will be called rtc-rs5c348. |
| 454 | |
Dennis Aberilla | 2f9b75e | 2008-10-15 22:02:57 -0700 | [diff] [blame] | 455 | config RTC_DRV_DS3234 |
| 456 | tristate "Maxim/Dallas DS3234" |
| 457 | help |
| 458 | If you say yes here you get support for the |
| 459 | Maxim/Dallas DS3234 SPI RTC chip. |
| 460 | |
| 461 | This driver can also be built as a module. If so, the module |
| 462 | will be called rtc-ds3234. |
| 463 | |
Chris Verges | 7f3923a | 2009-09-22 16:46:20 -0700 | [diff] [blame] | 464 | config RTC_DRV_PCF2123 |
| 465 | tristate "NXP PCF2123" |
| 466 | help |
| 467 | If you say yes here you get support for the NXP PCF2123 |
| 468 | RTC chip. |
| 469 | |
| 470 | This driver can also be built as a module. If so, the module |
| 471 | will be called rtc-pcf2123. |
| 472 | |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 473 | endif # SPI_MASTER |
| 474 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 475 | comment "Platform RTC drivers" |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 476 | |
David Brownell | 7be2c7c | 2007-02-10 01:46:02 -0800 | [diff] [blame] | 477 | # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> |
| 478 | # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a |
| 479 | # global rtc_lock ... it's not yet just another platform_device. |
| 480 | |
| 481 | config RTC_DRV_CMOS |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 482 | tristate "PC-style 'CMOS'" |
Andrew Morton | 5ec8770 | 2008-09-22 21:40:04 -0700 | [diff] [blame] | 483 | depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64 |
David Brownell | c750090 | 2008-04-28 02:11:52 -0700 | [diff] [blame] | 484 | default y if X86 |
David Brownell | 7be2c7c | 2007-02-10 01:46:02 -0800 | [diff] [blame] | 485 | help |
| 486 | Say "yes" here to get direct support for the real time clock |
| 487 | found in every PC or ACPI-based system, and some other boards. |
| 488 | Specifically the original MC146818, compatibles like those in |
| 489 | PC south bridges, the DS12887 or M48T86, some multifunction |
| 490 | or LPC bus chips, and so on. |
| 491 | |
| 492 | Your system will need to define the platform device used by |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 493 | this driver, otherwise it won't be accessible. This means |
David Brownell | 7be2c7c | 2007-02-10 01:46:02 -0800 | [diff] [blame] | 494 | you can safely enable this driver if you don't know whether |
| 495 | or not your board has this kind of hardware. |
| 496 | |
| 497 | This driver can also be built as a module. If so, the module |
| 498 | will be called rtc-cmos. |
| 499 | |
Feng Tang | 0146f26 | 2010-11-10 17:29:17 +0000 | [diff] [blame] | 500 | config RTC_DRV_VRTC |
Alan Cox | 933b946 | 2011-12-17 17:43:40 +0000 | [diff] [blame] | 501 | tristate "Virtual RTC for Intel MID platforms" |
| 502 | depends on X86_INTEL_MID |
| 503 | default y if X86_INTEL_MID |
Feng Tang | 0146f26 | 2010-11-10 17:29:17 +0000 | [diff] [blame] | 504 | |
| 505 | help |
| 506 | Say "yes" here to get direct support for the real time clock |
| 507 | found on Moorestown platforms. The VRTC is a emulated RTC that |
| 508 | derives its clock source from a real RTC in the PMIC. The MC146818 |
| 509 | style programming interface is mostly conserved, but any |
| 510 | updates are done via IPC calls to the system controller FW. |
| 511 | |
Thomas Bogendoerfer | 537739d | 2007-07-17 04:05:06 -0700 | [diff] [blame] | 512 | config RTC_DRV_DS1216 |
| 513 | tristate "Dallas DS1216" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 514 | depends on SNI_RM |
Thomas Bogendoerfer | 537739d | 2007-07-17 04:05:06 -0700 | [diff] [blame] | 515 | help |
| 516 | If you say yes here you get support for the Dallas DS1216 RTC chips. |
| 517 | |
Thomas Bogendoerfer | 5f119f2 | 2008-10-14 17:16:59 +0200 | [diff] [blame] | 518 | config RTC_DRV_DS1286 |
| 519 | tristate "Dallas DS1286" |
| 520 | help |
| 521 | If you say yes here you get support for the Dallas DS1286 RTC chips. |
| 522 | |
Paul Mundt | 739d340 | 2008-02-06 01:38:44 -0800 | [diff] [blame] | 523 | config RTC_DRV_DS1302 |
| 524 | tristate "Dallas DS1302" |
| 525 | depends on SH_SECUREEDGE5410 |
| 526 | help |
| 527 | If you say yes here you get support for the Dallas DS1302 RTC chips. |
| 528 | |
Andrew Sharp | 8f26795 | 2008-02-06 01:38:46 -0800 | [diff] [blame] | 529 | config RTC_DRV_DS1511 |
| 530 | tristate "Dallas DS1511" |
| 531 | depends on RTC_CLASS |
| 532 | help |
| 533 | If you say yes here you get support for the |
| 534 | Dallas DS1511 timekeeping/watchdog chip. |
| 535 | |
| 536 | This driver can also be built as a module. If so, the module |
| 537 | will be called rtc-ds1511. |
| 538 | |
Atsushi Nemoto | 9bf5b4f | 2006-06-25 05:48:28 -0700 | [diff] [blame] | 539 | config RTC_DRV_DS1553 |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 540 | tristate "Maxim/Dallas DS1553" |
Atsushi Nemoto | 9bf5b4f | 2006-06-25 05:48:28 -0700 | [diff] [blame] | 541 | help |
| 542 | If you say yes here you get support for the |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 543 | Maxim/Dallas DS1553 timekeeping chip. |
Atsushi Nemoto | 9bf5b4f | 2006-06-25 05:48:28 -0700 | [diff] [blame] | 544 | |
| 545 | This driver can also be built as a module. If so, the module |
| 546 | will be called rtc-ds1553. |
| 547 | |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 548 | config RTC_DRV_DS1742 |
| 549 | tristate "Maxim/Dallas DS1742/1743" |
| 550 | help |
| 551 | If you say yes here you get support for the |
| 552 | Maxim/Dallas DS1742/1743 timekeeping chip. |
| 553 | |
| 554 | This driver can also be built as a module. If so, the module |
| 555 | will be called rtc-ds1742. |
| 556 | |
Ashish Jangam | fef931f | 2012-03-23 15:02:36 -0700 | [diff] [blame] | 557 | config RTC_DRV_DA9052 |
| 558 | tristate "Dialog DA9052/DA9053 RTC" |
| 559 | depends on PMIC_DA9052 |
| 560 | help |
| 561 | Say y here to support the RTC driver for Dialog Semiconductor |
| 562 | DA9052-BC and DA9053-AA/Bx PMICs. |
| 563 | |
dann frazier | 5e3fd9e | 2009-03-31 15:24:48 -0700 | [diff] [blame] | 564 | config RTC_DRV_EFI |
| 565 | tristate "EFI RTC" |
| 566 | depends on IA64 |
| 567 | help |
| 568 | If you say yes here you will get support for the EFI |
| 569 | Real Time Clock. |
| 570 | |
| 571 | This driver can also be built as a module. If so, the module |
| 572 | will be called rtc-efi. |
| 573 | |
Thomas Hommel | 0296411 | 2007-07-21 04:37:58 -0700 | [diff] [blame] | 574 | config RTC_DRV_STK17TA8 |
| 575 | tristate "Simtek STK17TA8" |
| 576 | depends on RTC_CLASS |
| 577 | help |
| 578 | If you say yes here you get support for the |
| 579 | Simtek STK17TA8 timekeeping chip. |
| 580 | |
| 581 | This driver can also be built as a module. If so, the module |
| 582 | will be called rtc-stk17ta8. |
| 583 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 584 | config RTC_DRV_M48T86 |
| 585 | tristate "ST M48T86/Dallas DS12887" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 586 | help |
| 587 | If you say Y here you will get support for the |
| 588 | ST M48T86 and Dallas DS12887 RTC chips. |
| 589 | |
| 590 | This driver can also be built as a module. If so, the module |
| 591 | will be called rtc-m48t86. |
| 592 | |
Thomas Bogendoerfer | d1dbd82e | 2008-10-14 17:17:32 +0200 | [diff] [blame] | 593 | config RTC_DRV_M48T35 |
| 594 | tristate "ST M48T35" |
| 595 | help |
| 596 | If you say Y here you will get support for the |
| 597 | ST M48T35 RTC chip. |
| 598 | |
| 599 | This driver can also be built as a module, if so, the module |
| 600 | will be called "rtc-m48t35". |
| 601 | |
Mark Zhan | 2e774c7 | 2007-07-17 04:05:05 -0700 | [diff] [blame] | 602 | config RTC_DRV_M48T59 |
Krzysztof Helt | 94fe742 | 2008-09-03 15:12:34 -0700 | [diff] [blame] | 603 | tristate "ST M48T59/M48T08/M48T02" |
Mark Zhan | 2e774c7 | 2007-07-17 04:05:05 -0700 | [diff] [blame] | 604 | help |
| 605 | If you say Y here you will get support for the |
Krzysztof Helt | 94fe742 | 2008-09-03 15:12:34 -0700 | [diff] [blame] | 606 | ST M48T59 RTC chip and compatible ST M48T08 and M48T02. |
| 607 | |
| 608 | These chips are usually found in Sun SPARC and UltraSPARC |
| 609 | workstations. |
Mark Zhan | 2e774c7 | 2007-07-17 04:05:05 -0700 | [diff] [blame] | 610 | |
| 611 | This driver can also be built as a module, if so, the module |
| 612 | will be called "rtc-m48t59". |
| 613 | |
Geert Uytterhoeven | 4f9b9bb | 2009-03-18 23:29:27 +0100 | [diff] [blame] | 614 | config RTC_DRV_MSM6242 |
| 615 | tristate "Oki MSM6242" |
| 616 | help |
| 617 | If you say yes here you get support for the Oki MSM6242 |
| 618 | timekeeping chip. It is used in some Amiga models (e.g. A2000). |
| 619 | |
| 620 | This driver can also be built as a module. If so, the module |
| 621 | will be called rtc-msm6242. |
| 622 | |
David S. Miller | cca4c23 | 2008-08-29 01:29:53 -0700 | [diff] [blame] | 623 | config RTC_DRV_BQ4802 |
| 624 | tristate "TI BQ4802" |
| 625 | help |
| 626 | If you say Y here you will get support for the TI |
| 627 | BQ4802 RTC chip. |
| 628 | |
| 629 | This driver can also be built as a module. If so, the module |
| 630 | will be called rtc-bq4802. |
| 631 | |
Geert Uytterhoeven | 4f672ce | 2009-03-18 23:29:27 +0100 | [diff] [blame] | 632 | config RTC_DRV_RP5C01 |
| 633 | tristate "Ricoh RP5C01" |
| 634 | help |
| 635 | If you say yes here you get support for the Ricoh RP5C01 |
| 636 | timekeeping chip. It is used in some Amiga models (e.g. A3000 |
| 637 | and A4000). |
| 638 | |
| 639 | This driver can also be built as a module. If so, the module |
| 640 | will be called rtc-rp5c01. |
| 641 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 642 | config RTC_DRV_V3020 |
| 643 | tristate "EM Microelectronic V3020" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 644 | help |
| 645 | If you say yes here you will get support for the |
| 646 | EM Microelectronic v3020 RTC chip. |
| 647 | |
| 648 | This driver can also be built as a module. If so, the module |
| 649 | will be called rtc-v3020. |
| 650 | |
Mark Brown | 35c86bf | 2009-08-27 19:59:05 +0200 | [diff] [blame] | 651 | config RTC_DRV_WM831X |
| 652 | tristate "Wolfson Microelectronics WM831x RTC" |
| 653 | depends on MFD_WM831X |
| 654 | help |
| 655 | If you say yes here you will get support for the RTC subsystem |
| 656 | of the Wolfson Microelectronics WM831X series PMICs. |
| 657 | |
| 658 | This driver can also be built as a module. If so, the module |
| 659 | will be called "rtc-wm831x". |
| 660 | |
Mark Brown | 077eaf5 | 2008-11-12 13:27:04 -0800 | [diff] [blame] | 661 | config RTC_DRV_WM8350 |
| 662 | tristate "Wolfson Microelectronics WM8350 RTC" |
| 663 | depends on MFD_WM8350 |
| 664 | help |
| 665 | If you say yes here you will get support for the RTC subsystem |
| 666 | of the Wolfson Microelectronics WM8350. |
| 667 | |
| 668 | This driver can also be built as a module. If so, the module |
| 669 | will be called "rtc-wm8350". |
| 670 | |
Rajeev Kumar | 0942a71 | 2011-05-26 16:25:09 -0700 | [diff] [blame] | 671 | config RTC_DRV_SPEAR |
| 672 | tristate "SPEAR ST RTC" |
| 673 | depends on PLAT_SPEAR |
| 674 | default y |
| 675 | help |
| 676 | If you say Y here you will get support for the RTC found on |
| 677 | spear |
| 678 | |
Balaji Rao | eae854b | 2009-01-09 01:50:51 +0100 | [diff] [blame] | 679 | config RTC_DRV_PCF50633 |
| 680 | depends on MFD_PCF50633 |
| 681 | tristate "NXP PCF50633 RTC" |
| 682 | help |
| 683 | If you say yes here you get support for the RTC subsystem of the |
| 684 | NXP PCF50633 used in embedded systems. |
| 685 | |
Linus Walleij | bd207cf | 2009-08-30 23:49:04 +0200 | [diff] [blame] | 686 | config RTC_DRV_AB3100 |
| 687 | tristate "ST-Ericsson AB3100 RTC" |
| 688 | depends on AB3100_CORE |
| 689 | default y if AB3100_CORE |
| 690 | help |
| 691 | Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC |
| 692 | support. This chip contains a battery- and capacitor-backed RTC. |
| 693 | |
Virupax Sadashivpetimath | 0af62f4 | 2010-05-26 14:42:14 -0700 | [diff] [blame] | 694 | config RTC_DRV_AB8500 |
| 695 | tristate "ST-Ericsson AB8500 RTC" |
| 696 | depends on AB8500_CORE |
| 697 | help |
| 698 | Select this to enable the ST-Ericsson AB8500 power management IC RTC |
| 699 | support. This chip contains a battery- and capacitor-backed RTC. |
| 700 | |
Wan ZongShun | afd49a7e | 2009-12-15 16:46:17 -0800 | [diff] [blame] | 701 | config RTC_DRV_NUC900 |
| 702 | tristate "NUC910/NUC920 RTC driver" |
| 703 | depends on RTC_CLASS && ARCH_W90X900 |
| 704 | help |
| 705 | If you say yes here you get support for the RTC subsystem of the |
| 706 | NUC910/NUC920 used in embedded systems. |
Linus Walleij | bd207cf | 2009-08-30 23:49:04 +0200 | [diff] [blame] | 707 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 708 | comment "on-CPU RTC drivers" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 709 | |
Miguel Aguilar | 8ecf6c5 | 2009-11-05 08:51:34 -0600 | [diff] [blame] | 710 | config RTC_DRV_DAVINCI |
| 711 | tristate "TI DaVinci RTC" |
| 712 | depends on ARCH_DAVINCI_DM365 |
| 713 | help |
| 714 | If you say yes here you get support for the RTC on the |
| 715 | DaVinci platforms (DM365). |
| 716 | |
| 717 | This driver can also be built as a module. If so, the module |
| 718 | will be called rtc-davinci. |
| 719 | |
Fabio Estevam | b224b9a | 2012-05-29 15:07:37 -0700 | [diff] [blame] | 720 | config RTC_DRV_IMXDI |
| 721 | tristate "Freescale IMX DryIce Real Time Clock" |
| 722 | depends on SOC_IMX25 |
| 723 | depends on RTC_CLASS |
| 724 | help |
| 725 | Support for Freescale IMX DryIce RTC |
| 726 | |
| 727 | This driver can also be built as a module, if so, the module |
| 728 | will be called "rtc-imxdi". |
| 729 | |
David Brownell | db68b18 | 2006-12-06 20:38:36 -0800 | [diff] [blame] | 730 | config RTC_DRV_OMAP |
| 731 | tristate "TI OMAP1" |
Mark A. Greer | 8cfde8c | 2009-12-15 16:46:11 -0800 | [diff] [blame] | 732 | depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX |
David Brownell | db68b18 | 2006-12-06 20:38:36 -0800 | [diff] [blame] | 733 | help |
Mark A. Greer | 8cfde8c | 2009-12-15 16:46:11 -0800 | [diff] [blame] | 734 | Say "yes" here to support the real time clock on TI OMAP1 and |
| 735 | DA8xx/OMAP-L13x chips. This driver can also be built as a |
| 736 | module called rtc-omap. |
David Brownell | db68b18 | 2006-12-06 20:38:36 -0800 | [diff] [blame] | 737 | |
Atul Dahiya | 16f4efe | 2010-07-20 16:38:49 +0530 | [diff] [blame] | 738 | config HAVE_S3C_RTC |
| 739 | bool |
| 740 | help |
| 741 | This will include RTC support for Samsung SoCs. If |
| 742 | you want to include RTC support for any machine, kindly |
| 743 | select this in the respective mach-XXXX/Kconfig file. |
| 744 | |
Ben Dooks | 1add678 | 2006-07-01 04:36:26 -0700 | [diff] [blame] | 745 | config RTC_DRV_S3C |
| 746 | tristate "Samsung S3C series SoC RTC" |
Kukjin Kim | b130d5c | 2012-02-03 14:29:23 +0900 | [diff] [blame] | 747 | depends on ARCH_S3C64XX || HAVE_S3C_RTC |
Ben Dooks | 1add678 | 2006-07-01 04:36:26 -0700 | [diff] [blame] | 748 | help |
| 749 | RTC (Realtime Clock) driver for the clock inbuilt into the |
| 750 | Samsung S3C24XX series of SoCs. This can provide periodic |
| 751 | interrupt rates from 1Hz to 64Hz for user programs, and |
| 752 | wakeup from Alarm. |
| 753 | |
| 754 | The driver currently supports the common features on all the |
| 755 | S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 |
| 756 | and S3C2442. |
| 757 | |
| 758 | This driver can also be build as a module. If so, the module |
| 759 | will be called rtc-s3c. |
| 760 | |
Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 761 | config RTC_DRV_EP93XX |
| 762 | tristate "Cirrus Logic EP93XX" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 763 | depends on ARCH_EP93XX |
Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 764 | help |
| 765 | If you say yes here you get support for the |
| 766 | RTC embedded in the Cirrus Logic EP93XX processors. |
| 767 | |
| 768 | This driver can also be built as a module. If so, the module |
| 769 | will be called rtc-ep93xx. |
| 770 | |
Richard Purdie | e842f1c | 2006-03-27 01:16:46 -0800 | [diff] [blame] | 771 | config RTC_DRV_SA1100 |
Haojian Zhuang | 3888c09 | 2012-02-21 11:51:13 +0800 | [diff] [blame] | 772 | tristate "SA11x0/PXA2xx/PXA910" |
| 773 | depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP |
Richard Purdie | e842f1c | 2006-03-27 01:16:46 -0800 | [diff] [blame] | 774 | help |
| 775 | If you say Y here you will get access to the real time clock |
| 776 | built into your SA11x0 or PXA2xx CPU. |
| 777 | |
| 778 | To compile this driver as a module, choose M here: the |
| 779 | module will be called rtc-sa1100. |
Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 780 | |
Paul Mundt | 317a610 | 2006-09-27 17:13:19 +0900 | [diff] [blame] | 781 | config RTC_DRV_SH |
| 782 | tristate "SuperH On-Chip RTC" |
Paul Mundt | 063adc7 | 2009-04-16 14:12:22 +0900 | [diff] [blame] | 783 | depends on RTC_CLASS && SUPERH && HAVE_CLK |
Paul Mundt | 317a610 | 2006-09-27 17:13:19 +0900 | [diff] [blame] | 784 | help |
| 785 | Say Y here to enable support for the on-chip RTC found in |
| 786 | most SuperH processors. |
| 787 | |
| 788 | To compile this driver as a module, choose M here: the |
| 789 | module will be called rtc-sh. |
| 790 | |
Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 791 | config RTC_DRV_VR41XX |
Alessandro Zummo | 3e16f6a | 2006-04-10 22:54:48 -0700 | [diff] [blame] | 792 | tristate "NEC VR41XX" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 793 | depends on CPU_VR41XX |
Alessandro Zummo | 3e16f6a | 2006-04-10 22:54:48 -0700 | [diff] [blame] | 794 | help |
| 795 | If you say Y here you will get access to the real time clock |
| 796 | built into your NEC VR41XX CPU. |
| 797 | |
| 798 | To compile this driver as a module, choose M here: the |
| 799 | module will be called rtc-vr41xx. |
Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 800 | |
Russell King | a190901 | 2008-04-20 12:08:36 +0100 | [diff] [blame] | 801 | config RTC_DRV_PL030 |
| 802 | tristate "ARM AMBA PL030 RTC" |
| 803 | depends on ARM_AMBA |
| 804 | help |
| 805 | If you say Y here you will get access to ARM AMBA |
| 806 | PrimeCell PL030 RTC found on certain ARM SOCs. |
| 807 | |
| 808 | To compile this driver as a module, choose M here: the |
| 809 | module will be called rtc-pl030. |
| 810 | |
Deepak Saxena | 8ae6e16 | 2006-06-25 05:47:38 -0700 | [diff] [blame] | 811 | config RTC_DRV_PL031 |
| 812 | tristate "ARM AMBA PL031 RTC" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 813 | depends on ARM_AMBA |
Deepak Saxena | 8ae6e16 | 2006-06-25 05:47:38 -0700 | [diff] [blame] | 814 | help |
| 815 | If you say Y here you will get access to ARM AMBA |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 816 | PrimeCell PL031 RTC found on certain ARM SOCs. |
Deepak Saxena | 8ae6e16 | 2006-06-25 05:47:38 -0700 | [diff] [blame] | 817 | |
| 818 | To compile this driver as a module, choose M here: the |
| 819 | module will be called rtc-pl031. |
| 820 | |
Hans-Christian Egtvedt | fa04e78 | 2007-07-17 04:05:00 -0700 | [diff] [blame] | 821 | config RTC_DRV_AT32AP700X |
| 822 | tristate "AT32AP700X series RTC" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 823 | depends on PLATFORM_AT32AP |
Hans-Christian Egtvedt | fa04e78 | 2007-07-17 04:05:00 -0700 | [diff] [blame] | 824 | help |
| 825 | Driver for the internal RTC (Realtime Clock) on Atmel AVR32 |
| 826 | AT32AP700x family processors. |
| 827 | |
Andrew Victor | 7fc39f6 | 2006-12-10 02:19:03 -0800 | [diff] [blame] | 828 | config RTC_DRV_AT91RM9200 |
Nicolas Ferre | 24cecc1 | 2010-10-22 19:12:52 +0200 | [diff] [blame] | 829 | tristate "AT91RM9200 or some AT91SAM9 RTC" |
Nicolas Ferre | 938f970 | 2012-03-15 14:38:09 +0100 | [diff] [blame] | 830 | depends on ARCH_AT91 |
Andrew Victor | 788b1fc | 2006-06-25 05:48:27 -0700 | [diff] [blame] | 831 | help |
David Brownell | 4cdf854 | 2008-02-06 01:38:59 -0800 | [diff] [blame] | 832 | Driver for the internal RTC (Realtime Clock) module found on |
Nicolas Ferre | 24cecc1 | 2010-10-22 19:12:52 +0200 | [diff] [blame] | 833 | Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips |
David Brownell | 4cdf854 | 2008-02-06 01:38:59 -0800 | [diff] [blame] | 834 | this is powered by the backup power supply. |
| 835 | |
| 836 | config RTC_DRV_AT91SAM9 |
Nicolas Ferre | 24cecc1 | 2010-10-22 19:12:52 +0200 | [diff] [blame] | 837 | tristate "AT91SAM9x/AT91CAP9 RTT as RTC" |
David Brownell | 4cdf854 | 2008-02-06 01:38:59 -0800 | [diff] [blame] | 838 | depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40) |
| 839 | help |
Stelian Pop | 6b71dbf | 2008-04-05 21:16:15 +0100 | [diff] [blame] | 840 | RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT |
| 841 | (Real Time Timer). These timers are powered by the backup power |
| 842 | supply (such as a small coin cell battery), but do not need to |
| 843 | be used as RTCs. |
David Brownell | 4cdf854 | 2008-02-06 01:38:59 -0800 | [diff] [blame] | 844 | |
Nicolas Ferre | 24cecc1 | 2010-10-22 19:12:52 +0200 | [diff] [blame] | 845 | (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the |
| 846 | dedicated RTC module and leave the RTT available for other uses.) |
David Brownell | 4cdf854 | 2008-02-06 01:38:59 -0800 | [diff] [blame] | 847 | |
| 848 | config RTC_DRV_AT91SAM9_RTT |
| 849 | int |
| 850 | range 0 1 |
| 851 | default 0 |
| 852 | prompt "RTT module Number" if ARCH_AT91SAM9263 |
| 853 | depends on RTC_DRV_AT91SAM9 |
| 854 | help |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 855 | More than one RTT module is available. You can choose which |
| 856 | one will be used as an RTC. The default of zero is normally |
David Brownell | 4cdf854 | 2008-02-06 01:38:59 -0800 | [diff] [blame] | 857 | OK to use, though some systems use that for non-RTC purposes. |
| 858 | |
| 859 | config RTC_DRV_AT91SAM9_GPBR |
| 860 | int |
| 861 | range 0 3 if !ARCH_AT91SAM9263 |
| 862 | range 0 15 if ARCH_AT91SAM9263 |
| 863 | default 0 |
| 864 | prompt "Backup Register Number" |
| 865 | depends on RTC_DRV_AT91SAM9 |
| 866 | help |
| 867 | The RTC driver needs to use one of the General Purpose Backup |
Alessandro Zummo | ae64d16 | 2009-01-06 14:42:17 -0800 | [diff] [blame] | 868 | Registers (GPBRs) as well as the RTT. You can choose which one |
| 869 | will be used. The default of zero is normally OK to use, but |
David Brownell | 4cdf854 | 2008-02-06 01:38:59 -0800 | [diff] [blame] | 870 | on some systems other software needs to use that register. |
Andrew Victor | 788b1fc | 2006-06-25 05:48:27 -0700 | [diff] [blame] | 871 | |
Manuel Lauss | 45fd8a0 | 2009-01-06 14:42:18 -0800 | [diff] [blame] | 872 | config RTC_DRV_AU1XXX |
| 873 | tristate "Au1xxx Counter0 RTC support" |
Manuel Lauss | 42a4f17 | 2010-07-15 21:45:04 +0200 | [diff] [blame] | 874 | depends on MIPS_ALCHEMY |
Manuel Lauss | 45fd8a0 | 2009-01-06 14:42:18 -0800 | [diff] [blame] | 875 | help |
| 876 | This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year |
| 877 | counter) to be used as a RTC. |
| 878 | |
| 879 | This driver can also be built as a module. If so, the module |
| 880 | will be called rtc-au1xxx. |
| 881 | |
Wu, Bryan | 8cc75c9 | 2007-05-06 14:50:32 -0700 | [diff] [blame] | 882 | config RTC_DRV_BFIN |
| 883 | tristate "Blackfin On-Chip RTC" |
Graf Yang | 7f60459 | 2008-08-20 14:09:02 -0700 | [diff] [blame] | 884 | depends on BLACKFIN && !BF561 |
Wu, Bryan | 8cc75c9 | 2007-05-06 14:50:32 -0700 | [diff] [blame] | 885 | help |
| 886 | If you say yes here you will get support for the |
| 887 | Blackfin On-Chip Real Time Clock. |
| 888 | |
| 889 | This driver can also be built as a module. If so, the module |
| 890 | will be called rtc-bfin. |
| 891 | |
Nobuhiro Iwamatsu | e9f2bd8 | 2007-05-08 00:26:37 -0700 | [diff] [blame] | 892 | config RTC_DRV_RS5C313 |
| 893 | tristate "Ricoh RS5C313" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 894 | depends on SH_LANDISK |
Nobuhiro Iwamatsu | e9f2bd8 | 2007-05-08 00:26:37 -0700 | [diff] [blame] | 895 | help |
| 896 | If you say yes here you get support for the Ricoh RS5C313 RTC chips. |
| 897 | |
Geert Uytterhoeven | 3afe6d0 | 2009-02-19 16:46:49 +0100 | [diff] [blame] | 898 | config RTC_DRV_GENERIC |
| 899 | tristate "Generic RTC support" |
| 900 | # Please consider writing a new RTC driver instead of using the generic |
| 901 | # RTC abstraction |
Paul Mundt | 47c8a08 | 2009-04-27 17:34:39 +0900 | [diff] [blame] | 902 | depends on PARISC || M68K || PPC || SUPERH32 |
Kyle McMartin | 9eb1686 | 2008-09-10 14:24:07 +0000 | [diff] [blame] | 903 | help |
Geert Uytterhoeven | 3afe6d0 | 2009-02-19 16:46:49 +0100 | [diff] [blame] | 904 | Say Y or M here to enable RTC support on systems using the generic |
| 905 | RTC abstraction. If you do not know what you are doing, you should |
Kyle McMartin | 9eb1686 | 2008-09-10 14:24:07 +0000 | [diff] [blame] | 906 | just say Y. |
| 907 | |
Robert Jarzmik | dc94436 | 2009-01-06 14:42:14 -0800 | [diff] [blame] | 908 | config RTC_DRV_PXA |
| 909 | tristate "PXA27x/PXA3xx" |
| 910 | depends on ARCH_PXA |
| 911 | help |
| 912 | If you say Y here you will get access to the real time clock |
| 913 | built into your PXA27x or PXA3xx CPU. |
| 914 | |
| 915 | This RTC driver uses PXA RTC registers available since pxa27x |
| 916 | series (RDxR, RYxR) instead of legacy RCNR, RTAR. |
| 917 | |
Alexey Charkov | f77fbdf | 2011-05-26 16:25:03 -0700 | [diff] [blame] | 918 | config RTC_DRV_VT8500 |
| 919 | tristate "VIA/WonderMedia 85xx SoC RTC" |
| 920 | depends on ARCH_VT8500 |
| 921 | help |
| 922 | If you say Y here you will get access to the real time clock |
| 923 | built into your VIA VT8500 SoC or its relatives. |
| 924 | |
Robert Jarzmik | dc94436 | 2009-01-06 14:42:14 -0800 | [diff] [blame] | 925 | |
David S. Miller | 7a138ed | 2008-08-29 01:32:43 -0700 | [diff] [blame] | 926 | config RTC_DRV_SUN4V |
| 927 | bool "SUN4V Hypervisor RTC" |
| 928 | depends on SPARC64 |
| 929 | help |
| 930 | If you say Y here you will get support for the Hypervisor |
| 931 | based RTC on SUN4V systems. |
| 932 | |
David S. Miller | de2cf33 | 2008-08-28 23:02:36 -0700 | [diff] [blame] | 933 | config RTC_DRV_STARFIRE |
| 934 | bool "Starfire RTC" |
| 935 | depends on SPARC64 |
| 936 | help |
| 937 | If you say Y here you will get support for the RTC found on |
| 938 | Starfire systems. |
| 939 | |
Atsushi Nemoto | 0e14923 | 2009-01-06 14:42:22 -0800 | [diff] [blame] | 940 | config RTC_DRV_TX4939 |
| 941 | tristate "TX4939 SoC" |
| 942 | depends on SOC_TX4939 |
| 943 | help |
| 944 | Driver for the internal RTC (Realtime Clock) module found on |
| 945 | Toshiba TX4939 SoC. |
| 946 | |
Saeed Bishara | defb451 | 2009-01-06 14:42:24 -0800 | [diff] [blame] | 947 | config RTC_DRV_MV |
| 948 | tristate "Marvell SoC RTC" |
Saeed Bishara | da43243 | 2009-11-24 19:33:53 +0200 | [diff] [blame] | 949 | depends on ARCH_KIRKWOOD || ARCH_DOVE |
Saeed Bishara | defb451 | 2009-01-06 14:42:24 -0800 | [diff] [blame] | 950 | help |
| 951 | If you say yes here you will get support for the in-chip RTC |
| 952 | that can be found in some of Marvell's SoC devices, such as |
| 953 | the Kirkwood 88F6281 and 88F6192. |
| 954 | |
| 955 | This driver can also be built as a module. If so, the module |
| 956 | will be called rtc-mv. |
| 957 | |
Geert Uytterhoeven | 0b5f037 | 2009-02-24 14:04:20 +0100 | [diff] [blame] | 958 | config RTC_DRV_PS3 |
| 959 | tristate "PS3 RTC" |
| 960 | depends on PPC_PS3 |
| 961 | help |
| 962 | If you say yes here you will get support for the RTC on PS3. |
| 963 | |
| 964 | This driver can also be built as a module. If so, the module |
| 965 | will be called rtc-ps3. |
| 966 | |
Linus Walleij | aa958f5 | 2009-09-22 16:46:24 -0700 | [diff] [blame] | 967 | config RTC_DRV_COH901331 |
| 968 | tristate "ST-Ericsson COH 901 331 RTC" |
| 969 | depends on ARCH_U300 |
| 970 | help |
| 971 | If you say Y here you will get access to ST-Ericsson |
| 972 | COH 901 331 RTC clock found in some ST-Ericsson Mobile |
| 973 | Platforms. |
| 974 | |
| 975 | This driver can also be built as a module. If so, the module |
| 976 | will be called "rtc-coh901331". |
| 977 | |
| 978 | |
dmitry pervushin | df17f63 | 2009-09-22 16:46:26 -0700 | [diff] [blame] | 979 | config RTC_DRV_STMP |
Wolfram Sang | 46b2121 | 2011-05-25 12:56:50 +0200 | [diff] [blame] | 980 | tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC" |
| 981 | depends on ARCH_MXS |
dmitry pervushin | df17f63 | 2009-09-22 16:46:26 -0700 | [diff] [blame] | 982 | help |
| 983 | If you say yes here you will get support for the onboard |
Wolfram Sang | 46b2121 | 2011-05-25 12:56:50 +0200 | [diff] [blame] | 984 | STMP3xxx/i.MX23/i.MX28 RTC. |
dmitry pervushin | df17f63 | 2009-09-22 16:46:26 -0700 | [diff] [blame] | 985 | |
| 986 | This driver can also be built as a module. If so, the module |
| 987 | will be called rtc-stmp3xxx. |
| 988 | |
Daniel Ribeiro | d3c7a3f | 2009-09-22 16:46:27 -0700 | [diff] [blame] | 989 | config RTC_DRV_PCAP |
| 990 | tristate "PCAP RTC" |
| 991 | depends on EZX_PCAP |
| 992 | help |
| 993 | If you say Y here you will get support for the RTC found on |
| 994 | the PCAP2 ASIC used on some Motorola phones. |
| 995 | |
Uwe Kleine-König | 1c97872 | 2010-10-28 12:30:53 +0200 | [diff] [blame] | 996 | config RTC_DRV_MC13XXX |
| 997 | depends on MFD_MC13XXX |
| 998 | tristate "Freescale MC13xxx RTC" |
Uwe Kleine-König | 43299f285 | 2009-12-15 16:46:09 -0800 | [diff] [blame] | 999 | help |
Uwe Kleine-König | 1c97872 | 2010-10-28 12:30:53 +0200 | [diff] [blame] | 1000 | This enables support for the RTCs found on Freescale's PMICs |
| 1001 | MC13783 and MC13892. |
Uwe Kleine-König | 43299f285 | 2009-12-15 16:46:09 -0800 | [diff] [blame] | 1002 | |
Anatolij Gustschin | 50aae72 | 2010-02-16 10:47:35 -0700 | [diff] [blame] | 1003 | config RTC_DRV_MPC5121 |
| 1004 | tristate "Freescale MPC5121 built-in RTC" |
Dmitry Eremin-Solenikov | 955dbea | 2011-07-25 17:13:30 -0700 | [diff] [blame] | 1005 | depends on PPC_MPC512x || PPC_MPC52xx |
Anatolij Gustschin | 50aae72 | 2010-02-16 10:47:35 -0700 | [diff] [blame] | 1006 | help |
| 1007 | If you say yes here you will get support for the |
Dmitry Eremin-Solenikov | 955dbea | 2011-07-25 17:13:30 -0700 | [diff] [blame] | 1008 | built-in RTC on MPC5121 or on MPC5200. |
Anatolij Gustschin | 50aae72 | 2010-02-16 10:47:35 -0700 | [diff] [blame] | 1009 | |
| 1010 | This driver can also be built as a module. If so, the module |
| 1011 | will be called rtc-mpc5121. |
| 1012 | |
Lars-Peter Clausen | 3bf0eea | 2010-06-19 18:29:50 +0000 | [diff] [blame] | 1013 | config RTC_DRV_JZ4740 |
| 1014 | tristate "Ingenic JZ4740 SoC" |
| 1015 | depends on RTC_CLASS |
| 1016 | depends on MACH_JZ4740 |
| 1017 | help |
| 1018 | If you say yes here you get support for the Ingenic JZ4740 SoC RTC |
| 1019 | controller. |
| 1020 | |
| 1021 | This driver can also be buillt as a module. If so, the module |
| 1022 | will be called rtc-jz4740. |
| 1023 | |
Kevin Wells | 9aa449b | 2010-10-27 15:33:01 -0700 | [diff] [blame] | 1024 | config RTC_DRV_LPC32XX |
| 1025 | depends on ARCH_LPC32XX |
| 1026 | tristate "NXP LPC32XX RTC" |
| 1027 | help |
| 1028 | This enables support for the NXP RTC in the LPC32XX |
| 1029 | |
| 1030 | This driver can also be buillt as a module. If so, the module |
| 1031 | will be called rtc-lpc32xx. |
| 1032 | |
Anirudh Ghayal | 9a9a54a | 2011-07-25 17:13:33 -0700 | [diff] [blame] | 1033 | config RTC_DRV_PM8XXX |
| 1034 | tristate "Qualcomm PMIC8XXX RTC" |
| 1035 | depends on MFD_PM8XXX |
| 1036 | help |
| 1037 | If you say yes here you get support for the |
| 1038 | Qualcomm PMIC8XXX RTC. |
| 1039 | |
| 1040 | To compile this driver as a module, choose M here: the |
| 1041 | module will be called rtc-pm8xxx. |
| 1042 | |
Andrew Chew | ff859ba | 2011-03-22 16:34:55 -0700 | [diff] [blame] | 1043 | config RTC_DRV_TEGRA |
| 1044 | tristate "NVIDIA Tegra Internal RTC driver" |
| 1045 | depends on RTC_CLASS && ARCH_TEGRA |
| 1046 | help |
| 1047 | If you say yes here you get support for the |
| 1048 | Tegra 200 series internal RTC module. |
| 1049 | |
| 1050 | This drive can also be built as a module. If so, the module |
| 1051 | will be called rtc-tegra. |
| 1052 | |
Chris Metcalf | dd196a2 | 2011-05-09 13:28:43 -0400 | [diff] [blame] | 1053 | config RTC_DRV_TILE |
| 1054 | tristate "Tilera hypervisor RTC support" |
| 1055 | depends on TILE |
| 1056 | help |
| 1057 | Enable support for the Linux driver side of the Tilera |
| 1058 | hypervisor's real-time clock interface. |
| 1059 | |
Guan Xuetao | 2809e80 | 2011-05-26 16:43:27 +0800 | [diff] [blame] | 1060 | config RTC_DRV_PUV3 |
| 1061 | tristate "PKUnity v3 RTC support" |
| 1062 | depends on ARCH_PUV3 |
| 1063 | help |
| 1064 | This enables support for the RTC in the PKUnity-v3 SoCs. |
| 1065 | |
| 1066 | This drive can also be built as a module. If so, the module |
| 1067 | will be called rtc-puv3. |
| 1068 | |
zhao zhang | b4f0b88 | 2012-03-23 15:02:32 -0700 | [diff] [blame] | 1069 | config RTC_DRV_LOONGSON1 |
| 1070 | tristate "loongson1 RTC support" |
| 1071 | depends on MACH_LOONGSON1 |
| 1072 | help |
| 1073 | This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year |
| 1074 | counter) to be used as a RTC. |
| 1075 | |
| 1076 | This driver can also be built as a module. If so, the module |
| 1077 | will be called rtc-ls1x. |
| 1078 | |
Fabio Estevam | 7981159 | 2012-05-29 15:07:37 -0700 | [diff] [blame] | 1079 | config RTC_DRV_MXC |
Fabio Estevam | b224b9a | 2012-05-29 15:07:37 -0700 | [diff] [blame] | 1080 | tristate "Freescale MXC Real Time Clock" |
| 1081 | depends on ARCH_MXC |
| 1082 | depends on RTC_CLASS |
| 1083 | help |
| 1084 | If you say yes here you get support for the Freescale MXC |
| 1085 | RTC module. |
| 1086 | |
| 1087 | This driver can also be built as a module, if so, the module |
| 1088 | will be called "rtc-mxc". |
| 1089 | |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 1090 | endif # RTC_CLASS |