Commit 35697764 authored by Dirk van der Merwe's avatar Dirk van der Merwe Committed by David S. Miller

nfp: nsp: set higher timeout for flash bundle

The management firmware now supports being passed a bundle with
multiple components to be stored in flash at once. This makes it
easier to update all components to a known state with a single
user command, however, this also has the potential to increase
the time required to perform the update significantly.

The management firmware only updates the components out of a bundle
which are outdated, however, we need to make sure we can handle
the absolute worst case where a CPLD update can take a long time
to perform.

We set a very conservative total timeout of 900s which already
adds a contingency.
Signed-off-by: default avatarDirk van der Merwe <dirk.vandermerwe@netronome.com>
Reviewed-by: default avatarJakub Kicinski <jakub.kicinski@netronome.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent 34541513
...@@ -799,10 +799,7 @@ int nfp_nsp_write_flash(struct nfp_nsp *state, const struct firmware *fw) ...@@ -799,10 +799,7 @@ int nfp_nsp_write_flash(struct nfp_nsp *state, const struct firmware *fw)
{ {
.code = SPCODE_NSP_WRITE_FLASH, .code = SPCODE_NSP_WRITE_FLASH,
.option = fw->size, .option = fw->size,
/* The flash time is specified to take a maximum of 70s .timeout_sec = 900,
* so we add an additional factor to this spec time.
*/
.timeout_sec = 2.5 * 70,
}, },
.in_buf = fw->data, .in_buf = fw->data,
.in_size = fw->size, .in_size = fw->size,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment