This driver can also be built as a module. If so, the module
will be called tps6586x.
+config MFD_TPS65910
+ bool "TPS65910 Power Management chip"
+ depends on I2C=y && GPIOLIB
+ select MFD_CORE
+ select GPIO_TPS65910
+ select REGMAP_I2C
+ help
+ if you say yes here you get support for the TPS65910 series of
+ Power Management chips.
+
+config MFD_TPS65912
+ bool
+ depends on GPIOLIB
+
+config MFD_TPS65912_I2C
+ bool "TPS65912 Power Management chip with I2C"
+ select MFD_CORE
+ select MFD_TPS65912
+ depends on I2C=y && GPIOLIB
+ help
+ If you say yes here you get support for the TPS65912 series of
+ PM chips with I2C interface.
+
+config MFD_TPS65912_SPI
+ bool "TPS65912 Power Management chip with SPI"
+ select MFD_CORE
+ select MFD_TPS65912
+ depends on SPI_MASTER && GPIOLIB
+ help
+ If you say yes here you get support for the TPS65912 series of
+ PM chips with SPI interface.
config MENELAUS
bool "Texas Instruments TWL92330/Menelaus PM chip"
depends on I2C=y && ARCH_OMAP2
high speed USB OTG transceiver, an audio codec (on most
versions) and many other features.
+config TWL6030_POWER
+ bool "Support power resources on TWL6030 family chips"
+ depends on TWL4030_CORE
+ help
+ Say yes here if you want to use the power resources on the
+ TWL6030 family chips. Most of these resources are regulators,
+ which have a separate driver; some are control signals, such
+ as clock request handshaking.
+
+ This driver defaults to assuming only APPs processor uses
+ the resource, it can however be overridden by board file
+
config TWL4030_MADC
tristate "Texas Instruments TWL4030 MADC"
depends on TWL4030_CORE
Say yes here if you want support for TWL6030 PWM.
This is used to control charging LED brightness.
+config TWL6030_POWEROFF
+ bool "TWL6030 device poweroff"
+ depends on TWL4030_CORE
+
+config TWL6030_MADC
+ tristate "Texas Instruments TWL6030 MADC"
+ depends on TWL4030_CORE
+ help
+ This driver provides support for TWL6030-MADC. The
+ driver supports both RT and SW conversion methods.
+
+ This driver can be built as a module. If so it will be
+ named twl6030-madc
+
+config TWL6030_GPADC
+ tristate "TWL6030 GPADC (General Purpose A/D Convertor) Support"
+ depends on TWL4030_CORE
+ default n
+ help
+ Say yes here if you want support for the TWL6030 General Purpose
+ A/D Convertor.
+
+config MFD_RK808
+ bool "RK808 Power Management chip"
+ depends on I2C=y
+ select MFD_CORE
+ select RTC_RK808
+ help
+ if you say yes here you get support for the RK808 series of
+ Power Management chips.
+
+config MFD_RICOH619
+ bool "Ricoh RC5T619 Power Management system device"
+ depends on I2C && GPIOLIB && GENERIC_HARDIRQS
+ select MFD_CORE
+ default n
+ help
+ If you say yes here you get support for the RICOH619 Power
+ Management system device.
+ This driver provides common support for accessing the device,
+ additional drivers must be enabled in order to use the
+ functionality of the device.
+
+config AIC3262_CODEC
+ bool "Support TI Codec Aic3262"
+ select MFD_CORE
+ default n
+
config MFD_STMPE
bool "Support STMicroelectronics STMPE"
depends on I2C=y && GENERIC_HARDIRQS
for accessing the device, additional drivers must be enabled in
order to use the functionality of the device.
+config MFD_WM831X_SPI_A22
+ bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI for A22"
+ #select MFD_CORE
+ #select MFD_WM831X
+ depends on SPI_MASTER && GENERIC_HARDIRQS
+ help
+ Support for the Wolfson Microelecronics WM831x and WM832x PMICs
+ when controlled using SPI. This driver provides common support
+ for accessing the device, additional drivers must be enabled in
+ order to use the functionality of the device.
+
config MFD_WM8350
bool
depends on GENERIC_HARDIRQS
This is required to use certain other PM 8xxx features, such as GPIO
and MPP.
-config MFD_TPS65910
- bool "TPS65910 Power Management chip"
- depends on I2C=y && GPIOLIB
+config TPS65911_COMPARATOR
+ tristate
+
+config MFD_TPS65090
+ bool "TPS65090 Power Management chips"
+ depends on I2C=y && GENERIC_HARDIRQS
select MFD_CORE
- select GPIO_TPS65910
+ select REGMAP_I2C
help
- if you say yes here you get support for the TPS65910 series of
+ If you say yes here you get support for the TPS65090 series of
Power Management chips.
+ This driver provides common support for accessing the device,
+ additional drivers must be enabled in order to use the
+ functionality of the device.
+
+config MFD_RT5025
+ bool "RT5025 PMIC Chip Core driver"
+ depends on I2C
+ select MFD_CORE
+ default n
+ help
+ Enable RT5025 core driver.
-config TPS65911_COMPARATOR
- tristate
+config MFD_RT5025_MISC
+ bool "RT5025 PMIC chip misc configuration"
+ depends on MFD_RT5025
+ default n
+ help
+ Enable RT5025 Misc configuration.
+
+config MFD_RT5025_IRQ
+ bool "RT5025_PMIC chip irq driver"
+ depends on MFD_RT5025
+ default n
+ help
+ Enable RT5025 IRQ configuration and interrupt.
+
+config MFD_RT5025_DEBUG
+ bool "RT5025 PMIC Chip Core Debug"
+ depends on MFD_RT5025 && DEBUG_FS
+ default n
+ help
+ Enable RT5025 core debug driver.
+
+config MFD_RT_SHOW_INFO
+ bool "RT5025 debug message"
+ depends on MFD_RT5025
+ default n
+ help
+ Eneable RT5025 debug message
+
+config MFD_RK610
+ bool "RK610(Jetta) Multimedia support"
+ depends on I2C=y && GPIOLIB
+ select MFD_CORE
+ help
+ if you say yes here you get support for the RK610, with func as
+ HDMI LCD LVDS TVOUT CODEC.
+
+config MFD_RK616
+ bool "RK616(Jetta B) Multifunction device support"
+ depends on I2C=y
+ select MFD_CORE
+ help
+ if you say yes here you get support for the RK616, with func as
+ HDMI、LCD、LVDS、CODEC、MIPI.
+
+config RK616_USE_MCLK_12M
+ bool "Enable 12M clock for timing reconstruction"
+ depends on MFD_RK616
+ select RK_HDMI_CTL_CODEC
+ default y
+ help
+ if you say y here ,it will enable 12M clock for timing reconstruction
+
+config RK616_DEBUG
+ bool "RK616(JettaB) debug enable"
+ depends on MFD_RK616
+ help
+ if you say y here ,it will enable rk616 debug function
endif # MFD_SUPPORT
projects / firefly-linux-kernel-4.4.55.git / blobdiff