Commit | Line | Data |
---|---|---|
a4e137ab RK |
1 | # |
2 | # Multifunction miscellaneous devices | |
3 | # | |
4 | ||
8a0a8e8e AB |
5 | if HAS_IOMEM |
6 | menu "Multifunction device drivers" | |
b6d6454f | 7 | |
aa613de6 DB |
8 | config MFD_CORE |
9 | tristate | |
10 | default n | |
11 | ||
2cc50bee HZ |
12 | config MFD_88PM860X |
13 | bool "Support Marvell 88PM8606/88PM8607" | |
8d002bdc | 14 | depends on I2C=y && GENERIC_HARDIRQS |
b46a36c0 | 15 | select REGMAP_I2C |
2cc50bee HZ |
16 | select MFD_CORE |
17 | help | |
18 | This supports for Marvell 88PM8606/88PM8607 Power Management IC. | |
19 | This includes the I2C driver and the core APIs _only_, you have to | |
20 | select individual components like voltage regulators, RTC and | |
21 | battery-charger under the corresponding menus. | |
22 | ||
b6d6454f BD |
23 | config MFD_SM501 |
24 | tristate "Support for Silicon Motion SM501" | |
25 | ---help--- | |
26 | This is the core driver for the Silicon Motion SM501 multimedia | |
27 | companion chip. This device is a multifunction device which may | |
01dd2fbf ML |
28 | provide numerous interfaces including USB host controller, USB gadget, |
29 | asynchronous serial ports, audio functions, and a dual display video | |
b6d6454f BD |
30 | interface. The device may be connected by PCI or local bus with |
31 | varying functions enabled. | |
32 | ||
f61be273 BD |
33 | config MFD_SM501_GPIO |
34 | bool "Export GPIO via GPIO layer" | |
2eedd604 | 35 | depends on MFD_SM501 && GPIOLIB |
f61be273 BD |
36 | ---help--- |
37 | This option uses the gpio library layer to export the 64 GPIO | |
38 | lines on the SM501. The platform data is used to supply the | |
39 | base number for the first GPIO line to register. | |
40 | ||
fa9ff4b1 SO |
41 | config MFD_ASIC3 |
42 | bool "Support for Compaq ASIC3" | |
2eedd604 | 43 | depends on GENERIC_HARDIRQS && GPIOLIB && ARM |
9461f65a | 44 | select MFD_CORE |
fa9ff4b1 SO |
45 | ---help--- |
46 | This driver supports the ASIC3 multifunction chip found on many | |
47 | PDAs (mainly iPAQ and HTC based ones) | |
48 | ||
ca26308c MA |
49 | config MFD_DAVINCI_VOICECODEC |
50 | tristate | |
51 | select MFD_CORE | |
52 | ||
0931a4c6 DB |
53 | config MFD_DM355EVM_MSP |
54 | bool "DaVinci DM355 EVM microcontroller" | |
1819ebcf | 55 | depends on I2C=y && MACH_DAVINCI_DM355_EVM |
0931a4c6 DB |
56 | help |
57 | This driver supports the MSP430 microcontroller used on these | |
58 | boards. MSP430 firmware manages resets and power sequencing, | |
59 | inputs from buttons and the IR remote, LEDs, an RTC, and more. | |
60 | ||
03df0f62 CC |
61 | config MFD_TI_SSP |
62 | tristate "TI Sequencer Serial Port support" | |
63 | depends on ARCH_DAVINCI_TNETV107X | |
64 | select MFD_CORE | |
65 | ---help--- | |
66 | Say Y here if you want support for the Sequencer Serial Port | |
67 | in a Texas Instruments TNETV107X SoC. | |
68 | ||
69 | To compile this driver as a module, choose M here: the | |
70 | module will be called ti-ssp. | |
71 | ||
a1635b8f PZ |
72 | config HTC_EGPIO |
73 | bool "HTC EGPIO support" | |
7444a72e | 74 | depends on GENERIC_HARDIRQS && GPIOLIB && ARM |
a1635b8f PZ |
75 | help |
76 | This driver supports the CPLD egpio chip present on | |
77 | several HTC phones. It provides basic support for input | |
78 | pins, output pins, and irqs. | |
79 | ||
5dc3339a PZ |
80 | config HTC_PASIC3 |
81 | tristate "HTC PASIC3 LED/DS1WM chip support" | |
0254a8f4 | 82 | select MFD_CORE |
5dc3339a PZ |
83 | help |
84 | This core driver provides register access for the LED/DS1WM | |
85 | chips labeled "AIC2" and "AIC3", found on HTC Blueangel and | |
86 | HTC Magician devices, respectively. Actual functionality is | |
87 | handled by the leds-pasic3 and ds1wm drivers. | |
88 | ||
6048a3dd CM |
89 | config HTC_I2CPLD |
90 | bool "HTC I2C PLD chip support" | |
bef3e20c | 91 | depends on I2C=y && GPIOLIB |
6048a3dd CM |
92 | help |
93 | If you say yes here you get support for the supposed CPLD | |
94 | found on omap850 HTC devices like the HTC Wizard and HTC Herald. | |
95 | This device provides input and output GPIOs through an I2C | |
96 | interface to one or more sub-chips. | |
97 | ||
d9105c2b MV |
98 | config UCB1400_CORE |
99 | tristate "Philips UCB1400 Core driver" | |
e4831802 | 100 | depends on AC97_BUS |
5a49a540 | 101 | depends on GPIOLIB |
d9105c2b MV |
102 | help |
103 | This enables support for the Philips UCB1400 core functions. | |
104 | The UCB1400 is an AC97 audio codec. | |
105 | ||
106 | To compile this driver as a module, choose M here: the | |
107 | module will be called ucb1400_core. | |
108 | ||
798a8eee LW |
109 | config TPS6105X |
110 | tristate "TPS61050/61052 Boost Converters" | |
111 | depends on I2C | |
2edd3b69 | 112 | select REGULATOR |
fc498fa2 | 113 | select MFD_CORE |
2edd3b69 | 114 | select REGULATOR_FIXED_VOLTAGE |
798a8eee LW |
115 | help |
116 | This option enables a driver for the TP61050/TPS61052 | |
117 | high-power "white LED driver". This boost converter is | |
118 | sometimes used for other things than white LEDs, and | |
119 | also contains a GPIO pin. | |
120 | ||
87c13493 DB |
121 | config TPS65010 |
122 | tristate "TPS6501x Power Management chips" | |
123 | depends on I2C && GPIOLIB | |
124 | default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK | |
125 | help | |
126 | If you say yes here you get support for the TPS6501x series of | |
127 | Power Management chips. These include voltage regulators, | |
128 | lithium ion/polymer battery charging, and other features that | |
129 | are often used in portable devices like cell phones and cameras. | |
130 | ||
131 | This driver can also be built as a module. If so, the module | |
132 | will be called tps65010. | |
133 | ||
31dd6a26 TF |
134 | config TPS6507X |
135 | tristate "TPS6507x Power Management / Touch Screen chips" | |
136 | select MFD_CORE | |
137 | depends on I2C | |
138 | help | |
139 | If you say yes here you get support for the TPS6507x series of | |
140 | Power Management / Touch Screen chips. These include voltage | |
141 | regulators, lithium ion/polymer battery charging, touch screen | |
142 | and other features that are often used in portable devices. | |
143 | This driver can also be built as a module. If so, the module | |
144 | will be called tps6507x. | |
145 | ||
d48f411c AC |
146 | config MFD_TPS65217 |
147 | tristate "TPS65217 Power Management / White LED chips" | |
148 | depends on I2C | |
149 | select MFD_CORE | |
150 | select REGMAP_I2C | |
151 | help | |
152 | If you say yes here you get support for the TPS65217 series of | |
153 | Power Management / White LED chips. | |
154 | These include voltage regulators, lithium ion/polymer battery | |
155 | charger, wled and other features that are often used in portable | |
156 | devices. | |
157 | ||
158 | This driver can also be built as a module. If so, the module | |
159 | will be called tps65217. | |
160 | ||
37df003c AL |
161 | config MFD_TPS6586X |
162 | bool "TPS6586x Power Management chips" | |
163 | depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS | |
164 | select MFD_CORE | |
165 | help | |
166 | If you say yes here you get support for the TPS6586X series of | |
167 | Power Management chips. | |
168 | This driver provides common support for accessing the device, | |
169 | additional drivers must be enabled in order to use the | |
170 | functionality of the device. | |
171 | ||
172 | This driver can also be built as a module. If so, the module | |
173 | will be called tps6586x. | |
174 | ||
54f323b1 LW |
175 | config MFD_TPS65910 |
176 | bool "TPS65910 Power Management chip" | |
177 | depends on I2C=y && GPIOLIB | |
178 | select MFD_CORE | |
179 | select GPIO_TPS65910 | |
180 | help | |
181 | if you say yes here you get support for the TPS65910 series of | |
182 | Power Management chips. | |
183 | ||
36e52873 | 184 | config MFD_TPS65912 |
5608801b | 185 | bool |
36e52873 MO |
186 | depends on GPIOLIB |
187 | ||
188 | config MFD_TPS65912_I2C | |
189 | bool "TPS95612 Power Management chip with I2C" | |
190 | select MFD_CORE | |
191 | select MFD_TPS65912 | |
192 | depends on I2C=y && GPIOLIB | |
193 | help | |
194 | If you say yes here you get support for the TPS65912 series of | |
195 | PM chips with I2C interface. | |
196 | ||
197 | config MFD_TPS65912_SPI | |
198 | bool "TPS65912 Power Management chip with SPI" | |
199 | select MFD_CORE | |
200 | select MFD_TPS65912 | |
201 | depends on SPI_MASTER && GPIOLIB | |
202 | help | |
203 | If you say yes here you get support for the TPS65912 series of | |
204 | PM chips with SPI interface. | |
205 | ||
88e75cc3 DB |
206 | config MENELAUS |
207 | bool "Texas Instruments TWL92330/Menelaus PM chip" | |
088ef950 | 208 | depends on I2C=y && ARCH_OMAP2 |
88e75cc3 DB |
209 | help |
210 | If you say yes here you get support for the Texas Instruments | |
211 | TWL92330/Menelaus Power Management chip. This include voltage | |
692105b8 | 212 | regulators, Dual slot memory card transceivers, real-time clock |
88e75cc3 DB |
213 | and other features that are often used in portable devices like |
214 | cell phones and PDAs. | |
215 | ||
a603a7fa | 216 | config TWL4030_CORE |
e8deb28c | 217 | bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support" |
6252547b | 218 | depends on I2C=y && GENERIC_HARDIRQS |
a603a7fa | 219 | help |
e8deb28c | 220 | Say yes here if you have TWL4030 / TWL6030 family chip on your board. |
a603a7fa DB |
221 | This core driver provides register access and IRQ handling |
222 | facilities, and registers devices for the various functions | |
223 | so that function-specific drivers can bind to them. | |
224 | ||
225 | These multi-function chips are found on many OMAP2 and OMAP3 | |
226 | boards, providing power management, RTC, GPIO, keypad, a | |
227 | high speed USB OTG transceiver, an audio codec (on most | |
228 | versions) and many other features. | |
229 | ||
f99c1d4f K |
230 | config TWL4030_MADC |
231 | tristate "Texas Instruments TWL4030 MADC" | |
232 | depends on TWL4030_CORE | |
233 | help | |
234 | This driver provides support for triton TWL4030-MADC. The | |
235 | driver supports both RT and SW conversion methods. | |
236 | ||
237 | This driver can be built as a module. If so it will be | |
238 | named twl4030-madc | |
239 | ||
ebf0bd36 AK |
240 | config TWL4030_POWER |
241 | bool "Support power resources on TWL4030 family chips" | |
242 | depends on TWL4030_CORE && ARM | |
243 | help | |
244 | Say yes here if you want to use the power resources on the | |
245 | TWL4030 family chips. Most of these resources are regulators, | |
246 | which have a separate driver; some are control signals, such | |
247 | as clock request handshaking. | |
248 | ||
249 | This driver uses board-specific data to initialize the resources | |
25985edc | 250 | and load scripts controlling which resources are switched off/on |
ebf0bd36 AK |
251 | or reset when a sleep, wakeup or warm reset event occurs. |
252 | ||
57fe7251 | 253 | config MFD_TWL4030_AUDIO |
0b83ddeb PU |
254 | bool |
255 | depends on TWL4030_CORE | |
256 | select MFD_CORE | |
257 | default n | |
258 | ||
31fc03df H |
259 | config TWL6030_PWM |
260 | tristate "TWL6030 PWM (Pulse Width Modulator) Support" | |
261 | depends on TWL4030_CORE | |
262 | select HAVE_PWM | |
263 | default n | |
264 | help | |
265 | Say yes here if you want support for TWL6030 PWM. | |
266 | This is used to control charging LED brightness. | |
267 | ||
f19b2823 MLC |
268 | config TWL6040_CORE |
269 | bool | |
270 | depends on TWL4030_CORE && GENERIC_HARDIRQS | |
271 | select MFD_CORE | |
272 | default n | |
273 | ||
27e34995 RV |
274 | config MFD_STMPE |
275 | bool "Support STMicroelectronics STMPE" | |
e789995d | 276 | depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS |
27e34995 RV |
277 | select MFD_CORE |
278 | help | |
279 | Support for the STMPE family of I/O Expanders from | |
280 | STMicroelectronics. | |
281 | ||
282 | Currently supported devices are: | |
283 | ||
284 | STMPE811: GPIO, Touchscreen | |
285 | STMPE1601: GPIO, Keypad | |
286 | STMPE2401: GPIO, Keypad | |
287 | STMPE2403: GPIO, Keypad | |
288 | ||
289 | This driver provides common support for accessing the device, | |
290 | additional drivers must be enabled in order to use the functionality | |
291 | of the device. Currently available sub drivers are: | |
292 | ||
293 | GPIO: stmpe-gpio | |
294 | Keypad: stmpe-keypad | |
295 | Touchscreen: stmpe-ts | |
296 | ||
1a6e4b74 VK |
297 | menu "STMPE Interface Drivers" |
298 | depends on MFD_STMPE | |
299 | ||
300 | config STMPE_I2C | |
301 | bool "STMPE I2C Inteface" | |
eedea80f | 302 | depends on I2C=y |
1a6e4b74 VK |
303 | default y |
304 | help | |
305 | This is used to enable I2C interface of STMPE | |
e789995d VK |
306 | |
307 | config STMPE_SPI | |
308 | bool "STMPE SPI Inteface" | |
309 | depends on SPI_MASTER | |
310 | help | |
311 | This is used to enable SPI interface of STMPE | |
1a6e4b74 VK |
312 | endmenu |
313 | ||
f4e8afdc SI |
314 | config MFD_TC3589X |
315 | bool "Support Toshiba TC35892 and variants" | |
b4ecd326 RV |
316 | depends on I2C=y && GENERIC_HARDIRQS |
317 | select MFD_CORE | |
318 | help | |
f4e8afdc | 319 | Support for the Toshiba TC35892 and variants I/O Expander. |
b4ecd326 RV |
320 | |
321 | This driver provides common support for accessing the device, | |
322 | additional drivers must be enabled in order to use the | |
323 | functionality of the device. | |
324 | ||
1c2c30ac SO |
325 | config MFD_TMIO |
326 | bool | |
327 | default n | |
328 | ||
1f192015 IM |
329 | config MFD_T7L66XB |
330 | bool "Support Toshiba T7L66XB" | |
9ca68233 | 331 | depends on ARM && HAVE_CLK |
1f192015 | 332 | select MFD_CORE |
1c2c30ac | 333 | select MFD_TMIO |
1f192015 IM |
334 | help |
335 | Support for Toshiba Mobile IO Controller T7L66XB | |
336 | ||
cbdfb426 IM |
337 | config MFD_TC6387XB |
338 | bool "Support Toshiba TC6387XB" | |
9ca68233 | 339 | depends on ARM && HAVE_CLK |
cbdfb426 | 340 | select MFD_CORE |
1c2c30ac | 341 | select MFD_TMIO |
cbdfb426 IM |
342 | help |
343 | Support for Toshiba Mobile IO Controller TC6387XB | |
344 | ||
d6315949 DB |
345 | config MFD_TC6393XB |
346 | bool "Support Toshiba TC6393XB" | |
e959da10 | 347 | depends on GPIOLIB && ARM && HAVE_CLK |
f024ff10 | 348 | select MFD_CORE |
1c2c30ac | 349 | select MFD_TMIO |
d6315949 DB |
350 | help |
351 | Support for Toshiba Mobile IO Controller TC6393XB | |
352 | ||
8e2eaabf SO |
353 | config PMIC_DA903X |
354 | bool "Dialog Semiconductor DA9030/DA9034 PMIC Support" | |
355 | depends on I2C=y | |
356 | help | |
357 | Say yes here to support for Dialog Semiconductor DA9030 (a.k.a | |
358 | ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC | |
359 | usually found on PXA processors-based platforms. This includes | |
360 | the I2C driver and the core APIs _only_, you have to select | |
361 | individual components like LCD backlight, voltage regulators, | |
362 | LEDs and battery-charger under the corresponding menus. | |
a5736e0b | 363 | |
84c99db8 AJ |
364 | config PMIC_DA9052 |
365 | bool | |
366 | select MFD_CORE | |
367 | ||
cfe04478 AJ |
368 | config MFD_DA9052_SPI |
369 | bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI" | |
370 | select REGMAP_SPI | |
371 | select REGMAP_IRQ | |
372 | select PMIC_DA9052 | |
373 | depends on SPI_MASTER=y | |
374 | help | |
375 | Support for the Dialog Semiconductor DA9052 PMIC | |
376 | when controlled using SPI. This driver provides common support | |
377 | for accessing the device, additional drivers must be enabled in | |
378 | order to use the functionality of the device. | |
379 | ||
84c99db8 AJ |
380 | config MFD_DA9052_I2C |
381 | bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C" | |
382 | select REGMAP_I2C | |
383 | select REGMAP_IRQ | |
384 | select PMIC_DA9052 | |
385 | depends on I2C=y | |
386 | help | |
387 | Support for the Dialog Semiconductor DA9052 PMIC | |
388 | when controlled using I2C. This driver provides common support | |
389 | for accessing the device, additional drivers must be enabled in | |
390 | order to use the functionality of the device. | |
391 | ||
a5736e0b MH |
392 | config PMIC_ADP5520 |
393 | bool "Analog Devices ADP5520/01 MFD PMIC Core Support" | |
394 | depends on I2C=y | |
395 | help | |
396 | Say yes here to add support for Analog Devices AD5520 and ADP5501, | |
397 | Multifunction Power Management IC. This includes | |
398 | the I2C driver and the core APIs _only_, you have to select | |
399 | individual components like LCD backlight, LEDs, GPIOs and Kepad | |
400 | under the corresponding menus. | |
8e2eaabf | 401 | |
d50f8f33 | 402 | config MFD_MAX8925 |
1f1cf8f9 | 403 | bool "Maxim Semiconductor MAX8925 PMIC Support" |
8d002bdc | 404 | depends on I2C=y && GENERIC_HARDIRQS |
1ad99893 | 405 | select MFD_CORE |
d50f8f33 HZ |
406 | help |
407 | Say yes here to support for Maxim Semiconductor MAX8925. This is | |
408 | a Power Management IC. This driver provies common support for | |
409 | accessing the device, additional drivers must be enabled in order | |
410 | to use the functionality of the device. | |
411 | ||
527e7e9a MH |
412 | config MFD_MAX8997 |
413 | bool "Maxim Semiconductor MAX8997/8966 PMIC Support" | |
414 | depends on I2C=y && GENERIC_HARDIRQS | |
415 | select MFD_CORE | |
416 | help | |
417 | Say yes here to support for Maxim Semiconductor MAX8998/8966. | |
418 | This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic, | |
419 | MUIC controls on chip. | |
d7e8c01a | 420 | This driver provides common support for accessing the device; |
527e7e9a MH |
421 | additional drivers must be enabled in order to use the functionality |
422 | of the device. | |
423 | ||
156f2528 | 424 | config MFD_MAX8998 |
f8539ddc | 425 | bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support" |
2c7e6f57 | 426 | depends on I2C=y && GENERIC_HARDIRQS |
156f2528 KP |
427 | select MFD_CORE |
428 | help | |
f8539ddc KP |
429 | Say yes here to support for Maxim Semiconductor MAX8998 and |
430 | National Semiconductor LP3974. This is a Power Management IC. | |
431 | This driver provies common support for accessing the device, | |
432 | additional drivers must be enabled in order to use the functionality | |
433 | of the device. | |
156f2528 | 434 | |
c3d4d697 SK |
435 | config MFD_S5M_CORE |
436 | bool "SAMSUNG S5M Series Support" | |
437 | depends on I2C=y && GENERIC_HARDIRQS | |
438 | select MFD_CORE | |
439 | select REGMAP_I2C | |
440 | help | |
441 | Support for the Samsung Electronics S5M MFD series. | |
442 | This driver provies common support for accessing the device, | |
443 | additional drivers must be enabled in order to use the functionality | |
444 | of the device | |
445 | ||
1d9f9f04 MB |
446 | config MFD_WM8400 |
447 | tristate "Support Wolfson Microelectronics WM8400" | |
b8380c1a | 448 | select MFD_CORE |
9c366452 | 449 | depends on I2C |
2b247d06 | 450 | select REGMAP_I2C |
1d9f9f04 MB |
451 | help |
452 | Support for the Wolfson Microelecronics WM8400 PMIC and audio | |
9e5aca58 | 453 | CODEC. This driver provides common support for accessing |
1d9f9f04 MB |
454 | the device, additional drivers must be enabled in order to use |
455 | the functionality of the device. | |
456 | ||
b11062b9 | 457 | config MFD_WM831X |
e5b48684 MB |
458 | bool |
459 | depends on GENERIC_HARDIRQS | |
460 | ||
461 | config MFD_WM831X_I2C | |
462 | bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C" | |
b11062b9 | 463 | select MFD_CORE |
e5b48684 | 464 | select MFD_WM831X |
1df5981b | 465 | select REGMAP_I2C |
8d002bdc | 466 | depends on I2C=y && GENERIC_HARDIRQS |
b11062b9 | 467 | help |
e5b48684 MB |
468 | Support for the Wolfson Microelecronics WM831x and WM832x PMICs |
469 | when controlled using I2C. This driver provides common support | |
470 | for accessing the device, additional drivers must be enabled in | |
471 | order to use the functionality of the device. | |
b11062b9 | 472 | |
2aa13b9e MB |
473 | config MFD_WM831X_SPI |
474 | bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI" | |
475 | select MFD_CORE | |
476 | select MFD_WM831X | |
1df5981b | 477 | select REGMAP_SPI |
2aa13b9e MB |
478 | depends on SPI_MASTER && GENERIC_HARDIRQS |
479 | help | |
480 | Support for the Wolfson Microelecronics WM831x and WM832x PMICs | |
481 | when controlled using SPI. This driver provides common support | |
482 | for accessing the device, additional drivers must be enabled in | |
483 | order to use the functionality of the device. | |
484 | ||
89b4012b | 485 | config MFD_WM8350 |
ecf926bc | 486 | bool |
8d002bdc | 487 | depends on GENERIC_HARDIRQS |
89b4012b MB |
488 | |
489 | config MFD_WM8350_CONFIG_MODE_0 | |
490 | bool | |
491 | depends on MFD_WM8350 | |
492 | ||
493 | config MFD_WM8350_CONFIG_MODE_1 | |
494 | bool | |
495 | depends on MFD_WM8350 | |
496 | ||
497 | config MFD_WM8350_CONFIG_MODE_2 | |
498 | bool | |
499 | depends on MFD_WM8350 | |
500 | ||
501 | config MFD_WM8350_CONFIG_MODE_3 | |
502 | bool | |
503 | depends on MFD_WM8350 | |
504 | ||
ca23f8c1 MB |
505 | config MFD_WM8351_CONFIG_MODE_0 |
506 | bool | |
507 | depends on MFD_WM8350 | |
508 | ||
509 | config MFD_WM8351_CONFIG_MODE_1 | |
510 | bool | |
511 | depends on MFD_WM8350 | |
512 | ||
513 | config MFD_WM8351_CONFIG_MODE_2 | |
514 | bool | |
515 | depends on MFD_WM8350 | |
516 | ||
517 | config MFD_WM8351_CONFIG_MODE_3 | |
518 | bool | |
519 | depends on MFD_WM8350 | |
520 | ||
96920630 MB |
521 | config MFD_WM8352_CONFIG_MODE_0 |
522 | bool | |
523 | depends on MFD_WM8350 | |
524 | ||
525 | config MFD_WM8352_CONFIG_MODE_1 | |
526 | bool | |
527 | depends on MFD_WM8350 | |
528 | ||
529 | config MFD_WM8352_CONFIG_MODE_2 | |
530 | bool | |
531 | depends on MFD_WM8350 | |
532 | ||
533 | config MFD_WM8352_CONFIG_MODE_3 | |
534 | bool | |
535 | depends on MFD_WM8350 | |
536 | ||
c661a0b9 | 537 | config MFD_WM8350_I2C |
ecf926bc | 538 | bool "Support Wolfson Microelectronics WM8350 with I2C" |
c661a0b9 | 539 | select MFD_WM8350 |
8d002bdc | 540 | depends on I2C=y && GENERIC_HARDIRQS |
c661a0b9 MB |
541 | help |
542 | The WM8350 is an integrated audio and power management | |
543 | subsystem with watchdog and RTC functionality for embedded | |
544 | systems. This option enables core support for the WM8350 with | |
545 | I2C as the control interface. Additional options must be | |
546 | selected to enable support for the functionality of the chip. | |
547 | ||
9e501086 | 548 | config MFD_WM8994 |
c9fbf7e0 | 549 | bool "Support Wolfson Microelectronics WM8994" |
9e501086 | 550 | select MFD_CORE |
d6c645fc | 551 | select REGMAP_I2C |
8ab30691 | 552 | select REGMAP_IRQ |
c9fbf7e0 | 553 | depends on I2C=y && GENERIC_HARDIRQS |
9e501086 MB |
554 | help |
555 | The WM8994 is a highly integrated hi-fi CODEC designed for | |
556 | smartphone applicatiosn. As well as audio functionality it | |
557 | has on board GPIO and regulator functionality which is | |
558 | supported via the relevant subsystems. This driver provides | |
559 | core support for the WM8994, in order to use the actual | |
560 | functionaltiy of the device other drivers must be enabled. | |
561 | ||
f52046b1 BR |
562 | config MFD_PCF50633 |
563 | tristate "Support for NXP PCF50633" | |
564 | depends on I2C | |
6e3ad118 | 565 | select REGMAP_I2C |
f52046b1 BR |
566 | help |
567 | Say yes here if you have NXP PCF50633 chip on your board. | |
568 | This core driver provides register access and IRQ handling | |
569 | facilities, and registers devices for the various functions | |
570 | so that function-specific drivers can bind to them. | |
571 | ||
1305134e AL |
572 | config PCF50633_ADC |
573 | tristate "Support for NXP PCF50633 ADC" | |
574 | depends on MFD_PCF50633 | |
575 | help | |
576 | Say yes here if you want to include support for ADC in the | |
577 | NXP PCF50633 chip. | |
578 | ||
579 | config PCF50633_GPIO | |
580 | tristate "Support for NXP PCF50633 GPIO" | |
581 | depends on MFD_PCF50633 | |
582 | help | |
583 | Say yes here if you want to include support GPIO for pins on | |
584 | the PCF50633 chip. | |
585 | ||
8238addc | 586 | config MFD_MC13783 |
8e005935 UKK |
587 | tristate |
588 | ||
589 | config MFD_MC13XXX | |
590 | tristate "Support Freescale MC13783 and MC13892" | |
8238addc SH |
591 | depends on SPI_MASTER |
592 | select MFD_CORE | |
8e005935 | 593 | select MFD_MC13783 |
8238addc | 594 | help |
8e005935 UKK |
595 | Support for the Freescale (Atlas) PMIC and audio CODECs |
596 | MC13783 and MC13892. | |
8238addc SH |
597 | This driver provides common support for accessing the device, |
598 | additional drivers must be enabled in order to use the | |
599 | functionality of the device. | |
600 | ||
fa661258 MW |
601 | config ABX500_CORE |
602 | bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions" | |
47c16975 | 603 | default y if ARCH_U300 || ARCH_U8500 |
fa661258 MW |
604 | help |
605 | Say yes here if you have the ABX500 Mixed Signal IC family | |
606 | chips. This core driver expose register access functions. | |
607 | Functionality specific drivers using these functions can | |
608 | remain unchanged when IC changes. Binding of the functions to | |
609 | actual register access is done by the IC core driver. | |
610 | ||
14fa5691 | 611 | config AB3100_CORE |
2071db48 | 612 | bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions" |
fa661258 | 613 | depends on I2C=y && ABX500_CORE |
8c96aefb | 614 | select MFD_CORE |
14fa5691 LW |
615 | default y if ARCH_U300 |
616 | help | |
617 | Select this to enable the AB3100 Mixed Signal IC core | |
618 | functionality. This connects to a AB3100 on the I2C bus | |
619 | and expose a number of symbols needed for dependent devices | |
620 | to read and write registers and subscribe to events from | |
621 | this multi-functional IC. This is needed to use other features | |
622 | of the AB3100 such as battery-backed RTC, charging control, | |
623 | LEDs, vibrator, system power and temperature, power management | |
624 | and ALSA sound. | |
625 | ||
12992dd8 LW |
626 | config AB3100_OTP |
627 | tristate "ST-Ericsson AB3100 OTP functions" | |
628 | depends on AB3100_CORE | |
629 | default y if AB3100_CORE | |
630 | help | |
631 | Select this to enable the AB3100 Mixed Signal IC OTP (one-time | |
632 | programmable memory) support. This exposes a sysfs file to read | |
633 | out OTP values. | |
634 | ||
13a09f93 DR |
635 | config EZX_PCAP |
636 | bool "PCAP Support" | |
637 | depends on GENERIC_HARDIRQS && SPI_MASTER | |
638 | help | |
639 | This enables the PCAP ASIC present on EZX Phones. This is | |
640 | needed for MMC, TouchScreen, Sound, USB, etc.. | |
641 | ||
3d5e2cab MW |
642 | config AB5500_CORE |
643 | bool "ST-Ericsson AB5500 Mixed Signal Power Management chip" | |
644 | depends on ABX500_CORE && MFD_DB5500_PRCMU | |
645 | select MFD_CORE | |
646 | help | |
647 | Select this option to enable access to AB5500 power management | |
648 | chip. This connects to the db5500 chip via the I2C bus via PRCMU. | |
649 | This chip embeds various other multimedia funtionalities as well. | |
650 | ||
94be70d4 LW |
651 | config AB5500_DEBUG |
652 | bool "Enable debug info via debugfs" | |
653 | depends on AB5500_CORE && DEBUG_FS | |
654 | default y if DEBUG_FS | |
655 | help | |
656 | Select this option if you want debug information from the AB5500 | |
657 | using the debug filesystem, debugfs. | |
658 | ||
62579266 RV |
659 | config AB8500_CORE |
660 | bool "ST-Ericsson AB8500 Mixed Signal Power Management chip" | |
6680d940 | 661 | depends on GENERIC_HARDIRQS && ABX500_CORE |
62579266 | 662 | select MFD_CORE |
0c41839e | 663 | help |
62579266 | 664 | Select this option to enable access to AB8500 power management |
6680d940 SI |
665 | chip. This connects to U8500 either on the SSP/SPI bus (deprecated |
666 | since hardware version v1.0) or the I2C bus via PRCMU. It also adds | |
667 | the irq_chip parts for handling the Mixed Signal chip events. | |
0c41839e SK |
668 | This chip embeds various other multimedia funtionalities as well. |
669 | ||
39368eda MW |
670 | config AB8500_I2C_CORE |
671 | bool "AB8500 register access via PRCMU I2C" | |
650c2a21 | 672 | depends on AB8500_CORE && MFD_DB8500_PRCMU |
39368eda MW |
673 | default y |
674 | help | |
675 | This enables register access to the AB8500 chip via PRCMU I2C. | |
676 | The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware | |
677 | the I2C bus is connected to the Power Reset | |
678 | and Mangagement Unit, PRCMU. | |
679 | ||
5814fc35 MW |
680 | config AB8500_DEBUG |
681 | bool "Enable debug info via debugfs" | |
682 | depends on AB8500_CORE && DEBUG_FS | |
683 | default y if DEBUG_FS | |
684 | help | |
685 | Select this option if you want debug information using the debug | |
686 | filesystem, debugfs. | |
dae2db30 AM |
687 | |
688 | config AB8500_GPADC | |
689 | bool "AB8500 GPADC driver" | |
690 | depends on AB8500_CORE && REGULATOR_AB8500 | |
691 | default y | |
692 | help | |
693 | AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage | |
5814fc35 | 694 | |
650c2a21 LW |
695 | config MFD_DB8500_PRCMU |
696 | bool "ST-Ericsson DB8500 Power Reset Control Management Unit" | |
697 | depends on UX500_SOC_DB8500 | |
698 | select MFD_CORE | |
699 | help | |
700 | Select this option to enable support for the DB8500 Power Reset | |
701 | and Control Management Unit. This is basically an autonomous | |
702 | system controller running an XP70 microprocessor, which is accessed | |
703 | through a register map. | |
704 | ||
8317797c LW |
705 | config MFD_DB5500_PRCMU |
706 | bool "ST-Ericsson DB5500 Power Reset Control Management Unit" | |
707 | depends on UX500_SOC_DB5500 | |
708 | select MFD_CORE | |
709 | help | |
710 | Select this option to enable support for the DB5500 Power Reset | |
711 | and Control Management Unit. This is basically an autonomous | |
712 | system controller running an XP70 microprocessor, which is accessed | |
713 | through a register map. | |
714 | ||
f71e1afd AS |
715 | config MFD_CS5535 |
716 | tristate "Support for CS5535 and CS5536 southbridge core functions" | |
717 | select MFD_CORE | |
15b7cf14 | 718 | depends on PCI && X86 |
f71e1afd AS |
719 | ---help--- |
720 | This is the core driver for CS5535/CS5536 MFD functions. This is | |
721 | necessary for using the board's GPIO and MFGPT functionality. | |
722 | ||
8edbede9 RR |
723 | config MFD_TIMBERDALE |
724 | tristate "Support for the Timberdale FPGA" | |
725 | select MFD_CORE | |
546e29b6 | 726 | depends on PCI && GPIOLIB |
8edbede9 RR |
727 | ---help--- |
728 | This is the core driver for the timberdale FPGA. This device is a | |
729 | multifunction device which exposes numerous platform devices. | |
730 | ||
731 | The timberdale FPGA can be found on the Intel Atom development board | |
732 | for in-vehicle infontainment, called Russellville. | |
e82c60ae DT |
733 | |
734 | config LPC_SCH | |
735 | tristate "Intel SCH LPC" | |
736 | depends on PCI | |
737 | select MFD_CORE | |
738 | help | |
739 | LPC bridge function of the Intel SCH provides support for | |
740 | System Management Bus and General Purpose I/O. | |
741 | ||
e090d506 FF |
742 | config MFD_RDC321X |
743 | tristate "Support for RDC-R321x southbridge" | |
744 | select MFD_CORE | |
745 | depends on PCI | |
746 | help | |
747 | Say yes here if you want to have support for the RDC R-321x SoC | |
748 | southbridge which provides access to GPIOs and Watchdog using the | |
749 | southbridge PCI device configuration space. | |
750 | ||
bd358132 IS |
751 | config MFD_JANZ_CMODIO |
752 | tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board" | |
753 | select MFD_CORE | |
754 | depends on PCI | |
755 | help | |
756 | This is the core driver for the Janz CMOD-IO PCI MODULbus | |
757 | carrier board. This device is a PCI to MODULbus bridge which may | |
758 | host many different types of MODULbus daughterboards, including | |
759 | CAN and GPIO controllers. | |
760 | ||
91f4debf | 761 | config MFD_JZ4740_ADC |
914e6d4e | 762 | bool "Support for the JZ4740 SoC ADC core" |
91f4debf | 763 | select MFD_CORE |
914e6d4e | 764 | select GENERIC_IRQ_CHIP |
91f4debf LPC |
765 | depends on MACH_JZ4740 |
766 | help | |
767 | Say yes here if you want support for the ADC unit in the JZ4740 SoC. | |
768 | This driver is necessary for jz4740-battery and jz4740-hwmon driver. | |
769 | ||
375fc77b DD |
770 | config MFD_VX855 |
771 | tristate "Support for VIA VX855/VX875 integrated south bridge" | |
772 | depends on PCI | |
773 | select MFD_CORE | |
774 | help | |
775 | Say yes here to enable support for various functions of the | |
776 | VIA VX855/VX875 south bridge. You will need to enable the vx855_spi | |
777 | and/or vx855_gpio drivers for this to do anything useful. | |
778 | ||
383268a8 | 779 | config MFD_WL1273_CORE |
94fd5b74 | 780 | tristate "Support for TI WL1273 FM radio." |
383268a8 MA |
781 | depends on I2C |
782 | select MFD_CORE | |
783 | default n | |
784 | help | |
785 | This is the core driver for the TI WL1273 FM radio. This MFD | |
786 | driver connects the radio-wl1273 V4L2 module and the wl1273 | |
787 | audio codec. | |
788 | ||
17cdd29d KM |
789 | config MFD_OMAP_USB_HOST |
790 | bool "Support OMAP USBHS core driver" | |
791 | depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3 | |
792 | default y | |
793 | help | |
794 | This is the core driver for the OAMP EHCI and OHCI drivers. | |
795 | This MFD driver does the required setup functionalities for | |
796 | OMAP USB Host drivers. | |
797 | ||
cbdb53e1 AD |
798 | config MFD_PM8XXX |
799 | tristate | |
800 | ||
801 | config MFD_PM8921_CORE | |
802 | tristate "Qualcomm PM8921 PMIC chip" | |
803 | depends on MSM_SSBI | |
804 | select MFD_CORE | |
805 | select MFD_PM8XXX | |
806 | help | |
807 | If you say yes to this option, support will be included for the | |
808 | built-in PM8921 PMIC chip. | |
809 | ||
810 | This is required if your board has a PM8921 and uses its features, | |
811 | such as: MPPs, GPIOs, regulators, interrupts, and PWM. | |
812 | ||
813 | Say M here if you want to include support for PM8921 chip as a module. | |
814 | This will build a module called "pm8921-core". | |
815 | ||
c013f0a5 AD |
816 | config MFD_PM8XXX_IRQ |
817 | bool "Support for Qualcomm PM8xxx IRQ features" | |
818 | depends on MFD_PM8XXX | |
819 | default y if MFD_PM8XXX | |
820 | help | |
821 | This is the IRQ driver for Qualcomm PM 8xxx PMIC chips. | |
822 | ||
823 | This is required to use certain other PM 8xxx features, such as GPIO | |
824 | and MPP. | |
825 | ||
8509e142 AL |
826 | config TPS65911_COMPARATOR |
827 | tristate | |
828 | ||
09d6292b JP |
829 | config MFD_AAT2870_CORE |
830 | bool "Support for the AnalogicTech AAT2870" | |
831 | select MFD_CORE | |
832 | depends on I2C=y && GPIOLIB | |
833 | help | |
834 | If you say yes here you get support for the AAT2870. | |
835 | This driver provides common support for accessing the device, | |
836 | additional drivers must be enabled in order to use the | |
837 | functionality of the device. | |
838 | ||
1f5a371c MW |
839 | config MFD_INTEL_MSIC |
840 | bool "Support for Intel MSIC" | |
841 | depends on INTEL_SCU_IPC | |
842 | select MFD_CORE | |
843 | help | |
844 | Select this option to enable access to Intel MSIC (Avatele | |
845 | Passage) chip. This chip embeds audio, battery, GPIO, etc. | |
846 | devices used in Intel Medfield platforms. | |
847 | ||
8a0a8e8e AB |
848 | endmenu |
849 | endif | |
b6d6454f | 850 | |
a4e137ab | 851 | menu "Multimedia Capabilities Port drivers" |
f751d50f | 852 | depends on ARCH_SA1100 |
a4e137ab RK |
853 | |
854 | config MCP | |
855 | tristate | |
856 | ||
5e742ad6 RK |
857 | # Interface drivers |
858 | config MCP_SA11X0 | |
859 | tristate "Support SA11x0 MCP interface" | |
860 | depends on ARCH_SA1100 | |
861 | select MCP | |
862 | ||
05c45ca9 RK |
863 | # Chip drivers |
864 | config MCP_UCB1200 | |
865 | tristate "Support for UCB1200 / UCB1300" | |
866 | depends on MCP | |
867 | ||
acb45439 RK |
868 | config MCP_UCB1200_TS |
869 | tristate "Touchscreen interface support" | |
870 | depends on MCP_UCB1200 && INPUT | |
871 | ||
a4e137ab | 872 | endmenu |