Kconfig 28 KB

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