Kconfig 24 KB

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