diff options
Diffstat (limited to 'drivers/mtd/chips/Kconfig')
| -rw-r--r-- | drivers/mtd/chips/Kconfig | 21 |
1 files changed, 0 insertions, 21 deletions
diff --git a/drivers/mtd/chips/Kconfig b/drivers/mtd/chips/Kconfig index 0f6bb2e625d8..a7ec5954caf5 100644 --- a/drivers/mtd/chips/Kconfig +++ b/drivers/mtd/chips/Kconfig | |||
| @@ -200,27 +200,6 @@ config MTD_CFI_AMDSTD | |||
| 200 | provides support for one of those command sets, used on chips | 200 | provides support for one of those command sets, used on chips |
| 201 | including the AMD Am29LV320. | 201 | including the AMD Am29LV320. |
| 202 | 202 | ||
| 203 | config MTD_CFI_AMDSTD_RETRY | ||
| 204 | int "Retry failed commands (erase/program)" | ||
| 205 | depends on MTD_CFI_AMDSTD | ||
| 206 | default "0" | ||
| 207 | help | ||
| 208 | Some chips, when attached to a shared bus, don't properly filter | ||
| 209 | bus traffic that is destined to other devices. This broken | ||
| 210 | behavior causes erase and program sequences to be aborted when | ||
| 211 | the sequences are mixed with traffic for other devices. | ||
| 212 | |||
| 213 | SST49LF040 (and related) chips are know to be broken. | ||
| 214 | |||
| 215 | config MTD_CFI_AMDSTD_RETRY_MAX | ||
| 216 | int "Max retries of failed commands (erase/program)" | ||
| 217 | depends on MTD_CFI_AMDSTD_RETRY | ||
| 218 | default "0" | ||
| 219 | help | ||
| 220 | If you have an SST49LF040 (or related chip) then this value should | ||
| 221 | be set to at least 1. This can also be adjusted at driver load | ||
| 222 | time with the retry_cmd_max module parameter. | ||
| 223 | |||
| 224 | config MTD_CFI_STAA | 203 | config MTD_CFI_STAA |
| 225 | tristate "Support for ST (Advanced Architecture) flash chips" | 204 | tristate "Support for ST (Advanced Architecture) flash chips" |
| 226 | depends on MTD_GEN_PROBE | 205 | depends on MTD_GEN_PROBE |
