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 fschk 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.
40 comment "RTC interfaces"
45 depends on RTC_CLASS && SYSFS
48 Say yes here if you want to use your RTC using the sysfs
49 interface, /sys/class/rtc/rtcX .
51 This driver can also be built as a module. If so, the module
52 will be called rtc-sysfs.
56 depends on RTC_CLASS && PROC_FS
59 Say yes here if you want to use your RTC using the proc
60 interface, /proc/driver/rtc .
62 This driver can also be built as a module. If so, the module
63 will be called rtc-proc.
70 Say yes here if you want to use your RTC using the dev
73 This driver can also be built as a module. If so, the module
74 will be called rtc-dev.
76 config RTC_INTF_DEV_UIE_EMUL
77 bool "RTC UIE emulation on dev interface"
78 depends on RTC_INTF_DEV
80 Provides an emulation for RTC_UIE if the underlaying rtc chip
81 driver did not provide RTC_UIE ioctls.
87 tristate "Xicor/Intersil X1205"
88 depends on RTC_CLASS && I2C
90 If you say yes here you get support for the
91 Xicor/Intersil X1205 RTC chip.
93 This driver can also be built as a module. If so, the module
94 will be called rtc-x1205.
97 tristate "Dallas/Maxim DS1307 and similar I2C RTC chips"
98 depends on RTC_CLASS && I2C
100 If you say yes here you get support for various compatible RTC
101 chips (often with battery backup) connected with I2C. This driver
102 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
103 and probably other chips. In some cases the RTC must already
104 have been initialized (by manufacturing or a bootloader).
106 The first seven registers on these chips hold an RTC, and other
107 registers may add features such as NVRAM, a trickle charger for
108 the RTC/NVRAM backup power, and alarms. This driver may not
109 expose all those available chip features.
111 This driver can also be built as a module. If so, the module
112 will be called rtc-ds1307.
114 config RTC_DRV_DS1553
115 tristate "Dallas DS1553"
118 If you say yes here you get support for the
119 Dallas DS1553 timekeeping chip.
121 This driver can also be built as a module. If so, the module
122 will be called rtc-ds1553.
124 config RTC_DRV_DS1672
125 tristate "Dallas/Maxim DS1672"
126 depends on RTC_CLASS && I2C
128 If you say yes here you get support for the
129 Dallas/Maxim DS1672 timekeeping chip.
131 This driver can also be built as a module. If so, the module
132 will be called rtc-ds1672.
134 config RTC_DRV_DS1742
135 tristate "Dallas DS1742"
138 If you say yes here you get support for the
139 Dallas DS1742 timekeeping chip.
141 This driver can also be built as a module. If so, the module
142 will be called rtc-ds1742.
144 config RTC_DRV_PCF8563
145 tristate "Philips PCF8563/Epson RTC8564"
146 depends on RTC_CLASS && I2C
148 If you say yes here you get support for the
149 Philips PCF8563 RTC chip. The Epson RTC8564
152 This driver can also be built as a module. If so, the module
153 will be called rtc-pcf8563.
155 config RTC_DRV_PCF8583
156 tristate "Philips PCF8583"
157 depends on RTC_CLASS && I2C
159 If you say yes here you get support for the
160 Philips PCF8583 RTC chip.
162 This driver can also be built as a module. If so, the module
163 will be called rtc-pcf8583.
165 config RTC_DRV_RS5C348
166 tristate "Ricoh RS5C348A/B"
167 depends on RTC_CLASS && SPI
169 If you say yes here you get support for the
170 Ricoh RS5C348A and RS5C348B RTC chips.
172 This driver can also be built as a module. If so, the module
173 will be called rtc-rs5c348.
175 config RTC_DRV_RS5C372
176 tristate "Ricoh RS5C372A/B"
177 depends on RTC_CLASS && I2C
179 If you say yes here you get support for the
180 Ricoh RS5C372A and RS5C372B RTC chips.
182 This driver can also be built as a module. If so, the module
183 will be called rtc-rs5c372.
185 config RTC_DRV_M48T86
186 tristate "ST M48T86/Dallas DS12887"
189 If you say Y here you will get support for the
190 ST M48T86 and Dallas DS12887 RTC chips.
192 This driver can also be built as a module. If so, the module
193 will be called rtc-m48t86.
195 config RTC_DRV_EP93XX
196 tristate "Cirrus Logic EP93XX"
197 depends on RTC_CLASS && ARCH_EP93XX
199 If you say yes here you get support for the
200 RTC embedded in the Cirrus Logic EP93XX processors.
202 This driver can also be built as a module. If so, the module
203 will be called rtc-ep93xx.
205 config RTC_DRV_SA1100
206 tristate "SA11x0/PXA2xx"
207 depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA)
209 If you say Y here you will get access to the real time clock
210 built into your SA11x0 or PXA2xx CPU.
212 To compile this driver as a module, choose M here: the
213 module will be called rtc-sa1100.
215 config RTC_DRV_VR41XX
216 tristate "NEC VR41XX"
217 depends on RTC_CLASS && CPU_VR41XX
219 If you say Y here you will get access to the real time clock
220 built into your NEC VR41XX CPU.
222 To compile this driver as a module, choose M here: the
223 module will be called rtc-vr41xx.
226 tristate "ARM AMBA PL031 RTC"
227 depends on RTC_CLASS && ARM_AMBA
229 If you say Y here you will get access to ARM AMBA
230 PrimeCell PL031 UART found on certain ARM SOCs.
232 To compile this driver as a module, choose M here: the
233 module will be called rtc-pl031.
236 tristate "AT91RM9200"
237 depends on RTC_CLASS && ARCH_AT91RM9200
239 Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).
242 tristate "Test driver/device"
245 If you say yes here you get support for the
246 RTC test driver. It's a software RTC which can be
247 used to test the RTC subsystem APIs. It gets
248 the time from the system clock.
249 You want this driver only if you are doing development
250 on the RTC subsystem. Please read the source code
253 This driver can also be built as a module. If so, the module
254 will be called rtc-test.
256 config RTC_DRV_MAX6902
257 tristate "Maxim 6902"
258 depends on RTC_CLASS && SPI
260 If you say yes here you will get support for the
261 Maxim MAX6902 spi RTC chip.
263 This driver can also be built as a module. If so, the module
264 will be called rtc-max6902.
267 tristate "EM Microelectronic V3020"
270 If you say yes here you will get support for the
271 EM Microelectronic v3020 RTC chip.
273 This driver can also be built as a module. If so, the module
274 will be called rtc-v3020.