Kconfig 36 KB

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