Merge tag 'drm-vc4-fixes-2015-01-19' of http://github.com/anholt/linux into drm-fixes
[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 select IRQ_DOMAIN
11 default n
12
13 config MFD_CS5535
14 tristate "AMD CS5535 and CS5536 southbridge core functions"
15 select MFD_CORE
16 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
17 ---help---
18 This is the core driver for CS5535/CS5536 MFD functions. This is
19 necessary for using the board's GPIO and MFGPT functionality.
20
21 config MFD_AS3711
22 bool "AMS AS3711"
23 select MFD_CORE
24 select REGMAP_I2C
25 select REGMAP_IRQ
26 depends on I2C=y
27 help
28 Support for the AS3711 PMIC from AMS
29
30 config MFD_AS3722
31 bool "ams AS3722 Power Management IC"
32 select MFD_CORE
33 select REGMAP_I2C
34 select REGMAP_IRQ
35 depends on I2C=y && OF
36 help
37 The ams AS3722 is a compact system PMU suitable for mobile phones,
38 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
39 controllers, 11 LDOs, RTC, automatic battery, temperature and
40 over current monitoring, GPIOs, ADC and a watchdog.
41
42 config PMIC_ADP5520
43 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
44 depends on I2C=y
45 help
46 Say yes here to add support for Analog Devices AD5520 and ADP5501,
47 Multifunction Power Management IC. This includes
48 the I2C driver and the core APIs _only_, you have to select
49 individual components like LCD backlight, LEDs, GPIOs and Kepad
50 under the corresponding menus.
51
52 config MFD_AAT2870_CORE
53 bool "AnalogicTech AAT2870"
54 select MFD_CORE
55 depends on I2C=y
56 depends on GPIOLIB || COMPILE_TEST
57 help
58 If you say yes here you get support for the AAT2870.
59 This driver provides common support for accessing the device,
60 additional drivers must be enabled in order to use the
61 functionality of the device.
62
63 config MFD_ATMEL_FLEXCOM
64 tristate "Atmel Flexcom (Flexible Serial Communication Unit)"
65 select MFD_CORE
66 depends on OF
67 help
68 Select this to get support for Atmel Flexcom. This is a wrapper
69 which embeds a SPI controller, a I2C controller and a USART. Only
70 one function can be used at a time. The choice is done at boot time
71 by the probe function of this MFD driver according to a device tree
72 property.
73
74 config MFD_ATMEL_HLCDC
75 tristate "Atmel HLCDC (High-end LCD Controller)"
76 select MFD_CORE
77 select REGMAP_MMIO
78 depends on OF
79 help
80 If you say yes here you get support for the HLCDC block.
81 This driver provides common support for accessing the device,
82 additional drivers must be enabled in order to use the
83 functionality of the device.
84
85 config MFD_BCM590XX
86 tristate "Broadcom BCM590xx PMUs"
87 select MFD_CORE
88 select REGMAP_I2C
89 depends on I2C
90 help
91 Support for the BCM590xx PMUs from Broadcom
92
93 config MFD_AXP20X
94 bool "X-Powers AXP20X"
95 select MFD_CORE
96 select REGMAP_I2C
97 select REGMAP_IRQ
98 depends on I2C=y
99 help
100 If you say Y here you get support for the X-Powers AXP202, AXP209 and
101 AXP288 power management IC (PMIC).
102 This driver include only the core APIs. You have to select individual
103 components like regulators or the PEK (Power Enable Key) under the
104 corresponding menus.
105
106 config MFD_CROS_EC
107 tristate "ChromeOS Embedded Controller"
108 select MFD_CORE
109 select CHROME_PLATFORMS
110 select CROS_EC_PROTO
111 depends on X86 || ARM || COMPILE_TEST
112 help
113 If you say Y here you get support for the ChromeOS Embedded
114 Controller (EC) providing keyboard, battery and power services.
115 You also need to enable the driver for the bus you are using. The
116 protocol for talking to the EC is defined by the bus driver.
117
118 config MFD_CROS_EC_I2C
119 tristate "ChromeOS Embedded Controller (I2C)"
120 depends on MFD_CROS_EC && I2C
121
122 help
123 If you say Y here, you get support for talking to the ChromeOS
124 EC through an I2C bus. This uses a simple byte-level protocol with
125 a checksum. Failing accesses will be retried three times to
126 improve reliability.
127
128 config MFD_CROS_EC_SPI
129 tristate "ChromeOS Embedded Controller (SPI)"
130 depends on MFD_CROS_EC && SPI
131
132 ---help---
133 If you say Y here, you get support for talking to the ChromeOS EC
134 through a SPI bus, using a byte-level protocol. Since the EC's
135 response time cannot be guaranteed, we support ignoring
136 'pre-amble' bytes before the response actually starts.
137
138 config MFD_ASIC3
139 bool "Compaq ASIC3"
140 depends on GPIOLIB && ARM
141 select MFD_CORE
142 ---help---
143 This driver supports the ASIC3 multifunction chip found on many
144 PDAs (mainly iPAQ and HTC based ones)
145
146 config PMIC_DA903X
147 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
148 depends on I2C=y
149 help
150 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
151 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
152 usually found on PXA processors-based platforms. This includes
153 the I2C driver and the core APIs _only_, you have to select
154 individual components like LCD backlight, voltage regulators,
155 LEDs and battery-charger under the corresponding menus.
156
157 config PMIC_DA9052
158 bool
159 select MFD_CORE
160
161 config MFD_DA9052_SPI
162 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
163 select REGMAP_SPI
164 select REGMAP_IRQ
165 select PMIC_DA9052
166 depends on SPI_MASTER=y
167 help
168 Support for the Dialog Semiconductor DA9052 PMIC
169 when controlled using SPI. This driver provides common support
170 for accessing the device, additional drivers must be enabled in
171 order to use the functionality of the device.
172
173 config MFD_DA9052_I2C
174 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
175 select REGMAP_I2C
176 select REGMAP_IRQ
177 select PMIC_DA9052
178 depends on I2C=y
179 help
180 Support for the Dialog Semiconductor DA9052 PMIC
181 when controlled using I2C. This driver provides common support
182 for accessing the device, additional drivers must be enabled in
183 order to use the functionality of the device.
184
185 config MFD_DA9055
186 bool "Dialog Semiconductor DA9055 PMIC Support"
187 select REGMAP_I2C
188 select REGMAP_IRQ
189 select MFD_CORE
190 depends on I2C=y
191 help
192 Say yes here for support of Dialog Semiconductor DA9055. This is
193 a Power Management IC. This driver provides common support for
194 accessing the device as well as the I2C interface to the chip itself.
195 Additional drivers must be enabled in order to use the functionality
196 of the device.
197
198 This driver can be built as a module. If built as a module it will be
199 called "da9055"
200
201 config MFD_DA9062
202 tristate "Dialog Semiconductor DA9062 PMIC Support"
203 select MFD_CORE
204 select REGMAP_I2C
205 select REGMAP_IRQ
206 depends on I2C=y
207 help
208 Say yes here for support for the Dialog Semiconductor DA9062 PMIC.
209 This includes the I2C driver and core APIs.
210 Additional drivers must be enabled in order to use the functionality
211 of the device.
212
213 config MFD_DA9063
214 tristate "Dialog Semiconductor DA9063 PMIC Support"
215 select MFD_CORE
216 select REGMAP_I2C
217 select REGMAP_IRQ
218 depends on I2C=y
219 help
220 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
221 This includes the I2C driver and core APIs.
222 Additional drivers must be enabled in order to use the functionality
223 of the device.
224
225 config MFD_DA9150
226 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
227 depends on I2C=y
228 select MFD_CORE
229 select REGMAP_I2C
230 select REGMAP_IRQ
231 help
232 This adds support for the DA9150 integrated charger and fuel-gauge
233 chip. This driver provides common support for accessing the device.
234 Additional drivers must be enabled in order to use the specific
235 features of the device.
236
237 config MFD_DLN2
238 tristate "Diolan DLN2 support"
239 select MFD_CORE
240 depends on USB
241 help
242 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
243 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
244 etc. must be enabled in order to use the functionality of
245 the device.
246
247 config MFD_MC13XXX
248 tristate
249 depends on (SPI_MASTER || I2C)
250 select MFD_CORE
251 select REGMAP_IRQ
252 help
253 Enable support for the Freescale MC13783 and MC13892 PMICs.
254 This driver provides common support for accessing the device,
255 additional drivers must be enabled in order to use the
256 functionality of the device.
257
258 config MFD_MC13XXX_SPI
259 tristate "Freescale MC13783 and MC13892 SPI interface"
260 depends on SPI_MASTER
261 select REGMAP_SPI
262 select MFD_MC13XXX
263 help
264 Select this if your MC13xxx is connected via an SPI bus.
265
266 config MFD_MC13XXX_I2C
267 tristate "Freescale MC13892 I2C interface"
268 depends on I2C
269 select REGMAP_I2C
270 select MFD_MC13XXX
271 help
272 Select this if your MC13xxx is connected via an I2C bus.
273
274 config MFD_HI6421_PMIC
275 tristate "HiSilicon Hi6421 PMU/Codec IC"
276 depends on OF
277 select MFD_CORE
278 select REGMAP_MMIO
279 help
280 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
281 functions, such as regulators, RTC, codec, Coulomb counter, etc.
282 This driver includes core APIs _only_. You have to select
283 individul components like voltage regulators under corresponding
284 menus in order to enable them.
285 We communicate with the Hi6421 via memory-mapped I/O.
286
287 config HTC_EGPIO
288 bool "HTC EGPIO support"
289 depends on GPIOLIB && ARM
290 help
291 This driver supports the CPLD egpio chip present on
292 several HTC phones. It provides basic support for input
293 pins, output pins, and irqs.
294
295 config HTC_PASIC3
296 tristate "HTC PASIC3 LED/DS1WM chip support"
297 select MFD_CORE
298 help
299 This core driver provides register access for the LED/DS1WM
300 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
301 HTC Magician devices, respectively. Actual functionality is
302 handled by the leds-pasic3 and ds1wm drivers.
303
304 config HTC_I2CPLD
305 bool "HTC I2C PLD chip support"
306 depends on I2C=y && GPIOLIB
307 help
308 If you say yes here you get support for the supposed CPLD
309 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
310 This device provides input and output GPIOs through an I2C
311 interface to one or more sub-chips.
312
313 config MFD_INTEL_QUARK_I2C_GPIO
314 tristate "Intel Quark MFD I2C GPIO"
315 depends on PCI
316 depends on X86
317 depends on COMMON_CLK
318 select MFD_CORE
319 help
320 This MFD provides support for I2C and GPIO that exist only
321 in a single PCI device. It splits the 2 IO devices to
322 their respective IO driver.
323 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
324
325 config LPC_ICH
326 tristate "Intel ICH LPC"
327 depends on PCI
328 select MFD_CORE
329 help
330 The LPC bridge function of the Intel ICH provides support for
331 many functional units. This driver provides needed support for
332 other drivers to control these functions, currently GPIO and
333 watchdog.
334
335 config LPC_SCH
336 tristate "Intel SCH LPC"
337 depends on PCI
338 select MFD_CORE
339 help
340 LPC bridge function of the Intel SCH provides support for
341 System Management Bus and General Purpose I/O.
342
343 config INTEL_SOC_PMIC
344 bool "Support for Intel Atom SoC PMIC"
345 depends on GPIOLIB
346 depends on I2C=y
347 select MFD_CORE
348 select REGMAP_I2C
349 select REGMAP_IRQ
350 help
351 Select this option to enable support for the PMIC device
352 on some Intel SoC systems. The PMIC provides ADC, GPIO,
353 thermal, charger and related power management functions
354 on these systems.
355
356 config MFD_INTEL_LPSS
357 tristate
358 select COMMON_CLK
359 select MFD_CORE
360
361 config MFD_INTEL_LPSS_ACPI
362 tristate "Intel Low Power Subsystem support in ACPI mode"
363 select MFD_INTEL_LPSS
364 depends on X86 && ACPI
365 help
366 This driver supports Intel Low Power Subsystem (LPSS) devices such as
367 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
368 PCH) in ACPI mode.
369
370 config MFD_INTEL_LPSS_PCI
371 tristate "Intel Low Power Subsystem support in PCI mode"
372 select MFD_INTEL_LPSS
373 depends on X86 && PCI
374 help
375 This driver supports Intel Low Power Subsystem (LPSS) devices such as
376 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
377 PCH) in PCI mode.
378
379 config MFD_INTEL_MSIC
380 bool "Intel MSIC"
381 depends on INTEL_SCU_IPC
382 select MFD_CORE
383 help
384 Select this option to enable access to Intel MSIC (Avatele
385 Passage) chip. This chip embeds audio, battery, GPIO, etc.
386 devices used in Intel Medfield platforms.
387
388 config MFD_IPAQ_MICRO
389 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
390 depends on SA1100_H3100 || SA1100_H3600
391 select MFD_CORE
392 help
393 Select this to get support for the Microcontroller found in
394 the Compaq iPAQ handheld computers. This is an Atmel
395 AT90LS8535 microcontroller flashed with a special iPAQ
396 firmware using the custom protocol implemented in this driver.
397
398 config MFD_JANZ_CMODIO
399 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
400 select MFD_CORE
401 depends on PCI
402 help
403 This is the core driver for the Janz CMOD-IO PCI MODULbus
404 carrier board. This device is a PCI to MODULbus bridge which may
405 host many different types of MODULbus daughterboards, including
406 CAN and GPIO controllers.
407
408 config MFD_JZ4740_ADC
409 bool "Janz JZ4740 ADC core"
410 select MFD_CORE
411 select GENERIC_IRQ_CHIP
412 depends on MACH_JZ4740
413 help
414 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
415 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
416
417 config MFD_KEMPLD
418 tristate "Kontron module PLD device"
419 select MFD_CORE
420 help
421 This is the core driver for the PLD (Programmable Logic Device) found
422 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
423 device may provide functions like watchdog, GPIO, UART and I2C bus.
424
425 The following modules are supported:
426 * COMe-bBL6
427 * COMe-bHL6
428 * COMe-bIP#
429 * COMe-bPC2 (ETXexpress-PC)
430 * COMe-bSC# (ETXexpress-SC T#)
431 * COMe-cBL6
432 * COMe-cBT6
433 * COMe-cBW6
434 * COMe-cCT6
435 * COMe-cDC2 (microETXexpress-DC)
436 * COMe-cHL6
437 * COMe-cPC2 (microETXexpress-PC)
438 * COMe-mBT10
439 * COMe-mCT10
440 * COMe-mTT10 (nanoETXexpress-TT)
441 * ETX-OH
442
443 This driver can also be built as a module. If so, the module
444 will be called kempld-core.
445
446 config MFD_88PM800
447 tristate "Marvell 88PM800"
448 depends on I2C=y
449 select REGMAP_I2C
450 select REGMAP_IRQ
451 select MFD_CORE
452 help
453 This supports for Marvell 88PM800 Power Management IC.
454 This includes the I2C driver and the core APIs _only_, you have to
455 select individual components like voltage regulators, RTC and
456 battery-charger under the corresponding menus.
457
458 config MFD_88PM805
459 tristate "Marvell 88PM805"
460 depends on I2C=y
461 select REGMAP_I2C
462 select REGMAP_IRQ
463 select MFD_CORE
464 help
465 This supports for Marvell 88PM805 Power Management IC. This includes
466 the I2C driver and the core APIs _only_, you have to select individual
467 components like codec device, headset/Mic device under the
468 corresponding menus.
469
470 config MFD_88PM860X
471 bool "Marvell 88PM8606/88PM8607"
472 depends on I2C=y
473 select REGMAP_I2C
474 select MFD_CORE
475 help
476 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
477 This includes the I2C driver and the core APIs _only_, you have to
478 select individual components like voltage regulators, RTC and
479 battery-charger under the corresponding menus.
480
481 config MFD_MAX14577
482 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
483 depends on I2C=y
484 select MFD_CORE
485 select REGMAP_I2C
486 select REGMAP_IRQ
487 select IRQ_DOMAIN
488 help
489 Say yes here to add support for Maxim Semiconductor MAX14577 and
490 MAX77836 Micro-USB ICs with battery charger.
491 This driver provides common support for accessing the device;
492 additional drivers must be enabled in order to use the functionality
493 of the device.
494
495 config MFD_MAX77686
496 bool "Maxim Semiconductor MAX77686/802 PMIC Support"
497 depends on I2C=y
498 depends on OF
499 select MFD_CORE
500 select REGMAP_I2C
501 select REGMAP_IRQ
502 select IRQ_DOMAIN
503 help
504 Say yes here to add support for Maxim Semiconductor MAX77686 and
505 MAX77802 which are Power Management IC with an RTC on chip.
506 This driver provides common support for accessing the device;
507 additional drivers must be enabled in order to use the functionality
508 of the device.
509
510 config MFD_MAX77693
511 bool "Maxim Semiconductor MAX77693 PMIC Support"
512 depends on I2C=y
513 select MFD_CORE
514 select REGMAP_I2C
515 select REGMAP_IRQ
516 help
517 Say yes here to add support for Maxim Semiconductor MAX77693.
518 This is a companion Power Management IC with Flash, Haptic, Charger,
519 and MUIC(Micro USB Interface Controller) controls on chip.
520 This driver provides common support for accessing the device;
521 additional drivers must be enabled in order to use the functionality
522 of the device.
523
524 config MFD_MAX77843
525 bool "Maxim Semiconductor MAX77843 PMIC Support"
526 depends on I2C=y
527 select MFD_CORE
528 select REGMAP_I2C
529 select REGMAP_IRQ
530 help
531 Say yes here to add support for Maxim Semiconductor MAX77843.
532 This is companion Power Management IC with LEDs, Haptic, Charger,
533 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
534 This driver provides common support for accessing the device;
535 additional drivers must be enabled in order to use the functionality
536 of the device.
537
538 config MFD_MAX8907
539 tristate "Maxim Semiconductor MAX8907 PMIC Support"
540 select MFD_CORE
541 depends on I2C=y
542 select REGMAP_I2C
543 select REGMAP_IRQ
544 help
545 Say yes here to add support for Maxim Semiconductor MAX8907. This is
546 a Power Management IC. This driver provides common support for
547 accessing the device; additional drivers must be enabled in order
548 to use the functionality of the device.
549
550 config MFD_MAX8925
551 bool "Maxim Semiconductor MAX8925 PMIC Support"
552 depends on I2C=y
553 select MFD_CORE
554 help
555 Say yes here to add support for Maxim Semiconductor MAX8925. This is
556 a Power Management IC. This driver provides common support for
557 accessing the device, additional drivers must be enabled in order
558 to use the functionality of the device.
559
560 config MFD_MAX8997
561 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
562 depends on I2C=y
563 select MFD_CORE
564 select IRQ_DOMAIN
565 help
566 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
567 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
568 MUIC controls on chip.
569 This driver provides common support for accessing the device;
570 additional drivers must be enabled in order to use the functionality
571 of the device.
572
573 config MFD_MAX8998
574 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
575 depends on I2C=y
576 select MFD_CORE
577 select IRQ_DOMAIN
578 help
579 Say yes here to add support for Maxim Semiconductor MAX8998 and
580 National Semiconductor LP3974. This is a Power Management IC.
581 This driver provides common support for accessing the device,
582 additional drivers must be enabled in order to use the functionality
583 of the device.
584
585 config MFD_MT6397
586 tristate "MediaTek MT6397 PMIC Support"
587 select MFD_CORE
588 select IRQ_DOMAIN
589 help
590 Say yes here to add support for MediaTek MT6397 PMIC. This is
591 a Power Management IC. This driver provides common support for
592 accessing the device; additional drivers must be enabled in order
593 to use the functionality of the device.
594
595 config MFD_MENF21BMC
596 tristate "MEN 14F021P00 Board Management Controller Support"
597 depends on I2C
598 select MFD_CORE
599 help
600 Say yes here to add support for the MEN 14F021P00 BMC
601 which is a Board Management Controller connected to the I2C bus.
602 The device supports multiple sub-devices like LED, HWMON and WDT.
603 This driver provides common support for accessing the devices;
604 additional drivers must be enabled in order to use the
605 functionality of the BMC device.
606
607 This driver can also be built as a module. If so the module
608 will be called menf21bmc.
609
610 config EZX_PCAP
611 bool "Motorola EZXPCAP Support"
612 depends on SPI_MASTER
613 help
614 This enables the PCAP ASIC present on EZX Phones. This is
615 needed for MMC, TouchScreen, Sound, USB, etc..
616
617 config MFD_VIPERBOARD
618 tristate "Nano River Technologies Viperboard"
619 select MFD_CORE
620 depends on USB
621 default n
622 help
623 Say yes here if you want support for Nano River Technologies
624 Viperboard.
625 There are mfd cell drivers available for i2c master, adc and
626 both gpios found on the board. The spi part does not yet
627 have a driver.
628 You need to select the mfd cell drivers separately.
629 The drivers do not support all features the board exposes.
630
631 config MFD_RETU
632 tristate "Nokia Retu and Tahvo multi-function device"
633 select MFD_CORE
634 depends on I2C
635 select REGMAP_IRQ
636 help
637 Retu and Tahvo are a multi-function devices found on Nokia
638 Internet Tablets (770, N800 and N810).
639
640 config MFD_PCF50633
641 tristate "NXP PCF50633"
642 depends on I2C
643 select REGMAP_I2C
644 help
645 Say yes here if you have NXP PCF50633 chip on your board.
646 This core driver provides register access and IRQ handling
647 facilities, and registers devices for the various functions
648 so that function-specific drivers can bind to them.
649
650 config PCF50633_ADC
651 tristate "NXP PCF50633 ADC"
652 depends on MFD_PCF50633
653 help
654 Say yes here if you want to include support for ADC in the
655 NXP PCF50633 chip.
656
657 config PCF50633_GPIO
658 tristate "NXP PCF50633 GPIO"
659 depends on MFD_PCF50633
660 help
661 Say yes here if you want to include support GPIO for pins on
662 the PCF50633 chip.
663
664 config UCB1400_CORE
665 tristate "Philips UCB1400 Core driver"
666 depends on AC97_BUS
667 depends on GPIOLIB
668 help
669 This enables support for the Philips UCB1400 core functions.
670 The UCB1400 is an AC97 audio codec.
671
672 To compile this driver as a module, choose M here: the
673 module will be called ucb1400_core.
674
675 config MFD_PM8XXX
676 tristate
677
678 config MFD_PM8921_CORE
679 tristate "Qualcomm PM8921 PMIC chip"
680 depends on (ARM || HEXAGON)
681 select IRQ_DOMAIN
682 select MFD_CORE
683 select MFD_PM8XXX
684 select REGMAP
685 help
686 If you say yes to this option, support will be included for the
687 built-in PM8921 PMIC chip.
688
689 This is required if your board has a PM8921 and uses its features,
690 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
691
692 Say M here if you want to include support for PM8921 chip as a module.
693 This will build a module called "pm8921-core".
694
695 config MFD_QCOM_RPM
696 tristate "Qualcomm Resource Power Manager (RPM)"
697 depends on ARCH_QCOM && OF
698 help
699 If you say yes to this option, support will be included for the
700 Resource Power Manager system found in the Qualcomm 8660, 8960 and
701 8064 based devices.
702
703 This is required to access many regulators, clocks and bus
704 frequencies controlled by the RPM on these devices.
705
706 Say M here if you want to include support for the Qualcomm RPM as a
707 module. This will build a module called "qcom_rpm".
708
709 config MFD_SPMI_PMIC
710 tristate "Qualcomm SPMI PMICs"
711 depends on ARCH_QCOM || COMPILE_TEST
712 depends on OF
713 depends on SPMI
714 select REGMAP_SPMI
715 help
716 This enables support for the Qualcomm SPMI PMICs.
717 These PMICs are currently used with the Snapdragon 800 series of
718 SoCs. Note, that this will only be useful paired with descriptions
719 of the independent functions as children nodes in the device tree.
720
721 Say M here if you want to include support for the SPMI PMIC
722 series as a module. The module will be called "qcom-spmi-pmic".
723
724 config MFD_RDC321X
725 tristate "RDC R-321x southbridge"
726 select MFD_CORE
727 depends on PCI
728 help
729 Say yes here if you want to have support for the RDC R-321x SoC
730 southbridge which provides access to GPIOs and Watchdog using the
731 southbridge PCI device configuration space.
732
733 config MFD_RTSX_PCI
734 tristate "Realtek PCI-E card reader"
735 depends on PCI
736 select MFD_CORE
737 help
738 This supports for Realtek PCI-Express card reader including rts5209,
739 rts5227, rts522A, rts5229, rts5249, rts524A, rts525A, rtl8411, etc.
740 Realtek card reader supports access to many types of memory cards,
741 such as Memory Stick, Memory Stick Pro, Secure Digital and
742 MultiMediaCard.
743
744 config MFD_RT5033
745 tristate "Richtek RT5033 Power Management IC"
746 depends on I2C=y
747 select MFD_CORE
748 select REGMAP_I2C
749 select REGMAP_IRQ
750 help
751 This driver provides for the Richtek RT5033 Power Management IC,
752 which includes the I2C driver and the Core APIs. This driver provides
753 common support for accessing the device. The device supports multiple
754 sub-devices like charger, fuel gauge, flash LED, current source,
755 LDO and Buck.
756
757 config MFD_RTSX_USB
758 tristate "Realtek USB card reader"
759 depends on USB
760 select MFD_CORE
761 help
762 Select this option to get support for Realtek USB 2.0 card readers
763 including RTS5129, RTS5139, RTS5179 and RTS5170.
764 Realtek card reader supports access to many types of memory cards,
765 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
766
767 config MFD_RC5T583
768 bool "Ricoh RC5T583 Power Management system device"
769 depends on I2C=y
770 select MFD_CORE
771 select REGMAP_I2C
772 help
773 Select this option to get support for the RICOH583 Power
774 Management system device.
775 This driver provides common support for accessing the device
776 through i2c interface. The device supports multiple sub-devices
777 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
778 Additional drivers must be enabled in order to use the
779 different functionality of the device.
780
781 config MFD_RK808
782 tristate "Rockchip RK808 Power Management chip"
783 depends on I2C && OF
784 select MFD_CORE
785 select REGMAP_I2C
786 select REGMAP_IRQ
787 help
788 If you say yes here you get support for the RK808
789 Power Management chips.
790 This driver provides common support for accessing the device
791 through I2C interface. The device supports multiple sub-devices
792 including interrupts, RTC, LDO & DCDC regulators, and onkey.
793
794 config MFD_RN5T618
795 tristate "Ricoh RN5T5618 PMIC"
796 depends on I2C
797 select MFD_CORE
798 select REGMAP_I2C
799 help
800 Say yes here to add support for the Ricoh RN5T618 PMIC. This
801 driver provides common support for accessing the device,
802 additional drivers must be enabled in order to use the
803 functionality of the device.
804
805 config MFD_SEC_CORE
806 bool "SAMSUNG Electronics PMIC Series Support"
807 depends on I2C=y
808 select MFD_CORE
809 select REGMAP_I2C
810 select REGMAP_IRQ
811 help
812 Support for the Samsung Electronics MFD series.
813 This driver provides common support for accessing the device,
814 additional drivers must be enabled in order to use the functionality
815 of the device
816
817 config MFD_SI476X_CORE
818 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
819 depends on I2C
820 select MFD_CORE
821 select REGMAP_I2C
822 help
823 This is the core driver for the SI476x series of AM/FM
824 radio. This MFD driver connects the radio-si476x V4L2 module
825 and the si476x audio codec.
826
827 To compile this driver as a module, choose M here: the
828 module will be called si476x-core.
829
830 config MFD_SM501
831 tristate "Silicon Motion SM501"
832 ---help---
833 This is the core driver for the Silicon Motion SM501 multimedia
834 companion chip. This device is a multifunction device which may
835 provide numerous interfaces including USB host controller, USB gadget,
836 asynchronous serial ports, audio functions, and a dual display video
837 interface. The device may be connected by PCI or local bus with
838 varying functions enabled.
839
840 config MFD_SM501_GPIO
841 bool "Export GPIO via GPIO layer"
842 depends on MFD_SM501 && GPIOLIB
843 ---help---
844 This option uses the gpio library layer to export the 64 GPIO
845 lines on the SM501. The platform data is used to supply the
846 base number for the first GPIO line to register.
847
848 config MFD_SKY81452
849 tristate "Skyworks Solutions SKY81452"
850 select MFD_CORE
851 select REGMAP_I2C
852 depends on I2C
853 help
854 This is the core driver for the Skyworks SKY81452 backlight and
855 voltage regulator device.
856
857 This driver can also be built as a module. If so, the module
858 will be called sky81452.
859
860 config MFD_SMSC
861 bool "SMSC ECE1099 series chips"
862 depends on I2C=y
863 select MFD_CORE
864 select REGMAP_I2C
865 help
866 If you say yes here you get support for the
867 ece1099 chips from SMSC.
868
869 To compile this driver as a module, choose M here: the
870 module will be called smsc.
871
872 config ABX500_CORE
873 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
874 default y if ARCH_U300 || ARCH_U8500
875 help
876 Say yes here if you have the ABX500 Mixed Signal IC family
877 chips. This core driver expose register access functions.
878 Functionality specific drivers using these functions can
879 remain unchanged when IC changes. Binding of the functions to
880 actual register access is done by the IC core driver.
881
882 config AB3100_CORE
883 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
884 depends on I2C=y && ABX500_CORE
885 select MFD_CORE
886 default y if ARCH_U300
887 help
888 Select this to enable the AB3100 Mixed Signal IC core
889 functionality. This connects to a AB3100 on the I2C bus
890 and expose a number of symbols needed for dependent devices
891 to read and write registers and subscribe to events from
892 this multi-functional IC. This is needed to use other features
893 of the AB3100 such as battery-backed RTC, charging control,
894 LEDs, vibrator, system power and temperature, power management
895 and ALSA sound.
896
897 config AB3100_OTP
898 tristate "ST-Ericsson AB3100 OTP functions"
899 depends on AB3100_CORE
900 default y if AB3100_CORE
901 help
902 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
903 programmable memory) support. This exposes a sysfs file to read
904 out OTP values.
905
906 config AB8500_CORE
907 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
908 depends on ABX500_CORE && MFD_DB8500_PRCMU
909 select POWER_SUPPLY
910 select MFD_CORE
911 select IRQ_DOMAIN
912 help
913 Select this option to enable access to AB8500 power management
914 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
915 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
916 the irq_chip parts for handling the Mixed Signal chip events.
917 This chip embeds various other multimedia funtionalities as well.
918
919 config AB8500_DEBUG
920 bool "Enable debug info via debugfs"
921 depends on AB8500_GPADC && DEBUG_FS
922 default y if DEBUG_FS
923 help
924 Select this option if you want debug information using the debug
925 filesystem, debugfs.
926
927 config AB8500_GPADC
928 bool "ST-Ericsson AB8500 GPADC driver"
929 depends on AB8500_CORE && REGULATOR_AB8500
930 default y
931 help
932 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
933
934 config MFD_DB8500_PRCMU
935 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
936 depends on UX500_SOC_DB8500
937 select MFD_CORE
938 help
939 Select this option to enable support for the DB8500 Power Reset
940 and Control Management Unit. This is basically an autonomous
941 system controller running an XP70 microprocessor, which is accessed
942 through a register map.
943
944 config MFD_STMPE
945 bool "STMicroelectronics STMPE"
946 depends on (I2C=y || SPI_MASTER=y)
947 depends on OF
948 select MFD_CORE
949 help
950 Support for the STMPE family of I/O Expanders from
951 STMicroelectronics.
952
953 Currently supported devices are:
954
955 STMPE811: GPIO, Touchscreen
956 STMPE1601: GPIO, Keypad
957 STMPE1801: GPIO, Keypad
958 STMPE2401: GPIO, Keypad
959 STMPE2403: GPIO, Keypad
960
961 This driver provides common support for accessing the device,
962 additional drivers must be enabled in order to use the functionality
963 of the device. Currently available sub drivers are:
964
965 GPIO: stmpe-gpio
966 Keypad: stmpe-keypad
967 Touchscreen: stmpe-ts
968
969 menu "STMicroelectronics STMPE Interface Drivers"
970 depends on MFD_STMPE
971
972 config STMPE_I2C
973 bool "STMicroelectronics STMPE I2C Interface"
974 depends on I2C=y
975 default y
976 help
977 This is used to enable I2C interface of STMPE
978
979 config STMPE_SPI
980 bool "STMicroelectronics STMPE SPI Interface"
981 depends on SPI_MASTER
982 help
983 This is used to enable SPI interface of STMPE
984 endmenu
985
986 config MFD_STA2X11
987 bool "STMicroelectronics STA2X11"
988 depends on STA2X11
989 select MFD_CORE
990 select REGMAP_MMIO
991
992 config MFD_SUN6I_PRCM
993 bool "Allwinner A31 PRCM controller"
994 depends on ARCH_SUNXI
995 select MFD_CORE
996 help
997 Support for the PRCM (Power/Reset/Clock Management) unit available
998 in A31 SoC.
999
1000 config MFD_SYSCON
1001 bool "System Controller Register R/W Based on Regmap"
1002 select REGMAP_MMIO
1003 help
1004 Select this option to enable accessing system control registers
1005 via regmap.
1006
1007 config MFD_DAVINCI_VOICECODEC
1008 tristate
1009 select MFD_CORE
1010 select REGMAP_MMIO
1011
1012 config MFD_TI_AM335X_TSCADC
1013 tristate "TI ADC / Touch Screen chip support"
1014 select MFD_CORE
1015 select REGMAP
1016 select REGMAP_MMIO
1017 help
1018 If you say yes here you get support for Texas Instruments series
1019 of Touch Screen /ADC chips.
1020 To compile this driver as a module, choose M here: the
1021 module will be called ti_am335x_tscadc.
1022
1023 config MFD_DM355EVM_MSP
1024 bool "TI DaVinci DM355 EVM microcontroller"
1025 depends on I2C=y && MACH_DAVINCI_DM355_EVM
1026 help
1027 This driver supports the MSP430 microcontroller used on these
1028 boards. MSP430 firmware manages resets and power sequencing,
1029 inputs from buttons and the IR remote, LEDs, an RTC, and more.
1030
1031 config MFD_LP3943
1032 tristate "TI/National Semiconductor LP3943 MFD Driver"
1033 depends on I2C
1034 select MFD_CORE
1035 select REGMAP_I2C
1036 help
1037 Support for the TI/National Semiconductor LP3943.
1038 This driver consists of GPIO and PWM drivers.
1039 With these functionalities, it can be used for LED string control or
1040 general usage such like a GPIO controller and a PWM controller.
1041
1042 config MFD_LP8788
1043 bool "TI LP8788 Power Management Unit Driver"
1044 depends on I2C=y
1045 select MFD_CORE
1046 select REGMAP_I2C
1047 select IRQ_DOMAIN
1048 help
1049 TI LP8788 PMU supports regulators, battery charger, RTC,
1050 ADC, backlight driver and current sinks.
1051
1052 config MFD_OMAP_USB_HOST
1053 bool "TI OMAP USBHS core and TLL driver"
1054 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1055 default y
1056 help
1057 This is the core driver for the OAMP EHCI and OHCI drivers.
1058 This MFD driver does the required setup functionalities for
1059 OMAP USB Host drivers.
1060
1061 config MFD_PALMAS
1062 bool "TI Palmas series chips"
1063 select MFD_CORE
1064 select REGMAP_I2C
1065 select REGMAP_IRQ
1066 depends on I2C=y
1067 help
1068 If you say yes here you get support for the Palmas
1069 series of PMIC chips from Texas Instruments.
1070
1071 config TPS6105X
1072 tristate "TI TPS61050/61052 Boost Converters"
1073 depends on I2C
1074 select REGMAP_I2C
1075 select REGULATOR
1076 select MFD_CORE
1077 select REGULATOR_FIXED_VOLTAGE
1078 help
1079 This option enables a driver for the TP61050/TPS61052
1080 high-power "white LED driver". This boost converter is
1081 sometimes used for other things than white LEDs, and
1082 also contains a GPIO pin.
1083
1084 config TPS65010
1085 tristate "TI TPS6501x Power Management chips"
1086 depends on I2C && GPIOLIB
1087 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1088 help
1089 If you say yes here you get support for the TPS6501x series of
1090 Power Management chips. These include voltage regulators,
1091 lithium ion/polymer battery charging, and other features that
1092 are often used in portable devices like cell phones and cameras.
1093
1094 This driver can also be built as a module. If so, the module
1095 will be called tps65010.
1096
1097 config TPS6507X
1098 tristate "TI TPS6507x Power Management / Touch Screen chips"
1099 select MFD_CORE
1100 depends on I2C
1101 help
1102 If you say yes here you get support for the TPS6507x series of
1103 Power Management / Touch Screen chips. These include voltage
1104 regulators, lithium ion/polymer battery charging, touch screen
1105 and other features that are often used in portable devices.
1106 This driver can also be built as a module. If so, the module
1107 will be called tps6507x.
1108
1109 config TPS65911_COMPARATOR
1110 tristate
1111
1112 config MFD_TPS65090
1113 bool "TI TPS65090 Power Management chips"
1114 depends on I2C=y
1115 select MFD_CORE
1116 select REGMAP_I2C
1117 select REGMAP_IRQ
1118 help
1119 If you say yes here you get support for the TPS65090 series of
1120 Power Management chips.
1121 This driver provides common support for accessing the device,
1122 additional drivers must be enabled in order to use the
1123 functionality of the device.
1124
1125 config MFD_TPS65217
1126 tristate "TI TPS65217 Power Management / White LED chips"
1127 depends on I2C
1128 select MFD_CORE
1129 select REGMAP_I2C
1130 help
1131 If you say yes here you get support for the TPS65217 series of
1132 Power Management / White LED chips.
1133 These include voltage regulators, lithium ion/polymer battery
1134 charger, wled and other features that are often used in portable
1135 devices.
1136
1137 This driver can also be built as a module. If so, the module
1138 will be called tps65217.
1139
1140 config MFD_TPS65218
1141 tristate "TI TPS65218 Power Management chips"
1142 depends on I2C
1143 select MFD_CORE
1144 select REGMAP_I2C
1145 select REGMAP_IRQ
1146 help
1147 If you say yes here you get support for the TPS65218 series of
1148 Power Management chips.
1149 These include voltage regulators, gpio and other features
1150 that are often used in portable devices. Only regulator
1151 component is currently supported.
1152
1153 This driver can also be built as a module. If so, the module
1154 will be called tps65218.
1155
1156 config MFD_TPS6586X
1157 bool "TI TPS6586x Power Management chips"
1158 depends on I2C=y
1159 select MFD_CORE
1160 select REGMAP_I2C
1161 help
1162 If you say yes here you get support for the TPS6586X series of
1163 Power Management chips.
1164 This driver provides common support for accessing the device,
1165 additional drivers must be enabled in order to use the
1166 functionality of the device.
1167
1168 This driver can also be built as a module. If so, the module
1169 will be called tps6586x.
1170
1171 config MFD_TPS65910
1172 bool "TI TPS65910 Power Management chip"
1173 depends on I2C=y
1174 depends on GPIOLIB || COMPILE_TEST
1175 select MFD_CORE
1176 select REGMAP_I2C
1177 select REGMAP_IRQ
1178 select IRQ_DOMAIN
1179 help
1180 if you say yes here you get support for the TPS65910 series of
1181 Power Management chips.
1182
1183 config MFD_TPS65912
1184 bool "TI TPS65912 Power Management chip"
1185 depends on GPIOLIB
1186 select MFD_CORE
1187 help
1188 If you say yes here you get support for the TPS65912 series of
1189 PM chips.
1190
1191 config MFD_TPS65912_I2C
1192 bool "TI TPS65912 Power Management chip with I2C"
1193 select MFD_CORE
1194 select MFD_TPS65912
1195 depends on I2C=y && GPIOLIB
1196 help
1197 If you say yes here you get support for the TPS65912 series of
1198 PM chips with I2C interface.
1199
1200 config MFD_TPS65912_SPI
1201 bool "TI TPS65912 Power Management chip with SPI"
1202 select MFD_CORE
1203 select MFD_TPS65912
1204 depends on SPI_MASTER && GPIOLIB
1205 help
1206 If you say yes here you get support for the TPS65912 series of
1207 PM chips with SPI interface.
1208
1209 config MFD_TPS80031
1210 bool "TI TPS80031/TPS80032 Power Management chips"
1211 depends on I2C=y
1212 select MFD_CORE
1213 select REGMAP_I2C
1214 select REGMAP_IRQ
1215 help
1216 If you say yes here you get support for the Texas Instruments
1217 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1218 Path and Battery Charger. The device provides five configurable
1219 step-down converters, 11 general purpose LDOs, USB OTG Module,
1220 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1221 Power Path from USB, 32K clock generator.
1222
1223 config TWL4030_CORE
1224 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1225 depends on I2C=y
1226 select IRQ_DOMAIN
1227 select REGMAP_I2C
1228 help
1229 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1230 This core driver provides register access and IRQ handling
1231 facilities, and registers devices for the various functions
1232 so that function-specific drivers can bind to them.
1233
1234 These multi-function chips are found on many OMAP2 and OMAP3
1235 boards, providing power management, RTC, GPIO, keypad, a
1236 high speed USB OTG transceiver, an audio codec (on most
1237 versions) and many other features.
1238
1239 config TWL4030_POWER
1240 bool "TI TWL4030 power resources"
1241 depends on TWL4030_CORE && ARM
1242 help
1243 Say yes here if you want to use the power resources on the
1244 TWL4030 family chips. Most of these resources are regulators,
1245 which have a separate driver; some are control signals, such
1246 as clock request handshaking.
1247
1248 This driver uses board-specific data to initialize the resources
1249 and load scripts controlling which resources are switched off/on
1250 or reset when a sleep, wakeup or warm reset event occurs.
1251
1252 config MFD_TWL4030_AUDIO
1253 bool "TI TWL4030 Audio"
1254 depends on TWL4030_CORE
1255 select MFD_CORE
1256 default n
1257
1258 config TWL6040_CORE
1259 bool "TI TWL6040 audio codec"
1260 depends on I2C=y
1261 select MFD_CORE
1262 select REGMAP_I2C
1263 select REGMAP_IRQ
1264 default n
1265 help
1266 Say yes here if you want support for Texas Instruments TWL6040 audio
1267 codec.
1268 This driver provides common support for accessing the device,
1269 additional drivers must be enabled in order to use the
1270 functionality of the device (audio, vibra).
1271
1272 config MENELAUS
1273 bool "TI TWL92330/Menelaus PM chip"
1274 depends on I2C=y && ARCH_OMAP2
1275 help
1276 If you say yes here you get support for the Texas Instruments
1277 TWL92330/Menelaus Power Management chip. This include voltage
1278 regulators, Dual slot memory card transceivers, real-time clock
1279 and other features that are often used in portable devices like
1280 cell phones and PDAs.
1281
1282 config MFD_WL1273_CORE
1283 tristate "TI WL1273 FM radio"
1284 depends on I2C
1285 select MFD_CORE
1286 default n
1287 help
1288 This is the core driver for the TI WL1273 FM radio. This MFD
1289 driver connects the radio-wl1273 V4L2 module and the wl1273
1290 audio codec.
1291
1292 config MFD_LM3533
1293 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1294 depends on I2C
1295 select MFD_CORE
1296 select REGMAP_I2C
1297 help
1298 Say yes here to enable support for National Semiconductor / TI
1299 LM3533 Lighting Power chips.
1300
1301 This driver provides common support for accessing the device;
1302 additional drivers must be enabled in order to use the LED,
1303 backlight or ambient-light-sensor functionality of the device.
1304
1305 config MFD_TIMBERDALE
1306 tristate "Timberdale FPGA"
1307 select MFD_CORE
1308 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1309 ---help---
1310 This is the core driver for the timberdale FPGA. This device is a
1311 multifunction device which exposes numerous platform devices.
1312
1313 The timberdale FPGA can be found on the Intel Atom development board
1314 for in-vehicle infontainment, called Russellville.
1315
1316 config MFD_TC3589X
1317 bool "Toshiba TC35892 and variants"
1318 depends on I2C=y
1319 depends on OF
1320 select MFD_CORE
1321 help
1322 Support for the Toshiba TC35892 and variants I/O Expander.
1323
1324 This driver provides common support for accessing the device,
1325 additional drivers must be enabled in order to use the
1326 functionality of the device.
1327
1328 config MFD_TMIO
1329 bool
1330 default n
1331
1332 config MFD_T7L66XB
1333 bool "Toshiba T7L66XB"
1334 depends on ARM && HAVE_CLK
1335 select MFD_CORE
1336 select MFD_TMIO
1337 help
1338 Support for Toshiba Mobile IO Controller T7L66XB
1339
1340 config MFD_TC6387XB
1341 bool "Toshiba TC6387XB"
1342 depends on ARM && HAVE_CLK
1343 select MFD_CORE
1344 select MFD_TMIO
1345 help
1346 Support for Toshiba Mobile IO Controller TC6387XB
1347
1348 config MFD_TC6393XB
1349 bool "Toshiba TC6393XB"
1350 depends on ARM && HAVE_CLK
1351 select GPIOLIB
1352 select MFD_CORE
1353 select MFD_TMIO
1354 help
1355 Support for Toshiba Mobile IO Controller TC6393XB
1356
1357 config MFD_VX855
1358 tristate "VIA VX855/VX875 integrated south bridge"
1359 depends on PCI
1360 select MFD_CORE
1361 help
1362 Say yes here to enable support for various functions of the
1363 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1364 and/or vx855_gpio drivers for this to do anything useful.
1365
1366 config MFD_ARIZONA
1367 select REGMAP
1368 select REGMAP_IRQ
1369 select MFD_CORE
1370 bool
1371
1372 config MFD_ARIZONA_I2C
1373 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1374 select MFD_ARIZONA
1375 select MFD_CORE
1376 select REGMAP_I2C
1377 depends on I2C
1378 help
1379 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1380 audio SoC core functionality controlled via I2C.
1381
1382 config MFD_ARIZONA_SPI
1383 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1384 select MFD_ARIZONA
1385 select MFD_CORE
1386 select REGMAP_SPI
1387 depends on SPI_MASTER
1388 help
1389 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1390 audio SoC core functionality controlled via I2C.
1391
1392 config MFD_CS47L24
1393 bool "Cirrus Logic CS47L24 and WM1831"
1394 depends on MFD_ARIZONA
1395 help
1396 Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1397
1398 config MFD_WM5102
1399 bool "Wolfson Microelectronics WM5102"
1400 depends on MFD_ARIZONA
1401 help
1402 Support for Wolfson Microelectronics WM5102 low power audio SoC
1403
1404 config MFD_WM5110
1405 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1406 depends on MFD_ARIZONA
1407 help
1408 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1409 low power audio SoC
1410
1411 config MFD_WM8997
1412 bool "Wolfson Microelectronics WM8997"
1413 depends on MFD_ARIZONA
1414 help
1415 Support for Wolfson Microelectronics WM8997 low power audio SoC
1416
1417 config MFD_WM8998
1418 bool "Wolfson Microelectronics WM8998"
1419 depends on MFD_ARIZONA
1420 help
1421 Support for Wolfson Microelectronics WM8998 low power audio SoC
1422
1423 config MFD_WM8400
1424 bool "Wolfson Microelectronics WM8400"
1425 select MFD_CORE
1426 depends on I2C=y
1427 select REGMAP_I2C
1428 help
1429 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1430 CODEC. This driver provides common support for accessing
1431 the device, additional drivers must be enabled in order to use
1432 the functionality of the device.
1433
1434 config MFD_WM831X
1435 bool
1436
1437 config MFD_WM831X_I2C
1438 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1439 select MFD_CORE
1440 select MFD_WM831X
1441 select REGMAP_I2C
1442 select IRQ_DOMAIN
1443 depends on I2C=y
1444 help
1445 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1446 when controlled using I2C. This driver provides common support
1447 for accessing the device, additional drivers must be enabled in
1448 order to use the functionality of the device.
1449
1450 config MFD_WM831X_SPI
1451 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1452 select MFD_CORE
1453 select MFD_WM831X
1454 select REGMAP_SPI
1455 select IRQ_DOMAIN
1456 depends on SPI_MASTER
1457 help
1458 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1459 when controlled using SPI. This driver provides common support
1460 for accessing the device, additional drivers must be enabled in
1461 order to use the functionality of the device.
1462
1463 config MFD_WM8350
1464 bool
1465
1466 config MFD_WM8350_I2C
1467 bool "Wolfson Microelectronics WM8350 with I2C"
1468 select MFD_WM8350
1469 depends on I2C=y
1470 help
1471 The WM8350 is an integrated audio and power management
1472 subsystem with watchdog and RTC functionality for embedded
1473 systems. This option enables core support for the WM8350 with
1474 I2C as the control interface. Additional options must be
1475 selected to enable support for the functionality of the chip.
1476
1477 config MFD_WM8994
1478 tristate "Wolfson Microelectronics WM8994"
1479 select MFD_CORE
1480 select REGMAP_I2C
1481 select REGMAP_IRQ
1482 depends on I2C
1483 help
1484 The WM8994 is a highly integrated hi-fi CODEC designed for
1485 smartphone applications. As well as audio functionality it
1486 has on board GPIO and regulator functionality which is
1487 supported via the relevant subsystems. This driver provides
1488 core support for the WM8994, in order to use the actual
1489 functionaltiy of the device other drivers must be enabled.
1490
1491 config MFD_STW481X
1492 tristate "Support for ST Microelectronics STw481x"
1493 depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1494 select REGMAP_I2C
1495 select MFD_CORE
1496 help
1497 Select this option to enable the STw481x chip driver used
1498 in various ST Microelectronics and ST-Ericsson embedded
1499 Nomadik series.
1500
1501 menu "Multimedia Capabilities Port drivers"
1502 depends on ARCH_SA1100
1503
1504 config MCP
1505 tristate
1506
1507 # Interface drivers
1508 config MCP_SA11X0
1509 tristate "Support SA11x0 MCP interface"
1510 depends on ARCH_SA1100
1511 select MCP
1512
1513 # Chip drivers
1514 config MCP_UCB1200
1515 tristate "Support for UCB1200 / UCB1300"
1516 depends on MCP_SA11X0
1517 select MCP
1518
1519 config MCP_UCB1200_TS
1520 tristate "Touchscreen interface support"
1521 depends on MCP_UCB1200 && INPUT
1522
1523 endmenu
1524
1525 config MFD_VEXPRESS_SYSREG
1526 bool "Versatile Express System Registers"
1527 depends on VEXPRESS_CONFIG && GPIOLIB
1528 default y
1529 select CLKSRC_MMIO
1530 select GPIO_GENERIC_PLATFORM
1531 select MFD_CORE
1532 select MFD_SYSCON
1533 help
1534 System Registers are the platform configuration block
1535 on the ARM Ltd. Versatile Express board.
1536
1537 endmenu
1538 endif
This page took 0.060424 seconds and 6 git commands to generate.