Kconfig 27 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895
  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_TPS65217
  127. tristate "TPS65217 Power Management / White LED chips"
  128. depends on I2C
  129. select MFD_CORE
  130. select REGMAP_I2C
  131. help
  132. If you say yes here you get support for the TPS65217 series of
  133. Power Management / White LED chips.
  134. These include voltage regulators, lithium ion/polymer battery
  135. charger, wled and other features that are often used in portable
  136. devices.
  137. This driver can also be built as a module. If so, the module
  138. will be called tps65217.
  139. config MFD_TPS6586X
  140. bool "TPS6586x Power Management chips"
  141. depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
  142. select MFD_CORE
  143. help
  144. If you say yes here you get support for the TPS6586X series of
  145. Power Management chips.
  146. This driver provides common support for accessing the device,
  147. additional drivers must be enabled in order to use the
  148. functionality of the device.
  149. This driver can also be built as a module. If so, the module
  150. will be called tps6586x.
  151. config MFD_TPS65910
  152. bool "TPS65910 Power Management chip"
  153. depends on I2C=y && GPIOLIB
  154. select MFD_CORE
  155. select GPIO_TPS65910
  156. select REGMAP_I2C
  157. help
  158. if you say yes here you get support for the TPS65910 series of
  159. Power Management chips.
  160. config MFD_TPS65912
  161. bool
  162. depends on GPIOLIB
  163. config MFD_TPS65912_I2C
  164. bool "TPS65912 Power Management chip with I2C"
  165. select MFD_CORE
  166. select MFD_TPS65912
  167. depends on I2C=y && GPIOLIB
  168. help
  169. If you say yes here you get support for the TPS65912 series of
  170. PM chips with I2C interface.
  171. config MFD_TPS65912_SPI
  172. bool "TPS65912 Power Management chip with SPI"
  173. select MFD_CORE
  174. select MFD_TPS65912
  175. depends on SPI_MASTER && GPIOLIB
  176. help
  177. If you say yes here you get support for the TPS65912 series of
  178. PM chips with SPI interface.
  179. config MENELAUS
  180. bool "Texas Instruments TWL92330/Menelaus PM chip"
  181. depends on I2C=y && ARCH_OMAP2
  182. help
  183. If you say yes here you get support for the Texas Instruments
  184. TWL92330/Menelaus Power Management chip. This include voltage
  185. regulators, Dual slot memory card transceivers, real-time clock
  186. and other features that are often used in portable devices like
  187. cell phones and PDAs.
  188. config TWL4030_CORE
  189. bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
  190. depends on I2C=y && GENERIC_HARDIRQS
  191. help
  192. Say yes here if you have TWL4030 / TWL6030 family chip on your board.
  193. This core driver provides register access and IRQ handling
  194. facilities, and registers devices for the various functions
  195. so that function-specific drivers can bind to them.
  196. These multi-function chips are found on many OMAP2 and OMAP3
  197. boards, providing power management, RTC, GPIO, keypad, a
  198. high speed USB OTG transceiver, an audio codec (on most
  199. versions) and many other features.
  200. config TWL4030_MADC
  201. tristate "Texas Instruments TWL4030 MADC"
  202. depends on TWL4030_CORE
  203. help
  204. This driver provides support for triton TWL4030-MADC. The
  205. driver supports both RT and SW conversion methods.
  206. This driver can be built as a module. If so it will be
  207. named twl4030-madc
  208. config TWL4030_POWER
  209. bool "Support power resources on TWL4030 family chips"
  210. depends on TWL4030_CORE && ARM
  211. help
  212. Say yes here if you want to use the power resources on the
  213. TWL4030 family chips. Most of these resources are regulators,
  214. which have a separate driver; some are control signals, such
  215. as clock request handshaking.
  216. This driver uses board-specific data to initialize the resources
  217. and load scripts controlling which resources are switched off/on
  218. or reset when a sleep, wakeup or warm reset event occurs.
  219. config MFD_TWL4030_AUDIO
  220. bool
  221. depends on TWL4030_CORE
  222. select MFD_CORE
  223. default n
  224. config TWL6030_PWM
  225. tristate "TWL6030 PWM (Pulse Width Modulator) Support"
  226. depends on TWL4030_CORE
  227. select HAVE_PWM
  228. default n
  229. help
  230. Say yes here if you want support for TWL6030 PWM.
  231. This is used to control charging LED brightness.
  232. config TWL6040_CORE
  233. bool
  234. depends on TWL4030_CORE && GENERIC_HARDIRQS
  235. select MFD_CORE
  236. default n
  237. config MFD_STMPE
  238. bool "Support STMicroelectronics STMPE"
  239. depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
  240. select MFD_CORE
  241. help
  242. Support for the STMPE family of I/O Expanders from
  243. STMicroelectronics.
  244. Currently supported devices are:
  245. STMPE811: GPIO, Touchscreen
  246. STMPE1601: GPIO, Keypad
  247. STMPE2401: GPIO, Keypad
  248. STMPE2403: GPIO, Keypad
  249. This driver provides common support for accessing the device,
  250. additional drivers must be enabled in order to use the functionality
  251. of the device. Currently available sub drivers are:
  252. GPIO: stmpe-gpio
  253. Keypad: stmpe-keypad
  254. Touchscreen: stmpe-ts
  255. menu "STMPE Interface Drivers"
  256. depends on MFD_STMPE
  257. config STMPE_I2C
  258. bool "STMPE I2C Inteface"
  259. depends on I2C=y
  260. default y
  261. help
  262. This is used to enable I2C interface of STMPE
  263. config STMPE_SPI
  264. bool "STMPE SPI Inteface"
  265. depends on SPI_MASTER
  266. help
  267. This is used to enable SPI interface of STMPE
  268. endmenu
  269. config MFD_TC3589X
  270. bool "Support Toshiba TC35892 and variants"
  271. depends on I2C=y && GENERIC_HARDIRQS
  272. select MFD_CORE
  273. help
  274. Support for the Toshiba TC35892 and variants I/O Expander.
  275. This driver provides common support for accessing the device,
  276. additional drivers must be enabled in order to use the
  277. functionality of the device.
  278. config MFD_TMIO
  279. bool
  280. default n
  281. config MFD_T7L66XB
  282. bool "Support Toshiba T7L66XB"
  283. depends on ARM && HAVE_CLK
  284. select MFD_CORE
  285. select MFD_TMIO
  286. help
  287. Support for Toshiba Mobile IO Controller T7L66XB
  288. config MFD_TC6387XB
  289. bool "Support Toshiba TC6387XB"
  290. depends on ARM && HAVE_CLK
  291. select MFD_CORE
  292. select MFD_TMIO
  293. help
  294. Support for Toshiba Mobile IO Controller TC6387XB
  295. config MFD_TC6393XB
  296. bool "Support Toshiba TC6393XB"
  297. depends on GPIOLIB && ARM && HAVE_CLK
  298. select MFD_CORE
  299. select MFD_TMIO
  300. help
  301. Support for Toshiba Mobile IO Controller TC6393XB
  302. config PMIC_DA903X
  303. bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
  304. depends on I2C=y
  305. help
  306. Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
  307. ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
  308. usually found on PXA processors-based platforms. This includes
  309. the I2C driver and the core APIs _only_, you have to select
  310. individual components like LCD backlight, voltage regulators,
  311. LEDs and battery-charger under the corresponding menus.
  312. config PMIC_DA9052
  313. bool
  314. select MFD_CORE
  315. config MFD_DA9052_SPI
  316. bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
  317. select REGMAP_SPI
  318. select REGMAP_IRQ
  319. select PMIC_DA9052
  320. depends on SPI_MASTER=y
  321. help
  322. Support for the Dialog Semiconductor DA9052 PMIC
  323. when controlled using SPI. This driver provides common support
  324. for accessing the device, additional drivers must be enabled in
  325. order to use the functionality of the device.
  326. config MFD_DA9052_I2C
  327. bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
  328. select REGMAP_I2C
  329. select REGMAP_IRQ
  330. select PMIC_DA9052
  331. depends on I2C=y
  332. help
  333. Support for the Dialog Semiconductor DA9052 PMIC
  334. when controlled using I2C. This driver provides common support
  335. for accessing the device, additional drivers must be enabled in
  336. order to use the functionality of the device.
  337. config PMIC_ADP5520
  338. bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
  339. depends on I2C=y
  340. help
  341. Say yes here to add support for Analog Devices AD5520 and ADP5501,
  342. Multifunction Power Management IC. This includes
  343. the I2C driver and the core APIs _only_, you have to select
  344. individual components like LCD backlight, LEDs, GPIOs and Kepad
  345. under the corresponding menus.
  346. config MFD_MAX8925
  347. bool "Maxim Semiconductor MAX8925 PMIC Support"
  348. depends on I2C=y && GENERIC_HARDIRQS
  349. select MFD_CORE
  350. help
  351. Say yes here to support for Maxim Semiconductor MAX8925. This is
  352. a Power Management IC. This driver provies common support for
  353. accessing the device, additional drivers must be enabled in order
  354. to use the functionality of the device.
  355. config MFD_MAX8997
  356. bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
  357. depends on I2C=y && GENERIC_HARDIRQS
  358. select MFD_CORE
  359. help
  360. Say yes here to support for Maxim Semiconductor MAX8997/8966.
  361. This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
  362. MUIC controls on chip.
  363. This driver provides common support for accessing the device;
  364. additional drivers must be enabled in order to use the functionality
  365. of the device.
  366. config MFD_MAX8998
  367. bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
  368. depends on I2C=y && GENERIC_HARDIRQS
  369. select MFD_CORE
  370. help
  371. Say yes here to support for Maxim Semiconductor MAX8998 and
  372. National Semiconductor LP3974. This is a Power Management IC.
  373. This driver provies common support for accessing the device,
  374. additional drivers must be enabled in order to use the functionality
  375. of the device.
  376. config MFD_S5M_CORE
  377. bool "SAMSUNG S5M Series Support"
  378. depends on I2C=y && GENERIC_HARDIRQS
  379. select MFD_CORE
  380. select REGMAP_I2C
  381. help
  382. Support for the Samsung Electronics S5M MFD series.
  383. This driver provies common support for accessing the device,
  384. additional drivers must be enabled in order to use the functionality
  385. of the device
  386. config MFD_WM8400
  387. tristate "Support Wolfson Microelectronics WM8400"
  388. select MFD_CORE
  389. depends on I2C
  390. select REGMAP_I2C
  391. help
  392. Support for the Wolfson Microelecronics WM8400 PMIC and audio
  393. CODEC. This driver provides common support for accessing
  394. the device, additional drivers must be enabled in order to use
  395. the functionality of the device.
  396. config MFD_WM831X
  397. bool
  398. depends on GENERIC_HARDIRQS
  399. config MFD_WM831X_I2C
  400. bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
  401. select MFD_CORE
  402. select MFD_WM831X
  403. select REGMAP_I2C
  404. depends on I2C=y && GENERIC_HARDIRQS
  405. help
  406. Support for the Wolfson Microelecronics WM831x and WM832x PMICs
  407. when controlled using I2C. This driver provides common support
  408. for accessing the device, additional drivers must be enabled in
  409. order to use the functionality of the device.
  410. config MFD_WM831X_SPI
  411. bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
  412. select MFD_CORE
  413. select MFD_WM831X
  414. select REGMAP_SPI
  415. depends on SPI_MASTER && GENERIC_HARDIRQS
  416. help
  417. Support for the Wolfson Microelecronics WM831x and WM832x PMICs
  418. when controlled using SPI. This driver provides common support
  419. for accessing the device, additional drivers must be enabled in
  420. order to use the functionality of the device.
  421. config MFD_WM8350
  422. bool
  423. depends on GENERIC_HARDIRQS
  424. config MFD_WM8350_CONFIG_MODE_0
  425. bool
  426. depends on MFD_WM8350
  427. config MFD_WM8350_CONFIG_MODE_1
  428. bool
  429. depends on MFD_WM8350
  430. config MFD_WM8350_CONFIG_MODE_2
  431. bool
  432. depends on MFD_WM8350
  433. config MFD_WM8350_CONFIG_MODE_3
  434. bool
  435. depends on MFD_WM8350
  436. config MFD_WM8351_CONFIG_MODE_0
  437. bool
  438. depends on MFD_WM8350
  439. config MFD_WM8351_CONFIG_MODE_1
  440. bool
  441. depends on MFD_WM8350
  442. config MFD_WM8351_CONFIG_MODE_2
  443. bool
  444. depends on MFD_WM8350
  445. config MFD_WM8351_CONFIG_MODE_3
  446. bool
  447. depends on MFD_WM8350
  448. config MFD_WM8352_CONFIG_MODE_0
  449. bool
  450. depends on MFD_WM8350
  451. config MFD_WM8352_CONFIG_MODE_1
  452. bool
  453. depends on MFD_WM8350
  454. config MFD_WM8352_CONFIG_MODE_2
  455. bool
  456. depends on MFD_WM8350
  457. config MFD_WM8352_CONFIG_MODE_3
  458. bool
  459. depends on MFD_WM8350
  460. config MFD_WM8350_I2C
  461. bool "Support Wolfson Microelectronics WM8350 with I2C"
  462. select MFD_WM8350
  463. depends on I2C=y && GENERIC_HARDIRQS
  464. help
  465. The WM8350 is an integrated audio and power management
  466. subsystem with watchdog and RTC functionality for embedded
  467. systems. This option enables core support for the WM8350 with
  468. I2C as the control interface. Additional options must be
  469. selected to enable support for the functionality of the chip.
  470. config MFD_WM8994
  471. bool "Support Wolfson Microelectronics WM8994"
  472. select MFD_CORE
  473. select REGMAP_I2C
  474. select REGMAP_IRQ
  475. depends on I2C=y && GENERIC_HARDIRQS
  476. help
  477. The WM8994 is a highly integrated hi-fi CODEC designed for
  478. smartphone applicatiosn. As well as audio functionality it
  479. has on board GPIO and regulator functionality which is
  480. supported via the relevant subsystems. This driver provides
  481. core support for the WM8994, in order to use the actual
  482. functionaltiy of the device other drivers must be enabled.
  483. config MFD_PCF50633
  484. tristate "Support for NXP PCF50633"
  485. depends on I2C
  486. select REGMAP_I2C
  487. help
  488. Say yes here if you have NXP PCF50633 chip on your board.
  489. This core driver provides register access and IRQ handling
  490. facilities, and registers devices for the various functions
  491. so that function-specific drivers can bind to them.
  492. config PCF50633_ADC
  493. tristate "Support for NXP PCF50633 ADC"
  494. depends on MFD_PCF50633
  495. help
  496. Say yes here if you want to include support for ADC in the
  497. NXP PCF50633 chip.
  498. config PCF50633_GPIO
  499. tristate "Support for NXP PCF50633 GPIO"
  500. depends on MFD_PCF50633
  501. help
  502. Say yes here if you want to include support GPIO for pins on
  503. the PCF50633 chip.
  504. config MFD_MC13783
  505. tristate
  506. config MFD_MC13XXX
  507. tristate "Support Freescale MC13783 and MC13892"
  508. depends on SPI_MASTER
  509. select MFD_CORE
  510. select MFD_MC13783
  511. help
  512. Support for the Freescale (Atlas) PMIC and audio CODECs
  513. MC13783 and MC13892.
  514. This driver provides common support for accessing the device,
  515. additional drivers must be enabled in order to use the
  516. functionality of the device.
  517. config ABX500_CORE
  518. bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
  519. default y if ARCH_U300 || ARCH_U8500
  520. help
  521. Say yes here if you have the ABX500 Mixed Signal IC family
  522. chips. This core driver expose register access functions.
  523. Functionality specific drivers using these functions can
  524. remain unchanged when IC changes. Binding of the functions to
  525. actual register access is done by the IC core driver.
  526. config AB3100_CORE
  527. bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
  528. depends on I2C=y && ABX500_CORE
  529. select MFD_CORE
  530. default y if ARCH_U300
  531. help
  532. Select this to enable the AB3100 Mixed Signal IC core
  533. functionality. This connects to a AB3100 on the I2C bus
  534. and expose a number of symbols needed for dependent devices
  535. to read and write registers and subscribe to events from
  536. this multi-functional IC. This is needed to use other features
  537. of the AB3100 such as battery-backed RTC, charging control,
  538. LEDs, vibrator, system power and temperature, power management
  539. and ALSA sound.
  540. config AB3100_OTP
  541. tristate "ST-Ericsson AB3100 OTP functions"
  542. depends on AB3100_CORE
  543. default y if AB3100_CORE
  544. help
  545. Select this to enable the AB3100 Mixed Signal IC OTP (one-time
  546. programmable memory) support. This exposes a sysfs file to read
  547. out OTP values.
  548. config EZX_PCAP
  549. bool "PCAP Support"
  550. depends on GENERIC_HARDIRQS && SPI_MASTER
  551. help
  552. This enables the PCAP ASIC present on EZX Phones. This is
  553. needed for MMC, TouchScreen, Sound, USB, etc..
  554. config AB5500_CORE
  555. bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
  556. depends on ABX500_CORE && MFD_DB5500_PRCMU
  557. select MFD_CORE
  558. help
  559. Select this option to enable access to AB5500 power management
  560. chip. This connects to the db5500 chip via the I2C bus via PRCMU.
  561. This chip embeds various other multimedia funtionalities as well.
  562. config AB5500_DEBUG
  563. bool "Enable debug info via debugfs"
  564. depends on AB5500_CORE && DEBUG_FS
  565. default y if DEBUG_FS
  566. help
  567. Select this option if you want debug information from the AB5500
  568. using the debug filesystem, debugfs.
  569. config AB8500_CORE
  570. bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
  571. depends on GENERIC_HARDIRQS && ABX500_CORE
  572. select MFD_CORE
  573. help
  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.
  579. config AB8500_I2C_CORE
  580. bool "AB8500 register access via PRCMU I2C"
  581. depends on AB8500_CORE && MFD_DB8500_PRCMU
  582. default y
  583. help
  584. This enables register access to the AB8500 chip via PRCMU I2C.
  585. The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
  586. the I2C bus is connected to the Power Reset
  587. and Mangagement Unit, PRCMU.
  588. config AB8500_DEBUG
  589. bool "Enable debug info via debugfs"
  590. depends on AB8500_CORE && DEBUG_FS
  591. default y if DEBUG_FS
  592. help
  593. Select this option if you want debug information using the debug
  594. filesystem, debugfs.
  595. config AB8500_GPADC
  596. bool "AB8500 GPADC driver"
  597. depends on AB8500_CORE && REGULATOR_AB8500
  598. default y
  599. help
  600. AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
  601. config MFD_DB8500_PRCMU
  602. bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
  603. depends on UX500_SOC_DB8500
  604. select MFD_CORE
  605. help
  606. Select this option to enable support for the DB8500 Power Reset
  607. and Control Management Unit. This is basically an autonomous
  608. system controller running an XP70 microprocessor, which is accessed
  609. through a register map.
  610. config MFD_DB5500_PRCMU
  611. bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
  612. depends on UX500_SOC_DB5500
  613. select MFD_CORE
  614. help
  615. Select this option to enable support for the DB5500 Power Reset
  616. and Control Management Unit. This is basically an autonomous
  617. system controller running an XP70 microprocessor, which is accessed
  618. through a register map.
  619. config MFD_CS5535
  620. tristate "Support for CS5535 and CS5536 southbridge core functions"
  621. select MFD_CORE
  622. depends on PCI && X86
  623. ---help---
  624. This is the core driver for CS5535/CS5536 MFD functions. This is
  625. necessary for using the board's GPIO and MFGPT functionality.
  626. config MFD_TIMBERDALE
  627. tristate "Support for the Timberdale FPGA"
  628. select MFD_CORE
  629. depends on PCI && GPIOLIB
  630. ---help---
  631. This is the core driver for the timberdale FPGA. This device is a
  632. multifunction device which exposes numerous platform devices.
  633. The timberdale FPGA can be found on the Intel Atom development board
  634. for in-vehicle infontainment, called Russellville.
  635. config LPC_SCH
  636. tristate "Intel SCH LPC"
  637. depends on PCI
  638. select MFD_CORE
  639. help
  640. LPC bridge function of the Intel SCH provides support for
  641. System Management Bus and General Purpose I/O.
  642. config MFD_RDC321X
  643. tristate "Support for RDC-R321x southbridge"
  644. select MFD_CORE
  645. depends on PCI
  646. help
  647. Say yes here if you want to have support for the RDC R-321x SoC
  648. southbridge which provides access to GPIOs and Watchdog using the
  649. southbridge PCI device configuration space.
  650. config MFD_JANZ_CMODIO
  651. tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
  652. select MFD_CORE
  653. depends on PCI
  654. help
  655. This is the core driver for the Janz CMOD-IO PCI MODULbus
  656. carrier board. This device is a PCI to MODULbus bridge which may
  657. host many different types of MODULbus daughterboards, including
  658. CAN and GPIO controllers.
  659. config MFD_JZ4740_ADC
  660. bool "Support for the JZ4740 SoC ADC core"
  661. select MFD_CORE
  662. select GENERIC_IRQ_CHIP
  663. depends on MACH_JZ4740
  664. help
  665. Say yes here if you want support for the ADC unit in the JZ4740 SoC.
  666. This driver is necessary for jz4740-battery and jz4740-hwmon driver.
  667. config MFD_VX855
  668. tristate "Support for VIA VX855/VX875 integrated south bridge"
  669. depends on PCI
  670. select MFD_CORE
  671. help
  672. Say yes here to enable support for various functions of the
  673. VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
  674. and/or vx855_gpio drivers for this to do anything useful.
  675. config MFD_WL1273_CORE
  676. tristate "Support for TI WL1273 FM radio."
  677. depends on I2C
  678. select MFD_CORE
  679. default n
  680. help
  681. This is the core driver for the TI WL1273 FM radio. This MFD
  682. driver connects the radio-wl1273 V4L2 module and the wl1273
  683. audio codec.
  684. config MFD_OMAP_USB_HOST
  685. bool "Support OMAP USBHS core driver"
  686. depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
  687. default y
  688. help
  689. This is the core driver for the OAMP EHCI and OHCI drivers.
  690. This MFD driver does the required setup functionalities for
  691. OMAP USB Host drivers.
  692. config MFD_PM8XXX
  693. tristate
  694. config MFD_PM8921_CORE
  695. tristate "Qualcomm PM8921 PMIC chip"
  696. depends on MSM_SSBI
  697. select MFD_CORE
  698. select MFD_PM8XXX
  699. help
  700. If you say yes to this option, support will be included for the
  701. built-in PM8921 PMIC chip.
  702. This is required if your board has a PM8921 and uses its features,
  703. such as: MPPs, GPIOs, regulators, interrupts, and PWM.
  704. Say M here if you want to include support for PM8921 chip as a module.
  705. This will build a module called "pm8921-core".
  706. config MFD_PM8XXX_IRQ
  707. bool "Support for Qualcomm PM8xxx IRQ features"
  708. depends on MFD_PM8XXX
  709. default y if MFD_PM8XXX
  710. help
  711. This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
  712. This is required to use certain other PM 8xxx features, such as GPIO
  713. and MPP.
  714. config TPS65911_COMPARATOR
  715. tristate
  716. config MFD_AAT2870_CORE
  717. bool "Support for the AnalogicTech AAT2870"
  718. select MFD_CORE
  719. depends on I2C=y && GPIOLIB
  720. help
  721. If you say yes here you get support for the AAT2870.
  722. This driver provides common support for accessing the device,
  723. additional drivers must be enabled in order to use the
  724. functionality of the device.
  725. config MFD_INTEL_MSIC
  726. bool "Support for Intel MSIC"
  727. depends on INTEL_SCU_IPC
  728. select MFD_CORE
  729. help
  730. Select this option to enable access to Intel MSIC (Avatele
  731. Passage) chip. This chip embeds audio, battery, GPIO, etc.
  732. devices used in Intel Medfield platforms.
  733. config MFD_RC5T583
  734. bool "Ricoh RC5T583 Power Management system device"
  735. depends on I2C=y && GENERIC_HARDIRQS
  736. select MFD_CORE
  737. select REGMAP_I2C
  738. help
  739. Select this option to get support for the RICOH583 Power
  740. Management system device.
  741. This driver provides common support for accessing the device
  742. through i2c interface. The device supports multiple sub-devices
  743. like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
  744. Additional drivers must be enabled in order to use the
  745. different functionality of the device.
  746. config MFD_ANATOP
  747. bool "Support for Freescale i.MX on-chip ANATOP controller"
  748. depends on SOC_IMX6Q
  749. help
  750. Select this option to enable Freescale i.MX on-chip ANATOP
  751. MFD controller. This controller embeds regulator and
  752. thermal devices for Freescale i.MX platforms.
  753. endmenu
  754. endif
  755. menu "Multimedia Capabilities Port drivers"
  756. depends on ARCH_SA1100
  757. config MCP
  758. tristate
  759. # Interface drivers
  760. config MCP_SA11X0
  761. tristate "Support SA11x0 MCP interface"
  762. depends on ARCH_SA1100
  763. select MCP
  764. # Chip drivers
  765. config MCP_UCB1200
  766. tristate "Support for UCB1200 / UCB1300"
  767. depends on MCP
  768. config MCP_UCB1200_TS
  769. tristate "Touchscreen interface support"
  770. depends on MCP_UCB1200 && INPUT
  771. endmenu