2 # RTC class/drivers configuration
16 Generic RTC class support. If you say yes here, you will
17 be allowed to plug one or more RTCs to your system. You will
18 probably want to enable one or more of the interfaces below.
20 This driver can also be built as a module. If so, the module
21 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 This clock should be battery-backed, so that it reads the correct
42 time when the system boots from a power-off state. Otherwise, your
43 system will need an external clock source (like an NTP server).
45 If the clock you specify here is not battery backed, it may still
46 be useful to reinitialize system time when resuming from system
47 sleep states. Do not specify an RTC here unless it stays powered
48 during all this system's supported sleep states.
51 bool "RTC debug support"
52 depends on RTC_CLASS = y
54 Say yes here to enable debugging support in the RTC framework
55 and individual RTC drivers.
57 comment "RTC interfaces"
61 boolean "/sys/class/rtc/rtcN (sysfs)"
62 depends on RTC_CLASS && SYSFS
65 Say yes here if you want to use your RTCs using sysfs interfaces,
66 /sys/class/rtc/rtc0 through /sys/.../rtcN.
68 This driver can also be built as a module. If so, the module
69 will be called rtc-sysfs.
72 boolean "/proc/driver/rtc (procfs for rtc0)"
73 depends on RTC_CLASS && PROC_FS
76 Say yes here if you want to use your first RTC through the proc
77 interface, /proc/driver/rtc. Other RTCs will not be available
80 This driver can also be built as a module. If so, the module
81 will be called rtc-proc.
84 boolean "/dev/rtcN (character devices)"
88 Say yes here if you want to use your RTCs using the /dev
89 interfaces, which "udev" sets up as /dev/rtc0 through
90 /dev/rtcN. You may want to set up a symbolic link so one
91 of these can be accessed as /dev/rtc, which is a name
92 expected by "hwclock" and some other programs.
94 This driver can also be built as a module. If so, the module
95 will be called rtc-dev.
97 config RTC_INTF_DEV_UIE_EMUL
98 bool "RTC UIE emulation on dev interface"
99 depends on RTC_INTF_DEV
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.
106 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"
121 depends on RTC_CLASS && I2C
123 config RTC_DRV_DS1307
124 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00"
125 depends on RTC_CLASS && I2C
127 If you say yes here you get support for various compatible RTC
128 chips (often with battery backup) connected with I2C. This driver
129 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
130 and probably other chips. In some cases the RTC must already
131 have been initialized (by manufacturing or a bootloader).
133 The first seven registers on these chips hold an RTC, and other
134 registers may add features such as NVRAM, a trickle charger for
135 the RTC/NVRAM backup power, and alarms. This driver may not
136 expose all those available chip features.
138 This driver can also be built as a module. If so, the module
139 will be called rtc-ds1307.
141 config RTC_DRV_DS1672
142 tristate "Dallas/Maxim DS1672"
143 depends on RTC_CLASS && I2C
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"
153 depends on RTC_CLASS && I2C
155 If you say yes here you will get support for the
156 Maxim MAX6900 I2C RTC chip.
158 This driver can also be built as a module. If so, the module
159 will be called rtc-max6900.
161 config RTC_DRV_RS5C372
162 tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A"
163 depends on RTC_CLASS && I2C
165 If you say yes here you get support for the
166 Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
168 This driver can also be built as a module. If so, the module
169 will be called rtc-rs5c372.
171 config RTC_DRV_ISL1208
172 tristate "Intersil 1208"
173 depends on RTC_CLASS && I2C
175 If you say yes here you get support for the
176 Intersil 1208 RTC chip.
178 This driver can also be built as a module. If so, the module
179 will be called rtc-isl1208.
182 tristate "Xicor/Intersil X1205"
183 depends on RTC_CLASS && I2C
185 If you say yes here you get support for the
186 Xicor/Intersil X1205 RTC chip.
188 This driver can also be built as a module. If so, the module
189 will be called rtc-x1205.
191 config RTC_DRV_PCF8563
192 tristate "Philips PCF8563/Epson RTC8564"
193 depends on RTC_CLASS && I2C
195 If you say yes here you get support for the
196 Philips PCF8563 RTC chip. The Epson RTC8564
199 This driver can also be built as a module. If so, the module
200 will be called rtc-pcf8563.
202 config RTC_DRV_PCF8583
203 tristate "Philips PCF8583"
204 depends on RTC_CLASS && I2C
206 If you say yes here you get support for the Philips PCF8583
207 RTC chip found on Acorn RiscPCs. This driver supports the
208 platform specific method of retrieving the current year from
209 the RTC's SRAM. It will work on other platforms with the same
210 chip, but the year will probably have to be tweaked.
212 This driver can also be built as a module. If so, the module
213 will be called rtc-pcf8583.
215 config RTC_DRV_M41T80
216 tristate "ST M41T80 series RTC"
217 depends on RTC_CLASS && I2C
219 If you say Y here you will get support for the
220 ST M41T80 RTC chips series. Currently following chips are
221 supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85
224 This driver can also be built as a module. If so, the module
225 will be called rtc-m41t80.
227 comment "SPI RTC drivers"
228 depends on RTC_CLASS && SPI_MASTER
230 config RTC_DRV_RS5C348
231 tristate "Ricoh RS5C348A/B"
232 depends on RTC_CLASS && SPI_MASTER
234 If you say yes here you get support for the
235 Ricoh RS5C348A and RS5C348B RTC chips.
237 This driver can also be built as a module. If so, the module
238 will be called rtc-rs5c348.
240 config RTC_DRV_MAX6902
241 tristate "Maxim 6902"
242 depends on RTC_CLASS && SPI_MASTER
244 If you say yes here you will get support for the
245 Maxim MAX6902 SPI RTC chip.
247 This driver can also be built as a module. If so, the module
248 will be called rtc-max6902.
250 comment "Platform RTC drivers"
253 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
254 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
255 # global rtc_lock ... it's not yet just another platform_device.
258 tristate "PC-style 'CMOS'"
259 depends on RTC_CLASS && (X86 || ALPHA || ARM26 || ARM \
260 || M32R || ATARI || PPC || MIPS)
262 Say "yes" here to get direct support for the real time clock
263 found in every PC or ACPI-based system, and some other boards.
264 Specifically the original MC146818, compatibles like those in
265 PC south bridges, the DS12887 or M48T86, some multifunction
266 or LPC bus chips, and so on.
268 Your system will need to define the platform device used by
269 this driver, otherwise it won't be accessible. This means
270 you can safely enable this driver if you don't know whether
271 or not your board has this kind of hardware.
273 This driver can also be built as a module. If so, the module
274 will be called rtc-cmos.
276 config RTC_DRV_DS1553
277 tristate "Dallas DS1553"
280 If you say yes here you get support for the
281 Dallas DS1553 timekeeping chip.
283 This driver can also be built as a module. If so, the module
284 will be called rtc-ds1553.
286 config RTC_DRV_DS1742
287 tristate "Dallas DS1742/1743"
290 If you say yes here you get support for the
291 Dallas DS1742/1743 timekeeping chip.
293 This driver can also be built as a module. If so, the module
294 will be called rtc-ds1742.
296 config RTC_DRV_M48T86
297 tristate "ST M48T86/Dallas DS12887"
300 If you say Y here you will get support for the
301 ST M48T86 and Dallas DS12887 RTC chips.
303 This driver can also be built as a module. If so, the module
304 will be called rtc-m48t86.
307 tristate "EM Microelectronic V3020"
310 If you say yes here you will get support for the
311 EM Microelectronic v3020 RTC chip.
313 This driver can also be built as a module. If so, the module
314 will be called rtc-v3020.
316 comment "on-CPU RTC drivers"
321 depends on RTC_CLASS && ( \
322 ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 )
324 Say "yes" here to support the real time clock on TI OMAP1 chips.
325 This driver can also be built as a module called rtc-omap.
328 tristate "Samsung S3C series SoC RTC"
329 depends on RTC_CLASS && ARCH_S3C2410
331 RTC (Realtime Clock) driver for the clock inbuilt into the
332 Samsung S3C24XX series of SoCs. This can provide periodic
333 interrupt rates from 1Hz to 64Hz for user programs, and
336 The driver currently supports the common features on all the
337 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
340 This driver can also be build as a module. If so, the module
341 will be called rtc-s3c.
343 config RTC_DRV_EP93XX
344 tristate "Cirrus Logic EP93XX"
345 depends on RTC_CLASS && ARCH_EP93XX
347 If you say yes here you get support for the
348 RTC embedded in the Cirrus Logic EP93XX processors.
350 This driver can also be built as a module. If so, the module
351 will be called rtc-ep93xx.
353 config RTC_DRV_SA1100
354 tristate "SA11x0/PXA2xx"
355 depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA)
357 If you say Y here you will get access to the real time clock
358 built into your SA11x0 or PXA2xx CPU.
360 To compile this driver as a module, choose M here: the
361 module will be called rtc-sa1100.
364 tristate "SuperH On-Chip RTC"
365 depends on RTC_CLASS && SUPERH
367 Say Y here to enable support for the on-chip RTC found in
368 most SuperH processors.
370 To compile this driver as a module, choose M here: the
371 module will be called rtc-sh.
373 config RTC_DRV_VR41XX
374 tristate "NEC VR41XX"
375 depends on RTC_CLASS && CPU_VR41XX
377 If you say Y here you will get access to the real time clock
378 built into your NEC VR41XX CPU.
380 To compile this driver as a module, choose M here: the
381 module will be called rtc-vr41xx.
384 tristate "ARM AMBA PL031 RTC"
385 depends on RTC_CLASS && ARM_AMBA
387 If you say Y here you will get access to ARM AMBA
388 PrimeCell PL031 RTC found on certain ARM SOCs.
390 To compile this driver as a module, choose M here: the
391 module will be called rtc-pl031.
393 config RTC_DRV_AT32AP700X
394 tristate "AT32AP700X series RTC"
395 depends on RTC_CLASS && PLATFORM_AT32AP
397 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
398 AT32AP700x family processors.
400 config RTC_DRV_AT91RM9200
401 tristate "AT91RM9200"
402 depends on RTC_CLASS && ARCH_AT91RM9200
404 Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).
407 tristate "Blackfin On-Chip RTC"
408 depends on RTC_CLASS && BFIN
410 If you say yes here you will get support for the
411 Blackfin On-Chip Real Time Clock.
413 This driver can also be built as a module. If so, the module
414 will be called rtc-bfin.
416 config RTC_DRV_RS5C313
417 tristate "Ricoh RS5C313"
418 depends on RTC_CLASS && SH_LANDISK
420 If you say yes here you get support for the Ricoh RS5C313 RTC chips.