| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 1 | \# | 
| Alessandro Zummo | c58411e | 2006-03-27 01:16:34 -0800 | [diff] [blame] | 2 | # RTC class/drivers configuration | 
 | 3 | # | 
 | 4 |  | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 5 | menu "Real Time Clock" | 
 | 6 |  | 
| Alessandro Zummo | c58411e | 2006-03-27 01:16:34 -0800 | [diff] [blame] | 7 | config RTC_LIB | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 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 | 
| Adrian Bunk | 27ae410 | 2006-06-30 18:18:41 +0200 | [diff] [blame] | 18 | 	  probably want to enable one or more of the interfaces below. | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 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 | 
| Pavel Machek | af3ffa6 | 2006-09-29 02:01:14 -0700 | [diff] [blame] | 30 | 	  in order to avoid unnecessary fsck runs. | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 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 |  | 
| David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 40 | config 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 |  | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 47 | comment "RTC interfaces" | 
 | 48 | 	depends on RTC_CLASS | 
 | 49 |  | 
| Alessandro Zummo | c5c3e19 | 2006-03-27 01:16:39 -0800 | [diff] [blame] | 50 | config RTC_INTF_SYSFS | 
 | 51 | 	tristate "sysfs" | 
 | 52 | 	depends on RTC_CLASS && SYSFS | 
 | 53 | 	default RTC_CLASS | 
 | 54 | 	help | 
| David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 55 | 	  Say yes here if you want to use your RTCs using sysfs interfaces, | 
 | 56 | 	  /sys/class/rtc/rtc0 through /sys/.../rtcN. | 
| Alessandro Zummo | c5c3e19 | 2006-03-27 01:16:39 -0800 | [diff] [blame] | 57 |  | 
 | 58 | 	  This driver can also be built as a module. If so, the module | 
 | 59 | 	  will be called rtc-sysfs. | 
 | 60 |  | 
| Alessandro Zummo | 728a294 | 2006-03-27 01:16:40 -0800 | [diff] [blame] | 61 | config RTC_INTF_PROC | 
 | 62 | 	tristate "proc" | 
 | 63 | 	depends on RTC_CLASS && PROC_FS | 
 | 64 | 	default RTC_CLASS | 
 | 65 | 	help | 
| David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 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. | 
| Alessandro Zummo | 728a294 | 2006-03-27 01:16:40 -0800 | [diff] [blame] | 69 |  | 
 | 70 | 	  This driver can also be built as a module. If so, the module | 
 | 71 | 	  will be called rtc-proc. | 
 | 72 |  | 
| Alessandro Zummo | e824290 | 2006-03-27 01:16:41 -0800 | [diff] [blame] | 73 | config RTC_INTF_DEV | 
 | 74 | 	tristate "dev" | 
 | 75 | 	depends on RTC_CLASS | 
 | 76 | 	default RTC_CLASS | 
 | 77 | 	help | 
| David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 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. | 
| Alessandro Zummo | e824290 | 2006-03-27 01:16:41 -0800 | [diff] [blame] | 83 |  | 
 | 84 | 	  This driver can also be built as a module. If so, the module | 
 | 85 | 	  will be called rtc-dev. | 
 | 86 |  | 
| Atsushi Nemoto | 655066c | 2006-06-25 05:48:17 -0700 | [diff] [blame] | 87 | config 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 | 
| David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 92 | 	  driver does not expose RTC_UIE ioctls.  Those requests generate | 
 | 93 | 	  once-per-second update interrupts, used for synchronization. | 
| Atsushi Nemoto | 655066c | 2006-06-25 05:48:17 -0700 | [diff] [blame] | 94 |  | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 95 | comment "RTC drivers" | 
 | 96 | 	depends on RTC_CLASS | 
 | 97 |  | 
