| David Brownell | 7be2c7c | 2007-02-10 01:46:02 -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" | 
| Martin Schwidefsky | 9556fb7 | 2007-05-10 15:45:58 +0200 | [diff] [blame] | 6 | 	depends on !S390 | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 7 |  | 
| Alessandro Zummo | c58411e | 2006-03-27 01:16:34 -0800 | [diff] [blame] | 8 | config RTC_LIB | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 9 | 	tristate | 
 | 10 |  | 
 | 11 | config RTC_CLASS | 
 | 12 | 	tristate "RTC class" | 
 | 13 | 	depends on EXPERIMENTAL | 
 | 14 | 	default n | 
 | 15 | 	select RTC_LIB | 
 | 16 | 	help | 
 | 17 | 	  Generic RTC class support. If you say yes here, you will | 
 | 18 |  	  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] | 19 | 	  probably want to enable one or more of the interfaces below. | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 20 |  | 
 | 21 | 	  This driver can also be built as a module. If so, the module | 
 | 22 | 	  will be called rtc-class. | 
 | 23 |  | 
 | 24 | config RTC_HCTOSYS | 
| David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 25 | 	bool "Set system time from RTC on startup and resume" | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 26 | 	depends on RTC_CLASS = y | 
 | 27 | 	default y | 
 | 28 | 	help | 
| David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 29 | 	  If you say yes here, the system time (wall clock) will be set using | 
 | 30 | 	  the value read from a specified RTC device. This is useful to avoid | 
 | 31 | 	  unnecessary fsck runs at boot time, and to network better. | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 32 |  | 
 | 33 | config RTC_HCTOSYS_DEVICE | 
| David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 34 | 	string "RTC used to set the system time" | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 35 | 	depends on RTC_HCTOSYS = y | 
 | 36 | 	default "rtc0" | 
 | 37 | 	help | 
| David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 38 | 	  The RTC device that will be used to (re)initialize the system | 
 | 39 | 	  clock, usually rtc0.  Initialization is done when the system | 
 | 40 | 	  starts up, and when it resumes from a low power state. | 
 | 41 |  | 
 | 42 | 	  This clock should be battery-backed, so that it reads the correct | 
 | 43 | 	  time when the system boots from a power-off state.  Otherwise, your | 
 | 44 | 	  system will need an external clock source (like an NTP server). | 
 | 45 |  | 
 | 46 | 	  If the clock you specify here is not battery backed, it may still | 
 | 47 | 	  be useful to reinitialize system time when resuming from system | 
 | 48 | 	  sleep states.  Do not specify an RTC here unless it stays powered | 
 | 49 | 	  during all this system's supported sleep states. | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 50 |  | 
| David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 51 | config RTC_DEBUG | 
 | 52 | 	bool "RTC debug support" | 
 | 53 | 	depends on RTC_CLASS = y | 
 | 54 | 	help | 
 | 55 | 	  Say yes here to enable debugging support in the RTC framework | 
 | 56 | 	  and individual RTC drivers. | 
 | 57 |  | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 58 | comment "RTC interfaces" | 
 | 59 | 	depends on RTC_CLASS | 
 | 60 |  | 
| Alessandro Zummo | c5c3e19 | 2006-03-27 01:16:39 -0800 | [diff] [blame] | 61 | config RTC_INTF_SYSFS | 
| David Brownell | e40659c | 2007-05-16 22:11:15 -0700 | [diff] [blame] | 62 | 	boolean "/sys/class/rtc/rtcN (sysfs)" | 
| Alessandro Zummo | c5c3e19 | 2006-03-27 01:16:39 -0800 | [diff] [blame] | 63 | 	depends on RTC_CLASS && SYSFS | 
 | 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 RTCs using sysfs interfaces, | 
 | 67 | 	  /sys/class/rtc/rtc0 through /sys/.../rtcN. | 
| Alessandro Zummo | c5c3e19 | 2006-03-27 01:16:39 -0800 | [diff] [blame] | 68 |  | 
 | 69 | 	  This driver can also be built as a module. If so, the module | 
 | 70 | 	  will be called rtc-sysfs. | 
 | 71 |  | 
