Version:  2.6.34 2.6.35 2.6.36 2.6.37 2.6.38 2.6.39 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14

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_SYSTOHC
 29         bool "Set the RTC time based on NTP synchronization"
 30         default y
 31         help
 32           If you say yes here, the system time (wall clock) will be stored
 33           in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
 34           minutes if userspace reports synchronized NTP status.
 35 
 36 config RTC_HCTOSYS_DEVICE
 37         string "RTC used to set the system time"
 38         depends on RTC_HCTOSYS = y || RTC_SYSTOHC = y
 39         default "rtc0"
 40         help
 41           The RTC device that will be used to (re)initialize the system
 42           clock, usually rtc0. Initialization is done when the system
 43           starts up, and when it resumes from a low power state. This
 44           device should record time in UTC, since the kernel won't do
 45           timezone correction.
 46 
 47           The driver for this RTC device must be loaded before late_initcall
 48           functions run, so it must usually be statically linked.
 49 
 50           This clock should be battery-backed, so that it reads the correct
 51           time when the system boots from a power-off state. Otherwise, your
 52           system will need an external clock source (like an NTP server).
 53 
 54           If the clock you specify here is not battery backed, it may still
 55           be useful to reinitialize system time when resuming from system
 56           sleep states. Do not specify an RTC here unless it stays powered
 57           during all this system's supported sleep states.
 58 
 59 config RTC_DEBUG
 60         bool "RTC debug support"
 61         help
 62           Say yes here to enable debugging support in the RTC framework
 63           and individual RTC drivers.
 64 
 65 comment "RTC interfaces"
 66 
 67 config RTC_INTF_SYSFS
 68         boolean "/sys/class/rtc/rtcN (sysfs)"
 69         depends on SYSFS
 70         default RTC_CLASS
 71         help
 72           Say yes here if you want to use your RTCs using sysfs interfaces,
 73           /sys/class/rtc/rtc0 through /sys/.../rtcN.
 74 
 75           If unsure, say Y.
 76 
 77 config RTC_INTF_PROC
 78         boolean "/proc/driver/rtc (procfs for rtcN)"
 79         depends on PROC_FS
 80         default RTC_CLASS
 81         help
 82           Say yes here if you want to use your system clock RTC through
 83           the proc interface, /proc/driver/rtc.
 84           Other RTCs will not be available through that API.
 85           If there is no RTC for the system clock, then the first RTC(rtc0)
 86           is used by default.
 87 
 88           If unsure, say Y.
 89 
 90 config RTC_INTF_DEV
 91         boolean "/dev/rtcN (character devices)"
 92         default RTC_CLASS
 93         help
 94           Say yes here if you want to use your RTCs using the /dev
 95           interfaces, which "udev" sets up as /dev/rtc0 through
 96           /dev/rtcN.
 97 
 98           You may want to set up a symbolic link so one of these
 99           can be accessed as /dev/rtc, which is a name
