Kconfig 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374
  1. #
  2. # Multifunction miscellaneous devices
  3. #
  4. menu "Multifunction device drivers"
  5. depends on HAS_IOMEM
  6. config MFD_CORE
  7. tristate
  8. default n
  9. config MFD_SM501
  10. tristate "Support for Silicon Motion SM501"
  11. ---help---
  12. This is the core driver for the Silicon Motion SM501 multimedia
  13. companion chip. This device is a multifunction device which may
  14. provide numerous interfaces including USB host controller, USB gadget,
  15. asynchronous serial ports, audio functions, and a dual display video
  16. interface. The device may be connected by PCI or local bus with
  17. varying functions enabled.
  18. config MFD_SM501_GPIO
  19. bool "Export GPIO via GPIO layer"
  20. depends on MFD_SM501 && GPIOLIB
  21. ---help---
  22. This option uses the gpio library layer to export the 64 GPIO
  23. lines on the SM501. The platform data is used to supply the
  24. base number for the first GPIO line to register.
  25. config MFD_ASIC3
  26. bool "Support for Compaq ASIC3"
  27. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  28. select MFD_CORE
  29. ---help---
  30. This driver supports the ASIC3 multifunction chip found on many
  31. PDAs (mainly iPAQ and HTC based ones)
  32. config MFD_SH_MOBILE_SDHI
  33. bool "Support for SuperH Mobile SDHI"
  34. depends on SUPERH
  35. select MFD_CORE
  36. ---help---
  37. This driver supports the SDHI hardware block found in many
  38. SuperH Mobile SoCs.
  39. config MFD_DM355EVM_MSP
  40. bool "DaVinci DM355 EVM microcontroller"
  41. depends on I2C && MACH_DAVINCI_DM355_EVM
  42. help
  43. This driver supports the MSP430 microcontroller used on these
  44. boards. MSP430 firmware manages resets and power sequencing,
  45. inputs from buttons and the IR remote, LEDs, an RTC, and more.
  46. config HTC_EGPIO
  47. bool "HTC EGPIO support"
  48. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  49. help
  50. This driver supports the CPLD egpio chip present on
  51. several HTC phones. It provides basic support for input
  52. pins, output pins, and irqs.
  53. config HTC_PASIC3
  54. tristate "HTC PASIC3 LED/DS1WM chip support"
  55. select MFD_CORE
  56. help
  57. This core driver provides register access for the LED/DS1WM
  58. chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
  59. HTC Magician devices, respectively. Actual functionality is
  60. handled by the leds-pasic3 and ds1wm drivers.
  61. config UCB1400_CORE
  62. tristate "Philips UCB1400 Core driver"
  63. depends on AC97_BUS
  64. depends on GPIOLIB
  65. help
  66. This enables support for the Philips UCB1400 core functions.
  67. The UCB1400 is an AC97 audio codec.
  68. To compile this driver as a module, choose M here: the
  69. module will be called ucb1400_core.
  70. config TPS65010
  71. tristate "TPS6501x Power Management chips"
  72. depends on I2C && GPIOLIB
  73. default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
  74. help
  75. If you say yes here you get support for the TPS6501x series of
  76. Power Management chips. These include voltage regulators,
  77. lithium ion/polymer battery charging, and other features that
  78. are often used in portable devices like cell phones and cameras.
  79. This driver can also be built as a module. If so, the module
  80. will be called tps65010.
  81. config MENELAUS
  82. bool "Texas Instruments TWL92330/Menelaus PM chip"
  83. depends on I2C=y && ARCH_OMAP24XX
  84. help
  85. If you say yes here you get support for the Texas Instruments
  86. TWL92330/Menelaus Power Management chip. This include voltage
  87. regulators, Dual slot memory card transceivers, real-time clock
  88. and other features that are often used in portable devices like
  89. cell phones and PDAs.
  90. config TWL4030_CORE
  91. bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
  92. depends on I2C=y && GENERIC_HARDIRQS
  93. help
  94. Say yes here if you have TWL4030 / TWL6030 family chip on your board.
  95. This core driver provides register access and IRQ handling
  96. facilities, and registers devices for the various functions
  97. so that function-specific drivers can bind to them.
  98. These multi-function chips are found on many OMAP2 and OMAP3
  99. boards, providing power management, RTC, GPIO, keypad, a
  100. high speed USB OTG transceiver, an audio codec (on most
  101. versions) and many other features.
  102. config TWL4030_POWER
  103. bool "Support power resources on TWL4030 family chips"
  104. depends on TWL4030_CORE && ARM
  105. help
  106. Say yes here if you want to use the power resources on the
  107. TWL4030 family chips. Most of these resources are regulators,
  108. which have a separate driver; some are control signals, such
  109. as clock request handshaking.
  110. This driver uses board-specific data to initialize the resources
  111. and load scripts controling which resources are switched off/on
  112. or reset when a sleep, wakeup or warm reset event occurs.
  113. config TWL4030_CODEC
  114. bool
  115. depends on TWL4030_CORE
  116. select MFD_CORE
  117. default n
  118. config MFD_TMIO
  119. bool
  120. default n
  121. config MFD_T7L66XB
  122. bool "Support Toshiba T7L66XB"
  123. depends on ARM && HAVE_CLK
  124. select MFD_CORE
  125. select MFD_TMIO
  126. help
  127. Support for Toshiba Mobile IO Controller T7L66XB
  128. config MFD_TC6387XB
  129. bool "Support Toshiba TC6387XB"
  130. depends on ARM && HAVE_CLK
  131. select MFD_CORE
  132. select MFD_TMIO
  133. help
  134. Support for Toshiba Mobile IO Controller TC6387XB
  135. config MFD_TC6393XB
  136. bool "Support Toshiba TC6393XB"
  137. depends on GPIOLIB && ARM
  138. select MFD_CORE
  139. select MFD_TMIO
  140. help
  141. Support for Toshiba Mobile IO Controller TC6393XB
  142. config PMIC_DA903X
  143. bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
  144. depends on I2C=y
  145. help
  146. Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
  147. ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
  148. usually found on PXA processors-based platforms. This includes
  149. the I2C driver and the core APIs _only_, you have to select
  150. individual components like LCD backlight, voltage regulators,
  151. LEDs and battery-charger under the corresponding menus.
  152. config PMIC_ADP5520
  153. bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
  154. depends on I2C=y
  155. help
  156. Say yes here to add support for Analog Devices AD5520 and ADP5501,
  157. Multifunction Power Management IC. This includes
  158. the I2C driver and the core APIs _only_, you have to select
  159. individual components like LCD backlight, LEDs, GPIOs and Kepad
  160. under the corresponding menus.
  161. config MFD_WM8400
  162. tristate "Support Wolfson Microelectronics WM8400"
  163. select MFD_CORE
  164. depends on I2C
  165. help
  166. Support for the Wolfson Microelecronics WM8400 PMIC and audio
  167. CODEC. This driver provides common support for accessing
  168. the device, additional drivers must be enabled in order to use
  169. the functionality of the device.
  170. config MFD_WM831X
  171. bool "Support Wolfson Microelectronics WM831x/2x PMICs"
  172. select MFD_CORE
  173. depends on I2C=y
  174. help
  175. Support for the Wolfson Microelecronics WM831x and WM832x PMICs.
  176. This driver provides common support for accessing the device,
  177. additional drivers must be enabled in order to use the
  178. functionality of the device.
  179. config MFD_WM8350
  180. tristate
  181. config MFD_WM8350_CONFIG_MODE_0
  182. bool
  183. depends on MFD_WM8350
  184. config MFD_WM8350_CONFIG_MODE_1
  185. bool
  186. depends on MFD_WM8350
  187. config MFD_WM8350_CONFIG_MODE_2
  188. bool
  189. depends on MFD_WM8350
  190. config MFD_WM8350_CONFIG_MODE_3
  191. bool
  192. depends on MFD_WM8350
  193. config MFD_WM8351_CONFIG_MODE_0
  194. bool
  195. depends on MFD_WM8350
  196. config MFD_WM8351_CONFIG_MODE_1
  197. bool
  198. depends on MFD_WM8350
  199. config MFD_WM8351_CONFIG_MODE_2
  200. bool
  201. depends on MFD_WM8350
  202. config MFD_WM8351_CONFIG_MODE_3
  203. bool
  204. depends on MFD_WM8350
  205. config MFD_WM8352_CONFIG_MODE_0
  206. bool
  207. depends on MFD_WM8350
  208. config MFD_WM8352_CONFIG_MODE_1
  209. bool
  210. depends on MFD_WM8350
  211. config MFD_WM8352_CONFIG_MODE_2
  212. bool
  213. depends on MFD_WM8350
  214. config MFD_WM8352_CONFIG_MODE_3
  215. bool
  216. depends on MFD_WM8350
  217. config MFD_WM8350_I2C
  218. tristate "Support Wolfson Microelectronics WM8350 with I2C"
  219. select MFD_WM8350
  220. depends on I2C
  221. help
  222. The WM8350 is an integrated audio and power management
  223. subsystem with watchdog and RTC functionality for embedded
  224. systems. This option enables core support for the WM8350 with
  225. I2C as the control interface. Additional options must be
  226. selected to enable support for the functionality of the chip.
  227. config MFD_PCF50633
  228. tristate "Support for NXP PCF50633"
  229. depends on I2C
  230. help
  231. Say yes here if you have NXP PCF50633 chip on your board.
  232. This core driver provides register access and IRQ handling
  233. facilities, and registers devices for the various functions
  234. so that function-specific drivers can bind to them.
  235. config MFD_MC13783
  236. tristate "Support Freescale MC13783"
  237. depends on SPI_MASTER
  238. select MFD_CORE
  239. help
  240. Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC.
  241. This driver provides common support for accessing the device,
  242. additional drivers must be enabled in order to use the
  243. functionality of the device.
  244. config PCF50633_ADC
  245. tristate "Support for NXP PCF50633 ADC"
  246. depends on MFD_PCF50633
  247. help
  248. Say yes here if you want to include support for ADC in the
  249. NXP PCF50633 chip.
  250. config PCF50633_GPIO
  251. tristate "Support for NXP PCF50633 GPIO"
  252. depends on MFD_PCF50633
  253. help
  254. Say yes here if you want to include support GPIO for pins on
  255. the PCF50633 chip.
  256. config AB3100_CORE
  257. tristate "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
  258. depends on I2C
  259. default y if ARCH_U300
  260. help
  261. Select this to enable the AB3100 Mixed Signal IC core
  262. functionality. This connects to a AB3100 on the I2C bus
  263. and expose a number of symbols needed for dependent devices
  264. to read and write registers and subscribe to events from
  265. this multi-functional IC. This is needed to use other features
  266. of the AB3100 such as battery-backed RTC, charging control,
  267. LEDs, vibrator, system power and temperature, power management
  268. and ALSA sound.
  269. config AB3100_OTP
  270. tristate "ST-Ericsson AB3100 OTP functions"
  271. depends on AB3100_CORE
  272. default y if AB3100_CORE
  273. help
  274. Select this to enable the AB3100 Mixed Signal IC OTP (one-time
  275. programmable memory) support. This exposes a sysfs file to read
  276. out OTP values.
  277. config EZX_PCAP
  278. bool "PCAP Support"
  279. depends on GENERIC_HARDIRQS && SPI_MASTER
  280. help
  281. This enables the PCAP ASIC present on EZX Phones. This is
  282. needed for MMC, TouchScreen, Sound, USB, etc..
  283. config MFD_88PM8607
  284. bool "Support Marvell 88PM8607"
  285. depends on I2C=y
  286. select MFD_CORE
  287. help
  288. This supports for Marvell 88PM8607 Power Management IC. This includes
  289. the I2C driver and the core APIs _only_, you have to select
  290. individual components like voltage regulators, RTC and
  291. battery-charger under the corresponding menus.
  292. config AB4500_CORE
  293. tristate "ST-Ericsson's AB4500 Mixed Signal Power management chip"
  294. depends on SPI
  295. help
  296. Select this option to enable access to AB4500 power management
  297. chip. This connects to U8500 on the SSP/SPI bus and exports
  298. read/write functions for the devices to get access to this chip.
  299. This chip embeds various other multimedia funtionalities as well.
  300. endmenu
  301. menu "Multimedia Capabilities Port drivers"
  302. depends on ARCH_SA1100
  303. config MCP
  304. tristate
  305. # Interface drivers
  306. config MCP_SA11X0
  307. tristate "Support SA11x0 MCP interface"
  308. depends on ARCH_SA1100
  309. select MCP
  310. # Chip drivers
  311. config MCP_UCB1200
  312. tristate "Support for UCB1200 / UCB1300"
  313. depends on MCP
  314. config MCP_UCB1200_TS
  315. tristate "Touchscreen interface support"
  316. depends on MCP_UCB1200 && INPUT
  317. endmenu