Kconfig 22 KB

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