Kconfig 35 KB

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