diff options
| author | Tom Rini <trini@konsulko.com> | 2022-07-23 20:05:00 +0300 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2022-08-04 23:18:47 +0300 |
| commit | 5d68d2f41df5099f890052756f14f5a810f34312 (patch) | |
| tree | 2481188e8c651c8da0acb1890fad4a670bb3e1a0 /board/cobra5272 | |
| parent | 90e9b3d3353300bc65fbd7f400228926ee61b30c (diff) | |
| download | u-boot-5d68d2f41df5099f890052756f14f5a810f34312.tar.xz | |
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 <trini@konsulko.com>
Diffstat (limited to 'board/cobra5272')
| -rw-r--r-- | board/cobra5272/flash.c | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/board/cobra5272/flash.c b/board/cobra5272/flash.c index 4337f4879d..5d15ed4e69 100644 --- a/board/cobra5272/flash.c +++ b/board/cobra5272/flash.c @@ -200,8 +200,8 @@ int flash_erase(flash_info_t *info, int s_first, int s_last) do { result = *addr; - /* check timeout */ - if (get_timer(start) > CONFIG_SYS_FLASH_ERASE_TOUT) { + /* check timeout, 1000ms */ + if (get_timer(start) > 1000) { MEM_FLASH_ADDR1 = CMD_READ_ARRAY; chip1 = TMO; break; @@ -289,8 +289,8 @@ static int write_word(flash_info_t *info, ulong dest, ulong data) do { result = *addr; - /* check timeout */ - if (get_timer(start) > CONFIG_SYS_FLASH_ERASE_TOUT) { + /* check timeout, 1000ms */ + if (get_timer(start) > 1000) { chip1 = ERR | TMO; break; } |