Kconfig 28 KB

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