diff options
author | Boris Brezillon <boris.brezillon@bootlin.com> | 2018-07-18 11:09:52 -0400 |
---|---|---|
committer | Boris Brezillon <boris.brezillon@bootlin.com> | 2018-07-19 17:12:06 -0400 |
commit | a8222a84cefa9d3595a14cf076bc8c09287bf16c (patch) | |
tree | 65e93d2d710f3edbbb7d0e089629185a7fd6dcd2 | |
parent | 6c6bc9ea84d0008024606bf5ba10519e20d851bf (diff) |
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>
-rw-r--r-- | drivers/mtd/Kconfig | 24 | ||||
-rw-r--r-- | drivers/mtd/chips/Kconfig | 2 | ||||
-rw-r--r-- | drivers/mtd/devices/Kconfig | 4 | ||||
-rw-r--r-- | drivers/mtd/lpddr/Kconfig | 8 | ||||
-rw-r--r-- | drivers/mtd/maps/Kconfig | 24 |
5 files changed, 31 insertions, 31 deletions
diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig index 46ab7feec6b6..c77f537323ec 100644 --- a/drivers/mtd/Kconfig +++ b/drivers/mtd/Kconfig | |||
@@ -24,7 +24,7 @@ config MTD_TESTS | |||
24 | 24 | ||
25 | config MTD_REDBOOT_PARTS | 25 | config MTD_REDBOOT_PARTS |
26 | tristate "RedBoot partition table parsing" | 26 | tristate "RedBoot partition table parsing" |
27 | ---help--- | 27 | help |
28 | RedBoot is a ROM monitor and bootloader which deals with multiple | 28 | RedBoot is a ROM monitor and bootloader which deals with multiple |
29 | 'images' in flash devices by putting a table one of the erase | 29 | 'images' in flash devices by putting a table one of the erase |
30 | blocks on the device, similar to a partition table, which gives | 30 | blocks on the device, similar to a partition table, which gives |
@@ -45,7 +45,7 @@ if MTD_REDBOOT_PARTS | |||
45 | config MTD_REDBOOT_DIRECTORY_BLOCK | 45 | config MTD_REDBOOT_DIRECTORY_BLOCK |
46 | int "Location of RedBoot partition table" | 46 | int "Location of RedBoot partition table" |
47 | default "-1" | 47 | default "-1" |
48 | ---help--- | 48 | help |
49 | This option is the Linux counterpart to the | 49 | This option is the Linux counterpart to the |
50 | CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time | 50 | CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time |
51 | option. | 51 | option. |
@@ -75,7 +75,7 @@ endif # MTD_REDBOOT_PARTS | |||
75 | config MTD_CMDLINE_PARTS | 75 | config MTD_CMDLINE_PARTS |
76 | tristate "Command line partition table parsing" | 76 | tristate "Command line partition table parsing" |
77 | depends on MTD | 77 | depends on MTD |
78 | ---help--- | 78 | help |
79 | Allow generic configuration of the MTD partition tables via the kernel | 79 | Allow generic configuration of the MTD partition tables via the kernel |
80 | command line. Multiple flash resources are supported for hardware where | 80 | command line. Multiple flash resources are supported for hardware where |
81 | different kinds of flash memory are available. | 81 | different kinds of flash memory are available. |
@@ -112,7 +112,7 @@ config MTD_CMDLINE_PARTS | |||
112 | config MTD_AFS_PARTS | 112 | config MTD_AFS_PARTS |
113 | tristate "ARM Firmware Suite partition parsing" | 113 | tristate "ARM Firmware Suite partition parsing" |
114 | depends on (ARM || ARM64) | 114 | depends on (ARM || ARM64) |
115 | ---help--- | 115 | help |
116 | The ARM Firmware Suite allows the user to divide flash devices into | 116 | The ARM Firmware Suite allows the user to divide flash devices into |
117 | multiple 'images'. Each such image has a header containing its name | 117 | multiple 'images'. Each such image has a header containing its name |
118 | and offset/size etc. | 118 | and offset/size etc. |
@@ -136,7 +136,7 @@ config MTD_OF_PARTS | |||
136 | 136 | ||
137 | config MTD_AR7_PARTS | 137 | config MTD_AR7_PARTS |
138 | tristate "TI AR7 partitioning support" | 138 | tristate "TI AR7 partitioning support" |
139 | ---help--- | 139 | help |
140 | TI AR7 partitioning support | 140 | TI AR7 partitioning support |
141 | 141 | ||
142 | config MTD_BCM63XX_PARTS | 142 | config MTD_BCM63XX_PARTS |
@@ -170,7 +170,7 @@ config MTD_BLOCK | |||
170 | tristate "Caching block device access to MTD devices" | 170 | tristate "Caching block device access to MTD devices" |
171 | depends on BLOCK | 171 | depends on BLOCK |
172 | select MTD_BLKDEVS | 172 | select MTD_BLKDEVS |
173 | ---help--- | 173 | help |
174 | Although most flash chips have an erase size too large to be useful | 174 | Although most flash chips have an erase size too large to be useful |
175 | as block devices, it is possible to use MTD devices which are based | 175 | as block devices, it is possible to use MTD devices which are based |
176 | on RAM chips in this manner. This block device is a user of MTD | 176 | on RAM chips in this manner. This block device is a user of MTD |
@@ -205,7 +205,7 @@ config FTL | |||
205 | tristate "FTL (Flash Translation Layer) support" | 205 | tristate "FTL (Flash Translation Layer) support" |
206 | depends on BLOCK | 206 | depends on BLOCK |
207 | select MTD_BLKDEVS | 207 | select MTD_BLKDEVS |
208 | ---help--- | 208 | help |
209 | This provides support for the original Flash Translation Layer which | 209 | This provides support for the original Flash Translation Layer which |
210 | is part of the PCMCIA specification. It uses a kind of pseudo- | 210 | is part of the PCMCIA specification. It uses a kind of pseudo- |
211 | file system on a flash device to emulate a block device with | 211 | file system on a flash device to emulate a block device with |
@@ -222,7 +222,7 @@ config NFTL | |||
222 | tristate "NFTL (NAND Flash Translation Layer) support" | 222 | tristate "NFTL (NAND Flash Translation Layer) support" |
223 | depends on BLOCK | 223 | depends on BLOCK |
224 | select MTD_BLKDEVS | 224 | select MTD_BLKDEVS |
225 | ---help--- | 225 | help |
226 | This provides support for the NAND Flash Translation Layer which is | 226 | This provides support for the NAND Flash Translation Layer which is |
227 | used on M-Systems' DiskOnChip devices. It uses a kind of pseudo- | 227 | used on M-Systems' DiskOnChip devices. It uses a kind of pseudo- |
228 | file system on a flash device to emulate a block device with | 228 | file system on a flash device to emulate a block device with |
@@ -246,7 +246,7 @@ config INFTL | |||
246 | tristate "INFTL (Inverse NAND Flash Translation Layer) support" | 246 | tristate "INFTL (Inverse NAND Flash Translation Layer) support" |
247 | depends on BLOCK | 247 | depends on BLOCK |
248 | select MTD_BLKDEVS | 248 | select MTD_BLKDEVS |
249 | ---help--- | 249 | help |
250 | This provides support for the Inverse NAND Flash Translation | 250 | This provides support for the Inverse NAND Flash Translation |
251 | Layer which is used on M-Systems' newer DiskOnChip devices. It | 251 | Layer which is used on M-Systems' newer DiskOnChip devices. It |
252 | uses a kind of pseudo-file system on a flash device to emulate | 252 | uses a kind of pseudo-file system on a flash device to emulate |
@@ -261,10 +261,10 @@ config INFTL | |||
261 | not use it. | 261 | not use it. |
262 | 262 | ||
263 | config RFD_FTL | 263 | config RFD_FTL |
264 | tristate "Resident Flash Disk (Flash Translation Layer) support" | 264 | tristate "Resident Flash Disk (Flash Translation Layer) support" |
265 | depends on BLOCK | 265 | depends on BLOCK |
266 | select MTD_BLKDEVS | 266 | select MTD_BLKDEVS |
267 | ---help--- | 267 | help |
268 | This provides support for the flash translation layer known | 268 | This provides support for the flash translation layer known |
269 | as the Resident Flash Disk (RFD), as used by the Embedded BIOS | 269 | as the Resident Flash Disk (RFD), as used by the Embedded BIOS |
270 | of General Software. There is a blurb at: | 270 | of General Software. There is a blurb at: |
@@ -308,7 +308,7 @@ config MTD_SWAP | |||
308 | select MTD_BLKDEVS | 308 | select MTD_BLKDEVS |
309 | help | 309 | help |
310 | Provides volatile block device driver on top of mtd partition | 310 | Provides volatile block device driver on top of mtd partition |
311 | suitable for swapping. The mapping of written blocks is not saved. | 311 | suitable for swapping. The mapping of written blocks is not saved. |
312 | The driver provides wear leveling by storing erase counter into the | 312 | The driver provides wear leveling by storing erase counter into the |
313 | OOB. | 313 | OOB. |
314 | 314 | ||
diff --git a/drivers/mtd/chips/Kconfig b/drivers/mtd/chips/Kconfig index bbfa1f129266..39ec32a29051 100644 --- a/drivers/mtd/chips/Kconfig +++ b/drivers/mtd/chips/Kconfig | |||
@@ -44,7 +44,7 @@ choice | |||
44 | prompt "Flash cmd/query data swapping" | 44 | prompt "Flash cmd/query data swapping" |
45 | depends on MTD_CFI_ADV_OPTIONS | 45 | depends on MTD_CFI_ADV_OPTIONS |
46 | default MTD_CFI_NOSWAP | 46 | default MTD_CFI_NOSWAP |
47 | ---help--- | 47 | help |
48 | This option defines the way in which the CPU attempts to arrange | 48 | This option defines the way in which the CPU attempts to arrange |
49 | data bits when writing the 'magic' commands to the chips. Saying | 49 | data bits when writing the 'magic' commands to the chips. Saying |
50 | 'NO', which is the default when CONFIG_MTD_CFI_ADV_OPTIONS isn't | 50 | 'NO', which is the default when CONFIG_MTD_CFI_ADV_OPTIONS isn't |
diff --git a/drivers/mtd/devices/Kconfig b/drivers/mtd/devices/Kconfig index 57b02c4b3f63..e514d57a0419 100644 --- a/drivers/mtd/devices/Kconfig +++ b/drivers/mtd/devices/Kconfig | |||
@@ -5,7 +5,7 @@ menu "Self-contained MTD device drivers" | |||
5 | config MTD_PMC551 | 5 | config MTD_PMC551 |
6 | tristate "Ramix PMC551 PCI Mezzanine RAM card support" | 6 | tristate "Ramix PMC551 PCI Mezzanine RAM card support" |
7 | depends on PCI | 7 | depends on PCI |
8 | ---help--- | 8 | help |
9 | This provides a MTD device driver for the Ramix PMC551 RAM PCI card | 9 | This provides a MTD device driver for the Ramix PMC551 RAM PCI card |
10 | from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>. | 10 | from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>. |
11 | These devices come in memory configurations from 32M - 1G. If you | 11 | These devices come in memory configurations from 32M - 1G. If you |
@@ -209,7 +209,7 @@ config MTD_DOCG3 | |||
209 | select BCH | 209 | select BCH |
210 | select BCH_CONST_PARAMS | 210 | select BCH_CONST_PARAMS |
211 | select BITREVERSE | 211 | select BITREVERSE |
212 | ---help--- | 212 | help |
213 | This provides an MTD device driver for the M-Systems DiskOnChip | 213 | This provides an MTD device driver for the M-Systems DiskOnChip |
214 | G3 devices. | 214 | G3 devices. |
215 | 215 | ||
diff --git a/drivers/mtd/lpddr/Kconfig b/drivers/mtd/lpddr/Kconfig index 3a19cbee24d7..a5a332fbd593 100644 --- a/drivers/mtd/lpddr/Kconfig +++ b/drivers/mtd/lpddr/Kconfig | |||
@@ -13,10 +13,10 @@ config MTD_QINFO_PROBE | |||
13 | depends on MTD_LPDDR | 13 | depends on MTD_LPDDR |
14 | tristate "Detect flash chips by QINFO probe" | 14 | tristate "Detect flash chips by QINFO probe" |
15 | help | 15 | help |
16 | Device Information for LPDDR chips is offered through the Overlay | 16 | Device Information for LPDDR chips is offered through the Overlay |
17 | Window QINFO interface, permits software to be used for entire | 17 | Window QINFO interface, permits software to be used for entire |
18 | families of devices. This serves similar purpose of CFI on legacy | 18 | families of devices. This serves similar purpose of CFI on legacy |
19 | Flash products | 19 | Flash products |
20 | 20 | ||
21 | config MTD_LPDDR2_NVM | 21 | config MTD_LPDDR2_NVM |
22 | # ARM dependency is only for writel_relaxed() | 22 | # ARM dependency is only for writel_relaxed() |
diff --git a/drivers/mtd/maps/Kconfig b/drivers/mtd/maps/Kconfig index bdc1283f30fb..afb36bff13a7 100644 --- a/drivers/mtd/maps/Kconfig +++ b/drivers/mtd/maps/Kconfig | |||
@@ -207,13 +207,13 @@ config MTD_ICHXROM | |||
207 | BE VERY CAREFUL. | 207 | BE VERY CAREFUL. |
208 | 208 | ||
209 | config MTD_ESB2ROM | 209 | config MTD_ESB2ROM |
210 | tristate "BIOS flash chip on Intel ESB Controller Hub 2" | 210 | tristate "BIOS flash chip on Intel ESB Controller Hub 2" |
211 | depends on X86 && MTD_JEDECPROBE && PCI | 211 | depends on X86 && MTD_JEDECPROBE && PCI |
212 | help | 212 | help |
213 | Support for treating the BIOS flash chip on ESB2 motherboards | 213 | Support for treating the BIOS flash chip on ESB2 motherboards |
214 | as an MTD device - with this you can reprogram your BIOS. | 214 | as an MTD device - with this you can reprogram your BIOS. |
215 | 215 | ||
216 | BE VERY CAREFUL. | 216 | BE VERY CAREFUL. |
217 | 217 | ||
218 | config MTD_CK804XROM | 218 | config MTD_CK804XROM |
219 | tristate "BIOS flash chip on Nvidia CK804" | 219 | tristate "BIOS flash chip on Nvidia CK804" |
@@ -401,12 +401,12 @@ config MTD_PISMO | |||
401 | When built as a module, it will be called pismo.ko | 401 | When built as a module, it will be called pismo.ko |
402 | 402 | ||
403 | config MTD_LATCH_ADDR | 403 | config MTD_LATCH_ADDR |
404 | tristate "Latch-assisted Flash Chip Support" | 404 | tristate "Latch-assisted Flash Chip Support" |
405 | depends on MTD_COMPLEX_MAPPINGS | 405 | depends on MTD_COMPLEX_MAPPINGS |
406 | help | 406 | help |
407 | Map driver which allows flashes to be partially physically addressed | 407 | Map driver which allows flashes to be partially physically addressed |
408 | and have the upper address lines set by a board specific code. | 408 | and have the upper address lines set by a board specific code. |
409 | 409 | ||
410 | If compiled as a module, it will be called latch-addr-flash. | 410 | If compiled as a module, it will be called latch-addr-flash. |
411 | 411 | ||
412 | endmenu | 412 | endmenu |