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 98# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> 99# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a 100# global rtc_lock ... it's not yet just another platform_device. 101 102config RTC_DRV_CMOS 103 tristate "PC-style 'CMOS' real time clock" 104 depends on RTC_CLASS && (X86_PC || ALPHA || ARM26 || ARM \ 105 || M32R || ATARI || POWERPC) 106 help 107 Say "yes" here to get direct support for the real time clock 108 found in every PC or ACPI-based system, and some other boards. 109 Specifically the original MC146818, compatibles like those in 110 PC south bridges, the DS12887 or M48T86, some multifunction 111 or LPC bus chips, and so on. 112 113 Your system will need to define the platform device used by 114 this driver, otherwise it won't be accessible. This means 115 you can safely enable this driver if you don't know whether 116 or not your board has this kind of hardware. 117 118 This driver can also be built as a module. If so, the module 119 will be called rtc-cmos. 120 121config RTC_DRV_X1205 122 tristate "Xicor/Intersil X1205" 123 depends on RTC_CLASS && I2C 124 help 125 If you say yes here you get support for the 126 Xicor/Intersil X1205 RTC chip. 127 128 This driver can also be built as a module. If so, the module 129 will be called rtc-x1205. 130 131config RTC_DRV_DS1307 132 tristate "Dallas/Maxim DS1307 and similar I2C RTC chips" 133 depends on RTC_CLASS && I2C 134 help 135 If you say yes here you get support for various compatible RTC 136 chips (often with battery backup) connected with I2C. This driver 137 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00, 138 and probably other chips. In some cases the RTC must already 139 have been initialized (by manufacturing or a bootloader). 140 141 The first seven registers on these chips hold an RTC, and other 142 registers may add features such as NVRAM, a trickle charger for 143 the RTC/NVRAM backup power, and alarms. This driver may not 144 expose all those available chip features. 145 146 This driver can also be built as a module. If so, the module 147 will be called rtc-ds1307. 148 149config RTC_DRV_DS1553 150 tristate "Dallas DS1553" 151 depends on RTC_CLASS 152 help 153 If you say yes here you get support for the 154 Dallas DS1553 timekeeping chip. 155 156 This driver can also be built as a module. If so, the module 157 will be called rtc-ds1553. 158 159config RTC_DRV_ISL1208 160 tristate "Intersil 1208" 161 depends on RTC_CLASS && I2C 162 help 163 If you say yes here you get support for the 164 Intersil 1208 RTC chip. 165 166 This driver can also be built as a module. If so, the module 167 will be called rtc-isl1208. 168 169config RTC_DRV_DS1672 170 tristate "Dallas/Maxim DS1672" 171 depends on RTC_CLASS && I2C 172 help 173 If you say yes here you get support for the 174 Dallas/Maxim DS1672 timekeeping chip. 175 176 This driver can also be built as a module. If so, the module 177 will be called rtc-ds1672. 178 179config RTC_DRV_DS1742 180 tristate "Dallas DS1742/1743" 181 depends on RTC_CLASS 182 help 183 If you say yes here you get support for the 184 Dallas DS1742/1743 timekeeping chip. 185 186 This driver can also be built as a module. If so, the module 187 will be called rtc-ds1742. 188 189config RTC_DRV_OMAP 190 tristate "TI OMAP1" 191 depends on RTC_CLASS && ( \ 192 ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 ) 193 help 194 Say "yes" here to support the real time clock on TI OMAP1 chips. 195 This driver can also be built as a module called rtc-omap. 196 197config RTC_DRV_PCF8563 198 tristate "Philips PCF8563/Epson RTC8564" 199 depends on RTC_CLASS && I2C 200 help 201 If you say yes here you get support for the 202 Philips PCF8563 RTC chip. The Epson RTC8564 203 should work as well. 204 205 This driver can also be built as a module. If so, the module 206 will be called rtc-pcf8563. 207 208config RTC_DRV_PCF8583 209 tristate "Philips PCF8583" 210 depends on RTC_CLASS && I2C 211 help 212 If you say yes here you get support for the 213 Philips PCF8583 RTC chip. 214 215 This driver can also be built as a module. If so, the module 216 will be called rtc-pcf8583. 217 218config RTC_DRV_RS5C348 219 tristate "Ricoh RS5C348A/B" 220 depends on RTC_CLASS && SPI 221 help 222 If you say yes here you get support for the 223 Ricoh RS5C348A and RS5C348B RTC chips. 224 225 This driver can also be built as a module. If so, the module 226 will be called rtc-rs5c348. 227 228config RTC_DRV_RS5C372 229 tristate "Ricoh RS5C372A/B" 230 depends on RTC_CLASS && I2C 231 help 232 If you say yes here you get support for the 233 Ricoh RS5C372A and RS5C372B RTC chips. 234 235 This driver can also be built as a module. If so, the module 236 will be called rtc-rs5c372. 237 238config RTC_DRV_S3C 239 tristate "Samsung S3C series SoC RTC" 240 depends on RTC_CLASS && ARCH_S3C2410 241 help 242 RTC (Realtime Clock) driver for the clock inbuilt into the 243 Samsung S3C24XX series of SoCs. This can provide periodic 244 interrupt rates from 1Hz to 64Hz for user programs, and 245 wakeup from Alarm. 246 247 The driver currently supports the common features on all the 248 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 249 and S3C2442. 250 251 This driver can also be build as a module. If so, the module 252 will be called rtc-s3c. 253 254config RTC_DRV_M48T86 255 tristate "ST M48T86/Dallas DS12887" 256 depends on RTC_CLASS 257 help 258 If you say Y here you will get support for the 259 ST M48T86 and Dallas DS12887 RTC chips. 260 261 This driver can also be built as a module. If so, the module 262 will be called rtc-m48t86. 263 264config RTC_DRV_EP93XX 265 tristate "Cirrus Logic EP93XX" 266 depends on RTC_CLASS && ARCH_EP93XX 267 help 268 If you say yes here you get support for the 269 RTC embedded in the Cirrus Logic EP93XX processors. 270 271 This driver can also be built as a module. If so, the module 272 will be called rtc-ep93xx. 273 274config RTC_DRV_SA1100 275 tristate "SA11x0/PXA2xx" 276 depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA) 277 help 278 If you say Y here you will get access to the real time clock 279 built into your SA11x0 or PXA2xx CPU. 280 281 To compile this driver as a module, choose M here: the 282 module will be called rtc-sa1100. 283 284config RTC_DRV_SH 285 tristate "SuperH On-Chip RTC" 286 depends on RTC_CLASS && SUPERH 287 help 288 Say Y here to enable support for the on-chip RTC found in 289 most SuperH processors. 290 291 To compile this driver as a module, choose M here: the 292 module will be called rtc-sh. 293 294config RTC_DRV_VR41XX 295 tristate "NEC VR41XX" 296 depends on RTC_CLASS && CPU_VR41XX 297 help 298 If you say Y here you will get access to the real time clock 299 built into your NEC VR41XX CPU. 300 301 To compile this driver as a module, choose M here: the 302 module will be called rtc-vr41xx. 303 304config RTC_DRV_PL031 305 tristate "ARM AMBA PL031 RTC" 306 depends on RTC_CLASS && ARM_AMBA 307 help 308 If you say Y here you will get access to ARM AMBA 309 PrimeCell PL031 UART found on certain ARM SOCs. 310 311 To compile this driver as a module, choose M here: the 312 module will be called rtc-pl031. 313 314config RTC_DRV_AT91RM9200 315 tristate "AT91RM9200" 316 depends on RTC_CLASS && ARCH_AT91RM9200 317 help 318 Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock). 319 320config RTC_DRV_TEST 321 tristate "Test driver/device" 322 depends on RTC_CLASS 323 help 324 If you say yes here you get support for the 325 RTC test driver. It's a software RTC which can be 326 used to test the RTC subsystem APIs. It gets 327 the time from the system clock. 328 You want this driver only if you are doing development 329 on the RTC subsystem. Please read the source code 330 for further details. 331 332 This driver can also be built as a module. If so, the module 333 will be called rtc-test. 334 335config RTC_DRV_MAX6902 336 tristate "Maxim 6902" 337 depends on RTC_CLASS && SPI 338 help 339 If you say yes here you will get support for the 340 Maxim MAX6902 spi RTC chip. 341 342 This driver can also be built as a module. If so, the module 343 will be called rtc-max6902. 344 345config RTC_DRV_V3020 346 tristate "EM Microelectronic V3020" 347 depends on RTC_CLASS 348 help 349 If you say yes here you will get support for the 350 EM Microelectronic v3020 RTC chip. 351 352 This driver can also be built as a module. If so, the module 353 will be called rtc-v3020. 354 355endmenu 356