Kconfig 36 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182
  1. #
  2. # Multifunction miscellaneous devices
  3. #
  4. if HAS_IOMEM
  5. menu "Multifunction device drivers"
  6. config MFD_CORE
  7. tristate
  8. select IRQ_DOMAIN
  9. default n
  10. config MFD_88PM860X
  11. bool "Support Marvell 88PM8606/88PM8607"
  12. depends on I2C=y && GENERIC_HARDIRQS
  13. select REGMAP_I2C
  14. select MFD_CORE
  15. help
  16. This supports for Marvell 88PM8606/88PM8607 Power Management IC.
  17. This includes the I2C driver and the core APIs _only_, you have to
  18. select individual components like voltage regulators, RTC and
  19. battery-charger under the corresponding menus.
  20. config MFD_CROS_EC
  21. tristate "Support ChromeOS Embedded Controller"
  22. select MFD_CORE
  23. help
  24. If you say Y here you get support for the ChromeOS Embedded
  25. Controller (EC) providing keyboard, battery and power services.
  26. You also ned to enable the driver for the bus you are using. The
  27. protocol for talking to the EC is defined by the bus driver.
  28. config MFD_CROS_EC_I2C
  29. tristate "ChromeOS Embedded Controller (I2C)"
  30. depends on MFD_CROS_EC && I2C
  31. help
  32. If you say Y here, you get support for talking to the ChromeOS
  33. EC through an I2C bus. This uses a simple byte-level protocol with
  34. a checksum. Failing accesses will be retried three times to
  35. improve reliability.
  36. config MFD_CROS_EC_SPI
  37. tristate "ChromeOS Embedded Controller (SPI)"
  38. depends on MFD_CROS_EC && SPI
  39. ---help---
  40. If you say Y here, you get support for talking to the ChromeOS EC
  41. through a SPI bus, using a byte-level protocol. Since the EC's
  42. response time cannot be guaranteed, we support ignoring
  43. 'pre-amble' bytes before the response actually starts.
  44. config MFD_88PM800
  45. tristate "Support Marvell 88PM800"
  46. depends on I2C=y && GENERIC_HARDIRQS
  47. select REGMAP_I2C
  48. select REGMAP_IRQ
  49. select MFD_CORE
  50. help
  51. This supports for Marvell 88PM800 Power Management IC.
  52. This includes the I2C driver and the core APIs _only_, you have to
  53. select individual components like voltage regulators, RTC and
  54. battery-charger under the corresponding menus.
  55. config MFD_88PM805
  56. tristate "Support Marvell 88PM805"
  57. depends on I2C=y && GENERIC_HARDIRQS
  58. select REGMAP_I2C
  59. select REGMAP_IRQ
  60. select MFD_CORE
  61. help
  62. This supports for Marvell 88PM805 Power Management IC. This includes
  63. the I2C driver and the core APIs _only_, you have to select individual
  64. components like codec device, headset/Mic device under the
  65. corresponding menus.
  66. config MFD_SM501
  67. tristate "Support for Silicon Motion SM501"
  68. ---help---
  69. This is the core driver for the Silicon Motion SM501 multimedia
  70. companion chip. This device is a multifunction device which may
  71. provide numerous interfaces including USB host controller, USB gadget,
  72. asynchronous serial ports, audio functions, and a dual display video
  73. interface. The device may be connected by PCI or local bus with
  74. varying functions enabled.
  75. config MFD_SM501_GPIO
  76. bool "Export GPIO via GPIO layer"
  77. depends on MFD_SM501 && GPIOLIB
  78. ---help---
  79. This option uses the gpio library layer to export the 64 GPIO
  80. lines on the SM501. The platform data is used to supply the
  81. base number for the first GPIO line to register.
  82. config MFD_RTSX_PCI
  83. tristate "Support for Realtek PCI-E card reader"
  84. depends on PCI && GENERIC_HARDIRQS
  85. select MFD_CORE
  86. help
  87. This supports for Realtek PCI-Express card reader including rts5209,
  88. rts5229, rtl8411, etc. Realtek card reader supports access to many
  89. types of memory cards, such as Memory Stick, Memory Stick Pro,
  90. Secure Digital and MultiMediaCard.
  91. config MFD_ASIC3
  92. bool "Support for Compaq ASIC3"
  93. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  94. select MFD_CORE
  95. ---help---
  96. This driver supports the ASIC3 multifunction chip found on many
  97. PDAs (mainly iPAQ and HTC based ones)
  98. config MFD_DAVINCI_VOICECODEC
  99. tristate
  100. select MFD_CORE
  101. config MFD_DM355EVM_MSP
  102. bool "DaVinci DM355 EVM microcontroller"
  103. depends on I2C=y && MACH_DAVINCI_DM355_EVM
  104. help
  105. This driver supports the MSP430 microcontroller used on these
  106. boards. MSP430 firmware manages resets and power sequencing,
  107. inputs from buttons and the IR remote, LEDs, an RTC, and more.
  108. config MFD_TI_SSP
  109. tristate "TI Sequencer Serial Port support"
  110. depends on ARCH_DAVINCI_TNETV107X && GENERIC_HARDIRQS
  111. select MFD_CORE
  112. ---help---
  113. Say Y here if you want support for the Sequencer Serial Port
  114. in a Texas Instruments TNETV107X SoC.
  115. To compile this driver as a module, choose M here: the
  116. module will be called ti-ssp.
  117. config MFD_TI_AM335X_TSCADC
  118. tristate "TI ADC / Touch Screen chip support"
  119. select MFD_CORE
  120. select REGMAP
  121. select REGMAP_MMIO
  122. depends on GENERIC_HARDIRQS
  123. help
  124. If you say yes here you get support for Texas Instruments series
  125. of Touch Screen /ADC chips.
  126. To compile this driver as a module, choose M here: the
  127. module will be called ti_am335x_tscadc.
  128. config HTC_EGPIO
  129. bool "HTC EGPIO support"
  130. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  131. help
  132. This driver supports the CPLD egpio chip present on
  133. several HTC phones. It provides basic support for input
  134. pins, output pins, and irqs.
  135. config HTC_PASIC3
  136. tristate "HTC PASIC3 LED/DS1WM chip support"
  137. select MFD_CORE
  138. depends on GENERIC_HARDIRQS
  139. help
  140. This core driver provides register access for the LED/DS1WM
  141. chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
  142. HTC Magician devices, respectively. Actual functionality is
  143. handled by the leds-pasic3 and ds1wm drivers.
  144. config HTC_I2CPLD
  145. bool "HTC I2C PLD chip support"
  146. depends on I2C=y && GPIOLIB
  147. help
  148. If you say yes here you get support for the supposed CPLD
  149. found on omap850 HTC devices like the HTC Wizard and HTC Herald.
  150. This device provides input and output GPIOs through an I2C
  151. interface to one or more sub-chips.
  152. config UCB1400_CORE
  153. tristate "Philips UCB1400 Core driver"
  154. depends on AC97_BUS
  155. depends on GPIOLIB
  156. help
  157. This enables support for the Philips UCB1400 core functions.
  158. The UCB1400 is an AC97 audio codec.
  159. To compile this driver as a module, choose M here: the
  160. module will be called ucb1400_core.
  161. config MFD_LM3533
  162. tristate "LM3533 Lighting Power chip"
  163. depends on I2C
  164. select MFD_CORE
  165. select REGMAP_I2C
  166. depends on GENERIC_HARDIRQS
  167. help
  168. Say yes here to enable support for National Semiconductor / TI
  169. LM3533 Lighting Power chips.
  170. This driver provides common support for accessing the device;
  171. additional drivers must be enabled in order to use the LED,
  172. backlight or ambient-light-sensor functionality of the device.
  173. config TPS6105X
  174. tristate "TPS61050/61052 Boost Converters"
  175. depends on I2C
  176. select REGULATOR
  177. select MFD_CORE
  178. select REGULATOR_FIXED_VOLTAGE
  179. depends on GENERIC_HARDIRQS
  180. help
  181. This option enables a driver for the TP61050/TPS61052
  182. high-power "white LED driver". This boost converter is
  183. sometimes used for other things than white LEDs, and
  184. also contains a GPIO pin.
  185. config TPS65010
  186. tristate "TPS6501x Power Management chips"
  187. depends on I2C && GPIOLIB
  188. default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
  189. help
  190. If you say yes here you get support for the TPS6501x series of
  191. Power Management chips. These include voltage regulators,
  192. lithium ion/polymer battery charging, and other features that
  193. are often used in portable devices like cell phones and cameras.
  194. This driver can also be built as a module. If so, the module
  195. will be called tps65010.
  196. config TPS6507X
  197. tristate "TPS6507x Power Management / Touch Screen chips"
  198. select MFD_CORE
  199. depends on I2C && GENERIC_HARDIRQS
  200. help
  201. If you say yes here you get support for the TPS6507x series of
  202. Power Management / Touch Screen chips. These include voltage
  203. regulators, lithium ion/polymer battery charging, touch screen
  204. and other features that are often used in portable devices.
  205. This driver can also be built as a module. If so, the module
  206. will be called tps6507x.
  207. config MFD_TPS65217
  208. tristate "TPS65217 Power Management / White LED chips"
  209. depends on I2C && GENERIC_HARDIRQS
  210. select MFD_CORE
  211. select REGMAP_I2C
  212. help
  213. If you say yes here you get support for the TPS65217 series of
  214. Power Management / White LED chips.
  215. These include voltage regulators, lithium ion/polymer battery
  216. charger, wled and other features that are often used in portable
  217. devices.
  218. This driver can also be built as a module. If so, the module
  219. will be called tps65217.
  220. config MFD_TPS6586X
  221. bool "TPS6586x Power Management chips"
  222. depends on I2C=y && GENERIC_HARDIRQS
  223. select MFD_CORE
  224. select REGMAP_I2C
  225. help
  226. If you say yes here you get support for the TPS6586X series of
  227. Power Management chips.
  228. This driver provides common support for accessing the device,
  229. additional drivers must be enabled in order to use the
  230. functionality of the device.
  231. This driver can also be built as a module. If so, the module
  232. will be called tps6586x.
  233. config MFD_TPS65910
  234. bool "TPS65910 Power Management chip"
  235. depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
  236. select MFD_CORE
  237. select REGMAP_I2C
  238. select REGMAP_IRQ
  239. select IRQ_DOMAIN
  240. help
  241. if you say yes here you get support for the TPS65910 series of
  242. Power Management chips.
  243. config MFD_TPS65912
  244. bool
  245. depends on GPIOLIB
  246. config MFD_TPS65912_I2C
  247. bool "TPS65912 Power Management chip with I2C"
  248. select MFD_CORE
  249. select MFD_TPS65912
  250. depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
  251. help
  252. If you say yes here you get support for the TPS65912 series of
  253. PM chips with I2C interface.
  254. config MFD_TPS65912_SPI
  255. bool "TPS65912 Power Management chip with SPI"
  256. select MFD_CORE
  257. select MFD_TPS65912
  258. depends on SPI_MASTER && GPIOLIB && GENERIC_HARDIRQS
  259. help
  260. If you say yes here you get support for the TPS65912 series of
  261. PM chips with SPI interface.
  262. config MFD_TPS80031
  263. bool "TI TPS80031/TPS80032 Power Management chips"
  264. depends on I2C=y && GENERIC_HARDIRQS
  265. select MFD_CORE
  266. select REGMAP_I2C
  267. select REGMAP_IRQ
  268. help
  269. If you say yes here you get support for the Texas Instruments
  270. TPS80031/ TPS80032 Fully Integrated Power Management with Power
  271. Path and Battery Charger. The device provides five configurable
  272. step-down converters, 11 general purpose LDOs, USB OTG Module,
  273. ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
  274. Power Path from USB, 32K clock generator.
  275. config MENELAUS
  276. bool "Texas Instruments TWL92330/Menelaus PM chip"
  277. depends on I2C=y && ARCH_OMAP2
  278. help
  279. If you say yes here you get support for the Texas Instruments
  280. TWL92330/Menelaus Power Management chip. This include voltage
  281. regulators, Dual slot memory card transceivers, real-time clock
  282. and other features that are often used in portable devices like
  283. cell phones and PDAs.
  284. config TWL4030_CORE
  285. bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
  286. depends on I2C=y && GENERIC_HARDIRQS
  287. select IRQ_DOMAIN
  288. select REGMAP_I2C
  289. help
  290. Say yes here if you have TWL4030 / TWL6030 family chip on your board.
  291. This core driver provides register access and IRQ handling
  292. facilities, and registers devices for the various functions
  293. so that function-specific drivers can bind to them.
  294. These multi-function chips are found on many OMAP2 and OMAP3
  295. boards, providing power management, RTC, GPIO, keypad, a
  296. high speed USB OTG transceiver, an audio codec (on most
  297. versions) and many other features.
  298. config TWL4030_MADC
  299. tristate "Texas Instruments TWL4030 MADC"
  300. depends on TWL4030_CORE
  301. help
  302. This driver provides support for triton TWL4030-MADC. The
  303. driver supports both RT and SW conversion methods.
  304. This driver can be built as a module. If so it will be
  305. named twl4030-madc
  306. config TWL4030_POWER
  307. bool "Support power resources on TWL4030 family chips"
  308. depends on TWL4030_CORE && ARM
  309. help
  310. Say yes here if you want to use the power resources on the
  311. TWL4030 family chips. Most of these resources are regulators,
  312. which have a separate driver; some are control signals, such
  313. as clock request handshaking.
  314. This driver uses board-specific data to initialize the resources
  315. and load scripts controlling which resources are switched off/on
  316. or reset when a sleep, wakeup or warm reset event occurs.
  317. config MFD_TWL4030_AUDIO
  318. bool
  319. depends on TWL4030_CORE && GENERIC_HARDIRQS
  320. select MFD_CORE
  321. default n
  322. config TWL6040_CORE
  323. bool "Support for TWL6040 audio codec"
  324. depends on I2C=y && GENERIC_HARDIRQS
  325. select MFD_CORE
  326. select REGMAP_I2C
  327. select REGMAP_IRQ
  328. default n
  329. help
  330. Say yes here if you want support for Texas Instruments TWL6040 audio
  331. codec.
  332. This driver provides common support for accessing the device,
  333. additional drivers must be enabled in order to use the
  334. functionality of the device (audio, vibra).
  335. config MFD_STMPE
  336. bool "Support STMicroelectronics STMPE"
  337. depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
  338. select MFD_CORE
  339. help
  340. Support for the STMPE family of I/O Expanders from
  341. STMicroelectronics.
  342. Currently supported devices are:
  343. STMPE811: GPIO, Touchscreen
  344. STMPE1601: GPIO, Keypad
  345. STMPE2401: GPIO, Keypad
  346. STMPE2403: GPIO, Keypad
  347. This driver provides common support for accessing the device,
  348. additional drivers must be enabled in order to use the functionality
  349. of the device. Currently available sub drivers are:
  350. GPIO: stmpe-gpio
  351. Keypad: stmpe-keypad
  352. Touchscreen: stmpe-ts
  353. menu "STMPE Interface Drivers"
  354. depends on MFD_STMPE
  355. config STMPE_I2C
  356. bool "STMPE I2C Inteface"
  357. depends on I2C=y
  358. default y
  359. help
  360. This is used to enable I2C interface of STMPE
  361. config STMPE_SPI
  362. bool "STMPE SPI Inteface"
  363. depends on SPI_MASTER
  364. help
  365. This is used to enable SPI interface of STMPE
  366. endmenu
  367. config MFD_TC3589X
  368. bool "Support Toshiba TC35892 and variants"
  369. depends on I2C=y && GENERIC_HARDIRQS
  370. select MFD_CORE
  371. help
  372. Support for the Toshiba TC35892 and variants I/O Expander.
  373. This driver provides common support for accessing the device,
  374. additional drivers must be enabled in order to use the
  375. functionality of the device.
  376. config MFD_TMIO
  377. bool
  378. default n
  379. config MFD_T7L66XB
  380. bool "Support Toshiba T7L66XB"
  381. depends on ARM && HAVE_CLK && GENERIC_HARDIRQS
  382. select MFD_CORE
  383. select MFD_TMIO
  384. help
  385. Support for Toshiba Mobile IO Controller T7L66XB
  386. config MFD_SMSC
  387. bool "Support for the SMSC ECE1099 series chips"
  388. depends on I2C=y && GENERIC_HARDIRQS
  389. select MFD_CORE
  390. select REGMAP_I2C
  391. help
  392. If you say yes here you get support for the
  393. ece1099 chips from SMSC.
  394. To compile this driver as a module, choose M here: the
  395. module will be called smsc.
  396. config MFD_TC6387XB
  397. bool "Support Toshiba TC6387XB"
  398. depends on ARM && HAVE_CLK
  399. select MFD_CORE
  400. select MFD_TMIO
  401. help
  402. Support for Toshiba Mobile IO Controller TC6387XB
  403. config MFD_TC6393XB
  404. bool "Support Toshiba TC6393XB"
  405. depends on ARM && HAVE_CLK
  406. select GPIOLIB
  407. select MFD_CORE
  408. select MFD_TMIO
  409. help
  410. Support for Toshiba Mobile IO Controller TC6393XB
  411. config PMIC_DA903X
  412. bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
  413. depends on I2C=y
  414. help
  415. Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
  416. ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
  417. usually found on PXA processors-based platforms. This includes
  418. the I2C driver and the core APIs _only_, you have to select
  419. individual components like LCD backlight, voltage regulators,
  420. LEDs and battery-charger under the corresponding menus.
  421. config PMIC_DA9052
  422. bool
  423. select MFD_CORE
  424. config MFD_DA9052_SPI
  425. bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
  426. select REGMAP_SPI
  427. select REGMAP_IRQ
  428. select PMIC_DA9052
  429. depends on SPI_MASTER=y && GENERIC_HARDIRQS
  430. help
  431. Support for the Dialog Semiconductor DA9052 PMIC
  432. when controlled using SPI. This driver provides common support
  433. for accessing the device, additional drivers must be enabled in
  434. order to use the functionality of the device.
  435. config MFD_DA9052_I2C
  436. bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
  437. select REGMAP_I2C
  438. select REGMAP_IRQ
  439. select PMIC_DA9052
  440. depends on I2C=y && GENERIC_HARDIRQS
  441. help
  442. Support for the Dialog Semiconductor DA9052 PMIC
  443. when controlled using I2C. This driver provides common support
  444. for accessing the device, additional drivers must be enabled in
  445. order to use the functionality of the device.
  446. config MFD_DA9055
  447. bool "Dialog Semiconductor DA9055 PMIC Support"
  448. select REGMAP_I2C
  449. select REGMAP_IRQ
  450. select PMIC_DA9055
  451. select MFD_CORE
  452. depends on I2C=y && GENERIC_HARDIRQS
  453. help
  454. Say yes here for support of Dialog Semiconductor DA9055. This is
  455. a Power Management IC. This driver provides common support for
  456. accessing the device as well as the I2C interface to the chip itself.
  457. Additional drivers must be enabled in order to use the functionality
  458. of the device.
  459. This driver can be built as a module. If built as a module it will be
  460. called "da9055"
  461. config PMIC_ADP5520
  462. bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
  463. depends on I2C=y
  464. help
  465. Say yes here to add support for Analog Devices AD5520 and ADP5501,
  466. Multifunction Power Management IC. This includes
  467. the I2C driver and the core APIs _only_, you have to select
  468. individual components like LCD backlight, LEDs, GPIOs and Kepad
  469. under the corresponding menus.
  470. config MFD_LP8788
  471. bool "Texas Instruments LP8788 Power Management Unit Driver"
  472. depends on I2C=y && GENERIC_HARDIRQS
  473. select MFD_CORE
  474. select REGMAP_I2C
  475. select IRQ_DOMAIN
  476. help
  477. TI LP8788 PMU supports regulators, battery charger, RTC,
  478. ADC, backlight driver and current sinks.
  479. config MFD_MAX77686
  480. bool "Maxim Semiconductor MAX77686 PMIC Support"
  481. depends on I2C=y && GENERIC_HARDIRQS
  482. select MFD_CORE
  483. select REGMAP_I2C
  484. select IRQ_DOMAIN
  485. help
  486. Say yes here to support for Maxim Semiconductor MAX77686.
  487. This is a Power Management IC with RTC on chip.
  488. This driver provides common support for accessing the device;
  489. additional drivers must be enabled in order to use the functionality
  490. of the device.
  491. config MFD_MAX77693
  492. bool "Maxim Semiconductor MAX77693 PMIC Support"
  493. depends on I2C=y && GENERIC_HARDIRQS
  494. select MFD_CORE
  495. select REGMAP_I2C
  496. help
  497. Say yes here to support for Maxim Semiconductor MAX77693.
  498. This is a companion Power Management IC with Flash, Haptic, Charger,
  499. and MUIC(Micro USB Interface Controller) controls on chip.
  500. This driver provides common support for accessing the device;
  501. additional drivers must be enabled in order to use the functionality
  502. of the device.
  503. config MFD_MAX8907
  504. tristate "Maxim Semiconductor MAX8907 PMIC Support"
  505. select MFD_CORE
  506. depends on I2C=y && GENERIC_HARDIRQS
  507. select REGMAP_I2C
  508. select REGMAP_IRQ
  509. help
  510. Say yes here to support for Maxim Semiconductor MAX8907. This is
  511. a Power Management IC. This driver provides common support for
  512. accessing the device; additional drivers must be enabled in order
  513. to use the functionality of the device.
  514. config MFD_MAX8925
  515. bool "Maxim Semiconductor MAX8925 PMIC Support"
  516. depends on I2C=y && GENERIC_HARDIRQS
  517. select MFD_CORE
  518. help
  519. Say yes here to support for Maxim Semiconductor MAX8925. This is
  520. a Power Management IC. This driver provides common support for
  521. accessing the device, additional drivers must be enabled in order
  522. to use the functionality of the device.
  523. config MFD_MAX8997
  524. bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
  525. depends on I2C=y && GENERIC_HARDIRQS
  526. select MFD_CORE
  527. select IRQ_DOMAIN
  528. help
  529. Say yes here to support for Maxim Semiconductor MAX8997/8966.
  530. This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
  531. MUIC controls on chip.
  532. This driver provides common support for accessing the device;
  533. additional drivers must be enabled in order to use the functionality
  534. of the device.
  535. config MFD_MAX8998
  536. bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
  537. depends on I2C=y && GENERIC_HARDIRQS
  538. select MFD_CORE
  539. help
  540. Say yes here to support for Maxim Semiconductor MAX8998 and
  541. National Semiconductor LP3974. This is a Power Management IC.
  542. This driver provides common support for accessing the device,
  543. additional drivers must be enabled in order to use the functionality
  544. of the device.
  545. config MFD_SEC_CORE
  546. bool "SAMSUNG Electronics PMIC Series Support"
  547. depends on I2C=y && GENERIC_HARDIRQS
  548. select MFD_CORE
  549. select REGMAP_I2C
  550. select REGMAP_IRQ
  551. help
  552. Support for the Samsung Electronics MFD series.
  553. This driver provides common support for accessing the device,
  554. additional drivers must be enabled in order to use the functionality
  555. of the device
  556. config MFD_ARIZONA
  557. select REGMAP
  558. select REGMAP_IRQ
  559. select MFD_CORE
  560. bool
  561. config MFD_ARIZONA_I2C
  562. tristate "Support Wolfson Microelectronics Arizona platform with I2C"
  563. select MFD_ARIZONA
  564. select MFD_CORE
  565. select REGMAP_I2C
  566. depends on I2C && GENERIC_HARDIRQS
  567. help
  568. Support for the Wolfson Microelectronics Arizona platform audio SoC
  569. core functionality controlled via I2C.
  570. config MFD_ARIZONA_SPI
  571. tristate "Support Wolfson Microelectronics Arizona platform with SPI"
  572. select MFD_ARIZONA
  573. select MFD_CORE
  574. select REGMAP_SPI
  575. depends on SPI_MASTER && GENERIC_HARDIRQS
  576. help
  577. Support for the Wolfson Microelectronics Arizona platform audio SoC
  578. core functionality controlled via I2C.
  579. config MFD_WM5102
  580. bool "Support Wolfson Microelectronics WM5102"
  581. depends on MFD_ARIZONA
  582. help
  583. Support for Wolfson Microelectronics WM5102 low power audio SoC
  584. config MFD_WM5110
  585. bool "Support Wolfson Microelectronics WM5110"
  586. depends on MFD_ARIZONA
  587. help
  588. Support for Wolfson Microelectronics WM5110 low power audio SoC
  589. config MFD_WM8400
  590. bool "Support Wolfson Microelectronics WM8400"
  591. select MFD_CORE
  592. depends on I2C=y && GENERIC_HARDIRQS
  593. select REGMAP_I2C
  594. help
  595. Support for the Wolfson Microelecronics WM8400 PMIC and audio
  596. CODEC. This driver provides common support for accessing
  597. the device, additional drivers must be enabled in order to use
  598. the functionality of the device.
  599. config MFD_WM831X
  600. bool
  601. depends on GENERIC_HARDIRQS
  602. config MFD_WM831X_I2C
  603. bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
  604. select MFD_CORE
  605. select MFD_WM831X
  606. select REGMAP_I2C
  607. select IRQ_DOMAIN
  608. depends on I2C=y && GENERIC_HARDIRQS
  609. help
  610. Support for the Wolfson Microelecronics WM831x and WM832x PMICs
  611. when controlled using I2C. This driver provides common support
  612. for accessing the device, additional drivers must be enabled in
  613. order to use the functionality of the device.
  614. config MFD_WM831X_SPI
  615. bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
  616. select MFD_CORE
  617. select MFD_WM831X
  618. select REGMAP_SPI
  619. select IRQ_DOMAIN
  620. depends on SPI_MASTER && GENERIC_HARDIRQS
  621. help
  622. Support for the Wolfson Microelecronics WM831x and WM832x PMICs
  623. when controlled using SPI. This driver provides common support
  624. for accessing the device, additional drivers must be enabled in
  625. order to use the functionality of the device.
  626. config MFD_WM8350
  627. bool
  628. depends on GENERIC_HARDIRQS
  629. config MFD_WM8350_CONFIG_MODE_0
  630. bool
  631. depends on MFD_WM8350
  632. config MFD_WM8350_CONFIG_MODE_1
  633. bool
  634. depends on MFD_WM8350
  635. config MFD_WM8350_CONFIG_MODE_2
  636. bool
  637. depends on MFD_WM8350
  638. config MFD_WM8350_CONFIG_MODE_3
  639. bool
  640. depends on MFD_WM8350
  641. config MFD_WM8351_CONFIG_MODE_0
  642. bool
  643. depends on MFD_WM8350
  644. config MFD_WM8351_CONFIG_MODE_1
  645. bool
  646. depends on MFD_WM8350
  647. config MFD_WM8351_CONFIG_MODE_2
  648. bool
  649. depends on MFD_WM8350
  650. config MFD_WM8351_CONFIG_MODE_3
  651. bool
  652. depends on MFD_WM8350
  653. config MFD_WM8352_CONFIG_MODE_0
  654. bool
  655. depends on MFD_WM8350
  656. config MFD_WM8352_CONFIG_MODE_1
  657. bool
  658. depends on MFD_WM8350
  659. config MFD_WM8352_CONFIG_MODE_2
  660. bool
  661. depends on MFD_WM8350
  662. config MFD_WM8352_CONFIG_MODE_3
  663. bool
  664. depends on MFD_WM8350
  665. config MFD_WM8350_I2C
  666. bool "Support Wolfson Microelectronics WM8350 with I2C"
  667. select MFD_WM8350
  668. depends on I2C=y && GENERIC_HARDIRQS
  669. help
  670. The WM8350 is an integrated audio and power management
  671. subsystem with watchdog and RTC functionality for embedded
  672. systems. This option enables core support for the WM8350 with
  673. I2C as the control interface. Additional options must be
  674. selected to enable support for the functionality of the chip.
  675. config MFD_WM8994
  676. bool "Support Wolfson Microelectronics WM8994"
  677. select MFD_CORE
  678. select REGMAP_I2C
  679. select REGMAP_IRQ
  680. depends on I2C=y && GENERIC_HARDIRQS
  681. help
  682. The WM8994 is a highly integrated hi-fi CODEC designed for
  683. smartphone applicatiosn. As well as audio functionality it
  684. has on board GPIO and regulator functionality which is
  685. supported via the relevant subsystems. This driver provides
  686. core support for the WM8994, in order to use the actual
  687. functionaltiy of the device other drivers must be enabled.
  688. config MFD_PCF50633
  689. tristate "Support for NXP PCF50633"
  690. depends on I2C
  691. select REGMAP_I2C
  692. help
  693. Say yes here if you have NXP PCF50633 chip on your board.
  694. This core driver provides register access and IRQ handling
  695. facilities, and registers devices for the various functions
  696. so that function-specific drivers can bind to them.
  697. config PCF50633_ADC
  698. tristate "Support for NXP PCF50633 ADC"
  699. depends on MFD_PCF50633
  700. help
  701. Say yes here if you want to include support for ADC in the
  702. NXP PCF50633 chip.
  703. config PCF50633_GPIO
  704. tristate "Support for NXP PCF50633 GPIO"
  705. depends on MFD_PCF50633
  706. help
  707. Say yes here if you want to include support GPIO for pins on
  708. the PCF50633 chip.
  709. config MFD_MC13783
  710. tristate
  711. config MFD_MC13XXX
  712. tristate
  713. depends on (SPI_MASTER || I2C) && GENERIC_HARDIRQS
  714. select MFD_CORE
  715. select MFD_MC13783
  716. help
  717. Enable support for the Freescale MC13783 and MC13892 PMICs.
  718. This driver provides common support for accessing the device,
  719. additional drivers must be enabled in order to use the
  720. functionality of the device.
  721. config MFD_MC13XXX_SPI
  722. tristate "Freescale MC13783 and MC13892 SPI interface"
  723. depends on SPI_MASTER && GENERIC_HARDIRQS
  724. select REGMAP_SPI
  725. select MFD_MC13XXX
  726. help
  727. Select this if your MC13xxx is connected via an SPI bus.
  728. config MFD_MC13XXX_I2C
  729. tristate "Freescale MC13892 I2C interface"
  730. depends on I2C && GENERIC_HARDIRQS
  731. select REGMAP_I2C
  732. select MFD_MC13XXX
  733. help
  734. Select this if your MC13xxx is connected via an I2C bus.
  735. config ABX500_CORE
  736. bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
  737. default y if ARCH_U300 || ARCH_U8500
  738. help
  739. Say yes here if you have the ABX500 Mixed Signal IC family
  740. chips. This core driver expose register access functions.
  741. Functionality specific drivers using these functions can
  742. remain unchanged when IC changes. Binding of the functions to
  743. actual register access is done by the IC core driver.
  744. config AB3100_CORE
  745. bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
  746. depends on I2C=y && ABX500_CORE && GENERIC_HARDIRQS
  747. select MFD_CORE
  748. default y if ARCH_U300
  749. help
  750. Select this to enable the AB3100 Mixed Signal IC core
  751. functionality. This connects to a AB3100 on the I2C bus
  752. and expose a number of symbols needed for dependent devices
  753. to read and write registers and subscribe to events from
  754. this multi-functional IC. This is needed to use other features
  755. of the AB3100 such as battery-backed RTC, charging control,
  756. LEDs, vibrator, system power and temperature, power management
  757. and ALSA sound.
  758. config AB3100_OTP
  759. tristate "ST-Ericsson AB3100 OTP functions"
  760. depends on AB3100_CORE
  761. default y if AB3100_CORE
  762. help
  763. Select this to enable the AB3100 Mixed Signal IC OTP (one-time
  764. programmable memory) support. This exposes a sysfs file to read
  765. out OTP values.
  766. config EZX_PCAP
  767. bool "PCAP Support"
  768. depends on GENERIC_HARDIRQS && SPI_MASTER
  769. help
  770. This enables the PCAP ASIC present on EZX Phones. This is
  771. needed for MMC, TouchScreen, Sound, USB, etc..
  772. config AB8500_CORE
  773. bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
  774. depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
  775. select POWER_SUPPLY
  776. select MFD_CORE
  777. select IRQ_DOMAIN
  778. help
  779. Select this option to enable access to AB8500 power management
  780. chip. This connects to U8500 either on the SSP/SPI bus (deprecated
  781. since hardware version v1.0) or the I2C bus via PRCMU. It also adds
  782. the irq_chip parts for handling the Mixed Signal chip events.
  783. This chip embeds various other multimedia funtionalities as well.
  784. config AB8500_DEBUG
  785. bool "Enable debug info via debugfs"
  786. depends on AB8500_CORE && DEBUG_FS
  787. default y if DEBUG_FS
  788. help
  789. Select this option if you want debug information using the debug
  790. filesystem, debugfs.
  791. config AB8500_GPADC
  792. bool "AB8500 GPADC driver"
  793. depends on AB8500_CORE && REGULATOR_AB8500
  794. default y
  795. help
  796. AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
  797. config MFD_DB8500_PRCMU
  798. bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
  799. depends on UX500_SOC_DB8500
  800. select MFD_CORE
  801. help
  802. Select this option to enable support for the DB8500 Power Reset
  803. and Control Management Unit. This is basically an autonomous
  804. system controller running an XP70 microprocessor, which is accessed
  805. through a register map.
  806. config MFD_CS5535
  807. tristate "Support for CS5535 and CS5536 southbridge core functions"
  808. select MFD_CORE
  809. depends on PCI && X86
  810. ---help---
  811. This is the core driver for CS5535/CS5536 MFD functions. This is
  812. necessary for using the board's GPIO and MFGPT functionality.
  813. config MFD_TIMBERDALE
  814. tristate "Support for the Timberdale FPGA"
  815. select MFD_CORE
  816. depends on PCI && GPIOLIB
  817. ---help---
  818. This is the core driver for the timberdale FPGA. This device is a
  819. multifunction device which exposes numerous platform devices.
  820. The timberdale FPGA can be found on the Intel Atom development board
  821. for in-vehicle infontainment, called Russellville.
  822. config LPC_SCH
  823. tristate "Intel SCH LPC"
  824. depends on PCI && GENERIC_HARDIRQS
  825. select MFD_CORE
  826. help
  827. LPC bridge function of the Intel SCH provides support for
  828. System Management Bus and General Purpose I/O.
  829. config LPC_ICH
  830. tristate "Intel ICH LPC"
  831. depends on PCI && GENERIC_HARDIRQS
  832. select MFD_CORE
  833. help
  834. The LPC bridge function of the Intel ICH provides support for
  835. many functional units. This driver provides needed support for
  836. other drivers to control these functions, currently GPIO and
  837. watchdog.
  838. config MFD_RDC321X
  839. tristate "Support for RDC-R321x southbridge"
  840. select MFD_CORE
  841. depends on PCI && GENERIC_HARDIRQS
  842. help
  843. Say yes here if you want to have support for the RDC R-321x SoC
  844. southbridge which provides access to GPIOs and Watchdog using the
  845. southbridge PCI device configuration space.
  846. config MFD_JANZ_CMODIO
  847. tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
  848. select MFD_CORE
  849. depends on PCI && GENERIC_HARDIRQS
  850. help
  851. This is the core driver for the Janz CMOD-IO PCI MODULbus
  852. carrier board. This device is a PCI to MODULbus bridge which may
  853. host many different types of MODULbus daughterboards, including
  854. CAN and GPIO controllers.
  855. config MFD_JZ4740_ADC
  856. bool "Support for the JZ4740 SoC ADC core"
  857. select MFD_CORE
  858. select GENERIC_IRQ_CHIP
  859. depends on MACH_JZ4740
  860. help
  861. Say yes here if you want support for the ADC unit in the JZ4740 SoC.
  862. This driver is necessary for jz4740-battery and jz4740-hwmon driver.
  863. config MFD_VX855
  864. tristate "Support for VIA VX855/VX875 integrated south bridge"
  865. depends on PCI && GENERIC_HARDIRQS
  866. select MFD_CORE
  867. help
  868. Say yes here to enable support for various functions of the
  869. VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
  870. and/or vx855_gpio drivers for this to do anything useful.
  871. config MFD_WL1273_CORE
  872. tristate "Support for TI WL1273 FM radio."
  873. depends on I2C && GENERIC_HARDIRQS
  874. select MFD_CORE
  875. default n
  876. help
  877. This is the core driver for the TI WL1273 FM radio. This MFD
  878. driver connects the radio-wl1273 V4L2 module and the wl1273
  879. audio codec.
  880. config MFD_OMAP_USB_HOST
  881. bool "Support OMAP USBHS core and TLL driver"
  882. depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
  883. default y
  884. help
  885. This is the core driver for the OAMP EHCI and OHCI drivers.
  886. This MFD driver does the required setup functionalities for
  887. OMAP USB Host drivers.
  888. config MFD_PM8XXX
  889. tristate
  890. config MFD_PM8921_CORE
  891. tristate "Qualcomm PM8921 PMIC chip"
  892. depends on MSM_SSBI
  893. select MFD_CORE
  894. select MFD_PM8XXX
  895. help
  896. If you say yes to this option, support will be included for the
  897. built-in PM8921 PMIC chip.
  898. This is required if your board has a PM8921 and uses its features,
  899. such as: MPPs, GPIOs, regulators, interrupts, and PWM.
  900. Say M here if you want to include support for PM8921 chip as a module.
  901. This will build a module called "pm8921-core".
  902. config MFD_PM8XXX_IRQ
  903. bool "Support for Qualcomm PM8xxx IRQ features"
  904. depends on MFD_PM8XXX
  905. default y if MFD_PM8XXX
  906. help
  907. This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
  908. This is required to use certain other PM 8xxx features, such as GPIO
  909. and MPP.
  910. config TPS65911_COMPARATOR
  911. tristate
  912. config MFD_TPS65090
  913. bool "TPS65090 Power Management chips"
  914. depends on I2C=y && GENERIC_HARDIRQS
  915. select MFD_CORE
  916. select REGMAP_I2C
  917. select REGMAP_IRQ
  918. help
  919. If you say yes here you get support for the TPS65090 series of
  920. Power Management chips.
  921. This driver provides common support for accessing the device,
  922. additional drivers must be enabled in order to use the
  923. functionality of the device.
  924. config MFD_AAT2870_CORE
  925. bool "Support for the AnalogicTech AAT2870"
  926. select MFD_CORE
  927. depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
  928. help
  929. If you say yes here you get support for the AAT2870.
  930. This driver provides common support for accessing the device,
  931. additional drivers must be enabled in order to use the
  932. functionality of the device.
  933. config MFD_INTEL_MSIC
  934. bool "Support for Intel MSIC"
  935. depends on INTEL_SCU_IPC
  936. select MFD_CORE
  937. help
  938. Select this option to enable access to Intel MSIC (Avatele
  939. Passage) chip. This chip embeds audio, battery, GPIO, etc.
  940. devices used in Intel Medfield platforms.
  941. config MFD_RC5T583
  942. bool "Ricoh RC5T583 Power Management system device"
  943. depends on I2C=y && GENERIC_HARDIRQS
  944. select MFD_CORE
  945. select REGMAP_I2C
  946. help
  947. Select this option to get support for the RICOH583 Power
  948. Management system device.
  949. This driver provides common support for accessing the device
  950. through i2c interface. The device supports multiple sub-devices
  951. like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
  952. Additional drivers must be enabled in order to use the
  953. different functionality of the device.
  954. config MFD_STA2X11
  955. bool "STA2X11 multi function device support"
  956. depends on STA2X11 && GENERIC_HARDIRQS
  957. select MFD_CORE
  958. select REGMAP_MMIO
  959. config MFD_SYSCON
  960. bool "System Controller Register R/W Based on Regmap"
  961. depends on OF
  962. select REGMAP_MMIO
  963. help
  964. Select this option to enable accessing system control registers
  965. via regmap.
  966. config MFD_PALMAS
  967. bool "Support for the TI Palmas series chips"
  968. select MFD_CORE
  969. select REGMAP_I2C
  970. select REGMAP_IRQ
  971. depends on I2C=y && GENERIC_HARDIRQS
  972. help
  973. If you say yes here you get support for the Palmas
  974. series of PMIC chips from Texas Instruments.
  975. config MFD_VIPERBOARD
  976. tristate "Support for Nano River Technologies Viperboard"
  977. select MFD_CORE
  978. depends on USB && GENERIC_HARDIRQS
  979. default n
  980. help
  981. Say yes here if you want support for Nano River Technologies
  982. Viperboard.
  983. There are mfd cell drivers available for i2c master, adc and
  984. both gpios found on the board. The spi part does not yet
  985. have a driver.
  986. You need to select the mfd cell drivers separately.
  987. The drivers do not support all features the board exposes.
  988. config MFD_RETU
  989. tristate "Support for Retu multi-function device"
  990. select MFD_CORE
  991. depends on I2C && GENERIC_HARDIRQS
  992. select REGMAP_IRQ
  993. help
  994. Retu is a multi-function device found on Nokia Internet Tablets
  995. (770, N800 and N810).
  996. config MFD_AS3711
  997. bool "Support for AS3711"
  998. select MFD_CORE
  999. select REGMAP_I2C
  1000. select REGMAP_IRQ
  1001. depends on I2C=y && GENERIC_HARDIRQS
  1002. help
  1003. Support for the AS3711 PMIC from AMS
  1004. endmenu
  1005. endif
  1006. menu "Multimedia Capabilities Port drivers"
  1007. depends on ARCH_SA1100
  1008. config MCP
  1009. tristate
  1010. # Interface drivers
  1011. config MCP_SA11X0
  1012. tristate "Support SA11x0 MCP interface"
  1013. depends on ARCH_SA1100
  1014. select MCP
  1015. # Chip drivers
  1016. config MCP_UCB1200
  1017. bool "Support for UCB1200 / UCB1300"
  1018. depends on MCP_SA11X0
  1019. select MCP
  1020. config MCP_UCB1200_TS
  1021. tristate "Touchscreen interface support"
  1022. depends on MCP_UCB1200 && INPUT
  1023. endmenu
  1024. config VEXPRESS_CONFIG
  1025. bool
  1026. help
  1027. Platform configuration infrastructure for the ARM Ltd.
  1028. Versatile Express.