| Alessandro Zummo | 728a294 | 2006-03-27 01:16:40 -0800 | [diff] [blame] | 72 | config RTC_INTF_PROC | 
| David Brownell | e40659c | 2007-05-16 22:11:15 -0700 | [diff] [blame] | 73 | 	boolean "/proc/driver/rtc (procfs for rtc0)" | 
| Alessandro Zummo | 728a294 | 2006-03-27 01:16:40 -0800 | [diff] [blame] | 74 | 	depends on RTC_CLASS && PROC_FS | 
 | 75 | 	default RTC_CLASS | 
 | 76 | 	help | 
| David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 77 | 	  Say yes here if you want to use your first RTC through the proc | 
 | 78 | 	  interface, /proc/driver/rtc.  Other RTCs will not be available | 
 | 79 | 	  through that API. | 
| Alessandro Zummo | 728a294 | 2006-03-27 01:16:40 -0800 | [diff] [blame] | 80 |  | 
 | 81 | 	  This driver can also be built as a module. If so, the module | 
 | 82 | 	  will be called rtc-proc. | 
 | 83 |  | 
| Alessandro Zummo | e824290 | 2006-03-27 01:16:41 -0800 | [diff] [blame] | 84 | config RTC_INTF_DEV | 
| David Brownell | e40659c | 2007-05-16 22:11:15 -0700 | [diff] [blame] | 85 | 	boolean "/dev/rtcN (character devices)" | 
| Alessandro Zummo | e824290 | 2006-03-27 01:16:41 -0800 | [diff] [blame] | 86 | 	depends on RTC_CLASS | 
 | 87 | 	default RTC_CLASS | 
 | 88 | 	help | 
| David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 89 | 	  Say yes here if you want to use your RTCs using the /dev | 
 | 90 | 	  interfaces, which "udev" sets up as /dev/rtc0 through | 
 | 91 | 	  /dev/rtcN.  You may want to set up a symbolic link so one | 
 | 92 | 	  of these can be accessed as /dev/rtc, which is a name | 
 | 93 | 	  expected by "hwclock" and some other programs. | 
| Alessandro Zummo | e824290 | 2006-03-27 01:16:41 -0800 | [diff] [blame] | 94 |  | 
 | 95 | 	  This driver can also be built as a module. If so, the module | 
 | 96 | 	  will be called rtc-dev. | 
 | 97 |  | 
| Atsushi Nemoto | 655066c | 2006-06-25 05:48:17 -0700 | [diff] [blame] | 98 | config RTC_INTF_DEV_UIE_EMUL | 
 | 99 | 	bool "RTC UIE emulation on dev interface" | 
 | 100 | 	depends on RTC_INTF_DEV | 
 | 101 | 	help | 
| David Sterba | 3dde6ad | 2007-05-09 07:12:20 +0200 | [diff] [blame] | 102 | 	  Provides an emulation for RTC_UIE if the underlying rtc chip | 
| David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 103 | 	  driver does not expose RTC_UIE ioctls.  Those requests generate | 
 | 104 | 	  once-per-second update interrupts, used for synchronization. | 
