Kconfig: mtd: restyle

Restyle all Kconfigs for "mtd":
Menu entries   : no space left
Menu attributes: 1 TAB
Help text      : 1 TAB + 2 spaces
Replace '---help---' by 'help'

Signed-off-by: Johan Jonker <[email protected]>
[trini: Add missing indentation on a few more multi-paragraph help texts]
Signed-off-by: Tom Rini <[email protected]>

4 files changed, 58 insertions, 58 deletions

diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig
index 21b8b21f6b2..38d6dd142dd 100644
--- a/drivers/mtd/Kconfig
+++ b/drivers/mtd/Kconfig
@@ -205,16 +205,16 @@ config HBMC_AM654
 	bool "HyperBus controller driver for AM65x SoC"
 	depends on MULTIPLEXER && (MUX_MMIO || SPL_MUX_MMIO)
 	help
-	 This is the driver for HyperBus controller on TI's AM65x and
-	 other SoCs
+	  This is the driver for HyperBus controller on TI's AM65x and
+	  other SoCs
 
 config STM32_FLASH
 	bool "STM32 MCU Flash driver"
 	depends on ARCH_STM32
 	select USE_SYS_MAX_FLASH_BANKS
 	help
-	 This is the driver of embedded flash for some STMicroelectronics
-	 STM32 MCU.
+	  This is the driver of embedded flash for some STMicroelectronics
+	  STM32 MCU.
 
 config SYS_MAX_FLASH_SECT
 	int "Maximum number of sectors on a flash chip"
@@ -236,17 +236,17 @@ config SYS_MAX_FLASH_BANKS
 	depends on USE_SYS_MAX_FLASH_BANKS
 	default 1
 	help
-	 Max number of Flash memory banks using by the MTD framework, in the
-	 flash CFI driver and in some other driver to define the flash_info
-	 struct declaration.
+	  Max number of Flash memory banks using by the MTD framework, in the
+	  flash CFI driver and in some other driver to define the flash_info
+	  struct declaration.
 
 config SYS_MAX_FLASH_BANKS_DETECT
 	bool "Detection of flash banks number in CFI driver"
 	depends on CFI_FLASH && FLASH_CFI_DRIVER
 	help
-	 This enables detection of number of flash banks in CFI driver,
-	 to reduce the effective number of flash bank, between 0 and
-	 CONFIG_SYS_MAX_FLASH_BANKS
+	  This enables detection of number of flash banks in CFI driver,
+	  to reduce the effective number of flash bank, between 0 and
+	  CONFIG_SYS_MAX_FLASH_BANKS
 
 source "drivers/mtd/nand/Kconfig"
 
diff --git a/drivers/mtd/nand/raw/Kconfig b/drivers/mtd/nand/raw/Kconfig
index 2999e6b1710..b5dfad7380f 100644
--- a/drivers/mtd/nand/raw/Kconfig
+++ b/drivers/mtd/nand/raw/Kconfig
@@ -310,47 +310,47 @@ choice
 	prompt "ECC scheme"
 	default NAND_OMAP_ECCSCHEME_BCH8_CODE_HW
 	help
-	On OMAP platforms, this CONFIG specifies NAND ECC scheme.
-	It can take following values:
-	OMAP_ECC_HAM1_CODE_SW
+	  On OMAP platforms, this CONFIG specifies NAND ECC scheme.
+	  It can take following values:
+	  OMAP_ECC_HAM1_CODE_SW
 		1-bit Hamming code using software lib.
 		(for legacy devices only)
-	OMAP_ECC_HAM1_CODE_HW
+	  OMAP_ECC_HAM1_CODE_HW
 		1-bit Hamming code using GPMC hardware.
 		(for legacy devices only)
-	OMAP_ECC_BCH4_CODE_HW_DETECTION_SW
+	  OMAP_ECC_BCH4_CODE_HW_DETECTION_SW
 		4-bit BCH code (unsupported)
-	OMAP_ECC_BCH4_CODE_HW
+	  OMAP_ECC_BCH4_CODE_HW
 		4-bit BCH code (unsupported)
-	OMAP_ECC_BCH8_CODE_HW_DETECTION_SW
+	  OMAP_ECC_BCH8_CODE_HW_DETECTION_SW
 		8-bit BCH code with
 		- ecc calculation using GPMC hardware engine,
 		- error detection using software library.
 		- requires CONFIG_BCH to enable software BCH library
 		(For legacy device which do not have ELM h/w engine)
