| 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 | 
|  | 18 | probably want to enable one of 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 |  | 
|  | 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 |  | 
| Alessandro Zummo | c5c3e19 | 2006-03-27 01:16:39 -0800 | [diff] [blame] | 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 |  | 
| Alessandro Zummo | 728a294 | 2006-03-27 01:16:40 -0800 | [diff] [blame] | 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 |  | 
| Alessandro Zummo | e824290 | 2006-03-27 01:16:41 -0800 | [diff] [blame] | 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 |  | 
| Atsushi Nemoto | 655066c | 2006-06-25 05:48:17 -0700 | [diff] [blame] | 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 |  | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 83 | comment "RTC drivers" | 
|  | 84 | depends on RTC_CLASS | 
|  | 85 |  | 
| Alessandro Zummo | 1fec7c6 | 2006-03-27 01:16:42 -0800 | [diff] [blame] | 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 |  | 
| David Brownell | 1abb0dc | 2006-06-25 05:48:17 -0700 | [diff] [blame] | 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 |  | 
| Atsushi Nemoto | 9bf5b4f | 2006-06-25 05:48:28 -0700 | [diff] [blame] | 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 |  | 
| Alessandro Zummo | edf1aaa | 2006-03-27 01:16:43 -0800 | [diff] [blame] | 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 |  | 
| Atsushi Nemoto | 5ec3e4b | 2006-06-25 05:48:29 -0700 | [diff] [blame] | 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 |  | 
| Alessandro Zummo | b5a82d6 | 2006-03-27 01:16:44 -0800 | [diff] [blame] | 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 |  | 
| G. Liakhovetski | 9c0c570 | 2006-06-25 05:48:18 -0700 | [diff] [blame] | 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 |  | 
| Atsushi Nemoto | e0ac476 | 2006-06-28 04:26:47 -0700 | [diff] [blame^] | 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 |  | 
| Alessandro Zummo | 7520b94 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 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 |  | 
| Alessandro Zummo | 1d98af8 | 2006-03-27 01:16:47 -0800 | [diff] [blame] | 185 | config RTC_DRV_M48T86 | 
|  | 186 | tristate "ST M48T86/Dallas DS12887" | 
|  | 187 | depends on RTC_CLASS | 
|  | 188 | help | 
|  | 189 | If you say Y here you will get support for the | 
|  | 190 | ST M48T86 and Dallas DS12887 RTC chips. | 
|  | 191 |  | 
|  | 192 | This driver can also be built as a module. If so, the module | 
|  | 193 | will be called rtc-m48t86. | 
|  | 194 |  | 
| Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 195 | config RTC_DRV_EP93XX | 
|  | 196 | tristate "Cirrus Logic EP93XX" | 
|  | 197 | depends on RTC_CLASS && ARCH_EP93XX | 
|  | 198 | help | 
|  | 199 | If you say yes here you get support for the | 
|  | 200 | RTC embedded in the Cirrus Logic EP93XX processors. | 
|  | 201 |  | 
|  | 202 | This driver can also be built as a module. If so, the module | 
|  | 203 | will be called rtc-ep93xx. | 
|  | 204 |  | 
| Richard Purdie | e842f1c | 2006-03-27 01:16:46 -0800 | [diff] [blame] | 205 | config RTC_DRV_SA1100 | 
|  | 206 | tristate "SA11x0/PXA2xx" | 
|  | 207 | depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA) | 
|  | 208 | help | 
|  | 209 | If you say Y here you will get access to the real time clock | 
|  | 210 | built into your SA11x0 or PXA2xx CPU. | 
|  | 211 |  | 
|  | 212 | To compile this driver as a module, choose M here: the | 
|  | 213 | module will be called rtc-sa1100. | 
| Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 214 |  | 
| Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 215 | config RTC_DRV_VR41XX | 
| Alessandro Zummo | 3e16f6a | 2006-04-10 22:54:48 -0700 | [diff] [blame] | 216 | tristate "NEC VR41XX" | 
| Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 217 | depends on RTC_CLASS && CPU_VR41XX | 
| Alessandro Zummo | 3e16f6a | 2006-04-10 22:54:48 -0700 | [diff] [blame] | 218 | help | 
|  | 219 | If you say Y here you will get access to the real time clock | 
|  | 220 | built into your NEC VR41XX CPU. | 
|  | 221 |  | 
|  | 222 | To compile this driver as a module, choose M here: the | 
|  | 223 | module will be called rtc-vr41xx. | 
| Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 224 |  | 
| Deepak Saxena | 8ae6e16 | 2006-06-25 05:47:38 -0700 | [diff] [blame] | 225 | config RTC_DRV_PL031 | 
|  | 226 | tristate "ARM AMBA PL031 RTC" | 
|  | 227 | depends on RTC_CLASS && ARM_AMBA | 
|  | 228 | help | 
|  | 229 | If you say Y here you will get access to ARM AMBA | 
|  | 230 | PrimeCell PL031 UART found on certain ARM SOCs. | 
|  | 231 |  | 
|  | 232 | To compile this driver as a module, choose M here: the | 
|  | 233 | module will be called rtc-pl031. | 
|  | 234 |  | 
| Andrew Victor | 788b1fc | 2006-06-25 05:48:27 -0700 | [diff] [blame] | 235 | config RTC_DRV_AT91 | 
|  | 236 | tristate "AT91RM9200" | 
|  | 237 | depends on RTC_CLASS && ARCH_AT91RM9200 | 
|  | 238 | help | 
|  | 239 | Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock). | 
|  | 240 |  | 
| Alessandro Zummo | a95579c | 2006-03-27 01:16:42 -0800 | [diff] [blame] | 241 | config RTC_DRV_TEST | 
|  | 242 | tristate "Test driver/device" | 
|  | 243 | depends on RTC_CLASS | 
|  | 244 | help | 
|  | 245 | If you say yes here you get support for the | 
|  | 246 | RTC test driver. It's a software RTC which can be | 
|  | 247 | used to test the RTC subsystem APIs. It gets | 
|  | 248 | the time from the system clock. | 
|  | 249 | You want this driver only if you are doing development | 
|  | 250 | on the RTC subsystem. Please read the source code | 
|  | 251 | for further details. | 
|  | 252 |  | 
|  | 253 | This driver can also be built as a module. If so, the module | 
|  | 254 | will be called rtc-test. | 
|  | 255 |  | 
| Raphael Assenat | 8e12ecc | 2006-06-25 05:48:23 -0700 | [diff] [blame] | 256 | config RTC_DRV_MAX6902 | 
|  | 257 | tristate "Maxim 6902" | 
|  | 258 | depends on RTC_CLASS && SPI | 
|  | 259 | help | 
|  | 260 | If you say yes here you will get support for the | 
|  | 261 | Maxim MAX6902 spi RTC chip. | 
|  | 262 |  | 
|  | 263 | This driver can also be built as a module. If so, the module | 
|  | 264 | will be called rtc-max6902. | 
|  | 265 |  | 
| Raphael Assenat | 362600f | 2006-06-25 05:48:24 -0700 | [diff] [blame] | 266 | config RTC_DRV_V3020 | 
|  | 267 | tristate "EM Microelectronic V3020" | 
|  | 268 | depends on RTC_CLASS | 
|  | 269 | help | 
|  | 270 | If you say yes here you will get support for the | 
|  | 271 | EM Microelectronic v3020 RTC chip. | 
|  | 272 |  | 
|  | 273 | This driver can also be built as a module. If so, the module | 
|  | 274 | will be called rtc-v3020. | 
|  | 275 |  | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 276 | endmenu |