Kconfig 6.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233
  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. ---help---
  29. This driver supports the ASIC3 multifunction chip found on many
  30. PDAs (mainly iPAQ and HTC based ones)
  31. config MFD_DM355EVM_MSP
  32. bool "DaVinci DM355 EVM microcontroller"
  33. depends on I2C && MACH_DAVINCI_DM355_EVM
  34. help
  35. This driver supports the MSP430 microcontroller used on these
  36. boards. MSP430 firmware manages resets and power sequencing,
  37. inputs from buttons and the IR remote, LEDs, an RTC, and more.
  38. config HTC_EGPIO
  39. bool "HTC EGPIO support"
  40. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  41. help
  42. This driver supports the CPLD egpio chip present on
  43. several HTC phones. It provides basic support for input
  44. pins, output pins, and irqs.
  45. config HTC_PASIC3
  46. tristate "HTC PASIC3 LED/DS1WM chip support"
  47. help
  48. This core driver provides register access for the LED/DS1WM
  49. chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
  50. HTC Magician devices, respectively. Actual functionality is
  51. handled by the leds-pasic3 and ds1wm drivers.
  52. config UCB1400_CORE
  53. tristate "Philips UCB1400 Core driver"
  54. depends on AC97_BUS
  55. depends on GPIOLIB
  56. help
  57. This enables support for the Philips UCB1400 core functions.
  58. The UCB1400 is an AC97 audio codec.
  59. To compile this driver as a module, choose M here: the
  60. module will be called ucb1400_core.
  61. config TPS65010
  62. tristate "TPS6501x Power Management chips"
  63. depends on I2C && GPIOLIB
  64. default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
  65. help
  66. If you say yes here you get support for the TPS6501x series of
  67. Power Management chips. These include voltage regulators,
  68. lithium ion/polymer battery charging, and other features that
  69. are often used in portable devices like cell phones and cameras.
  70. This driver can also be built as a module. If so, the module
  71. will be called tps65010.
  72. config TWL4030_CORE
  73. bool "Texas Instruments TWL4030/TPS659x0 Support"
  74. depends on I2C=y && GENERIC_HARDIRQS
  75. help
  76. Say yes here if you have TWL4030 family chip on your board.
  77. This core driver provides register access and IRQ handling
  78. facilities, and registers devices for the various functions
  79. so that function-specific drivers can bind to them.
  80. These multi-function chips are found on many OMAP2 and OMAP3
  81. boards, providing power management, RTC, GPIO, keypad, a
  82. high speed USB OTG transceiver, an audio codec (on most
  83. versions) and many other features.
  84. config MFD_TMIO
  85. bool
  86. default n
  87. config MFD_T7L66XB
  88. bool "Support Toshiba T7L66XB"
  89. depends on ARM && HAVE_CLK
  90. select MFD_CORE
  91. select MFD_TMIO
  92. help
  93. Support for Toshiba Mobile IO Controller T7L66XB
  94. config MFD_TC6387XB
  95. bool "Support Toshiba TC6387XB"
  96. depends on ARM && HAVE_CLK
  97. select MFD_CORE
  98. select MFD_TMIO
  99. help
  100. Support for Toshiba Mobile IO Controller TC6387XB
  101. config MFD_TC6393XB
  102. bool "Support Toshiba TC6393XB"
  103. depends on GPIOLIB && ARM
  104. select MFD_CORE
  105. select MFD_TMIO
  106. help
  107. Support for Toshiba Mobile IO Controller TC6393XB
  108. config PMIC_DA903X
  109. bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
  110. depends on I2C=y
  111. help
  112. Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
  113. ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
  114. usually found on PXA processors-based platforms. This includes
  115. the I2C driver and the core APIs _only_, you have to select
  116. individual components like LCD backlight, voltage regulators,
  117. LEDs and battery-charger under the corresponding menus.
  118. config MFD_WM8400
  119. tristate "Support Wolfson Microelectronics WM8400"
  120. select MFD_CORE
  121. depends on I2C
  122. help
  123. Support for the Wolfson Microelecronics WM8400 PMIC and audio
  124. CODEC. This driver adds provides common support for accessing
  125. the device, additional drivers must be enabled in order to use
  126. the functionality of the device.
  127. config MFD_WM8350
  128. tristate
  129. config MFD_WM8350_CONFIG_MODE_0
  130. bool
  131. depends on MFD_WM8350
  132. config MFD_WM8350_CONFIG_MODE_1
  133. bool
  134. depends on MFD_WM8350
  135. config MFD_WM8350_CONFIG_MODE_2
  136. bool
  137. depends on MFD_WM8350
  138. config MFD_WM8350_CONFIG_MODE_3
  139. bool
  140. depends on MFD_WM8350
  141. config MFD_WM8351_CONFIG_MODE_0
  142. bool
  143. depends on MFD_WM8350
  144. config MFD_WM8351_CONFIG_MODE_1
  145. bool
  146. depends on MFD_WM8350
  147. config MFD_WM8351_CONFIG_MODE_2
  148. bool
  149. depends on MFD_WM8350
  150. config MFD_WM8351_CONFIG_MODE_3
  151. bool
  152. depends on MFD_WM8350
  153. config MFD_WM8352_CONFIG_MODE_0
  154. bool
  155. depends on MFD_WM8350
  156. config MFD_WM8352_CONFIG_MODE_1
  157. bool
  158. depends on MFD_WM8350
  159. config MFD_WM8352_CONFIG_MODE_2
  160. bool
  161. depends on MFD_WM8350
  162. config MFD_WM8352_CONFIG_MODE_3
  163. bool
  164. depends on MFD_WM8350
  165. config MFD_WM8350_I2C
  166. tristate "Support Wolfson Microelectronics WM8350 with I2C"
  167. select MFD_WM8350
  168. depends on I2C
  169. help
  170. The WM8350 is an integrated audio and power management
  171. subsystem with watchdog and RTC functionality for embedded
  172. systems. This option enables core support for the WM8350 with
  173. I2C as the control interface. Additional options must be
  174. selected to enable support for the functionality of the chip.
  175. endmenu
  176. menu "Multimedia Capabilities Port drivers"
  177. depends on ARCH_SA1100
  178. config MCP
  179. tristate
  180. # Interface drivers
  181. config MCP_SA11X0
  182. tristate "Support SA11x0 MCP interface"
  183. depends on ARCH_SA1100
  184. select MCP
  185. # Chip drivers
  186. config MCP_UCB1200
  187. tristate "Support for UCB1200 / UCB1300"
  188. depends on MCP
  189. config MCP_UCB1200_TS
  190. tristate "Touchscreen interface support"
  191. depends on MCP_UCB1200 && INPUT
  192. endmenu