Kconfig 30 KB

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