| 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 |  | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 76 | comment "RTC drivers" | 
|  | 77 | depends on RTC_CLASS | 
|  | 78 |  | 
| Alessandro Zummo | 1fec7c6 | 2006-03-27 01:16:42 -0800 | [diff] [blame] | 79 | config RTC_DRV_X1205 | 
|  | 80 | tristate "Xicor/Intersil X1205" | 
|  | 81 | depends on RTC_CLASS && I2C | 
|  | 82 | help | 
|  | 83 | If you say yes here you get support for the | 
|  | 84 | Xicor/Intersil X1205 RTC chip. | 
|  | 85 |  | 
|  | 86 | This driver can also be built as a module. If so, the module | 
|  | 87 | will be called rtc-x1205. | 
|  | 88 |  | 
| David Brownell | 1abb0dc | 2006-06-25 05:48:17 -0700 | [diff] [blame^] | 89 | config RTC_DRV_DS1307 | 
|  | 90 | tristate "Dallas/Maxim DS1307 and similar I2C RTC chips" | 
|  | 91 | depends on RTC_CLASS && I2C | 
|  | 92 | help | 
|  | 93 | If you say yes here you get support for various compatible RTC | 
|  | 94 | chips (often with battery backup) connected with I2C.  This driver | 
|  | 95 | should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00, | 
|  | 96 | and probably other chips.  In some cases the RTC must already | 
|  | 97 | have been initialized (by manufacturing or a bootloader). | 
|  | 98 |  | 
|  | 99 | The first seven registers on these chips hold an RTC, and other | 
|  | 100 | registers may add features such as NVRAM, a trickle charger for | 
|  | 101 | the RTC/NVRAM backup power, and alarms.  This driver may not | 
|  | 102 | expose all those available chip features. | 
|  | 103 |  | 
|  | 104 | This driver can also be built as a module. If so, the module | 
|  | 105 | will be called rtc-ds1307. | 
|  | 106 |  | 
| Alessandro Zummo | edf1aaa | 2006-03-27 01:16:43 -0800 | [diff] [blame] | 107 | config RTC_DRV_DS1672 | 
|  | 108 | tristate "Dallas/Maxim DS1672" | 
|  | 109 | depends on RTC_CLASS && I2C | 
|  | 110 | help | 
|  | 111 | If you say yes here you get support for the | 
|  | 112 | Dallas/Maxim DS1672 timekeeping chip. | 
|  | 113 |  | 
|  | 114 | This driver can also be built as a module. If so, the module | 
|  | 115 | will be called rtc-ds1672. | 
|  | 116 |  | 
| Alessandro Zummo | b5a82d6 | 2006-03-27 01:16:44 -0800 | [diff] [blame] | 117 | config RTC_DRV_PCF8563 | 
|  | 118 | tristate "Philips PCF8563/Epson RTC8564" | 
|  | 119 | depends on RTC_CLASS && I2C | 
|  | 120 | help | 
|  | 121 | If you say yes here you get support for the | 
|  | 122 | Philips PCF8563 RTC chip. The Epson RTC8564 | 
|  | 123 | should work as well. | 
|  | 124 |  | 
|  | 125 | This driver can also be built as a module. If so, the module | 
|  | 126 | will be called rtc-pcf8563. | 
|  | 127 |  | 
| Alessandro Zummo | 7520b94 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 128 | config RTC_DRV_RS5C372 | 
|  | 129 | tristate "Ricoh RS5C372A/B" | 
|  | 130 | depends on RTC_CLASS && I2C | 
|  | 131 | help | 
|  | 132 | If you say yes here you get support for the | 
|  | 133 | Ricoh RS5C372A and RS5C372B RTC chips. | 
|  | 134 |  | 
|  | 135 | This driver can also be built as a module. If so, the module | 
|  | 136 | will be called rtc-rs5c372. | 
|  | 137 |  | 
| Alessandro Zummo | 1d98af8 | 2006-03-27 01:16:47 -0800 | [diff] [blame] | 138 | config RTC_DRV_M48T86 | 
|  | 139 | tristate "ST M48T86/Dallas DS12887" | 
|  | 140 | depends on RTC_CLASS | 
|  | 141 | help | 
|  | 142 | If you say Y here you will get support for the | 
|  | 143 | ST M48T86 and Dallas DS12887 RTC chips. | 
|  | 144 |  | 
|  | 145 | This driver can also be built as a module. If so, the module | 
|  | 146 | will be called rtc-m48t86. | 
|  | 147 |  | 
| Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 148 | config RTC_DRV_EP93XX | 
|  | 149 | tristate "Cirrus Logic EP93XX" | 
|  | 150 | depends on RTC_CLASS && ARCH_EP93XX | 
|  | 151 | help | 
|  | 152 | If you say yes here you get support for the | 
|  | 153 | RTC embedded in the Cirrus Logic EP93XX processors. | 
|  | 154 |  | 
|  | 155 | This driver can also be built as a module. If so, the module | 
|  | 156 | will be called rtc-ep93xx. | 
|  | 157 |  | 
| Richard Purdie | e842f1c | 2006-03-27 01:16:46 -0800 | [diff] [blame] | 158 | config RTC_DRV_SA1100 | 
|  | 159 | tristate "SA11x0/PXA2xx" | 
|  | 160 | depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA) | 
|  | 161 | help | 
|  | 162 | If you say Y here you will get access to the real time clock | 
|  | 163 | built into your SA11x0 or PXA2xx CPU. | 
|  | 164 |  | 
|  | 165 | To compile this driver as a module, choose M here: the | 
|  | 166 | module will be called rtc-sa1100. | 
| Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 167 |  | 
| Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 168 | config RTC_DRV_VR41XX | 
| Alessandro Zummo | 3e16f6a | 2006-04-10 22:54:48 -0700 | [diff] [blame] | 169 | tristate "NEC VR41XX" | 
| Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 170 | depends on RTC_CLASS && CPU_VR41XX | 
| Alessandro Zummo | 3e16f6a | 2006-04-10 22:54:48 -0700 | [diff] [blame] | 171 | help | 
|  | 172 | If you say Y here you will get access to the real time clock | 
|  | 173 | built into your NEC VR41XX CPU. | 
|  | 174 |  | 
|  | 175 | To compile this driver as a module, choose M here: the | 
|  | 176 | module will be called rtc-vr41xx. | 
| Yoichi Yuasa | 8417eb7 | 2006-04-10 22:54:47 -0700 | [diff] [blame] | 177 |  | 
| Deepak Saxena | 8ae6e16 | 2006-06-25 05:47:38 -0700 | [diff] [blame] | 178 | config RTC_DRV_PL031 | 
|  | 179 | tristate "ARM AMBA PL031 RTC" | 
|  | 180 | depends on RTC_CLASS && ARM_AMBA | 
|  | 181 | help | 
|  | 182 | If you say Y here you will get access to ARM AMBA | 
|  | 183 | PrimeCell PL031 UART found on certain ARM SOCs. | 
|  | 184 |  | 
|  | 185 | To compile this driver as a module, choose M here: the | 
|  | 186 | module will be called rtc-pl031. | 
|  | 187 |  | 
| Alessandro Zummo | a95579c | 2006-03-27 01:16:42 -0800 | [diff] [blame] | 188 | config RTC_DRV_TEST | 
|  | 189 | tristate "Test driver/device" | 
|  | 190 | depends on RTC_CLASS | 
|  | 191 | help | 
|  | 192 | If you say yes here you get support for the | 
|  | 193 | RTC test driver. It's a software RTC which can be | 
|  | 194 | used to test the RTC subsystem APIs. It gets | 
|  | 195 | the time from the system clock. | 
|  | 196 | You want this driver only if you are doing development | 
|  | 197 | on the RTC subsystem. Please read the source code | 
|  | 198 | for further details. | 
|  | 199 |  | 
|  | 200 | This driver can also be built as a module. If so, the module | 
|  | 201 | will be called rtc-test. | 
|  | 202 |  | 
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 203 | endmenu |