Kconfig 35 KB

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