| Atsushi Nemoto | 655066c | 2006-06-25 05:48:17 -0700 | [diff] [blame] | 105 |  | 
| Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 106 | config RTC_DRV_TEST | 
 | 107 | 	tristate "Test driver/device" | 
 | 108 | 	depends on RTC_CLASS | 
 | 109 | 	help | 
 | 110 | 	  If you say yes here you get support for the | 
 | 111 | 	  RTC test driver. It's a software RTC which can be | 
 | 112 | 	  used to test the RTC subsystem APIs. It gets | 
 | 113 | 	  the time from the system clock. | 
 | 114 | 	  You want this driver only if you are doing development | 
 | 115 | 	  on the RTC subsystem. Please read the source code | 
 | 116 | 	  for further details. | 
 | 117 |  | 
 | 118 | 	  This driver can also be built as a module. If so, the module | 
 | 119 | 	  will be called rtc-test. | 
 | 120 |  | 
 | 121 | comment "I2C RTC drivers" | 
 | 122 | 	depends on RTC_CLASS | 
 | 123 |  | 
 | 124 | config RTC_DRV_DS1307 | 
 | 125 | 	tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00" | 
 | 126 | 	depends on RTC_CLASS && I2C | 
 | 127 | 	help | 
 | 128 | 	  If you say yes here you get support for various compatible RTC | 
 | 129 | 	  chips (often with battery backup) connected with I2C.  This driver | 
 | 130 | 	  should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00, | 
 | 131 | 	  and probably other chips.  In some cases the RTC must already | 
 | 132 | 	  have been initialized (by manufacturing or a bootloader). | 
 | 133 |  | 
 | 134 | 	  The first seven registers on these chips hold an RTC, and other | 
 | 135 | 	  registers may add features such as NVRAM, a trickle charger for | 
 | 136 | 	  the RTC/NVRAM backup power, and alarms.  This driver may not | 
 | 137 | 	  expose all those available chip features. | 
 | 138 |  | 
 | 139 | 	  This driver can also be built as a module. If so, the module | 
 | 140 | 	  will be called rtc-ds1307. | 
 | 141 |  | 
 | 142 | config RTC_DRV_DS1672 | 
 | 143 | 	tristate "Dallas/Maxim DS1672" | 
 | 144 | 	depends on RTC_CLASS && I2C | 
 | 145 | 	help | 
 | 146 | 	  If you say yes here you get support for the | 
 | 147 | 	  Dallas/Maxim DS1672 timekeeping chip. | 
 | 148 |  | 
 | 149 | 	  This driver can also be built as a module. If so, the module | 
 | 150 | 	  will be called rtc-ds1672. | 
 | 151 |  | 
 | 152 | config RTC_DRV_MAX6900 | 
 | 153 | 	tristate "Maxim 6900" | 
 | 154 | 	depends on RTC_CLASS && I2C | 
 | 155 | 	help | 
 | 156 | 	  If you say yes here you will get support for the | 
 | 157 | 	  Maxim MAX6900 I2C RTC chip. | 
 | 158 |  | 
 | 159 | 	  This driver can also be built as a module. If so, the module | 
 | 160 | 	  will be called rtc-max6900. | 
 | 161 |  | 
 | 162 | config RTC_DRV_RS5C372 | 
 | 163 | 	tristate "Ricoh RS5C372A/B" | 
 | 164 | 	depends on RTC_CLASS && I2C | 
 | 165 | 	help | 
 | 166 | 	  If you say yes here you get support for the | 
 | 167 | 	  Ricoh RS5C372A and RS5C372B RTC chips. | 
 | 168 |  | 
 | 169 | 	  This driver can also be built as a module. If so, the module | 
 | 170 | 	  will be called rtc-rs5c372. | 
 | 171 |  | 
 | 172 | config RTC_DRV_ISL1208 | 
 | 173 | 	tristate "Intersil 1208" | 
 | 174 | 	depends on RTC_CLASS && I2C | 
 | 175 | 	help | 
 | 176 | 	  If you say yes here you get support for the | 
 | 177 | 	  Intersil 1208 RTC chip. | 
 | 178 |  | 
 | 179 | 	  This driver can also be built as a module. If so, the module | 
 | 180 | 	  will be called rtc-isl1208. | 
 | 181 |  | 
 | 182 | config RTC_DRV_X1205 | 
 | 183 | 	tristate "Xicor/Intersil X1205" | 
 | 184 | 	depends on RTC_CLASS && I2C | 
 | 185 | 	help | 
 | 186 | 	  If you say yes here you get support for the | 
 | 187 | 	  Xicor/Intersil X1205 RTC chip. | 
 | 188 |  | 
 | 189 | 	  This driver can also be built as a module. If so, the module | 
 | 190 | 	  will be called rtc-x1205. | 
 | 191 |  | 
 | 192 | config RTC_DRV_PCF8563 | 
 | 193 | 	tristate "Philips PCF8563/Epson RTC8564" | 
 | 194 | 	depends on RTC_CLASS && I2C | 
 | 195 | 	help | 
 | 196 | 	  If you say yes here you get support for the | 
 | 197 | 	  Philips PCF8563 RTC chip. The Epson RTC8564 | 
 | 198 | 	  should work as well. | 
 | 199 |  | 
 | 200 | 	  This driver can also be built as a module. If so, the module | 
 | 201 | 	  will be called rtc-pcf8563. | 
 | 202 |  | 
 | 203 | config RTC_DRV_PCF8583 | 
 | 204 | 	tristate "Philips PCF8583" | 
 | 205 | 	depends on RTC_CLASS && I2C | 
 | 206 | 	help | 
 | 207 | 	  If you say yes here you get support for the Philips PCF8583 | 
 | 208 | 	  RTC chip found on Acorn RiscPCs. This driver supports the | 
 | 209 | 	  platform specific method of retrieving the current year from | 
 | 210 | 	  the RTC's SRAM. It will work on other platforms with the same | 
 | 211 | 	  chip, but the year will probably have to be tweaked. | 
 | 212 |  | 
 | 213 | 	  This driver can also be built as a module. If so, the module | 
 | 214 | 	  will be called rtc-pcf8583. | 
 | 215 |  | 
 | 216 | comment "SPI RTC drivers" | 
 | 217 | 	depends on RTC_CLASS | 
 | 218 |  | 
 | 219 | config RTC_DRV_RS5C348 | 
 | 220 | 	tristate "Ricoh RS5C348A/B" | 
 | 221 | 	depends on RTC_CLASS && SPI | 
 | 222 | 	help | 
 | 223 | 	  If you say yes here you get support for the | 
 | 224 | 	  Ricoh RS5C348A and RS5C348B RTC chips. | 
 | 225 |  | 
 | 226 | 	  This driver can also be built as a module. If so, the module | 
 | 227 | 	  will be called rtc-rs5c348. | 
 | 228 |  | 
 | 229 | config RTC_DRV_MAX6902 | 
 | 230 | 	tristate "Maxim 6902" | 
 | 231 | 	depends on RTC_CLASS && SPI | 
 | 232 | 	help | 
 | 233 | 	  If you say yes here you will get support for the | 
 | 234 | 	  Maxim MAX6902 SPI RTC chip. | 
 | 235 |  | 
 | 236 | 	  This driver can also be built as a module. If so, the module | 
 | 237 | 	  will be called rtc-max6902. | 
 | 238 |  | 
 | 239 | comment "Platform RTC drivers" | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 240 | 	depends on RTC_CLASS | 
 | 241 |  | 
