2 # Multifunction miscellaneous devices
6 menu "Multifunction device drivers"
13 bool "Support Marvell 88PM8606/88PM8607"
14 depends on I2C=y && GENERIC_HARDIRQS
18 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
19 This includes the I2C driver and the core APIs _only_, you have to
20 select individual components like voltage regulators, RTC and
21 battery-charger under the corresponding menus.
24 tristate "Support for Silicon Motion SM501"
26 This is the core driver for the Silicon Motion SM501 multimedia
27 companion chip. This device is a multifunction device which may
28 provide numerous interfaces including USB host controller, USB gadget,
29 asynchronous serial ports, audio functions, and a dual display video
30 interface. The device may be connected by PCI or local bus with
31 varying functions enabled.
34 bool "Export GPIO via GPIO layer"
35 depends on MFD_SM501 && GPIOLIB
37 This option uses the gpio library layer to export the 64 GPIO
38 lines on the SM501. The platform data is used to supply the
39 base number for the first GPIO line to register.
42 bool "Support for Compaq ASIC3"
43 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
46 This driver supports the ASIC3 multifunction chip found on many
47 PDAs (mainly iPAQ and HTC based ones)
49 config MFD_DAVINCI_VOICECODEC
53 config MFD_DM355EVM_MSP
54 bool "DaVinci DM355 EVM microcontroller"
55 depends on I2C=y && MACH_DAVINCI_DM355_EVM
57 This driver supports the MSP430 microcontroller used on these
58 boards. MSP430 firmware manages resets and power sequencing,
59 inputs from buttons and the IR remote, LEDs, an RTC, and more.
62 tristate "TI Sequencer Serial Port support"
63 depends on ARCH_DAVINCI_TNETV107X
66 Say Y here if you want support for the Sequencer Serial Port
67 in a Texas Instruments TNETV107X SoC.
69 To compile this driver as a module, choose M here: the
70 module will be called ti-ssp.
73 bool "HTC EGPIO support"
74 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
76 This driver supports the CPLD egpio chip present on
77 several HTC phones. It provides basic support for input
78 pins, output pins, and irqs.
81 tristate "HTC PASIC3 LED/DS1WM chip support"
84 This core driver provides register access for the LED/DS1WM
85 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
86 HTC Magician devices, respectively. Actual functionality is
87 handled by the leds-pasic3 and ds1wm drivers.
90 bool "HTC I2C PLD chip support"
91 depends on I2C=y && GPIOLIB
93 If you say yes here you get support for the supposed CPLD
94 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
95 This device provides input and output GPIOs through an I2C
96 interface to one or more sub-chips.
99 tristate "Philips UCB1400 Core driver"
103 This enables support for the Philips UCB1400 core functions.
104 The UCB1400 is an AC97 audio codec.
106 To compile this driver as a module, choose M here: the
107 module will be called ucb1400_core.
110 tristate "LM3533 Lighting Power chip"
115 Say yes here to enable support for National Semiconductor / TI
116 LM3533 Lighting Power chips.
118 This driver provides common support for accessing the device;
119 additional drivers must be enabled in order to use the LED,
120 backlight or ambient-light-sensor functionality of the device.
123 tristate "TPS61050/61052 Boost Converters"
127 select REGULATOR_FIXED_VOLTAGE
129 This option enables a driver for the TP61050/TPS61052
130 high-power "white LED driver". This boost converter is
131 sometimes used for other things than white LEDs, and
132 also contains a GPIO pin.
135 tristate "TPS6501x Power Management chips"
136 depends on I2C && GPIOLIB
137 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
139 If you say yes here you get support for the TPS6501x series of
140 Power Management chips. These include voltage regulators,
141 lithium ion/polymer battery charging, and other features that
142 are often used in portable devices like cell phones and cameras.
144 This driver can also be built as a module. If so, the module
145 will be called tps65010.
148 tristate "TPS6507x Power Management / Touch Screen chips"
152 If you say yes here you get support for the TPS6507x series of
153 Power Management / Touch Screen chips. These include voltage
154 regulators, lithium ion/polymer battery charging, touch screen
155 and other features that are often used in portable devices.
156 This driver can also be built as a module. If so, the module
157 will be called tps6507x.
160 tristate "TPS65217 Power Management / White LED chips"
165 If you say yes here you get support for the TPS65217 series of
166 Power Management / White LED chips.
167 These include voltage regulators, lithium ion/polymer battery
168 charger, wled and other features that are often used in portable
171 This driver can also be built as a module. If so, the module
172 will be called tps65217.
175 bool "TPS6586x Power Management chips"
176 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
180 If you say yes here you get support for the TPS6586X series of
181 Power Management chips.
182 This driver provides common support for accessing the device,
183 additional drivers must be enabled in order to use the
184 functionality of the device.
186 This driver can also be built as a module. If so, the module
187 will be called tps6586x.
190 bool "TPS65910 Power Management chip"
191 depends on I2C=y && GPIOLIB
196 if you say yes here you get support for the TPS65910 series of
197 Power Management chips.
203 config MFD_TPS65912_I2C
204 bool "TPS65912 Power Management chip with I2C"
207 depends on I2C=y && GPIOLIB
209 If you say yes here you get support for the TPS65912 series of
210 PM chips with I2C interface.
212 config MFD_TPS65912_SPI
213 bool "TPS65912 Power Management chip with SPI"
216 depends on SPI_MASTER && GPIOLIB
218 If you say yes here you get support for the TPS65912 series of
219 PM chips with SPI interface.
222 bool "Texas Instruments TWL92330/Menelaus PM chip"
223 depends on I2C=y && ARCH_OMAP2
225 If you say yes here you get support for the Texas Instruments
226 TWL92330/Menelaus Power Management chip. This include voltage
227 regulators, Dual slot memory card transceivers, real-time clock
228 and other features that are often used in portable devices like
229 cell phones and PDAs.
232 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
233 depends on I2C=y && GENERIC_HARDIRQS
236 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
237 This core driver provides register access and IRQ handling
238 facilities, and registers devices for the various functions
239 so that function-specific drivers can bind to them.
241 These multi-function chips are found on many OMAP2 and OMAP3
242 boards, providing power management, RTC, GPIO, keypad, a
243 high speed USB OTG transceiver, an audio codec (on most
244 versions) and many other features.
247 tristate "Texas Instruments TWL4030 MADC"
248 depends on TWL4030_CORE
250 This driver provides support for triton TWL4030-MADC. The
251 driver supports both RT and SW conversion methods.
253 This driver can be built as a module. If so it will be
257 bool "Support power resources on TWL4030 family chips"
258 depends on TWL4030_CORE && ARM
260 Say yes here if you want to use the power resources on the
261 TWL4030 family chips. Most of these resources are regulators,
262 which have a separate driver; some are control signals, such
263 as clock request handshaking.
265 This driver uses board-specific data to initialize the resources
266 and load scripts controlling which resources are switched off/on
267 or reset when a sleep, wakeup or warm reset event occurs.
269 config MFD_TWL4030_AUDIO
271 depends on TWL4030_CORE
276 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
277 depends on TWL4030_CORE
282 Say yes here if you want support for TWL6030 PWM.
283 This is used to control charging LED brightness.
286 bool "Support for TWL6040 audio codec"
287 depends on I2C=y && GENERIC_HARDIRQS
293 Say yes here if you want support for Texas Instruments TWL6040 audio
295 This driver provides common support for accessing the device,
296 additional drivers must be enabled in order to use the
297 functionality of the device (audio, vibra).
300 bool "Support STMicroelectronics STMPE"
301 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
304 Support for the STMPE family of I/O Expanders from
307 Currently supported devices are:
309 STMPE811: GPIO, Touchscreen
310 STMPE1601: GPIO, Keypad
311 STMPE2401: GPIO, Keypad
312 STMPE2403: GPIO, Keypad
314 This driver provides common support for accessing the device,
315 additional drivers must be enabled in order to use the functionality
316 of the device. Currently available sub drivers are:
320 Touchscreen: stmpe-ts
322 menu "STMPE Interface Drivers"
326 bool "STMPE I2C Inteface"
330 This is used to enable I2C interface of STMPE
333 bool "STMPE SPI Inteface"
334 depends on SPI_MASTER
336 This is used to enable SPI interface of STMPE
340 bool "Support Toshiba TC35892 and variants"
341 depends on I2C=y && GENERIC_HARDIRQS
344 Support for the Toshiba TC35892 and variants I/O Expander.
346 This driver provides common support for accessing the device,
347 additional drivers must be enabled in order to use the
348 functionality of the device.
355 bool "Support Toshiba T7L66XB"
356 depends on ARM && HAVE_CLK
360 Support for Toshiba Mobile IO Controller T7L66XB
363 bool "Support Toshiba TC6387XB"
364 depends on ARM && HAVE_CLK
368 Support for Toshiba Mobile IO Controller TC6387XB
371 bool "Support Toshiba TC6393XB"
372 depends on GPIOLIB && ARM && HAVE_CLK
376 Support for Toshiba Mobile IO Controller TC6393XB
379 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
382 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
383 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
384 usually found on PXA processors-based platforms. This includes
385 the I2C driver and the core APIs _only_, you have to select
386 individual components like LCD backlight, voltage regulators,
387 LEDs and battery-charger under the corresponding menus.
393 config MFD_DA9052_SPI
394 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
398 depends on SPI_MASTER=y
400 Support for the Dialog Semiconductor DA9052 PMIC
401 when controlled using SPI. This driver provides common support
402 for accessing the device, additional drivers must be enabled in
403 order to use the functionality of the device.
405 config MFD_DA9052_I2C
406 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
412 Support for the Dialog Semiconductor DA9052 PMIC
413 when controlled using I2C. This driver provides common support
414 for accessing the device, additional drivers must be enabled in
415 order to use the functionality of the device.
418 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
421 Say yes here to add support for Analog Devices AD5520 and ADP5501,
422 Multifunction Power Management IC. This includes
423 the I2C driver and the core APIs _only_, you have to select
424 individual components like LCD backlight, LEDs, GPIOs and Kepad
425 under the corresponding menus.
428 bool "Maxim Semiconductor MAX77693 PMIC Support"
429 depends on I2C=y && GENERIC_HARDIRQS
433 Say yes here to support for Maxim Semiconductor MAX77693.
434 This is a companion Power Management IC with Flash, Haptic, Charger,
435 and MUIC(Micro USB Interface Controller) controls on chip.
436 This driver provides common support for accessing the device;
437 additional drivers must be enabled in order to use the functionality
441 bool "Maxim Semiconductor MAX8925 PMIC Support"
442 depends on I2C=y && GENERIC_HARDIRQS
445 Say yes here to support for Maxim Semiconductor MAX8925. This is
446 a Power Management IC. This driver provides common support for
447 accessing the device, additional drivers must be enabled in order
448 to use the functionality of the device.
451 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
452 depends on I2C=y && GENERIC_HARDIRQS
455 Say yes here to support for Maxim Semiconductor MAX8997/8966.
456 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
457 MUIC controls on chip.
458 This driver provides common support for accessing the device;
459 additional drivers must be enabled in order to use the functionality
463 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
464 depends on I2C=y && GENERIC_HARDIRQS
467 Say yes here to support for Maxim Semiconductor MAX8998 and
468 National Semiconductor LP3974. This is a Power Management IC.
469 This driver provides common support for accessing the device,
470 additional drivers must be enabled in order to use the functionality
474 bool "SAMSUNG S5M Series Support"
475 depends on I2C=y && GENERIC_HARDIRQS
479 Support for the Samsung Electronics S5M MFD series.
480 This driver provides common support for accessing the device,
481 additional drivers must be enabled in order to use the functionality
485 bool "Support Wolfson Microelectronics WM8400"
490 Support for the Wolfson Microelecronics WM8400 PMIC and audio
491 CODEC. This driver provides common support for accessing
492 the device, additional drivers must be enabled in order to use
493 the functionality of the device.
497 depends on GENERIC_HARDIRQS
499 config MFD_WM831X_I2C
500 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
505 depends on I2C=y && GENERIC_HARDIRQS
507 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
508 when controlled using I2C. This driver provides common support
509 for accessing the device, additional drivers must be enabled in
510 order to use the functionality of the device.
512 config MFD_WM831X_SPI
513 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
518 depends on SPI_MASTER && GENERIC_HARDIRQS
520 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
521 when controlled using SPI. This driver provides common support
522 for accessing the device, additional drivers must be enabled in
523 order to use the functionality of the device.
527 depends on GENERIC_HARDIRQS
529 config MFD_WM8350_CONFIG_MODE_0
531 depends on MFD_WM8350
533 config MFD_WM8350_CONFIG_MODE_1
535 depends on MFD_WM8350
537 config MFD_WM8350_CONFIG_MODE_2
539 depends on MFD_WM8350
541 config MFD_WM8350_CONFIG_MODE_3
543 depends on MFD_WM8350
545 config MFD_WM8351_CONFIG_MODE_0
547 depends on MFD_WM8350
549 config MFD_WM8351_CONFIG_MODE_1
551 depends on MFD_WM8350
553 config MFD_WM8351_CONFIG_MODE_2
555 depends on MFD_WM8350
557 config MFD_WM8351_CONFIG_MODE_3
559 depends on MFD_WM8350
561 config MFD_WM8352_CONFIG_MODE_0
563 depends on MFD_WM8350
565 config MFD_WM8352_CONFIG_MODE_1
567 depends on MFD_WM8350
569 config MFD_WM8352_CONFIG_MODE_2
571 depends on MFD_WM8350
573 config MFD_WM8352_CONFIG_MODE_3
575 depends on MFD_WM8350
577 config MFD_WM8350_I2C
578 bool "Support Wolfson Microelectronics WM8350 with I2C"
580 depends on I2C=y && GENERIC_HARDIRQS
582 The WM8350 is an integrated audio and power management
583 subsystem with watchdog and RTC functionality for embedded
584 systems. This option enables core support for the WM8350 with
585 I2C as the control interface. Additional options must be
586 selected to enable support for the functionality of the chip.
589 bool "Support Wolfson Microelectronics WM8994"
593 depends on I2C=y && GENERIC_HARDIRQS
595 The WM8994 is a highly integrated hi-fi CODEC designed for
596 smartphone applicatiosn. As well as audio functionality it
597 has on board GPIO and regulator functionality which is
598 supported via the relevant subsystems. This driver provides
599 core support for the WM8994, in order to use the actual
600 functionaltiy of the device other drivers must be enabled.
603 tristate "Support for NXP PCF50633"
607 Say yes here if you have NXP PCF50633 chip on your board.
608 This core driver provides register access and IRQ handling
609 facilities, and registers devices for the various functions
610 so that function-specific drivers can bind to them.
613 tristate "Support for NXP PCF50633 ADC"
614 depends on MFD_PCF50633
616 Say yes here if you want to include support for ADC in the
620 tristate "Support for NXP PCF50633 GPIO"
621 depends on MFD_PCF50633
623 Say yes here if you want to include support GPIO for pins on
631 depends on SPI_MASTER || I2C
635 Enable support for the Freescale MC13783 and MC13892 PMICs.
636 This driver provides common support for accessing the device,
637 additional drivers must be enabled in order to use the
638 functionality of the device.
640 config MFD_MC13XXX_SPI
641 tristate "Freescale MC13783 and MC13892 SPI interface"
642 depends on SPI_MASTER
646 Select this if your MC13xxx is connected via an SPI bus.
648 config MFD_MC13XXX_I2C
649 tristate "Freescale MC13892 I2C interface"
654 Select this if your MC13xxx is connected via an I2C bus.
657 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
658 default y if ARCH_U300 || ARCH_U8500
660 Say yes here if you have the ABX500 Mixed Signal IC family
661 chips. This core driver expose register access functions.
662 Functionality specific drivers using these functions can
663 remain unchanged when IC changes. Binding of the functions to
664 actual register access is done by the IC core driver.
667 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
668 depends on I2C=y && ABX500_CORE
670 default y if ARCH_U300
672 Select this to enable the AB3100 Mixed Signal IC core
673 functionality. This connects to a AB3100 on the I2C bus
674 and expose a number of symbols needed for dependent devices
675 to read and write registers and subscribe to events from
676 this multi-functional IC. This is needed to use other features
677 of the AB3100 such as battery-backed RTC, charging control,
678 LEDs, vibrator, system power and temperature, power management
682 tristate "ST-Ericsson AB3100 OTP functions"
683 depends on AB3100_CORE
684 default y if AB3100_CORE
686 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
687 programmable memory) support. This exposes a sysfs file to read
692 depends on GENERIC_HARDIRQS && SPI_MASTER
694 This enables the PCAP ASIC present on EZX Phones. This is
695 needed for MMC, TouchScreen, Sound, USB, etc..
698 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
699 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
702 Select this option to enable access to AB8500 power management
703 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
704 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
705 the irq_chip parts for handling the Mixed Signal chip events.
706 This chip embeds various other multimedia funtionalities as well.
708 config AB8500_I2C_CORE
709 bool "AB8500 register access via PRCMU I2C"
710 depends on AB8500_CORE && MFD_DB8500_PRCMU
713 This enables register access to the AB8500 chip via PRCMU I2C.
714 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
715 the I2C bus is connected to the Power Reset
716 and Mangagement Unit, PRCMU.
719 bool "Enable debug info via debugfs"
720 depends on AB8500_CORE && DEBUG_FS
721 default y if DEBUG_FS
723 Select this option if you want debug information using the debug
727 bool "AB8500 GPADC driver"
728 depends on AB8500_CORE && REGULATOR_AB8500
731 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
733 config MFD_DB8500_PRCMU
734 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
735 depends on UX500_SOC_DB8500
738 Select this option to enable support for the DB8500 Power Reset
739 and Control Management Unit. This is basically an autonomous
740 system controller running an XP70 microprocessor, which is accessed
741 through a register map.
744 tristate "Support for CS5535 and CS5536 southbridge core functions"
746 depends on PCI && X86
748 This is the core driver for CS5535/CS5536 MFD functions. This is
749 necessary for using the board's GPIO and MFGPT functionality.
751 config MFD_TIMBERDALE
752 tristate "Support for the Timberdale FPGA"
754 depends on PCI && GPIOLIB
756 This is the core driver for the timberdale FPGA. This device is a
757 multifunction device which exposes numerous platform devices.
759 The timberdale FPGA can be found on the Intel Atom development board
760 for in-vehicle infontainment, called Russellville.
763 tristate "Intel SCH LPC"
767 LPC bridge function of the Intel SCH provides support for
768 System Management Bus and General Purpose I/O.
771 tristate "Intel ICH LPC"
775 The LPC bridge function of the Intel ICH provides support for
776 many functional units. This driver provides needed support for
777 other drivers to control these functions, currently GPIO and
781 tristate "Support for RDC-R321x southbridge"
785 Say yes here if you want to have support for the RDC R-321x SoC
786 southbridge which provides access to GPIOs and Watchdog using the
787 southbridge PCI device configuration space.
789 config MFD_JANZ_CMODIO
790 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
794 This is the core driver for the Janz CMOD-IO PCI MODULbus
795 carrier board. This device is a PCI to MODULbus bridge which may
796 host many different types of MODULbus daughterboards, including
797 CAN and GPIO controllers.
799 config MFD_JZ4740_ADC
800 bool "Support for the JZ4740 SoC ADC core"
802 select GENERIC_IRQ_CHIP
803 depends on MACH_JZ4740
805 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
806 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
809 tristate "Support for VIA VX855/VX875 integrated south bridge"
813 Say yes here to enable support for various functions of the
814 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
815 and/or vx855_gpio drivers for this to do anything useful.
817 config MFD_WL1273_CORE
818 tristate "Support for TI WL1273 FM radio."
823 This is the core driver for the TI WL1273 FM radio. This MFD
824 driver connects the radio-wl1273 V4L2 module and the wl1273
827 config MFD_OMAP_USB_HOST
828 bool "Support OMAP USBHS core driver"
829 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
832 This is the core driver for the OAMP EHCI and OHCI drivers.
833 This MFD driver does the required setup functionalities for
834 OMAP USB Host drivers.
839 config MFD_PM8921_CORE
840 tristate "Qualcomm PM8921 PMIC chip"
845 If you say yes to this option, support will be included for the
846 built-in PM8921 PMIC chip.
848 This is required if your board has a PM8921 and uses its features,
849 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
851 Say M here if you want to include support for PM8921 chip as a module.
852 This will build a module called "pm8921-core".
854 config MFD_PM8XXX_IRQ
855 bool "Support for Qualcomm PM8xxx IRQ features"
856 depends on MFD_PM8XXX
857 default y if MFD_PM8XXX
859 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
861 This is required to use certain other PM 8xxx features, such as GPIO
864 config TPS65911_COMPARATOR
868 bool "TPS65090 Power Management chips"
869 depends on I2C=y && GENERIC_HARDIRQS
873 If you say yes here you get support for the TPS65090 series of
874 Power Management chips.
875 This driver provides common support for accessing the device,
876 additional drivers must be enabled in order to use the
877 functionality of the device.
879 config MFD_AAT2870_CORE
880 bool "Support for the AnalogicTech AAT2870"
882 depends on I2C=y && GPIOLIB
884 If you say yes here you get support for the AAT2870.
885 This driver provides common support for accessing the device,
886 additional drivers must be enabled in order to use the
887 functionality of the device.
889 config MFD_INTEL_MSIC
890 bool "Support for Intel MSIC"
891 depends on INTEL_SCU_IPC
894 Select this option to enable access to Intel MSIC (Avatele
895 Passage) chip. This chip embeds audio, battery, GPIO, etc.
896 devices used in Intel Medfield platforms.
899 bool "Ricoh RC5T583 Power Management system device"
900 depends on I2C=y && GENERIC_HARDIRQS
904 Select this option to get support for the RICOH583 Power
905 Management system device.
906 This driver provides common support for accessing the device
907 through i2c interface. The device supports multiple sub-devices
908 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
909 Additional drivers must be enabled in order to use the
910 different functionality of the device.
913 bool "STA2X11 multi function device support"
918 bool "Support for Freescale i.MX on-chip ANATOP controller"
921 Select this option to enable Freescale i.MX on-chip ANATOP
922 MFD controller. This controller embeds regulator and
923 thermal devices for Freescale i.MX platforms.
926 bool "Support for the TI Palmas series chips"
932 If you say yes here you get support for the Palmas
933 series of PMIC chips from Texas Instruments.
938 menu "Multimedia Capabilities Port drivers"
939 depends on ARCH_SA1100
946 tristate "Support SA11x0 MCP interface"
947 depends on ARCH_SA1100
952 bool "Support for UCB1200 / UCB1300"
953 depends on MCP_SA11X0
956 config MCP_UCB1200_TS
957 tristate "Touchscreen interface support"
958 depends on MCP_UCB1200 && INPUT