Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tjh.dev
kernel
os
linux
1#
2# Multifunction miscellaneous devices
3#
4
5menuconfig MFD_SUPPORT
6 bool "Multifunction device drivers"
7 depends on HAS_IOMEM
8 default y
9 help
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.
20
21if MFD_SUPPORT
22
23config MFD_CORE
24 tristate
25 default n
26
27config MFD_88PM860X
28 bool "Support Marvell 88PM8606/88PM8607"
29 depends on I2C=y && GENERIC_HARDIRQS
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
37config 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
42 provide numerous interfaces including USB host controller, USB gadget,
43 asynchronous serial ports, audio functions, and a dual display video
44 interface. The device may be connected by PCI or local bus with
45 varying functions enabled.
46
47config MFD_SM501_GPIO
48 bool "Export GPIO via GPIO layer"
49 depends on MFD_SM501 && GPIOLIB
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
55config MFD_ASIC3
56 bool "Support for Compaq ASIC3"
57 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
58 select MFD_CORE
59 ---help---
60 This driver supports the ASIC3 multifunction chip found on many
61 PDAs (mainly iPAQ and HTC based ones)
62
63config MFD_DAVINCI_VOICECODEC
64 tristate
65 select MFD_CORE
66
67config MFD_DM355EVM_MSP
68 bool "DaVinci DM355 EVM microcontroller"
69 depends on I2C=y && MACH_DAVINCI_DM355_EVM
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
75config 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
86config HTC_EGPIO
87 bool "HTC EGPIO support"
88 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
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
94config HTC_PASIC3
95 tristate "HTC PASIC3 LED/DS1WM chip support"
96 select MFD_CORE
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
103config HTC_I2CPLD
104 bool "HTC I2C PLD chip support"
105 depends on I2C=y && GPIOLIB
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
112config UCB1400_CORE
113 tristate "Philips UCB1400 Core driver"
114 depends on AC97_BUS
115 depends on GPIOLIB
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
123config TPS6105X
124 tristate "TPS61050/61052 Boost Converters"
125 depends on I2C
126 select REGULATOR
127 select MFD_CORE
128 select REGULATOR_FIXED_VOLTAGE
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
135config 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
148config 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
160config 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
174config 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
183config MFD_TPS65912
184 bool
185 depends on GPIOLIB
186
187config 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
196config 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
205config MENELAUS
206 bool "Texas Instruments TWL92330/Menelaus PM chip"
207 depends on I2C=y && ARCH_OMAP2
208 help
209 If you say yes here you get support for the Texas Instruments
210 TWL92330/Menelaus Power Management chip. This include voltage
211 regulators, Dual slot memory card transceivers, real-time clock
212 and other features that are often used in portable devices like
213 cell phones and PDAs.
214
215config TWL4030_CORE
216 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
217 depends on I2C=y && GENERIC_HARDIRQS
218 help
219 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
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
229config 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
239config 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
249 and load scripts controlling which resources are switched off/on
250 or reset when a sleep, wakeup or warm reset event occurs.
251
252config MFD_TWL4030_AUDIO
253 bool
254 depends on TWL4030_CORE
255 select MFD_CORE
256 default n
257
258config 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
267config TWL6040_CORE
268 bool
269 depends on TWL4030_CORE && GENERIC_HARDIRQS
270 select MFD_CORE
271 default n
272
273config 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
296config MFD_TC3589X
297 bool "Support Toshiba TC35892 and variants"
298 depends on I2C=y && GENERIC_HARDIRQS
299 select MFD_CORE
300 help
301 Support for the Toshiba TC35892 and variants I/O Expander.
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
307config MFD_TMIO
308 bool
309 default n
310
311config MFD_T7L66XB
312 bool "Support Toshiba T7L66XB"
313 depends on ARM && HAVE_CLK
314 select MFD_CORE
315 select MFD_TMIO
316 help
317 Support for Toshiba Mobile IO Controller T7L66XB
318
319config MFD_TC6387XB
320 bool "Support Toshiba TC6387XB"
321 depends on ARM && HAVE_CLK
322 select MFD_CORE
323 select MFD_TMIO
324 help
325 Support for Toshiba Mobile IO Controller TC6387XB
326
327config MFD_TC6393XB
328 bool "Support Toshiba TC6393XB"
329 depends on GPIOLIB && ARM
330 select MFD_CORE
331 select MFD_TMIO
332 help
333 Support for Toshiba Mobile IO Controller TC6393XB
334
335config 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.
345
346config 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.
355
356config MFD_MAX8925
357 bool "Maxim Semiconductor MAX8925 PMIC Support"
358 depends on I2C=y && GENERIC_HARDIRQS
359 select MFD_CORE
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
366config 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.
374 This driver provides common support for accessing the device;
375 additional drivers must be enabled in order to use the functionality
376 of the device.
377
378config MFD_MAX8998
379 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
380 depends on I2C=y && GENERIC_HARDIRQS
381 select MFD_CORE
382 help
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.
388
389config MFD_WM8400
390 tristate "Support Wolfson Microelectronics WM8400"
391 select MFD_CORE
392 depends on I2C
393 help
394 Support for the Wolfson Microelecronics WM8400 PMIC and audio
395 CODEC. This driver provides common support for accessing
396 the device, additional drivers must be enabled in order to use
397 the functionality of the device.
398
399config MFD_WM831X
400 bool
401 depends on GENERIC_HARDIRQS
402
403config MFD_WM831X_I2C
404 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
405 select MFD_CORE
406 select MFD_WM831X
407 depends on I2C=y && GENERIC_HARDIRQS
408 help
409 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
410 when controlled using I2C. This driver provides common support
411 for accessing the device, additional drivers must be enabled in
412 order to use the functionality of the device.
413
414config MFD_WM831X_SPI
415 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
416 select MFD_CORE
417 select MFD_WM831X
418 depends on SPI_MASTER && GENERIC_HARDIRQS
419 help
420 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
421 when controlled using SPI. This driver provides common support
422 for accessing the device, additional drivers must be enabled in
423 order to use the functionality of the device.
424
425config MFD_WM8350
426 bool
427 depends on GENERIC_HARDIRQS
428
429config MFD_WM8350_CONFIG_MODE_0
430 bool
431 depends on MFD_WM8350
432
433config MFD_WM8350_CONFIG_MODE_1
434 bool
435 depends on MFD_WM8350
436
437config MFD_WM8350_CONFIG_MODE_2
438 bool
439 depends on MFD_WM8350
440
441config MFD_WM8350_CONFIG_MODE_3
442 bool
443 depends on MFD_WM8350
444
445config MFD_WM8351_CONFIG_MODE_0
446 bool
447 depends on MFD_WM8350
448
449config MFD_WM8351_CONFIG_MODE_1
450 bool
451 depends on MFD_WM8350
452
453config MFD_WM8351_CONFIG_MODE_2
454 bool
455 depends on MFD_WM8350
456
457config MFD_WM8351_CONFIG_MODE_3
458 bool
459 depends on MFD_WM8350
460
461config MFD_WM8352_CONFIG_MODE_0
462 bool
463 depends on MFD_WM8350
464
465config MFD_WM8352_CONFIG_MODE_1
466 bool
467 depends on MFD_WM8350
468
469config MFD_WM8352_CONFIG_MODE_2
470 bool
471 depends on MFD_WM8350
472
473config MFD_WM8352_CONFIG_MODE_3
474 bool
475 depends on MFD_WM8350
476
477config MFD_WM8350_I2C
478 bool "Support Wolfson Microelectronics WM8350 with I2C"
479 select MFD_WM8350
480 depends on I2C=y && GENERIC_HARDIRQS
481 help
482 The WM8350 is an integrated audio and power management
483 subsystem with watchdog and RTC functionality for embedded
484 systems. This option enables core support for the WM8350 with
485 I2C as the control interface. Additional options must be
486 selected to enable support for the functionality of the chip.
487
488config MFD_WM8994
489 bool "Support Wolfson Microelectronics WM8994"
490 select MFD_CORE
491 depends on I2C=y && GENERIC_HARDIRQS
492 help
493 The WM8994 is a highly integrated hi-fi CODEC designed for
494 smartphone applicatiosn. As well as audio functionality it
495 has on board GPIO and regulator functionality which is
496 supported via the relevant subsystems. This driver provides
497 core support for the WM8994, in order to use the actual
498 functionaltiy of the device other drivers must be enabled.
499
500config MFD_PCF50633
501 tristate "Support for NXP PCF50633"
502 depends on I2C
503 help
504 Say yes here if you have NXP PCF50633 chip on your board.
505 This core driver provides register access and IRQ handling
506 facilities, and registers devices for the various functions
507 so that function-specific drivers can bind to them.
508
509config PCF50633_ADC
510 tristate "Support for NXP PCF50633 ADC"
511 depends on MFD_PCF50633
512 help
513 Say yes here if you want to include support for ADC in the
514 NXP PCF50633 chip.
515
516config PCF50633_GPIO
517 tristate "Support for NXP PCF50633 GPIO"
518 depends on MFD_PCF50633
519 help
520 Say yes here if you want to include support GPIO for pins on
521 the PCF50633 chip.
522
523config MFD_MC13783
524 tristate
525
526config MFD_MC13XXX
527 tristate "Support Freescale MC13783 and MC13892"
528 depends on SPI_MASTER
529 select MFD_CORE
530 select MFD_MC13783
531 help
532 Support for the Freescale (Atlas) PMIC and audio CODECs
533 MC13783 and MC13892.
534 This driver provides common support for accessing the device,
535 additional drivers must be enabled in order to use the
536 functionality of the device.
537
538config ABX500_CORE
539 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
540 default y if ARCH_U300 || ARCH_U8500
541 help
542 Say yes here if you have the ABX500 Mixed Signal IC family
543 chips. This core driver expose register access functions.
544 Functionality specific drivers using these functions can
545 remain unchanged when IC changes. Binding of the functions to
546 actual register access is done by the IC core driver.
547
548config AB3100_CORE
549 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
550 depends on I2C=y && ABX500_CORE
551 select MFD_CORE
552 default y if ARCH_U300
553 help
554 Select this to enable the AB3100 Mixed Signal IC core
555 functionality. This connects to a AB3100 on the I2C bus
556 and expose a number of symbols needed for dependent devices
557 to read and write registers and subscribe to events from
558 this multi-functional IC. This is needed to use other features
559 of the AB3100 such as battery-backed RTC, charging control,
560 LEDs, vibrator, system power and temperature, power management
561 and ALSA sound.
562
563config AB3100_OTP
564 tristate "ST-Ericsson AB3100 OTP functions"
565 depends on AB3100_CORE
566 default y if AB3100_CORE
567 help
568 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
569 programmable memory) support. This exposes a sysfs file to read
570 out OTP values.
571
572config EZX_PCAP
573 bool "PCAP Support"
574 depends on GENERIC_HARDIRQS && SPI_MASTER
575 help
576 This enables the PCAP ASIC present on EZX Phones. This is
577 needed for MMC, TouchScreen, Sound, USB, etc..
578
579config AB8500_CORE
580 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
581 depends on GENERIC_HARDIRQS && ABX500_CORE
582 select MFD_CORE
583 help
584 Select this option to enable access to AB8500 power management
585 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
586 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
587 the irq_chip parts for handling the Mixed Signal chip events.
588 This chip embeds various other multimedia funtionalities as well.
589
590config AB8500_I2C_CORE
591 bool "AB8500 register access via PRCMU I2C"
592 depends on AB8500_CORE && MFD_DB8500_PRCMU
593 default y
594 help
595 This enables register access to the AB8500 chip via PRCMU I2C.
596 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
597 the I2C bus is connected to the Power Reset
598 and Mangagement Unit, PRCMU.
599
600config AB8500_DEBUG
601 bool "Enable debug info via debugfs"
602 depends on AB8500_CORE && DEBUG_FS
603 default y if DEBUG_FS
604 help
605 Select this option if you want debug information using the debug
606 filesystem, debugfs.
607
608config AB8500_GPADC
609 bool "AB8500 GPADC driver"
610 depends on AB8500_CORE && REGULATOR_AB8500
611 default y
612 help
613 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
614
615config AB3550_CORE
616 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
617 select MFD_CORE
618 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
619 help
620 Select this to enable the AB3550 Mixed Signal IC core
621 functionality. This connects to a AB3550 on the I2C bus
622 and expose a number of symbols needed for dependent devices
623 to read and write registers and subscribe to events from
624 this multi-functional IC. This is needed to use other features
625 of the AB3550 such as battery-backed RTC, charging control,
626 LEDs, vibrator, system power and temperature, power management
627 and ALSA sound.
628
629config MFD_DB8500_PRCMU
630 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
631 depends on UX500_SOC_DB8500
632 select MFD_CORE
633 help
634 Select this option to enable support for the DB8500 Power Reset
635 and Control Management Unit. This is basically an autonomous
636 system controller running an XP70 microprocessor, which is accessed
637 through a register map.
638
639config MFD_DB5500_PRCMU
640 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
641 depends on UX500_SOC_DB5500
642 select MFD_CORE
643 help
644 Select this option to enable support for the DB5500 Power Reset
645 and Control Management Unit. This is basically an autonomous
646 system controller running an XP70 microprocessor, which is accessed
647 through a register map.
648
649config MFD_CS5535
650 tristate "Support for CS5535 and CS5536 southbridge core functions"
651 select MFD_CORE
652 depends on PCI && X86
653 ---help---
654 This is the core driver for CS5535/CS5536 MFD functions. This is
655 necessary for using the board's GPIO and MFGPT functionality.
656
657config MFD_TIMBERDALE
658 tristate "Support for the Timberdale FPGA"
659 select MFD_CORE
660 depends on PCI && GPIOLIB
661 ---help---
662 This is the core driver for the timberdale FPGA. This device is a
663 multifunction device which exposes numerous platform devices.
664
665 The timberdale FPGA can be found on the Intel Atom development board
666 for in-vehicle infontainment, called Russellville.
667
668config LPC_SCH
669 tristate "Intel SCH LPC"
670 depends on PCI
671 select MFD_CORE
672 help
673 LPC bridge function of the Intel SCH provides support for
674 System Management Bus and General Purpose I/O.
675
676config MFD_RDC321X
677 tristate "Support for RDC-R321x southbridge"
678 select MFD_CORE
679 depends on PCI
680 help
681 Say yes here if you want to have support for the RDC R-321x SoC
682 southbridge which provides access to GPIOs and Watchdog using the
683 southbridge PCI device configuration space.
684
685config MFD_JANZ_CMODIO
686 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
687 select MFD_CORE
688 depends on PCI
689 help
690 This is the core driver for the Janz CMOD-IO PCI MODULbus
691 carrier board. This device is a PCI to MODULbus bridge which may
692 host many different types of MODULbus daughterboards, including
693 CAN and GPIO controllers.
694
695config MFD_JZ4740_ADC
696 bool "Support for the JZ4740 SoC ADC core"
697 select MFD_CORE
698 select GENERIC_IRQ_CHIP
699 depends on MACH_JZ4740
700 help
701 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
702 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
703
704config MFD_VX855
705 tristate "Support for VIA VX855/VX875 integrated south bridge"
706 depends on PCI
707 select MFD_CORE
708 help
709 Say yes here to enable support for various functions of the
710 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
711 and/or vx855_gpio drivers for this to do anything useful.
712
713config MFD_WL1273_CORE
714 tristate "Support for TI WL1273 FM radio."
715 depends on I2C
716 select MFD_CORE
717 default n
718 help
719 This is the core driver for the TI WL1273 FM radio. This MFD
720 driver connects the radio-wl1273 V4L2 module and the wl1273
721 audio codec.
722
723config MFD_OMAP_USB_HOST
724 bool "Support OMAP USBHS core driver"
725 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
726 default y
727 help
728 This is the core driver for the OAMP EHCI and OHCI drivers.
729 This MFD driver does the required setup functionalities for
730 OMAP USB Host drivers.
731
732config MFD_PM8XXX
733 tristate
734
735config MFD_PM8921_CORE
736 tristate "Qualcomm PM8921 PMIC chip"
737 depends on MSM_SSBI
738 select MFD_CORE
739 select MFD_PM8XXX
740 help
741 If you say yes to this option, support will be included for the
742 built-in PM8921 PMIC chip.
743
744 This is required if your board has a PM8921 and uses its features,
745 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
746
747 Say M here if you want to include support for PM8921 chip as a module.
748 This will build a module called "pm8921-core".
749
750config MFD_PM8XXX_IRQ
751 bool "Support for Qualcomm PM8xxx IRQ features"
752 depends on MFD_PM8XXX
753 default y if MFD_PM8XXX
754 help
755 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
756
757 This is required to use certain other PM 8xxx features, such as GPIO
758 and MPP.
759
760config TPS65911_COMPARATOR
761 tristate
762
763config MFD_AAT2870_CORE
764 bool "Support for the AnalogicTech AAT2870"
765 select MFD_CORE
766 depends on I2C=y && GPIOLIB
767 help
768 If you say yes here you get support for the AAT2870.
769 This driver provides common support for accessing the device,
770 additional drivers must be enabled in order to use the
771 functionality of the device.
772
773endif # MFD_SUPPORT
774
775menu "Multimedia Capabilities Port drivers"
776 depends on ARCH_SA1100
777
778config MCP
779 tristate
780
781# Interface drivers
782config MCP_SA11X0
783 tristate "Support SA11x0 MCP interface"
784 depends on ARCH_SA1100
785 select MCP
786
787# Chip drivers
788config MCP_UCB1200
789 tristate "Support for UCB1200 / UCB1300"
790 depends on MCP
791
792config MCP_UCB1200_TS
793 tristate "Touchscreen interface support"
794 depends on MCP_UCB1200 && INPUT
795
796endmenu