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_DS1672
143 tristate "Dallas/Maxim DS1672"
145 If you say yes here you get support for the
146 Dallas/Maxim DS1672 timekeeping chip.
148 This driver can also be built as a module. If so, the module
149 will be called rtc-ds1672.
151 config RTC_DRV_MAX6900
152 tristate "Maxim 6900"
154 If you say yes here you will get support for the
155 Maxim MAX6900 I2C RTC chip.
157 This driver can also be built as a module. If so, the module
158 will be called rtc-max6900.
160 config RTC_DRV_RS5C372
161 tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A"
163 If you say yes here you get support for the
164 Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
166 This driver can also be built as a module. If so, the module
167 will be called rtc-rs5c372.
169 config RTC_DRV_ISL1208
170 tristate "Intersil 1208"
172 If you say yes here you get support for the
173 Intersil 1208 RTC chip.
175 This driver can also be built as a module. If so, the module
176 will be called rtc-isl1208.
179 tristate "Xicor/Intersil X1205"
181 If you say yes here you get support for the
182 Xicor/Intersil X1205 RTC chip.
184 This driver can also be built as a module. If so, the module
185 will be called rtc-x1205.
187 config RTC_DRV_PCF8563
188 tristate "Philips PCF8563/Epson RTC8564"
190 If you say yes here you get support for the
191 Philips PCF8563 RTC chip. The Epson RTC8564
194 This driver can also be built as a module. If so, the module
195 will be called rtc-pcf8563.
197 config RTC_DRV_PCF8583
198 tristate "Philips PCF8583"
200 If you say yes here you get support for the Philips PCF8583
201 RTC chip found on Acorn RiscPCs. This driver supports the
202 platform specific method of retrieving the current year from
203 the RTC's SRAM. It will work on other platforms with the same
204 chip, but the year will probably have to be tweaked.
206 This driver can also be built as a module. If so, the module
207 will be called rtc-pcf8583.
209 config RTC_DRV_M41T80
210 tristate "ST M41T80 series RTC"
212 If you say Y here you will get support for the
213 ST M41T80 RTC chips series. Currently following chips are
214 supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85
217 This driver can also be built as a module. If so, the module
218 will be called rtc-m41t80.
220 config RTC_DRV_M41T80_WDT
221 bool "ST M41T80 series RTC watchdog timer"
222 depends on RTC_DRV_M41T80
224 If you say Y here you will get support for the
225 watchdog timer in ST M41T80 RTC chips series.
227 config RTC_DRV_TWL92330
228 boolean "TI TWL92330/Menelaus"
231 If you say yes here you get support for the RTC on the
232 TWL92330 "Menelaus" power mangement chip, used with OMAP2
233 platforms. The support is integrated with the rest of
234 the Menelaus driver; it's not separate module.
236 config RTC_DRV_TWL4030
237 tristate "OMAP TWL4030 Real Time Clock"
238 depends on RTC_CLASS && TWL4030_CORE
240 If you say yes here you get support for internal Real-Time
241 Clock of TWL4030 chip.
243 This driver can also be built as a module. If so, the module
244 will be called rtc-twl4030.
248 comment "SPI RTC drivers"
252 config RTC_DRV_RS5C348
253 tristate "Ricoh RS5C348A/B"
255 If you say yes here you get support for the
256 Ricoh RS5C348A and RS5C348B RTC chips.
258 This driver can also be built as a module. If so, the module
259 will be called rtc-rs5c348.
261 config RTC_DRV_MAX6902
262 tristate "Maxim 6902"
264 If you say yes here you will get support for the
265 Maxim MAX6902 SPI RTC chip.
267 This driver can also be built as a module. If so, the module
268 will be called rtc-max6902.
272 comment "Platform RTC drivers"
274 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
275 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
276 # global rtc_lock ... it's not yet just another platform_device.
279 tristate "PC-style 'CMOS'"
280 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS
282 Say "yes" here to get direct support for the real time clock
283 found in every PC or ACPI-based system, and some other boards.
284 Specifically the original MC146818, compatibles like those in
285 PC south bridges, the DS12887 or M48T86, some multifunction
286 or LPC bus chips, and so on.
288 Your system will need to define the platform device used by
289 this driver, otherwise it won't be accessible. This means
290 you can safely enable this driver if you don't know whether
291 or not your board has this kind of hardware.
293 This driver can also be built as a module. If so, the module
294 will be called rtc-cmos.
296 config RTC_DRV_DS1216
297 tristate "Dallas DS1216"
300 If you say yes here you get support for the Dallas DS1216 RTC chips.
302 config RTC_DRV_DS1553
303 tristate "Dallas DS1553"
305 If you say yes here you get support for the
306 Dallas DS1553 timekeeping chip.
308 This driver can also be built as a module. If so, the module
309 will be called rtc-ds1553.
311 config RTC_DRV_STK17TA8
312 tristate "Simtek STK17TA8"
315 If you say yes here you get support for the
316 Simtek STK17TA8 timekeeping chip.
318 This driver can also be built as a module. If so, the module
319 will be called rtc-stk17ta8.
321 config RTC_DRV_DS1742
322 tristate "Dallas DS1742/1743"
324 If you say yes here you get support for the
325 Dallas DS1742/1743 timekeeping chip.
327 This driver can also be built as a module. If so, the module
328 will be called rtc-ds1742.
330 config RTC_DRV_M48T86
331 tristate "ST M48T86/Dallas DS12887"
333 If you say Y here you will get support for the
334 ST M48T86 and Dallas DS12887 RTC chips.
336 This driver can also be built as a module. If so, the module
337 will be called rtc-m48t86.
339 config RTC_DRV_M48T59
342 If you say Y here you will get support for the
345 This driver can also be built as a module, if so, the module
346 will be called "rtc-m48t59".
349 tristate "EM Microelectronic V3020"
351 If you say yes here you will get support for the
352 EM Microelectronic v3020 RTC chip.
354 This driver can also be built as a module. If so, the module
355 will be called rtc-v3020.
357 comment "on-CPU RTC drivers"
361 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730
363 Say "yes" here to support the real time clock on TI OMAP1 chips.
364 This driver can also be built as a module called rtc-omap.
367 tristate "Samsung S3C series SoC RTC"
368 depends on ARCH_S3C2410
370 RTC (Realtime Clock) driver for the clock inbuilt into the
371 Samsung S3C24XX series of SoCs. This can provide periodic
372 interrupt rates from 1Hz to 64Hz for user programs, and
375 The driver currently supports the common features on all the
376 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
379 This driver can also be build as a module. If so, the module
380 will be called rtc-s3c.
382 config RTC_DRV_EP93XX
383 tristate "Cirrus Logic EP93XX"
384 depends on ARCH_EP93XX
386 If you say yes here you get support for the
387 RTC embedded in the Cirrus Logic EP93XX processors.
389 This driver can also be built as a module. If so, the module
390 will be called rtc-ep93xx.
392 config RTC_DRV_SA1100
393 tristate "SA11x0/PXA2xx"
394 depends on ARCH_SA1100 || ARCH_PXA
396 If you say Y here you will get access to the real time clock
397 built into your SA11x0 or PXA2xx CPU.
399 To compile this driver as a module, choose M here: the
400 module will be called rtc-sa1100.
403 tristate "SuperH On-Chip RTC"
404 depends on RTC_CLASS && (CPU_SH3 || CPU_SH4)
406 Say Y here to enable support for the on-chip RTC found in
407 most SuperH processors.
409 To compile this driver as a module, choose M here: the
410 module will be called rtc-sh.
412 config RTC_DRV_VR41XX
413 tristate "NEC VR41XX"
414 depends on CPU_VR41XX
416 If you say Y here you will get access to the real time clock
417 built into your NEC VR41XX CPU.
419 To compile this driver as a module, choose M here: the
420 module will be called rtc-vr41xx.
423 tristate "ARM AMBA PL031 RTC"
426 If you say Y here you will get access to ARM AMBA
427 PrimeCell PL031 RTC found on certain ARM SOCs.
429 To compile this driver as a module, choose M here: the
430 module will be called rtc-pl031.
432 config RTC_DRV_AT32AP700X
433 tristate "AT32AP700X series RTC"
434 depends on PLATFORM_AT32AP
436 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
437 AT32AP700x family processors.
439 config RTC_DRV_AT91RM9200
440 tristate "AT91RM9200"
441 depends on ARCH_AT91RM9200
443 Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).
446 tristate "Blackfin On-Chip RTC"
449 If you say yes here you will get support for the
450 Blackfin On-Chip Real Time Clock.
452 This driver can also be built as a module. If so, the module
453 will be called rtc-bfin.
455 config RTC_DRV_RS5C313
456 tristate "Ricoh RS5C313"
457 depends on SH_LANDISK
459 If you say yes here you get support for the Ricoh RS5C313 RTC chips.