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