diff options
| author | Igor Russkikh <irusskikh@marvell.com> | 2020-02-14 18:44:52 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2020-02-16 19:03:39 -0800 |
| commit | e7b5f97e6574dc4918e375d5f8d24ec31653cd6d (patch) | |
| tree | 738695e1b2b35ec1506640fdff5453571a17472d /drivers/mmc | |
| parent | 15beab0a9d797be1b7c67458da007a62269be29a (diff) | |
| download | linux-e7b5f97e6574dc4918e375d5f8d24ec31653cd6d.tar.gz linux-e7b5f97e6574dc4918e375d5f8d24ec31653cd6d.tar.bz2 linux-e7b5f97e6574dc4918e375d5f8d24ec31653cd6d.zip | |
net: atlantic: check rpc result and wait for rpc address
Artificial HW reliability tests revealed a possible hangup in
the driver. Normally, when device disappears from bus, all
register reads returns 0xFFFFFFFF.
At remote procedure invocation towards FW there is a logic
where result is compared with -1 in a loop.
That caused an infinite loop if hardware due to some issues
disappears from bus.
Add extra result checks to prevent this.
Signed-off-by: Dmitry Bogdanov <dbogdanov@marvell.com>
Signed-off-by: Igor Russkikh <irusskikh@marvell.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/mmc')
0 files changed, 0 insertions, 0 deletions