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
281 Say yes here if you want support for TWL6030 PWM.
282 This is used to control charging LED brightness.
285 bool "Support for TWL6040 audio codec"
286 depends on I2C=y && GENERIC_HARDIRQS
292 Say yes here if you want support for Texas Instruments TWL6040 audio
294 This driver provides common support for accessing the device,
295 additional drivers must be enabled in order to use the
296 functionality of the device (audio, vibra).
299 bool "Support STMicroelectronics STMPE"
300 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
303 Support for the STMPE family of I/O Expanders from
306 Currently supported devices are:
308 STMPE811: GPIO, Touchscreen
309 STMPE1601: GPIO, Keypad
310 STMPE2401: GPIO, Keypad
311 STMPE2403: GPIO, Keypad
313 This driver provides common support for accessing the device,
314 additional drivers must be enabled in order to use the functionality
315 of the device. Currently available sub drivers are:
319 Touchscreen: stmpe-ts
321 menu "STMPE Interface Drivers"
325 bool "STMPE I2C Inteface"
329 This is used to enable I2C interface of STMPE
332 bool "STMPE SPI Inteface"
333 depends on SPI_MASTER
335 This is used to enable SPI interface of STMPE
339 bool "Support Toshiba TC35892 and variants"
340 depends on I2C=y && GENERIC_HARDIRQS
343 Support for the Toshiba TC35892 and variants I/O Expander.
345 This driver provides common support for accessing the device,
346 additional drivers must be enabled in order to use the
347 functionality of the device.
354 bool "Support Toshiba T7L66XB"
355 depends on ARM && HAVE_CLK
359 Support for Toshiba Mobile IO Controller T7L66XB
362 bool "Support Toshiba TC6387XB"
363 depends on ARM && HAVE_CLK
367 Support for Toshiba Mobile IO Controller TC6387XB
370 bool "Support Toshiba TC6393XB"
371 depends on GPIOLIB && ARM && HAVE_CLK
375 Support for Toshiba Mobile IO Controller TC6393XB
378 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
381 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
382 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
383 usually found on PXA processors-based platforms. This includes
384 the I2C driver and the core APIs _only_, you have to select
385 individual components like LCD backlight, voltage regulators,
386 LEDs and battery-charger under the corresponding menus.
392 config MFD_DA9052_SPI
393 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
397 depends on SPI_MASTER=y
399 Support for the Dialog Semiconductor DA9052 PMIC
400 when controlled using SPI. This driver provides common support
401 for accessing the device, additional drivers must be enabled in
402 order to use the functionality of the device.
404 config MFD_DA9052_I2C
405 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
411 Support for the Dialog Semiconductor DA9052 PMIC
412 when controlled using I2C. This driver provides common support
413 for accessing the device, additional drivers must be enabled in
414 order to use the functionality of the device.
417 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
420 Say yes here to add support for Analog Devices AD5520 and ADP5501,
421 Multifunction Power Management IC. This includes
422 the I2C driver and the core APIs _only_, you have to select
423 individual components like LCD backlight, LEDs, GPIOs and Kepad
424 under the corresponding menus.
427 bool "Maxim Semiconductor MAX77693 PMIC Support"
428 depends on I2C=y && GENERIC_HARDIRQS
432 Say yes here to support for Maxim Semiconductor MAX77693.
433 This is a companion Power Management IC with Flash, Haptic, Charger,
434 and MUIC(Micro USB Interface Controller) controls on chip.
435 This driver provides common support for accessing the device;
436 additional drivers must be enabled in order to use the functionality
440 bool "Maxim Semiconductor MAX8925 PMIC Support"
441 depends on I2C=y && GENERIC_HARDIRQS
444 Say yes here to support for Maxim Semiconductor MAX8925. This is
445 a Power Management IC. This driver provides common support for
446 accessing the device, additional drivers must be enabled in order
447 to use the functionality of the device.
450 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
451 depends on I2C=y && GENERIC_HARDIRQS
454 Say yes here to support for Maxim Semiconductor MAX8997/8966.
455 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
456 MUIC controls on chip.
457 This driver provides common support for accessing the device;
458 additional drivers must be enabled in order to use the functionality
462 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
463 depends on I2C=y && GENERIC_HARDIRQS
466 Say yes here to support for Maxim Semiconductor MAX8998 and
467 National Semiconductor LP3974. This is a Power Management IC.
468 This driver provides common support for accessing the device,
469 additional drivers must be enabled in order to use the functionality
473 bool "SAMSUNG S5M Series Support"
474 depends on I2C=y && GENERIC_HARDIRQS
478 Support for the Samsung Electronics S5M MFD series.
479 This driver provides common support for accessing the device,
480 additional drivers must be enabled in order to use the functionality
484 bool "Support Wolfson Microelectronics WM8400"
489 Support for the Wolfson Microelecronics WM8400 PMIC and audio
490 CODEC. This driver provides common support for accessing
491 the device, additional drivers must be enabled in order to use
492 the functionality of the device.
496 depends on GENERIC_HARDIRQS
498 config MFD_WM831X_I2C
499 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
504 depends on I2C=y && GENERIC_HARDIRQS
506 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
507 when controlled using I2C. This driver provides common support
508 for accessing the device, additional drivers must be enabled in
509 order to use the functionality of the device.
511 config MFD_WM831X_SPI
512 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
517 depends on SPI_MASTER && GENERIC_HARDIRQS
519 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
520 when controlled using SPI. This driver provides common support
521 for accessing the device, additional drivers must be enabled in
522 order to use the functionality of the device.
526 depends on GENERIC_HARDIRQS
528 config MFD_WM8350_CONFIG_MODE_0
530 depends on MFD_WM8350
532 config MFD_WM8350_CONFIG_MODE_1
534 depends on MFD_WM8350
536 config MFD_WM8350_CONFIG_MODE_2
538 depends on MFD_WM8350
540 config MFD_WM8350_CONFIG_MODE_3
542 depends on MFD_WM8350
544 config MFD_WM8351_CONFIG_MODE_0
546 depends on MFD_WM8350
548 config MFD_WM8351_CONFIG_MODE_1
550 depends on MFD_WM8350
552 config MFD_WM8351_CONFIG_MODE_2
554 depends on MFD_WM8350
556 config MFD_WM8351_CONFIG_MODE_3
558 depends on MFD_WM8350
560 config MFD_WM8352_CONFIG_MODE_0
562 depends on MFD_WM8350
564 config MFD_WM8352_CONFIG_MODE_1
566 depends on MFD_WM8350
568 config MFD_WM8352_CONFIG_MODE_2
570 depends on MFD_WM8350
572 config MFD_WM8352_CONFIG_MODE_3
574 depends on MFD_WM8350
576 config MFD_WM8350_I2C
577 bool "Support Wolfson Microelectronics WM8350 with I2C"
579 depends on I2C=y && GENERIC_HARDIRQS
581 The WM8350 is an integrated audio and power management
582 subsystem with watchdog and RTC functionality for embedded
583 systems. This option enables core support for the WM8350 with
584 I2C as the control interface. Additional options must be
585 selected to enable support for the functionality of the chip.
588 bool "Support Wolfson Microelectronics WM8994"
592 depends on I2C=y && GENERIC_HARDIRQS
594 The WM8994 is a highly integrated hi-fi CODEC designed for
595 smartphone applicatiosn. As well as audio functionality it
596 has on board GPIO and regulator functionality which is
597 supported via the relevant subsystems. This driver provides
598 core support for the WM8994, in order to use the actual
599 functionaltiy of the device other drivers must be enabled.
602 tristate "Support for NXP PCF50633"
606 Say yes here if you have NXP PCF50633 chip on your board.
607 This core driver provides register access and IRQ handling
608 facilities, and registers devices for the various functions
609 so that function-specific drivers can bind to them.
612 tristate "Support for NXP PCF50633 ADC"
613 depends on MFD_PCF50633
615 Say yes here if you want to include support for ADC in the
619 tristate "Support for NXP PCF50633 GPIO"
620 depends on MFD_PCF50633
622 Say yes here if you want to include support GPIO for pins on
630 depends on SPI_MASTER || I2C
634 Enable support for the Freescale MC13783 and MC13892 PMICs.
635 This driver provides common support for accessing the device,
636 additional drivers must be enabled in order to use the
637 functionality of the device.
639 config MFD_MC13XXX_SPI
640 tristate "Freescale MC13783 and MC13892 SPI interface"
641 depends on SPI_MASTER
645 Select this if your MC13xxx is connected via an SPI bus.
647 config MFD_MC13XXX_I2C
648 tristate "Freescale MC13892 I2C interface"
653 Select this if your MC13xxx is connected via an I2C bus.
656 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
657 default y if ARCH_U300 || ARCH_U8500
659 Say yes here if you have the ABX500 Mixed Signal IC family
660 chips. This core driver expose register access functions.
661 Functionality specific drivers using these functions can
662 remain unchanged when IC changes. Binding of the functions to
663 actual register access is done by the IC core driver.
666 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
667 depends on I2C=y && ABX500_CORE
669 default y if ARCH_U300
671 Select this to enable the AB3100 Mixed Signal IC core
672 functionality. This connects to a AB3100 on the I2C bus
673 and expose a number of symbols needed for dependent devices
674 to read and write registers and subscribe to events from
675 this multi-functional IC. This is needed to use other features
676 of the AB3100 such as battery-backed RTC, charging control,
677 LEDs, vibrator, system power and temperature, power management
681 tristate "ST-Ericsson AB3100 OTP functions"
682 depends on AB3100_CORE
683 default y if AB3100_CORE
685 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
686 programmable memory) support. This exposes a sysfs file to read
691 depends on GENERIC_HARDIRQS && SPI_MASTER
693 This enables the PCAP ASIC present on EZX Phones. This is
694 needed for MMC, TouchScreen, Sound, USB, etc..
697 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
698 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
701 Select this option to enable access to AB8500 power management
702 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
703 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
704 the irq_chip parts for handling the Mixed Signal chip events.
705 This chip embeds various other multimedia funtionalities as well.
707 config AB8500_I2C_CORE
708 bool "AB8500 register access via PRCMU I2C"
709 depends on AB8500_CORE && MFD_DB8500_PRCMU
712 This enables register access to the AB8500 chip via PRCMU I2C.
713 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
714 the I2C bus is connected to the Power Reset
715 and Mangagement Unit, PRCMU.
718 bool "Enable debug info via debugfs"
719 depends on AB8500_CORE && DEBUG_FS
720 default y if DEBUG_FS
722 Select this option if you want debug information using the debug
726 bool "AB8500 GPADC driver"
727 depends on AB8500_CORE && REGULATOR_AB8500
730 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
732 config MFD_DB8500_PRCMU
733 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
734 depends on UX500_SOC_DB8500
737 Select this option to enable support for the DB8500 Power Reset
738 and Control Management Unit. This is basically an autonomous
739 system controller running an XP70 microprocessor, which is accessed
740 through a register map.
743 tristate "Support for CS5535 and CS5536 southbridge core functions"
745 depends on PCI && X86
747 This is the core driver for CS5535/CS5536 MFD functions. This is
748 necessary for using the board's GPIO and MFGPT functionality.
750 config MFD_TIMBERDALE
751 tristate "Support for the Timberdale FPGA"
753 depends on PCI && GPIOLIB
755 This is the core driver for the timberdale FPGA. This device is a
756 multifunction device which exposes numerous platform devices.
758 The timberdale FPGA can be found on the Intel Atom development board
759 for in-vehicle infontainment, called Russellville.
762 tristate "Intel SCH LPC"
766 LPC bridge function of the Intel SCH provides support for
767 System Management Bus and General Purpose I/O.
770 tristate "Intel ICH LPC"
774 The LPC bridge function of the Intel ICH provides support for
775 many functional units. This driver provides needed support for
776 other drivers to control these functions, currently GPIO and
780 tristate "Support for RDC-R321x southbridge"
784 Say yes here if you want to have support for the RDC R-321x SoC
785 southbridge which provides access to GPIOs and Watchdog using the
786 southbridge PCI device configuration space.
788 config MFD_JANZ_CMODIO
789 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
793 This is the core driver for the Janz CMOD-IO PCI MODULbus
794 carrier board. This device is a PCI to MODULbus bridge which may
795 host many different types of MODULbus daughterboards, including
796 CAN and GPIO controllers.
798 config MFD_JZ4740_ADC
799 bool "Support for the JZ4740 SoC ADC core"
801 select GENERIC_IRQ_CHIP
802 depends on MACH_JZ4740
804 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
805 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
808 tristate "Support for VIA VX855/VX875 integrated south bridge"
812 Say yes here to enable support for various functions of the
813 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
814 and/or vx855_gpio drivers for this to do anything useful.
816 config MFD_WL1273_CORE
817 tristate "Support for TI WL1273 FM radio."
822 This is the core driver for the TI WL1273 FM radio. This MFD
823 driver connects the radio-wl1273 V4L2 module and the wl1273
826 config MFD_OMAP_USB_HOST
827 bool "Support OMAP USBHS core driver"
828 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
831 This is the core driver for the OAMP EHCI and OHCI drivers.
832 This MFD driver does the required setup functionalities for
833 OMAP USB Host drivers.
838 config MFD_PM8921_CORE
839 tristate "Qualcomm PM8921 PMIC chip"
844 If you say yes to this option, support will be included for the
845 built-in PM8921 PMIC chip.
847 This is required if your board has a PM8921 and uses its features,
848 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
850 Say M here if you want to include support for PM8921 chip as a module.
851 This will build a module called "pm8921-core".
853 config MFD_PM8XXX_IRQ
854 bool "Support for Qualcomm PM8xxx IRQ features"
855 depends on MFD_PM8XXX
856 default y if MFD_PM8XXX
858 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
860 This is required to use certain other PM 8xxx features, such as GPIO
863 config TPS65911_COMPARATOR
867 bool "TPS65090 Power Management chips"
868 depends on I2C=y && GENERIC_HARDIRQS
872 If you say yes here you get support for the TPS65090 series of
873 Power Management chips.
874 This driver provides common support for accessing the device,
875 additional drivers must be enabled in order to use the
876 functionality of the device.
878 config MFD_AAT2870_CORE
879 bool "Support for the AnalogicTech AAT2870"
881 depends on I2C=y && GPIOLIB
883 If you say yes here you get support for the AAT2870.
884 This driver provides common support for accessing the device,
885 additional drivers must be enabled in order to use the
886 functionality of the device.
888 config MFD_INTEL_MSIC
889 bool "Support for Intel MSIC"
890 depends on INTEL_SCU_IPC
893 Select this option to enable access to Intel MSIC (Avatele
894 Passage) chip. This chip embeds audio, battery, GPIO, etc.
895 devices used in Intel Medfield platforms.
898 bool "Ricoh RC5T583 Power Management system device"
899 depends on I2C=y && GENERIC_HARDIRQS
903 Select this option to get support for the RICOH583 Power
904 Management system device.
905 This driver provides common support for accessing the device
906 through i2c interface. The device supports multiple sub-devices
907 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
908 Additional drivers must be enabled in order to use the
909 different functionality of the device.
912 bool "STA2X11 multi function device support"
917 bool "Support for Freescale i.MX on-chip ANATOP controller"
920 Select this option to enable Freescale i.MX on-chip ANATOP
921 MFD controller. This controller embeds regulator and
922 thermal devices for Freescale i.MX platforms.
925 bool "Support for the TI Palmas series chips"
931 If you say yes here you get support for the Palmas
932 series of PMIC chips from Texas Instruments.
937 menu "Multimedia Capabilities Port drivers"
938 depends on ARCH_SA1100
945 tristate "Support SA11x0 MCP interface"
946 depends on ARCH_SA1100
951 bool "Support for UCB1200 / UCB1300"
952 depends on MCP_SA11X0
955 config MCP_UCB1200_TS
956 tristate "Touchscreen interface support"
957 depends on MCP_UCB1200 && INPUT