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 | |
| 5 | config RTC_LIB |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 6 | tristate |
| 7 | |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 8 | menuconfig RTC_CLASS |
| 9 | tristate "Real Time Clock" |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 10 | default n |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 11 | depends on !S390 |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 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 |
Adrian Bunk | 27ae410 | 2006-06-30 18:18:41 +0200 | [diff] [blame] | 16 | probably want to enable one or more of the interfaces below. |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 17 | |
| 18 | This driver can also be built as a module. If so, the module |
| 19 | will be called rtc-class. |
| 20 | |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 21 | if RTC_CLASS |
| 22 | |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 23 | config RTC_HCTOSYS |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 24 | bool "Set system time from RTC on startup and resume" |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 25 | depends on RTC_CLASS = y |
| 26 | default y |
| 27 | help |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 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. |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 31 | |
| 32 | config RTC_HCTOSYS_DEVICE |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 33 | string "RTC used to set the system time" |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 34 | depends on RTC_HCTOSYS = y |
| 35 | default "rtc0" |
| 36 | help |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 37 | The RTC device that will be used to (re)initialize the system |
| 38 | clock, usually rtc0. Initialization is done when the system |
David Brownell | 779d208 | 2007-11-14 16:58:29 -0800 | [diff] [blame] | 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. |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 42 | |
David Brownell | 55ff1ab | 2007-07-21 04:37:56 -0700 | [diff] [blame] | 43 | The driver for this RTC device must be loaded before late_initcall |
| 44 | functions run, so it must usually be statically linked. |
| 45 | |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 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. |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 54 | |
David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 55 | config 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 | |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 62 | comment "RTC interfaces" |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 63 | |
Alessandro Zummo | c5c3e19 | 2006-03-27 01:16:39 -0800 | [diff] [blame] | 64 | config RTC_INTF_SYSFS |
David Brownell | e40659c | 2007-05-16 22:11:15 -0700 | [diff] [blame] | 65 | boolean "/sys/class/rtc/rtcN (sysfs)" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 66 | depends on SYSFS |
Alessandro Zummo | c5c3e19 | 2006-03-27 01:16:39 -0800 | [diff] [blame] | 67 | default RTC_CLASS |
| 68 | help |
David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 69 | Say yes here if you want to use your RTCs using sysfs interfaces, |
| 70 | /sys/class/rtc/rtc0 through /sys/.../rtcN. |
Alessandro Zummo | c5c3e19 | 2006-03-27 01:16:39 -0800 | [diff] [blame] | 71 | |
| 72 | This driver can also be built as a module. If so, the module |
| 73 | will be called rtc-sysfs. |
| 74 | |
Alessandro Zummo | 728a294 | 2006-03-27 01:16:40 -0800 | [diff] [blame] | 75 | config RTC_INTF_PROC |
David Brownell | e40659c | 2007-05-16 22:11:15 -0700 | [diff] [blame] | 76 | boolean "/proc/driver/rtc (procfs for rtc0)" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 77 | depends on PROC_FS |
Alessandro Zummo | 728a294 | 2006-03-27 01:16:40 -0800 | [diff] [blame] | 78 | default RTC_CLASS |
| 79 | help |
David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 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. |
Alessandro Zummo | 728a294 | 2006-03-27 01:16:40 -0800 | [diff] [blame] | 83 | |
| 84 | This driver can also be built as a module. If so, the module |
| 85 | will be called rtc-proc. |
| 86 | |
Alessandro Zummo | e824290 | 2006-03-27 01:16:41 -0800 | [diff] [blame] | 87 | config RTC_INTF_DEV |
David Brownell | e40659c | 2007-05-16 22:11:15 -0700 | [diff] [blame] | 88 | boolean "/dev/rtcN (character devices)" |
Alessandro Zummo | e824290 | 2006-03-27 01:16:41 -0800 | [diff] [blame] | 89 | default RTC_CLASS |
| 90 | help |
David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 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. |
Alessandro Zummo | e824290 | 2006-03-27 01:16:41 -0800 | [diff] [blame] | 96 | |
| 97 | This driver can also be built as a module. If so, the module |
| 98 | will be called rtc-dev. |
| 99 | |
Atsushi Nemoto | 655066c | 2006-06-25 05:48:17 -0700 | [diff] [blame] | 100 | config RTC_INTF_DEV_UIE_EMUL |
| 101 | bool "RTC UIE emulation on dev interface" |
| 102 | depends on RTC_INTF_DEV |
| 103 | help |
David Sterba | 3dde6ad | 2007-05-09 07:12:20 +0200 | [diff] [blame] | 104 | Provides an emulation for RTC_UIE if the underlying rtc chip |
David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 105 | driver does not expose RTC_UIE ioctls. Those requests generate |
| 106 | once-per-second update interrupts, used for synchronization. |
Atsushi Nemoto | 655066c | 2006-06-25 05:48:17 -0700 | [diff] [blame] | 107 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 108 | config RTC_DRV_TEST |
| 109 | tristate "Test driver/device" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 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 | |
| 122 | comment "I2C RTC drivers" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 123 | depends on I2C |
| 124 | |
| 125 | if I2C |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 126 | |
| 127 | config RTC_DRV_DS1307 |
| 128 | tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 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 |
David Brownell | 682d73f | 2007-11-14 16:58:32 -0800 | [diff] [blame] | 138 | the RTC/NVRAM backup power, and alarms. NVRAM is visible in |
| 139 | sysfs, but other chip features may not be available. |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 140 | |
| 141 | This driver can also be built as a module. If so, the module |
| 142 | will be called rtc-ds1307. |
| 143 | |
Scott Wood | bf4994d | 2007-10-16 01:28:19 -0700 | [diff] [blame] | 144 | config 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 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 155 | config RTC_DRV_DS1672 |
| 156 | tristate "Dallas/Maxim DS1672" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 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 | |
| 164 | config RTC_DRV_MAX6900 |
| 165 | tristate "Maxim 6900" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 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 | |
| 173 | config RTC_DRV_RS5C372 |
David Brownell | d815461 | 2007-07-17 04:04:55 -0700 | [diff] [blame] | 174 | tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 175 | help |
| 176 | If you say yes here you get support for the |
David Brownell | d815461 | 2007-07-17 04:04:55 -0700 | [diff] [blame] | 177 | Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 178 | |
| 179 | This driver can also be built as a module. If so, the module |
| 180 | will be called rtc-rs5c372. |
| 181 | |
| 182 | config RTC_DRV_ISL1208 |
| 183 | tristate "Intersil 1208" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 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 | |
| 191 | config RTC_DRV_X1205 |
| 192 | tristate "Xicor/Intersil X1205" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 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 | |
| 200 | config RTC_DRV_PCF8563 |
| 201 | tristate "Philips PCF8563/Epson RTC8564" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 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 | |
| 210 | config RTC_DRV_PCF8583 |
| 211 | tristate "Philips PCF8583" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 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 | |
Atsushi Nemoto | caaff56 | 2007-07-17 04:05:02 -0700 | [diff] [blame] | 222 | config RTC_DRV_M41T80 |
| 223 | tristate "ST M41T80 series RTC" |
Atsushi Nemoto | caaff56 | 2007-07-17 04:05:02 -0700 | [diff] [blame] | 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 | |
Atsushi Nemoto | 617780d | 2007-07-17 04:05:04 -0700 | [diff] [blame] | 233 | config 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 | |
Tony Lindgren | 0c4a59f | 2007-07-17 04:06:09 -0700 | [diff] [blame] | 240 | config RTC_DRV_TWL92330 |
| 241 | boolean "TI TWL92330/Menelaus" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 242 | depends on MENELAUS |
Tony Lindgren | 0c4a59f | 2007-07-17 04:06:09 -0700 | [diff] [blame] | 243 | help |
| 244 | If you say yes here you get support for the RTC on the |
Matt LaPlante | 01dd2fb | 2007-10-20 01:34:40 +0200 | [diff] [blame] | 245 | TWL92330 "Menelaus" power management chip, used with OMAP2 |
Tony Lindgren | 0c4a59f | 2007-07-17 04:06:09 -0700 | [diff] [blame] | 246 | platforms. The support is integrated with the rest of |
| 247 | the Menelaus driver; it's not separate module. |
| 248 | |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 249 | endif # I2C |
| 250 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 251 | comment "SPI RTC drivers" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 252 | |
| 253 | if SPI_MASTER |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 254 | |
| 255 | config RTC_DRV_RS5C348 |
| 256 | tristate "Ricoh RS5C348A/B" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 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 | |
| 264 | config RTC_DRV_MAX6902 |
| 265 | tristate "Maxim 6902" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 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 | |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 273 | endif # SPI_MASTER |
| 274 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 275 | comment "Platform RTC drivers" |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 276 | |
David Brownell | 7be2c7c | 2007-02-10 01:46:02 -0800 | [diff] [blame] | 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 | |
| 281 | config RTC_DRV_CMOS |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 282 | tristate "PC-style 'CMOS'" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 283 | depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS |
David Brownell | 7be2c7c | 2007-02-10 01:46:02 -0800 | [diff] [blame] | 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 | |
Thomas Bogendoerfer | 537739d | 2007-07-17 04:05:06 -0700 | [diff] [blame] | 299 | config RTC_DRV_DS1216 |
| 300 | tristate "Dallas DS1216" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 301 | depends on SNI_RM |
Thomas Bogendoerfer | 537739d | 2007-07-17 04:05:06 -0700 | [diff] [blame] | 302 | help |
| 303 | If you say yes here you get support for the Dallas DS1216 RTC chips. |
| 304 | |
Atsushi Nemoto | 9bf5b4f | 2006-06-25 05:48:28 -0700 | [diff] [blame] | 305 | config RTC_DRV_DS1553 |
| 306 | tristate "Dallas DS1553" |
Atsushi Nemoto | 9bf5b4f | 2006-06-25 05:48:28 -0700 | [diff] [blame] | 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 | |
Thomas Hommel | 0296411 | 2007-07-21 04:37:58 -0700 | [diff] [blame] | 314 | config 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 | |
Atsushi Nemoto | 5ec3e4b | 2006-06-25 05:48:29 -0700 | [diff] [blame] | 324 | config RTC_DRV_DS1742 |
Torsten Ertbjerg Rasmussen | f9231a0 | 2006-12-06 20:39:41 -0800 | [diff] [blame] | 325 | tristate "Dallas DS1742/1743" |
Atsushi Nemoto | 5ec3e4b | 2006-06-25 05:48:29 -0700 | [diff] [blame] | 326 | help |
| 327 | If you say yes here you get support for the |
Torsten Ertbjerg Rasmussen | f9231a0 | 2006-12-06 20:39:41 -0800 | [diff] [blame] | 328 | Dallas DS1742/1743 timekeeping chip. |
Atsushi Nemoto | 5ec3e4b | 2006-06-25 05:48:29 -0700 | [diff] [blame] | 329 | |
| 330 | This driver can also be built as a module. If so, the module |
| 331 | will be called rtc-ds1742. |
| 332 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 333 | config RTC_DRV_M48T86 |
| 334 | tristate "ST M48T86/Dallas DS12887" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 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 | |
Mark Zhan | 2e774c7 | 2007-07-17 04:05:05 -0700 | [diff] [blame] | 342 | config RTC_DRV_M48T59 |
| 343 | tristate "ST M48T59" |
Mark Zhan | 2e774c7 | 2007-07-17 04:05:05 -0700 | [diff] [blame] | 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 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 351 | config RTC_DRV_V3020 |
| 352 | tristate "EM Microelectronic V3020" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 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 | |
| 360 | comment "on-CPU RTC drivers" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 361 | |
David Brownell | db68b18 | 2006-12-06 20:38:36 -0800 | [diff] [blame] | 362 | config RTC_DRV_OMAP |
| 363 | tristate "TI OMAP1" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 364 | depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 |
David Brownell | db68b18 | 2006-12-06 20:38:36 -0800 | [diff] [blame] | 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 | |
Ben Dooks | 1add678 | 2006-07-01 04:36:26 -0700 | [diff] [blame] | 369 | config RTC_DRV_S3C |
| 370 | tristate "Samsung S3C series SoC RTC" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 371 | depends on ARCH_S3C2410 |
Ben Dooks | 1add678 | 2006-07-01 04:36:26 -0700 | [diff] [blame] | 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 | |
Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 385 | config RTC_DRV_EP93XX |
| 386 | tristate "Cirrus Logic EP93XX" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 387 | depends on ARCH_EP93XX |
Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 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 | |
Richard Purdie | e842f1c | 2006-03-27 01:16:46 -0800 | [diff] [blame] | 395 | config RTC_DRV_SA1100 |
| 396 | tristate "SA11x0/PXA2xx" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 397 | depends on ARCH_SA1100 || ARCH_PXA |
Richard Purdie | e842f1c | 2006-03-27 01:16:46 -0800 | [diff] [blame] | 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. |
Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 404 | |
Paul Mundt | 317a610 | 2006-09-27 17:13:19 +0900 | [diff] [blame] | 405 | config RTC_DRV_SH |
| 406 | tristate "SuperH On-Chip RTC" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 407 | depends on RTC_CLASS && (CPU_SH3 || CPU_SH4) |
Paul Mundt | 317a610 | 2006-09-27 17:13:19 +0900 | [diff] [blame] | 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 | |
Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 415 | config RTC_DRV_VR41XX |
Alessandro Zummo | 3e16f6a | 2006-04-10 22:54:48 -0700 | [diff] [blame] | 416 | tristate "NEC VR41XX" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 417 | depends on CPU_VR41XX |
Alessandro Zummo | 3e16f6a | 2006-04-10 22:54:48 -0700 | [diff] [blame] | 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. |
Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 424 | |
Deepak Saxena | 8ae6e16 | 2006-06-25 05:47:38 -0700 | [diff] [blame] | 425 | config RTC_DRV_PL031 |
| 426 | tristate "ARM AMBA PL031 RTC" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 427 | depends on ARM_AMBA |
Deepak Saxena | 8ae6e16 | 2006-06-25 05:47:38 -0700 | [diff] [blame] | 428 | help |
| 429 | If you say Y here you will get access to ARM AMBA |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 430 | PrimeCell PL031 RTC found on certain ARM SOCs. |
Deepak Saxena | 8ae6e16 | 2006-06-25 05:47:38 -0700 | [diff] [blame] | 431 | |
| 432 | To compile this driver as a module, choose M here: the |
| 433 | module will be called rtc-pl031. |
| 434 | |
Hans-Christian Egtvedt | fa04e78 | 2007-07-17 04:05:00 -0700 | [diff] [blame] | 435 | config RTC_DRV_AT32AP700X |
| 436 | tristate "AT32AP700X series RTC" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 437 | depends on PLATFORM_AT32AP |
Hans-Christian Egtvedt | fa04e78 | 2007-07-17 04:05:00 -0700 | [diff] [blame] | 438 | help |
| 439 | Driver for the internal RTC (Realtime Clock) on Atmel AVR32 |
| 440 | AT32AP700x family processors. |
| 441 | |
Andrew Victor | 7fc39f6 | 2006-12-10 02:19:03 -0800 | [diff] [blame] | 442 | config RTC_DRV_AT91RM9200 |
Andrew Victor | 788b1fc | 2006-06-25 05:48:27 -0700 | [diff] [blame] | 443 | tristate "AT91RM9200" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 444 | depends on ARCH_AT91RM9200 |
Andrew Victor | 788b1fc | 2006-06-25 05:48:27 -0700 | [diff] [blame] | 445 | help |
| 446 | Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock). |
| 447 | |
Wu, Bryan | 8cc75c9 | 2007-05-06 14:50:32 -0700 | [diff] [blame] | 448 | config RTC_DRV_BFIN |
| 449 | tristate "Blackfin On-Chip RTC" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 450 | depends on BFIN |
Wu, Bryan | 8cc75c9 | 2007-05-06 14:50:32 -0700 | [diff] [blame] | 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 | |
Nobuhiro Iwamatsu | e9f2bd8 | 2007-05-08 00:26:37 -0700 | [diff] [blame] | 458 | config RTC_DRV_RS5C313 |
| 459 | tristate "Ricoh RS5C313" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 460 | depends on SH_LANDISK |
Nobuhiro Iwamatsu | e9f2bd8 | 2007-05-08 00:26:37 -0700 | [diff] [blame] | 461 | help |
| 462 | If you say yes here you get support for the Ricoh RS5C313 RTC chips. |
| 463 | |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 464 | endif # RTC_CLASS |