Gitiles
Code Review Sign In
review.evervolv.com / android_kernel_htc_msm8960 / 231dd9c8994430d4aaa75cdee95af13c154f489f / . / drivers / mfd / Kconfig
blob: d92bea2c468fd6854f24507437b8eb3dff4138b8 [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
180 help
181 if you say yes here you get support for the TPS65910 series of
182 Power Management chips.
183
Margarita Olaya36e52872011-06-09 14:50:00 -0500[diff] [blame]184config MFD_TPS65912
Mark Brown56088012011-06-22 14:53:58 +0100[diff] [blame]185 bool
Margarita Olaya36e52872011-06-09 14:50:00 -0500[diff] [blame]186 depends on GPIOLIB
187
188config MFD_TPS65912_I2C
Axel Lin231dd9c2012-02-15 16:05:24 +0800[diff] [blame^]189 bool "TPS65912 Power Management chip with I2C"
Margarita Olaya36e52872011-06-09 14:50:00 -0500[diff] [blame]190 select MFD_CORE
191 select MFD_TPS65912
192 depends on I2C=y && GPIOLIB
193 help
194 If you say yes here you get support for the TPS65912 series of
195 PM chips with I2C interface.
196
197config MFD_TPS65912_SPI
198 bool "TPS65912 Power Management chip with SPI"
199 select MFD_CORE
200 select MFD_TPS65912
201 depends on SPI_MASTER && GPIOLIB
202 help
203 If you say yes here you get support for the TPS65912 series of
204 PM chips with SPI interface.
205
David Brownell88e75cc2008-12-22 12:18:02 +0100[diff] [blame]206config MENELAUS
207 bool "Texas Instruments TWL92330/Menelaus PM chip"
Tony Lindgren088ef952010-02-12 12:26:47 -0800[diff] [blame]208 depends on I2C=y && ARCH_OMAP2
David Brownell88e75cc2008-12-22 12:18:02 +0100[diff] [blame]209 help
210 If you say yes here you get support for the Texas Instruments
211 TWL92330/Menelaus Power Management chip. This include voltage
Matt LaPlante692105b2009-01-26 11:12:25 +0100[diff] [blame]212 regulators, Dual slot memory card transceivers, real-time clock
David Brownell88e75cc2008-12-22 12:18:02 +0100[diff] [blame]213 and other features that are often used in portable devices like
214 cell phones and PDAs.
215
David Brownella603a7f2008-10-15 12:15:39 +0200[diff] [blame]216config TWL4030_CORE
Balaji T Ke8deb282009-12-14 00:25:31 +0100[diff] [blame]217 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
Russell King62525472012-02-07 09:47:21 +0000[diff] [blame]218 depends on I2C=y && GENERIC_HARDIRQS
David Brownella603a7f2008-10-15 12:15:39 +0200[diff] [blame]219 help
Balaji T Ke8deb282009-12-14 00:25:31 +0100[diff] [blame]220 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
David Brownella603a7f2008-10-15 12:15:39 +0200[diff] [blame]221 This core driver provides register access and IRQ handling
222 facilities, and registers devices for the various functions
223 so that function-specific drivers can bind to them.
224
225 These multi-function chips are found on many OMAP2 and OMAP3
226 boards, providing power management, RTC, GPIO, keypad, a
227 high speed USB OTG transceiver, an audio codec (on most
228 versions) and many other features.
229
Keerthyf99c1d42011-03-01 19:12:26 +0530[diff] [blame]230config TWL4030_MADC
231 tristate "Texas Instruments TWL4030 MADC"
232 depends on TWL4030_CORE
233 help
234 This driver provides support for triton TWL4030-MADC. The
235 driver supports both RT and SW conversion methods.
236
237 This driver can be built as a module. If so it will be
238 named twl4030-madc
239
Amit Kucheriaebf0bd32009-08-31 18:32:18 +0200[diff] [blame]240config TWL4030_POWER
241 bool "Support power resources on TWL4030 family chips"
242 depends on TWL4030_CORE && ARM
243 help
244 Say yes here if you want to use the power resources on the
245 TWL4030 family chips. Most of these resources are regulators,
246 which have a separate driver; some are control signals, such
247 as clock request handshaking.
248
249 This driver uses board-specific data to initialize the resources
Lucas De Marchi25985ed2011-03-30 22:57:33 -0300[diff] [blame]250 and load scripts controlling which resources are switched off/on
Amit Kucheriaebf0bd32009-08-31 18:32:18 +0200[diff] [blame]251 or reset when a sleep, wakeup or warm reset event occurs.
252
Peter Ujfalusi57fe7252011-05-31 12:02:49 +0300[diff] [blame]253config MFD_TWL4030_AUDIO
Peter Ujfalusi0b83dde2009-10-22 13:26:45 +0300[diff] [blame]254 bool
255 depends on TWL4030_CORE
256 select MFD_CORE
257 default n
258
Hemanth V31fc03d2010-07-14 12:04:56 +0200[diff] [blame]259config TWL6030_PWM
260 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
261 depends on TWL4030_CORE
262 select HAVE_PWM
263 default n
264 help
265 Say yes here if you want support for TWL6030 PWM.
266 This is used to control charging LED brightness.
267
Misael Lopez Cruzf19b2822011-04-27 02:14:07 -0500[diff] [blame]268config TWL6040_CORE
269 bool
270 depends on TWL4030_CORE && GENERIC_HARDIRQS
271 select MFD_CORE
272 default n
273
Rabin Vincent27e34992010-07-02 16:52:08 +0530[diff] [blame]274config MFD_STMPE
275 bool "Support STMicroelectronics STMPE"
Viresh Kumare7899952011-11-17 11:02:21 +0530[diff] [blame]276 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
Rabin Vincent27e34992010-07-02 16:52:08 +0530[diff] [blame]277 select MFD_CORE
278 help
279 Support for the STMPE family of I/O Expanders from
280 STMicroelectronics.
281
282 Currently supported devices are:
283
284 STMPE811: GPIO, Touchscreen
285 STMPE1601: GPIO, Keypad
286 STMPE2401: GPIO, Keypad
287 STMPE2403: GPIO, Keypad
288
289 This driver provides common support for accessing the device,
290 additional drivers must be enabled in order to use the functionality
291 of the device. Currently available sub drivers are:
292
293 GPIO: stmpe-gpio
294 Keypad: stmpe-keypad
295 Touchscreen: stmpe-ts
296
Viresh Kumar1a6e4b72011-11-17 11:02:20 +0530[diff] [blame]297menu "STMPE Interface Drivers"
298depends on MFD_STMPE
299
300config STMPE_I2C
301 bool "STMPE I2C Inteface"
Samuel Ortizeedea802011-12-20 18:28:19 +0100[diff] [blame]302 depends on I2C=y
Viresh Kumar1a6e4b72011-11-17 11:02:20 +0530[diff] [blame]303 default y
304 help
305 This is used to enable I2C interface of STMPE
Viresh Kumare7899952011-11-17 11:02:21 +0530[diff] [blame]306
307config STMPE_SPI
308 bool "STMPE SPI Inteface"
309 depends on SPI_MASTER
310 help
311 This is used to enable SPI interface of STMPE
Viresh Kumar1a6e4b72011-11-17 11:02:20 +0530[diff] [blame]312endmenu
313
Sundar Iyerf4e8afd2010-12-13 09:33:13 +0530[diff] [blame]314config MFD_TC3589X
315 bool "Support Toshiba TC35892 and variants"
Rabin Vincentb4ecd322010-05-10 23:39:47 +0200[diff] [blame]316 depends on I2C=y && GENERIC_HARDIRQS
317 select MFD_CORE
318 help
Sundar Iyerf4e8afd2010-12-13 09:33:13 +0530[diff] [blame]319 Support for the Toshiba TC35892 and variants I/O Expander.
Rabin Vincentb4ecd322010-05-10 23:39:47 +0200[diff] [blame]320
321 This driver provides common support for accessing the device,
322 additional drivers must be enabled in order to use the
323 functionality of the device.
324
Samuel Ortiz1c2c30a2008-08-05 19:27:58 +0200[diff] [blame]325config MFD_TMIO
326 bool
327 default n
328
Ian Molton1f192012008-07-15 15:09:43 +0100[diff] [blame]329config MFD_T7L66XB
330 bool "Support Toshiba T7L66XB"
Al Viro9ca68232008-11-01 18:19:59 +0000[diff] [blame]331 depends on ARM && HAVE_CLK
Ian Molton1f192012008-07-15 15:09:43 +0100[diff] [blame]332 select MFD_CORE
Samuel Ortiz1c2c30a2008-08-05 19:27:58 +0200[diff] [blame]333 select MFD_TMIO
Ian Molton1f192012008-07-15 15:09:43 +0100[diff] [blame]334 help
335 Support for Toshiba Mobile IO Controller T7L66XB
336
Ian Moltoncbdfb422008-07-15 15:12:52 +0100[diff] [blame]337config MFD_TC6387XB
338 bool "Support Toshiba TC6387XB"
Al Viro9ca68232008-11-01 18:19:59 +0000[diff] [blame]339 depends on ARM && HAVE_CLK
Ian Moltoncbdfb422008-07-15 15:12:52 +0100[diff] [blame]340 select MFD_CORE
Samuel Ortiz1c2c30a2008-08-05 19:27:58 +0200[diff] [blame]341 select MFD_TMIO
Ian Moltoncbdfb422008-07-15 15:12:52 +0100[diff] [blame]342 help
343 Support for Toshiba Mobile IO Controller TC6387XB
344
Dmitry Baryshkovd6315942008-06-22 12:01:58 +0100[diff] [blame]345config MFD_TC6393XB
346 bool "Support Toshiba TC6393XB"
Christoph Fritze959da12011-11-29 19:38:38 +0100[diff] [blame]347 depends on GPIOLIB && ARM && HAVE_CLK
Dmitry Baryshkovf024ff12008-06-27 10:37:57 +0100[diff] [blame]348 select MFD_CORE
Samuel Ortiz1c2c30a2008-08-05 19:27:58 +0200[diff] [blame]349 select MFD_TMIO
Dmitry Baryshkovd6315942008-06-22 12:01:58 +0100[diff] [blame]350 help
351 Support for Toshiba Mobile IO Controller TC6393XB
352
Samuel Ortiz8e2eaab2008-10-24 17:10:05 +0200[diff] [blame]353config PMIC_DA903X
354 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
355 depends on I2C=y
356 help
357 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
358 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
359 usually found on PXA processors-based platforms. This includes
360 the I2C driver and the core APIs _only_, you have to select
361 individual components like LCD backlight, voltage regulators,
362 LEDs and battery-charger under the corresponding menus.
363
Ashish Jangam84c99db2011-12-12 20:06:56 +0530[diff] [blame]364config PMIC_DA9052
365 bool
366 select MFD_CORE
367
Ashish Jangamcfe04472011-12-12 20:37:41 +0530[diff] [blame]368config MFD_DA9052_SPI
369 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
370 select REGMAP_SPI
371 select REGMAP_IRQ
372 select PMIC_DA9052
373 depends on SPI_MASTER=y
374 help
375 Support for the Dialog Semiconductor DA9052 PMIC
376 when controlled using SPI. This driver provides common support
377 for accessing the device, additional drivers must be enabled in
378 order to use the functionality of the device.
379
Ashish Jangam84c99db2011-12-12 20:06:56 +0530[diff] [blame]380config MFD_DA9052_I2C
381 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
382 select REGMAP_I2C
383 select REGMAP_IRQ
384 select PMIC_DA9052
385 depends on I2C=y
386 help
387 Support for the Dialog Semiconductor DA9052 PMIC
388 when controlled using I2C. This driver provides common support
389 for accessing the device, additional drivers must be enabled in
390 order to use the functionality of the device.
391
Michael Hennericha5736e02009-10-12 17:22:38 +0200[diff] [blame]392config PMIC_ADP5520
393 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
394 depends on I2C=y
395 help
396 Say yes here to add support for Analog Devices AD5520 and ADP5501,
397 Multifunction Power Management IC. This includes
398 the I2C driver and the core APIs _only_, you have to select
399 individual components like LCD backlight, LEDs, GPIOs and Kepad
400 under the corresponding menus.
401
Haojian Zhuangd50f8f32010-01-08 12:29:23 +0100[diff] [blame]402config MFD_MAX8925
Haojian Zhuang1f1cf8f2010-02-05 16:07:54 +0100[diff] [blame]403 bool "Maxim Semiconductor MAX8925 PMIC Support"
Geert Uytterhoeven8d002bd2009-12-15 21:49:57 +0100[diff] [blame]404 depends on I2C=y && GENERIC_HARDIRQS
Haojian Zhuang1ad99892010-01-08 12:43:29 -0500[diff] [blame]405 select MFD_CORE
Haojian Zhuangd50f8f32010-01-08 12:29:23 +0100[diff] [blame]406 help
407 Say yes here to support for Maxim Semiconductor MAX8925. This is
408 a Power Management IC. This driver provies common support for
409 accessing the device, additional drivers must be enabled in order
410 to use the functionality of the device.
411
MyungJoo Ham527e7e92011-03-04 15:50:26 +0900[diff] [blame]412config MFD_MAX8997
413 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
414 depends on I2C=y && GENERIC_HARDIRQS
415 select MFD_CORE
416 help
417 Say yes here to support for Maxim Semiconductor MAX8998/8966.
418 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
419 MUIC controls on chip.
Randy Dunlapd7e8c012011-03-14 11:28:37 +0100[diff] [blame]420 This driver provides common support for accessing the device;
MyungJoo Ham527e7e92011-03-04 15:50:26 +0900[diff] [blame]421 additional drivers must be enabled in order to use the functionality
422 of the device.
423
Kyungmin Park156f2522010-06-16 09:04:16 +0200[diff] [blame]424config MFD_MAX8998
Kyungmin Parkf8539dd2010-08-23 13:46:49 +0900[diff] [blame]425 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
Joonyoung Shim2c7e6f52010-09-10 18:36:39 +0200[diff] [blame]426 depends on I2C=y && GENERIC_HARDIRQS
Kyungmin Park156f2522010-06-16 09:04:16 +0200[diff] [blame]427 select MFD_CORE
428 help
Kyungmin Parkf8539dd2010-08-23 13:46:49 +0900[diff] [blame]429 Say yes here to support for Maxim Semiconductor MAX8998 and
430 National Semiconductor LP3974. This is a Power Management IC.
431 This driver provies common support for accessing the device,
432 additional drivers must be enabled in order to use the functionality
433 of the device.
Kyungmin Park156f2522010-06-16 09:04:16 +0200[diff] [blame]434
Sangbeom Kimc3d4d692012-01-09 00:09:09 +0100[diff] [blame]435config MFD_S5M_CORE
436 bool "SAMSUNG S5M Series Support"
437 depends on I2C=y && GENERIC_HARDIRQS
438 select MFD_CORE
439 select REGMAP_I2C
440 help
441 Support for the Samsung Electronics S5M MFD series.
442 This driver provies common support for accessing the device,
443 additional drivers must be enabled in order to use the functionality
444 of the device
445
Mark Brown1d9f9f02008-09-10 18:58:42 +0100[diff] [blame]446config MFD_WM8400
447 tristate "Support Wolfson Microelectronics WM8400"
Mark Brownb8380c12008-12-18 10:54:22 +0100[diff] [blame]448 select MFD_CORE
Mark Brown9c366452008-10-24 17:16:11 +0200[diff] [blame]449 depends on I2C
Mark Brown2b247d02011-08-23 18:56:19 +0100[diff] [blame]450 select REGMAP_I2C
Mark Brown1d9f9f02008-09-10 18:58:42 +0100[diff] [blame]451 help
452 Support for the Wolfson Microelecronics WM8400 PMIC and audio
Mark Brown9e5aca52009-05-29 11:34:18 +0100[diff] [blame]453 CODEC. This driver provides common support for accessing
Mark Brown1d9f9f02008-09-10 18:58:42 +0100[diff] [blame]454 the device, additional drivers must be enabled in order to use
455 the functionality of the device.
456
Mark Brownb11062b2009-07-27 14:45:58 +0100[diff] [blame]457config MFD_WM831X
Mark Browne5b48682010-10-19 23:57:56 +0200[diff] [blame]458 bool
459 depends on GENERIC_HARDIRQS
460
461config MFD_WM831X_I2C
462 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
Mark Brownb11062b2009-07-27 14:45:58 +0100[diff] [blame]463 select MFD_CORE
Mark Browne5b48682010-10-19 23:57:56 +0200[diff] [blame]464 select MFD_WM831X
Mark Brown1df59812011-06-10 19:28:10 +0100[diff] [blame]465 select REGMAP_I2C
Geert Uytterhoeven8d002bd2009-12-15 21:49:57 +0100[diff] [blame]466 depends on I2C=y && GENERIC_HARDIRQS
Mark Brownb11062b2009-07-27 14:45:58 +0100[diff] [blame]467 help
Mark Browne5b48682010-10-19 23:57:56 +0200[diff] [blame]468 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
469 when controlled using I2C. This driver provides common support
470 for accessing the device, additional drivers must be enabled in
471 order to use the functionality of the device.
Mark Brownb11062b2009-07-27 14:45:58 +0100[diff] [blame]472
Mark Brown2aa13b92010-10-20 00:00:11 +0200[diff] [blame]473config MFD_WM831X_SPI
474 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
475 select MFD_CORE
476 select MFD_WM831X
Mark Brown1df59812011-06-10 19:28:10 +0100[diff] [blame]477 select REGMAP_SPI
Mark Brown2aa13b92010-10-20 00:00:11 +0200[diff] [blame]478 depends on SPI_MASTER && GENERIC_HARDIRQS
479 help
480 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
481 when controlled using SPI. This driver provides common support
482 for accessing the device, additional drivers must be enabled in
483 order to use the functionality of the device.
484
Mark Brown89b40122008-10-10 15:58:10 +0100[diff] [blame]485config MFD_WM8350
Mark Brownecf926b2010-01-05 20:40:47 +0000[diff] [blame]486 bool
Geert Uytterhoeven8d002bd2009-12-15 21:49:57 +0100[diff] [blame]487 depends on GENERIC_HARDIRQS
Mark Brown89b40122008-10-10 15:58:10 +0100[diff] [blame]488
489config MFD_WM8350_CONFIG_MODE_0
490 bool
491 depends on MFD_WM8350
492
493config MFD_WM8350_CONFIG_MODE_1
494 bool
495 depends on MFD_WM8350
496
497config MFD_WM8350_CONFIG_MODE_2
498 bool
499 depends on MFD_WM8350
500
501config MFD_WM8350_CONFIG_MODE_3
502 bool
503 depends on MFD_WM8350
504
Mark Brownca23f8c2008-12-18 23:12:28 +0100[diff] [blame]505config MFD_WM8351_CONFIG_MODE_0
506 bool
507 depends on MFD_WM8350
508
509config MFD_WM8351_CONFIG_MODE_1
510 bool
511 depends on MFD_WM8350
512
513config MFD_WM8351_CONFIG_MODE_2
514 bool
515 depends on MFD_WM8350
516
517config MFD_WM8351_CONFIG_MODE_3
518 bool
519 depends on MFD_WM8350
520
Mark Brown96920632008-12-18 23:09:50 +0100[diff] [blame]521config MFD_WM8352_CONFIG_MODE_0
522 bool
523 depends on MFD_WM8350
524
525config MFD_WM8352_CONFIG_MODE_1
526 bool
527 depends on MFD_WM8350
528
529config MFD_WM8352_CONFIG_MODE_2
530 bool
531 depends on MFD_WM8350
532
533config MFD_WM8352_CONFIG_MODE_3
534 bool
535 depends on MFD_WM8350
536
Mark Brownc661a0b2008-10-10 15:58:11 +0100[diff] [blame]537config MFD_WM8350_I2C
Mark Brownecf926b2010-01-05 20:40:47 +0000[diff] [blame]538 bool "Support Wolfson Microelectronics WM8350 with I2C"
Mark Brownc661a0b2008-10-10 15:58:11 +0100[diff] [blame]539 select MFD_WM8350
Geert Uytterhoeven8d002bd2009-12-15 21:49:57 +0100[diff] [blame]540 depends on I2C=y && GENERIC_HARDIRQS
Mark Brownc661a0b2008-10-10 15:58:11 +0100[diff] [blame]541 help
542 The WM8350 is an integrated audio and power management
543 subsystem with watchdog and RTC functionality for embedded
544 systems. This option enables core support for the WM8350 with
545 I2C as the control interface. Additional options must be
546 selected to enable support for the functionality of the chip.
547
Mark Brown9e501082010-01-29 18:20:29 +0000[diff] [blame]548config MFD_WM8994
Mark Brownc9fbf7e2010-03-26 16:49:15 +0000[diff] [blame]549 bool "Support Wolfson Microelectronics WM8994"
Mark Brown9e501082010-01-29 18:20:29 +0000[diff] [blame]550 select MFD_CORE
Mark Brownd6c645f2011-06-17 13:02:27 +0100[diff] [blame]551 select REGMAP_I2C
Mark Brown8ab30692011-10-25 10:19:04 +0200[diff] [blame]552 select REGMAP_IRQ
Mark Brownc9fbf7e2010-03-26 16:49:15 +0000[diff] [blame]553 depends on I2C=y && GENERIC_HARDIRQS
Mark Brown9e501082010-01-29 18:20:29 +0000[diff] [blame]554 help
555 The WM8994 is a highly integrated hi-fi CODEC designed for
556 smartphone applicatiosn. As well as audio functionality it
557 has on board GPIO and regulator functionality which is
558 supported via the relevant subsystems. This driver provides
559 core support for the WM8994, in order to use the actual
560 functionaltiy of the device other drivers must be enabled.
561
Balaji Raof52046b2009-01-09 01:49:01 +0100[diff] [blame]562config MFD_PCF50633
563 tristate "Support for NXP PCF50633"
564 depends on I2C
Mark Brown6e3ad112011-08-08 17:04:40 +0900[diff] [blame]565 select REGMAP_I2C
Balaji Raof52046b2009-01-09 01:49:01 +0100[diff] [blame]566 help
567 Say yes here if you have NXP PCF50633 chip on your board.
568 This core driver provides register access and IRQ handling
569 facilities, and registers devices for the various functions
570 so that function-specific drivers can bind to them.
571
Axel Lin13051342011-04-15 20:06:37 +0800[diff] [blame]572config PCF50633_ADC
573 tristate "Support for NXP PCF50633 ADC"
574 depends on MFD_PCF50633
575 help
576 Say yes here if you want to include support for ADC in the
577 NXP PCF50633 chip.
578
579config PCF50633_GPIO
580 tristate "Support for NXP PCF50633 GPIO"
581 depends on MFD_PCF50633
582 help
583 Say yes here if you want to include support GPIO for pins on
584 the PCF50633 chip.
585
Sascha Hauer8238add2009-08-19 01:40:28 +0200[diff] [blame]586config MFD_MC13783
Uwe Kleine-König8e005932010-09-28 16:37:20 +0200[diff] [blame]587 tristate
588
589config MFD_MC13XXX
590 tristate "Support Freescale MC13783 and MC13892"
Sascha Hauer8238add2009-08-19 01:40:28 +0200[diff] [blame]591 depends on SPI_MASTER
592 select MFD_CORE
Uwe Kleine-König8e005932010-09-28 16:37:20 +0200[diff] [blame]593 select MFD_MC13783
Sascha Hauer8238add2009-08-19 01:40:28 +0200[diff] [blame]594 help
Uwe Kleine-König8e005932010-09-28 16:37:20 +0200[diff] [blame]595 Support for the Freescale (Atlas) PMIC and audio CODECs
596 MC13783 and MC13892.
Sascha Hauer8238add2009-08-19 01:40:28 +0200[diff] [blame]597 This driver provides common support for accessing the device,
598 additional drivers must be enabled in order to use the
599 functionality of the device.
600
Mattias Wallinfa661252010-05-01 18:26:20 +0200[diff] [blame]601config ABX500_CORE
602 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
Mattias Wallin47c16972010-09-10 17:47:56 +0200[diff] [blame]603 default y if ARCH_U300 || ARCH_U8500
Mattias Wallinfa661252010-05-01 18:26:20 +0200[diff] [blame]604 help
605 Say yes here if you have the ABX500 Mixed Signal IC family
606 chips. This core driver expose register access functions.
607 Functionality specific drivers using these functions can
608 remain unchanged when IC changes. Binding of the functions to
609 actual register access is done by the IC core driver.
610
Linus Walleij14fa5692009-05-21 23:17:06 +0200[diff] [blame]611config AB3100_CORE
Linus Walleij2071db42010-01-19 11:41:52 +0100[diff] [blame]612 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
Mattias Wallinfa661252010-05-01 18:26:20 +0200[diff] [blame]613 depends on I2C=y && ABX500_CORE
Linus Walleij8c96aef2010-08-20 10:27:12 +0200[diff] [blame]614 select MFD_CORE
Linus Walleij14fa5692009-05-21 23:17:06 +0200[diff] [blame]615 default y if ARCH_U300
616 help
617 Select this to enable the AB3100 Mixed Signal IC core
618 functionality. This connects to a AB3100 on the I2C bus
619 and expose a number of symbols needed for dependent devices
620 to read and write registers and subscribe to events from
621 this multi-functional IC. This is needed to use other features
622 of the AB3100 such as battery-backed RTC, charging control,
623 LEDs, vibrator, system power and temperature, power management
624 and ALSA sound.
625
Linus Walleij12992dd2009-08-18 22:52:26 +0200[diff] [blame]626config AB3100_OTP
627 tristate "ST-Ericsson AB3100 OTP functions"
628 depends on AB3100_CORE
629 default y if AB3100_CORE
630 help
631 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
632 programmable memory) support. This exposes a sysfs file to read
633 out OTP values.
634
Daniel Ribeiro13a09f92009-05-28 15:43:37 -0300[diff] [blame]635config EZX_PCAP
636 bool "PCAP Support"
637 depends on GENERIC_HARDIRQS && SPI_MASTER
638 help
639 This enables the PCAP ASIC present on EZX Phones. This is
640 needed for MMC, TouchScreen, Sound, USB, etc..
641
Mattias Wallin3d5e2ca2011-09-22 08:22:18 +0200[diff] [blame]642config AB5500_CORE
643 bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
644 depends on ABX500_CORE && MFD_DB5500_PRCMU
645 select MFD_CORE
646 help
647 Select this option to enable access to AB5500 power management
648 chip. This connects to the db5500 chip via the I2C bus via PRCMU.
649 This chip embeds various other multimedia funtionalities as well.
650
Linus Walleij94be70d2011-09-22 08:22:33 +0200[diff] [blame]651config AB5500_DEBUG
652 bool "Enable debug info via debugfs"
653 depends on AB5500_CORE && DEBUG_FS
654 default y if DEBUG_FS
655 help
656 Select this option if you want debug information from the AB5500
657 using the debug filesystem, debugfs.
658
Rabin Vincent62579262010-05-19 11:39:02 +0200[diff] [blame]659config AB8500_CORE
660 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
Sundar Iyer6680d942010-12-24 11:52:08 +0100[diff] [blame]661 depends on GENERIC_HARDIRQS && ABX500_CORE
Rabin Vincent62579262010-05-19 11:39:02 +0200[diff] [blame]662 select MFD_CORE
Srinidhi Kasagar0c418392009-10-12 17:11:52 +0200[diff] [blame]663 help
Rabin Vincent62579262010-05-19 11:39:02 +0200[diff] [blame]664 Select this option to enable access to AB8500 power management
Sundar Iyer6680d942010-12-24 11:52:08 +0100[diff] [blame]665 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
666 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
667 the irq_chip parts for handling the Mixed Signal chip events.
Srinidhi Kasagar0c418392009-10-12 17:11:52 +0200[diff] [blame]668 This chip embeds various other multimedia funtionalities as well.
669
Mattias Wallin39368ed2010-09-15 13:12:03 +0200[diff] [blame]670config AB8500_I2C_CORE
671 bool "AB8500 register access via PRCMU I2C"
Linus Walleij650c2a22011-05-15 22:53:56 +0200[diff] [blame]672 depends on AB8500_CORE && MFD_DB8500_PRCMU
Mattias Wallin39368ed2010-09-15 13:12:03 +0200[diff] [blame]673 default y
674 help
675 This enables register access to the AB8500 chip via PRCMU I2C.
676 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
677 the I2C bus is connected to the Power Reset
678 and Mangagement Unit, PRCMU.
679
Mattias Wallin5814fc32010-09-13 16:05:04 +0200[diff] [blame]680config AB8500_DEBUG
681 bool "Enable debug info via debugfs"
682 depends on AB8500_CORE && DEBUG_FS
683 default y if DEBUG_FS
684 help
685 Select this option if you want debug information using the debug
686 filesystem, debugfs.
687
Arun Murthydae2db32011-02-22 10:11:13 +0100[diff] [blame]688config AB8500_GPADC
689 bool "AB8500 GPADC driver"
690 depends on AB8500_CORE && REGULATOR_AB8500
691 default y
692 help
693 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
694
Linus Walleij650c2a22011-05-15 22:53:56 +0200[diff] [blame]695config MFD_DB8500_PRCMU
696 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
697 depends on UX500_SOC_DB8500
698 select MFD_CORE
699 help
700 Select this option to enable support for the DB8500 Power Reset
701 and Control Management Unit. This is basically an autonomous
702 system controller running an XP70 microprocessor, which is accessed
703 through a register map.
704
Linus Walleij83177972011-05-03 18:14:48 +0200[diff] [blame]705config MFD_DB5500_PRCMU
706 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
707 depends on UX500_SOC_DB5500
708 select MFD_CORE
709 help
710 Select this option to enable support for the DB5500 Power Reset
711 and Control Management Unit. This is basically an autonomous
712 system controller running an XP70 microprocessor, which is accessed
713 through a register map.
714
Andres Salomonf71e1af2010-11-26 11:52:35 +0100[diff] [blame]715config MFD_CS5535
716 tristate "Support for CS5535 and CS5536 southbridge core functions"
717 select MFD_CORE
Andres Salomon15b7cf12011-03-27 21:26:03 -0700[diff] [blame]718 depends on PCI && X86
Andres Salomonf71e1af2010-11-26 11:52:35 +0100[diff] [blame]719 ---help---
720 This is the core driver for CS5535/CS5536 MFD functions. This is
721 necessary for using the board's GPIO and MFGPT functionality.
722
Richard Röjfors8edbede2010-02-04 08:18:52 -0300[diff] [blame]723config MFD_TIMBERDALE
724 tristate "Support for the Timberdale FPGA"
725 select MFD_CORE
Randy Dunlap546e29b2010-02-12 12:30:55 -0300[diff] [blame]726 depends on PCI && GPIOLIB
Richard Röjfors8edbede2010-02-04 08:18:52 -0300[diff] [blame]727 ---help---
728 This is the core driver for the timberdale FPGA. This device is a
729 multifunction device which exposes numerous platform devices.
730
731 The timberdale FPGA can be found on the Intel Atom development board
732 for in-vehicle infontainment, called Russellville.
Denis Turischeve82c60a2010-02-19 11:26:25 +0100[diff] [blame]733
734config LPC_SCH
735 tristate "Intel SCH LPC"
736 depends on PCI
737 select MFD_CORE
738 help
739 LPC bridge function of the Intel SCH provides support for
740 System Management Bus and General Purpose I/O.
741
Florian Fainellie090d502010-03-21 01:06:05 +0100[diff] [blame]742config MFD_RDC321X
743 tristate "Support for RDC-R321x southbridge"
744 select MFD_CORE
745 depends on PCI
746 help
747 Say yes here if you want to have support for the RDC R-321x SoC
748 southbridge which provides access to GPIOs and Watchdog using the
749 southbridge PCI device configuration space.
750
Ira W. Snyderbd358132010-04-07 09:43:00 +0200[diff] [blame]751config MFD_JANZ_CMODIO
752 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
753 select MFD_CORE
754 depends on PCI
755 help
756 This is the core driver for the Janz CMOD-IO PCI MODULbus
757 carrier board. This device is a PCI to MODULbus bridge which may
758 host many different types of MODULbus daughterboards, including
759 CAN and GPIO controllers.
760
Lars-Peter Clausen91f4deb2010-07-12 03:48:08 +0200[diff] [blame]761config MFD_JZ4740_ADC
Lars-Peter Clausen914e6d42011-06-03 03:14:26 +0200[diff] [blame]762 bool "Support for the JZ4740 SoC ADC core"
Lars-Peter Clausen91f4deb2010-07-12 03:48:08 +0200[diff] [blame]763 select MFD_CORE
Lars-Peter Clausen914e6d42011-06-03 03:14:26 +0200[diff] [blame]764 select GENERIC_IRQ_CHIP
Lars-Peter Clausen91f4deb2010-07-12 03:48:08 +0200[diff] [blame]765 depends on MACH_JZ4740
766 help
767 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
768 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
769
Daniel Drake375fc772010-09-30 21:55:41 +0100[diff] [blame]770config MFD_VX855
771 tristate "Support for VIA VX855/VX875 integrated south bridge"
772 depends on PCI
773 select MFD_CORE
774 help
775 Say yes here to enable support for various functions of the
776 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
777 and/or vx855_gpio drivers for this to do anything useful.
778
Matti Aaltonen383268a2010-12-10 11:41:33 -0300[diff] [blame]779config MFD_WL1273_CORE
Matti Aaltonen94fd5b72011-03-01 10:10:35 -0300[diff] [blame]780 tristate "Support for TI WL1273 FM radio."
Matti Aaltonen383268a2010-12-10 11:41:33 -0300[diff] [blame]781 depends on I2C
782 select MFD_CORE
783 default n
784 help
785 This is the core driver for the TI WL1273 FM radio. This MFD
786 driver connects the radio-wl1273 V4L2 module and the wl1273
787 audio codec.
788
Keshava Munegowda17cdd292011-03-01 20:08:17 +0530[diff] [blame]789config MFD_OMAP_USB_HOST
790 bool "Support OMAP USBHS core driver"
791 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
792 default y
793 help
794 This is the core driver for the OAMP EHCI and OHCI drivers.
795 This MFD driver does the required setup functionalities for
796 OMAP USB Host drivers.
797
Abhijeet Dharmapurikarcbdb53e2011-04-05 14:40:52 -0700[diff] [blame]798config MFD_PM8XXX
799 tristate
800
801config MFD_PM8921_CORE
802 tristate "Qualcomm PM8921 PMIC chip"
803 depends on MSM_SSBI
804 select MFD_CORE
805 select MFD_PM8XXX
806 help
807 If you say yes to this option, support will be included for the
808 built-in PM8921 PMIC chip.
809
810 This is required if your board has a PM8921 and uses its features,
811 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
812
813 Say M here if you want to include support for PM8921 chip as a module.
814 This will build a module called "pm8921-core".
815
Abhijeet Dharmapurikarc013f0a2011-04-05 14:40:53 -0700[diff] [blame]816config MFD_PM8XXX_IRQ
817 bool "Support for Qualcomm PM8xxx IRQ features"
818 depends on MFD_PM8XXX
819 default y if MFD_PM8XXX
820 help
821 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
822
823 This is required to use certain other PM 8xxx features, such as GPIO
824 and MPP.
825
Axel Lin8509e142011-06-23 10:15:51 +0800[diff] [blame]826config TPS65911_COMPARATOR
827 tristate
828
Jin Park09d62922011-07-04 19:48:12 +0200[diff] [blame]829config MFD_AAT2870_CORE
830 bool "Support for the AnalogicTech AAT2870"
831 select MFD_CORE
832 depends on I2C=y && GPIOLIB
833 help
834 If you say yes here you get support for the AAT2870.
835 This driver provides common support for accessing the device,
836 additional drivers must be enabled in order to use the
837 functionality of the device.
838
Mika Westerberg1f5a3712011-09-21 13:03:07 +0200[diff] [blame]839config MFD_INTEL_MSIC
840 bool "Support for Intel MSIC"
841 depends on INTEL_SCU_IPC
842 select MFD_CORE
843 help
844 Select this option to enable access to Intel MSIC (Avatele
845 Passage) chip. This chip embeds audio, battery, GPIO, etc.
846 devices used in Intel Medfield platforms.
847
Arnd Bergmann8a0a8e82011-09-02 16:43:36 +0200[diff] [blame]848endmenu
849endif
Ben Dooksb6d64542007-02-20 13:58:01 -0800[diff] [blame]850
Russell Kinga4e137a2005-08-18 10:06:59 +0100[diff] [blame]851menu "Multimedia Capabilities Port drivers"
Adrian Bunkf751d502006-03-24 03:18:21 -0800[diff] [blame]852 depends on ARCH_SA1100
Russell Kinga4e137a2005-08-18 10:06:59 +0100[diff] [blame]853
854config MCP
855 tristate
856
Russell King5e742ad2005-08-18 10:08:15 +0100[diff] [blame]857# Interface drivers
858config MCP_SA11X0
859 tristate "Support SA11x0 MCP interface"
860 depends on ARCH_SA1100
861 select MCP
862
Russell King05c45ca2005-09-11 10:26:31 +0100[diff] [blame]863# Chip drivers
864config MCP_UCB1200
865 tristate "Support for UCB1200 / UCB1300"
866 depends on MCP
867
Russell Kingacb45432005-09-11 10:26:57 +0100[diff] [blame]868config MCP_UCB1200_TS
869 tristate "Touchscreen interface support"
870 depends on MCP_UCB1200 && INPUT
871
Russell Kinga4e137a2005-08-18 10:06:59 +0100[diff] [blame]872endmenu