2 # RTC class/drivers configuration
9 tristate "Real Time Clock"
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 This driver can also be built as a module. If so, the module
19 will be called rtc-class.
24 bool "Set system time from RTC on startup and resume"
25 depends on RTC_CLASS = y
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.
32 config RTC_HCTOSYS_DEVICE
33 string "RTC used to set the system time"
34 depends on RTC_HCTOSYS = y
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.
41 The driver for this RTC device must be loaded before late_initcall
42 functions run, so it must usually be statically linked.
44 This clock should be battery-backed, so that it reads the correct
45 time when the system boots from a power-off state. Otherwise, your
46 system will need an external clock source (like an NTP server).
48 If the clock you specify here is not battery backed, it may still
49 be useful to reinitialize system time when resuming from system
50 sleep states. Do not specify an RTC here unless it stays powered
51 during all this system's supported sleep states.
54 bool "RTC debug support"
55 depends on RTC_CLASS = y
57 Say yes here to enable debugging support in the RTC framework
58 and individual RTC drivers.
60 comment "RTC interfaces"
63 boolean "/sys/class/rtc/rtcN (sysfs)"
67 Say yes here if you want to use your RTCs using sysfs interfaces,
68 /sys/class/rtc/rtc0 through /sys/.../rtcN.
70 This driver can also be built as a module. If so, the module
71 will be called rtc-sysfs.
74 boolean "/proc/driver/rtc (procfs for rtc0)"
78 Say yes here if you want to use your first RTC through the proc
79 interface, /proc/driver/rtc. Other RTCs will not be available
82 This driver can also be built as a module. If so, the module
83 will be called rtc-proc.
86 boolean "/dev/rtcN (character devices)"
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. You may want to set up a symbolic link so one
92 of these can be accessed as /dev/rtc, which is a name
93 expected by "hwclock" and some other programs.
95 This driver can also be built as a module. If so, the module
96 will be called rtc-dev.
98 config RTC_INTF_DEV_UIE_EMUL
99 bool "RTC UIE emulation on dev interface"
100 depends on RTC_INTF_DEV
102 Provides an emulation for RTC_UIE if the underlying rtc chip
103 driver does not expose RTC_UIE ioctls. Those requests generate
104 once-per-second update interrupts, used for synchronization.
107 tristate "Test driver/device"
109 If you say yes here you get support for the
110 RTC test driver. It's a software RTC which can be
111 used to test the RTC subsystem APIs. It gets
112 the time from the system clock.
113 You want this driver only if you are doing development
114 on the RTC subsystem. Please read the source code
117 This driver can also be built as a module. If so, the module
118 will be called rtc-test.
120 comment "I2C RTC drivers"
125 config RTC_DRV_DS1307
126 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00"
128 If you say yes here you get support for various compatible RTC
129 chips (often with battery backup) connected with I2C. This driver
130 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
131 and probably other chips. In some cases the RTC must already
132 have been initialized (by manufacturing or a bootloader).
134 The first seven registers on these chips hold an RTC, and other
135 registers may add features such as NVRAM, a trickle charger for
136 the RTC/NVRAM backup power, and alarms. This driver may not
137 expose all those available chip features.
139 This driver can also be built as a module. If so, the module
140 will be called rtc-ds1307.
142 config RTC_DRV_DS1374
143 tristate "Maxim/Dallas Semiconductor DS1374 Real Time Clock"
144 depends on RTC_CLASS && I2C
146 If you say yes here you get support for Dallas Semiconductor
147 DS1374 real-time clock chips. If an interrupt is associated
148 with the device, the alarm functionality is supported.
150 This driver can also be built as a module. If so, the module
151 will be called rtc-ds1374.
153 config RTC_DRV_DS1672
154 tristate "Dallas/Maxim DS1672"
156 If you say yes here you get support for the
157 Dallas/Maxim DS1672 timekeeping chip.
159 This driver can also be built as a module. If so, the module
160 will be called rtc-ds1672.
162 config RTC_DRV_MAX6900
163 tristate "Maxim 6900"
165 If you say yes here you will get support for the
166 Maxim MAX6900 I2C RTC chip.
168 This driver can also be built as a module. If so, the module
169 will be called rtc-max6900.
171 config RTC_DRV_RS5C372
172 tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A"
174 If you say yes here you get support for the
175 Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
177 This driver can also be built as a module. If so, the module
178 will be called rtc-rs5c372.
180 config RTC_DRV_ISL1208
181 tristate "Intersil 1208"
183 If you say yes here you get support for the
184 Intersil 1208 RTC chip.
186 This driver can also be built as a module. If so, the module
187 will be called rtc-isl1208.
190 tristate "Xicor/Intersil X1205"
192 If you say yes here you get support for the
193 Xicor/Intersil X1205 RTC chip.
195 This driver can also be built as a module. If so, the module
196 will be called rtc-x1205.
198 config RTC_DRV_PCF8563
199 tristate "Philips PCF8563/Epson RTC8564"
201 If you say yes here you get support for the
202 Philips PCF8563 RTC chip. The Epson RTC8564
205 This driver can also be built as a module. If so, the module
206 will be called rtc-pcf8563.
208 config RTC_DRV_PCF8583
209 tristate "Philips PCF8583"
211 If you say yes here you get support for the Philips PCF8583
212 RTC chip found on Acorn RiscPCs. This driver supports the
213 platform specific method of retrieving the current year from
214 the RTC's SRAM. It will work on other platforms with the same
215 chip, but the year will probably have to be tweaked.
217 This driver can also be built as a module. If so, the module
218 will be called rtc-pcf8583.
220 config RTC_DRV_M41T80
221 tristate "ST M41T80 series RTC"
223 If you say Y here you will get support for the
224 ST M41T80 RTC chips series. Currently following chips are
225 supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85
228 This driver can also be built as a module. If so, the module
229 will be called rtc-m41t80.
231 config RTC_DRV_M41T80_WDT
232 bool "ST M41T80 series RTC watchdog timer"
233 depends on RTC_DRV_M41T80
235 If you say Y here you will get support for the
236 watchdog timer in ST M41T80 RTC chips series.
238 config RTC_DRV_TWL92330
239 boolean "TI TWL92330/Menelaus"
242 If you say yes here you get support for the RTC on the
243 TWL92330 "Menelaus" power management chip, used with OMAP2
244 platforms. The support is integrated with the rest of
245 the Menelaus driver; it's not separate module.
247 config RTC_DRV_TWL4030
248 tristate "OMAP TWL4030 Real Time Clock"
249 depends on RTC_CLASS && TWL4030_CORE
251 If you say yes here you get support for internal Real-Time
252 Clock of TWL4030 chip.
254 This driver can also be built as a module. If so, the module
255 will be called rtc-twl4030.
259 comment "SPI RTC drivers"
263 config RTC_DRV_RS5C348
264 tristate "Ricoh RS5C348A/B"
266 If you say yes here you get support for the
267 Ricoh RS5C348A and RS5C348B RTC chips.
269 This driver can also be built as a module. If so, the module
270 will be called rtc-rs5c348.
272 config RTC_DRV_MAX6902
273 tristate "Maxim 6902"
275 If you say yes here you will get support for the
276 Maxim MAX6902 SPI RTC chip.
278 This driver can also be built as a module. If so, the module
279 will be called rtc-max6902.
283 comment "Platform RTC drivers"
285 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
286 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
287 # global rtc_lock ... it's not yet just another platform_device.
290 tristate "PC-style 'CMOS'"
291 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS
293 Say "yes" here to get direct support for the real time clock
294 found in every PC or ACPI-based system, and some other boards.
295 Specifically the original MC146818, compatibles like those in
296 PC south bridges, the DS12887 or M48T86, some multifunction
297 or LPC bus chips, and so on.
299 Your system will need to define the platform device used by
300 this driver, otherwise it won't be accessible. This means
301 you can safely enable this driver if you don't know whether
302 or not your board has this kind of hardware.
304 This driver can also be built as a module. If so, the module
305 will be called rtc-cmos.
307 config RTC_DRV_DS1216
308 tristate "Dallas DS1216"
311 If you say yes here you get support for the Dallas DS1216 RTC chips.
313 config RTC_DRV_DS1553
314 tristate "Dallas DS1553"
316 If you say yes here you get support for the
317 Dallas DS1553 timekeeping chip.
319 This driver can also be built as a module. If so, the module
320 will be called rtc-ds1553.
322 config RTC_DRV_STK17TA8
323 tristate "Simtek STK17TA8"
326 If you say yes here you get support for the
327 Simtek STK17TA8 timekeeping chip.
329 This driver can also be built as a module. If so, the module
330 will be called rtc-stk17ta8.
332 config RTC_DRV_DS1742
333 tristate "Dallas DS1742/1743"
335 If you say yes here you get support for the
336 Dallas DS1742/1743 timekeeping chip.
338 This driver can also be built as a module. If so, the module
339 will be called rtc-ds1742.
341 config RTC_DRV_M48T86
342 tristate "ST M48T86/Dallas DS12887"
344 If you say Y here you will get support for the
345 ST M48T86 and Dallas DS12887 RTC chips.
347 This driver can also be built as a module. If so, the module
348 will be called rtc-m48t86.
350 config RTC_DRV_M48T59
353 If you say Y here you will get support for the
356 This driver can also be built as a module, if so, the module
357 will be called "rtc-m48t59".
360 tristate "EM Microelectronic V3020"
362 If you say yes here you will get support for the
363 EM Microelectronic v3020 RTC chip.
365 This driver can also be built as a module. If so, the module
366 will be called rtc-v3020.
368 comment "on-CPU RTC drivers"
372 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730
374 Say "yes" here to support the real time clock on TI OMAP1 chips.
375 This driver can also be built as a module called rtc-omap.
378 tristate "Samsung S3C series SoC RTC"
379 depends on ARCH_S3C2410
381 RTC (Realtime Clock) driver for the clock inbuilt into the
382 Samsung S3C24XX series of SoCs. This can provide periodic
383 interrupt rates from 1Hz to 64Hz for user programs, and
386 The driver currently supports the common features on all the
387 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
390 This driver can also be build as a module. If so, the module
391 will be called rtc-s3c.
393 config RTC_DRV_EP93XX
394 tristate "Cirrus Logic EP93XX"
395 depends on ARCH_EP93XX
397 If you say yes here you get support for the
398 RTC embedded in the Cirrus Logic EP93XX processors.
400 This driver can also be built as a module. If so, the module
401 will be called rtc-ep93xx.
403 config RTC_DRV_SA1100
404 tristate "SA11x0/PXA2xx"
405 depends on ARCH_SA1100 || ARCH_PXA
407 If you say Y here you will get access to the real time clock
408 built into your SA11x0 or PXA2xx CPU.
410 To compile this driver as a module, choose M here: the
411 module will be called rtc-sa1100.
414 tristate "SuperH On-Chip RTC"
415 depends on RTC_CLASS && (CPU_SH3 || CPU_SH4)
417 Say Y here to enable support for the on-chip RTC found in
418 most SuperH processors.
420 To compile this driver as a module, choose M here: the
421 module will be called rtc-sh.
423 config RTC_DRV_VR41XX
424 tristate "NEC VR41XX"
425 depends on CPU_VR41XX
427 If you say Y here you will get access to the real time clock
428 built into your NEC VR41XX CPU.
430 To compile this driver as a module, choose M here: the
431 module will be called rtc-vr41xx.
434 tristate "ARM AMBA PL031 RTC"
437 If you say Y here you will get access to ARM AMBA
438 PrimeCell PL031 RTC found on certain ARM SOCs.
440 To compile this driver as a module, choose M here: the
441 module will be called rtc-pl031.
443 config RTC_DRV_AT32AP700X
444 tristate "AT32AP700X series RTC"
445 depends on PLATFORM_AT32AP
447 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
448 AT32AP700x family processors.
450 config RTC_DRV_AT91RM9200
451 tristate "AT91RM9200"
452 depends on ARCH_AT91RM9200
454 Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).
457 tristate "Blackfin On-Chip RTC"
460 If you say yes here you will get support for the
461 Blackfin On-Chip Real Time Clock.
463 This driver can also be built as a module. If so, the module
464 will be called rtc-bfin.
466 config RTC_DRV_RS5C313
467 tristate "Ricoh RS5C313"
468 depends on SH_LANDISK
470 If you say yes here you get support for the Ricoh RS5C313 RTC chips.