1 #
2 # RTC class/drivers configuration
3 #
5 config RTC_LIB
6 bool
8 menuconfig RTC_CLASS
9 bool "Real Time Clock"
10 default n
11 depends on !S390 && !UML
12 select RTC_LIB
13 help
14 Generic RTC class support. If you say yes here, you will
15 be allowed to plug one or more RTCs to your system. You will
16 probably want to enable one or more of the interfaces below.
18 if RTC_CLASS
20 config RTC_HCTOSYS
21 bool "Set system time from RTC on startup and resume"
22 default y
23 help
24 If you say yes here, the system time (wall clock) will be set using
25 the value read from a specified RTC device. This is useful to avoid
26 unnecessary fsck runs at boot time, and to network better.
28 config RTC_HCTOSYS_DEVICE
29 string "RTC used to set the system time"
30 depends on RTC_HCTOSYS = y
31 default "rtc0"
32 help
33 The RTC device that will be used to (re)initialize the system
34 clock, usually rtc0. Initialization is done when the system
35 starts up, and when it resumes from a low power state. This
36 device should record time in UTC, since the kernel won't do
37 timezone correction.
39 The driver for this RTC device must be loaded before late_initcall
40 functions run, so it must usually be statically linked.
42 This clock should be battery-backed, so that it reads the correct
43 time when the system boots from a power-off state. Otherwise, your
44 system will need an external clock source (like an NTP server).
46 If the clock you specify here is not battery backed, it may still
47 be useful to reinitialize system time when resuming from system
48 sleep states. Do not specify an RTC here unless it stays powered
49 during all this system's supported sleep states.
51 config RTC_DEBUG
52 bool "RTC debug support"
53 help
54 Say yes here to enable debugging support in the RTC framework
55 and individual RTC drivers.
57 comment "RTC interfaces"
59 config RTC_INTF_SYSFS
60 boolean "/sys/class/rtc/rtcN (sysfs)"
61 depends on SYSFS
62 default RTC_CLASS
63 help
64 Say yes here if you want to use your RTCs using sysfs interfaces,
65 /sys/class/rtc/rtc0 through /sys/.../rtcN.
67 If unsure, say Y.
69 config RTC_INTF_PROC
70 boolean "/proc/driver/rtc (procfs for rtcN)"
71 depends on PROC_FS
72 default RTC_CLASS
73 help
74 Say yes here if you want to use your system clock RTC through
75 the proc interface, /proc/driver/rtc.
76 Other RTCs will not be available through that API.
77 If there is no RTC for the system clock, then the first RTC(rtc0)
78 is used by default.
80 If unsure, say Y.
82 config RTC_INTF_DEV
83 boolean "/dev/rtcN (character devices)"
84 default RTC_CLASS
85 help
86 Say yes here if you want to use your RTCs using the /dev
87 interfaces, which "udev" sets up as /dev/rtc0 through
88 /dev/rtcN.
90 You may want to set up a symbolic link so one of these
91 can be accessed as /dev/rtc, which is a name
92 expected by "hwclock" and some other programs. Recent
93 versions of "udev" are known to set up the symlink for you.
95 If unsure, say Y.
97 config RTC_INTF_DEV_UIE_EMUL
98 bool "RTC UIE emulation on dev interface"
99 depends on RTC_INTF_DEV
100 help
101 Provides an emulation for RTC_UIE if the underlying rtc chip
102 driver does not expose RTC_UIE ioctls. Those requests generate
103 once-per-second update interrupts, used for synchronization.
105 The emulation code will read the time from the hardware
106 clock several times per second, please enable this option
107 only if you know that you really need it.
109 config RTC_DRV_TEST
110 tristate "Test driver/device"
111 help
112 If you say yes here you get support for the
113 RTC test driver. It's a software RTC which can be
114 used to test the RTC subsystem APIs. It gets
115 the time from the system clock.
116 You want this driver only if you are doing development
117 on the RTC subsystem. Please read the source code
118 for further details.
120 This driver can also be built as a module. If so, the module
121 will be called rtc-test.
123 comment "I2C RTC drivers"
124 depends on I2C
126 if I2C
128 config RTC_DRV_88PM860X
129 tristate "Marvell 88PM860x"
130 depends on I2C && MFD_88PM860X
131 help
132 If you say yes here you get support for RTC function in Marvell
133 88PM860x chips.
135 This driver can also be built as a module. If so, the module
136 will be called rtc-88pm860x.
138 config RTC_DRV_88PM80X
139 tristate "Marvell 88PM80x"
140 depends on I2C && MFD_88PM800
141 help
142 If you say yes here you get support for RTC function in Marvell
143 88PM80x chips.
145 This driver can also be built as a module. If so, the module
146 will be called rtc-88pm80x.
148 config RTC_DRV_DS1307
149 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
150 help
151 If you say yes here you get support for various compatible RTC
152 chips (often with battery backup) connected with I2C. This driver
153 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
154 EPSON RX-8025 and probably other chips. In some cases the RTC
155 must already have been initialized (by manufacturing or a
156 bootloader).
158 The first seven registers on these chips hold an RTC, and other
159 registers may add features such as NVRAM, a trickle charger for
160 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
161 sysfs, but other chip features may not be available.
163 This driver can also be built as a module. If so, the module
164 will be called rtc-ds1307.
166 config RTC_DRV_DS1374
167 tristate "Dallas/Maxim DS1374"
168 depends on I2C
169 help
170 If you say yes here you get support for Dallas Semiconductor
171 DS1374 real-time clock chips. If an interrupt is associated
172 with the device, the alarm functionality is supported.
174 This driver can also be built as a module. If so, the module
175 will be called rtc-ds1374.
177 config RTC_DRV_DS1672
178 tristate "Dallas/Maxim DS1672"
179 help
180 If you say yes here you get support for the
181 Dallas/Maxim DS1672 timekeeping chip.
183 This driver can also be built as a module. If so, the module
184 will be called rtc-ds1672.
186 config RTC_DRV_DS3232
187 tristate "Dallas/Maxim DS3232"
188 depends on I2C
189 help
190 If you say yes here you get support for Dallas Semiconductor
191 DS3232 real-time clock chips. If an interrupt is associated
192 with the device, the alarm functionality is supported.
194 This driver can also be built as a module. If so, the module
195 will be called rtc-ds3232.
197 config RTC_DRV_MAX6900
198 tristate "Maxim MAX6900"
199 help
200 If you say yes here you will get support for the
201 Maxim MAX6900 I2C RTC chip.
203 This driver can also be built as a module. If so, the module
204 will be called rtc-max6900.
206 config RTC_DRV_MAX8907
207 tristate "Maxim MAX8907"
208 depends on MFD_MAX8907
209 help
210 If you say yes here you will get support for the
211 RTC of Maxim MAX8907 PMIC.
213 This driver can also be built as a module. If so, the module
214 will be called rtc-max8907.
216 config RTC_DRV_MAX8925
217 tristate "Maxim MAX8925"
218 depends on MFD_MAX8925
219 help
220 If you say yes here you will get support for the
221 RTC of Maxim MAX8925 PMIC.
223 This driver can also be built as a module. If so, the module
224 will be called rtc-max8925.
226 config RTC_DRV_MAX8998
227 tristate "Maxim MAX8998"
228 depends on MFD_MAX8998
229 help
230 If you say yes here you will get support for the
231 RTC of Maxim MAX8998 PMIC.
233 This driver can also be built as a module. If so, the module
234 will be called rtc-max8998.
236 config RTC_DRV_RS5C372
237 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
238 help
239 If you say yes here you get support for the
240 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
242 This driver can also be built as a module. If so, the module
243 will be called rtc-rs5c372.
245 config RTC_DRV_ISL1208
246 tristate "Intersil ISL1208"
247 help
248 If you say yes here you get support for the
249 Intersil ISL1208 RTC chip.
251 This driver can also be built as a module. If so, the module
252 will be called rtc-isl1208.
254 config RTC_DRV_ISL12022
255 tristate "Intersil ISL12022"
256 help
257 If you say yes here you get support for the
258 Intersil ISL12022 RTC chip.
260 This driver can also be built as a module. If so, the module
261 will be called rtc-isl12022.
263 config RTC_DRV_X1205
264 tristate "Xicor/Intersil X1205"
265 help
266 If you say yes here you get support for the
267 Xicor/Intersil X1205 RTC chip.
269 This driver can also be built as a module. If so, the module
270 will be called rtc-x1205.
272 config RTC_DRV_PALMAS
273 tristate "TI Palmas RTC driver"
274 depends on MFD_PALMAS
275 help
276 If you say yes here you get support for the RTC of TI PALMA series PMIC
277 chips.
279 This driver can also be built as a module. If so, the module
280 will be called rtc-palma.
282 config RTC_DRV_PCF8523
283 tristate "NXP PCF8523"
284 help
285 If you say yes here you get support for the NXP PCF8523 RTC
286 chips.
288 This driver can also be built as a module. If so, the module
289 will be called rtc-pcf8523.
291 config RTC_DRV_PCF8563
292 tristate "Philips PCF8563/Epson RTC8564"
293 help
294 If you say yes here you get support for the
295 Philips PCF8563 RTC chip. The Epson RTC8564
296 should work as well.
298 This driver can also be built as a module. If so, the module
299 will be called rtc-pcf8563.
301 config RTC_DRV_PCF8583
302 tristate "Philips PCF8583"
303 help
304 If you say yes here you get support for the Philips PCF8583
305 RTC chip found on Acorn RiscPCs. This driver supports the
306 platform specific method of retrieving the current year from
307 the RTC's SRAM. It will work on other platforms with the same
308 chip, but the year will probably have to be tweaked.
310 This driver can also be built as a module. If so, the module
311 will be called rtc-pcf8583.
313 config RTC_DRV_M41T80
314 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
315 help
316 If you say Y here you will get support for the ST M41T60
317 and M41T80 RTC chips series. Currently, the following chips are
318 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
319 M41ST85, and M41ST87.
321 This driver can also be built as a module. If so, the module
322 will be called rtc-m41t80.
324 config RTC_DRV_M41T80_WDT
325 bool "ST M41T65/M41T80 series RTC watchdog timer"
326 depends on RTC_DRV_M41T80
327 help
328 If you say Y here you will get support for the
329 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
331 config RTC_DRV_BQ32K
332 tristate "TI BQ32000"
333 help
334 If you say Y here you will get support for the TI
335 BQ32000 I2C RTC chip.
337 This driver can also be built as a module. If so, the module
338 will be called rtc-bq32k.
340 config RTC_DRV_DM355EVM
341 tristate "TI DaVinci DM355 EVM RTC"
342 depends on MFD_DM355EVM_MSP
343 help
344 Supports the RTC firmware in the MSP430 on the DM355 EVM.
346 config RTC_DRV_TWL92330
347 boolean "TI TWL92330/Menelaus"
348 depends on MENELAUS
349 help
350 If you say yes here you get support for the RTC on the
351 TWL92330 "Menelaus" power management chip, used with OMAP2
352 platforms. The support is integrated with the rest of
353 the Menelaus driver; it's not separate module.
355 config RTC_DRV_TWL4030
356 tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
357 depends on TWL4030_CORE
358 help
359 If you say yes here you get support for the RTC on the
360 TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
362 This driver can also be built as a module. If so, the module
363 will be called rtc-twl.
365 config RTC_DRV_TPS6586X
366 tristate "TI TPS6586X RTC driver"
367 depends on MFD_TPS6586X
368 help
369 TI Power Managment IC TPS6586X supports RTC functionality
370 along with alarm. This driver supports the RTC driver for
371 the TPS6586X RTC module.
373 config RTC_DRV_TPS65910
374 tristate "TI TPS65910 RTC driver"
375 depends on RTC_CLASS && MFD_TPS65910
376 help
377 If you say yes here you get support for the RTC on the
378 TPS65910 chips.
380 This driver can also be built as a module. If so, the module
381 will be called rtc-tps65910.
383 config RTC_DRV_RC5T583
384 tristate "RICOH 5T583 RTC driver"
385 depends on MFD_RC5T583
386 help
387 If you say yes here you get support for the RTC on the
388 RICOH 5T583 chips.
390 This driver can also be built as a module. If so, the module
391 will be called rtc-rc5t583.
393 config RTC_DRV_S35390A
394 tristate "Seiko Instruments S-35390A"
395 select BITREVERSE
396 help
397 If you say yes here you will get support for the Seiko
398 Instruments S-35390A.
400 This driver can also be built as a module. If so the module
401 will be called rtc-s35390a.
403 config RTC_DRV_FM3130
404 tristate "Ramtron FM3130"
405 help
406 If you say Y here you will get support for the
407 Ramtron FM3130 RTC chips.
408 Ramtron FM3130 is a chip with two separate devices inside,
409 RTC clock and FRAM. This driver provides only RTC functionality.
411 This driver can also be built as a module. If so the module
412 will be called rtc-fm3130.
414 config RTC_DRV_RX8581
415 tristate "Epson RX-8581"
416 help
417 If you say yes here you will get support for the Epson RX-8581.
419 This driver can also be built as a module. If so the module
420 will be called rtc-rx8581.
422 config RTC_DRV_RX8025
423 tristate "Epson RX-8025SA/NB"
424 help
425 If you say yes here you get support for the Epson
426 RX-8025SA/NB RTC chips.
428 This driver can also be built as a module. If so, the module
429 will be called rtc-rx8025.
431 config RTC_DRV_EM3027
432 tristate "EM Microelectronic EM3027"
433 help
434 If you say yes here you get support for the EM
435 Microelectronic EM3027 RTC chips.
437 This driver can also be built as a module. If so, the module
438 will be called rtc-em3027.
440 config RTC_DRV_RV3029C2
441 tristate "Micro Crystal RTC"
442 help
443 If you say yes here you get support for the Micro Crystal
444 RV3029-C2 RTC chips.
446 This driver can also be built as a module. If so, the module
447 will be called rtc-rv3029c2.
449 endif # I2C
451 comment "SPI RTC drivers"
453 if SPI_MASTER
455 config RTC_DRV_M41T93
456 tristate "ST M41T93"
457 help
458 If you say yes here you will get support for the
459 ST M41T93 SPI RTC chip.
461 This driver can also be built as a module. If so, the module
462 will be called rtc-m41t93.
464 config RTC_DRV_M41T94
465 tristate "ST M41T94"
466 help
467 If you say yes here you will get support for the
468 ST M41T94 SPI RTC chip.
470 This driver can also be built as a module. If so, the module
471 will be called rtc-m41t94.
473 config RTC_DRV_DS1305
474 tristate "Dallas/Maxim DS1305/DS1306"
475 help
476 Select this driver to get support for the Dallas/Maxim DS1305
477 and DS1306 real time clock chips. These support a trickle
478 charger, alarms, and NVRAM in addition to the clock.
480 This driver can also be built as a module. If so, the module
481 will be called rtc-ds1305.
483 config RTC_DRV_DS1390
484 tristate "Dallas/Maxim DS1390/93/94"
485 help
486 If you say yes here you get support for the
487 Dallas/Maxim DS1390/93/94 chips.
489 This driver only supports the RTC feature, and not other chip
490 features such as alarms and trickle charging.
492 This driver can also be built as a module. If so, the module
493 will be called rtc-ds1390.
495 config RTC_DRV_MAX6902
496 tristate "Maxim MAX6902"
497 help
498 If you say yes here you will get support for the
499 Maxim MAX6902 SPI RTC chip.
501 This driver can also be built as a module. If so, the module
502 will be called rtc-max6902.
504 config RTC_DRV_R9701
505 tristate "Epson RTC-9701JE"
506 help
507 If you say yes here you will get support for the
508 Epson RTC-9701JE SPI RTC chip.
510 This driver can also be built as a module. If so, the module
511 will be called rtc-r9701.
513 config RTC_DRV_RS5C348
514 tristate "Ricoh RS5C348A/B"
515 help
516 If you say yes here you get support for the
517 Ricoh RS5C348A and RS5C348B RTC chips.
519 This driver can also be built as a module. If so, the module
520 will be called rtc-rs5c348.
522 config RTC_DRV_DS3234
523 tristate "Maxim/Dallas DS3234"
524 help
525 If you say yes here you get support for the
526 Maxim/Dallas DS3234 SPI RTC chip.
528 This driver can also be built as a module. If so, the module
529 will be called rtc-ds3234.
531 config RTC_DRV_PCF2123
532 tristate "NXP PCF2123"
533 help
534 If you say yes here you get support for the NXP PCF2123
535 RTC chip.
537 This driver can also be built as a module. If so, the module
538 will be called rtc-pcf2123.
540 endif # SPI_MASTER
542 comment "Platform RTC drivers"
544 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
545 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
546 # global rtc_lock ... it's not yet just another platform_device.
548 config RTC_DRV_CMOS
549 tristate "PC-style 'CMOS'"
550 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
551 default y if X86
552 help
553 Say "yes" here to get direct support for the real time clock
554 found in every PC or ACPI-based system, and some other boards.
555 Specifically the original MC146818, compatibles like those in
556 PC south bridges, the DS12887 or M48T86, some multifunction
557 or LPC bus chips, and so on.
559 Your system will need to define the platform device used by
560 this driver, otherwise it won't be accessible. This means
561 you can safely enable this driver if you don't know whether
562 or not your board has this kind of hardware.
564 This driver can also be built as a module. If so, the module
565 will be called rtc-cmos.
567 config RTC_DRV_VRTC
568 tristate "Virtual RTC for Intel MID platforms"
569 depends on X86_INTEL_MID
570 default y if X86_INTEL_MID
572 help
573 Say "yes" here to get direct support for the real time clock
574 found on Moorestown platforms. The VRTC is a emulated RTC that
575 derives its clock source from a real RTC in the PMIC. The MC146818
576 style programming interface is mostly conserved, but any
577 updates are done via IPC calls to the system controller FW.
579 config RTC_DRV_DS1216
580 tristate "Dallas DS1216"
581 depends on SNI_RM
582 help
583 If you say yes here you get support for the Dallas DS1216 RTC chips.
585 config RTC_DRV_DS1286
586 tristate "Dallas DS1286"
587 help
588 If you say yes here you get support for the Dallas DS1286 RTC chips.
590 config RTC_DRV_DS1302
591 tristate "Dallas DS1302"
592 depends on SH_SECUREEDGE5410
593 help
594 If you say yes here you get support for the Dallas DS1302 RTC chips.
596 config RTC_DRV_DS1511
597 tristate "Dallas DS1511"
598 help
599 If you say yes here you get support for the
600 Dallas DS1511 timekeeping/watchdog chip.
602 This driver can also be built as a module. If so, the module
603 will be called rtc-ds1511.
605 config RTC_DRV_DS1553
606 tristate "Maxim/Dallas DS1553"
607 help
608 If you say yes here you get support for the
609 Maxim/Dallas DS1553 timekeeping chip.
611 This driver can also be built as a module. If so, the module
612 will be called rtc-ds1553.
614 config RTC_DRV_DS1742
615 tristate "Maxim/Dallas DS1742/1743"
616 help
617 If you say yes here you get support for the
618 Maxim/Dallas DS1742/1743 timekeeping chip.
620 This driver can also be built as a module. If so, the module
621 will be called rtc-ds1742.
623 config RTC_DRV_DA9052
624 tristate "Dialog DA9052/DA9053 RTC"
625 depends on PMIC_DA9052
626 help
627 Say y here to support the RTC driver for Dialog Semiconductor
628 DA9052-BC and DA9053-AA/Bx PMICs.
630 config RTC_DRV_DA9055
631 tristate "Dialog Semiconductor DA9055 RTC"
632 depends on MFD_DA9055
633 help
634 If you say yes here you will get support for the
635 RTC of the Dialog DA9055 PMIC.
637 This driver can also be built as a module. If so, the module
638 will be called rtc-da9055
640 config RTC_DRV_EFI
641 tristate "EFI RTC"
642 depends on IA64
643 help
644 If you say yes here you will get support for the EFI
645 Real Time Clock.
647 This driver can also be built as a module. If so, the module
648 will be called rtc-efi.
650 config RTC_DRV_STK17TA8
651 tristate "Simtek STK17TA8"
652 help
653 If you say yes here you get support for the
654 Simtek STK17TA8 timekeeping chip.
656 This driver can also be built as a module. If so, the module
657 will be called rtc-stk17ta8.
659 config RTC_DRV_M48T86
660 tristate "ST M48T86/Dallas DS12887"
661 help
662 If you say Y here you will get support for the
663 ST M48T86 and Dallas DS12887 RTC chips.
665 This driver can also be built as a module. If so, the module
666 will be called rtc-m48t86.
668 config RTC_DRV_M48T35
669 tristate "ST M48T35"
670 help
671 If you say Y here you will get support for the
672 ST M48T35 RTC chip.
674 This driver can also be built as a module, if so, the module
675 will be called "rtc-m48t35".
677 config RTC_DRV_M48T59
678 tristate "ST M48T59/M48T08/M48T02"
679 help
680 If you say Y here you will get support for the
681 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
683 These chips are usually found in Sun SPARC and UltraSPARC
684 workstations.
686 This driver can also be built as a module, if so, the module
687 will be called "rtc-m48t59".
689 config RTC_DRV_MSM6242
690 tristate "Oki MSM6242"
691 help
692 If you say yes here you get support for the Oki MSM6242
693 timekeeping chip. It is used in some Amiga models (e.g. A2000).
695 This driver can also be built as a module. If so, the module
696 will be called rtc-msm6242.
698 config RTC_DRV_BQ4802
699 tristate "TI BQ4802"
700 help
701 If you say Y here you will get support for the TI
702 BQ4802 RTC chip.
704 This driver can also be built as a module. If so, the module
705 will be called rtc-bq4802.
707 config RTC_DRV_RP5C01
708 tristate "Ricoh RP5C01"
709 help
710 If you say yes here you get support for the Ricoh RP5C01
711 timekeeping chip. It is used in some Amiga models (e.g. A3000
712 and A4000).
714 This driver can also be built as a module. If so, the module
715 will be called rtc-rp5c01.
717 config RTC_DRV_V3020
718 tristate "EM Microelectronic V3020"
719 help
720 If you say yes here you will get support for the
721 EM Microelectronic v3020 RTC chip.
723 This driver can also be built as a module. If so, the module
724 will be called rtc-v3020.
726 config RTC_DRV_DS2404
727 tristate "Dallas DS2404"
728 help
729 If you say yes here you get support for the
730 Dallas DS2404 RTC chip.
732 This driver can also be built as a module. If so, the module
733 will be called rtc-ds2404.
735 config RTC_DRV_WM831X
736 tristate "Wolfson Microelectronics WM831x RTC"
737 depends on MFD_WM831X
738 help
739 If you say yes here you will get support for the RTC subsystem
740 of the Wolfson Microelectronics WM831X series PMICs.
742 This driver can also be built as a module. If so, the module
743 will be called "rtc-wm831x".
745 config RTC_DRV_WM8350
746 tristate "Wolfson Microelectronics WM8350 RTC"
747 depends on MFD_WM8350
748 help
749 If you say yes here you will get support for the RTC subsystem
750 of the Wolfson Microelectronics WM8350.
752 This driver can also be built as a module. If so, the module
753 will be called "rtc-wm8350".
755 config RTC_DRV_SPEAR
756 tristate "SPEAR ST RTC"
757 depends on PLAT_SPEAR
758 default y
759 help
760 If you say Y here you will get support for the RTC found on
761 spear
763 config RTC_DRV_PCF50633
764 depends on MFD_PCF50633
765 tristate "NXP PCF50633 RTC"
766 help
767 If you say yes here you get support for the RTC subsystem of the
768 NXP PCF50633 used in embedded systems.
770 config RTC_DRV_AB3100
771 tristate "ST-Ericsson AB3100 RTC"
772 depends on AB3100_CORE
773 default y if AB3100_CORE
774 help
775 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
776 support. This chip contains a battery- and capacitor-backed RTC.
778 config RTC_DRV_AB8500
779 tristate "ST-Ericsson AB8500 RTC"
780 depends on AB8500_CORE
781 select RTC_INTF_DEV
782 select RTC_INTF_DEV_UIE_EMUL
783 help
784 Select this to enable the ST-Ericsson AB8500 power management IC RTC
785 support. This chip contains a battery- and capacitor-backed RTC.
787 config RTC_DRV_NUC900
788 tristate "NUC910/NUC920 RTC driver"
789 depends on ARCH_W90X900
790 help
791 If you say yes here you get support for the RTC subsystem of the
792 NUC910/NUC920 used in embedded systems.
794 comment "on-CPU RTC drivers"
796 config RTC_DRV_DAVINCI
797 tristate "TI DaVinci RTC"
798 depends on ARCH_DAVINCI_DM365
799 help
800 If you say yes here you get support for the RTC on the
801 DaVinci platforms (DM365).
803 This driver can also be built as a module. If so, the module
804 will be called rtc-davinci.
806 config RTC_DRV_IMXDI
807 tristate "Freescale IMX DryIce Real Time Clock"
808 depends on ARCH_MXC
809 help
810 Support for Freescale IMX DryIce RTC
812 This driver can also be built as a module, if so, the module
813 will be called "rtc-imxdi".
815 config RTC_DRV_OMAP
816 tristate "TI OMAP1"
817 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
818 help
819 Say "yes" here to support the on chip real time clock
820 present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
822 This driver can also be built as a module, if so, module
823 will be called rtc-omap.
825 config HAVE_S3C_RTC
826 bool
827 help
828 This will include RTC support for Samsung SoCs. If
829 you want to include RTC support for any machine, kindly
830 select this in the respective mach-XXXX/Kconfig file.
832 config RTC_DRV_S3C
833 tristate "Samsung S3C series SoC RTC"
834 depends on ARCH_S3C64XX || HAVE_S3C_RTC
835 help
836 RTC (Realtime Clock) driver for the clock inbuilt into the
837 Samsung S3C24XX series of SoCs. This can provide periodic
838 interrupt rates from 1Hz to 64Hz for user programs, and
839 wakeup from Alarm.
841 The driver currently supports the common features on all the
842 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
843 and S3C2442.
845 This driver can also be build as a module. If so, the module
846 will be called rtc-s3c.
848 config RTC_DRV_EP93XX
849 tristate "Cirrus Logic EP93XX"
850 depends on ARCH_EP93XX
851 help
852 If you say yes here you get support for the
853 RTC embedded in the Cirrus Logic EP93XX processors.
855 This driver can also be built as a module. If so, the module
856 will be called rtc-ep93xx.
858 config RTC_DRV_SA1100
859 tristate "SA11x0/PXA2xx/PXA910"
860 depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
861 help
862 If you say Y here you will get access to the real time clock
863 built into your SA11x0 or PXA2xx CPU.
865 To compile this driver as a module, choose M here: the
866 module will be called rtc-sa1100.
868 config RTC_DRV_SH
869 tristate "SuperH On-Chip RTC"
870 depends on SUPERH && HAVE_CLK
871 help
872 Say Y here to enable support for the on-chip RTC found in
873 most SuperH processors.
875 To compile this driver as a module, choose M here: the
876 module will be called rtc-sh.
878 config RTC_DRV_VR41XX
879 tristate "NEC VR41XX"
880 depends on CPU_VR41XX
881 help
882 If you say Y here you will get access to the real time clock
883 built into your NEC VR41XX CPU.
885 To compile this driver as a module, choose M here: the
886 module will be called rtc-vr41xx.
888 config RTC_DRV_PL030
889 tristate "ARM AMBA PL030 RTC"
890 depends on ARM_AMBA
891 help
892 If you say Y here you will get access to ARM AMBA
893 PrimeCell PL030 RTC found on certain ARM SOCs.
895 To compile this driver as a module, choose M here: the
896 module will be called rtc-pl030.
898 config RTC_DRV_PL031
899 tristate "ARM AMBA PL031 RTC"
900 depends on ARM_AMBA
901 help
902 If you say Y here you will get access to ARM AMBA
903 PrimeCell PL031 RTC found on certain ARM SOCs.
905 To compile this driver as a module, choose M here: the
906 module will be called rtc-pl031.
908 config RTC_DRV_AT32AP700X
909 tristate "AT32AP700X series RTC"
910 depends on PLATFORM_AT32AP
911 help
912 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
913 AT32AP700x family processors.
915 config RTC_DRV_AT91RM9200
916 tristate "AT91RM9200 or some AT91SAM9 RTC"
917 depends on ARCH_AT91
918 help
919 Driver for the internal RTC (Realtime Clock) module found on
920 Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
921 this is powered by the backup power supply.
923 config RTC_DRV_AT91SAM9
924 tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
925 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
926 help
927 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
928 (Real Time Timer). These timers are powered by the backup power
929 supply (such as a small coin cell battery), but do not need to
930 be used as RTCs.
932 (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
933 dedicated RTC module and leave the RTT available for other uses.)
935 config RTC_DRV_AT91SAM9_RTT
936 int
937 range 0 1
938 default 0
939 prompt "RTT module Number" if ARCH_AT91SAM9263
940 depends on RTC_DRV_AT91SAM9
941 help
942 More than one RTT module is available. You can choose which
943 one will be used as an RTC. The default of zero is normally
944 OK to use, though some systems use that for non-RTC purposes.
946 config RTC_DRV_AT91SAM9_GPBR
947 int
948 range 0 3 if !ARCH_AT91SAM9263
949 range 0 15 if ARCH_AT91SAM9263
950 default 0
951 prompt "Backup Register Number"
952 depends on RTC_DRV_AT91SAM9
953 help
954 The RTC driver needs to use one of the General Purpose Backup
955 Registers (GPBRs) as well as the RTT. You can choose which one
956 will be used. The default of zero is normally OK to use, but
957 on some systems other software needs to use that register.
959 config RTC_DRV_AU1XXX
960 tristate "Au1xxx Counter0 RTC support"
961 depends on MIPS_ALCHEMY
962 help
963 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
964 counter) to be used as a RTC.
966 This driver can also be built as a module. If so, the module
967 will be called rtc-au1xxx.
969 config RTC_DRV_BFIN
970 tristate "Blackfin On-Chip RTC"
971 depends on BLACKFIN && !BF561
972 help
973 If you say yes here you will get support for the
974 Blackfin On-Chip Real Time Clock.
976 This driver can also be built as a module. If so, the module
977 will be called rtc-bfin.
979 config RTC_DRV_RS5C313
980 tristate "Ricoh RS5C313"
981 depends on SH_LANDISK
982 help
983 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
985 config RTC_DRV_GENERIC
986 tristate "Generic RTC support"
987 # Please consider writing a new RTC driver instead of using the generic
988 # RTC abstraction
989 depends on PARISC || M68K || PPC || SUPERH32
990 help
991 Say Y or M here to enable RTC support on systems using the generic
992 RTC abstraction. If you do not know what you are doing, you should
993 just say Y.
995 config RTC_DRV_PXA
996 tristate "PXA27x/PXA3xx"
997 depends on ARCH_PXA
998 help
999 If you say Y here you will get access to the real time clock
1000 built into your PXA27x or PXA3xx CPU.
1002 This RTC driver uses PXA RTC registers available since pxa27x
1003 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1005 config RTC_DRV_VT8500
1006 tristate "VIA/WonderMedia 85xx SoC RTC"
1007 depends on ARCH_VT8500
1008 help
1009 If you say Y here you will get access to the real time clock
1010 built into your VIA VT8500 SoC or its relatives.
1013 config RTC_DRV_SUN4V
1014 bool "SUN4V Hypervisor RTC"
1015 depends on SPARC64
1016 help
1017 If you say Y here you will get support for the Hypervisor
1018 based RTC on SUN4V systems.
1020 config RTC_DRV_STARFIRE
1021 bool "Starfire RTC"
1022 depends on SPARC64
1023 help
1024 If you say Y here you will get support for the RTC found on
1025 Starfire systems.
1027 config RTC_DRV_TX4939
1028 tristate "TX4939 SoC"
1029 depends on SOC_TX4939
1030 help
1031 Driver for the internal RTC (Realtime Clock) module found on
1032 Toshiba TX4939 SoC.
1034 config RTC_DRV_MV
1035 tristate "Marvell SoC RTC"
1036 depends on ARCH_KIRKWOOD || ARCH_DOVE
1037 help
1038 If you say yes here you will get support for the in-chip RTC
1039 that can be found in some of Marvell's SoC devices, such as
1040 the Kirkwood 88F6281 and 88F6192.
1042 This driver can also be built as a module. If so, the module
1043 will be called rtc-mv.
1045 config RTC_DRV_PS3
1046 tristate "PS3 RTC"
1047 depends on PPC_PS3
1048 help
1049 If you say yes here you will get support for the RTC on PS3.
1051 This driver can also be built as a module. If so, the module
1052 will be called rtc-ps3.
1054 config RTC_DRV_COH901331
1055 tristate "ST-Ericsson COH 901 331 RTC"
1056 depends on ARCH_U300
1057 help
1058 If you say Y here you will get access to ST-Ericsson
1059 COH 901 331 RTC clock found in some ST-Ericsson Mobile
1060 Platforms.
1062 This driver can also be built as a module. If so, the module
1063 will be called "rtc-coh901331".
1066 config RTC_DRV_STMP
1067 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1068 depends on ARCH_MXS
1069 help
1070 If you say yes here you will get support for the onboard
1071 STMP3xxx/i.MX23/i.MX28 RTC.
1073 This driver can also be built as a module. If so, the module
1074 will be called rtc-stmp3xxx.
1076 config RTC_DRV_PCAP
1077 tristate "PCAP RTC"
1078 depends on EZX_PCAP
1079 help
1080 If you say Y here you will get support for the RTC found on
1081 the PCAP2 ASIC used on some Motorola phones.
1083 config RTC_DRV_MC13XXX
1084 depends on MFD_MC13XXX
1085 tristate "Freescale MC13xxx RTC"
1086 help
1087 This enables support for the RTCs found on Freescale's PMICs
1088 MC13783 and MC13892.
1090 config RTC_DRV_MPC5121
1091 tristate "Freescale MPC5121 built-in RTC"
1092 depends on PPC_MPC512x || PPC_MPC52xx
1093 help
1094 If you say yes here you will get support for the
1095 built-in RTC on MPC5121 or on MPC5200.
1097 This driver can also be built as a module. If so, the module
1098 will be called rtc-mpc5121.
1100 config RTC_DRV_JZ4740
1101 tristate "Ingenic JZ4740 SoC"
1102 depends on MACH_JZ4740
1103 help
1104 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
1105 controller.
1107 This driver can also be buillt as a module. If so, the module
1108 will be called rtc-jz4740.
1110 config RTC_DRV_LPC32XX
1111 depends on ARCH_LPC32XX
1112 tristate "NXP LPC32XX RTC"
1113 help
1114 This enables support for the NXP RTC in the LPC32XX
1116 This driver can also be buillt as a module. If so, the module
1117 will be called rtc-lpc32xx.
1119 config RTC_DRV_PM8XXX
1120 tristate "Qualcomm PMIC8XXX RTC"
1121 depends on MFD_PM8XXX
1122 help
1123 If you say yes here you get support for the
1124 Qualcomm PMIC8XXX RTC.
1126 To compile this driver as a module, choose M here: the
1127 module will be called rtc-pm8xxx.
1129 config RTC_DRV_TEGRA
1130 tristate "NVIDIA Tegra Internal RTC driver"
1131 depends on ARCH_TEGRA
1132 help
1133 If you say yes here you get support for the
1134 Tegra 200 series internal RTC module.
1136 This drive can also be built as a module. If so, the module
1137 will be called rtc-tegra.
1139 config RTC_DRV_TILE
1140 tristate "Tilera hypervisor RTC support"
1141 depends on TILE
1142 help
1143 Enable support for the Linux driver side of the Tilera
1144 hypervisor's real-time clock interface.
1146 config RTC_DRV_PUV3
1147 tristate "PKUnity v3 RTC support"
1148 depends on ARCH_PUV3
1149 help
1150 This enables support for the RTC in the PKUnity-v3 SoCs.
1152 This drive can also be built as a module. If so, the module
1153 will be called rtc-puv3.
1155 config RTC_DRV_LOONGSON1
1156 tristate "loongson1 RTC support"
1157 depends on MACH_LOONGSON1
1158 help
1159 This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1160 counter) to be used as a RTC.
1162 This driver can also be built as a module. If so, the module
1163 will be called rtc-ls1x.
1165 config RTC_DRV_MXC
1166 tristate "Freescale MXC Real Time Clock"
1167 depends on ARCH_MXC
1168 help
1169 If you say yes here you get support for the Freescale MXC
1170 RTC module.
1172 This driver can also be built as a module, if so, the module
1173 will be called "rtc-mxc".
1175 config RTC_DRV_SNVS
1176 tristate "Freescale SNVS RTC support"
1177 depends on HAS_IOMEM
1178 depends on OF
1179 help
1180 If you say yes here you get support for the Freescale SNVS
1181 Low Power (LP) RTC module.
1183 This driver can also be built as a module, if so, the module
1184 will be called "rtc-snvs".
1186 endif # RTC_CLASS