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