Kconfig 29 KB

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