1# 2# Multifunction miscellaneous devices 3# 4 5menu "Multifunction device drivers" 6 depends on HAS_IOMEM 7 8config MFD_CORE 9 tristate 10 default n 11 12config MFD_SM501 13 tristate "Support for Silicon Motion SM501" 14 ---help--- 15 This is the core driver for the Silicon Motion SM501 multimedia 16 companion chip. This device is a multifunction device which may 17 provide numerous interfaces including USB host controller, USB gadget, 18 asynchronous serial ports, audio functions, and a dual display video 19 interface. The device may be connected by PCI or local bus with 20 varying functions enabled. 21 22config MFD_SM501_GPIO 23 bool "Export GPIO via GPIO layer" 24 depends on MFD_SM501 && GPIOLIB 25 ---help--- 26 This option uses the gpio library layer to export the 64 GPIO 27 lines on the SM501. The platform data is used to supply the 28 base number for the first GPIO line to register. 29 30config MFD_ASIC3 31 bool "Support for Compaq ASIC3" 32 depends on GENERIC_HARDIRQS && GPIOLIB && ARM 33 select MFD_CORE 34 ---help--- 35 This driver supports the ASIC3 multifunction chip found on many 36 PDAs (mainly iPAQ and HTC based ones) 37 38config MFD_DM355EVM_MSP 39 bool "DaVinci DM355 EVM microcontroller" 40 depends on I2C && MACH_DAVINCI_DM355_EVM 41 help 42 This driver supports the MSP430 microcontroller used on these 43 boards. MSP430 firmware manages resets and power sequencing, 44 inputs from buttons and the IR remote, LEDs, an RTC, and more. 45 46config HTC_EGPIO 47 bool "HTC EGPIO support" 48 depends on GENERIC_HARDIRQS && GPIOLIB && ARM 49 help 50 This driver supports the CPLD egpio chip present on 51 several HTC phones. It provides basic support for input 52 pins, output pins, and irqs. 53 54config HTC_PASIC3 55 tristate "HTC PASIC3 LED/DS1WM chip support" 56 select MFD_CORE 57 help 58 This core driver provides register access for the LED/DS1WM 59 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and 60 HTC Magician devices, respectively. Actual functionality is 61 handled by the leds-pasic3 and ds1wm drivers. 62 63config UCB1400_CORE 64 tristate "Philips UCB1400 Core driver" 65 depends on AC97_BUS 66 depends on GPIOLIB 67 help 68 This enables support for the Philips UCB1400 core functions. 69 The UCB1400 is an AC97 audio codec. 70 71 To compile this driver as a module, choose M here: the 72 module will be called ucb1400_core. 73 74config TPS65010 75 tristate "TPS6501x Power Management chips" 76 depends on I2C && GPIOLIB 77 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK 78 help 79 If you say yes here you get support for the TPS6501x series of 80 Power Management chips. These include voltage regulators, 81 lithium ion/polymer battery charging, and other features that 82 are often used in portable devices like cell phones and cameras. 83 84 This driver can also be built as a module. If so, the module 85 will be called tps65010. 86 87config MENELAUS 88 bool "Texas Instruments TWL92330/Menelaus PM chip" 89 depends on I2C=y && ARCH_OMAP24XX 90 help 91 If you say yes here you get support for the Texas Instruments 92 TWL92330/Menelaus Power Management chip. This include voltage 93 regulators, Dual slot memory card transceivers, real-time clock 94 and other features that are often used in portable devices like 95 cell phones and PDAs. 96 97config TWL4030_CORE 98 bool "Texas Instruments TWL4030/TPS659x0 Support" 99 depends on I2C=y && GENERIC_HARDIRQS 100 help 101 Say yes here if you have TWL4030 family chip on your board. 102 This core driver provides register access and IRQ handling 103 facilities, and registers devices for the various functions 104 so that function-specific drivers can bind to them. 105 106 These multi-function chips are found on many OMAP2 and OMAP3 107 boards, providing power management, RTC, GPIO, keypad, a 108 high speed USB OTG transceiver, an audio codec (on most 109 versions) and many other features. 110 111config TWL4030_POWER 112 bool "Support power resources on TWL4030 family chips" 113 depends on TWL4030_CORE && ARM 114 help 115 Say yes here if you want to use the power resources on the 116 TWL4030 family chips. Most of these resources are regulators, 117 which have a separate driver; some are control signals, such 118 as clock request handshaking. 119 120 This driver uses board-specific data to initialize the resources 121 and load scripts controling which resources are switched off/on 122 or reset when a sleep, wakeup or warm reset event occurs. 123 124config MFD_TMIO 125 bool 126 default n 127 128config MFD_T7L66XB 129 bool "Support Toshiba T7L66XB" 130 depends on ARM && HAVE_CLK 131 select MFD_CORE 132 select MFD_TMIO 133 help 134 Support for Toshiba Mobile IO Controller T7L66XB 135 136config MFD_TC6387XB 137 bool "Support Toshiba TC6387XB" 138 depends on ARM && HAVE_CLK 139 select MFD_CORE 140 select MFD_TMIO 141 help 142 Support for Toshiba Mobile IO Controller TC6387XB 143 144config MFD_TC6393XB 145 bool "Support Toshiba TC6393XB" 146 depends on GPIOLIB && ARM 147 select MFD_CORE 148 select MFD_TMIO 149 help 150 Support for Toshiba Mobile IO Controller TC6393XB 151 152config PMIC_DA903X 153 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support" 154 depends on I2C=y 155 help 156 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a 157 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC 158 usually found on PXA processors-based platforms. This includes 159 the I2C driver and the core APIs _only_, you have to select 160 individual components like LCD backlight, voltage regulators, 161 LEDs and battery-charger under the corresponding menus. 162 163config MFD_WM8400 164 tristate "Support Wolfson Microelectronics WM8400" 165 select MFD_CORE 166 depends on I2C 167 help 168 Support for the Wolfson Microelecronics WM8400 PMIC and audio 169 CODEC. This driver provides common support for accessing 170 the device, additional drivers must be enabled in order to use 171 the functionality of the device. 172 173config MFD_WM831X 174 tristate "Support Wolfson Microelectronics WM831x PMICs" 175 select MFD_CORE 176 depends on I2C 177 help 178 Support for the Wolfson Microelecronics WM831x PMICs. This 179 driver provides common support for accessing the device, 180 additional drivers must be enabled in order to use the 181 functionality of the device. 182 183config MFD_WM8350 184 tristate 185 186config MFD_WM8350_CONFIG_MODE_0 187 bool 188 depends on MFD_WM8350 189 190config MFD_WM8350_CONFIG_MODE_1 191 bool 192 depends on MFD_WM8350 193 194config MFD_WM8350_CONFIG_MODE_2 195 bool 196 depends on MFD_WM8350 197 198config MFD_WM8350_CONFIG_MODE_3 199 bool 200 depends on MFD_WM8350 201 202config MFD_WM8351_CONFIG_MODE_0 203 bool 204 depends on MFD_WM8350 205 206config MFD_WM8351_CONFIG_MODE_1 207 bool 208 depends on MFD_WM8350 209 210config MFD_WM8351_CONFIG_MODE_2 211 bool 212 depends on MFD_WM8350 213 214config MFD_WM8351_CONFIG_MODE_3 215 bool 216 depends on MFD_WM8350 217 218config MFD_WM8352_CONFIG_MODE_0 219 bool 220 depends on MFD_WM8350 221 222config MFD_WM8352_CONFIG_MODE_1 223 bool 224 depends on MFD_WM8350 225 226config MFD_WM8352_CONFIG_MODE_2 227 bool 228 depends on MFD_WM8350 229 230config MFD_WM8352_CONFIG_MODE_3 231 bool 232 depends on MFD_WM8350 233 234config MFD_WM8350_I2C 235 tristate "Support Wolfson Microelectronics WM8350 with I2C" 236 select MFD_WM8350 237 depends on I2C 238 help 239 The WM8350 is an integrated audio and power management 240 subsystem with watchdog and RTC functionality for embedded 241 systems. This option enables core support for the WM8350 with 242 I2C as the control interface. Additional options must be 243 selected to enable support for the functionality of the chip. 244 245config MFD_PCF50633 246 tristate "Support for NXP PCF50633" 247 depends on I2C 248 help 249 Say yes here if you have NXP PCF50633 chip on your board. 250 This core driver provides register access and IRQ handling 251 facilities, and registers devices for the various functions 252 so that function-specific drivers can bind to them. 253 254config MFD_MC13783 255 tristate "Support Freescale MC13783" 256 depends on SPI_MASTER 257 select MFD_CORE 258 help 259 Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC. 260 This driver provides common support for accessing the device, 261 additional drivers must be enabled in order to use the 262 functionality of the device. 263 264config PCF50633_ADC 265 tristate "Support for NXP PCF50633 ADC" 266 depends on MFD_PCF50633 267 help 268 Say yes here if you want to include support for ADC in the 269 NXP PCF50633 chip. 270 271config PCF50633_GPIO 272 tristate "Support for NXP PCF50633 GPIO" 273 depends on MFD_PCF50633 274 help 275 Say yes here if you want to include support GPIO for pins on 276 the PCF50633 chip. 277 278config AB3100_CORE 279 tristate "ST-Ericsson AB3100 Mixed Signal Circuit core functions" 280 depends on I2C 281 default y if ARCH_U300 282 help 283 Select this to enable the AB3100 Mixed Signal IC core 284 functionality. This connects to a AB3100 on the I2C bus 285 and expose a number of symbols needed for dependent devices 286 to read and write registers and subscribe to events from 287 this multi-functional IC. This is needed to use other features 288 of the AB3100 such as battery-backed RTC, charging control, 289 LEDs, vibrator, system power and temperature, power management 290 and ALSA sound. 291 292config AB3100_OTP 293 tristate "ST-Ericsson AB3100 OTP functions" 294 depends on AB3100_CORE 295 default y if AB3100_CORE 296 help 297 Select this to enable the AB3100 Mixed Signal IC OTP (one-time 298 programmable memory) support. This exposes a sysfs file to read 299 out OTP values. 300 301config EZX_PCAP 302 bool "PCAP Support" 303 depends on GENERIC_HARDIRQS && SPI_MASTER 304 help 305 This enables the PCAP ASIC present on EZX Phones. This is 306 needed for MMC, TouchScreen, Sound, USB, etc.. 307 308endmenu 309 310menu "Multimedia Capabilities Port drivers" 311 depends on ARCH_SA1100 312 313config MCP 314 tristate 315 316# Interface drivers 317config MCP_SA11X0 318 tristate "Support SA11x0 MCP interface" 319 depends on ARCH_SA1100 320 select MCP 321 322# Chip drivers 323config MCP_UCB1200 324 tristate "Support for UCB1200 / UCB1300" 325 depends on MCP 326 327config MCP_UCB1200_TS 328 tristate "Touchscreen interface support" 329 depends on MCP_UCB1200 && INPUT 330 331endmenu 332