Version:  2.0.40 2.2.26 2.4.37 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9

Linux/drivers/rtc/Kconfig

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

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