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 |
Alessandro Zummo | 44e0451 | 2008-03-19 17:00:51 -0700 | [diff] [blame] | 19 | will be called rtc-core. |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 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 |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 52 | sleep states. Do not specify an RTC here unless it stays powered |
David Brownell | 7ca1d48 | 2007-05-08 00:33:42 -0700 | [diff] [blame] | 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 |
Alessandro Zummo | 099e657 | 2009-01-04 12:00:54 -0800 | [diff] [blame^] | 105 | driver does not expose RTC_UIE ioctls. Those requests generate |
David Brownell | 9e86ecb | 2006-09-30 23:28:14 -0700 | [diff] [blame] | 106 | once-per-second update interrupts, used for synchronization. |
Atsushi Nemoto | 655066c | 2006-06-25 05:48:17 -0700 | [diff] [blame] | 107 | |
Alessandro Zummo | 099e657 | 2009-01-04 12:00:54 -0800 | [diff] [blame^] | 108 | The emulation code will read the time from the hardware |
| 109 | clock several times per second, please enable this option |
| 110 | only if you know that you really need it. |
| 111 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 112 | config RTC_DRV_TEST |
| 113 | tristate "Test driver/device" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 114 | help |
| 115 | If you say yes here you get support for the |
| 116 | RTC test driver. It's a software RTC which can be |
| 117 | used to test the RTC subsystem APIs. It gets |
| 118 | the time from the system clock. |
| 119 | You want this driver only if you are doing development |
| 120 | on the RTC subsystem. Please read the source code |
| 121 | for further details. |
| 122 | |
| 123 | This driver can also be built as a module. If so, the module |
| 124 | will be called rtc-test. |
| 125 | |
| 126 | comment "I2C RTC drivers" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 127 | depends on I2C |
| 128 | |
| 129 | if I2C |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 130 | |
| 131 | config RTC_DRV_DS1307 |
| 132 | tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 133 | help |
| 134 | If you say yes here you get support for various compatible RTC |
| 135 | chips (often with battery backup) connected with I2C. This driver |
| 136 | should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00, |
| 137 | and probably other chips. In some cases the RTC must already |
| 138 | have been initialized (by manufacturing or a bootloader). |
| 139 | |
| 140 | The first seven registers on these chips hold an RTC, and other |
| 141 | registers may add features such as NVRAM, a trickle charger for |
David Brownell | 682d73f | 2007-11-14 16:58:32 -0800 | [diff] [blame] | 142 | the RTC/NVRAM backup power, and alarms. NVRAM is visible in |
| 143 | sysfs, but other chip features may not be available. |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 144 | |
| 145 | This driver can also be built as a module. If so, the module |
| 146 | will be called rtc-ds1307. |
| 147 | |
Scott Wood | bf4994d | 2007-10-16 01:28:19 -0700 | [diff] [blame] | 148 | config RTC_DRV_DS1374 |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 149 | tristate "Dallas/Maxim DS1374" |
Scott Wood | bf4994d | 2007-10-16 01:28:19 -0700 | [diff] [blame] | 150 | depends on RTC_CLASS && I2C |
| 151 | help |
| 152 | If you say yes here you get support for Dallas Semiconductor |
| 153 | DS1374 real-time clock chips. If an interrupt is associated |
| 154 | with the device, the alarm functionality is supported. |
| 155 | |
| 156 | This driver can also be built as a module. If so, the module |
| 157 | will be called rtc-ds1374. |
| 158 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 159 | config RTC_DRV_DS1672 |
| 160 | tristate "Dallas/Maxim DS1672" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 161 | help |
| 162 | If you say yes here you get support for the |
| 163 | Dallas/Maxim DS1672 timekeeping chip. |
| 164 | |
| 165 | This driver can also be built as a module. If so, the module |
| 166 | will be called rtc-ds1672. |
| 167 | |
| 168 | config RTC_DRV_MAX6900 |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 169 | tristate "Maxim MAX6900" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 170 | help |
| 171 | If you say yes here you will get support for the |
| 172 | Maxim MAX6900 I2C RTC chip. |
| 173 | |
| 174 | This driver can also be built as a module. If so, the module |
| 175 | will be called rtc-max6900. |
| 176 | |
| 177 | config RTC_DRV_RS5C372 |
Paul Mundt | 5d4529b | 2008-10-21 20:12:59 +0900 | [diff] [blame] | 178 | tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 179 | help |
| 180 | If you say yes here you get support for the |
Paul Mundt | 5d4529b | 2008-10-21 20:12:59 +0900 | [diff] [blame] | 181 | Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips. |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 182 | |
| 183 | This driver can also be built as a module. If so, the module |
| 184 | will be called rtc-rs5c372. |
| 185 | |
| 186 | config RTC_DRV_ISL1208 |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 187 | tristate "Intersil ISL1208" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 188 | help |
| 189 | If you say yes here you get support for the |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 190 | Intersil ISL1208 RTC chip. |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 191 | |
| 192 | This driver can also be built as a module. If so, the module |
| 193 | will be called rtc-isl1208. |
| 194 | |
| 195 | config RTC_DRV_X1205 |
| 196 | tristate "Xicor/Intersil X1205" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 197 | help |
| 198 | If you say yes here you get support for the |
| 199 | Xicor/Intersil X1205 RTC chip. |
| 200 | |
| 201 | This driver can also be built as a module. If so, the module |
| 202 | will be called rtc-x1205. |
| 203 | |
| 204 | config RTC_DRV_PCF8563 |
| 205 | tristate "Philips PCF8563/Epson RTC8564" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 206 | help |
| 207 | If you say yes here you get support for the |
| 208 | Philips PCF8563 RTC chip. The Epson RTC8564 |
| 209 | should work as well. |
| 210 | |
| 211 | This driver can also be built as a module. If so, the module |
| 212 | will be called rtc-pcf8563. |
| 213 | |
| 214 | config RTC_DRV_PCF8583 |
| 215 | tristate "Philips PCF8583" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 216 | help |
| 217 | If you say yes here you get support for the Philips PCF8583 |
| 218 | RTC chip found on Acorn RiscPCs. This driver supports the |
| 219 | platform specific method of retrieving the current year from |
| 220 | the RTC's SRAM. It will work on other platforms with the same |
| 221 | chip, but the year will probably have to be tweaked. |
| 222 | |
| 223 | This driver can also be built as a module. If so, the module |
| 224 | will be called rtc-pcf8583. |
| 225 | |
Atsushi Nemoto | caaff56 | 2007-07-17 04:05:02 -0700 | [diff] [blame] | 226 | config RTC_DRV_M41T80 |
Steven A. Falco | d3a126f | 2008-10-15 22:03:07 -0700 | [diff] [blame] | 227 | tristate "ST M41T65/M41T80/81/82/83/84/85/87" |
Atsushi Nemoto | caaff56 | 2007-07-17 04:05:02 -0700 | [diff] [blame] | 228 | help |
Steven A. Falco | d3a126f | 2008-10-15 22:03:07 -0700 | [diff] [blame] | 229 | If you say Y here you will get support for the ST M41T60 |
| 230 | and M41T80 RTC chips series. Currently, the following chips are |
| 231 | supported: M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84, |
| 232 | M41ST85, and M41ST87. |
Atsushi Nemoto | caaff56 | 2007-07-17 04:05:02 -0700 | [diff] [blame] | 233 | |
| 234 | This driver can also be built as a module. If so, the module |
| 235 | will be called rtc-m41t80. |
| 236 | |
Atsushi Nemoto | 617780d | 2007-07-17 04:05:04 -0700 | [diff] [blame] | 237 | config RTC_DRV_M41T80_WDT |
Steven A. Falco | d3a126f | 2008-10-15 22:03:07 -0700 | [diff] [blame] | 238 | bool "ST M41T65/M41T80 series RTC watchdog timer" |
Atsushi Nemoto | 617780d | 2007-07-17 04:05:04 -0700 | [diff] [blame] | 239 | depends on RTC_DRV_M41T80 |
| 240 | help |
| 241 | If you say Y here you will get support for the |
Steven A. Falco | d3a126f | 2008-10-15 22:03:07 -0700 | [diff] [blame] | 242 | watchdog timer in the ST M41T60 and M41T80 RTC chips series. |
Atsushi Nemoto | 617780d | 2007-07-17 04:05:04 -0700 | [diff] [blame] | 243 | |
Tony Lindgren | 0c4a59f | 2007-07-17 04:06:09 -0700 | [diff] [blame] | 244 | config RTC_DRV_TWL92330 |
| 245 | boolean "TI TWL92330/Menelaus" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 246 | depends on MENELAUS |
Tony Lindgren | 0c4a59f | 2007-07-17 04:06:09 -0700 | [diff] [blame] | 247 | help |
| 248 | 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] | 249 | TWL92330 "Menelaus" power management chip, used with OMAP2 |
Tony Lindgren | 0c4a59f | 2007-07-17 04:06:09 -0700 | [diff] [blame] | 250 | platforms. The support is integrated with the rest of |
| 251 | the Menelaus driver; it's not separate module. |
| 252 | |
David Brownell | f96411a | 2008-10-20 23:50:05 +0200 | [diff] [blame] | 253 | config RTC_DRV_TWL4030 |
| 254 | tristate "TI TWL4030/TWL5030/TPS659x0" |
| 255 | depends on RTC_CLASS && TWL4030_CORE |
| 256 | help |
| 257 | If you say yes here you get support for the RTC on the |
| 258 | TWL4030 family chips, used mostly with OMAP3 platforms. |
| 259 | |
| 260 | This driver can also be built as a module. If so, the module |
| 261 | will be called rtc-twl4030. |
| 262 | |
Byron Bradley | c46288b | 2008-03-04 14:28:25 -0800 | [diff] [blame] | 263 | config RTC_DRV_S35390A |
| 264 | tristate "Seiko Instruments S-35390A" |
Randy Dunlap | d479540 | 2008-04-10 21:29:18 -0700 | [diff] [blame] | 265 | select BITREVERSE |
Byron Bradley | c46288b | 2008-03-04 14:28:25 -0800 | [diff] [blame] | 266 | help |
| 267 | If you say yes here you will get support for the Seiko |
| 268 | Instruments S-35390A. |
| 269 | |
| 270 | This driver can also be built as a module. If so the module |
| 271 | will be called rtc-s35390a. |
| 272 | |
Sergey Lapin | c6d8f40 | 2008-06-12 15:21:55 -0700 | [diff] [blame] | 273 | config RTC_DRV_FM3130 |
| 274 | tristate "Ramtron FM3130" |
| 275 | help |
| 276 | If you say Y here you will get support for the |
| 277 | Ramtron FM3130 RTC chips. |
| 278 | Ramtron FM3130 is a chip with two separate devices inside, |
| 279 | RTC clock and FRAM. This driver provides only RTC functionality. |
| 280 | |
| 281 | This driver can also be built as a module. If so the module |
| 282 | will be called rtc-fm3130. |
| 283 | |
Martyn Welch | a7fa985 | 2008-11-12 13:27:06 -0800 | [diff] [blame] | 284 | config RTC_DRV_RX8581 |
| 285 | tristate "Epson RX-8581" |
| 286 | help |
| 287 | If you say yes here you will get support for the Epson RX-8581. |
| 288 | |
| 289 | This driver can also be built as a module. If so the module |
| 290 | will be called rtc-rx8581. |
| 291 | |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 292 | endif # I2C |
| 293 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 294 | comment "SPI RTC drivers" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 295 | |
| 296 | if SPI_MASTER |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 297 | |
Kim B. Heino | 8fc2c76 | 2008-07-23 21:30:34 -0700 | [diff] [blame] | 298 | config RTC_DRV_M41T94 |
| 299 | tristate "ST M41T94" |
| 300 | help |
| 301 | If you say yes here you will get support for the |
| 302 | ST M41T94 SPI RTC chip. |
| 303 | |
| 304 | This driver can also be built as a module. If so, the module |
| 305 | will be called rtc-m41t94. |
| 306 | |
David Brownell | 53e84b6 | 2008-07-23 21:30:36 -0700 | [diff] [blame] | 307 | config RTC_DRV_DS1305 |
| 308 | tristate "Dallas/Maxim DS1305/DS1306" |
| 309 | help |
| 310 | Select this driver to get support for the Dallas/Maxim DS1305 |
| 311 | and DS1306 real time clock chips. These support a trickle |
| 312 | charger, alarms, and NVRAM in addition to the clock. |
| 313 | |
| 314 | This driver can also be built as a module. If so, the module |
| 315 | will be called rtc-ds1305. |
| 316 | |
Mark Jackson | 06de180 | 2008-11-12 13:27:07 -0800 | [diff] [blame] | 317 | config RTC_DRV_DS1390 |
| 318 | tristate "Dallas/Maxim DS1390/93/94" |
| 319 | help |
| 320 | If you say yes here you get support for the DS1390/93/94 chips. |
| 321 | |
| 322 | This driver only supports the RTC feature, and not other chip |
| 323 | features such as alarms and trickle charging. |
| 324 | |
| 325 | This driver can also be built as a module. If so, the module |
| 326 | will be called rtc-ds1390. |
| 327 | |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 328 | config RTC_DRV_MAX6902 |
| 329 | tristate "Maxim MAX6902" |
| 330 | help |
| 331 | If you say yes here you will get support for the |
| 332 | Maxim MAX6902 SPI RTC chip. |
| 333 | |
| 334 | This driver can also be built as a module. If so, the module |
| 335 | will be called rtc-max6902. |
| 336 | |
Magnus Damm | 2805b96 | 2008-02-06 01:38:53 -0800 | [diff] [blame] | 337 | config RTC_DRV_R9701 |
| 338 | tristate "Epson RTC-9701JE" |
| 339 | help |
| 340 | If you say yes here you will get support for the |
| 341 | Epson RTC-9701JE SPI RTC chip. |
| 342 | |
| 343 | This driver can also be built as a module. If so, the module |
| 344 | will be called rtc-r9701. |
| 345 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 346 | config RTC_DRV_RS5C348 |
| 347 | tristate "Ricoh RS5C348A/B" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 348 | help |
| 349 | If you say yes here you get support for the |
| 350 | Ricoh RS5C348A and RS5C348B RTC chips. |
| 351 | |
| 352 | This driver can also be built as a module. If so, the module |
| 353 | will be called rtc-rs5c348. |
| 354 | |
Dennis Aberilla | 2f9b75e | 2008-10-15 22:02:57 -0700 | [diff] [blame] | 355 | config RTC_DRV_DS3234 |
| 356 | tristate "Maxim/Dallas DS3234" |
| 357 | help |
| 358 | If you say yes here you get support for the |
| 359 | Maxim/Dallas DS3234 SPI RTC chip. |
| 360 | |
| 361 | This driver can also be built as a module. If so, the module |
| 362 | will be called rtc-ds3234. |
| 363 | |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 364 | endif # SPI_MASTER |
| 365 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 366 | comment "Platform RTC drivers" |
Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 367 | |
David Brownell | 7be2c7c | 2007-02-10 01:46:02 -0800 | [diff] [blame] | 368 | # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h> |
| 369 | # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a |
| 370 | # global rtc_lock ... it's not yet just another platform_device. |
| 371 | |
| 372 | config RTC_DRV_CMOS |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 373 | tristate "PC-style 'CMOS'" |
Andrew Morton | 5ec8770 | 2008-09-22 21:40:04 -0700 | [diff] [blame] | 374 | depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64 |
David Brownell | c750090 | 2008-04-28 02:11:52 -0700 | [diff] [blame] | 375 | default y if X86 |
David Brownell | 7be2c7c | 2007-02-10 01:46:02 -0800 | [diff] [blame] | 376 | help |
| 377 | Say "yes" here to get direct support for the real time clock |
| 378 | found in every PC or ACPI-based system, and some other boards. |
| 379 | Specifically the original MC146818, compatibles like those in |
| 380 | PC south bridges, the DS12887 or M48T86, some multifunction |
| 381 | or LPC bus chips, and so on. |
| 382 | |
| 383 | Your system will need to define the platform device used by |
| 384 | this driver, otherwise it won't be accessible. This means |
| 385 | you can safely enable this driver if you don't know whether |
| 386 | or not your board has this kind of hardware. |
| 387 | |
| 388 | This driver can also be built as a module. If so, the module |
| 389 | will be called rtc-cmos. |
| 390 | |
Thomas Bogendoerfer | 537739d | 2007-07-17 04:05:06 -0700 | [diff] [blame] | 391 | config RTC_DRV_DS1216 |
| 392 | tristate "Dallas DS1216" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 393 | depends on SNI_RM |
Thomas Bogendoerfer | 537739d | 2007-07-17 04:05:06 -0700 | [diff] [blame] | 394 | help |
| 395 | If you say yes here you get support for the Dallas DS1216 RTC chips. |
| 396 | |
Thomas Bogendoerfer | 5f119f2 | 2008-10-14 17:16:59 +0200 | [diff] [blame] | 397 | config RTC_DRV_DS1286 |
| 398 | tristate "Dallas DS1286" |
| 399 | help |
| 400 | If you say yes here you get support for the Dallas DS1286 RTC chips. |
| 401 | |
Paul Mundt | 739d340 | 2008-02-06 01:38:44 -0800 | [diff] [blame] | 402 | config RTC_DRV_DS1302 |
| 403 | tristate "Dallas DS1302" |
| 404 | depends on SH_SECUREEDGE5410 |
| 405 | help |
| 406 | If you say yes here you get support for the Dallas DS1302 RTC chips. |
| 407 | |
Andrew Sharp | 8f26795 | 2008-02-06 01:38:46 -0800 | [diff] [blame] | 408 | config RTC_DRV_DS1511 |
| 409 | tristate "Dallas DS1511" |
| 410 | depends on RTC_CLASS |
| 411 | help |
| 412 | If you say yes here you get support for the |
| 413 | Dallas DS1511 timekeeping/watchdog chip. |
| 414 | |
| 415 | This driver can also be built as a module. If so, the module |
| 416 | will be called rtc-ds1511. |
| 417 | |
Atsushi Nemoto | 9bf5b4f | 2006-06-25 05:48:28 -0700 | [diff] [blame] | 418 | config RTC_DRV_DS1553 |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 419 | tristate "Maxim/Dallas DS1553" |
Atsushi Nemoto | 9bf5b4f | 2006-06-25 05:48:28 -0700 | [diff] [blame] | 420 | help |
| 421 | If you say yes here you get support for the |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 422 | Maxim/Dallas DS1553 timekeeping chip. |
Atsushi Nemoto | 9bf5b4f | 2006-06-25 05:48:28 -0700 | [diff] [blame] | 423 | |
| 424 | This driver can also be built as a module. If so, the module |
| 425 | will be called rtc-ds1553. |
| 426 | |
Alessandro Zummo | 09b6bdb3b | 2008-02-06 01:38:40 -0800 | [diff] [blame] | 427 | config RTC_DRV_DS1742 |
| 428 | tristate "Maxim/Dallas DS1742/1743" |
| 429 | help |
| 430 | If you say yes here you get support for the |
| 431 | Maxim/Dallas DS1742/1743 timekeeping chip. |
| 432 | |
| 433 | This driver can also be built as a module. If so, the module |
| 434 | will be called rtc-ds1742. |
| 435 | |
Thomas Hommel | 0296411 | 2007-07-21 04:37:58 -0700 | [diff] [blame] | 436 | config RTC_DRV_STK17TA8 |
| 437 | tristate "Simtek STK17TA8" |
| 438 | depends on RTC_CLASS |
| 439 | help |
| 440 | If you say yes here you get support for the |
| 441 | Simtek STK17TA8 timekeeping chip. |
| 442 | |
| 443 | This driver can also be built as a module. If so, the module |
| 444 | will be called rtc-stk17ta8. |
| 445 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 446 | config RTC_DRV_M48T86 |
| 447 | tristate "ST M48T86/Dallas DS12887" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 448 | help |
| 449 | If you say Y here you will get support for the |
| 450 | ST M48T86 and Dallas DS12887 RTC chips. |
| 451 | |
| 452 | This driver can also be built as a module. If so, the module |
| 453 | will be called rtc-m48t86. |
| 454 | |
Thomas Bogendoerfer | d1dbd82e | 2008-10-14 17:17:32 +0200 | [diff] [blame] | 455 | config RTC_DRV_M48T35 |
| 456 | tristate "ST M48T35" |
| 457 | help |
| 458 | If you say Y here you will get support for the |
| 459 | ST M48T35 RTC chip. |
| 460 | |
| 461 | This driver can also be built as a module, if so, the module |
| 462 | will be called "rtc-m48t35". |
| 463 | |
Mark Zhan | 2e774c7 | 2007-07-17 04:05:05 -0700 | [diff] [blame] | 464 | config RTC_DRV_M48T59 |
Krzysztof Helt | 94fe742 | 2008-09-03 15:12:34 -0700 | [diff] [blame] | 465 | tristate "ST M48T59/M48T08/M48T02" |
Mark Zhan | 2e774c7 | 2007-07-17 04:05:05 -0700 | [diff] [blame] | 466 | help |
| 467 | If you say Y here you will get support for the |
Krzysztof Helt | 94fe742 | 2008-09-03 15:12:34 -0700 | [diff] [blame] | 468 | ST M48T59 RTC chip and compatible ST M48T08 and M48T02. |
| 469 | |
| 470 | These chips are usually found in Sun SPARC and UltraSPARC |
| 471 | workstations. |
Mark Zhan | 2e774c7 | 2007-07-17 04:05:05 -0700 | [diff] [blame] | 472 | |
| 473 | This driver can also be built as a module, if so, the module |
| 474 | will be called "rtc-m48t59". |
| 475 | |
David S. Miller | cca4c23 | 2008-08-29 01:29:53 -0700 | [diff] [blame] | 476 | config RTC_DRV_BQ4802 |
| 477 | tristate "TI BQ4802" |
| 478 | help |
| 479 | If you say Y here you will get support for the TI |
| 480 | BQ4802 RTC chip. |
| 481 | |
| 482 | This driver can also be built as a module. If so, the module |
| 483 | will be called rtc-bq4802. |
| 484 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 485 | config RTC_DRV_V3020 |
| 486 | tristate "EM Microelectronic V3020" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 487 | help |
| 488 | If you say yes here you will get support for the |
| 489 | EM Microelectronic v3020 RTC chip. |
| 490 | |
| 491 | This driver can also be built as a module. If so, the module |
| 492 | will be called rtc-v3020. |
| 493 | |
Mark Brown | 077eaf5 | 2008-11-12 13:27:04 -0800 | [diff] [blame] | 494 | config RTC_DRV_WM8350 |
| 495 | tristate "Wolfson Microelectronics WM8350 RTC" |
| 496 | depends on MFD_WM8350 |
| 497 | help |
| 498 | If you say yes here you will get support for the RTC subsystem |
| 499 | of the Wolfson Microelectronics WM8350. |
| 500 | |
| 501 | This driver can also be built as a module. If so, the module |
| 502 | will be called "rtc-wm8350". |
| 503 | |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 504 | comment "on-CPU RTC drivers" |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 505 | |
David Brownell | db68b18 | 2006-12-06 20:38:36 -0800 | [diff] [blame] | 506 | config RTC_DRV_OMAP |
| 507 | tristate "TI OMAP1" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 508 | depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 |
David Brownell | db68b18 | 2006-12-06 20:38:36 -0800 | [diff] [blame] | 509 | help |
| 510 | Say "yes" here to support the real time clock on TI OMAP1 chips. |
| 511 | This driver can also be built as a module called rtc-omap. |
| 512 | |
Ben Dooks | 1add678 | 2006-07-01 04:36:26 -0700 | [diff] [blame] | 513 | config RTC_DRV_S3C |
| 514 | tristate "Samsung S3C series SoC RTC" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 515 | depends on ARCH_S3C2410 |
Ben Dooks | 1add678 | 2006-07-01 04:36:26 -0700 | [diff] [blame] | 516 | help |
| 517 | RTC (Realtime Clock) driver for the clock inbuilt into the |
| 518 | Samsung S3C24XX series of SoCs. This can provide periodic |
| 519 | interrupt rates from 1Hz to 64Hz for user programs, and |
| 520 | wakeup from Alarm. |
| 521 | |
| 522 | The driver currently supports the common features on all the |
| 523 | S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440 |
| 524 | and S3C2442. |
| 525 | |
| 526 | This driver can also be build as a module. If so, the module |
| 527 | will be called rtc-s3c. |
| 528 | |
Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 529 | config RTC_DRV_EP93XX |
| 530 | tristate "Cirrus Logic EP93XX" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 531 | depends on ARCH_EP93XX |
Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 532 | help |
| 533 | If you say yes here you get support for the |
| 534 | RTC embedded in the Cirrus Logic EP93XX processors. |
| 535 | |
| 536 | This driver can also be built as a module. If so, the module |
| 537 | will be called rtc-ep93xx. |
| 538 | |
Richard Purdie | e842f1c | 2006-03-27 01:16:46 -0800 | [diff] [blame] | 539 | config RTC_DRV_SA1100 |
| 540 | tristate "SA11x0/PXA2xx" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 541 | depends on ARCH_SA1100 || ARCH_PXA |
Richard Purdie | e842f1c | 2006-03-27 01:16:46 -0800 | [diff] [blame] | 542 | help |
| 543 | If you say Y here you will get access to the real time clock |
| 544 | built into your SA11x0 or PXA2xx CPU. |
| 545 | |
| 546 | To compile this driver as a module, choose M here: the |
| 547 | module will be called rtc-sa1100. |
Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 548 | |
Paul Mundt | 317a610 | 2006-09-27 17:13:19 +0900 | [diff] [blame] | 549 | config RTC_DRV_SH |
| 550 | tristate "SuperH On-Chip RTC" |
Paul Mundt | ff1b750 | 2007-11-26 17:56:31 +0900 | [diff] [blame] | 551 | depends on RTC_CLASS && SUPERH |
Paul Mundt | 317a610 | 2006-09-27 17:13:19 +0900 | [diff] [blame] | 552 | help |
| 553 | Say Y here to enable support for the on-chip RTC found in |
| 554 | most SuperH processors. |
| 555 | |
| 556 | To compile this driver as a module, choose M here: the |
| 557 | module will be called rtc-sh. |
| 558 | |
Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 559 | config RTC_DRV_VR41XX |
Alessandro Zummo | 3e16f6a | 2006-04-10 22:54:48 -0700 | [diff] [blame] | 560 | tristate "NEC VR41XX" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 561 | depends on CPU_VR41XX |
Alessandro Zummo | 3e16f6a | 2006-04-10 22:54:48 -0700 | [diff] [blame] | 562 | help |
| 563 | If you say Y here you will get access to the real time clock |
| 564 | built into your NEC VR41XX CPU. |
| 565 | |
| 566 | To compile this driver as a module, choose M here: the |
| 567 | module will be called rtc-vr41xx. |
Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 568 | |
Russell King | a190901 | 2008-04-20 12:08:36 +0100 | [diff] [blame] | 569 | config RTC_DRV_PL030 |
| 570 | tristate "ARM AMBA PL030 RTC" |
| 571 | depends on ARM_AMBA |
| 572 | help |
| 573 | If you say Y here you will get access to ARM AMBA |
| 574 | PrimeCell PL030 RTC found on certain ARM SOCs. |
| 575 | |
| 576 | To compile this driver as a module, choose M here: the |
| 577 | module will be called rtc-pl030. |
| 578 | |
Deepak Saxena | 8ae6e16 | 2006-06-25 05:47:38 -0700 | [diff] [blame] | 579 | config RTC_DRV_PL031 |
| 580 | tristate "ARM AMBA PL031 RTC" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 581 | depends on ARM_AMBA |
Deepak Saxena | 8ae6e16 | 2006-06-25 05:47:38 -0700 | [diff] [blame] | 582 | help |
| 583 | If you say Y here you will get access to ARM AMBA |
Alessandro Zummo | 09a21e5 | 2007-05-08 00:33:48 -0700 | [diff] [blame] | 584 | PrimeCell PL031 RTC found on certain ARM SOCs. |
Deepak Saxena | 8ae6e16 | 2006-06-25 05:47:38 -0700 | [diff] [blame] | 585 | |
| 586 | To compile this driver as a module, choose M here: the |
| 587 | module will be called rtc-pl031. |
| 588 | |
Hans-Christian Egtvedt | fa04e78 | 2007-07-17 04:05:00 -0700 | [diff] [blame] | 589 | config RTC_DRV_AT32AP700X |
| 590 | tristate "AT32AP700X series RTC" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 591 | depends on PLATFORM_AT32AP |
Hans-Christian Egtvedt | fa04e78 | 2007-07-17 04:05:00 -0700 | [diff] [blame] | 592 | help |
| 593 | Driver for the internal RTC (Realtime Clock) on Atmel AVR32 |
| 594 | AT32AP700x family processors. |
| 595 | |
Andrew Victor | 7fc39f6 | 2006-12-10 02:19:03 -0800 | [diff] [blame] | 596 | config RTC_DRV_AT91RM9200 |
David Brownell | 4cdf854 | 2008-02-06 01:38:59 -0800 | [diff] [blame] | 597 | tristate "AT91RM9200 or AT91SAM9RL" |
| 598 | depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL |
Andrew Victor | 788b1fc | 2006-06-25 05:48:27 -0700 | [diff] [blame] | 599 | help |
David Brownell | 4cdf854 | 2008-02-06 01:38:59 -0800 | [diff] [blame] | 600 | Driver for the internal RTC (Realtime Clock) module found on |
| 601 | Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips |
| 602 | this is powered by the backup power supply. |
| 603 | |
| 604 | config RTC_DRV_AT91SAM9 |
Stelian Pop | 6b71dbf | 2008-04-05 21:16:15 +0100 | [diff] [blame] | 605 | tristate "AT91SAM9x/AT91CAP9" |
David Brownell | 4cdf854 | 2008-02-06 01:38:59 -0800 | [diff] [blame] | 606 | depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40) |
| 607 | help |
Stelian Pop | 6b71dbf | 2008-04-05 21:16:15 +0100 | [diff] [blame] | 608 | RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT |
| 609 | (Real Time Timer). These timers are powered by the backup power |
| 610 | supply (such as a small coin cell battery), but do not need to |
| 611 | be used as RTCs. |
David Brownell | 4cdf854 | 2008-02-06 01:38:59 -0800 | [diff] [blame] | 612 | |
| 613 | (On AT91SAM9rl chips you probably want to use the dedicated RTC |
| 614 | module and leave the RTT available for other uses.) |
| 615 | |
| 616 | config RTC_DRV_AT91SAM9_RTT |
| 617 | int |
| 618 | range 0 1 |
| 619 | default 0 |
| 620 | prompt "RTT module Number" if ARCH_AT91SAM9263 |
| 621 | depends on RTC_DRV_AT91SAM9 |
| 622 | help |
| 623 | More than one RTT module is available. You can choose which |
| 624 | one will be used as an RTC. The default of zero is normally |
| 625 | OK to use, though some systems use that for non-RTC purposes. |
| 626 | |
| 627 | config RTC_DRV_AT91SAM9_GPBR |
| 628 | int |
| 629 | range 0 3 if !ARCH_AT91SAM9263 |
| 630 | range 0 15 if ARCH_AT91SAM9263 |
| 631 | default 0 |
| 632 | prompt "Backup Register Number" |
| 633 | depends on RTC_DRV_AT91SAM9 |
| 634 | help |
| 635 | The RTC driver needs to use one of the General Purpose Backup |
| 636 | Registers (GPBRs) as well as the RTT. You can choose which one |
| 637 | will be used. The default of zero is normally OK to use, but |
| 638 | on some systems other software needs to use that register. |
Andrew Victor | 788b1fc | 2006-06-25 05:48:27 -0700 | [diff] [blame] | 639 | |
Wu, Bryan | 8cc75c9 | 2007-05-06 14:50:32 -0700 | [diff] [blame] | 640 | config RTC_DRV_BFIN |
| 641 | tristate "Blackfin On-Chip RTC" |
Graf Yang | 7f60459 | 2008-08-20 14:09:02 -0700 | [diff] [blame] | 642 | depends on BLACKFIN && !BF561 |
Wu, Bryan | 8cc75c9 | 2007-05-06 14:50:32 -0700 | [diff] [blame] | 643 | help |
| 644 | If you say yes here you will get support for the |
| 645 | Blackfin On-Chip Real Time Clock. |
| 646 | |
| 647 | This driver can also be built as a module. If so, the module |
| 648 | will be called rtc-bfin. |
| 649 | |
Nobuhiro Iwamatsu | e9f2bd8 | 2007-05-08 00:26:37 -0700 | [diff] [blame] | 650 | config RTC_DRV_RS5C313 |
| 651 | tristate "Ricoh RS5C313" |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 652 | depends on SH_LANDISK |
Nobuhiro Iwamatsu | e9f2bd8 | 2007-05-08 00:26:37 -0700 | [diff] [blame] | 653 | help |
| 654 | If you say yes here you get support for the Ricoh RS5C313 RTC chips. |
| 655 | |
Kyle McMartin | 9eb1686 | 2008-09-10 14:24:07 +0000 | [diff] [blame] | 656 | config RTC_DRV_PARISC |
| 657 | tristate "PA-RISC firmware RTC support" |
| 658 | depends on PARISC |
| 659 | help |
| 660 | Say Y or M here to enable RTC support on PA-RISC systems using |
| 661 | firmware calls. If you do not know what you are doing, you should |
| 662 | just say Y. |
| 663 | |
David Woodhouse | aabe188 | 2008-06-05 22:46:50 -0700 | [diff] [blame] | 664 | config RTC_DRV_PPC |
| 665 | tristate "PowerPC machine dependent RTC support" |
Kumar Gala | 0327457 | 2008-10-15 22:03:06 -0700 | [diff] [blame] | 666 | depends on PPC |
David Woodhouse | aabe188 | 2008-06-05 22:46:50 -0700 | [diff] [blame] | 667 | help |
| 668 | The PowerPC kernel has machine-specific functions for accessing |
| 669 | the RTC. This exposes that functionality through the generic RTC |
| 670 | class. |
| 671 | |
David S. Miller | 7a138ed | 2008-08-29 01:32:43 -0700 | [diff] [blame] | 672 | config RTC_DRV_SUN4V |
| 673 | bool "SUN4V Hypervisor RTC" |
| 674 | depends on SPARC64 |
| 675 | help |
| 676 | If you say Y here you will get support for the Hypervisor |
| 677 | based RTC on SUN4V systems. |
| 678 | |
David S. Miller | de2cf33 | 2008-08-28 23:02:36 -0700 | [diff] [blame] | 679 | config RTC_DRV_STARFIRE |
| 680 | bool "Starfire RTC" |
| 681 | depends on SPARC64 |
| 682 | help |
| 683 | If you say Y here you will get support for the RTC found on |
| 684 | Starfire systems. |
| 685 | |
Jan Engelhardt | bb35fb2 | 2007-07-31 00:39:46 -0700 | [diff] [blame] | 686 | endif # RTC_CLASS |