100           expected by "hwclock" and some other programs. Recent
101           versions of "udev" are known to set up the symlink for you.
102 
103           If unsure, say Y.
104 
105 config RTC_INTF_DEV_UIE_EMUL
106         bool "RTC UIE emulation on dev interface"
107         depends on RTC_INTF_DEV
108         help
109           Provides an emulation for RTC_UIE if the underlying rtc chip
110           driver does not expose RTC_UIE ioctls. Those requests generate
111           once-per-second update interrupts, used for synchronization.
112 
113           The emulation code will read the time from the hardware
114           clock several times per second, please enable this option
115           only if you know that you really need it.
116 
117 config RTC_DRV_TEST
118         tristate "Test driver/device"
119         help
120           If you say yes here you get support for the
121           RTC test driver. It's a software RTC which can be
122           used to test the RTC subsystem APIs. It gets
123           the time from the system clock.
124           You want this driver only if you are doing development
125           on the RTC subsystem. Please read the source code
126           for further details.
127 
128           This driver can also be built as a module. If so, the module
129           will be called rtc-test.
130 
131 comment "I2C RTC drivers"
132         depends on I2C
133 
134 if I2C
135 
136 config RTC_DRV_88PM860X
137         tristate "Marvell 88PM860x"
138         depends on I2C && MFD_88PM860X
139         help
140           If you say yes here you get support for RTC function in Marvell
141           88PM860x chips.
142 
143           This driver can also be built as a module. If so, the module
144           will be called rtc-88pm860x.
145 
146 config RTC_DRV_88PM80X
147         tristate "Marvell 88PM80x"
148         depends on I2C && MFD_88PM800
149         help
150           If you say yes here you get support for RTC function in Marvell
151           88PM80x chips.
152 
153           This driver can also be built as a module. If so, the module
154           will be called rtc-88pm80x.
155 
156 config RTC_DRV_AS3722
157         tristate "ams AS3722 RTC driver"
158         depends on MFD_AS3722
159         help
160           If you say yes here you get support for the RTC of ams AS3722 PMIC
161           chips.
162 
163           This driver can also be built as a module. If so, the module
164           will be called rtc-as3722.
165 
166 config RTC_DRV_DS1307
167         tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
168         help
169           If you say yes here you get support for various compatible RTC
170           chips (often with battery backup) connected with I2C. This driver
171           should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
172           EPSON RX-8025 and probably other chips. In some cases the RTC
173           must already have been initialized (by manufacturing or a
174           bootloader).
175 
176           The first seven registers on these chips hold an RTC, and other
177           registers may add features such as NVRAM, a trickle charger for
178           the RTC/NVRAM backup power, and alarms. NVRAM is visible in
179           sysfs, but other chip features may not be available.
180 
181           This driver can also be built as a module. If so, the module
182           will be called rtc-ds1307.
183 
184 config RTC_DRV_DS1374
185         tristate "Dallas/Maxim DS1374"
186         depends on I2C
187         help
188           If you say yes here you get support for Dallas Semiconductor
189           DS1374 real-time clock chips. If an interrupt is associated
190           with the device, the alarm functionality is supported.
191 
192           This driver can also be built as a module. If so, the module
193           will be called rtc-ds1374.
194 
195 config RTC_DRV_DS1672
196         tristate "Dallas/Maxim DS1672"
197         help
198           If you say yes here you get support for the
199           Dallas/Maxim DS1672 timekeeping chip.
200 
201           This driver can also be built as a module. If so, the module
202           will be called rtc-ds1672.
203 
204 config RTC_DRV_DS3232
205         tristate "Dallas/Maxim DS3232"
206         depends on I2C
207         help
208           If you say yes here you get support for Dallas Semiconductor
209           DS3232 real-time clock chips. If an interrupt is associated
210           with the device, the alarm functionality is supported.
211 
212           This driver can also be built as a module.  If so, the module
213           will be called rtc-ds3232.
214 
215 config RTC_DRV_HYM8563
216         tristate "Haoyu Microelectronics HYM8563"
217         depends on I2C && OF
218         help
219           Say Y to enable support for the HYM8563 I2C RTC chip. Apart
220           from the usual rtc functions it provides a clock output of
221           up to 32kHz.
222 
223           This driver can also be built as a module. If so, the module
224           will be called rtc-hym8563.
225 
226 config RTC_DRV_LP8788
227         tristate "TI LP8788 RTC driver"
228         depends on MFD_LP8788
229         help
230           Say Y to enable support for the LP8788 RTC/ALARM driver.
231 
232 config RTC_DRV_MAX6900
233         tristate "Maxim MAX6900"
234         help
235           If you say yes here you will get support for the
236           Maxim MAX6900 I2C RTC chip.
237 
238           This driver can also be built as a module. If so, the module
239           will be called rtc-max6900.
240 
241 config RTC_DRV_MAX8907
242         tristate "Maxim MAX8907"
243         depends on MFD_MAX8907
244         help
245           If you say yes here you will get support for the
246           RTC of Maxim MAX8907 PMIC.
247 
248           This driver can also be built as a module. If so, the module
249           will be called rtc-max8907.
250 
251 config RTC_DRV_MAX8925
252         tristate "Maxim MAX8925"
253         depends on MFD_MAX8925
254         help
255           If you say yes here you will get support for the
256           RTC of Maxim MAX8925 PMIC.
257 
258           This driver can also be built as a module. If so, the module
259           will be called rtc-max8925.
260 
261 config RTC_DRV_MAX8998
262         tristate "Maxim MAX8998"
263         depends on MFD_MAX8998
264         help
265           If you say yes here you will get support for the
266           RTC of Maxim MAX8998 PMIC.
267 
268           This driver can also be built as a module. If so, the module
269           will be called rtc-max8998.
270 
271 config RTC_DRV_MAX8997
272         tristate "Maxim MAX8997"
273         depends on MFD_MAX8997
274         help
275           If you say yes here you will get support for the
276           RTC of Maxim MAX8997 PMIC.
277 
278           This driver can also be built as a module. If so, the module
279           will be called rtc-max8997.
280 
281 config RTC_DRV_MAX77686
282         tristate "Maxim MAX77686"
283         depends on MFD_MAX77686
284         help
285           If you say yes here you will get support for the
286           RTC of Maxim MAX77686 PMIC.
287 
288           This driver can also be built as a module. If so, the module
289           will be called rtc-max77686.
290 
291 config RTC_DRV_RS5C372
292         tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
293         help
294           If you say yes here you get support for the
295           Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
296 
297           This driver can also be built as a module. If so, the module
298           will be called rtc-rs5c372.
299 
300 config RTC_DRV_ISL1208
301         tristate "Intersil ISL1208"
302         help
303           If you say yes here you get support for the
304           Intersil ISL1208 RTC chip.
305 
306           This driver can also be built as a module. If so, the module
307           will be called rtc-isl1208.
308 
309 config RTC_DRV_ISL12022
310         tristate "Intersil ISL12022"
311         help
312           If you say yes here you get support for the
313           Intersil ISL12022 RTC chip.
314 
315           This driver can also be built as a module. If so, the module
316           will be called rtc-isl12022.
317 
318 config RTC_DRV_ISL12057
319        depends on I2C
320        select REGMAP_I2C
321        tristate "Intersil ISL12057"
322        help
323           If you say yes here you get support for the Intersil ISL12057
324           I2C RTC chip.
325 
326           This driver can also be built as a module. If so, the module
327           will be called rtc-isl12057.
328 
329 config RTC_DRV_X1205
330         tristate "Xicor/Intersil X1205"
331         help
332           If you say yes here you get support for the
333           Xicor/Intersil X1205 RTC chip.
334 
335           This driver can also be built as a module. If so, the module
336           will be called rtc-x1205.
337 
338 config RTC_DRV_PALMAS
339         tristate "TI Palmas RTC driver"
340         depends on MFD_PALMAS
341         help
342           If you say yes here you get support for the RTC of TI PALMA series PMIC
343           chips.
344 
345           This driver can also be built as a module. If so, the module
346           will be called rtc-palma.
347 
348 config RTC_DRV_PCF2127
349         tristate "NXP PCF2127"
350         help
351           If you say yes here you get support for the NXP PCF2127/29 RTC
352           chips.
353 
354           This driver can also be built as a module. If so, the module
355           will be called rtc-pcf2127.
356 
357 config RTC_DRV_PCF8523
358         tristate "NXP PCF8523"
359         help
360           If you say yes here you get support for the NXP PCF8523 RTC
361           chips.
362 
363           This driver can also be built as a module. If so, the module
364           will be called rtc-pcf8523.
365 
366 config RTC_DRV_PCF8563
367         tristate "Philips PCF8563/Epson RTC8564"
368         help
369           If you say yes here you get support for the
370           Philips PCF8563 RTC chip. The Epson RTC8564
371           should work as well.
372 
373           This driver can also be built as a module. If so, the module
374           will be called rtc-pcf8563.
375 
376 config RTC_DRV_PCF8583
377         tristate "Philips PCF8583"
378         help
379           If you say yes here you get support for the Philips PCF8583
380           RTC chip found on Acorn RiscPCs. This driver supports the
381           platform specific method of retrieving the current year from
382           the RTC's SRAM. It will work on other platforms with the same
383           chip, but the year will probably have to be tweaked.
384 
385           This driver can also be built as a module. If so, the module
386           will be called rtc-pcf8583.
387 
388 config RTC_DRV_M41T80
389         tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
390         help
391           If you say Y here you will get support for the ST M41T60
392           and M41T80 RTC chips series. Currently, the following chips are
393           supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
394           M41ST85, and M41ST87.
395 
396           This driver can also be built as a module. If so, the module
397           will be called rtc-m41t80.
398 
399 config RTC_DRV_M41T80_WDT
400         bool "ST M41T65/M41T80 series RTC watchdog timer"
401         depends on RTC_DRV_M41T80
402         help
403           If you say Y here you will get support for the
404           watchdog timer in the ST M41T60 and M41T80 RTC chips series.
405 
406 config RTC_DRV_BQ32K
407         tristate "TI BQ32000"
408         help
409           If you say Y here you will get support for the TI
410           BQ32000 I2C RTC chip.
411 
412           This driver can also be built as a module. If so, the module
413           will be called rtc-bq32k.
414 
415 config RTC_DRV_DM355EVM
416         tristate "TI DaVinci DM355 EVM RTC"
417         depends on MFD_DM355EVM_MSP
418         help
419           Supports the RTC firmware in the MSP430 on the DM355 EVM.
420 
421 config RTC_DRV_TWL92330
422         boolean "TI TWL92330/Menelaus"
423         depends on MENELAUS
424         help
425           If you say yes here you get support for the RTC on the
426           TWL92330 "Menelaus" power management chip, used with OMAP2
427           platforms. The support is integrated with the rest of
428           the Menelaus driver; it's not separate module.
429 
430 config RTC_DRV_TWL4030
431         tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
432         depends on TWL4030_CORE
433         help
434           If you say yes here you get support for the RTC on the
435           TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
436 
437           This driver can also be built as a module. If so, the module
438           will be called rtc-twl.
439 
440 config RTC_DRV_TPS6586X
441         tristate "TI TPS6586X RTC driver"
442         depends on MFD_TPS6586X
443         help
444           TI Power Management IC TPS6586X supports RTC functionality
445           along with alarm. This driver supports the RTC driver for
446           the TPS6586X RTC module.
447 
448 config RTC_DRV_TPS65910
449         tristate "TI TPS65910 RTC driver"
450         depends on RTC_CLASS && MFD_TPS65910
451         help
452           If you say yes here you get support for the RTC on the
453           TPS65910 chips.
454 
455           This driver can also be built as a module. If so, the module
456           will be called rtc-tps65910.
457 
458 config RTC_DRV_TPS80031
459         tristate "TI TPS80031/TPS80032 RTC driver"
460         depends on MFD_TPS80031
461         help
462           TI Power Management IC TPS80031 supports RTC functionality
463           along with alarm. This driver supports the RTC driver for
464           the TPS80031 RTC module.
465 
466 config RTC_DRV_RC5T583
467         tristate "RICOH 5T583 RTC driver"
468         depends on MFD_RC5T583
469         help
470           If you say yes here you get support for the RTC on the
471           RICOH 5T583 chips.
472 
473           This driver can also be built as a module. If so, the module
474           will be called rtc-rc5t583.
475 
476 config RTC_DRV_S35390A
477         tristate "Seiko Instruments S-35390A"
478         select BITREVERSE
479         help
480           If you say yes here you will get support for the Seiko
481           Instruments S-35390A.
482 
483           This driver can also be built as a module. If so the module
484           will be called rtc-s35390a.
485 
486 config RTC_DRV_FM3130
487         tristate "Ramtron FM3130"
488         help
489           If you say Y here you will get support for the
490           Ramtron FM3130 RTC chips.
491           Ramtron FM3130 is a chip with two separate devices inside,
492           RTC clock and FRAM. This driver provides only RTC functionality.
493 
494           This driver can also be built as a module. If so the module
495           will be called rtc-fm3130.
496 
497 config RTC_DRV_RX8581
498         tristate "Epson RX-8581"
499         help
500           If you say yes here you will get support for the Epson RX-8581.
501 
502           This driver can also be built as a module. If so the module
503           will be called rtc-rx8581.
504 
505 config RTC_DRV_RX8025
506         tristate "Epson RX-8025SA/NB"
507         help
508           If you say yes here you get support for the Epson
509           RX-8025SA/NB RTC chips.
510 
511           This driver can also be built as a module. If so, the module
512           will be called rtc-rx8025.
513 
514 config RTC_DRV_EM3027
515         tristate "EM Microelectronic EM3027"
516         help
517           If you say yes here you get support for the EM
518           Microelectronic EM3027 RTC chips.
519 
520           This driver can also be built as a module. If so, the module
521           will be called rtc-em3027.
522 
523 config RTC_DRV_RV3029C2
524         tristate "Micro Crystal RTC"
525         help
526           If you say yes here you get support for the Micro Crystal
527           RV3029-C2 RTC chips.
528 
529           This driver can also be built as a module. If so, the module
530           will be called rtc-rv3029c2.
531 
532 config RTC_DRV_S5M
533         tristate "Samsung S5M series"
534         depends on MFD_SEC_CORE
535         help
536           If you say yes here you will get support for the
537           RTC of Samsung S5M PMIC series.
538 
539           This driver can also be built as a module. If so, the module
540           will be called rtc-s5m.
541 
542 endif # I2C
543 
544 comment "SPI RTC drivers"
545 
546 if SPI_MASTER
547 
548 config RTC_DRV_M41T93
549         tristate "ST M41T93"
550         help
551           If you say yes here you will get support for the
552           ST M41T93 SPI RTC chip.
553 
554           This driver can also be built as a module. If so, the module
555           will be called rtc-m41t93.
556 
557 config RTC_DRV_M41T94
558         tristate "ST M41T94"
559         help
560           If you say yes here you will get support for the
561           ST M41T94 SPI RTC chip.
562 
563           This driver can also be built as a module. If so, the module
564           will be called rtc-m41t94.
565 
566 config RTC_DRV_DS1305
567         tristate "Dallas/Maxim DS1305/DS1306"
568         help
569           Select this driver to get support for the Dallas/Maxim DS1305
570           and DS1306 real time clock chips. These support a trickle
571           charger, alarms, and NVRAM in addition to the clock.
572 
573           This driver can also be built as a module. If so, the module
574           will be called rtc-ds1305.
575 
576 config RTC_DRV_DS1390
577         tristate "Dallas/Maxim DS1390/93/94"
578         help
579           If you say yes here you get support for the
580           Dallas/Maxim DS1390/93/94 chips.
581 
582           This driver only supports the RTC feature, and not other chip
583           features such as alarms and trickle charging.
584 
585           This driver can also be built as a module. If so, the module
586           will be called rtc-ds1390.
587 
588 config RTC_DRV_MAX6902
589         tristate "Maxim MAX6902"
590         help
591           If you say yes here you will get support for the
592           Maxim MAX6902 SPI RTC chip.
593 
594           This driver can also be built as a module. If so, the module
595           will be called rtc-max6902.
596 
597 config RTC_DRV_R9701
598         tristate "Epson RTC-9701JE"
599         help
600           If you say yes here you will get support for the
601           Epson RTC-9701JE SPI RTC chip.
602 
603           This driver can also be built as a module. If so, the module
604           will be called rtc-r9701.
605 
606 config RTC_DRV_RS5C348
607         tristate "Ricoh RS5C348A/B"
608         help
609           If you say yes here you get support for the
610           Ricoh RS5C348A and RS5C348B RTC chips.
611 
612           This driver can also be built as a module. If so, the module
613           will be called rtc-rs5c348.
614 
615 config RTC_DRV_DS3234
616         tristate "Maxim/Dallas DS3234"
617         help
618           If you say yes here you get support for the
619           Maxim/Dallas DS3234 SPI RTC chip.
620 
621           This driver can also be built as a module. If so, the module
622           will be called rtc-ds3234.
623 
624 config RTC_DRV_PCF2123
625         tristate "NXP PCF2123"
626         help
627           If you say yes here you get support for the NXP PCF2123
628           RTC chip.
629 
630           This driver can also be built as a module. If so, the module
631           will be called rtc-pcf2123.
632 
633 config RTC_DRV_RX4581
634         tristate "Epson RX-4581"
635         help
636           If you say yes here you will get support for the Epson RX-4581.
637 
638           This driver can also be built as a module. If so the module
639           will be called rtc-rx4581.
640 
641 endif # SPI_MASTER
642 
643 comment "Platform RTC drivers"
644 
645 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
646 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
647 # global rtc_lock ... it's not yet just another platform_device.
648 
649 config RTC_DRV_CMOS
650         tristate "PC-style 'CMOS'"
651         depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
652         default y if X86
653         help
654           Say "yes" here to get direct support for the real time clock
655           found in every PC or ACPI-based system, and some other boards.
656           Specifically the original MC146818, compatibles like those in
657           PC south bridges, the DS12887 or M48T86, some multifunction
658           or LPC bus chips, and so on.
659 
660           Your system will need to define the platform device used by
661           this driver, otherwise it won't be accessible. This means
662           you can safely enable this driver if you don't know whether
663           or not your board has this kind of hardware.
664 
665           This driver can also be built as a module. If so, the module
666           will be called rtc-cmos.
667 
668 config RTC_DRV_ALPHA
669         bool "Alpha PC-style CMOS"
670         depends on ALPHA
671         default y
672         help
673           Direct support for the real-time clock found on every Alpha
674           system, specifically MC146818 compatibles.  If in doubt, say Y.
675 
676 config RTC_DRV_VRTC
677         tristate "Virtual RTC for Intel MID platforms"
678         depends on X86_INTEL_MID
679         default y if X86_INTEL_MID
680 
681         help
682         Say "yes" here to get direct support for the real time clock
683         found on Moorestown platforms. The VRTC is a emulated RTC that
684         derives its clock source from a real RTC in the PMIC. The MC146818
685         style programming interface is mostly conserved, but any
686         updates are done via IPC calls to the system controller FW.
687 
688 config RTC_DRV_DS1216
689         tristate "Dallas DS1216"
690         depends on SNI_RM
691         help
692           If you say yes here you get support for the Dallas DS1216 RTC chips.
693 
694 config RTC_DRV_DS1286
695         tristate "Dallas DS1286"
696         help
697           If you say yes here you get support for the Dallas DS1286 RTC chips.
698 
699 config RTC_DRV_DS1302
700         tristate "Dallas DS1302"
701         depends on SH_SECUREEDGE5410
702         help
703           If you say yes here you get support for the Dallas DS1302 RTC chips.
704 
705 config RTC_DRV_DS1511
706         tristate "Dallas DS1511"
707         help
708           If you say yes here you get support for the
709           Dallas DS1511 timekeeping/watchdog chip.
710 
711           This driver can also be built as a module. If so, the module
712           will be called rtc-ds1511.
713 
714 config RTC_DRV_DS1553
715         tristate "Maxim/Dallas DS1553"
716         help
717           If you say yes here you get support for the
718           Maxim/Dallas DS1553 timekeeping chip.
719 
720           This driver can also be built as a module. If so, the module
721           will be called rtc-ds1553.
722 
723 config RTC_DRV_DS1742
724         tristate "Maxim/Dallas DS1742/1743"
725         help
726           If you say yes here you get support for the
727           Maxim/Dallas DS1742/1743 timekeeping chip.
728 
729           This driver can also be built as a module. If so, the module
730           will be called rtc-ds1742.
731 
732 config RTC_DRV_DA9052
733         tristate "Dialog DA9052/DA9053 RTC"
734         depends on PMIC_DA9052
735         help
736           Say y here to support the RTC driver for Dialog Semiconductor
737           DA9052-BC and DA9053-AA/Bx PMICs.
738 
739 config RTC_DRV_DA9055
740         tristate "Dialog Semiconductor DA9055 RTC"
741         depends on MFD_DA9055
742         help
743           If you say yes here you will get support for the
744           RTC of the Dialog DA9055 PMIC.
745 
746           This driver can also be built as a module. If so, the module
747           will be called rtc-da9055
748 
749 config RTC_DRV_EFI
750         tristate "EFI RTC"
751         depends on IA64
752         help
753           If you say yes here you will get support for the EFI
754           Real Time Clock.
755 
756           This driver can also be built as a module. If so, the module
757           will be called rtc-efi.
758 
759 config RTC_DRV_STK17TA8
760         tristate "Simtek STK17TA8"
761         help
762           If you say yes here you get support for the
763           Simtek STK17TA8 timekeeping chip.
764 
765           This driver can also be built as a module. If so, the module
766           will be called rtc-stk17ta8.
767 
768 config RTC_DRV_M48T86
769         tristate "ST M48T86/Dallas DS12887"
770         help
771           If you say Y here you will get support for the
772           ST M48T86 and Dallas DS12887 RTC chips.
773 
774           This driver can also be built as a module. If so, the module
775           will be called rtc-m48t86.
776 
777 config RTC_DRV_M48T35
778         tristate "ST M48T35"
779         help
780           If you say Y here you will get support for the
781           ST M48T35 RTC chip.
782 
783           This driver can also be built as a module, if so, the module
784           will be called "rtc-m48t35".
785 
786 config RTC_DRV_M48T59
787         tristate "ST M48T59/M48T08/M48T02"
788         help
789           If you say Y here you will get support for the
790           ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
791 
792           These chips are usually found in Sun SPARC and UltraSPARC
793           workstations.
794 
795           This driver can also be built as a module, if so, the module
796           will be called "rtc-m48t59".
797 
798 config RTC_DRV_MSM6242
799         tristate "Oki MSM6242"
800         help
801           If you say yes here you get support for the Oki MSM6242
802           timekeeping chip. It is used in some Amiga models (e.g. A2000).
803 
804           This driver can also be built as a module. If so, the module
805           will be called rtc-msm6242.
806 
807 config RTC_DRV_BQ4802
808         tristate "TI BQ4802"
809         help
810           If you say Y here you will get support for the TI
811           BQ4802 RTC chip.
812 
813           This driver can also be built as a module. If so, the module
814           will be called rtc-bq4802.
815 
816 config RTC_DRV_RP5C01
817         tristate "Ricoh RP5C01"
818         help
819           If you say yes here you get support for the Ricoh RP5C01
820           timekeeping chip. It is used in some Amiga models (e.g. A3000
821           and A4000).
822 
823           This driver can also be built as a module. If so, the module
824           will be called rtc-rp5c01.
825 
826 config RTC_DRV_V3020
827         tristate "EM Microelectronic V3020"
828         help
829           If you say yes here you will get support for the
830           EM Microelectronic v3020 RTC chip.
831 
832           This driver can also be built as a module. If so, the module
833           will be called rtc-v3020.
834 
835 config RTC_DRV_DS2404
836         tristate "Dallas DS2404"
837         help
838           If you say yes here you get support for the
839           Dallas DS2404 RTC chip.
840 
841           This driver can also be built as a module. If so, the module
842           will be called rtc-ds2404.
843 
844 config RTC_DRV_WM831X
845         tristate "Wolfson Microelectronics WM831x RTC"
846         depends on MFD_WM831X
847         help
848           If you say yes here you will get support for the RTC subsystem
849           of the Wolfson Microelectronics WM831X series PMICs.
850 
851           This driver can also be built as a module. If so, the module
852           will be called "rtc-wm831x".
853 
854 config RTC_DRV_WM8350
855         tristate "Wolfson Microelectronics WM8350 RTC"
856         depends on MFD_WM8350
857         help
858           If you say yes here you will get support for the RTC subsystem
859           of the Wolfson Microelectronics WM8350.
860 
861           This driver can also be built as a module. If so, the module
862           will be called "rtc-wm8350".
863 
864 config RTC_DRV_SPEAR
865         tristate "SPEAR ST RTC"
866         depends on PLAT_SPEAR
867         default y
868         help
869          If you say Y here you will get support for the RTC found on
870          spear
871 
872 config RTC_DRV_PCF50633
873         depends on MFD_PCF50633
874         tristate "NXP PCF50633 RTC"
875         help
876           If you say yes here you get support for the RTC subsystem of the
877           NXP PCF50633 used in embedded systems.
878 
879 config RTC_DRV_AB3100
880         tristate "ST-Ericsson AB3100 RTC"
881         depends on AB3100_CORE
882         default y if AB3100_CORE
883         help
884           Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
885           support. This chip contains a battery- and capacitor-backed RTC.
886 
887 config RTC_DRV_AB8500
888         tristate "ST-Ericsson AB8500 RTC"
889         depends on AB8500_CORE
890         select RTC_INTF_DEV
891         select RTC_INTF_DEV_UIE_EMUL
892         help
893           Select this to enable the ST-Ericsson AB8500 power management IC RTC
894           support. This chip contains a battery- and capacitor-backed RTC.
895 
896 config RTC_DRV_NUC900
897         tristate "NUC910/NUC920 RTC driver"
898         depends on ARCH_W90X900
899         help
900           If you say yes here you get support for the RTC subsystem of the
901           NUC910/NUC920 used in embedded systems.
902 
903 comment "on-CPU RTC drivers"
904 
905 config RTC_DRV_DAVINCI
906         tristate "TI DaVinci RTC"
907         depends on ARCH_DAVINCI_DM365
908         help
909           If you say yes here you get support for the RTC on the
910           DaVinci platforms (DM365).
911 
912           This driver can also be built as a module. If so, the module
913           will be called rtc-davinci.
914 
915 config RTC_DRV_IMXDI
916         tristate "Freescale IMX DryIce Real Time Clock"
917         depends on ARCH_MXC
918         help
919            Support for Freescale IMX DryIce RTC
920 
921            This driver can also be built as a module, if so, the module
922            will be called "rtc-imxdi".
923 
924 config RTC_DRV_OMAP
925         tristate "TI OMAP1"
926         depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
927         help
928           Say "yes" here to support the on chip real time clock
929           present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
930 
931           This driver can also be built as a module, if so, module
932           will be called rtc-omap.
933 
934 config HAVE_S3C_RTC
935         bool
936         help
937           This will include RTC support for Samsung SoCs. If
938           you want to include RTC support for any machine, kindly
939           select this in the respective mach-XXXX/Kconfig file.
940 
941 config RTC_DRV_S3C
942         tristate "Samsung S3C series SoC RTC"
943         depends on ARCH_S3C64XX || HAVE_S3C_RTC
944         help
945           RTC (Realtime Clock) driver for the clock inbuilt into the
946           Samsung S3C24XX series of SoCs. This can provide periodic
947           interrupt rates from 1Hz to 64Hz for user programs, and
948           wakeup from Alarm.
949 
950           The driver currently supports the common features on all the
951           S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
952           and S3C2442.
953 
954           This driver can also be build as a module. If so, the module
955           will be called rtc-s3c.
956 
957 config RTC_DRV_EP93XX
958         tristate "Cirrus Logic EP93XX"
959         depends on ARCH_EP93XX
960         help
961           If you say yes here you get support for the
962           RTC embedded in the Cirrus Logic EP93XX processors.
963 
964           This driver can also be built as a module. If so, the module
965           will be called rtc-ep93xx.
966 
967 config RTC_DRV_SA1100
968         tristate "SA11x0/PXA2xx/PXA910"
969         depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
970         help
971           If you say Y here you will get access to the real time clock
972           built into your SA11x0 or PXA2xx CPU.
973 
974           To compile this driver as a module, choose M here: the
975           module will be called rtc-sa1100.
976 
977 config RTC_DRV_SH
978         tristate "SuperH On-Chip RTC"
979         depends on SUPERH && HAVE_CLK
980         help
981           Say Y here to enable support for the on-chip RTC found in
982           most SuperH processors.
983 
984           To compile this driver as a module, choose M here: the
985           module will be called rtc-sh.
986 
987 config RTC_DRV_VR41XX
988         tristate "NEC VR41XX"
989         depends on CPU_VR41XX
990         help
991           If you say Y here you will get access to the real time clock
992           built into your NEC VR41XX CPU.
993 
994           To compile this driver as a module, choose M here: the
995           module will be called rtc-vr41xx.
996 
997 config RTC_DRV_PL030
998         tristate "ARM AMBA PL030 RTC"
999         depends on ARM_AMBA
1000         help
1001           If you say Y here you will get access to ARM AMBA
1002           PrimeCell PL030 RTC found on certain ARM SOCs.
1003 
1004           To compile this driver as a module, choose M here: the
1005           module will be called rtc-pl030.
1006 
1007 config RTC_DRV_PL031
1008         tristate "ARM AMBA PL031 RTC"
1009         depends on ARM_AMBA
1010         help
1011           If you say Y here you will get access to ARM AMBA
1012           PrimeCell PL031 RTC found on certain ARM SOCs.
1013 
1014           To compile this driver as a module, choose M here: the
1015           module will be called rtc-pl031.
1016 
1017 config RTC_DRV_AT32AP700X
1018         tristate "AT32AP700X series RTC"
1019         depends on PLATFORM_AT32AP
1020         help
1021           Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1022           AT32AP700x family processors.
1023 
1024 config RTC_DRV_AT91RM9200
1025         tristate "AT91RM9200 or some AT91SAM9 RTC"
1026         depends on ARCH_AT91
1027         help
1028           Driver for the internal RTC (Realtime Clock) module found on
1029           Atmel AT91RM9200's and some  AT91SAM9 chips. On AT91SAM9 chips
1030           this is powered by the backup power supply.
1031 
1032 config RTC_DRV_AT91SAM9
1033         tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
1034         depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
1035         help
1036           RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
1037           (Real Time Timer). These timers are powered by the backup power
1038           supply (such as a small coin cell battery), but do not need to
1039           be used as RTCs.
1040 
1041           (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
1042           dedicated RTC module and leave the RTT available for other uses.)
1043 
1044 config RTC_DRV_AT91SAM9_RTT
1045         int
1046         range 0 1
1047         default 0
1048         prompt "RTT module Number" if ARCH_AT91SAM9263
1049         depends on RTC_DRV_AT91SAM9
1050         help
1051           More than one RTT module is available. You can choose which
1052           one will be used as an RTC. The default of zero is normally
1053           OK to use, though some systems use that for non-RTC purposes.
1054 
1055 config RTC_DRV_AT91SAM9_GPBR
1056         int
1057         range 0 3 if !ARCH_AT91SAM9263
1058         range 0 15 if ARCH_AT91SAM9263
1059         default 0
1060         prompt "Backup Register Number"
1061         depends on RTC_DRV_AT91SAM9
1062         help
1063           The RTC driver needs to use one of the General Purpose Backup
1064           Registers (GPBRs) as well as the RTT. You can choose which one
1065           will be used. The default of zero is normally OK to use, but
1066           on some systems other software needs to use that register.
1067 
1068 config RTC_DRV_AU1XXX
1069         tristate "Au1xxx Counter0 RTC support"
1070         depends on MIPS_ALCHEMY
1071         help
1072           This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1073           counter) to be used as a RTC.
1074 
1075           This driver can also be built as a module. If so, the module
1076           will be called rtc-au1xxx.
1077 
1078 config RTC_DRV_BFIN
1079         tristate "Blackfin On-Chip RTC"
1080         depends on BLACKFIN && !BF561
1081         help
1082           If you say yes here you will get support for the
1083           Blackfin On-Chip Real Time Clock.
1084 
1085           This driver can also be built as a module. If so, the module
1086           will be called rtc-bfin.
1087 
1088 config RTC_DRV_RS5C313
1089         tristate "Ricoh RS5C313"
1090         depends on SH_LANDISK
1091         help
1092           If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1093 
1094 config RTC_DRV_GENERIC
1095         tristate "Generic RTC support"
1096         # Please consider writing a new RTC driver instead of using the generic
1097         # RTC abstraction
1098         depends on PARISC || M68K || PPC || SUPERH32
1099         help
1100           Say Y or M here to enable RTC support on systems using the generic
1101           RTC abstraction. If you do not know what you are doing, you should
1102           just say Y.
1103 
1104 config RTC_DRV_PXA
1105        tristate "PXA27x/PXA3xx"
1106        depends on ARCH_PXA
1107        help
1108          If you say Y here you will get access to the real time clock
1109          built into your PXA27x or PXA3xx CPU.
1110 
1111          This RTC driver uses PXA RTC registers available since pxa27x
1112          series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1113 
1114 config RTC_DRV_VT8500
1115         tristate "VIA/WonderMedia 85xx SoC RTC"
1116         depends on ARCH_VT8500
1117         help
1118           If you say Y here you will get access to the real time clock
1119           built into your VIA VT8500 SoC or its relatives.
1120 
1121 
1122 config RTC_DRV_SUN4V
1123         bool "SUN4V Hypervisor RTC"
1124         depends on SPARC64
1125         help
1126           If you say Y here you will get support for the Hypervisor
1127           based RTC on SUN4V systems.
1128 
1129 config RTC_DRV_SUNXI
1130         tristate "Allwinner sun4i/sun7i RTC"
1131         depends on ARCH_SUNXI
1132         help
1133           If you say Y here you will get support for the RTC found on
1134           Allwinner A10/A20.
1135 
1136 config RTC_DRV_STARFIRE
1137         bool "Starfire RTC"
1138         depends on SPARC64
1139         help
1140           If you say Y here you will get support for the RTC found on
1141           Starfire systems.
1142 
1143 config RTC_DRV_TX4939
1144         tristate "TX4939 SoC"
1145         depends on SOC_TX4939
1146         help
1147           Driver for the internal RTC (Realtime Clock) module found on
1148           Toshiba TX4939 SoC.
1149 
1150 config RTC_DRV_MV
1151         tristate "Marvell SoC RTC"
1152         depends on ARCH_KIRKWOOD || ARCH_DOVE || ARCH_MVEBU
1153         help
1154           If you say yes here you will get support for the in-chip RTC
1155           that can be found in some of Marvell's SoC devices, such as
1156           the Kirkwood 88F6281 and 88F6192.
1157 
1158           This driver can also be built as a module. If so, the module
1159           will be called rtc-mv.
1160 
1161 config RTC_DRV_PS3
1162         tristate "PS3 RTC"
1163         depends on PPC_PS3
1164         help
1165           If you say yes here you will get support for the RTC on PS3.
1166 
1167           This driver can also be built as a module. If so, the module
1168           will be called rtc-ps3.
1169 
1170 config RTC_DRV_COH901331
1171         tristate "ST-Ericsson COH 901 331 RTC"
1172         depends on ARCH_U300
1173         help
1174           If you say Y here you will get access to ST-Ericsson
1175           COH 901 331 RTC clock found in some ST-Ericsson Mobile
1176           Platforms.
1177 
1178           This driver can also be built as a module. If so, the module
1179           will be called "rtc-coh901331".
1180 
1181 
1182 config RTC_DRV_STMP
1183         tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1184         depends on ARCH_MXS
1185         help
1186           If you say yes here you will get support for the onboard
1187           STMP3xxx/i.MX23/i.MX28 RTC.
1188 
1189           This driver can also be built as a module. If so, the module
1190           will be called rtc-stmp3xxx.
1191 
1192 config RTC_DRV_PCAP
1193         tristate "PCAP RTC"
1194         depends on EZX_PCAP
1195         help
1196           If you say Y here you will get support for the RTC found on
1197           the PCAP2 ASIC used on some Motorola phones.
1198 
1199 config RTC_DRV_MC13XXX
1200         depends on MFD_MC13XXX
1201         tristate "Freescale MC13xxx RTC"
1202         help
1203           This enables support for the RTCs found on Freescale's PMICs
1204           MC13783 and MC13892.
1205 
1206 config RTC_DRV_MPC5121
1207         tristate "Freescale MPC5121 built-in RTC"
1208         depends on PPC_MPC512x || PPC_MPC52xx
1209         help
1210           If you say yes here you will get support for the
1211           built-in RTC on MPC5121 or on MPC5200.
1212 
1213           This driver can also be built as a module. If so, the module
1214           will be called rtc-mpc5121.
1215 
1216 config RTC_DRV_JZ4740
1217         tristate "Ingenic JZ4740 SoC"
1218         depends on MACH_JZ4740
1219         help
1220           If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1221           controller.
1222 
1223           This driver can also be buillt as a module. If so, the module
1224           will be called rtc-jz4740.
1225 
1226 config RTC_DRV_LPC32XX
1227         depends on ARCH_LPC32XX
1228         tristate "NXP LPC32XX RTC"
1229         help
1230           This enables support for the NXP RTC in the LPC32XX
1231 
1232           This driver can also be buillt as a module. If so, the module
1233           will be called rtc-lpc32xx.
1234 
1235 config RTC_DRV_PM8XXX
1236         tristate "Qualcomm PMIC8XXX RTC"
1237         depends on MFD_PM8XXX
1238         help
1239           If you say yes here you get support for the
1240           Qualcomm PMIC8XXX RTC.
1241 
1242           To compile this driver as a module, choose M here: the
1243           module will be called rtc-pm8xxx.
1244 
1245 config RTC_DRV_TEGRA
1246         tristate "NVIDIA Tegra Internal RTC driver"
1247         depends on ARCH_TEGRA
1248         help
1249           If you say yes here you get support for the
1250           Tegra 200 series internal RTC module.
1251 
1252           This drive can also be built as a module. If so, the module
1253           will be called rtc-tegra.
1254 
1255 config RTC_DRV_TILE
1256         tristate "Tilera hypervisor RTC support"
1257         depends on TILE
1258         help
1259           Enable support for the Linux driver side of the Tilera
1260           hypervisor's real-time clock interface.
1261 
1262 config RTC_DRV_PUV3
1263         tristate "PKUnity v3 RTC support"
1264         depends on ARCH_PUV3
1265         help
1266           This enables support for the RTC in the PKUnity-v3 SoCs.
1267 
1268           This drive can also be built as a module. If so, the module
1269           will be called rtc-puv3.
1270 
1271 config RTC_DRV_LOONGSON1
1272         tristate "loongson1 RTC support"
1273         depends on MACH_LOONGSON1
1274         help
1275           This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1276           counter) to be used as a RTC.
1277 
1278           This driver can also be built as a module. If so, the module
1279           will be called rtc-ls1x.
1280 
1281 config RTC_DRV_MXC
1282         tristate "Freescale MXC Real Time Clock"
1283         depends on ARCH_MXC
1284         help
1285            If you say yes here you get support for the Freescale MXC
1286            RTC module.
1287 
1288            This driver can also be built as a module, if so, the module
1289            will be called "rtc-mxc".
1290 
1291 config RTC_DRV_SNVS
1292         tristate "Freescale SNVS RTC support"
1293         depends on HAS_IOMEM
1294         depends on OF
1295         help
1296            If you say yes here you get support for the Freescale SNVS
1297            Low Power (LP) RTC module.
1298 
1299            This driver can also be built as a module, if so, the module
1300            will be called "rtc-snvs".
1301 
1302 config RTC_DRV_SIRFSOC
1303         tristate "SiRFSOC RTC"
1304         depends on ARCH_SIRF
1305         help
1306           Say "yes" here to support the real time clock on SiRF SOC chips.
1307           This driver can also be built as a module called rtc-sirfsoc.
1308 
1309 config RTC_DRV_MOXART
1310         tristate "MOXA ART RTC"
1311         help
1312            If you say yes here you get support for the MOXA ART
1313            RTC module.
1314 
1315            This driver can also be built as a module. If so, the module
1316            will be called rtc-moxart
1317 
1318 comment "HID Sensor RTC drivers"
1319 
1320 config RTC_DRV_HID_SENSOR_TIME
1321         tristate "HID Sensor Time"
1322         depends on USB_HID
1323         select IIO
1324         select HID_SENSOR_HUB
1325         select HID_SENSOR_IIO_COMMON
1326         help
1327           Say yes here to build support for the HID Sensors of type Time.
1328           This drivers makes such sensors available as RTCs.
1329 
1330           If this driver is compiled as a module, it will be named
1331           rtc-hid-sensor-time.
1332 
1333 
1334 endif # RTC_CLASS

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