]>
Commit | Line | Data |
---|---|---|
0c86edc0 | 1 | \# |
c58411e9 AZ |
2 | # RTC class/drivers configuration |
3 | # | |
4 | ||
0c86edc0 AZ |
5 | menu "Real Time Clock" |
6 | ||
c58411e9 | 7 | config RTC_LIB |
0c86edc0 AZ |
8 | tristate |
9 | ||
10 | config RTC_CLASS | |
11 | tristate "RTC class" | |
12 | depends on EXPERIMENTAL | |
13 | default n | |
14 | select RTC_LIB | |
15 | help | |
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 | |
27ae4104 | 18 | probably want to enable one or more of the interfaces below. |
0c86edc0 AZ |
19 | |
20 | This driver can also be built as a module. If so, the module | |
21 | will be called rtc-class. | |
22 | ||
23 | config RTC_HCTOSYS | |
24 | bool "Set system time from RTC on startup" | |
25 | depends on RTC_CLASS = y | |
26 | default y | |
27 | help | |
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. | |
31 | ||
32 | config RTC_HCTOSYS_DEVICE | |
33 | string "The RTC to read the time from" | |
34 | depends on RTC_HCTOSYS = y | |
35 | default "rtc0" | |
36 | help | |
37 | The RTC device that will be used as the source for | |
38 | the system time, usually rtc0. | |
39 | ||
40 | comment "RTC interfaces" | |
41 | depends on RTC_CLASS | |
42 | ||
c5c3e192 AZ |
43 | config RTC_INTF_SYSFS |
44 | tristate "sysfs" | |
45 | depends on RTC_CLASS && SYSFS | |
46 | default RTC_CLASS | |
47 | help | |
48 | Say yes here if you want to use your RTC using the sysfs | |
49 | interface, /sys/class/rtc/rtcX . | |
50 | ||
51 | This driver can also be built as a module. If so, the module | |
52 | will be called rtc-sysfs. | |
53 | ||
728a2947 AZ |
54 | config RTC_INTF_PROC |
55 | tristate "proc" | |
56 | depends on RTC_CLASS && PROC_FS | |
57 | default RTC_CLASS | |
58 | help | |
59 | Say yes here if you want to use your RTC using the proc | |
60 | interface, /proc/driver/rtc . | |
61 | ||
62 | This driver can also be built as a module. If so, the module | |
63 | will be called rtc-proc. | |
64 | ||
e824290e AZ |
65 | config RTC_INTF_DEV |
66 | tristate "dev" | |
67 | depends on RTC_CLASS | |
68 | default RTC_CLASS | |
69 | help | |
70 | Say yes here if you want to use your RTC using the dev | |
71 | interface, /dev/rtc . | |
72 | ||
73 | This driver can also be built as a module. If so, the module | |
74 | will be called rtc-dev. | |
75 | ||
655066c3 AN |
76 | config RTC_INTF_DEV_UIE_EMUL |
77 | bool "RTC UIE emulation on dev interface" | |
78 | depends on RTC_INTF_DEV | |
79 | help | |
80 | Provides an emulation for RTC_UIE if the underlaying rtc chip | |
81 | driver did not provide RTC_UIE ioctls. | |
82 | ||
0c86edc0 AZ |
83 | comment "RTC drivers" |
84 | depends on RTC_CLASS | |
85 | ||
1fec7c66 AZ |
86 | config RTC_DRV_X1205 |
87 | tristate "Xicor/Intersil X1205" | |
88 | depends on RTC_CLASS && I2C | |
89 | help | |
90 | If you say yes here you get support for the | |
91 | Xicor/Intersil X1205 RTC chip. | |
92 | ||
93 | This driver can also be built as a module. If so, the module | |
94 | will be called rtc-x1205. | |
95 | ||
1abb0dc9 DB |
96 | config RTC_DRV_DS1307 |
97 | tristate "Dallas/Maxim DS1307 and similar I2C RTC chips" | |
98 | depends on RTC_CLASS && I2C | |
99 | help | |
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). | |
105 | ||
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. | |
110 | ||
111 | This driver can also be built as a module. If so, the module | |
112 | will be called rtc-ds1307. | |
113 | ||
9bf5b4f5 AN |
114 | config RTC_DRV_DS1553 |
115 | tristate "Dallas DS1553" | |
116 | depends on RTC_CLASS | |
117 | help | |
118 | If you say yes here you get support for the | |
119 | Dallas DS1553 timekeeping chip. | |
120 | ||
121 | This driver can also be built as a module. If so, the module | |
122 | will be called rtc-ds1553. | |
123 | ||
edf1aaa3 AZ |
124 | config RTC_DRV_DS1672 |
125 | tristate "Dallas/Maxim DS1672" | |
126 | depends on RTC_CLASS && I2C | |
127 | help | |
128 | If you say yes here you get support for the | |
129 | Dallas/Maxim DS1672 timekeeping chip. | |
130 | ||
131 | This driver can also be built as a module. If so, the module | |
132 | will be called rtc-ds1672. | |
133 | ||
5ec3e4b7 AN |
134 | config RTC_DRV_DS1742 |
135 | tristate "Dallas DS1742" | |
136 | depends on RTC_CLASS | |
137 | help | |
138 | If you say yes here you get support for the | |
139 | Dallas DS1742 timekeeping chip. | |
140 | ||
141 | This driver can also be built as a module. If so, the module | |
142 | will be called rtc-ds1742. | |
143 | ||
b5a82d62 AZ |
144 | config RTC_DRV_PCF8563 |
145 | tristate "Philips PCF8563/Epson RTC8564" | |
146 | depends on RTC_CLASS && I2C | |
147 | help | |
148 | If you say yes here you get support for the | |
149 | Philips PCF8563 RTC chip. The Epson RTC8564 | |
150 | should work as well. | |
151 | ||
152 | This driver can also be built as a module. If so, the module | |
153 | will be called rtc-pcf8563. | |
154 | ||
9c0c5705 L |
155 | config RTC_DRV_PCF8583 |
156 | tristate "Philips PCF8583" | |
157 | depends on RTC_CLASS && I2C | |
158 | help | |
159 | If you say yes here you get support for the | |
160 | Philips PCF8583 RTC chip. | |
161 | ||
162 | This driver can also be built as a module. If so, the module | |
163 | will be called rtc-pcf8583. | |
164 | ||
e0ac4761 AN |
165 | config RTC_DRV_RS5C348 |
166 | tristate "Ricoh RS5C348A/B" | |
167 | depends on RTC_CLASS && SPI | |
168 | help | |
169 | If you say yes here you get support for the | |
170 | Ricoh RS5C348A and RS5C348B RTC chips. | |
171 | ||
172 | This driver can also be built as a module. If so, the module | |
173 | will be called rtc-rs5c348. | |
174 | ||
7520b94d AZ |
175 | config RTC_DRV_RS5C372 |
176 | tristate "Ricoh RS5C372A/B" | |
177 | depends on RTC_CLASS && I2C | |
178 | help | |
179 | If you say yes here you get support for the | |
180 | Ricoh RS5C372A and RS5C372B RTC chips. | |
181 | ||
182 | This driver can also be built as a module. If so, the module | |
183 | will be called rtc-rs5c372. | |
184 | ||
1add6781 BD |
185 | config RTC_DRV_S3C |
186 | tristate "Samsung S3C series SoC RTC" | |
187 | depends on RTC_CLASS && ARCH_S3C2410 | |
188 | help | |
189 | RTC (Realtime Clock) driver for the clock inbuilt into the | |
190 | Samsung S3C24XX series of SoCs. This can provide periodic | |
191 | interrupt rates from 1Hz to 64Hz for user programs, and | |
192 | wakeup from Alarm. | |
193 | ||
194 | The driver currently supports the common features on all the | |
195 | S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 | |
196 | and S3C2442. | |
197 | ||
198 | This driver can also be build as a module. If so, the module | |
199 | will be called rtc-s3c. | |
200 | ||
1d98af87 AZ |
201 | config RTC_DRV_M48T86 |
202 | tristate "ST M48T86/Dallas DS12887" | |
203 | depends on RTC_CLASS | |
204 | help | |
205 | If you say Y here you will get support for the | |
206 | ST M48T86 and Dallas DS12887 RTC chips. | |
207 | ||
208 | This driver can also be built as a module. If so, the module | |
209 | will be called rtc-m48t86. | |
210 | ||
fd507e2f AZ |
211 | config RTC_DRV_EP93XX |
212 | tristate "Cirrus Logic EP93XX" | |
213 | depends on RTC_CLASS && ARCH_EP93XX | |
214 | help | |
215 | If you say yes here you get support for the | |
216 | RTC embedded in the Cirrus Logic EP93XX processors. | |
217 | ||
218 | This driver can also be built as a module. If so, the module | |
219 | will be called rtc-ep93xx. | |
220 | ||
e842f1c8 RP |
221 | config RTC_DRV_SA1100 |
222 | tristate "SA11x0/PXA2xx" | |
223 | depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA) | |
224 | help | |
225 | If you say Y here you will get access to the real time clock | |
226 | built into your SA11x0 or PXA2xx CPU. | |
227 | ||
228 | To compile this driver as a module, choose M here: the | |
229 | module will be called rtc-sa1100. | |
fd507e2f | 230 | |
8417eb7a | 231 | config RTC_DRV_VR41XX |
3e16f6af | 232 | tristate "NEC VR41XX" |
8417eb7a | 233 | depends on RTC_CLASS && CPU_VR41XX |
3e16f6af AZ |
234 | help |
235 | If you say Y here you will get access to the real time clock | |
236 | built into your NEC VR41XX CPU. | |
237 | ||
238 | To compile this driver as a module, choose M here: the | |
239 | module will be called rtc-vr41xx. | |
8417eb7a | 240 | |
8ae6e163 DS |
241 | config RTC_DRV_PL031 |
242 | tristate "ARM AMBA PL031 RTC" | |
243 | depends on RTC_CLASS && ARM_AMBA | |
244 | help | |
245 | If you say Y here you will get access to ARM AMBA | |
246 | PrimeCell PL031 UART found on certain ARM SOCs. | |
247 | ||
248 | To compile this driver as a module, choose M here: the | |
249 | module will be called rtc-pl031. | |
250 | ||
788b1fc6 AV |
251 | config RTC_DRV_AT91 |
252 | tristate "AT91RM9200" | |
253 | depends on RTC_CLASS && ARCH_AT91RM9200 | |
254 | help | |
255 | Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock). | |
256 | ||
a95579cd AZ |
257 | config RTC_DRV_TEST |
258 | tristate "Test driver/device" | |
259 | depends on RTC_CLASS | |
260 | help | |
261 | If you say yes here you get support for the | |
262 | RTC test driver. It's a software RTC which can be | |
263 | used to test the RTC subsystem APIs. It gets | |
264 | the time from the system clock. | |
265 | You want this driver only if you are doing development | |
266 | on the RTC subsystem. Please read the source code | |
267 | for further details. | |
268 | ||
269 | This driver can also be built as a module. If so, the module | |
270 | will be called rtc-test. | |
271 | ||
8e12ecc2 RA |
272 | config RTC_DRV_MAX6902 |
273 | tristate "Maxim 6902" | |
274 | depends on RTC_CLASS && SPI | |
275 | help | |
276 | If you say yes here you will get support for the | |
277 | Maxim MAX6902 spi RTC chip. | |
278 | ||
279 | This driver can also be built as a module. If so, the module | |
280 | will be called rtc-max6902. | |
281 | ||
362600fe RA |
282 | config RTC_DRV_V3020 |
283 | tristate "EM Microelectronic V3020" | |
284 | depends on RTC_CLASS | |
285 | help | |
286 | If you say yes here you will get support for the | |
287 | EM Microelectronic v3020 RTC chip. | |
288 | ||
289 | This driver can also be built as a module. If so, the module | |
290 | will be called rtc-v3020. | |
291 | ||
0c86edc0 | 292 | endmenu |