Kconfig 30 KB

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