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