projects / deliverable / linux.git / blame_incremental
? search:
summary | shortlog | log | commit | commitdiff | tree
blob | blame (non-incremental) | history | HEAD
mfd: Fix arizona-irq.c build by selecting REGMAP_IRQ
[deliverable/linux.git] / drivers / mfd / Kconfig
... / ...
CommitLineData
1#
2# Multifunction miscellaneous devices
3#
4
5if HAS_IOMEM
6menu "Multifunction device drivers"
7
8config MFD_CORE
9 tristate
10 select IRQ_DOMAIN
11 default n
12
13config MFD_88PM860X
14 bool "Support Marvell 88PM8606/88PM8607"
15 depends on I2C=y && GENERIC_HARDIRQS
16 select REGMAP_I2C
17 select MFD_CORE
18 help
19 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
20 This includes the I2C driver and the core APIs _only_, you have to
21 select individual components like voltage regulators, RTC and
22 battery-charger under the corresponding menus.
23
24config MFD_88PM800
25 tristate "Support Marvell 88PM800"
26 depends on I2C=y && GENERIC_HARDIRQS
27 select REGMAP_I2C
28 select REGMAP_IRQ
29 select MFD_CORE
30 help
31 This supports for Marvell 88PM800 Power Management IC.
32 This includes the I2C driver and the core APIs _only_, you have to
33 select individual components like voltage regulators, RTC and
34 battery-charger under the corresponding menus.
35
36config MFD_88PM805
37 tristate "Support Marvell 88PM805"
38 depends on I2C=y && GENERIC_HARDIRQS
39 select REGMAP_I2C
40 select REGMAP_IRQ
41 select MFD_CORE
42 help
43 This supports for Marvell 88PM805 Power Management IC. This includes
44 the I2C driver and the core APIs _only_, you have to select individual
45 components like codec device, headset/Mic device under the
46 corresponding menus.
47
48config MFD_SM501
49 tristate "Support for Silicon Motion SM501"
50 ---help---
51 This is the core driver for the Silicon Motion SM501 multimedia
52 companion chip. This device is a multifunction device which may
53 provide numerous interfaces including USB host controller, USB gadget,
54 asynchronous serial ports, audio functions, and a dual display video
55 interface. The device may be connected by PCI or local bus with
56 varying functions enabled.
57
58config MFD_SM501_GPIO
59 bool "Export GPIO via GPIO layer"
60 depends on MFD_SM501 && GPIOLIB
61 ---help---
62 This option uses the gpio library layer to export the 64 GPIO
63 lines on the SM501. The platform data is used to supply the
64 base number for the first GPIO line to register.
65
66config MFD_ASIC3
67 bool "Support for Compaq ASIC3"
68 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
69 select MFD_CORE
70 ---help---
71 This driver supports the ASIC3 multifunction chip found on many
72 PDAs (mainly iPAQ and HTC based ones)
73
74config MFD_DAVINCI_VOICECODEC
75 tristate
76 select MFD_CORE
77
78config MFD_DM355EVM_MSP
79 bool "DaVinci DM355 EVM microcontroller"
80 depends on I2C=y && MACH_DAVINCI_DM355_EVM
81 help
82 This driver supports the MSP430 microcontroller used on these
83 boards. MSP430 firmware manages resets and power sequencing,
84 inputs from buttons and the IR remote, LEDs, an RTC, and more.
85
86config MFD_TI_SSP
87 tristate "TI Sequencer Serial Port support"
88 depends on ARCH_DAVINCI_TNETV107X
89 select MFD_CORE
90 ---help---
91 Say Y here if you want support for the Sequencer Serial Port
92 in a Texas Instruments TNETV107X SoC.
93
94 To compile this driver as a module, choose M here: the
95 module will be called ti-ssp.
96
97config HTC_EGPIO
98 bool "HTC EGPIO support"
99 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
100 help
101 This driver supports the CPLD egpio chip present on
102 several HTC phones. It provides basic support for input
103 pins, output pins, and irqs.
104
105config HTC_PASIC3
106 tristate "HTC PASIC3 LED/DS1WM chip support"
107 select MFD_CORE
108 help
109 This core driver provides register access for the LED/DS1WM
110 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
111 HTC Magician devices, respectively. Actual functionality is
112 handled by the leds-pasic3 and ds1wm drivers.
113
114config HTC_I2CPLD
115 bool "HTC I2C PLD chip support"
116 depends on I2C=y && GPIOLIB
117 help
118 If you say yes here you get support for the supposed CPLD
119 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
120 This device provides input and output GPIOs through an I2C
121 interface to one or more sub-chips.
122
123config UCB1400_CORE
124 tristate "Philips UCB1400 Core driver"
125 depends on AC97_BUS
126 depends on GPIOLIB
127 help
128 This enables support for the Philips UCB1400 core functions.
129 The UCB1400 is an AC97 audio codec.
130
131 To compile this driver as a module, choose M here: the
132 module will be called ucb1400_core.
133
134config MFD_LM3533
135 tristate "LM3533 Lighting Power chip"
136 depends on I2C
137 select MFD_CORE
138 select REGMAP_I2C
139 help
140 Say yes here to enable support for National Semiconductor / TI
141 LM3533 Lighting Power chips.
142
143 This driver provides common support for accessing the device;
144 additional drivers must be enabled in order to use the LED,
145 backlight or ambient-light-sensor functionality of the device.
146
147config TPS6105X
148 tristate "TPS61050/61052 Boost Converters"
149 depends on I2C
150 select REGULATOR
151 select MFD_CORE
152 select REGULATOR_FIXED_VOLTAGE
153 help
154 This option enables a driver for the TP61050/TPS61052
155 high-power "white LED driver". This boost converter is
156 sometimes used for other things than white LEDs, and
157 also contains a GPIO pin.
158
159config TPS65010
160 tristate "TPS6501x Power Management chips"
161 depends on I2C && GPIOLIB
162 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
163 help
164 If you say yes here you get support for the TPS6501x series of
165 Power Management chips. These include voltage regulators,
166 lithium ion/polymer battery charging, and other features that
167 are often used in portable devices like cell phones and cameras.
168
169 This driver can also be built as a module. If so, the module
170 will be called tps65010.
171
172config TPS6507X
173 tristate "TPS6507x Power Management / Touch Screen chips"
174 select MFD_CORE
175 depends on I2C
176 help
177 If you say yes here you get support for the TPS6507x series of
178 Power Management / Touch Screen chips. These include voltage
179 regulators, lithium ion/polymer battery charging, touch screen
180 and other features that are often used in portable devices.
181 This driver can also be built as a module. If so, the module
182 will be called tps6507x.
183
184config MFD_TPS65217
185 tristate "TPS65217 Power Management / White LED chips"
186 depends on I2C
187 select MFD_CORE
188 select REGMAP_I2C
189 help
190 If you say yes here you get support for the TPS65217 series of
191 Power Management / White LED chips.
192 These include voltage regulators, lithium ion/polymer battery
193 charger, wled and other features that are often used in portable
194 devices.
195
196 This driver can also be built as a module. If so, the module
197 will be called tps65217.
198
199config MFD_TPS6586X
200 bool "TPS6586x Power Management chips"
201 depends on I2C=y && GENERIC_HARDIRQS
202 select MFD_CORE
203 select REGMAP_I2C
204 depends on REGULATOR
205 help
206 If you say yes here you get support for the TPS6586X series of
207 Power Management chips.
208 This driver provides common support for accessing the device,
209 additional drivers must be enabled in order to use the
210 functionality of the device.
211
212 This driver can also be built as a module. If so, the module
213 will be called tps6586x.
214
215config MFD_TPS65910
216 bool "TPS65910 Power Management chip"
217 depends on I2C=y && GPIOLIB
218 select MFD_CORE
219 select REGMAP_I2C
220 select IRQ_DOMAIN
221 help
222 if you say yes here you get support for the TPS65910 series of
223 Power Management chips.
224
225config MFD_TPS65912
226 bool
227 depends on GPIOLIB
228
229config MFD_TPS65912_I2C
230 bool "TPS65912 Power Management chip with I2C"
231 select MFD_CORE
232 select MFD_TPS65912
233 depends on I2C=y && GPIOLIB
234 help
235 If you say yes here you get support for the TPS65912 series of
236 PM chips with I2C interface.
237
238config MFD_TPS65912_SPI
239 bool "TPS65912 Power Management chip with SPI"
240 select MFD_CORE
241 select MFD_TPS65912
242 depends on SPI_MASTER && GPIOLIB
243 help
244 If you say yes here you get support for the TPS65912 series of
245 PM chips with SPI interface.
246
247config MENELAUS
248 bool "Texas Instruments TWL92330/Menelaus PM chip"
249 depends on I2C=y && ARCH_OMAP2
250 help
251 If you say yes here you get support for the Texas Instruments
252 TWL92330/Menelaus Power Management chip. This include voltage
253 regulators, Dual slot memory card transceivers, real-time clock
254 and other features that are often used in portable devices like
255 cell phones and PDAs.
256
257config TWL4030_CORE
258 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
259 depends on I2C=y && GENERIC_HARDIRQS
260 select IRQ_DOMAIN
261 help
262 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
263 This core driver provides register access and IRQ handling
264 facilities, and registers devices for the various functions
265 so that function-specific drivers can bind to them.
266
267 These multi-function chips are found on many OMAP2 and OMAP3
268 boards, providing power management, RTC, GPIO, keypad, a
269 high speed USB OTG transceiver, an audio codec (on most
270 versions) and many other features.
271
272config TWL4030_MADC
273 tristate "Texas Instruments TWL4030 MADC"
274 depends on TWL4030_CORE
275 help
276 This driver provides support for triton TWL4030-MADC. The
277 driver supports both RT and SW conversion methods.
278
279 This driver can be built as a module. If so it will be
280 named twl4030-madc
281
282config TWL4030_POWER
283 bool "Support power resources on TWL4030 family chips"
284 depends on TWL4030_CORE && ARM
285 help
286 Say yes here if you want to use the power resources on the
287 TWL4030 family chips. Most of these resources are regulators,
288 which have a separate driver; some are control signals, such
289 as clock request handshaking.
290
291 This driver uses board-specific data to initialize the resources
292 and load scripts controlling which resources are switched off/on
293 or reset when a sleep, wakeup or warm reset event occurs.
294
295config MFD_TWL4030_AUDIO
296 bool
297 depends on TWL4030_CORE
298 select MFD_CORE
299 default n
300
301config TWL6030_PWM
302 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
303 depends on TWL4030_CORE
304 select HAVE_PWM
305 default n
306 help
307 Say yes here if you want support for TWL6030 PWM.
308 This is used to control charging LED brightness.
309
310config TWL6040_CORE
311 bool "Support for TWL6040 audio codec"
312 depends on I2C=y && GENERIC_HARDIRQS
313 select MFD_CORE
314 select REGMAP_I2C
315 select IRQ_DOMAIN
316 default n
317 help
318 Say yes here if you want support for Texas Instruments TWL6040 audio
319 codec.
320 This driver provides common support for accessing the device,
321 additional drivers must be enabled in order to use the
322 functionality of the device (audio, vibra).
323
324config MFD_STMPE
325 bool "Support STMicroelectronics STMPE"
326 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
327 select MFD_CORE
328 help
329 Support for the STMPE family of I/O Expanders from
330 STMicroelectronics.
331
332 Currently supported devices are:
333
334 STMPE811: GPIO, Touchscreen
335 STMPE1601: GPIO, Keypad
336 STMPE2401: GPIO, Keypad
337 STMPE2403: GPIO, Keypad
338
339 This driver provides common support for accessing the device,
340 additional drivers must be enabled in order to use the functionality
341 of the device. Currently available sub drivers are:
342
343 GPIO: stmpe-gpio
344 Keypad: stmpe-keypad
345 Touchscreen: stmpe-ts
346
347menu "STMPE Interface Drivers"
348depends on MFD_STMPE
349
350config STMPE_I2C
351 bool "STMPE I2C Inteface"
352 depends on I2C=y
353 default y
354 help
355 This is used to enable I2C interface of STMPE
356
357config STMPE_SPI
358 bool "STMPE SPI Inteface"
359 depends on SPI_MASTER
360 help
361 This is used to enable SPI interface of STMPE
362endmenu
363
364config MFD_TC3589X
365 bool "Support Toshiba TC35892 and variants"
366 depends on I2C=y && GENERIC_HARDIRQS
367 select MFD_CORE
368 help
369 Support for the Toshiba TC35892 and variants I/O Expander.
370
371 This driver provides common support for accessing the device,
372 additional drivers must be enabled in order to use the
373 functionality of the device.
374
375config MFD_TMIO
376 bool
377 default n
378
379config MFD_T7L66XB
380 bool "Support Toshiba T7L66XB"
381 depends on ARM && HAVE_CLK
382 select MFD_CORE
383 select MFD_TMIO
384 help
385 Support for Toshiba Mobile IO Controller T7L66XB
386
387config MFD_TC6387XB
388 bool "Support Toshiba TC6387XB"
389 depends on ARM && HAVE_CLK
390 select MFD_CORE
391 select MFD_TMIO
392 help
393 Support for Toshiba Mobile IO Controller TC6387XB
394
395config MFD_TC6393XB
396 bool "Support Toshiba TC6393XB"
397 depends on GPIOLIB && ARM && HAVE_CLK
398 select MFD_CORE
399 select MFD_TMIO
400 help
401 Support for Toshiba Mobile IO Controller TC6393XB
402
403config PMIC_DA903X
404 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
405 depends on I2C=y
406 help
407 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
408 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
409 usually found on PXA processors-based platforms. This includes
410 the I2C driver and the core APIs _only_, you have to select
411 individual components like LCD backlight, voltage regulators,
412 LEDs and battery-charger under the corresponding menus.
413
414config PMIC_DA9052
415 bool
416 select MFD_CORE
417
418config MFD_DA9052_SPI
419 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
420 select REGMAP_SPI
421 select REGMAP_IRQ
422 select PMIC_DA9052
423 depends on SPI_MASTER=y
424 help
425 Support for the Dialog Semiconductor DA9052 PMIC
426 when controlled using SPI. This driver provides common support
427 for accessing the device, additional drivers must be enabled in
428 order to use the functionality of the device.
429
430config MFD_DA9052_I2C
431 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
432 select REGMAP_I2C
433 select REGMAP_IRQ
434 select PMIC_DA9052
435 depends on I2C=y
436 help
437 Support for the Dialog Semiconductor DA9052 PMIC
438 when controlled using I2C. This driver provides common support
439 for accessing the device, additional drivers must be enabled in
440 order to use the functionality of the device.
441
442config PMIC_ADP5520
443 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
444 depends on I2C=y
445 help
446 Say yes here to add support for Analog Devices AD5520 and ADP5501,
447 Multifunction Power Management IC. This includes
448 the I2C driver and the core APIs _only_, you have to select
449 individual components like LCD backlight, LEDs, GPIOs and Kepad
450 under the corresponding menus.
451
452config MFD_MAX77686
453 bool "Maxim Semiconductor MAX77686 PMIC Support"
454 depends on I2C=y && GENERIC_HARDIRQS
455 select MFD_CORE
456 select REGMAP_I2C
457 select IRQ_DOMAIN
458 help
459 Say yes here to support for Maxim Semiconductor MAX77686.
460 This is a Power Management IC with RTC on chip.
461 This driver provides common support for accessing the device;
462 additional drivers must be enabled in order to use the functionality
463 of the device.
464
465config MFD_MAX77693
466 bool "Maxim Semiconductor MAX77693 PMIC Support"
467 depends on I2C=y && GENERIC_HARDIRQS
468 select MFD_CORE
469 select REGMAP_I2C
470 help
471 Say yes here to support for Maxim Semiconductor MAX77693.
472 This is a companion Power Management IC with Flash, Haptic, Charger,
473 and MUIC(Micro USB Interface Controller) controls on chip.
474 This driver provides common support for accessing the device;
475 additional drivers must be enabled in order to use the functionality
476 of the device.
477
478config MFD_MAX8925
479 bool "Maxim Semiconductor MAX8925 PMIC Support"
480 depends on I2C=y && GENERIC_HARDIRQS
481 select MFD_CORE
482 help
483 Say yes here to support for Maxim Semiconductor MAX8925. This is
484 a Power Management IC. This driver provides common support for
485 accessing the device, additional drivers must be enabled in order
486 to use the functionality of the device.
487
488config MFD_MAX8997
489 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
490 depends on I2C=y && GENERIC_HARDIRQS
491 select MFD_CORE
492 select IRQ_DOMAIN
493 help
494 Say yes here to support for Maxim Semiconductor MAX8997/8966.
495 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
496 MUIC controls on chip.
497 This driver provides common support for accessing the device;
498 additional drivers must be enabled in order to use the functionality
499 of the device.
500
501config MFD_MAX8998
502 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
503 depends on I2C=y && GENERIC_HARDIRQS
504 select MFD_CORE
505 help
506 Say yes here to support for Maxim Semiconductor MAX8998 and
507 National Semiconductor LP3974. This is a Power Management IC.
508 This driver provides common support for accessing the device,
509 additional drivers must be enabled in order to use the functionality
510 of the device.
511
512config MFD_SEC_CORE
513 bool "SAMSUNG Electronics PMIC Series Support"
514 depends on I2C=y && GENERIC_HARDIRQS
515 select MFD_CORE
516 select REGMAP_I2C
517 select REGMAP_IRQ
518 help
519 Support for the Samsung Electronics MFD series.
520 This driver provides common support for accessing the device,
521 additional drivers must be enabled in order to use the functionality
522 of the device
523
524config MFD_ARIZONA
525 select REGMAP
526 select REGMAP_IRQ
527 bool
528
529config MFD_ARIZONA_I2C
530 tristate "Support Wolfson Microelectronics Arizona platform with I2C"
531 select MFD_ARIZONA
532 select MFD_CORE
533 select REGMAP_I2C
534 depends on I2C
535 help
536 Support for the Wolfson Microelectronics Arizona platform audio SoC
537 core functionality controlled via I2C.
538
539config MFD_ARIZONA_SPI
540 tristate "Support Wolfson Microelectronics Arizona platform with SPI"
541 select MFD_ARIZONA
542 select MFD_CORE
543 select REGMAP_SPI
544 depends on SPI_MASTER
545 help
546 Support for the Wolfson Microelectronics Arizona platform audio SoC
547 core functionality controlled via I2C.
548
549config MFD_WM5102
550 bool "Support Wolfson Microelectronics WM5102"
551 depends on MFD_ARIZONA
552 help
553 Support for Wolfson Microelectronics WM5102 low power audio SoC
554
555config MFD_WM5110
556 bool "Support Wolfson Microelectronics WM5110"
557 depends on MFD_ARIZONA
558 help
559 Support for Wolfson Microelectronics WM5110 low power audio SoC
560
561config MFD_WM8400
562 bool "Support Wolfson Microelectronics WM8400"
563 select MFD_CORE
564 depends on I2C=y
565 select REGMAP_I2C
566 help
567 Support for the Wolfson Microelecronics WM8400 PMIC and audio
568 CODEC. This driver provides common support for accessing
569 the device, additional drivers must be enabled in order to use
570 the functionality of the device.
571
572config MFD_WM831X
573 bool
574 depends on GENERIC_HARDIRQS
575
576config MFD_WM831X_I2C
577 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
578 select MFD_CORE
579 select MFD_WM831X
580 select REGMAP_I2C
581 select IRQ_DOMAIN
582 depends on I2C=y && GENERIC_HARDIRQS
583 help
584 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
585 when controlled using I2C. This driver provides common support
586 for accessing the device, additional drivers must be enabled in
587 order to use the functionality of the device.
588
589config MFD_WM831X_SPI
590 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
591 select MFD_CORE
592 select MFD_WM831X
593 select REGMAP_SPI
594 select IRQ_DOMAIN
595 depends on SPI_MASTER && GENERIC_HARDIRQS
596 help
597 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
598 when controlled using SPI. This driver provides common support
599 for accessing the device, additional drivers must be enabled in
600 order to use the functionality of the device.
601
602config MFD_WM8350
603 bool
604 depends on GENERIC_HARDIRQS
605
606config MFD_WM8350_CONFIG_MODE_0
607 bool
608 depends on MFD_WM8350
609
610config MFD_WM8350_CONFIG_MODE_1
611 bool
612 depends on MFD_WM8350
613
614config MFD_WM8350_CONFIG_MODE_2
615 bool
616 depends on MFD_WM8350
617
618config MFD_WM8350_CONFIG_MODE_3
619 bool
620 depends on MFD_WM8350
621
622config MFD_WM8351_CONFIG_MODE_0
623 bool
624 depends on MFD_WM8350
625
626config MFD_WM8351_CONFIG_MODE_1
627 bool
628 depends on MFD_WM8350
629
630config MFD_WM8351_CONFIG_MODE_2
631 bool
632 depends on MFD_WM8350
633
634config MFD_WM8351_CONFIG_MODE_3
635 bool
636 depends on MFD_WM8350
637
638config MFD_WM8352_CONFIG_MODE_0
639 bool
640 depends on MFD_WM8350
641
642config MFD_WM8352_CONFIG_MODE_1
643 bool
644 depends on MFD_WM8350
645
646config MFD_WM8352_CONFIG_MODE_2
647 bool
648 depends on MFD_WM8350
649
650config MFD_WM8352_CONFIG_MODE_3
651 bool
652 depends on MFD_WM8350
653
654config MFD_WM8350_I2C
655 bool "Support Wolfson Microelectronics WM8350 with I2C"
656 select MFD_WM8350
657 depends on I2C=y && GENERIC_HARDIRQS
658 help
659 The WM8350 is an integrated audio and power management
660 subsystem with watchdog and RTC functionality for embedded
661 systems. This option enables core support for the WM8350 with
662 I2C as the control interface. Additional options must be
663 selected to enable support for the functionality of the chip.
664
665config MFD_WM8994
666 bool "Support Wolfson Microelectronics WM8994"
667 select MFD_CORE
668 select REGMAP_I2C
669 select REGMAP_IRQ
670 depends on I2C=y && GENERIC_HARDIRQS
671 help
672 The WM8994 is a highly integrated hi-fi CODEC designed for
673 smartphone applicatiosn. As well as audio functionality it
674 has on board GPIO and regulator functionality which is
675 supported via the relevant subsystems. This driver provides
676 core support for the WM8994, in order to use the actual
677 functionaltiy of the device other drivers must be enabled.
678
679config MFD_PCF50633
680 tristate "Support for NXP PCF50633"
681 depends on I2C
682 select REGMAP_I2C
683 help
684 Say yes here if you have NXP PCF50633 chip on your board.
685 This core driver provides register access and IRQ handling
686 facilities, and registers devices for the various functions
687 so that function-specific drivers can bind to them.
688
689config PCF50633_ADC
690 tristate "Support for NXP PCF50633 ADC"
691 depends on MFD_PCF50633
692 help
693 Say yes here if you want to include support for ADC in the
694 NXP PCF50633 chip.
695
696config PCF50633_GPIO
697 tristate "Support for NXP PCF50633 GPIO"
698 depends on MFD_PCF50633
699 help
700 Say yes here if you want to include support GPIO for pins on
701 the PCF50633 chip.
702
703config MFD_MC13783
704 tristate
705
706config MFD_MC13XXX
707 tristate
708 depends on SPI_MASTER || I2C
709 select MFD_CORE
710 select MFD_MC13783
711 help
712 Enable support for the Freescale MC13783 and MC13892 PMICs.
713 This driver provides common support for accessing the device,
714 additional drivers must be enabled in order to use the
715 functionality of the device.
716
717config MFD_MC13XXX_SPI
718 tristate "Freescale MC13783 and MC13892 SPI interface"
719 depends on SPI_MASTER
720 select REGMAP_SPI
721 select MFD_MC13XXX
722 help
723 Select this if your MC13xxx is connected via an SPI bus.
724
725config MFD_MC13XXX_I2C
726 tristate "Freescale MC13892 I2C interface"
727 depends on I2C
728 select REGMAP_I2C
729 select MFD_MC13XXX
730 help
731 Select this if your MC13xxx is connected via an I2C bus.
732
733config ABX500_CORE
734 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
735 default y if ARCH_U300 || ARCH_U8500
736 help
737 Say yes here if you have the ABX500 Mixed Signal IC family
738 chips. This core driver expose register access functions.
739 Functionality specific drivers using these functions can
740 remain unchanged when IC changes. Binding of the functions to
741 actual register access is done by the IC core driver.
742
743config AB3100_CORE
744 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
745 depends on I2C=y && ABX500_CORE
746 select MFD_CORE
747 default y if ARCH_U300
748 help
749 Select this to enable the AB3100 Mixed Signal IC core
750 functionality. This connects to a AB3100 on the I2C bus
751 and expose a number of symbols needed for dependent devices
752 to read and write registers and subscribe to events from
753 this multi-functional IC. This is needed to use other features
754 of the AB3100 such as battery-backed RTC, charging control,
755 LEDs, vibrator, system power and temperature, power management
756 and ALSA sound.
757
758config AB3100_OTP
759 tristate "ST-Ericsson AB3100 OTP functions"
760 depends on AB3100_CORE
761 default y if AB3100_CORE
762 help
763 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
764 programmable memory) support. This exposes a sysfs file to read
765 out OTP values.
766
767config EZX_PCAP
768 bool "PCAP Support"
769 depends on GENERIC_HARDIRQS && SPI_MASTER
770 help
771 This enables the PCAP ASIC present on EZX Phones. This is
772 needed for MMC, TouchScreen, Sound, USB, etc..
773
774config AB8500_CORE
775 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
776 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
777 select MFD_CORE
778 select IRQ_DOMAIN
779 help
780 Select this option to enable access to AB8500 power management
781 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
782 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
783 the irq_chip parts for handling the Mixed Signal chip events.
784 This chip embeds various other multimedia funtionalities as well.
785
786config AB8500_DEBUG
787 bool "Enable debug info via debugfs"
788 depends on AB8500_CORE && DEBUG_FS
789 default y if DEBUG_FS
790 help
791 Select this option if you want debug information using the debug
792 filesystem, debugfs.
793
794config AB8500_GPADC
795 bool "AB8500 GPADC driver"
796 depends on AB8500_CORE && REGULATOR_AB8500
797 default y
798 help
799 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
800
801config MFD_DB8500_PRCMU
802 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
803 depends on UX500_SOC_DB8500
804 select MFD_CORE
805 help
806 Select this option to enable support for the DB8500 Power Reset
807 and Control Management Unit. This is basically an autonomous
808 system controller running an XP70 microprocessor, which is accessed
809 through a register map.
810
811config MFD_CS5535
812 tristate "Support for CS5535 and CS5536 southbridge core functions"
813 select MFD_CORE
814 depends on PCI && X86
815 ---help---
816 This is the core driver for CS5535/CS5536 MFD functions. This is
817 necessary for using the board's GPIO and MFGPT functionality.
818
819config MFD_TIMBERDALE
820 tristate "Support for the Timberdale FPGA"
821 select MFD_CORE
822 depends on PCI && GPIOLIB
823 ---help---
824 This is the core driver for the timberdale FPGA. This device is a
825 multifunction device which exposes numerous platform devices.
826
827 The timberdale FPGA can be found on the Intel Atom development board
828 for in-vehicle infontainment, called Russellville.
829
830config LPC_SCH
831 tristate "Intel SCH LPC"
832 depends on PCI
833 select MFD_CORE
834 help
835 LPC bridge function of the Intel SCH provides support for
836 System Management Bus and General Purpose I/O.
837
838config LPC_ICH
839 tristate "Intel ICH LPC"
840 depends on PCI
841 select MFD_CORE
842 help
843 The LPC bridge function of the Intel ICH provides support for
844 many functional units. This driver provides needed support for
845 other drivers to control these functions, currently GPIO and
846 watchdog.
847
848config MFD_RDC321X
849 tristate "Support for RDC-R321x southbridge"
850 select MFD_CORE
851 depends on PCI
852 help
853 Say yes here if you want to have support for the RDC R-321x SoC
854 southbridge which provides access to GPIOs and Watchdog using the
855 southbridge PCI device configuration space.
856
857config MFD_JANZ_CMODIO
858 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
859 select MFD_CORE
860 depends on PCI
861 help
862 This is the core driver for the Janz CMOD-IO PCI MODULbus
863 carrier board. This device is a PCI to MODULbus bridge which may
864 host many different types of MODULbus daughterboards, including
865 CAN and GPIO controllers.
866
867config MFD_JZ4740_ADC
868 bool "Support for the JZ4740 SoC ADC core"
869 select MFD_CORE
870 select GENERIC_IRQ_CHIP
871 depends on MACH_JZ4740
872 help
873 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
874 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
875
876config MFD_VX855
877 tristate "Support for VIA VX855/VX875 integrated south bridge"
878 depends on PCI
879 select MFD_CORE
880 help
881 Say yes here to enable support for various functions of the
882 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
883 and/or vx855_gpio drivers for this to do anything useful.
884
885config MFD_WL1273_CORE
886 tristate "Support for TI WL1273 FM radio."
887 depends on I2C
888 select MFD_CORE
889 default n
890 help
891 This is the core driver for the TI WL1273 FM radio. This MFD
892 driver connects the radio-wl1273 V4L2 module and the wl1273
893 audio codec.
894
895config MFD_OMAP_USB_HOST
896 bool "Support OMAP USBHS core driver"
897 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
898 default y
899 help
900 This is the core driver for the OAMP EHCI and OHCI drivers.
901 This MFD driver does the required setup functionalities for
902 OMAP USB Host drivers.
903
904config MFD_PM8XXX
905 tristate
906
907config MFD_PM8921_CORE
908 tristate "Qualcomm PM8921 PMIC chip"
909 depends on MSM_SSBI
910 select MFD_CORE
911 select MFD_PM8XXX
912 help
913 If you say yes to this option, support will be included for the
914 built-in PM8921 PMIC chip.
915
916 This is required if your board has a PM8921 and uses its features,
917 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
918
919 Say M here if you want to include support for PM8921 chip as a module.
920 This will build a module called "pm8921-core".
921
922config MFD_PM8XXX_IRQ
923 bool "Support for Qualcomm PM8xxx IRQ features"
924 depends on MFD_PM8XXX
925 default y if MFD_PM8XXX
926 help
927 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
928
929 This is required to use certain other PM 8xxx features, such as GPIO
930 and MPP.
931
932config TPS65911_COMPARATOR
933 tristate
934
935config MFD_TPS65090
936 bool "TPS65090 Power Management chips"
937 depends on I2C=y && GENERIC_HARDIRQS
938 select MFD_CORE
939 select REGMAP_I2C
940 help
941 If you say yes here you get support for the TPS65090 series of
942 Power Management chips.
943 This driver provides common support for accessing the device,
944 additional drivers must be enabled in order to use the
945 functionality of the device.
946
947config MFD_AAT2870_CORE
948 bool "Support for the AnalogicTech AAT2870"
949 select MFD_CORE
950 depends on I2C=y && GPIOLIB
951 help
952 If you say yes here you get support for the AAT2870.
953 This driver provides common support for accessing the device,
954 additional drivers must be enabled in order to use the
955 functionality of the device.
956
957config MFD_INTEL_MSIC
958 bool "Support for Intel MSIC"
959 depends on INTEL_SCU_IPC
960 select MFD_CORE
961 help
962 Select this option to enable access to Intel MSIC (Avatele
963 Passage) chip. This chip embeds audio, battery, GPIO, etc.
964 devices used in Intel Medfield platforms.
965
966config MFD_RC5T583
967 bool "Ricoh RC5T583 Power Management system device"
968 depends on I2C=y && GENERIC_HARDIRQS
969 select MFD_CORE
970 select REGMAP_I2C
971 help
972 Select this option to get support for the RICOH583 Power
973 Management system device.
974 This driver provides common support for accessing the device
975 through i2c interface. The device supports multiple sub-devices
976 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
977 Additional drivers must be enabled in order to use the
978 different functionality of the device.
979
980config MFD_STA2X11
981 bool "STA2X11 multi function device support"
982 depends on STA2X11
983 select MFD_CORE
984
985config MFD_ANATOP
986 bool "Support for Freescale i.MX on-chip ANATOP controller"
987 depends on SOC_IMX6Q
988 help
989 Select this option to enable Freescale i.MX on-chip ANATOP
990 MFD controller. This controller embeds regulator and
991 thermal devices for Freescale i.MX platforms.
992
993config MFD_PALMAS
994 bool "Support for the TI Palmas series chips"
995 select MFD_CORE
996 select REGMAP_I2C
997 select REGMAP_IRQ
998 depends on I2C=y
999 help
1000 If you say yes here you get support for the Palmas
1001 series of PMIC chips from Texas Instruments.
1002
1003endmenu
1004endif
1005
1006menu "Multimedia Capabilities Port drivers"
1007 depends on ARCH_SA1100
1008
1009config MCP
1010 tristate
1011
1012# Interface drivers
1013config MCP_SA11X0
1014 tristate "Support SA11x0 MCP interface"
1015 depends on ARCH_SA1100
1016 select MCP
1017
1018# Chip drivers
1019config MCP_UCB1200
1020 bool "Support for UCB1200 / UCB1300"
1021 depends on MCP_SA11X0
1022 select MCP
1023
1024config MCP_UCB1200_TS
1025 tristate "Touchscreen interface support"
1026 depends on MCP_UCB1200 && INPUT
1027
1028endmenu
Linux kernel - Deliverables
This page took 0.026284 seconds and 5 git commands to generate.