Kconfig 26 KB

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