-	OMAP_ECC_BCH8_CODE_HW
+	  OMAP_ECC_BCH8_CODE_HW
 		8-bit BCH code with
 		- ecc calculation using GPMC hardware engine,
 		- error detection using ELM hardware engine.
-	OMAP_ECC_BCH16_CODE_HW
+	  OMAP_ECC_BCH16_CODE_HW
 		16-bit BCH code with
 		- ecc calculation using GPMC hardware engine,
 		- error detection using ELM hardware engine.
 
-	How to select ECC scheme on OMAP and AMxx platforms ?
-	-----------------------------------------------------
-	Though higher ECC schemes have more capability to detect and correct
-	bit-flips, but still selection of ECC scheme is dependent on following
-	- hardware engines present in SoC.
+	  How to select ECC scheme on OMAP and AMxx platforms ?
+	  -----------------------------------------------------
+	  Though higher ECC schemes have more capability to detect and correct
+	  bit-flips, but still selection of ECC scheme is dependent on following
+	  - hardware engines present in SoC.
 		Some legacy OMAP SoC do not have ELM h/w engine thus such
 		SoC cannot support BCHx_HW ECC schemes.
-	- size of OOB/Spare region
+	  - size of OOB/Spare region
 		With higher ECC schemes, more OOB/Spare area is required to
 		store ECC. So choice of ECC scheme is limited by NAND oobsize.
 
-	In general following expression can help:
+	  In general following expression can help:
 		NAND_OOBSIZE >= 2 + (NAND_PAGESIZE / 512) * ECC_BYTES
-	where
+	  where
 		NAND_OOBSIZE	= number of bytes available in
 				OOB/spare area per NAND page.
 		NAND_PAGESIZE	= bytes in main-area of NAND page.
diff --git a/drivers/mtd/spi/Kconfig b/drivers/mtd/spi/Kconfig
index de78a6cb707..4ff58380b59 100644
--- a/drivers/mtd/spi/Kconfig
+++ b/drivers/mtd/spi/Kconfig
@@ -94,39 +94,39 @@ config SPI_FLASH_SFDP_SUPPORT
 	bool "SFDP table parsing support for SPI NOR flashes"
 	depends on !SPI_FLASH_BAR
 	help
-	 Enable support for parsing and auto discovery of parameters for
-	 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
-	 tables as per JESD216 standard.
+	  Enable support for parsing and auto discovery of parameters for
+	  SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
+	  tables as per JESD216 standard.
 
 config SPI_FLASH_SMART_HWCAPS
 	bool "Smart hardware capability detection based on SPI MEM supports_op() hook"
 	default y
 	help
-	 Enable support for smart hardware capability detection based on SPI
-	 MEM supports_op() hook that lets controllers express whether they
-	 can support a type of operation in a much more refined way compared
-	 to using flags like SPI_RX_DUAL, SPI_TX_QUAD, etc.
+	  Enable support for smart hardware capability detection based on SPI
+	  MEM supports_op() hook that lets controllers express whether they
+	  can support a type of operation in a much more refined way compared
+	  to using flags like SPI_RX_DUAL, SPI_TX_QUAD, etc.
 
 config SPI_NOR_BOOT_SOFT_RESET_EXT_INVERT
 	bool "Command extension type is INVERT for Software Reset on boot"
 	help
-	 Because of SFDP information can not be get before boot.
-	 So define command extension type is INVERT when Software Reset on boot only.
+	  Because of SFDP information can not be get before boot.
+	  So define command extension type is INVERT when Software Reset on boot only.
 
 config SPI_FLASH_SOFT_RESET
 	bool "Software Reset support for SPI NOR flashes"
 	help
-	 Enable support for xSPI Software Reset. It will be used to switch from
-	 Octal DTR mode to legacy mode on shutdown and boot (if enabled).
+	  Enable support for xSPI Software Reset. It will be used to switch from
+	  Octal DTR mode to legacy mode on shutdown and boot (if enabled).
 
 config SPI_FLASH_SOFT_RESET_ON_BOOT
 	bool "Perform a Software Reset on boot on flashes that boot in stateful mode"
 	depends on SPI_FLASH_SOFT_RESET
 	help
