Kconfig 25 KB

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