Kconfig 29 KB

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