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