| David Brownell | 7be2c7c | 2007-02-10 01:46:02 -0800 | [diff] [blame] | 242 | # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> | 
 | 243 | # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a | 
 | 244 | # global rtc_lock ... it's not yet just another platform_device. | 
 | 245 |  | 
 | 246 | config RTC_DRV_CMOS | 
| Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 247 | 	tristate "PC-style 'CMOS'" | 
| Dave Jones | c066332 | 2007-02-20 13:58:07 -0800 | [diff] [blame] | 248 | 	depends on RTC_CLASS && (X86 || ALPHA || ARM26 || ARM \ | 
| Wade Farnsworth | 57cc705 | 2007-06-07 02:57:43 +1000 | [diff] [blame^] | 249 | 		|| M32R || ATARI || PPC || MIPS) | 
| David Brownell | 7be2c7c | 2007-02-10 01:46:02 -0800 | [diff] [blame] | 250 | 	help | 
 | 251 | 	  Say "yes" here to get direct support for the real time clock | 
 | 252 | 	  found in every PC or ACPI-based system, and some other boards. | 
 | 253 | 	  Specifically the original MC146818, compatibles like those in | 
 | 254 | 	  PC south bridges, the DS12887 or M48T86, some multifunction | 
 | 255 | 	  or LPC bus chips, and so on. | 
 | 256 |  | 
 | 257 | 	  Your system will need to define the platform device used by | 
 | 258 | 	  this driver, otherwise it won't be accessible.  This means | 
 | 259 | 	  you can safely enable this driver if you don't know whether | 
 | 260 | 	  or not your board has this kind of hardware. | 
 | 261 |  | 
 | 262 | 	  This driver can also be built as a module. If so, the module | 
 | 263 | 	  will be called rtc-cmos. | 
 | 264 |  | 
| Atsushi Nemoto | 9bf5b4f | 2006-06-25 05:48:28 -0700 | [diff] [blame] | 265 | config RTC_DRV_DS1553 | 
 | 266 | 	tristate "Dallas DS1553" | 
 | 267 | 	depends on RTC_CLASS | 
 | 268 | 	help | 
 | 269 | 	  If you say yes here you get support for the | 
 | 270 | 	  Dallas DS1553 timekeeping chip. | 
 | 271 |  | 
 | 272 | 	  This driver can also be built as a module. If so, the module | 
 | 273 | 	  will be called rtc-ds1553. | 
 | 274 |  | 
| Atsushi Nemoto | 5ec3e4b | 2006-06-25 05:48:29 -0700 | [diff] [blame] | 275 | config RTC_DRV_DS1742 | 
| Torsten Ertbjerg Rasmussen | f9231a0 | 2006-12-06 20:39:41 -0800 | [diff] [blame] | 276 | 	tristate "Dallas DS1742/1743" | 
| Atsushi Nemoto | 5ec3e4b | 2006-06-25 05:48:29 -0700 | [diff] [blame] | 277 | 	depends on RTC_CLASS | 
 | 278 | 	help | 
 | 279 | 	  If you say yes here you get support for the | 
