1# 2# RTC class/drivers configuration 3# 4 5config RTC_LIB 6 tristate 7 8menuconfig RTC_CLASS 9 tristate "Real Time Clock" 10 default n 11 depends on !S390 12 select RTC_LIB 13 help 14 Generic RTC class support. If you say yes here, you will 15 be allowed to plug one or more RTCs to your system. You will 16 probably want to enable one or more of the interfaces below. 17 18 This driver can also be built as a module. If so, the module 19 will be called rtc-class. 20 21if RTC_CLASS 22 23config RTC_HCTOSYS 24 bool "Set system time from RTC on startup and resume" 25 depends on RTC_CLASS = y 26 default y 27 help 28 If you say yes here, the system time (wall clock) will be set using 29 the value read from a specified RTC device. This is useful to avoid 30 unnecessary fsck runs at boot time, and to network better. 31 32config RTC_HCTOSYS_DEVICE 33 string "RTC used to set the system time" 34 depends on RTC_HCTOSYS = y 35 default "rtc0" 36 help 37 The RTC device that will be used to (re)initialize the system 38 clock, usually rtc0. Initialization is done when the system 39 starts up, and when it resumes from a low power state. This 40 device should record time in UTC, since the kernel won't do 41 timezone correction. 42 43 The driver for this RTC device must be loaded before late_initcall 44 functions run, so it must usually be statically linked. 45 46 This clock should be battery-backed, so that it reads the correct 47 time when the system boots from a power-off state. Otherwise, your 48 system will need an external clock source (like an NTP server). 49 50 If the clock you specify here is not battery backed, it may still 51 be useful to reinitialize system time when resuming from system 52 sleep states. Do not specify an RTC here unless it stays powered 53 during all this system's supported sleep states. 54 55config RTC_DEBUG 56 bool "RTC debug support" 57 depends on RTC_CLASS = y 58 help 59 Say yes here to enable debugging support in the RTC framework 60 and individual RTC drivers. 61 62comment "RTC interfaces" 63 64config RTC_INTF_SYSFS 65 boolean "/sys/class/rtc/rtcN (sysfs)" 66 depends on SYSFS 67 default RTC_CLASS 68 help 69 Say yes here if you want to use your RTCs using sysfs interfaces, 70 /sys/class/rtc/rtc0 through /sys/.../rtcN. 71 72 This driver can also be built as a module. If so, the module 73 will be called rtc-sysfs. 74 75config RTC_INTF_PROC 76 boolean "/proc/driver/rtc (procfs for rtc0)" 77 depends on PROC_FS 78 default RTC_CLASS 79 help 80 Say yes here if you want to use your first RTC through the proc 81 interface, /proc/driver/rtc. Other RTCs will not be available 82 through that API. 83 84 This driver can also be built as a module. If so, the module 85 will be called rtc-proc. 86 87config RTC_INTF_DEV 88 boolean "/dev/rtcN (character devices)" 89 default RTC_CLASS 90 help 91 Say yes here if you want to use your RTCs using the /dev 92 interfaces, which "udev" sets up as /dev/rtc0 through 93 /dev/rtcN. You may want to set up a symbolic link so one 94 of these can be accessed as /dev/rtc, which is a name 95 expected by "hwclock" and some other programs. 96 97 This driver can also be built as a module. If so, the module 98 will be called rtc-dev. 99 100config RTC_INTF_DEV_UIE_EMUL 101 bool "RTC UIE emulation on dev interface" 102 depends on RTC_INTF_DEV 103 help 104 Provides an emulation for RTC_UIE if the underlying rtc chip 105 driver does not expose RTC_UIE ioctls. Those requests generate 106 once-per-second update interrupts, used for synchronization. 107 108config RTC_DRV_TEST 109 tristate "Test driver/device" 110 help 111 If you say yes here you get support for the 112 RTC test driver. It's a software RTC which can be 113 used to test the RTC subsystem APIs. It gets 114 the time from the system clock. 115 You want this driver only if you are doing development 116 on the RTC subsystem. Please read the source code 117 for further details. 118 119 This driver can also be built as a module. If so, the module 120 will be called rtc-test. 121 122comment "I2C RTC drivers" 123 depends on I2C 124 125if I2C 126 127config RTC_DRV_DS1307 128 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00" 129 help 130 If you say yes here you get support for various compatible RTC 131 chips (often with battery backup) connected with I2C. This driver 132 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00, 133 and probably other chips. In some cases the RTC must already 134 have been initialized (by manufacturing or a bootloader). 135 136 The first seven registers on these chips hold an RTC, and other 137 registers may add features such as NVRAM, a trickle charger for 138 the RTC/NVRAM backup power, and alarms. NVRAM is visible in 139 sysfs, but other chip features may not be available. 140 141 This driver can also be built as a module. If so, the module 142 will be called rtc-ds1307. 143 144config RTC_DRV_DS1374 145 tristate "Maxim/Dallas Semiconductor DS1374 Real Time Clock" 146 depends on RTC_CLASS && I2C 147 help 148 If you say yes here you get support for Dallas Semiconductor 149 DS1374 real-time clock chips. If an interrupt is associated 150 with the device, the alarm functionality is supported. 151 152 This driver can also be built as a module. If so, the module 153 will be called rtc-ds1374. 154 155config RTC_DRV_DS1672 156 tristate "Dallas/Maxim DS1672" 157 help 158 If you say yes here you get support for the 159 Dallas/Maxim DS1672 timekeeping chip. 160 161 This driver can also be built as a module. If so, the module 162 will be called rtc-ds1672. 163 164config RTC_DRV_MAX6900 165 tristate "Maxim 6900" 166 help 167 If you say yes here you will get support for the 168 Maxim MAX6900 I2C RTC chip. 169 170 This driver can also be built as a module. If so, the module 171 will be called rtc-max6900. 172 173config RTC_DRV_RS5C372 174 tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A" 175 help 176 If you say yes here you get support for the 177 Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. 178 179 This driver can also be built as a module. If so, the module 180 will be called rtc-rs5c372. 181 182config RTC_DRV_ISL1208 183 tristate "Intersil 1208" 184 help 185 If you say yes here you get support for the 186 Intersil 1208 RTC chip. 187 188 This driver can also be built as a module. If so, the module 189 will be called rtc-isl1208. 190 191config RTC_DRV_X1205 192 tristate "Xicor/Intersil X1205" 193 help 194 If you say yes here you get support for the 195 Xicor/Intersil X1205 RTC chip. 196 197 This driver can also be built as a module. If so, the module 198 will be called rtc-x1205. 199 200config RTC_DRV_PCF8563 201 tristate "Philips PCF8563/Epson RTC8564" 202 help 203 If you say yes here you get support for the 204 Philips PCF8563 RTC chip. The Epson RTC8564 205 should work as well. 206 207 This driver can also be built as a module. If so, the module 208 will be called rtc-pcf8563. 209 210config RTC_DRV_PCF8583 211 tristate "Philips PCF8583" 212 help 213 If you say yes here you get support for the Philips PCF8583 214 RTC chip found on Acorn RiscPCs. This driver supports the 215 platform specific method of retrieving the current year from 216 the RTC's SRAM. It will work on other platforms with the same 217 chip, but the year will probably have to be tweaked. 218 219 This driver can also be built as a module. If so, the module 220 will be called rtc-pcf8583. 221 222config RTC_DRV_M41T80 223 tristate "ST M41T80 series RTC" 224 help 225 If you say Y here you will get support for the 226 ST M41T80 RTC chips series. Currently following chips are 227 supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85 228 and M41ST87. 229 230 This driver can also be built as a module. If so, the module 231 will be called rtc-m41t80. 232 233config RTC_DRV_M41T80_WDT 234 bool "ST M41T80 series RTC watchdog timer" 235 depends on RTC_DRV_M41T80 236 help 237 If you say Y here you will get support for the 238 watchdog timer in ST M41T80 RTC chips series. 239 240config RTC_DRV_TWL92330 241 boolean "TI TWL92330/Menelaus" 242 depends on MENELAUS 243 help 244 If you say yes here you get support for the RTC on the 245 TWL92330 "Menelaus" power management chip, used with OMAP2 246 platforms. The support is integrated with the rest of 247 the Menelaus driver; it's not separate module. 248 249endif # I2C 250 251comment "SPI RTC drivers" 252 253if SPI_MASTER 254 255config RTC_DRV_RS5C348 256 tristate "Ricoh RS5C348A/B" 257 help 258 If you say yes here you get support for the 259 Ricoh RS5C348A and RS5C348B RTC chips. 260 261 This driver can also be built as a module. If so, the module 262 will be called rtc-rs5c348. 263 264config RTC_DRV_MAX6902 265 tristate "Maxim 6902" 266 help 267 If you say yes here you will get support for the 268 Maxim MAX6902 SPI RTC chip. 269 270 This driver can also be built as a module. If so, the module 271 will be called rtc-max6902. 272 273endif # SPI_MASTER 274 275comment "Platform RTC drivers" 276 277# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> 278# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a 279# global rtc_lock ... it's not yet just another platform_device. 280 281config RTC_DRV_CMOS 282 tristate "PC-style 'CMOS'" 283 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS 284 help 285 Say "yes" here to get direct support for the real time clock 286 found in every PC or ACPI-based system, and some other boards. 287 Specifically the original MC146818, compatibles like those in 288 PC south bridges, the DS12887 or M48T86, some multifunction 289 or LPC bus chips, and so on. 290 291 Your system will need to define the platform device used by 292 this driver, otherwise it won't be accessible. This means 293 you can safely enable this driver if you don't know whether 294 or not your board has this kind of hardware. 295 296 This driver can also be built as a module. If so, the module 297 will be called rtc-cmos. 298 299config RTC_DRV_DS1216 300 tristate "Dallas DS1216" 301 depends on SNI_RM 302 help 303 If you say yes here you get support for the Dallas DS1216 RTC chips. 304 305config RTC_DRV_DS1553 306 tristate "Dallas DS1553" 307 help 308 If you say yes here you get support for the 309 Dallas DS1553 timekeeping chip. 310 311 This driver can also be built as a module. If so, the module 312 will be called rtc-ds1553. 313 314config RTC_DRV_STK17TA8 315 tristate "Simtek STK17TA8" 316 depends on RTC_CLASS 317 help 318 If you say yes here you get support for the 319 Simtek STK17TA8 timekeeping chip. 320 321 This driver can also be built as a module. If so, the module 322 will be called rtc-stk17ta8. 323 324config RTC_DRV_DS1742 325 tristate "Dallas DS1742/1743" 326 help 327 If you say yes here you get support for the 328 Dallas DS1742/1743 timekeeping chip. 329 330 This driver can also be built as a module. If so, the module 331 will be called rtc-ds1742. 332 333config RTC_DRV_M48T86 334 tristate "ST M48T86/Dallas DS12887" 335 help 336 If you say Y here you will get support for the 337 ST M48T86 and Dallas DS12887 RTC chips. 338 339 This driver can also be built as a module. If so, the module 340 will be called rtc-m48t86. 341 342config RTC_DRV_M48T59 343 tristate "ST M48T59" 344 help 345 If you say Y here you will get support for the 346 ST M48T59 RTC chip. 347 348 This driver can also be built as a module, if so, the module 349 will be called "rtc-m48t59". 350 351config RTC_DRV_V3020 352 tristate "EM Microelectronic V3020" 353 help 354 If you say yes here you will get support for the 355 EM Microelectronic v3020 RTC chip. 356 357 This driver can also be built as a module. If so, the module 358 will be called rtc-v3020. 359 360comment "on-CPU RTC drivers" 361 362config RTC_DRV_OMAP 363 tristate "TI OMAP1" 364 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 365 help 366 Say "yes" here to support the real time clock on TI OMAP1 chips. 367 This driver can also be built as a module called rtc-omap. 368 369config RTC_DRV_S3C 370 tristate "Samsung S3C series SoC RTC" 371 depends on ARCH_S3C2410 372 help 373 RTC (Realtime Clock) driver for the clock inbuilt into the 374 Samsung S3C24XX series of SoCs. This can provide periodic 375 interrupt rates from 1Hz to 64Hz for user programs, and 376 wakeup from Alarm. 377 378 The driver currently supports the common features on all the 379 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 380 and S3C2442. 381 382 This driver can also be build as a module. If so, the module 383 will be called rtc-s3c. 384 385config RTC_DRV_EP93XX 386 tristate "Cirrus Logic EP93XX" 387 depends on ARCH_EP93XX 388 help 389 If you say yes here you get support for the 390 RTC embedded in the Cirrus Logic EP93XX processors. 391 392 This driver can also be built as a module. If so, the module 393 will be called rtc-ep93xx. 394 395config RTC_DRV_SA1100 396 tristate "SA11x0/PXA2xx" 397 depends on ARCH_SA1100 || ARCH_PXA 398 help 399 If you say Y here you will get access to the real time clock 400 built into your SA11x0 or PXA2xx CPU. 401 402 To compile this driver as a module, choose M here: the 403 module will be called rtc-sa1100. 404 405config RTC_DRV_SH 406 tristate "SuperH On-Chip RTC" 407 depends on RTC_CLASS && SUPERH 408 help 409 Say Y here to enable support for the on-chip RTC found in 410 most SuperH processors. 411 412 To compile this driver as a module, choose M here: the 413 module will be called rtc-sh. 414 415config RTC_DRV_VR41XX 416 tristate "NEC VR41XX" 417 depends on CPU_VR41XX 418 help 419 If you say Y here you will get access to the real time clock 420 built into your NEC VR41XX CPU. 421 422 To compile this driver as a module, choose M here: the 423 module will be called rtc-vr41xx. 424 425config RTC_DRV_PL031 426 tristate "ARM AMBA PL031 RTC" 427 depends on ARM_AMBA 428 help 429 If you say Y here you will get access to ARM AMBA 430 PrimeCell PL031 RTC found on certain ARM SOCs. 431 432 To compile this driver as a module, choose M here: the 433 module will be called rtc-pl031. 434 435config RTC_DRV_AT32AP700X 436 tristate "AT32AP700X series RTC" 437 depends on PLATFORM_AT32AP 438 help 439 Driver for the internal RTC (Realtime Clock) on Atmel AVR32 440 AT32AP700x family processors. 441 442config RTC_DRV_AT91RM9200 443 tristate "AT91RM9200" 444 depends on ARCH_AT91RM9200 445 help 446 Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock). 447 448config RTC_DRV_BFIN 449 tristate "Blackfin On-Chip RTC" 450 depends on BLACKFIN 451 help 452 If you say yes here you will get support for the 453 Blackfin On-Chip Real Time Clock. 454 455 This driver can also be built as a module. If so, the module 456 will be called rtc-bfin. 457 458config RTC_DRV_RS5C313 459 tristate "Ricoh RS5C313" 460 depends on SH_LANDISK 461 help 462 If you say yes here you get support for the Ricoh RS5C313 RTC chips. 463 464endif # RTC_CLASS 465