Kconfig 9.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339
  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/TPS659x0 Support"
  92. depends on I2C=y && GENERIC_HARDIRQS
  93. help
  94. Say yes here if you have TWL4030 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 MFD_TMIO
  114. bool
  115. default n
  116. config MFD_T7L66XB
  117. bool "Support Toshiba T7L66XB"
  118. depends on ARM && HAVE_CLK
  119. select MFD_CORE
  120. select MFD_TMIO
  121. help
  122. Support for Toshiba Mobile IO Controller T7L66XB
  123. config MFD_TC6387XB
  124. bool "Support Toshiba TC6387XB"
  125. depends on ARM && HAVE_CLK
  126. select MFD_CORE
  127. select MFD_TMIO
  128. help
  129. Support for Toshiba Mobile IO Controller TC6387XB
  130. config MFD_TC6393XB
  131. bool "Support Toshiba TC6393XB"
  132. depends on GPIOLIB && ARM
  133. select MFD_CORE
  134. select MFD_TMIO
  135. help
  136. Support for Toshiba Mobile IO Controller TC6393XB
  137. config PMIC_DA903X
  138. bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
  139. depends on I2C=y
  140. help
  141. Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
  142. ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
  143. usually found on PXA processors-based platforms. This includes
  144. the I2C driver and the core APIs _only_, you have to select
  145. individual components like LCD backlight, voltage regulators,
  146. LEDs and battery-charger under the corresponding menus.
  147. config MFD_WM8400
  148. tristate "Support Wolfson Microelectronics WM8400"
  149. select MFD_CORE
  150. depends on I2C
  151. help
  152. Support for the Wolfson Microelecronics WM8400 PMIC and audio
  153. CODEC. This driver provides common support for accessing
  154. the device, additional drivers must be enabled in order to use
  155. the functionality of the device.
  156. config MFD_WM831X
  157. tristate "Support Wolfson Microelectronics WM831x PMICs"
  158. select MFD_CORE
  159. depends on I2C
  160. help
  161. Support for the Wolfson Microelecronics WM831x PMICs. This
  162. driver provides common support for accessing the device,
  163. additional drivers must be enabled in order to use the
  164. functionality of the device.
  165. config MFD_WM8350
  166. tristate
  167. config MFD_WM8350_CONFIG_MODE_0
  168. bool
  169. depends on MFD_WM8350
  170. config MFD_WM8350_CONFIG_MODE_1
  171. bool
  172. depends on MFD_WM8350
  173. config MFD_WM8350_CONFIG_MODE_2
  174. bool
  175. depends on MFD_WM8350
  176. config MFD_WM8350_CONFIG_MODE_3
  177. bool
  178. depends on MFD_WM8350
  179. config MFD_WM8351_CONFIG_MODE_0
  180. bool
  181. depends on MFD_WM8350
  182. config MFD_WM8351_CONFIG_MODE_1
  183. bool
  184. depends on MFD_WM8350
  185. config MFD_WM8351_CONFIG_MODE_2
  186. bool
  187. depends on MFD_WM8350
  188. config MFD_WM8351_CONFIG_MODE_3
  189. bool
  190. depends on MFD_WM8350
  191. config MFD_WM8352_CONFIG_MODE_0
  192. bool
  193. depends on MFD_WM8350
  194. config MFD_WM8352_CONFIG_MODE_1
  195. bool
  196. depends on MFD_WM8350
  197. config MFD_WM8352_CONFIG_MODE_2
  198. bool
  199. depends on MFD_WM8350
  200. config MFD_WM8352_CONFIG_MODE_3
  201. bool
  202. depends on MFD_WM8350
  203. config MFD_WM8350_I2C
  204. tristate "Support Wolfson Microelectronics WM8350 with I2C"
  205. select MFD_WM8350
  206. depends on I2C
  207. help
  208. The WM8350 is an integrated audio and power management
  209. subsystem with watchdog and RTC functionality for embedded
  210. systems. This option enables core support for the WM8350 with
  211. I2C as the control interface. Additional options must be
  212. selected to enable support for the functionality of the chip.
  213. config MFD_PCF50633
  214. tristate "Support for NXP PCF50633"
  215. depends on I2C
  216. help
  217. Say yes here if you have NXP PCF50633 chip on your board.
  218. This core driver provides register access and IRQ handling
  219. facilities, and registers devices for the various functions
  220. so that function-specific drivers can bind to them.
  221. config MFD_MC13783
  222. tristate "Support Freescale MC13783"
  223. depends on SPI_MASTER
  224. select MFD_CORE
  225. help
  226. Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC.
  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 PCF50633_ADC
  231. tristate "Support for NXP PCF50633 ADC"
  232. depends on MFD_PCF50633
  233. help
  234. Say yes here if you want to include support for ADC in the
  235. NXP PCF50633 chip.
  236. config PCF50633_GPIO
  237. tristate "Support for NXP PCF50633 GPIO"
  238. depends on MFD_PCF50633
  239. help
  240. Say yes here if you want to include support GPIO for pins on
  241. the PCF50633 chip.
  242. config AB3100_CORE
  243. tristate "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
  244. depends on I2C
  245. default y if ARCH_U300
  246. help
  247. Select this to enable the AB3100 Mixed Signal IC core
  248. functionality. This connects to a AB3100 on the I2C bus
  249. and expose a number of symbols needed for dependent devices
  250. to read and write registers and subscribe to events from
  251. this multi-functional IC. This is needed to use other features
  252. of the AB3100 such as battery-backed RTC, charging control,
  253. LEDs, vibrator, system power and temperature, power management
  254. and ALSA sound.
  255. config AB3100_OTP
  256. tristate "ST-Ericsson AB3100 OTP functions"
  257. depends on AB3100_CORE
  258. default y if AB3100_CORE
  259. help
  260. Select this to enable the AB3100 Mixed Signal IC OTP (one-time
  261. programmable memory) support. This exposes a sysfs file to read
  262. out OTP values.
  263. config EZX_PCAP
  264. bool "PCAP Support"
  265. depends on GENERIC_HARDIRQS && SPI_MASTER
  266. help
  267. This enables the PCAP ASIC present on EZX Phones. This is
  268. needed for MMC, TouchScreen, Sound, USB, etc..
  269. endmenu
  270. menu "Multimedia Capabilities Port drivers"
  271. depends on ARCH_SA1100
  272. config MCP
  273. tristate
  274. # Interface drivers
  275. config MCP_SA11X0
  276. tristate "Support SA11x0 MCP interface"
  277. depends on ARCH_SA1100
  278. select MCP
  279. # Chip drivers
  280. config MCP_UCB1200
  281. tristate "Support for UCB1200 / UCB1300"
  282. depends on MCP
  283. config MCP_UCB1200_TS
  284. tristate "Touchscreen interface support"
  285. depends on MCP_UCB1200 && INPUT
  286. endmenu