2 # Miscellaneous I2C chip drivers configuration
5 menu "Miscellaneous I2C Chip support"
8 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
9 depends on EXPERIMENTAL
11 If you say yes here you get support for Dallas Semiconductor
12 DS1682 Total Elapsed Time Recorder.
14 This driver can also be built as a module. If so, the module
15 will be called ds1682.
18 tristate "EEPROMs from most vendors"
19 depends on SYSFS && EXPERIMENTAL
21 Enable this driver to get read/write support to most I2C EEPROMs,
22 after you configure the driver to know about each EEPROM on
23 your target board. Use these generic chip names, instead of
24 vendor-specific ones like at24c64 or 24lc02:
26 24c00, 24c01, 24c02, spd (readonly 24c02), 24c04, 24c08,
27 24c16, 24c32, 24c64, 24c128, 24c256, 24c512, 24c1024
29 Unless you like data loss puzzles, always be sure that any chip
30 you configure as a 24c32 (32 kbit) or larger is NOT really a
31 24c16 (16 kbit) or smaller, and vice versa. Marking the chip
32 as read-only won't help recover from this. Also, if your chip
33 has any software write-protect mechanism you may want to review the
34 code to make sure this driver won't turn it on by accident.
36 If you use this with an SMBus adapter instead of an I2C adapter,
37 full functionality is not available. Only smaller devices are
38 supported (24c16 and below, max 4 kByte).
40 This driver can also be built as a module. If so, the module
44 tristate "EEPROM reader"
45 depends on EXPERIMENTAL
47 If you say yes here you get read-only access to the EEPROM data
48 available on modern memory DIMMs and Sony Vaio laptops. Such
49 EEPROMs could theoretically be available on other devices as well.
51 This driver can also be built as a module. If so, the module
52 will be called eeprom.
54 config SENSORS_PCF8574
55 tristate "Philips PCF8574 and PCF8574A (DEPRECATED)"
56 depends on EXPERIMENTAL && GPIO_PCF857X = "n"
59 If you say yes here you get support for Philips PCF8574 and
60 PCF8574A chips. These chips are 8-bit I/O expanders for the I2C bus.
62 This driver can also be built as a module. If so, the module
63 will be called pcf8574.
65 This driver is deprecated and will be dropped soon. Use
66 drivers/gpio/pcf857x.c instead.
68 These devices are hard to detect and rarely found on mainstream
69 hardware. If unsure, say N.
72 tristate "Philips PCF8575 (DEPRECATED)"
74 depends on GPIO_PCF857X = "n"
76 If you say yes here you get support for Philips PCF8575 chip.
77 This chip is a 16-bit I/O expander for the I2C bus. Several other
78 chip manufacturers sell equivalent chips, e.g. Texas Instruments.
80 This driver can also be built as a module. If so, the module
81 will be called pcf8575.
83 This driver is deprecated and will be dropped soon. Use
84 drivers/gpio/pcf857x.c instead.
86 This device is hard to detect and is rarely found on mainstream
87 hardware. If unsure, say N.
89 config SENSORS_PCA9539
90 tristate "Philips PCA9539 16-bit I/O port (DEPRECATED)"
91 depends on EXPERIMENTAL && GPIO_PCA953X = "n"
93 If you say yes here you get support for the Philips PCA9539
96 This driver can also be built as a module. If so, the module
97 will be called pca9539.
99 This driver is deprecated and will be dropped soon. Use
100 drivers/gpio/pca953x.c instead.
102 config SENSORS_PCF8591
103 tristate "Philips PCF8591"
104 depends on EXPERIMENTAL
107 If you say yes here you get support for Philips PCF8591 chips.
109 This driver can also be built as a module. If so, the module
110 will be called pcf8591.
112 These devices are hard to detect and rarely found on mainstream
113 hardware. If unsure, say N.
116 tristate "Philips ISP1301 with OMAP OTG"
117 depends on ARCH_OMAP_OTG
119 If you say yes here you get support for the Philips ISP1301
120 USB-On-The-Go transceiver working with the OMAP OTG controller.
121 The ISP1301 is used in products including H2 and H3 development
122 boards for Texas Instruments OMAP processors.
124 This driver can also be built as a module. If so, the module
125 will be called isp1301_omap.
128 tristate "TPS6501x Power Management chips"
130 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
132 If you say yes here you get support for the TPS6501x series of
133 Power Management chips. These include voltage regulators,
134 lithium ion/polymer battery charging, and other features that
135 are often used in portable devices like cell phones and cameras.
137 This driver can also be built as a module. If so, the module
138 will be called tps65010.
140 config SENSORS_MAX6875
141 tristate "Maxim MAX6875 Power supply supervisor"
142 depends on EXPERIMENTAL
144 If you say yes here you get support for the Maxim MAX6875
145 EEPROM-programmable, quad power-supply sequencer/supervisor.
147 This provides an interface to program the EEPROM and reset the chip.
149 This driver also supports the Maxim MAX6874 hex power-supply
150 sequencer/supervisor if found at a compatible address.
152 This driver can also be built as a module. If so, the module
153 will be called max6875.
155 config SENSORS_TSL2550
156 tristate "Taos TSL2550 ambient light sensor"
157 depends on EXPERIMENTAL
159 If you say yes here you get support for the Taos TSL2550
160 ambient light sensor.
162 This driver can also be built as a module. If so, the module
163 will be called tsl2550.
166 bool "TWL92330/Menelaus PM chip"
167 depends on I2C=y && ARCH_OMAP24XX
169 If you say yes here you get support for the Texas Instruments
170 TWL92330/Menelaus Power Management chip. This include voltage
171 regulators, Dual slot memory card tranceivers, real-time clock
172 and other features that are often used in portable devices like
173 cell phones and PDAs.
175 config MCU_MPC8349EMITX
176 tristate "MPC8349E-mITX MCU driver"
177 depends on I2C && PPC_83xx
179 select ARCH_REQUIRE_GPIOLIB
181 Say Y here to enable soft power-off functionality on the Freescale
182 boards with the MPC8349E-mITX-compatible MCU chips. This driver will
183 also register MCU GPIOs with the generic GPIO API, so you'll able
184 to use MCU pins as GPIOs.