Kconfig 8.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289
  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_DM355EVM_MSP
  33. bool "DaVinci DM355 EVM microcontroller"
  34. depends on I2C && MACH_DAVINCI_DM355_EVM
  35. help
  36. This driver supports the MSP430 microcontroller used on these
  37. boards. MSP430 firmware manages resets and power sequencing,
  38. inputs from buttons and the IR remote, LEDs, an RTC, and more.
  39. config HTC_EGPIO
  40. bool "HTC EGPIO support"
  41. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  42. help
  43. This driver supports the CPLD egpio chip present on
  44. several HTC phones. It provides basic support for input
  45. pins, output pins, and irqs.
  46. config HTC_PASIC3
  47. tristate "HTC PASIC3 LED/DS1WM chip support"
  48. select MFD_CORE
  49. help
  50. This core driver provides register access for the LED/DS1WM
  51. chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
  52. HTC Magician devices, respectively. Actual functionality is
  53. handled by the leds-pasic3 and ds1wm drivers.
  54. config UCB1400_CORE
  55. tristate "Philips UCB1400 Core driver"
  56. depends on AC97_BUS
  57. depends on GPIOLIB
  58. help
  59. This enables support for the Philips UCB1400 core functions.
  60. The UCB1400 is an AC97 audio codec.
  61. To compile this driver as a module, choose M here: the
  62. module will be called ucb1400_core.
  63. config TPS65010
  64. tristate "TPS6501x Power Management chips"
  65. depends on I2C && GPIOLIB
  66. default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
  67. help
  68. If you say yes here you get support for the TPS6501x series of
  69. Power Management chips. These include voltage regulators,
  70. lithium ion/polymer battery charging, and other features that
  71. are often used in portable devices like cell phones and cameras.
  72. This driver can also be built as a module. If so, the module
  73. will be called tps65010.
  74. config MENELAUS
  75. bool "Texas Instruments TWL92330/Menelaus PM chip"
  76. depends on I2C=y && ARCH_OMAP24XX
  77. help
  78. If you say yes here you get support for the Texas Instruments
  79. TWL92330/Menelaus Power Management chip. This include voltage
  80. regulators, Dual slot memory card transceivers, real-time clock
  81. and other features that are often used in portable devices like
  82. cell phones and PDAs.
  83. config TWL4030_CORE
  84. bool "Texas Instruments TWL4030/TPS659x0 Support"
  85. depends on I2C=y && GENERIC_HARDIRQS
  86. help
  87. Say yes here if you have TWL4030 family chip on your board.
  88. This core driver provides register access and IRQ handling
  89. facilities, and registers devices for the various functions
  90. so that function-specific drivers can bind to them.
  91. These multi-function chips are found on many OMAP2 and OMAP3
  92. boards, providing power management, RTC, GPIO, keypad, a
  93. high speed USB OTG transceiver, an audio codec (on most
  94. versions) and many other features.
  95. config MFD_TMIO
  96. bool
  97. default n
  98. config MFD_T7L66XB
  99. bool "Support Toshiba T7L66XB"
  100. depends on ARM && HAVE_CLK
  101. select MFD_CORE
  102. select MFD_TMIO
  103. help
  104. Support for Toshiba Mobile IO Controller T7L66XB
  105. config MFD_TC6387XB
  106. bool "Support Toshiba TC6387XB"
  107. depends on ARM && HAVE_CLK
  108. select MFD_CORE
  109. select MFD_TMIO
  110. help
  111. Support for Toshiba Mobile IO Controller TC6387XB
  112. config MFD_TC6393XB
  113. bool "Support Toshiba TC6393XB"
  114. depends on GPIOLIB && ARM
  115. select MFD_CORE
  116. select MFD_TMIO
  117. help
  118. Support for Toshiba Mobile IO Controller TC6393XB
  119. config PMIC_DA903X
  120. bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
  121. depends on I2C=y
  122. help
  123. Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
  124. ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
  125. usually found on PXA processors-based platforms. This includes
  126. the I2C driver and the core APIs _only_, you have to select
  127. individual components like LCD backlight, voltage regulators,
  128. LEDs and battery-charger under the corresponding menus.
  129. config MFD_WM8400
  130. tristate "Support Wolfson Microelectronics WM8400"
  131. select MFD_CORE
  132. depends on I2C
  133. help
  134. Support for the Wolfson Microelecronics WM8400 PMIC and audio
  135. CODEC. This driver provides common support for accessing
  136. the device, additional drivers must be enabled in order to use
  137. the functionality of the device.
  138. config MFD_WM8350
  139. tristate
  140. config MFD_WM8350_CONFIG_MODE_0
  141. bool
  142. depends on MFD_WM8350
  143. config MFD_WM8350_CONFIG_MODE_1
  144. bool
  145. depends on MFD_WM8350
  146. config MFD_WM8350_CONFIG_MODE_2
  147. bool
  148. depends on MFD_WM8350
  149. config MFD_WM8350_CONFIG_MODE_3
  150. bool
  151. depends on MFD_WM8350
  152. config MFD_WM8351_CONFIG_MODE_0
  153. bool
  154. depends on MFD_WM8350
  155. config MFD_WM8351_CONFIG_MODE_1
  156. bool
  157. depends on MFD_WM8350
  158. config MFD_WM8351_CONFIG_MODE_2
  159. bool
  160. depends on MFD_WM8350
  161. config MFD_WM8351_CONFIG_MODE_3
  162. bool
  163. depends on MFD_WM8350
  164. config MFD_WM8352_CONFIG_MODE_0
  165. bool
  166. depends on MFD_WM8350
  167. config MFD_WM8352_CONFIG_MODE_1
  168. bool
  169. depends on MFD_WM8350
  170. config MFD_WM8352_CONFIG_MODE_2
  171. bool
  172. depends on MFD_WM8350
  173. config MFD_WM8352_CONFIG_MODE_3
  174. bool
  175. depends on MFD_WM8350
  176. config MFD_WM8350_I2C
  177. tristate "Support Wolfson Microelectronics WM8350 with I2C"
  178. select MFD_WM8350
  179. depends on I2C
  180. help
  181. The WM8350 is an integrated audio and power management
  182. subsystem with watchdog and RTC functionality for embedded
  183. systems. This option enables core support for the WM8350 with
  184. I2C as the control interface. Additional options must be
  185. selected to enable support for the functionality of the chip.
  186. config MFD_PCF50633
  187. tristate "Support for NXP PCF50633"
  188. depends on I2C
  189. help
  190. Say yes here if you have NXP PCF50633 chip on your board.
  191. This core driver provides register access and IRQ handling
  192. facilities, and registers devices for the various functions
  193. so that function-specific drivers can bind to them.
  194. config PCF50633_ADC
  195. tristate "Support for NXP PCF50633 ADC"
  196. depends on MFD_PCF50633
  197. help
  198. Say yes here if you want to include support for ADC in the
  199. NXP PCF50633 chip.
  200. config PCF50633_GPIO
  201. tristate "Support for NXP PCF50633 GPIO"
  202. depends on MFD_PCF50633
  203. help
  204. Say yes here if you want to include support GPIO for pins on
  205. the PCF50633 chip.
  206. config AB3100_CORE
  207. tristate "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
  208. depends on I2C
  209. default y if ARCH_U300
  210. help
  211. Select this to enable the AB3100 Mixed Signal IC core
  212. functionality. This connects to a AB3100 on the I2C bus
  213. and expose a number of symbols needed for dependent devices
  214. to read and write registers and subscribe to events from
  215. this multi-functional IC. This is needed to use other features
  216. of the AB3100 such as battery-backed RTC, charging control,
  217. LEDs, vibrator, system power and temperature, power management
  218. and ALSA sound.
  219. config EZX_PCAP
  220. bool "PCAP Support"
  221. depends on GENERIC_HARDIRQS && SPI_MASTER
  222. help
  223. This enables the PCAP ASIC present on EZX Phones. This is
  224. needed for MMC, TouchScreen, Sound, USB, etc..
  225. endmenu
  226. menu "Multimedia Capabilities Port drivers"
  227. depends on ARCH_SA1100
  228. config MCP
  229. tristate
  230. # Interface drivers
  231. config MCP_SA11X0
  232. tristate "Support SA11x0 MCP interface"
  233. depends on ARCH_SA1100
  234. select MCP
  235. # Chip drivers
  236. config MCP_UCB1200
  237. tristate "Support for UCB1200 / UCB1300"
  238. depends on MCP
  239. config MCP_UCB1200_TS
  240. tristate "Touchscreen interface support"
  241. depends on MCP_UCB1200 && INPUT
  242. endmenu