Kconfig 31 KB

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