Root/drivers/rtc/Kconfig

Source at commit dd98c5ca8053f8955ce9da31c4dccc84ae29bec1 created 14 years 3 months ago.
By xiangfu, 052-rtc.patch
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_RS5C372
179    tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
180    help
181      If you say yes here you get support for the
182      Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
183
184      This driver can also be built as a module. If so, the module
185      will be called rtc-rs5c372.
186
187config RTC_DRV_ISL1208
188    tristate "Intersil ISL1208"
189    help
190      If you say yes here you get support for the
191      Intersil ISL1208 RTC chip.
192
193      This driver can also be built as a module. If so, the module
194      will be called rtc-isl1208.
195
196config RTC_DRV_X1205
197    tristate "Xicor/Intersil X1205"
198    help
199      If you say yes here you get support for the
200      Xicor/Intersil X1205 RTC chip.
201
202      This driver can also be built as a module. If so, the module
203      will be called rtc-x1205.
204
205config RTC_DRV_PCF8563
206    tristate "Philips PCF8563/Epson RTC8564"
207    help
208      If you say yes here you get support for the
209      Philips PCF8563 RTC chip. The Epson RTC8564
210      should work as well.
211
212      This driver can also be built as a module. If so, the module
213      will be called rtc-pcf8563.
214
215config RTC_DRV_PCF8583
216    tristate "Philips PCF8583"
217    help
218      If you say yes here you get support for the Philips PCF8583
219      RTC chip found on Acorn RiscPCs. This driver supports the
220      platform specific method of retrieving the current year from
221      the RTC's SRAM. It will work on other platforms with the same
222      chip, but the year will probably have to be tweaked.
223
224      This driver can also be built as a module. If so, the module
225      will be called rtc-pcf8583.
226
227config RTC_DRV_M41T80
228    tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
229    help
230      If you say Y here you will get support for the ST M41T60
231      and M41T80 RTC chips series. Currently, the following chips are
232      supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
233      M41ST85, and M41ST87.
234
235      This driver can also be built as a module. If so, the module
236      will be called rtc-m41t80.
237
238config RTC_DRV_M41T80_WDT
239    bool "ST M41T65/M41T80 series RTC watchdog timer"
240    depends on RTC_DRV_M41T80
241    help
242      If you say Y here you will get support for the
243      watchdog timer in the ST M41T60 and M41T80 RTC chips series.
244
245config RTC_DRV_DM355EVM
246    tristate "TI DaVinci DM355 EVM RTC"
247    depends on MFD_DM355EVM_MSP
248    help
249      Supports the RTC firmware in the MSP430 on the DM355 EVM.
250
251config RTC_DRV_TWL92330
252    boolean "TI TWL92330/Menelaus"
253    depends on MENELAUS
254    help
255      If you say yes here you get support for the RTC on the
256      TWL92330 "Menelaus" power management chip, used with OMAP2
257      platforms. The support is integrated with the rest of
258      the Menelaus driver; it's not separate module.
259
260config RTC_DRV_TWL4030
261    tristate "TI TWL4030/TWL5030/TPS659x0"
262    depends on RTC_CLASS && TWL4030_CORE
263    help
264      If you say yes here you get support for the RTC on the
265      TWL4030 family chips, used mostly with OMAP3 platforms.
266
267      This driver can also be built as a module. If so, the module
268      will be called rtc-twl4030.
269
270config RTC_DRV_S35390A
271    tristate "Seiko Instruments S-35390A"
272    select BITREVERSE
273    help
274      If you say yes here you will get support for the Seiko
275      Instruments S-35390A.
276
277      This driver can also be built as a module. If so the module
278      will be called rtc-s35390a.
279
280config RTC_DRV_FM3130
281    tristate "Ramtron FM3130"
282    help
283      If you say Y here you will get support for the
284      Ramtron FM3130 RTC chips.
285      Ramtron FM3130 is a chip with two separate devices inside,
286      RTC clock and FRAM. This driver provides only RTC functionality.
287
288      This driver can also be built as a module. If so the module
289      will be called rtc-fm3130.
290
291config RTC_DRV_RX8581
292    tristate "Epson RX-8581"
293    help
294      If you say yes here you will get support for the Epson RX-8581.
295
296      This driver can also be built as a module. If so the module
297      will be called rtc-rx8581.
298
299config RTC_DRV_RX8025
300    tristate "Epson RX-8025SA/NB"
301    help
302      If you say yes here you get support for the Epson
303      RX-8025SA/NB RTC chips.
304
305      This driver can also be built as a module. If so, the module
306      will be called rtc-rx8025.
307
308endif # I2C
309
310comment "SPI RTC drivers"
311
312if SPI_MASTER
313
314config RTC_DRV_M41T94
315    tristate "ST M41T94"
316    help
317      If you say yes here you will get support for the
318      ST M41T94 SPI RTC chip.
319
320      This driver can also be built as a module. If so, the module
321      will be called rtc-m41t94.
322
323config RTC_DRV_DS1305
324    tristate "Dallas/Maxim DS1305/DS1306"
325    help
326      Select this driver to get support for the Dallas/Maxim DS1305
327      and DS1306 real time clock chips. These support a trickle
328      charger, alarms, and NVRAM in addition to the clock.
329
330      This driver can also be built as a module. If so, the module
331      will be called rtc-ds1305.
332
333config RTC_DRV_DS1390
334    tristate "Dallas/Maxim DS1390/93/94"
335    help
336      If you say yes here you get support for the
337      Dallas/Maxim DS1390/93/94 chips.
338
339      This driver only supports the RTC feature, and not other chip
340      features such as alarms and trickle charging.
341
342      This driver can also be built as a module. If so, the module
343      will be called rtc-ds1390.
344
345config RTC_DRV_MAX6902
346    tristate "Maxim MAX6902"
347    help
348      If you say yes here you will get support for the
349      Maxim MAX6902 SPI RTC chip.
350
351      This driver can also be built as a module. If so, the module
352      will be called rtc-max6902.
353
354config RTC_DRV_R9701
355    tristate "Epson RTC-9701JE"
356    help
357      If you say yes here you will get support for the
358      Epson RTC-9701JE SPI RTC chip.
359
360      This driver can also be built as a module. If so, the module
361      will be called rtc-r9701.
362
363config RTC_DRV_RS5C348
364    tristate "Ricoh RS5C348A/B"
365    help
366      If you say yes here you get support for the
367      Ricoh RS5C348A and RS5C348B RTC chips.
368
369      This driver can also be built as a module. If so, the module
370      will be called rtc-rs5c348.
371
372config RTC_DRV_DS3234
373    tristate "Maxim/Dallas DS3234"
374    help
375      If you say yes here you get support for the
376      Maxim/Dallas DS3234 SPI RTC chip.
377
378      This driver can also be built as a module. If so, the module
379      will be called rtc-ds3234.
380
381endif # SPI_MASTER
382
383comment "Platform RTC drivers"
384
385# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
386# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
387# global rtc_lock ... it's not yet just another platform_device.
388
389config RTC_DRV_CMOS
390    tristate "PC-style 'CMOS'"
391    depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
392    default y if X86
393    help
394      Say "yes" here to get direct support for the real time clock
395      found in every PC or ACPI-based system, and some other boards.
396      Specifically the original MC146818, compatibles like those in
397      PC south bridges, the DS12887 or M48T86, some multifunction
398      or LPC bus chips, and so on.
399
400      Your system will need to define the platform device used by
401      this driver, otherwise it won't be accessible. This means
402      you can safely enable this driver if you don't know whether
403      or not your board has this kind of hardware.
404
405      This driver can also be built as a module. If so, the module
406      will be called rtc-cmos.
407
408config RTC_DRV_DS1216
409    tristate "Dallas DS1216"
410    depends on SNI_RM
411    help
412      If you say yes here you get support for the Dallas DS1216 RTC chips.
413
414config RTC_DRV_DS1286
415    tristate "Dallas DS1286"
416    help
417      If you say yes here you get support for the Dallas DS1286 RTC chips.
418
419config RTC_DRV_DS1302
420    tristate "Dallas DS1302"
421    depends on SH_SECUREEDGE5410
422    help
423      If you say yes here you get support for the Dallas DS1302 RTC chips.
424
425config RTC_DRV_DS1511
426    tristate "Dallas DS1511"
427    depends on RTC_CLASS
428    help
429      If you say yes here you get support for the
430      Dallas DS1511 timekeeping/watchdog chip.
431
432      This driver can also be built as a module. If so, the module
433      will be called rtc-ds1511.
434
435config RTC_DRV_DS1553
436    tristate "Maxim/Dallas DS1553"
437    help
438      If you say yes here you get support for the
439      Maxim/Dallas DS1553 timekeeping chip.
440
441      This driver can also be built as a module. If so, the module
442      will be called rtc-ds1553.
443
444config RTC_DRV_DS1742
445    tristate "Maxim/Dallas DS1742/1743"
446    help
447      If you say yes here you get support for the
448      Maxim/Dallas DS1742/1743 timekeeping chip.
449
450      This driver can also be built as a module. If so, the module
451      will be called rtc-ds1742.
452
453config RTC_DRV_EFI
454    tristate "EFI RTC"
455    depends on IA64
456    help
457      If you say yes here you will get support for the EFI
458      Real Time Clock.
459
460      This driver can also be built as a module. If so, the module
461      will be called rtc-efi.
462
463config RTC_DRV_JZ4740
464    tristate "Ingenic JZ4720/JZ4740 SoC"
465    depends on RTC_CLASS
466    depends on SOC_JZ4740
467    help
468      If you say yes here you get support for the
469      Ingenic JZ4720/JZ4740 SoC RTC controller.
470
471      This driver can also be buillt as a module. If so, the module
472      will be called rtc-jz4740.
473
474config RTC_DRV_STK17TA8
475    tristate "Simtek STK17TA8"
476    depends on RTC_CLASS
477    help
478      If you say yes here you get support for the
479      Simtek STK17TA8 timekeeping chip.
480
481      This driver can also be built as a module. If so, the module
482      will be called rtc-stk17ta8.
483
484config RTC_DRV_M48T86
485    tristate "ST M48T86/Dallas DS12887"
486    help
487      If you say Y here you will get support for the
488      ST M48T86 and Dallas DS12887 RTC chips.
489
490      This driver can also be built as a module. If so, the module
491      will be called rtc-m48t86.
492
493config RTC_DRV_M48T35
494    tristate "ST M48T35"
495    help
496      If you say Y here you will get support for the
497      ST M48T35 RTC chip.
498
499      This driver can also be built as a module, if so, the module
500      will be called "rtc-m48t35".
501
502config RTC_DRV_M48T59
503    tristate "ST M48T59/M48T08/M48T02"
504    help
505      If you say Y here you will get support for the
506      ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
507
508      These chips are usually found in Sun SPARC and UltraSPARC
509      workstations.
510
511      This driver can also be built as a module, if so, the module
512      will be called "rtc-m48t59".
513
514config RTC_DRV_BQ4802
515    tristate "TI BQ4802"
516    help
517      If you say Y here you will get support for the TI
518      BQ4802 RTC chip.
519
520      This driver can also be built as a module. If so, the module
521      will be called rtc-bq4802.
522
523config RTC_DRV_V3020
524    tristate "EM Microelectronic V3020"
525    help
526      If you say yes here you will get support for the
527      EM Microelectronic v3020 RTC chip.
528
529      This driver can also be built as a module. If so, the module
530      will be called rtc-v3020.
531
532config RTC_DRV_WM8350
533    tristate "Wolfson Microelectronics WM8350 RTC"
534    depends on MFD_WM8350
535    help
536      If you say yes here you will get support for the RTC subsystem
537      of the Wolfson Microelectronics WM8350.
538
539      This driver can also be built as a module. If so, the module
540      will be called "rtc-wm8350".
541
542config RTC_DRV_PCF50633
543    depends on MFD_PCF50633
544    tristate "NXP PCF50633 RTC"
545    help
546      If you say yes here you get support for the RTC subsystem of the
547      NXP PCF50633 used in embedded systems.
548
549config RTC_DRV_RTC7301
550    tristate "Epson RTC-7301 SF/DG"
551    help
552      If you say Y here you will get support for the
553      Epson RTC-7301 SF/DG RTC chips.
554
555      This driver can also be built as a module. If so, the module
556      will be called rtc-7301.
557
558comment "on-CPU RTC drivers"
559
560config RTC_DRV_OMAP
561    tristate "TI OMAP1"
562    depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730
563    help
564      Say "yes" here to support the real time clock on TI OMAP1 chips.
565      This driver can also be built as a module called rtc-omap.
566
567config RTC_DRV_S3C
568    tristate "Samsung S3C series SoC RTC"
569    depends on ARCH_S3C2410
570    help
571      RTC (Realtime Clock) driver for the clock inbuilt into the
572      Samsung S3C24XX series of SoCs. This can provide periodic
573      interrupt rates from 1Hz to 64Hz for user programs, and
574      wakeup from Alarm.
575
576      The driver currently supports the common features on all the
577      S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
578      and S3C2442.
579
580      This driver can also be build as a module. If so, the module
581      will be called rtc-s3c.
582
583config RTC_DRV_EP93XX
584    tristate "Cirrus Logic EP93XX"
585    depends on ARCH_EP93XX
586    help
587      If you say yes here you get support for the
588      RTC embedded in the Cirrus Logic EP93XX processors.
589
590      This driver can also be built as a module. If so, the module
591      will be called rtc-ep93xx.
592
593config RTC_DRV_SA1100
594    tristate "SA11x0/PXA2xx"
595    depends on ARCH_SA1100 || ARCH_PXA
596    help
597      If you say Y here you will get access to the real time clock
598      built into your SA11x0 or PXA2xx CPU.
599
600      To compile this driver as a module, choose M here: the
601      module will be called rtc-sa1100.
602
603config RTC_DRV_SH
604    tristate "SuperH On-Chip RTC"
605    depends on RTC_CLASS && SUPERH && HAVE_CLK
606    help
607      Say Y here to enable support for the on-chip RTC found in
608      most SuperH processors.
609
610       To compile this driver as a module, choose M here: the
611      module will be called rtc-sh.
612
613config RTC_DRV_VR41XX
614    tristate "NEC VR41XX"
615    depends on CPU_VR41XX
616    help
617      If you say Y here you will get access to the real time clock
618      built into your NEC VR41XX CPU.
619
620      To compile this driver as a module, choose M here: the
621      module will be called rtc-vr41xx.
622
623config RTC_DRV_PL030
624    tristate "ARM AMBA PL030 RTC"
625    depends on ARM_AMBA
626    help
627      If you say Y here you will get access to ARM AMBA
628      PrimeCell PL030 RTC found on certain ARM SOCs.
629
630      To compile this driver as a module, choose M here: the
631      module will be called rtc-pl030.
632
633config RTC_DRV_PL031
634    tristate "ARM AMBA PL031 RTC"
635    depends on ARM_AMBA
636    help
637      If you say Y here you will get access to ARM AMBA
638      PrimeCell PL031 RTC found on certain ARM SOCs.
639
640      To compile this driver as a module, choose M here: the
641      module will be called rtc-pl031.
642
643config RTC_DRV_AT32AP700X
644    tristate "AT32AP700X series RTC"
645    depends on PLATFORM_AT32AP
646    help
647      Driver for the internal RTC (Realtime Clock) on Atmel AVR32
648      AT32AP700x family processors.
649
650config RTC_DRV_AT91RM9200
651    tristate "AT91RM9200 or AT91SAM9RL"
652    depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
653    help
654      Driver for the internal RTC (Realtime Clock) module found on
655      Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips
656      this is powered by the backup power supply.
657
658config RTC_DRV_AT91SAM9
659    tristate "AT91SAM9x/AT91CAP9"
660    depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
661    help
662      RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
663      (Real Time Timer). These timers are powered by the backup power
664      supply (such as a small coin cell battery), but do not need to
665      be used as RTCs.
666
667      (On AT91SAM9rl chips you probably want to use the dedicated RTC
668      module and leave the RTT available for other uses.)
669
670config RTC_DRV_AT91SAM9_RTT
671    int
672    range 0 1
673    default 0
674    prompt "RTT module Number" if ARCH_AT91SAM9263
675    depends on RTC_DRV_AT91SAM9
676    help
677      More than one RTT module is available. You can choose which
678      one will be used as an RTC. The default of zero is normally
679      OK to use, though some systems use that for non-RTC purposes.
680
681config RTC_DRV_AT91SAM9_GPBR
682    int
683    range 0 3 if !ARCH_AT91SAM9263
684    range 0 15 if ARCH_AT91SAM9263
685    default 0
686    prompt "Backup Register Number"
687    depends on RTC_DRV_AT91SAM9
688    help
689      The RTC driver needs to use one of the General Purpose Backup
690      Registers (GPBRs) as well as the RTT. You can choose which one
691      will be used. The default of zero is normally OK to use, but
692      on some systems other software needs to use that register.
693
694config RTC_DRV_AU1XXX
695    tristate "Au1xxx Counter0 RTC support"
696    depends on SOC_AU1X00
697    help
698      This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
699      counter) to be used as a RTC.
700
701      This driver can also be built as a module. If so, the module
702      will be called rtc-au1xxx.
703
704config RTC_DRV_BFIN
705    tristate "Blackfin On-Chip RTC"
706    depends on BLACKFIN && !BF561
707    help
708      If you say yes here you will get support for the
709      Blackfin On-Chip Real Time Clock.
710
711      This driver can also be built as a module. If so, the module
712      will be called rtc-bfin.
713
714config RTC_DRV_RS5C313
715    tristate "Ricoh RS5C313"
716    depends on SH_LANDISK
717    help
718      If you say yes here you get support for the Ricoh RS5C313 RTC chips.
719
720config RTC_DRV_GENERIC
721    tristate "Generic RTC support"
722    # Please consider writing a new RTC driver instead of using the generic
723    # RTC abstraction
724    depends on PARISC || M68K || PPC || SUPERH32
725    help
726      Say Y or M here to enable RTC support on systems using the generic
727      RTC abstraction. If you do not know what you are doing, you should
728      just say Y.
729
730config RTC_DRV_PXA
731       tristate "PXA27x/PXA3xx"
732       depends on ARCH_PXA
733       help
734         If you say Y here you will get access to the real time clock
735         built into your PXA27x or PXA3xx CPU.
736
737         This RTC driver uses PXA RTC registers available since pxa27x
738         series (RDxR, RYxR) instead of legacy RCNR, RTAR.
739
740
741config RTC_DRV_SUN4V
742    bool "SUN4V Hypervisor RTC"
743    depends on SPARC64
744    help
745      If you say Y here you will get support for the Hypervisor
746      based RTC on SUN4V systems.
747
748config RTC_DRV_STARFIRE
749    bool "Starfire RTC"
750    depends on SPARC64
751    help
752      If you say Y here you will get support for the RTC found on
753      Starfire systems.
754
755config RTC_DRV_TX4939
756    tristate "TX4939 SoC"
757    depends on SOC_TX4939
758    help
759      Driver for the internal RTC (Realtime Clock) module found on
760      Toshiba TX4939 SoC.
761
762config RTC_DRV_MV
763    tristate "Marvell SoC RTC"
764    depends on ARCH_KIRKWOOD
765    help
766      If you say yes here you will get support for the in-chip RTC
767      that can be found in some of Marvell's SoC devices, such as
768      the Kirkwood 88F6281 and 88F6192.
769
770      This driver can also be built as a module. If so, the module
771      will be called rtc-mv.
772
773config RTC_DRV_PS3
774    tristate "PS3 RTC"
775    depends on PPC_PS3
776    help
777      If you say yes here you will get support for the RTC on PS3.
778
779      This driver can also be built as a module. If so, the module
780      will be called rtc-ps3.
781
782endif # RTC_CLASS
783

Archive Download this file



interactive