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