summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorTom Rini <[email protected]>2022-07-23 13:05:00 -0400
committerTom Rini <[email protected]>2022-08-04 16:18:47 -0400
commit5d68d2f41df5099f890052756f14f5a810f34312 (patch)
tree2481188e8c651c8da0acb1890fad4a670bb3e1a0 /README
parent90e9b3d3353300bc65fbd7f400228926ee61b30c (diff)
Convert CONFIG_SYS_FLASH_ERASE_TOUT et al to Kconfig
This converts the following to Kconfig: CONFIG_SYS_FLASH_ERASE_TOUT CONFIG_SYS_FLASH_LOCK_TOUT CONFIG_SYS_FLASH_UNLOCK_TOUT CONFIG_SYS_FLASH_WRITE_TOUT In practice, for two m68k platforms we move to hard-coding with a comment the timeout values, rather than try and make convoluted Kconfig logic. We add options for the write and erase options to the pic32 flash driver, as this driver does make use of them. Everywhere else these are unreferenced values. Signed-off-by: Tom Rini <[email protected]>
Diffstat (limited to 'README')
-rw-r--r--README12
1 files changed, 0 insertions, 12 deletions
diff --git a/README b/README
index 8a50bf645cb..697b0d3a357 100644
--- a/README
+++ b/README
@@ -1731,18 +1731,6 @@ Configuration Settings:
- CONFIG_SYS_MAX_FLASH_SECT:
Max number of sectors on a Flash chip
-- CONFIG_SYS_FLASH_ERASE_TOUT:
- Timeout for Flash erase operations (in ms)
-
-- CONFIG_SYS_FLASH_WRITE_TOUT:
- Timeout for Flash write operations (in ms)
-
-- CONFIG_SYS_FLASH_LOCK_TOUT
- Timeout for Flash set sector lock bit operation (in ms)
-
-- CONFIG_SYS_FLASH_UNLOCK_TOUT
- Timeout for Flash clear lock bits operation (in ms)
-
- CONFIG_SYS_FLASH_PROTECTION
If defined, hardware flash sectors protection is used
instead of U-Boot software protection.