Kconfig 30 KB

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