Kconfig 34 KB

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