mfd: Don't try to flag IRQ 0 as a wm831x wake source
[deliverable/linux.git] / drivers / mfd / Kconfig
CommitLineData
a4e137ab
RK
1#
2# Multifunction miscellaneous devices
3#
4
8a0a8e8e
AB
5if HAS_IOMEM
6menu "Multifunction device drivers"
b6d6454f 7
aa613de6
DB
8config MFD_CORE
9 tristate
10 default n
11
2cc50bee
HZ
12config MFD_88PM860X
13 bool "Support Marvell 88PM8606/88PM8607"
8d002bdc 14 depends on I2C=y && GENERIC_HARDIRQS
b46a36c0 15 select REGMAP_I2C
2cc50bee
HZ
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
b6d6454f
BD
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
01dd2fbf
ML
28 provide numerous interfaces including USB host controller, USB gadget,
29 asynchronous serial ports, audio functions, and a dual display video
b6d6454f
BD
30 interface. The device may be connected by PCI or local bus with
31 varying functions enabled.
32
f61be273
BD
33config MFD_SM501_GPIO
34 bool "Export GPIO via GPIO layer"
2eedd604 35 depends on MFD_SM501 && GPIOLIB
f61be273
BD
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
fa9ff4b1
SO
41config MFD_ASIC3
42 bool "Support for Compaq ASIC3"
2eedd604 43 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
9461f65a 44 select MFD_CORE
fa9ff4b1
SO
45 ---help---
46 This driver supports the ASIC3 multifunction chip found on many
47 PDAs (mainly iPAQ and HTC based ones)
48
ca26308c
MA
49config MFD_DAVINCI_VOICECODEC
50 tristate
51 select MFD_CORE
52
0931a4c6
DB
53config MFD_DM355EVM_MSP
54 bool "DaVinci DM355 EVM microcontroller"
1819ebcf 55 depends on I2C=y && MACH_DAVINCI_DM355_EVM
0931a4c6
DB
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
03df0f62
CC
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
a1635b8f
PZ
72config HTC_EGPIO
73 bool "HTC EGPIO support"
7444a72e 74 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
a1635b8f
PZ
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
5dc3339a
PZ
80config HTC_PASIC3
81 tristate "HTC PASIC3 LED/DS1WM chip support"
0254a8f4 82 select MFD_CORE
5dc3339a
PZ
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
6048a3dd
CM
89config HTC_I2CPLD
90 bool "HTC I2C PLD chip support"
bef3e20c 91 depends on I2C=y && GPIOLIB
6048a3dd
CM
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
d9105c2b
MV
98config UCB1400_CORE
99 tristate "Philips UCB1400 Core driver"
e4831802 100 depends on AC97_BUS
5a49a540 101 depends on GPIOLIB
d9105c2b
MV
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
16c5c023
JH
109config MFD_LM3533
110 tristate "LM3533 Lighting Power chip"
111 depends on I2C
112 select MFD_CORE
113 select REGMAP_I2C
114 help
115 Say yes here to enable support for National Semiconductor / TI
116 LM3533 Lighting Power chips.
117
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.
121
798a8eee
LW
122config TPS6105X
123 tristate "TPS61050/61052 Boost Converters"
124 depends on I2C
2edd3b69 125 select REGULATOR
fc498fa2 126 select MFD_CORE
2edd3b69 127 select REGULATOR_FIXED_VOLTAGE
798a8eee
LW
128 help
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.
133
87c13493
DB
134config TPS65010
135 tristate "TPS6501x Power Management chips"
136 depends on I2C && GPIOLIB
137 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
138 help
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.
143
144 This driver can also be built as a module. If so, the module
145 will be called tps65010.
146
31dd6a26
TF
147config TPS6507X
148 tristate "TPS6507x Power Management / Touch Screen chips"
149 select MFD_CORE
150 depends on I2C
151 help
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.
158
d48f411c
AC
159config MFD_TPS65217
160 tristate "TPS65217 Power Management / White LED chips"
161 depends on I2C
162 select MFD_CORE
163 select REGMAP_I2C
164 help
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
169 devices.
170
171 This driver can also be built as a module. If so, the module
172 will be called tps65217.
173
37df003c
AL
174config MFD_TPS6586X
175 bool "TPS6586x Power Management chips"
176 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
177 select MFD_CORE
178 help
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.
184
185 This driver can also be built as a module. If so, the module
186 will be called tps6586x.
187
54f323b1
LW
188config MFD_TPS65910
189 bool "TPS65910 Power Management chip"
190 depends on I2C=y && GPIOLIB
191 select MFD_CORE
dc9913a0 192 select REGMAP_I2C
54f323b1
LW
193 help
194 if you say yes here you get support for the TPS65910 series of
195 Power Management chips.
196
36e52873 197config MFD_TPS65912
5608801b 198 bool
36e52873
MO
199 depends on GPIOLIB
200
201config MFD_TPS65912_I2C
231dd9c8 202 bool "TPS65912 Power Management chip with I2C"
36e52873
MO
203 select MFD_CORE
204 select MFD_TPS65912
205 depends on I2C=y && GPIOLIB
206 help
207 If you say yes here you get support for the TPS65912 series of
208 PM chips with I2C interface.
209
210config MFD_TPS65912_SPI
211 bool "TPS65912 Power Management chip with SPI"
212 select MFD_CORE
213 select MFD_TPS65912
214 depends on SPI_MASTER && GPIOLIB
215 help
216 If you say yes here you get support for the TPS65912 series of
217 PM chips with SPI interface.
218
88e75cc3
DB
219config MENELAUS
220 bool "Texas Instruments TWL92330/Menelaus PM chip"
088ef950 221 depends on I2C=y && ARCH_OMAP2
88e75cc3
DB
222 help
223 If you say yes here you get support for the Texas Instruments
224 TWL92330/Menelaus Power Management chip. This include voltage
692105b8 225 regulators, Dual slot memory card transceivers, real-time clock
88e75cc3
DB
226 and other features that are often used in portable devices like
227 cell phones and PDAs.
228
a603a7fa 229config TWL4030_CORE
e8deb28c 230 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
6252547b 231 depends on I2C=y && GENERIC_HARDIRQS
280ad7fd 232 select IRQ_DOMAIN
a603a7fa 233 help
e8deb28c 234 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
a603a7fa
DB
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.
238
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.
243
f99c1d4f
K
244config TWL4030_MADC
245 tristate "Texas Instruments TWL4030 MADC"
246 depends on TWL4030_CORE
247 help
248 This driver provides support for triton TWL4030-MADC. The
249 driver supports both RT and SW conversion methods.
250
251 This driver can be built as a module. If so it will be
252 named twl4030-madc
253
ebf0bd36
AK
254config TWL4030_POWER
255 bool "Support power resources on TWL4030 family chips"
256 depends on TWL4030_CORE && ARM
257 help
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.
262
263 This driver uses board-specific data to initialize the resources
25985edc 264 and load scripts controlling which resources are switched off/on
ebf0bd36
AK
265 or reset when a sleep, wakeup or warm reset event occurs.
266
57fe7251 267config MFD_TWL4030_AUDIO
0b83ddeb
PU
268 bool
269 depends on TWL4030_CORE
270 select MFD_CORE
271 default n
272
31fc03df
H
273config TWL6030_PWM
274 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
275 depends on TWL4030_CORE
276 select HAVE_PWM
277 default n
278 help
279 Say yes here if you want support for TWL6030 PWM.
280 This is used to control charging LED brightness.
281
f19b2823 282config TWL6040_CORE
8eaeb939
PU
283 bool "Support for TWL6040 audio codec"
284 depends on I2C=y && GENERIC_HARDIRQS
f19b2823 285 select MFD_CORE
8eaeb939 286 select REGMAP_I2C
f19b2823 287 default n
8eaeb939
PU
288 help
289 Say yes here if you want support for Texas Instruments TWL6040 audio
290 codec.
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).
f19b2823 294
27e34995
RV
295config MFD_STMPE
296 bool "Support STMicroelectronics STMPE"
e789995d 297 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
27e34995
RV
298 select MFD_CORE
299 help
300 Support for the STMPE family of I/O Expanders from
301 STMicroelectronics.
302
303 Currently supported devices are:
304
305 STMPE811: GPIO, Touchscreen
306 STMPE1601: GPIO, Keypad
307 STMPE2401: GPIO, Keypad
308 STMPE2403: GPIO, Keypad
309
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:
313
314 GPIO: stmpe-gpio
315 Keypad: stmpe-keypad
316 Touchscreen: stmpe-ts
317
1a6e4b74
VK
318menu "STMPE Interface Drivers"
319depends on MFD_STMPE
320
321config STMPE_I2C
322 bool "STMPE I2C Inteface"
eedea80f 323 depends on I2C=y
1a6e4b74
VK
324 default y
325 help
326 This is used to enable I2C interface of STMPE
e789995d
VK
327
328config STMPE_SPI
329 bool "STMPE SPI Inteface"
330 depends on SPI_MASTER
331 help
332 This is used to enable SPI interface of STMPE
1a6e4b74
VK
333endmenu
334
f4e8afdc
SI
335config MFD_TC3589X
336 bool "Support Toshiba TC35892 and variants"
b4ecd326
RV
337 depends on I2C=y && GENERIC_HARDIRQS
338 select MFD_CORE
339 help
f4e8afdc 340 Support for the Toshiba TC35892 and variants I/O Expander.
b4ecd326
RV
341
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.
345
1c2c30ac
SO
346config MFD_TMIO
347 bool
348 default n
349
1f192015
IM
350config MFD_T7L66XB
351 bool "Support Toshiba T7L66XB"
9ca68233 352 depends on ARM && HAVE_CLK
1f192015 353 select MFD_CORE
1c2c30ac 354 select MFD_TMIO
1f192015
IM
355 help
356 Support for Toshiba Mobile IO Controller T7L66XB
357
cbdfb426
IM
358config MFD_TC6387XB
359 bool "Support Toshiba TC6387XB"
9ca68233 360 depends on ARM && HAVE_CLK
cbdfb426 361 select MFD_CORE
1c2c30ac 362 select MFD_TMIO
cbdfb426
IM
363 help
364 Support for Toshiba Mobile IO Controller TC6387XB
365
d6315949
DB
366config MFD_TC6393XB
367 bool "Support Toshiba TC6393XB"
e959da10 368 depends on GPIOLIB && ARM && HAVE_CLK
f024ff10 369 select MFD_CORE
1c2c30ac 370 select MFD_TMIO
d6315949
DB
371 help
372 Support for Toshiba Mobile IO Controller TC6393XB
373
8e2eaabf
SO
374config PMIC_DA903X
375 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
376 depends on I2C=y
377 help
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.
a5736e0b 384
84c99db8
AJ
385config PMIC_DA9052
386 bool
387 select MFD_CORE
388
cfe04478
AJ
389config MFD_DA9052_SPI
390 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
391 select REGMAP_SPI
392 select REGMAP_IRQ
393 select PMIC_DA9052
394 depends on SPI_MASTER=y
395 help
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.
400
84c99db8
AJ
401config MFD_DA9052_I2C
402 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
403 select REGMAP_I2C
404 select REGMAP_IRQ
405 select PMIC_DA9052
406 depends on I2C=y
407 help
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.
412
a5736e0b
MH
413config PMIC_ADP5520
414 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
415 depends on I2C=y
416 help
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.
8e2eaabf 422
83871c00
CC
423config MFD_MAX77693
424 bool "Maxim Semiconductor MAX77693 PMIC Support"
425 depends on I2C=y && GENERIC_HARDIRQS
426 select MFD_CORE
427 help
428 Say yes here to support for Maxim Semiconductor MAX77693.
429 This is a companion Power Management IC with Flash, Haptic, Charger,
430 and MUIC(Micro USB Interface Controller) controls on chip.
431 This driver provides common support for accessing the device;
432 additional drivers must be enabled in order to use the functionality
433 of the device.
434
d50f8f33 435config MFD_MAX8925
1f1cf8f9 436 bool "Maxim Semiconductor MAX8925 PMIC Support"
8d002bdc 437 depends on I2C=y && GENERIC_HARDIRQS
1ad99893 438 select MFD_CORE
d50f8f33
HZ
439 help
440 Say yes here to support for Maxim Semiconductor MAX8925. This is
441 a Power Management IC. This driver provies common support for
442 accessing the device, additional drivers must be enabled in order
443 to use the functionality of the device.
444
527e7e9a
MH
445config MFD_MAX8997
446 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
447 depends on I2C=y && GENERIC_HARDIRQS
448 select MFD_CORE
449 help
5a924d13 450 Say yes here to support for Maxim Semiconductor MAX8997/8966.
527e7e9a
MH
451 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
452 MUIC controls on chip.
d7e8c01a 453 This driver provides common support for accessing the device;
527e7e9a
MH
454 additional drivers must be enabled in order to use the functionality
455 of the device.
456
156f2528 457config MFD_MAX8998
f8539ddc 458 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
2c7e6f57 459 depends on I2C=y && GENERIC_HARDIRQS
156f2528
KP
460 select MFD_CORE
461 help
f8539ddc
KP
462 Say yes here to support for Maxim Semiconductor MAX8998 and
463 National Semiconductor LP3974. This is a Power Management IC.
464 This driver provies common support for accessing the device,
465 additional drivers must be enabled in order to use the functionality
466 of the device.
156f2528 467
c3d4d697
SK
468config MFD_S5M_CORE
469 bool "SAMSUNG S5M Series Support"
470 depends on I2C=y && GENERIC_HARDIRQS
471 select MFD_CORE
472 select REGMAP_I2C
473 help
474 Support for the Samsung Electronics S5M MFD series.
475 This driver provies common support for accessing the device,
476 additional drivers must be enabled in order to use the functionality
477 of the device
478
1d9f9f04 479config MFD_WM8400
eee0e4b4 480 bool "Support Wolfson Microelectronics WM8400"
b8380c1a 481 select MFD_CORE
9c366452 482 depends on I2C
2b247d06 483 select REGMAP_I2C
1d9f9f04
MB
484 help
485 Support for the Wolfson Microelecronics WM8400 PMIC and audio
9e5aca58 486 CODEC. This driver provides common support for accessing
1d9f9f04
MB
487 the device, additional drivers must be enabled in order to use
488 the functionality of the device.
489
b11062b9 490config MFD_WM831X
e5b48684
MB
491 bool
492 depends on GENERIC_HARDIRQS
493
494config MFD_WM831X_I2C
495 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
b11062b9 496 select MFD_CORE
e5b48684 497 select MFD_WM831X
1df5981b 498 select REGMAP_I2C
8d002bdc 499 depends on I2C=y && GENERIC_HARDIRQS
b11062b9 500 help
e5b48684
MB
501 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
502 when controlled using I2C. 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.
b11062b9 505
2aa13b9e
MB
506config MFD_WM831X_SPI
507 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
508 select MFD_CORE
509 select MFD_WM831X
1df5981b 510 select REGMAP_SPI
2aa13b9e
MB
511 depends on SPI_MASTER && GENERIC_HARDIRQS
512 help
513 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
514 when controlled using SPI. This driver provides common support
515 for accessing the device, additional drivers must be enabled in
516 order to use the functionality of the device.
517
89b4012b 518config MFD_WM8350
ecf926bc 519 bool
8d002bdc 520 depends on GENERIC_HARDIRQS
89b4012b
MB
521
522config MFD_WM8350_CONFIG_MODE_0
523 bool
524 depends on MFD_WM8350
525
526config MFD_WM8350_CONFIG_MODE_1
527 bool
528 depends on MFD_WM8350
529
530config MFD_WM8350_CONFIG_MODE_2
531 bool
532 depends on MFD_WM8350
533
534config MFD_WM8350_CONFIG_MODE_3
535 bool
536 depends on MFD_WM8350
537
ca23f8c1
MB
538config MFD_WM8351_CONFIG_MODE_0
539 bool
540 depends on MFD_WM8350
541
542config MFD_WM8351_CONFIG_MODE_1
543 bool
544 depends on MFD_WM8350
545
546config MFD_WM8351_CONFIG_MODE_2
547 bool
548 depends on MFD_WM8350
549
550config MFD_WM8351_CONFIG_MODE_3
551 bool
552 depends on MFD_WM8350
553
96920630
MB
554config MFD_WM8352_CONFIG_MODE_0
555 bool
556 depends on MFD_WM8350
557
558config MFD_WM8352_CONFIG_MODE_1
559 bool
560 depends on MFD_WM8350
561
562config MFD_WM8352_CONFIG_MODE_2
563 bool
564 depends on MFD_WM8350
565
566config MFD_WM8352_CONFIG_MODE_3
567 bool
568 depends on MFD_WM8350
569
c661a0b9 570config MFD_WM8350_I2C
ecf926bc 571 bool "Support Wolfson Microelectronics WM8350 with I2C"
c661a0b9 572 select MFD_WM8350
8d002bdc 573 depends on I2C=y && GENERIC_HARDIRQS
c661a0b9
MB
574 help
575 The WM8350 is an integrated audio and power management
576 subsystem with watchdog and RTC functionality for embedded
577 systems. This option enables core support for the WM8350 with
578 I2C as the control interface. Additional options must be
579 selected to enable support for the functionality of the chip.
580
9e501086 581config MFD_WM8994
c9fbf7e0 582 bool "Support Wolfson Microelectronics WM8994"
9e501086 583 select MFD_CORE
d6c645fc 584 select REGMAP_I2C
8ab30691 585 select REGMAP_IRQ
c9fbf7e0 586 depends on I2C=y && GENERIC_HARDIRQS
9e501086
MB
587 help
588 The WM8994 is a highly integrated hi-fi CODEC designed for
589 smartphone applicatiosn. As well as audio functionality it
590 has on board GPIO and regulator functionality which is
591 supported via the relevant subsystems. This driver provides
592 core support for the WM8994, in order to use the actual
593 functionaltiy of the device other drivers must be enabled.
594
f52046b1
BR
595config MFD_PCF50633
596 tristate "Support for NXP PCF50633"
597 depends on I2C
6e3ad118 598 select REGMAP_I2C
f52046b1
BR
599 help
600 Say yes here if you have NXP PCF50633 chip on your board.
601 This core driver provides register access and IRQ handling
602 facilities, and registers devices for the various functions
603 so that function-specific drivers can bind to them.
604
1305134e
AL
605config PCF50633_ADC
606 tristate "Support for NXP PCF50633 ADC"
607 depends on MFD_PCF50633
608 help
609 Say yes here if you want to include support for ADC in the
610 NXP PCF50633 chip.
611
612config PCF50633_GPIO
613 tristate "Support for NXP PCF50633 GPIO"
614 depends on MFD_PCF50633
615 help
616 Say yes here if you want to include support GPIO for pins on
617 the PCF50633 chip.
618
8238addc 619config MFD_MC13783
8e005935
UKK
620 tristate
621
622config MFD_MC13XXX
623 tristate "Support Freescale MC13783 and MC13892"
df3df646 624 depends on SPI_MASTER || I2C
8238addc 625 select MFD_CORE
8e005935 626 select MFD_MC13783
8238addc 627 help
a0c7c1d4
MR
628 Enable support for the Freescale MC13783 and MC13892 PMICs.
629 This driver provides common support for accessing the device,
8238addc
SH
630 additional drivers must be enabled in order to use the
631 functionality of the device.
632
a0c7c1d4
MR
633if MFD_MC13XXX
634
635config MFD_MC13XXX_SPI
636 tristate "MC13xxx SPI interface" if SPI_MASTER
637 default SPI_MASTER
638 select REGMAP_SPI
639 help
640 Select this if your MC13xxx is connected via an SPI bus.
641
df3df646
MR
642config MFD_MC13XXX_I2C
643 tristate "MC13xxx I2C interface" if I2C
644 default I2C
645 select REGMAP_I2C
646 help
647 Select this if your MC13xxx is connected via an I2C bus.
648
a0c7c1d4
MR
649endif
650
fa661258
MW
651config ABX500_CORE
652 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
47c16975 653 default y if ARCH_U300 || ARCH_U8500
fa661258
MW
654 help
655 Say yes here if you have the ABX500 Mixed Signal IC family
656 chips. This core driver expose register access functions.
657 Functionality specific drivers using these functions can
658 remain unchanged when IC changes. Binding of the functions to
659 actual register access is done by the IC core driver.
660
14fa5691 661config AB3100_CORE
2071db48 662 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
fa661258 663 depends on I2C=y && ABX500_CORE
8c96aefb 664 select MFD_CORE
14fa5691
LW
665 default y if ARCH_U300
666 help
667 Select this to enable the AB3100 Mixed Signal IC core
668 functionality. This connects to a AB3100 on the I2C bus
669 and expose a number of symbols needed for dependent devices
670 to read and write registers and subscribe to events from
671 this multi-functional IC. This is needed to use other features
672 of the AB3100 such as battery-backed RTC, charging control,
673 LEDs, vibrator, system power and temperature, power management
674 and ALSA sound.
675
12992dd8
LW
676config AB3100_OTP
677 tristate "ST-Ericsson AB3100 OTP functions"
678 depends on AB3100_CORE
679 default y if AB3100_CORE
680 help
681 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
682 programmable memory) support. This exposes a sysfs file to read
683 out OTP values.
684
13a09f93
DR
685config EZX_PCAP
686 bool "PCAP Support"
687 depends on GENERIC_HARDIRQS && SPI_MASTER
688 help
689 This enables the PCAP ASIC present on EZX Phones. This is
690 needed for MMC, TouchScreen, Sound, USB, etc..
691
3d5e2cab
MW
692config AB5500_CORE
693 bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
694 depends on ABX500_CORE && MFD_DB5500_PRCMU
695 select MFD_CORE
696 help
697 Select this option to enable access to AB5500 power management
698 chip. This connects to the db5500 chip via the I2C bus via PRCMU.
699 This chip embeds various other multimedia funtionalities as well.
700
94be70d4
LW
701config AB5500_DEBUG
702 bool "Enable debug info via debugfs"
703 depends on AB5500_CORE && DEBUG_FS
704 default y if DEBUG_FS
705 help
706 Select this option if you want debug information from the AB5500
707 using the debug filesystem, debugfs.
708
62579266
RV
709config AB8500_CORE
710 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
6680d940 711 depends on GENERIC_HARDIRQS && ABX500_CORE
62579266 712 select MFD_CORE
0c41839e 713 help
62579266 714 Select this option to enable access to AB8500 power management
6680d940
SI
715 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
716 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
717 the irq_chip parts for handling the Mixed Signal chip events.
0c41839e
SK
718 This chip embeds various other multimedia funtionalities as well.
719
39368eda
MW
720config AB8500_I2C_CORE
721 bool "AB8500 register access via PRCMU I2C"
650c2a21 722 depends on AB8500_CORE && MFD_DB8500_PRCMU
39368eda
MW
723 default y
724 help
725 This enables register access to the AB8500 chip via PRCMU I2C.
726 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
727 the I2C bus is connected to the Power Reset
728 and Mangagement Unit, PRCMU.
729
5814fc35
MW
730config AB8500_DEBUG
731 bool "Enable debug info via debugfs"
732 depends on AB8500_CORE && DEBUG_FS
733 default y if DEBUG_FS
734 help
735 Select this option if you want debug information using the debug
736 filesystem, debugfs.
dae2db30
AM
737
738config AB8500_GPADC
739 bool "AB8500 GPADC driver"
740 depends on AB8500_CORE && REGULATOR_AB8500
741 default y
742 help
743 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
5814fc35 744
650c2a21
LW
745config MFD_DB8500_PRCMU
746 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
747 depends on UX500_SOC_DB8500
748 select MFD_CORE
749 help
750 Select this option to enable support for the DB8500 Power Reset
751 and Control Management Unit. This is basically an autonomous
752 system controller running an XP70 microprocessor, which is accessed
753 through a register map.
754
8317797c
LW
755config MFD_DB5500_PRCMU
756 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
757 depends on UX500_SOC_DB5500
758 select MFD_CORE
759 help
760 Select this option to enable support for the DB5500 Power Reset
761 and Control Management Unit. This is basically an autonomous
762 system controller running an XP70 microprocessor, which is accessed
763 through a register map.
764
f71e1afd
AS
765config MFD_CS5535
766 tristate "Support for CS5535 and CS5536 southbridge core functions"
767 select MFD_CORE
15b7cf14 768 depends on PCI && X86
f71e1afd
AS
769 ---help---
770 This is the core driver for CS5535/CS5536 MFD functions. This is
771 necessary for using the board's GPIO and MFGPT functionality.
772
8edbede9
RR
773config MFD_TIMBERDALE
774 tristate "Support for the Timberdale FPGA"
775 select MFD_CORE
546e29b6 776 depends on PCI && GPIOLIB
8edbede9
RR
777 ---help---
778 This is the core driver for the timberdale FPGA. This device is a
779 multifunction device which exposes numerous platform devices.
780
781 The timberdale FPGA can be found on the Intel Atom development board
782 for in-vehicle infontainment, called Russellville.
e82c60ae
DT
783
784config LPC_SCH
785 tristate "Intel SCH LPC"
786 depends on PCI
787 select MFD_CORE
788 help
789 LPC bridge function of the Intel SCH provides support for
790 System Management Bus and General Purpose I/O.
791
4630b130
AS
792config LPC_ICH
793 tristate "Intel ICH LPC"
794 depends on PCI
795 select MFD_CORE
796 help
797 The LPC bridge function of the Intel ICH provides support for
798 many functional units. This driver provides needed support for
887c8ec7
AS
799 other drivers to control these functions, currently GPIO and
800 watchdog.
4630b130 801
e090d506
FF
802config MFD_RDC321X
803 tristate "Support for RDC-R321x southbridge"
804 select MFD_CORE
805 depends on PCI
806 help
807 Say yes here if you want to have support for the RDC R-321x SoC
808 southbridge which provides access to GPIOs and Watchdog using the
809 southbridge PCI device configuration space.
810
bd358132
IS
811config MFD_JANZ_CMODIO
812 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
813 select MFD_CORE
814 depends on PCI
815 help
816 This is the core driver for the Janz CMOD-IO PCI MODULbus
817 carrier board. This device is a PCI to MODULbus bridge which may
818 host many different types of MODULbus daughterboards, including
819 CAN and GPIO controllers.
820
91f4debf 821config MFD_JZ4740_ADC
914e6d4e 822 bool "Support for the JZ4740 SoC ADC core"
91f4debf 823 select MFD_CORE
914e6d4e 824 select GENERIC_IRQ_CHIP
91f4debf
LPC
825 depends on MACH_JZ4740
826 help
827 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
828 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
829
375fc77b
DD
830config MFD_VX855
831 tristate "Support for VIA VX855/VX875 integrated south bridge"
832 depends on PCI
833 select MFD_CORE
834 help
835 Say yes here to enable support for various functions of the
836 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
837 and/or vx855_gpio drivers for this to do anything useful.
838
383268a8 839config MFD_WL1273_CORE
94fd5b74 840 tristate "Support for TI WL1273 FM radio."
383268a8
MA
841 depends on I2C
842 select MFD_CORE
843 default n
844 help
845 This is the core driver for the TI WL1273 FM radio. This MFD
846 driver connects the radio-wl1273 V4L2 module and the wl1273
847 audio codec.
848
17cdd29d
KM
849config MFD_OMAP_USB_HOST
850 bool "Support OMAP USBHS core driver"
851 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
852 default y
853 help
854 This is the core driver for the OAMP EHCI and OHCI drivers.
855 This MFD driver does the required setup functionalities for
856 OMAP USB Host drivers.
857
cbdb53e1
AD
858config MFD_PM8XXX
859 tristate
860
861config MFD_PM8921_CORE
862 tristate "Qualcomm PM8921 PMIC chip"
863 depends on MSM_SSBI
864 select MFD_CORE
865 select MFD_PM8XXX
866 help
867 If you say yes to this option, support will be included for the
868 built-in PM8921 PMIC chip.
869
870 This is required if your board has a PM8921 and uses its features,
871 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
872
873 Say M here if you want to include support for PM8921 chip as a module.
874 This will build a module called "pm8921-core".
875
c013f0a5
AD
876config MFD_PM8XXX_IRQ
877 bool "Support for Qualcomm PM8xxx IRQ features"
878 depends on MFD_PM8XXX
879 default y if MFD_PM8XXX
880 help
881 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
882
883 This is required to use certain other PM 8xxx features, such as GPIO
884 and MPP.
885
8509e142
AL
886config TPS65911_COMPARATOR
887 tristate
888
3c33be06
VB
889config MFD_TPS65090
890 bool "TPS65090 Power Management chips"
891 depends on I2C=y && GENERIC_HARDIRQS
892 select MFD_CORE
893 select REGMAP_I2C
894 help
895 If you say yes here you get support for the TPS65090 series of
896 Power Management chips.
897 This driver provides common support for accessing the device,
898 additional drivers must be enabled in order to use the
899 functionality of the device.
900
09d6292b
JP
901config MFD_AAT2870_CORE
902 bool "Support for the AnalogicTech AAT2870"
903 select MFD_CORE
904 depends on I2C=y && GPIOLIB
905 help
906 If you say yes here you get support for the AAT2870.
907 This driver provides common support for accessing the device,
908 additional drivers must be enabled in order to use the
909 functionality of the device.
910
1f5a371c
MW
911config MFD_INTEL_MSIC
912 bool "Support for Intel MSIC"
913 depends on INTEL_SCU_IPC
914 select MFD_CORE
915 help
916 Select this option to enable access to Intel MSIC (Avatele
917 Passage) chip. This chip embeds audio, battery, GPIO, etc.
918 devices used in Intel Medfield platforms.
919
1b1247dd
LD
920config MFD_RC5T583
921 bool "Ricoh RC5T583 Power Management system device"
5364d0b8 922 depends on I2C=y && GENERIC_HARDIRQS
1b1247dd
LD
923 select MFD_CORE
924 select REGMAP_I2C
925 help
926 Select this option to get support for the RICOH583 Power
927 Management system device.
928 This driver provides common support for accessing the device
929 through i2c interface. The device supports multiple sub-devices
930 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
931 Additional drivers must be enabled in order to use the
932 different functionality of the device.
933
35bdd290
AR
934config MFD_STA2X11
935 bool "STA2X11 multi function device support"
936 depends on STA2X11
937 select MFD_CORE
938
75060a1d
YCLP
939config MFD_ANATOP
940 bool "Support for Freescale i.MX on-chip ANATOP controller"
941 depends on SOC_IMX6Q
942 help
943 Select this option to enable Freescale i.MX on-chip ANATOP
944 MFD controller. This controller embeds regulator and
945 thermal devices for Freescale i.MX platforms.
946
8a0a8e8e
AB
947endmenu
948endif
b6d6454f 949
a4e137ab 950menu "Multimedia Capabilities Port drivers"
f751d50f 951 depends on ARCH_SA1100
a4e137ab
RK
952
953config MCP
954 tristate
955
5e742ad6
RK
956# Interface drivers
957config MCP_SA11X0
958 tristate "Support SA11x0 MCP interface"
959 depends on ARCH_SA1100
960 select MCP
961
05c45ca9
RK
962# Chip drivers
963config MCP_UCB1200
a3364409
RK
964 bool "Support for UCB1200 / UCB1300"
965 depends on MCP_SA11X0
966 select MCP
05c45ca9 967
acb45439
RK
968config MCP_UCB1200_TS
969 tristate "Touchscreen interface support"
970 depends on MCP_UCB1200 && INPUT
971
a4e137ab 972endmenu
This page took 0.659498 seconds and 5 git commands to generate.