2 # RTC class/drivers configuration
12 depends on EXPERIMENTAL
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"
25 depends on RTC_CLASS = y
28 If you say yes here, the system time will be set using
29 the value read from the specified RTC device. This is useful
30 in order to avoid unnecessary fsck runs.
32 config RTC_HCTOSYS_DEVICE
33 string "The RTC to read the time from"
34 depends on RTC_HCTOSYS = y
37 The RTC device that will be used as the source for
38 the system time, usually rtc0.
41 bool "RTC debug support"
42 depends on RTC_CLASS = y
44 Say yes here to enable debugging support in the RTC framework
45 and individual RTC drivers.
47 comment "RTC interfaces"
52 depends on RTC_CLASS && SYSFS
55 Say yes here if you want to use your RTCs using sysfs interfaces,
56 /sys/class/rtc/rtc0 through /sys/.../rtcN.
58 This driver can also be built as a module. If so, the module
59 will be called rtc-sysfs.
63 depends on RTC_CLASS && PROC_FS
66 Say yes here if you want to use your first RTC through the proc
67 interface, /proc/driver/rtc. Other RTCs will not be available
70 This driver can also be built as a module. If so, the module
71 will be called rtc-proc.
78 Say yes here if you want to use your RTCs using the /dev
79 interfaces, which "udev" sets up as /dev/rtc0 through
80 /dev/rtcN. You may want to set up a symbolic link so one
81 of these can be accessed as /dev/rtc, which is a name
82 expected by "hwclock" and some other programs.
84 This driver can also be built as a module. If so, the module
85 will be called rtc-dev.
87 config RTC_INTF_DEV_UIE_EMUL
88 bool "RTC UIE emulation on dev interface"
89 depends on RTC_INTF_DEV
91 Provides an emulation for RTC_UIE if the underlaying rtc chip
92 driver does not expose RTC_UIE ioctls. Those requests generate
93 once-per-second update interrupts, used for synchronization.
99 tristate "Xicor/Intersil X1205"
100 depends on RTC_CLASS && I2C
102 If you say yes here you get support for the
103 Xicor/Intersil X1205 RTC chip.
105 This driver can also be built as a module. If so, the module
106 will be called rtc-x1205.
108 config RTC_DRV_DS1307
109 tristate "Dallas/Maxim DS1307 and similar I2C RTC chips"
110 depends on RTC_CLASS && I2C
112 If you say yes here you get support for various compatible RTC
113 chips (often with battery backup) connected with I2C. This driver
114 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
115 and probably other chips. In some cases the RTC must already
116 have been initialized (by manufacturing or a bootloader).
118 The first seven registers on these chips hold an RTC, and other
119 registers may add features such as NVRAM, a trickle charger for
120 the RTC/NVRAM backup power, and alarms. This driver may not
121 expose all those available chip features.
123 This driver can also be built as a module. If so, the module
124 will be called rtc-ds1307.
126 config RTC_DRV_DS1553
127 tristate "Dallas DS1553"
130 If you say yes here you get support for the
131 Dallas DS1553 timekeeping chip.
133 This driver can also be built as a module. If so, the module
134 will be called rtc-ds1553.
136 config RTC_DRV_ISL1208
137 tristate "Intersil 1208"
138 depends on RTC_CLASS && I2C
140 If you say yes here you get support for the
141 Intersil 1208 RTC chip.
143 This driver can also be built as a module. If so, the module
144 will be called rtc-isl1208.
146 config RTC_DRV_DS1672
147 tristate "Dallas/Maxim DS1672"
148 depends on RTC_CLASS && I2C
150 If you say yes here you get support for the
151 Dallas/Maxim DS1672 timekeeping chip.
153 This driver can also be built as a module. If so, the module
154 will be called rtc-ds1672.
156 config RTC_DRV_DS1742
157 tristate "Dallas DS1742/1743"
160 If you say yes here you get support for the
161 Dallas DS1742/1743 timekeeping chip.
163 This driver can also be built as a module. If so, the module
164 will be called rtc-ds1742.
168 depends on RTC_CLASS && ( \
169 ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 )
171 Say "yes" here to support the real time clock on TI OMAP1 chips.
172 This driver can also be built as a module called rtc-omap.
174 config RTC_DRV_PCF8563
175 tristate "Philips PCF8563/Epson RTC8564"
176 depends on RTC_CLASS && I2C
178 If you say yes here you get support for the
179 Philips PCF8563 RTC chip. The Epson RTC8564
182 This driver can also be built as a module. If so, the module
183 will be called rtc-pcf8563.
185 config RTC_DRV_PCF8583
186 tristate "Philips PCF8583"
187 depends on RTC_CLASS && I2C
189 If you say yes here you get support for the
190 Philips PCF8583 RTC chip.
192 This driver can also be built as a module. If so, the module
193 will be called rtc-pcf8583.
195 config RTC_DRV_RS5C348
196 tristate "Ricoh RS5C348A/B"
197 depends on RTC_CLASS && SPI
199 If you say yes here you get support for the
200 Ricoh RS5C348A and RS5C348B RTC chips.
202 This driver can also be built as a module. If so, the module
203 will be called rtc-rs5c348.
205 config RTC_DRV_RS5C372
206 tristate "Ricoh RS5C372A/B"
207 depends on RTC_CLASS && I2C
209 If you say yes here you get support for the
210 Ricoh RS5C372A and RS5C372B RTC chips.
212 This driver can also be built as a module. If so, the module
213 will be called rtc-rs5c372.
216 tristate "Samsung S3C series SoC RTC"
217 depends on RTC_CLASS && ARCH_S3C2410
219 RTC (Realtime Clock) driver for the clock inbuilt into the
220 Samsung S3C24XX series of SoCs. This can provide periodic
221 interrupt rates from 1Hz to 64Hz for user programs, and
224 The driver currently supports the common features on all the
225 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
228 This driver can also be build as a module. If so, the module
229 will be called rtc-s3c.
231 config RTC_DRV_M48T86
232 tristate "ST M48T86/Dallas DS12887"
235 If you say Y here you will get support for the
236 ST M48T86 and Dallas DS12887 RTC chips.
238 This driver can also be built as a module. If so, the module
239 will be called rtc-m48t86.
241 config RTC_DRV_EP93XX
242 tristate "Cirrus Logic EP93XX"
243 depends on RTC_CLASS && ARCH_EP93XX
245 If you say yes here you get support for the
246 RTC embedded in the Cirrus Logic EP93XX processors.
248 This driver can also be built as a module. If so, the module
249 will be called rtc-ep93xx.
251 config RTC_DRV_SA1100
252 tristate "SA11x0/PXA2xx"
253 depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA)
255 If you say Y here you will get access to the real time clock
256 built into your SA11x0 or PXA2xx CPU.
258 To compile this driver as a module, choose M here: the
259 module will be called rtc-sa1100.
262 tristate "SuperH On-Chip RTC"
263 depends on RTC_CLASS && SUPERH
265 Say Y here to enable support for the on-chip RTC found in
266 most SuperH processors.
268 To compile this driver as a module, choose M here: the
269 module will be called rtc-sh.
271 config RTC_DRV_VR41XX
272 tristate "NEC VR41XX"
273 depends on RTC_CLASS && CPU_VR41XX
275 If you say Y here you will get access to the real time clock
276 built into your NEC VR41XX CPU.
278 To compile this driver as a module, choose M here: the
279 module will be called rtc-vr41xx.
282 tristate "ARM AMBA PL031 RTC"
283 depends on RTC_CLASS && ARM_AMBA
285 If you say Y here you will get access to ARM AMBA
286 PrimeCell PL031 UART found on certain ARM SOCs.
288 To compile this driver as a module, choose M here: the
289 module will be called rtc-pl031.
291 config RTC_DRV_AT91RM9200
292 tristate "AT91RM9200"
293 depends on RTC_CLASS && ARCH_AT91RM9200
295 Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).
298 tristate "Test driver/device"
301 If you say yes here you get support for the
302 RTC test driver. It's a software RTC which can be
303 used to test the RTC subsystem APIs. It gets
304 the time from the system clock.
305 You want this driver only if you are doing development
306 on the RTC subsystem. Please read the source code
309 This driver can also be built as a module. If so, the module
310 will be called rtc-test.
312 config RTC_DRV_MAX6902
313 tristate "Maxim 6902"
314 depends on RTC_CLASS && SPI
316 If you say yes here you will get support for the
317 Maxim MAX6902 spi RTC chip.
319 This driver can also be built as a module. If so, the module
320 will be called rtc-max6902.
323 tristate "EM Microelectronic V3020"
326 If you say yes here you will get support for the
327 EM Microelectronic v3020 RTC chip.
329 This driver can also be built as a module. If so, the module
330 will be called rtc-v3020.