Kconfig 32 KB

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