| commit | 89b872e2e476833cde8aaac658c75817f67e8f81 | |
| author | Lennert Buytenhek <buytenh@wantstofly.org> | |
| Mon, 30 Nov 2009 17:13:20 +0000 (30 18:13 +0100) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Mon, 7 Dec 2009 21:51:21 +0000 (7 16:51 -0500) | ||
| tree | f8f5d70e9f933e75fbf3a1070dd077c9958deb46 | treesnapshot (tar.gz zip) |
| parent | 7e1112d34aea10fdd689422e6bdc918309043bf3 | commitdiff |
mwl8k: increase firmware loading timeouts
The time between loading the helper image and starting to upload the
main firmware image should be at least 5 ms or so. We were doing an
msleep(1) before, and 1 ms appears to not be enough in almost all
cases, but building with HZ=100 has always masked this so far. Bumping
the msleep argument to 5 fixes firmware loading e.g. when HZ=1000.
Some firmware images need more than 200ms to initialize. Bump the
ready code timeout to 500ms to accommodate for this.
Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
The time between loading the helper image and starting to upload the
main firmware image should be at least 5 ms or so. We were doing an
msleep(1) before, and 1 ms appears to not be enough in almost all
cases, but building with HZ=100 has always masked this so far. Bumping
the msleep argument to 5 fixes firmware loading e.g. when HZ=1000.
Some firmware images need more than 200ms to initialize. Bump the
ready code timeout to 500ms to accommodate for this.
Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
| drivers/net/wireless/mwl8k.c | diffblobblamehistory |