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