Root/drivers/rtc/Kconfig

Source at commit df1752a3ca1c25a4627735a04cf79da0fe44e6cd created 13 years 24 days ago.
By Peter Zotov, Add RTC platform device support for JZ4750.
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_DS3232
170    tristate "Dallas/Maxim DS3232"
171    depends on RTC_CLASS && I2C
172    help
173      If you say yes here you get support for Dallas Semiconductor
174      DS3232 real-time clock chips. If an interrupt is associated
175      with the device, the alarm functionality is supported.
176
177      This driver can also be built as a module. If so, the module
178      will be called rtc-ds3232.
179
180config RTC_DRV_MAX6900
181    tristate "Maxim MAX6900"
182    help
183      If you say yes here you will get support for the
184      Maxim MAX6900 I2C RTC chip.
185
186      This driver can also be built as a module. If so, the module
187      will be called rtc-max6900.
188
189config RTC_DRV_MAX8925
190    tristate "Maxim MAX8925"
191    depends on MFD_MAX8925
192    help
193      If you say yes here you will get support for the
194      RTC of Maxim MAX8925 PMIC.
195
196      This driver can also be built as a module. If so, the module
197      will be called rtc-max8925.
198
199config RTC_DRV_MAX8998
200    tristate "Maxim MAX8998"
201    depends on MFD_MAX8998
202    help
203      If you say yes here you will get support for the
204      RTC of Maxim MAX8998 PMIC.
205
206      This driver can also be built as a module. If so, the module
207      will be called rtc-max8998.
208
209config RTC_DRV_RS5C372
210    tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
211    help
212      If you say yes here you get support for the
213      Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
214
215      This driver can also be built as a module. If so, the module
216      will be called rtc-rs5c372.
217
218config RTC_DRV_ISL1208
219    tristate "Intersil ISL1208"
220    help
221      If you say yes here you get support for the
222      Intersil ISL1208 RTC chip.
223
224      This driver can also be built as a module. If so, the module
225      will be called rtc-isl1208.
226
227config RTC_DRV_ISL12022
228    tristate "Intersil ISL12022"
229    help
230      If you say yes here you get support for the
231      Intersil ISL12022 RTC chip.
232
233      This driver can also be built as a module. If so, the module
234      will be called rtc-isl12022.
235
236config RTC_DRV_X1205
237    tristate "Xicor/Intersil X1205"
238    help
239      If you say yes here you get support for the
240      Xicor/Intersil X1205 RTC chip.
241
242      This driver can also be built as a module. If so, the module
243      will be called rtc-x1205.
244
245config RTC_DRV_PCF8563
246    tristate "Philips PCF8563/Epson RTC8564"
247    help
248      If you say yes here you get support for the
249      Philips PCF8563 RTC chip. The Epson RTC8564
250      should work as well.
251
252      This driver can also be built as a module. If so, the module
253      will be called rtc-pcf8563.
254
255config RTC_DRV_PCF8583
256    tristate "Philips PCF8583"
257    help
258      If you say yes here you get support for the Philips PCF8583
259      RTC chip found on Acorn RiscPCs. This driver supports the
260      platform specific method of retrieving the current year from
261      the RTC's SRAM. It will work on other platforms with the same
262      chip, but the year will probably have to be tweaked.
263
264      This driver can also be built as a module. If so, the module
265      will be called rtc-pcf8583.
266
267config RTC_DRV_M41T80
268    tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
269    help
270      If you say Y here you will get support for the ST M41T60
271      and M41T80 RTC chips series. Currently, the following chips are
272      supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
273      M41ST85, and M41ST87.
274
275      This driver can also be built as a module. If so, the module
276      will be called rtc-m41t80.
277
278config RTC_DRV_M41T80_WDT
279    bool "ST M41T65/M41T80 series RTC watchdog timer"
280    depends on RTC_DRV_M41T80
281    help
282      If you say Y here you will get support for the
283      watchdog timer in the ST M41T60 and M41T80 RTC chips series.
284
285config RTC_DRV_BQ32K
286    tristate "TI BQ32000"
287    help
288      If you say Y here you will get support for the TI
289      BQ32000 I2C RTC chip.
290
291      This driver can also be built as a module. If so, the module
292      will be called rtc-bq32k.
293
294config RTC_DRV_DM355EVM
295    tristate "TI DaVinci DM355 EVM RTC"
296    depends on MFD_DM355EVM_MSP
297    help
298      Supports the RTC firmware in the MSP430 on the DM355 EVM.
299
300config RTC_DRV_TWL92330
301    boolean "TI TWL92330/Menelaus"
302    depends on MENELAUS
303    help
304      If you say yes here you get support for the RTC on the
305      TWL92330 "Menelaus" power management chip, used with OMAP2
306      platforms. The support is integrated with the rest of
307      the Menelaus driver; it's not separate module.
308
309config RTC_DRV_TWL4030
310    tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
311    depends on RTC_CLASS && TWL4030_CORE
312    help
313      If you say yes here you get support for the RTC on the
314      TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
315
316      This driver can also be built as a module. If so, the module
317      will be called rtc-twl.
318
319config RTC_DRV_S35390A
320    tristate "Seiko Instruments S-35390A"
321    select BITREVERSE
322    help
323      If you say yes here you will get support for the Seiko
324      Instruments S-35390A.
325
326      This driver can also be built as a module. If so the module
327      will be called rtc-s35390a.
328
329config RTC_DRV_FM3130
330    tristate "Ramtron FM3130"
331    help
332      If you say Y here you will get support for the
333      Ramtron FM3130 RTC chips.
334      Ramtron FM3130 is a chip with two separate devices inside,
335      RTC clock and FRAM. This driver provides only RTC functionality.
336
337      This driver can also be built as a module. If so the module
338      will be called rtc-fm3130.
339
340config RTC_DRV_RX8581
341    tristate "Epson RX-8581"
342    help
343      If you say yes here you will get support for the Epson RX-8581.
344
345      This driver can also be built as a module. If so the module
346      will be called rtc-rx8581.
347
348config RTC_DRV_RX8025
349    tristate "Epson RX-8025SA/NB"
350    help
351      If you say yes here you get support for the Epson
352      RX-8025SA/NB RTC chips.
353
354      This driver can also be built as a module. If so, the module
355      will be called rtc-rx8025.
356
357endif # I2C
358
359comment "SPI RTC drivers"
360
361if SPI_MASTER
362
363config RTC_DRV_M41T94
364    tristate "ST M41T94"
365    help
366      If you say yes here you will get support for the
367      ST M41T94 SPI RTC chip.
368
369      This driver can also be built as a module. If so, the module
370      will be called rtc-m41t94.
371
372config RTC_DRV_DS1305
373    tristate "Dallas/Maxim DS1305/DS1306"
374    help
375      Select this driver to get support for the Dallas/Maxim DS1305
376      and DS1306 real time clock chips. These support a trickle
377      charger, alarms, and NVRAM in addition to the clock.
378
379      This driver can also be built as a module. If so, the module
380      will be called rtc-ds1305.
381
382config RTC_DRV_DS1390
383    tristate "Dallas/Maxim DS1390/93/94"
384    help
385      If you say yes here you get support for the
386      Dallas/Maxim DS1390/93/94 chips.
387
388      This driver only supports the RTC feature, and not other chip
389      features such as alarms and trickle charging.
390
391      This driver can also be built as a module. If so, the module
392      will be called rtc-ds1390.
393
394config RTC_DRV_MAX6902
395    tristate "Maxim MAX6902"
396    help
397      If you say yes here you will get support for the
398      Maxim MAX6902 SPI RTC chip.
399
400      This driver can also be built as a module. If so, the module
401      will be called rtc-max6902.
402
403config RTC_DRV_R9701
404    tristate "Epson RTC-9701JE"
405    help
406      If you say yes here you will get support for the
407      Epson RTC-9701JE SPI RTC chip.
408
409      This driver can also be built as a module. If so, the module
410      will be called rtc-r9701.
411
412config RTC_DRV_RS5C348
413    tristate "Ricoh RS5C348A/B"
414    help
415      If you say yes here you get support for the
416      Ricoh RS5C348A and RS5C348B RTC chips.
417
418      This driver can also be built as a module. If so, the module
419      will be called rtc-rs5c348.
420
421config RTC_DRV_DS3234
422    tristate "Maxim/Dallas DS3234"
423    help
424      If you say yes here you get support for the
425      Maxim/Dallas DS3234 SPI RTC chip.
426
427      This driver can also be built as a module. If so, the module
428      will be called rtc-ds3234.
429
430config RTC_DRV_PCF2123
431    tristate "NXP PCF2123"
432    help
433      If you say yes here you get support for the NXP PCF2123
434      RTC chip.
435
436      This driver can also be built as a module. If so, the module
437      will be called rtc-pcf2123.
438
439endif # SPI_MASTER
440
441comment "Platform RTC drivers"
442
443# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
444# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
445# global rtc_lock ... it's not yet just another platform_device.
446
447config RTC_DRV_CMOS
448    tristate "PC-style 'CMOS'"
449    depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
450    default y if X86
451    help
452      Say "yes" here to get direct support for the real time clock
453      found in every PC or ACPI-based system, and some other boards.
454      Specifically the original MC146818, compatibles like those in
455      PC south bridges, the DS12887 or M48T86, some multifunction
456      or LPC bus chips, and so on.
457
458      Your system will need to define the platform device used by
459      this driver, otherwise it won't be accessible. This means
460      you can safely enable this driver if you don't know whether
461      or not your board has this kind of hardware.
462
463      This driver can also be built as a module. If so, the module
464      will be called rtc-cmos.
465
466config RTC_DRV_DS1216
467    tristate "Dallas DS1216"
468    depends on SNI_RM
469    help
470      If you say yes here you get support for the Dallas DS1216 RTC chips.
471
472config RTC_DRV_DS1286
473    tristate "Dallas DS1286"
474    help
475      If you say yes here you get support for the Dallas DS1286 RTC chips.
476
477config RTC_DRV_DS1302
478    tristate "Dallas DS1302"
479    depends on SH_SECUREEDGE5410
480    help
481      If you say yes here you get support for the Dallas DS1302 RTC chips.
482
483config RTC_DRV_DS1511
484    tristate "Dallas DS1511"
485    depends on RTC_CLASS
486    help
487      If you say yes here you get support for the
488      Dallas DS1511 timekeeping/watchdog chip.
489
490      This driver can also be built as a module. If so, the module
491      will be called rtc-ds1511.
492
493config RTC_DRV_DS1553
494    tristate "Maxim/Dallas DS1553"
495    help
496      If you say yes here you get support for the
497      Maxim/Dallas DS1553 timekeeping chip.
498
499      This driver can also be built as a module. If so, the module
500      will be called rtc-ds1553.
501
502config RTC_DRV_DS1742
503    tristate "Maxim/Dallas DS1742/1743"
504    help
505      If you say yes here you get support for the
506      Maxim/Dallas DS1742/1743 timekeeping chip.
507
508      This driver can also be built as a module. If so, the module
509      will be called rtc-ds1742.
510
511config RTC_DRV_EFI
512    tristate "EFI RTC"
513    depends on IA64
514    help
515      If you say yes here you will get support for the EFI
516      Real Time Clock.
517
518      This driver can also be built as a module. If so, the module
519      will be called rtc-efi.
520
521config RTC_DRV_STK17TA8
522    tristate "Simtek STK17TA8"
523    depends on RTC_CLASS
524    help
525      If you say yes here you get support for the
526      Simtek STK17TA8 timekeeping chip.
527
528      This driver can also be built as a module. If so, the module
529      will be called rtc-stk17ta8.
530
531config RTC_DRV_M48T86
532    tristate "ST M48T86/Dallas DS12887"
533    help
534      If you say Y here you will get support for the
535      ST M48T86 and Dallas DS12887 RTC chips.
536
537      This driver can also be built as a module. If so, the module
538      will be called rtc-m48t86.
539
540config RTC_DRV_M48T35
541    tristate "ST M48T35"
542    help
543      If you say Y here you will get support for the
544      ST M48T35 RTC chip.
545
546      This driver can also be built as a module, if so, the module
547      will be called "rtc-m48t35".
548
549config RTC_DRV_M48T59
550    tristate "ST M48T59/M48T08/M48T02"
551    help
552      If you say Y here you will get support for the
553      ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
554
555      These chips are usually found in Sun SPARC and UltraSPARC
556      workstations.
557
558      This driver can also be built as a module, if so, the module
559      will be called "rtc-m48t59".
560
561config RTC_DRV_MSM6242
562    tristate "Oki MSM6242"
563    help
564      If you say yes here you get support for the Oki MSM6242
565      timekeeping chip. It is used in some Amiga models (e.g. A2000).
566
567      This driver can also be built as a module. If so, the module
568      will be called rtc-msm6242.
569
570config RTC_DRV_IMXDI
571    tristate "Freescale IMX DryIce Real Time Clock"
572    depends on ARCH_MX25
573    depends on RTC_CLASS
574    help
575       Support for Freescale IMX DryIce RTC
576
577       This driver can also be built as a module, if so, the module
578       will be called "rtc-imxdi".
579
580config RTC_MXC
581    tristate "Freescale MXC Real Time Clock"
582    depends on ARCH_MXC
583    depends on RTC_CLASS
584    help
585       If you say yes here you get support for the Freescale MXC
586       RTC module.
587
588       This driver can also be built as a module, if so, the module
589       will be called "rtc-mxc".
590
591config RTC_DRV_BQ4802
592    tristate "TI BQ4802"
593    help
594      If you say Y here you will get support for the TI
595      BQ4802 RTC chip.
596
597      This driver can also be built as a module. If so, the module
598      will be called rtc-bq4802.
599
600config RTC_DRV_RP5C01
601    tristate "Ricoh RP5C01"
602    help
603      If you say yes here you get support for the Ricoh RP5C01
604      timekeeping chip. It is used in some Amiga models (e.g. A3000
605      and A4000).
606
607      This driver can also be built as a module. If so, the module
608      will be called rtc-rp5c01.
609
610config RTC_DRV_V3020
611    tristate "EM Microelectronic V3020"
612    help
613      If you say yes here you will get support for the
614      EM Microelectronic v3020 RTC chip.
615
616      This driver can also be built as a module. If so, the module
617      will be called rtc-v3020.
618
619config RTC_DRV_WM831X
620    tristate "Wolfson Microelectronics WM831x RTC"
621    depends on MFD_WM831X
622    help
623      If you say yes here you will get support for the RTC subsystem
624      of the Wolfson Microelectronics WM831X series PMICs.
625
626      This driver can also be built as a module. If so, the module
627      will be called "rtc-wm831x".
628
629config RTC_DRV_WM8350
630    tristate "Wolfson Microelectronics WM8350 RTC"
631    depends on MFD_WM8350
632    help
633      If you say yes here you will get support for the RTC subsystem
634      of the Wolfson Microelectronics WM8350.
635
636      This driver can also be built as a module. If so, the module
637      will be called "rtc-wm8350".
638
639config RTC_DRV_PCF50633
640    depends on MFD_PCF50633
641    tristate "NXP PCF50633 RTC"
642    help
643      If you say yes here you get support for the RTC subsystem of the
644      NXP PCF50633 used in embedded systems.
645
646config RTC_DRV_AB3100
647    tristate "ST-Ericsson AB3100 RTC"
648    depends on AB3100_CORE
649    default y if AB3100_CORE
650    help
651      Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
652      support. This chip contains a battery- and capacitor-backed RTC.
653
654config RTC_DRV_AB8500
655    tristate "ST-Ericsson AB8500 RTC"
656    depends on AB8500_CORE
657    help
658      Select this to enable the ST-Ericsson AB8500 power management IC RTC
659      support. This chip contains a battery- and capacitor-backed RTC.
660
661config RTC_DRV_NUC900
662    tristate "NUC910/NUC920 RTC driver"
663    depends on RTC_CLASS && ARCH_W90X900
664    help
665      If you say yes here you get support for the RTC subsystem of the
666      NUC910/NUC920 used in embedded systems.
667
668comment "on-CPU RTC drivers"
669
670config RTC_DRV_DAVINCI
671    tristate "TI DaVinci RTC"
672    depends on ARCH_DAVINCI_DM365
673    help
674      If you say yes here you get support for the RTC on the
675      DaVinci platforms (DM365).
676
677      This driver can also be built as a module. If so, the module
678      will be called rtc-davinci.
679
680config RTC_DRV_OMAP
681    tristate "TI OMAP1"
682    depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
683    help
684      Say "yes" here to support the real time clock on TI OMAP1 and
685      DA8xx/OMAP-L13x chips. This driver can also be built as a
686      module called rtc-omap.
687
688config HAVE_S3C_RTC
689    bool
690    help
691      This will include RTC support for Samsung SoCs. If
692      you want to include RTC support for any machine, kindly
693      select this in the respective mach-XXXX/Kconfig file.
694
695config RTC_DRV_S3C
696    tristate "Samsung S3C series SoC RTC"
697    depends on ARCH_S3C2410 || ARCH_S3C64XX || HAVE_S3C_RTC
698    help
699      RTC (Realtime Clock) driver for the clock inbuilt into the
700      Samsung S3C24XX series of SoCs. This can provide periodic
701      interrupt rates from 1Hz to 64Hz for user programs, and
702      wakeup from Alarm.
703
704      The driver currently supports the common features on all the
705      S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
706      and S3C2442.
707
708      This driver can also be build as a module. If so, the module
709      will be called rtc-s3c.
710
711config RTC_DRV_EP93XX
712    tristate "Cirrus Logic EP93XX"
713    depends on ARCH_EP93XX
714    help
715      If you say yes here you get support for the
716      RTC embedded in the Cirrus Logic EP93XX processors.
717
718      This driver can also be built as a module. If so, the module
719      will be called rtc-ep93xx.
720
721config RTC_DRV_SA1100
722    tristate "SA11x0/PXA2xx"
723    depends on ARCH_SA1100 || ARCH_PXA
724    help
725      If you say Y here you will get access to the real time clock
726      built into your SA11x0 or PXA2xx CPU.
727
728      To compile this driver as a module, choose M here: the
729      module will be called rtc-sa1100.
730
731config RTC_DRV_SH
732    tristate "SuperH On-Chip RTC"
733    depends on RTC_CLASS && SUPERH && HAVE_CLK
734    help
735      Say Y here to enable support for the on-chip RTC found in
736      most SuperH processors.
737
738       To compile this driver as a module, choose M here: the
739      module will be called rtc-sh.
740
741config RTC_DRV_VR41XX
742    tristate "NEC VR41XX"
743    depends on CPU_VR41XX
744    help
745      If you say Y here you will get access to the real time clock
746      built into your NEC VR41XX CPU.
747
748      To compile this driver as a module, choose M here: the
749      module will be called rtc-vr41xx.
750
751config RTC_DRV_PL030
752    tristate "ARM AMBA PL030 RTC"
753    depends on ARM_AMBA
754    help
755      If you say Y here you will get access to ARM AMBA
756      PrimeCell PL030 RTC found on certain ARM SOCs.
757
758      To compile this driver as a module, choose M here: the
759      module will be called rtc-pl030.
760
761config RTC_DRV_PL031
762    tristate "ARM AMBA PL031 RTC"
763    depends on ARM_AMBA
764    help
765      If you say Y here you will get access to ARM AMBA
766      PrimeCell PL031 RTC found on certain ARM SOCs.
767
768      To compile this driver as a module, choose M here: the
769      module will be called rtc-pl031.
770
771config RTC_DRV_AT32AP700X
772    tristate "AT32AP700X series RTC"
773    depends on PLATFORM_AT32AP
774    help
775      Driver for the internal RTC (Realtime Clock) on Atmel AVR32
776      AT32AP700x family processors.
777
778config RTC_DRV_AT91RM9200
779    tristate "AT91RM9200 or some AT91SAM9 RTC"
780    depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
781    help
782      Driver for the internal RTC (Realtime Clock) module found on
783      Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
784      this is powered by the backup power supply.
785
786config RTC_DRV_AT91SAM9
787    tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
788    depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
789    help
790      RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
791      (Real Time Timer). These timers are powered by the backup power
792      supply (such as a small coin cell battery), but do not need to
793      be used as RTCs.
794
795      (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
796      dedicated RTC module and leave the RTT available for other uses.)
797
798config RTC_DRV_AT91SAM9_RTT
799    int
800    range 0 1
801    default 0
802    prompt "RTT module Number" if ARCH_AT91SAM9263
803    depends on RTC_DRV_AT91SAM9
804    help
805      More than one RTT module is available. You can choose which
806      one will be used as an RTC. The default of zero is normally
807      OK to use, though some systems use that for non-RTC purposes.
808
809config RTC_DRV_AT91SAM9_GPBR
810    int
811    range 0 3 if !ARCH_AT91SAM9263
812    range 0 15 if ARCH_AT91SAM9263
813    default 0
814    prompt "Backup Register Number"
815    depends on RTC_DRV_AT91SAM9
816    help
817      The RTC driver needs to use one of the General Purpose Backup
818      Registers (GPBRs) as well as the RTT. You can choose which one
819      will be used. The default of zero is normally OK to use, but
820      on some systems other software needs to use that register.
821
822config RTC_DRV_AU1XXX
823    tristate "Au1xxx Counter0 RTC support"
824    depends on MIPS_ALCHEMY
825    help
826      This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
827      counter) to be used as a RTC.
828
829      This driver can also be built as a module. If so, the module
830      will be called rtc-au1xxx.
831
832config RTC_DRV_BFIN
833    tristate "Blackfin On-Chip RTC"
834    depends on BLACKFIN && !BF561
835    help
836      If you say yes here you will get support for the
837      Blackfin On-Chip Real Time Clock.
838
839      This driver can also be built as a module. If so, the module
840      will be called rtc-bfin.
841
842config RTC_DRV_RS5C313
843    tristate "Ricoh RS5C313"
844    depends on SH_LANDISK
845    help
846      If you say yes here you get support for the Ricoh RS5C313 RTC chips.
847
848config RTC_DRV_GENERIC
849    tristate "Generic RTC support"
850    # Please consider writing a new RTC driver instead of using the generic
851    # RTC abstraction
852    depends on PARISC || M68K || PPC || SUPERH32
853    help
854      Say Y or M here to enable RTC support on systems using the generic
855      RTC abstraction. If you do not know what you are doing, you should
856      just say Y.
857
858config RTC_DRV_PXA
859       tristate "PXA27x/PXA3xx"
860       depends on ARCH_PXA
861       help
862         If you say Y here you will get access to the real time clock
863         built into your PXA27x or PXA3xx CPU.
864
865         This RTC driver uses PXA RTC registers available since pxa27x
866         series (RDxR, RYxR) instead of legacy RCNR, RTAR.
867
868
869config RTC_DRV_SUN4V
870    bool "SUN4V Hypervisor RTC"
871    depends on SPARC64
872    help
873      If you say Y here you will get support for the Hypervisor
874      based RTC on SUN4V systems.
875
876config RTC_DRV_STARFIRE
877    bool "Starfire RTC"
878    depends on SPARC64
879    help
880      If you say Y here you will get support for the RTC found on
881      Starfire systems.
882
883config RTC_DRV_TX4939
884    tristate "TX4939 SoC"
885    depends on SOC_TX4939
886    help
887      Driver for the internal RTC (Realtime Clock) module found on
888      Toshiba TX4939 SoC.
889
890config RTC_DRV_MV
891    tristate "Marvell SoC RTC"
892    depends on ARCH_KIRKWOOD || ARCH_DOVE
893    help
894      If you say yes here you will get support for the in-chip RTC
895      that can be found in some of Marvell's SoC devices, such as
896      the Kirkwood 88F6281 and 88F6192.
897
898      This driver can also be built as a module. If so, the module
899      will be called rtc-mv.
900
901config RTC_DRV_PS3
902    tristate "PS3 RTC"
903    depends on PPC_PS3
904    help
905      If you say yes here you will get support for the RTC on PS3.
906
907      This driver can also be built as a module. If so, the module
908      will be called rtc-ps3.
909
910config RTC_DRV_COH901331
911    tristate "ST-Ericsson COH 901 331 RTC"
912    depends on ARCH_U300
913    help
914      If you say Y here you will get access to ST-Ericsson
915      COH 901 331 RTC clock found in some ST-Ericsson Mobile
916      Platforms.
917
918      This driver can also be built as a module. If so, the module
919      will be called "rtc-coh901331".
920
921
922config RTC_DRV_STMP
923    tristate "Freescale STMP3xxx RTC"
924    depends on ARCH_STMP3XXX
925    help
926      If you say yes here you will get support for the onboard
927      STMP3xxx RTC.
928
929      This driver can also be built as a module. If so, the module
930      will be called rtc-stmp3xxx.
931
932config RTC_DRV_PCAP
933    tristate "PCAP RTC"
934    depends on EZX_PCAP
935    help
936      If you say Y here you will get support for the RTC found on
937      the PCAP2 ASIC used on some Motorola phones.
938
939config RTC_DRV_MC13XXX
940    depends on MFD_MC13XXX
941    tristate "Freescale MC13xxx RTC"
942    help
943      This enables support for the RTCs found on Freescale's PMICs
944      MC13783 and MC13892.
945
946config RTC_DRV_MPC5121
947    tristate "Freescale MPC5121 built-in RTC"
948    depends on PPC_MPC512x && RTC_CLASS
949    help
950      If you say yes here you will get support for the
951      built-in RTC MPC5121.
952
953      This driver can also be built as a module. If so, the module
954      will be called rtc-mpc5121.
955
956config RTC_DRV_JZ4740
957    tristate "Ingenic JZ4740 SoC"
958    depends on RTC_CLASS
959    depends on MACH_JZ4740 || MACH_JZ4750
960    help
961      If you say yes here you get support for the Ingenic JZ4740 SoC RTC
962      controller.
963
964      This driver can also be buillt as a module. If so, the module
965      will be called rtc-jz4740.
966
967config RTC_DRV_LPC32XX
968    depends on ARCH_LPC32XX
969    tristate "NXP LPC32XX RTC"
970    help
971      This enables support for the NXP RTC in the LPC32XX
972
973      This driver can also be buillt as a module. If so, the module
974      will be called rtc-lpc32xx.
975
976endif # RTC_CLASS
977

Archive Download this file



interactive