Kconfig 35 KB

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