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
5if HAS_IOMEM
6menu "Multifunction device drivers"
7
8config MFD_CORE
9 tristate
10 select IRQ_DOMAIN
11 default n
12
13config MFD_88PM860X
14 bool "Support Marvell 88PM8606/88PM8607"
15 depends on I2C=y && GENERIC_HARDIRQS
16 select REGMAP_I2C
17 select MFD_CORE
18 help
19 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
20 This includes the I2C driver and the core APIs _only_, you have to
21 select individual components like voltage regulators, RTC and
22 battery-charger under the corresponding menus.
23
24config MFD_88PM800
25 tristate "Support Marvell 88PM800"
26 depends on I2C=y && GENERIC_HARDIRQS
27 select REGMAP_I2C
28 select REGMAP_IRQ
29 select MFD_CORE
30 help
31 This supports for Marvell 88PM800 Power Management IC.
32 This includes the I2C driver and the core APIs _only_, you have to
33 select individual components like voltage regulators, RTC and
34 battery-charger under the corresponding menus.
35
36config MFD_88PM805
37 tristate "Support Marvell 88PM805"
38 depends on I2C=y && GENERIC_HARDIRQS
39 select REGMAP_I2C
40 select REGMAP_IRQ
41 select MFD_CORE
42 help
43 This supports for Marvell 88PM805 Power Management IC. This includes
44 the I2C driver and the core APIs _only_, you have to select individual
45 components like codec device, headset/Mic device under the
46 corresponding menus.
47
48config MFD_SM501
49 tristate "Support for Silicon Motion SM501"
50 ---help---
51 This is the core driver for the Silicon Motion SM501 multimedia
52 companion chip. This device is a multifunction device which may
53 provide numerous interfaces including USB host controller, USB gadget,
54 asynchronous serial ports, audio functions, and a dual display video
55 interface. The device may be connected by PCI or local bus with
56 varying functions enabled.
57
58config MFD_SM501_GPIO
59 bool "Export GPIO via GPIO layer"
60 depends on MFD_SM501 && GPIOLIB
61 ---help---
62 This option uses the gpio library layer to export the 64 GPIO
63 lines on the SM501. The platform data is used to supply the
64 base number for the first GPIO line to register.
65
66config MFD_ASIC3
67 bool "Support for Compaq ASIC3"
68 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
69 select MFD_CORE
70 ---help---
71 This driver supports the ASIC3 multifunction chip found on many
72 PDAs (mainly iPAQ and HTC based ones)
73
74config MFD_DAVINCI_VOICECODEC
75 tristate
76 select MFD_CORE
77
78config MFD_DM355EVM_MSP
79 bool "DaVinci DM355 EVM microcontroller"
80 depends on I2C=y && MACH_DAVINCI_DM355_EVM
81 help
82 This driver supports the MSP430 microcontroller used on these
83 boards. MSP430 firmware manages resets and power sequencing,
84 inputs from buttons and the IR remote, LEDs, an RTC, and more.
85
86config MFD_TI_SSP
87 tristate "TI Sequencer Serial Port support"
88 depends on ARCH_DAVINCI_TNETV107X
89 select MFD_CORE
90 ---help---
91 Say Y here if you want support for the Sequencer Serial Port
92 in a Texas Instruments TNETV107X SoC.
93
94 To compile this driver as a module, choose M here: the
95 module will be called ti-ssp.
96
97config HTC_EGPIO
98 bool "HTC EGPIO support"
99 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
100 help
101 This driver supports the CPLD egpio chip present on
102 several HTC phones. It provides basic support for input
103 pins, output pins, and irqs.
104
105config HTC_PASIC3
106 tristate "HTC PASIC3 LED/DS1WM chip support"
107 select MFD_CORE
108 help
109 This core driver provides register access for the LED/DS1WM
110 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
111 HTC Magician devices, respectively. Actual functionality is
112 handled by the leds-pasic3 and ds1wm drivers.
113
114config HTC_I2CPLD
115 bool "HTC I2C PLD chip support"
116 depends on I2C=y && GPIOLIB
117 help
118 If you say yes here you get support for the supposed CPLD
119 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
120 This device provides input and output GPIOs through an I2C
121 interface to one or more sub-chips.
122
123config UCB1400_CORE
124 tristate "Philips UCB1400 Core driver"
125 depends on AC97_BUS
126 depends on GPIOLIB
127 help
128 This enables support for the Philips UCB1400 core functions.
129 The UCB1400 is an AC97 audio codec.
130
131 To compile this driver as a module, choose M here: the
132 module will be called ucb1400_core.
133
134config MFD_LM3533
135 tristate "LM3533 Lighting Power chip"
136 depends on I2C
137 select MFD_CORE
138 select REGMAP_I2C
139 help
140 Say yes here to enable support for National Semiconductor / TI
141 LM3533 Lighting Power chips.
142
143 This driver provides common support for accessing the device;
144 additional drivers must be enabled in order to use the LED,
145 backlight or ambient-light-sensor functionality of the device.
146
147config TPS6105X
148 tristate "TPS61050/61052 Boost Converters"
149 depends on I2C
150 select REGULATOR
151 select MFD_CORE
152 select REGULATOR_FIXED_VOLTAGE
153 help
154 This option enables a driver for the TP61050/TPS61052
155 high-power "white LED driver". This boost converter is
156 sometimes used for other things than white LEDs, and
157 also contains a GPIO pin.
158
159config TPS65010
160 tristate "TPS6501x Power Management chips"
161 depends on I2C && GPIOLIB
162 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
163 help
164 If you say yes here you get support for the TPS6501x series of
165 Power Management chips. These include voltage regulators,
166 lithium ion/polymer battery charging, and other features that
167 are often used in portable devices like cell phones and cameras.
168
169 This driver can also be built as a module. If so, the module
170 will be called tps65010.
171
172config TPS6507X
173 tristate "TPS6507x Power Management / Touch Screen chips"
174 select MFD_CORE
175 depends on I2C
176 help
177 If you say yes here you get support for the TPS6507x series of
178 Power Management / Touch Screen chips. These include voltage
179 regulators, lithium ion/polymer battery charging, touch screen
180 and other features that are often used in portable devices.
181 This driver can also be built as a module. If so, the module
182 will be called tps6507x.
183
184config MFD_TPS65217
185 tristate "TPS65217 Power Management / White LED chips"
186 depends on I2C
187 select MFD_CORE
188 select REGMAP_I2C
189 help
190 If you say yes here you get support for the TPS65217 series of
191 Power Management / White LED chips.
192 These include voltage regulators, lithium ion/polymer battery
193 charger, wled and other features that are often used in portable
194 devices.
195
196 This driver can also be built as a module. If so, the module
197 will be called tps65217.
198
199config MFD_TPS6586X
200 bool "TPS6586x Power Management chips"
201 depends on I2C=y && GENERIC_HARDIRQS
202 select MFD_CORE
203 select REGMAP_I2C
204 depends on REGULATOR
205 help
206 If you say yes here you get support for the TPS6586X series of
207 Power Management chips.
208 This driver provides common support for accessing the device,
209 additional drivers must be enabled in order to use the
210 functionality of the device.
211
212 This driver can also be built as a module. If so, the module
213 will be called tps6586x.
214
215config MFD_TPS65910
216 bool "TPS65910 Power Management chip"
217 depends on I2C=y && GPIOLIB
218 select MFD_CORE
219 select REGMAP_I2C
220 select IRQ_DOMAIN
221 help
222 if you say yes here you get support for the TPS65910 series of
223 Power Management chips.
224
225config MFD_TPS65912
226 bool
227 depends on GPIOLIB
228
229config MFD_TPS65912_I2C
230 bool "TPS65912 Power Management chip with I2C"
231 select MFD_CORE
232 select MFD_TPS65912
233 depends on I2C=y && GPIOLIB
234 help
235 If you say yes here you get support for the TPS65912 series of
236 PM chips with I2C interface.
237
238config MFD_TPS65912_SPI
239 bool "TPS65912 Power Management chip with SPI"
240 select MFD_CORE
241 select MFD_TPS65912
242 depends on SPI_MASTER && GPIOLIB
243 help
244 If you say yes here you get support for the TPS65912 series of
245 PM chips with SPI interface.
246
247config MENELAUS
248 bool "Texas Instruments TWL92330/Menelaus PM chip"
249 depends on I2C=y && ARCH_OMAP2
250 help
251 If you say yes here you get support for the Texas Instruments
252 TWL92330/Menelaus Power Management chip. This include voltage
253 regulators, Dual slot memory card transceivers, real-time clock
254 and other features that are often used in portable devices like
255 cell phones and PDAs.
256
257config TWL4030_CORE
258 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
259 depends on I2C=y && GENERIC_HARDIRQS
260 select IRQ_DOMAIN
261 help
262 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
263 This core driver provides register access and IRQ handling
264 facilities, and registers devices for the various functions
265 so that function-specific drivers can bind to them.
266
267 These multi-function chips are found on many OMAP2 and OMAP3
268 boards, providing power management, RTC, GPIO, keypad, a
269 high speed USB OTG transceiver, an audio codec (on most
270 versions) and many other features.
271
272config TWL4030_MADC
273 tristate "Texas Instruments TWL4030 MADC"
274 depends on TWL4030_CORE
275 help
276 This driver provides support for triton TWL4030-MADC. The
277 driver supports both RT and SW conversion methods.
278
279 This driver can be built as a module. If so it will be
280 named twl4030-madc
281
282config TWL4030_POWER
283 bool "Support power resources on TWL4030 family chips"
284 depends on TWL4030_CORE && ARM
285 help
286 Say yes here if you want to use the power resources on the
287 TWL4030 family chips. Most of these resources are regulators,
288 which have a separate driver; some are control signals, such
289 as clock request handshaking.
290
291 This driver uses board-specific data to initialize the resources
292 and load scripts controlling which resources are switched off/on
293 or reset when a sleep, wakeup or warm reset event occurs.
294
295config MFD_TWL4030_AUDIO
296 bool
297 depends on TWL4030_CORE
298 select MFD_CORE
299 default n
300
301config TWL6030_PWM
302 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
303 depends on TWL4030_CORE
304 select HAVE_PWM
305 depends on !PWM
306 default n
307 help
308 Say yes here if you want support for TWL6030 PWM.
309 This is used to control charging LED brightness.
310
311config TWL6040_CORE
312 bool "Support for TWL6040 audio codec"
313 depends on I2C=y && GENERIC_HARDIRQS
314 select MFD_CORE
315 select REGMAP_I2C
316 select IRQ_DOMAIN
317 default n
318 help
319 Say yes here if you want support for Texas Instruments TWL6040 audio
320 codec.
321 This driver provides common support for accessing the device,
322 additional drivers must be enabled in order to use the
323 functionality of the device (audio, vibra).
324
325config MFD_STMPE
326 bool "Support STMicroelectronics STMPE"
327 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
328 select MFD_CORE
329 help
330 Support for the STMPE family of I/O Expanders from
331 STMicroelectronics.
332
333 Currently supported devices are:
334
335 STMPE811: GPIO, Touchscreen
336 STMPE1601: GPIO, Keypad
337 STMPE2401: GPIO, Keypad
338 STMPE2403: GPIO, Keypad
339
340 This driver provides common support for accessing the device,
341 additional drivers must be enabled in order to use the functionality
342 of the device. Currently available sub drivers are:
343
344 GPIO: stmpe-gpio
345 Keypad: stmpe-keypad
346 Touchscreen: stmpe-ts
347
348menu "STMPE Interface Drivers"
349depends on MFD_STMPE
350
351config STMPE_I2C
352 bool "STMPE I2C Inteface"
353 depends on I2C=y
354 default y
355 help
356 This is used to enable I2C interface of STMPE
357
358config STMPE_SPI
359 bool "STMPE SPI Inteface"
360 depends on SPI_MASTER
361 help
362 This is used to enable SPI interface of STMPE
363endmenu
364
365config MFD_TC3589X
366 bool "Support Toshiba TC35892 and variants"
367 depends on I2C=y && GENERIC_HARDIRQS
368 select MFD_CORE
369 help
370 Support for the Toshiba TC35892 and variants I/O Expander.
371
372 This driver provides common support for accessing the device,
373 additional drivers must be enabled in order to use the
374 functionality of the device.
375
376config MFD_TMIO
377 bool
378 default n
379
380config MFD_T7L66XB
381 bool "Support Toshiba T7L66XB"
382 depends on ARM && HAVE_CLK
383 select MFD_CORE
384 select MFD_TMIO
385 help
386 Support for Toshiba Mobile IO Controller T7L66XB
387
388config MFD_TC6387XB
389 bool "Support Toshiba TC6387XB"
390 depends on ARM && HAVE_CLK
391 select MFD_CORE
392 select MFD_TMIO
393 help
394 Support for Toshiba Mobile IO Controller TC6387XB
395
396config MFD_TC6393XB
397 bool "Support Toshiba TC6393XB"
398 depends on ARM && HAVE_CLK
399 select GPIOLIB
400 select MFD_CORE
401 select MFD_TMIO
402 help
403 Support for Toshiba Mobile IO Controller TC6393XB
404
405config PMIC_DA903X
406 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
407 depends on I2C=y
408 help
409 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
410 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
411 usually found on PXA processors-based platforms. This includes
412 the I2C driver and the core APIs _only_, you have to select
413 individual components like LCD backlight, voltage regulators,
414 LEDs and battery-charger under the corresponding menus.
415
416config PMIC_DA9052
417 bool
418 select MFD_CORE
419
420config MFD_DA9052_SPI
421 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
422 select REGMAP_SPI
423 select REGMAP_IRQ
424 select PMIC_DA9052
425 depends on SPI_MASTER=y
426 help
427 Support for the Dialog Semiconductor DA9052 PMIC
428 when controlled using SPI. This driver provides common support
429 for accessing the device, additional drivers must be enabled in
430 order to use the functionality of the device.
431
432config MFD_DA9052_I2C
433 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
434 select REGMAP_I2C
435 select REGMAP_IRQ
436 select PMIC_DA9052
437 depends on I2C=y
438 help
439 Support for the Dialog Semiconductor DA9052 PMIC
440 when controlled using I2C. This driver provides common support
441 for accessing the device, additional drivers must be enabled in
442 order to use the functionality of the device.
443
444config PMIC_ADP5520
445 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
446 depends on I2C=y
447 help
448 Say yes here to add support for Analog Devices AD5520 and ADP5501,
449 Multifunction Power Management IC. This includes
450 the I2C driver and the core APIs _only_, you have to select
451 individual components like LCD backlight, LEDs, GPIOs and Kepad
452 under the corresponding menus.
453
454config MFD_MAX77686
455 bool "Maxim Semiconductor MAX77686 PMIC Support"
456 depends on I2C=y && GENERIC_HARDIRQS
457 select MFD_CORE
458 select REGMAP_I2C
459 select IRQ_DOMAIN
460 help
461 Say yes here to support for Maxim Semiconductor MAX77686.
462 This is a Power Management IC with RTC on chip.
463 This driver provides common support for accessing the device;
464 additional drivers must be enabled in order to use the functionality
465 of the device.
466
467config MFD_MAX77693
468 bool "Maxim Semiconductor MAX77693 PMIC Support"
469 depends on I2C=y && GENERIC_HARDIRQS
470 select MFD_CORE
471 select REGMAP_I2C
472 help
473 Say yes here to support for Maxim Semiconductor MAX77693.
474 This is a companion Power Management IC with Flash, Haptic, Charger,
475 and MUIC(Micro USB Interface Controller) controls on chip.
476 This driver provides common support for accessing the device;
477 additional drivers must be enabled in order to use the functionality
478 of the device.
479
480config MFD_MAX8925
481 bool "Maxim Semiconductor MAX8925 PMIC Support"
482 depends on I2C=y && GENERIC_HARDIRQS
483 select MFD_CORE
484 help
485 Say yes here to support for Maxim Semiconductor MAX8925. This is
486 a Power Management IC. This driver provides common support for
487 accessing the device, additional drivers must be enabled in order
488 to use the functionality of the device.
489
490config MFD_MAX8997
491 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
492 depends on I2C=y && GENERIC_HARDIRQS
493 select MFD_CORE
494 select IRQ_DOMAIN
495 help
496 Say yes here to support for Maxim Semiconductor MAX8997/8966.
497 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
498 MUIC controls on chip.
499 This driver provides common support for accessing the device;
500 additional drivers must be enabled in order to use the functionality
501 of the device.
502
503config MFD_MAX8998
504 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
505 depends on I2C=y && GENERIC_HARDIRQS
506 select MFD_CORE
507 help
508 Say yes here to support for Maxim Semiconductor MAX8998 and
509 National Semiconductor LP3974. This is a Power Management IC.
510 This driver provides common support for accessing the device,
511 additional drivers must be enabled in order to use the functionality
512 of the device.
513
514config MFD_SEC_CORE
515 bool "SAMSUNG Electronics PMIC Series Support"
516 depends on I2C=y && GENERIC_HARDIRQS
517 select MFD_CORE
518 select REGMAP_I2C
519 select REGMAP_IRQ
520 help
521 Support for the Samsung Electronics MFD series.
522 This driver provides common support for accessing the device,
523 additional drivers must be enabled in order to use the functionality
524 of the device
525
526config MFD_ARIZONA
527 select REGMAP
528 select REGMAP_IRQ
529 select MFD_CORE
530 bool
531
532config MFD_ARIZONA_I2C
533 tristate "Support Wolfson Microelectronics Arizona platform with I2C"
534 select MFD_ARIZONA
535 select MFD_CORE
536 select REGMAP_I2C
537 depends on I2C
538 help
539 Support for the Wolfson Microelectronics Arizona platform audio SoC
540 core functionality controlled via I2C.
541
542config MFD_ARIZONA_SPI
543 tristate "Support Wolfson Microelectronics Arizona platform with SPI"
544 select MFD_ARIZONA
545 select MFD_CORE
546 select REGMAP_SPI
547 depends on SPI_MASTER
548 help
549 Support for the Wolfson Microelectronics Arizona platform audio SoC
550 core functionality controlled via I2C.
551
552config MFD_WM5102
553 bool "Support Wolfson Microelectronics WM5102"
554 depends on MFD_ARIZONA
555 help
556 Support for Wolfson Microelectronics WM5102 low power audio SoC
557
558config MFD_WM5110
559 bool "Support Wolfson Microelectronics WM5110"
560 depends on MFD_ARIZONA
561 help
562 Support for Wolfson Microelectronics WM5110 low power audio SoC
563
564config MFD_WM8400
565 bool "Support Wolfson Microelectronics WM8400"
566 select MFD_CORE
567 depends on I2C=y
568 select REGMAP_I2C
569 help
570 Support for the Wolfson Microelecronics WM8400 PMIC and audio
571 CODEC. This driver provides common support for accessing
572 the device, additional drivers must be enabled in order to use
573 the functionality of the device.
574
575config MFD_WM831X
576 bool
577 depends on GENERIC_HARDIRQS
578
579config MFD_WM831X_I2C
580 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
581 select MFD_CORE
582 select MFD_WM831X
583 select REGMAP_I2C
584 select IRQ_DOMAIN
585 depends on I2C=y && GENERIC_HARDIRQS
586 help
587 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
588 when controlled using I2C. This driver provides common support
589 for accessing the device, additional drivers must be enabled in
590 order to use the functionality of the device.
591
592config MFD_WM831X_SPI
593 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
594 select MFD_CORE
595 select MFD_WM831X
596 select REGMAP_SPI
597 select IRQ_DOMAIN
598 depends on SPI_MASTER && GENERIC_HARDIRQS
599 help
600 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
601 when controlled using SPI. This driver provides common support
602 for accessing the device, additional drivers must be enabled in
603 order to use the functionality of the device.
604
605config MFD_WM8350
606 bool
607 depends on GENERIC_HARDIRQS
608
609config MFD_WM8350_CONFIG_MODE_0
610 bool
611 depends on MFD_WM8350
612
613config MFD_WM8350_CONFIG_MODE_1
614 bool
615 depends on MFD_WM8350
616
617config MFD_WM8350_CONFIG_MODE_2
618 bool
619 depends on MFD_WM8350
620
621config MFD_WM8350_CONFIG_MODE_3
622 bool
623 depends on MFD_WM8350
624
625config MFD_WM8351_CONFIG_MODE_0
626 bool
627 depends on MFD_WM8350
628
629config MFD_WM8351_CONFIG_MODE_1
630 bool
631 depends on MFD_WM8350
632
633config MFD_WM8351_CONFIG_MODE_2
634 bool
635 depends on MFD_WM8350
636
637config MFD_WM8351_CONFIG_MODE_3
638 bool
639 depends on MFD_WM8350
640
641config MFD_WM8352_CONFIG_MODE_0
642 bool
643 depends on MFD_WM8350
644
645config MFD_WM8352_CONFIG_MODE_1
646 bool
647 depends on MFD_WM8350
648
649config MFD_WM8352_CONFIG_MODE_2
650 bool
651 depends on MFD_WM8350
652
653config MFD_WM8352_CONFIG_MODE_3
654 bool
655 depends on MFD_WM8350
656
657config MFD_WM8350_I2C
658 bool "Support Wolfson Microelectronics WM8350 with I2C"
659 select MFD_WM8350
660 depends on I2C=y && GENERIC_HARDIRQS
661 help
662 The WM8350 is an integrated audio and power management
663 subsystem with watchdog and RTC functionality for embedded
664 systems. This option enables core support for the WM8350 with
665 I2C as the control interface. Additional options must be
666 selected to enable support for the functionality of the chip.
667
668config MFD_WM8994
669 bool "Support Wolfson Microelectronics WM8994"
670 select MFD_CORE
671 select REGMAP_I2C
672 select REGMAP_IRQ
673 depends on I2C=y && GENERIC_HARDIRQS
674 help
675 The WM8994 is a highly integrated hi-fi CODEC designed for
676 smartphone applicatiosn. As well as audio functionality it
677 has on board GPIO and regulator functionality which is
678 supported via the relevant subsystems. This driver provides
679 core support for the WM8994, in order to use the actual
680 functionaltiy of the device other drivers must be enabled.
681
682config MFD_PCF50633
683 tristate "Support for NXP PCF50633"
684 depends on I2C
685 select REGMAP_I2C
686 help
687 Say yes here if you have NXP PCF50633 chip on your board.
688 This core driver provides register access and IRQ handling
689 facilities, and registers devices for the various functions
690 so that function-specific drivers can bind to them.
691
692config PCF50633_ADC
693 tristate "Support for NXP PCF50633 ADC"
694 depends on MFD_PCF50633
695 help
696 Say yes here if you want to include support for ADC in the
697 NXP PCF50633 chip.
698
699config PCF50633_GPIO
700 tristate "Support for NXP PCF50633 GPIO"
701 depends on MFD_PCF50633
702 help
703 Say yes here if you want to include support GPIO for pins on
704 the PCF50633 chip.
705
706config MFD_MC13783
707 tristate
708
709config MFD_MC13XXX
710 tristate
711 depends on SPI_MASTER || I2C
712 select MFD_CORE
713 select MFD_MC13783
714 help
715 Enable support for the Freescale MC13783 and MC13892 PMICs.
716 This driver provides common support for accessing the device,
717 additional drivers must be enabled in order to use the
718 functionality of the device.
719
720config MFD_MC13XXX_SPI
721 tristate "Freescale MC13783 and MC13892 SPI interface"
722 depends on SPI_MASTER
723 select REGMAP_SPI
724 select MFD_MC13XXX
725 help
726 Select this if your MC13xxx is connected via an SPI bus.
727
728config MFD_MC13XXX_I2C
729 tristate "Freescale MC13892 I2C interface"
730 depends on I2C
731 select REGMAP_I2C
732 select MFD_MC13XXX
733 help
734 Select this if your MC13xxx is connected via an I2C bus.
735
736config ABX500_CORE
737 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
738 default y if ARCH_U300 || ARCH_U8500
739 help
740 Say yes here if you have the ABX500 Mixed Signal IC family
741 chips. This core driver expose register access functions.
742 Functionality specific drivers using these functions can
743 remain unchanged when IC changes. Binding of the functions to
744 actual register access is done by the IC core driver.
745
746config AB3100_CORE
747 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
748 depends on I2C=y && ABX500_CORE
749 select MFD_CORE
750 default y if ARCH_U300
751 help
752 Select this to enable the AB3100 Mixed Signal IC core
753 functionality. This connects to a AB3100 on the I2C bus
754 and expose a number of symbols needed for dependent devices
755 to read and write registers and subscribe to events from
756 this multi-functional IC. This is needed to use other features
757 of the AB3100 such as battery-backed RTC, charging control,
758 LEDs, vibrator, system power and temperature, power management
759 and ALSA sound.
760
761config AB3100_OTP
762 tristate "ST-Ericsson AB3100 OTP functions"
763 depends on AB3100_CORE
764 default y if AB3100_CORE
765 help
766 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
767 programmable memory) support. This exposes a sysfs file to read
768 out OTP values.
769
770config EZX_PCAP
771 bool "PCAP Support"
772 depends on GENERIC_HARDIRQS && SPI_MASTER
773 help
774 This enables the PCAP ASIC present on EZX Phones. This is
775 needed for MMC, TouchScreen, Sound, USB, etc..
776
777config AB8500_CORE
778 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
779 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
780 select MFD_CORE
781 select IRQ_DOMAIN
782 help
783 Select this option to enable access to AB8500 power management
784 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
785 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
786 the irq_chip parts for handling the Mixed Signal chip events.
787 This chip embeds various other multimedia funtionalities as well.
788
789config AB8500_DEBUG
790 bool "Enable debug info via debugfs"
791 depends on AB8500_CORE && DEBUG_FS
792 default y if DEBUG_FS
793 help
794 Select this option if you want debug information using the debug
795 filesystem, debugfs.
796
797config AB8500_GPADC
798 bool "AB8500 GPADC driver"
799 depends on AB8500_CORE && REGULATOR_AB8500
800 default y
801 help
802 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
803
804config MFD_DB8500_PRCMU
805 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
806 depends on UX500_SOC_DB8500
807 select MFD_CORE
808 help
809 Select this option to enable support for the DB8500 Power Reset
810 and Control Management Unit. This is basically an autonomous
811 system controller running an XP70 microprocessor, which is accessed
812 through a register map.
813
814config MFD_CS5535
815 tristate "Support for CS5535 and CS5536 southbridge core functions"
816 select MFD_CORE
817 depends on PCI && X86
818 ---help---
819 This is the core driver for CS5535/CS5536 MFD functions. This is
820 necessary for using the board's GPIO and MFGPT functionality.
821
822config MFD_TIMBERDALE
823 tristate "Support for the Timberdale FPGA"
824 select MFD_CORE
825 depends on PCI && GPIOLIB
826 ---help---
827 This is the core driver for the timberdale FPGA. This device is a
828 multifunction device which exposes numerous platform devices.
829
830 The timberdale FPGA can be found on the Intel Atom development board
831 for in-vehicle infontainment, called Russellville.
832
833config LPC_SCH
834 tristate "Intel SCH LPC"
835 depends on PCI
836 select MFD_CORE
837 help
838 LPC bridge function of the Intel SCH provides support for
839 System Management Bus and General Purpose I/O.
840
841config LPC_ICH
842 tristate "Intel ICH LPC"
843 depends on PCI
844 select MFD_CORE
845 help
846 The LPC bridge function of the Intel ICH provides support for
847 many functional units. This driver provides needed support for
848 other drivers to control these functions, currently GPIO and
849 watchdog.
850
851config MFD_RDC321X
852 tristate "Support for RDC-R321x southbridge"
853 select MFD_CORE
854 depends on PCI
855 help
856 Say yes here if you want to have support for the RDC R-321x SoC
857 southbridge which provides access to GPIOs and Watchdog using the
858 southbridge PCI device configuration space.
859
860config MFD_JANZ_CMODIO
861 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
862 select MFD_CORE
863 depends on PCI
864 help
865 This is the core driver for the Janz CMOD-IO PCI MODULbus
866 carrier board. This device is a PCI to MODULbus bridge which may
867 host many different types of MODULbus daughterboards, including
868 CAN and GPIO controllers.
869
870config MFD_JZ4740_ADC
871 bool "Support for the JZ4740 SoC ADC core"
872 select MFD_CORE
873 select GENERIC_IRQ_CHIP
874 depends on MACH_JZ4740
875 help
876 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
877 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
878
879config MFD_VX855
880 tristate "Support for VIA VX855/VX875 integrated south bridge"
881 depends on PCI
882 select MFD_CORE
883 help
884 Say yes here to enable support for various functions of the
885 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
886 and/or vx855_gpio drivers for this to do anything useful.
887
888config MFD_WL1273_CORE
889 tristate "Support for TI WL1273 FM radio."
890 depends on I2C
891 select MFD_CORE
892 default n
893 help
894 This is the core driver for the TI WL1273 FM radio. This MFD
895 driver connects the radio-wl1273 V4L2 module and the wl1273
896 audio codec.
897
898config MFD_OMAP_USB_HOST
899 bool "Support OMAP USBHS core driver"
900 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
901 default y
902 help
903 This is the core driver for the OAMP EHCI and OHCI drivers.
904 This MFD driver does the required setup functionalities for
905 OMAP USB Host drivers.
906
907config MFD_PM8XXX
908 tristate
909
910config MFD_PM8921_CORE
911 tristate "Qualcomm PM8921 PMIC chip"
912 depends on MSM_SSBI
913 select MFD_CORE
914 select MFD_PM8XXX
915 help
916 If you say yes to this option, support will be included for the
917 built-in PM8921 PMIC chip.
918
919 This is required if your board has a PM8921 and uses its features,
920 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
921
922 Say M here if you want to include support for PM8921 chip as a module.
923 This will build a module called "pm8921-core".
924
925config MFD_PM8XXX_IRQ
926 bool "Support for Qualcomm PM8xxx IRQ features"
927 depends on MFD_PM8XXX
928 default y if MFD_PM8XXX
929 help
930 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
931
932 This is required to use certain other PM 8xxx features, such as GPIO
933 and MPP.
934
935config TPS65911_COMPARATOR
936 tristate
937
938config MFD_TPS65090
939 bool "TPS65090 Power Management chips"
940 depends on I2C=y && GENERIC_HARDIRQS
941 select MFD_CORE
942 select REGMAP_I2C
943 help
944 If you say yes here you get support for the TPS65090 series of
945 Power Management chips.
946 This driver provides common support for accessing the device,
947 additional drivers must be enabled in order to use the
948 functionality of the device.
949
950config MFD_AAT2870_CORE
951 bool "Support for the AnalogicTech AAT2870"
952 select MFD_CORE
953 depends on I2C=y && GPIOLIB
954 help
955 If you say yes here you get support for the AAT2870.
956 This driver provides common support for accessing the device,
957 additional drivers must be enabled in order to use the
958 functionality of the device.
959
960config MFD_INTEL_MSIC
961 bool "Support for Intel MSIC"
962 depends on INTEL_SCU_IPC
963 select MFD_CORE
964 help
965 Select this option to enable access to Intel MSIC (Avatele
966 Passage) chip. This chip embeds audio, battery, GPIO, etc.
967 devices used in Intel Medfield platforms.
968
969config MFD_RC5T583
970 bool "Ricoh RC5T583 Power Management system device"
971 depends on I2C=y && GENERIC_HARDIRQS
972 select MFD_CORE
973 select REGMAP_I2C
974 help
975 Select this option to get support for the RICOH583 Power
976 Management system device.
977 This driver provides common support for accessing the device
978 through i2c interface. The device supports multiple sub-devices
979 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
980 Additional drivers must be enabled in order to use the
981 different functionality of the device.
982
983config MFD_STA2X11
984 bool "STA2X11 multi function device support"
985 depends on STA2X11
986 select MFD_CORE
987
988config MFD_ANATOP
989 bool "Support for Freescale i.MX on-chip ANATOP controller"
990 depends on SOC_IMX6Q
991 help
992 Select this option to enable Freescale i.MX on-chip ANATOP
993 MFD controller. This controller embeds regulator and
994 thermal devices for Freescale i.MX platforms.
995
996config MFD_PALMAS
997 bool "Support for the TI Palmas series chips"
998 select MFD_CORE
999 select REGMAP_I2C
1000 select REGMAP_IRQ
1001 depends on I2C=y
1002 help
1003 If you say yes here you get support for the Palmas
1004 series of PMIC chips from Texas Instruments.
1005
1006endmenu
1007endif
1008
1009menu "Multimedia Capabilities Port drivers"
1010 depends on ARCH_SA1100
1011
1012config MCP
1013 tristate
1014
1015# Interface drivers
1016config MCP_SA11X0
1017 tristate "Support SA11x0 MCP interface"
1018 depends on ARCH_SA1100
1019 select MCP
1020
1021# Chip drivers
1022config MCP_UCB1200
1023 bool "Support for UCB1200 / UCB1300"
1024 depends on MCP_SA11X0
1025 select MCP
1026
1027config MCP_UCB1200_TS
1028 tristate "Touchscreen interface support"
1029 depends on MCP_UCB1200 && INPUT
1030
1031endmenu