Kconfig 30 KB

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