Kconfig 12 KB

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