Kconfig 24 KB

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