2
# Multifunction miscellaneous devices
6
menu "Multifunction device drivers"
13
bool "Support Marvell 88PM8606/88PM8607"
14
depends on I2C=y && GENERIC_HARDIRQS
17
This supports for Marvell 88PM8606/88PM8607 Power Management IC.
18
This includes the I2C driver and the core APIs _only_, you have to
19
select individual components like voltage regulators, RTC and
20
battery-charger under the corresponding menus.
23
tristate "Support for Silicon Motion SM501"
25
This is the core driver for the Silicon Motion SM501 multimedia
26
companion chip. This device is a multifunction device which may
27
provide numerous interfaces including USB host controller, USB gadget,
28
asynchronous serial ports, audio functions, and a dual display video
29
interface. The device may be connected by PCI or local bus with
30
varying functions enabled.
33
bool "Export GPIO via GPIO layer"
34
depends on MFD_SM501 && GPIOLIB
36
This option uses the gpio library layer to export the 64 GPIO
37
lines on the SM501. The platform data is used to supply the
38
base number for the first GPIO line to register.
41
bool "Support for Compaq ASIC3"
42
depends on GENERIC_HARDIRQS && GPIOLIB && ARM
45
This driver supports the ASIC3 multifunction chip found on many
46
PDAs (mainly iPAQ and HTC based ones)
48
config MFD_DAVINCI_VOICECODEC
52
config MFD_DM355EVM_MSP
53
bool "DaVinci DM355 EVM microcontroller"
54
depends on I2C=y && MACH_DAVINCI_DM355_EVM
56
This driver supports the MSP430 microcontroller used on these
57
boards. MSP430 firmware manages resets and power sequencing,
58
inputs from buttons and the IR remote, LEDs, an RTC, and more.
61
tristate "TI Sequencer Serial Port support"
62
depends on ARCH_DAVINCI_TNETV107X
65
Say Y here if you want support for the Sequencer Serial Port
66
in a Texas Instruments TNETV107X SoC.
68
To compile this driver as a module, choose M here: the
69
module will be called ti-ssp.
72
bool "HTC EGPIO support"
73
depends on GENERIC_HARDIRQS && GPIOLIB && ARM
75
This driver supports the CPLD egpio chip present on
76
several HTC phones. It provides basic support for input
77
pins, output pins, and irqs.
80
tristate "HTC PASIC3 LED/DS1WM chip support"
83
This core driver provides register access for the LED/DS1WM
84
chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
85
HTC Magician devices, respectively. Actual functionality is
86
handled by the leds-pasic3 and ds1wm drivers.
89
bool "HTC I2C PLD chip support"
90
depends on I2C=y && GPIOLIB
92
If you say yes here you get support for the supposed CPLD
93
found on omap850 HTC devices like the HTC Wizard and HTC Herald.
94
This device provides input and output GPIOs through an I2C
95
interface to one or more sub-chips.
98
tristate "Philips UCB1400 Core driver"
102
This enables support for the Philips UCB1400 core functions.
103
The UCB1400 is an AC97 audio codec.
105
To compile this driver as a module, choose M here: the
106
module will be called ucb1400_core.
109
tristate "TPS61050/61052 Boost Converters"
113
select REGULATOR_FIXED_VOLTAGE
115
This option enables a driver for the TP61050/TPS61052
116
high-power "white LED driver". This boost converter is
117
sometimes used for other things than white LEDs, and
118
also contains a GPIO pin.
121
tristate "TPS6501x Power Management chips"
122
depends on I2C && GPIOLIB
123
default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
125
If you say yes here you get support for the TPS6501x series of
126
Power Management chips. These include voltage regulators,
127
lithium ion/polymer battery charging, and other features that
128
are often used in portable devices like cell phones and cameras.
130
This driver can also be built as a module. If so, the module
131
will be called tps65010.
134
tristate "TPS6507x Power Management / Touch Screen chips"
138
If you say yes here you get support for the TPS6507x series of
139
Power Management / Touch Screen chips. These include voltage
140
regulators, lithium ion/polymer battery charging, touch screen
141
and other features that are often used in portable devices.
142
This driver can also be built as a module. If so, the module
143
will be called tps6507x.
146
bool "TPS6586x Power Management chips"
147
depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
150
If you say yes here you get support for the TPS6586X series of
151
Power Management chips.
152
This driver provides common support for accessing the device,
153
additional drivers must be enabled in order to use the
154
functionality of the device.
156
This driver can also be built as a module. If so, the module
157
will be called tps6586x.
160
bool "TPS65910 Power Management chip"
161
depends on I2C=y && GPIOLIB
165
if you say yes here you get support for the TPS65910 series of
166
Power Management chips.
172
config MFD_TPS65912_I2C
173
bool "TPS95612 Power Management chip with I2C"
176
depends on I2C=y && GPIOLIB
178
If you say yes here you get support for the TPS65912 series of
179
PM chips with I2C interface.
181
config MFD_TPS65912_SPI
182
bool "TPS65912 Power Management chip with SPI"
185
depends on SPI_MASTER && GPIOLIB
187
If you say yes here you get support for the TPS65912 series of
188
PM chips with SPI interface.
191
bool "Texas Instruments TWL92330/Menelaus PM chip"
192
depends on I2C=y && ARCH_OMAP2
194
If you say yes here you get support for the Texas Instruments
195
TWL92330/Menelaus Power Management chip. This include voltage
196
regulators, Dual slot memory card transceivers, real-time clock
197
and other features that are often used in portable devices like
198
cell phones and PDAs.
201
bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
202
depends on I2C=y && GENERIC_HARDIRQS
204
Say yes here if you have TWL4030 / TWL6030 family chip on your board.
205
This core driver provides register access and IRQ handling
206
facilities, and registers devices for the various functions
207
so that function-specific drivers can bind to them.
209
These multi-function chips are found on many OMAP2 and OMAP3
210
boards, providing power management, RTC, GPIO, keypad, a
211
high speed USB OTG transceiver, an audio codec (on most
212
versions) and many other features.
215
tristate "Texas Instruments TWL4030 MADC"
216
depends on TWL4030_CORE
218
This driver provides support for triton TWL4030-MADC. The
219
driver supports both RT and SW conversion methods.
221
This driver can be built as a module. If so it will be
225
bool "Support power resources on TWL4030 family chips"
226
depends on TWL4030_CORE && ARM
228
Say yes here if you want to use the power resources on the
229
TWL4030 family chips. Most of these resources are regulators,
230
which have a separate driver; some are control signals, such
231
as clock request handshaking.
233
This driver uses board-specific data to initialize the resources
234
and load scripts controlling which resources are switched off/on
235
or reset when a sleep, wakeup or warm reset event occurs.
237
config MFD_TWL4030_AUDIO
239
depends on TWL4030_CORE
244
tristate "TWL6030 PWM (Pulse Width Modulator) Support"
245
depends on TWL4030_CORE
249
Say yes here if you want support for TWL6030 PWM.
250
This is used to control charging LED brightness.
254
depends on TWL4030_CORE && GENERIC_HARDIRQS
259
bool "Support STMicroelectronics STMPE"
260
depends on I2C=y && GENERIC_HARDIRQS
263
Support for the STMPE family of I/O Expanders from
266
Currently supported devices are:
268
STMPE811: GPIO, Touchscreen
269
STMPE1601: GPIO, Keypad
270
STMPE2401: GPIO, Keypad
271
STMPE2403: GPIO, Keypad
273
This driver provides common support for accessing the device,
274
additional drivers must be enabled in order to use the functionality
275
of the device. Currently available sub drivers are:
279
Touchscreen: stmpe-ts
282
bool "Support Toshiba TC35892 and variants"
283
depends on I2C=y && GENERIC_HARDIRQS
286
Support for the Toshiba TC35892 and variants I/O Expander.
288
This driver provides common support for accessing the device,
289
additional drivers must be enabled in order to use the
290
functionality of the device.
297
bool "Support Toshiba T7L66XB"
298
depends on ARM && HAVE_CLK
302
Support for Toshiba Mobile IO Controller T7L66XB
305
bool "Support Toshiba TC6387XB"
306
depends on ARM && HAVE_CLK
310
Support for Toshiba Mobile IO Controller TC6387XB
313
bool "Support Toshiba TC6393XB"
314
depends on GPIOLIB && ARM
318
Support for Toshiba Mobile IO Controller TC6393XB
321
bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
324
Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
325
ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
326
usually found on PXA processors-based platforms. This includes
327
the I2C driver and the core APIs _only_, you have to select
328
individual components like LCD backlight, voltage regulators,
329
LEDs and battery-charger under the corresponding menus.
332
bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
335
Say yes here to add support for Analog Devices AD5520 and ADP5501,
336
Multifunction Power Management IC. This includes
337
the I2C driver and the core APIs _only_, you have to select
338
individual components like LCD backlight, LEDs, GPIOs and Kepad
339
under the corresponding menus.
342
bool "Maxim Semiconductor MAX8925 PMIC Support"
343
depends on I2C=y && GENERIC_HARDIRQS
346
Say yes here to support for Maxim Semiconductor MAX8925. This is
347
a Power Management IC. This driver provies common support for
348
accessing the device, additional drivers must be enabled in order
349
to use the functionality of the device.
352
bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
353
depends on I2C=y && GENERIC_HARDIRQS
356
Say yes here to support for Maxim Semiconductor MAX8998/8966.
357
This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
358
MUIC controls on chip.
359
This driver provides common support for accessing the device;
360
additional drivers must be enabled in order to use the functionality
364
bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
365
depends on I2C=y && GENERIC_HARDIRQS
368
Say yes here to support for Maxim Semiconductor MAX8998 and
369
National Semiconductor LP3974. This is a Power Management IC.
370
This driver provies common support for accessing the device,
371
additional drivers must be enabled in order to use the functionality
375
tristate "Support Wolfson Microelectronics WM8400"
380
Support for the Wolfson Microelecronics WM8400 PMIC and audio
381
CODEC. This driver provides common support for accessing
382
the device, additional drivers must be enabled in order to use
383
the functionality of the device.
387
depends on GENERIC_HARDIRQS
389
config MFD_WM831X_I2C
390
bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
394
depends on I2C=y && GENERIC_HARDIRQS
396
Support for the Wolfson Microelecronics WM831x and WM832x PMICs
397
when controlled using I2C. This driver provides common support
398
for accessing the device, additional drivers must be enabled in
399
order to use the functionality of the device.
401
config MFD_WM831X_SPI
402
bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
406
depends on SPI_MASTER && GENERIC_HARDIRQS
408
Support for the Wolfson Microelecronics WM831x and WM832x PMICs
409
when controlled using SPI. This driver provides common support
410
for accessing the device, additional drivers must be enabled in
411
order to use the functionality of the device.
415
depends on GENERIC_HARDIRQS
417
config MFD_WM8350_CONFIG_MODE_0
419
depends on MFD_WM8350
421
config MFD_WM8350_CONFIG_MODE_1
423
depends on MFD_WM8350
425
config MFD_WM8350_CONFIG_MODE_2
427
depends on MFD_WM8350
429
config MFD_WM8350_CONFIG_MODE_3
431
depends on MFD_WM8350
433
config MFD_WM8351_CONFIG_MODE_0
435
depends on MFD_WM8350
437
config MFD_WM8351_CONFIG_MODE_1
439
depends on MFD_WM8350
441
config MFD_WM8351_CONFIG_MODE_2
443
depends on MFD_WM8350
445
config MFD_WM8351_CONFIG_MODE_3
447
depends on MFD_WM8350
449
config MFD_WM8352_CONFIG_MODE_0
451
depends on MFD_WM8350
453
config MFD_WM8352_CONFIG_MODE_1
455
depends on MFD_WM8350
457
config MFD_WM8352_CONFIG_MODE_2
459
depends on MFD_WM8350
461
config MFD_WM8352_CONFIG_MODE_3
463
depends on MFD_WM8350
465
config MFD_WM8350_I2C
466
bool "Support Wolfson Microelectronics WM8350 with I2C"
468
depends on I2C=y && GENERIC_HARDIRQS
470
The WM8350 is an integrated audio and power management
471
subsystem with watchdog and RTC functionality for embedded
472
systems. This option enables core support for the WM8350 with
473
I2C as the control interface. Additional options must be
474
selected to enable support for the functionality of the chip.
477
bool "Support Wolfson Microelectronics WM8994"
480
depends on I2C=y && GENERIC_HARDIRQS
482
The WM8994 is a highly integrated hi-fi CODEC designed for
483
smartphone applicatiosn. As well as audio functionality it
484
has on board GPIO and regulator functionality which is
485
supported via the relevant subsystems. This driver provides
486
core support for the WM8994, in order to use the actual
487
functionaltiy of the device other drivers must be enabled.
490
tristate "Support for NXP PCF50633"
494
Say yes here if you have NXP PCF50633 chip on your board.
495
This core driver provides register access and IRQ handling
496
facilities, and registers devices for the various functions
497
so that function-specific drivers can bind to them.
500
tristate "Support for NXP PCF50633 ADC"
501
depends on MFD_PCF50633
503
Say yes here if you want to include support for ADC in the
507
tristate "Support for NXP PCF50633 GPIO"
508
depends on MFD_PCF50633
510
Say yes here if you want to include support GPIO for pins on
517
tristate "Support Freescale MC13783 and MC13892"
518
depends on SPI_MASTER
522
Support for the Freescale (Atlas) PMIC and audio CODECs
524
This driver provides common support for accessing the device,
525
additional drivers must be enabled in order to use the
526
functionality of the device.
529
bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
530
default y if ARCH_U300 || ARCH_U8500
532
Say yes here if you have the ABX500 Mixed Signal IC family
533
chips. This core driver expose register access functions.
534
Functionality specific drivers using these functions can
535
remain unchanged when IC changes. Binding of the functions to
536
actual register access is done by the IC core driver.
539
bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
540
depends on I2C=y && ABX500_CORE
542
default y if ARCH_U300
544
Select this to enable the AB3100 Mixed Signal IC core
545
functionality. This connects to a AB3100 on the I2C bus
546
and expose a number of symbols needed for dependent devices
547
to read and write registers and subscribe to events from
548
this multi-functional IC. This is needed to use other features
549
of the AB3100 such as battery-backed RTC, charging control,
550
LEDs, vibrator, system power and temperature, power management
554
tristate "ST-Ericsson AB3100 OTP functions"
555
depends on AB3100_CORE
556
default y if AB3100_CORE
558
Select this to enable the AB3100 Mixed Signal IC OTP (one-time
559
programmable memory) support. This exposes a sysfs file to read
564
depends on GENERIC_HARDIRQS && SPI_MASTER
566
This enables the PCAP ASIC present on EZX Phones. This is
567
needed for MMC, TouchScreen, Sound, USB, etc..
570
bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
571
depends on ABX500_CORE && MFD_DB5500_PRCMU
574
Select this option to enable access to AB5500 power management
575
chip. This connects to the db5500 chip via the I2C bus via PRCMU.
576
This chip embeds various other multimedia funtionalities as well.
579
bool "Enable debug info via debugfs"
580
depends on AB5500_CORE && DEBUG_FS
581
default y if DEBUG_FS
583
Select this option if you want debug information from the AB5500
584
using the debug filesystem, debugfs.
587
bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
588
depends on GENERIC_HARDIRQS && ABX500_CORE
591
Select this option to enable access to AB8500 power management
592
chip. This connects to U8500 either on the SSP/SPI bus (deprecated
593
since hardware version v1.0) or the I2C bus via PRCMU. It also adds
594
the irq_chip parts for handling the Mixed Signal chip events.
595
This chip embeds various other multimedia funtionalities as well.
597
config AB8500_I2C_CORE
598
bool "AB8500 register access via PRCMU I2C"
599
depends on AB8500_CORE && MFD_DB8500_PRCMU
602
This enables register access to the AB8500 chip via PRCMU I2C.
603
The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
604
the I2C bus is connected to the Power Reset
605
and Mangagement Unit, PRCMU.
608
bool "Enable debug info via debugfs"
609
depends on AB8500_CORE && DEBUG_FS
610
default y if DEBUG_FS
612
Select this option if you want debug information using the debug
616
bool "AB8500 GPADC driver"
617
depends on AB8500_CORE && REGULATOR_AB8500
620
AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
622
config MFD_DB8500_PRCMU
623
bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
624
depends on UX500_SOC_DB8500
627
Select this option to enable support for the DB8500 Power Reset
628
and Control Management Unit. This is basically an autonomous
629
system controller running an XP70 microprocessor, which is accessed
630
through a register map.
632
config MFD_DB5500_PRCMU
633
bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
634
depends on UX500_SOC_DB5500
637
Select this option to enable support for the DB5500 Power Reset
638
and Control Management Unit. This is basically an autonomous
639
system controller running an XP70 microprocessor, which is accessed
640
through a register map.
643
tristate "Support for CS5535 and CS5536 southbridge core functions"
645
depends on PCI && X86
647
This is the core driver for CS5535/CS5536 MFD functions. This is
648
necessary for using the board's GPIO and MFGPT functionality.
650
config MFD_TIMBERDALE
651
tristate "Support for the Timberdale FPGA"
653
depends on PCI && GPIOLIB
655
This is the core driver for the timberdale FPGA. This device is a
656
multifunction device which exposes numerous platform devices.
658
The timberdale FPGA can be found on the Intel Atom development board
659
for in-vehicle infontainment, called Russellville.
662
tristate "Intel SCH LPC"
666
LPC bridge function of the Intel SCH provides support for
667
System Management Bus and General Purpose I/O.
670
tristate "Support for RDC-R321x southbridge"
674
Say yes here if you want to have support for the RDC R-321x SoC
675
southbridge which provides access to GPIOs and Watchdog using the
676
southbridge PCI device configuration space.
678
config MFD_JANZ_CMODIO
679
tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
683
This is the core driver for the Janz CMOD-IO PCI MODULbus
684
carrier board. This device is a PCI to MODULbus bridge which may
685
host many different types of MODULbus daughterboards, including
686
CAN and GPIO controllers.
688
config MFD_JZ4740_ADC
689
bool "Support for the JZ4740 SoC ADC core"
691
select GENERIC_IRQ_CHIP
692
depends on MACH_JZ4740
694
Say yes here if you want support for the ADC unit in the JZ4740 SoC.
695
This driver is necessary for jz4740-battery and jz4740-hwmon driver.
698
tristate "Support for VIA VX855/VX875 integrated south bridge"
702
Say yes here to enable support for various functions of the
703
VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
704
and/or vx855_gpio drivers for this to do anything useful.
706
config MFD_WL1273_CORE
707
tristate "Support for TI WL1273 FM radio."
712
This is the core driver for the TI WL1273 FM radio. This MFD
713
driver connects the radio-wl1273 V4L2 module and the wl1273
716
config MFD_OMAP_USB_HOST
717
bool "Support OMAP USBHS core driver"
718
depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
721
This is the core driver for the OAMP EHCI and OHCI drivers.
722
This MFD driver does the required setup functionalities for
723
OMAP USB Host drivers.
728
config MFD_PM8921_CORE
729
tristate "Qualcomm PM8921 PMIC chip"
734
If you say yes to this option, support will be included for the
735
built-in PM8921 PMIC chip.
737
This is required if your board has a PM8921 and uses its features,
738
such as: MPPs, GPIOs, regulators, interrupts, and PWM.
740
Say M here if you want to include support for PM8921 chip as a module.
741
This will build a module called "pm8921-core".
743
config MFD_PM8XXX_IRQ
744
bool "Support for Qualcomm PM8xxx IRQ features"
745
depends on MFD_PM8XXX
746
default y if MFD_PM8XXX
748
This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
750
This is required to use certain other PM 8xxx features, such as GPIO
753
config TPS65911_COMPARATOR
756
config MFD_AAT2870_CORE
757
bool "Support for the AnalogicTech AAT2870"
759
depends on I2C=y && GPIOLIB
761
If you say yes here you get support for the AAT2870.
762
This driver provides common support for accessing the device,
763
additional drivers must be enabled in order to use the
764
functionality of the device.
766
config MFD_INTEL_MSIC
767
bool "Support for Intel MSIC"
768
depends on INTEL_SCU_IPC
771
Select this option to enable access to Intel MSIC (Avatele
772
Passage) chip. This chip embeds audio, battery, GPIO, etc.
773
devices used in Intel Medfield platforms.
778
menu "Multimedia Capabilities Port drivers"
779
depends on ARCH_SA1100
786
tristate "Support SA11x0 MCP interface"
787
depends on ARCH_SA1100
792
tristate "Support for UCB1200 / UCB1300"
795
config MCP_UCB1200_TS
796
tristate "Touchscreen interface support"
797
depends on MCP_UCB1200 && INPUT