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