| Torsten Ertbjerg Rasmussen | f9231a0 | 2006-12-06 20:39:41 -0800 | [diff] [blame] | 280 | 	  Dallas DS1742/1743 timekeeping chip. | 
| Atsushi Nemoto | 5ec3e4b | 2006-06-25 05:48:29 -0700 | [diff] [blame] | 281 |  | 
 | 282 | 	  This driver can also be built as a module. If so, the module | 
 | 283 | 	  will be called rtc-ds1742. | 
 | 284 |  | 
| Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 285 | config RTC_DRV_M48T86 | 
 | 286 | 	tristate "ST M48T86/Dallas DS12887" | 
 | 287 | 	depends on RTC_CLASS | 
 | 288 | 	help | 
 | 289 | 	  If you say Y here you will get support for the | 
 | 290 | 	  ST M48T86 and Dallas DS12887 RTC chips. | 
 | 291 |  | 
 | 292 | 	  This driver can also be built as a module. If so, the module | 
 | 293 | 	  will be called rtc-m48t86. | 
 | 294 |  | 
 | 295 | config RTC_DRV_V3020 | 
 | 296 | 	tristate "EM Microelectronic V3020" | 
 | 297 | 	depends on RTC_CLASS | 
 | 298 | 	help | 
 | 299 | 	  If you say yes here you will get support for the | 
 | 300 | 	  EM Microelectronic v3020 RTC chip. | 
 | 301 |  | 
 | 302 | 	  This driver can also be built as a module. If so, the module | 
 | 303 | 	  will be called rtc-v3020. | 
 | 304 |  | 
 | 305 | comment "on-CPU RTC drivers" | 
 | 306 | 	depends on RTC_CLASS | 
 | 307 |  | 
| David Brownell | db68b18 | 2006-12-06 20:38:36 -0800 | [diff] [blame] | 308 | config RTC_DRV_OMAP | 
 | 309 | 	tristate "TI OMAP1" | 
 | 310 | 	depends on RTC_CLASS && ( \ | 
 | 311 | 		ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 ) | 
 | 312 | 	help | 
 | 313 | 	  Say "yes" here to support the real time clock on TI OMAP1 chips. | 
 | 314 | 	  This driver can also be built as a module called rtc-omap. | 
 | 315 |  | 
| Ben Dooks | 1add678 | 2006-07-01 04:36:26 -0700 | [diff] [blame] | 316 | config RTC_DRV_S3C | 
 | 317 | 	tristate "Samsung S3C series SoC RTC" | 
 | 318 | 	depends on RTC_CLASS && ARCH_S3C2410 | 
 | 319 | 	help | 
 | 320 | 	  RTC (Realtime Clock) driver for the clock inbuilt into the | 
 | 321 | 	  Samsung S3C24XX series of SoCs. This can provide periodic | 
 | 322 | 	  interrupt rates from 1Hz to 64Hz for user programs, and | 
 | 323 | 	  wakeup from Alarm. | 
 | 324 |  | 
 | 325 | 	  The driver currently supports the common features on all the | 
 | 326 | 	  S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 | 
 | 327 | 	  and S3C2442. | 
 | 328 |  | 
 | 329 | 	  This driver can also be build as a module. If so, the module | 
 | 330 | 	  will be called rtc-s3c. | 
 | 331 |  | 
| Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 332 | config RTC_DRV_EP93XX | 
 | 333 | 	tristate "Cirrus Logic EP93XX" | 
 | 334 | 	depends on RTC_CLASS && ARCH_EP93XX | 
 | 335 | 	help | 
 | 336 | 	  If you say yes here you get support for the | 
 | 337 | 	  RTC embedded in the Cirrus Logic EP93XX processors. | 
 | 338 |  | 
 | 339 | 	  This driver can also be built as a module. If so, the module | 
 | 340 | 	  will be called rtc-ep93xx. | 
 | 341 |  | 
| Richard Purdie | e842f1c | 2006-03-27 01:16:46 -0800 | [diff] [blame] | 342 | config RTC_DRV_SA1100 | 
 | 343 | 	tristate "SA11x0/PXA2xx" | 
 | 344 | 	depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA) | 
 | 345 | 	help | 
 | 346 | 	  If you say Y here you will get access to the real time clock | 
 | 347 | 	  built into your SA11x0 or PXA2xx CPU. | 
 | 348 |  | 
 | 349 | 	  To compile this driver as a module, choose M here: the | 
 | 350 | 	  module will be called rtc-sa1100. | 
| Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 351 |  | 
| Paul Mundt | 317a610 | 2006-09-27 17:13:19 +0900 | [diff] [blame] | 352 | config RTC_DRV_SH | 
 | 353 | 	tristate "SuperH On-Chip RTC" | 
 | 354 | 	depends on RTC_CLASS && SUPERH | 
 | 355 | 	help | 
 | 356 | 	  Say Y here to enable support for the on-chip RTC found in | 
 | 357 | 	  most SuperH processors. | 
 | 358 |  | 
 | 359 |  	  To compile this driver as a module, choose M here: the | 
 | 360 | 	  module will be called rtc-sh. | 
 | 361 |  | 
| Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 362 | config RTC_DRV_VR41XX | 
| Alessandro Zummo | 3e16f6a | 2006-04-10 22:54:48 -0700 | [diff] [blame] | 363 | 	tristate "NEC VR41XX" | 
| Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 364 | 	depends on RTC_CLASS && CPU_VR41XX | 
| Alessandro Zummo | 3e16f6a | 2006-04-10 22:54:48 -0700 | [diff] [blame] | 365 | 	help | 
 | 366 | 	  If you say Y here you will get access to the real time clock | 
 | 367 | 	  built into your NEC VR41XX CPU. | 
 | 368 |  | 
 | 369 | 	  To compile this driver as a module, choose M here: the | 
 | 370 | 	  module will be called rtc-vr41xx. | 
| Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 371 |  | 
| Deepak Saxena | 8ae6e16 | 2006-06-25 05:47:38 -0700 | [diff] [blame] | 372 | config RTC_DRV_PL031 | 
 | 373 | 	tristate "ARM AMBA PL031 RTC" | 
 | 374 | 	depends on RTC_CLASS && ARM_AMBA | 
 | 375 | 	help | 
 | 376 | 	  If you say Y here you will get access to ARM AMBA | 
| Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 377 | 	  PrimeCell PL031 RTC found on certain ARM SOCs. | 
| Deepak Saxena | 8ae6e16 | 2006-06-25 05:47:38 -0700 | [diff] [blame] | 378 |  | 
 | 379 | 	  To compile this driver as a module, choose M here: the | 
 | 380 | 	  module will be called rtc-pl031. | 
 | 381 |  | 
| Andrew Victor | 7fc39f6 | 2006-12-10 02:19:03 -0800 | [diff] [blame] | 382 | config RTC_DRV_AT91RM9200 | 
| Andrew Victor | 788b1fc | 2006-06-25 05:48:27 -0700 | [diff] [blame] | 383 | 	tristate "AT91RM9200" | 
 | 384 | 	depends on RTC_CLASS && ARCH_AT91RM9200 | 
 | 385 | 	help | 
 | 386 | 	  Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock). | 
 | 387 |  | 
| Wu, Bryan | 8cc75c9 | 2007-05-06 14:50:32 -0700 | [diff] [blame] | 388 | config RTC_DRV_BFIN | 
 | 389 | 	tristate "Blackfin On-Chip RTC" | 
 | 390 | 	depends on RTC_CLASS && BFIN | 
 | 391 | 	help | 
 | 392 | 	  If you say yes here you will get support for the | 
 | 393 | 	  Blackfin On-Chip Real Time Clock. | 
 | 394 |  | 
 | 395 | 	  This driver can also be built as a module. If so, the module | 
 | 396 | 	  will be called rtc-bfin. | 
 | 397 |  | 
| Nobuhiro Iwamatsu | e9f2bd8 | 2007-05-08 00:26:37 -0700 | [diff] [blame] | 398 | config RTC_DRV_RS5C313 | 
 | 399 | 	tristate "Ricoh RS5C313" | 
| kogiidena | 9a3f1d5 | 2007-05-10 22:22:54 -0700 | [diff] [blame] | 400 | 	depends on RTC_CLASS && SH_LANDISK | 
| Nobuhiro Iwamatsu | e9f2bd8 | 2007-05-08 00:26:37 -0700 | [diff] [blame] | 401 | 	help | 
 | 402 | 	  If you say yes here you get support for the Ricoh RS5C313 RTC chips. | 
 | 403 |  | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 404 | endmenu |