Kconfig 34 KB

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