Version:  2.0.40 2.2.26 2.4.37 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 3.15 3.16 3.17

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_PCF85063
377         tristate "nxp PCF85063"
378         help
379           If you say yes here you get support for the PCF85063 RTC chip
380 
381           This driver can also be built as a module. If so, the module
382           will be called rtc-pcf85063.
383 
384 config RTC_DRV_PCF8583
385         tristate "Philips PCF8583"
386         help
387           If you say yes here you get support for the Philips PCF8583
388           RTC chip found on Acorn RiscPCs. This driver supports the
389           platform specific method of retrieving the current year from
390           the RTC's SRAM. It will work on other platforms with the same
391           chip, but the year will probably have to be tweaked.
392 
393           This driver can also be built as a module. If so, the module
394           will be called rtc-pcf8583.
395 
396 config RTC_DRV_M41T80
397         tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
398         help
399           If you say Y here you will get support for the ST M41T60
400           and M41T80 RTC chips series. Currently, the following chips are
401           supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
402           M41ST85, M41ST87, and MicroCrystal RV4162.
403 
404           This driver can also be built as a module. If so, the module
405           will be called rtc-m41t80.
406 
407 config RTC_DRV_M41T80_WDT
408         bool "ST M41T65/M41T80 series RTC watchdog timer"
409         depends on RTC_DRV_M41T80
410         help
411           If you say Y here you will get support for the
412           watchdog timer in the ST M41T60 and M41T80 RTC chips series.
413 
414 config RTC_DRV_BQ32K
415         tristate "TI BQ32000"
416         help
417           If you say Y here you will get support for the TI
418           BQ32000 I2C RTC chip.
419 
420           This driver can also be built as a module. If so, the module
421           will be called rtc-bq32k.
422 
423 config RTC_DRV_DM355EVM
424         tristate "TI DaVinci DM355 EVM RTC"
425         depends on MFD_DM355EVM_MSP
426         help
427           Supports the RTC firmware in the MSP430 on the DM355 EVM.
428 
429 config RTC_DRV_TWL92330
430         boolean "TI TWL92330/Menelaus"
431         depends on MENELAUS
432         help
433           If you say yes here you get support for the RTC on the
434           TWL92330 "Menelaus" power management chip, used with OMAP2
435           platforms. The support is integrated with the rest of
436           the Menelaus driver; it's not separate module.
437 
438 config RTC_DRV_TWL4030
439         tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
440         depends on TWL4030_CORE
441         help
442           If you say yes here you get support for the RTC on the
443           TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
444 
445           This driver can also be built as a module. If so, the module
446           will be called rtc-twl.
447 
448 config RTC_DRV_TPS6586X
449         tristate "TI TPS6586X RTC driver"
450         depends on MFD_TPS6586X
451         help
452           TI Power Management IC TPS6586X supports RTC functionality
453           along with alarm. This driver supports the RTC driver for
454           the TPS6586X RTC module.
455 
456 config RTC_DRV_TPS65910
457         tristate "TI TPS65910 RTC driver"
458         depends on RTC_CLASS && MFD_TPS65910
459         help
460           If you say yes here you get support for the RTC on the
461           TPS65910 chips.
462 
463           This driver can also be built as a module. If so, the module
464           will be called rtc-tps65910.
465 
466 config RTC_DRV_TPS80031
467         tristate "TI TPS80031/TPS80032 RTC driver"
468         depends on MFD_TPS80031
469         help
470           TI Power Management IC TPS80031 supports RTC functionality
471           along with alarm. This driver supports the RTC driver for
472           the TPS80031 RTC module.
473 
474 config RTC_DRV_RC5T583
475         tristate "RICOH 5T583 RTC driver"
476         depends on MFD_RC5T583
477         help
478           If you say yes here you get support for the RTC on the
479           RICOH 5T583 chips.
480 
481           This driver can also be built as a module. If so, the module
482           will be called rtc-rc5t583.
483 
484 config RTC_DRV_S35390A
485         tristate "Seiko Instruments S-35390A"
486         select BITREVERSE
487         help
488           If you say yes here you will get support for the Seiko
489           Instruments S-35390A.
490 
491           This driver can also be built as a module. If so the module
492           will be called rtc-s35390a.
493 
494 config RTC_DRV_FM3130
495         tristate "Ramtron FM3130"
496         help
497           If you say Y here you will get support for the
498           Ramtron FM3130 RTC chips.
499           Ramtron FM3130 is a chip with two separate devices inside,
500           RTC clock and FRAM. This driver provides only RTC functionality.
501 
502           This driver can also be built as a module. If so the module
503           will be called rtc-fm3130.
504 
505 config RTC_DRV_RX8581
506         tristate "Epson RX-8581"
507         help
508           If you say yes here you will get support for the Epson RX-8581.
509 
510           This driver can also be built as a module. If so the module
511           will be called rtc-rx8581.
512 
513 config RTC_DRV_RX8025
514         tristate "Epson RX-8025SA/NB"
515         help
516           If you say yes here you get support for the Epson
517           RX-8025SA/NB RTC chips.
518 
519           This driver can also be built as a module. If so, the module
520           will be called rtc-rx8025.
521 
522 config RTC_DRV_EM3027
523         tristate "EM Microelectronic EM3027"
524         help
525           If you say yes here you get support for the EM
526           Microelectronic EM3027 RTC chips.
527 
528           This driver can also be built as a module. If so, the module
529           will be called rtc-em3027.
530 
531 config RTC_DRV_RV3029C2
532         tristate "Micro Crystal RTC"
533         help
534           If you say yes here you get support for the Micro Crystal
535           RV3029-C2 RTC chips.
536 
537           This driver can also be built as a module. If so, the module
538           will be called rtc-rv3029c2.
539 
540 config RTC_DRV_S5M
541         tristate "Samsung S2M/S5M series"
542         depends on MFD_SEC_CORE
543         help
544           If you say yes here you will get support for the
545           RTC of Samsung S2MPS14 and S5M PMIC series.
546 
547           This driver can also be built as a module. If so, the module
548           will be called rtc-s5m.
549 
550 endif # I2C
551 
552 comment "SPI RTC drivers"
553 
554 if SPI_MASTER
555 
556 config RTC_DRV_M41T93
557         tristate "ST M41T93"
558         help
559           If you say yes here you will get support for the
560           ST M41T93 SPI RTC chip.
561 
562           This driver can also be built as a module. If so, the module
563           will be called rtc-m41t93.
564 
565 config RTC_DRV_M41T94
566         tristate "ST M41T94"
567         help
568           If you say yes here you will get support for the
569           ST M41T94 SPI RTC chip.
570 
571           This driver can also be built as a module. If so, the module
572           will be called rtc-m41t94.
573 
574 config RTC_DRV_DS1305
575         tristate "Dallas/Maxim DS1305/DS1306"
576         help
577           Select this driver to get support for the Dallas/Maxim DS1305
578           and DS1306 real time clock chips. These support a trickle
579           charger, alarms, and NVRAM in addition to the clock.
580 
581           This driver can also be built as a module. If so, the module
582           will be called rtc-ds1305.
583 
584 config RTC_DRV_DS1343
585         select REGMAP_SPI
586         tristate "Dallas/Maxim DS1343/DS1344"
587         help
588           If you say yes here you get support for the
589           Dallas/Maxim DS1343 and DS1344 real time clock chips.
590           Support for trickle charger, alarm is provided.
591 
592           This driver can also be built as a module. If so, the module
593           will be called rtc-ds1343.
594 
595 config RTC_DRV_DS1347
596         tristate "Dallas/Maxim DS1347"
597         help
598           If you say yes here you get support for the
599           Dallas/Maxim DS1347 chips.
600 
601           This driver only supports the RTC feature, and not other chip
602           features such as alarms.
603 
604           This driver can also be built as a module. If so, the module
605           will be called rtc-ds1347.
606 
607 config RTC_DRV_DS1390
608         tristate "Dallas/Maxim DS1390/93/94"
609         help
610           If you say yes here you get support for the
611           Dallas/Maxim DS1390/93/94 chips.
612 
613           This driver only supports the RTC feature, and not other chip
614           features such as alarms and trickle charging.
615 
616           This driver can also be built as a module. If so, the module
617           will be called rtc-ds1390.
618 
619 config RTC_DRV_MAX6902
620         tristate "Maxim MAX6902"
621         help
622           If you say yes here you will get support for the
623           Maxim MAX6902 SPI RTC chip.
624 
625           This driver can also be built as a module. If so, the module
626           will be called rtc-max6902.
627 
628 config RTC_DRV_R9701
629         tristate "Epson RTC-9701JE"
630         help
631           If you say yes here you will get support for the
632           Epson RTC-9701JE SPI RTC chip.
633 
634           This driver can also be built as a module. If so, the module
635           will be called rtc-r9701.
636 
637 config RTC_DRV_RS5C348
638         tristate "Ricoh RS5C348A/B"
639         help
640           If you say yes here you get support for the
641           Ricoh RS5C348A and RS5C348B RTC chips.
642 
643           This driver can also be built as a module. If so, the module
644           will be called rtc-rs5c348.
645 
646 config RTC_DRV_DS3234
647         tristate "Maxim/Dallas DS3234"
648         help
649           If you say yes here you get support for the
650           Maxim/Dallas DS3234 SPI RTC chip.
651 
652           This driver can also be built as a module. If so, the module
653           will be called rtc-ds3234.
654 
655 config RTC_DRV_PCF2123
656         tristate "NXP PCF2123"
657         help
658           If you say yes here you get support for the NXP PCF2123
659           RTC chip.
660 
661           This driver can also be built as a module. If so, the module
662           will be called rtc-pcf2123.
663 
664 config RTC_DRV_RX4581
665         tristate "Epson RX-4581"
666         help
667           If you say yes here you will get support for the Epson RX-4581.
668 
669           This driver can also be built as a module. If so the module
670           will be called rtc-rx4581.
671 
672 config RTC_DRV_MCP795
673         tristate "Microchip MCP795"
674         help
675           If you say yes here you will get support for the Microchip MCP795.
676 
677           This driver can also be built as a module. If so the module
678           will be called rtc-mcp795.
679 
680 endif # SPI_MASTER
681 
682 comment "Platform RTC drivers"
683 
684 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
685 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
686 # global rtc_lock ... it's not yet just another platform_device.
687 
688 config RTC_DRV_CMOS
689         tristate "PC-style 'CMOS'"
690         depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
691         default y if X86
692         help
693           Say "yes" here to get direct support for the real time clock
694           found in every PC or ACPI-based system, and some other boards.
695           Specifically the original MC146818, compatibles like those in
696           PC south bridges, the DS12887 or M48T86, some multifunction
697           or LPC bus chips, and so on.
698 
699           Your system will need to define the platform device used by
700           this driver, otherwise it won't be accessible. This means
701           you can safely enable this driver if you don't know whether
702           or not your board has this kind of hardware.
703 
704           This driver can also be built as a module. If so, the module
705           will be called rtc-cmos.
706 
707 config RTC_DRV_ALPHA
708         bool "Alpha PC-style CMOS"
709         depends on ALPHA
710         default y
711         help
712           Direct support for the real-time clock found on every Alpha
713           system, specifically MC146818 compatibles.  If in doubt, say Y.
714 
715 config RTC_DRV_VRTC
716         tristate "Virtual RTC for Intel MID platforms"
717         depends on X86_INTEL_MID
718         default y if X86_INTEL_MID
719 
720         help
721         Say "yes" here to get direct support for the real time clock
722         found on Moorestown platforms. The VRTC is a emulated RTC that
723         derives its clock source from a real RTC in the PMIC. The MC146818
724         style programming interface is mostly conserved, but any
725         updates are done via IPC calls to the system controller FW.
726 
727 config RTC_DRV_DS1216
728         tristate "Dallas DS1216"
729         depends on SNI_RM
730         help
731           If you say yes here you get support for the Dallas DS1216 RTC chips.
732 
733 config RTC_DRV_DS1286
734         tristate "Dallas DS1286"
735         help
736           If you say yes here you get support for the Dallas DS1286 RTC chips.
737 
738 config RTC_DRV_DS1302
739         tristate "Dallas DS1302"
740         depends on SH_SECUREEDGE5410
741         help
742           If you say yes here you get support for the Dallas DS1302 RTC chips.
743 
744 config RTC_DRV_DS1511
745         tristate "Dallas DS1511"
746         help
747           If you say yes here you get support for the
748           Dallas DS1511 timekeeping/watchdog chip.
749 
750           This driver can also be built as a module. If so, the module
751           will be called rtc-ds1511.
752 
753 config RTC_DRV_DS1553
754         tristate "Maxim/Dallas DS1553"
755         help
756           If you say yes here you get support for the
757           Maxim/Dallas DS1553 timekeeping chip.
758 
759           This driver can also be built as a module. If so, the module
760           will be called rtc-ds1553.
761 
762 config RTC_DRV_DS1742
763         tristate "Maxim/Dallas DS1742/1743"
764         help
765           If you say yes here you get support for the
766           Maxim/Dallas DS1742/1743 timekeeping chip.
767 
768           This driver can also be built as a module. If so, the module
769           will be called rtc-ds1742.
770 
771 config RTC_DRV_DS2404
772         tristate "Maxim/Dallas DS2404"
773         help
774           If you say yes here you get support for the
775           Dallas DS2404 RTC chip.
776 
777           This driver can also be built as a module. If so, the module
778           will be called rtc-ds2404.
779 
780 config RTC_DRV_DA9052
781         tristate "Dialog DA9052/DA9053 RTC"
782         depends on PMIC_DA9052
783         help
784           Say y here to support the RTC driver for Dialog Semiconductor
785           DA9052-BC and DA9053-AA/Bx PMICs.
786 
787 config RTC_DRV_DA9055
788         tristate "Dialog Semiconductor DA9055 RTC"
789         depends on MFD_DA9055
790         help
791           If you say yes here you will get support for the
792           RTC of the Dialog DA9055 PMIC.
793 
794           This driver can also be built as a module. If so, the module
795           will be called rtc-da9055
796 
797 config RTC_DRV_DA9063
798         tristate "Dialog Semiconductor DA9063 RTC"
799         depends on MFD_DA9063
800         help
801           If you say yes here you will get support for the RTC subsystem
802           of the Dialog Semiconductor DA9063.
803 
804           This driver can also be built as a module. If so, the module
805           will be called "rtc-da9063".
806 
807 config RTC_DRV_EFI
808         tristate "EFI RTC"
809         depends on EFI
810         help
811           If you say yes here you will get support for the EFI
812           Real Time Clock.
813 
814           This driver can also be built as a module. If so, the module
815           will be called rtc-efi.
816 
817 config RTC_DRV_STK17TA8
818         tristate "Simtek STK17TA8"
819         help
820           If you say yes here you get support for the
821           Simtek STK17TA8 timekeeping chip.
822 
823           This driver can also be built as a module. If so, the module
824           will be called rtc-stk17ta8.
825 
826 config RTC_DRV_M48T86
827         tristate "ST M48T86/Dallas DS12887"
828         help
829           If you say Y here you will get support for the
830           ST M48T86 and Dallas DS12887 RTC chips.
831 
832           This driver can also be built as a module. If so, the module
833           will be called rtc-m48t86.
834 
835 config RTC_DRV_M48T35
836         tristate "ST M48T35"
837         help
838           If you say Y here you will get support for the
839           ST M48T35 RTC chip.
840 
841           This driver can also be built as a module, if so, the module
842           will be called "rtc-m48t35".
843 
844 config RTC_DRV_M48T59
845         tristate "ST M48T59/M48T08/M48T02"
846         help
847           If you say Y here you will get support for the
848           ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
849 
850           These chips are usually found in Sun SPARC and UltraSPARC
851           workstations.
852 
853           This driver can also be built as a module, if so, the module
854           will be called "rtc-m48t59".
855 
856 config RTC_DRV_MSM6242
857         tristate "Oki MSM6242"
858         help
859           If you say yes here you get support for the Oki MSM6242
860           timekeeping chip. It is used in some Amiga models (e.g. A2000).
861 
862           This driver can also be built as a module. If so, the module
863           will be called rtc-msm6242.
864 
865 config RTC_DRV_BQ4802
866         tristate "TI BQ4802"
867         help
868           If you say Y here you will get support for the TI
869           BQ4802 RTC chip.
870 
871           This driver can also be built as a module. If so, the module
872           will be called rtc-bq4802.
873 
874 config RTC_DRV_RP5C01
875         tristate "Ricoh RP5C01"
876         help
877           If you say yes here you get support for the Ricoh RP5C01
878           timekeeping chip. It is used in some Amiga models (e.g. A3000
879           and A4000).
880 
881           This driver can also be built as a module. If so, the module
882           will be called rtc-rp5c01.
883 
884 config RTC_DRV_V3020
885         tristate "EM Microelectronic V3020"
886         help
887           If you say yes here you will get support for the
888           EM Microelectronic v3020 RTC chip.
889 
890           This driver can also be built as a module. If so, the module
891           will be called rtc-v3020.
892 
893 config RTC_DRV_WM831X
894         tristate "Wolfson Microelectronics WM831x RTC"
895         depends on MFD_WM831X
896         help
897           If you say yes here you will get support for the RTC subsystem
898           of the Wolfson Microelectronics WM831X series PMICs.
899 
900           This driver can also be built as a module. If so, the module
901           will be called "rtc-wm831x".
902 
903 config RTC_DRV_WM8350
904         tristate "Wolfson Microelectronics WM8350 RTC"
905         depends on MFD_WM8350
906         help
907           If you say yes here you will get support for the RTC subsystem
908           of the Wolfson Microelectronics WM8350.
909 
910           This driver can also be built as a module. If so, the module
911           will be called "rtc-wm8350".
912 
913 config RTC_DRV_SPEAR
914         tristate "SPEAR ST RTC"
915         depends on PLAT_SPEAR
916         default y
917         help
918          If you say Y here you will get support for the RTC found on
919          spear
920 
921 config RTC_DRV_PCF50633
922         depends on MFD_PCF50633
923         tristate "NXP PCF50633 RTC"
924         help
925           If you say yes here you get support for the RTC subsystem of the
926           NXP PCF50633 used in embedded systems.
927 
928 config RTC_DRV_AB3100
929         tristate "ST-Ericsson AB3100 RTC"
930         depends on AB3100_CORE
931         default y if AB3100_CORE
932         help
933           Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
934           support. This chip contains a battery- and capacitor-backed RTC.
935 
936 config RTC_DRV_AB8500
937         tristate "ST-Ericsson AB8500 RTC"
938         depends on AB8500_CORE
939         select RTC_INTF_DEV
940         select RTC_INTF_DEV_UIE_EMUL
941         help
942           Select this to enable the ST-Ericsson AB8500 power management IC RTC
943           support. This chip contains a battery- and capacitor-backed RTC.
944 
945 config RTC_DRV_NUC900
946         tristate "NUC910/NUC920 RTC driver"
947         depends on ARCH_W90X900
948         help
949           If you say yes here you get support for the RTC subsystem of the
950           NUC910/NUC920 used in embedded systems.
951 
952 comment "on-CPU RTC drivers"
953 
954 config RTC_DRV_DAVINCI
955         tristate "TI DaVinci RTC"
956         depends on ARCH_DAVINCI_DM365
957         help
958           If you say yes here you get support for the RTC on the
959           DaVinci platforms (DM365).
960 
961           This driver can also be built as a module. If so, the module
962           will be called rtc-davinci.
963 
964 config RTC_DRV_IMXDI
965         tristate "Freescale IMX DryIce Real Time Clock"
966         depends on ARCH_MXC
967         help
968            Support for Freescale IMX DryIce RTC
969 
970            This driver can also be built as a module, if so, the module
971            will be called "rtc-imxdi".
972 
973 config RTC_DRV_OMAP
974         tristate "TI OMAP1"
975         depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
976         help
977           Say "yes" here to support the on chip real time clock
978           present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
979 
980           This driver can also be built as a module, if so, module
981           will be called rtc-omap.
982 
983 config HAVE_S3C_RTC
984         bool
985         help
986           This will include RTC support for Samsung SoCs. If
987           you want to include RTC support for any machine, kindly
988           select this in the respective mach-XXXX/Kconfig file.
989 
990 config RTC_DRV_S3C
991         tristate "Samsung S3C series SoC RTC"
992         depends on ARCH_S3C64XX || HAVE_S3C_RTC
993         help
994           RTC (Realtime Clock) driver for the clock inbuilt into the
995           Samsung S3C24XX series of SoCs. This can provide periodic
996           interrupt rates from 1Hz to 64Hz for user programs, and
997           wakeup from Alarm.
998 
999           The driver currently supports the common features on all the
1000           S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1001           and S3C2442.
1002 
1003           This driver can also be build as a module. If so, the module
1004           will be called rtc-s3c.
1005 
1006 config RTC_DRV_EP93XX
1007         tristate "Cirrus Logic EP93XX"
1008         depends on ARCH_EP93XX
1009         help
1010           If you say yes here you get support for the
1011           RTC embedded in the Cirrus Logic EP93XX processors.
1012 
1013           This driver can also be built as a module. If so, the module
1014           will be called rtc-ep93xx.
1015 
1016 config RTC_DRV_SA1100
1017         tristate "SA11x0/PXA2xx/PXA910"
1018         depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1019         help
1020           If you say Y here you will get access to the real time clock
1021           built into your SA11x0 or PXA2xx CPU.
1022 
1023           To compile this driver as a module, choose M here: the
1024           module will be called rtc-sa1100.
1025 
1026 config RTC_DRV_SH
1027         tristate "SuperH On-Chip RTC"
1028         depends on SUPERH && HAVE_CLK
1029         help
1030           Say Y here to enable support for the on-chip RTC found in
1031           most SuperH processors.
1032 
1033           To compile this driver as a module, choose M here: the
1034           module will be called rtc-sh.
1035 
1036 config RTC_DRV_VR41XX
1037         tristate "NEC VR41XX"
1038         depends on CPU_VR41XX
1039         help
1040           If you say Y here you will get access to the real time clock
1041           built into your NEC VR41XX CPU.
1042 
1043           To compile this driver as a module, choose M here: the
1044           module will be called rtc-vr41xx.
1045 
1046 config RTC_DRV_PL030
1047         tristate "ARM AMBA PL030 RTC"
1048         depends on ARM_AMBA
1049         help
1050           If you say Y here you will get access to ARM AMBA
1051           PrimeCell PL030 RTC found on certain ARM SOCs.
1052 
1053           To compile this driver as a module, choose M here: the
1054           module will be called rtc-pl030.
1055 
1056 config RTC_DRV_PL031
1057         tristate "ARM AMBA PL031 RTC"
1058         depends on ARM_AMBA
1059         help
1060           If you say Y here you will get access to ARM AMBA
1061           PrimeCell PL031 RTC found on certain ARM SOCs.
1062 
1063           To compile this driver as a module, choose M here: the
1064           module will be called rtc-pl031.
1065 
1066 config RTC_DRV_AT32AP700X
1067         tristate "AT32AP700X series RTC"
1068         depends on PLATFORM_AT32AP
1069         help
1070           Driver for the internal RTC (Realtime Clock) on Atmel AVR32
1071           AT32AP700x family processors.
1072 
1073 config RTC_DRV_AT91RM9200
1074         tristate "AT91RM9200 or some AT91SAM9 RTC"
1075         depends on ARCH_AT91
1076         help
1077           Driver for the internal RTC (Realtime Clock) module found on
1078           Atmel AT91RM9200's and some  AT91SAM9 chips. On AT91SAM9 chips
1079           this is powered by the backup power supply.
1080 
1081 config RTC_DRV_AT91SAM9
1082         tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
1083         depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
1084         help
1085           RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
1086           (Real Time Timer). These timers are powered by the backup power
1087           supply (such as a small coin cell battery), but do not need to
1088           be used as RTCs.
1089 
1090           (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
1091           dedicated RTC module and leave the RTT available for other uses.)
1092 
1093 config RTC_DRV_AT91SAM9_RTT
1094         int
1095         range 0 1
1096         default 0
1097         prompt "RTT module Number" if ARCH_AT91SAM9263
1098         depends on RTC_DRV_AT91SAM9
1099         help
1100           More than one RTT module is available. You can choose which
1101           one will be used as an RTC. The default of zero is normally
1102           OK to use, though some systems use that for non-RTC purposes.
1103 
1104 config RTC_DRV_AT91SAM9_GPBR
1105         int
1106         range 0 3 if !ARCH_AT91SAM9263
1107         range 0 15 if ARCH_AT91SAM9263
1108         default 0
1109         prompt "Backup Register Number"
1110         depends on RTC_DRV_AT91SAM9
1111         help
1112           The RTC driver needs to use one of the General Purpose Backup
1113           Registers (GPBRs) as well as the RTT. You can choose which one
1114           will be used. The default of zero is normally OK to use, but
1115           on some systems other software needs to use that register.
1116 
1117 config RTC_DRV_AU1XXX
1118         tristate "Au1xxx Counter0 RTC support"
1119         depends on MIPS_ALCHEMY
1120         help
1121           This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1122           counter) to be used as a RTC.
1123 
1124           This driver can also be built as a module. If so, the module
1125           will be called rtc-au1xxx.
1126 
1127 config RTC_DRV_BFIN
1128         tristate "Blackfin On-Chip RTC"
1129         depends on BLACKFIN && !BF561
1130         help
1131           If you say yes here you will get support for the
1132           Blackfin On-Chip Real Time Clock.
1133 
1134           This driver can also be built as a module. If so, the module
1135           will be called rtc-bfin.
1136 
1137 config RTC_DRV_RS5C313
1138         tristate "Ricoh RS5C313"
1139         depends on SH_LANDISK
1140         help
1141           If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1142 
1143 config RTC_DRV_GENERIC
1144         tristate "Generic RTC support"
1145         # Please consider writing a new RTC driver instead of using the generic
1146         # RTC abstraction
1147         depends on PARISC || M68K || PPC || SUPERH32
1148         help
1149           Say Y or M here to enable RTC support on systems using the generic
1150           RTC abstraction. If you do not know what you are doing, you should
1151           just say Y.
1152 
1153 config RTC_DRV_PXA
1154        tristate "PXA27x/PXA3xx"
1155        depends on ARCH_PXA
1156        help
1157          If you say Y here you will get access to the real time clock
1158          built into your PXA27x or PXA3xx CPU.
1159 
1160          This RTC driver uses PXA RTC registers available since pxa27x
1161          series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1162 
1163 config RTC_DRV_VT8500
1164         tristate "VIA/WonderMedia 85xx SoC RTC"
1165         depends on ARCH_VT8500
1166         help
1167           If you say Y here you will get access to the real time clock
1168           built into your VIA VT8500 SoC or its relatives.
1169 
1170 
1171 config RTC_DRV_SUN4V
1172         bool "SUN4V Hypervisor RTC"
1173         depends on SPARC64
1174         help
1175           If you say Y here you will get support for the Hypervisor
1176           based RTC on SUN4V systems.
1177 
1178 config RTC_DRV_SUNXI
1179         tristate "Allwinner sun4i/sun7i RTC"
1180         depends on ARCH_SUNXI
1181         help
1182           If you say Y here you will get support for the RTC found on
1183           Allwinner A10/A20.
1184 
1185 config RTC_DRV_STARFIRE
1186         bool "Starfire RTC"
1187         depends on SPARC64
1188         help
1189           If you say Y here you will get support for the RTC found on
1190           Starfire systems.
1191 
1192 config RTC_DRV_TX4939
1193         tristate "TX4939 SoC"
1194         depends on SOC_TX4939
1195         help
1196           Driver for the internal RTC (Realtime Clock) module found on
1197           Toshiba TX4939 SoC.
1198 
1199 config RTC_DRV_MV
1200         tristate "Marvell SoC RTC"
1201         depends on ARCH_KIRKWOOD || ARCH_DOVE || ARCH_MVEBU
1202         help
1203           If you say yes here you will get support for the in-chip RTC
1204           that can be found in some of Marvell's SoC devices, such as
1205           the Kirkwood 88F6281 and 88F6192.
1206 
1207           This driver can also be built as a module. If so, the module
1208           will be called rtc-mv.
1209 
1210 config RTC_DRV_PS3
1211         tristate "PS3 RTC"
1212         depends on PPC_PS3
1213         help
1214           If you say yes here you will get support for the RTC on PS3.
1215 
1216           This driver can also be built as a module. If so, the module
1217           will be called rtc-ps3.
1218 
1219 config RTC_DRV_COH901331
1220         tristate "ST-Ericsson COH 901 331 RTC"
1221         depends on ARCH_U300
1222         help
1223           If you say Y here you will get access to ST-Ericsson
1224           COH 901 331 RTC clock found in some ST-Ericsson Mobile
1225           Platforms.
1226 
1227           This driver can also be built as a module. If so, the module
1228           will be called "rtc-coh901331".
1229 
1230 
1231 config RTC_DRV_STMP
1232         tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1233         depends on ARCH_MXS
1234         help
1235           If you say yes here you will get support for the onboard
1236           STMP3xxx/i.MX23/i.MX28 RTC.
1237 
1238           This driver can also be built as a module. If so, the module
1239           will be called rtc-stmp3xxx.
1240 
1241 config RTC_DRV_PCAP
1242         tristate "PCAP RTC"
1243         depends on EZX_PCAP
1244         help
1245           If you say Y here you will get support for the RTC found on
1246           the PCAP2 ASIC used on some Motorola phones.
1247 
1248 config RTC_DRV_MC13XXX
1249         depends on MFD_MC13XXX
1250         tristate "Freescale MC13xxx RTC"
1251         help
1252           This enables support for the RTCs found on Freescale's PMICs
1253           MC13783 and MC13892.
1254 
1255 config RTC_DRV_MPC5121
1256         tristate "Freescale MPC5121 built-in RTC"
1257         depends on PPC_MPC512x || PPC_MPC52xx
1258         help
1259           If you say yes here you will get support for the
1260           built-in RTC on MPC5121 or on MPC5200.
1261 
1262           This driver can also be built as a module. If so, the module
1263           will be called rtc-mpc5121.
1264 
1265 config RTC_DRV_JZ4740
1266         tristate "Ingenic JZ4740 SoC"
1267         depends on MACH_JZ4740
1268         help
1269           If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1270           controller.
1271 
1272           This driver can also be buillt as a module. If so, the module
1273           will be called rtc-jz4740.
1274 
1275 config RTC_DRV_LPC32XX
1276         depends on ARCH_LPC32XX
1277         tristate "NXP LPC32XX RTC"
1278         help
1279           This enables support for the NXP RTC in the LPC32XX
1280 
1281           This driver can also be buillt as a module. If so, the module
1282           will be called rtc-lpc32xx.
1283 
1284 config RTC_DRV_PM8XXX
1285         tristate "Qualcomm PMIC8XXX RTC"
1286         depends on MFD_PM8XXX
1287         help
1288           If you say yes here you get support for the
1289           Qualcomm PMIC8XXX RTC.
1290 
1291           To compile this driver as a module, choose M here: the
1292           module will be called rtc-pm8xxx.
1293 
1294 config RTC_DRV_TEGRA
1295         tristate "NVIDIA Tegra Internal RTC driver"
1296         depends on ARCH_TEGRA
1297         help
1298           If you say yes here you get support for the
1299           Tegra 200 series internal RTC module.
1300 
1301           This drive can also be built as a module. If so, the module
1302           will be called rtc-tegra.
1303 
1304 config RTC_DRV_TILE
1305         tristate "Tilera hypervisor RTC support"
1306         depends on TILE
1307         help
1308           Enable support for the Linux driver side of the Tilera
1309           hypervisor's real-time clock interface.
1310 
1311 config RTC_DRV_PUV3
1312         tristate "PKUnity v3 RTC support"
1313         depends on ARCH_PUV3
1314         help
1315           This enables support for the RTC in the PKUnity-v3 SoCs.
1316 
1317           This drive can also be built as a module. If so, the module
1318           will be called rtc-puv3.
1319 
1320 config RTC_DRV_LOONGSON1
1321         tristate "loongson1 RTC support"
1322         depends on MACH_LOONGSON1
1323         help
1324           This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1325           counter) to be used as a RTC.
1326 
1327           This driver can also be built as a module. If so, the module
1328           will be called rtc-ls1x.
1329 
1330 config RTC_DRV_MXC
1331         tristate "Freescale MXC Real Time Clock"
1332         depends on ARCH_MXC
1333         help
1334            If you say yes here you get support for the Freescale MXC
1335            RTC module.
1336 
1337            This driver can also be built as a module, if so, the module
1338            will be called "rtc-mxc".
1339 
1340 config RTC_DRV_SNVS
1341         tristate "Freescale SNVS RTC support"
1342         depends on HAS_IOMEM
1343         depends on OF
1344         help
1345            If you say yes here you get support for the Freescale SNVS
1346            Low Power (LP) RTC module.
1347 
1348            This driver can also be built as a module, if so, the module
1349            will be called "rtc-snvs".
1350 
1351 config RTC_DRV_SIRFSOC
1352         tristate "SiRFSOC RTC"
1353         depends on ARCH_SIRF
1354         help
1355           Say "yes" here to support the real time clock on SiRF SOC chips.
1356           This driver can also be built as a module called rtc-sirfsoc.
1357 
1358 config RTC_DRV_MOXART
1359         tristate "MOXA ART RTC"
1360         depends on ARCH_MOXART || COMPILE_TEST
1361         help
1362            If you say yes here you get support for the MOXA ART
1363            RTC module.
1364 
1365            This driver can also be built as a module. If so, the module
1366            will be called rtc-moxart
1367 
1368 config RTC_DRV_XGENE
1369         tristate "APM X-Gene RTC"
1370         help
1371           If you say yes here you get support for the APM X-Gene SoC real time
1372           clock.
1373 
1374           This driver can also be built as a module, if so, the module
1375           will be called "rtc-xgene".
1376 
1377 comment "HID Sensor RTC drivers"
1378 
1379 config RTC_DRV_HID_SENSOR_TIME
1380         tristate "HID Sensor Time"
1381         depends on USB_HID
1382         select IIO
1383         select HID_SENSOR_HUB
1384         select HID_SENSOR_IIO_COMMON
1385         help
1386           Say yes here to build support for the HID Sensors of type Time.
1387           This drivers makes such sensors available as RTCs.
1388 
1389           If this driver is compiled as a module, it will be named
1390           rtc-hid-sensor-time.
1391 
1392 
1393 endif # RTC_CLASS

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