]>
Commit | Line | Data |
---|---|---|
1 | # | |
2 | # Multifunction miscellaneous devices | |
3 | # | |
4 | ||
5 | if HAS_IOMEM | |
6 | menu "Multifunction device drivers" | |
7 | ||
8 | config MFD_CORE | |
9 | tristate | |
10 | default n | |
11 | ||
12 | config MFD_88PM860X | |
13 | bool "Support Marvell 88PM8606/88PM8607" | |
14 | depends on I2C=y && GENERIC_HARDIRQS | |
15 | select REGMAP_I2C | |
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 | ||
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 | |
28 | provide numerous interfaces including USB host controller, USB gadget, | |
29 | asynchronous serial ports, audio functions, and a dual display video | |
30 | interface. The device may be connected by PCI or local bus with | |
31 | varying functions enabled. | |
32 | ||
33 | config MFD_SM501_GPIO | |
34 | bool "Export GPIO via GPIO layer" | |
35 | depends on MFD_SM501 && GPIOLIB | |
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 | ||
41 | config MFD_ASIC3 | |
42 | bool "Support for Compaq ASIC3" | |
43 | depends on GENERIC_HARDIRQS && GPIOLIB && ARM | |
44 | select MFD_CORE | |
45 | ---help--- | |
46 | This driver supports the ASIC3 multifunction chip found on many | |
47 | PDAs (mainly iPAQ and HTC based ones) | |
48 | ||
49 | config MFD_DAVINCI_VOICECODEC | |
50 | tristate | |
51 | select MFD_CORE | |
52 | ||
53 | config MFD_DM355EVM_MSP | |
54 | bool "DaVinci DM355 EVM microcontroller" | |
55 | depends on I2C=y && MACH_DAVINCI_DM355_EVM | |
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 | ||
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 | ||
72 | config HTC_EGPIO | |
73 | bool "HTC EGPIO support" | |
74 | depends on GENERIC_HARDIRQS && GPIOLIB && ARM | |
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 | ||
80 | config HTC_PASIC3 | |
81 | tristate "HTC PASIC3 LED/DS1WM chip support" | |
82 | select MFD_CORE | |
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 | ||
89 | config HTC_I2CPLD | |
90 | bool "HTC I2C PLD chip support" | |
91 | depends on I2C=y && GPIOLIB | |
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 | ||
98 | config UCB1400_CORE | |
99 | tristate "Philips UCB1400 Core driver" | |
100 | depends on AC97_BUS | |
101 | depends on GPIOLIB | |
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 | ||
109 | config TPS6105X | |
110 | tristate "TPS61050/61052 Boost Converters" | |
111 | depends on I2C | |
112 | select REGULATOR | |
113 | select MFD_CORE | |
114 | select REGULATOR_FIXED_VOLTAGE | |
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 | ||
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 | ||
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 | ||
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 | ||
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 | ||
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 | select REGMAP_I2C | |
181 | help | |
182 | if you say yes here you get support for the TPS65910 series of | |
183 | Power Management chips. | |
184 | ||
185 | config MFD_TPS65912 | |
186 | bool | |
187 | depends on GPIOLIB | |
188 | ||
189 | config MFD_TPS65912_I2C | |
190 | bool "TPS65912 Power Management chip with I2C" | |
191 | select MFD_CORE | |
192 | select MFD_TPS65912 | |
193 | depends on I2C=y && GPIOLIB | |
194 | help | |
195 | If you say yes here you get support for the TPS65912 series of | |
196 | PM chips with I2C interface. | |
197 | ||
198 | config MFD_TPS65912_SPI | |
199 | bool "TPS65912 Power Management chip with SPI" | |
200 | select MFD_CORE | |
201 | select MFD_TPS65912 | |
202 | depends on SPI_MASTER && GPIOLIB | |
203 | help | |
204 | If you say yes here you get support for the TPS65912 series of | |
205 | PM chips with SPI interface. | |
206 | ||
207 | config MENELAUS | |
208 | bool "Texas Instruments TWL92330/Menelaus PM chip" | |
209 | depends on I2C=y && ARCH_OMAP2 | |
210 | help | |
211 | If you say yes here you get support for the Texas Instruments | |
212 | TWL92330/Menelaus Power Management chip. This include voltage | |
213 | regulators, Dual slot memory card transceivers, real-time clock | |
214 | and other features that are often used in portable devices like | |
215 | cell phones and PDAs. | |
216 | ||
217 | config TWL4030_CORE | |
218 | bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support" | |
219 | depends on I2C=y && GENERIC_HARDIRQS | |
220 | select IRQ_DOMAIN | |
221 | help | |
222 | Say yes here if you have TWL4030 / TWL6030 family chip on your board. | |
223 | This core driver provides register access and IRQ handling | |
224 | facilities, and registers devices for the various functions | |
225 | so that function-specific drivers can bind to them. | |
226 | ||
227 | These multi-function chips are found on many OMAP2 and OMAP3 | |
228 | boards, providing power management, RTC, GPIO, keypad, a | |
229 | high speed USB OTG transceiver, an audio codec (on most | |
230 | versions) and many other features. | |
231 | ||
232 | config TWL4030_MADC | |
233 | tristate "Texas Instruments TWL4030 MADC" | |
234 | depends on TWL4030_CORE | |
235 | help | |
236 | This driver provides support for triton TWL4030-MADC. The | |
237 | driver supports both RT and SW conversion methods. | |
238 | ||
239 | This driver can be built as a module. If so it will be | |
240 | named twl4030-madc | |
241 | ||
242 | config TWL4030_POWER | |
243 | bool "Support power resources on TWL4030 family chips" | |
244 | depends on TWL4030_CORE && ARM | |
245 | help | |
246 | Say yes here if you want to use the power resources on the | |
247 | TWL4030 family chips. Most of these resources are regulators, | |
248 | which have a separate driver; some are control signals, such | |
249 | as clock request handshaking. | |
250 | ||
251 | This driver uses board-specific data to initialize the resources | |
252 | and load scripts controlling which resources are switched off/on | |
253 | or reset when a sleep, wakeup or warm reset event occurs. | |
254 | ||
255 | config MFD_TWL4030_AUDIO | |
256 | bool | |
257 | depends on TWL4030_CORE | |
258 | select MFD_CORE | |
259 | default n | |
260 | ||
261 | config TWL6030_PWM | |
262 | tristate "TWL6030 PWM (Pulse Width Modulator) Support" | |
263 | depends on TWL4030_CORE | |
264 | select HAVE_PWM | |
265 | default n | |
266 | help | |
267 | Say yes here if you want support for TWL6030 PWM. | |
268 | This is used to control charging LED brightness. | |
269 | ||
270 | config TWL6040_CORE | |
271 | bool | |
272 | depends on TWL4030_CORE && GENERIC_HARDIRQS | |
273 | select MFD_CORE | |
274 | default n | |
275 | ||
276 | config MFD_STMPE | |
277 | bool "Support STMicroelectronics STMPE" | |
278 | depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS | |
279 | select MFD_CORE | |
280 | help | |
281 | Support for the STMPE family of I/O Expanders from | |
282 | STMicroelectronics. | |
283 | ||
284 | Currently supported devices are: | |
285 | ||
286 | STMPE811: GPIO, Touchscreen | |
287 | STMPE1601: GPIO, Keypad | |
288 | STMPE2401: GPIO, Keypad | |
289 | STMPE2403: GPIO, Keypad | |
290 | ||
291 | This driver provides common support for accessing the device, | |
292 | additional drivers must be enabled in order to use the functionality | |
293 | of the device. Currently available sub drivers are: | |
294 | ||
295 | GPIO: stmpe-gpio | |
296 | Keypad: stmpe-keypad | |
297 | Touchscreen: stmpe-ts | |
298 | ||
299 | menu "STMPE Interface Drivers" | |
300 | depends on MFD_STMPE | |
301 | ||
302 | config STMPE_I2C | |
303 | bool "STMPE I2C Inteface" | |
304 | depends on I2C=y | |
305 | default y | |
306 | help | |
307 | This is used to enable I2C interface of STMPE | |
308 | ||
309 | config STMPE_SPI | |
310 | bool "STMPE SPI Inteface" | |
311 | depends on SPI_MASTER | |
312 | help | |
313 | This is used to enable SPI interface of STMPE | |
314 | endmenu | |
315 | ||
316 | config MFD_TC3589X | |
317 | bool "Support Toshiba TC35892 and variants" | |
318 | depends on I2C=y && GENERIC_HARDIRQS | |
319 | select MFD_CORE | |
320 | help | |
321 | Support for the Toshiba TC35892 and variants I/O Expander. | |
322 | ||
323 | This driver provides common support for accessing the device, | |
324 | additional drivers must be enabled in order to use the | |
325 | functionality of the device. | |
326 | ||
327 | config MFD_TMIO | |
328 | bool | |
329 | default n | |
330 | ||
331 | config MFD_T7L66XB | |
332 | bool "Support Toshiba T7L66XB" | |
333 | depends on ARM && HAVE_CLK | |
334 | select MFD_CORE | |
335 | select MFD_TMIO | |
336 | help | |
337 | Support for Toshiba Mobile IO Controller T7L66XB | |
338 | ||
339 | config MFD_TC6387XB | |
340 | bool "Support Toshiba TC6387XB" | |
341 | depends on ARM && HAVE_CLK | |
342 | select MFD_CORE | |
343 | select MFD_TMIO | |
344 | help | |
345 | Support for Toshiba Mobile IO Controller TC6387XB | |
346 | ||
347 | config MFD_TC6393XB | |
348 | bool "Support Toshiba TC6393XB" | |
349 | depends on GPIOLIB && ARM && HAVE_CLK | |
350 | select MFD_CORE | |
351 | select MFD_TMIO | |
352 | help | |
353 | Support for Toshiba Mobile IO Controller TC6393XB | |
354 | ||
355 | config PMIC_DA903X | |
356 | bool "Dialog Semiconductor DA9030/DA9034 PMIC Support" | |
357 | depends on I2C=y | |
358 | help | |
359 | Say yes here to support for Dialog Semiconductor DA9030 (a.k.a | |
360 | ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC | |
361 | usually found on PXA processors-based platforms. This includes | |
362 | the I2C driver and the core APIs _only_, you have to select | |
363 | individual components like LCD backlight, voltage regulators, | |
364 | LEDs and battery-charger under the corresponding menus. | |
365 | ||
366 | config PMIC_DA9052 | |
367 | bool | |
368 | select MFD_CORE | |
369 | ||
370 | config MFD_DA9052_SPI | |
371 | bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI" | |
372 | select REGMAP_SPI | |
373 | select REGMAP_IRQ | |
374 | select PMIC_DA9052 | |
375 | depends on SPI_MASTER=y | |
376 | help | |
377 | Support for the Dialog Semiconductor DA9052 PMIC | |
378 | when controlled using SPI. This driver provides common support | |
379 | for accessing the device, additional drivers must be enabled in | |
380 | order to use the functionality of the device. | |
381 | ||
382 | config MFD_DA9052_I2C | |
383 | bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C" | |
384 | select REGMAP_I2C | |
385 | select REGMAP_IRQ | |
386 | select PMIC_DA9052 | |
387 | depends on I2C=y | |
388 | help | |
389 | Support for the Dialog Semiconductor DA9052 PMIC | |
390 | when controlled using I2C. This driver provides common support | |
391 | for accessing the device, additional drivers must be enabled in | |
392 | order to use the functionality of the device. | |
393 | ||
394 | config PMIC_ADP5520 | |
395 | bool "Analog Devices ADP5520/01 MFD PMIC Core Support" | |
396 | depends on I2C=y | |
397 | help | |
398 | Say yes here to add support for Analog Devices AD5520 and ADP5501, | |
399 | Multifunction Power Management IC. This includes | |
400 | the I2C driver and the core APIs _only_, you have to select | |
401 | individual components like LCD backlight, LEDs, GPIOs and Kepad | |
402 | under the corresponding menus. | |
403 | ||
404 | config MFD_MAX8925 | |
405 | bool "Maxim Semiconductor MAX8925 PMIC Support" | |
406 | depends on I2C=y && GENERIC_HARDIRQS | |
407 | select MFD_CORE | |
408 | help | |
409 | Say yes here to support for Maxim Semiconductor MAX8925. This is | |
410 | a Power Management IC. This driver provies common support for | |
411 | accessing the device, additional drivers must be enabled in order | |
412 | to use the functionality of the device. | |
413 | ||
414 | config MFD_MAX8997 | |
415 | bool "Maxim Semiconductor MAX8997/8966 PMIC Support" | |
416 | depends on I2C=y && GENERIC_HARDIRQS | |
417 | select MFD_CORE | |
418 | help | |
419 | Say yes here to support for Maxim Semiconductor MAX8997/8966. | |
420 | This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic, | |
421 | MUIC controls on chip. | |
422 | This driver provides common support for accessing the device; | |
423 | additional drivers must be enabled in order to use the functionality | |
424 | of the device. | |
425 | ||
426 | config MFD_MAX8998 | |
427 | bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support" | |
428 | depends on I2C=y && GENERIC_HARDIRQS | |
429 | select MFD_CORE | |
430 | help | |
431 | Say yes here to support for Maxim Semiconductor MAX8998 and | |
432 | National Semiconductor LP3974. This is a Power Management IC. | |
433 | This driver provies common support for accessing the device, | |
434 | additional drivers must be enabled in order to use the functionality | |
435 | of the device. | |
436 | ||
437 | config MFD_S5M_CORE | |
438 | bool "SAMSUNG S5M Series Support" | |
439 | depends on I2C=y && GENERIC_HARDIRQS | |
440 | select MFD_CORE | |
441 | select REGMAP_I2C | |
442 | help | |
443 | Support for the Samsung Electronics S5M MFD series. | |
444 | This driver provies common support for accessing the device, | |
445 | additional drivers must be enabled in order to use the functionality | |
446 | of the device | |
447 | ||
448 | config MFD_WM8400 | |
449 | tristate "Support Wolfson Microelectronics WM8400" | |
450 | select MFD_CORE | |
451 | depends on I2C | |
452 | select REGMAP_I2C | |
453 | help | |
454 | Support for the Wolfson Microelecronics WM8400 PMIC and audio | |
455 | CODEC. This driver provides common support for accessing | |
456 | the device, additional drivers must be enabled in order to use | |
457 | the functionality of the device. | |
458 | ||
459 | config MFD_WM831X | |
460 | bool | |
461 | depends on GENERIC_HARDIRQS | |
462 | ||
463 | config MFD_WM831X_I2C | |
464 | bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C" | |
465 | select MFD_CORE | |
466 | select MFD_WM831X | |
467 | select REGMAP_I2C | |
468 | depends on I2C=y && GENERIC_HARDIRQS | |
469 | help | |
470 | Support for the Wolfson Microelecronics WM831x and WM832x PMICs | |
471 | when controlled using I2C. This driver provides common support | |
472 | for accessing the device, additional drivers must be enabled in | |
473 | order to use the functionality of the device. | |
474 | ||
475 | config MFD_WM831X_SPI | |
476 | bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI" | |
477 | select MFD_CORE | |
478 | select MFD_WM831X | |
479 | select REGMAP_SPI | |
480 | depends on SPI_MASTER && GENERIC_HARDIRQS | |
481 | help | |
482 | Support for the Wolfson Microelecronics WM831x and WM832x PMICs | |
483 | when controlled using SPI. This driver provides common support | |
484 | for accessing the device, additional drivers must be enabled in | |
485 | order to use the functionality of the device. | |
486 | ||
487 | config MFD_WM8350 | |
488 | bool | |
489 | depends on GENERIC_HARDIRQS | |
490 | ||
491 | config MFD_WM8350_CONFIG_MODE_0 | |
492 | bool | |
493 | depends on MFD_WM8350 | |
494 | ||
495 | config MFD_WM8350_CONFIG_MODE_1 | |
496 | bool | |
497 | depends on MFD_WM8350 | |
498 | ||
499 | config MFD_WM8350_CONFIG_MODE_2 | |
500 | bool | |
501 | depends on MFD_WM8350 | |
502 | ||
503 | config MFD_WM8350_CONFIG_MODE_3 | |
504 | bool | |
505 | depends on MFD_WM8350 | |
506 | ||
507 | config MFD_WM8351_CONFIG_MODE_0 | |
508 | bool | |
509 | depends on MFD_WM8350 | |
510 | ||
511 | config MFD_WM8351_CONFIG_MODE_1 | |
512 | bool | |
513 | depends on MFD_WM8350 | |
514 | ||
515 | config MFD_WM8351_CONFIG_MODE_2 | |
516 | bool | |
517 | depends on MFD_WM8350 | |
518 | ||
519 | config MFD_WM8351_CONFIG_MODE_3 | |
520 | bool | |
521 | depends on MFD_WM8350 | |
522 | ||
523 | config MFD_WM8352_CONFIG_MODE_0 | |
524 | bool | |
525 | depends on MFD_WM8350 | |
526 | ||
527 | config MFD_WM8352_CONFIG_MODE_1 | |
528 | bool | |
529 | depends on MFD_WM8350 | |
530 | ||
531 | config MFD_WM8352_CONFIG_MODE_2 | |
532 | bool | |
533 | depends on MFD_WM8350 | |
534 | ||
535 | config MFD_WM8352_CONFIG_MODE_3 | |
536 | bool | |
537 | depends on MFD_WM8350 | |
538 | ||
539 | config MFD_WM8350_I2C | |
540 | bool "Support Wolfson Microelectronics WM8350 with I2C" | |
541 | select MFD_WM8350 | |
542 | depends on I2C=y && GENERIC_HARDIRQS | |
543 | help | |
544 | The WM8350 is an integrated audio and power management | |
545 | subsystem with watchdog and RTC functionality for embedded | |
546 | systems. This option enables core support for the WM8350 with | |
547 | I2C as the control interface. Additional options must be | |
548 | selected to enable support for the functionality of the chip. | |
549 | ||
550 | config MFD_WM8994 | |
551 | bool "Support Wolfson Microelectronics WM8994" | |
552 | select MFD_CORE | |
553 | select REGMAP_I2C | |
554 | select REGMAP_IRQ | |
555 | depends on I2C=y && GENERIC_HARDIRQS | |
556 | help | |
557 | The WM8994 is a highly integrated hi-fi CODEC designed for | |
558 | smartphone applicatiosn. As well as audio functionality it | |
559 | has on board GPIO and regulator functionality which is | |
560 | supported via the relevant subsystems. This driver provides | |
561 | core support for the WM8994, in order to use the actual | |
562 | functionaltiy of the device other drivers must be enabled. | |
563 | ||
564 | config MFD_PCF50633 | |
565 | tristate "Support for NXP PCF50633" | |
566 | depends on I2C | |
567 | select REGMAP_I2C | |
568 | help | |
569 | Say yes here if you have NXP PCF50633 chip on your board. | |
570 | This core driver provides register access and IRQ handling | |
571 | facilities, and registers devices for the various functions | |
572 | so that function-specific drivers can bind to them. | |
573 | ||
574 | config PCF50633_ADC | |
575 | tristate "Support for NXP PCF50633 ADC" | |
576 | depends on MFD_PCF50633 | |
577 | help | |
578 | Say yes here if you want to include support for ADC in the | |
579 | NXP PCF50633 chip. | |
580 | ||
581 | config PCF50633_GPIO | |
582 | tristate "Support for NXP PCF50633 GPIO" | |
583 | depends on MFD_PCF50633 | |
584 | help | |
585 | Say yes here if you want to include support GPIO for pins on | |
586 | the PCF50633 chip. | |
587 | ||
588 | config MFD_MC13783 | |
589 | tristate | |
590 | ||
591 | config MFD_MC13XXX | |
592 | tristate "Support Freescale MC13783 and MC13892" | |
593 | depends on SPI_MASTER | |
594 | select MFD_CORE | |
595 | select MFD_MC13783 | |
596 | help | |
597 | Support for the Freescale (Atlas) PMIC and audio CODECs | |
598 | MC13783 and MC13892. | |
599 | This driver provides common support for accessing the device, | |
600 | additional drivers must be enabled in order to use the | |
601 | functionality of the device. | |
602 | ||
603 | config ABX500_CORE | |
604 | bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions" | |
605 | default y if ARCH_U300 || ARCH_U8500 | |
606 | help | |
607 | Say yes here if you have the ABX500 Mixed Signal IC family | |
608 | chips. This core driver expose register access functions. | |
609 | Functionality specific drivers using these functions can | |
610 | remain unchanged when IC changes. Binding of the functions to | |
611 | actual register access is done by the IC core driver. | |
612 | ||
613 | config AB3100_CORE | |
614 | bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions" | |
615 | depends on I2C=y && ABX500_CORE | |
616 | select MFD_CORE | |
617 | default y if ARCH_U300 | |
618 | help | |
619 | Select this to enable the AB3100 Mixed Signal IC core | |
620 | functionality. This connects to a AB3100 on the I2C bus | |
621 | and expose a number of symbols needed for dependent devices | |
622 | to read and write registers and subscribe to events from | |
623 | this multi-functional IC. This is needed to use other features | |
624 | of the AB3100 such as battery-backed RTC, charging control, | |
625 | LEDs, vibrator, system power and temperature, power management | |
626 | and ALSA sound. | |
627 | ||
628 | config AB3100_OTP | |
629 | tristate "ST-Ericsson AB3100 OTP functions" | |
630 | depends on AB3100_CORE | |
631 | default y if AB3100_CORE | |
632 | help | |
633 | Select this to enable the AB3100 Mixed Signal IC OTP (one-time | |
634 | programmable memory) support. This exposes a sysfs file to read | |
635 | out OTP values. | |
636 | ||
637 | config EZX_PCAP | |
638 | bool "PCAP Support" | |
639 | depends on GENERIC_HARDIRQS && SPI_MASTER | |
640 | help | |
641 | This enables the PCAP ASIC present on EZX Phones. This is | |
642 | needed for MMC, TouchScreen, Sound, USB, etc.. | |
643 | ||
644 | config AB5500_CORE | |
645 | bool "ST-Ericsson AB5500 Mixed Signal Power Management chip" | |
646 | depends on ABX500_CORE && MFD_DB5500_PRCMU | |
647 | select MFD_CORE | |
648 | help | |
649 | Select this option to enable access to AB5500 power management | |
650 | chip. This connects to the db5500 chip via the I2C bus via PRCMU. | |
651 | This chip embeds various other multimedia funtionalities as well. | |
652 | ||
653 | config AB5500_DEBUG | |
654 | bool "Enable debug info via debugfs" | |
655 | depends on AB5500_CORE && DEBUG_FS | |
656 | default y if DEBUG_FS | |
657 | help | |
658 | Select this option if you want debug information from the AB5500 | |
659 | using the debug filesystem, debugfs. | |
660 | ||
661 | config AB8500_CORE | |
662 | bool "ST-Ericsson AB8500 Mixed Signal Power Management chip" | |
663 | depends on GENERIC_HARDIRQS && ABX500_CORE | |
664 | select MFD_CORE | |
665 | help | |
666 | Select this option to enable access to AB8500 power management | |
667 | chip. This connects to U8500 either on the SSP/SPI bus (deprecated | |
668 | since hardware version v1.0) or the I2C bus via PRCMU. It also adds | |
669 | the irq_chip parts for handling the Mixed Signal chip events. | |
670 | This chip embeds various other multimedia funtionalities as well. | |
671 | ||
672 | config AB8500_I2C_CORE | |
673 | bool "AB8500 register access via PRCMU I2C" | |
674 | depends on AB8500_CORE && MFD_DB8500_PRCMU | |
675 | default y | |
676 | help | |
677 | This enables register access to the AB8500 chip via PRCMU I2C. | |
678 | The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware | |
679 | the I2C bus is connected to the Power Reset | |
680 | and Mangagement Unit, PRCMU. | |
681 | ||
682 | config AB8500_DEBUG | |
683 | bool "Enable debug info via debugfs" | |
684 | depends on AB8500_CORE && DEBUG_FS | |
685 | default y if DEBUG_FS | |
686 | help | |
687 | Select this option if you want debug information using the debug | |
688 | filesystem, debugfs. | |
689 | ||
690 | config AB8500_GPADC | |
691 | bool "AB8500 GPADC driver" | |
692 | depends on AB8500_CORE && REGULATOR_AB8500 | |
693 | default y | |
694 | help | |
695 | AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage | |
696 | ||
697 | config MFD_DB8500_PRCMU | |
698 | bool "ST-Ericsson DB8500 Power Reset Control Management Unit" | |
699 | depends on UX500_SOC_DB8500 | |
700 | select MFD_CORE | |
701 | help | |
702 | Select this option to enable support for the DB8500 Power Reset | |
703 | and Control Management Unit. This is basically an autonomous | |
704 | system controller running an XP70 microprocessor, which is accessed | |
705 | through a register map. | |
706 | ||
707 | config MFD_DB5500_PRCMU | |
708 | bool "ST-Ericsson DB5500 Power Reset Control Management Unit" | |
709 | depends on UX500_SOC_DB5500 | |
710 | select MFD_CORE | |
711 | help | |
712 | Select this option to enable support for the DB5500 Power Reset | |
713 | and Control Management Unit. This is basically an autonomous | |
714 | system controller running an XP70 microprocessor, which is accessed | |
715 | through a register map. | |
716 | ||
717 | config MFD_CS5535 | |
718 | tristate "Support for CS5535 and CS5536 southbridge core functions" | |
719 | select MFD_CORE | |
720 | depends on PCI && X86 | |
721 | ---help--- | |
722 | This is the core driver for CS5535/CS5536 MFD functions. This is | |
723 | necessary for using the board's GPIO and MFGPT functionality. | |
724 | ||
725 | config MFD_TIMBERDALE | |
726 | tristate "Support for the Timberdale FPGA" | |
727 | select MFD_CORE | |
728 | depends on PCI && GPIOLIB | |
729 | ---help--- | |
730 | This is the core driver for the timberdale FPGA. This device is a | |
731 | multifunction device which exposes numerous platform devices. | |
732 | ||
733 | The timberdale FPGA can be found on the Intel Atom development board | |
734 | for in-vehicle infontainment, called Russellville. | |
735 | ||
736 | config LPC_SCH | |
737 | tristate "Intel SCH LPC" | |
738 | depends on PCI | |
739 | select MFD_CORE | |
740 | help | |
741 | LPC bridge function of the Intel SCH provides support for | |
742 | System Management Bus and General Purpose I/O. | |
743 | ||
744 | config MFD_RDC321X | |
745 | tristate "Support for RDC-R321x southbridge" | |
746 | select MFD_CORE | |
747 | depends on PCI | |
748 | help | |
749 | Say yes here if you want to have support for the RDC R-321x SoC | |
750 | southbridge which provides access to GPIOs and Watchdog using the | |
751 | southbridge PCI device configuration space. | |
752 | ||
753 | config MFD_JANZ_CMODIO | |
754 | tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board" | |
755 | select MFD_CORE | |
756 | depends on PCI | |
757 | help | |
758 | This is the core driver for the Janz CMOD-IO PCI MODULbus | |
759 | carrier board. This device is a PCI to MODULbus bridge which may | |
760 | host many different types of MODULbus daughterboards, including | |
761 | CAN and GPIO controllers. | |
762 | ||
763 | config MFD_JZ4740_ADC | |
764 | bool "Support for the JZ4740 SoC ADC core" | |
765 | select MFD_CORE | |
766 | select GENERIC_IRQ_CHIP | |
767 | depends on MACH_JZ4740 | |
768 | help | |
769 | Say yes here if you want support for the ADC unit in the JZ4740 SoC. | |
770 | This driver is necessary for jz4740-battery and jz4740-hwmon driver. | |
771 | ||
772 | config MFD_VX855 | |
773 | tristate "Support for VIA VX855/VX875 integrated south bridge" | |
774 | depends on PCI | |
775 | select MFD_CORE | |
776 | help | |
777 | Say yes here to enable support for various functions of the | |
778 | VIA VX855/VX875 south bridge. You will need to enable the vx855_spi | |
779 | and/or vx855_gpio drivers for this to do anything useful. | |
780 | ||
781 | config MFD_WL1273_CORE | |
782 | tristate "Support for TI WL1273 FM radio." | |
783 | depends on I2C | |
784 | select MFD_CORE | |
785 | default n | |
786 | help | |
787 | This is the core driver for the TI WL1273 FM radio. This MFD | |
788 | driver connects the radio-wl1273 V4L2 module and the wl1273 | |
789 | audio codec. | |
790 | ||
791 | config MFD_OMAP_USB_HOST | |
792 | bool "Support OMAP USBHS core driver" | |
793 | depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3 | |
794 | default y | |
795 | help | |
796 | This is the core driver for the OAMP EHCI and OHCI drivers. | |
797 | This MFD driver does the required setup functionalities for | |
798 | OMAP USB Host drivers. | |
799 | ||
800 | config MFD_PM8XXX | |
801 | tristate | |
802 | ||
803 | config MFD_PM8921_CORE | |
804 | tristate "Qualcomm PM8921 PMIC chip" | |
805 | depends on MSM_SSBI | |
806 | select MFD_CORE | |
807 | select MFD_PM8XXX | |
808 | help | |
809 | If you say yes to this option, support will be included for the | |
810 | built-in PM8921 PMIC chip. | |
811 | ||
812 | This is required if your board has a PM8921 and uses its features, | |
813 | such as: MPPs, GPIOs, regulators, interrupts, and PWM. | |
814 | ||
815 | Say M here if you want to include support for PM8921 chip as a module. | |
816 | This will build a module called "pm8921-core". | |
817 | ||
818 | config MFD_PM8XXX_IRQ | |
819 | bool "Support for Qualcomm PM8xxx IRQ features" | |
820 | depends on MFD_PM8XXX | |
821 | default y if MFD_PM8XXX | |
822 | help | |
823 | This is the IRQ driver for Qualcomm PM 8xxx PMIC chips. | |
824 | ||
825 | This is required to use certain other PM 8xxx features, such as GPIO | |
826 | and MPP. | |
827 | ||
828 | config TPS65911_COMPARATOR | |
829 | tristate | |
830 | ||
831 | config MFD_TPS65090 | |
832 | bool "TPS65090 Power Management chips" | |
833 | depends on I2C=y && GENERIC_HARDIRQS | |
834 | select MFD_CORE | |
835 | select REGMAP_I2C | |
836 | help | |
837 | If you say yes here you get support for the TPS65090 series of | |
838 | Power Management chips. | |
839 | This driver provides common support for accessing the device, | |
840 | additional drivers must be enabled in order to use the | |
841 | functionality of the device. | |
842 | ||
843 | config MFD_AAT2870_CORE | |
844 | bool "Support for the AnalogicTech AAT2870" | |
845 | select MFD_CORE | |
846 | depends on I2C=y && GPIOLIB | |
847 | help | |
848 | If you say yes here you get support for the AAT2870. | |
849 | This driver provides common support for accessing the device, | |
850 | additional drivers must be enabled in order to use the | |
851 | functionality of the device. | |
852 | ||
853 | config MFD_INTEL_MSIC | |
854 | bool "Support for Intel MSIC" | |
855 | depends on INTEL_SCU_IPC | |
856 | select MFD_CORE | |
857 | help | |
858 | Select this option to enable access to Intel MSIC (Avatele | |
859 | Passage) chip. This chip embeds audio, battery, GPIO, etc. | |
860 | devices used in Intel Medfield platforms. | |
861 | ||
862 | config MFD_RC5T583 | |
863 | bool "Ricoh RC5T583 Power Management system device" | |
864 | depends on I2C=y && GENERIC_HARDIRQS | |
865 | select MFD_CORE | |
866 | select REGMAP_I2C | |
867 | help | |
868 | Select this option to get support for the RICOH583 Power | |
869 | Management system device. | |
870 | This driver provides common support for accessing the device | |
871 | through i2c interface. The device supports multiple sub-devices | |
872 | like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey. | |
873 | Additional drivers must be enabled in order to use the | |
874 | different functionality of the device. | |
875 | ||
876 | config MFD_ANATOP | |
877 | bool "Support for Freescale i.MX on-chip ANATOP controller" | |
878 | depends on SOC_IMX6Q | |
879 | help | |
880 | Select this option to enable Freescale i.MX on-chip ANATOP | |
881 | MFD controller. This controller embeds regulator and | |
882 | thermal devices for Freescale i.MX platforms. | |
883 | ||
884 | endmenu | |
885 | endif | |
886 | ||
887 | menu "Multimedia Capabilities Port drivers" | |
888 | depends on ARCH_SA1100 | |
889 | ||
890 | config MCP | |
891 | tristate | |
892 | ||
893 | # Interface drivers | |
894 | config MCP_SA11X0 | |
895 | tristate "Support SA11x0 MCP interface" | |
896 | depends on ARCH_SA1100 | |
897 | select MCP | |
898 | ||
899 | # Chip drivers | |
900 | config MCP_UCB1200 | |
901 | bool "Support for UCB1200 / UCB1300" | |
902 | depends on MCP_SA11X0 | |
903 | select MCP | |
904 | ||
905 | config MCP_UCB1200_TS | |
906 | tristate "Touchscreen interface support" | |
907 | depends on MCP_UCB1200 && INPUT | |
908 | ||
909 | endmenu |