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