Kconfig 29 KB

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