| Alessandro Zummo | 1fec7c6 | 2006-03-27 01:16:42 -0800 | [diff] [blame] | 98 | config 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 |  | 
| David Brownell | 1abb0dc | 2006-06-25 05:48:17 -0700 | [diff] [blame] | 108 | config 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 |  | 
| Atsushi Nemoto | 9bf5b4f | 2006-06-25 05:48:28 -0700 | [diff] [blame] | 126 | config 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 |  | 
| Herbert Valerio Riedel | 7e56a7d | 2006-07-14 00:24:11 -0700 | [diff] [blame] | 136 | config 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 |  | 
| Alessandro Zummo | edf1aaa | 2006-03-27 01:16:43 -0800 | [diff] [blame] | 146 | config 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 |  | 
| Atsushi Nemoto | 5ec3e4b | 2006-06-25 05:48:29 -0700 | [diff] [blame] | 156 | config 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 |  | 
| David Brownell | db68b18 | 2006-12-06 20:38:36 -0800 | [diff] [blame^] | 166 | config RTC_DRV_OMAP | 
 | 167 | 	tristate "TI OMAP1" | 
 | 168 | 	depends on RTC_CLASS && ( \ | 
 | 169 | 		ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 ) | 
 | 170 | 	help | 
 | 171 | 	  Say "yes" here to support the real time clock on TI OMAP1 chips. | 
 | 172 | 	  This driver can also be built as a module called rtc-omap. | 
 | 173 |  | 
| Alessandro Zummo | b5a82d6 | 2006-03-27 01:16:44 -0800 | [diff] [blame] | 174 | config RTC_DRV_PCF8563 | 
 | 175 | 	tristate "Philips PCF8563/Epson RTC8564" | 
 | 176 | 	depends on RTC_CLASS && I2C | 
 | 177 | 	help | 
 | 178 | 	  If you say yes here you get support for the | 
 | 179 | 	  Philips PCF8563 RTC chip. The Epson RTC8564 | 
 | 180 | 	  should work as well. | 
 | 181 |  | 
 | 182 | 	  This driver can also be built as a module. If so, the module | 
 | 183 | 	  will be called rtc-pcf8563. | 
 | 184 |  | 
| G. Liakhovetski | 9c0c570 | 2006-06-25 05:48:18 -0700 | [diff] [blame] | 185 | config RTC_DRV_PCF8583 | 
 | 186 | 	tristate "Philips PCF8583" | 
 | 187 | 	depends on RTC_CLASS && I2C | 
 | 188 | 	help | 
 | 189 | 	  If you say yes here you get support for the | 
 | 190 | 	  Philips PCF8583 RTC chip. | 
 | 191 |  | 
 | 192 | 	  This driver can also be built as a module. If so, the module | 
 | 193 | 	  will be called rtc-pcf8583. | 
 | 194 |  | 
| Atsushi Nemoto | e0ac476 | 2006-06-28 04:26:47 -0700 | [diff] [blame] | 195 | config RTC_DRV_RS5C348 | 
 | 196 | 	tristate "Ricoh RS5C348A/B" | 
 | 197 | 	depends on RTC_CLASS && SPI | 
 | 198 | 	help | 
 | 199 | 	  If you say yes here you get support for the | 
 | 200 | 	  Ricoh RS5C348A and RS5C348B RTC chips. | 
 | 201 |  | 
 | 202 | 	  This driver can also be built as a module. If so, the module | 
 | 203 | 	  will be called rtc-rs5c348. | 
 | 204 |  | 
| Alessandro Zummo | 7520b94 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 205 | config RTC_DRV_RS5C372 | 
 | 206 | 	tristate "Ricoh RS5C372A/B" | 
 | 207 | 	depends on RTC_CLASS && I2C | 
 | 208 | 	help | 
 | 209 | 	  If you say yes here you get support for the | 
 | 210 | 	  Ricoh RS5C372A and RS5C372B RTC chips. | 
 | 211 |  | 
 | 212 | 	  This driver can also be built as a module. If so, the module | 
 | 213 | 	  will be called rtc-rs5c372. | 
 | 214 |  | 
