Kconfig 23 KB

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