Kconfig 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508
  1. #
  2. # Multifunction miscellaneous devices
  3. #
  4. menuconfig MFD_SUPPORT
  5. bool "Multifunction device drivers"
  6. depends on HAS_IOMEM
  7. default y
  8. help
  9. Configure MFD device drivers.
  10. if MFD_SUPPORT
  11. config MFD_CORE
  12. tristate
  13. default n
  14. config MFD_88PM860X
  15. bool "Support Marvell 88PM8606/88PM8607"
  16. depends on I2C=y && GENERIC_HARDIRQS
  17. select MFD_CORE
  18. help
  19. This supports for Marvell 88PM8606/88PM8607 Power Management IC.
  20. This includes the I2C driver and the core APIs _only_, you have to
  21. select individual components like voltage regulators, RTC and
  22. battery-charger under the corresponding menus.
  23. config MFD_SM501
  24. tristate "Support for Silicon Motion SM501"
  25. ---help---
  26. This is the core driver for the Silicon Motion SM501 multimedia
  27. companion chip. This device is a multifunction device which may
  28. provide numerous interfaces including USB host controller, USB gadget,
  29. asynchronous serial ports, audio functions, and a dual display video
  30. interface. The device may be connected by PCI or local bus with
  31. varying functions enabled.
  32. config MFD_SM501_GPIO
  33. bool "Export GPIO via GPIO layer"
  34. depends on MFD_SM501 && GPIOLIB
  35. ---help---
  36. This option uses the gpio library layer to export the 64 GPIO
  37. lines on the SM501. The platform data is used to supply the
  38. base number for the first GPIO line to register.
  39. config MFD_ASIC3
  40. bool "Support for Compaq ASIC3"
  41. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  42. select MFD_CORE
  43. ---help---
  44. This driver supports the ASIC3 multifunction chip found on many
  45. PDAs (mainly iPAQ and HTC based ones)
  46. config MFD_SH_MOBILE_SDHI
  47. bool "Support for SuperH Mobile SDHI"
  48. depends on SUPERH || ARCH_SHMOBILE
  49. select MFD_CORE
  50. select TMIO_MMC_DMA
  51. ---help---
  52. This driver supports the SDHI hardware block found in many
  53. SuperH Mobile SoCs.
  54. config MFD_DAVINCI_VOICECODEC
  55. tristate
  56. select MFD_CORE
  57. config MFD_DM355EVM_MSP
  58. bool "DaVinci DM355 EVM microcontroller"
  59. depends on I2C && MACH_DAVINCI_DM355_EVM
  60. help
  61. This driver supports the MSP430 microcontroller used on these
  62. boards. MSP430 firmware manages resets and power sequencing,
  63. inputs from buttons and the IR remote, LEDs, an RTC, and more.
  64. config HTC_EGPIO
  65. bool "HTC EGPIO support"
  66. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  67. help
  68. This driver supports the CPLD egpio chip present on
  69. several HTC phones. It provides basic support for input
  70. pins, output pins, and irqs.
  71. config HTC_PASIC3
  72. tristate "HTC PASIC3 LED/DS1WM chip support"
  73. select MFD_CORE
  74. help
  75. This core driver provides register access for the LED/DS1WM
  76. chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
  77. HTC Magician devices, respectively. Actual functionality is
  78. handled by the leds-pasic3 and ds1wm drivers.
  79. config HTC_I2CPLD
  80. bool "HTC I2C PLD chip support"
  81. depends on I2C=y && GPIOLIB
  82. help
  83. If you say yes here you get support for the supposed CPLD
  84. found on omap850 HTC devices like the HTC Wizard and HTC Herald.
  85. This device provides input and output GPIOs through an I2C
  86. interface to one or more sub-chips.
  87. config UCB1400_CORE
  88. tristate "Philips UCB1400 Core driver"
  89. depends on AC97_BUS
  90. depends on GPIOLIB
  91. help
  92. This enables support for the Philips UCB1400 core functions.
  93. The UCB1400 is an AC97 audio codec.
  94. To compile this driver as a module, choose M here: the
  95. module will be called ucb1400_core.
  96. config TPS65010
  97. tristate "TPS6501x Power Management chips"
  98. depends on I2C && GPIOLIB
  99. default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
  100. help
  101. If you say yes here you get support for the TPS6501x series of
  102. Power Management chips. These include voltage regulators,
  103. lithium ion/polymer battery charging, and other features that
  104. are often used in portable devices like cell phones and cameras.
  105. This driver can also be built as a module. If so, the module
  106. will be called tps65010.
  107. config TPS6507X
  108. tristate "TPS6507x Power Management / Touch Screen chips"
  109. select MFD_CORE
  110. depends on I2C
  111. help
  112. If you say yes here you get support for the TPS6507x series of
  113. Power Management / Touch Screen chips. These include voltage
  114. regulators, lithium ion/polymer battery charging, touch screen
  115. and other features that are often used in portable devices.
  116. This driver can also be built as a module. If so, the module
  117. will be called tps6507x.
  118. config MENELAUS
  119. bool "Texas Instruments TWL92330/Menelaus PM chip"
  120. depends on I2C=y && ARCH_OMAP2
  121. help
  122. If you say yes here you get support for the Texas Instruments
  123. TWL92330/Menelaus Power Management chip. This include voltage
  124. regulators, Dual slot memory card transceivers, real-time clock
  125. and other features that are often used in portable devices like
  126. cell phones and PDAs.
  127. config TWL4030_CORE
  128. bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
  129. depends on I2C=y && GENERIC_HARDIRQS
  130. help
  131. Say yes here if you have TWL4030 / TWL6030 family chip on your board.
  132. This core driver provides register access and IRQ handling
  133. facilities, and registers devices for the various functions
  134. so that function-specific drivers can bind to them.
  135. These multi-function chips are found on many OMAP2 and OMAP3
  136. boards, providing power management, RTC, GPIO, keypad, a
  137. high speed USB OTG transceiver, an audio codec (on most
  138. versions) and many other features.
  139. config TWL4030_POWER
  140. bool "Support power resources on TWL4030 family chips"
  141. depends on TWL4030_CORE && ARM
  142. help
  143. Say yes here if you want to use the power resources on the
  144. TWL4030 family chips. Most of these resources are regulators,
  145. which have a separate driver; some are control signals, such
  146. as clock request handshaking.
  147. This driver uses board-specific data to initialize the resources
  148. and load scripts controling which resources are switched off/on
  149. or reset when a sleep, wakeup or warm reset event occurs.
  150. config TWL4030_CODEC
  151. bool
  152. depends on TWL4030_CORE
  153. select MFD_CORE
  154. default n
  155. config MFD_TC35892
  156. bool "Support Toshiba TC35892"
  157. depends on I2C=y && GENERIC_HARDIRQS
  158. select MFD_CORE
  159. help
  160. Support for the Toshiba TC35892 I/O Expander.
  161. This driver provides common support for accessing the device,
  162. additional drivers must be enabled in order to use the
  163. functionality of the device.
  164. config MFD_TMIO
  165. bool
  166. default n
  167. config TMIO_MMC_DMA
  168. bool
  169. select DMA_ENGINE
  170. select DMADEVICES
  171. config MFD_T7L66XB
  172. bool "Support Toshiba T7L66XB"
  173. depends on ARM && HAVE_CLK
  174. select MFD_CORE
  175. select MFD_TMIO
  176. help
  177. Support for Toshiba Mobile IO Controller T7L66XB
  178. config MFD_TC6387XB
  179. bool "Support Toshiba TC6387XB"
  180. depends on ARM && HAVE_CLK
  181. select MFD_CORE
  182. select MFD_TMIO
  183. help
  184. Support for Toshiba Mobile IO Controller TC6387XB
  185. config MFD_TC6393XB
  186. bool "Support Toshiba TC6393XB"
  187. depends on GPIOLIB && ARM
  188. select MFD_CORE
  189. select MFD_TMIO
  190. help
  191. Support for Toshiba Mobile IO Controller TC6393XB
  192. config PMIC_DA903X
  193. bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
  194. depends on I2C=y
  195. help
  196. Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
  197. ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
  198. usually found on PXA processors-based platforms. This includes
  199. the I2C driver and the core APIs _only_, you have to select
  200. individual components like LCD backlight, voltage regulators,
  201. LEDs and battery-charger under the corresponding menus.
  202. config PMIC_ADP5520
  203. bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
  204. depends on I2C=y
  205. help
  206. Say yes here to add support for Analog Devices AD5520 and ADP5501,
  207. Multifunction Power Management IC. This includes
  208. the I2C driver and the core APIs _only_, you have to select
  209. individual components like LCD backlight, LEDs, GPIOs and Kepad
  210. under the corresponding menus.
  211. config MFD_MAX8925
  212. bool "Maxim Semiconductor MAX8925 PMIC Support"
  213. depends on I2C=y && GENERIC_HARDIRQS
  214. select MFD_CORE
  215. help
  216. Say yes here to support for Maxim Semiconductor MAX8925. This is
  217. a Power Management IC. This driver provies common support for
  218. accessing the device, additional drivers must be enabled in order
  219. to use the functionality of the device.
  220. config MFD_WM8400
  221. tristate "Support Wolfson Microelectronics WM8400"
  222. select MFD_CORE
  223. depends on I2C
  224. help
  225. Support for the Wolfson Microelecronics WM8400 PMIC and audio
  226. CODEC. This driver provides common support for accessing
  227. the device, additional drivers must be enabled in order to use
  228. the functionality of the device.
  229. config MFD_WM831X
  230. bool "Support Wolfson Microelectronics WM831x/2x PMICs"
  231. select MFD_CORE
  232. depends on I2C=y && GENERIC_HARDIRQS
  233. help
  234. Support for the Wolfson Microelecronics WM831x and WM832x PMICs.
  235. This driver provides common support for accessing the device,
  236. additional drivers must be enabled in order to use the
  237. functionality of the device.
  238. config MFD_WM8350
  239. bool
  240. depends on GENERIC_HARDIRQS
  241. config MFD_WM8350_CONFIG_MODE_0
  242. bool
  243. depends on MFD_WM8350
  244. config MFD_WM8350_CONFIG_MODE_1
  245. bool
  246. depends on MFD_WM8350
  247. config MFD_WM8350_CONFIG_MODE_2
  248. bool
  249. depends on MFD_WM8350
  250. config MFD_WM8350_CONFIG_MODE_3
  251. bool
  252. depends on MFD_WM8350
  253. config MFD_WM8351_CONFIG_MODE_0
  254. bool
  255. depends on MFD_WM8350
  256. config MFD_WM8351_CONFIG_MODE_1
  257. bool
  258. depends on MFD_WM8350
  259. config MFD_WM8351_CONFIG_MODE_2
  260. bool
  261. depends on MFD_WM8350
  262. config MFD_WM8351_CONFIG_MODE_3
  263. bool
  264. depends on MFD_WM8350
  265. config MFD_WM8352_CONFIG_MODE_0
  266. bool
  267. depends on MFD_WM8350
  268. config MFD_WM8352_CONFIG_MODE_1
  269. bool
  270. depends on MFD_WM8350
  271. config MFD_WM8352_CONFIG_MODE_2
  272. bool
  273. depends on MFD_WM8350
  274. config MFD_WM8352_CONFIG_MODE_3
  275. bool
  276. depends on MFD_WM8350
  277. config MFD_WM8350_I2C
  278. bool "Support Wolfson Microelectronics WM8350 with I2C"
  279. select MFD_WM8350
  280. depends on I2C=y && GENERIC_HARDIRQS
  281. help
  282. The WM8350 is an integrated audio and power management
  283. subsystem with watchdog and RTC functionality for embedded
  284. systems. This option enables core support for the WM8350 with
  285. I2C as the control interface. Additional options must be
  286. selected to enable support for the functionality of the chip.
  287. config MFD_WM8994
  288. bool "Support Wolfson Microelectronics WM8994"
  289. select MFD_CORE
  290. depends on I2C=y && GENERIC_HARDIRQS
  291. help
  292. The WM8994 is a highly integrated hi-fi CODEC designed for
  293. smartphone applicatiosn. As well as audio functionality it
  294. has on board GPIO and regulator functionality which is
  295. supported via the relevant subsystems. This driver provides
  296. core support for the WM8994, in order to use the actual
  297. functionaltiy of the device other drivers must be enabled.
  298. config MFD_PCF50633
  299. tristate "Support for NXP PCF50633"
  300. depends on I2C
  301. help
  302. Say yes here if you have NXP PCF50633 chip on your board.
  303. This core driver provides register access and IRQ handling
  304. facilities, and registers devices for the various functions
  305. so that function-specific drivers can bind to them.
  306. config MFD_MC13783
  307. tristate "Support Freescale MC13783"
  308. depends on SPI_MASTER
  309. select MFD_CORE
  310. help
  311. Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC.
  312. This driver provides common support for accessing the device,
  313. additional drivers must be enabled in order to use the
  314. functionality of the device.
  315. config PCF50633_ADC
  316. tristate "Support for NXP PCF50633 ADC"
  317. depends on MFD_PCF50633
  318. help
  319. Say yes here if you want to include support for ADC in the
  320. NXP PCF50633 chip.
  321. config PCF50633_GPIO
  322. tristate "Support for NXP PCF50633 GPIO"
  323. depends on MFD_PCF50633
  324. help
  325. Say yes here if you want to include support GPIO for pins on
  326. the PCF50633 chip.
  327. config ABX500_CORE
  328. bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
  329. default y if ARCH_U300
  330. help
  331. Say yes here if you have the ABX500 Mixed Signal IC family
  332. chips. This core driver expose register access functions.
  333. Functionality specific drivers using these functions can
  334. remain unchanged when IC changes. Binding of the functions to
  335. actual register access is done by the IC core driver.
  336. config AB3100_CORE
  337. bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
  338. depends on I2C=y && ABX500_CORE
  339. default y if ARCH_U300
  340. help
  341. Select this to enable the AB3100 Mixed Signal IC core
  342. functionality. This connects to a AB3100 on the I2C bus
  343. and expose a number of symbols needed for dependent devices
  344. to read and write registers and subscribe to events from
  345. this multi-functional IC. This is needed to use other features
  346. of the AB3100 such as battery-backed RTC, charging control,
  347. LEDs, vibrator, system power and temperature, power management
  348. and ALSA sound.
  349. config AB3100_OTP
  350. tristate "ST-Ericsson AB3100 OTP functions"
  351. depends on AB3100_CORE
  352. default y if AB3100_CORE
  353. help
  354. Select this to enable the AB3100 Mixed Signal IC OTP (one-time
  355. programmable memory) support. This exposes a sysfs file to read
  356. out OTP values.
  357. config EZX_PCAP
  358. bool "PCAP Support"
  359. depends on GENERIC_HARDIRQS && SPI_MASTER
  360. help
  361. This enables the PCAP ASIC present on EZX Phones. This is
  362. needed for MMC, TouchScreen, Sound, USB, etc..
  363. config AB8500_CORE
  364. bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
  365. depends on SPI=y && GENERIC_HARDIRQS
  366. select MFD_CORE
  367. help
  368. Select this option to enable access to AB8500 power management
  369. chip. This connects to U8500 on the SSP/SPI bus and exports
  370. read/write functions for the devices to get access to this chip.
  371. This chip embeds various other multimedia funtionalities as well.
  372. config AB3550_CORE
  373. bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
  374. select MFD_CORE
  375. depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
  376. help
  377. Select this to enable the AB3550 Mixed Signal IC core
  378. functionality. This connects to a AB3550 on the I2C bus
  379. and expose a number of symbols needed for dependent devices
  380. to read and write registers and subscribe to events from
  381. this multi-functional IC. This is needed to use other features
  382. of the AB3550 such as battery-backed RTC, charging control,
  383. LEDs, vibrator, system power and temperature, power management
  384. and ALSA sound.
  385. config MFD_TIMBERDALE
  386. tristate "Support for the Timberdale FPGA"
  387. select MFD_CORE
  388. depends on PCI && GPIOLIB
  389. ---help---
  390. This is the core driver for the timberdale FPGA. This device is a
  391. multifunction device which exposes numerous platform devices.
  392. The timberdale FPGA can be found on the Intel Atom development board
  393. for in-vehicle infontainment, called Russellville.
  394. config LPC_SCH
  395. tristate "Intel SCH LPC"
  396. depends on PCI
  397. select MFD_CORE
  398. help
  399. LPC bridge function of the Intel SCH provides support for
  400. System Management Bus and General Purpose I/O.
  401. config MFD_RDC321X
  402. tristate "Support for RDC-R321x southbridge"
  403. select MFD_CORE
  404. depends on PCI
  405. help
  406. Say yes here if you want to have support for the RDC R-321x SoC
  407. southbridge which provides access to GPIOs and Watchdog using the
  408. southbridge PCI device configuration space.
  409. config MFD_JANZ_CMODIO
  410. tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
  411. select MFD_CORE
  412. depends on PCI
  413. help
  414. This is the core driver for the Janz CMOD-IO PCI MODULbus
  415. carrier board. This device is a PCI to MODULbus bridge which may
  416. host many different types of MODULbus daughterboards, including
  417. CAN and GPIO controllers.
  418. endif # MFD_SUPPORT
  419. menu "Multimedia Capabilities Port drivers"
  420. depends on ARCH_SA1100
  421. config MCP
  422. tristate
  423. # Interface drivers
  424. config MCP_SA11X0
  425. tristate "Support SA11x0 MCP interface"
  426. depends on ARCH_SA1100
  427. select MCP
  428. # Chip drivers
  429. config MCP_UCB1200
  430. tristate "Support for UCB1200 / UCB1300"
  431. depends on MCP
  432. config MCP_UCB1200_TS
  433. tristate "Touchscreen interface support"
  434. depends on MCP_UCB1200 && INPUT
  435. endmenu