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
179 If you say yes here you get support for the TPS6586X series of
180 Power Management chips.
181 This driver provides common support for accessing the device,
182 additional drivers must be enabled in order to use the
183 functionality of the device.
185 This driver can also be built as a module. If so, the module
186 will be called tps6586x.
189 bool "TPS65910 Power Management chip"
190 depends on I2C=y && GPIOLIB
194 if you say yes here you get support for the TPS65910 series of
195 Power Management chips.
201 config MFD_TPS65912_I2C
202 bool "TPS65912 Power Management chip with I2C"
205 depends on I2C=y && GPIOLIB
207 If you say yes here you get support for the TPS65912 series of
208 PM chips with I2C interface.
210 config MFD_TPS65912_SPI
211 bool "TPS65912 Power Management chip with SPI"
214 depends on SPI_MASTER && GPIOLIB
216 If you say yes here you get support for the TPS65912 series of
217 PM chips with SPI interface.
220 bool "Texas Instruments TWL92330/Menelaus PM chip"
221 depends on I2C=y && ARCH_OMAP2
223 If you say yes here you get support for the Texas Instruments
224 TWL92330/Menelaus Power Management chip. This include voltage
225 regulators, Dual slot memory card transceivers, real-time clock
226 and other features that are often used in portable devices like
227 cell phones and PDAs.
230 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
231 depends on I2C=y && GENERIC_HARDIRQS
234 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
235 This core driver provides register access and IRQ handling
236 facilities, and registers devices for the various functions
237 so that function-specific drivers can bind to them.
239 These multi-function chips are found on many OMAP2 and OMAP3
240 boards, providing power management, RTC, GPIO, keypad, a
241 high speed USB OTG transceiver, an audio codec (on most
242 versions) and many other features.
245 tristate "Texas Instruments TWL4030 MADC"
246 depends on TWL4030_CORE
248 This driver provides support for triton TWL4030-MADC. The
249 driver supports both RT and SW conversion methods.
251 This driver can be built as a module. If so it will be
255 bool "Support power resources on TWL4030 family chips"
256 depends on TWL4030_CORE && ARM
258 Say yes here if you want to use the power resources on the
259 TWL4030 family chips. Most of these resources are regulators,
260 which have a separate driver; some are control signals, such
261 as clock request handshaking.
263 This driver uses board-specific data to initialize the resources
264 and load scripts controlling which resources are switched off/on
265 or reset when a sleep, wakeup or warm reset event occurs.
267 config MFD_TWL4030_AUDIO
269 depends on TWL4030_CORE
274 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
275 depends on TWL4030_CORE
279 Say yes here if you want support for TWL6030 PWM.
280 This is used to control charging LED brightness.
283 bool "Support for TWL6040 audio codec"
284 depends on I2C=y && GENERIC_HARDIRQS
289 Say yes here if you want support for Texas Instruments TWL6040 audio
291 This driver provides common support for accessing the device,
292 additional drivers must be enabled in order to use the
293 functionality of the device (audio, vibra).
296 bool "Support STMicroelectronics STMPE"
297 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
300 Support for the STMPE family of I/O Expanders from
303 Currently supported devices are:
305 STMPE811: GPIO, Touchscreen
306 STMPE1601: GPIO, Keypad
307 STMPE2401: GPIO, Keypad
308 STMPE2403: GPIO, Keypad
310 This driver provides common support for accessing the device,
311 additional drivers must be enabled in order to use the functionality
312 of the device. Currently available sub drivers are:
316 Touchscreen: stmpe-ts
318 menu "STMPE Interface Drivers"
322 bool "STMPE I2C Inteface"
326 This is used to enable I2C interface of STMPE
329 bool "STMPE SPI Inteface"
330 depends on SPI_MASTER
332 This is used to enable SPI interface of STMPE
336 bool "Support Toshiba TC35892 and variants"
337 depends on I2C=y && GENERIC_HARDIRQS
340 Support for the Toshiba TC35892 and variants I/O Expander.
342 This driver provides common support for accessing the device,
343 additional drivers must be enabled in order to use the
344 functionality of the device.
351 bool "Support Toshiba T7L66XB"
352 depends on ARM && HAVE_CLK
356 Support for Toshiba Mobile IO Controller T7L66XB
359 bool "Support Toshiba TC6387XB"
360 depends on ARM && HAVE_CLK
364 Support for Toshiba Mobile IO Controller TC6387XB
367 bool "Support Toshiba TC6393XB"
368 depends on GPIOLIB && ARM && HAVE_CLK
372 Support for Toshiba Mobile IO Controller TC6393XB
375 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
378 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
379 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
380 usually found on PXA processors-based platforms. This includes
381 the I2C driver and the core APIs _only_, you have to select
382 individual components like LCD backlight, voltage regulators,
383 LEDs and battery-charger under the corresponding menus.
389 config MFD_DA9052_SPI
390 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
394 depends on SPI_MASTER=y
396 Support for the Dialog Semiconductor DA9052 PMIC
397 when controlled using SPI. 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_DA9052_I2C
402 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
408 Support for the Dialog Semiconductor DA9052 PMIC
409 when controlled using I2C. 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.
414 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
417 Say yes here to add support for Analog Devices AD5520 and ADP5501,
418 Multifunction Power Management IC. This includes
419 the I2C driver and the core APIs _only_, you have to select
420 individual components like LCD backlight, LEDs, GPIOs and Kepad
421 under the corresponding menus.
424 bool "Maxim Semiconductor MAX8925 PMIC Support"
425 depends on I2C=y && GENERIC_HARDIRQS
428 Say yes here to support for Maxim Semiconductor MAX8925. This is
429 a Power Management IC. This driver provies common support for
430 accessing the device, additional drivers must be enabled in order
431 to use the functionality of the device.
434 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
435 depends on I2C=y && GENERIC_HARDIRQS
438 Say yes here to support for Maxim Semiconductor MAX8997/8966.
439 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
440 MUIC controls on chip.
441 This driver provides common support for accessing the device;
442 additional drivers must be enabled in order to use the functionality
446 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
447 depends on I2C=y && GENERIC_HARDIRQS
450 Say yes here to support for Maxim Semiconductor MAX8998 and
451 National Semiconductor LP3974. This is a Power Management IC.
452 This driver provies common support for accessing the device,
453 additional drivers must be enabled in order to use the functionality
457 bool "SAMSUNG S5M Series Support"
458 depends on I2C=y && GENERIC_HARDIRQS
462 Support for the Samsung Electronics S5M MFD series.
463 This driver provies common support for accessing the device,
464 additional drivers must be enabled in order to use the functionality
468 tristate "Support Wolfson Microelectronics WM8400"
473 Support for the Wolfson Microelecronics WM8400 PMIC and audio
474 CODEC. This driver provides common support for accessing
475 the device, additional drivers must be enabled in order to use
476 the functionality of the device.
480 depends on GENERIC_HARDIRQS
482 config MFD_WM831X_I2C
483 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
487 depends on I2C=y && GENERIC_HARDIRQS
489 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
490 when controlled using I2C. This driver provides common support
491 for accessing the device, additional drivers must be enabled in
492 order to use the functionality of the device.
494 config MFD_WM831X_SPI
495 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
499 depends on SPI_MASTER && GENERIC_HARDIRQS
501 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
502 when controlled using SPI. This driver provides common support
503 for accessing the device, additional drivers must be enabled in
504 order to use the functionality of the device.
508 depends on GENERIC_HARDIRQS
510 config MFD_WM8350_CONFIG_MODE_0
512 depends on MFD_WM8350
514 config MFD_WM8350_CONFIG_MODE_1
516 depends on MFD_WM8350
518 config MFD_WM8350_CONFIG_MODE_2
520 depends on MFD_WM8350
522 config MFD_WM8350_CONFIG_MODE_3
524 depends on MFD_WM8350
526 config MFD_WM8351_CONFIG_MODE_0
528 depends on MFD_WM8350
530 config MFD_WM8351_CONFIG_MODE_1
532 depends on MFD_WM8350
534 config MFD_WM8351_CONFIG_MODE_2
536 depends on MFD_WM8350
538 config MFD_WM8351_CONFIG_MODE_3
540 depends on MFD_WM8350
542 config MFD_WM8352_CONFIG_MODE_0
544 depends on MFD_WM8350
546 config MFD_WM8352_CONFIG_MODE_1
548 depends on MFD_WM8350
550 config MFD_WM8352_CONFIG_MODE_2
552 depends on MFD_WM8350
554 config MFD_WM8352_CONFIG_MODE_3
556 depends on MFD_WM8350
558 config MFD_WM8350_I2C
559 bool "Support Wolfson Microelectronics WM8350 with I2C"
561 depends on I2C=y && GENERIC_HARDIRQS
563 The WM8350 is an integrated audio and power management
564 subsystem with watchdog and RTC functionality for embedded
565 systems. This option enables core support for the WM8350 with
566 I2C as the control interface. Additional options must be
567 selected to enable support for the functionality of the chip.
570 bool "Support Wolfson Microelectronics WM8994"
574 depends on I2C=y && GENERIC_HARDIRQS
576 The WM8994 is a highly integrated hi-fi CODEC designed for
577 smartphone applicatiosn. As well as audio functionality it
578 has on board GPIO and regulator functionality which is
579 supported via the relevant subsystems. This driver provides
580 core support for the WM8994, in order to use the actual
581 functionaltiy of the device other drivers must be enabled.
584 tristate "Support for NXP PCF50633"
588 Say yes here if you have NXP PCF50633 chip on your board.
589 This core driver provides register access and IRQ handling
590 facilities, and registers devices for the various functions
591 so that function-specific drivers can bind to them.
594 tristate "Support for NXP PCF50633 ADC"
595 depends on MFD_PCF50633
597 Say yes here if you want to include support for ADC in the
601 tristate "Support for NXP PCF50633 GPIO"
602 depends on MFD_PCF50633
604 Say yes here if you want to include support GPIO for pins on
611 tristate "Support Freescale MC13783 and MC13892"
612 depends on SPI_MASTER || I2C
616 Enable support for the Freescale MC13783 and MC13892 PMICs.
617 This driver provides common support for accessing the device,
618 additional drivers must be enabled in order to use the
619 functionality of the device.
623 config MFD_MC13XXX_SPI
624 tristate "MC13xxx SPI interface" if SPI_MASTER
628 Select this if your MC13xxx is connected via an SPI bus.
630 config MFD_MC13XXX_I2C
631 tristate "MC13xxx I2C interface" if I2C
635 Select this if your MC13xxx is connected via an I2C bus.
640 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
641 default y if ARCH_U300 || ARCH_U8500
643 Say yes here if you have the ABX500 Mixed Signal IC family
644 chips. This core driver expose register access functions.
645 Functionality specific drivers using these functions can
646 remain unchanged when IC changes. Binding of the functions to
647 actual register access is done by the IC core driver.
650 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
651 depends on I2C=y && ABX500_CORE
653 default y if ARCH_U300
655 Select this to enable the AB3100 Mixed Signal IC core
656 functionality. This connects to a AB3100 on the I2C bus
657 and expose a number of symbols needed for dependent devices
658 to read and write registers and subscribe to events from
659 this multi-functional IC. This is needed to use other features
660 of the AB3100 such as battery-backed RTC, charging control,
661 LEDs, vibrator, system power and temperature, power management
665 tristate "ST-Ericsson AB3100 OTP functions"
666 depends on AB3100_CORE
667 default y if AB3100_CORE
669 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
670 programmable memory) support. This exposes a sysfs file to read
675 depends on GENERIC_HARDIRQS && SPI_MASTER
677 This enables the PCAP ASIC present on EZX Phones. This is
678 needed for MMC, TouchScreen, Sound, USB, etc..
681 bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
682 depends on ABX500_CORE && MFD_DB5500_PRCMU
685 Select this option to enable access to AB5500 power management
686 chip. This connects to the db5500 chip via the I2C bus via PRCMU.
687 This chip embeds various other multimedia funtionalities as well.
690 bool "Enable debug info via debugfs"
691 depends on AB5500_CORE && DEBUG_FS
692 default y if DEBUG_FS
694 Select this option if you want debug information from the AB5500
695 using the debug filesystem, debugfs.
698 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
699 depends on GENERIC_HARDIRQS && ABX500_CORE
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.
743 config MFD_DB5500_PRCMU
744 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
745 depends on UX500_SOC_DB5500
748 Select this option to enable support for the DB5500 Power Reset
749 and Control Management Unit. This is basically an autonomous
750 system controller running an XP70 microprocessor, which is accessed
751 through a register map.
754 tristate "Support for CS5535 and CS5536 southbridge core functions"
756 depends on PCI && X86
758 This is the core driver for CS5535/CS5536 MFD functions. This is
759 necessary for using the board's GPIO and MFGPT functionality.
761 config MFD_TIMBERDALE
762 tristate "Support for the Timberdale FPGA"
764 depends on PCI && GPIOLIB
766 This is the core driver for the timberdale FPGA. This device is a
767 multifunction device which exposes numerous platform devices.
769 The timberdale FPGA can be found on the Intel Atom development board
770 for in-vehicle infontainment, called Russellville.
773 tristate "Intel SCH LPC"
777 LPC bridge function of the Intel SCH provides support for
778 System Management Bus and General Purpose I/O.
781 tristate "Intel ICH LPC"
785 The LPC bridge function of the Intel ICH provides support for
786 many functional units. This driver provides needed support for
787 other drivers to control these functions, currently GPIO and
791 tristate "Support for RDC-R321x southbridge"
795 Say yes here if you want to have support for the RDC R-321x SoC
796 southbridge which provides access to GPIOs and Watchdog using the
797 southbridge PCI device configuration space.
799 config MFD_JANZ_CMODIO
800 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
804 This is the core driver for the Janz CMOD-IO PCI MODULbus
805 carrier board. This device is a PCI to MODULbus bridge which may
806 host many different types of MODULbus daughterboards, including
807 CAN and GPIO controllers.
809 config MFD_JZ4740_ADC
810 bool "Support for the JZ4740 SoC ADC core"
812 select GENERIC_IRQ_CHIP
813 depends on MACH_JZ4740
815 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
816 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
819 tristate "Support for VIA VX855/VX875 integrated south bridge"
823 Say yes here to enable support for various functions of the
824 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
825 and/or vx855_gpio drivers for this to do anything useful.
827 config MFD_WL1273_CORE
828 tristate "Support for TI WL1273 FM radio."
833 This is the core driver for the TI WL1273 FM radio. This MFD
834 driver connects the radio-wl1273 V4L2 module and the wl1273
837 config MFD_OMAP_USB_HOST
838 bool "Support OMAP USBHS core driver"
839 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
842 This is the core driver for the OAMP EHCI and OHCI drivers.
843 This MFD driver does the required setup functionalities for
844 OMAP USB Host drivers.
849 config MFD_PM8921_CORE
850 tristate "Qualcomm PM8921 PMIC chip"
855 If you say yes to this option, support will be included for the
856 built-in PM8921 PMIC chip.
858 This is required if your board has a PM8921 and uses its features,
859 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
861 Say M here if you want to include support for PM8921 chip as a module.
862 This will build a module called "pm8921-core".
864 config MFD_PM8XXX_IRQ
865 bool "Support for Qualcomm PM8xxx IRQ features"
866 depends on MFD_PM8XXX
867 default y if MFD_PM8XXX
869 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
871 This is required to use certain other PM 8xxx features, such as GPIO
874 config TPS65911_COMPARATOR
878 bool "TPS65090 Power Management chips"
879 depends on I2C=y && GENERIC_HARDIRQS
883 If you say yes here you get support for the TPS65090 series of
884 Power Management chips.
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_AAT2870_CORE
890 bool "Support for the AnalogicTech AAT2870"
892 depends on I2C=y && GPIOLIB
894 If you say yes here you get support for the AAT2870.
895 This driver provides common support for accessing the device,
896 additional drivers must be enabled in order to use the
897 functionality of the device.
899 config MFD_INTEL_MSIC
900 bool "Support for Intel MSIC"
901 depends on INTEL_SCU_IPC
904 Select this option to enable access to Intel MSIC (Avatele
905 Passage) chip. This chip embeds audio, battery, GPIO, etc.
906 devices used in Intel Medfield platforms.
909 bool "Ricoh RC5T583 Power Management system device"
910 depends on I2C=y && GENERIC_HARDIRQS
914 Select this option to get support for the RICOH583 Power
915 Management system device.
916 This driver provides common support for accessing the device
917 through i2c interface. The device supports multiple sub-devices
918 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
919 Additional drivers must be enabled in order to use the
920 different functionality of the device.
923 bool "STA2X11 multi function device support"
928 bool "Support for Freescale i.MX on-chip ANATOP controller"
931 Select this option to enable Freescale i.MX on-chip ANATOP
932 MFD controller. This controller embeds regulator and
933 thermal devices for Freescale i.MX platforms.
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