Version:  2.0.40 2.2.26 2.4.37 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1 4.2 4.3 4.4 4.5

Linux/drivers/rtc/Kconfig

  1 #
  2 # RTC class/drivers configuration
  3 #
  4 
  5 config RTC_LIB
  6         bool
  7 
  8 menuconfig RTC_CLASS
  9         bool "Real Time Clock"
 10         default n
 11         depends on !S390 && !UML
 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
 16           probably want to enable one or more of the interfaces below.
 17 
 18 if RTC_CLASS
 19 
 20 config RTC_HCTOSYS
 21         bool "Set system time from RTC on startup and resume"
 22         default y
 23         help
 24           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.
 27 
 28 config RTC_HCTOSYS_DEVICE
 29         string "RTC used to set the system time"
 30         depends on RTC_HCTOSYS
 31         default "rtc0"
 32         help
 33           The RTC device that will be used to (re)initialize the system
 34           clock, usually rtc0. Initialization is done when the system
 35           starts up, and when it resumes from a low power state. This
 36           device should record time in UTC, since the kernel won't do
 37           timezone correction.
 38 
 39           The driver for this RTC device must be loaded before late_initcall
 40           functions run, so it must usually be statically linked.
 41 
 42           This clock should be battery-backed, so that it reads the correct
 43           time when the system boots from a power-off state. Otherwise, your
 44           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
 48           sleep states. Do not specify an RTC here unless it stays powered
 49           during all this system's supported sleep states.
 50 
 51 config 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 
 59 config 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 
 70 config RTC_DEBUG
 71         bool "RTC debug support"
 72         help
 73           Say yes here to enable debugging support in the RTC framework
 74           and individual RTC drivers.
 75 
 76 comment "RTC interfaces"
 77 
 78 config RTC_INTF_SYSFS
 79         bool "/sys/class/rtc/rtcN (sysfs)"
 80         depends on SYSFS
 81         default RTC_CLASS
 82         help
 83           Say yes here if you want to use your RTCs using sysfs interfaces,
 84           /sys/class/rtc/rtc0 through /sys/.../rtcN.
 85 
 86           If unsure, say Y.
 87 
 88 config RTC_INTF_PROC
 89         bool "/proc/driver/rtc (procfs for rtcN)"
 90         depends on PROC_FS
 91         default RTC_CLASS
 92         help
 93           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.
 98 
 99           If unsure, say Y.
