mtd: Make Kconfig formatting consistent
Fix indentation and replace '---help---' by 'help' to make things consistent. Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com> Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
This commit is contained in:
parent
6c6bc9ea84
commit
a8222a84ce
|
@ -24,7 +24,7 @@ config MTD_TESTS
|
|||
|
||||
config MTD_REDBOOT_PARTS
|
||||
tristate "RedBoot partition table parsing"
|
||||
---help---
|
||||
help
|
||||
RedBoot is a ROM monitor and bootloader which deals with multiple
|
||||
'images' in flash devices by putting a table one of the erase
|
||||
blocks on the device, similar to a partition table, which gives
|
||||
|
@ -45,7 +45,7 @@ if MTD_REDBOOT_PARTS
|
|||
config MTD_REDBOOT_DIRECTORY_BLOCK
|
||||
int "Location of RedBoot partition table"
|
||||
default "-1"
|
||||
---help---
|
||||
help
|
||||
This option is the Linux counterpart to the
|
||||
CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time
|
||||
option.
|
||||
|
@ -75,7 +75,7 @@ endif # MTD_REDBOOT_PARTS
|
|||
config MTD_CMDLINE_PARTS
|
||||
tristate "Command line partition table parsing"
|
||||
depends on MTD
|
||||
---help---
|
||||
help
|
||||
Allow generic configuration of the MTD partition tables via the kernel
|
||||
command line. Multiple flash resources are supported for hardware where
|
||||
different kinds of flash memory are available.
|
||||
|
@ -112,7 +112,7 @@ config MTD_CMDLINE_PARTS
|
|||
config MTD_AFS_PARTS
|
||||
tristate "ARM Firmware Suite partition parsing"
|
||||
depends on (ARM || ARM64)
|
||||
---help---
|
||||
help
|
||||
The ARM Firmware Suite allows the user to divide flash devices into
|
||||
multiple 'images'. Each such image has a header containing its name
|
||||
and offset/size etc.
|
||||
|
@ -136,7 +136,7 @@ config MTD_OF_PARTS
|
|||
|
||||
config MTD_AR7_PARTS
|
||||
tristate "TI AR7 partitioning support"
|
||||
---help---
|
||||
help
|
||||
TI AR7 partitioning support
|
||||
|
||||
config MTD_BCM63XX_PARTS
|
||||
|
@ -170,7 +170,7 @@ config MTD_BLOCK
|
|||
tristate "Caching block device access to MTD devices"
|
||||
depends on BLOCK
|
||||
select MTD_BLKDEVS
|
||||
---help---
|
||||
help
|
||||
Although most flash chips have an erase size too large to be useful
|
||||
as block devices, it is possible to use MTD devices which are based
|
||||
on RAM chips in this manner. This block device is a user of MTD
|
||||
|
@ -205,7 +205,7 @@ config FTL
|
|||
tristate "FTL (Flash Translation Layer) support"
|
||||
depends on BLOCK
|
||||
select MTD_BLKDEVS
|
||||
---help---
|
||||
help
|
||||
This provides support for the original Flash Translation Layer which
|
||||
is part of the PCMCIA specification. It uses a kind of pseudo-
|
||||
file system on a flash device to emulate a block device with
|
||||
|
@ -222,7 +222,7 @@ config NFTL
|
|||
tristate "NFTL (NAND Flash Translation Layer) support"
|
||||
depends on BLOCK
|
||||
select MTD_BLKDEVS
|
||||
---help---
|
||||
help
|
||||
This provides support for the NAND Flash Translation Layer which is
|
||||
used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
|
||||
file system on a flash device to emulate a block device with
|
||||
|
@ -246,7 +246,7 @@ config INFTL
|
|||
tristate "INFTL (Inverse NAND Flash Translation Layer) support"
|
||||
depends on BLOCK
|
||||
select MTD_BLKDEVS
|
||||
---help---
|
||||
help
|
||||
This provides support for the Inverse NAND Flash Translation
|
||||
Layer which is used on M-Systems' newer DiskOnChip devices. It
|
||||
uses a kind of pseudo-file system on a flash device to emulate
|
||||
|
@ -261,10 +261,10 @@ config INFTL
|
|||
not use it.
|
||||
|
||||
config RFD_FTL
|
||||
tristate "Resident Flash Disk (Flash Translation Layer) support"
|
||||
tristate "Resident Flash Disk (Flash Translation Layer) support"
|
||||
depends on BLOCK
|
||||
select MTD_BLKDEVS
|
||||
---help---
|
||||
help
|
||||
This provides support for the flash translation layer known
|
||||
as the Resident Flash Disk (RFD), as used by the Embedded BIOS
|
||||
of General Software. There is a blurb at:
|
||||
|
@ -308,7 +308,7 @@ config MTD_SWAP
|
|||
select MTD_BLKDEVS
|
||||
help
|
||||
Provides volatile block device driver on top of mtd partition
|
||||
suitable for swapping. The mapping of written blocks is not saved.
|
||||
suitable for swapping. The mapping of written blocks is not saved.
|
||||
The driver provides wear leveling by storing erase counter into the
|
||||
OOB.
|
||||
|
||||
|
|
|
@ -44,7 +44,7 @@ choice
|
|||
prompt "Flash cmd/query data swapping"
|
||||
depends on MTD_CFI_ADV_OPTIONS
|
||||
default MTD_CFI_NOSWAP
|
||||
---help---
|
||||
help
|
||||
This option defines the way in which the CPU attempts to arrange
|
||||
data bits when writing the 'magic' commands to the chips. Saying
|
||||
'NO', which is the default when CONFIG_MTD_CFI_ADV_OPTIONS isn't
|
||||
|
|
|
@ -5,7 +5,7 @@ menu "Self-contained MTD device drivers"
|
|||
config MTD_PMC551
|
||||
tristate "Ramix PMC551 PCI Mezzanine RAM card support"
|
||||
depends on PCI
|
||||
---help---
|
||||
help
|
||||
This provides a MTD device driver for the Ramix PMC551 RAM PCI card
|
||||
from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
|
||||
These devices come in memory configurations from 32M - 1G. If you
|
||||
|
@ -209,7 +209,7 @@ config MTD_DOCG3
|
|||
select BCH
|
||||
select BCH_CONST_PARAMS
|
||||
select BITREVERSE
|
||||
---help---
|
||||
help
|
||||
This provides an MTD device driver for the M-Systems DiskOnChip
|
||||
G3 devices.
|
||||
|
||||
|
|
|
@ -13,10 +13,10 @@ config MTD_QINFO_PROBE
|
|||
depends on MTD_LPDDR
|
||||
tristate "Detect flash chips by QINFO probe"
|
||||
help
|
||||
Device Information for LPDDR chips is offered through the Overlay
|
||||
Window QINFO interface, permits software to be used for entire
|
||||
families of devices. This serves similar purpose of CFI on legacy
|
||||
Flash products
|
||||
Device Information for LPDDR chips is offered through the Overlay
|
||||
Window QINFO interface, permits software to be used for entire
|
||||
families of devices. This serves similar purpose of CFI on legacy
|
||||
Flash products
|
||||
|
||||
config MTD_LPDDR2_NVM
|
||||
# ARM dependency is only for writel_relaxed()
|
||||
|
|
|
@ -207,13 +207,13 @@ config MTD_ICHXROM
|
|||
BE VERY CAREFUL.
|
||||
|
||||
config MTD_ESB2ROM
|
||||
tristate "BIOS flash chip on Intel ESB Controller Hub 2"
|
||||
depends on X86 && MTD_JEDECPROBE && PCI
|
||||
help
|
||||
Support for treating the BIOS flash chip on ESB2 motherboards
|
||||
as an MTD device - with this you can reprogram your BIOS.
|
||||
tristate "BIOS flash chip on Intel ESB Controller Hub 2"
|
||||
depends on X86 && MTD_JEDECPROBE && PCI
|
||||
help
|
||||
Support for treating the BIOS flash chip on ESB2 motherboards
|
||||
as an MTD device - with this you can reprogram your BIOS.
|
||||
|
||||
BE VERY CAREFUL.
|
||||
BE VERY CAREFUL.
|
||||
|
||||
config MTD_CK804XROM
|
||||
tristate "BIOS flash chip on Nvidia CK804"
|
||||
|
@ -401,12 +401,12 @@ config MTD_PISMO
|
|||
When built as a module, it will be called pismo.ko
|
||||
|
||||
config MTD_LATCH_ADDR
|
||||
tristate "Latch-assisted Flash Chip Support"
|
||||
depends on MTD_COMPLEX_MAPPINGS
|
||||
help
|
||||
Map driver which allows flashes to be partially physically addressed
|
||||
and have the upper address lines set by a board specific code.
|
||||
tristate "Latch-assisted Flash Chip Support"
|
||||
depends on MTD_COMPLEX_MAPPINGS
|
||||
help
|
||||
Map driver which allows flashes to be partially physically addressed
|
||||
and have the upper address lines set by a board specific code.
|
||||
|
||||
If compiled as a module, it will be called latch-addr-flash.
|
||||
If compiled as a module, it will be called latch-addr-flash.
|
||||
|
||||
endmenu
|
||||
|
|
Loading…
Reference in New Issue