Gitiles
Code Review Sign In
gerrit-public.fairphone.software / kernel / msm-4.19 / df3df6469fd1e59284d6b5d4dd9dbe1bd7861040 / . / drivers / mfd / Kconfig
blob: ef86a741b7e271bcb6b131a74e843f40e15d44a7 [file] [log] [blame]
Russell Kinga4e137a2005-08-18 10:06:59 +0100[diff] [blame]1#
2# Multifunction miscellaneous devices
3#
4
Arnd Bergmann8a0a8e82011-09-02 16:43:36 +0200[diff] [blame]5if HAS_IOMEM
6menu "Multifunction device drivers"
Ben Dooksb6d64542007-02-20 13:58:01 -0800[diff] [blame]7
Dmitry Baryshkovaa613de2008-06-27 10:37:19 +0100[diff] [blame]8config MFD_CORE
9 tristate
10 default n
11
Haojian Zhuang2cc50be2010-01-06 17:07:13 -0500[diff] [blame]12config MFD_88PM860X
13 bool "Support Marvell 88PM8606/88PM8607"
Geert Uytterhoeven8d002bd2009-12-15 21:49:57 +0100[diff] [blame]14 depends on I2C=y && GENERIC_HARDIRQS
Jett.Zhoub46a36c2011-11-11 15:38:27 +0800[diff] [blame]15 select REGMAP_I2C
Haojian Zhuang2cc50be2010-01-06 17:07:13 -0500[diff] [blame]16 select MFD_CORE
17 help
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.
22
Ben Dooksb6d64542007-02-20 13:58:01 -0800[diff] [blame]23config MFD_SM501
24 tristate "Support for Silicon Motion SM501"
25 ---help---
26 This is the core driver for the Silicon Motion SM501 multimedia
27 companion chip. This device is a multifunction device which may
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200[diff] [blame]28 provide numerous interfaces including USB host controller, USB gadget,
29 asynchronous serial ports, audio functions, and a dual display video
Ben Dooksb6d64542007-02-20 13:58:01 -0800[diff] [blame]30 interface. The device may be connected by PCI or local bus with
31 varying functions enabled.
32
Ben Dooksf61be272008-07-25 01:45:59 -0700[diff] [blame]33config MFD_SM501_GPIO
34 bool "Export GPIO via GPIO layer"
Samuel Ortiz2eedd602008-09-25 00:39:05 +0200[diff] [blame]35 depends on MFD_SM501 && GPIOLIB
Ben Dooksf61be272008-07-25 01:45:59 -0700[diff] [blame]36 ---help---
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.
40
Samuel Ortizfa9ff4b2008-02-07 00:14:49 -0800[diff] [blame]41config MFD_ASIC3
42 bool "Support for Compaq ASIC3"
Samuel Ortiz2eedd602008-09-25 00:39:05 +0200[diff] [blame]43 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
Philipp Zabel9461f652009-06-15 12:10:24 +0200[diff] [blame]44 select MFD_CORE
Samuel Ortizfa9ff4b2008-02-07 00:14:49 -0800[diff] [blame]45 ---help---
46 This driver supports the ASIC3 multifunction chip found on many
47 PDAs (mainly iPAQ and HTC based ones)
48
Miguel Aguilarca263082010-03-11 09:32:21 -0600[diff] [blame]49config MFD_DAVINCI_VOICECODEC
50 tristate
51 select MFD_CORE
52
David Brownell0931a4c2008-12-22 12:05:27 +0100[diff] [blame]53config MFD_DM355EVM_MSP
54 bool "DaVinci DM355 EVM microcontroller"
Samuel Ortiz1819ebc2010-09-20 00:19:27 +0200[diff] [blame]55 depends on I2C=y && MACH_DAVINCI_DM355_EVM
David Brownell0931a4c2008-12-22 12:05:27 +0100[diff] [blame]56 help
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.
60
Cyril Chemparathy03df0f62011-01-18 19:21:35 +0000[diff] [blame]61config MFD_TI_SSP
62 tristate "TI Sequencer Serial Port support"
63 depends on ARCH_DAVINCI_TNETV107X
64 select MFD_CORE
65 ---help---
66 Say Y here if you want support for the Sequencer Serial Port
67 in a Texas Instruments TNETV107X SoC.
68
69 To compile this driver as a module, choose M here: the
70 module will be called ti-ssp.
71
Philipp Zabela1635b82008-04-09 19:20:34 +0100[diff] [blame]72config HTC_EGPIO
73 bool "HTC EGPIO support"
Michael Buesch7444a722008-07-25 01:46:11 -0700[diff] [blame]74 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
Philipp Zabela1635b82008-04-09 19:20:34 +0100[diff] [blame]75 help
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.
79
Philipp Zabel5dc33392008-04-12 13:25:41 +0100[diff] [blame]80config HTC_PASIC3
81 tristate "HTC PASIC3 LED/DS1WM chip support"
Philipp Zabel0254a8f2009-02-17 10:06:45 +0100[diff] [blame]82 select MFD_CORE
Philipp Zabel5dc33392008-04-12 13:25:41 +0100[diff] [blame]83 help
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.
88
Cory Maccarrone6048a3d2010-01-19 11:22:45 +0100[diff] [blame]89config HTC_I2CPLD
90 bool "HTC I2C PLD chip support"
Randy Dunlapbef3e202010-01-20 19:55:34 -0800[diff] [blame]91 depends on I2C=y && GPIOLIB
Cory Maccarrone6048a3d2010-01-19 11:22:45 +0100[diff] [blame]92 help
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.
97
Marek Vašutd9105c22008-08-03 21:34:08 +0100[diff] [blame]98config UCB1400_CORE
99 tristate "Philips UCB1400 Core driver"
Randy Dunlape4831802008-10-15 13:29:07 +0200[diff] [blame]100 depends on AC97_BUS
Andrew Morton5a49a542008-10-15 13:30:47 +0200[diff] [blame]101 depends on GPIOLIB
Marek Vašutd9105c22008-08-03 21:34:08 +0100[diff] [blame]102 help
103 This enables support for the Philips UCB1400 core functions.
104 The UCB1400 is an AC97 audio codec.
105
106 To compile this driver as a module, choose M here: the
107 module will be called ucb1400_core.
108
Linus Walleij798a8ee2011-03-09 13:02:38 +0100[diff] [blame]109config TPS6105X
110 tristate "TPS61050/61052 Boost Converters"
111 depends on I2C
Linus Walleij2edd3b62011-03-09 12:02:55 +0000[diff] [blame]112 select REGULATOR
Guenter Roeckfc498fa2011-03-24 12:12:47 -0700[diff] [blame]113 select MFD_CORE
Linus Walleij2edd3b62011-03-09 12:02:55 +0000[diff] [blame]114 select REGULATOR_FIXED_VOLTAGE
Linus Walleij798a8ee2011-03-09 13:02:38 +0100[diff] [blame]115 help
116 This option enables a driver for the TP61050/TPS61052
117 high-power "white LED driver". This boost converter is
118 sometimes used for other things than white LEDs, and
119 also contains a GPIO pin.
120
David Brownell87c13492008-12-22 12:16:27 +0100[diff] [blame]121config TPS65010
122 tristate "TPS6501x Power Management chips"
123 depends on I2C && GPIOLIB
124 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
125 help
126 If you say yes here you get support for the TPS6501x series of
127 Power Management chips. These include voltage regulators,
128 lithium ion/polymer battery charging, and other features that
129 are often used in portable devices like cell phones and cameras.
130
131 This driver can also be built as a module. If so, the module
132 will be called tps65010.
133
Todd Fischer31dd6a22010-04-08 09:04:55 +0200[diff] [blame]134config TPS6507X
135 tristate "TPS6507x Power Management / Touch Screen chips"
136 select MFD_CORE
137 depends on I2C
138 help
139 If you say yes here you get support for the TPS6507x series of
140 Power Management / Touch Screen chips. These include voltage
141 regulators, lithium ion/polymer battery charging, touch screen
142 and other features that are often used in portable devices.
143 This driver can also be built as a module. If so, the module
144 will be called tps6507x.
145
AnilKumar Chd48f4112012-01-11 16:11:41 +0530[diff] [blame]146config MFD_TPS65217
147 tristate "TPS65217 Power Management / White LED chips"
148 depends on I2C
149 select MFD_CORE
150 select REGMAP_I2C
151 help
152 If you say yes here you get support for the TPS65217 series of
153 Power Management / White LED chips.
154 These include voltage regulators, lithium ion/polymer battery
155 charger, wled and other features that are often used in portable
156 devices.
157
158 This driver can also be built as a module. If so, the module
159 will be called tps65217.
160
Axel Lin37df0032011-04-15 20:04:45 +0800[diff] [blame]161config MFD_TPS6586X
162 bool "TPS6586x Power Management chips"
163 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
164 select MFD_CORE
165 help
166 If you say yes here you get support for the TPS6586X series of
167 Power Management chips.
168 This driver provides common support for accessing the device,
169 additional drivers must be enabled in order to use the
170 functionality of the device.
171
172 This driver can also be built as a module. If so, the module
173 will be called tps6586x.
174
Linus Walleij54f323b2011-07-04 17:34:16 +0200[diff] [blame]175config MFD_TPS65910
176 bool "TPS65910 Power Management chip"
177 depends on I2C=y && GPIOLIB
178 select MFD_CORE
179 select GPIO_TPS65910
Laxman Dewangandc9913a2012-02-21 18:21:34 +0530[diff] [blame]180 select REGMAP_I2C
Linus Walleij54f323b2011-07-04 17:34:16 +0200[diff] [blame]181 help
182 if you say yes here you get support for the TPS65910 series of
183 Power Management chips.
184
Margarita Olaya36e52872011-06-09 14:50:00 -0500[diff] [blame]185config MFD_TPS65912
Mark Brown56088012011-06-22 14:53:58 +0100[diff] [blame]186 bool
Margarita Olaya36e52872011-06-09 14:50:00 -0500[diff] [blame]187 depends on GPIOLIB
188
189config MFD_TPS65912_I2C
Axel Lin231dd9c2012-02-15 16:05:24 +0800[diff] [blame]190 bool "TPS65912 Power Management chip with I2C"
Margarita Olaya36e52872011-06-09 14:50:00 -0500[diff] [blame]191 select MFD_CORE
192 select MFD_TPS65912
193 depends on I2C=y && GPIOLIB
194 help
195 If you say yes here you get support for the TPS65912 series of
196 PM chips with I2C interface.
197
198config MFD_TPS65912_SPI
199 bool "TPS65912 Power Management chip with SPI"
200 select MFD_CORE
201 select MFD_TPS65912
202 depends on SPI_MASTER && GPIOLIB
203 help
204 If you say yes here you get support for the TPS65912 series of
205 PM chips with SPI interface.
206
David Brownell88e75cc2008-12-22 12:18:02 +0100[diff] [blame]207config MENELAUS
208 bool "Texas Instruments TWL92330/Menelaus PM chip"
Tony Lindgren088ef952010-02-12 12:26:47 -0800[diff] [blame]209 depends on I2C=y && ARCH_OMAP2
David Brownell88e75cc2008-12-22 12:18:02 +0100[diff] [blame]210 help
211 If you say yes here you get support for the Texas Instruments
212 TWL92330/Menelaus Power Management chip. This include voltage
Matt LaPlante692105b2009-01-26 11:12:25 +0100[diff] [blame]213 regulators, Dual slot memory card transceivers, real-time clock
David Brownell88e75cc2008-12-22 12:18:02 +0100[diff] [blame]214 and other features that are often used in portable devices like
215 cell phones and PDAs.
216
David Brownella603a7f2008-10-15 12:15:39 +0200[diff] [blame]217config TWL4030_CORE
Balaji T Ke8deb282009-12-14 00:25:31 +0100[diff] [blame]218 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
Russell King62525472012-02-07 09:47:21 +0000[diff] [blame]219 depends on I2C=y && GENERIC_HARDIRQS
Grant Likely280ad7f2012-02-24 14:58:54 -0700[diff] [blame]220 select IRQ_DOMAIN
David Brownella603a7f2008-10-15 12:15:39 +0200[diff] [blame]221 help
Balaji T Ke8deb282009-12-14 00:25:31 +0100[diff] [blame]222 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
David Brownella603a7f2008-10-15 12:15:39 +0200[diff] [blame]223 This core driver provides register access and IRQ handling
224 facilities, and registers devices for the various functions
225 so that function-specific drivers can bind to them.
226
227 These multi-function chips are found on many OMAP2 and OMAP3
228 boards, providing power management, RTC, GPIO, keypad, a
229 high speed USB OTG transceiver, an audio codec (on most
230 versions) and many other features.
231
Keerthyf99c1d42011-03-01 19:12:26 +0530[diff] [blame]232config TWL4030_MADC
233 tristate "Texas Instruments TWL4030 MADC"
234 depends on TWL4030_CORE
235 help
236 This driver provides support for triton TWL4030-MADC. The
237 driver supports both RT and SW conversion methods.
238
239 This driver can be built as a module. If so it will be
240 named twl4030-madc
241
Amit Kucheriaebf0bd32009-08-31 18:32:18 +0200[diff] [blame]242config TWL4030_POWER
243 bool "Support power resources on TWL4030 family chips"
244 depends on TWL4030_CORE && ARM
245 help
246 Say yes here if you want to use the power resources on the
247 TWL4030 family chips. Most of these resources are regulators,
248 which have a separate driver; some are control signals, such
249 as clock request handshaking.
250
251 This driver uses board-specific data to initialize the resources
Lucas De Marchi25985ed2011-03-30 22:57:33 -0300[diff] [blame]252 and load scripts controlling which resources are switched off/on
Amit Kucheriaebf0bd32009-08-31 18:32:18 +0200[diff] [blame]253 or reset when a sleep, wakeup or warm reset event occurs.
254
Peter Ujfalusi57fe7252011-05-31 12:02:49 +0300[diff] [blame]255config MFD_TWL4030_AUDIO
Peter Ujfalusi0b83dde2009-10-22 13:26:45 +0300[diff] [blame]256 bool
257 depends on TWL4030_CORE
258 select MFD_CORE
259 default n
260
Hemanth V31fc03d2010-07-14 12:04:56 +0200[diff] [blame]261config TWL6030_PWM
262 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
263 depends on TWL4030_CORE
264 select HAVE_PWM
265 default n
266 help
267 Say yes here if you want support for TWL6030 PWM.
268 This is used to control charging LED brightness.
269
Misael Lopez Cruzf19b2822011-04-27 02:14:07 -0500[diff] [blame]270config TWL6040_CORE
Peter Ujfalusi8eaeb932012-04-03 11:56:51 +0300[diff] [blame]271 bool "Support for TWL6040 audio codec"
272 depends on I2C=y && GENERIC_HARDIRQS
Misael Lopez Cruzf19b2822011-04-27 02:14:07 -0500[diff] [blame]273 select MFD_CORE
Peter Ujfalusi8eaeb932012-04-03 11:56:51 +0300[diff] [blame]274 select REGMAP_I2C
Misael Lopez Cruzf19b2822011-04-27 02:14:07 -0500[diff] [blame]275 default n
Peter Ujfalusi8eaeb932012-04-03 11:56:51 +0300[diff] [blame]276 help
277 Say yes here if you want support for Texas Instruments TWL6040 audio
278 codec.
279 This driver provides common support for accessing the device,
280 additional drivers must be enabled in order to use the
281 functionality of the device (audio, vibra).
Misael Lopez Cruzf19b2822011-04-27 02:14:07 -0500[diff] [blame]282
Rabin Vincent27e34992010-07-02 16:52:08 +0530[diff] [blame]283config MFD_STMPE
284 bool "Support STMicroelectronics STMPE"
Viresh Kumare7899952011-11-17 11:02:21 +0530[diff] [blame]285 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
Rabin Vincent27e34992010-07-02 16:52:08 +0530[diff] [blame]286 select MFD_CORE
287 help
288 Support for the STMPE family of I/O Expanders from
289 STMicroelectronics.
290
291 Currently supported devices are:
292
293 STMPE811: GPIO, Touchscreen
294 STMPE1601: GPIO, Keypad
295 STMPE2401: GPIO, Keypad
296 STMPE2403: GPIO, Keypad
297
298 This driver provides common support for accessing the device,
299 additional drivers must be enabled in order to use the functionality
300 of the device. Currently available sub drivers are:
301
302 GPIO: stmpe-gpio
303 Keypad: stmpe-keypad
304 Touchscreen: stmpe-ts
305
Viresh Kumar1a6e4b72011-11-17 11:02:20 +0530[diff] [blame]306menu "STMPE Interface Drivers"
307depends on MFD_STMPE
308
309config STMPE_I2C
310 bool "STMPE I2C Inteface"
Samuel Ortizeedea802011-12-20 18:28:19 +0100[diff] [blame]311 depends on I2C=y
Viresh Kumar1a6e4b72011-11-17 11:02:20 +0530[diff] [blame]312 default y
313 help
314 This is used to enable I2C interface of STMPE
Viresh Kumare7899952011-11-17 11:02:21 +0530[diff] [blame]315
316config STMPE_SPI
317 bool "STMPE SPI Inteface"
318 depends on SPI_MASTER
319 help
320 This is used to enable SPI interface of STMPE
Viresh Kumar1a6e4b72011-11-17 11:02:20 +0530[diff] [blame]321endmenu
322
Sundar Iyerf4e8afd2010-12-13 09:33:13 +0530[diff] [blame]323config MFD_TC3589X
324 bool "Support Toshiba TC35892 and variants"
Rabin Vincentb4ecd322010-05-10 23:39:47 +0200[diff] [blame]325 depends on I2C=y && GENERIC_HARDIRQS
326 select MFD_CORE
327 help
Sundar Iyerf4e8afd2010-12-13 09:33:13 +0530[diff] [blame]328 Support for the Toshiba TC35892 and variants I/O Expander.
Rabin Vincentb4ecd322010-05-10 23:39:47 +0200[diff] [blame]329
330 This driver provides common support for accessing the device,
331 additional drivers must be enabled in order to use the
332 functionality of the device.
333
Samuel Ortiz1c2c30a2008-08-05 19:27:58 +0200[diff] [blame]334config MFD_TMIO
335 bool
336 default n
337
Ian Molton1f192012008-07-15 15:09:43 +0100[diff] [blame]338config MFD_T7L66XB
339 bool "Support Toshiba T7L66XB"
Al Viro9ca68232008-11-01 18:19:59 +0000[diff] [blame]340 depends on ARM && HAVE_CLK
Ian Molton1f192012008-07-15 15:09:43 +0100[diff] [blame]341 select MFD_CORE
Samuel Ortiz1c2c30a2008-08-05 19:27:58 +0200[diff] [blame]342 select MFD_TMIO
Ian Molton1f192012008-07-15 15:09:43 +0100[diff] [blame]343 help
344 Support for Toshiba Mobile IO Controller T7L66XB
345
Ian Moltoncbdfb422008-07-15 15:12:52 +0100[diff] [blame]346config MFD_TC6387XB
347 bool "Support Toshiba TC6387XB"
Al Viro9ca68232008-11-01 18:19:59 +0000[diff] [blame]348 depends on ARM && HAVE_CLK
Ian Moltoncbdfb422008-07-15 15:12:52 +0100[diff] [blame]349 select MFD_CORE
Samuel Ortiz1c2c30a2008-08-05 19:27:58 +0200[diff] [blame]350 select MFD_TMIO
Ian Moltoncbdfb422008-07-15 15:12:52 +0100[diff] [blame]351 help
352 Support for Toshiba Mobile IO Controller TC6387XB
353
Dmitry Baryshkovd6315942008-06-22 12:01:58 +0100[diff] [blame]354config MFD_TC6393XB
355 bool "Support Toshiba TC6393XB"
Christoph Fritze959da12011-11-29 19:38:38 +0100[diff] [blame]356 depends on GPIOLIB && ARM && HAVE_CLK
Dmitry Baryshkovf024ff12008-06-27 10:37:57 +0100[diff] [blame]357 select MFD_CORE
Samuel Ortiz1c2c30a2008-08-05 19:27:58 +0200[diff] [blame]358 select MFD_TMIO
Dmitry Baryshkovd6315942008-06-22 12:01:58 +0100[diff] [blame]359 help
360 Support for Toshiba Mobile IO Controller TC6393XB
361
Samuel Ortiz8e2eaab2008-10-24 17:10:05 +0200[diff] [blame]362config PMIC_DA903X
363 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
364 depends on I2C=y
365 help
366 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
367 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
368 usually found on PXA processors-based platforms. This includes
369 the I2C driver and the core APIs _only_, you have to select
370 individual components like LCD backlight, voltage regulators,
371 LEDs and battery-charger under the corresponding menus.
372
Ashish Jangam84c99db2011-12-12 20:06:56 +0530[diff] [blame]373config PMIC_DA9052
374 bool
375 select MFD_CORE
376
Ashish Jangamcfe04472011-12-12 20:37:41 +0530[diff] [blame]377config MFD_DA9052_SPI
378 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
379 select REGMAP_SPI
380 select REGMAP_IRQ
381 select PMIC_DA9052
382 depends on SPI_MASTER=y
383 help
384 Support for the Dialog Semiconductor DA9052 PMIC
385 when controlled using SPI. This driver provides common support
386 for accessing the device, additional drivers must be enabled in
387 order to use the functionality of the device.
388
Ashish Jangam84c99db2011-12-12 20:06:56 +0530[diff] [blame]389config MFD_DA9052_I2C
390 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
391 select REGMAP_I2C
392 select REGMAP_IRQ
393 select PMIC_DA9052
394 depends on I2C=y
395 help
396 Support for the Dialog Semiconductor DA9052 PMIC
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.
400
Michael Hennericha5736e02009-10-12 17:22:38 +0200[diff] [blame]401config PMIC_ADP5520
402 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
403 depends on I2C=y
404 help
405 Say yes here to add support for Analog Devices AD5520 and ADP5501,
406 Multifunction Power Management IC. This includes
407 the I2C driver and the core APIs _only_, you have to select
408 individual components like LCD backlight, LEDs, GPIOs and Kepad
409 under the corresponding menus.
410
Haojian Zhuangd50f8f32010-01-08 12:29:23 +0100[diff] [blame]411config MFD_MAX8925
Haojian Zhuang1f1cf8f2010-02-05 16:07:54 +0100[diff] [blame]412 bool "Maxim Semiconductor MAX8925 PMIC Support"
Geert Uytterhoeven8d002bd2009-12-15 21:49:57 +0100[diff] [blame]413 depends on I2C=y && GENERIC_HARDIRQS
Haojian Zhuang1ad99892010-01-08 12:43:29 -0500[diff] [blame]414 select MFD_CORE
Haojian Zhuangd50f8f32010-01-08 12:29:23 +0100[diff] [blame]415 help
416 Say yes here to support for Maxim Semiconductor MAX8925. This is
417 a Power Management IC. This driver provies common support for
418 accessing the device, additional drivers must be enabled in order
419 to use the functionality of the device.
420
MyungJoo Ham527e7e92011-03-04 15:50:26 +0900[diff] [blame]421config MFD_MAX8997
422 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
423 depends on I2C=y && GENERIC_HARDIRQS
424 select MFD_CORE
425 help
Axel Lin5a924d12012-03-01 09:31:25 +0800[diff] [blame]426 Say yes here to support for Maxim Semiconductor MAX8997/8966.
MyungJoo Ham527e7e92011-03-04 15:50:26 +0900[diff] [blame]427 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
428 MUIC controls on chip.
Randy Dunlapd7e8c012011-03-14 11:28:37 +0100[diff] [blame]429 This driver provides common support for accessing the device;
MyungJoo Ham527e7e92011-03-04 15:50:26 +0900[diff] [blame]430 additional drivers must be enabled in order to use the functionality
431 of the device.
432
Kyungmin Park156f2522010-06-16 09:04:16 +0200[diff] [blame]433config MFD_MAX8998
Kyungmin Parkf8539dd2010-08-23 13:46:49 +0900[diff] [blame]434 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
Joonyoung Shim2c7e6f52010-09-10 18:36:39 +0200[diff] [blame]435 depends on I2C=y && GENERIC_HARDIRQS
Kyungmin Park156f2522010-06-16 09:04:16 +0200[diff] [blame]436 select MFD_CORE
437 help
Kyungmin Parkf8539dd2010-08-23 13:46:49 +0900[diff] [blame]438 Say yes here to support for Maxim Semiconductor MAX8998 and
439 National Semiconductor LP3974. This is a Power Management IC.
440 This driver provies common support for accessing the device,
441 additional drivers must be enabled in order to use the functionality
442 of the device.
Kyungmin Park156f2522010-06-16 09:04:16 +0200[diff] [blame]443
Sangbeom Kimc3d4d692012-01-09 00:09:09 +0100[diff] [blame]444config MFD_S5M_CORE
445 bool "SAMSUNG S5M Series Support"
446 depends on I2C=y && GENERIC_HARDIRQS
447 select MFD_CORE
448 select REGMAP_I2C
449 help
450 Support for the Samsung Electronics S5M MFD series.
451 This driver provies common support for accessing the device,
452 additional drivers must be enabled in order to use the functionality
453 of the device
454
Mark Brown1d9f9f02008-09-10 18:58:42 +0100[diff] [blame]455config MFD_WM8400
456 tristate "Support Wolfson Microelectronics WM8400"
Mark Brownb8380c12008-12-18 10:54:22 +0100[diff] [blame]457 select MFD_CORE
Mark Brown9c366452008-10-24 17:16:11 +0200[diff] [blame]458 depends on I2C
Mark Brown2b247d02011-08-23 18:56:19 +0100[diff] [blame]459 select REGMAP_I2C
Mark Brown1d9f9f02008-09-10 18:58:42 +0100[diff] [blame]460 help
461 Support for the Wolfson Microelecronics WM8400 PMIC and audio
Mark Brown9e5aca52009-05-29 11:34:18 +0100[diff] [blame]462 CODEC. This driver provides common support for accessing
Mark Brown1d9f9f02008-09-10 18:58:42 +0100[diff] [blame]463 the device, additional drivers must be enabled in order to use
464 the functionality of the device.
465
Mark Brownb11062b2009-07-27 14:45:58 +0100[diff] [blame]466config MFD_WM831X
Mark Browne5b48682010-10-19 23:57:56 +0200[diff] [blame]467 bool
468 depends on GENERIC_HARDIRQS
469
470config MFD_WM831X_I2C
471 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
Mark Brownb11062b2009-07-27 14:45:58 +0100[diff] [blame]472 select MFD_CORE
Mark Browne5b48682010-10-19 23:57:56 +0200[diff] [blame]473 select MFD_WM831X
Mark Brown1df59812011-06-10 19:28:10 +0100[diff] [blame]474 select REGMAP_I2C
Geert Uytterhoeven8d002bd2009-12-15 21:49:57 +0100[diff] [blame]475 depends on I2C=y && GENERIC_HARDIRQS
Mark Brownb11062b2009-07-27 14:45:58 +0100[diff] [blame]476 help
Mark Browne5b48682010-10-19 23:57:56 +0200[diff] [blame]477 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
478 when controlled using I2C. This driver provides common support
479 for accessing the device, additional drivers must be enabled in
480 order to use the functionality of the device.
Mark Brownb11062b2009-07-27 14:45:58 +0100[diff] [blame]481
Mark Brown2aa13b92010-10-20 00:00:11 +0200[diff] [blame]482config MFD_WM831X_SPI
483 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
484 select MFD_CORE
485 select MFD_WM831X
Mark Brown1df59812011-06-10 19:28:10 +0100[diff] [blame]486 select REGMAP_SPI
Mark Brown2aa13b92010-10-20 00:00:11 +0200[diff] [blame]487 depends on SPI_MASTER && GENERIC_HARDIRQS
488 help
489 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
490 when controlled using SPI. 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.
493
Mark Brown89b40122008-10-10 15:58:10 +0100[diff] [blame]494config MFD_WM8350
Mark Brownecf926b2010-01-05 20:40:47 +0000[diff] [blame]495 bool
Geert Uytterhoeven8d002bd2009-12-15 21:49:57 +0100[diff] [blame]496 depends on GENERIC_HARDIRQS
Mark Brown89b40122008-10-10 15:58:10 +0100[diff] [blame]497
498config MFD_WM8350_CONFIG_MODE_0
499 bool
500 depends on MFD_WM8350
501
502config MFD_WM8350_CONFIG_MODE_1
503 bool
504 depends on MFD_WM8350
505
506config MFD_WM8350_CONFIG_MODE_2
507 bool
508 depends on MFD_WM8350
509
510config MFD_WM8350_CONFIG_MODE_3
511 bool
512 depends on MFD_WM8350
513
Mark Brownca23f8c2008-12-18 23:12:28 +0100[diff] [blame]514config MFD_WM8351_CONFIG_MODE_0
515 bool
516 depends on MFD_WM8350
517
518config MFD_WM8351_CONFIG_MODE_1
519 bool
520 depends on MFD_WM8350
521
522config MFD_WM8351_CONFIG_MODE_2
523 bool
524 depends on MFD_WM8350
525
526config MFD_WM8351_CONFIG_MODE_3
527 bool
528 depends on MFD_WM8350
529
Mark Brown96920632008-12-18 23:09:50 +0100[diff] [blame]530config MFD_WM8352_CONFIG_MODE_0
531 bool
532 depends on MFD_WM8350
533
534config MFD_WM8352_CONFIG_MODE_1
535 bool
536 depends on MFD_WM8350
537
538config MFD_WM8352_CONFIG_MODE_2
539 bool
540 depends on MFD_WM8350
541
542config MFD_WM8352_CONFIG_MODE_3
543 bool
544 depends on MFD_WM8350
545
Mark Brownc661a0b2008-10-10 15:58:11 +0100[diff] [blame]546config MFD_WM8350_I2C
Mark Brownecf926b2010-01-05 20:40:47 +0000[diff] [blame]547 bool "Support Wolfson Microelectronics WM8350 with I2C"
Mark Brownc661a0b2008-10-10 15:58:11 +0100[diff] [blame]548 select MFD_WM8350
Geert Uytterhoeven8d002bd2009-12-15 21:49:57 +0100[diff] [blame]549 depends on I2C=y && GENERIC_HARDIRQS
Mark Brownc661a0b2008-10-10 15:58:11 +0100[diff] [blame]550 help
551 The WM8350 is an integrated audio and power management
552 subsystem with watchdog and RTC functionality for embedded
553 systems. This option enables core support for the WM8350 with
554 I2C as the control interface. Additional options must be
555 selected to enable support for the functionality of the chip.
556
Mark Brown9e501082010-01-29 18:20:29 +0000[diff] [blame]557config MFD_WM8994
Mark Brownc9fbf7e2010-03-26 16:49:15 +0000[diff] [blame]558 bool "Support Wolfson Microelectronics WM8994"
Mark Brown9e501082010-01-29 18:20:29 +0000[diff] [blame]559 select MFD_CORE
Mark Brownd6c645fc2011-06-17 13:02:27 +0100[diff] [blame]560 select REGMAP_I2C
Mark Brown8ab30692011-10-25 10:19:04 +0200[diff] [blame]561 select REGMAP_IRQ
Mark Brownc9fbf7e2010-03-26 16:49:15 +0000[diff] [blame]562 depends on I2C=y && GENERIC_HARDIRQS
Mark Brown9e501082010-01-29 18:20:29 +0000[diff] [blame]563 help
564 The WM8994 is a highly integrated hi-fi CODEC designed for
565 smartphone applicatiosn. As well as audio functionality it
566 has on board GPIO and regulator functionality which is
567 supported via the relevant subsystems. This driver provides
568 core support for the WM8994, in order to use the actual
569 functionaltiy of the device other drivers must be enabled.
570
Balaji Raof52046b2009-01-09 01:49:01 +0100[diff] [blame]571config MFD_PCF50633
572 tristate "Support for NXP PCF50633"
573 depends on I2C
Mark Brown6e3ad112011-08-08 17:04:40 +0900[diff] [blame]574 select REGMAP_I2C
Balaji Raof52046b2009-01-09 01:49:01 +0100[diff] [blame]575 help
576 Say yes here if you have NXP PCF50633 chip on your board.
577 This core driver provides register access and IRQ handling
578 facilities, and registers devices for the various functions
579 so that function-specific drivers can bind to them.
580
Axel Lin13051342011-04-15 20:06:37 +0800[diff] [blame]581config PCF50633_ADC
582 tristate "Support for NXP PCF50633 ADC"
583 depends on MFD_PCF50633
584 help
585 Say yes here if you want to include support for ADC in the
586 NXP PCF50633 chip.
587
588config PCF50633_GPIO
589 tristate "Support for NXP PCF50633 GPIO"
590 depends on MFD_PCF50633
591 help
592 Say yes here if you want to include support GPIO for pins on
593 the PCF50633 chip.
594
Sascha Hauer8238add2009-08-19 01:40:28 +0200[diff] [blame]595config MFD_MC13783
Uwe Kleine-König8e005932010-09-28 16:37:20 +0200[diff] [blame]596 tristate
597
598config MFD_MC13XXX
599 tristate "Support Freescale MC13783 and MC13892"
Marc Reillydf3df642012-04-01 16:41:39 +1000[diff] [blame^]600 depends on SPI_MASTER || I2C
Sascha Hauer8238add2009-08-19 01:40:28 +0200[diff] [blame]601 select MFD_CORE
Uwe Kleine-König8e005932010-09-28 16:37:20 +0200[diff] [blame]602 select MFD_MC13783
Sascha Hauer8238add2009-08-19 01:40:28 +0200[diff] [blame]603 help
Marc Reillya0c7c1d2012-04-01 16:41:38 +1000[diff] [blame]604 Enable support for the Freescale MC13783 and MC13892 PMICs.
605 This driver provides common support for accessing the device,
Sascha Hauer8238add2009-08-19 01:40:28 +0200[diff] [blame]606 additional drivers must be enabled in order to use the
607 functionality of the device.
608
Marc Reillya0c7c1d2012-04-01 16:41:38 +1000[diff] [blame]609if MFD_MC13XXX
610
611config MFD_MC13XXX_SPI
612 tristate "MC13xxx SPI interface" if SPI_MASTER
613 default SPI_MASTER
614 select REGMAP_SPI
615 help
616 Select this if your MC13xxx is connected via an SPI bus.
617
Marc Reillydf3df642012-04-01 16:41:39 +1000[diff] [blame^]618config MFD_MC13XXX_I2C
619 tristate "MC13xxx I2C interface" if I2C
620 default I2C
621 select REGMAP_I2C
622 help
623 Select this if your MC13xxx is connected via an I2C bus.
624
Marc Reillya0c7c1d2012-04-01 16:41:38 +1000[diff] [blame]625endif
626
Mattias Wallinfa661252010-05-01 18:26:20 +0200[diff] [blame]627config ABX500_CORE
628 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
Mattias Wallin47c16972010-09-10 17:47:56 +0200[diff] [blame]629 default y if ARCH_U300 || ARCH_U8500
Mattias Wallinfa661252010-05-01 18:26:20 +0200[diff] [blame]630 help
631 Say yes here if you have the ABX500 Mixed Signal IC family
632 chips. This core driver expose register access functions.
633 Functionality specific drivers using these functions can
634 remain unchanged when IC changes. Binding of the functions to
635 actual register access is done by the IC core driver.
636
Linus Walleij14fa5692009-05-21 23:17:06 +0200[diff] [blame]637config AB3100_CORE
Linus Walleij2071db42010-01-19 11:41:52 +0100[diff] [blame]638 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
Mattias Wallinfa661252010-05-01 18:26:20 +0200[diff] [blame]639 depends on I2C=y && ABX500_CORE
Linus Walleij8c96aef2010-08-20 10:27:12 +0200[diff] [blame]640 select MFD_CORE
Linus Walleij14fa5692009-05-21 23:17:06 +0200[diff] [blame]641 default y if ARCH_U300
642 help
643 Select this to enable the AB3100 Mixed Signal IC core
644 functionality. This connects to a AB3100 on the I2C bus
645 and expose a number of symbols needed for dependent devices
646 to read and write registers and subscribe to events from
647 this multi-functional IC. This is needed to use other features
648 of the AB3100 such as battery-backed RTC, charging control,
649 LEDs, vibrator, system power and temperature, power management
650 and ALSA sound.
651
Linus Walleij12992dd2009-08-18 22:52:26 +0200[diff] [blame]652config AB3100_OTP
653 tristate "ST-Ericsson AB3100 OTP functions"
654 depends on AB3100_CORE
655 default y if AB3100_CORE
656 help
657 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
658 programmable memory) support. This exposes a sysfs file to read
659 out OTP values.
660
Daniel Ribeiro13a09f92009-05-28 15:43:37 -0300[diff] [blame]661config EZX_PCAP
662 bool "PCAP Support"
663 depends on GENERIC_HARDIRQS && SPI_MASTER
664 help
665 This enables the PCAP ASIC present on EZX Phones. This is
666 needed for MMC, TouchScreen, Sound, USB, etc..
667
Mattias Wallin3d5e2ca2011-09-22 08:22:18 +0200[diff] [blame]668config AB5500_CORE
669 bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
670 depends on ABX500_CORE && MFD_DB5500_PRCMU
671 select MFD_CORE
672 help
673 Select this option to enable access to AB5500 power management
674 chip. This connects to the db5500 chip via the I2C bus via PRCMU.
675 This chip embeds various other multimedia funtionalities as well.
676
Linus Walleij94be70d2011-09-22 08:22:33 +0200[diff] [blame]677config AB5500_DEBUG
678 bool "Enable debug info via debugfs"
679 depends on AB5500_CORE && DEBUG_FS
680 default y if DEBUG_FS
681 help
682 Select this option if you want debug information from the AB5500
683 using the debug filesystem, debugfs.
684
Rabin Vincent62579262010-05-19 11:39:02 +0200[diff] [blame]685config AB8500_CORE
686 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
Sundar Iyer6680d942010-12-24 11:52:08 +0100[diff] [blame]687 depends on GENERIC_HARDIRQS && ABX500_CORE
Rabin Vincent62579262010-05-19 11:39:02 +0200[diff] [blame]688 select MFD_CORE
Srinidhi Kasagar0c418392009-10-12 17:11:52 +0200[diff] [blame]689 help
Rabin Vincent62579262010-05-19 11:39:02 +0200[diff] [blame]690 Select this option to enable access to AB8500 power management
Sundar Iyer6680d942010-12-24 11:52:08 +0100[diff] [blame]691 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
692 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
693 the irq_chip parts for handling the Mixed Signal chip events.
Srinidhi Kasagar0c418392009-10-12 17:11:52 +0200[diff] [blame]694 This chip embeds various other multimedia funtionalities as well.
695
Mattias Wallin39368ed2010-09-15 13:12:03 +0200[diff] [blame]696config AB8500_I2C_CORE
697 bool "AB8500 register access via PRCMU I2C"
Linus Walleij650c2a22011-05-15 22:53:56 +0200[diff] [blame]698 depends on AB8500_CORE && MFD_DB8500_PRCMU
Mattias Wallin39368ed2010-09-15 13:12:03 +0200[diff] [blame]699 default y
700 help
701 This enables register access to the AB8500 chip via PRCMU I2C.
702 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
703 the I2C bus is connected to the Power Reset
704 and Mangagement Unit, PRCMU.
705
Mattias Wallin5814fc32010-09-13 16:05:04 +0200[diff] [blame]706config AB8500_DEBUG
707 bool "Enable debug info via debugfs"
708 depends on AB8500_CORE && DEBUG_FS
709 default y if DEBUG_FS
710 help
711 Select this option if you want debug information using the debug
712 filesystem, debugfs.
713
Arun Murthydae2db32011-02-22 10:11:13 +0100[diff] [blame]714config AB8500_GPADC
715 bool "AB8500 GPADC driver"
716 depends on AB8500_CORE && REGULATOR_AB8500
717 default y
718 help
719 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
720
Linus Walleij650c2a22011-05-15 22:53:56 +0200[diff] [blame]721config MFD_DB8500_PRCMU
722 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
723 depends on UX500_SOC_DB8500
724 select MFD_CORE
725 help
726 Select this option to enable support for the DB8500 Power Reset
727 and Control Management Unit. This is basically an autonomous
728 system controller running an XP70 microprocessor, which is accessed
729 through a register map.
730
Linus Walleij83177972011-05-03 18:14:48 +0200[diff] [blame]731config MFD_DB5500_PRCMU
732 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
733 depends on UX500_SOC_DB5500
734 select MFD_CORE
735 help
736 Select this option to enable support for the DB5500 Power Reset
737 and Control Management Unit. This is basically an autonomous
738 system controller running an XP70 microprocessor, which is accessed
739 through a register map.
740
Andres Salomonf71e1af2010-11-26 11:52:35 +0100[diff] [blame]741config MFD_CS5535
742 tristate "Support for CS5535 and CS5536 southbridge core functions"
743 select MFD_CORE
Andres Salomon15b7cf12011-03-27 21:26:03 -0700[diff] [blame]744 depends on PCI && X86
Andres Salomonf71e1af2010-11-26 11:52:35 +0100[diff] [blame]745 ---help---
746 This is the core driver for CS5535/CS5536 MFD functions. This is
747 necessary for using the board's GPIO and MFGPT functionality.
748
Richard Röjfors8edbede2010-02-04 08:18:52 -0300[diff] [blame]749config MFD_TIMBERDALE
750 tristate "Support for the Timberdale FPGA"
751 select MFD_CORE
Randy Dunlap546e29b62010-02-12 12:30:55 -0300[diff] [blame]752 depends on PCI && GPIOLIB
Richard Röjfors8edbede2010-02-04 08:18:52 -0300[diff] [blame]753 ---help---
754 This is the core driver for the timberdale FPGA. This device is a
755 multifunction device which exposes numerous platform devices.
756
757 The timberdale FPGA can be found on the Intel Atom development board
758 for in-vehicle infontainment, called Russellville.
Denis Turischeve82c60a2010-02-19 11:26:25 +0100[diff] [blame]759
760config LPC_SCH
761 tristate "Intel SCH LPC"
762 depends on PCI
763 select MFD_CORE
764 help
765 LPC bridge function of the Intel SCH provides support for
766 System Management Bus and General Purpose I/O.
767
Aaron Sierra4630b132012-03-28 09:43:10 -0500[diff] [blame]768config LPC_ICH
769 tristate "Intel ICH LPC"
770 depends on PCI
771 select MFD_CORE
772 help
773 The LPC bridge function of the Intel ICH provides support for
774 many functional units. This driver provides needed support for
775 other drivers to control these functions, currently GPIO.
776
Florian Fainellie090d502010-03-21 01:06:05 +0100[diff] [blame]777config MFD_RDC321X
778 tristate "Support for RDC-R321x southbridge"
779 select MFD_CORE
780 depends on PCI
781 help
782 Say yes here if you want to have support for the RDC R-321x SoC
783 southbridge which provides access to GPIOs and Watchdog using the
784 southbridge PCI device configuration space.
785
Ira W. Snyderbd358132010-04-07 09:43:00 +0200[diff] [blame]786config MFD_JANZ_CMODIO
787 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
788 select MFD_CORE
789 depends on PCI
790 help
791 This is the core driver for the Janz CMOD-IO PCI MODULbus
792 carrier board. This device is a PCI to MODULbus bridge which may
793 host many different types of MODULbus daughterboards, including
794 CAN and GPIO controllers.
795
Lars-Peter Clausen91f4deb2010-07-12 03:48:08 +0200[diff] [blame]796config MFD_JZ4740_ADC
Lars-Peter Clausen914e6d42011-06-03 03:14:26 +0200[diff] [blame]797 bool "Support for the JZ4740 SoC ADC core"
Lars-Peter Clausen91f4deb2010-07-12 03:48:08 +0200[diff] [blame]798 select MFD_CORE
Lars-Peter Clausen914e6d42011-06-03 03:14:26 +0200[diff] [blame]799 select GENERIC_IRQ_CHIP
Lars-Peter Clausen91f4deb2010-07-12 03:48:08 +0200[diff] [blame]800 depends on MACH_JZ4740
801 help
802 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
803 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
804
Daniel Drake375fc772010-09-30 21:55:41 +0100[diff] [blame]805config MFD_VX855
806 tristate "Support for VIA VX855/VX875 integrated south bridge"
807 depends on PCI
808 select MFD_CORE
809 help
810 Say yes here to enable support for various functions of the
811 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
812 and/or vx855_gpio drivers for this to do anything useful.
813
Matti Aaltonen383268a2010-12-10 11:41:33 -0300[diff] [blame]814config MFD_WL1273_CORE
Matti Aaltonen94fd5b72011-03-01 10:10:35 -0300[diff] [blame]815 tristate "Support for TI WL1273 FM radio."
Matti Aaltonen383268a2010-12-10 11:41:33 -0300[diff] [blame]816 depends on I2C
817 select MFD_CORE
818 default n
819 help
820 This is the core driver for the TI WL1273 FM radio. This MFD
821 driver connects the radio-wl1273 V4L2 module and the wl1273
822 audio codec.
823
Keshava Munegowda17cdd292011-03-01 20:08:17 +0530[diff] [blame]824config MFD_OMAP_USB_HOST
825 bool "Support OMAP USBHS core driver"
826 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
827 default y
828 help
829 This is the core driver for the OAMP EHCI and OHCI drivers.
830 This MFD driver does the required setup functionalities for
831 OMAP USB Host drivers.
832
Abhijeet Dharmapurikarcbdb53e2011-04-05 14:40:52 -0700[diff] [blame]833config MFD_PM8XXX
834 tristate
835
836config MFD_PM8921_CORE
837 tristate "Qualcomm PM8921 PMIC chip"
838 depends on MSM_SSBI
839 select MFD_CORE
840 select MFD_PM8XXX
841 help
842 If you say yes to this option, support will be included for the
843 built-in PM8921 PMIC chip.
844
845 This is required if your board has a PM8921 and uses its features,
846 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
847
848 Say M here if you want to include support for PM8921 chip as a module.
849 This will build a module called "pm8921-core".
850
Abhijeet Dharmapurikarc013f0a2011-04-05 14:40:53 -0700[diff] [blame]851config MFD_PM8XXX_IRQ
852 bool "Support for Qualcomm PM8xxx IRQ features"
853 depends on MFD_PM8XXX
854 default y if MFD_PM8XXX
855 help
856 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
857
858 This is required to use certain other PM 8xxx features, such as GPIO
859 and MPP.
860
Axel Lin8509e142011-06-23 10:15:51 +0800[diff] [blame]861config TPS65911_COMPARATOR
862 tristate
863
Venu Byravarasu3c33be062012-03-16 11:10:19 +0530[diff] [blame]864config MFD_TPS65090
865 bool "TPS65090 Power Management chips"
866 depends on I2C=y && GENERIC_HARDIRQS
867 select MFD_CORE
868 select REGMAP_I2C
869 help
870 If you say yes here you get support for the TPS65090 series of
871 Power Management chips.
872 This driver provides common support for accessing the device,
873 additional drivers must be enabled in order to use the
874 functionality of the device.
875
Jin Park09d62922011-07-04 19:48:12 +0200[diff] [blame]876config MFD_AAT2870_CORE
877 bool "Support for the AnalogicTech AAT2870"
878 select MFD_CORE
879 depends on I2C=y && GPIOLIB
880 help
881 If you say yes here you get support for the AAT2870.
882 This driver provides common support for accessing the device,
883 additional drivers must be enabled in order to use the
884 functionality of the device.
885
Mika Westerberg1f5a3712011-09-21 13:03:07 +0200[diff] [blame]886config MFD_INTEL_MSIC
887 bool "Support for Intel MSIC"
888 depends on INTEL_SCU_IPC
889 select MFD_CORE
890 help
891 Select this option to enable access to Intel MSIC (Avatele
892 Passage) chip. This chip embeds audio, battery, GPIO, etc.
893 devices used in Intel Medfield platforms.
894
Laxman Dewangan1b1247d2012-02-28 18:35:17 +0530[diff] [blame]895config MFD_RC5T583
896 bool "Ricoh RC5T583 Power Management system device"
Laxman Dewangan5364d0b82012-03-19 11:44:55 +0530[diff] [blame]897 depends on I2C=y && GENERIC_HARDIRQS
Laxman Dewangan1b1247d2012-02-28 18:35:17 +0530[diff] [blame]898 select MFD_CORE
899 select REGMAP_I2C
900 help
901 Select this option to get support for the RICOH583 Power
902 Management system device.
903 This driver provides common support for accessing the device
904 through i2c interface. The device supports multiple sub-devices
905 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
906 Additional drivers must be enabled in order to use the
907 different functionality of the device.
908
Ying-Chun Liu (PaulLiu)75060a12012-03-16 21:12:32 +0100[diff] [blame]909config MFD_ANATOP
910 bool "Support for Freescale i.MX on-chip ANATOP controller"
911 depends on SOC_IMX6Q
912 help
913 Select this option to enable Freescale i.MX on-chip ANATOP
914 MFD controller. This controller embeds regulator and
915 thermal devices for Freescale i.MX platforms.
916
Arnd Bergmann8a0a8e82011-09-02 16:43:36 +0200[diff] [blame]917endmenu
918endif
Ben Dooksb6d64542007-02-20 13:58:01 -0800[diff] [blame]919
Russell Kinga4e137a2005-08-18 10:06:59 +0100[diff] [blame]920menu "Multimedia Capabilities Port drivers"
Adrian Bunkf751d502006-03-24 03:18:21 -0800[diff] [blame]921 depends on ARCH_SA1100
Russell Kinga4e137a2005-08-18 10:06:59 +0100[diff] [blame]922
923config MCP
924 tristate
925
Russell King5e742ad2005-08-18 10:08:15 +0100[diff] [blame]926# Interface drivers
927config MCP_SA11X0
928 tristate "Support SA11x0 MCP interface"
929 depends on ARCH_SA1100
930 select MCP
931
Russell King05c45ca2005-09-11 10:26:31 +0100[diff] [blame]932# Chip drivers
933config MCP_UCB1200
Russell Kinga3364402012-01-21 14:58:28 +0000[diff] [blame]934 bool "Support for UCB1200 / UCB1300"
935 depends on MCP_SA11X0
936 select MCP
Russell King05c45ca2005-09-11 10:26:31 +0100[diff] [blame]937
Russell Kingacb45432005-09-11 10:26:57 +0100[diff] [blame]938config MCP_UCB1200_TS
939 tristate "Touchscreen interface support"
940 depends on MCP_UCB1200 && INPUT
941
Russell Kinga4e137a2005-08-18 10:06:59 +0100[diff] [blame]942endmenu