Commit 2cd0ee3b authored by Enrico Weigelt, metux IT consult's avatar Enrico Weigelt, metux IT consult Committed by Lee Jones

mfd: Kconfig: Pedantic formatting

Formatting of Kconfig files doesn't look so pretty, so let the
Great White Handkerchief come around and clean it up.
Signed-off-by: default avatarEnrico Weigelt, metux IT consult <info@metux.net>
Signed-off-by: default avatarLee Jones <lee.jones@linaro.org>
parent 129fc677
...@@ -16,7 +16,7 @@ config MFD_CS5535 ...@@ -16,7 +16,7 @@ config MFD_CS5535
depends on PCI && (X86_32 || (X86 && COMPILE_TEST)) depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
---help--- ---help---
This is the core driver for CS5535/CS5536 MFD functions. This is This is the core driver for CS5535/CS5536 MFD functions. This is
necessary for using the board's GPIO and MFGPT functionality. necessary for using the board's GPIO and MFGPT functionality.
config MFD_ALTERA_A10SR config MFD_ALTERA_A10SR
bool "Altera Arria10 DevKit System Resource chip" bool "Altera Arria10 DevKit System Resource chip"
...@@ -223,13 +223,13 @@ config MFD_CROS_EC ...@@ -223,13 +223,13 @@ config MFD_CROS_EC
protocol for talking to the EC is defined by the bus driver. protocol for talking to the EC is defined by the bus driver.
config MFD_CROS_EC_CHARDEV config MFD_CROS_EC_CHARDEV
tristate "Chrome OS Embedded Controller userspace device interface" tristate "Chrome OS Embedded Controller userspace device interface"
depends on MFD_CROS_EC depends on MFD_CROS_EC
---help--- ---help---
This driver adds support to talk with the ChromeOS EC from userspace. This driver adds support to talk with the ChromeOS EC from userspace.
If you have a supported Chromebook, choose Y or M here. If you have a supported Chromebook, choose Y or M here.
The module will be called cros_ec_dev. The module will be called cros_ec_dev.
config MFD_MADERA config MFD_MADERA
tristate "Cirrus Logic Madera codecs" tristate "Cirrus Logic Madera codecs"
...@@ -891,7 +891,7 @@ config MFD_CPCAP ...@@ -891,7 +891,7 @@ config MFD_CPCAP
At least Motorola Droid 4 is known to use CPCAP. At least Motorola Droid 4 is known to use CPCAP.
config MFD_VIPERBOARD config MFD_VIPERBOARD
tristate "Nano River Technologies Viperboard" tristate "Nano River Technologies Viperboard"
select MFD_CORE select MFD_CORE
depends on USB depends on USB
default n default n
...@@ -927,15 +927,15 @@ config PCF50633_ADC ...@@ -927,15 +927,15 @@ config PCF50633_ADC
tristate "NXP PCF50633 ADC" tristate "NXP PCF50633 ADC"
depends on MFD_PCF50633 depends on MFD_PCF50633
help help
Say yes here if you want to include support for ADC in the Say yes here if you want to include support for ADC in the
NXP PCF50633 chip. NXP PCF50633 chip.
config PCF50633_GPIO config PCF50633_GPIO
tristate "NXP PCF50633 GPIO" tristate "NXP PCF50633 GPIO"
depends on MFD_PCF50633 depends on MFD_PCF50633
help help
Say yes here if you want to include support GPIO for pins on Say yes here if you want to include support GPIO for pins on
the PCF50633 chip. the PCF50633 chip.
config UCB1400_CORE config UCB1400_CORE
tristate "Philips UCB1400 Core driver" tristate "Philips UCB1400 Core driver"
...@@ -1050,7 +1050,7 @@ config MFD_RN5T618 ...@@ -1050,7 +1050,7 @@ config MFD_RN5T618
select REGMAP_I2C select REGMAP_I2C
help help
Say yes here to add support for the Ricoh RN5T567, Say yes here to add support for the Ricoh RN5T567,
RN5T618, RC5T619 PMIC. RN5T618, RC5T619 PMIC.
This driver provides common support for accessing the device, This driver provides common support for accessing the device,
additional drivers must be enabled in order to use the additional drivers must be enabled in order to use the
functionality of the device. functionality of the device.
...@@ -1103,9 +1103,9 @@ config MFD_SM501_GPIO ...@@ -1103,9 +1103,9 @@ config MFD_SM501_GPIO
bool "Export GPIO via GPIO layer" bool "Export GPIO via GPIO layer"
depends on MFD_SM501 && GPIOLIB depends on MFD_SM501 && GPIOLIB
---help--- ---help---
This option uses the gpio library layer to export the 64 GPIO This option uses the gpio library layer to export the 64 GPIO
lines on the SM501. The platform data is used to supply the lines on the SM501. The platform data is used to supply the
base number for the first GPIO line to register. base number for the first GPIO line to register.
config MFD_SKY81452 config MFD_SKY81452
tristate "Skyworks Solutions SKY81452" tristate "Skyworks Solutions SKY81452"
...@@ -1120,16 +1120,16 @@ config MFD_SKY81452 ...@@ -1120,16 +1120,16 @@ config MFD_SKY81452
will be called sky81452. will be called sky81452.
config MFD_SMSC config MFD_SMSC
bool "SMSC ECE1099 series chips" bool "SMSC ECE1099 series chips"
depends on I2C=y depends on I2C=y
select MFD_CORE select MFD_CORE
select REGMAP_I2C select REGMAP_I2C
help help
If you say yes here you get support for the If you say yes here you get support for the
ece1099 chips from SMSC. ece1099 chips from SMSC.
To compile this driver as a module, choose M here: the To compile this driver as a module, choose M here: the
module will be called smsc. module will be called smsc.
config MFD_SC27XX_PMIC config MFD_SC27XX_PMIC
tristate "Spreadtrum SC27xx PMICs" tristate "Spreadtrum SC27xx PMICs"
...@@ -1195,12 +1195,12 @@ config AB8500_CORE ...@@ -1195,12 +1195,12 @@ config AB8500_CORE
This chip embeds various other multimedia funtionalities as well. This chip embeds various other multimedia funtionalities as well.
config AB8500_DEBUG config AB8500_DEBUG
bool "Enable debug info via debugfs" bool "Enable debug info via debugfs"
depends on AB8500_GPADC && DEBUG_FS depends on AB8500_GPADC && DEBUG_FS
default y if DEBUG_FS default y if DEBUG_FS
help help
Select this option if you want debug information using the debug Select this option if you want debug information using the debug
filesystem, debugfs. filesystem, debugfs.
config AB8500_GPADC config AB8500_GPADC
bool "ST-Ericsson AB8500 GPADC driver" bool "ST-Ericsson AB8500 GPADC driver"
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment