Root/drivers/rtc/Kconfig

1#
2# RTC class/drivers configuration
3#
4
5config RTC_LIB
6    tristate
7
8menuconfig RTC_CLASS
9    tristate "Real Time Clock"
10    default n
11    depends on !S390
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      This driver can also be built as a module. If so, the module
19      will be called rtc-core.
20
21if RTC_CLASS
22
23config RTC_HCTOSYS
24    bool "Set system time from RTC on startup and resume"
25    depends on RTC_CLASS = y
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
32config RTC_HCTOSYS_DEVICE
33    string "RTC used to set the system time"
34    depends on RTC_HCTOSYS = y
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
55config RTC_DEBUG
56    bool "RTC debug support"
57    depends on RTC_CLASS = y
58    help
59      Say yes here to enable debugging support in the RTC framework
60      and individual RTC drivers.
61
62comment "RTC interfaces"
63
64config RTC_INTF_SYSFS
65    boolean "/sys/class/rtc/rtcN (sysfs)"
66    depends on SYSFS
67    default RTC_CLASS
68    help
69      Say yes here if you want to use your RTCs using sysfs interfaces,
70      /sys/class/rtc/rtc0 through /sys/.../rtcN.
71
72      If unsure, say Y.
73
74config RTC_INTF_PROC
75    boolean "/proc/driver/rtc (procfs for rtc0)"
76    depends on PROC_FS
77    default RTC_CLASS
78    help
79      Say yes here if you want to use your first RTC through the proc
80      interface, /proc/driver/rtc. Other RTCs will not be available
81      through that API.
82
83      If unsure, say Y.
84
85config RTC_INTF_DEV
86    boolean "/dev/rtcN (character devices)"
87    default RTC_CLASS
88    help
89      Say yes here if you want to use your RTCs using the /dev
90      interfaces, which "udev" sets up as /dev/rtc0 through
91      /dev/rtcN.
92
93      You may want to set up a symbolic link so one of these
94      can be accessed as /dev/rtc, which is a name
95      expected by "hwclock" and some other programs. Recent
96      versions of "udev" are known to set up the symlink for you.
97
98      If unsure, say Y.
99
100config RTC_INTF_DEV_UIE_EMUL
101    bool "RTC UIE emulation on dev interface"
102    depends on RTC_INTF_DEV
103    help
104      Provides an emulation for RTC_UIE if the underlying rtc chip
105      driver does not expose RTC_UIE ioctls. Those requests generate
106      once-per-second update interrupts, used for synchronization.
107
108      The emulation code will read the time from the hardware
109      clock several times per second, please enable this option
110      only if you know that you really need it.
111
112config RTC_DRV_TEST
113    tristate "Test driver/device"
114    help
115      If you say yes here you get support for the
116      RTC test driver. It's a software RTC which can be
117      used to test the RTC subsystem APIs. It gets
118      the time from the system clock.
119      You want this driver only if you are doing development
120      on the RTC subsystem. Please read the source code
121      for further details.
122
123      This driver can also be built as a module. If so, the module
124      will be called rtc-test.
125
126comment "I2C RTC drivers"
127    depends on I2C
128
129if I2C
130
131config RTC_DRV_DS1307
132    tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
133    help
134      If you say yes here you get support for various compatible RTC
135      chips (often with battery backup) connected with I2C. This driver
136      should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
137      EPSON RX-8025 and probably other chips. In some cases the RTC
138      must already have been initialized (by manufacturing or a
139      bootloader).
140
141      The first seven registers on these chips hold an RTC, and other
142      registers may add features such as NVRAM, a trickle charger for
143      the RTC/NVRAM backup power, and alarms. NVRAM is visible in
144      sysfs, but other chip features may not be available.
145
146      This driver can also be built as a module. If so, the module
147      will be called rtc-ds1307.
148
149config RTC_DRV_DS1374
150    tristate "Dallas/Maxim DS1374"
151    depends on RTC_CLASS && I2C
152    help
153      If you say yes here you get support for Dallas Semiconductor
154      DS1374 real-time clock chips. If an interrupt is associated
155      with the device, the alarm functionality is supported.
156
157      This driver can also be built as a module. If so, the module
158      will be called rtc-ds1374.
159
160config RTC_DRV_DS1672
161    tristate "Dallas/Maxim DS1672"
162    help
163      If you say yes here you get support for the
164      Dallas/Maxim DS1672 timekeeping chip.
165
166      This driver can also be built as a module. If so, the module
167      will be called rtc-ds1672.
168
169config RTC_DRV_MAX6900
170    tristate "Maxim MAX6900"
171    help
172      If you say yes here you will get support for the
173      Maxim MAX6900 I2C RTC chip.
174
175      This driver can also be built as a module. If so, the module
176      will be called rtc-max6900.
177
178config RTC_DRV_MAX8925
179    tristate "Maxim MAX8925"
180    depends on MFD_MAX8925
181    help
182      If you say yes here you will get support for the
183      RTC of Maxim MAX8925 PMIC.
184
185      This driver can also be built as a module. If so, the module
186      will be called rtc-max8925.
187
188config RTC_DRV_RS5C372
189    tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
190    help
191      If you say yes here you get support for the
192      Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
193
194      This driver can also be built as a module. If so, the module
195      will be called rtc-rs5c372.
196
197config RTC_DRV_ISL1208
198    tristate "Intersil ISL1208"
199    help
200      If you say yes here you get support for the
201      Intersil ISL1208 RTC chip.
202
203      This driver can also be built as a module. If so, the module
204      will be called rtc-isl1208.
205
206config RTC_DRV_X1205
207    tristate "Xicor/Intersil X1205"
208    help
209      If you say yes here you get support for the
210      Xicor/Intersil X1205 RTC chip.
211
212      This driver can also be built as a module. If so, the module
213      will be called rtc-x1205.
214
215config RTC_DRV_PCF8563
216    tristate "Philips PCF8563/Epson RTC8564"
217    help
218      If you say yes here you get support for the
219      Philips PCF8563 RTC chip. The Epson RTC8564
220      should work as well.
221
222      This driver can also be built as a module. If so, the module
223      will be called rtc-pcf8563.
224
225config RTC_DRV_PCF8583
226    tristate "Philips PCF8583"
227    help
228      If you say yes here you get support for the Philips PCF8583
229      RTC chip found on Acorn RiscPCs. This driver supports the
230      platform specific method of retrieving the current year from
231      the RTC's SRAM. It will work on other platforms with the same
232      chip, but the year will probably have to be tweaked.
233
234      This driver can also be built as a module. If so, the module
235      will be called rtc-pcf8583.
236
237config RTC_DRV_M41T80
238    tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
239    help
240      If you say Y here you will get support for the ST M41T60
241      and M41T80 RTC chips series. Currently, the following chips are
242      supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
243      M41ST85, and M41ST87.
244
245      This driver can also be built as a module. If so, the module
246      will be called rtc-m41t80.
247
248config RTC_DRV_M41T80_WDT
249    bool "ST M41T65/M41T80 series RTC watchdog timer"
250    depends on RTC_DRV_M41T80
251    help
252      If you say Y here you will get support for the
253      watchdog timer in the ST M41T60 and M41T80 RTC chips series.
254
255config RTC_DRV_BQ32K
256    tristate "TI BQ32000"
257    help
258      If you say Y here you will get support for the TI
259      BQ32000 I2C RTC chip.
260
261      This driver can also be built as a module. If so, the module
262      will be called rtc-bq32k.
263
264config RTC_DRV_DM355EVM
265    tristate "TI DaVinci DM355 EVM RTC"
266    depends on MFD_DM355EVM_MSP
267    help
268      Supports the RTC firmware in the MSP430 on the DM355 EVM.
269
270config RTC_DRV_TWL92330
271    boolean "TI TWL92330/Menelaus"
272    depends on MENELAUS
273    help
274      If you say yes here you get support for the RTC on the
275      TWL92330 "Menelaus" power management chip, used with OMAP2
276      platforms. The support is integrated with the rest of
277      the Menelaus driver; it's not separate module.
278
279config RTC_DRV_TWL4030
280    tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
281    depends on RTC_CLASS && TWL4030_CORE
282    help
283      If you say yes here you get support for the RTC on the
284      TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
285
286      This driver can also be built as a module. If so, the module
287      will be called rtc-twl.
288
289config RTC_DRV_S35390A
290    tristate "Seiko Instruments S-35390A"
291    select BITREVERSE
292    help
293      If you say yes here you will get support for the Seiko
294      Instruments S-35390A.
295
296      This driver can also be built as a module. If so the module
297      will be called rtc-s35390a.
298
299config RTC_DRV_FM3130
300    tristate "Ramtron FM3130"
301    help
302      If you say Y here you will get support for the
303      Ramtron FM3130 RTC chips.
304      Ramtron FM3130 is a chip with two separate devices inside,
305      RTC clock and FRAM. This driver provides only RTC functionality.
306
307      This driver can also be built as a module. If so the module
308      will be called rtc-fm3130.
309
310config RTC_DRV_RX8581
311    tristate "Epson RX-8581"
312    help
313      If you say yes here you will get support for the Epson RX-8581.
314
315      This driver can also be built as a module. If so the module
316      will be called rtc-rx8581.
317
318config RTC_DRV_RX8025
319    tristate "Epson RX-8025SA/NB"
320    help
321      If you say yes here you get support for the Epson
322      RX-8025SA/NB RTC chips.
323
324      This driver can also be built as a module. If so, the module
325      will be called rtc-rx8025.
326
327endif # I2C
328
329comment "SPI RTC drivers"
330
331if SPI_MASTER
332
333config RTC_DRV_M41T94
334    tristate "ST M41T94"
335    help
336      If you say yes here you will get support for the
337      ST M41T94 SPI RTC chip.
338
339      This driver can also be built as a module. If so, the module
340      will be called rtc-m41t94.
341
342config RTC_DRV_DS1305
343    tristate "Dallas/Maxim DS1305/DS1306"
344    help
345      Select this driver to get support for the Dallas/Maxim DS1305
346      and DS1306 real time clock chips. These support a trickle
347      charger, alarms, and NVRAM in addition to the clock.
348
349      This driver can also be built as a module. If so, the module
350      will be called rtc-ds1305.
351
352config RTC_DRV_DS1390
353    tristate "Dallas/Maxim DS1390/93/94"
354    help
355      If you say yes here you get support for the
356      Dallas/Maxim DS1390/93/94 chips.
357
358      This driver only supports the RTC feature, and not other chip
359      features such as alarms and trickle charging.
360
361      This driver can also be built as a module. If so, the module
362      will be called rtc-ds1390.
363
364config RTC_DRV_MAX6902
365    tristate "Maxim MAX6902"
366    help
367      If you say yes here you will get support for the
368      Maxim MAX6902 SPI RTC chip.
369
370      This driver can also be built as a module. If so, the module
371      will be called rtc-max6902.
372
373config RTC_DRV_R9701
374    tristate "Epson RTC-9701JE"
375    help
376      If you say yes here you will get support for the
377      Epson RTC-9701JE SPI RTC chip.
378
379      This driver can also be built as a module. If so, the module
380      will be called rtc-r9701.
381
382config RTC_DRV_RS5C348
383    tristate "Ricoh RS5C348A/B"
384    help
385      If you say yes here you get support for the
386      Ricoh RS5C348A and RS5C348B RTC chips.
387
388      This driver can also be built as a module. If so, the module
389      will be called rtc-rs5c348.
390
391config RTC_DRV_DS3234
392    tristate "Maxim/Dallas DS3234"
393    help
394      If you say yes here you get support for the
395      Maxim/Dallas DS3234 SPI RTC chip.
396
397      This driver can also be built as a module. If so, the module
398      will be called rtc-ds3234.
399
400config RTC_DRV_PCF2123
401    tristate "NXP PCF2123"
402    help
403      If you say yes here you get support for the NXP PCF2123
404      RTC chip.
405
406      This driver can also be built as a module. If so, the module
407      will be called rtc-pcf2123.
408
409endif # SPI_MASTER
410
411comment "Platform RTC drivers"
412
413# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
414# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
415# global rtc_lock ... it's not yet just another platform_device.
416
417config RTC_DRV_CMOS
418    tristate "PC-style 'CMOS'"
419    depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
420    default y if X86
421    help
422      Say "yes" here to get direct support for the real time clock
423      found in every PC or ACPI-based system, and some other boards.
424      Specifically the original MC146818, compatibles like those in
425      PC south bridges, the DS12887 or M48T86, some multifunction
426      or LPC bus chips, and so on.
427
428      Your system will need to define the platform device used by
429      this driver, otherwise it won't be accessible. This means
430      you can safely enable this driver if you don't know whether
431      or not your board has this kind of hardware.
432
433      This driver can also be built as a module. If so, the module
434      will be called rtc-cmos.
435
436config RTC_DRV_DS1216
437    tristate "Dallas DS1216"
438    depends on SNI_RM
439    help
440      If you say yes here you get support for the Dallas DS1216 RTC chips.
441
442config RTC_DRV_DS1286
443    tristate "Dallas DS1286"
444    help
445      If you say yes here you get support for the Dallas DS1286 RTC chips.
446
447config RTC_DRV_DS1302
448    tristate "Dallas DS1302"
449    depends on SH_SECUREEDGE5410
450    help
451      If you say yes here you get support for the Dallas DS1302 RTC chips.
452
453config RTC_DRV_DS1511
454    tristate "Dallas DS1511"
455    depends on RTC_CLASS
456    help
457      If you say yes here you get support for the
458      Dallas DS1511 timekeeping/watchdog chip.
459
460      This driver can also be built as a module. If so, the module
461      will be called rtc-ds1511.
462
463config RTC_DRV_DS1553
464    tristate "Maxim/Dallas DS1553"
465    help
466      If you say yes here you get support for the
467      Maxim/Dallas DS1553 timekeeping chip.
468
469      This driver can also be built as a module. If so, the module
470      will be called rtc-ds1553.
471
472config RTC_DRV_DS1742
473    tristate "Maxim/Dallas DS1742/1743"
474    help
475      If you say yes here you get support for the
476      Maxim/Dallas DS1742/1743 timekeeping chip.
477
478      This driver can also be built as a module. If so, the module
479      will be called rtc-ds1742.
480
481config RTC_DRV_EFI
482    tristate "EFI RTC"
483    depends on IA64
484    help
485      If you say yes here you will get support for the EFI
486      Real Time Clock.
487
488      This driver can also be built as a module. If so, the module
489      will be called rtc-efi.
490
491config RTC_DRV_STK17TA8
492    tristate "Simtek STK17TA8"
493    depends on RTC_CLASS
494    help
495      If you say yes here you get support for the
496      Simtek STK17TA8 timekeeping chip.
497
498      This driver can also be built as a module. If so, the module
499      will be called rtc-stk17ta8.
500
501config RTC_DRV_M48T86
502    tristate "ST M48T86/Dallas DS12887"
503    help
504      If you say Y here you will get support for the
505      ST M48T86 and Dallas DS12887 RTC chips.
506
507      This driver can also be built as a module. If so, the module
508      will be called rtc-m48t86.
509
510config RTC_DRV_M48T35
511    tristate "ST M48T35"
512    help
513      If you say Y here you will get support for the
514      ST M48T35 RTC chip.
515
516      This driver can also be built as a module, if so, the module
517      will be called "rtc-m48t35".
518
519config RTC_DRV_M48T59
520    tristate "ST M48T59/M48T08/M48T02"
521    help
522      If you say Y here you will get support for the
523      ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
524
525      These chips are usually found in Sun SPARC and UltraSPARC
526      workstations.
527
528      This driver can also be built as a module, if so, the module
529      will be called "rtc-m48t59".
530
531config RTC_DRV_MSM6242
532    tristate "Oki MSM6242"
533    help
534      If you say yes here you get support for the Oki MSM6242
535      timekeeping chip. It is used in some Amiga models (e.g. A2000).
536
537      This driver can also be built as a module. If so, the module
538      will be called rtc-msm6242.
539
540config RTC_MXC
541    tristate "Freescale MXC Real Time Clock"
542    depends on ARCH_MXC
543    depends on RTC_CLASS
544    help
545       If you say yes here you get support for the Freescale MXC
546       RTC module.
547
548       This driver can also be built as a module, if so, the module
549       will be called "rtc-mxc".
550
551config RTC_DRV_BQ4802
552    tristate "TI BQ4802"
553    help
554      If you say Y here you will get support for the TI
555      BQ4802 RTC chip.
556
557      This driver can also be built as a module. If so, the module
558      will be called rtc-bq4802.
559
560config RTC_DRV_RP5C01
561    tristate "Ricoh RP5C01"
562    help
563      If you say yes here you get support for the Ricoh RP5C01
564      timekeeping chip. It is used in some Amiga models (e.g. A3000
565      and A4000).
566
567      This driver can also be built as a module. If so, the module
568      will be called rtc-rp5c01.
569
570config RTC_DRV_V3020
571    tristate "EM Microelectronic V3020"
572    help
573      If you say yes here you will get support for the
574      EM Microelectronic v3020 RTC chip.
575
576      This driver can also be built as a module. If so, the module
577      will be called rtc-v3020.
578
579config RTC_DRV_WM831X
580    tristate "Wolfson Microelectronics WM831x RTC"
581    depends on MFD_WM831X
582    help
583      If you say yes here you will get support for the RTC subsystem
584      of the Wolfson Microelectronics WM831X series PMICs.
585
586      This driver can also be built as a module. If so, the module
587      will be called "rtc-wm831x".
588
589config RTC_DRV_WM8350
590    tristate "Wolfson Microelectronics WM8350 RTC"
591    depends on MFD_WM8350
592    help
593      If you say yes here you will get support for the RTC subsystem
594      of the Wolfson Microelectronics WM8350.
595
596      This driver can also be built as a module. If so, the module
597      will be called "rtc-wm8350".
598
599config RTC_DRV_PCF50633
600    depends on MFD_PCF50633
601    tristate "NXP PCF50633 RTC"
602    help
603      If you say yes here you get support for the RTC subsystem of the
604      NXP PCF50633 used in embedded systems.
605
606config RTC_DRV_AB3100
607    tristate "ST-Ericsson AB3100 RTC"
608    depends on AB3100_CORE
609    default y if AB3100_CORE
610    help
611      Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
612      support. This chip contains a battery- and capacitor-backed RTC.
613
614config RTC_DRV_NUC900
615    tristate "NUC910/NUC920 RTC driver"
616    depends on RTC_CLASS && ARCH_W90X900
617    help
618      If you say yes here you get support for the RTC subsystem of the
619      NUC910/NUC920 used in embedded systems.
620
621comment "on-CPU RTC drivers"
622
623config RTC_DRV_OMAP
624    tristate "TI OMAP1"
625    depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
626    help
627      Say "yes" here to support the real time clock on TI OMAP1 and
628      DA8xx/OMAP-L13x chips. This driver can also be built as a
629      module called rtc-omap.
630
631config RTC_DRV_S3C
632    tristate "Samsung S3C series SoC RTC"
633    depends on ARCH_S3C2410
634    help
635      RTC (Realtime Clock) driver for the clock inbuilt into the
636      Samsung S3C24XX series of SoCs. This can provide periodic
637      interrupt rates from 1Hz to 64Hz for user programs, and
638      wakeup from Alarm.
639
640      The driver currently supports the common features on all the
641      S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
642      and S3C2442.
643
644      This driver can also be build as a module. If so, the module
645      will be called rtc-s3c.
646
647config RTC_DRV_EP93XX
648    tristate "Cirrus Logic EP93XX"
649    depends on ARCH_EP93XX
650    help
651      If you say yes here you get support for the
652      RTC embedded in the Cirrus Logic EP93XX processors.
653
654      This driver can also be built as a module. If so, the module
655      will be called rtc-ep93xx.
656
657config RTC_DRV_SA1100
658    tristate "SA11x0/PXA2xx"
659    depends on ARCH_SA1100 || ARCH_PXA
660    help
661      If you say Y here you will get access to the real time clock
662      built into your SA11x0 or PXA2xx CPU.
663
664      To compile this driver as a module, choose M here: the
665      module will be called rtc-sa1100.
666
667config RTC_DRV_SH
668    tristate "SuperH On-Chip RTC"
669    depends on RTC_CLASS && SUPERH && HAVE_CLK
670    help
671      Say Y here to enable support for the on-chip RTC found in
672      most SuperH processors.
673
674       To compile this driver as a module, choose M here: the
675      module will be called rtc-sh.
676
677config RTC_DRV_VR41XX
678    tristate "NEC VR41XX"
679    depends on CPU_VR41XX
680    help
681      If you say Y here you will get access to the real time clock
682      built into your NEC VR41XX CPU.
683
684      To compile this driver as a module, choose M here: the
685      module will be called rtc-vr41xx.
686
687config RTC_DRV_PL030
688    tristate "ARM AMBA PL030 RTC"
689    depends on ARM_AMBA
690    help
691      If you say Y here you will get access to ARM AMBA
692      PrimeCell PL030 RTC found on certain ARM SOCs.
693
694      To compile this driver as a module, choose M here: the
695      module will be called rtc-pl030.
696
697config RTC_DRV_PL031
698    tristate "ARM AMBA PL031 RTC"
699    depends on ARM_AMBA
700    help
701      If you say Y here you will get access to ARM AMBA
702      PrimeCell PL031 RTC found on certain ARM SOCs.
703
704      To compile this driver as a module, choose M here: the
705      module will be called rtc-pl031.
706
707config RTC_DRV_AT32AP700X
708    tristate "AT32AP700X series RTC"
709    depends on PLATFORM_AT32AP
710    help
711      Driver for the internal RTC (Realtime Clock) on Atmel AVR32
712      AT32AP700x family processors.
713
714config RTC_DRV_AT91RM9200
715    tristate "AT91RM9200 or AT91SAM9RL"
716    depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
717    help
718      Driver for the internal RTC (Realtime Clock) module found on
719      Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips
720      this is powered by the backup power supply.
721
722config RTC_DRV_AT91SAM9
723    tristate "AT91SAM9x/AT91CAP9"
724    depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
725    help
726      RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
727      (Real Time Timer). These timers are powered by the backup power
728      supply (such as a small coin cell battery), but do not need to
729      be used as RTCs.
730
731      (On AT91SAM9rl chips you probably want to use the dedicated RTC
732      module and leave the RTT available for other uses.)
733
734config RTC_DRV_AT91SAM9_RTT
735    int
736    range 0 1
737    default 0
738    prompt "RTT module Number" if ARCH_AT91SAM9263
739    depends on RTC_DRV_AT91SAM9
740    help
741      More than one RTT module is available. You can choose which
742      one will be used as an RTC. The default of zero is normally
743      OK to use, though some systems use that for non-RTC purposes.
744
745config RTC_DRV_AT91SAM9_GPBR
746    int
747    range 0 3 if !ARCH_AT91SAM9263
748    range 0 15 if ARCH_AT91SAM9263
749    default 0
750    prompt "Backup Register Number"
751    depends on RTC_DRV_AT91SAM9
752    help
753      The RTC driver needs to use one of the General Purpose Backup
754      Registers (GPBRs) as well as the RTT. You can choose which one
755      will be used. The default of zero is normally OK to use, but
756      on some systems other software needs to use that register.
757
758config RTC_DRV_AU1XXX
759    tristate "Au1xxx Counter0 RTC support"
760    depends on SOC_AU1X00
761    help
762      This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
763      counter) to be used as a RTC.
764
765      This driver can also be built as a module. If so, the module
766      will be called rtc-au1xxx.
767
768config RTC_DRV_BFIN
769    tristate "Blackfin On-Chip RTC"
770    depends on BLACKFIN && !BF561
771    help
772      If you say yes here you will get support for the
773      Blackfin On-Chip Real Time Clock.
774
775      This driver can also be built as a module. If so, the module
776      will be called rtc-bfin.
777
778config RTC_DRV_RS5C313
779    tristate "Ricoh RS5C313"
780    depends on SH_LANDISK
781    help
782      If you say yes here you get support for the Ricoh RS5C313 RTC chips.
783
784config RTC_DRV_GENERIC
785    tristate "Generic RTC support"
786    # Please consider writing a new RTC driver instead of using the generic
787    # RTC abstraction
788    depends on PARISC || M68K || PPC || SUPERH32
789    help
790      Say Y or M here to enable RTC support on systems using the generic
791      RTC abstraction. If you do not know what you are doing, you should
792      just say Y.
793
794config RTC_DRV_PXA
795       tristate "PXA27x/PXA3xx"
796       depends on ARCH_PXA
797       help
798         If you say Y here you will get access to the real time clock
799         built into your PXA27x or PXA3xx CPU.
800
801         This RTC driver uses PXA RTC registers available since pxa27x
802         series (RDxR, RYxR) instead of legacy RCNR, RTAR.
803
804
805config RTC_DRV_SUN4V
806    bool "SUN4V Hypervisor RTC"
807    depends on SPARC64
808    help
809      If you say Y here you will get support for the Hypervisor
810      based RTC on SUN4V systems.
811
812config RTC_DRV_STARFIRE
813    bool "Starfire RTC"
814    depends on SPARC64
815    help
816      If you say Y here you will get support for the RTC found on
817      Starfire systems.
818
819config RTC_DRV_TX4939
820    tristate "TX4939 SoC"
821    depends on SOC_TX4939
822    help
823      Driver for the internal RTC (Realtime Clock) module found on
824      Toshiba TX4939 SoC.
825
826config RTC_DRV_MV
827    tristate "Marvell SoC RTC"
828    depends on ARCH_KIRKWOOD || ARCH_DOVE
829    help
830      If you say yes here you will get support for the in-chip RTC
831      that can be found in some of Marvell's SoC devices, such as
832      the Kirkwood 88F6281 and 88F6192.
833
834      This driver can also be built as a module. If so, the module
835      will be called rtc-mv.
836
837config RTC_DRV_PS3
838    tristate "PS3 RTC"
839    depends on PPC_PS3
840    help
841      If you say yes here you will get support for the RTC on PS3.
842
843      This driver can also be built as a module. If so, the module
844      will be called rtc-ps3.
845
846config RTC_DRV_COH901331
847    tristate "ST-Ericsson COH 901 331 RTC"
848    depends on ARCH_U300
849    help
850      If you say Y here you will get access to ST-Ericsson
851      COH 901 331 RTC clock found in some ST-Ericsson Mobile
852      Platforms.
853
854      This driver can also be built as a module. If so, the module
855      will be called "rtc-coh901331".
856
857
858config RTC_DRV_STMP
859    tristate "Freescale STMP3xxx RTC"
860    depends on ARCH_STMP3XXX
861    help
862      If you say yes here you will get support for the onboard
863      STMP3xxx RTC.
864
865      This driver can also be built as a module. If so, the module
866      will be called rtc-stmp3xxx.
867
868config RTC_DRV_PCAP
869    tristate "PCAP RTC"
870    depends on EZX_PCAP
871    help
872      If you say Y here you will get support for the RTC found on
873      the PCAP2 ASIC used on some Motorola phones.
874
875config RTC_DRV_MC13783
876    depends on MFD_MC13783
877    tristate "Freescale MC13783 RTC"
878    help
879      This enables support for the Freescale MC13783 PMIC RTC
880
881config RTC_DRV_MPC5121
882    tristate "Freescale MPC5121 built-in RTC"
883    depends on PPC_MPC512x && RTC_CLASS
884    help
885      If you say yes here you will get support for the
886      built-in RTC MPC5121.
887
888      This driver can also be built as a module. If so, the module
889      will be called rtc-mpc5121.
890
891config RTC_DRV_JZ4740
892    tristate "Ingenic JZ4740 SoC"
893    depends on RTC_CLASS
894    depends on SOC_JZ4740
895    help
896      If you say yes here you get support for the
897      Ingenic JZ4740 SoC RTC controller.
898
899      This driver can also be buillt as a module. If so, the module
900      will be called rtc-jz4740.
901
902endif # RTC_CLASS
903

Archive Download this file



interactive