summaryrefslogtreecommitdiffstats
path: root/drivers/mfd
diff options
context:
space:
mode:
authorSamuel Ortiz <sameo@linux.intel.com>2010-06-19 02:29:24 +0200
committerSamuel Ortiz <sameo@linux.intel.com>2010-08-12 11:27:23 +0200
commit15742c8a42c89aa5e63542b0de00b0dc4c5038cf (patch)
treea342b299378a82f74ba0d15109ba227265151849 /drivers/mfd
parent3cb46ac058f8ce3ed339fc5dcf6faae4329153c9 (diff)
downloadlinux-15742c8a42c89aa5e63542b0de00b0dc4c5038cf.tar.gz
linux-15742c8a42c89aa5e63542b0de00b0dc4c5038cf.tar.bz2
linux-15742c8a42c89aa5e63542b0de00b0dc4c5038cf.zip
mfd: More verbose MFD Kconfig entry
For people to be able to intellingibly decide if they want to enable MFD drivers or not, we have to give them a much better description of what they are.
Diffstat (limited to 'drivers/mfd')
-rw-r--r--drivers/mfd/Kconfig11
1 files changed, 10 insertions, 1 deletions
diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
index 9da0e504bbe9..29781ca1eb6f 100644
--- a/drivers/mfd/Kconfig
+++ b/drivers/mfd/Kconfig
@@ -7,7 +7,16 @@ menuconfig MFD_SUPPORT
depends on HAS_IOMEM
default y
help
- Configure MFD device drivers.
+ Multifunction devices embed several functions (e.g. GPIOs,
+ touchscreens, keyboards, current regulators, power management chips,
+ etc...) in one single integrated circuit. They usually talk to the
+ main CPU through one or more IRQ lines and low speed data busses (SPI,
+ I2C, etc..). They appear as one single device to the main system
+ through the data bus and the MFD framework allows for sub devices
+ (a.k.a. functions) to appear as discrete platform devices.
+ MFDs are typically found on embedded platforms.
+
+ This option alone does not add any kernel code.
if MFD_SUPPORT