100 
101 config RTC_INTF_DEV
102         bool "/dev/rtcN (character devices)"
103         default RTC_CLASS
104         help
105           Say yes here if you want to use your RTCs using the /dev
106           interfaces, which "udev" sets up as /dev/rtc0 through
107           /dev/rtcN.
108 
109           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.
115 
116 config 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 
128 config RTC_DRV_TEST
129         tristate "Test driver/device"
130         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 
142 comment "I2C RTC drivers"
143         depends on I2C
144 
145 if I2C
146 
147 config RTC_DRV_88PM860X
148         tristate "Marvell 88PM860x"
149         depends on MFD_88PM860X
150         help
151           If you say yes here you get support for RTC function in Marvell
152           88PM860x chips.
153 
154           This driver can also be built as a module. If so, the module
155           will be called rtc-88pm860x.
156 
157 config RTC_DRV_88PM80X
158         tristate "Marvell 88PM80x"
159         depends on MFD_88PM800
160         help
161           If you say yes here you get support for RTC function in Marvell
162           88PM80x chips.
163 
164           This driver can also be built as a module. If so, the module
165           will be called rtc-88pm80x.
166 
167 config RTC_DRV_ABB5ZES3
168         select REGMAP_I2C
169         tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
170         help
171           If you say yes here you get support for the Abracon
172           AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
173 
174           This driver can also be built as a module. If so, the module
175           will be called rtc-ab-b5ze-s3.
176 
177 config RTC_DRV_ABX80X
178         tristate "Abracon ABx80x"
179         help
180           If you say yes here you get support for Abracon AB080X and AB180X
181           families of ultra-low-power  battery- and capacitor-backed real-time
182           clock chips.
183 
184           This driver can also be built as a module. If so, the module
185           will be called rtc-abx80x.
186 
187 config RTC_DRV_AS3722
188         tristate "ams AS3722 RTC driver"
189         depends on MFD_AS3722
190         help
191           If you say yes here you get support for the RTC of ams AS3722 PMIC
192           chips.
193 
194           This driver can also be built as a module. If so, the module
195           will be called rtc-as3722.
196 
197 config RTC_DRV_DS1307
198         tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
199         help
200           If you say yes here you get support for various compatible RTC
201           chips (often with battery backup) connected with I2C. This driver
202           should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
203           EPSON RX-8025 and probably other chips. In some cases the RTC
204           must already have been initialized (by manufacturing or a
205           bootloader).
206 
207           The first seven registers on these chips hold an RTC, and other
208           registers may add features such as NVRAM, a trickle charger for
209           the RTC/NVRAM backup power, and alarms. NVRAM is visible in
210           sysfs, but other chip features may not be available.
211 
212           This driver can also be built as a module. If so, the module
213           will be called rtc-ds1307.
214 
215 config RTC_DRV_DS1374
216         tristate "Dallas/Maxim DS1374"
217         help
218           If you say yes here you get support for Dallas Semiconductor
219           DS1374 real-time clock chips. If an interrupt is associated
220           with the device, the alarm functionality is supported.
221 
222           This driver can also be built as a module. If so, the module
223           will be called rtc-ds1374.
224 
225 config RTC_DRV_DS1374_WDT
226         bool "Dallas/Maxim DS1374 watchdog timer"
227         depends on RTC_DRV_DS1374
228         help
229           If you say Y here you will get support for the
230           watchdog timer in the Dallas Semiconductor DS1374
231           real-time clock chips.
232 
233 config RTC_DRV_DS1672
234         tristate "Dallas/Maxim DS1672"
235         help
236           If you say yes here you get support for the
237           Dallas/Maxim DS1672 timekeeping chip.
238 
239           This driver can also be built as a module. If so, the module
240           will be called rtc-ds1672.
241 
242 config RTC_DRV_DS3232
243         tristate "Dallas/Maxim DS3232"
244         help
245           If you say yes here you get support for Dallas Semiconductor
246           DS3232 real-time clock chips. If an interrupt is associated
247           with the device, the alarm functionality is supported.
248 
249           This driver can also be built as a module.  If so, the module
250           will be called rtc-ds3232.
251 
252 config RTC_DRV_HYM8563
253         tristate "Haoyu Microelectronics HYM8563"
254         depends on OF
255         help
256           Say Y to enable support for the HYM8563 I2C RTC chip. Apart
257           from the usual rtc functions it provides a clock output of
258           up to 32kHz.
259 
260           This driver can also be built as a module. If so, the module
261           will be called rtc-hym8563.
262 
263 config RTC_DRV_LP8788
264         tristate "TI LP8788 RTC driver"
265         depends on MFD_LP8788
266         help
267           Say Y to enable support for the LP8788 RTC/ALARM driver.
268 
269 config RTC_DRV_MAX6900
270         tristate "Maxim MAX6900"
271         help
272           If you say yes here you will get support for the
273           Maxim MAX6900 I2C RTC chip.
274 
275           This driver can also be built as a module. If so, the module
276           will be called rtc-max6900.
277 
278 config RTC_DRV_MAX8907
279         tristate "Maxim MAX8907"
280         depends on MFD_MAX8907
281         help
282           If you say yes here you will get support for the
283           RTC of Maxim MAX8907 PMIC.
284 
285           This driver can also be built as a module. If so, the module
286           will be called rtc-max8907.
287 
288 config RTC_DRV_MAX8925
289         tristate "Maxim MAX8925"
290         depends on MFD_MAX8925
291         help
292           If you say yes here you will get support for the
293           RTC of Maxim MAX8925 PMIC.
294 
295           This driver can also be built as a module. If so, the module
296           will be called rtc-max8925.
297 
298 config RTC_DRV_MAX8998
299         tristate "Maxim MAX8998"
300         depends on MFD_MAX8998
301         help
302           If you say yes here you will get support for the
303           RTC of Maxim MAX8998 PMIC.
304 
305           This driver can also be built as a module. If so, the module
306           will be called rtc-max8998.
307 
308 config RTC_DRV_MAX8997
309         tristate "Maxim MAX8997"
310         depends on MFD_MAX8997
311         help
312           If you say yes here you will get support for the
313           RTC of Maxim MAX8997 PMIC.
314 
315           This driver can also be built as a module. If so, the module
316           will be called rtc-max8997.
317 
318 config RTC_DRV_MAX77686
319         tristate "Maxim MAX77686"
320         depends on MFD_MAX77686
321         help
322           If you say yes here you will get support for the
323           RTC of Maxim MAX77686 PMIC.
324 
325           This driver can also be built as a module. If so, the module
326           will be called rtc-max77686.
327 
328 config RTC_DRV_RK808
329         tristate "Rockchip RK808 RTC"
330         depends on MFD_RK808
331         help
332           If you say yes here you will get support for the
333           RTC of RK808 PMIC.
334 
335           This driver can also be built as a module. If so, the module
336           will be called rk808-rtc.
337 
338 config RTC_DRV_MAX77802
339         tristate "Maxim 77802 RTC"
340         depends on MFD_MAX77686
341         help
342           If you say yes here you will get support for the
343           RTC of Maxim MAX77802 PMIC.
344 
345           This driver can also be built as a module. If so, the module
346           will be called rtc-max77802.
347 
348 config RTC_DRV_RS5C372
349         tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
350         help
351           If you say yes here you get support for the
352           Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
353 
354           This driver can also be built as a module. If so, the module
355           will be called rtc-rs5c372.
356 
357 config RTC_DRV_ISL1208
358         tristate "Intersil ISL1208"
359         help
360           If you say yes here you get support for the
361           Intersil ISL1208 RTC chip.
362 
363           This driver can also be built as a module. If so, the module
364           will be called rtc-isl1208.
365 
366 config RTC_DRV_ISL12022
367         tristate "Intersil ISL12022"
368         help
369           If you say yes here you get support for the
370           Intersil ISL12022 RTC chip.
371 
372           This driver can also be built as a module. If so, the module
373           will be called rtc-isl12022.
374 
375 config RTC_DRV_ISL12057
376         select REGMAP_I2C
377         tristate "Intersil ISL12057"
378         help
379           If you say yes here you get support for the Intersil ISL12057
380           I2C RTC chip.
381 
382           This driver can also be built as a module. If so, the module
383           will be called rtc-isl12057.
384 
385 config RTC_DRV_X1205
386         tristate "Xicor/Intersil X1205"
387         help
388           If you say yes here you get support for the
389           Xicor/Intersil X1205 RTC chip.
390 
391           This driver can also be built as a module. If so, the module
392           will be called rtc-x1205.
393 
394 config RTC_DRV_PALMAS
395         tristate "TI Palmas RTC driver"
396         depends on MFD_PALMAS
397         help
398           If you say yes here you get support for the RTC of TI PALMA series PMIC
399           chips.
400 
401           This driver can also be built as a module. If so, the module
402           will be called rtc-palma.
403 
404 config RTC_DRV_PCF2127
405         tristate "NXP PCF2127"
406         help
407           If you say yes here you get support for the NXP PCF2127/29 RTC
408           chips.
409 
410           This driver can also be built as a module. If so, the module
411           will be called rtc-pcf2127.
412 
413 config RTC_DRV_PCF8523
414         tristate "NXP PCF8523"
415         help
416           If you say yes here you get support for the NXP PCF8523 RTC
417           chips.
418 
419           This driver can also be built as a module. If so, the module
420           will be called rtc-pcf8523.
421 
422 config RTC_DRV_PCF8563
423         tristate "Philips PCF8563/Epson RTC8564"
424         help
425           If you say yes here you get support for the
426           Philips PCF8563 RTC chip. The Epson RTC8564
427           should work as well.
428 
429           This driver can also be built as a module. If so, the module
430           will be called rtc-pcf8563.
431 
432 config RTC_DRV_PCF85063
433         tristate "nxp PCF85063"
434         help
435           If you say yes here you get support for the PCF85063 RTC chip
436 
437           This driver can also be built as a module. If so, the module
438           will be called rtc-pcf85063.
439 
440 config RTC_DRV_PCF8583
441         tristate "Philips PCF8583"
442         help
443           If you say yes here you get support for the Philips PCF8583
444           RTC chip found on Acorn RiscPCs. This driver supports the
445           platform specific method of retrieving the current year from
446           the RTC's SRAM. It will work on other platforms with the same
447           chip, but the year will probably have to be tweaked.
448 
449           This driver can also be built as a module. If so, the module
450           will be called rtc-pcf8583.
451 
452 config RTC_DRV_M41T80
453         tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
454         help
455           If you say Y here you will get support for the ST M41T60
456           and M41T80 RTC chips series. Currently, the following chips are
457           supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
458           M41ST85, M41ST87, and MicroCrystal RV4162.
459 
460           This driver can also be built as a module. If so, the module
461           will be called rtc-m41t80.
462 
463 config RTC_DRV_M41T80_WDT
464         bool "ST M41T65/M41T80 series RTC watchdog timer"
465         depends on RTC_DRV_M41T80
466         help
467           If you say Y here you will get support for the
468           watchdog timer in the ST M41T60 and M41T80 RTC chips series.
469 
470 config RTC_DRV_BQ32K
471         tristate "TI BQ32000"
472         help
473           If you say Y here you will get support for the TI
474           BQ32000 I2C RTC chip.
475 
476           This driver can also be built as a module. If so, the module
477           will be called rtc-bq32k.
478 
479 config RTC_DRV_DM355EVM
480         tristate "TI DaVinci DM355 EVM RTC"
481         depends on MFD_DM355EVM_MSP
482         help
483           Supports the RTC firmware in the MSP430 on the DM355 EVM.
484 
485 config RTC_DRV_TWL92330
486         bool "TI TWL92330/Menelaus"
487         depends on MENELAUS
488         help
489           If you say yes here you get support for the RTC on the
490           TWL92330 "Menelaus" power management chip, used with OMAP2
491           platforms. The support is integrated with the rest of
492           the Menelaus driver; it's not separate module.
493 
494 config RTC_DRV_TWL4030
495         tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
496         depends on TWL4030_CORE
497         help
498           If you say yes here you get support for the RTC on the
499           TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
500 
501           This driver can also be built as a module. If so, the module
502           will be called rtc-twl.
503 
504 config RTC_DRV_TPS6586X
505         tristate "TI TPS6586X RTC driver"
506         depends on MFD_TPS6586X
507         help
508           TI Power Management IC TPS6586X supports RTC functionality
509           along with alarm. This driver supports the RTC driver for
510           the TPS6586X RTC module.
511 
512 config RTC_DRV_TPS65910
513         tristate "TI TPS65910 RTC driver"
514         depends on RTC_CLASS && MFD_TPS65910
515         help
516           If you say yes here you get support for the RTC on the
517           TPS65910 chips.
518 
519           This driver can also be built as a module. If so, the module
520           will be called rtc-tps65910.
521 
522 config RTC_DRV_TPS80031
523         tristate "TI TPS80031/TPS80032 RTC driver"
524         depends on MFD_TPS80031
525         help
526           TI Power Management IC TPS80031 supports RTC functionality
527           along with alarm. This driver supports the RTC driver for
528           the TPS80031 RTC module.
529 
530 config RTC_DRV_RC5T583
531         tristate "RICOH 5T583 RTC driver"
532         depends on MFD_RC5T583
533         help
534           If you say yes here you get support for the RTC on the
535           RICOH 5T583 chips.
536 
537           This driver can also be built as a module. If so, the module
538           will be called rtc-rc5t583.
539 
540 config RTC_DRV_S35390A
541         tristate "Seiko Instruments S-35390A"
542         select BITREVERSE
543         help
544           If you say yes here you will get support for the Seiko
545           Instruments S-35390A.
546 
547           This driver can also be built as a module. If so the module
548           will be called rtc-s35390a.
549 
550 config RTC_DRV_FM3130
551         tristate "Ramtron FM3130"
552         help
553           If you say Y here you will get support for the
554           Ramtron FM3130 RTC chips.
555           Ramtron FM3130 is a chip with two separate devices inside,
556           RTC clock and FRAM. This driver provides only RTC functionality.
557 
558           This driver can also be built as a module. If so the module
559           will be called rtc-fm3130.
560 
561 config RTC_DRV_RX8010
562         tristate "Epson RX8010SJ"
563         depends on I2C
564         help
565           If you say yes here you get support for the Epson RX8010SJ RTC
566           chip.
567 
568           This driver can also be built as a module. If so, the module
569           will be called rtc-rx8010.
570 
571 config RTC_DRV_RX8581
572         tristate "Epson RX-8581"
573         help
574           If you say yes here you will get support for the Epson RX-8581.
575 
576           This driver can also be built as a module. If so the module
577           will be called rtc-rx8581.
578 
579 config RTC_DRV_RX8025
580         tristate "Epson RX-8025SA/NB"
581         help
582           If you say yes here you get support for the Epson
583           RX-8025SA/NB RTC chips.
584 
585           This driver can also be built as a module. If so, the module
586           will be called rtc-rx8025.
587 
588 config RTC_DRV_EM3027
589         tristate "EM Microelectronic EM3027"
590         help
591           If you say yes here you get support for the EM
592           Microelectronic EM3027 RTC chips.
593 
594           This driver can also be built as a module. If so, the module
595           will be called rtc-em3027.
596 
597 config RTC_DRV_RV3029C2
598         tristate "Micro Crystal RTC"
599         help
600           If you say yes here you get support for the Micro Crystal
601           RV3029-C2 RTC chips.
602 
603           This driver can also be built as a module. If so, the module
604           will be called rtc-rv3029c2.
605 
606 config RTC_DRV_RV8803
607         tristate "Micro Crystal RV8803"
608         help
609           If you say yes here you get support for the Micro Crystal
610           RV8803 RTC chips.
611 
612           This driver can also be built as a module. If so, the module
613           will be called rtc-rv8803.
614 
615 config RTC_DRV_S5M
616         tristate "Samsung S2M/S5M series"
617         depends on MFD_SEC_CORE
618         help
619           If you say yes here you will get support for the
620           RTC of Samsung S2MPS14 and S5M PMIC series.
621 
622           This driver can also be built as a module. If so, the module
623           will be called rtc-s5m.
624 
625 endif # I2C
626 
627 comment "SPI RTC drivers"
628 
629 if SPI_MASTER
630 
631 config RTC_DRV_M41T93
632         tristate "ST M41T93"
633         help
634           If you say yes here you will get support for the
635           ST M41T93 SPI RTC chip.
636 
637           This driver can also be built as a module. If so, the module
638           will be called rtc-m41t93.
639 
640 config RTC_DRV_M41T94
641         tristate "ST M41T94"
642         help
643           If you say yes here you will get support for the
644           ST M41T94 SPI RTC chip.
645 
646           This driver can also be built as a module. If so, the module
647           will be called rtc-m41t94.
648 
649 config RTC_DRV_DS1305
650         tristate "Dallas/Maxim DS1305/DS1306"
651         help
652           Select this driver to get support for the Dallas/Maxim DS1305
653           and DS1306 real time clock chips. These support a trickle
654           charger, alarms, and NVRAM in addition to the clock.
655 
656           This driver can also be built as a module. If so, the module
657           will be called rtc-ds1305.
658 
659 config RTC_DRV_DS1343
660         select REGMAP_SPI
661         tristate "Dallas/Maxim DS1343/DS1344"
662         help
663           If you say yes here you get support for the
664           Dallas/Maxim DS1343 and DS1344 real time clock chips.
665           Support for trickle charger, alarm is provided.
666 
667           This driver can also be built as a module. If so, the module
668           will be called rtc-ds1343.
669 
670 config RTC_DRV_DS1347
671         tristate "Dallas/Maxim DS1347"
672         help
673           If you say yes here you get support for the
674           Dallas/Maxim DS1347 chips.
675 
676           This driver only supports the RTC feature, and not other chip
677           features such as alarms.
678 
679           This driver can also be built as a module. If so, the module
680           will be called rtc-ds1347.
681 
682 config RTC_DRV_DS1390
683         tristate "Dallas/Maxim DS1390/93/94"
684         help
685           If you say yes here you get support for the
686           Dallas/Maxim DS1390/93/94 chips.
687 
688           This driver supports the RTC feature and trickle charging but not
689           other chip features such as alarms.
690 
691           This driver can also be built as a module. If so, the module
692           will be called rtc-ds1390.
693 
694 config RTC_DRV_MAX6902
695         tristate "Maxim MAX6902"
696         help
697           If you say yes here you will get support for the
698           Maxim MAX6902 SPI RTC chip.
699 
700           This driver can also be built as a module. If so, the module
701           will be called rtc-max6902.
702 
703 config RTC_DRV_R9701
704         tristate "Epson RTC-9701JE"
705         help
706           If you say yes here you will get support for the
707           Epson RTC-9701JE SPI RTC chip.
708 
709           This driver can also be built as a module. If so, the module
710           will be called rtc-r9701.
711 
712 config RTC_DRV_RS5C348
713         tristate "Ricoh RS5C348A/B"
714         help
715           If you say yes here you get support for the
716           Ricoh RS5C348A and RS5C348B RTC chips.
717 
718           This driver can also be built as a module. If so, the module
719           will be called rtc-rs5c348.
720 
721 config RTC_DRV_DS3234
722         tristate "Maxim/Dallas DS3234"
723         help
724           If you say yes here you get support for the
725           Maxim/Dallas DS3234 SPI RTC chip.
726 
727           This driver can also be built as a module. If so, the module
728           will be called rtc-ds3234.
729 
730 config RTC_DRV_PCF2123
731         tristate "NXP PCF2123"
732         help
733           If you say yes here you get support for the NXP PCF2123
734           RTC chip.
735 
736           This driver can also be built as a module. If so, the module
737           will be called rtc-pcf2123.
738 
739 config RTC_DRV_RX4581
740         tristate "Epson RX-4581"
741         help
742           If you say yes here you will get support for the Epson RX-4581.
743 
744           This driver can also be built as a module. If so the module
745           will be called rtc-rx4581.
746 
747 config RTC_DRV_MCP795
748         tristate "Microchip MCP795"
749         help
750           If you say yes here you will get support for the Microchip MCP795.
751 
752           This driver can also be built as a module. If so the module
753           will be called rtc-mcp795.
754 
755 endif # SPI_MASTER
756 
757 comment "Platform RTC drivers"
758 
759 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
760 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
761 # global rtc_lock ... it's not yet just another platform_device.
762 
763 config RTC_DRV_CMOS
764         tristate "PC-style 'CMOS'"
765         depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
766         default y if X86
767         help
768           Say "yes" here to get direct support for the real time clock
769           found in every PC or ACPI-based system, and some other boards.
770           Specifically the original MC146818, compatibles like those in
771           PC south bridges, the DS12887 or M48T86, some multifunction
772           or LPC bus chips, and so on.
773 
774           Your system will need to define the platform device used by
775           this driver, otherwise it won't be accessible. This means
776           you can safely enable this driver if you don't know whether
777           or not your board has this kind of hardware.
778 
779           This driver can also be built as a module. If so, the module
780           will be called rtc-cmos.
781 
782 config RTC_DRV_ALPHA
783         bool "Alpha PC-style CMOS"
784         depends on ALPHA
785         default y
786         help
787           Direct support for the real-time clock found on every Alpha
788           system, specifically MC146818 compatibles.  If in doubt, say Y.
789 
790 config RTC_DRV_VRTC
791         tristate "Virtual RTC for Intel MID platforms"
792         depends on X86_INTEL_MID
793         default y if X86_INTEL_MID
794 
795         help
796         Say "yes" here to get direct support for the real time clock
797         found on Moorestown platforms. The VRTC is a emulated RTC that
798         derives its clock source from a real RTC in the PMIC. The MC146818
799         style programming interface is mostly conserved, but any
800         updates are done via IPC calls to the system controller FW.
801 
802 config RTC_DRV_DS1216
803         tristate "Dallas DS1216"
804         depends on SNI_RM
805         help
806           If you say yes here you get support for the Dallas DS1216 RTC chips.
807 
808 config RTC_DRV_DS1286
809         tristate "Dallas DS1286"
810         depends on HAS_IOMEM
811         help
812           If you say yes here you get support for the Dallas DS1286 RTC chips.
813 
814 config RTC_DRV_DS1302
815         tristate "Dallas DS1302"
816         depends on SH_SECUREEDGE5410
817         help
818           If you say yes here you get support for the Dallas DS1302 RTC chips.
819 
820 config RTC_DRV_DS1511
821         tristate "Dallas DS1511"
822         depends on HAS_IOMEM
823         help
824           If you say yes here you get support for the
825           Dallas DS1511 timekeeping/watchdog chip.
826 
827           This driver can also be built as a module. If so, the module
828           will be called rtc-ds1511.
829 
830 config RTC_DRV_DS1553
831         tristate "Maxim/Dallas DS1553"
832         depends on HAS_IOMEM
833         help
834           If you say yes here you get support for the
835           Maxim/Dallas DS1553 timekeeping chip.
836 
837           This driver can also be built as a module. If so, the module
838           will be called rtc-ds1553.
839 
840 config RTC_DRV_DS1685_FAMILY
841         tristate "Dallas/Maxim DS1685 Family"
842         help
843           If you say yes here you get support for the Dallas/Maxim DS1685
844           family of real time chips.  This family includes the DS1685/DS1687,
845           DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
846           DS17885/DS17887 chips.
847 
848           This driver can also be built as a module. If so, the module
849           will be called rtc-ds1685.
850 
851 choice
852         prompt "Subtype"
853         depends on RTC_DRV_DS1685_FAMILY
854         default RTC_DRV_DS1685
855 
856 config RTC_DRV_DS1685
857         bool "DS1685/DS1687"
858         help
859           This enables support for the Dallas/Maxim DS1685/DS1687 real time
860           clock chip.
861 
862           This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
863           systems, as well as EPPC-405-UC modules by electronic system design
864           GmbH.
865 
866 config RTC_DRV_DS1689
867         bool "DS1689/DS1693"
868         help
869           This enables support for the Dallas/Maxim DS1689/DS1693 real time
870           clock chip.
871 
872           This is an older RTC chip, supplanted by the DS1685/DS1687 above,
873           which supports a few minor features such as Vcc, Vbat, and Power
874           Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
875 
876           It also works for the even older DS1688/DS1691 RTC chips, which are
877           virtually the same and carry the same model number.  Both chips
878           have 114 bytes of user NVRAM.
879 
880 config RTC_DRV_DS17285
881         bool "DS17285/DS17287"
882         help
883           This enables support for the Dallas/Maxim DS17285/DS17287 real time
884           clock chip.
885 
886           This chip features 2kb of extended NV-SRAM.  It may possibly be
887           found in some SGI O2 systems (rare).
888 
889 config RTC_DRV_DS17485
890         bool "DS17485/DS17487"
891         help
892           This enables support for the Dallas/Maxim DS17485/DS17487 real time
893           clock chip.
894 
895           This chip features 4kb of extended NV-SRAM.
896 
897 config RTC_DRV_DS17885
898         bool "DS17885/DS17887"
899         help
900           This enables support for the Dallas/Maxim DS17885/DS17887 real time
901           clock chip.
902 
903           This chip features 8kb of extended NV-SRAM.
904 
905 endchoice
906 
907 config RTC_DS1685_PROC_REGS
908         bool "Display register values in /proc"
909         depends on RTC_DRV_DS1685_FAMILY && PROC_FS
910         help
911           Enable this to display a readout of all of the RTC registers in
912           /proc/drivers/rtc.  Keep in mind that this can potentially lead
913           to lost interrupts, as reading Control Register C will clear
914           all pending IRQ flags.
915 
916           Unless you are debugging this driver, choose N.
917 
918 config RTC_DS1685_SYSFS_REGS
919         bool "SysFS access to RTC register bits"
920         depends on RTC_DRV_DS1685_FAMILY && SYSFS
921         help
922           Enable this to provide access to the RTC control register bits
923           in /sys.  Some of the bits are read-write, others are read-only.
924 
925           Keep in mind that reading Control C's bits automatically clears
926           all pending IRQ flags - this can cause lost interrupts.
927 
928           If you know that you need access to these bits, choose Y, Else N.
929 
930 config RTC_DRV_DS1742
931         tristate "Maxim/Dallas DS1742/1743"
932         depends on HAS_IOMEM
933         help
934           If you say yes here you get support for the
935           Maxim/Dallas DS1742/1743 timekeeping chip.
936 
937           This driver can also be built as a module. If so, the module
938           will be called rtc-ds1742.
939 
940 config RTC_DRV_DS2404
941         tristate "Maxim/Dallas DS2404"
942         help
943           If you say yes here you get support for the
944           Dallas DS2404 RTC chip.
945 
946           This driver can also be built as a module. If so, the module
947           will be called rtc-ds2404.
948 
949 config RTC_DRV_DA9052
950         tristate "Dialog DA9052/DA9053 RTC"
951         depends on PMIC_DA9052
952         help
953           Say y here to support the RTC driver for Dialog Semiconductor
954           DA9052-BC and DA9053-AA/Bx PMICs.
955 
956 config RTC_DRV_DA9055
957         tristate "Dialog Semiconductor DA9055 RTC"
958         depends on MFD_DA9055
959         help
960           If you say yes here you will get support for the
961           RTC of the Dialog DA9055 PMIC.
962 
963           This driver can also be built as a module. If so, the module
964           will be called rtc-da9055
965 
966 config RTC_DRV_DA9063
967         tristate "Dialog Semiconductor DA9063/DA9062 RTC"
968         depends on MFD_DA9063 || MFD_DA9062
969         help
970           If you say yes here you will get support for the RTC subsystem
971           for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
972 
973           This driver can also be built as a module. If so, the module
974           will be called "rtc-da9063".
975 
976 config RTC_DRV_EFI
977         tristate "EFI RTC"
978         depends on EFI && !X86
979         help
980           If you say yes here you will get support for the EFI
981           Real Time Clock.
982 
983           This driver can also be built as a module. If so, the module
984           will be called rtc-efi.
985 
986 config RTC_DRV_STK17TA8
987         tristate "Simtek STK17TA8"
988         depends on HAS_IOMEM
989         help
990           If you say yes here you get support for the
991           Simtek STK17TA8 timekeeping chip.
992 
993           This driver can also be built as a module. If so, the module
994           will be called rtc-stk17ta8.
995 
996 config RTC_DRV_M48T86
997         tristate "ST M48T86/Dallas DS12887"
998         help
999           If you say Y here you will get support for the
1000           ST M48T86 and Dallas DS12887 RTC chips.
1001 
1002           This driver can also be built as a module. If so, the module
1003           will be called rtc-m48t86.
1004 
1005 config RTC_DRV_M48T35
1006         tristate "ST M48T35"
1007         depends on HAS_IOMEM
1008         help
1009           If you say Y here you will get support for the
1010           ST M48T35 RTC chip.
1011 
1012           This driver can also be built as a module, if so, the module
1013           will be called "rtc-m48t35".
1014 
1015 config RTC_DRV_M48T59
1016         tristate "ST M48T59/M48T08/M48T02"
1017         depends on HAS_IOMEM
1018         help
1019           If you say Y here you will get support for the
1020           ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1021 
1022           These chips are usually found in Sun SPARC and UltraSPARC
1023           workstations.
1024 
1025           This driver can also be built as a module, if so, the module
1026           will be called "rtc-m48t59".
1027 
1028 config RTC_DRV_MSM6242
1029         tristate "Oki MSM6242"
1030         depends on HAS_IOMEM
1031         help
1032           If you say yes here you get support for the Oki MSM6242
1033           timekeeping chip. It is used in some Amiga models (e.g. A2000).
1034 
1035           This driver can also be built as a module. If so, the module
1036           will be called rtc-msm6242.
1037 
1038 config RTC_DRV_BQ4802
1039         tristate "TI BQ4802"
1040         depends on HAS_IOMEM
1041         help
1042           If you say Y here you will get support for the TI
1043           BQ4802 RTC chip.
1044 
1045           This driver can also be built as a module. If so, the module
1046           will be called rtc-bq4802.
1047 
1048 config RTC_DRV_RP5C01
1049         tristate "Ricoh RP5C01"
1050         depends on HAS_IOMEM
1051         help
1052           If you say yes here you get support for the Ricoh RP5C01
1053           timekeeping chip. It is used in some Amiga models (e.g. A3000
1054           and A4000).
1055 
1056           This driver can also be built as a module. If so, the module
1057           will be called rtc-rp5c01.
1058 
1059 config RTC_DRV_V3020
1060         tristate "EM Microelectronic V3020"
1061         help
1062           If you say yes here you will get support for the
1063           EM Microelectronic v3020 RTC chip.
1064 
1065           This driver can also be built as a module. If so, the module
1066           will be called rtc-v3020.
1067 
1068 config RTC_DRV_WM831X
1069         tristate "Wolfson Microelectronics WM831x RTC"
1070         depends on MFD_WM831X
1071         help
1072           If you say yes here you will get support for the RTC subsystem
1073           of the Wolfson Microelectronics WM831X series PMICs.
1074 
1075           This driver can also be built as a module. If so, the module
1076           will be called "rtc-wm831x".
1077 
1078 config RTC_DRV_WM8350
1079         tristate "Wolfson Microelectronics WM8350 RTC"
1080         depends on MFD_WM8350
1081         help
1082           If you say yes here you will get support for the RTC subsystem
1083           of the Wolfson Microelectronics WM8350.
1084 
1085           This driver can also be built as a module. If so, the module
1086           will be called "rtc-wm8350".
1087 
1088 config RTC_DRV_SPEAR
1089         tristate "SPEAR ST RTC"
1090         depends on PLAT_SPEAR
1091         default y
1092         help
1093          If you say Y here you will get support for the RTC found on
1094          spear
1095 
1096 config RTC_DRV_PCF50633
1097         depends on MFD_PCF50633
1098         tristate "NXP PCF50633 RTC"
1099         help
1100           If you say yes here you get support for the RTC subsystem of the
1101           NXP PCF50633 used in embedded systems.
1102 
1103 config RTC_DRV_AB3100
1104         tristate "ST-Ericsson AB3100 RTC"
1105         depends on AB3100_CORE
1106         default y if AB3100_CORE
1107         help
1108           Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
1109           support. This chip contains a battery- and capacitor-backed RTC.
1110 
1111 config RTC_DRV_AB8500
1112         tristate "ST-Ericsson AB8500 RTC"
1113         depends on AB8500_CORE
1114         select RTC_INTF_DEV
1115         select RTC_INTF_DEV_UIE_EMUL
1116         help
1117           Select this to enable the ST-Ericsson AB8500 power management IC RTC
1118           support. This chip contains a battery- and capacitor-backed RTC.
1119 
1120 config RTC_DRV_NUC900
1121         tristate "NUC910/NUC920 RTC driver"
1122         depends on ARCH_W90X900
1123         help
1124           If you say yes here you get support for the RTC subsystem of the
1125           NUC910/NUC920 used in embedded systems.
1126 
1127 config RTC_DRV_OPAL
1128         tristate "IBM OPAL RTC driver"
1129         depends on PPC_POWERNV
1130         default y
1131         help
1132           If you say yes here you get support for the PowerNV platform RTC
1133           driver based on OPAL interfaces.
1134 
1135           This driver can also be built as a module. If so, the module
1136           will be called rtc-opal.
1137 
1138 config RTC_DRV_ZYNQMP
1139         tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1140         depends on OF
1141         help
1142           If you say yes here you get support for the RTC controller found on
1143           Xilinx Zynq Ultrascale+ MPSoC.
1144 
1145 comment "on-CPU RTC drivers"
1146 
1147 config RTC_DRV_DAVINCI
1148         tristate "TI DaVinci RTC"
1149         depends on ARCH_DAVINCI_DM365
1150         help
1151           If you say yes here you get support for the RTC on the
1152           DaVinci platforms (DM365).
1153 
1154           This driver can also be built as a module. If so, the module
1155           will be called rtc-davinci.
1156 
1157 config RTC_DRV_DIGICOLOR
1158         tristate "Conexant Digicolor RTC"
1159         depends on ARCH_DIGICOLOR
1160         help
1161           If you say yes here you get support for the RTC on Conexant
1162           Digicolor platforms. This currently includes the CX92755 SoC.
1163 
1164           This driver can also be built as a module. If so, the module
1165           will be called rtc-digicolor.
1166 
1167 config RTC_DRV_IMXDI
1168         tristate "Freescale IMX DryIce Real Time Clock"
1169         depends on ARCH_MXC
1170         help
1171            Support for Freescale IMX DryIce RTC
1172 
1173            This driver can also be built as a module, if so, the module
1174            will be called "rtc-imxdi".
1175 
1176 config RTC_DRV_OMAP
1177         tristate "TI OMAP Real Time Clock"
1178         depends on ARCH_OMAP || ARCH_DAVINCI
1179         help
1180           Say "yes" here to support the on chip real time clock
1181           present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1182 
1183           This driver can also be built as a module, if so, module
1184           will be called rtc-omap.
1185 
1186 config HAVE_S3C_RTC
1187         bool
1188         help
1189           This will include RTC support for Samsung SoCs. If
1190           you want to include RTC support for any machine, kindly
1191           select this in the respective mach-XXXX/Kconfig file.
1192 
1193 config RTC_DRV_S3C
1194         tristate "Samsung S3C series SoC RTC"
1195         depends on ARCH_S3C64XX || HAVE_S3C_RTC
1196         help
1197           RTC (Realtime Clock) driver for the clock inbuilt into the
1198           Samsung S3C24XX series of SoCs. This can provide periodic
1199           interrupt rates from 1Hz to 64Hz for user programs, and
1200           wakeup from Alarm.
1201 
1202           The driver currently supports the common features on all the
1203           S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1204           and S3C2442.
1205 
1206           This driver can also be build as a module. If so, the module
1207           will be called rtc-s3c.
1208 
1209 config RTC_DRV_EP93XX
1210         tristate "Cirrus Logic EP93XX"
1211         depends on ARCH_EP93XX
1212         help
1213           If you say yes here you get support for the
1214           RTC embedded in the Cirrus Logic EP93XX processors.
1215 
1216           This driver can also be built as a module. If so, the module
1217           will be called rtc-ep93xx.
1218 
1219 config RTC_DRV_SA1100
1220         tristate "SA11x0/PXA2xx/PXA910"
1221         depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1222         help
1223           If you say Y here you will get access to the real time clock
1224           built into your SA11x0 or PXA2xx CPU.
1225 
1226           To compile this driver as a module, choose M here: the
1227           module will be called rtc-sa1100.
1228 
1229 config RTC_DRV_SH
1230         tristate "SuperH On-Chip RTC"
1231         depends on SUPERH && HAVE_CLK
1232         help
1233           Say Y here to enable support for the on-chip RTC found in
1234           most SuperH processors.
1235 
1236           To compile this driver as a module, choose M here: the
1237           module will be called rtc-sh.
1238 
1239 config RTC_DRV_VR41XX
1240         tristate "NEC VR41XX"
1241         depends on CPU_VR41XX
1242         help
1243           If you say Y here you will get access to the real time clock
1244           built into your NEC VR41XX CPU.
1245 
1246           To compile this driver as a module, choose M here: the
1247           module will be called rtc-vr41xx.
1248 
1249 config RTC_DRV_PL030
1250         tristate "ARM AMBA PL030 RTC"
1251         depends on ARM_AMBA
1252         help
1253           If you say Y here you will get access to ARM AMBA
1254           PrimeCell PL030 RTC found on certain ARM SOCs.
1255 
1256           To compile this driver as a module, choose M here: the
1257           module will be called rtc-pl030.
1258 
1259 config RTC_DRV_PL031
1260         tristate "ARM AMBA PL031 RTC"
1261         depends on ARM_AMBA
1262         help
1263           If you say Y here you will get access to ARM AMBA
1264           PrimeCell PL031 RTC found on certain ARM SOCs.
1265 
1266           To compile this driver as a module, choose M here: the
1267           module will be called rtc-pl031.
1268 
1269 config RTC_DRV_AT32AP700X
1270         tristate "AT32AP700X series RTC"
1271         depends on PLATFORM_AT32AP
1272         help
1273           Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1274           AT32AP700x family processors.
1275 
1276 config RTC_DRV_AT91RM9200
1277         tristate "AT91RM9200 or some AT91SAM9 RTC"
1278         depends on ARCH_AT91
1279         help
1280           Driver for the internal RTC (Realtime Clock) module found on
1281           Atmel AT91RM9200's and some  AT91SAM9 chips. On AT91SAM9 chips
1282           this is powered by the backup power supply.
1283 
1284 config RTC_DRV_AT91SAM9
1285         tristate "AT91SAM9 RTT as RTC"
1286         depends on ARCH_AT91
1287         select MFD_SYSCON
1288         help
1289           Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1290           can be used as an RTC thanks to the backup power supply (e.g. a
1291           small coin cell battery) which keeps this block and the GPBR
1292           (General Purpose Backup Registers) block powered when the device
1293           is shutdown.
1294           Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1295           probably want to use the real RTC block instead of the "RTT as an
1296           RTC" driver.
1297 
1298 config RTC_DRV_AU1XXX
1299         tristate "Au1xxx Counter0 RTC support"
1300         depends on MIPS_ALCHEMY
1301         help
1302           This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1303           counter) to be used as a RTC.
1304 
1305           This driver can also be built as a module. If so, the module
1306           will be called rtc-au1xxx.
1307 
1308 config RTC_DRV_BFIN
1309         tristate "Blackfin On-Chip RTC"
1310         depends on BLACKFIN && !BF561
1311         help
1312           If you say yes here you will get support for the
1313           Blackfin On-Chip Real Time Clock.
1314 
1315           This driver can also be built as a module. If so, the module
1316           will be called rtc-bfin.
1317 
1318 config RTC_DRV_RS5C313
1319         tristate "Ricoh RS5C313"
1320         depends on SH_LANDISK
1321         help
1322           If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1323 
1324 config RTC_DRV_GENERIC
1325         tristate "Generic RTC support"
1326         # Please consider writing a new RTC driver instead of using the generic
1327         # RTC abstraction
1328         depends on PARISC || M68K || PPC || SUPERH32
1329         help
1330           Say Y or M here to enable RTC support on systems using the generic
1331           RTC abstraction. If you do not know what you are doing, you should
1332           just say Y.
1333 
1334 config RTC_DRV_PXA
1335        tristate "PXA27x/PXA3xx"
1336        depends on ARCH_PXA
1337        select RTC_DRV_SA1100
1338        help
1339          If you say Y here you will get access to the real time clock
1340          built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1341          consisting of an SA1100 compatible RTC and the extended PXA RTC.
1342 
1343          This RTC driver uses PXA RTC registers available since pxa27x
1344          series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1345 
1346 config RTC_DRV_VT8500
1347         tristate "VIA/WonderMedia 85xx SoC RTC"
1348         depends on ARCH_VT8500
1349         help
1350           If you say Y here you will get access to the real time clock
1351           built into your VIA VT8500 SoC or its relatives.
1352 
1353 
1354 config RTC_DRV_SUN4V
1355         bool "SUN4V Hypervisor RTC"
1356         depends on SPARC64
1357         help
1358           If you say Y here you will get support for the Hypervisor
1359           based RTC on SUN4V systems.
1360 
1361 config RTC_DRV_SUN6I
1362         tristate "Allwinner A31 RTC"
1363         depends on MACH_SUN6I || MACH_SUN8I
1364         help
1365           If you say Y here you will get support for the RTC found on
1366           Allwinner A31.
1367 
1368 config RTC_DRV_SUNXI
1369         tristate "Allwinner sun4i/sun7i RTC"
1370         depends on MACH_SUN4I || MACH_SUN7I
1371         help
1372           If you say Y here you will get support for the RTC found on
1373           Allwinner A10/A20.
1374 
1375 config RTC_DRV_STARFIRE
1376         bool "Starfire RTC"
1377         depends on SPARC64
1378         help
1379           If you say Y here you will get support for the RTC found on
1380           Starfire systems.
1381 
1382 config RTC_DRV_TX4939
1383         tristate "TX4939 SoC"
1384         depends on SOC_TX4939
1385         help
1386           Driver for the internal RTC (Realtime Clock) module found on
1387           Toshiba TX4939 SoC.
1388 
1389 config RTC_DRV_MV
1390         tristate "Marvell SoC RTC"
1391         depends on ARCH_DOVE || ARCH_MVEBU
1392         help
1393           If you say yes here you will get support for the in-chip RTC
1394           that can be found in some of Marvell's SoC devices, such as
1395           the Kirkwood 88F6281 and 88F6192.
1396 
1397           This driver can also be built as a module. If so, the module
1398           will be called rtc-mv.
1399 
1400 config RTC_DRV_ARMADA38X
1401         tristate "Armada 38x Marvell SoC RTC"
1402         depends on ARCH_MVEBU
1403         help
1404           If you say yes here you will get support for the in-chip RTC
1405           that can be found in the Armada 38x Marvell's SoC device
1406 
1407           This driver can also be built as a module. If so, the module
1408           will be called armada38x-rtc.
1409 
1410 config RTC_DRV_GEMINI
1411         tristate "Gemini SoC RTC"
1412         depends on ARCH_GEMINI || COMPILE_TEST
1413         depends on HAS_IOMEM
1414         help
1415           If you say Y here you will get support for the
1416           RTC found on Gemini SoC's.
1417 
1418           This driver can also be built as a module. If so, the module
1419           will be called rtc-gemini.
1420 
1421 config RTC_DRV_PS3
1422         tristate "PS3 RTC"
1423         depends on PPC_PS3
1424         help
1425           If you say yes here you will get support for the RTC on PS3.
1426 
1427           This driver can also be built as a module. If so, the module
1428           will be called rtc-ps3.
1429 
1430 config RTC_DRV_COH901331
1431         tristate "ST-Ericsson COH 901 331 RTC"
1432         depends on ARCH_U300
1433         help
1434           If you say Y here you will get access to ST-Ericsson
1435           COH 901 331 RTC clock found in some ST-Ericsson Mobile
1436           Platforms.
1437 
1438           This driver can also be built as a module. If so, the module
1439           will be called "rtc-coh901331".
1440 
1441 
1442 config RTC_DRV_STMP
1443         tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1444         depends on ARCH_MXS
1445         select STMP_DEVICE
1446         help
1447           If you say yes here you will get support for the onboard
1448           STMP3xxx/i.MX23/i.MX28 RTC.
1449 
1450           This driver can also be built as a module. If so, the module
1451           will be called rtc-stmp3xxx.
1452 
1453 config RTC_DRV_PCAP
1454         tristate "PCAP RTC"
1455         depends on EZX_PCAP
1456         help
1457           If you say Y here you will get support for the RTC found on
1458           the PCAP2 ASIC used on some Motorola phones.
1459 
1460 config RTC_DRV_MC13XXX
1461         depends on MFD_MC13XXX
1462         tristate "Freescale MC13xxx RTC"
1463         help
1464           This enables support for the RTCs found on Freescale's PMICs
1465           MC13783 and MC13892.
1466 
1467 config RTC_DRV_MPC5121
1468         tristate "Freescale MPC5121 built-in RTC"
1469         depends on PPC_MPC512x || PPC_MPC52xx
1470         help
1471           If you say yes here you will get support for the
1472           built-in RTC on MPC5121 or on MPC5200.
1473 
1474           This driver can also be built as a module. If so, the module
1475           will be called rtc-mpc5121.
1476 
1477 config RTC_DRV_JZ4740
1478         tristate "Ingenic JZ4740 SoC"
1479         depends on MACH_JZ4740
1480         help
1481           If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1482           controller.
1483 
1484           This driver can also be buillt as a module. If so, the module
1485           will be called rtc-jz4740.
1486 
1487 config RTC_DRV_LPC24XX
1488         tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1489         depends on ARCH_LPC18XX || COMPILE_TEST
1490         depends on OF && HAS_IOMEM
1491         help
1492           This enables support for the NXP RTC found which can be found on
1493           NXP LPC178x/18xx/408x/43xx devices.
1494 
1495           If you have one of the devices above enable this driver to use
1496           the hardware RTC. This driver can also be buillt as a module. If
1497           so, the module will be called rtc-lpc24xx.
1498 
1499 config RTC_DRV_LPC32XX
1500         depends on ARCH_LPC32XX
1501         tristate "NXP LPC32XX RTC"
1502         help
1503           This enables support for the NXP RTC in the LPC32XX
1504 
1505           This driver can also be buillt as a module. If so, the module
1506           will be called rtc-lpc32xx.
1507 
1508 config RTC_DRV_PM8XXX
1509         tristate "Qualcomm PMIC8XXX RTC"
1510         depends on MFD_PM8XXX || MFD_SPMI_PMIC
1511         help
1512           If you say yes here you get support for the
1513           Qualcomm PMIC8XXX RTC.
1514 
1515           To compile this driver as a module, choose M here: the
1516           module will be called rtc-pm8xxx.
1517 
1518 config RTC_DRV_TEGRA
1519         tristate "NVIDIA Tegra Internal RTC driver"
1520         depends on ARCH_TEGRA
1521         help
1522           If you say yes here you get support for the
1523           Tegra 200 series internal RTC module.
1524 
1525           This drive can also be built as a module. If so, the module
1526           will be called rtc-tegra.
1527 
1528 config RTC_DRV_TILE
1529         tristate "Tilera hypervisor RTC support"
1530         depends on TILE
1531         help
1532           Enable support for the Linux driver side of the Tilera
1533           hypervisor's real-time clock interface.
1534 
1535 config RTC_DRV_PUV3
1536         tristate "PKUnity v3 RTC support"
1537         depends on ARCH_PUV3
1538         help
1539           This enables support for the RTC in the PKUnity-v3 SoCs.
1540 
1541           This drive can also be built as a module. If so, the module
1542           will be called rtc-puv3.
1543 
1544 config RTC_DRV_LOONGSON1
1545         tristate "loongson1 RTC support"
1546         depends on MACH_LOONGSON32
1547         help
1548           This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1549           counter) to be used as a RTC.
1550 
1551           This driver can also be built as a module. If so, the module
1552           will be called rtc-ls1x.
1553 
1554 config RTC_DRV_MXC
1555         tristate "Freescale MXC Real Time Clock"
1556         depends on ARCH_MXC
1557         help
1558            If you say yes here you get support for the Freescale MXC
1559            RTC module.
1560 
1561            This driver can also be built as a module, if so, the module
1562            will be called "rtc-mxc".
1563 
1564 config RTC_DRV_SNVS
1565         tristate "Freescale SNVS RTC support"
1566         select REGMAP_MMIO
1567         depends on HAS_IOMEM
1568         depends on OF
1569         help
1570            If you say yes here you get support for the Freescale SNVS
1571            Low Power (LP) RTC module.
1572 
1573            This driver can also be built as a module, if so, the module
1574            will be called "rtc-snvs".
1575 
1576 config RTC_DRV_SIRFSOC
1577         tristate "SiRFSOC RTC"
1578         depends on ARCH_SIRF
1579         help
1580           Say "yes" here to support the real time clock on SiRF SOC chips.
1581           This driver can also be built as a module called rtc-sirfsoc.
1582 
1583 config RTC_DRV_ST_LPC
1584         tristate "STMicroelectronics LPC RTC"
1585         depends on ARCH_STI
1586         depends on OF
1587         help
1588           Say Y here to include STMicroelectronics Low Power Controller
1589           (LPC) based RTC support.
1590 
1591           To compile this driver as a module, choose M here: the
1592           module will be called rtc-st-lpc.
1593 
1594 config RTC_DRV_MOXART
1595         tristate "MOXA ART RTC"
1596         depends on ARCH_MOXART || COMPILE_TEST
1597         help
1598            If you say yes here you get support for the MOXA ART
1599            RTC module.
1600 
1601            This driver can also be built as a module. If so, the module
1602            will be called rtc-moxart
1603 
1604 config RTC_DRV_MT6397
1605         tristate "Mediatek Real Time Clock driver"
1606         depends on MFD_MT6397 || COMPILE_TEST
1607         help
1608           This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
1609           MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1610           Mediatek(R) RTC driver.
1611 
1612           If you want to use Mediatek(R) RTC interface, select Y or M here.
1613 
1614 config RTC_DRV_XGENE
1615         tristate "APM X-Gene RTC"
1616         depends on HAS_IOMEM
1617         depends on ARCH_XGENE || COMPILE_TEST
1618         help
1619           If you say yes here you get support for the APM X-Gene SoC real time
1620           clock.
1621 
1622           This driver can also be built as a module, if so, the module
1623           will be called "rtc-xgene".
1624 
1625 comment "HID Sensor RTC drivers"
1626 
1627 config RTC_DRV_HID_SENSOR_TIME
1628         tristate "HID Sensor Time"
1629         depends on USB_HID
1630         select IIO
1631         select HID_SENSOR_HUB
1632         select HID_SENSOR_IIO_COMMON
1633         help
1634           Say yes here to build support for the HID Sensors of type Time.
1635           This drivers makes such sensors available as RTCs.
1636 
1637           If this driver is compiled as a module, it will be named
1638           rtc-hid-sensor-time.
1639 
1640 
1641 endif # RTC_CLASS

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us