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 comment "Conflicting RTC option has been selected, check GEN_RTC and RTC"
28 bool "Set system time from RTC on startup and resume"
29 depends on RTC_CLASS = y
32 If you say yes here, the system time (wall clock) will be set using
33 the value read from a specified RTC device. This is useful to avoid
34 unnecessary fsck runs at boot time, and to network better.
36 config RTC_HCTOSYS_DEVICE
37 string "RTC used to set the system time"
38 depends on RTC_HCTOSYS = y
41 The RTC device that will be used to (re)initialize the system
42 clock, usually rtc0. Initialization is done when the system
43 starts up, and when it resumes from a low power state. This
44 device should record time in UTC, since the kernel won't do
47 The driver for this RTC device must be loaded before late_initcall
48 functions run, so it must usually be statically linked.
50 This clock should be battery-backed, so that it reads the correct
51 time when the system boots from a power-off state. Otherwise, your
52 system will need an external clock source (like an NTP server).
54 If the clock you specify here is not battery backed, it may still
55 be useful to reinitialize system time when resuming from system
56 sleep states. Do not specify an RTC here unless it stays powered
57 during all this system's supported sleep states.
60 bool "RTC debug support"
61 depends on RTC_CLASS = y
63 Say yes here to enable debugging support in the RTC framework
64 and individual RTC drivers.
66 comment "RTC interfaces"
69 boolean "/sys/class/rtc/rtcN (sysfs)"
73 Say yes here if you want to use your RTCs using sysfs interfaces,
74 /sys/class/rtc/rtc0 through /sys/.../rtcN.
76 This driver can also be built as a module. If so, the module
77 will be called rtc-sysfs.
80 boolean "/proc/driver/rtc (procfs for rtc0)"
84 Say yes here if you want to use your first RTC through the proc
85 interface, /proc/driver/rtc. Other RTCs will not be available
88 This driver can also be built as a module. If so, the module
89 will be called rtc-proc.
92 boolean "/dev/rtcN (character devices)"
95 Say yes here if you want to use your RTCs using the /dev
96 interfaces, which "udev" sets up as /dev/rtc0 through
97 /dev/rtcN. You may want to set up a symbolic link so one
98 of these can be accessed as /dev/rtc, which is a name
99 expected by "hwclock" and some other programs.
101 This driver can also be built as a module. If so, the module
102 will be called rtc-dev.
104 config RTC_INTF_DEV_UIE_EMUL
105 bool "RTC UIE emulation on dev interface"
106 depends on RTC_INTF_DEV
108 Provides an emulation for RTC_UIE if the underlying rtc chip
109 driver does not expose RTC_UIE ioctls. Those requests generate
110 once-per-second update interrupts, used for synchronization.
113 tristate "Test driver/device"
115 If you say yes here you get support for the
116 RTC test driver. It's a software RTC which can be
117 used to test the RTC subsystem APIs. It gets
118 the time from the system clock.
119 You want this driver only if you are doing development
120 on the RTC subsystem. Please read the source code
123 This driver can also be built as a module. If so, the module
124 will be called rtc-test.
126 comment "I2C RTC drivers"
131 config RTC_DRV_DS1307
132 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00"
134 If you say yes here you get support for various compatible RTC
135 chips (often with battery backup) connected with I2C. This driver
136 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
137 and probably other chips. In some cases the RTC must already
138 have been initialized (by manufacturing or a bootloader).
140 The first seven registers on these chips hold an RTC, and other
141 registers may add features such as NVRAM, a trickle charger for
142 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
143 sysfs, but other chip features may not be available.
145 This driver can also be built as a module. If so, the module
146 will be called rtc-ds1307.
148 config RTC_DRV_DS1374
149 tristate "Dallas/Maxim DS1374"
150 depends on RTC_CLASS && I2C
152 If you say yes here you get support for Dallas Semiconductor
153 DS1374 real-time clock chips. If an interrupt is associated
154 with the device, the alarm functionality is supported.
156 This driver can also be built as a module. If so, the module
157 will be called rtc-ds1374.
159 config RTC_DRV_DS1672
160 tristate "Dallas/Maxim DS1672"
162 If you say yes here you get support for the
163 Dallas/Maxim DS1672 timekeeping chip.
165 This driver can also be built as a module. If so, the module
166 will be called rtc-ds1672.
168 config RTC_DRV_MAX6900
169 tristate "Maxim MAX6900"
171 If you say yes here you will get support for the
172 Maxim MAX6900 I2C RTC chip.
174 This driver can also be built as a module. If so, the module
175 will be called rtc-max6900.
177 config RTC_DRV_RS5C372
178 tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A"
180 If you say yes here you get support for the
181 Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
183 This driver can also be built as a module. If so, the module
184 will be called rtc-rs5c372.
186 config RTC_DRV_ISL1208
187 tristate "Intersil ISL1208"
189 If you say yes here you get support for the
190 Intersil ISL1208 RTC chip.
192 This driver can also be built as a module. If so, the module
193 will be called rtc-isl1208.
196 tristate "Xicor/Intersil X1205"
198 If you say yes here you get support for the
199 Xicor/Intersil X1205 RTC chip.
201 This driver can also be built as a module. If so, the module
202 will be called rtc-x1205.
204 config RTC_DRV_PCF8563
205 tristate "Philips PCF8563/Epson RTC8564"
207 If you say yes here you get support for the
208 Philips PCF8563 RTC chip. The Epson RTC8564
211 This driver can also be built as a module. If so, the module
212 will be called rtc-pcf8563.
214 config RTC_DRV_PCF8583
215 tristate "Philips PCF8583"
217 If you say yes here you get support for the Philips PCF8583
218 RTC chip found on Acorn RiscPCs. This driver supports the
219 platform specific method of retrieving the current year from
220 the RTC's SRAM. It will work on other platforms with the same
221 chip, but the year will probably have to be tweaked.
223 This driver can also be built as a module. If so, the module
224 will be called rtc-pcf8583.
226 config RTC_DRV_M41T80
227 tristate "ST M41T80/81/82/83/84/85/87"
229 If you say Y here you will get support for the
230 ST M41T80 RTC chips series. Currently following chips are
231 supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85
234 This driver can also be built as a module. If so, the module
235 will be called rtc-m41t80.
237 config RTC_DRV_M41T80_WDT
238 bool "ST M41T80 series RTC watchdog timer"
239 depends on RTC_DRV_M41T80
241 If you say Y here you will get support for the
242 watchdog timer in ST M41T80 RTC chips series.
244 config RTC_DRV_TWL92330
245 boolean "TI TWL92330/Menelaus"
248 If you say yes here you get support for the RTC on the
249 TWL92330 "Menelaus" power management chip, used with OMAP2
250 platforms. The support is integrated with the rest of
251 the Menelaus driver; it's not separate module.
255 comment "SPI RTC drivers"
259 config RTC_DRV_MAX6902
260 tristate "Maxim MAX6902"
262 If you say yes here you will get support for the
263 Maxim MAX6902 SPI RTC chip.
265 This driver can also be built as a module. If so, the module
266 will be called rtc-max6902.
268 config RTC_DRV_RS5C348
269 tristate "Ricoh RS5C348A/B"
271 If you say yes here you get support for the
272 Ricoh RS5C348A and RS5C348B RTC chips.
274 This driver can also be built as a module. If so, the module
275 will be called rtc-rs5c348.
279 comment "Platform RTC drivers"
281 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
282 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
283 # global rtc_lock ... it's not yet just another platform_device.
286 tristate "PC-style 'CMOS'"
287 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS
289 Say "yes" here to get direct support for the real time clock
290 found in every PC or ACPI-based system, and some other boards.
291 Specifically the original MC146818, compatibles like those in
292 PC south bridges, the DS12887 or M48T86, some multifunction
293 or LPC bus chips, and so on.
295 Your system will need to define the platform device used by
296 this driver, otherwise it won't be accessible. This means
297 you can safely enable this driver if you don't know whether
298 or not your board has this kind of hardware.
300 This driver can also be built as a module. If so, the module
301 will be called rtc-cmos.
303 config RTC_DRV_DS1216
304 tristate "Dallas DS1216"
307 If you say yes here you get support for the Dallas DS1216 RTC chips.
309 config RTC_DRV_DS1302
310 tristate "Dallas DS1302"
311 depends on SH_SECUREEDGE5410
313 If you say yes here you get support for the Dallas DS1302 RTC chips.
315 config RTC_DRV_DS1511
316 tristate "Dallas DS1511"
319 If you say yes here you get support for the
320 Dallas DS1511 timekeeping/watchdog chip.
322 This driver can also be built as a module. If so, the module
323 will be called rtc-ds1511.
325 config RTC_DRV_DS1553
326 tristate "Maxim/Dallas DS1553"
328 If you say yes here you get support for the
329 Maxim/Dallas DS1553 timekeeping chip.
331 This driver can also be built as a module. If so, the module
332 will be called rtc-ds1553.
334 config RTC_DRV_DS1742
335 tristate "Maxim/Dallas DS1742/1743"
337 If you say yes here you get support for the
338 Maxim/Dallas DS1742/1743 timekeeping chip.
340 This driver can also be built as a module. If so, the module
341 will be called rtc-ds1742.
343 config RTC_DRV_STK17TA8
344 tristate "Simtek STK17TA8"
347 If you say yes here you get support for the
348 Simtek STK17TA8 timekeeping chip.
350 This driver can also be built as a module. If so, the module
351 will be called rtc-stk17ta8.
353 config RTC_DRV_M48T86
354 tristate "ST M48T86/Dallas DS12887"
356 If you say Y here you will get support for the
357 ST M48T86 and Dallas DS12887 RTC chips.
359 This driver can also be built as a module. If so, the module
360 will be called rtc-m48t86.
362 config RTC_DRV_M48T59
365 If you say Y here you will get support for the
368 This driver can also be built as a module, if so, the module
369 will be called "rtc-m48t59".
372 tristate "EM Microelectronic V3020"
374 If you say yes here you will get support for the
375 EM Microelectronic v3020 RTC chip.
377 This driver can also be built as a module. If so, the module
378 will be called rtc-v3020.
380 comment "on-CPU RTC drivers"
384 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730
386 Say "yes" here to support the real time clock on TI OMAP1 chips.
387 This driver can also be built as a module called rtc-omap.
390 tristate "Samsung S3C series SoC RTC"
391 depends on ARCH_S3C2410
393 RTC (Realtime Clock) driver for the clock inbuilt into the
394 Samsung S3C24XX series of SoCs. This can provide periodic
395 interrupt rates from 1Hz to 64Hz for user programs, and
398 The driver currently supports the common features on all the
399 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
402 This driver can also be build as a module. If so, the module
403 will be called rtc-s3c.
405 config RTC_DRV_EP93XX
406 tristate "Cirrus Logic EP93XX"
407 depends on ARCH_EP93XX
409 If you say yes here you get support for the
410 RTC embedded in the Cirrus Logic EP93XX processors.
412 This driver can also be built as a module. If so, the module
413 will be called rtc-ep93xx.
415 config RTC_DRV_SA1100
416 tristate "SA11x0/PXA2xx"
417 depends on ARCH_SA1100 || ARCH_PXA
419 If you say Y here you will get access to the real time clock
420 built into your SA11x0 or PXA2xx CPU.
422 To compile this driver as a module, choose M here: the
423 module will be called rtc-sa1100.
426 tristate "SuperH On-Chip RTC"
427 depends on RTC_CLASS && SUPERH
429 Say Y here to enable support for the on-chip RTC found in
430 most SuperH processors.
432 To compile this driver as a module, choose M here: the
433 module will be called rtc-sh.
435 config RTC_DRV_VR41XX
436 tristate "NEC VR41XX"
437 depends on CPU_VR41XX
439 If you say Y here you will get access to the real time clock
440 built into your NEC VR41XX CPU.
442 To compile this driver as a module, choose M here: the
443 module will be called rtc-vr41xx.
446 tristate "ARM AMBA PL031 RTC"
449 If you say Y here you will get access to ARM AMBA
450 PrimeCell PL031 RTC found on certain ARM SOCs.
452 To compile this driver as a module, choose M here: the
453 module will be called rtc-pl031.
455 config RTC_DRV_AT32AP700X
456 tristate "AT32AP700X series RTC"
457 depends on PLATFORM_AT32AP
459 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
460 AT32AP700x family processors.
462 config RTC_DRV_AT91RM9200
463 tristate "AT91RM9200"
464 depends on ARCH_AT91RM9200
466 Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).
469 tristate "Blackfin On-Chip RTC"
472 If you say yes here you will get support for the
473 Blackfin On-Chip Real Time Clock.
475 This driver can also be built as a module. If so, the module
476 will be called rtc-bfin.
478 config RTC_DRV_RS5C313
479 tristate "Ricoh RS5C313"
480 depends on SH_LANDISK
482 If you say yes here you get support for the Ricoh RS5C313 RTC chips.