Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tjh.dev
kernel
os
linux
1\#
2# RTC class/drivers configuration
3#
4
5menu "Real Time Clock"
6
7config RTC_LIB
8 tristate
9
10config 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
18 probably want to enable one or more of the interfaces below.
19
20 This driver can also be built as a module. If so, the module
21 will be called rtc-class.
22
23config 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 fsck runs.
31
32config 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
40config RTC_DEBUG
41 bool "RTC debug support"
42 depends on RTC_CLASS = y
43 help
44 Say yes here to enable debugging support in the RTC framework
45 and individual RTC drivers.
46
47comment "RTC interfaces"
48 depends on RTC_CLASS
49
50config RTC_INTF_SYSFS
51 tristate "sysfs"
52 depends on RTC_CLASS && SYSFS
53 default RTC_CLASS
54 help
55 Say yes here if you want to use your RTCs using sysfs interfaces,
56 /sys/class/rtc/rtc0 through /sys/.../rtcN.
57
58 This driver can also be built as a module. If so, the module
59 will be called rtc-sysfs.
60
61config RTC_INTF_PROC
62 tristate "proc"
63 depends on RTC_CLASS && PROC_FS
64 default RTC_CLASS
65 help
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
68 through that API.
69
70 This driver can also be built as a module. If so, the module
71 will be called rtc-proc.
72
73config RTC_INTF_DEV
74 tristate "dev"
75 depends on RTC_CLASS
76 default RTC_CLASS
77 help
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.
83
84 This driver can also be built as a module. If so, the module
85 will be called rtc-dev.
86
87config RTC_INTF_DEV_UIE_EMUL
88 bool "RTC UIE emulation on dev interface"
89 depends on RTC_INTF_DEV
90 help
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.
94
95comment "RTC drivers"
96 depends on RTC_CLASS
97
98config RTC_DRV_X1205
99 tristate "Xicor/Intersil X1205"
100 depends on RTC_CLASS && I2C
101 help
102 If you say yes here you get support for the
103 Xicor/Intersil X1205 RTC chip.
104
105 This driver can also be built as a module. If so, the module
106 will be called rtc-x1205.
107
108config RTC_DRV_DS1307
109 tristate "Dallas/Maxim DS1307 and similar I2C RTC chips"
110 depends on RTC_CLASS && I2C
111 help
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).
117
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.
122
123 This driver can also be built as a module. If so, the module
124 will be called rtc-ds1307.
125
126config RTC_DRV_DS1553
127 tristate "Dallas DS1553"
128 depends on RTC_CLASS
129 help
130 If you say yes here you get support for the
131 Dallas DS1553 timekeeping chip.
132
133 This driver can also be built as a module. If so, the module
134 will be called rtc-ds1553.
135
136config RTC_DRV_ISL1208
137 tristate "Intersil 1208"
138 depends on RTC_CLASS && I2C
139 help
140 If you say yes here you get support for the
141 Intersil 1208 RTC chip.
142
143 This driver can also be built as a module. If so, the module
144 will be called rtc-isl1208.
145
146config RTC_DRV_DS1672
147 tristate "Dallas/Maxim DS1672"
148 depends on RTC_CLASS && I2C
149 help
150 If you say yes here you get support for the
151 Dallas/Maxim DS1672 timekeeping chip.
152
153 This driver can also be built as a module. If so, the module
154 will be called rtc-ds1672.
155
156config RTC_DRV_DS1742
157 tristate "Dallas DS1742"
158 depends on RTC_CLASS
159 help
160 If you say yes here you get support for the
161 Dallas DS1742 timekeeping chip.
162
163 This driver can also be built as a module. If so, the module
164 will be called rtc-ds1742.
165
166config RTC_DRV_PCF8563
167 tristate "Philips PCF8563/Epson RTC8564"
168 depends on RTC_CLASS && I2C
169 help
170 If you say yes here you get support for the
171 Philips PCF8563 RTC chip. The Epson RTC8564
172 should work as well.
173
174 This driver can also be built as a module. If so, the module
175 will be called rtc-pcf8563.
176
177config RTC_DRV_PCF8583
178 tristate "Philips PCF8583"
179 depends on RTC_CLASS && I2C
180 help
181 If you say yes here you get support for the
182 Philips PCF8583 RTC chip.
183
184 This driver can also be built as a module. If so, the module
185 will be called rtc-pcf8583.
186
187config RTC_DRV_RS5C348
188 tristate "Ricoh RS5C348A/B"
189 depends on RTC_CLASS && SPI
190 help
191 If you say yes here you get support for the
192 Ricoh RS5C348A and RS5C348B RTC chips.
193
194 This driver can also be built as a module. If so, the module
195 will be called rtc-rs5c348.
196
197config RTC_DRV_RS5C372
198 tristate "Ricoh RS5C372A/B"
199 depends on RTC_CLASS && I2C
200 help
201 If you say yes here you get support for the
202 Ricoh RS5C372A and RS5C372B RTC chips.
203
204 This driver can also be built as a module. If so, the module
205 will be called rtc-rs5c372.
206
207config RTC_DRV_S3C
208 tristate "Samsung S3C series SoC RTC"
209 depends on RTC_CLASS && ARCH_S3C2410
210 help
211 RTC (Realtime Clock) driver for the clock inbuilt into the
212 Samsung S3C24XX series of SoCs. This can provide periodic
213 interrupt rates from 1Hz to 64Hz for user programs, and
214 wakeup from Alarm.
215
216 The driver currently supports the common features on all the
217 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
218 and S3C2442.
219
220 This driver can also be build as a module. If so, the module
221 will be called rtc-s3c.
222
223config RTC_DRV_M48T86
224 tristate "ST M48T86/Dallas DS12887"
225 depends on RTC_CLASS
226 help
227 If you say Y here you will get support for the
228 ST M48T86 and Dallas DS12887 RTC chips.
229
230 This driver can also be built as a module. If so, the module
231 will be called rtc-m48t86.
232
233config RTC_DRV_EP93XX
234 tristate "Cirrus Logic EP93XX"
235 depends on RTC_CLASS && ARCH_EP93XX
236 help
237 If you say yes here you get support for the
238 RTC embedded in the Cirrus Logic EP93XX processors.
239
240 This driver can also be built as a module. If so, the module
241 will be called rtc-ep93xx.
242
243config RTC_DRV_SA1100
244 tristate "SA11x0/PXA2xx"
245 depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA)
246 help
247 If you say Y here you will get access to the real time clock
248 built into your SA11x0 or PXA2xx CPU.
249
250 To compile this driver as a module, choose M here: the
251 module will be called rtc-sa1100.
252
253config RTC_DRV_SH
254 tristate "SuperH On-Chip RTC"
255 depends on RTC_CLASS && SUPERH
256 help
257 Say Y here to enable support for the on-chip RTC found in
258 most SuperH processors.
259
260 To compile this driver as a module, choose M here: the
261 module will be called rtc-sh.
262
263config RTC_DRV_VR41XX
264 tristate "NEC VR41XX"
265 depends on RTC_CLASS && CPU_VR41XX
266 help
267 If you say Y here you will get access to the real time clock
268 built into your NEC VR41XX CPU.
269
270 To compile this driver as a module, choose M here: the
271 module will be called rtc-vr41xx.
272
273config RTC_DRV_PL031
274 tristate "ARM AMBA PL031 RTC"
275 depends on RTC_CLASS && ARM_AMBA
276 help
277 If you say Y here you will get access to ARM AMBA
278 PrimeCell PL031 UART found on certain ARM SOCs.
279
280 To compile this driver as a module, choose M here: the
281 module will be called rtc-pl031.
282
283config RTC_DRV_AT91
284 tristate "AT91RM9200"
285 depends on RTC_CLASS && ARCH_AT91RM9200
286 help
287 Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).
288
289config RTC_DRV_TEST
290 tristate "Test driver/device"
291 depends on RTC_CLASS
292 help
293 If you say yes here you get support for the
294 RTC test driver. It's a software RTC which can be
295 used to test the RTC subsystem APIs. It gets
296 the time from the system clock.
297 You want this driver only if you are doing development
298 on the RTC subsystem. Please read the source code
299 for further details.
300
301 This driver can also be built as a module. If so, the module
302 will be called rtc-test.
303
304config RTC_DRV_MAX6902
305 tristate "Maxim 6902"
306 depends on RTC_CLASS && SPI
307 help
308 If you say yes here you will get support for the
309 Maxim MAX6902 spi RTC chip.
310
311 This driver can also be built as a module. If so, the module
312 will be called rtc-max6902.
313
314config RTC_DRV_V3020
315 tristate "EM Microelectronic V3020"
316 depends on RTC_CLASS
317 help
318 If you say yes here you will get support for the
319 EM Microelectronic v3020 RTC chip.
320
321 This driver can also be built as a module. If so, the module
322 will be called rtc-v3020.
323
324endmenu