2 # RTC class/drivers configuration
11 depends on !S390 && !UML
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.
21 bool "Set system time from RTC on startup and resume"
23 depends on !ALWAYS_USE_PERSISTENT_CLOCK
25 If you say yes here, the system time (wall clock) will be set using
26 the value read from a specified RTC device. This is useful to avoid
27 unnecessary fsck runs at boot time, and to network better.
30 bool "Set the RTC time based on NTP synchronization"
32 depends on !ALWAYS_USE_PERSISTENT_CLOCK
34 If you say yes here, the system time (wall clock) will be stored
35 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
36 minutes if userspace reports synchronized NTP status.
38 config RTC_HCTOSYS_DEVICE
39 string "RTC used to set the system time"
40 depends on RTC_HCTOSYS = y || RTC_SYSTOHC = y
43 The RTC device that will be used to (re)initialize the system
44 clock, usually rtc0. Initialization is done when the system
45 starts up, and when it resumes from a low power state. This
46 device should record time in UTC, since the kernel won't do
49 The driver for this RTC device must be loaded before late_initcall
50 functions run, so it must usually be statically linked.
52 This clock should be battery-backed, so that it reads the correct
53 time when the system boots from a power-off state. Otherwise, your
54 system will need an external clock source (like an NTP server).
56 If the clock you specify here is not battery backed, it may still
57 be useful to reinitialize system time when resuming from system
58 sleep states. Do not specify an RTC here unless it stays powered
59 during all this system's supported sleep states.
62 bool "RTC debug support"
64 Say yes here to enable debugging support in the RTC framework
65 and individual RTC drivers.
67 comment "RTC interfaces"
70 boolean "/sys/class/rtc/rtcN (sysfs)"
74 Say yes here if you want to use your RTCs using sysfs interfaces,
75 /sys/class/rtc/rtc0 through /sys/.../rtcN.
80 boolean "/proc/driver/rtc (procfs for rtcN)"
84 Say yes here if you want to use your system clock RTC through
85 the proc interface, /proc/driver/rtc.
86 Other RTCs will not be available through that API.
87 If there is no RTC for the system clock, then the first RTC(rtc0)
93 boolean "/dev/rtcN (character devices)"
96 Say yes here if you want to use your RTCs using the /dev
97 interfaces, which "udev" sets up as /dev/rtc0 through
100 You may want to set up a symbolic link so one of these
101 can be accessed as /dev/rtc, which is a name
102 expected by "hwclock" and some other programs. Recent
103 versions of "udev" are known to set up the symlink for you.
107 config RTC_INTF_DEV_UIE_EMUL
108 bool "RTC UIE emulation on dev interface"
109 depends on RTC_INTF_DEV
111 Provides an emulation for RTC_UIE if the underlying rtc chip
112 driver does not expose RTC_UIE ioctls. Those requests generate
113 once-per-second update interrupts, used for synchronization.
115 The emulation code will read the time from the hardware
116 clock several times per second, please enable this option
117 only if you know that you really need it.
120 tristate "Test driver/device"
122 If you say yes here you get support for the
123 RTC test driver. It's a software RTC which can be
124 used to test the RTC subsystem APIs. It gets
125 the time from the system clock.
126 You want this driver only if you are doing development
127 on the RTC subsystem. Please read the source code
130 This driver can also be built as a module. If so, the module
131 will be called rtc-test.
133 comment "I2C RTC drivers"
138 config RTC_DRV_88PM860X
139 tristate "Marvell 88PM860x"
140 depends on I2C && MFD_88PM860X
142 If you say yes here you get support for RTC function in Marvell
145 This driver can also be built as a module. If so, the module
146 will be called rtc-88pm860x.
148 config RTC_DRV_88PM80X
149 tristate "Marvell 88PM80x"
150 depends on I2C && MFD_88PM800
152 If you say yes here you get support for RTC function in Marvell
155 This driver can also be built as a module. If so, the module
156 will be called rtc-88pm80x.
158 config RTC_DRV_DS1307
159 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
161 If you say yes here you get support for various compatible RTC
162 chips (often with battery backup) connected with I2C. This driver
163 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
164 EPSON RX-8025 and probably other chips. In some cases the RTC
165 must already have been initialized (by manufacturing or a
168 The first seven registers on these chips hold an RTC, and other
169 registers may add features such as NVRAM, a trickle charger for
170 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
171 sysfs, but other chip features may not be available.
173 This driver can also be built as a module. If so, the module
174 will be called rtc-ds1307.
176 config RTC_DRV_DS1374
177 tristate "Dallas/Maxim DS1374"
180 If you say yes here you get support for Dallas Semiconductor
181 DS1374 real-time clock chips. If an interrupt is associated
182 with the device, the alarm functionality is supported.
184 This driver can also be built as a module. If so, the module
185 will be called rtc-ds1374.
187 config RTC_DRV_DS1672
188 tristate "Dallas/Maxim DS1672"
190 If you say yes here you get support for the
191 Dallas/Maxim DS1672 timekeeping chip.
193 This driver can also be built as a module. If so, the module
194 will be called rtc-ds1672.
196 config RTC_DRV_DS3232
197 tristate "Dallas/Maxim DS3232"
200 If you say yes here you get support for Dallas Semiconductor
201 DS3232 real-time clock chips. If an interrupt is associated
202 with the device, the alarm functionality is supported.
204 This driver can also be built as a module. If so, the module
205 will be called rtc-ds3232.
207 config RTC_DRV_MAX6900
208 tristate "Maxim MAX6900"
210 If you say yes here you will get support for the
211 Maxim MAX6900 I2C RTC chip.
213 This driver can also be built as a module. If so, the module
214 will be called rtc-max6900.
216 config RTC_DRV_MAX8907
217 tristate "Maxim MAX8907"
218 depends on MFD_MAX8907
220 If you say yes here you will get support for the
221 RTC of Maxim MAX8907 PMIC.
223 This driver can also be built as a module. If so, the module
224 will be called rtc-max8907.
226 config RTC_DRV_MAX8925
227 tristate "Maxim MAX8925"
228 depends on MFD_MAX8925
230 If you say yes here you will get support for the
231 RTC of Maxim MAX8925 PMIC.
233 This driver can also be built as a module. If so, the module
234 will be called rtc-max8925.
236 config RTC_DRV_MAX8998
237 tristate "Maxim MAX8998"
238 depends on MFD_MAX8998
240 If you say yes here you will get support for the
241 RTC of Maxim MAX8998 PMIC.
243 This driver can also be built as a module. If so, the module
244 will be called rtc-max8998.
246 config RTC_DRV_RS5C372
247 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
249 If you say yes here you get support for the
250 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
252 This driver can also be built as a module. If so, the module
253 will be called rtc-rs5c372.
255 config RTC_DRV_ISL1208
256 tristate "Intersil ISL1208"
258 If you say yes here you get support for the
259 Intersil ISL1208 RTC chip.
261 This driver can also be built as a module. If so, the module
262 will be called rtc-isl1208.
264 config RTC_DRV_ISL12022
265 tristate "Intersil ISL12022"
267 If you say yes here you get support for the
268 Intersil ISL12022 RTC chip.
270 This driver can also be built as a module. If so, the module
271 will be called rtc-isl12022.
274 tristate "Xicor/Intersil X1205"
276 If you say yes here you get support for the
277 Xicor/Intersil X1205 RTC chip.
279 This driver can also be built as a module. If so, the module
280 will be called rtc-x1205.
282 config RTC_DRV_PCF8523
283 tristate "NXP PCF8523"
285 If you say yes here you get support for the NXP PCF8523 RTC
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"
294 If you say yes here you get support for the
295 Philips PCF8563 RTC chip. The Epson RTC8564
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"
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"
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
328 If you say Y here you will get support for the
329 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
332 tristate "TI BQ32000"
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
344 Supports the RTC firmware in the MSP430 on the DM355 EVM.
346 config RTC_DRV_TWL92330
347 boolean "TI TWL92330/Menelaus"
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
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
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
377 If you say yes here you get support for the RTC on the
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
387 If you say yes here you get support for the RTC on the
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"
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"
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"
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"
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"
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"
443 If you say yes here you get support for the Micro Crystal
446 This driver can also be built as a module. If so, the module
447 will be called rtc-rv3029c2.
451 comment "SPI RTC drivers"
455 config RTC_DRV_M41T93
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
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"
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"
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"
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.
505 tristate "Epson RTC-9701JE"
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"
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"
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"
534 If you say yes here you get support for the NXP PCF2123
537 This driver can also be built as a module. If so, the module
538 will be called rtc-pcf2123.
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.
549 tristate "PC-style 'CMOS'"
550 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
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.
568 tristate "Virtual RTC for Intel MID platforms"
569 depends on X86_INTEL_MID
570 default y if X86_INTEL_MID
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"
583 If you say yes here you get support for the Dallas DS1216 RTC chips.
585 config RTC_DRV_DS1286
586 tristate "Dallas DS1286"
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
594 If you say yes here you get support for the Dallas DS1302 RTC chips.
596 config RTC_DRV_DS1511
597 tristate "Dallas DS1511"
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"
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"
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
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
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
644 If you say yes here you will get support for the EFI
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"
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"
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
671 If you say Y here you will get support for the
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"
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
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"
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
701 If you say Y here you will get support for the TI
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"
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
714 This driver can also be built as a module. If so, the module
715 will be called rtc-rp5c01.
718 tristate "EM Microelectronic V3020"
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"
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
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
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".
756 tristate "SPEAR ST RTC"
757 depends on PLAT_SPEAR
760 If you say Y here you will get support for the RTC found on
763 config RTC_DRV_PCF50633
764 depends on MFD_PCF50633
765 tristate "NXP PCF50633 RTC"
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
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
782 select RTC_INTF_DEV_UIE_EMUL
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
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
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.
807 tristate "Freescale IMX DryIce Real Time Clock"
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".
817 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
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.
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.
833 tristate "Samsung S3C series SoC RTC"
834 depends on ARCH_S3C64XX || HAVE_S3C_RTC
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
841 The driver currently supports the common features on all the
842 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
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
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
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.
869 tristate "SuperH On-Chip RTC"
870 depends on SUPERH && HAVE_CLK
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
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.
889 tristate "ARM AMBA PL030 RTC"
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.
899 tristate "ARM AMBA PL031 RTC"
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
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"
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)
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
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
939 prompt "RTT module Number" if ARCH_AT91SAM9263
940 depends on RTC_DRV_AT91SAM9
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
948 range 0 3 if !ARCH_AT91SAM9263
949 range 0 15 if ARCH_AT91SAM9263
951 prompt "Backup Register Number"
952 depends on RTC_DRV_AT91SAM9
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
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.
970 tristate "Blackfin On-Chip RTC"
971 depends on BLACKFIN && !BF561
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
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
989 depends on PARISC || M68K || PPC || SUPERH32
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
996 tristate "PXA27x/PXA3xx"
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
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"
1017 If you say Y here you will get support for the Hypervisor
1018 based RTC on SUN4V systems.
1020 config RTC_DRV_STARFIRE
1024 If you say Y here you will get support for the RTC found on
1027 config RTC_DRV_TX4939
1028 tristate "TX4939 SoC"
1029 depends on SOC_TX4939
1031 Driver for the internal RTC (Realtime Clock) module found on
1035 tristate "Marvell SoC RTC"
1036 depends on ARCH_KIRKWOOD || ARCH_DOVE
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.
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
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
1062 This driver can also be built as a module. If so, the module
1063 will be called "rtc-coh901331".
1067 tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
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.
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"
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
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
1104 If you say yes here you get support for the Ingenic JZ4740 SoC RTC
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"
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
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
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.
1140 tristate "Tilera hypervisor RTC support"
1143 Enable support for the Linux driver side of the Tilera
1144 hypervisor's real-time clock interface.
1147 tristate "PKUnity v3 RTC support"
1148 depends on ARCH_PUV3
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
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.
1166 tristate "Freescale MXC Real Time Clock"
1169 If you say yes here you get support for the Freescale MXC
1172 This driver can also be built as a module, if so, the module
1173 will be called "rtc-mxc".
1176 tristate "Freescale SNVS RTC support"
1177 depends on HAS_IOMEM
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".