blob: 987c50168fd8e1be3db9d91dc42401abfc01bd6b [file] [log] [blame]
David Brownell7be2c7c2007-02-10 01:46:02 -08001#
Alessandro Zummoc58411e2006-03-27 01:16:34 -08002# RTC class/drivers configuration
3#
4
5config RTC_LIB
John Stultzb4d246b2011-04-29 15:03:11 -07006 bool
Alessandro Zummo0c86edc2006-03-27 01:16:37 -08007
Jan Engelhardtbb35fb22007-07-31 00:39:46 -07008menuconfig RTC_CLASS
John Stultzb4d246b2011-04-29 15:03:11 -07009 bool "Real Time Clock"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080010 default n
Al Viro33694652011-08-18 20:11:59 +010011 depends on !S390 && !UML
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080012 select RTC_LIB
13 help
14 Generic RTC class support. If you say yes here, you will
Alexandre Belloni98ab2c92015-05-09 21:21:54 +020015 be allowed to plug one or more RTCs to your system. You will
Adrian Bunk27ae4102006-06-30 18:18:41 +020016 probably want to enable one or more of the interfaces below.
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080017
Jan Engelhardtbb35fb22007-07-31 00:39:46 -070018if RTC_CLASS
19
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080020config RTC_HCTOSYS
David Brownell7ca1d482007-05-08 00:33:42 -070021 bool "Set system time from RTC on startup and resume"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080022 default y
23 help
David Brownell7ca1d482007-05-08 00:33:42 -070024 If you say yes here, the system time (wall clock) will be set using
25 the value read from a specified RTC device. This is useful to avoid
26 unnecessary fsck runs at boot time, and to network better.
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080027
28config RTC_HCTOSYS_DEVICE
David Brownell7ca1d482007-05-08 00:33:42 -070029 string "RTC used to set the system time"
Xunlei Pang9c5150b2015-06-12 11:10:16 +080030 depends on RTC_HCTOSYS
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080031 default "rtc0"
32 help
David Brownell7ca1d482007-05-08 00:33:42 -070033 The RTC device that will be used to (re)initialize the system
Alessandro Zummoae64d162009-01-06 14:42:17 -080034 clock, usually rtc0. Initialization is done when the system
35 starts up, and when it resumes from a low power state. This
David Brownell779d2082007-11-14 16:58:29 -080036 device should record time in UTC, since the kernel won't do
37 timezone correction.
David Brownell7ca1d482007-05-08 00:33:42 -070038
David Brownell55ff1ab2007-07-21 04:37:56 -070039 The driver for this RTC device must be loaded before late_initcall
40 functions run, so it must usually be statically linked.
41
David Brownell7ca1d482007-05-08 00:33:42 -070042 This clock should be battery-backed, so that it reads the correct
Alessandro Zummoae64d162009-01-06 14:42:17 -080043 time when the system boots from a power-off state. Otherwise, your
David Brownell7ca1d482007-05-08 00:33:42 -070044 system will need an external clock source (like an NTP server).
45
46 If the clock you specify here is not battery backed, it may still
47 be useful to reinitialize system time when resuming from system
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -080048 sleep states. Do not specify an RTC here unless it stays powered
David Brownell7ca1d482007-05-08 00:33:42 -070049 during all this system's supported sleep states.
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080050
Xunlei Pang9c5150b2015-06-12 11:10:16 +080051config RTC_SYSTOHC
52 bool "Set the RTC time based on NTP synchronization"
53 default y
54 help
55 If you say yes here, the system time (wall clock) will be stored
56 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
57 minutes if userspace reports synchronized NTP status.
58
59config RTC_SYSTOHC_DEVICE
60 string "RTC used to synchronize NTP adjustment"
61 depends on RTC_SYSTOHC
62 default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS
63 default "rtc0"
64 help
65 The RTC device used for NTP synchronization. The main difference
66 between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this
67 one can sleep when setting time, because it runs in the workqueue
68 context.
69
David Brownell9e86ecb2006-09-30 23:28:14 -070070config RTC_DEBUG
71 bool "RTC debug support"
David Brownell9e86ecb2006-09-30 23:28:14 -070072 help
73 Say yes here to enable debugging support in the RTC framework
74 and individual RTC drivers.
75
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080076comment "RTC interfaces"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -080077
Alessandro Zummoc5c3e192006-03-27 01:16:39 -080078config RTC_INTF_SYSFS
Christoph Jaeger6341e622014-12-20 15:41:11 -050079 bool "/sys/class/rtc/rtcN (sysfs)"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -070080 depends on SYSFS
Kevin Hilman8dc08392012-10-10 15:54:06 -070081 default RTC_CLASS
Alessandro Zummoc5c3e192006-03-27 01:16:39 -080082 help
David Brownell9e86ecb2006-09-30 23:28:14 -070083 Say yes here if you want to use your RTCs using sysfs interfaces,
84 /sys/class/rtc/rtc0 through /sys/.../rtcN.
Alessandro Zummoc5c3e192006-03-27 01:16:39 -080085
Alessandro Zummoae64d162009-01-06 14:42:17 -080086 If unsure, say Y.
Alessandro Zummoc5c3e192006-03-27 01:16:39 -080087
Alessandro Zummo728a2942006-03-27 01:16:40 -080088config RTC_INTF_PROC
Christoph Jaeger6341e622014-12-20 15:41:11 -050089 bool "/proc/driver/rtc (procfs for rtcN)"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -070090 depends on PROC_FS
Kevin Hilman8dc08392012-10-10 15:54:06 -070091 default RTC_CLASS
Alessandro Zummo728a2942006-03-27 01:16:40 -080092 help
Kim, Milo92589c92012-10-04 17:13:45 -070093 Say yes here if you want to use your system clock RTC through
94 the proc interface, /proc/driver/rtc.
95 Other RTCs will not be available through that API.
96 If there is no RTC for the system clock, then the first RTC(rtc0)
97 is used by default.
Alessandro Zummo728a2942006-03-27 01:16:40 -080098
Alessandro Zummoae64d162009-01-06 14:42:17 -080099 If unsure, say Y.
Alessandro Zummo728a2942006-03-27 01:16:40 -0800100
Alessandro Zummoe8242902006-03-27 01:16:41 -0800101config RTC_INTF_DEV
Christoph Jaeger6341e622014-12-20 15:41:11 -0500102 bool "/dev/rtcN (character devices)"
Kevin Hilman8dc08392012-10-10 15:54:06 -0700103 default RTC_CLASS
Alessandro Zummoe8242902006-03-27 01:16:41 -0800104 help
David Brownell9e86ecb2006-09-30 23:28:14 -0700105 Say yes here if you want to use your RTCs using the /dev
106 interfaces, which "udev" sets up as /dev/rtc0 through
Alessandro Zummoae64d162009-01-06 14:42:17 -0800107 /dev/rtcN.
Alessandro Zummoe8242902006-03-27 01:16:41 -0800108
Alessandro Zummoae64d162009-01-06 14:42:17 -0800109 You may want to set up a symbolic link so one of these
110 can be accessed as /dev/rtc, which is a name
111 expected by "hwclock" and some other programs. Recent
112 versions of "udev" are known to set up the symlink for you.
113
114 If unsure, say Y.
Alessandro Zummoe8242902006-03-27 01:16:41 -0800115
John Stultz6e57b1d2011-02-11 17:45:40 -0800116config RTC_INTF_DEV_UIE_EMUL
117 bool "RTC UIE emulation on dev interface"
118 depends on RTC_INTF_DEV
119 help
120 Provides an emulation for RTC_UIE if the underlying rtc chip
121 driver does not expose RTC_UIE ioctls. Those requests generate
122 once-per-second update interrupts, used for synchronization.
123
124 The emulation code will read the time from the hardware
125 clock several times per second, please enable this option
126 only if you know that you really need it.
127
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700128config RTC_DRV_TEST
129 tristate "Test driver/device"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700130 help
131 If you say yes here you get support for the
132 RTC test driver. It's a software RTC which can be
133 used to test the RTC subsystem APIs. It gets
134 the time from the system clock.
135 You want this driver only if you are doing development
136 on the RTC subsystem. Please read the source code
137 for further details.
138
139 This driver can also be built as a module. If so, the module
140 will be called rtc-test.
141
142comment "I2C RTC drivers"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700143
144if I2C
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700145
Haojian Zhuang008b3042011-05-06 17:21:20 +0800146config RTC_DRV_88PM860X
147 tristate "Marvell 88PM860x"
Alexandre Belloni37830552015-06-08 19:27:37 +0200148 depends on MFD_88PM860X
Haojian Zhuang008b3042011-05-06 17:21:20 +0800149 help
150 If you say yes here you get support for RTC function in Marvell
151 88PM860x chips.
152
153 This driver can also be built as a module. If so, the module
154 will be called rtc-88pm860x.
155
Qiao Zhou2985c292012-07-09 14:37:34 +0800156config RTC_DRV_88PM80X
157 tristate "Marvell 88PM80x"
Alexandre Belloni37830552015-06-08 19:27:37 +0200158 depends on MFD_88PM800
Qiao Zhou2985c292012-07-09 14:37:34 +0800159 help
160 If you say yes here you get support for RTC function in Marvell
161 88PM80x chips.
162
163 This driver can also be built as a module. If so, the module
164 will be called rtc-88pm80x.
165
Arnaud Ebalard0b2f6222015-02-13 14:41:00 -0800166config RTC_DRV_ABB5ZES3
Alexandre Belloni98ab2c92015-05-09 21:21:54 +0200167 select REGMAP_I2C
168 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
169 help
Arnaud Ebalard0b2f6222015-02-13 14:41:00 -0800170 If you say yes here you get support for the Abracon
171 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
172
173 This driver can also be built as a module. If so, the module
174 will be called rtc-ab-b5ze-s3.
175
Philippe De Muyter4d61ff62015-05-05 16:23:44 -0700176config RTC_DRV_ABX80X
177 tristate "Abracon ABx80x"
178 help
179 If you say yes here you get support for Abracon AB080X and AB180X
180 families of ultra-low-power battery- and capacitor-backed real-time
181 clock chips.
182
183 This driver can also be built as a module. If so, the module
184 will be called rtc-abx80x.
185
Laxman Dewanganb4506262013-11-12 15:11:05 -0800186config RTC_DRV_AS3722
187 tristate "ams AS3722 RTC driver"
188 depends on MFD_AS3722
189 help
190 If you say yes here you get support for the RTC of ams AS3722 PMIC
191 chips.
192
193 This driver can also be built as a module. If so, the module
194 will be called rtc-as3722.
195
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700196config RTC_DRV_DS1307
Matthias Fuchsa2166852009-03-31 15:24:58 -0700197 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700198 help
199 If you say yes here you get support for various compatible RTC
Alessandro Zummoae64d162009-01-06 14:42:17 -0800200 chips (often with battery backup) connected with I2C. This driver
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700201 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
Matthias Fuchsa2166852009-03-31 15:24:58 -0700202 EPSON RX-8025 and probably other chips. In some cases the RTC
203 must already have been initialized (by manufacturing or a
204 bootloader).
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700205
206 The first seven registers on these chips hold an RTC, and other
207 registers may add features such as NVRAM, a trickle charger for
Alessandro Zummoae64d162009-01-06 14:42:17 -0800208 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
David Brownell682d73f2007-11-14 16:58:32 -0800209 sysfs, but other chip features may not be available.
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700210
211 This driver can also be built as a module. If so, the module
212 will be called rtc-ds1307.
213
Akinobu Mita445c0202016-01-25 00:22:16 +0900214config RTC_DRV_DS1307_HWMON
215 bool "HWMON support for rtc-ds1307"
216 depends on RTC_DRV_DS1307 && HWMON
217 depends on !(RTC_DRV_DS1307=y && HWMON=m)
218 default y
219 help
220 Say Y here if you want to expose temperature sensor data on
221 rtc-ds1307 (only DS3231)
222
Scott Woodbf4994d2007-10-16 01:28:19 -0700223config RTC_DRV_DS1374
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800224 tristate "Dallas/Maxim DS1374"
Scott Woodbf4994d2007-10-16 01:28:19 -0700225 help
226 If you say yes here you get support for Dallas Semiconductor
Alessandro Zummoae64d162009-01-06 14:42:17 -0800227 DS1374 real-time clock chips. If an interrupt is associated
Scott Woodbf4994d2007-10-16 01:28:19 -0700228 with the device, the alarm functionality is supported.
229
Alessandro Zummoae64d162009-01-06 14:42:17 -0800230 This driver can also be built as a module. If so, the module
Scott Woodbf4994d2007-10-16 01:28:19 -0700231 will be called rtc-ds1374.
232
Søren Andersen920f91e2014-12-10 15:53:54 -0800233config RTC_DRV_DS1374_WDT
234 bool "Dallas/Maxim DS1374 watchdog timer"
235 depends on RTC_DRV_DS1374
236 help
237 If you say Y here you will get support for the
238 watchdog timer in the Dallas Semiconductor DS1374
239 real-time clock chips.
240
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700241config RTC_DRV_DS1672
242 tristate "Dallas/Maxim DS1672"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700243 help
244 If you say yes here you get support for the
245 Dallas/Maxim DS1672 timekeeping chip.
246
247 This driver can also be built as a module. If so, the module
248 will be called rtc-ds1672.
249
Heiko Stuebnerdcaf0382014-01-23 15:55:10 -0800250config RTC_DRV_HYM8563
251 tristate "Haoyu Microelectronics HYM8563"
Alexandre Belloni37830552015-06-08 19:27:37 +0200252 depends on OF
Heiko Stuebnerdcaf0382014-01-23 15:55:10 -0800253 help
254 Say Y to enable support for the HYM8563 I2C RTC chip. Apart
255 from the usual rtc functions it provides a clock output of
256 up to 32kHz.
257
258 This driver can also be built as a module. If so, the module
259 will be called rtc-hym8563.
260
Kim, Milo38ae1762013-02-21 16:44:32 -0800261config RTC_DRV_LP8788
262 tristate "TI LP8788 RTC driver"
263 depends on MFD_LP8788
264 help
265 Say Y to enable support for the LP8788 RTC/ALARM driver.
266
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700267config RTC_DRV_MAX6900
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800268 tristate "Maxim MAX6900"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700269 help
270 If you say yes here you will get support for the
271 Maxim MAX6900 I2C RTC chip.
272
273 This driver can also be built as a module. If so, the module
274 will be called rtc-max6900.
275
Stephen Warren94c01ab2012-10-04 17:13:56 -0700276config RTC_DRV_MAX8907
277 tristate "Maxim MAX8907"
278 depends on MFD_MAX8907
279 help
280 If you say yes here you will get support for the
281 RTC of Maxim MAX8907 PMIC.
282
283 This driver can also be built as a module. If so, the module
284 will be called rtc-max8907.
285
Haojian Zhuanga39069f2010-01-25 06:30:29 -0500286config RTC_DRV_MAX8925
287 tristate "Maxim MAX8925"
288 depends on MFD_MAX8925
289 help
290 If you say yes here you will get support for the
291 RTC of Maxim MAX8925 PMIC.
292
293 This driver can also be built as a module. If so, the module
294 will be called rtc-max8925.
295
Joonyoung Shim9b16c0a2010-08-06 11:28:08 +0900296config RTC_DRV_MAX8998
297 tristate "Maxim MAX8998"
298 depends on MFD_MAX8998
299 help
300 If you say yes here you will get support for the
301 RTC of Maxim MAX8998 PMIC.
302
303 This driver can also be built as a module. If so, the module
304 will be called rtc-max8998.
305
Jonghwa Lee5e0b2702013-02-21 16:45:07 -0800306config RTC_DRV_MAX8997
307 tristate "Maxim MAX8997"
308 depends on MFD_MAX8997
309 help
310 If you say yes here you will get support for the
311 RTC of Maxim MAX8997 PMIC.
312
313 This driver can also be built as a module. If so, the module
314 will be called rtc-max8997.
315
Jonghwa Leefca1dd02013-02-21 16:44:26 -0800316config RTC_DRV_MAX77686
317 tristate "Maxim MAX77686"
Laxman Dewangan726fe732016-03-02 14:06:24 +0530318 depends on MFD_MAX77686 || MFD_MAX77620
Jonghwa Leefca1dd02013-02-21 16:44:26 -0800319 help
320 If you say yes here you will get support for the
Laxman Dewangan726fe732016-03-02 14:06:24 +0530321 RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
Jonghwa Leefca1dd02013-02-21 16:44:26 -0800322
323 This driver can also be built as a module. If so, the module
324 will be called rtc-max77686.
325
Chris Zhong3ca1e322014-10-13 15:52:42 -0700326config RTC_DRV_RK808
327 tristate "Rockchip RK808 RTC"
328 depends on MFD_RK808
329 help
330 If you say yes here you will get support for the
331 RTC of RK808 PMIC.
332
333 This driver can also be built as a module. If so, the module
334 will be called rk808-rtc.
335
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700336config RTC_DRV_RS5C372
Paul Mundt5d4529b2008-10-21 20:12:59 +0900337 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700338 help
339 If you say yes here you get support for the
Paul Mundt5d4529b2008-10-21 20:12:59 +0900340 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700341
342 This driver can also be built as a module. If so, the module
343 will be called rtc-rs5c372.
344
345config RTC_DRV_ISL1208
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800346 tristate "Intersil ISL1208"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700347 help
348 If you say yes here you get support for the
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800349 Intersil ISL1208 RTC chip.
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700350
351 This driver can also be built as a module. If so, the module
352 will be called rtc-isl1208.
353
Roman Fietzed6c74282010-08-10 18:02:14 -0700354config RTC_DRV_ISL12022
355 tristate "Intersil ISL12022"
356 help
357 If you say yes here you get support for the
358 Intersil ISL12022 RTC chip.
359
360 This driver can also be built as a module. If so, the module
361 will be called rtc-isl12022.
362
Arnaud Ebalard70e12332013-12-19 23:27:28 +0100363config RTC_DRV_ISL12057
Alexandre Belloni98ab2c92015-05-09 21:21:54 +0200364 select REGMAP_I2C
365 tristate "Intersil ISL12057"
366 help
Arnaud Ebalard70e12332013-12-19 23:27:28 +0100367 If you say yes here you get support for the Intersil ISL12057
368 I2C RTC chip.
369
370 This driver can also be built as a module. If so, the module
371 will be called rtc-isl12057.
372
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700373config RTC_DRV_X1205
374 tristate "Xicor/Intersil X1205"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700375 help
376 If you say yes here you get support for the
377 Xicor/Intersil X1205 RTC chip.
378
379 This driver can also be built as a module. If so, the module
380 will be called rtc-x1205.
381
Renaud Cerrato18cb6362013-07-03 15:08:01 -0700382config RTC_DRV_PCF2127
383 tristate "NXP PCF2127"
384 help
385 If you say yes here you get support for the NXP PCF2127/29 RTC
386 chips.
387
388 This driver can also be built as a module. If so, the module
389 will be called rtc-pcf2127.
390
Thierry Redingf803f0d2012-12-17 16:02:44 -0800391config RTC_DRV_PCF8523
392 tristate "NXP PCF8523"
393 help
394 If you say yes here you get support for the NXP PCF8523 RTC
395 chips.
396
397 This driver can also be built as a module. If so, the module
398 will be called rtc-pcf8523.
399
Soren Brinkmannd0848852015-11-03 23:13:46 -0800400config RTC_DRV_PCF85063
401 tristate "NXP PCF85063"
402 help
403 If you say yes here you get support for the PCF85063 RTC chip
404
405 This driver can also be built as a module. If so, the module
406 will be called rtc-pcf85063.
407
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700408config RTC_DRV_PCF8563
409 tristate "Philips PCF8563/Epson RTC8564"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700410 help
411 If you say yes here you get support for the
412 Philips PCF8563 RTC chip. The Epson RTC8564
413 should work as well.
414
415 This driver can also be built as a module. If so, the module
416 will be called rtc-pcf8563.
417
418config RTC_DRV_PCF8583
419 tristate "Philips PCF8583"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700420 help
421 If you say yes here you get support for the Philips PCF8583
422 RTC chip found on Acorn RiscPCs. This driver supports the
423 platform specific method of retrieving the current year from
424 the RTC's SRAM. It will work on other platforms with the same
425 chip, but the year will probably have to be tweaked.
426
427 This driver can also be built as a module. If so, the module
428 will be called rtc-pcf8583.
429
Atsushi Nemotocaaff562007-07-17 04:05:02 -0700430config RTC_DRV_M41T80
Wolfram Sang6b1a5232014-06-06 14:35:47 -0700431 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
Atsushi Nemotocaaff562007-07-17 04:05:02 -0700432 help
Steven A. Falcod3a126f2008-10-15 22:03:07 -0700433 If you say Y here you will get support for the ST M41T60
434 and M41T80 RTC chips series. Currently, the following chips are
Daniel Glocknerf30281f2009-04-02 16:57:03 -0700435 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
Wolfram Sang6b1a5232014-06-06 14:35:47 -0700436 M41ST85, M41ST87, and MicroCrystal RV4162.
Atsushi Nemotocaaff562007-07-17 04:05:02 -0700437
438 This driver can also be built as a module. If so, the module
439 will be called rtc-m41t80.
440
Atsushi Nemoto617780d2007-07-17 04:05:04 -0700441config RTC_DRV_M41T80_WDT
Steven A. Falcod3a126f2008-10-15 22:03:07 -0700442 bool "ST M41T65/M41T80 series RTC watchdog timer"
Atsushi Nemoto617780d2007-07-17 04:05:04 -0700443 depends on RTC_DRV_M41T80
444 help
445 If you say Y here you will get support for the
Steven A. Falcod3a126f2008-10-15 22:03:07 -0700446 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
Atsushi Nemoto617780d2007-07-17 04:05:04 -0700447
Piotr Ziecik1ce7c832009-12-15 16:46:12 -0800448config RTC_DRV_BQ32K
449 tristate "TI BQ32000"
450 help
451 If you say Y here you will get support for the TI
452 BQ32000 I2C RTC chip.
453
454 This driver can also be built as a module. If so, the module
455 will be called rtc-bq32k.
456
David Brownellafd8d0f2009-02-04 15:12:01 -0800457config RTC_DRV_DM355EVM
458 tristate "TI DaVinci DM355 EVM RTC"
459 depends on MFD_DM355EVM_MSP
460 help
461 Supports the RTC firmware in the MSP430 on the DM355 EVM.
462
Tony Lindgren0c4a59f2007-07-17 04:06:09 -0700463config RTC_DRV_TWL92330
Christoph Jaeger6341e622014-12-20 15:41:11 -0500464 bool "TI TWL92330/Menelaus"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700465 depends on MENELAUS
Tony Lindgren0c4a59f2007-07-17 04:06:09 -0700466 help
467 If you say yes here you get support for the RTC on the
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200468 TWL92330 "Menelaus" power management chip, used with OMAP2
Alessandro Zummoae64d162009-01-06 14:42:17 -0800469 platforms. The support is integrated with the rest of
Tony Lindgren0c4a59f2007-07-17 04:06:09 -0700470 the Menelaus driver; it's not separate module.
471
David Brownellf96411a2008-10-20 23:50:05 +0200472config RTC_DRV_TWL4030
Balaji T Ka6b49ff2009-12-13 22:16:31 +0100473 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
Venu Byravarasu6b8029f2012-10-04 17:13:59 -0700474 depends on TWL4030_CORE
David Brownellf96411a2008-10-20 23:50:05 +0200475 help
476 If you say yes here you get support for the RTC on the
Balaji T Ka6b49ff2009-12-13 22:16:31 +0100477 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
David Brownellf96411a2008-10-20 23:50:05 +0200478
479 This driver can also be built as a module. If so, the module
Balaji T Ka6b49ff2009-12-13 22:16:31 +0100480 will be called rtc-twl.
David Brownellf96411a2008-10-20 23:50:05 +0200481
Soren Brinkmannd0848852015-11-03 23:13:46 -0800482config RTC_DRV_PALMAS
483 tristate "TI Palmas RTC driver"
484 depends on MFD_PALMAS
485 help
486 If you say yes here you get support for the RTC of TI PALMA series PMIC
487 chips.
488
489 This driver can also be built as a module. If so, the module
490 will be called rtc-palma.
491
Laxman Dewangandc59ed32013-01-04 15:35:44 -0800492config RTC_DRV_TPS6586X
493 tristate "TI TPS6586X RTC driver"
494 depends on MFD_TPS6586X
495 help
Masanari Iidaa895d572013-04-09 02:06:50 +0900496 TI Power Management IC TPS6586X supports RTC functionality
Laxman Dewangandc59ed32013-01-04 15:35:44 -0800497 along with alarm. This driver supports the RTC driver for
498 the TPS6586X RTC module.
499
Venu Byravarasu0e783982012-10-04 17:13:55 -0700500config RTC_DRV_TPS65910
501 tristate "TI TPS65910 RTC driver"
502 depends on RTC_CLASS && MFD_TPS65910
503 help
504 If you say yes here you get support for the RTC on the
505 TPS65910 chips.
506
507 This driver can also be built as a module. If so, the module
508 will be called rtc-tps65910.
509
Laxman Dewangan36d61822013-02-21 16:44:34 -0800510config RTC_DRV_TPS80031
511 tristate "TI TPS80031/TPS80032 RTC driver"
512 depends on MFD_TPS80031
513 help
Masanari Iidaa895d572013-04-09 02:06:50 +0900514 TI Power Management IC TPS80031 supports RTC functionality
Laxman Dewangan36d61822013-02-21 16:44:34 -0800515 along with alarm. This driver supports the RTC driver for
516 the TPS80031 RTC module.
517
Venu Byravarasu90829c02012-10-04 17:14:04 -0700518config RTC_DRV_RC5T583
519 tristate "RICOH 5T583 RTC driver"
520 depends on MFD_RC5T583
521 help
522 If you say yes here you get support for the RTC on the
523 RICOH 5T583 chips.
524
525 This driver can also be built as a module. If so, the module
526 will be called rtc-rc5t583.
527
Byron Bradleyc46288b2008-03-04 14:28:25 -0800528config RTC_DRV_S35390A
529 tristate "Seiko Instruments S-35390A"
Randy Dunlapd4795402008-04-10 21:29:18 -0700530 select BITREVERSE
Byron Bradleyc46288b2008-03-04 14:28:25 -0800531 help
532 If you say yes here you will get support for the Seiko
533 Instruments S-35390A.
534
535 This driver can also be built as a module. If so the module
536 will be called rtc-s35390a.
537
Sergey Lapinc6d8f402008-06-12 15:21:55 -0700538config RTC_DRV_FM3130
539 tristate "Ramtron FM3130"
540 help
541 If you say Y here you will get support for the
542 Ramtron FM3130 RTC chips.
543 Ramtron FM3130 is a chip with two separate devices inside,
544 RTC clock and FRAM. This driver provides only RTC functionality.
545
546 This driver can also be built as a module. If so the module
547 will be called rtc-fm3130.
548
Akshay Bhated13d892015-12-03 14:41:21 -0500549config RTC_DRV_RX8010
550 tristate "Epson RX8010SJ"
551 depends on I2C
552 help
553 If you say yes here you get support for the Epson RX8010SJ RTC
554 chip.
555
556 This driver can also be built as a module. If so, the module
557 will be called rtc-rx8010.
558
Martyn Welcha7fa9852008-11-12 13:27:06 -0800559config RTC_DRV_RX8581
560 tristate "Epson RX-8581"
561 help
562 If you say yes here you will get support for the Epson RX-8581.
563
564 This driver can also be built as a module. If so the module
565 will be called rtc-rx8581.
566
Wolfgang Grandegger3c2b9072009-06-17 16:26:11 -0700567config RTC_DRV_RX8025
568 tristate "Epson RX-8025SA/NB"
569 help
570 If you say yes here you get support for the Epson
571 RX-8025SA/NB RTC chips.
572
573 This driver can also be built as a module. If so, the module
574 will be called rtc-rx8025.
575
Mike Rapoportae3551f2011-05-26 16:25:04 -0700576config RTC_DRV_EM3027
577 tristate "EM Microelectronic EM3027"
578 help
579 If you say yes here you get support for the EM
580 Microelectronic EM3027 RTC chips.
581
582 This driver can also be built as a module. If so, the module
583 will be called rtc-em3027.
584
Heiko Schocher52365232011-05-26 16:25:05 -0700585config RTC_DRV_RV3029C2
Alexandre Bellonid2c6b872016-02-29 00:47:49 +0100586 tristate "Micro Crystal RV3029"
Heiko Schocher52365232011-05-26 16:25:05 -0700587 help
588 If you say yes here you get support for the Micro Crystal
Alexandre Bellonid2c6b872016-02-29 00:47:49 +0100589 RV3029 RTC chips.
Heiko Schocher52365232011-05-26 16:25:05 -0700590
591 This driver can also be built as a module. If so, the module
592 will be called rtc-rv3029c2.
593
Alexandre Belloni1e3929e2015-11-02 23:48:32 +0100594config RTC_DRV_RV8803
595 tristate "Micro Crystal RV8803"
596 help
597 If you say yes here you get support for the Micro Crystal
598 RV8803 RTC chips.
599
600 This driver can also be built as a module. If so, the module
601 will be called rtc-rv8803.
602
Sangbeom Kim5bccae62013-11-12 15:11:04 -0800603config RTC_DRV_S5M
Krzysztof Kozlowski0c5deb12014-06-10 15:18:46 -0700604 tristate "Samsung S2M/S5M series"
Sangbeom Kim5bccae62013-11-12 15:11:04 -0800605 depends on MFD_SEC_CORE
606 help
607 If you say yes here you will get support for the
Krzysztof Kozlowski0c5deb12014-06-10 15:18:46 -0700608 RTC of Samsung S2MPS14 and S5M PMIC series.
Sangbeom Kim5bccae62013-11-12 15:11:04 -0800609
610 This driver can also be built as a module. If so, the module
611 will be called rtc-s5m.
612
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700613endif # I2C
614
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700615comment "SPI RTC drivers"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700616
617if SPI_MASTER
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700618
Voss, Nikolaus74d34d42011-05-26 16:25:07 -0700619config RTC_DRV_M41T93
Alexandre Belloni98ab2c92015-05-09 21:21:54 +0200620 tristate "ST M41T93"
621 help
622 If you say yes here you will get support for the
623 ST M41T93 SPI RTC chip.
Voss, Nikolaus74d34d42011-05-26 16:25:07 -0700624
Alexandre Belloni98ab2c92015-05-09 21:21:54 +0200625 This driver can also be built as a module. If so, the module
626 will be called rtc-m41t93.
Voss, Nikolaus74d34d42011-05-26 16:25:07 -0700627
Kim B. Heino8fc2c762008-07-23 21:30:34 -0700628config RTC_DRV_M41T94
629 tristate "ST M41T94"
630 help
631 If you say yes here you will get support for the
632 ST M41T94 SPI RTC chip.
633
634 This driver can also be built as a module. If so, the module
635 will be called rtc-m41t94.
636
David Brownell53e84b62008-07-23 21:30:36 -0700637config RTC_DRV_DS1305
638 tristate "Dallas/Maxim DS1305/DS1306"
639 help
640 Select this driver to get support for the Dallas/Maxim DS1305
Alessandro Zummoae64d162009-01-06 14:42:17 -0800641 and DS1306 real time clock chips. These support a trickle
David Brownell53e84b62008-07-23 21:30:36 -0700642 charger, alarms, and NVRAM in addition to the clock.
643
644 This driver can also be built as a module. If so, the module
645 will be called rtc-ds1305.
646
Raghavendra Ganiga1d6316f2014-06-06 14:35:59 -0700647config RTC_DRV_DS1343
Raghavendra Ganiga0dd449b2014-06-06 14:36:00 -0700648 select REGMAP_SPI
Raghavendra Ganiga1d6316f2014-06-06 14:35:59 -0700649 tristate "Dallas/Maxim DS1343/DS1344"
650 help
651 If you say yes here you get support for the
652 Dallas/Maxim DS1343 and DS1344 real time clock chips.
653 Support for trickle charger, alarm is provided.
654
655 This driver can also be built as a module. If so, the module
656 will be called rtc-ds1343.
657
Raghavendra Ganiga617b26a2014-04-03 14:50:16 -0700658config RTC_DRV_DS1347
659 tristate "Dallas/Maxim DS1347"
660 help
661 If you say yes here you get support for the
662 Dallas/Maxim DS1347 chips.
663
664 This driver only supports the RTC feature, and not other chip
665 features such as alarms.
666
667 This driver can also be built as a module. If so, the module
668 will be called rtc-ds1347.
669
Mark Jackson06de1802008-11-12 13:27:07 -0800670config RTC_DRV_DS1390
671 tristate "Dallas/Maxim DS1390/93/94"
672 help
Alessandro Zummo7b9b2ef2009-01-06 14:42:16 -0800673 If you say yes here you get support for the
674 Dallas/Maxim DS1390/93/94 chips.
Mark Jackson06de1802008-11-12 13:27:07 -0800675
Ivan Grimaldifa395fb2015-09-18 17:27:57 +0200676 This driver supports the RTC feature and trickle charging but not
677 other chip features such as alarms.
Mark Jackson06de1802008-11-12 13:27:07 -0800678
679 This driver can also be built as a module. If so, the module
680 will be called rtc-ds1390.
681
Magnus Damm2805b962008-02-06 01:38:53 -0800682config RTC_DRV_R9701
683 tristate "Epson RTC-9701JE"
684 help
685 If you say yes here you will get support for the
686 Epson RTC-9701JE SPI RTC chip.
687
688 This driver can also be built as a module. If so, the module
689 will be called rtc-r9701.
690
Soren Brinkmannd0848852015-11-03 23:13:46 -0800691config RTC_DRV_RX4581
692 tristate "Epson RX-4581"
693 help
694 If you say yes here you will get support for the Epson RX-4581.
695
696 This driver can also be built as a module. If so the module
697 will be called rtc-rx4581.
698
699config RTC_DRV_RX6110
700 tristate "Epson RX-6110"
701 select REGMAP_SPI
702 help
703 If you say yes here you will get support for the Epson RX-6610.
704
705 This driver can also be built as a module. If so the module
706 will be called rtc-rx6110.
707
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700708config RTC_DRV_RS5C348
709 tristate "Ricoh RS5C348A/B"
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700710 help
711 If you say yes here you get support for the
712 Ricoh RS5C348A and RS5C348B RTC chips.
713
714 This driver can also be built as a module. If so, the module
715 will be called rtc-rs5c348.
716
Soren Brinkmannd0848852015-11-03 23:13:46 -0800717config RTC_DRV_MAX6902
718 tristate "Maxim MAX6902"
719 help
720 If you say yes here you will get support for the
721 Maxim MAX6902 SPI RTC chip.
722
723 This driver can also be built as a module. If so, the module
724 will be called rtc-max6902.
725
Chris Verges7f3923a2009-09-22 16:46:20 -0700726config RTC_DRV_PCF2123
727 tristate "NXP PCF2123"
728 help
729 If you say yes here you get support for the NXP PCF2123
730 RTC chip.
731
732 This driver can also be built as a module. If so, the module
733 will be called rtc-pcf2123.
734
Josef Gajdusek1fcbe422014-06-06 14:36:02 -0700735config RTC_DRV_MCP795
736 tristate "Microchip MCP795"
737 help
738 If you say yes here you will get support for the Microchip MCP795.
739
740 This driver can also be built as a module. If so the module
741 will be called rtc-mcp795.
742
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700743endif # SPI_MASTER
744
Akinobu Mita080481f52016-03-07 00:27:48 +0900745#
746# Helper to resolve issues with configs that have SPI enabled but I2C
747# modular. See SND_SOC_I2C_AND_SPI for more information
748#
749config RTC_I2C_AND_SPI
750 tristate
751 default m if I2C=m
752 default y if I2C=y
753 default y if SPI_MASTER=y
754 select REGMAP_I2C if I2C
755 select REGMAP_SPI if SPI_MASTER
756
757comment "SPI and I2C RTC drivers"
758
759config RTC_DRV_DS3232
760 tristate "Dallas/Maxim DS3232/DS3234"
761 depends on RTC_I2C_AND_SPI
762 help
763 If you say yes here you get support for Dallas Semiconductor
764 DS3232 and DS3234 real-time clock chips. If an interrupt is associated
765 with the device, the alarm functionality is supported.
766
767 This driver can also be built as a module. If so, the module
768 will be called rtc-ds3232.
769
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700770comment "Platform RTC drivers"
Alessandro Zummo0c86edc2006-03-27 01:16:37 -0800771
David Brownell7be2c7c2007-02-10 01:46:02 -0800772# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
773# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
774# global rtc_lock ... it's not yet just another platform_device.
775
776config RTC_DRV_CMOS
Alessandro Zummo09a21e52007-05-08 00:33:48 -0700777 tristate "PC-style 'CMOS'"
Geert Uytterhoeven41c9dbf2014-01-23 15:55:12 -0800778 depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
David Brownellc7500902008-04-28 02:11:52 -0700779 default y if X86
David Brownell7be2c7c2007-02-10 01:46:02 -0800780 help
781 Say "yes" here to get direct support for the real time clock
782 found in every PC or ACPI-based system, and some other boards.
783 Specifically the original MC146818, compatibles like those in
784 PC south bridges, the DS12887 or M48T86, some multifunction
785 or LPC bus chips, and so on.
786
787 Your system will need to define the platform device used by
Alessandro Zummoae64d162009-01-06 14:42:17 -0800788 this driver, otherwise it won't be accessible. This means
David Brownell7be2c7c2007-02-10 01:46:02 -0800789 you can safely enable this driver if you don't know whether
790 or not your board has this kind of hardware.
791
792 This driver can also be built as a module. If so, the module
793 will be called rtc-cmos.
794
Richard Henderson85d0b3a2013-07-13 15:49:45 -0700795config RTC_DRV_ALPHA
796 bool "Alpha PC-style CMOS"
797 depends on ALPHA
798 default y
799 help
800 Direct support for the real-time clock found on every Alpha
801 system, specifically MC146818 compatibles. If in doubt, say Y.
802
Feng Tang0146f262010-11-10 17:29:17 +0000803config RTC_DRV_VRTC
Alan Cox933b9462011-12-17 17:43:40 +0000804 tristate "Virtual RTC for Intel MID platforms"
805 depends on X86_INTEL_MID
806 default y if X86_INTEL_MID
Feng Tang0146f262010-11-10 17:29:17 +0000807
808 help
809 Say "yes" here to get direct support for the real time clock
810 found on Moorestown platforms. The VRTC is a emulated RTC that
811 derives its clock source from a real RTC in the PMIC. The MC146818
812 style programming interface is mostly conserved, but any
813 updates are done via IPC calls to the system controller FW.
814
Thomas Bogendoerfer537739d2007-07-17 04:05:06 -0700815config RTC_DRV_DS1216
816 tristate "Dallas DS1216"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -0700817 depends on SNI_RM
Thomas Bogendoerfer537739d2007-07-17 04:05:06 -0700818 help
819 If you say yes here you get support for the Dallas DS1216 RTC chips.
820
Thomas Bogendoerfer5f119f22008-10-14 17:16:59 +0200821config RTC_DRV_DS1286
822 tristate "Dallas DS1286"
Chen Gang706b6322014-10-13 15:53:14 -0700823 depends on HAS_IOMEM
Thomas Bogendoerfer5f119f22008-10-14 17:16:59 +0200824 help
825 If you say yes here you get support for the Dallas DS1286 RTC chips.
826
Paul Mundt739d3402008-02-06 01:38:44 -0800827config RTC_DRV_DS1302
828 tristate "Dallas DS1302"
829 depends on SH_SECUREEDGE5410
830 help
831 If you say yes here you get support for the Dallas DS1302 RTC chips.
832
Andrew Sharp8f267952008-02-06 01:38:46 -0800833config RTC_DRV_DS1511
834 tristate "Dallas DS1511"
Chen Gang706b6322014-10-13 15:53:14 -0700835 depends on HAS_IOMEM
Andrew Sharp8f267952008-02-06 01:38:46 -0800836 help
837 If you say yes here you get support for the
838 Dallas DS1511 timekeeping/watchdog chip.
839
840 This driver can also be built as a module. If so, the module
841 will be called rtc-ds1511.
842
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700843config RTC_DRV_DS1553
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800844 tristate "Maxim/Dallas DS1553"
Chen Gang706b6322014-10-13 15:53:14 -0700845 depends on HAS_IOMEM
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700846 help
847 If you say yes here you get support for the
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800848 Maxim/Dallas DS1553 timekeeping chip.
Atsushi Nemoto9bf5b4f2006-06-25 05:48:28 -0700849
850 This driver can also be built as a module. If so, the module
851 will be called rtc-ds1553.
852
Joshua Kinardaaaf5fb2015-02-16 16:00:26 -0800853config RTC_DRV_DS1685_FAMILY
854 tristate "Dallas/Maxim DS1685 Family"
855 help
856 If you say yes here you get support for the Dallas/Maxim DS1685
857 family of real time chips. This family includes the DS1685/DS1687,
858 DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
859 DS17885/DS17887 chips.
860
861 This driver can also be built as a module. If so, the module
862 will be called rtc-ds1685.
863
864choice
865 prompt "Subtype"
866 depends on RTC_DRV_DS1685_FAMILY
867 default RTC_DRV_DS1685
868
869config RTC_DRV_DS1685
870 bool "DS1685/DS1687"
871 help
872 This enables support for the Dallas/Maxim DS1685/DS1687 real time
873 clock chip.
874
875 This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
876 systems, as well as EPPC-405-UC modules by electronic system design
877 GmbH.
878
879config RTC_DRV_DS1689
880 bool "DS1689/DS1693"
881 help
882 This enables support for the Dallas/Maxim DS1689/DS1693 real time
883 clock chip.
884
885 This is an older RTC chip, supplanted by the DS1685/DS1687 above,
886 which supports a few minor features such as Vcc, Vbat, and Power
887 Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
888
889 It also works for the even older DS1688/DS1691 RTC chips, which are
890 virtually the same and carry the same model number. Both chips
891 have 114 bytes of user NVRAM.
892
893config RTC_DRV_DS17285
894 bool "DS17285/DS17287"
895 help
896 This enables support for the Dallas/Maxim DS17285/DS17287 real time
897 clock chip.
898
899 This chip features 2kb of extended NV-SRAM. It may possibly be
900 found in some SGI O2 systems (rare).
901
902config RTC_DRV_DS17485
903 bool "DS17485/DS17487"
904 help
905 This enables support for the Dallas/Maxim DS17485/DS17487 real time
906 clock chip.
907
908 This chip features 4kb of extended NV-SRAM.
909
910config RTC_DRV_DS17885
911 bool "DS17885/DS17887"
912 help
913 This enables support for the Dallas/Maxim DS17885/DS17887 real time
914 clock chip.
915
916 This chip features 8kb of extended NV-SRAM.
917
918endchoice
919
920config RTC_DS1685_PROC_REGS
921 bool "Display register values in /proc"
922 depends on RTC_DRV_DS1685_FAMILY && PROC_FS
923 help
924 Enable this to display a readout of all of the RTC registers in
925 /proc/drivers/rtc. Keep in mind that this can potentially lead
926 to lost interrupts, as reading Control Register C will clear
927 all pending IRQ flags.
928
929 Unless you are debugging this driver, choose N.
930
931config RTC_DS1685_SYSFS_REGS
932 bool "SysFS access to RTC register bits"
933 depends on RTC_DRV_DS1685_FAMILY && SYSFS
934 help
935 Enable this to provide access to the RTC control register bits
936 in /sys. Some of the bits are read-write, others are read-only.
937
938 Keep in mind that reading Control C's bits automatically clears
939 all pending IRQ flags - this can cause lost interrupts.
940
941 If you know that you need access to these bits, choose Y, Else N.
942
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800943config RTC_DRV_DS1742
944 tristate "Maxim/Dallas DS1742/1743"
Chen Gang706b6322014-10-13 15:53:14 -0700945 depends on HAS_IOMEM
Alessandro Zummo09b6bdb3b2008-02-06 01:38:40 -0800946 help
947 If you say yes here you get support for the
948 Maxim/Dallas DS1742/1743 timekeeping chip.
949
950 This driver can also be built as a module. If so, the module
951 will be called rtc-ds1742.
952
Jean Delvaread0200f2014-08-08 14:20:03 -0700953config RTC_DRV_DS2404
954 tristate "Maxim/Dallas DS2404"
955 help
956 If you say yes here you get support for the
957 Dallas DS2404 RTC chip.
958
959 This driver can also be built as a module. If so, the module
960 will be called rtc-ds2404.
961
Ashish Jangamfef931f2012-03-23 15:02:36 -0700962config RTC_DRV_DA9052
963 tristate "Dialog DA9052/DA9053 RTC"
964 depends on PMIC_DA9052
965 help
966 Say y here to support the RTC driver for Dialog Semiconductor
967 DA9052-BC and DA9053-AA/Bx PMICs.
968
Ashish Jangam6920d992012-12-17 16:02:53 -0800969config RTC_DRV_DA9055
970 tristate "Dialog Semiconductor DA9055 RTC"
971 depends on MFD_DA9055
972 help
973 If you say yes here you will get support for the
974 RTC of the Dialog DA9055 PMIC.
975
976 This driver can also be built as a module. If so, the module
977 will be called rtc-da9055
978
Opensource [Steve Twiss]c2a57552014-06-06 14:36:03 -0700979config RTC_DRV_DA9063
S Twiss80ca3272015-07-21 11:29:07 +0100980 tristate "Dialog Semiconductor DA9063/DA9062 RTC"
981 depends on MFD_DA9063 || MFD_DA9062
Opensource [Steve Twiss]c2a57552014-06-06 14:36:03 -0700982 help
983 If you say yes here you will get support for the RTC subsystem
S Twiss80ca3272015-07-21 11:29:07 +0100984 for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
Opensource [Steve Twiss]c2a57552014-06-06 14:36:03 -0700985
986 This driver can also be built as a module. If so, the module
987 will be called "rtc-da9063".
988
dann frazier5e3fd9e2009-03-31 15:24:48 -0700989config RTC_DRV_EFI
990 tristate "EFI RTC"
Matt Fleming7efe6652014-10-03 13:06:33 +0100991 depends on EFI && !X86
dann frazier5e3fd9e2009-03-31 15:24:48 -0700992 help
993 If you say yes here you will get support for the EFI
994 Real Time Clock.
995
996 This driver can also be built as a module. If so, the module
997 will be called rtc-efi.
998
Thomas Hommel02964112007-07-21 04:37:58 -0700999config RTC_DRV_STK17TA8
1000 tristate "Simtek STK17TA8"
Chen Gang706b6322014-10-13 15:53:14 -07001001 depends on HAS_IOMEM
Thomas Hommel02964112007-07-21 04:37:58 -07001002 help
1003 If you say yes here you get support for the
1004 Simtek STK17TA8 timekeeping chip.
1005
1006 This driver can also be built as a module. If so, the module
1007 will be called rtc-stk17ta8.
1008
Alessandro Zummo09a21e52007-05-08 00:33:48 -07001009config RTC_DRV_M48T86
1010 tristate "ST M48T86/Dallas DS12887"
Alessandro Zummo09a21e52007-05-08 00:33:48 -07001011 help
1012 If you say Y here you will get support for the
1013 ST M48T86 and Dallas DS12887 RTC chips.
1014
1015 This driver can also be built as a module. If so, the module
1016 will be called rtc-m48t86.
1017
Thomas Bogendoerferd1dbd82e2008-10-14 17:17:32 +02001018config RTC_DRV_M48T35
1019 tristate "ST M48T35"
Chen Gang706b6322014-10-13 15:53:14 -07001020 depends on HAS_IOMEM
Thomas Bogendoerferd1dbd82e2008-10-14 17:17:32 +02001021 help
1022 If you say Y here you will get support for the
1023 ST M48T35 RTC chip.
1024
1025 This driver can also be built as a module, if so, the module
1026 will be called "rtc-m48t35".
1027
Mark Zhan2e774c72007-07-17 04:05:05 -07001028config RTC_DRV_M48T59
Krzysztof Helt94fe7422008-09-03 15:12:34 -07001029 tristate "ST M48T59/M48T08/M48T02"
Chen Gang706b6322014-10-13 15:53:14 -07001030 depends on HAS_IOMEM
Mark Zhan2e774c72007-07-17 04:05:05 -07001031 help
1032 If you say Y here you will get support for the
Krzysztof Helt94fe7422008-09-03 15:12:34 -07001033 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1034
1035 These chips are usually found in Sun SPARC and UltraSPARC
1036 workstations.
Mark Zhan2e774c72007-07-17 04:05:05 -07001037
1038 This driver can also be built as a module, if so, the module
1039 will be called "rtc-m48t59".
1040
Geert Uytterhoeven4f9b9bb2009-03-18 23:29:27 +01001041config RTC_DRV_MSM6242
1042 tristate "Oki MSM6242"
Chen Gang706b6322014-10-13 15:53:14 -07001043 depends on HAS_IOMEM
Geert Uytterhoeven4f9b9bb2009-03-18 23:29:27 +01001044 help
1045 If you say yes here you get support for the Oki MSM6242
1046 timekeeping chip. It is used in some Amiga models (e.g. A2000).
1047
1048 This driver can also be built as a module. If so, the module
1049 will be called rtc-msm6242.
1050
David S. Millercca4c232008-08-29 01:29:53 -07001051config RTC_DRV_BQ4802
1052 tristate "TI BQ4802"
Chen Gang706b6322014-10-13 15:53:14 -07001053 depends on HAS_IOMEM
David S. Millercca4c232008-08-29 01:29:53 -07001054 help
1055 If you say Y here you will get support for the TI
1056 BQ4802 RTC chip.
1057
1058 This driver can also be built as a module. If so, the module
1059 will be called rtc-bq4802.
1060
Geert Uytterhoeven4f672ce2009-03-18 23:29:27 +01001061config RTC_DRV_RP5C01
1062 tristate "Ricoh RP5C01"
Chen Gang706b6322014-10-13 15:53:14 -07001063 depends on HAS_IOMEM
Geert Uytterhoeven4f672ce2009-03-18 23:29:27 +01001064 help
1065 If you say yes here you get support for the Ricoh RP5C01
1066 timekeeping chip. It is used in some Amiga models (e.g. A3000
1067 and A4000).
1068
1069 This driver can also be built as a module. If so, the module
1070 will be called rtc-rp5c01.
1071
Alessandro Zummo09a21e52007-05-08 00:33:48 -07001072config RTC_DRV_V3020
1073 tristate "EM Microelectronic V3020"
Alessandro Zummo09a21e52007-05-08 00:33:48 -07001074 help
1075 If you say yes here you will get support for the
1076 EM Microelectronic v3020 RTC chip.
1077
1078 This driver can also be built as a module. If so, the module
1079 will be called rtc-v3020.
1080
Mark Brown35c86bf2009-08-27 19:59:05 +02001081config RTC_DRV_WM831X
1082 tristate "Wolfson Microelectronics WM831x RTC"
1083 depends on MFD_WM831X
1084 help
1085 If you say yes here you will get support for the RTC subsystem
1086 of the Wolfson Microelectronics WM831X series PMICs.
1087
1088 This driver can also be built as a module. If so, the module
1089 will be called "rtc-wm831x".
1090
Mark Brown077eaf52008-11-12 13:27:04 -08001091config RTC_DRV_WM8350
1092 tristate "Wolfson Microelectronics WM8350 RTC"
1093 depends on MFD_WM8350
1094 help
1095 If you say yes here you will get support for the RTC subsystem
1096 of the Wolfson Microelectronics WM8350.
1097
1098 This driver can also be built as a module. If so, the module
1099 will be called "rtc-wm8350".
1100
Rajeev Kumar0942a712011-05-26 16:25:09 -07001101config RTC_DRV_SPEAR
1102 tristate "SPEAR ST RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001103 depends on PLAT_SPEAR || COMPILE_TEST
Rajeev Kumar0942a712011-05-26 16:25:09 -07001104 default y
1105 help
1106 If you say Y here you will get support for the RTC found on
1107 spear
1108
Balaji Raoeae854b2009-01-09 01:50:51 +01001109config RTC_DRV_PCF50633
1110 depends on MFD_PCF50633
1111 tristate "NXP PCF50633 RTC"
1112 help
1113 If you say yes here you get support for the RTC subsystem of the
1114 NXP PCF50633 used in embedded systems.
1115
Linus Walleijbd207cf2009-08-30 23:49:04 +02001116config RTC_DRV_AB3100
1117 tristate "ST-Ericsson AB3100 RTC"
1118 depends on AB3100_CORE
1119 default y if AB3100_CORE
1120 help
1121 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1122 support. This chip contains a battery- and capacitor-backed RTC.
1123
Virupax Sadashivpetimath0af62f42010-05-26 14:42:14 -07001124config RTC_DRV_AB8500
1125 tristate "ST-Ericsson AB8500 RTC"
1126 depends on AB8500_CORE
Ulf Hansson651fb482012-10-04 17:14:32 -07001127 select RTC_INTF_DEV
Ramesh Chandrasekarandc43d4a2012-07-30 14:41:41 -07001128 select RTC_INTF_DEV_UIE_EMUL
Virupax Sadashivpetimath0af62f42010-05-26 14:42:14 -07001129 help
1130 Select this to enable the ST-Ericsson AB8500 power management IC RTC
1131 support. This chip contains a battery- and capacitor-backed RTC.
1132
Wan ZongShunafd49a7e2009-12-15 16:46:17 -08001133config RTC_DRV_NUC900
1134 tristate "NUC910/NUC920 RTC driver"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001135 depends on ARCH_W90X900 || COMPILE_TEST
Wan ZongShunafd49a7e2009-12-15 16:46:17 -08001136 help
1137 If you say yes here you get support for the RTC subsystem of the
1138 NUC910/NUC920 used in embedded systems.
Linus Walleijbd207cf2009-08-30 23:49:04 +02001139
Neelesh Gupta16b1d262014-10-14 14:08:36 +05301140config RTC_DRV_OPAL
1141 tristate "IBM OPAL RTC driver"
1142 depends on PPC_POWERNV
1143 default y
1144 help
1145 If you say yes here you get support for the PowerNV platform RTC
1146 driver based on OPAL interfaces.
1147
1148 This driver can also be built as a module. If so, the module
1149 will be called rtc-opal.
1150
Suneel Garapati11143c12015-08-19 15:23:22 +05301151config RTC_DRV_ZYNQMP
1152 tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1153 depends on OF
1154 help
1155 If you say yes here you get support for the RTC controller found on
1156 Xilinx Zynq Ultrascale+ MPSoC.
1157
Alessandro Zummo09a21e52007-05-08 00:33:48 -07001158comment "on-CPU RTC drivers"
Alessandro Zummo09a21e52007-05-08 00:33:48 -07001159
Oleksij Rempel125e5502016-02-02 20:56:10 +01001160config RTC_DRV_ASM9260
1161 tristate "Alphascale asm9260 RTC"
1162 depends on MACH_ASM9260
1163 help
1164 If you say yes here you get support for the RTC on the
1165 Alphascale asm9260 SoC.
1166
1167 This driver can also be built as a module. If so, the module
1168 will be called rtc-asm9260.
1169
Miguel Aguilar8ecf6c52009-11-05 08:51:34 -06001170config RTC_DRV_DAVINCI
1171 tristate "TI DaVinci RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001172 depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
Miguel Aguilar8ecf6c52009-11-05 08:51:34 -06001173 help
1174 If you say yes here you get support for the RTC on the
1175 DaVinci platforms (DM365).
1176
1177 This driver can also be built as a module. If so, the module
1178 will be called rtc-davinci.
1179
Baruch Siachba172202015-04-16 12:45:40 -07001180config RTC_DRV_DIGICOLOR
1181 tristate "Conexant Digicolor RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001182 depends on ARCH_DIGICOLOR || COMPILE_TEST
Baruch Siachba172202015-04-16 12:45:40 -07001183 help
1184 If you say yes here you get support for the RTC on Conexant
1185 Digicolor platforms. This currently includes the CX92755 SoC.
1186
1187 This driver can also be built as a module. If so, the module
1188 will be called rtc-digicolor.
1189
Fabio Estevamb224b9a2012-05-29 15:07:37 -07001190config RTC_DRV_IMXDI
1191 tristate "Freescale IMX DryIce Real Time Clock"
Roland Stiggeef216ad2012-12-17 16:02:22 -08001192 depends on ARCH_MXC
Fabio Estevamb224b9a2012-05-29 15:07:37 -07001193 help
1194 Support for Freescale IMX DryIce RTC
1195
1196 This driver can also be built as a module, if so, the module
1197 will be called "rtc-imxdi".
1198
David Brownelldb68b182006-12-06 20:38:36 -08001199config RTC_DRV_OMAP
Lokesh Vutla86089762015-04-16 12:46:03 -07001200 tristate "TI OMAP Real Time Clock"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001201 depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
David Brownelldb68b182006-12-06 20:38:36 -08001202 help
Afzal Mohammed427af9a2012-12-17 16:02:17 -08001203 Say "yes" here to support the on chip real time clock
Lokesh Vutla86089762015-04-16 12:46:03 -07001204 present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
Afzal Mohammed427af9a2012-12-17 16:02:17 -08001205
1206 This driver can also be built as a module, if so, module
1207 will be called rtc-omap.
David Brownelldb68b182006-12-06 20:38:36 -08001208
Atul Dahiya16f4efe2010-07-20 16:38:49 +05301209config HAVE_S3C_RTC
1210 bool
1211 help
1212 This will include RTC support for Samsung SoCs. If
1213 you want to include RTC support for any machine, kindly
1214 select this in the respective mach-XXXX/Kconfig file.
1215
Ben Dooks1add6782006-07-01 04:36:26 -07001216config RTC_DRV_S3C
1217 tristate "Samsung S3C series SoC RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001218 depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
Ben Dooks1add6782006-07-01 04:36:26 -07001219 help
1220 RTC (Realtime Clock) driver for the clock inbuilt into the
1221 Samsung S3C24XX series of SoCs. This can provide periodic
1222 interrupt rates from 1Hz to 64Hz for user programs, and
1223 wakeup from Alarm.
1224
1225 The driver currently supports the common features on all the
1226 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1227 and S3C2442.
1228
1229 This driver can also be build as a module. If so, the module
1230 will be called rtc-s3c.
1231
Alessandro Zummofd507e22006-03-27 01:16:45 -08001232config RTC_DRV_EP93XX
1233 tristate "Cirrus Logic EP93XX"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001234 depends on ARCH_EP93XX || COMPILE_TEST
Alessandro Zummofd507e22006-03-27 01:16:45 -08001235 help
1236 If you say yes here you get support for the
1237 RTC embedded in the Cirrus Logic EP93XX processors.
1238
1239 This driver can also be built as a module. If so, the module
1240 will be called rtc-ep93xx.
1241
Richard Purdiee842f1c2006-03-27 01:16:46 -08001242config RTC_DRV_SA1100
Haojian Zhuang3888c092012-02-21 11:51:13 +08001243 tristate "SA11x0/PXA2xx/PXA910"
1244 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
Richard Purdiee842f1c2006-03-27 01:16:46 -08001245 help
1246 If you say Y here you will get access to the real time clock
1247 built into your SA11x0 or PXA2xx CPU.
1248
1249 To compile this driver as a module, choose M here: the
1250 module will be called rtc-sa1100.
Alessandro Zummofd507e22006-03-27 01:16:45 -08001251
Paul Mundt317a6102006-09-27 17:13:19 +09001252config RTC_DRV_SH
1253 tristate "SuperH On-Chip RTC"
Venu Byravarasu6b8029f2012-10-04 17:13:59 -07001254 depends on SUPERH && HAVE_CLK
Paul Mundt317a6102006-09-27 17:13:19 +09001255 help
1256 Say Y here to enable support for the on-chip RTC found in
1257 most SuperH processors.
1258
Alexandre Belloni98ab2c92015-05-09 21:21:54 +02001259 To compile this driver as a module, choose M here: the
Paul Mundt317a6102006-09-27 17:13:19 +09001260 module will be called rtc-sh.
1261
Yoichi Yuasa8417eb72006-04-10 22:54:47 -07001262config RTC_DRV_VR41XX
Alessandro Zummo3e16f6a2006-04-10 22:54:48 -07001263 tristate "NEC VR41XX"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001264 depends on CPU_VR41XX || COMPILE_TEST
Alessandro Zummo3e16f6a2006-04-10 22:54:48 -07001265 help
1266 If you say Y here you will get access to the real time clock
1267 built into your NEC VR41XX CPU.
1268
1269 To compile this driver as a module, choose M here: the
1270 module will be called rtc-vr41xx.
Yoichi Yuasa8417eb72006-04-10 22:54:47 -07001271
Russell Kinga1909012008-04-20 12:08:36 +01001272config RTC_DRV_PL030
1273 tristate "ARM AMBA PL030 RTC"
1274 depends on ARM_AMBA
1275 help
1276 If you say Y here you will get access to ARM AMBA
1277 PrimeCell PL030 RTC found on certain ARM SOCs.
1278
1279 To compile this driver as a module, choose M here: the
1280 module will be called rtc-pl030.
1281
Deepak Saxena8ae6e162006-06-25 05:47:38 -07001282config RTC_DRV_PL031
1283 tristate "ARM AMBA PL031 RTC"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -07001284 depends on ARM_AMBA
Deepak Saxena8ae6e162006-06-25 05:47:38 -07001285 help
1286 If you say Y here you will get access to ARM AMBA
Alessandro Zummo09a21e52007-05-08 00:33:48 -07001287 PrimeCell PL031 RTC found on certain ARM SOCs.
Deepak Saxena8ae6e162006-06-25 05:47:38 -07001288
1289 To compile this driver as a module, choose M here: the
1290 module will be called rtc-pl031.
1291
Hans-Christian Egtvedtfa04e782007-07-17 04:05:00 -07001292config RTC_DRV_AT32AP700X
1293 tristate "AT32AP700X series RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001294 depends on PLATFORM_AT32AP || COMPILE_TEST
Hans-Christian Egtvedtfa04e782007-07-17 04:05:00 -07001295 help
1296 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1297 AT32AP700x family processors.
1298
Andrew Victor7fc39f62006-12-10 02:19:03 -08001299config RTC_DRV_AT91RM9200
Nicolas Ferre24cecc12010-10-22 19:12:52 +02001300 tristate "AT91RM9200 or some AT91SAM9 RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001301 depends on ARCH_AT91 || COMPILE_TEST
Andrew Victor788b1fc2006-06-25 05:48:27 -07001302 help
David Brownell4cdf8542008-02-06 01:38:59 -08001303 Driver for the internal RTC (Realtime Clock) module found on
Nicolas Ferre24cecc12010-10-22 19:12:52 +02001304 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
David Brownell4cdf8542008-02-06 01:38:59 -08001305 this is powered by the backup power supply.
1306
1307config RTC_DRV_AT91SAM9
Boris BREZILLON3969eb42014-09-23 13:16:05 +02001308 tristate "AT91SAM9 RTT as RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001309 depends on ARCH_AT91 || COMPILE_TEST
Boris BREZILLON43e112b2014-09-23 13:14:44 +02001310 select MFD_SYSCON
David Brownell4cdf8542008-02-06 01:38:59 -08001311 help
Boris BREZILLON3969eb42014-09-23 13:16:05 +02001312 Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1313 can be used as an RTC thanks to the backup power supply (e.g. a
1314 small coin cell battery) which keeps this block and the GPBR
1315 (General Purpose Backup Registers) block powered when the device
1316 is shutdown.
1317 Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1318 probably want to use the real RTC block instead of the "RTT as an
1319 RTC" driver.
David Brownell4cdf8542008-02-06 01:38:59 -08001320
Manuel Lauss45fd8a02009-01-06 14:42:18 -08001321config RTC_DRV_AU1XXX
1322 tristate "Au1xxx Counter0 RTC support"
Manuel Lauss42a4f172010-07-15 21:45:04 +02001323 depends on MIPS_ALCHEMY
Manuel Lauss45fd8a02009-01-06 14:42:18 -08001324 help
1325 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1326 counter) to be used as a RTC.
1327
1328 This driver can also be built as a module. If so, the module
1329 will be called rtc-au1xxx.
1330
Wu, Bryan8cc75c92007-05-06 14:50:32 -07001331config RTC_DRV_BFIN
1332 tristate "Blackfin On-Chip RTC"
Graf Yang7f604592008-08-20 14:09:02 -07001333 depends on BLACKFIN && !BF561
Wu, Bryan8cc75c92007-05-06 14:50:32 -07001334 help
1335 If you say yes here you will get support for the
1336 Blackfin On-Chip Real Time Clock.
1337
1338 This driver can also be built as a module. If so, the module
1339 will be called rtc-bfin.
1340
Nobuhiro Iwamatsue9f2bd82007-05-08 00:26:37 -07001341config RTC_DRV_RS5C313
1342 tristate "Ricoh RS5C313"
Jan Engelhardtbb35fb22007-07-31 00:39:46 -07001343 depends on SH_LANDISK
Nobuhiro Iwamatsue9f2bd82007-05-08 00:26:37 -07001344 help
1345 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1346
Geert Uytterhoeven3afe6d02009-02-19 16:46:49 +01001347config RTC_DRV_GENERIC
1348 tristate "Generic RTC support"
1349 # Please consider writing a new RTC driver instead of using the generic
1350 # RTC abstraction
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001351 depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
Kyle McMartin9eb16862008-09-10 14:24:07 +00001352 help
Geert Uytterhoeven3afe6d02009-02-19 16:46:49 +01001353 Say Y or M here to enable RTC support on systems using the generic
1354 RTC abstraction. If you do not know what you are doing, you should
Kyle McMartin9eb16862008-09-10 14:24:07 +00001355 just say Y.
1356
Robert Jarzmikdc944362009-01-06 14:42:14 -08001357config RTC_DRV_PXA
Alexandre Belloni832315b2016-03-10 05:46:18 +01001358 tristate "PXA27x/PXA3xx"
1359 depends on ARCH_PXA
1360 select RTC_DRV_SA1100
1361 help
Rob Herring3cdf4ad2015-05-13 09:20:04 -05001362 If you say Y here you will get access to the real time clock
1363 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1364 consisting of an SA1100 compatible RTC and the extended PXA RTC.
Robert Jarzmikdc944362009-01-06 14:42:14 -08001365
Alexandre Belloni98ab2c92015-05-09 21:21:54 +02001366 This RTC driver uses PXA RTC registers available since pxa27x
1367 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
Robert Jarzmikdc944362009-01-06 14:42:14 -08001368
Alexey Charkovf77fbdf2011-05-26 16:25:03 -07001369config RTC_DRV_VT8500
1370 tristate "VIA/WonderMedia 85xx SoC RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001371 depends on ARCH_VT8500 || COMPILE_TEST
Alexey Charkovf77fbdf2011-05-26 16:25:03 -07001372 help
1373 If you say Y here you will get access to the real time clock
1374 built into your VIA VT8500 SoC or its relatives.
1375
Robert Jarzmikdc944362009-01-06 14:42:14 -08001376
David S. Miller7a138ed2008-08-29 01:32:43 -07001377config RTC_DRV_SUN4V
1378 bool "SUN4V Hypervisor RTC"
1379 depends on SPARC64
1380 help
1381 If you say Y here you will get support for the Hypervisor
1382 based RTC on SUN4V systems.
1383
Chen-Yu Tsai9765d2d2014-08-26 11:54:55 +08001384config RTC_DRV_SUN6I
1385 tristate "Allwinner A31 RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001386 default MACH_SUN6I || MACH_SUN8I || COMPILE_TEST
Andre Przywara28639342016-02-01 17:39:22 +00001387 depends on ARCH_SUNXI
Chen-Yu Tsai9765d2d2014-08-26 11:54:55 +08001388 help
Andre Przywara28639342016-02-01 17:39:22 +00001389 If you say Y here you will get support for the RTC found in
1390 some Allwinner SoCs like the A31 or the A64.
Chen-Yu Tsai9765d2d2014-08-26 11:54:55 +08001391
Carlo Caione594c6fb2013-11-16 18:33:54 +01001392config RTC_DRV_SUNXI
1393 tristate "Allwinner sun4i/sun7i RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001394 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
Carlo Caione594c6fb2013-11-16 18:33:54 +01001395 help
1396 If you say Y here you will get support for the RTC found on
1397 Allwinner A10/A20.
1398
David S. Millerde2cf332008-08-28 23:02:36 -07001399config RTC_DRV_STARFIRE
1400 bool "Starfire RTC"
1401 depends on SPARC64
1402 help
1403 If you say Y here you will get support for the RTC found on
1404 Starfire systems.
1405
Atsushi Nemoto0e149232009-01-06 14:42:22 -08001406config RTC_DRV_TX4939
1407 tristate "TX4939 SoC"
1408 depends on SOC_TX4939
1409 help
1410 Driver for the internal RTC (Realtime Clock) module found on
1411 Toshiba TX4939 SoC.
1412
Saeed Bisharadefb4512009-01-06 14:42:24 -08001413config RTC_DRV_MV
1414 tristate "Marvell SoC RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001415 depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
Saeed Bisharadefb4512009-01-06 14:42:24 -08001416 help
1417 If you say yes here you will get support for the in-chip RTC
1418 that can be found in some of Marvell's SoC devices, such as
1419 the Kirkwood 88F6281 and 88F6192.
1420
1421 This driver can also be built as a module. If so, the module
1422 will be called rtc-mv.
1423
Gregory CLEMENTa3a42802015-02-13 14:41:11 -08001424config RTC_DRV_ARMADA38X
1425 tristate "Armada 38x Marvell SoC RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001426 depends on ARCH_MVEBU || COMPILE_TEST
Gregory CLEMENTa3a42802015-02-13 14:41:11 -08001427 help
1428 If you say yes here you will get support for the in-chip RTC
1429 that can be found in the Armada 38x Marvell's SoC device
1430
1431 This driver can also be built as a module. If so, the module
1432 will be called armada38x-rtc.
1433
Hans Ulli Kroll98a9bb52015-05-20 17:49:31 +02001434config RTC_DRV_GEMINI
1435 tristate "Gemini SoC RTC"
1436 depends on ARCH_GEMINI || COMPILE_TEST
1437 depends on HAS_IOMEM
1438 help
1439 If you say Y here you will get support for the
1440 RTC found on Gemini SoC's.
1441
1442 This driver can also be built as a module. If so, the module
1443 will be called rtc-gemini.
1444
Geert Uytterhoeven0b5f0372009-02-24 14:04:20 +01001445config RTC_DRV_PS3
1446 tristate "PS3 RTC"
1447 depends on PPC_PS3
1448 help
1449 If you say yes here you will get support for the RTC on PS3.
1450
1451 This driver can also be built as a module. If so, the module
1452 will be called rtc-ps3.
1453
Linus Walleijaa958f52009-09-22 16:46:24 -07001454config RTC_DRV_COH901331
1455 tristate "ST-Ericsson COH 901 331 RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001456 depends on ARCH_U300 || COMPILE_TEST
Linus Walleijaa958f52009-09-22 16:46:24 -07001457 help
1458 If you say Y here you will get access to ST-Ericsson
1459 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1460 Platforms.
1461
1462 This driver can also be built as a module. If so, the module
1463 will be called "rtc-coh901331".
1464
1465
dmitry pervushindf17f632009-09-22 16:46:26 -07001466config RTC_DRV_STMP
Wolfram Sang46b21212011-05-25 12:56:50 +02001467 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001468 depends on ARCH_MXS || COMPILE_TEST
Alexandre Belloni20d048a2015-05-03 11:29:44 +02001469 select STMP_DEVICE
dmitry pervushindf17f632009-09-22 16:46:26 -07001470 help
1471 If you say yes here you will get support for the onboard
Wolfram Sang46b21212011-05-25 12:56:50 +02001472 STMP3xxx/i.MX23/i.MX28 RTC.
dmitry pervushindf17f632009-09-22 16:46:26 -07001473
1474 This driver can also be built as a module. If so, the module
1475 will be called rtc-stmp3xxx.
1476
Daniel Ribeirod3c7a3f2009-09-22 16:46:27 -07001477config RTC_DRV_PCAP
1478 tristate "PCAP RTC"
1479 depends on EZX_PCAP
1480 help
1481 If you say Y here you will get support for the RTC found on
1482 the PCAP2 ASIC used on some Motorola phones.
1483
Uwe Kleine-König1c978722010-10-28 12:30:53 +02001484config RTC_DRV_MC13XXX
1485 depends on MFD_MC13XXX
1486 tristate "Freescale MC13xxx RTC"
Uwe Kleine-König43299f2852009-12-15 16:46:09 -08001487 help
Uwe Kleine-König1c978722010-10-28 12:30:53 +02001488 This enables support for the RTCs found on Freescale's PMICs
1489 MC13783 and MC13892.
Uwe Kleine-König43299f2852009-12-15 16:46:09 -08001490
Anatolij Gustschin50aae722010-02-16 10:47:35 -07001491config RTC_DRV_MPC5121
1492 tristate "Freescale MPC5121 built-in RTC"
Dmitry Eremin-Solenikov955dbea2011-07-25 17:13:30 -07001493 depends on PPC_MPC512x || PPC_MPC52xx
Anatolij Gustschin50aae722010-02-16 10:47:35 -07001494 help
1495 If you say yes here you will get support for the
Dmitry Eremin-Solenikov955dbea2011-07-25 17:13:30 -07001496 built-in RTC on MPC5121 or on MPC5200.
Anatolij Gustschin50aae722010-02-16 10:47:35 -07001497
1498 This driver can also be built as a module. If so, the module
1499 will be called rtc-mpc5121.
1500
Lars-Peter Clausen3bf0eea2010-06-19 18:29:50 +00001501config RTC_DRV_JZ4740
1502 tristate "Ingenic JZ4740 SoC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001503 depends on MACH_JZ4740 || COMPILE_TEST
Lars-Peter Clausen3bf0eea2010-06-19 18:29:50 +00001504 help
1505 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1506 controller.
1507
1508 This driver can also be buillt as a module. If so, the module
1509 will be called rtc-jz4740.
1510
Joachim Eastwoodc28b42e2015-07-11 19:28:49 +02001511config RTC_DRV_LPC24XX
1512 tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1513 depends on ARCH_LPC18XX || COMPILE_TEST
1514 depends on OF && HAS_IOMEM
1515 help
1516 This enables support for the NXP RTC found which can be found on
1517 NXP LPC178x/18xx/408x/43xx devices.
1518
1519 If you have one of the devices above enable this driver to use
1520 the hardware RTC. This driver can also be buillt as a module. If
1521 so, the module will be called rtc-lpc24xx.
1522
Kevin Wells9aa449b2010-10-27 15:33:01 -07001523config RTC_DRV_LPC32XX
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001524 depends on ARCH_LPC32XX || COMPILE_TEST
Kevin Wells9aa449b2010-10-27 15:33:01 -07001525 tristate "NXP LPC32XX RTC"
1526 help
1527 This enables support for the NXP RTC in the LPC32XX
1528
1529 This driver can also be buillt as a module. If so, the module
1530 will be called rtc-lpc32xx.
1531
Anirudh Ghayal9a9a54a2011-07-25 17:13:33 -07001532config RTC_DRV_PM8XXX
1533 tristate "Qualcomm PMIC8XXX RTC"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001534 depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
Anirudh Ghayal9a9a54a2011-07-25 17:13:33 -07001535 help
1536 If you say yes here you get support for the
1537 Qualcomm PMIC8XXX RTC.
1538
1539 To compile this driver as a module, choose M here: the
1540 module will be called rtc-pm8xxx.
1541
Andrew Chewff859ba2011-03-22 16:34:55 -07001542config RTC_DRV_TEGRA
1543 tristate "NVIDIA Tegra Internal RTC driver"
Alexandre Belloni7a587ea2015-05-03 11:00:57 +02001544 depends on ARCH_TEGRA || COMPILE_TEST
Andrew Chewff859ba2011-03-22 16:34:55 -07001545 help
1546 If you say yes here you get support for the
1547 Tegra 200 series internal RTC module.
1548
1549 This drive can also be built as a module. If so, the module
1550 will be called rtc-tegra.
1551
Chris Metcalfdd196a22011-05-09 13:28:43 -04001552config RTC_DRV_TILE
1553 tristate "Tilera hypervisor RTC support"
1554 depends on TILE
1555 help
1556 Enable support for the Linux driver side of the Tilera
1557 hypervisor's real-time clock interface.
1558
Guan Xuetao2809e802011-05-26 16:43:27 +08001559config RTC_DRV_PUV3
1560 tristate "PKUnity v3 RTC support"
1561 depends on ARCH_PUV3
1562 help
1563 This enables support for the RTC in the PKUnity-v3 SoCs.
1564
1565 This drive can also be built as a module. If so, the module
1566 will be called rtc-puv3.
1567
zhao zhangb4f0b882012-03-23 15:02:32 -07001568config RTC_DRV_LOONGSON1
1569 tristate "loongson1 RTC support"
Huacai Chen30ad29b2015-04-21 10:00:35 +08001570 depends on MACH_LOONGSON32
zhao zhangb4f0b882012-03-23 15:02:32 -07001571 help
1572 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1573 counter) to be used as a RTC.
1574
1575 This driver can also be built as a module. If so, the module
1576 will be called rtc-ls1x.
1577
Fabio Estevam79811592012-05-29 15:07:37 -07001578config RTC_DRV_MXC
Fabio Estevamb224b9a2012-05-29 15:07:37 -07001579 tristate "Freescale MXC Real Time Clock"
1580 depends on ARCH_MXC
Fabio Estevamb224b9a2012-05-29 15:07:37 -07001581 help
1582 If you say yes here you get support for the Freescale MXC
1583 RTC module.
1584
1585 This driver can also be built as a module, if so, the module
1586 will be called "rtc-mxc".
1587
Shawn Guo179a5022012-10-04 17:13:49 -07001588config RTC_DRV_SNVS
1589 tristate "Freescale SNVS RTC support"
Shawn Guo8a0fa182015-07-13 15:58:51 +08001590 select REGMAP_MMIO
Shawn Guo179a5022012-10-04 17:13:49 -07001591 depends on HAS_IOMEM
1592 depends on OF
1593 help
1594 If you say yes here you get support for the Freescale SNVS
1595 Low Power (LP) RTC module.
1596
1597 This driver can also be built as a module, if so, the module
1598 will be called "rtc-snvs".
1599
Xianglong Due88b8152013-07-03 15:08:04 -07001600config RTC_DRV_SIRFSOC
1601 tristate "SiRFSOC RTC"
1602 depends on ARCH_SIRF
1603 help
1604 Say "yes" here to support the real time clock on SiRF SOC chips.
1605 This driver can also be built as a module called rtc-sirfsoc.
1606
Lee Jonesb5b2bdf2015-04-09 15:47:33 +01001607config RTC_DRV_ST_LPC
1608 tristate "STMicroelectronics LPC RTC"
1609 depends on ARCH_STI
1610 depends on OF
1611 help
1612 Say Y here to include STMicroelectronics Low Power Controller
1613 (LPC) based RTC support.
1614
1615 To compile this driver as a module, choose M here: the
1616 module will be called rtc-st-lpc.
1617
Jonas Jensen453b4c62013-09-11 14:24:17 -07001618config RTC_DRV_MOXART
1619 tristate "MOXA ART RTC"
Jean Delvare441fb762014-08-08 14:20:05 -07001620 depends on ARCH_MOXART || COMPILE_TEST
Jonas Jensen453b4c62013-09-11 14:24:17 -07001621 help
1622 If you say yes here you get support for the MOXA ART
1623 RTC module.
1624
1625 This driver can also be built as a module. If so, the module
1626 will be called rtc-moxart
1627
Tianping Fangfc297912015-05-06 15:23:41 +08001628config RTC_DRV_MT6397
1629 tristate "Mediatek Real Time Clock driver"
Arnd Bergmann04d3ba72016-01-25 17:04:46 +01001630 depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
Tianping Fangfc297912015-05-06 15:23:41 +08001631 help
1632 This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
1633 MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1634 Mediatek(R) RTC driver.
1635
1636 If you want to use Mediatek(R) RTC interface, select Y or M here.
1637
Loc Hof12d8692014-06-06 14:35:42 -07001638config RTC_DRV_XGENE
1639 tristate "APM X-Gene RTC"
Chen Gang706b6322014-10-13 15:53:14 -07001640 depends on HAS_IOMEM
Jean Delvarefdf8afa2015-05-06 09:24:42 +02001641 depends on ARCH_XGENE || COMPILE_TEST
Loc Hof12d8692014-06-06 14:35:42 -07001642 help
1643 If you say yes here you get support for the APM X-Gene SoC real time
1644 clock.
1645
1646 This driver can also be built as a module, if so, the module
1647 will be called "rtc-xgene".
1648
Joshua Henderson51aa9052016-02-25 10:30:44 -07001649config RTC_DRV_PIC32
1650 tristate "Microchip PIC32 RTC"
1651 depends on MACH_PIC32
1652 default y
1653 help
1654 If you say yes here you get support for the PIC32 RTC module.
1655
1656 This driver can also be built as a module. If so, the module
1657 will be called rtc-pic32
1658
Alexander Holler62e00cb2012-12-15 12:45:00 +00001659comment "HID Sensor RTC drivers"
1660
1661config RTC_DRV_HID_SENSOR_TIME
1662 tristate "HID Sensor Time"
1663 depends on USB_HID
1664 select IIO
1665 select HID_SENSOR_HUB
1666 select HID_SENSOR_IIO_COMMON
1667 help
1668 Say yes here to build support for the HID Sensors of type Time.
1669 This drivers makes such sensors available as RTCs.
1670
1671 If this driver is compiled as a module, it will be named
1672 rtc-hid-sensor-time.
1673
1674
Jan Engelhardtbb35fb22007-07-31 00:39:46 -07001675endif # RTC_CLASS