Kconfig 29 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961
  1. #
  2. # Multifunction miscellaneous devices
  3. #
  4. if HAS_IOMEM
  5. menu "Multifunction device drivers"
  6. config MFD_CORE
  7. tristate
  8. default n
  9. config MFD_88PM860X
  10. bool "Support Marvell 88PM8606/88PM8607"
  11. depends on I2C=y && GENERIC_HARDIRQS
  12. select REGMAP_I2C
  13. select MFD_CORE
  14. help
  15. This supports for Marvell 88PM8606/88PM8607 Power Management IC.
  16. This includes the I2C driver and the core APIs _only_, you have to
  17. select individual components like voltage regulators, RTC and
  18. battery-charger under the corresponding menus.
  19. config MFD_SM501
  20. tristate "Support for Silicon Motion SM501"
  21. ---help---
  22. This is the core driver for the Silicon Motion SM501 multimedia
  23. companion chip. This device is a multifunction device which may
  24. provide numerous interfaces including USB host controller, USB gadget,
  25. asynchronous serial ports, audio functions, and a dual display video
  26. interface. The device may be connected by PCI or local bus with
  27. varying functions enabled.
  28. config MFD_SM501_GPIO
  29. bool "Export GPIO via GPIO layer"
  30. depends on MFD_SM501 && GPIOLIB
  31. ---help---
  32. This option uses the gpio library layer to export the 64 GPIO
  33. lines on the SM501. The platform data is used to supply the
  34. base number for the first GPIO line to register.
  35. config MFD_ASIC3
  36. bool "Support for Compaq ASIC3"
  37. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  38. select MFD_CORE
  39. ---help---
  40. This driver supports the ASIC3 multifunction chip found on many
  41. PDAs (mainly iPAQ and HTC based ones)
  42. config MFD_DAVINCI_VOICECODEC
  43. tristate
  44. select MFD_CORE
  45. config MFD_DM355EVM_MSP
  46. bool "DaVinci DM355 EVM microcontroller"
  47. depends on I2C=y && MACH_DAVINCI_DM355_EVM
  48. help
  49. This driver supports the MSP430 microcontroller used on these
  50. boards. MSP430 firmware manages resets and power sequencing,
  51. inputs from buttons and the IR remote, LEDs, an RTC, and more.
  52. config MFD_TI_SSP
  53. tristate "TI Sequencer Serial Port support"
  54. depends on ARCH_DAVINCI_TNETV107X
  55. select MFD_CORE
  56. ---help---
  57. Say Y here if you want support for the Sequencer Serial Port
  58. in a Texas Instruments TNETV107X SoC.
  59. To compile this driver as a module, choose M here: the
  60. module will be called ti-ssp.
  61. config HTC_EGPIO
  62. bool "HTC EGPIO support"
  63. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  64. help
  65. This driver supports the CPLD egpio chip present on
  66. several HTC phones. It provides basic support for input
  67. pins, output pins, and irqs.
  68. config HTC_PASIC3
  69. tristate "HTC PASIC3 LED/DS1WM chip support"
  70. select MFD_CORE
  71. help
  72. This core driver provides register access for the LED/DS1WM
  73. chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
  74. HTC Magician devices, respectively. Actual functionality is
  75. handled by the leds-pasic3 and ds1wm drivers.
  76. config HTC_I2CPLD
  77. bool "HTC I2C PLD chip support"
  78. depends on I2C=y && GPIOLIB
  79. help
  80. If you say yes here you get support for the supposed CPLD
  81. found on omap850 HTC devices like the HTC Wizard and HTC Herald.
  82. This device provides input and output GPIOs through an I2C
  83. interface to one or more sub-chips.
  84. config UCB1400_CORE
  85. tristate "Philips UCB1400 Core driver"
  86. depends on AC97_BUS
  87. depends on GPIOLIB
  88. help
  89. This enables support for the Philips UCB1400 core functions.
  90. The UCB1400 is an AC97 audio codec.
  91. To compile this driver as a module, choose M here: the
  92. module will be called ucb1400_core.
  93. config MFD_LM3533
  94. tristate "LM3533 Lighting Power chip"
  95. depends on I2C
  96. select MFD_CORE
  97. select REGMAP_I2C
  98. help
  99. Say yes here to enable support for National Semiconductor / TI
  100. LM3533 Lighting Power chips.
  101. This driver provides common support for accessing the device;
  102. additional drivers must be enabled in order to use the LED,
  103. backlight or ambient-light-sensor functionality of the device.
  104. config TPS6105X
  105. tristate "TPS61050/61052 Boost Converters"
  106. depends on I2C
  107. select REGULATOR
  108. select MFD_CORE
  109. select REGULATOR_FIXED_VOLTAGE
  110. help
  111. This option enables a driver for the TP61050/TPS61052
  112. high-power "white LED driver". This boost converter is
  113. sometimes used for other things than white LEDs, and
  114. also contains a GPIO pin.
  115. config TPS65010
  116. tristate "TPS6501x Power Management chips"
  117. depends on I2C && GPIOLIB
  118. default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
  119. help
  120. If you say yes here you get support for the TPS6501x series of
  121. Power Management chips. These include voltage regulators,
  122. lithium ion/polymer battery charging, and other features that
  123. are often used in portable devices like cell phones and cameras.
  124. This driver can also be built as a module. If so, the module
  125. will be called tps65010.
  126. config TPS6507X
  127. tristate "TPS6507x Power Management / Touch Screen chips"
  128. select MFD_CORE
  129. depends on I2C
  130. help
  131. If you say yes here you get support for the TPS6507x series of
  132. Power Management / Touch Screen chips. These include voltage
  133. regulators, lithium ion/polymer battery charging, touch screen
  134. and other features that are often used in portable devices.
  135. This driver can also be built as a module. If so, the module
  136. will be called tps6507x.
  137. config MFD_TPS65217
  138. tristate "TPS65217 Power Management / White LED chips"
  139. depends on I2C
  140. select MFD_CORE
  141. select REGMAP_I2C
  142. help
  143. If you say yes here you get support for the TPS65217 series of
  144. Power Management / White LED chips.
  145. These include voltage regulators, lithium ion/polymer battery
  146. charger, wled and other features that are often used in portable
  147. devices.
  148. This driver can also be built as a module. If so, the module
  149. will be called tps65217.
  150. config MFD_TPS6586X
  151. bool "TPS6586x Power Management chips"
  152. depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
  153. select MFD_CORE
  154. help
  155. If you say yes here you get support for the TPS6586X series of
  156. Power Management chips.
  157. This driver provides common support for accessing the device,
  158. additional drivers must be enabled in order to use the
  159. functionality of the device.
  160. This driver can also be built as a module. If so, the module
  161. will be called tps6586x.
  162. config MFD_TPS65910
  163. bool "TPS65910 Power Management chip"
  164. depends on I2C=y && GPIOLIB
  165. select MFD_CORE
  166. select GPIO_TPS65910
  167. select REGMAP_I2C
  168. help
  169. if you say yes here you get support for the TPS65910 series of
  170. Power Management chips.
  171. config MFD_TPS65912
  172. bool
  173. depends on GPIOLIB
  174. config MFD_TPS65912_I2C
  175. bool "TPS65912 Power Management chip with I2C"
  176. select MFD_CORE
  177. select MFD_TPS65912
  178. depends on I2C=y && GPIOLIB
  179. help
  180. If you say yes here you get support for the TPS65912 series of
  181. PM chips with I2C interface.
  182. config MFD_TPS65912_SPI
  183. bool "TPS65912 Power Management chip with SPI"
  184. select MFD_CORE
  185. select MFD_TPS65912
  186. depends on SPI_MASTER && GPIOLIB
  187. help
  188. If you say yes here you get support for the TPS65912 series of
  189. PM chips with SPI interface.
  190. config MENELAUS
  191. bool "Texas Instruments TWL92330/Menelaus PM chip"
  192. depends on I2C=y && ARCH_OMAP2
  193. help
  194. If you say yes here you get support for the Texas Instruments
  195. TWL92330/Menelaus Power Management chip. This include voltage
  196. regulators, Dual slot memory card transceivers, real-time clock
  197. and other features that are often used in portable devices like
  198. cell phones and PDAs.
  199. config TWL4030_CORE
  200. bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
  201. depends on I2C=y && GENERIC_HARDIRQS
  202. select IRQ_DOMAIN
  203. help
  204. Say yes here if you have TWL4030 / TWL6030 family chip on your board.
  205. This core driver provides register access and IRQ handling
  206. facilities, and registers devices for the various functions
  207. so that function-specific drivers can bind to them.
  208. These multi-function chips are found on many OMAP2 and OMAP3
  209. boards, providing power management, RTC, GPIO, keypad, a
  210. high speed USB OTG transceiver, an audio codec (on most
  211. versions) and many other features.
  212. config TWL4030_MADC
  213. tristate "Texas Instruments TWL4030 MADC"
  214. depends on TWL4030_CORE
  215. help
  216. This driver provides support for triton TWL4030-MADC. The
  217. driver supports both RT and SW conversion methods.
  218. This driver can be built as a module. If so it will be
  219. named twl4030-madc
  220. config TWL4030_POWER
  221. bool "Support power resources on TWL4030 family chips"
  222. depends on TWL4030_CORE && ARM
  223. help
  224. Say yes here if you want to use the power resources on the
  225. TWL4030 family chips. Most of these resources are regulators,
  226. which have a separate driver; some are control signals, such
  227. as clock request handshaking.
  228. This driver uses board-specific data to initialize the resources
  229. and load scripts controlling which resources are switched off/on
  230. or reset when a sleep, wakeup or warm reset event occurs.
  231. config MFD_TWL4030_AUDIO
  232. bool
  233. depends on TWL4030_CORE
  234. select MFD_CORE
  235. default n
  236. config TWL6030_PWM
  237. tristate "TWL6030 PWM (Pulse Width Modulator) Support"
  238. depends on TWL4030_CORE
  239. select HAVE_PWM
  240. default n
  241. help
  242. Say yes here if you want support for TWL6030 PWM.
  243. This is used to control charging LED brightness.
  244. config TWL6040_CORE
  245. bool "Support for TWL6040 audio codec"
  246. depends on I2C=y && GENERIC_HARDIRQS
  247. select MFD_CORE
  248. select REGMAP_I2C
  249. default n
  250. help
  251. Say yes here if you want support for Texas Instruments TWL6040 audio
  252. codec.
  253. This driver provides common support for accessing the device,
  254. additional drivers must be enabled in order to use the
  255. functionality of the device (audio, vibra).
  256. config MFD_STMPE
  257. bool "Support STMicroelectronics STMPE"
  258. depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
  259. select MFD_CORE
  260. help
  261. Support for the STMPE family of I/O Expanders from
  262. STMicroelectronics.
  263. Currently supported devices are:
  264. STMPE811: GPIO, Touchscreen
  265. STMPE1601: GPIO, Keypad
  266. STMPE2401: GPIO, Keypad
  267. STMPE2403: GPIO, Keypad
  268. This driver provides common support for accessing the device,
  269. additional drivers must be enabled in order to use the functionality
  270. of the device. Currently available sub drivers are:
  271. GPIO: stmpe-gpio
  272. Keypad: stmpe-keypad
  273. Touchscreen: stmpe-ts
  274. menu "STMPE Interface Drivers"
  275. depends on MFD_STMPE
  276. config STMPE_I2C
  277. bool "STMPE I2C Inteface"
  278. depends on I2C=y
  279. default y
  280. help
  281. This is used to enable I2C interface of STMPE
  282. config STMPE_SPI
  283. bool "STMPE SPI Inteface"
  284. depends on SPI_MASTER
  285. help
  286. This is used to enable SPI interface of STMPE
  287. endmenu
  288. config MFD_TC3589X
  289. bool "Support Toshiba TC35892 and variants"
  290. depends on I2C=y && GENERIC_HARDIRQS
  291. select MFD_CORE
  292. help
  293. Support for the Toshiba TC35892 and variants I/O Expander.
  294. This driver provides common support for accessing the device,
  295. additional drivers must be enabled in order to use the
  296. functionality of the device.
  297. config MFD_TMIO
  298. bool
  299. default n
  300. config MFD_T7L66XB
  301. bool "Support Toshiba T7L66XB"
  302. depends on ARM && HAVE_CLK
  303. select MFD_CORE
  304. select MFD_TMIO
  305. help
  306. Support for Toshiba Mobile IO Controller T7L66XB
  307. config MFD_TC6387XB
  308. bool "Support Toshiba TC6387XB"
  309. depends on ARM && HAVE_CLK
  310. select MFD_CORE
  311. select MFD_TMIO
  312. help
  313. Support for Toshiba Mobile IO Controller TC6387XB
  314. config MFD_TC6393XB
  315. bool "Support Toshiba TC6393XB"
  316. depends on GPIOLIB && ARM && HAVE_CLK
  317. select MFD_CORE
  318. select MFD_TMIO
  319. help
  320. Support for Toshiba Mobile IO Controller TC6393XB
  321. config PMIC_DA903X
  322. bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
  323. depends on I2C=y
  324. help
  325. Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
  326. ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
  327. usually found on PXA processors-based platforms. This includes
  328. the I2C driver and the core APIs _only_, you have to select
  329. individual components like LCD backlight, voltage regulators,
  330. LEDs and battery-charger under the corresponding menus.
  331. config PMIC_DA9052
  332. bool
  333. select MFD_CORE
  334. config MFD_DA9052_SPI
  335. bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
  336. select REGMAP_SPI
  337. select REGMAP_IRQ
  338. select PMIC_DA9052
  339. depends on SPI_MASTER=y
  340. help
  341. Support for the Dialog Semiconductor DA9052 PMIC
  342. when controlled using SPI. This driver provides common support
  343. for accessing the device, additional drivers must be enabled in
  344. order to use the functionality of the device.
  345. config MFD_DA9052_I2C
  346. bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
  347. select REGMAP_I2C
  348. select REGMAP_IRQ
  349. select PMIC_DA9052
  350. depends on I2C=y
  351. help
  352. Support for the Dialog Semiconductor DA9052 PMIC
  353. when controlled using I2C. This driver provides common support
  354. for accessing the device, additional drivers must be enabled in
  355. order to use the functionality of the device.
  356. config PMIC_ADP5520
  357. bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
  358. depends on I2C=y
  359. help
  360. Say yes here to add support for Analog Devices AD5520 and ADP5501,
  361. Multifunction Power Management IC. This includes
  362. the I2C driver and the core APIs _only_, you have to select
  363. individual components like LCD backlight, LEDs, GPIOs and Kepad
  364. under the corresponding menus.
  365. config MFD_MAX8925
  366. bool "Maxim Semiconductor MAX8925 PMIC Support"
  367. depends on I2C=y && GENERIC_HARDIRQS
  368. select MFD_CORE
  369. help
  370. Say yes here to support for Maxim Semiconductor MAX8925. This is
  371. a Power Management IC. This driver provies common support for
  372. accessing the device, additional drivers must be enabled in order
  373. to use the functionality of the device.
  374. config MFD_MAX8997
  375. bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
  376. depends on I2C=y && GENERIC_HARDIRQS
  377. select MFD_CORE
  378. help
  379. Say yes here to support for Maxim Semiconductor MAX8997/8966.
  380. This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
  381. MUIC controls on chip.
  382. This driver provides common support for accessing the device;
  383. additional drivers must be enabled in order to use the functionality
  384. of the device.
  385. config MFD_MAX8998
  386. bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
  387. depends on I2C=y && GENERIC_HARDIRQS
  388. select MFD_CORE
  389. help
  390. Say yes here to support for Maxim Semiconductor MAX8998 and
  391. National Semiconductor LP3974. This is a Power Management IC.
  392. This driver provies common support for accessing the device,
  393. additional drivers must be enabled in order to use the functionality
  394. of the device.
  395. config MFD_S5M_CORE
  396. bool "SAMSUNG S5M Series Support"
  397. depends on I2C=y && GENERIC_HARDIRQS
  398. select MFD_CORE
  399. select REGMAP_I2C
  400. help
  401. Support for the Samsung Electronics S5M MFD series.
  402. This driver provies common support for accessing the device,
  403. additional drivers must be enabled in order to use the functionality
  404. of the device
  405. config MFD_WM8400
  406. tristate "Support Wolfson Microelectronics WM8400"
  407. select MFD_CORE
  408. depends on I2C
  409. select REGMAP_I2C
  410. help
  411. Support for the Wolfson Microelecronics WM8400 PMIC and audio
  412. CODEC. This driver provides common support for accessing
  413. the device, additional drivers must be enabled in order to use
  414. the functionality of the device.
  415. config MFD_WM831X
  416. bool
  417. depends on GENERIC_HARDIRQS
  418. config MFD_WM831X_I2C
  419. bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
  420. select MFD_CORE
  421. select MFD_WM831X
  422. select REGMAP_I2C
  423. depends on I2C=y && GENERIC_HARDIRQS
  424. help
  425. Support for the Wolfson Microelecronics WM831x and WM832x PMICs
  426. when controlled using I2C. This driver provides common support
  427. for accessing the device, additional drivers must be enabled in
  428. order to use the functionality of the device.
  429. config MFD_WM831X_SPI
  430. bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
  431. select MFD_CORE
  432. select MFD_WM831X
  433. select REGMAP_SPI
  434. depends on SPI_MASTER && GENERIC_HARDIRQS
  435. help
  436. Support for the Wolfson Microelecronics WM831x and WM832x PMICs
  437. when controlled using SPI. This driver provides common support
  438. for accessing the device, additional drivers must be enabled in
  439. order to use the functionality of the device.
  440. config MFD_WM8350
  441. bool
  442. depends on GENERIC_HARDIRQS
  443. config MFD_WM8350_CONFIG_MODE_0
  444. bool
  445. depends on MFD_WM8350
  446. config MFD_WM8350_CONFIG_MODE_1
  447. bool
  448. depends on MFD_WM8350
  449. config MFD_WM8350_CONFIG_MODE_2
  450. bool
  451. depends on MFD_WM8350
  452. config MFD_WM8350_CONFIG_MODE_3
  453. bool
  454. depends on MFD_WM8350
  455. config MFD_WM8351_CONFIG_MODE_0
  456. bool
  457. depends on MFD_WM8350
  458. config MFD_WM8351_CONFIG_MODE_1
  459. bool
  460. depends on MFD_WM8350
  461. config MFD_WM8351_CONFIG_MODE_2
  462. bool
  463. depends on MFD_WM8350
  464. config MFD_WM8351_CONFIG_MODE_3
  465. bool
  466. depends on MFD_WM8350
  467. config MFD_WM8352_CONFIG_MODE_0
  468. bool
  469. depends on MFD_WM8350
  470. config MFD_WM8352_CONFIG_MODE_1
  471. bool
  472. depends on MFD_WM8350
  473. config MFD_WM8352_CONFIG_MODE_2
  474. bool
  475. depends on MFD_WM8350
  476. config MFD_WM8352_CONFIG_MODE_3
  477. bool
  478. depends on MFD_WM8350
  479. config MFD_WM8350_I2C
  480. bool "Support Wolfson Microelectronics WM8350 with I2C"
  481. select MFD_WM8350
  482. depends on I2C=y && GENERIC_HARDIRQS
  483. help
  484. The WM8350 is an integrated audio and power management
  485. subsystem with watchdog and RTC functionality for embedded
  486. systems. This option enables core support for the WM8350 with
  487. I2C as the control interface. Additional options must be
  488. selected to enable support for the functionality of the chip.
  489. config MFD_WM8994
  490. bool "Support Wolfson Microelectronics WM8994"
  491. select MFD_CORE
  492. select REGMAP_I2C
  493. select REGMAP_IRQ
  494. depends on I2C=y && GENERIC_HARDIRQS
  495. help
  496. The WM8994 is a highly integrated hi-fi CODEC designed for
  497. smartphone applicatiosn. As well as audio functionality it
  498. has on board GPIO and regulator functionality which is
  499. supported via the relevant subsystems. This driver provides
  500. core support for the WM8994, in order to use the actual
  501. functionaltiy of the device other drivers must be enabled.
  502. config MFD_PCF50633
  503. tristate "Support for NXP PCF50633"
  504. depends on I2C
  505. select REGMAP_I2C
  506. help
  507. Say yes here if you have NXP PCF50633 chip on your board.
  508. This core driver provides register access and IRQ handling
  509. facilities, and registers devices for the various functions
  510. so that function-specific drivers can bind to them.
  511. config PCF50633_ADC
  512. tristate "Support for NXP PCF50633 ADC"
  513. depends on MFD_PCF50633
  514. help
  515. Say yes here if you want to include support for ADC in the
  516. NXP PCF50633 chip.
  517. config PCF50633_GPIO
  518. tristate "Support for NXP PCF50633 GPIO"
  519. depends on MFD_PCF50633
  520. help
  521. Say yes here if you want to include support GPIO for pins on
  522. the PCF50633 chip.
  523. config MFD_MC13783
  524. tristate
  525. config MFD_MC13XXX
  526. tristate "Support Freescale MC13783 and MC13892"
  527. depends on SPI_MASTER || I2C
  528. select MFD_CORE
  529. select MFD_MC13783
  530. help
  531. Enable support for the Freescale MC13783 and MC13892 PMICs.
  532. This driver provides common support for accessing the device,
  533. additional drivers must be enabled in order to use the
  534. functionality of the device.
  535. if MFD_MC13XXX
  536. config MFD_MC13XXX_SPI
  537. tristate "MC13xxx SPI interface" if SPI_MASTER
  538. default SPI_MASTER
  539. select REGMAP_SPI
  540. help
  541. Select this if your MC13xxx is connected via an SPI bus.
  542. config MFD_MC13XXX_I2C
  543. tristate "MC13xxx I2C interface" if I2C
  544. default I2C
  545. select REGMAP_I2C
  546. help
  547. Select this if your MC13xxx is connected via an I2C bus.
  548. endif
  549. config ABX500_CORE
  550. bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
  551. default y if ARCH_U300 || ARCH_U8500
  552. help
  553. Say yes here if you have the ABX500 Mixed Signal IC family
  554. chips. This core driver expose register access functions.
  555. Functionality specific drivers using these functions can
  556. remain unchanged when IC changes. Binding of the functions to
  557. actual register access is done by the IC core driver.
  558. config AB3100_CORE
  559. bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
  560. depends on I2C=y && ABX500_CORE
  561. select MFD_CORE
  562. default y if ARCH_U300
  563. help
  564. Select this to enable the AB3100 Mixed Signal IC core
  565. functionality. This connects to a AB3100 on the I2C bus
  566. and expose a number of symbols needed for dependent devices
  567. to read and write registers and subscribe to events from
  568. this multi-functional IC. This is needed to use other features
  569. of the AB3100 such as battery-backed RTC, charging control,
  570. LEDs, vibrator, system power and temperature, power management
  571. and ALSA sound.
  572. config AB3100_OTP
  573. tristate "ST-Ericsson AB3100 OTP functions"
  574. depends on AB3100_CORE
  575. default y if AB3100_CORE
  576. help
  577. Select this to enable the AB3100 Mixed Signal IC OTP (one-time
  578. programmable memory) support. This exposes a sysfs file to read
  579. out OTP values.
  580. config EZX_PCAP
  581. bool "PCAP Support"
  582. depends on GENERIC_HARDIRQS && SPI_MASTER
  583. help
  584. This enables the PCAP ASIC present on EZX Phones. This is
  585. needed for MMC, TouchScreen, Sound, USB, etc..
  586. config AB5500_CORE
  587. bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
  588. depends on ABX500_CORE && MFD_DB5500_PRCMU
  589. select MFD_CORE
  590. help
  591. Select this option to enable access to AB5500 power management
  592. chip. This connects to the db5500 chip via the I2C bus via PRCMU.
  593. This chip embeds various other multimedia funtionalities as well.
  594. config AB5500_DEBUG
  595. bool "Enable debug info via debugfs"
  596. depends on AB5500_CORE && DEBUG_FS
  597. default y if DEBUG_FS
  598. help
  599. Select this option if you want debug information from the AB5500
  600. using the debug filesystem, debugfs.
  601. config AB8500_CORE
  602. bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
  603. depends on GENERIC_HARDIRQS && ABX500_CORE
  604. select MFD_CORE
  605. help
  606. Select this option to enable access to AB8500 power management
  607. chip. This connects to U8500 either on the SSP/SPI bus (deprecated
  608. since hardware version v1.0) or the I2C bus via PRCMU. It also adds
  609. the irq_chip parts for handling the Mixed Signal chip events.
  610. This chip embeds various other multimedia funtionalities as well.
  611. config AB8500_I2C_CORE
  612. bool "AB8500 register access via PRCMU I2C"
  613. depends on AB8500_CORE && MFD_DB8500_PRCMU
  614. default y
  615. help
  616. This enables register access to the AB8500 chip via PRCMU I2C.
  617. The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
  618. the I2C bus is connected to the Power Reset
  619. and Mangagement Unit, PRCMU.
  620. config AB8500_DEBUG
  621. bool "Enable debug info via debugfs"
  622. depends on AB8500_CORE && DEBUG_FS
  623. default y if DEBUG_FS
  624. help
  625. Select this option if you want debug information using the debug
  626. filesystem, debugfs.
  627. config AB8500_GPADC
  628. bool "AB8500 GPADC driver"
  629. depends on AB8500_CORE && REGULATOR_AB8500
  630. default y
  631. help
  632. AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
  633. config MFD_DB8500_PRCMU
  634. bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
  635. depends on UX500_SOC_DB8500
  636. select MFD_CORE
  637. help
  638. Select this option to enable support for the DB8500 Power Reset
  639. and Control Management Unit. This is basically an autonomous
  640. system controller running an XP70 microprocessor, which is accessed
  641. through a register map.
  642. config MFD_DB5500_PRCMU
  643. bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
  644. depends on UX500_SOC_DB5500
  645. select MFD_CORE
  646. help
  647. Select this option to enable support for the DB5500 Power Reset
  648. and Control Management Unit. This is basically an autonomous
  649. system controller running an XP70 microprocessor, which is accessed
  650. through a register map.
  651. config MFD_CS5535
  652. tristate "Support for CS5535 and CS5536 southbridge core functions"
  653. select MFD_CORE
  654. depends on PCI && X86
  655. ---help---
  656. This is the core driver for CS5535/CS5536 MFD functions. This is
  657. necessary for using the board's GPIO and MFGPT functionality.
  658. config MFD_TIMBERDALE
  659. tristate "Support for the Timberdale FPGA"
  660. select MFD_CORE
  661. depends on PCI && GPIOLIB
  662. ---help---
  663. This is the core driver for the timberdale FPGA. This device is a
  664. multifunction device which exposes numerous platform devices.
  665. The timberdale FPGA can be found on the Intel Atom development board
  666. for in-vehicle infontainment, called Russellville.
  667. config LPC_SCH
  668. tristate "Intel SCH LPC"
  669. depends on PCI
  670. select MFD_CORE
  671. help
  672. LPC bridge function of the Intel SCH provides support for
  673. System Management Bus and General Purpose I/O.
  674. config LPC_ICH
  675. tristate "Intel ICH LPC"
  676. depends on PCI
  677. select MFD_CORE
  678. help
  679. The LPC bridge function of the Intel ICH provides support for
  680. many functional units. This driver provides needed support for
  681. other drivers to control these functions, currently GPIO and
  682. watchdog.
  683. config MFD_RDC321X
  684. tristate "Support for RDC-R321x southbridge"
  685. select MFD_CORE
  686. depends on PCI
  687. help
  688. Say yes here if you want to have support for the RDC R-321x SoC
  689. southbridge which provides access to GPIOs and Watchdog using the
  690. southbridge PCI device configuration space.
  691. config MFD_JANZ_CMODIO
  692. tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
  693. select MFD_CORE
  694. depends on PCI
  695. help
  696. This is the core driver for the Janz CMOD-IO PCI MODULbus
  697. carrier board. This device is a PCI to MODULbus bridge which may
  698. host many different types of MODULbus daughterboards, including
  699. CAN and GPIO controllers.
  700. config MFD_JZ4740_ADC
  701. bool "Support for the JZ4740 SoC ADC core"
  702. select MFD_CORE
  703. select GENERIC_IRQ_CHIP
  704. depends on MACH_JZ4740
  705. help
  706. Say yes here if you want support for the ADC unit in the JZ4740 SoC.
  707. This driver is necessary for jz4740-battery and jz4740-hwmon driver.
  708. config MFD_VX855
  709. tristate "Support for VIA VX855/VX875 integrated south bridge"
  710. depends on PCI
  711. select MFD_CORE
  712. help
  713. Say yes here to enable support for various functions of the
  714. VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
  715. and/or vx855_gpio drivers for this to do anything useful.
  716. config MFD_WL1273_CORE
  717. tristate "Support for TI WL1273 FM radio."
  718. depends on I2C
  719. select MFD_CORE
  720. default n
  721. help
  722. This is the core driver for the TI WL1273 FM radio. This MFD
  723. driver connects the radio-wl1273 V4L2 module and the wl1273
  724. audio codec.
  725. config MFD_OMAP_USB_HOST
  726. bool "Support OMAP USBHS core driver"
  727. depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
  728. default y
  729. help
  730. This is the core driver for the OAMP EHCI and OHCI drivers.
  731. This MFD driver does the required setup functionalities for
  732. OMAP USB Host drivers.
  733. config MFD_PM8XXX
  734. tristate
  735. config MFD_PM8921_CORE
  736. tristate "Qualcomm PM8921 PMIC chip"
  737. depends on MSM_SSBI
  738. select MFD_CORE
  739. select MFD_PM8XXX
  740. help
  741. If you say yes to this option, support will be included for the
  742. built-in PM8921 PMIC chip.
  743. This is required if your board has a PM8921 and uses its features,
  744. such as: MPPs, GPIOs, regulators, interrupts, and PWM.
  745. Say M here if you want to include support for PM8921 chip as a module.
  746. This will build a module called "pm8921-core".
  747. config MFD_PM8XXX_IRQ
  748. bool "Support for Qualcomm PM8xxx IRQ features"
  749. depends on MFD_PM8XXX
  750. default y if MFD_PM8XXX
  751. help
  752. This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
  753. This is required to use certain other PM 8xxx features, such as GPIO
  754. and MPP.
  755. config TPS65911_COMPARATOR
  756. tristate
  757. config MFD_TPS65090
  758. bool "TPS65090 Power Management chips"
  759. depends on I2C=y && GENERIC_HARDIRQS
  760. select MFD_CORE
  761. select REGMAP_I2C
  762. help
  763. If you say yes here you get support for the TPS65090 series of
  764. Power Management chips.
  765. This driver provides common support for accessing the device,
  766. additional drivers must be enabled in order to use the
  767. functionality of the device.
  768. config MFD_AAT2870_CORE
  769. bool "Support for the AnalogicTech AAT2870"
  770. select MFD_CORE
  771. depends on I2C=y && GPIOLIB
  772. help
  773. If you say yes here you get support for the AAT2870.
  774. This driver provides common support for accessing the device,
  775. additional drivers must be enabled in order to use the
  776. functionality of the device.
  777. config MFD_INTEL_MSIC
  778. bool "Support for Intel MSIC"
  779. depends on INTEL_SCU_IPC
  780. select MFD_CORE
  781. help
  782. Select this option to enable access to Intel MSIC (Avatele
  783. Passage) chip. This chip embeds audio, battery, GPIO, etc.
  784. devices used in Intel Medfield platforms.
  785. config MFD_RC5T583
  786. bool "Ricoh RC5T583 Power Management system device"
  787. depends on I2C=y && GENERIC_HARDIRQS
  788. select MFD_CORE
  789. select REGMAP_I2C
  790. help
  791. Select this option to get support for the RICOH583 Power
  792. Management system device.
  793. This driver provides common support for accessing the device
  794. through i2c interface. The device supports multiple sub-devices
  795. like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
  796. Additional drivers must be enabled in order to use the
  797. different functionality of the device.
  798. config MFD_STA2X11
  799. bool "STA2X11 multi function device support"
  800. depends on STA2X11
  801. select MFD_CORE
  802. config MFD_ANATOP
  803. bool "Support for Freescale i.MX on-chip ANATOP controller"
  804. depends on SOC_IMX6Q
  805. help
  806. Select this option to enable Freescale i.MX on-chip ANATOP
  807. MFD controller. This controller embeds regulator and
  808. thermal devices for Freescale i.MX platforms.
  809. endmenu
  810. endif
  811. menu "Multimedia Capabilities Port drivers"
  812. depends on ARCH_SA1100
  813. config MCP
  814. tristate
  815. # Interface drivers
  816. config MCP_SA11X0
  817. tristate "Support SA11x0 MCP interface"
  818. depends on ARCH_SA1100
  819. select MCP
  820. # Chip drivers
  821. config MCP_UCB1200
  822. bool "Support for UCB1200 / UCB1300"
  823. depends on MCP_SA11X0
  824. select MCP
  825. config MCP_UCB1200_TS
  826. tristate "Touchscreen interface support"
  827. depends on MCP_UCB1200 && INPUT
  828. endmenu