projects / deliverable / linux.git / blame_incremental
? search:
summary | shortlog | log | commit | commitdiff | tree
blob | blame (non-incremental) | history | HEAD
TTY: move allocations to tty_alloc_driver
[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 depends on !PWM
306 default n
307 help
308 Say yes here if you want support for TWL6030 PWM.
309 This is used to control charging LED brightness.
310
311config TWL6040_CORE
312 bool "Support for TWL6040 audio codec"
313 depends on I2C=y && GENERIC_HARDIRQS
314 select MFD_CORE
315 select REGMAP_I2C
316 select IRQ_DOMAIN
317 default n
318 help
319 Say yes here if you want support for Texas Instruments TWL6040 audio
320 codec.
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 (audio, vibra).
324
325config MFD_STMPE
326 bool "Support STMicroelectronics STMPE"
327 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
328 select MFD_CORE
329 help
330 Support for the STMPE family of I/O Expanders from
331 STMicroelectronics.
332
333 Currently supported devices are:
334
335 STMPE811: GPIO, Touchscreen
336 STMPE1601: GPIO, Keypad
337 STMPE2401: GPIO, Keypad
338 STMPE2403: GPIO, Keypad
339
340 This driver provides common support for accessing the device,
341 additional drivers must be enabled in order to use the functionality
342 of the device. Currently available sub drivers are:
343
344 GPIO: stmpe-gpio
345 Keypad: stmpe-keypad
346 Touchscreen: stmpe-ts
347
348menu "STMPE Interface Drivers"
349depends on MFD_STMPE
350
351config STMPE_I2C
352 bool "STMPE I2C Inteface"
353 depends on I2C=y
354 default y
355 help
356 This is used to enable I2C interface of STMPE
357
358config STMPE_SPI
359 bool "STMPE SPI Inteface"
360 depends on SPI_MASTER
361 help
362 This is used to enable SPI interface of STMPE
363endmenu
364
365config MFD_TC3589X
366 bool "Support Toshiba TC35892 and variants"
367 depends on I2C=y && GENERIC_HARDIRQS
368 select MFD_CORE
369 help
370 Support for the Toshiba TC35892 and variants I/O Expander.
371
372 This driver provides common support for accessing the device,
373 additional drivers must be enabled in order to use the
374 functionality of the device.
375
376config MFD_TMIO
377 bool
378 default n
379
380config MFD_T7L66XB
381 bool "Support Toshiba T7L66XB"
382 depends on ARM && HAVE_CLK
383 select MFD_CORE
384 select MFD_TMIO
385 help
386 Support for Toshiba Mobile IO Controller T7L66XB
387
388config MFD_TC6387XB
389 bool "Support Toshiba TC6387XB"
390 depends on ARM && HAVE_CLK
391 select MFD_CORE
392 select MFD_TMIO
393 help
394 Support for Toshiba Mobile IO Controller TC6387XB
395
396config MFD_TC6393XB
397 bool "Support Toshiba TC6393XB"
398 depends on GPIOLIB && ARM && HAVE_CLK
399 select MFD_CORE
400 select MFD_TMIO
401 help
402 Support for Toshiba Mobile IO Controller TC6393XB
403
404config PMIC_DA903X
405 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
406 depends on I2C=y
407 help
408 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
409 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
410 usually found on PXA processors-based platforms. This includes
411 the I2C driver and the core APIs _only_, you have to select
412 individual components like LCD backlight, voltage regulators,
413 LEDs and battery-charger under the corresponding menus.
414
415config PMIC_DA9052
416 bool
417 select MFD_CORE
418
419config MFD_DA9052_SPI
420 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
421 select REGMAP_SPI
422 select REGMAP_IRQ
423 select PMIC_DA9052
424 depends on SPI_MASTER=y
425 help
426 Support for the Dialog Semiconductor DA9052 PMIC
427 when controlled using SPI. This driver provides common support
428 for accessing the device, additional drivers must be enabled in
429 order to use the functionality of the device.
430
431config MFD_DA9052_I2C
432 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
433 select REGMAP_I2C
434 select REGMAP_IRQ
435 select PMIC_DA9052
436 depends on I2C=y
437 help
438 Support for the Dialog Semiconductor DA9052 PMIC
439 when controlled using I2C. This driver provides common support
440 for accessing the device, additional drivers must be enabled in
441 order to use the functionality of the device.
442
443config PMIC_ADP5520
444 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
445 depends on I2C=y
446 help
447 Say yes here to add support for Analog Devices AD5520 and ADP5501,
448 Multifunction Power Management IC. This includes
449 the I2C driver and the core APIs _only_, you have to select
450 individual components like LCD backlight, LEDs, GPIOs and Kepad
451 under the corresponding menus.
452
453config MFD_MAX77686
454 bool "Maxim Semiconductor MAX77686 PMIC Support"
455 depends on I2C=y && GENERIC_HARDIRQS
456 select MFD_CORE
457 select REGMAP_I2C
458 select IRQ_DOMAIN
459 help
460 Say yes here to support for Maxim Semiconductor MAX77686.
461 This is a Power Management IC with RTC on chip.
462 This driver provides common support for accessing the device;
463 additional drivers must be enabled in order to use the functionality
464 of the device.
465
466config MFD_MAX77693
467 bool "Maxim Semiconductor MAX77693 PMIC Support"
468 depends on I2C=y && GENERIC_HARDIRQS
469 select MFD_CORE
470 select REGMAP_I2C
471 help
472 Say yes here to support for Maxim Semiconductor MAX77693.
473 This is a companion Power Management IC with Flash, Haptic, Charger,
474 and MUIC(Micro USB Interface Controller) controls on chip.
475 This driver provides common support for accessing the device;
476 additional drivers must be enabled in order to use the functionality
477 of the device.
478
479config MFD_MAX8925
480 bool "Maxim Semiconductor MAX8925 PMIC Support"
481 depends on I2C=y && GENERIC_HARDIRQS
482 select MFD_CORE
483 help
484 Say yes here to support for Maxim Semiconductor MAX8925. This is
485 a Power Management IC. This driver provides common support for
486 accessing the device, additional drivers must be enabled in order
487 to use the functionality of the device.
488
489config MFD_MAX8997
490 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
491 depends on I2C=y && GENERIC_HARDIRQS
492 select MFD_CORE
493 select IRQ_DOMAIN
494 help
495 Say yes here to support for Maxim Semiconductor MAX8997/8966.
496 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
497 MUIC controls on chip.
498 This driver provides common support for accessing the device;
499 additional drivers must be enabled in order to use the functionality
500 of the device.
501
502config MFD_MAX8998
503 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
504 depends on I2C=y && GENERIC_HARDIRQS
505 select MFD_CORE
506 help
507 Say yes here to support for Maxim Semiconductor MAX8998 and
508 National Semiconductor LP3974. This is a Power Management IC.
509 This driver provides common support for accessing the device,
510 additional drivers must be enabled in order to use the functionality
511 of the device.
512
513config MFD_SEC_CORE
514 bool "SAMSUNG Electronics PMIC Series Support"
515 depends on I2C=y && GENERIC_HARDIRQS
516 select MFD_CORE
517 select REGMAP_I2C
518 select REGMAP_IRQ
519 help
520 Support for the Samsung Electronics MFD series.
521 This driver provides common support for accessing the device,
522 additional drivers must be enabled in order to use the functionality
523 of the device
524
525config MFD_ARIZONA
526 select REGMAP
527 select REGMAP_IRQ
528 select MFD_CORE
529 bool
530
531config MFD_ARIZONA_I2C
532 tristate "Support Wolfson Microelectronics Arizona platform with I2C"
533 select MFD_ARIZONA
534 select MFD_CORE
535 select REGMAP_I2C
536 depends on I2C
537 help
538 Support for the Wolfson Microelectronics Arizona platform audio SoC
539 core functionality controlled via I2C.
540
541config MFD_ARIZONA_SPI
542 tristate "Support Wolfson Microelectronics Arizona platform with SPI"
543 select MFD_ARIZONA
544 select MFD_CORE
545 select REGMAP_SPI
546 depends on SPI_MASTER
547 help
548 Support for the Wolfson Microelectronics Arizona platform audio SoC
549 core functionality controlled via I2C.
550
551config MFD_WM5102
552 bool "Support Wolfson Microelectronics WM5102"
553 depends on MFD_ARIZONA
554 help
555 Support for Wolfson Microelectronics WM5102 low power audio SoC
556
557config MFD_WM5110
558 bool "Support Wolfson Microelectronics WM5110"
559 depends on MFD_ARIZONA
560 help
561 Support for Wolfson Microelectronics WM5110 low power audio SoC
562
563config MFD_WM8400
564 bool "Support Wolfson Microelectronics WM8400"
565 select MFD_CORE
566 depends on I2C=y
567 select REGMAP_I2C
568 help
569 Support for the Wolfson Microelecronics WM8400 PMIC and audio
570 CODEC. This driver provides common support for accessing
571 the device, additional drivers must be enabled in order to use
572 the functionality of the device.
573
574config MFD_WM831X
575 bool
576 depends on GENERIC_HARDIRQS
577
578config MFD_WM831X_I2C
579 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
580 select MFD_CORE
581 select MFD_WM831X
582 select REGMAP_I2C
583 select IRQ_DOMAIN
584 depends on I2C=y && GENERIC_HARDIRQS
585 help
586 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
587 when controlled using I2C. This driver provides common support
588 for accessing the device, additional drivers must be enabled in
589 order to use the functionality of the device.
590
591config MFD_WM831X_SPI
592 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
593 select MFD_CORE
594 select MFD_WM831X
595 select REGMAP_SPI
596 select IRQ_DOMAIN
597 depends on SPI_MASTER && GENERIC_HARDIRQS
598 help
599 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
600 when controlled using SPI. This driver provides common support
601 for accessing the device, additional drivers must be enabled in
602 order to use the functionality of the device.
603
604config MFD_WM8350
605 bool
606 depends on GENERIC_HARDIRQS
607
608config MFD_WM8350_CONFIG_MODE_0
609 bool
610 depends on MFD_WM8350
611
612config MFD_WM8350_CONFIG_MODE_1
613 bool
614 depends on MFD_WM8350
615
616config MFD_WM8350_CONFIG_MODE_2
617 bool
618 depends on MFD_WM8350
619
620config MFD_WM8350_CONFIG_MODE_3
621 bool
622 depends on MFD_WM8350
623
624config MFD_WM8351_CONFIG_MODE_0
625 bool
626 depends on MFD_WM8350
627
628config MFD_WM8351_CONFIG_MODE_1
629 bool
630 depends on MFD_WM8350
631
632config MFD_WM8351_CONFIG_MODE_2
633 bool
634 depends on MFD_WM8350
635
636config MFD_WM8351_CONFIG_MODE_3
637 bool
638 depends on MFD_WM8350
639
640config MFD_WM8352_CONFIG_MODE_0
641 bool
642 depends on MFD_WM8350
643
644config MFD_WM8352_CONFIG_MODE_1
645 bool
646 depends on MFD_WM8350
647
648config MFD_WM8352_CONFIG_MODE_2
649 bool
650 depends on MFD_WM8350
651
652config MFD_WM8352_CONFIG_MODE_3
653 bool
654 depends on MFD_WM8350
655
656config MFD_WM8350_I2C
657 bool "Support Wolfson Microelectronics WM8350 with I2C"
658 select MFD_WM8350
659 depends on I2C=y && GENERIC_HARDIRQS
660 help
661 The WM8350 is an integrated audio and power management
662 subsystem with watchdog and RTC functionality for embedded
663 systems. This option enables core support for the WM8350 with
664 I2C as the control interface. Additional options must be
665 selected to enable support for the functionality of the chip.
666
667config MFD_WM8994
668 bool "Support Wolfson Microelectronics WM8994"
669 select MFD_CORE
670 select REGMAP_I2C
671 select REGMAP_IRQ
672 depends on I2C=y && GENERIC_HARDIRQS
673 help
674 The WM8994 is a highly integrated hi-fi CODEC designed for
675 smartphone applicatiosn. As well as audio functionality it
676 has on board GPIO and regulator functionality which is
677 supported via the relevant subsystems. This driver provides
678 core support for the WM8994, in order to use the actual
679 functionaltiy of the device other drivers must be enabled.
680
681config MFD_PCF50633
682 tristate "Support for NXP PCF50633"
683 depends on I2C
684 select REGMAP_I2C
685 help
686 Say yes here if you have NXP PCF50633 chip on your board.
687 This core driver provides register access and IRQ handling
688 facilities, and registers devices for the various functions
689 so that function-specific drivers can bind to them.
690
691config PCF50633_ADC
692 tristate "Support for NXP PCF50633 ADC"
693 depends on MFD_PCF50633
694 help
695 Say yes here if you want to include support for ADC in the
696 NXP PCF50633 chip.
697
698config PCF50633_GPIO
699 tristate "Support for NXP PCF50633 GPIO"
700 depends on MFD_PCF50633
701 help
702 Say yes here if you want to include support GPIO for pins on
703 the PCF50633 chip.
704
705config MFD_MC13783
706 tristate
707
708config MFD_MC13XXX
709 tristate
710 depends on SPI_MASTER || I2C
711 select MFD_CORE
712 select MFD_MC13783
713 help
714 Enable support for the Freescale MC13783 and MC13892 PMICs.
715 This driver provides common support for accessing the device,
716 additional drivers must be enabled in order to use the
717 functionality of the device.
718
719config MFD_MC13XXX_SPI
720 tristate "Freescale MC13783 and MC13892 SPI interface"
721 depends on SPI_MASTER
722 select REGMAP_SPI
723 select MFD_MC13XXX
724 help
725 Select this if your MC13xxx is connected via an SPI bus.
726
727config MFD_MC13XXX_I2C
728 tristate "Freescale MC13892 I2C interface"
729 depends on I2C
730 select REGMAP_I2C
731 select MFD_MC13XXX
732 help
733 Select this if your MC13xxx is connected via an I2C bus.
734
735config ABX500_CORE
736 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
737 default y if ARCH_U300 || ARCH_U8500
738 help
739 Say yes here if you have the ABX500 Mixed Signal IC family
740 chips. This core driver expose register access functions.
741 Functionality specific drivers using these functions can
742 remain unchanged when IC changes. Binding of the functions to
743 actual register access is done by the IC core driver.
744
745config AB3100_CORE
746 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
747 depends on I2C=y && ABX500_CORE
748 select MFD_CORE
749 default y if ARCH_U300
750 help
751 Select this to enable the AB3100 Mixed Signal IC core
752 functionality. This connects to a AB3100 on the I2C bus
753 and expose a number of symbols needed for dependent devices
754 to read and write registers and subscribe to events from
755 this multi-functional IC. This is needed to use other features
756 of the AB3100 such as battery-backed RTC, charging control,
757 LEDs, vibrator, system power and temperature, power management
758 and ALSA sound.
759
760config AB3100_OTP
761 tristate "ST-Ericsson AB3100 OTP functions"
762 depends on AB3100_CORE
763 default y if AB3100_CORE
764 help
765 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
766 programmable memory) support. This exposes a sysfs file to read
767 out OTP values.
768
769config EZX_PCAP
770 bool "PCAP Support"
771 depends on GENERIC_HARDIRQS && SPI_MASTER
772 help
773 This enables the PCAP ASIC present on EZX Phones. This is
774 needed for MMC, TouchScreen, Sound, USB, etc..
775
776config AB8500_CORE
777 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
778 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
779 select MFD_CORE
780 select IRQ_DOMAIN
781 help
782 Select this option to enable access to AB8500 power management
783 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
784 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
785 the irq_chip parts for handling the Mixed Signal chip events.
786 This chip embeds various other multimedia funtionalities as well.
787
788config AB8500_DEBUG
789 bool "Enable debug info via debugfs"
790 depends on AB8500_CORE && DEBUG_FS
791 default y if DEBUG_FS
792 help
793 Select this option if you want debug information using the debug
794 filesystem, debugfs.
795
796config AB8500_GPADC
797 bool "AB8500 GPADC driver"
798 depends on AB8500_CORE && REGULATOR_AB8500
799 default y
800 help
801 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
802
803config MFD_DB8500_PRCMU
804 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
805 depends on UX500_SOC_DB8500
806 select MFD_CORE
807 help
808 Select this option to enable support for the DB8500 Power Reset
809 and Control Management Unit. This is basically an autonomous
810 system controller running an XP70 microprocessor, which is accessed
811 through a register map.
812
813config MFD_CS5535
814 tristate "Support for CS5535 and CS5536 southbridge core functions"
815 select MFD_CORE
816 depends on PCI && X86
817 ---help---
818 This is the core driver for CS5535/CS5536 MFD functions. This is
819 necessary for using the board's GPIO and MFGPT functionality.
820
821config MFD_TIMBERDALE
822 tristate "Support for the Timberdale FPGA"
823 select MFD_CORE
824 depends on PCI && GPIOLIB
825 ---help---
826 This is the core driver for the timberdale FPGA. This device is a
827 multifunction device which exposes numerous platform devices.
828
829 The timberdale FPGA can be found on the Intel Atom development board
830 for in-vehicle infontainment, called Russellville.
831
832config LPC_SCH
833 tristate "Intel SCH LPC"
834 depends on PCI
835 select MFD_CORE
836 help
837 LPC bridge function of the Intel SCH provides support for
838 System Management Bus and General Purpose I/O.
839
840config LPC_ICH
841 tristate "Intel ICH LPC"
842 depends on PCI
843 select MFD_CORE
844 help
845 The LPC bridge function of the Intel ICH provides support for
846 many functional units. This driver provides needed support for
847 other drivers to control these functions, currently GPIO and
848 watchdog.
849
850config MFD_RDC321X
851 tristate "Support for RDC-R321x southbridge"
852 select MFD_CORE
853 depends on PCI
854 help
855 Say yes here if you want to have support for the RDC R-321x SoC
856 southbridge which provides access to GPIOs and Watchdog using the
857 southbridge PCI device configuration space.
858
859config MFD_JANZ_CMODIO
860 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
861 select MFD_CORE
862 depends on PCI
863 help
864 This is the core driver for the Janz CMOD-IO PCI MODULbus
865 carrier board. This device is a PCI to MODULbus bridge which may
866 host many different types of MODULbus daughterboards, including
867 CAN and GPIO controllers.
868
869config MFD_JZ4740_ADC
870 bool "Support for the JZ4740 SoC ADC core"
871 select MFD_CORE
872 select GENERIC_IRQ_CHIP
873 depends on MACH_JZ4740
874 help
875 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
876 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
877
878config MFD_VX855
879 tristate "Support for VIA VX855/VX875 integrated south bridge"
880 depends on PCI
881 select MFD_CORE
882 help
883 Say yes here to enable support for various functions of the
884 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
885 and/or vx855_gpio drivers for this to do anything useful.
886
887config MFD_WL1273_CORE
888 tristate "Support for TI WL1273 FM radio."
889 depends on I2C
890 select MFD_CORE
891 default n
892 help
893 This is the core driver for the TI WL1273 FM radio. This MFD
894 driver connects the radio-wl1273 V4L2 module and the wl1273
895 audio codec.
896
897config MFD_OMAP_USB_HOST
898 bool "Support OMAP USBHS core driver"
899 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
900 default y
901 help
902 This is the core driver for the OAMP EHCI and OHCI drivers.
903 This MFD driver does the required setup functionalities for
904 OMAP USB Host drivers.
905
906config MFD_PM8XXX
907 tristate
908
909config MFD_PM8921_CORE
910 tristate "Qualcomm PM8921 PMIC chip"
911 depends on MSM_SSBI
912 select MFD_CORE
913 select MFD_PM8XXX
914 help
915 If you say yes to this option, support will be included for the
916 built-in PM8921 PMIC chip.
917
918 This is required if your board has a PM8921 and uses its features,
919 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
920
921 Say M here if you want to include support for PM8921 chip as a module.
922 This will build a module called "pm8921-core".
923
924config MFD_PM8XXX_IRQ
925 bool "Support for Qualcomm PM8xxx IRQ features"
926 depends on MFD_PM8XXX
927 default y if MFD_PM8XXX
928 help
929 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
930
931 This is required to use certain other PM 8xxx features, such as GPIO
932 and MPP.
933
934config TPS65911_COMPARATOR
935 tristate
936
937config MFD_TPS65090
938 bool "TPS65090 Power Management chips"
939 depends on I2C=y && GENERIC_HARDIRQS
940 select MFD_CORE
941 select REGMAP_I2C
942 help
943 If you say yes here you get support for the TPS65090 series of
944 Power Management chips.
945 This driver provides common support for accessing the device,
946 additional drivers must be enabled in order to use the
947 functionality of the device.
948
949config MFD_AAT2870_CORE
950 bool "Support for the AnalogicTech AAT2870"
951 select MFD_CORE
952 depends on I2C=y && GPIOLIB
953 help
954 If you say yes here you get support for the AAT2870.
955 This driver provides common support for accessing the device,
956 additional drivers must be enabled in order to use the
957 functionality of the device.
958
959config MFD_INTEL_MSIC
960 bool "Support for Intel MSIC"
961 depends on INTEL_SCU_IPC
962 select MFD_CORE
963 help
964 Select this option to enable access to Intel MSIC (Avatele
965 Passage) chip. This chip embeds audio, battery, GPIO, etc.
966 devices used in Intel Medfield platforms.
967
968config MFD_RC5T583
969 bool "Ricoh RC5T583 Power Management system device"
970 depends on I2C=y && GENERIC_HARDIRQS
971 select MFD_CORE
972 select REGMAP_I2C
973 help
974 Select this option to get support for the RICOH583 Power
975 Management system device.
976 This driver provides common support for accessing the device
977 through i2c interface. The device supports multiple sub-devices
978 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
979 Additional drivers must be enabled in order to use the
980 different functionality of the device.
981
982config MFD_STA2X11
983 bool "STA2X11 multi function device support"
984 depends on STA2X11
985 select MFD_CORE
986
987config MFD_ANATOP
988 bool "Support for Freescale i.MX on-chip ANATOP controller"
989 depends on SOC_IMX6Q
990 help
991 Select this option to enable Freescale i.MX on-chip ANATOP
992 MFD controller. This controller embeds regulator and
993 thermal devices for Freescale i.MX platforms.
994
995config MFD_PALMAS
996 bool "Support for the TI Palmas series chips"
997 select MFD_CORE
998 select REGMAP_I2C
999 select REGMAP_IRQ
1000 depends on I2C=y
1001 help
1002 If you say yes here you get support for the Palmas
1003 series of PMIC chips from Texas Instruments.
1004
1005endmenu
1006endif
1007
1008menu "Multimedia Capabilities Port drivers"
1009 depends on ARCH_SA1100
1010
1011config MCP
1012 tristate
1013
1014# Interface drivers
1015config MCP_SA11X0
1016 tristate "Support SA11x0 MCP interface"
1017 depends on ARCH_SA1100
1018 select MCP
1019
1020# Chip drivers
1021config MCP_UCB1200
1022 bool "Support for UCB1200 / UCB1300"
1023 depends on MCP_SA11X0
1024 select MCP
1025
1026config MCP_UCB1200_TS
1027 tristate "Touchscreen interface support"
1028 depends on MCP_UCB1200 && INPUT
1029
1030endmenu
Linux kernel - Deliverables
This page took 0.028203 seconds and 5 git commands to generate.