| Ben Dooks | 1add678 | 2006-07-01 04:36:26 -0700 | [diff] [blame] | 215 | config RTC_DRV_S3C | 
 | 216 | 	tristate "Samsung S3C series SoC RTC" | 
 | 217 | 	depends on RTC_CLASS && ARCH_S3C2410 | 
 | 218 | 	help | 
 | 219 | 	  RTC (Realtime Clock) driver for the clock inbuilt into the | 
 | 220 | 	  Samsung S3C24XX series of SoCs. This can provide periodic | 
 | 221 | 	  interrupt rates from 1Hz to 64Hz for user programs, and | 
 | 222 | 	  wakeup from Alarm. | 
 | 223 |  | 
 | 224 | 	  The driver currently supports the common features on all the | 
 | 225 | 	  S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 | 
 | 226 | 	  and S3C2442. | 
 | 227 |  | 
 | 228 | 	  This driver can also be build as a module. If so, the module | 
 | 229 | 	  will be called rtc-s3c. | 
 | 230 |  | 
| Alessandro Zummo | 1d98af8 | 2006-03-27 01:16:47 -0800 | [diff] [blame] | 231 | config RTC_DRV_M48T86 | 
 | 232 | 	tristate "ST M48T86/Dallas DS12887" | 
 | 233 | 	depends on RTC_CLASS | 
 | 234 | 	help | 
 | 235 | 	  If you say Y here you will get support for the | 
 | 236 | 	  ST M48T86 and Dallas DS12887 RTC chips. | 
 | 237 |  | 
 | 238 | 	  This driver can also be built as a module. If so, the module | 
 | 239 | 	  will be called rtc-m48t86. | 
 | 240 |  | 
| Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 241 | config RTC_DRV_EP93XX | 
 | 242 | 	tristate "Cirrus Logic EP93XX" | 
 | 243 | 	depends on RTC_CLASS && ARCH_EP93XX | 
 | 244 | 	help | 
 | 245 | 	  If you say yes here you get support for the | 
 | 246 | 	  RTC embedded in the Cirrus Logic EP93XX processors. | 
 | 247 |  | 
 | 248 | 	  This driver can also be built as a module. If so, the module | 
 | 249 | 	  will be called rtc-ep93xx. | 
 | 250 |  | 
| Richard Purdie | e842f1c | 2006-03-27 01:16:46 -0800 | [diff] [blame] | 251 | config RTC_DRV_SA1100 | 
 | 252 | 	tristate "SA11x0/PXA2xx" | 
 | 253 | 	depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA) | 
 | 254 | 	help | 
 | 255 | 	  If you say Y here you will get access to the real time clock | 
 | 256 | 	  built into your SA11x0 or PXA2xx CPU. | 
 | 257 |  | 
 | 258 | 	  To compile this driver as a module, choose M here: the | 
 | 259 | 	  module will be called rtc-sa1100. | 
| Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 260 |  | 
| Paul Mundt | 317a610 | 2006-09-27 17:13:19 +0900 | [diff] [blame] | 261 | config RTC_DRV_SH | 
 | 262 | 	tristate "SuperH On-Chip RTC" | 
 | 263 | 	depends on RTC_CLASS && SUPERH | 
 | 264 | 	help | 
 | 265 | 	  Say Y here to enable support for the on-chip RTC found in | 
 | 266 | 	  most SuperH processors. | 
 | 267 |  | 
 | 268 |  	  To compile this driver as a module, choose M here: the | 
 | 269 | 	  module will be called rtc-sh. | 
 | 270 |  | 
| Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 271 | config RTC_DRV_VR41XX | 
| Alessandro Zummo | 3e16f6a | 2006-04-10 22:54:48 -0700 | [diff] [blame] | 272 | 	tristate "NEC VR41XX" | 
| Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 273 | 	depends on RTC_CLASS && CPU_VR41XX | 
| Alessandro Zummo | 3e16f6a | 2006-04-10 22:54:48 -0700 | [diff] [blame] | 274 | 	help | 
 | 275 | 	  If you say Y here you will get access to the real time clock | 
 | 276 | 	  built into your NEC VR41XX CPU. | 
 | 277 |  | 
 | 278 | 	  To compile this driver as a module, choose M here: the | 
 | 279 | 	  module will be called rtc-vr41xx. | 
| Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 280 |  | 
| Deepak Saxena | 8ae6e16 | 2006-06-25 05:47:38 -0700 | [diff] [blame] | 281 | config RTC_DRV_PL031 | 
 | 282 | 	tristate "ARM AMBA PL031 RTC" | 
 | 283 | 	depends on RTC_CLASS && ARM_AMBA | 
 | 284 | 	help | 
 | 285 | 	  If you say Y here you will get access to ARM AMBA | 
 | 286 | 	  PrimeCell PL031 UART found on certain ARM SOCs. | 
 | 287 |  | 
 | 288 | 	  To compile this driver as a module, choose M here: the | 
 | 289 | 	  module will be called rtc-pl031. | 
 | 290 |  | 
| Andrew Victor | 788b1fc | 2006-06-25 05:48:27 -0700 | [diff] [blame] | 291 | config RTC_DRV_AT91 | 
 | 292 | 	tristate "AT91RM9200" | 
 | 293 | 	depends on RTC_CLASS && ARCH_AT91RM9200 | 
 | 294 | 	help | 
 | 295 | 	  Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock). | 
 | 296 |  | 
| Alessandro Zummo | a95579c | 2006-03-27 01:16:42 -0800 | [diff] [blame] | 297 | config RTC_DRV_TEST | 
 | 298 | 	tristate "Test driver/device" | 
 | 299 | 	depends on RTC_CLASS | 
 | 300 | 	help | 
 | 301 | 	  If you say yes here you get support for the | 
 | 302 | 	  RTC test driver. It's a software RTC which can be | 
 | 303 | 	  used to test the RTC subsystem APIs. It gets | 
 | 304 | 	  the time from the system clock. | 
 | 305 | 	  You want this driver only if you are doing development | 
 | 306 | 	  on the RTC subsystem. Please read the source code | 
 | 307 | 	  for further details. | 
 | 308 |  | 
 | 309 | 	  This driver can also be built as a module. If so, the module | 
 | 310 | 	  will be called rtc-test. | 
 | 311 |  | 
| Raphael Assenat | 8e12ecc | 2006-06-25 05:48:23 -0700 | [diff] [blame] | 312 | config RTC_DRV_MAX6902 | 
 | 313 | 	tristate "Maxim 6902" | 
 | 314 | 	depends on RTC_CLASS && SPI | 
 | 315 | 	help | 
 | 316 | 	  If you say yes here you will get support for the | 
 | 317 | 	  Maxim MAX6902 spi RTC chip. | 
 | 318 |  | 
 | 319 | 	  This driver can also be built as a module. If so, the module | 
 | 320 | 	  will be called rtc-max6902. | 
 | 321 |  | 
| Raphael Assenat | 362600f | 2006-06-25 05:48:24 -0700 | [diff] [blame] | 322 | config RTC_DRV_V3020 | 
 | 323 | 	tristate "EM Microelectronic V3020" | 
 | 324 | 	depends on RTC_CLASS | 
 | 325 | 	help | 
 | 326 | 	  If you say yes here you will get support for the | 
 | 327 | 	  EM Microelectronic v3020 RTC chip. | 
 | 328 |  | 
 | 329 | 	  This driver can also be built as a module. If so, the module | 
 | 330 | 	  will be called rtc-v3020. | 
 | 331 |  | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 332 | endmenu |