-	 Perform a Software Reset on boot to allow detecting flashes that are
-	 handed to us in Octal DTR mode. Do not enable this config on flashes
-	 that are not supposed to be handed to U-Boot in Octal DTR mode, even
-	 if they _do_ support the Soft Reset sequence.
+	  Perform a Software Reset on boot to allow detecting flashes that are
+	  handed to us in Octal DTR mode. Do not enable this config on flashes
+	  that are not supposed to be handed to U-Boot in Octal DTR mode, even
+	  if they _do_ support the Soft Reset sequence.
 
 config SPI_FLASH_BAR
 	bool "SPI flash Bank/Extended address register support"
@@ -139,18 +139,18 @@ config SPI_FLASH_LOCK
 	bool "Enable the Locking feature"
 	default y
 	help
-	 Enable the SPI flash lock support. By default this is set to y.
-	 If you intend not to use the lock support you should say n here.
+	  Enable the SPI flash lock support. By default this is set to y.
+	  If you intend not to use the lock support you should say n here.
 
 config SPI_FLASH_UNLOCK_ALL
 	bool "Unlock the entire SPI flash on u-boot startup"
 	default y
 	help
-	 Some flashes tend to power up with the software write protection
-	 bits set. If this option is set, the whole flash will be unlocked.
+	  Some flashes tend to power up with the software write protection
+	  bits set. If this option is set, the whole flash will be unlocked.
 
-	 For legacy reasons, this option default to y. But if you intend to
-	 actually use the software protection bits you should say n here.
+	  For legacy reasons, this option default to y. But if you intend to
+	  actually use the software protection bits you should say n here.
 
 config SPI_FLASH_ATMEL
 	bool "Atmel SPI flash support"
@@ -201,9 +201,9 @@ config SPI_FLASH_S28HX_T
 	bool "Cypress SEMPER Octal (S28) chip support"
 	depends on SPI_FLASH_SPANSION
 	help
-	 Add support for the Cypress S28HL-T and S28HS-T chip. This is a separate
-	 config because the fixup hooks for this flash add extra size overhead.
-	 Boards that don't use the flash can disable this to save space.
+	  Add support for the Cypress S28HL-T and S28HS-T chip. This is a separate
+	  config because the fixup hooks for this flash add extra size overhead.
+	  Boards that don't use the flash can disable this to save space.
 
 config SPI_FLASH_STMICRO
 	bool "STMicro SPI flash support"
@@ -214,9 +214,9 @@ config SPI_FLASH_MT35XU
 	bool "Micron MT35XU chip support"
 	depends on SPI_FLASH_STMICRO
 	help
-	 Add support for the Micron MT35XU chip. This is a separate config
-	 because the fixup hooks for this flash add extra size overhead. Boards
-	 that don't use the flash can disable this to save space.
+	  Add support for the Micron MT35XU chip. This is a separate config
+	  because the fixup hooks for this flash add extra size overhead. Boards
+	  that don't use the flash can disable this to save space.
 
 config SPI_FLASH_SST
 	bool "SST SPI flash support"
@@ -282,7 +282,7 @@ config SPI_FLASH_MTD
 	bool "SPI Flash MTD support"
 	depends on SPI_FLASH && MTD
 	help
-          Enable the MTD support for spi flash layer, this adapter is for
+	  Enable the MTD support for spi flash layer, this adapter is for
 	  translating mtd_read/mtd_write commands into spi_flash_read/write
 	  commands. It is not intended to use it within sf_cmd or the SPI
 	  flash subsystem. Such an adapter is needed for subsystems like
@@ -294,7 +294,7 @@ config SPL_SPI_FLASH_MTD
 	bool "SPI flash MTD support for SPL"
 	depends on SPI_FLASH && SPL
 	help
-          Enable the MTD support for the SPI flash layer in SPL.
+	  Enable the MTD support for the SPI flash layer in SPL.
 
 	  If unsure, say N
 
diff --git a/drivers/mtd/ubi/Kconfig b/drivers/mtd/ubi/Kconfig
index ba77c034736..e523a4c4707 100644
--- a/drivers/mtd/ubi/Kconfig
+++ b/drivers/mtd/ubi/Kconfig
@@ -82,8 +82,8 @@ config MTD_UBI_BEB_LIMIT
 config MTD_UBI_FASTMAP
 	bool "UBI Fastmap (Experimental feature)"
 	help
-	   Important: this feature is experimental so far and the on-flash
-	   format for fastmap may change in the next kernel versions
+	  Important: this feature is experimental so far and the on-flash
+	  format for fastmap may change in the next kernel versions
 
 	   Fastmap is a mechanism which allows attaching an UBI device
 	   in nearly constant time. Instead of scanning the whole MTD device it