Kconfig 36 KB

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