Version:  2.0.40 2.2.26 2.4.37 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 3.18

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

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