bnxt_en: Wait longer for the firmware message response to complete.
authorMichael Chan <michael.chan@broadcom.com>
Thu, 21 Feb 2019 00:07:32 +0000 (19:07 -0500)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 23 Mar 2019 19:09:52 +0000 (20:09 +0100)
commit29e4bfbc79b44a49f435592cea95db0b4ff51897
treefbcf3d318ac3786ea4523b74baae45a12aa966d6
parentb4baeab7e084af2cf55c9c1ec97214fa9c2afcf4
bnxt_en: Wait longer for the firmware message response to complete.

[ Upstream commit 0000b81a063b5f3ab82fa18041c28327ce72c312 ]

The code waits up to 20 usec for the firmware response to complete
once we've seen the valid response header in the buffer.  It turns
out that in some scenarios, this wait time is not long enough.
Extend it to 150 usec and use usleep_range() instead of udelay().

Fixes: 9751e8e71487 ("bnxt_en: reduce timeout on initial HWRM calls")
Signed-off-by: Michael Chan <michael.chan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/net/ethernet/broadcom/bnxt/bnxt.c
drivers/net/ethernet/broadcom/bnxt/bnxt.h