diff options
Diffstat (limited to 'drivers/i2c/chips/Kconfig')
-rw-r--r-- | drivers/i2c/chips/Kconfig | 443 |
1 files changed, 443 insertions, 0 deletions
diff --git a/drivers/i2c/chips/Kconfig b/drivers/i2c/chips/Kconfig new file mode 100644 index 000000000000..74d23cfce2a3 --- /dev/null +++ b/drivers/i2c/chips/Kconfig | |||
@@ -0,0 +1,443 @@ | |||
1 | # | ||
2 | # I2C Sensor device configuration | ||
3 | # | ||
4 | |||
5 | menu "Hardware Sensors Chip support" | ||
6 | depends on I2C | ||
7 | |||
8 | config I2C_SENSOR | ||
9 | tristate | ||
10 | default n | ||
11 | |||
12 | config SENSORS_ADM1021 | ||
13 | tristate "Analog Devices ADM1021 and compatibles" | ||
14 | depends on I2C && EXPERIMENTAL | ||
15 | select I2C_SENSOR | ||
16 | help | ||
17 | If you say yes here you get support for Analog Devices ADM1021 | ||
18 | and ADM1023 sensor chips and clones: Maxim MAX1617 and MAX1617A, | ||
19 | Genesys Logic GL523SM, National Semiconductor LM84, TI THMC10, | ||
20 | and the XEON processor built-in sensor. | ||
21 | |||
22 | This driver can also be built as a module. If so, the module | ||
23 | will be called adm1021. | ||
24 | |||
25 | config SENSORS_ADM1025 | ||
26 | tristate "Analog Devices ADM1025 and compatibles" | ||
27 | depends on I2C && EXPERIMENTAL | ||
28 | select I2C_SENSOR | ||
29 | help | ||
30 | If you say yes here you get support for Analog Devices ADM1025 | ||
31 | and Philips NE1619 sensor chips. | ||
32 | This driver can also be built as a module. If so, the module | ||
33 | will be called adm1025. | ||
34 | |||
35 | config SENSORS_ADM1026 | ||
36 | tristate "Analog Devices ADM1026 and compatibles" | ||
37 | depends on I2C && EXPERIMENTAL | ||
38 | select I2C_SENSOR | ||
39 | help | ||
40 | If you say yes here you get support for Analog Devices ADM1026 | ||
41 | This driver can also be built as a module. If so, the module | ||
42 | will be called adm1026. | ||
43 | |||
44 | config SENSORS_ADM1031 | ||
45 | tristate "Analog Devices ADM1031 and compatibles" | ||
46 | depends on I2C && EXPERIMENTAL | ||
47 | select I2C_SENSOR | ||
48 | help | ||
49 | If you say yes here you get support for Analog Devices ADM1031 | ||
50 | and ADM1030 sensor chips. | ||
51 | This driver can also be built as a module. If so, the module | ||
52 | will be called adm1031. | ||
53 | |||
54 | config SENSORS_ASB100 | ||
55 | tristate "Asus ASB100 Bach" | ||
56 | depends on I2C && EXPERIMENTAL | ||
57 | select I2C_SENSOR | ||
58 | help | ||
59 | If you say yes here you get support for the ASB100 Bach sensor | ||
60 | chip found on some Asus mainboards. | ||
61 | |||
62 | This driver can also be built as a module. If so, the module | ||
63 | will be called asb100. | ||
64 | |||
65 | config SENSORS_DS1621 | ||
66 | tristate "Dallas Semiconductor DS1621 and DS1625" | ||
67 | depends on I2C && EXPERIMENTAL | ||
68 | select I2C_SENSOR | ||
69 | help | ||
70 | If you say yes here you get support for Dallas Semiconductor | ||
71 | DS1621 and DS1625 sensor chips. | ||
72 | |||
73 | This driver can also be built as a module. If so, the module | ||
74 | will be called ds1621. | ||
75 | |||
76 | config SENSORS_FSCHER | ||
77 | tristate "FSC Hermes" | ||
78 | depends on I2C && EXPERIMENTAL | ||
79 | select I2C_SENSOR | ||
80 | help | ||
81 | If you say yes here you get support for Fujitsu Siemens | ||
82 | Computers Hermes sensor chips. | ||
83 | |||
84 | This driver can also be built as a module. If so, the module | ||
85 | will be called fscher. | ||
86 | |||
87 | config SENSORS_FSCPOS | ||
88 | tristate "FSC Poseidon" | ||
89 | depends on I2C && EXPERIMENTAL | ||
90 | select I2C_SENSOR | ||
91 | help | ||
92 | If you say yes here you get support for Fujitsu Siemens | ||
93 | Computers Poseidon sensor chips. | ||
94 | |||
95 | This driver can also be built as a module. If so, the module | ||
96 | will be called fscpos. | ||
97 | |||
98 | config SENSORS_GL518SM | ||
99 | tristate "Genesys Logic GL518SM" | ||
100 | depends on I2C && EXPERIMENTAL | ||
101 | select I2C_SENSOR | ||
102 | help | ||
103 | If you say yes here you get support for Genesys Logic GL518SM | ||
104 | sensor chips. | ||
105 | |||
106 | This driver can also be built as a module. If so, the module | ||
107 | will be called gl518sm. | ||
108 | |||
109 | config SENSORS_GL520SM | ||
110 | tristate "Genesys Logic GL520SM" | ||
111 | depends on I2C && EXPERIMENTAL | ||
112 | select I2C_SENSOR | ||
113 | help | ||
114 | If you say yes here you get support for Genesys Logic GL520SM | ||
115 | sensor chips. | ||
116 | |||
117 | This driver can also be built as a module. If so, the module | ||
118 | will be called gl520sm. | ||
119 | |||
120 | config SENSORS_IT87 | ||
121 | tristate "ITE IT87xx and compatibles" | ||
122 | depends on I2C && EXPERIMENTAL | ||
123 | select I2C_SENSOR | ||
124 | help | ||
125 | If you say yes here you get support for ITE IT87xx sensor chips | ||
126 | and clones: SiS960. | ||
127 | |||
128 | This driver can also be built as a module. If so, the module | ||
129 | will be called it87. | ||
130 | |||
131 | config SENSORS_LM63 | ||
132 | tristate "National Semiconductor LM63" | ||
133 | depends on I2C && EXPERIMENTAL | ||
134 | select I2C_SENSOR | ||
135 | help | ||
136 | If you say yes here you get support for the National Semiconductor | ||
137 | LM63 remote diode digital temperature sensor with integrated fan | ||
138 | control. Such chips are found on the Tyan S4882 (Thunder K8QS Pro) | ||
139 | motherboard, among others. | ||
140 | |||
141 | This driver can also be built as a module. If so, the module | ||
142 | will be called lm63. | ||
143 | |||
144 | config SENSORS_LM75 | ||
145 | tristate "National Semiconductor LM75 and compatibles" | ||
146 | depends on I2C && EXPERIMENTAL | ||
147 | select I2C_SENSOR | ||
148 | help | ||
149 | If you say yes here you get support for National Semiconductor LM75 | ||
150 | sensor chips and clones: Dallas Semiconductor DS75 and DS1775 (in | ||
151 | 9-bit precision mode), and TelCom (now Microchip) TCN75. | ||
152 | |||
153 | The DS75 and DS1775 in 10- to 12-bit precision modes will require | ||
154 | a force module parameter. The driver will not handle the extra | ||
155 | precision anyhow. | ||
156 | |||
157 | This driver can also be built as a module. If so, the module | ||
158 | will be called lm75. | ||
159 | |||
160 | config SENSORS_LM77 | ||
161 | tristate "National Semiconductor LM77" | ||
162 | depends on I2C && EXPERIMENTAL | ||
163 | select I2C_SENSOR | ||
164 | help | ||
165 | If you say yes here you get support for National Semiconductor LM77 | ||
166 | sensor chips. | ||
167 | |||
168 | This driver can also be built as a module. If so, the module | ||
169 | will be called lm77. | ||
170 | |||
171 | config SENSORS_LM78 | ||
172 | tristate "National Semiconductor LM78 and compatibles" | ||
173 | depends on I2C && EXPERIMENTAL | ||
174 | select I2C_SENSOR | ||
175 | help | ||
176 | If you say yes here you get support for National Semiconductor LM78, | ||
177 | LM78-J and LM79. This can also be built as a module which can be | ||
178 | inserted and removed while the kernel is running. | ||
179 | |||
180 | This driver can also be built as a module. If so, the module | ||
181 | will be called lm78. | ||
182 | |||
183 | config SENSORS_LM80 | ||
184 | tristate "National Semiconductor LM80" | ||
185 | depends on I2C && EXPERIMENTAL | ||
186 | select I2C_SENSOR | ||
187 | help | ||
188 | If you say yes here you get support for National Semiconductor | ||
189 | LM80 sensor chips. | ||
190 | |||
191 | This driver can also be built as a module. If so, the module | ||
192 | will be called lm80. | ||
193 | |||
194 | config SENSORS_LM83 | ||
195 | tristate "National Semiconductor LM83" | ||
196 | depends on I2C | ||
197 | select I2C_SENSOR | ||
198 | help | ||
199 | If you say yes here you get support for National Semiconductor | ||
200 | LM83 sensor chips. | ||
201 | |||
202 | This driver can also be built as a module. If so, the module | ||
203 | will be called lm83. | ||
204 | |||
205 | config SENSORS_LM85 | ||
206 | tristate "National Semiconductor LM85 and compatibles" | ||
207 | depends on I2C && EXPERIMENTAL | ||
208 | select I2C_SENSOR | ||
209 | help | ||
210 | If you say yes here you get support for National Semiconductor LM85 | ||
211 | sensor chips and clones: ADT7463 and ADM1027. | ||
212 | |||
213 | This driver can also be built as a module. If so, the module | ||
214 | will be called lm85. | ||
215 | |||
216 | config SENSORS_LM87 | ||
217 | tristate "National Semiconductor LM87" | ||
218 | depends on I2C && EXPERIMENTAL | ||
219 | select I2C_SENSOR | ||
220 | help | ||
221 | If you say yes here you get support for National Semiconductor LM87 | ||
222 | sensor chips. | ||
223 | |||
224 | This driver can also be built as a module. If so, the module | ||
225 | will be called lm87. | ||
226 | |||
227 | config SENSORS_LM90 | ||
228 | tristate "National Semiconductor LM90 and compatibles" | ||
229 | depends on I2C | ||
230 | select I2C_SENSOR | ||
231 | help | ||
232 | If you say yes here you get support for National Semiconductor LM90, | ||
233 | LM86, LM89 and LM99, Analog Devices ADM1032 and Maxim MAX6657 and | ||
234 | MAX6658 sensor chips. | ||
235 | |||
236 | The Analog Devices ADT7461 sensor chip is also supported, but only | ||
237 | if found in ADM1032 compatibility mode. | ||
238 | |||
239 | This driver can also be built as a module. If so, the module | ||
240 | will be called lm90. | ||
241 | |||
242 | config SENSORS_LM92 | ||
243 | tristate "National Semiconductor LM92 and compatibles" | ||
244 | depends on I2C && EXPERIMENTAL | ||
245 | select I2C_SENSOR | ||
246 | help | ||
247 | If you say yes here you get support for National Semiconductor LM92 | ||
248 | and Maxim MAX6635 sensor chips. | ||
249 | |||
250 | This driver can also be built as a module. If so, the module | ||
251 | will be called lm92. | ||
252 | |||
253 | config SENSORS_MAX1619 | ||
254 | tristate "Maxim MAX1619 sensor chip" | ||
255 | depends on I2C && EXPERIMENTAL | ||
256 | select I2C_SENSOR | ||
257 | help | ||
258 | If you say yes here you get support for MAX1619 sensor chip. | ||
259 | |||
260 | This driver can also be built as a module. If so, the module | ||
261 | will be called max1619. | ||
262 | |||
263 | config SENSORS_PC87360 | ||
264 | tristate "National Semiconductor PC87360 family" | ||
265 | depends on I2C && EXPERIMENTAL | ||
266 | select I2C_SENSOR | ||
267 | select I2C_ISA | ||
268 | help | ||
269 | If you say yes here you get access to the hardware monitoring | ||
270 | functions of the National Semiconductor PC8736x Super-I/O chips. | ||
271 | The PC87360, PC87363 and PC87364 only have fan monitoring and | ||
272 | control. The PC87365 and PC87366 additionally have voltage and | ||
273 | temperature monitoring. | ||
274 | |||
275 | This driver can also be built as a module. If so, the module | ||
276 | will be called pc87360. | ||
277 | |||
278 | config SENSORS_SMSC47B397 | ||
279 | tristate "SMSC LPC47B397-NC" | ||
280 | depends on I2C && EXPERIMENTAL | ||
281 | select I2C_SENSOR | ||
282 | select I2C_ISA | ||
283 | help | ||
284 | If you say yes here you get support for the SMSC LPC47B397-NC | ||
285 | sensor chip. | ||
286 | |||
287 | This driver can also be built as a module. If so, the module | ||
288 | will be called smsc47b397. | ||
289 | |||
290 | config SENSORS_SIS5595 | ||
291 | tristate "Silicon Integrated Systems Corp. SiS5595" | ||
292 | depends on I2C && PCI && EXPERIMENTAL | ||
293 | select I2C_SENSOR | ||
294 | select I2C_ISA | ||
295 | help | ||
296 | If you say yes here you get support for the integrated sensors in | ||
297 | SiS5595 South Bridges. | ||
298 | |||
299 | This driver can also be built as a module. If so, the module | ||
300 | will be called sis5595. | ||
301 | |||
302 | config SENSORS_SMSC47M1 | ||
303 | tristate "SMSC LPC47M10x and compatibles" | ||
304 | depends on I2C && EXPERIMENTAL | ||
305 | select I2C_SENSOR | ||
306 | select I2C_ISA | ||
307 | help | ||
308 | If you say yes here you get support for the integrated fan | ||
309 | monitoring and control capabilities of the SMSC LPC47B27x, | ||
310 | LPC47M10x, LPC47M13x and LPC47M14x chips. | ||
311 | |||
312 | This driver can also be built as a module. If so, the module | ||
313 | will be called smsc47m1. | ||
314 | |||
315 | config SENSORS_VIA686A | ||
316 | tristate "VIA686A" | ||
317 | depends on I2C && PCI && EXPERIMENTAL | ||
318 | select I2C_SENSOR | ||
319 | select I2C_ISA | ||
320 | help | ||
321 | If you say yes here you get support for the integrated sensors in | ||
322 | Via 686A/B South Bridges. | ||
323 | |||
324 | This driver can also be built as a module. If so, the module | ||
325 | will be called via686a. | ||
326 | |||
327 | config SENSORS_W83781D | ||
328 | tristate "Winbond W83781D, W83782D, W83783S, W83627HF, Asus AS99127F" | ||
329 | depends on I2C && EXPERIMENTAL | ||
330 | select I2C_SENSOR | ||
331 | help | ||
332 | If you say yes here you get support for the Winbond W8378x series | ||
333 | of sensor chips: the W83781D, W83782D, W83783S and W83627HF, | ||
334 | and the similar Asus AS99127F. | ||
335 | |||
336 | This driver can also be built as a module. If so, the module | ||
337 | will be called w83781d. | ||
338 | |||
339 | config SENSORS_W83L785TS | ||
340 | tristate "Winbond W83L785TS-S" | ||
341 | depends on I2C && EXPERIMENTAL | ||
342 | select I2C_SENSOR | ||
343 | help | ||
344 | If you say yes here you get support for the Winbond W83L785TS-S | ||
345 | sensor chip, which is used on the Asus A7N8X, among other | ||
346 | motherboards. | ||
347 | |||
348 | This driver can also be built as a module. If so, the module | ||
349 | will be called w83l785ts. | ||
350 | |||
351 | config SENSORS_W83627HF | ||
352 | tristate "Winbond W83627HF, W83627THF, W83637HF, W83697HF" | ||
353 | depends on I2C && EXPERIMENTAL | ||
354 | select I2C_SENSOR | ||
355 | select I2C_ISA | ||
356 | help | ||
357 | If you say yes here you get support for the Winbond W836X7 series | ||
358 | of sensor chips: the W83627HF, W83627THF, W83637HF, and the W83697HF | ||
359 | |||
360 | This driver can also be built as a module. If so, the module | ||
361 | will be called w83627hf. | ||
362 | |||
363 | endmenu | ||
364 | |||
365 | menu "Other I2C Chip support" | ||
366 | depends on I2C | ||
367 | |||
368 | config SENSORS_DS1337 | ||
369 | tristate "Dallas Semiconductor DS1337 Real Time Clock" | ||
370 | depends on I2C && EXPERIMENTAL | ||
371 | select I2C_SENSOR | ||
372 | help | ||
373 | If you say yes here you get support for Dallas Semiconductor | ||
374 | DS1337 real-time clock chips. | ||
375 | |||
376 | This driver can also be built as a module. If so, the module | ||
377 | will be called ds1337. | ||
378 | |||
379 | config SENSORS_EEPROM | ||
380 | tristate "EEPROM reader" | ||
381 | depends on I2C && EXPERIMENTAL | ||
382 | select I2C_SENSOR | ||
383 | help | ||
384 | If you say yes here you get read-only access to the EEPROM data | ||
385 | available on modern memory DIMMs and Sony Vaio laptops. Such | ||
386 | EEPROMs could theoretically be available on other devices as well. | ||
387 | |||
388 | This driver can also be built as a module. If so, the module | ||
389 | will be called eeprom. | ||
390 | |||
391 | config SENSORS_PCF8574 | ||
392 | tristate "Philips PCF8574 and PCF8574A" | ||
393 | depends on I2C && EXPERIMENTAL | ||
394 | select I2C_SENSOR | ||
395 | help | ||
396 | If you say yes here you get support for Philips PCF8574 and | ||
397 | PCF8574A chips. | ||
398 | |||
399 | This driver can also be built as a module. If so, the module | ||
400 | will be called pcf8574. | ||
401 | |||
402 | config SENSORS_PCF8591 | ||
403 | tristate "Philips PCF8591" | ||
404 | depends on I2C && EXPERIMENTAL | ||
405 | select I2C_SENSOR | ||
406 | help | ||
407 | If you say yes here you get support for Philips PCF8591 chips. | ||
408 | |||
409 | This driver can also be built as a module. If so, the module | ||
410 | will be called pcf8591. | ||
411 | |||
412 | config SENSORS_RTC8564 | ||
413 | tristate "Epson 8564 RTC chip" | ||
414 | depends on I2C && EXPERIMENTAL | ||
415 | select I2C_SENSOR | ||
416 | help | ||
417 | If you say yes here you get support for the Epson 8564 RTC chip. | ||
418 | |||
419 | This driver can also be built as a module. If so, the module | ||
420 | will be called i2c-rtc8564. | ||
421 | |||
422 | config ISP1301_OMAP | ||
423 | tristate "Philips ISP1301 with OMAP OTG" | ||
424 | depends on I2C && ARCH_OMAP_OTG | ||
425 | help | ||
426 | If you say yes here you get support for the Philips ISP1301 | ||
427 | USB-On-The-Go transceiver working with the OMAP OTG controller. | ||
428 | The ISP1301 is used in products including H2 and H3 development | ||
429 | boards for Texas Instruments OMAP processors. | ||
430 | |||
431 | This driver can also be built as a module. If so, the module | ||
432 | will be called isp1301_omap. | ||
433 | |||
434 | config SENSORS_M41T00 | ||
435 | tristate "ST M41T00 RTC chip" | ||
436 | depends on I2C && PPC32 | ||
437 | help | ||
438 | If you say yes here you get support for the ST M41T00 RTC chip. | ||
439 | |||
440 | This driver can also be built as a module. If so, the module | ||
441 | will be called m41t00. | ||
442 | |||
443 | endmenu | ||