Kconfig 24 KB

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